Real Time Communications
Abstract the SIP Handling Using the Call API
The Call API is a management front-end for OpenSIPS 3.1+ SIP servers, aiming to abstract the SIP layer and to simplify the management of more advanced SIP call flows. Moreover, it enables event-driven architectures by providing real-time events on the handled call scenarios.
The OpenSIPS 3.1 major release is not just about one piece of software, rather an entire ecosystem! After the recently introduced opensips-cli console environment, aimed at improving the interaction with an OpenSIPS 3.0+ server, we are proud to introduce the Call API -- a responsive, fully asynchronous, high-throughput API, built to abstract all the complexity behind the more arcane SIP calling scenarios (think click-to-dial scenarios, blind transfers, attended transfers, etc.) into intuitive, easy-to-invoke JSON-RPC commands.
The first half of the presentation will include an architectural overview of the API. You will learn how to interact with it, how the API further interacts with the OpenSIPS backend, as well as some best practices on writing API clients in your favourite programming language.
In the second half, you will learn about the specific SIP scenarios exposed by the API, how they work behind the curtains and what kind of services you can build on top of them.
Additional information
| Type | devroom |
|---|
More sessions
| 2/6/21 |
Having been an advocate of free (as in freedom) communication systems for almost as long as I've been on the internet, the number of people I successfully converted away from proprietary networks was surprisingly low for a very long time. In this talk I will share the lessons I have learned while trying to implement (Prosody/Snikket), document (modernxmpp.org) and promote communication freedom to people.
|
| 2/6/21 |
Matrix (https://matrix.org) is an open protocol for secure, decentralised communication - defining an end-to-end-encrypted real-time communication layer for the open Web. Historically the network has been made up of newly written native Matrix clients, or bridges to 3rd party existing chat systems (e.g. Slack, Discord, Telegram). This year, however, we added production-grade native Matrix support for the first time to a major 3rd party chat system: Gitter (https://gitter.im) over the course of ...
|
| 2/6/21 |
Last year, the world changed, and musicians were among those that were hit the most, and music lovers with them. Can WebRTC help, here? This presentation will try to cover different areas where it could, and in some cases already is.
|
| 2/6/21 |
Exploring viable methods to build decentralized, secure, encrypted p2p tracing/logging/capture swarms using HEP and DHT to provide for the present and future needs of webRTC platforms and other next-generation real-time communication systems.
|
| 2/6/21 |
WebRTC means many things to many people. One of these things is the C++ library that is used to implement the WebRTC functionality such as audio, video and data channels in the Chrome browser. The library is a complex beast with more than a million lines of code and a history dating back to 2004. It implements a wide range of network protocols and audio/video codecs. The interaction between WebRTC and Chrome is heavily influencing the how features are developed, reviewed and shipped to millions ...
|
| 2/6/21 |
Seeing Zoom used for interviews and "virtual audiences" throughout the pandemic was humiliating for those of us who build projects and products with WebRTC. There must be a better way; and there is - building a WebRTC platform to generate feeds that broadcasters and event producers can consume as they see fit - no need to show Zoom's UI on TV any longer! This is the tale of how and why we built the service that's been used to record all of the RTC track sessions at FOSDEM.
|
| 2/6/21 |
Instruct the audience for achieving high throughput online exports of charged events with in-memory data only.
|
