# Cisco Jabber service discovery and sign-in Canonical: https://warmtransfer.net/knowledge/cisco-jabber-service-discovery Last verified: 2026-09-25 The Cisco Jabber client uses service discovery to identify available services and establish connections[^56][^46]. For initial sign-in, users provide an email-style address (username@domain) or use a configuration URL that specifies the ServicesDomain parameter[^14]. ## Discovery sequence and DNS lookups Before querying DNS SRV records, Jabber sends HTTPS requests to the Cisco Webex Platform Service to evaluate whether to enter team messaging mode[^56]. During discovery, the client also issues an HTTP query to a Central Authentication Service (CAS) URL for Webex Messenger to verify whether the sign-in domain is a valid Webex domain[^5]. When querying DNS SRV records, Jabber requests `_cisco-uds` and `_collab-edge` in that specific order of priority[^46]: - If the name server returns the `_cisco-uds` record, Jabber determines it is on the corporate network and connects directly to Cisco Unified Communications Manager[^50]. - If the name server returns the `_collab-edge` record, Jabber attempts to reach the internal network using Expressway for Mobile and Remote Access (MRA)[^8]. Jabber 9.6 and later can discover services using the legacy `_cuplogin` SRV record, but the `_cisco-uds` record takes precedence when present[^11]. Manual connection settings entered from the sign-in screen override SRV records and, on Jabber for Windows, take priority over the bootstrap file[^32][^31]. In hybrid deployments, the `VOICE_SERVICES_DOMAIN` installer parameter (or `VoiceServicesDomain` in the configuration URL) directs Jabber to use an alternative DNS domain for SRV lookups instead of the services domain[^53]. Once `_cisco-uds` is located, the client attempts to connect to the first 2 servers within 20 seconds[^48]. The planning guide's example `_cisco-uds._tcp.example.com` record uses priority 1, weight 5, port 8443, and target host `cucm1.example.com`[^52]. ## Cluster discovery and profile retrieval Locating the home cluster provides the client with the user's device list and allows automated registration with Cisco Unified Communications Manager[^28]. In multi-cluster environments, the Intercluster Lookup Service (ILS) allows Jabber to identify the home cluster and discover services[^29]. In Cisco's 12.x preferred architecture, Jabber discovers the home cluster using the UDS `/cucm-uds/clusterUser` resource, then invokes `/cucm-uds/servers` to enumerate all UDS nodes in that cluster to load-balance subsequent requests across them[^47]. The 12.x architecture recommends publishing `_cisco-uds` SRV records for all Unified CM publisher and TFTP subscriber nodes[^40]. Following home cluster identification, Jabber retrieves the user's service profile—which provides the UC service addresses, settings, and client configuration—and extracts the authenticator from that profile[^44]. Cisco advises configuring each service in the service profile with a fully qualified domain name (FQDN) rather than an IP address or hostname, as public CAs generally require an FQDN[^26]. ## DNS architectures and MRA configuration Cisco documents 2 DNS designs: a separate-domain design with distinct internal and external domains, and a same-domain design that is either split-brain or non-split-brain[^12]. In separate-domain designs, external name servers may forward requests to other external servers but cannot forward requests to internal name servers[^19]. For Mobile and Remote Access: - Public external DNS must publish `_collab-edge._tls.` SRV records pointing to the Expressway-E FQDN on port 8443 so endpoints discover Expressway-E servers[^41][^9]. - `_cisco-uds` SRV records must not resolve externally; resolving them externally prevents Jabber from initiating MRA negotiation through Expressway-E[^51]. - Internal `_cisco-uds._tcp.` SRV records are recommended for MRA by Cisco, but starting in Expressway X12.5 they are not required[^49]. - Internal forward and reverse DNS records are required for every Unified Communications node deployed with MRA[^27]. - In multi-cluster setups, MRA requires Home Cluster Discovery, with users configured with the Home Cluster field set in End User Configuration so Expressway-C routes them correctly, with ILS as the recommended mechanism[^35]. - Expressway server certificates must include the Client Authentication extension (Expressway rejects uploads without it), and the Subject Alternative Names (SAN) must contain the Unified CM registration domains, XMPP federation domains, and IM and Presence chat node aliases if federated group chat is deployed[^7][^18]. - The external firewall must allow inbound TCP 5061 (SIP), TCP 8443 (HTTPS), TCP 5222 (XMPP) and UDP 36002-59999 (media) to Expressway-E for MRA[^34]. Minimum versions specified in the Expressway X15.2 MRA deployment guide are Expressway X8.1.1, Unified CM 10.0, and IM and Presence Service 10.0[^37]. Minimum compatible Jabber versions listed in that guide are Windows 9.7, Mac 9.6, Android 9.6, and iPhone/iPad 9.6.1[^36]. ## Certificate handling and validation When connecting to UC services: - Self-signed certificates generate an accept/decline prompt for the user, while CA-signed certificates deployed by an administrator connect without prompting[^42]. - Accepting an untrusted certificate establishes the connection and saves the certificate, while declining it causes the connection to fail[^6]. - Jabber on Android 7.0 and later only accepts CA-signed certificates[^3]. SRV records can be verified using `nslookup` (setting query type to SRV and querying names such as `_cisco-uds._tcp.`), where a failure returns a "Non-existent domain" error[^38]. Cisco also directs administrators to the SRV check tool in the Collaboration Solutions Analyzer (CSA) to validate records, verifying whether `_collab-edge` resolves and TCP 8443 is reachable[^10]. ## Lifecycle Cisco Jabber for Windows, Mac, and VDI versions 12.8.x and 12.9.x reached end of sale, end of software maintenance, end of vulnerability support, and last date of support on July 31, 2026[^15]. The end-of-life announcement advises customers to upgrade to the latest Cisco Jabber release[^16]. As of 2026-09-25, Cisco's Jabber for Windows release-notes listing includes release notes for Jabber 15.0, 15.1, 15.2, and 15.3, with 15.3 the highest version listed[^2]. ## See also See also [Expressway and Mobile and Remote Access](https://warmtransfer.net/knowledge/cucm-expressway-mra). See also [Setting up Mobile and Remote Access on Cisco Expressway](https://warmtransfer.net/knowledge/expressway-mra-setup). ## Applicability The Expressway X15.2 documentation specifies minimum versions of Expressway X8.1.1, Unified CM 10.0, IM and Presence Service 10.0, and client releases of Windows 9.7, Mac 9.6, Android 9.6, and iPhone/iPad 9.6.1[^37][^36]. Jabber 12.8.x and 12.9.x across Windows, Mac, and VDI reached end of sale and end of support on July 31, 2026[^15]. ## What remains uncertain WarmTransfer's reading of the sources is that because the newest Jabber planning and on-premises deployment guides on Cisco's Jabber for Windows series page as of 2026-09-25 are for release 14.1 (dated April 2024) even though 15.x clients have shipped, service-discovery guidance for 15.x is presumably the 14.1 text, but Cisco does not state this[^1]. ## Sources [^1]: As of 2026-09-25 the newest Jabber planning and on-premises deployment guides on Cisco's Jabber for Windows series page are for release 14.1 (dated April 2024), even though 15.x clients have shipped. Service-discovery guidance for 15.x is therefore presumably the 14.1 text, but Cisco does not state this (inferred). Source: [Cisco Jabber for Windows - Support series page](https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/series.html), Planning and deployment guides list. Checked 2026-09-25. [^2]: Cisco's Jabber for Windows release-notes listing includes release notes for Jabber 15.0, 15.1, 15.2 and 15.3, with 15.3 the highest version listed as of 2026-09-25. Source: [Cisco Jabber for Windows - Release Notes](https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-release-notes-list.html), Release Notes list, PDF entries. Checked 2026-09-25. [^3]: Jabber on Android 7.0 and later recognizes only CA-signed certificates. Source: [Planning Guide for Cisco Jabber 14.1 - Security and certificates](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-security-and-certificates-129.html), Certificate signing / CA-signed versus self-signed. Checked 2026-09-25. [^4]: The Jabber 14.1 planning guide gives the Webex Messenger CAS lookup URL as https://loginp.webexconnect.com/cas/FederatedSSO?org=. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Cisco Webex Messenger / CAS lookup subsection of Service discovery chapter. Checked 2026-09-25. [^5]: During service discovery the Jabber client issues an HTTP query to a Central Authentication Service (CAS) URL for the Webex Messenger service to determine whether the sign-in domain is a valid Webex domain. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), How the Client Discovers Available Services. Checked 2026-09-25. [^6]: If a user accepts an untrusted certificate, Jabber connects and saves the certificate. If the user declines it, the connection to that service fails. Source: [Planning Guide for Cisco Jabber 14.1 - Security and certificates](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-security-and-certificates-129.html), Certificate validation process. Checked 2026-09-25. [^7]: The Expressway server certificate used for MRA must include the Client Authentication extension, and Expressway refuses to upload a certificate without it. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-2/mra/exwy_b_mra-deployment-guide-x152/exwy_m_requirements-for-mra.html), CSR Requirements for Expressway Servers. Checked 2026-09-25. [^8]: When the name server returns the _collab-edge SRV record, the Jabber client tries to reach the internal network through Expressway for Mobile and Remote Access. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), How the Client Discovers Available Services. Checked 2026-09-25. [^9]: The _collab-edge SRV record points to the Expressway-E FQDN on port 8443. Source: [Resolve Collaboration Edge Most Common Issues](https://www.cisco.com/c/en/us/support/docs/unified-communications/expressway/118798-technote-cucm-00.html), Log in issues: _collab-edge SRV record / port 8443. Checked 2026-09-25. [^10]: Cisco points to the SRV check tool in the Collaboration Solutions Analyzer (CSA) for validating Jabber SRV records, including whether _collab-edge resolves and TCP 8443 is reachable. Source: [On-Premises Deployment for Cisco Jabber 14.1 - Configure Service Discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_onprem-deployment-for-jabber141/cjab_b_deploy-jabber-on-premises-129_chapter_01101.html), Configure Service Discovery, Test SRV Records. Checked 2026-09-25. [^11]: Jabber 9.6 and later can still discover services with the legacy _cuplogin SRV record, but a _cisco-uds record takes precedence when present. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Service discovery chapter, _cuplogin note. Checked 2026-09-25. [^12]: The Jabber planning guide describes two DNS designs: a separate-domain design with different internal and external domains, and a same-domain design, which is either split-brain (separate internal and external zones) or not split-brain (one set of name servers). Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Domain Name System Designs. Checked 2026-09-25. [^13]: The Jabber client caches the results of its DNS service-discovery query and loads them on later launches. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Service discovery chapter, cached discovery results. Checked 2026-09-25. [^14]: For service discovery at first sign-in, users enter an email-style address (username@domain), or open a configuration URL that carries the ServicesDomain parameter. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Service discovery chapter, user input / URL configuration. Checked 2026-09-25. [^15]: Cisco Jabber for Windows, Mac and VDI 12.8.x and 12.9.x reached end of sale, end of software maintenance, end of vulnerability support and last date of support on July 31, 2026. Source: [End-of-Sale and End-of-Life Announcement for the Cisco Jabber for Windows, Mac and VDI version 12.8.x and 12.9.x](https://www.cisco.com/c/en/us/products/collateral/unified-communications/jabber-windows/jabber-12-8-x-12-9-x-eol.html), End-of-life milestones table. Checked 2026-09-25. [^16]: For Jabber 12.8.x and 12.9.x, Cisco's end-of-life notice advises customers to upgrade to the latest Cisco Jabber version. Source: [End-of-Sale and End-of-Life Announcement for the Cisco Jabber for Windows, Mac and VDI version 12.8.x and 12.9.x](https://www.cisco.com/c/en/us/products/collateral/unified-communications/jabber-windows/jabber-12-8-x-12-9-x-eol.html), Product migration options. Checked 2026-09-25. [^17]: The Jabber configuration URL parameter ServiceDiscoveryExcludedServices can exclude Webex, CUCM or CUP from service discovery as a comma-separated list, and the URL parameters are case sensitive. Source: [On-Premises Deployment for Cisco Jabber 14.1 - Configure Service Discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_onprem-deployment-for-jabber141/cjab_b_deploy-jabber-on-premises-129_chapter_01101.html), Configure Service Discovery, URL Configuration parameters. Checked 2026-09-25. [^18]: The Expressway-E certificate's Subject Alternative Names must include the Unified CM registration domains and the XMPP federation domains, plus IM and Presence chat node aliases when federated group chat is used. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-2/mra/exwy_b_mra-deployment-guide-x152/exwy_m_requirements-for-mra.html), CSR Requirements for Expressway Servers. Checked 2026-09-25. [^19]: In the separate-domain DNS design, the external name server may forward requests to other external name servers but cannot forward requests to the internal name server. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Separate Domain Design. Checked 2026-09-25. [^20]: Jabber MRA sign-in fails when the _collab-edge SRV record is missing or not externally resolvable, or when TCP 8443 to Expressway-E is blocked. Source: [Resolve Collaboration Edge Most Common Issues](https://www.cisco.com/c/en/us/support/docs/unified-communications/expressway/118798-technote-cucm-00.html), Log in issues: _collab-edge SRV / port 8443 item. Checked 2026-09-25. [^21]: Microsoft DirectAccess can break Jabber MRA sign-in because it tunnels DNS queries into the internal network. Cisco states DirectAccess is not officially supported with MRA. Source: [Resolve Collaboration Edge Most Common Issues](https://www.cisco.com/c/en/us/support/docs/unified-communications/expressway/118798-technote-cucm-00.html), Log in issues: Microsoft DirectAccess item. Checked 2026-09-25. [^22]: MRA sign-in can fail when the Expressway-E hostname or domain set on its DNS page does not match the target in the _collab-edge SRV answer. Source: [Resolve Collaboration Edge Most Common Issues](https://www.cisco.com/c/en/us/support/docs/unified-communications/expressway/118798-technote-cucm-00.html), Log in issues: Expressway-E hostname/domain mismatch item. Checked 2026-09-25. [^23]: 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. Source: [Resolve Collaboration Edge Most Common Issues](https://www.cisco.com/c/en/us/support/docs/unified-communications/expressway/118798-technote-cucm-00.html), Log in issues: no UDS servers found in edge configuration. Checked 2026-09-25. [^24]: The Expressway-C status 'Waiting for traversal server info' is caused by the Expressway-C's internal DNS servers holding two A records for the Expressway-E. Source: [Resolve Collaboration Edge Most Common Issues](https://www.cisco.com/c/en/us/support/docs/unified-communications/expressway/118798-technote-cucm-00.html), Log in issues: 'Waiting for traversal server info' item. Checked 2026-09-25. [^25]: An active Webex Connect (Webex Messenger) subscription for the user's domain can redirect Jabber sign-in to Webex. The documented workaround is to exclude the WEBEX service, for example with the installer argument EXCLUDED_SERVICES=WEBEX. Source: [Resolve Collaboration Edge Most Common Issues](https://www.cisco.com/c/en/us/support/docs/unified-communications/expressway/118798-technote-cucm-00.html), Log in issues: WebEx Connect active subscription item. Checked 2026-09-25. [^26]: 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. Source: [Planning Guide for Cisco Jabber 14.1 - Security and certificates](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-security-and-certificates-129.html), Server identity / FQDN requirements. Checked 2026-09-25. [^27]: MRA requires internal forward and reverse DNS records for every Unified Communications node used with MRA. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-2/mra/exwy_b_mra-deployment-guide-x152/exwy_m_requirements-for-mra.html), Local DNS (Internal Domains). Checked 2026-09-25. [^28]: Finding the user's home cluster lets the Jabber client automatically get the user's device list and register with Cisco Unified Communications Manager. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Cisco UDS SRV Record. Checked 2026-09-25. [^29]: With multiple Unified CM clusters, the Intercluster Lookup Service (ILS) lets the Jabber client find the user's home cluster and discover services. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Cisco UDS SRV Record. Checked 2026-09-25. [^30]: The Jabber configuration URL parameter InvalidCertificateBehavior accepts RejectAndNotify or PromptPerSession. Source: [On-Premises Deployment for Cisco Jabber 14.1 - Configure Service Discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_onprem-deployment-for-jabber141/cjab_b_deploy-jabber-on-premises-129_chapter_01101.html), Configure Service Discovery, URL Configuration parameters. Checked 2026-09-25. [^31]: As an advanced option, users can connect to services manually from the Jabber sign-in screen instead of relying on automatic discovery. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Service discovery chapter, manual connection settings. Checked 2026-09-25. [^32]: Manual connection settings take priority over SRV records and, for Jabber for Windows, over the bootstrap file. Source: [On-Premises Deployment for Cisco Jabber 14.1 - Configure Service Discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_onprem-deployment-for-jabber141/cjab_b_deploy-jabber-on-premises-129_chapter_01101.html), Configure Service Discovery, Manual Connection Settings. Checked 2026-09-25. [^33]: From Unified CM 12.0, administrators can assign per-user Mobile and Remote Access access policies that limit Jabber over MRA to no service, IM and Presence only, or IM and Presence plus voice and video calls. Source: [On-Premises Deployment for Cisco Jabber 14.1 - Remote Access](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_onprem-deployment-for-jabber141/cjab_b_deploy-jabber-on-premises-129_chapter_010001.html), Remote Access, Mobile and Remote Access Policies. Checked 2026-09-25. [^34]: The external firewall must allow inbound TCP 5061 (SIP), TCP 8443 (HTTPS), TCP 5222 (XMPP) and UDP 36002-59999 (media) to Expressway-E for MRA. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-2/mra/exwy_b_mra-deployment-guide-x152/exwy_m_requirements-for-mra.html), Firewall Configuration. Checked 2026-09-25. [^35]: With multiple Unified CM clusters, MRA requires Home Cluster Discovery. End users must have the Home Cluster field set in End User Configuration so that Expressway-C can send them to the correct cluster, and ILS is the recommended approach. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-2/mra/exwy_b_mra-deployment-guide-x152/exwy_m_requirements-for-mra.html), Unified CM Requirements, Multiple Unified CM clusters. Checked 2026-09-25. [^36]: The X15.2 MRA guide lists these MRA-compatible Jabber minimums: Windows 9.7, iPhone/iPad 9.6.1, Android 9.6 and Mac 9.6. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-2/mra/exwy_b_mra-deployment-guide-x152/exwy_m_requirements-for-mra.html), MRA-Compatible Client Versions (Table 6). Checked 2026-09-25. [^37]: The X15.2 MRA guide lists minimum versions of Expressway X8.1.1, Unified CM 10.0 and IM and Presence Service 10.0. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-2/mra/exwy_b_mra-deployment-guide-x152/exwy_m_requirements-for-mra.html), Product Versions (Table 3). Checked 2026-09-25. [^38]: Cisco documents testing Jabber SRV records with nslookup (set type=SRV, then query e.g. _cisco-uds._tcp.). A failed lookup returns a 'Non-existent domain' error. Source: [On-Premises Deployment for Cisco Jabber 14.1 - Configure Service Discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_onprem-deployment-for-jabber141/cjab_b_deploy-jabber-on-premises-129_chapter_01101.html), Configure Service Discovery, Test SRV Records. Checked 2026-09-25. [^39]: The Jabber 14.1 on-premises deployment guide's _cisco-uds example shows priority 0, weight 0, port 8443 and an SRV target written as _cisco-uds._tcp.example.com instead of a server hostname, which conflicts with the planning guide example and with SRV semantics (disputed). Source: [On-Premises Deployment for Cisco Jabber 14.1 - Configure Service Discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_onprem-deployment-for-jabber141/cjab_b_deploy-jabber-on-premises-129_chapter_01101.html), Configure Service Discovery, SRV record example. Checked 2026-09-25. [^40]: Cisco's 12.x preferred architecture recommends publishing _cisco-uds SRV records for all Unified CM publisher and TFTP subscriber nodes. Source: [Preferred Architecture for Cisco Collaboration 12.x Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/12x/120/collbcvd/control.html), DNS SRV records for service discovery (Example 2-1 context). Checked 2026-09-25. [^41]: For Mobile and Remote Access, public external DNS must contain _collab-edge._tls. SRV records so that endpoints can discover the Expressway-E servers. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-2/mra/exwy_b_mra-deployment-guide-x152/exwy_m_requirements-for-mra.html), Public DNS (External Domains). Checked 2026-09-25. [^42]: When services present self-signed certificates, Jabber users are always prompted to accept or decline them. With administrator-deployed CA-signed certificates, users are not prompted. Source: [Planning Guide for Cisco Jabber 14.1 - Security and certificates](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-security-and-certificates-129.html), Certificate signing / CA-signed versus self-signed. Checked 2026-09-25. [^43]: The servers that present certificates to Jabber include Unified CM (HTTP/Tomcat and CallManager), IM and Presence (HTTP/Tomcat and XMPP), Unity Connection (HTTP/Tomcat), and Expressway-E (one server certificate for HTTP, XMPP and SIP). Source: [Planning Guide for Cisco Jabber 14.1 - Security and certificates](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-security-and-certificates-129.html), Required certificates / servers presenting certificates. Checked 2026-09-25. [^44]: After finding the home cluster, the Jabber client retrieves the user's service profile, which holds the addresses and settings for UC services and client configuration, and it takes the authenticator from that profile. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Cisco UDS SRV Record. Checked 2026-09-25. [^45]: On a fresh installation, the SERVICES_DOMAIN installer parameter lets Jabber skip the email-address screen. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Service discovery chapter, installer / customization options. Checked 2026-09-25. [^46]: The Jabber client requests the DNS SRV records _cisco-uds and _collab-edge, in that order of priority. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), How the Client Discovers Available Services. Checked 2026-09-25. [^47]: In Cisco's 12.x preferred architecture, Jabber locates the home cluster with the UDS /cucm-uds/clusterUser resource, then calls /cucm-uds/servers to list all UDS nodes in that cluster so that later UDS requests are load-balanced across them. Source: [Preferred Architecture for Cisco Collaboration 12.x Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/12x/120/collbcvd/control.html), DNS requirements / Endpoints discussion of UDS service discovery. Checked 2026-09-25. [^48]: Once Jabber finds _cisco-uds during service discovery, it tries to connect to the first two servers within 20 seconds. Source: [On-Premises Deployment for Cisco Jabber 14.1 - Configure Service Discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_onprem-deployment-for-jabber141/cjab_b_deploy-jabber-on-premises-129_chapter_01101.html), Configure Service Discovery, UDS failover note. Checked 2026-09-25. [^49]: Cisco recommends internal _cisco-uds._tcp. SRV records for MRA, but from Expressway X12.5 they are no longer a requirement. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-2/mra/exwy_b_mra-deployment-guide-x152/exwy_m_requirements-for-mra.html), Local DNS (Internal Domains). Checked 2026-09-25. [^50]: When the name server returns the _cisco-uds SRV record, the Jabber client concludes it is inside the corporate network and connects to Cisco Unified Communications Manager. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), How the Client Discovers Available Services. Checked 2026-09-25. [^51]: _cisco-uds SRV records must not be resolvable from outside the internal network; if they are, Jabber will not start MRA negotiation through Expressway-E. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-2/mra/exwy_b_mra-deployment-guide-x152/exwy_m_requirements-for-mra.html), Local DNS (Internal Domains). Checked 2026-09-25. [^52]: The Jabber planning guide's example _cisco-uds._tcp.example.com SRV record uses priority 1, weight 5, port 8443 and target host cucm1.example.com. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Cisco UDS SRV Record. Checked 2026-09-25. [^53]: The VOICE_SERVICES_DOMAIN parameter (VoiceServicesDomain in the configuration URL) tells Jabber to use a different DNS domain for SRV lookups than the services domain, and is used in hybrid deployments. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Service discovery chapter, installer / URL configuration. Checked 2026-09-25. [^54]: In hybrid deployments where the IM and Presence domain differs from the voice domain, the Voice Services Domain is what Jabber uses to locate the _collab-edge record. Source: [On-Premises Deployment for Cisco Jabber 14.1 - Remote Access](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_onprem-deployment-for-jabber141/cjab_b_deploy-jabber-on-premises-129_chapter_010001.html), Remote Access, service discovery requirements. Checked 2026-09-25. [^55]: When the voice services domain is the same as the sign-in domain, the Jabber 14.1 planning guide says not to configure voiceservicesdomain for MRA. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), Service discovery chapter, note under voice services domain. Checked 2026-09-25. [^56]: Before querying DNS SRV records, the Cisco Jabber client issues HTTPS requests to the Cisco Webex Platform Service to decide whether it enters team messaging mode. Source: [Planning Guide for Cisco Jabber 14.1 - Service discovery](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-service-discovery-129.html), How the Client Discovers Available Services. Checked 2026-09-25.