The phrase Active Monitoring can mean many different things, ranging from a periodic ping to verify that a server is reachable, to an HTTP transaction to measure responsiveness of a website, to a multi-party voice transaction to determine the quality levels that users are experiencing. Today, I am going to focus on active voice transactions.
As we enter early summer, it’s time to take a look back at IAUG, as well as the third consideration for a migration to SIP: what happens once you go live. Prior posts in this series focused on design and core technology decisions and up through the point of testing just prior to go live, […]
Have you ever had something go wrong with your system? How do you find out people are having a bad experience while trying to use your enterprise communication system? Here are three ways I can think of – some of which less desirable than others.
WebRTC doesn’t come with a back end infrastructure, especially not one that can harmonize all the different protocols, codecs, various services and devices available today. CSPs however, are perfectly aligned to leverage their current IMS/PacketCable implementations to compliment the WebRTC services that they or their customers are looking to deploy.
Customers punish carriers who put them in the middle of back-end politics. Think that’s not true? Just read the news about the spat between Verizon, Netflix and its bandwidth provider, Cogent Communications.
Imagine how happy a mobile service provider (MSP) would be if instead of a customer calling in to complain “I’m having trouble with YouTube” they simply said “The video queuing mechanism on server SW-304 is overloaded.” The company could just fix the problem instead of transferring the call to an engineer to manually sort through the hundreds of possible factors that degrade service – all while the caller waits for an answer.