IBM WebSphere Liberty Real-Time Communications and WebRTC
If you are still skeptical about the momentum WebRTC is gathering, particularly with developers with an eye on the enterprise, you need to rethink things. As noted in another posting this week about AT&T’s promotion of WebRTC on its developers site, readers are encouraged to check out and possibly bookmark the home of IBM’s WebSphere Liberty Real-Time Communications (Rtcomm) feature. As IBM says, “For those struggling to find a WebRTC platform that integrates well with your existing Web and mobile application infrastructure, you’ve come to the right place. If you’re frustrated with solutions that feel more like you’re installing a telephone network than adding a promising new enhancement to your existing Systems of Engagement, we feel your pain.”
Rather than spoil the enjoyment of replicating all of IBM’s encouragement to HTML5 developers who may know little about telephony, but should seize on WebRTC as a tool to generate significant value-added new services, below is a list of capabilities provided by WebSphere Liberty Rtcomm. It is comprehensive and includes:
Peer-to-peer calling – Set up an Rtcomm demo using the built in endpoint registry in minutes.
Call Queues -- Queues subscribed-on by agents and called-to by Web users.
Third-Party Call Control – Initiate calls from 3rd-party sources like IoT events.
Contextual Presence – Use context to locate endpoints to connect with.
Real-Time Messaging – Exchange text, audio and video in real-time.
Gateway – Rtcomm-to-SIP gateway for federation with SIP Trunking, IMS and the PSTN.
SIP Servlet Programming Model – For developers wishing to drill deeper into the signaling.
Media server integration – Support for media server control via JSR 309 for multiway, record/playback of media and much more.
They even provide a link on how to enable and configure the Liberty Rtcomm feature.
One final thing of note that applies to everyone’s WebRTC efforts is that simplicity and interoperability are part of the pitch to developers. This happens to be why WebRTC is busy gaining traction. Indeed, as IBM notes, “While many features and functions can be derived from the Liberty Rtcomm feature with no backend programming, the feature also supports the ability to extend the base platform through the SIP Servlet (JSR 289) programming model and through services like third-party call control that are exposed via MQTT topics, and has been made to be cloud-friendly, and fast and easy to develop and deploy.
In short, whether it is communications service providers or enterprises, WebRTC is creating exciting opportunities for developers and clearly the time for developers to get with the program is now.
Edited by Rory J. Thompson