Quobis is announcing the general availability of the API Sippo.js running on top of the Sippo WebRTC Application Controller. This API has been designed to expose network functionalities of service providers and help web developers to add real time communications features to existing or new web applications.
Different vendors are offering proprietary client-side APIs or SDK to help web developers to create their applications. While this is an acceptable option where a vendor is a long-term provider, there are different scenarios where a standard interface is preferred. Avoid vendor lock-in is one of the key points to prevent spurious dependences when you want to add or remove services or change vendors. Another key point is to help web developers to code once and make the application run in any ecosystems, with no specific adaptations.
There are different standardization bodies and associations that are looking to have some defined standard methods in a API to integrate all the UC mechanisms involved in RTC web applications. The Device Solution Initiative (or DSI group) of the ATIS (http://www.atis.org/dsi) is defining a method called ORCA.js to expose the value of the network to devices and applications by reducing complexity in the adoption of network APIs by web developers. The goal is to provide application developers with network-agnostic, client-side APIs that simplify the access to the network. This way, web developers can develop applications via this API, that can handle with WebRTC functionalities in an easy way, with no need to have a deep knowledge of WebRTC standards and protocols.
ORCA.js initiative is supported by large network equipment vendors like Alcatel-Lucent and Ericsson and tier-1 telcos and service providers like AT&T, Verizon, CenturyLink or Sprint. We can foresee a way where the same network applications can work with any of these service providers and telcos with no adaptations or changes.
Sippo.js adopts all the methods defined in the orca.js initiative to have full compatibility and add new ones to enhance user experience, make easier the interconnection with the core network, manage user provisioning and add multimedia capabilities.
Sippo WebRTC Application Controller (or WAC) hosts and manages all the WebRTC applications developed on top of this API. Sippo.js takes advantage of the features of the WebRTC Application Controller like handling all the complexity behind the different signaling, browser implementation and user devices.
Ask your sales representative to get a full list of all the methods implemented in the Sippo.js API or visit Telecom API on October 7-9 in London (UK) http://telecomapis-advanced.com/