Usually this name is used to identify the human user for a RTC application. Generally identified with a contact center customer engagement role.
audiomixer (amx)
SIP back to back user agent used for SIP trunking interconnection. It is also mixes the audio of the conferences and calls the SIP trunking. It enables the adaptation to the particular needs of the SIP trunk. Currenlty implemented using Sangoma Asterisk
SDK provided by the community or the browser vendors handle the access to media devices and the WebRTC API. It provides the functionalities required to obtain the media that is transferred to the other side/party in order to achieve a real time communication. It is necessary to make sure that the application will work in different browsers and platforms.
Usually this name is used to identify the human user for a RTC application. Generally identified as the party that receives or consumes products or services.
Database (db)
A database is an organized collection of long-lasting data used by the different service to store the information which must be shared between service instances and be persistent across restarts.
Computer system in which a computer program or software component is deployed and executed.
Collection of physical elements that constitutes a computer system.
HTML5 application
The business logic application, the one that covers the interface between the user and the functionalities and cover the part that is not technologically related. It is the core of the use case.
Identity provider
Third party role that grants and assure the valid identity of an entity. Usually refer to this on certification and authentication procedures.
User access data to a specific feature or application.
message-broker (mb)
Messaging broker that handles communication of messages and events between independent internal Sippo services. Currently implemented using RabbitMQ
Collection of terminal nodes and connected links which allows computers to exchange data.
Standard authenitication protocol for double side proof of authentication.
oauth2-proxy (oa2p)
Service developed by Quobis to handle access delegation based on open standard OAuth2. It enables the authentication of SippoSDK applications and also plays the role of identifying the authentication provider based on its configuration. It also allows the Sippo solutions to handle non-standard OAuth2 access delegation systems by the implementation of ad-hoc custom modifications.
rec-post-proc (rpp)
Quobis development used to generate media recordings from the media captured in the sfu and audiomixer.
Infrastructure element that stores dynamic data about an endpoint and allows to identify and locate the network element and its proper unique ID.
REpresentational State Transfer Application Programming Interface. Set of protocols, routines and tools to coordinate two services or pieces of software.
Reverse-proxy (rp)
A type of proxy server that retrieves resources on behalf of a client from one or more servers. These resources are then returned to the client, appearing as if they originated from the proxy server itself.
Abbreviation of Real Time Communications
Service API –> Third party applications interface. This interface is used to communicate the Sippo wac with third party services or applications. For example, when federating the authentication via a OAuth2 connection.
Service provider
Third party or outsourced suppliers.
Network element to handle WebRTC media streams. It receives streams from each conference participant and forwards them to the rest of participants. It does not do media processing: it does not change neither the codec nor the bit rate and resolution of the video flows. It is able to play the WebRTC gateway role providing media interworking: WebRTC to SIP media profiles, DTLS-SRTP to RTP and timestamps modifications. When used with codecs which support Scalable Video Codec (SVC) it enables the delivery of flows different bit rates and resolutions to different endpoints based on defined rules.
Linked directly to the sfu, the wrapper grants connection between the sfu unit and the sfu-dispatcher to handle redundancy and scaling. It also receives direct connections from the applications in order to join to rooms and negotiate the characteristics of the media flows published and received.
Family of Quobis products dedicated to the RTC applications. Including the Sippo wac, Sippo collaborator and others.
Sippo application server (Sippo AS)
Entity that manages and implements all the application logic. The Sippo AS serves the WebRTC applications, to achieve some of its features the Sippo AS is integrated with third party elements to cover the signaling part of the WebRTC communication, and for other context actions, like authentication, recordings, storage and similar.
Sippo Connector
WAC service that uses a third party service (hosted at the same machine or at an external one) in order to provide a specific feature. Example: Google connectors provide Google Contacts and others.
Sippo ecco
Telco-class ready-to-use OTT client fully integrable with IMS, VoLTE, VoWifi and MVNO architectures and AAA elements.
Sippo hub
Enterprise-grade server that enables companies with customer-care applications based on multimedia real time communications to defeat the challenges of digital transformation while keeping the existing call center infrastructure.
Sippo wac
Telco-class real-time communication application server for the exposure of APIs. It provides tools for developers to create real-time communication apps while managing all the complexity related to device-fragmentation, AAA interconnection, service enablement and troubleshooting and user management
sippo-server (ss)
Quobis development that handles all the application logic and orchestration of different internal services of the Sippo solutions.
The SippoSDK acts as an application abstract layer to interact with the different services of the Sippo AS and provides the functionality to the HTML5 application. It provides the ability to implement the same application with different WebRTC gateway vendors. This avoids a vendor lock-in and provides extra functionalities in order to have freedom to choose the better technical solution for each use case.
Part of a computer system that consists of encoded information or computer instructions. On the present document we will refer to the developed solution to cover the customer requirements.
turn-server (turn)
Backend support for TURN protocol. This element implements connectivity protocols used to achieve real-time connectivity with endpoints which are behind NAT and restrictive firewalls. Currenlty implemented using coturn
Person using a generic system of a commercial product or service.
Javascript, Android and iOS SDK provided by the vendor of WebRTC gateway. This element is typically not open-sourced and implements proprietary protocols. It enables the interaction between Sippo SDK and the WebRTC infrastructure.
Communication between two locations by simultaneous two-way video and audio transmissions.
Abbreviation of WebRTC Application Controller
WAC API –> Sippo applications interface. It is the standard way to communicate a Sippo application with the Sippo AS (application server).
web-server (ws)
The primary function of a web server is to store, process and serve web pages to clients. The communication between client and server takes place using the Hypertext Transfer Protocol (HTTP). Pages delivered are most frequently HTML, which normally include images, CSS style sheets and Javascript files in addition to the text content. Currently implemented using NGINX
Web Real-Time Communication) is an API definition that supports browser-to-browser applications for voice calling, video chat, and P2P file sharing without the need of either internal or external plugins.
WebRTC Application Controller
Network element designed to expand the Application Server definition granting all required features for WebRTC applications.
xmpp-server (xmpp)
Messaging XMPP server to handle asynchronous message exchange between SippoSDK clients. Currently implemented using Prosody