Source note · Cisco Jabber service discovery and sign-in
If Expressway-C cannot resolve internal _cisco-uds SRV records, the edge configuration returned to Jabber contains no UDS servers, which Cisco says is common in dual-domain deployments.
Checked 2026-09-25
- Vendor
- Cisco
- Product
- Cisco Expressway
- Subsystem
- sign-in failures
- Deployment
- on-premises
- Region
- not restricted
- Release range
- Expressway releases before X12.5 (UDS SRV no longer required from X12.5)
- Checked
- 2026-09-25
Sources
- Resolve Collaboration Edge Most Common Issues — Cisco Systems · tier 2 current vendor documentation · Log in issues: no UDS servers found in edge configuration
Cite this note
APA
WarmTransfer. (2026, September 25). Cisco Jabber service discovery and sign-in: source note cisco-jabber-service-discovery-fail-no-uds-in-edge-config. WarmTransfer. https://warmtransfer.net/knowledge/claims/cisco-jabber-service-discovery-fail-no-uds-in-edge-config
BibTeX
@misc{warmtransfer-claim-cisco-jabber-service-discovery-fail-no-uds-in-edge-config,
title = {Cisco Jabber service discovery and sign-in: source note cisco-jabber-service-discovery-fail-no-uds-in-edge-config},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cisco-jabber-service-discovery-fail-no-uds-in-edge-config},
note = {Source note cisco-jabber-service-discovery-fail-no-uds-in-edge-config, checked 2026-09-25}
}