What is the recommended redundancy method for gateways?

• A. Use a single route to avoid complexity.
• B. Use multiple route groups/route lists or SIP trunk failover.
• C. Rely on dynamic routing protocols for dial-peer reachability.
• D. Use a hardware redundancy without signaling changes.

Answer: (B)

Ensuring calls stay up when a gateway goes down relies on signaling-level backup paths rather than just a single connection. The recommended approach is to configure backup options that the system can switch to automatically. Using multiple route groups within a route list lets you place a primary gateway in the first group and a backup gateway in subsequent groups. The route list will attempt the primary group first and, if that path becomes unavailable, seamlessly try the next one, providing automatic failover for calls. Similarly, setting up SIP trunk failover gives you an alternate signaling path to a backup trunk or gateway, so calls can continue without manual intervention when the primary trunk fails.

This is preferable to having just one route, which creates a single point of failure; relying on dynamic routing protocols for dial-peer reachability isn’t the usual method for per-call failover and signaling path management; and hardware redundancy alone doesn’t guarantee call signaling will reroute if the signaling path isn’t also configured for failover.