Back to Blog
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.

Christian Stredicke

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
Announcement

Vodia Monitor: Centralized PBX infrastructure monitoring for V70

Vodia Monitor is a self-hosted monitoring platform for Vodia PBX deployments that gives administrators and service providers centralized oversight across multiple systems. Monitor uptime, SIP trunks, TLS certificates, ports, tenant activity, blocked IPs, and infrastructure events from a single dashboard. With alerts, historical tracking, rankings, AI health summaries, and operational insights, Vodia Monitor helps teams identify issues faster, reduce manual monitoring, and maintain infrastructure health across distributed PBX environments.

June 11, 2026
Editorial

Why Call Transcription Is Only the Beginning of AI in Business Communications

Call transcription is often the first AI feature organizations encounter, but it is only the beginning. AI is now helping businesses automate call handling, analyze conversations, monitor infrastructure, and gain deeper operational insight across their communication platforms. From AI receptionists and conversation analytics to sentiment analysis and AI-assisted monitoring, modern business communications are becoming more intelligent, proactive, and efficient.

June 9, 2026
Announcement

Vodia Phone 2: Your Work Phone, Built Into Your Android Smartphone

Vodia Phone 2 brings business calling directly into your Android smartphone experience. By integrating with Android's native calling framework, work calls ring, answer, and behave like regular phone calls, eliminating the need to switch between separate calling apps. Users can place calls from the standard phone dialer, answer from the lock screen, and take advantage of familiar Android features while still benefiting from business tools such as call history, messaging, voicemail, call forwarding, DND, and custom status settings.

June 4, 2026