WebRTC Solutions Featured Article

Sipwise and T-Labs WebRTC Platform Partnership: RTC:engine Ready for Market

August 05, 2015

If you are not aware of Austrian software manufacturer Sipwise and Deutsche Telekom's T-Labs collaboration the WebRTC-based RTC:engine, you may wish to check in on what the partners have been up to recently.  Not only have they concluded a cooperation agreement for marketing and developing the communication solution RTC:engine, but they also have committed to further develop the T-Labs software platform ComX with RTC:engine. 

Image via Shutterstock

Under the agreement, Deutsche Telekom will provide marketing support for the products, and Sipwise will assume technical, sales and commercial responsibility. And as a continuation of the joint development activities that led to the creation of RTC:engine, Deutsche Telekom (DT) will continue to provide support by contributing personnel and know-how. Sipwise includes the solution in their product portfolio and will provide vertical products and solutions (like call center, e-learning, etc.) on top. 

Revving up the RTC:engine

So what is the RTC:engine?  The short answer is that it is a virtual WebRTC gateway API, which allows communication providers (CSPs) to offer a full suite of WebRTC functionality via an in-broswer experience. 

A bit more technical answer as explained by Sipwise is: “RTC:engine both back-end technology for high performance signaling and media routing, and web services and CDKs, allowing easy front-end application development in HTML5 for rapidly building cutting edge cloud communication applications.” 

As might be expected based the involvement of DT, the software-only approach encapsulating different signaling protocols and media handling in simple APIs focuses on on-premise scenarios that allow operators of RTC:engine to launch new services within their own private cloud infrastructure. In an insightful white paper on RTC:engine Sipwise cites the key USP of the solution as, “its capability to extend traditional communication infrastructure like SIP and XMPP services and enrich it with purely web-based scenarios in a very short time-to-market, without the need to dive into low level APIs or protocols.”

The full paper is worth a read as it covers such things as new use cases (cloud telco, smart video sharing in call centers, and multi-party video conferencing and collaboration), the relationship of RTC:engine and WebRTC, mobility, native apps and support of third party components. A taste of this can be seen in the graphic below on mixing and matching.

Source: Sipwise

The reason the above caught my attention obviously is that list at the bottom. As I have mentioned in previous articles on the community the objective for WebRTC, or any communications capability for that matter, is interoperability. The reason is simple and historically demonstrable, i.e., all boats really do rise when the tide comes in and interoperability is the tide. It is one of the reasons Apple’s refusal to support WebRTC is so galling on the one hand, and is a driver of support for open source solutions throughout ICT on the other.

If WebRTC is to fulfill its promise, all of the charts from all of the solutions providers need to look like the one above with only the names changed for illustration purposes. It is one of the reasons why the participation of DT in all of this is so important as the use cases need to cover all possible real-time scenarios for maximum monetization for everyone.  

Edited by Maurice Nagle

Article comments powered by Disqus