Source note · Cisco Jabber service discovery and sign-in
Cisco advises using an FQDN, not an IP address or bare hostname, for each service in the Unified CM service profile, because public CAs generally require an FQDN as the server identity.
Checked 2026-09-25
Ensure that you specify FQDN in the service profile for each service, instead of the IP address or hostname
- Vendor
- Cisco
- Product
- Cisco Jabber
- Subsystem
- certificates
- Deployment
- on-premises
- Region
- not restricted
- Release range
- Jabber 14.1 documentation
- Checked
- 2026-09-25
Sources
- Planning Guide for Cisco Jabber 14.1 - Security and certificates — Cisco Systems · tier 2 current vendor documentation · Server identity / FQDN requirements
Cite this note
APA
WarmTransfer. (2026, September 25). Cisco Jabber service discovery and sign-in: source note cisco-jabber-service-discovery-fqdn-in-service-profile. WarmTransfer. https://warmtransfer.net/knowledge/claims/cisco-jabber-service-discovery-fqdn-in-service-profile
BibTeX
@misc{warmtransfer-claim-cisco-jabber-service-discovery-fqdn-in-service-profile,
title = {Cisco Jabber service discovery and sign-in: source note cisco-jabber-service-discovery-fqdn-in-service-profile},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cisco-jabber-service-discovery-fqdn-in-service-profile},
note = {Source note cisco-jabber-service-discovery-fqdn-in-service-profile, checked 2026-09-25}
}