Hookflash Keynote: “The State of WebRTC” Enterprise Connect 2016 – Monday, March 7, 2016 – Orlando, Florida.

Hookflash is proud to keynote at Enterprise Connect, the leading conference and exhibition for enterprise IP Telephony, Converged Networks and Unified Communications in North America. Enterprise Connect brings corporate IT decision makers together with the industry’s vendors, analysts and consultants to focus on the issues central to enterprise networks and communications.

After several years of WebRTC development what is the state of the standard today? What are the implications of ORTC and it’s implementation by Google and Microsoft? Is WebRTC really bringing any new capabilities to the UC space? What is ready for use today, and what is still coming down the road? Are the video codec wars being resolved? What about the security issues that have been raised? Have they been solved? How do people develop WebRTC apps for mobile devices?

During this session we’ll answer all these questions and more as we discuss the current state of WebRTC technology.

Visit the site for registration and additional information.

What Developers Should Know About ORTC Versus WebRTC

Janet Wagner, of ProgrammableWeb, provides an in-depth and insightful analysis of ORTC and compares it to WebRTC.

The key difference between the ORTC API and the WebRTC 1.0 API is that the ORTC API is a lower-level JavaScript API that provides the same components as the WebRTC 1.0 API while allowing greater flexibility than what is currently available in the WebRTC 1.0 SDP interface. Developers can use the ORTC API to implement advanced capabilities such as layered video coding, simulcast, scalable video coding (SVC), and more. These capabilities can also be implemented using SDP in WebRTC 1.0. However, WebRTC 1.0 communication capabilities can be more difficult for developers to implement. A JavaScript API like the ORTC API, provides greater access to more controls. In WebRTC 1.0, modifying the same controls would require browser source code changes. ORTC is also taking the approach of JavaScript shim libraries; for example, ORTC allows a JavaScript-based shim (“upshim”) to be built on top of ORTC.js which would provide the same functionality of WebRTC 1.0 APIs, including the RTCPeerConnection API. It should also be noted that ORTC APIs do not replace WebRTC 1.0 APIs, but rather augment the existing SDP APIs in WebRTC 1.0 which have been integrated into millions upon millions of devices.

Read the full article at ProgrammableWeb.