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

Vodia Podcast: How Brandywine Built a Multimillion-Dollar Business with Vodia

Yori Kasprzak, founder of Brandywine Technical Partners, joins Vodia’s Eric Altman to share how he built a multimillion-dollar business and the role Vodia has played in its growth. From cloud telephony and CRM integrations to door systems, AI and mobile workforces, he explains how Brandywine solves customer challenges with Vodia’s open platform and shares advice for partners looking to grow. His story shows how finding customer pain points can create business opportunities beyond traditional phone services.

September 17, 2026
Announcement

Turn PBX Activity Into Customer Invoices with Vodia Billing

Vodia Billing turns PBX activity into customer invoices by bringing call rating, recurring charges, taxes, invoice generation and payment tracking into one dedicated platform. Built for Vodia PBX fleets, it can process CDRs, count recurring PBX items, produce branded invoices, connect with Xero and QuickBooks Online, monitor overdue payments and flag potential fraud. It also gives MSPs clearer visibility into margins, helping them understand not only what customers owe, but what their services are actually costing to deliver.

September 15, 2026
Editorial

Keep Talking: AI and the Future of Business Communication

From the moment humans learned to speak, communication has shaped how we live, work, and connect. Today, voice remains one of the most natural and information-rich forms of human interaction, even as business communication expands across chat, video, messaging, and digital platforms. As AI becomes more deeply integrated into phone systems and contact centers, voice may play an increasingly important role in how intelligent systems understand context, respond to people, and support real-time communication.

September 9, 2026