Unified Communications

10:17 AM
Eric Krapf
Eric Krapf
Commentary
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Microsoft For Corporate Telephony?

There's been a lot of buzz over at No Jitter about the most recent Gartner report in the area of IP telephony/Unified Communications, in which Gartner gave a spot in its coveted Magic Quadrant to Microsoft. What drove the commentary was the fact that Microsoft made the Magic Quadrant for Corporate Telephony, an area in which

There's been a lot of buzz over at No Jitter about the most recent Gartner report in the area of IP telephony/Unified Communications, in which Gartner gave a spot in its coveted Magic Quadrant to Microsoft. What drove the commentary was the fact that Microsoft made the Magic Quadrant for Corporate Telephony, an area in which most observers have seen Microsoft coming up short, at least relative to the incumbent vendors, in terms of feature/function.Of course, there was the requisite Gartner-bashing, but underneath the sound and fury was a debate about what "corporate telephony" means now, and what it is evolving to mean.

As Brian Riggs pointed out in a follow-up post, you really don't find anyone arguing that Microsoft Office Communications Server (OCS) can replace a TDM or IP PBX, feature for feature. That's because everybody knows it can't. This is all about where your investments should be placed as you move forward.

One of our commenters made a point that I think is worthy of further discussion:

Interestingly, the [Gartner] report states that Microsoft OCS is being deployed by customers for remote and nomadic workers, people who spend most or all of their time away from a desk (e.g., working from home, on the road, etc.). For these people you don't need some of the features that OCS is missing today, such as E911, (but is meant to have soon).

That comment may give us a glimpse of one means by which OCS may work its way into enterprise telephony. As long as you have main corporate locations, you'll need PBX features for these. But remote and nomadic work, while certainly something that has been in existence for awhile, could become a lot more important than they are even now. As rising energy costs foster more telework, this segment of workers may become more than the afterthought that they currently are. Enterprise procurements may treat teleworkers as truly part of the extended campus, in terms of feature/function and connectivity requirements.

Does that automatically lead to OCS? Of course not. Your incumbent PBX vendors are building solutions that incorporate presence, unified messaging, video, and the host of supporting technologies that make up UC; and of course IBM Lotus counters OCS with its Sametime.

But the bottom line is that corporate telephony always has evolved, and its continued evolution will take it in the direction of Unified Communications.

Comment  | 
Print  | 
More Insights
Cartoon
Slideshows
Audio Interviews
Archived Audio Interviews
Jeremy Schulman, founder of Schprockits, a network automation startup operating in stealth mode, joins us to explore whether networking professionals all need to learn programming in order to remain employed.
White Papers
Register for Network Computing Newsletters
Current Issue
2014 State of Unified Communications
2014 State of Unified Communications
If you thought consumerization killed UC, think again: 70% of our 488 respondents have or plan to put systems in place. Of those, 34% will roll UC out to 76% or more of their user base. And there’s some good news for UCaaS providers.
Video
Twitter Feed