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 Attends HITEC North America 2026 to Expand Hospitality Technology Conversations

Vodia Sales Engineer Eric Altman attended HITEC North America 2026 to connect with hospitality technology providers, discuss current PMS integrations, and explore future opportunities around Vodia V70. The event highlighted the growing importance of reliable hotel communication, front-desk workflows, staff coordination, and integrations between cloud phone systems and the platforms hotels already use every day, especially as hospitality teams look for more connected and efficient ways to serve their guests.

June 19, 2026
Announcement

Introducing the Vodia Partner Program: higher discounts as you grow

The Vodia Partner Program and new Vodia Partner Portal give service providers, MSPs, system integrators, and technology partners a clearer way to grow their Vodia business. Partners can earn status points through revenue, certifications, customer acquisition, referrals, and other activities, then use those points to progress through partner levels and unlock higher discounts. The launch also includes a limited-time Summer Launch Promotion, giving new partners a faster path toward Gold status and a 20% discount.

June 18, 2026
Editorial

Traditional Interactive Voice Response (IVR) vs. AI Receptionist

Traditional IVR and AI receptionists both help businesses manage incoming calls, but they are built for different caller experiences. IVR works well for predictable routing, fixed menus and simple call flows, especially when callers need to reach a department, queue or mailbox. AI receptionists support more natural conversations, smarter responses and more flexible automation, helping callers explain what they need and reach the right outcome faster. The right choice depends on call volume, caller needs, budget and how much personalization your business wants to offer.

June 17, 2026