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
Editorial

Mobile Apps, Desk Phones, and Browser Calling: Choosing the Right Endpoint by Role

Business communication is no longer tied to a single device. Desk phones remain valuable for employees who manage high call volumes, mobile apps give remote and travelling teams access to business calling wherever they work, and browser calling fits naturally into computer-based workflows. This article looks at the strengths and limitations of each endpoint, explains which roles they suit best and shows why most organizations benefit from building the right mix rather than selecting one option for everyone.

July 30, 2026
Announcement

Your Vodia Extension, Built for iPhone

The new Vodia iOS app gives users a native way to use their Vodia PBX extension from iPhone and iPad. Built around a cleaner, card-based interface, the app makes it easier to manage calls, voicemail, chat, extensions, call history, and active call controls in one place. Users can place and receive calls, park or transfer calls, check voicemail, and view extension status from the app. It also adds readiness checks, visual audio feedback, call quality visibility, and adaptive recovery when network conditions change, helping teams stay connected with a reliable mobile PBX experience.

July 28, 2026
Editorial

Why MSPs Should Own the Customer Relationship in Cloud Communications

Cloud communications can create a valuable recurring revenue opportunity for MSPs, but only when they remain in control of the customer relationship. By managing branding, pricing, service delivery, and support, MSPs can build stronger customer loyalty, protect long-term account value, and expand their offering as customer needs evolve. A white-label approach also gives them the flexibility to package voice, AI, integrations, and managed services under their own brand.

July 22, 2026