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 Customer Service: Vodia PBX Integrates Seamlessly with Freshdesk

Vodia PBX now integrates seamlessly with Freshdesk, an AI-powered customer service platform used by over 73,000 companies worldwide. This integration combines intelligent ticketing and automation with enterprise-grade telephony, enabling automatic contact creation, detailed call tracking, and streamlined agent workflows. By improving call center efficiency and customer interaction management, it helps businesses enhance productivity and customer satisfaction. Vodia continues to strengthen its ecosystem with integrations to leading business software, delivering top-tier cloud PBX solutions.

July 29, 2025

Prepaid Cloud Instances: The Future of PBX Deployment

Prepaid cloud instances are transforming how PBX systems are deployed by offering a faster, simpler, and more flexible approach. With Vodia PBX now available on AWS, Azure, and DigitalOcean, businesses can launch a fully licensed, production-ready phone system in just minutes, without complicated setup or licensing delays. These preconfigured environments allow IT teams, decision-makers, and MSPs to test real-world VoIP performance, MS Teams integration, and mobile apps directly within their own cloud account. By removing traditional friction and offering full control, Vodia’s prepaid cloud instances provide a smarter and more efficient way to evaluate and deploy a modern PBX.

July 25, 2025

Vodia to Attend ChannelCon 2025

Vodia will participate in ChannelCon 2025, taking place in Nashville, TN, from July 29 to 31, with Sales Engineer Eric Altman attending on behalf of the company. ChannelCon, hosted by the Global Technology Industry Alliance (GTIA), is the premier vendor-neutral event dedicated to the worldwide IT channel. It brings together MSPs, service providers, vendors, and distributors for three days of expert panels, networking sessions, and special events designed to foster innovation and collaboration in the tech industry. Altman will highlight Vodia’s latest CRM integrations underscoring Vodia’s commitment to equipping partners with dynamic, enterprise-grade phone systems.

July 24, 2025