Companies such as Microsoft are shifting their revenue mix to services. In such a business model, opening the service to developers to integrate with is a power multiplier, not in R&D resources but in creativity and innovation. That is a paradigm shift from POBX vendors closing their system for their phones only to making it as open as possible.
ORTC is a pretty hot topic on the technology side of WebRTC. Many still see it as a competing technology to WebRTC and therefore are worried it will delay adoption of WebRTC. On the other hand, some are not clear technically what new capabilities ORTC brings and what are the challenges associated with it. In a very high level, it is not correct to compare ORTC with WebRTC but rather to compare it to SDP.
ORTC is not a wildcard anymore. It was originally pushed by Hookflash and Microsoft but today Google is part of this initiative and eventually it will find its way into the standard. 4 takeaways: WebRTC is gradually adding ORTC functionalities into it. It is not the full ORTC story but just some parts of it. ORTC is all about setting and getting media parameters…
Last Friday the official word came out. ORTC API is now available in Microsoft Edge with current focus on audio and video communication. The support is currently in the Windows Insider Preview release. Microsoft now claims to be enabling seamless communication experiences for the web with Skype, but is it really seamless? Let’s take a closer look at what exactly is being provided and more importantly, where are the pitfalls.
In this issue we cover W3C related work including: Constrainable properties – What are they and where are they used?; getUserMedia sources; Low-level media control and information; Control over DTLS-SRTP keys; WebRTC statistics; DTMF support
Last year when I spoke with some large vendors and service providers, a common answer to “What are you doing with WebRTC?” was – “We are looking at it”.