WebRTC is hot. Without doubt, it has been the buzzword of 2014 in the telecommunications industry. Reasonably so – it has high disruptive potential. WebRTC allows people and enterprises to connect with each other in real-time with chat, voice and video without having to rely on a telecommunications company or even being on the same OTT network.
To date, over 500 technology companies and service providers, including some most the industry’s most reputable names, have already joined the WebRTC ecosystem. It is clear: WebRTC is here to stay.
That said, WebRTC is a nascent standard. The technology has several limitations common to new technologies finding their place in existing technology ecosystems: browser support, codec limitations, or compatibility with legacy systems are some of the most commonly known. In addition to those challenges, WebRTC also has limitations unique to itself. WebRTC is a framework that enables Real Time Communications in the browser. It includes the fundamental technology building blocks including codecs, media processing capabilities, NAT, and firewall traversal mechanisms. But it doesn’t handle routing and addressing. As a result, when it comes to person-to-person calling, WebRTC will not replace the telephone network – through which billions of people can call each other through the use of telephone numbers, regardless of the type of phone network or operator.
But of course, telecommunications is not just about person-to-person calling. Specifically within the enterprise, there are several use cases where WebRTC currently has the capacity to add tremendous value by enriching business processes. At Voxbone, we strongly believe in the relevance of these use cases. That is why we have enabled WebRTC calling over our global IP backbone, adding quality of service and security to these use cases of WebRTC for the enterprise.
We noticed a lot of confusion about which WebRTC use case is suitable for what, and conversely, for which use cases it is not suitable for. So, we thought it would be useful to sum up these use cases in a white paper, explaining in detail their benefits as well as their limitations and how to surpass those limitations. To do this, we worked with Tsahi Levent-Levi at BlogGeek.Me.
The white paper can be downloaded here. Enjoy reading!
Dries holds a masters degree in economics from the University of Leuven and a postgraduate masters degree in ICT from the University of Namur.
Latest posts by Dries Plasman (see all)
- Cost-effective telephony makes it a small world after all - January 13, 2017
- Hanging on (to) the Telephone - November 22, 2016
- Do Your Homework: 5 Key Questions to ask before Picking A SIP Provider - October 28, 2016