If reading the title of this article only brought to mind a whale, it’s time to learn more. WebRTC has not one, but two different and totally distinct ORCA projects. Here is what they mean for both WebRTC and the telecom industry as a whole.
There are several complaints with the current WebRTC API, namely the necessity of using session description protocol (SDP) with its complexity and traditional-telephony design for newer, more advanced applications. To address these issues, W3C is implementing many of concepts initially proposed by Microsoft more than a year ago in its CU-RTC-Web proposal for WebRTC. Importantly, this group includes many active participants, including Google. ORTC is very much a work in progress, but it includes a “shim” to provide backward compatibility with the existing WebRTC API. Many who are involved in WebRTC’s standardization believe it is very likely that parts or ORTC will find their way into version two of WebRTC specifications.
I have not come across too many implementations of this technology yet. Dialogic plays at the media layer, not the signaling plane where this sits. Still, I’m excited to report that our business partner Quobis is part of the steering board for this effort. You can check out our public demo that uses Quobis’ orca.js-compliant SIPPO WebRTC Application Controller.
Stay tuned, and should you have any questions in the meantime, please reach out to email@example.com.