300-820 · Question #129
An administrator is deploying Cisco Expressways for Mobile and Remote Access. The registration domain is "example.com", and the Expressway-E FQDN is "expe.example.com". Cisco Jabber clients on the…
The correct answer is A. _collab-edge._tls.example.com. For Cisco Jabber clients on the internet to discover the Expressway-E via Mobile and Remote Access (MRA), the public DNS must contain the SRV record '_collab-edge._tls.<registration_domain>'. Since the registration domain is 'example.com', the record must be…
Question
An administrator is deploying Cisco Expressways for Mobile and Remote Access. The registration domain is "example.com", and the Expressway-E FQDN is "expe.example.com". Cisco Jabber clients on the internet cannot discover services via DNS lookup. Which SRV records must be configured in the public DNS to allow Service Discovery?
Options
- A_collab-edge._tls.example.com
- B_cisco-uds_tcp.expe.example.com
- C_cisco-uds_tcp.example.com
- D_collab-edge_tls.expe.example.com
How the community answered
(44 responses)- A95% (42)
- B2% (1)
- D2% (1)
Explanation
For Cisco Jabber clients on the internet to discover the Expressway-E via Mobile and Remote Access (MRA), the public DNS must contain the SRV record '_collab-edge._tls.<registration_domain>'. Since the registration domain is 'example.com', the record must be '_collab-edge._tls.example.com', pointing to the Expressway-E FQDN (expe.example.com). Jabber first queries this SRV record to locate the edge server for MRA. The '_cisco-uds._tcp' records are used for internal UC service discovery within the corporate network, not for external MRA discovery. SRV records for MRA are always scoped to the registration domain, not the Expressway-E's own FQDN.
Topics
Community Discussion
No community discussion yet for this question.