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

Turn Your Android Phone into a Vodia Extension with the Vodia Android App

Vodia Phone 2 turns your Android device into an extension of your Vodia Phone System, making it easier to stay connected wherever you work. Native Android integration lets users make and receive business calls using their office number and identity, even when the app is running in the background. From one mobile app, they can hold, transfer and park calls, access voicemail, messages and contacts, review call history, view extension activity and manage important settings such as Do Not Disturb and call forwarding.

August 7, 2026
Announcement

Introducing the Vodia PBX Installer Wizard for Windows

The new Vodia PBX Installer Wizard makes it easier for administrators to deploy Vodia PBX on Windows. It automatically detects the latest supported version, while still letting admins choose a specific V68, V69, or V70 build. The wizard downloads the required files, creates the Windows service, sets up the installation folder, and generates the access details needed to open the PBX. A download-only option is also available for preparing and inspecting the files without completing the installation.

August 4, 2026
Editorial

Mobile Apps, Desk Phones, and Browser Calling: Choosing the Right Endpoint by Role

Business communication is no longer tied to a single device. Desk phones remain valuable for employees who manage high call volumes, mobile apps give remote and travelling teams access to business calling wherever they work, and browser calling fits naturally into computer-based workflows. This article looks at the strengths and limitations of each endpoint, explains which roles they suit best and shows why most organizations benefit from building the right mix rather than selecting one option for everyone.

July 30, 2026