Thrupoint is now in beta with its WebRTC development program. Thrupoint Juice, as the program is known, focuses on simplifying the integration of WebRTC and SIP. Thrupoint Fusion Web also allows for the integration of WebRTC with legacy IP PBX and PSTN infrastructure, which enables organizations to leverage their existing assets while adding new capabilities.
David Jodoin, CIO at Thrupoint, is among the keynote speakers this week at the WebRTC Conference and Expo at the South San Francisco Conference Center.
“Enterprises are excited about WebRTC for any number of reasons, whether to reduce communications costs, transform interactions with customers, make video ubiquitous or provide remote workers with a thin client collaboration experience,” noted Jodoin. “The challenge and opportunity, however, is to extend this new technology to today’s corporate communication environments without forcing large-scale upgrades or infrastructure upheaval.”
Thrupoint Juice is aimed at Web developers who want to embed voice and video communications into Web apps as simply as possible; create mobile collaboration mashups for smartphones and tablets; integrate unified communications with enterprise and social apps like Salesforce, Facebook and LinkedIn; avoid thinking about signaling for Web-based collaboration; avoid intricacies of WebRTC API Connect WebRTC to traditional enterprise communication endpoints including VoIP, mobile and landline devices; and build communication-enabled apps to enhance B2C collaboration with customers.
As will be discussed in the December issue of TMC’s INTERNET TELEPHONY magazine, WebRTC allow real-time voice and video interactions to be launched from a Web browser, and without requiring special client software. The WebRTC standard, on which work is still being done, consists of a combination of APIs and a protocol.
The protocol part, an effort out of the Internet Engineering Task Force, comes into play to enable one person’s Web browser to communicate with the Web browser of another individual. The APIs, which allow a server to tell the browser what to do – are the fruits of the W3C’s labors.
WebRTC is expected to be included in Chrome and Mozilla Firefox browsers by the end of the first quarter of 2013. Ericsson is reportedly working on a WebRTC-enabled browser for iOS and Android-based mobile devices. And conventional wisdom is that other popular browsers will also include WebRTC in the not-too-distant future, likely by 2014.
Sajeel Hussain, vice president of product management and marketing for Thrupoint, recently told INTERNET TELEPHONY and Webrtcworld that his company over the last year has been developing a SIP-WebRTC gateway, RTP proxy, and WebRTC-based application mash ups of web-based applications.
“The SWIS extends WebRTC to SIP environments across UC vendors,” Hussain explained. “The RTP proxy converts between WebRTC RTP streams and RTP flows of SIP entities. When coupled with our Thrupoint Service Broker (session management) technology, we are able to address a number of use cases around SIP and WebRTC interoperability.”
Thrupoint has been working with customers, including several Fortune 100 firms (primarily in the financial services vertical), on a few uses cases involving WebRTC. One use case, for private banking, would give high-net-worth clients a unified UC experience on tablet devices with rich communication capabilities.
“Clients can see presence status of financial advisors and initiate IM chat, voice call, full screen H.264 video call or n-way conference,” said Hussain. “File sharing, non-persistent data streaming and visual voicemail are also rendered through this single interface. Voice and video are provided by Thrupoint’s SWIS and RTP proxy, and the tablet application leverages existing enterprise services for IM, presence, conferencing, etc. [This is] also relevant for [the] health care sector to do with physician-patient interactions.”
Other use cases on which Thrupoint and clients have been focused include a virtual support portal, and using federation of WebRTC with existing video and contact center infrastructure to provide collaborative retail customer experiences involving video kiosks, mobile banking and virtual tellers.
Edited by Braden Becker