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

Resilience in Communication: Why Vodia’s Distributed Approach Leads the Way

Vodia Networks utilizes a distributed architecture for its communication platform, reducing the risks associated with centralized systems. Unlike single-server solutions that create a single point of failure, Vodia’s approach spreads the load across multiple servers, ensuring continuous operation even in the event of hardware or software issues. Each server operates independently with its own data, enabling quick failover and minimizing disruption. On-premise deployment options provide additional control over security and performance, while the decentralized structure enhances resilience against large-scale outages and cyber threats.

February 5, 2025

The Vodia PBX for Communication in Nursing Homes

Nursing homes require seamless, secure communication to ensure quality care, and Vodia’s cloud-based PBX is the ideal solution. With features like ACD, call recording, emergency notifications and MS Teams integration, Vodia streamlines staff coordination, enhances resident safety, and simplifies admin workflows. Our system supports DECT, SIP phones, smartphones, and web browsers, providing flexible connectivity. Vodia’s Smart Fax ensures secure document transmission, while our API enables custom integrations with EHRs and telemedicine software. Designed for scalability, privacy, and reliability, Vodia empowers nursing homes to maintain smooth operations.

January 29, 2025

Vodia Looks Forward to IT Expo 2025

Vodia is excited to participate in IT Expo 2025, taking place from February 11 to February 13 in Ft. Lauderdale, FL. Sales Engineer Eric Altman will be attending to meet with partners, discuss Vodia's latest milestones, including our Microsoft Teams certification and integration with Realtime AI via APIs, and explore the future of AI in business communication. "2025 is shaping up to be an exciting year for Vodia, and we’re eager to engage with our partners and industry peers to discuss how we can continue to innovate and grow," said Eric. We encourage both current and prospective partners to reach out to Eric at ea@vodia.com or +1 (617) 861-3490 to arrange a meeting. We look forward to seeing you in Ft. Lauderdale for an exciting and productive event.

January 29, 2025