Failover Routing

Flexible call forwarding for various scenarios

The Failover Routing feature in anynode allows you to define multiple target nodes within a route, each with specific routing and rewriting rules. This enables automatic switching to the next entry based on certain status messages, ensuring flexible and reliable call management.

What makes this solution unique is that it’s configurable directly within the routing settings. This allows for a wide variety of target types. Additionally, rewrites can be applied during the failover process, offering further flexibility.

Failover Routing ensures that calls reach their destination even when the primary route fails. It automatically adjusts the routing, minimizes downtime, and guarantees stable communication.

Characteristics

Support for multiple target nodes within a single route.
Customizable routing based on flexible status codes.
Integrated routing-forward profiles and rewriting rules.
Ensures seamless call forwarding during network outages, maintenance, or when participants are no longer reachable.
Reduces complexity in setting up and managing call forwarding.

Benefits

Prevents communication interruptions during server failures or network changes.
Enables flexible call forwarding for various scenarios.
Reduces configuration effort and minimizes the risk of errors.
Allows rewrites during failover for additional flexibility.

Infographic: With anynode – The Software SBC and failover routing, calls from the provider can first be routed to Microsoft Teams. If Microsoft Teams returns the status code '404 Not Found,' the call is automatically redirected to the traditional phone system. It is possible to define additional destinations in the failover list.

With anynode – The Software SBC and failover routing, calls from the provider can first be routed to Microsoft Teams. If Microsoft Teams returns the status code ‘404 Not Found,’ the call is automatically redirected to the traditional phone system. It is possible to define additional destinations in the failover list.

GIF Animation: Process of a Failover Routing configuration with anynode – The Software SBC. Initially, all calls are routed to Microsoft Teams. If Microsoft Teams returns the status code '404 Not Found,' the call is automatically redirected to the traditional telephone system. It is possible to define additional targets in the failover list.

Process of a Failover Routing configuration with anynode. Initially, all calls are routed to Microsoft Teams. If Microsoft Teams returns the status code ‘404 Not Found,’ the call is automatically redirected to the traditional telephone system. It is possible to define additional targets in the failover list.

anynode – The Software SBC with Route Assistant and a flexibly configurable list of status codes for failover routing.

anynode – The Software SBC with Route Assistant and the list of target nodes in Route Establishment. Number rewriting is optional.

Screenshot: anynode – The Software SBC with trace from a failover routing. The dialed number from a Teams participant with the last three digits 300 is not available. The response in the SIP message is 404 Not Found. Since this is configured as a rejection reason in the failover routing, the call is routed to the PBX.

anynode – The Software SBC with trace from a failover routing. The dialed number from a Teams participant with the last three digits 300 is not available. The response in the SIP message is 404 Not Found. Since this is configured as a rejection reason in the failover routing, the call is routed to the PBX.