Sponsored By

Microsoft OCS and Telephony: Please Don't Shoot the Messenger (Again)Microsoft OCS and Telephony: Please Don't Shoot the Messenger (Again)

There's been a whole lotta analyst hatin' over on this other NoJitter thread, so please forgive me for being a bit nervous about returning to the topic of Microsoft as a developer of telephony software. I'll overlook all those disparaging remarks made about my fellow analysts. (After all, I disparage them all the time!) Instead I want to focus on the contention Microsoft lacks the ability to provide the most basic core telephony functions and because of this the company should not be referenced in the Mystic Dodecahedron ... or whatever Gartner calls that report of theirs.

Brian Riggs

August 18, 2008

2 Min Read
No Jitter logo in a gray background | No Jitter

There's been a whole lotta analyst hatin' over on this other NoJitter thread, so please forgive me for being a bit nervous about returning to the topic of Microsoft as a developer of telephony software. I'll overlook all those disparaging remarks made about my fellow analysts. (After all, I disparage them all the time!) Instead I want to focus on the contention Microsoft lacks the ability to provide the most basic core telephony functions and because of this the company should not be referenced in the Mystic Dodecahedron ... or whatever Gartner calls that report of theirs.

There's been a whole lotta analyst hatin' over on this other NoJitter thread, so please forgive me for being a bit nervous about returning to the topic of Microsoft as a developer of telephony software. I'll overlook all those disparaging remarks made about my fellow analysts. (After all, I disparage them all the time!) Instead I want to focus on the contention Microsoft lacks the ability to provide the most basic core telephony functions and because of this the company should not be referenced in the Mystic Dodecahedron ... or whatever Gartner calls that report of theirs.Last time I checked the Office Communications Server documentation, basic core telephony were in no way lacking from the software. Though typically deployed as an adjunct to a PBX, OCS can just as easily be set up as a standalone voice platform. In such a scenario, OCS provides call control, allowing users to make and receive calls without connecting to a PBX. Users can also put calls on hold, forward them, and set up audio conferences. Phones - of both the deskset and soft phone variety - are connected directly to OCS. There's some basic IVR-like capabilities courtesy of Speech Server. DTMF tones can be generated. Voice mail and auto attendant software is available from Exchange 2007. A third-party media gateway provides connectivity to the PSTN.

To be honest, this is not the most impressive of feature lists, particularly when compared with the hundreds of really snazzy voice features available on your run-of-the-mill PBX. But - maintaining this theme of honesty - these are in fact core telephony functions. So if you ask me, the problem is not that Microsoft's unified communications solution lacks the most basic core telephony functions. The problem is that basic telephony functions are all that OCS can presently provide, at least when it comes to voice features. Until Microsoft can provide more than these most basic of telephony functions, businesses will not take OCS seriously as an alternative to a traditional PBX. I fully expect this to change going forward ... and, frankly, so should you. Just please don't shoot the messenger.

About the Author

Brian Riggs

Brian is a member of Ovum's Enterprise team, tracking emerging trends, technologies, and market dynamics in the unified communications and collaboration (UC&C) space. He looks at the market for both hosted UC&C services offered by service providers and UC&C solutions deployed on premise within the enterprise. Before joining Ovum, Brian for 12 years tracked the UC market for Current Analysis.