Retour au 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. Traditionally, PBX systems use LAN-based IP addresses, but dynamically switching to a public IP address during failover has posed challenges. To address this, a new feature has been introduced where 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 land-line based internet access becomes unavailable.

We have for a long time the possibility to run the PBX in the LAN, replacing the local IP address with publicly routable IP addresses. The IP replacement list was already a topic of many forum discussions.

However when it comes to dynamically switching the presented IP address in the case of a failover, we were in trouble. In theory, it would be possible to run a script that tests for the public IP address and then uses the REST interface and change the routing table. However not everyone is a bash wizard 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 a 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.

The PBX expects in the response from the web server a 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 is possible to use public servers, but you also use your own servers obviously.

The failover will obviously take some time. The polling interval determines how fast the change is being detected. Obviously there is 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. It will be available in 5.2.5.

Derniers articles

Voir tous
Announcement

US Court of Appeals Rules Federal Communications Commission (FCC) Lacks Legal Authority to Reinstate Net Neutrality Rules

The FCC has reinstated net neutrality rules, classifying broadband as an essential service under Title II to prevent ISPs from blocking, throttling, or prioritizing content for payment. Originally introduced in 2015 under President Obama and repealed in 2017 during the Trump administration, the rules have been a point of contention, with tech giants like Amazon, Apple, and Meta supporting their return. However, a federal court ruling in early 2024 challenged the FCC’s authority, potentially halting decades-long efforts for comprehensive oversight.

March 4, 2025
Tech

Vodia Announces Integration with Cliniko

Vodia Networks is excited to announce its integration with Cliniko, a leading practice management software for healthcare providers. This integration enables seamless call handling by automatically displaying patient records from Cliniko when calls come in, allowing staff to quickly access the relevant details. The integration enhances patient interactions, streamlines workflows, and supports healthcare organizations in providing better care while maintaining HIPAA compliance and data security. Vodia’s feature-rich PBX ensures improved operational efficiency and reduced telephony costs for healthcare providers.

February 24, 2025
Webinar

Integrating OpenAI's Realtime API with Vodia PBX: Webinar Recording Now Available

In our recent webinar, "Integrate OpenAI’s Realtime API with Vodia PBX," we explored how integrating AI with your communication systems can revolutionize the way your business operates. From automating repetitive tasks to improving workflow efficiency, the webinar covered how the collaboration between Vodia PBX and OpenAI’s Realtime API can streamline operations, enhance collaboration - especially for Microsoft Teams users - and provide intelligent automation to stay ahead in a competitive landscape. If you missed the live session or want to revisit the insights, the recording is now available for you to access.

December 18, 2024