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

Monitoring Your Vodia PBX: Ensuring Continuous Communication

The Vodia PBX comes equipped with powerful built-in monitoring tools and integration options to ensure seamless, uninterrupted communication. From real-time system graphs and syslog analysis to packet capture tracking and detailed CDRs, Vodia enables proactive issue detection, performance optimization, and enhanced call quality. With support for SNMP, Prometheus, and external services like Pingdom and Site24x7, you can monitor everything from registration anomalies to system resource usage and SIP connectivity across multiple servers—all in one comprehensive solution.

May 15, 2025

Real Telecom and CallSmart Announce the Integration of the Vodia PBX with the CallSmart

Real Telecom and CallSmart have announced the integration of the Vodia PBX with the CallSmart AI communication platform, delivering a feature-rich, cost-effective voice solution tailored for modern dental and healthcare practices. The integration empowers clinics with advanced call center functionality, HIPAA-compliant data security, and seamless communication tools that reduce missed appointments and enhance patient engagement. CallSmart’s AI captures missed calls and automatically engages patients via SMS, while Vodia PBX ensures easy installation and reliable performance.

May 13, 2025

Fast and Easy: Vodia Prepaid Cloud for Microsoft Azure

Vodia’s prepaid cloud PBX solution for Microsoft Azure enables businesses to quickly deploy a fully licensed, enterprise-grade phone system without the complexity of traditional installations. Designed for speed, scalability, and ease of use, the offering supports packages for up to 80 users and includes a Teams-certified Session Border Controller (SBC) that allows seamless integration of Vodia PBX features—such as auto-attendants, call queues, and intelligent routing—directly within Microsoft Teams. Whether you’re an SMB or a growing enterprise, Vodia’s prepaid PBX is a powerful and flexible solution that’s easy to scale as your business evolves.

May 12, 2025