Quobis, a seven-year-old Spanish company focused on security, interconnection and integration related to unified communications, came to WebRTC early.
About three years ago, Quobis started creating its own solutions, and the first product it designed was a softphone with special caller authentication capabilities. But there was a problem, says Iago Soto Mata, Quobis telecom engineer, who spoke to Webrtcworld this week at WebRTC Conference & Expo in Atlanta. That problem was that the phone needed to adapt to different operating systems. So Quobis looked around and discovered that WebRTC could help it reduce the problems in adapting the softphone for different operating systems.
Later on, Acme Packet asked Quobis to create a softphone for it. Quobis had at that moment all of the knowledge to do the job, so it created a corporate endpoint – this one with no special authentication methods – for Acme Packet. In doing this job, Quobis recognized an opportunity in the market related to interconnecting and allowing for interoperability between corporate endpoints and network elements such as session border controllers and media gateways, he says.
Image via Shutterstock
So a few months ago, Quobis unveiled something called SIPPO, a corporate WebRTC softphone used by corporate users but deployed by service providers, that can interoperate with network elements from any vendor. SIPPO supports SIP over Web circuits and also supports REST and other signaling methods. The solution has passed some interoperability tests with different vendors, some of which will be announced this week, and more that will come following that. SIPPO implements all UC methods – audio, video, Web chat, call recording, screen serving, file transfer, the ability to work with LDAP and address book (which can be stored locally or in the cloud). The solution, released a couple of months ago and now in pilot, can be priced based on the number of concurrent calls, or on the number of users.
Edited by
Rachel Ramsey
