SHARE



ABOUT THE AUTHOR


Andrew Davis
Andrew W. Davis is a researcher, analyst, and opinion leader in the field of collaboration and conferencing. He is a...
Read Full Bio >>
SHARE



Andrew Davis | March 13, 2012 |

 
   

Cisco Redefines Chutzpah

Cisco Redefines Chutzpah Though it's now opposing a proprietary Microsoft-Skype combination, supporting standards wasn't always Cisco's goal.

Though it's now opposing a proprietary Microsoft-Skype combination, supporting standards wasn't always Cisco's goal.

Last month's bold move by Cisco, appealing to the European Commission to impose restrictions on the already approved Microsoft-Skype merger, brings new meaning to the technical term "chutzpah" in the IP communications world. It also promises to make our upcoming session on "Interoperability--What is it and how do you get it" (27 March 8:00am) a potential fisticuffs experience at Enterprise Connect.

Those who have followed the videoconferencing industry for any length of time will be very familiar with the history of mergers/acquisitions, lawsuits, patent claims, and outright hostility between competitors. But fundamentally the issue since the 1980s has been the dynamic tension between industry standards, which in the communications world are defined by the Geneva-based ITU's Recommendations, and proprietary protocols, which most developers feel provide superior performance for their own products. Theoretically, products that comply with industry standards can interoperate. (Interoperability and standards have been the core religion in fax and telephony since 1886.)

In reality, this is mostly true for videoconferencing, but not always; and when it is true, it doesn't always give the best result--i.e., systems from different vendors can connect, but may not provide the optimum quality of experience. Systems that are not interoperable cannot connect at all. Further complicating the videoconferencing scene (and UC as well) is that the nice thing about standards is that there are so many to choose from.

Some "protocols" or solutions become industry standards by default. A classic example is Microsoft Windows, clearly a proprietary technology, but so dominant that it is essentially an industry standard. Skype would fall into this category as well. While it's true that Skype is proprietary, the fact that it is being used by over 170 million users worldwide makes it almost an industry de facto standard. And the fact that it can be downloaded for free makes the argument even more persuasive.

In the videoconferencing industry today, we have many protocol islands, some of which are standards-compliant, like H.323; others are on their way to standardization, like SIP. Others are large, like Skype, and others are small but growing fast, like Microsoft Lync, and Apple's FaceTime. Users can talk to other users on the same island, but cannot communicate with users on other islands unless a special gateway is available within the enterprise or via a service provider. Gateways generally introduce cost, scalability and performance issues that are not present when "native" interoperability is possible.

This brings us to the current Cisco-Skype situation and raises at least three questions: Why is Cisco doing this now? What does Cisco hope to achieve by this appeal? And how can we not see this as an example of hypocrisy on the part of the world's largest telecommunications equipment provider?





COMMENTS



April 19, 2017

Now more than ever, enterprise contact centers have a unique opportunity to lead the way towards complete, digital transformation. Moving your contact center to the cloud is a starting point, quick

April 5, 2017

Its no secret that the cloud offers significant benefits to enterprises - including cost reduction, scalability, higher efficiency, and more flexibility. If your phone system and contact center are

March 22, 2017

As today's competitive business environments push workforces into overdrive, many enterprises are seeking ways of streamlining workflows while optimizing productivity, business agility, and speed.

April 20, 2017
Robin Gareiss, president of Nemertes Research, shares insight gleaned from the firm's 12th annual UCC Total Cost of Operations study.
March 23, 2017
Tim Banting, of Current Analysis, gives us a peek into what the next three years will bring in advance of his Enterprise Connect session exploring the question: Will there be a new model for enterpris....
March 15, 2017
Andrew Prokop, communications evangelist with Arrow Systems Integration, discusses the evolving role of the all-important session border controller.
March 9, 2017
Organizer Alan Quayle gives us the lowdown on programmable communications and all you need to know about participating in this pre-Enterprise Connect hackathon.
March 3, 2017
From protecting against new vulnerabilities to keeping security assessments up to date, security consultant Mark Collier shares tips on how best to protect your UC systems.
February 24, 2017
UC analyst Blair Pleasant sorts through the myriad cloud architectural models underlying UCaaS and CCaaS offerings, and explains why knowing the differences matter.
February 17, 2017
From the most basics of basics to the hidden gotchas, UC consultant Melissa Swartz helps demystify the complex world of SIP trunking.
February 7, 2017
UC&C consultant Kevin Kieller, a partner at enableUC, shares pointers for making the right architectural choices for your Skype for Business deployment.
February 1, 2017
Elka Popova, a Frost & Sullivan program director, shares a status report on the UCaaS market today and offers her perspective on what large enterprises need before committing to UC in the cloud.
January 26, 2017
Andrew Davis, co-founder of Wainhouse Research and chair of the Video track at Enterprise Connect 2017, sorts through the myriad cloud video service options and shares how to tell if your choice is en....
January 23, 2017
Sheila McGee-Smith, Contact Center/Customer Experience track chair for Enterprise Connect 2017, tells us what we need to know about the role cloud software is playing in contact centers today.