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

Mastering Vodia PBX Installation on Linux: A Complete Guide for System Administrators

Installing Vodia PBX on Linux offers system administrators a powerful, enterprise-grade communication solution with built-in monitoring, automated backups, and disaster recovery features. This guide walks through supported Linux distributions, pre-installation requirements, and step-by-step instructions using a universal install script. With options for service monitoring, backup scheduling, and cloud deployment, it ensures a scalable and secure setup. Post-installation, standard Linux tools manage service status, updates, and logs, making ongoing maintenance simple.

June 26, 2025

Vodia Now Integrates with Microsoft Dynamics 365

Vodia now integrates its industry-leading PBX with Microsoft Dynamics 365, enabling automatic synchronization of call data with the CRM to enhance customer interaction tracking and streamline communications. This integration offers features such as automatic contact creation for unknown numbers, comprehensive call activity logging including direction, duration, and outcomes, and seamless user matching for accurate call attribution. Designed to empower businesses, this connection supports more efficient and scalable communication workflows within the Microsoft ecosystem.

June 24, 2025

Vodia Attends HITEC 2025 Indianapolis

Vodia visited HITEC 2025 in Indianapolis to engage with key hospitality technology partners and explore the latest innovations in the industry. Represented by Sales Engineer Eric Altman, Vodia connected with leaders from Shiji, Agilysis, Maestro, and Oracle. The event offered valuable insights into the evolving hospitality tech stack and affirmed Vodia’s commitment to AI-powered communications. With its recent integration of OpenAI’s Realtime API, Vodia continues to deliver smarter, multilingual guest experiences and more efficient hotel operations.

June 24, 2025