As more and more organizations transition to next generation communication networks, they are quickly finding out that today’s networks are becoming more and more complex. Today’s UC networks are built off of a multi-vendor architecture and enables multimodal communications that can be accessed from anywhere, corporate LAN, home network, mobile network or even public WiFi.
The shift from traditional telephony platforms to Unified Communications (UC) has put organizations in more of a consumption model, which is causing a shift in how UC is supported. The concept of a call server or PBX is really going away, as all the functions of a UC environment – voice, video and collaboration – are more and more distributed. This trend causes server monitoring and availability to be de-emphasized.
If the mere mention of MOS (Mean Opinion Score) conjures up some high level sales terminology that’s meant to gloss over the details and provides little impact to troubleshooting VoIP QoS, then don’t worry because you are not alone. Over the past few years, I’ve noticed a growing trend amongst our technology peers who have similar feelings when discussing MOS as a factor of visibility to VoIP networks. Most anecdotal responses to my queries of dismissal end in “…I can’t fix my network using MOS.” So I ponder the dismissal; Has the audience expertise surpassed the oversimplified value of MOS? Has MOS outgrown it’s value in how we operate our VoIP networks? or is there something more subtle creating the perception of dismissal?