Tech

Inter-Office Trunks

Published on:

June 21, 2013

Previous versions of the PBX allowed calls from one trunk to be routed through another for cost-effective call termination - this was commonly used by international offices. Now, the new inter-office trunk feature enhances this by assigning a dial plan directly to the trunk, offering greater flexibility in caller ID presentation. This allows businesses to optimize call routing without linking to specific extensions. While prepaid accounts aren’t supported, the feature enables broader applications, such as acting as a session border controller (SBC), handling LAN-WAN traffic, and translating calls between IPv4 and IPv6. Available from version 5.0.10i, this expands the role of the PBX in networked environments.

In previous versions of the PBX, there was already a setting, “assume the call comes from extension so-and-so”. This was a trick to make it possible for a call coming in on one trunk to end up on another trunk for outbound call termination.

The practical relevance for this was international offices could use this trick to locally terminate calls from their branch offices. For example, when a company had offices in Boston and Berlin, making a phone call in Germany from the Boston office could be done using the PBX in the Berlin office, saving international call termination fees.

We have now taken this to the next level by adding an “inter-office” trunk feature. Instead of using the dial plan of an extension, the trunk uses a dial plan directly. It also provides more flexibility in presenting the caller-ID: the presented caller-ID does not have to be linked to an extension. Of course this depends on the carrier’s ability and willingness to present caller-ID that aren't within the PBX address range.

Because extensions aren't charged any more, the interoffice trunk feature doesn't support prepaid accounts. Our feeling, however, is the practical relevance for this is relatively low anyway.

The term “office” goes beyond the example which I have made previously. Technically the PBX identified inbound traffic attached to a trunk, no matter if the call came from the same organization or from another source. This way, the PBX is able to perform general call routing functions and act as a general-purpose session border controller. Especially since the PBX is able to operate on multiple network interfaces, it can be used to translate traffic between LAN and WAN. Other scenarios, like translating calls between IPv4 and IPv6, or just transcoding codecs, are now also possible. Time will tell what customers want to see.

The inter-office trunk feature will be available from version 5.0.10i onwards.

Latest Articles

View All

Why Area Codes Still Matter in a Mobile World

Even in 2025, area codes remain important for personal and business communications. People move frequently but usually keep their original phone numbers because changing them is inconvenient and tied to banking, two-factor authentication, and multiple online accounts. For PBX administrators, area codes are essential for routing calls accurately, displaying the correct caller ID, and managing costs. Vodia PBX simplifies area code management with pattern-based dial plans, automatic updates, and smart trunk selection. This ensures that calls reach the right destination efficiently, maintain a local presence to increase pickup rates, and provide reliable communication both in North America and internationally.

September 16, 2025

Keycloak OpenID Connect Integration for the Vodia PBX

Vodia’s PBX now integrates with Keycloak OpenID Connect, providing secure single sign-on for users so they can access all connected applications without repeated authentication. Logging out from one application automatically logs the user out of all connected systems, simplifying user management and improving security. Keycloak, a Cloud Native Computing Foundation project, supports standard protocols including OpenID Connect, OAuth 2.0, and SAML, offering enterprise-grade identity and access management. To ensure proper integration, Keycloak user emails must match the corresponding PBX extension emails. Complete guidance is available in the Vodia Keycloak integration guide.

September 12, 2025

Vodia Announces Partnership with Comms Group Global

Vodia Networks has announced a strategic distribution partnership with Comms Group Global (ASX: CCG), aiming to expand the reach of its feature-rich cloud PBX solutions across APAC and EMEA. Through this collaboration, Comms Group Global will serve as an official reseller, providing businesses of all sizes with scalable, secure, and integrated telephony solutions. Customers will benefit from advanced call management features, Microsoft Teams integration, and robust security standards, while also gaining access to Comms Group’s SIP coverage in over 65 countries. The partnership enables a streamlined “one-touch” provisioning process, ensuring fast and seamless deployment for enterprises and SMEs seeking to improve efficiency.

September 8, 2025