UDS is an integrated network service that runs on all Unified CM servers in a cluster and is critical to server discovery.

To ensure that client interaction with the UDS service avoids the publisher node simply deactivate the Cisco User Data Services on the Pubisher Node:

The UDS method of corporate directory access relies on HTTP communication between the Jabber client and Unified CM UDS services running on each Unified CM node. This ensures that client interaction with the UDS service avoids the publisher node and instead distributes the load across call processing nodes within the cluster. While the UDS service runs on all nodes in the Unified CM cluster, when configuring DNS SRV records for Unified CM UDS service, administrators should configure records for resolution to Unified CM subscriber nodes only. You can populate the UDS contact source data by using the Unified CM web interface (by creating end users),by using the LDAP sync function to Active Directory or other supported LDAP source, or by using the UDS-to-LDAP Proxy function. The UDS contact service is always used for remote Jabber clients connected over MRA access and it is an optional contact service for clients on the corporate network. This enables Jabber clients to search a corporate directory that exceeds the maximum number of users supported within Unified CM. When enabled, contact searches are still handled by UDS but are proxied to the corporate LDAP directory, with UDS relaying results back to the Jabber client.

The UDS contact source uses the Unified CM end user table information to provide a contact lookup service.īeginning with Cisco Unified CM 11.5, the UDS-to-LDAP Proxy feature can also be used for contact searches. UDS provides a contact source API that can be used by Jabber over Cisco Expressway mobile and remote access (MRA) for the contact source.

Cisco jabber for windows dns srv