Back to Blog
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.

Christian Stredicke

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
Announcement

The World of Vodia: One Extension, Every Way You Work

Your Vodia extension is no longer tied to a single device or location. Native iOS and Android apps, the browser-based User Portal, PWA support, Vodia Hub and click-to-dial extensions provide different ways to connect with the same Vodia PBX. Make and receive business calls from your smartphone, manage communication from your browser, control calls from the Windows desktop or dial numbers directly from the applications and webpages you already use. Wherever work takes place, Vodia provides an experience designed for the device and workflow at hand.

August 20, 2026
Announcement

From Check-In to Check-Out: Two Years of the Vodia-Cloudbeds Integration

The Vodia-Cloudbeds integration connects hotel communications with essential property-management workflows. From check-in to check-out, it automatically enables and personalizes room extensions, applies guest calling permissions, posts eligible call charges to Cloudbeds and resets extension data after each stay. Two years on, the integration continues Vodia’s long-standing work in hospitality, helping hotel teams reduce manual administration, protect guest information and keep telephone services synchronized with their daily operations.

August 18, 2026
Announcement

The Vodia-Jitsi Meet Integration: Some Thoughts on Content Privacy

The Vodia integration with Jitsi Meet brings secure, self-hosted video conferencing directly into the Vodia PBX web portal. Users can launch meetings with a single click, while organizations maintain control over their infrastructure, meeting content and access. With JWT-based authentication, automatic room creation tied to extensions and controlled guest access, the integration offers a private, scalable alternative to conventional hosted video conferencing platforms while bringing voice and video together in one communications environment.

August 13, 2026