UDS provides a contact source API that can be used by Jabber over Cisco Expressway mobile and remote access (MRA) for the contact source.The UDS contact source uses the Unified CM end user table information to provide a contact lookup service.
Beginning with Cisco Unified CM 11.5, the UDS-to-LDAP Proxy feature can also be used for contact searches. 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. This enables Jabber clients to search a corporate directory that exceeds the maximum number of users supported within Unified CM.
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. 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.
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. 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.
Unified CM User Data Services (UDS)
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.
To ensure that client interaction with the UDS service avoids the publisher node simply deactivate the Cisco User Data Services on the Pubisher Node:
UDS is an integrated network service that runs on all Unified CM servers in a cluster and is critical to server discovery.
Once service discovery, Jabber must authenticate and download a service profile and/or the jabber-config.xml file (if available), which directs the client to additional back-end application services such as voicemail and directory and enables appropriate configuration.
Cisco Jabber Corporate Directory Access Cisco Jabber clients rely on various methods for accessing enterprise contact information. In addition to local device contacts and contacts previously added to Jabber , Jabber clients are also able to access corporate directory services using the following methods:
• Cisco Directory Integration (CDI)
The CDI method of corporate directory access relies on LDAP communication between the Jabber client and supported LDAP compliant directories such as Microsoft Active Directory and OpenLDAP. CDI is the default method of directory integration for on-premises Jabber clients.
In Summary:
UDS usage considerations for on-premise deployments:
• Jabber on-premises (on-net) can use LDAP or UDS as a contact source.
• UDS is a set of HTTP-based services provided by Unified CM. The UDS contact source is one UDS service, which provides contact and number resolution.
• When Jabber is connected remotely over Expressway mobile and remote access, it always uses UDS as a contact source.
SOURCE Cisco Systems, Inc.