Microsoft Unified Communications: part 4 (a brief note on Cisco, QoS and codecs)

This content is 16 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

As might be expected for a series of blog posts about the Microsoft view of Unified Communications (UC), it is heavily biased towards Microsoft products but I wanted to take a brief look at another major player in the unified communications space – Cisco. It should be said that I have very limited experience of Cisco’s UC offerings (only as an end user of their IP telephony products) but it’s worth highlighting the differences between the Microsoft and Cisco approaches.

Microsoft and Cisco are partners, but they are also competitors. Some googling suggests that Cisco and Microsoft’s VoIP products can be integrated but not always without challenges (Aaron Tiensivu’s post on integrating Microsoft Exchange and Cisco CallManager is just one example of such a challenge) but it should be considered that they have come to UC from different directions.

Cisco are a networking company and they have approached UC as a networking problem for which there is a networking solution. On the other hand, Microsoft are a software company – they have looked at the overall user experience an attempted to engineer a software solution.

Whilst Cisco concentrates on providing a VoIP solution that offers Quality of Service (QoS) and has grown out of PBX technology, Microsoft relies on codecs that are tolerant of poor network conditions to deliver what they refer to as Quality of Experience (QoE). Those with far more experience than I have commented that the Microsoft approach is sensible for calls that are routed across the Internet (where there is no QoS) but less so in an enterprise environment and Ed Horley made a very valid observation that network links, particularly WAN links, tend to be under-provisioned. I have to say that using the SCCP/UCM solution at work provides fantastic call quality but I also find that the Cisco IP Phone (running SIP) on my desk at home provides a great experience too and, at a recent event, Microsoft even compared their solution with Skype, citing this as a well-known example of a software solution that provides good call quality over variable consumer Internet connections (something which I was surprised to find when I was using Skype for a video call between the UK and Australia recently).

Microsoft’s general recommendation is to let the software select an appropriate codec and Office Communicator will constantly assess the available bandwidth and select an appropriate codec, even switching codecs and/or tuning parameters as required during a call.

The main concern is with voice traffic saturating network bandwidth at the expense of data – that’s where QoS can be used effectively – to manage the network.

In the final post in this series, I’ll wrap things up with some notes from my own OCS implementation last year.

2 thoughts on “Microsoft Unified Communications: part 4 (a brief note on Cisco, QoS and codecs)

  1. Good article Mark. I found your comment about Microsoft comparing OCS to Skype amusing since I have often made the same reference “OCS voice is like Skype with several layers of marketing”.

    When it comes the maturity of voice, I believe that OCS is about where the leaders such as Cisco, Avaya, Nortel, etc, were five or more years ago. I do not consider the voice services suitable for “enterprise class telephony”.

    As you mentioned their approach of using variable rate CODECs is well suited to a best-effort type service such as Skype. But, lack of QoS and Call Admission Control makes it unsuitable for large enterprise. I have been using best-effort voice services for the past eight years and as you mentioned the voice quality is great, MOST of the time. And that’s the difference. In enterprise-class telephony voice quality must great all of the time; even when network congestion occurs.

    I wrote an article a little while ago on the subject QoS and Admission Control are IPT Requirements – Even for OCS


  2. Hi Rick – glad you liked the article… I linked to you in the original post too – just after I wrote “Those with far more experience than I” ;-)

    You’re right though about enterprise call quality though. I often speak to a service desk in South Africa and, in stark contrast to our internal Cisco IP Phone system, the call quality is awful. In that case it’s poor lines, not VoIP codecs (I think) but I completely understand what you mean about needing great quality all of the time.

    In Microsoft’s defence, they are often a little way behind the market leaders (in many technology areas) but they tend to catch up fast… it will be interesting to see what the next version of OCS brings but I tend to think that even OCS 2007 is probably fine for small and medium sized enterprises who are looking to dip their toes in the water with regards to VoIP but don’t have a big budget. In the meantime, the big boys will carry on buying Cisco etc.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.