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.

Latest Articles

View All

The Vodia PBX Now Integrates with ActiveCampaign

Vodia’s latest integration with ActiveCampaign brings together a powerful cloud PBX system and a leading customer experience automation platform. This integration enables businesses to automatically track and manage customer interactions by creating and updating contacts based on call activity, recording detailed call information, and linking calls to the appropriate users within ActiveCampaign. By combining Vodia’s advanced telephony features with ActiveCampaign’s AI-driven marketing and sales automation tools, companies can deliver more personalized experiences, improve team productivity, and drive growth through smarter, data-backed communication.

May 29, 2025

Five-Star Hospitality Communications: Fanvil IP Hotel Phones and the Vodia Phone System

Hotels today need more than luxury amenities—they need smart, reliable communication systems that enhance the guest experience and streamline operations. The combination of Vodia’s powerful VoIP PBX and Fanvil’s new IP Hotel Phones delivers exactly that: seamless in-room communication, fast response to guest requests, and integration with leading PMS. With features like programmable keys, built-in Wi-Fi, AP mode, and USB charging, Fanvil’s devices are purpose-built for hospitality, while Vodia’s system brings automation, multilingual support, and cost-efficient call handling to the table.

May 27, 2025

Smarter Hotel Communication: Vodia PBX Now Integrates with Shiji PMS

Vodia now offers seamless integration with the Shiji Property Management System (PMS), empowering hotels to streamline operations, automate routine tasks, and enhance guest experiences through smarter communication. From check-in to check-out, the integration connects telephony with front desk functions—enabling features like personalized extension setup, automated call billing, room status updates via maid codes, and effortless room changes. With a secure real-time interface, no complex middleware, and support for cloud, on-prem, or hybrid deployments, the Vodia-Shiji solution is built for reliability, scalability, and modern hospitality.

May 23, 2025