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
Editorial

How MSPs Can Build Recurring Revenue by White-Labeling the Vodia PBX

White-labeling the Vodia PBX enables MSPs and VARs to offer business communications under their own brand without developing and maintaining the underlying PBX technology. Providers control branding, packaging, pricing, service delivery, and customer relationships, while Vodia supplies the multi-tenant platform. With V70’s expanded branding and management tools, MSPs can get to market faster and create new recurring-revenue opportunities.

September 3, 2026
Announcement

CarPlay Now Available with the New Vodia iOS App

Apple CarPlay support is now available with the Vodia iOS app, bringing essential PBX communication features to the vehicle display through Apple’s native in-car interface. Users can access recent calls, browse the extension directory, view colleague presence, listen to voicemail, use Siri for calls and PBX messages, and receive communication alerts, while built-in readiness checks and automatic recovery help maintain reliable access when network conditions change. The experience supports compatible wired and wireless CarPlay systems.

September 1, 2026
Announcement

The Vodia PBX and the Infor Hospitality Platform

The certified integration between the Vodia PBX and the Infor Hospitality Platform brings hotel operations and guest communications together. Through support for UHLL and FIAS, the two systems can exchange essential guest and room information, helping hotels automate extension activation at check-in, room resets at check-out, guest moves, calling permissions, call billing, Do Not Disturb settings, housekeeping updates, and wake-up calls. This reduces manual work for hotel staff and keeps telephone services synchronized throughout each guest’s stay.

August 28, 2026