A collaboration engineer is troubleshooting an issue with Cisco Jabber for Windows clients. Users in a new branch location report that "cannot locate server" is displayed when they launch the client.

Question

Options

• AAdd a firewall rule to allow TCP/8443 from the branch to HQ.
• BAdd a _cisco-uds._tcp.company.com SRV record to the branch DNS server.
• CReinstall the Jabber clients with UPN_DISCOVERY_ENABLED=false.
• DAdd a _collab-edge._tls.company.com SRV record to the branch DNS server.

• A
  4% (1)
• B
  4% (1)
• C
  8% (2)
• D
  84% (21)

Explanation

When Jabber clients fail auto-discovery but succeed with manual server configuration, the issue is missing DNS SRV records. Because the IM&P servers are at corporate HQ across the WAN, branch clients are connecting as off-network (remote) clients and require Mobile and Remote Access (MRA) via Cisco Expressway. The '_collab-edge._tls.company.com' SRV record is used for off-network/MRA discovery, pointing Jabber to the Expressway-E edge server. Option B (_cisco-uds._tcp) is for on-network internal discovery and would not resolve MRA connectivity. Option A (TCP/8443 firewall) would not help if DNS discovery itself is failing. Option C (UPN_DISCOVERY_ENABLED) is unrelated to this scenario.

No community discussion yet for this question.