Current Location ：
Voice Failover: Designing What Happens When the Primary Path Fails
Every voice design has a primary path, and every primary path fails eventually. What separates a resilient deployment from an expensive week is whether the failure was designed for or discovered. Failover design is where the design decisions get tested, because a failover that has never been exercised is an assumption about behaviour that may not be true. This article covers what to fail over, what to keep running when the primary fails, and how to test the design without telling anyone in advance.
Name the Paths Before You Need to Fail Over
The first discipline in failover design is naming the paths: what carries calls normally, what carries them when that fails, and what carries emergency traffic regardless. A design that has never written down which path is which will discover the answer during an incident, and the answer will be different from what anyone expected. The useful exercise is a written map of paths and their failure behaviour.
| Path element | Normal behaviour | What should happen when it fails |
|---|---|---|
| Central platform | Carries calls and features | Failover to a secondary or survivable mode, with known behaviour |
| Trunk or carrier | Carries inbound and outbound traffic | Failover to a secondary path, with tested switch behaviour |
| WAN link | Connects sites to the platform | Sites continue with what they can, as designed |
| Emergency routing | Routes emergency calls to the right service | Emergency behaviour survives every failure mode |
| Admin access | Manages the system | Access through the defined path, not a direct interface |
What to Keep Running When the Primary Fails
Failover design is not only about the system; it is about the services that must continue when it fails. Emergency calling, reachability of published numbers, and the ability to reach a human at all are the services that matter most, and they should be designed to survive the failure modes that are most likely. The useful test is to ask, for each failure mode, which of those three services still work.
- Define, in writing, which services must survive each failure mode
- Ensure emergency calling survives every failure mode, including total platform loss
- Keep a reachable path to a human, even in a degraded state
- Document the degradation order, so people know what they are losing and in what order
- Make the degradation visible to staff rather than discovered by customers
Test It Without Telling Anyone
A failover that is only tested when everyone knows it is being tested has not been tested. The useful test is one where the behaviour is observed under conditions close to reality: with live traffic, during a realistic window, and with the people who would respond if it were real. The test should also include the restore, because recovery is a second transition and the second transition is where things break.
Redstone Approach
Redstone supports failover and survivability design for voice deployments on the REX IP-PBX platform, including path mapping, degradation order, emergency behaviour, and controlled failover testing. Our teams can help you name the paths, define what must survive each failure mode, and run a failover test that includes restoration. Survivability scope is agreed in writing against your site list and carrier arrangements.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.
