300-815 practice question 21 of 30

An engineer set up and successfully tested a TEHO solution on the Cisco UCM. PSTN calls are routed correctly using the IP WAN as close to the final PSTN destination as possible. However, suddenly, calls start using the backup local gateway instead. What is causing the issue?

Full set: 221 questions
Answer options
A: WAN connectivity Correct answer
B: LAN connectivity
C: route pattern
D: route list and route group
Correct Answer:
A. WAN connectivity
Explanation

Tail-End Hop-Off (TEHO) routes calls over the IP Wide Area Network (WAN) to a remote site's gateway. The call routing is typically configured in a route list where the primary route group points to the WAN path (e.g., a SIP trunk to the remote gateway) and a secondary route group points to a local gateway for backup. If calls suddenly start using the backup local gateway, it means the primary path has failed. The primary path's availability is dependent on the IP connectivity between the sites, which is the WAN. Therefore, a WAN connectivity issue is the most direct cause of this behavior.

Why Incorrect

B. A LAN connectivity issue at the source would likely prevent the call from being placed at all, as the phone could not reach the call processor.
C. The route pattern is working, as it correctly directs the call into the route list. If the pattern were the issue, the call would likely fail completely.
D. The route list and route group configuration is functioning as designed by failing over to the backup path. The issue is not the configuration but the status of the primary path it points to.

References

1. Cisco Collaboration System 12.x Solution Reference Network Designs (SRND), Chapter "Call Routing", Section "Tail-End Hop-Off". This section describes TEHO as routing calls "across the IP WAN to a remote-site gateway". It also discusses high availability, where failure of the primary WAN path would cause calls to use an alternate path, such as a local gateway.

2. Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1), "Call Routing and Dial Plan Issues". This guide details how route list exhaustion works. When all devices in a route group are unavailable (e.g., due to a network outage), CUCM proceeds to the next route group in the list.

Scroll to Top