Tech

Different IP Addresses for Failover

Published on:

December 5, 2014

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.

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.

Latest Articles

View All

Why Is Vodia the Best Business Phone System? 10 Reasons You Need to Know

Vodia Networks provides state-of-the-art cloud communication solutions tailored for enterprises, contact centers, and service providers. With MS Teams certification, TLS 1.3 compliance, and support for over 6,000 extensions per virtual machine, Vodia’s phone system stands out as the most feature-rich, scalable, and secure option on the market. Whether you’re seeking seamless integration with SIP devices, robust call center management tools, or the ability to white-label the system as an MSP, Vodia offers unparalleled flexibility and value. Explore the 10 reasons why Vodia is the best business phone system for organizations of all sizes.

January 23, 2025

Webinar On-Demand: Integrating Vodia SBC with MS Teams and Fanvil Devices

In our latest webinar, we dive into the seamless integration of Vodia SBC with MS Teams and Fanvil devices, offering a comprehensive overview of how these solutions can enhance your business communication system. Our experts share insights on the benefits of connecting MS Teams with Vodia’s cloud-based PBX, the flexibility of supporting over 50 SIP trunk providers, and the advanced features of Fanvil’s IP phones. Whether you’re looking to optimize your Teams environment or explore new deployment options for your communication setup, this session provides valuable takeaways for businesses of all sizes. Watch the on-demand webinar now.

January 22, 2025

Vodia Participates in VoIP Planning Meeting

Vodia Sales Engineer Eric Altman participated in a strategic planning meeting in Washington, DC, with BCM One, SIP Trunk, Cove Central, and elite resellers to discuss joint strategies and goals for 2025. As a trusted partner of these organizations and a member of the Cove Central Technology Alliance Partner Program (TAPP) since November 2023, Vodia continues to build on its strong industry relationships. The meeting highlighted opportunities for collaboration and innovation, aligning with Vodia's recent milestone: the certification of the Vodia PBX for Microsoft Teams. Announced in November, this certification enables businesses to enhance their Teams ecosystems with critical functionalities such as SIP trunk call routing and VoIP endpoint connectivity.

January 17, 2025