Tech

PBX for SIP Trunking

Published on:

February 27, 2014

Version 5.2.0 introduces a valuable improvement for extensions with multiple alias numbers. Now, when an inbound call is received, the PBX will send the called alias number to the registered device; if the number isn't on the alias list, the primary extension name is used. This change enhances the role of the PBX, so it also serves as a trunk engine. It’s particularly beneficial for SIP trunking providers, who can leverage features like PCAP recording, RTCP-XR for SLA monitoring, and the management of both IPv4 and IPv6 interfaces. Additionally, with improved CDR reporting, billing becomes easier, and the PBX scales efficiently with virtualization support.

5.2.0 introduces a small but important improvement: if an extension has more than one alias number, it will send the called alias number to the registered device on inbound calls. In case a number was called that wasn't on the list of alias names, it will still pick the primary name of the extension.

The background for this change is the PBX isn't always used purely as a PBX. Instead, because of its functionality for dealing with devices behind NAT (session border controller) and other features like SRTP encryption, it's useful as a trunk engine. Customers register their devices as extensions on the PBX and, although the PBX treats this as extensions, what the customer sees is a SIP trunk.

Service providers who are using the Vodia PBX for SIP trunking can also benefit from the PCAP recording the PBX provides for easy, customer-based trouble shooting. Our PBX is probably one of the few that supports RTCP-XR for SLA monitoring. The automatic blacklisting feature makes it resilient against common scanners, while the multi-tenant feature can serve as additional support for to reduce the risk of unauthorized access.

That the PBX is able to operate on multiple IPv4/IPv6 interfaces makes it possible to run other SIP devices in a private network while customers see the public interface. It's even possible to have customers register on IPv6 while the private network is still on IPv4.

With the new CDR reporting, it also becomes a lot easier to bill the customer. SIP trunk providers can use the template PHP code to integrate the PBX CDR with their billing systems. Because the PBX is software based, it scales with the availability of powerful server hardware. The support for virtualization makes it possible to have a failover, with even calls staying up.

In the private network, customers can run another SIP-compliant PBX. For example, we've had a case where a customer was running a Cisco CallManager in the corporate network and needed a solution to interface with the public Internet using the PBX as the session border controller. It worked well.

Latest Articles

View All

Vodia Monitor: Centralized PBX infrastructure monitoring for V70

Vodia Monitor is a self-hosted monitoring platform for Vodia PBX deployments that gives administrators and service providers centralized oversight across multiple systems. Monitor uptime, SIP trunks, TLS certificates, ports, tenant activity, blocked IPs, and infrastructure events from a single dashboard. With alerts, historical tracking, rankings, AI health summaries, and operational insights, Vodia Monitor helps teams identify issues faster, reduce manual monitoring, and maintain infrastructure health across distributed PBX environments.

June 11, 2026

Why Call Transcription Is Only the Beginning of AI in Business Communications

Call transcription is often the first AI feature organizations encounter, but it is only the beginning. AI is now helping businesses automate call handling, analyze conversations, monitor infrastructure, and gain deeper operational insight across their communication platforms. From AI receptionists and conversation analytics to sentiment analysis and AI-assisted monitoring, modern business communications are becoming more intelligent, proactive, and efficient.

June 9, 2026

Vodia Phone 2: Your Work Phone, Built Into Your Android Smartphone

Vodia Phone 2 brings business calling directly into your Android smartphone experience. By integrating with Android's native calling framework, work calls ring, answer, and behave like regular phone calls, eliminating the need to switch between separate calling apps. Users can place calls from the standard phone dialer, answer from the lock screen, and take advantage of familiar Android features while still benefiting from business tools such as call history, messaging, voicemail, call forwarding, DND, and custom status settings.

June 4, 2026