Schedule

What is a carrier to do?

Becoming more than a carrier is very legitimate answer, but this could be a costly transition if one’s infrastructure is based on bespoke services with unhealthy licence fees and maintenance costs.

Whether you’re a carrier, or a developer serving carriers or large-scale enterprises, combatting the decline of voice traffic revenue presents an opportunity best served with open source solutions.

In this session we’ll take an overview of the situation, suggest a way forward and give examples of where Simwood has forged a path to the future.

It sounds simple, but maintaining a stable connection across changing networks can be quite a challenge.

Discover how pascom uses a smart, consistent approach to handle a wide range of connection loss scenarios with ease.

As part of the solution, it was required to provide a functionality for the customers to allow the usage of public emergency calls too, i.e. Type 1 Emergency Call 112 as well as national Type 2 Emergency Calls (e.g. 122, 133 or 144 in Austria).

The presentation includes a short recap of the overall solution and then focus on the steps how public emergency calls have been integrated for various use cases in their deployment and highlight how Kamailio has been used for this purpose.

In this session, we will dive into CAMARA’s Telco APIs, with a special focus on the WebRTC working group, led by Quobis. This group defines key APIs—webrtc-register, webrtc-call-handling, and webrtc-events—that enable device authentication on IMS networks, call management, and real-time event monitoring. We will explore how these APIs empower developers to integrate telecom services seamlessly into their applications.

Beyond the API definitions, we will discuss real-world implementations and the strategic role of Kamailio as a key enabler in this ecosystem. Through practical examples, we will showcase how Kamailio + CAMARA can be leveraged to build scalable and robust WebRTC solutions.

Join us to discover how open-source and standardization efforts are reshaping telco innovation, and why Quobis is leading the way in bridging the gap between WebRTC and next-generation telecom networks.

This presentation will focus more specifically on RTP Over QUIC, on its current state as a specification and its untapped potential. It will discuss whether it has any place in the current VoIP ecosystem, if there’s room for QUIC in SIP too, and what may happen in the future.

It tells a story that begins by evaluating different SIP frameworks and stacks, and how once Kamailio is selected, it can be used in a way very different from what it was intended (like using native scripting or Kemi) in favor of building a new module but implemented in a high-level language as C++ and using Kamailio as a framework rather than as a SIP server.

Finally, we will illustrate how we solved certain aspects and problems that this approach triggered, covering aspects such as handling locks and mutexes in different processes shared with Kamailio, how to isolate Kamailio to enable unit testing of our code, memory management, how to invoke functions from other modules written in C, etc.

You’ll be taken through a journey of vulnerable configuration patterns, focusing on Kamailio configuration pitfalls that could compromise your systems. Through practical examples based on actual real configurations seen out there, we’ll demonstrate how these vulnerabilities can be exploited and, more importantly, how to effectively mitigate them.

But we don’t stop at quick fixes. This presentation then moves on to discussing strategic thinking, offering innovative approaches to break free from the endless cat-and-mouse game of security fixes. Join us to learn about proactive security strategies that will help you leverage Kamailio’s flexibility while maintaining robust security posture.

Whether you’re a seasoned Kamailio administrator or just getting started, this session provides actionable insights and practical solutions to stay ahead of potential threats in your Kamailio infrastructure.

This session will explore the pivotal role Kamailio plays in our solution:
• Challenges addressed effectively using Kamailio “out-of-the-box.”
• Customizations made to the core product to accommodate our diverse use cases.
Special focus will be placed on:
• SIP routing in dynamic andIP networks.
Addressing RTP routing challenges and exploring potential solutions.

The focus is on scenarios where multiple registrars (such as Asterisk instances without a shared database) operate behind a MID-Registrar. This setup allows the same user to authenticate across different registrars while keeping them synchronized, even though they are unaware of each other.

MID-Registrar Approaches:

Proxy-Registrar: Propagates the same request to multiple registrars without sharing credentials.
MID-Registrar With Shared Credentials: Uses shared authentication credentials for seamless operation.

The content comes with configuration examples, infrastructure diagrams, detailed guides, and practical tips. Additionally, it highlights the pros and cons of each approach.

The Kamailio Code Challenge features real-world code snippets submitted by the community. Each snippet includes the Kamailio version and, optionally, the company and product context where it’s used. How it works:

* A mysterious Kamailio script appears on the big screen.
* The audience has 2 minutes to figure out what it does.
* If someone solves it, they win a prize!
* If no one cracks the code, the submitter wins instead!

Ready for the challenge? Put your Kamailio knowledge to the test and claim the prize!

Config snippet submission via the web form available at:

• https://www.kamailioworld.com/k2025/kamailio-code-challenge/

Some highlights include:

– using crypto wallet for registration instead of username and password

– how one Kamailio can serves different service providers

– decentralised solution based on Kamailio

– allowing combination of different user identities such as ENS, e-mail or phone number using the same server

– examples from the Kamailio flow that are integrated with Polygon blockchain – for call establishment.