Tech

Different IP Addresses for Failover

Published on:

December 5, 2014

Failover capabilities are essential for ensuring uninterrupted service in PBX installations, especially with the growing use of high-bandwidth wireless connections like 4G. PBX systems traditionally use LAN-based IP addresses, but dynamically switching to a public IP address during failover has posed challenges. To address this, we've introduced a new feature - the PBX periodically probes a specified URL to detect its public IP address and adjusts the routing table accordingly. This feature simplifies the process, eliminating the need for complex scripts and allowing systems to automatically switch to the correct IP during failover, ensuring continuous operation. The feature will be available in version 5.2.5.

Failover is an important feature for most PBX installations. With the availability of high-bandwidth wireless like 4G, it becomes more and more popular to use the wireless connection when the primary landline internet access becomes unavailable.

For a long time, we've made it possible for the PBX to run in the LAN, which replaced the local IP address with publicly routable IP addresses. The IP replacement list was already a topic of many forum discussions.

When it comes to dynamically switching the presented IP address in the case of a failover, however, we were in trouble. In theory, it'd be possible to run a script that tests for the public IP address and then uses the REST interface and changes the routing table. Not everyone is a bash wizard, however, and it would even require different scripts for the different operating systems.

This was the reason why we went ahead and added a new feature that takes the URL for probing the public IP address of the PBX and an interval time value. The PBX will then periodically download the URL and set the public IP address of the PBX accordingly. The public IP address can be referenced with the magic name “public” in the routing list, like this:

192.168.0.0/255.255.0.0/192.168.1.1 0.0.0.0/0.0.0.0/public

Then the PBX would present 192.168.1.1 in the LAN and whatever-is-the-public-address in all other cases.

In the response from the web server, the PBX expects an IP address in human readable format, or in JSON-format, where the object must contain a entry called “ip” (for example, see http://myjsonip.appspot.com/). It's possible to use public servers, but obviously you can also use your own servers.

The failover will obviously take some time. The polling interval determines how fast the change is being detected. Obviously there's a tradeoff between polling (too) often and the time it takes to reflect the new address.

The new settings will be available right under the replacement list in 5.2.5.

Latest Articles

View All

Smarter Hotel Communication: Vodia PBX Now Integrates with Shiji PMS

Vodia now offers seamless integration with the Shiji Property Management System (PMS), empowering hotels to streamline operations, automate routine tasks, and enhance guest experiences through smarter communication. From check-in to check-out, the integration connects telephony with front desk functions—enabling features like personalized extension setup, automated call billing, room status updates via maid codes, and effortless room changes. With a secure real-time interface, no complex middleware, and support for cloud, on-prem, or hybrid deployments, the Vodia-Shiji solution is built for reliability, scalability, and modern hospitality.

May 23, 2025

The Vodia - Microsoft Teams Integration Tool

The Vodia-Teams NPM Integration Tool makes it easy for enterprises and SMBs to connect Vodia PBX with Microsoft Teams, enabling secure, seamless voice communication within Teams. Certified by Microsoft for direct routing, this tool automates extension mapping and phone number assignments across multi-tenant Microsoft 365 environments, allowing users to make and receive calls through the PBX via Teams. This integration opens new possibilities in industries like hospitality, healthcare, and education by unifying voice services, supporting door phones, paging, and flexible call routing — all managed centrally for simplicity and scalability.

May 20, 2025

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