This topic describes how Cisco Jabber accesses different resources for contacts.
Cisco Jabber can use different sources to find contacts:
Cisco Jabber must always be deployed with a contact source. Cisco Jabber clients reference contacts using the Jabber ID (JID). Cisco Jabber looks up contacts by using this process:
- An LDAP-based contact source (Enhanced Directory Integration [EDI] or Basic Directory Integration [BDI]) must be used for on-premises deployments. For more information about the differences between BDI and EDI, go to the Configuring Active Directory for Cisco Unified Personal Communicator document and review Table 17-1 (Feature Comparison of Enhanced and Basic Directory Integration) at:http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cups/8_6/english/install_upgrade/deployment/guide/dgactivedirconfig.html.
- Cisco User Data Service (UDS) is used as an HTTP-based or REST-based contact source.
- Custom contacts are nondirectory-based contacts and are stored on the Cisco Unified Communications IM and Presence Service node.
- When using Microsoft Outlook, Cisco Jabber can search for local contacts as well.
This topic describes how Cisco Jabber searches the directory according to the request.
For contact lookup by Jabber ID, use the Account Name:
- (&(objectCategory=person)(objectClass=user) (sAMAccountName=cholland))
In this example, a user searched for the last name Holland and the search scope focuses on the sAMAccountname. After finding a contact, Cisco Jabber presents the result and the contact attributes for the person.
For contact lookup using predictive search, use ANR to locate user objects:
Ambiguous Name Resolution (ANR) is an efficient search algorithm in Microsoft Active Directory that allows you to specify complex filters involving multiple naming-related attributes in a single clause. It can be used to locate objects in Active Directory when you know something about the name of the object, but not necessarily which naming attribute has the information. While ANR is usually used to locate user objects, it can be used to find any class of object in Active Directory.
Contact lookup by telephone number:
- (&(objectCategory=person)(objectClass=user) (telephoneNumber=+1 (408) 555 6666)) (&(objectCategory=person)(objectClass=user) (|(|(|(mobile=+14085555555))(homePhone=14085555555)) (otherTelephone=14085555555)))
The calling number of an incoming call is used to search for a matching contact in the LDAP directory based on the home phone, telephone, and mobile number attributes.
Cisco UDS Directory Access
This topic describes how Cisco Jabber uses Cisco User Data Service (UDS) as a contact source.
Cisco UDS directory integration is used when Cisco Jabber clients are connected via mobile and remote access:
- When performing service discovery, Cisco Jabber will request a list of Cisco UDS nodes in its home cluster.
- Cisco Jabber will randomize the returned list and connect to a node in the cluster.
- Cisco UDS does not support photo objects, so a web source must be used instead.
All nodes in a Cisco Unified Communications Manager cluster run Cisco UDS. Cisco Jabber will request a list of Cisco UDS nodes in its home cluster, randomize the returned list, and connect to a node in the cluster.
A Cisco Unified Communications Manager node can support connections for 50 percent of the total OVA size for the server. For example, the 2500-user Cisco Unified Communications Manager OVA template supports up to 1250 UDS users per server and 5000 in a cluster.
It is not recommended to use service profiles with UDS. UDS settings are not required for mobile and remote access. Cisco TelePresence Video Communication Server Expressway (VCS-E) edge detection will automatically switch the client to UDS as the contact source. Note that Cisco UDS does not provide the full attribute list that LDAP provides.
This topic describes how Cisco Jabber receives contact photos.
The Cisco Jabber experience is greatly enhanced with contact photos:
- All clients now support retrieval of binary photo objects from an LDAP contact source.
- An alternative method for photo retrieval is HTTP from a web server.
Cisco Jabber retrieves and displays contact photos with the following methods:
- URI substitution: Cisco Jabber dynamically builds a URL to connect photos with a directory attribute and a URL template.
- Binary objects: Cisco Jabber retrieves the binary data for the photo from your database. If using binary objects from Microsoft Active Directory, PhotoUriWithToken should not be set in the jabber-config.xml file.
Cisco Jabber supports the following formats for contact photos in your directory: JPG, PNG, BMP, and GIF. Cisco Jabber does not apply any modifications to enhance rendering for contact photos in GIF format. As a result, contact photos in GIF format might render incorrectly or with less than optimal quality. To obtain the best quality, you should use the PNG format for your contact photos. The optimum dimensions for contact photos are 128 pixels by 128 pixels with an aspect ratio of 1:1.
The HTTP method can only be configured in the jabber-config.xml file. Remote users who are using Cisco TelePresence Video Communication Server Expressway (VCS-E) must use the HTTP method to present contact photos.