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

Transforming Maritime Connectivity with MS Teams: A Communication Solution for Cruise Ships

Reliable communication is essential for cruise ship safety, operational efficiency, and an exceptional guest experience, yet it faces unique challenges including remote connectivity, signal interference from metal structures, and stringent network security requirements. The Vodia PBX, now certified for MS Teams, offers seamless satellite integration, emergency calling, and direct communication between crew and passengers. This combination ensures continuous 24/7 connectivity, supports emergency protocols, and enhances onboard collaboration.

June 5, 2025

Embrace Unparalleled Digital Diversity and Secure Data Ownership with the Vodia PBX

Vodia gives you full control over your communications with operating system independence, multi-cloud VoIP capability, and complete data ownership. Whether you deploy on-premise, in your own data center, or across major cloud platforms like AWS or Azure, Vodia’s flexibility ensures resilience, scalability, and freedom from vendor lock-in. With support for multiple OS environments and features like zero-touch provisioning and redundant SIP trunks, it’s a future-proof solution built for secure, adaptable business communications.

June 3, 2025

The Vodia PBX Now Integrates with ActiveCampaign

Vodia’s latest integration with ActiveCampaign brings together a powerful cloud PBX system and a leading customer experience automation platform. This integration enables businesses to automatically track and manage customer interactions by creating and updating contacts based on call activity, recording detailed call information, and linking calls to the appropriate users within ActiveCampaign. By combining Vodia’s advanced telephony features with ActiveCampaign’s AI-driven marketing and sales automation tools, companies can deliver more personalized experiences, improve team productivity, and drive growth through smarter, data-backed communication.

May 29, 2025