What do WebEx QoS and Phone Troubleshooting have in Common?
If you read my previous blog then you’ll already know that the answer is Medianet. In Part 1 of this 2 Part blog series I discussed the new reverse Metadata capability, provided by a Cisco network, that allows an Enterprise to enable granular QoS marking for all the different media streams that make up a WebEx meeting. In this 2nd instalment, we’re going to take a look at how we can extend Medianet’s Mediatrace capability to Cisco’s 79XX, 89XX and 99XX IP Phone portfolio.
The other recent innovation for Medianet is Prime Collaboration’s ability to now invoke a Mediatrace for a number of IP Phones models that don’t support the MSI (Media Services Interface). As these devices cannot originate Metadata, it has been previously impossible start a Mediatrace through end point selection for telephones in Prime Collaboration. It is now possible, reactively and proactively, to troubleshoot voice quality issues on 79XX, 89XX and 99XX devices, using the same combination of Medianet and Prime Collaboration tools that have previously only been applicable to personal and room based video systems. Take a look at one of my previous blogs, “Medianet in Action”, for some additional background material on video troubleshooting. The demonstration below shows how to start a Mediatrace for a pair of phones.
What do WebEx QoS and Phone Troubleshooting have in Common?
The answer is Medianet, which in conjunction with a Cisco network can provide an innovative solution for two very different real life problems. In Part 1 of this 2 Part blog we’re going to discuss how customers can use Medianet Metadata to provide a robust QoS mechanism for the WebEx cloud service within their Enterprise Networks. Keep an eye out for Part 2 where we’re going to take a look at how we can extend Medianet’s Mediatrace capability to Cisco’s 79XX, 89XX and 99XX IP Phone portfolio. I’ll also point out the benefits for each of these completely different Medianet use cases.
WebEx is a SaaS Conferencing service providing web based data, audio and video conferencing for millions of users. As it’s a cloud service, it’s inherently secure and in a lot of use cases it will tunnel all its media streams within HTTPS. That’s great for secure transport, but it’s resultantly challenging to map the constituent parts of the WebEx application into a granular Enterprise QoS policy. Why would we want to do that anyway? Isn’t it good enough to mark all the WebEx traffic the same? As the saying goes, there is a method to our madness.The tunnelled WebEx traffic contains control packets, data-sharing traffic and possibly VoIP, which are relatively low bandwidth media streams. On the flip side any tunnelled video traffic will likely be bandwidth hungry by nature. The challenge we want to circumvent is how to ensure the WebEx video traffic does not “swamp” the other types of meeting traffic. Ultimately, we want to allow end users to enable the video service they have paid for, without the risk of video having a negative impact on the overall quality of the online conference. We do everything with the end user in mind to make sure you have the best possible experience.
For those of you that don’t know, a WebEx client can generate Medianet Metadata. In simple terms, Metadata is a way for a Cisco application to announce itself to a Cisco network. In the case of WebEx, different Metadata packets are transmitted onto the network, uniquely identifying all the component media streams (including video) that comprise a WebEx conference. This allows a Cisco network to useWebEx Metadata to differentiate between any WebEx traffic types, even when securely tunnelled over a HTTPS connection. The figure below provides an illustration of the different Metadata packets that will be generated for different types of WebEx traffic.
Figure 1 – Identifying Different Flows using Metadata
More people than ever are talking about “shadow IT” nowadays. As the name implies, it’s mysterious, perhaps even malevolent by some people’s standards. From a traditional IT vantage point, this negative view may be somewhat justified given the risks it creates around security, compliance, productivity, and technology investment.
But let’s look at it from another perspective. Shadow IT is on the rise because more people outside of IT are gaining awareness and access to technology, and harnessing it as a business differentiator. More importantly, many of these people are business leaders with growing budgets that align to their priorities. Here’s how much technology budget growth business leaders expect in the next year:
“Neither snow nor rain nor heat nor gloom of night stays these couriers from the swift completion of their appointed rounds.” – Popular US Postal Service motto
Many of my US colleagues have told me that they grew up hearing the phrase above and thinking how reliable their mail service is, even under the harshest conditions, they always got their mail. We in Cisco think that your network should be as reliable and resilient, and work under all conditions, particularly now when the Internet of Things (IoT) requires a level of resiliency at a scale never imagined before, and under conditions beyond what the traditional datacenter or wiring closet can offer.
These days, one of the challenges that the Internet of Things has to deal with is that it “…is already connecting the physical world today, but the real world, unlike the digital world, is much more uncertain and variable. We have to connect objects in unpredictable environments, often subject to Mother Nature or just the movement of our earth and its inhabitants…”
In fact Cisco defines the Internet of Things as “the intelligent connectivity of physical devices driving massive gains in efficiency, business growth and quality of life.”
In order to establish intelligent connectivity to physical devices, networking equipment have to be able to coexist in the same environmental in which the physical device are operating.
Very often, these physical devices are operating in harsh environments both from a temperature prospective (like in a smelting furnace or in a mining field located in Siberia), from a dustiness prospective (like in a cement production plant), from a vibrations prospective (like on a train or on a mining truck) etc.
To properly operate in these environments networking devices have to be specifically designed with highly ruggedized casing to protect the device’s internal components, and with specific connectors to avoid any possible water penetration or to get unplugged because of hard vibrations.