300-820 · Question #12
When determining why Mobile and Remote Access to Cisco TelePresence equipment does not work anymore for an organization. There are several administrators and configuration changes could have happened
The correct answer is A. link to the DefaultZone. On Cisco Expressway, zones must be explicitly linked together to allow call routing between them. A TraversalZone handles calls coming in from external sources (via Expressway-E), but for those calls to reach internal registered devices (which are in the DefaultZone), a 'link' mu
Question
When determining why Mobile and Remote Access to Cisco TelePresence equipment does not work anymore for an organization. There are several administrators and configuration changes could have happened without anyone knowing. Internal communication seems to be working, but no external system can register or call anywhere. Gathering symptoms, you also discover that no internal systems can call out either. What is TraversalZone missing that causes this issue?
Options
- Alink to the DefaultZone
- Bpipe to the DefaultZone
- CSIP trunk to the DefaultZone
- Droute pattern to the DefaultZone
How the community answered
(62 responses)- A81% (50)
- B11% (7)
- C5% (3)
- D3% (2)
Explanation
On Cisco Expressway, zones must be explicitly linked together to allow call routing between them. A TraversalZone handles calls coming in from external sources (via Expressway-E), but for those calls to reach internal registered devices (which are in the DefaultZone), a 'link' must exist between the TraversalZone and the DefaultZone. Without this link, the Expressway has no path to route calls from the traversal zone to internally registered endpoints or vice versa, which explains why internal systems cannot call out and external systems cannot register. Options B (pipe), C (SIP trunk), and D (route pattern) are not the correct Expressway constructs used to connect zones - links are the proper mechanism.
Topics
Community Discussion
No community discussion yet for this question.