300-820 · Question #14
Refer to the exhibit. When a Jabber user attempts to connect from outside of the organization, the user enters the login information as "[email protected]" and receives the error "Cannot find your…
The correct answer is C. Remove the cisco-uds SRV record for the external DNS. The cisco-uds SRV record in external DNS causes Jabber to attempt a direct connection to CUCM from outside the network, which fails; removing it forces Jabber to use the collab-edge path via Expressway.
Question
Refer to the exhibit. When a Jabber user attempts to connect from outside of the organization, the user enters the login information as "[email protected]" and receives the error "Cannot find your services Automatically". The engineer tries to resolve SRV records used by Jabber. DNS A record "expressway-e.example.com" points to the Expressway-E IP and "cucm.example.com" points to the Cisco Unified Communications Manager. Which change resolves the DNS problem?
Exhibit
Options
- AChange cisco-uds to point to the Expressway-E FQDN.
- BChange the collab-edge record to point to 5061.
- CRemove the cisco-uds SRV record for the external DNS.
- DChange the priority of the SRV record for cisco-uds.
How the community answered
(22 responses)- A14% (3)
- B9% (2)
- C73% (16)
- D5% (1)
Why each option
The cisco-uds SRV record in external DNS causes Jabber to attempt a direct connection to CUCM from outside the network, which fails; removing it forces Jabber to use the collab-edge path via Expressway.
Pointing cisco-uds to Expressway-E is incorrect because cisco-uds is intended for direct CUCM communication and Expressway-E does not serve that UDS interface.
The collab-edge record should point to port 8443, not 5061; changing it to 5061 would break the HTTPS-based edge discovery mechanism.
Jabber's service discovery uses DNS SRV records to locate services. When an external user queries DNS and finds a cisco-uds record, Jabber attempts to reach CUCM directly, which is unreachable externally. Removing cisco-uds from external DNS causes Jabber to fall back to the _collab-edge SRV record, correctly routing the connection through Expressway-E for Mobile and Remote Access.
Changing the priority of cisco-uds would still leave the record present in external DNS, and Jabber would still attempt to reach CUCM directly before or instead of using collab-edge.
Concept tested: Jabber MRA external DNS SRV record configuration
Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_0/cjab_b_planning-guide-cisco-jabber-12_0/cjab_b_planning-guide-cisco-jabber-12_0_chapter_01010.html
Topics
Community Discussion
No community discussion yet for this question.