Tech

IP-based authentication is not dead yet

Published on:

June 30, 2015

Usually every domain needs their own telephone number or numbers that link the world of VoIP with the good old telecom industry. This is done using SIP trunks. While it is possible to share a SIP trunk with several domains, most hosted providers prefer one trunk per domain. But how does the SIP trunk provider know which trunk is being addressed when there is a call coming in?

Running multiple instances on a single IP address has a lot of benefits, especially when you are still on IPV4. Many clients can share the same host similar to what is standard today on web servers that can have hundreds and thousands of domains on a single server.

Usually every domain needs their own telephone number or numbers that link the world of VoIP with the good old telecom industry. This is done using SIP trunks. While it is possible to share a SIP trunk with several domains, most hosted providers prefer one trunk per domain. But how does the SIP trunk provider know which trunk is being addressed when there is a call coming in?

The SIP RFC provides several ways to identify where the call comes from on the SIP side. The caller-ID itself is not very useful as it can be spoofed easily, so it does not really count. Most service providers use a simple registration with the right password and a somehow unique contact in the SIP request to figure out where the request comes from.

Thinks get tricky on a multi-tenant PBX when the trunk identification is based on the IP address and the port. If it is only based on the IP address, then the potentially hundreds of domains can use only one telephone number, practically putting that SIP trunk provider out of business for that hosted PBX. Some trunk providers also consider the port, then it would be possible to open another port on the host for that trunk, so that all communication inbound and outbound run on that port.

This is what we have just added to the Vodia PBX. With the next version (post 5.2.6) it will be possible to use SIP service providers that solely rely on the IP address and port for the authentication. All you need to do to make this happen is to add another port to the list of SIP UDP ports on the PBX admin level and then mention that port number in the trunk setting. Then when that port is really available, the PBX will prefer that port for sending traffic from that trunk.

This feature is possible because the PBX is able to deal with a list of ports, not just one port for IPv4 and for IPv6. The performance implications are modest as long as there are not hundreds of those ports. The new open ports also slightly increase the exposure to SIP attacks; however realistically if you have already port 5060 open an attacker would not have any reason to try non-standard ports anyway.

The whole story reminds me a little bit about H.323, where a lot of the backbone VoIP traffic was sent based on the IP address for authentication. Let’s hope hackers don’t find an easy way to put themselves into the middle of that traffic and use this primitive authentication method to their advantage.

Derniers articles

Voir tous

Building Intelligent Voice Response Systems with Vodia's JavaScript IVR

JavaScript IVR transforms the way businesses handle incoming calls by enabling fully customizable, intelligent phone menu systems. Unlike static IVR setups with limited, pre-defined options, JavaScript IVR allows you to create dynamic call flows that adapt in real time based on caller input, business data, or even external API integrations. This means you can route calls more efficiently, automate complex processes, and offer highly personalized experiences to your customers. Whether you want to check customer records before transferring a call, adjust menu options based on time of day, or integrate with CRM systems for instant data access, JavaScript IVR gives you the flexibility and control to make it happen - all while improving efficiency and enhancing caller satisfaction.

August 11, 2025

Get The Support You Need Easily Through The Vodia Help Center On Jira

Vodia support is now easier to access through the Vodia Help Center on Jira, giving partners and customers a centralized platform to submit technical support tickets, ask sales or licensing questions, and suggest new features. With a valid license key, users can open detailed requests and track their status in one place. The portal also brings together Vodia documentation, the PBX API, and the Vodia forum, making it the go-to resource for everything Vodia. Whether you're troubleshooting, planning an upgrade, or just need guidance, the Help Center is designed to streamline your experience and connect you with the right support faster.

August 7, 2025

Vodia Attends ChannelCon 2025 in Nashville

At ChannelCon 2025 in Nashville, Vodia Sales Engineer Eric Altman engaged with MSPs and IT professionals to explore how AI is shaping the future of managed services. He emphasized that ChannelCon remains a valuable space for building strong vendor-partner relationships, especially as AI continues to dominate industry conversations. Altman noted how Vodia is helping MSPs unlock greater flexibility by combining powerful PBX features with AI-driven capabilities like dynamic call analytics, customized call flows, and automated performance reporting. He also highlighted Vodia’s recent launch of prepaid cloud instances on AWS, DigitalOcean, and Microsoft Azure, designed to streamline deployment for MSPs without infrastructure or licensing delays.

August 5, 2025