PDF(151.5 KB) View with Adobe Reader on a variety of devices
Updated:June 10, 2015
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the configurations required in order to use flexible instant messaging (IM) address scheme with Cisco Jabber. The feature is supported from Cisco Jabber version 10.6 and later and IM Presence server 10.x. You can deploy this feature if there are users based on multiple domains that coexist in the same presence deployment. Furthermore, a user can still log into Jabber with the respective sAMAccountName attribute, even though the IM address is mapped to the Directory Uniform Resource Identifier (URI) field.
Cisco recommends that you have basic knowledge of Cisco Jabber for Windows, Cisco Unified Communications Manager (CUCM) and Cisco Unified Communications Manager IM and Presence.
The information in this document is based on these software and hardware versions:
Cisco Unified Communications Manager IM and Presence version 10.x or later
Cisco Unified Communications Manager version 10.x or later
All Jabber clients that run on Windows, Mac, IOS and Android version 10.6 or later
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Configure the Server
The available IM address schemes in the Advanced Presence Settings are:
Change the IM address scheme to Directory URI in order to support multiple domains as this procedure shows:
Ensure the Directory URI field is mapped to the desired Lightweight Directory Access Protocol (LDAP) attribute. Possible attributes are msRTCSIP-primaryuseraddress and mail. Check for this in the LDAP Directory configuration page in CUCM.
Choose System > LDAP > LDAP Directory. Click the configured LDAP. In the Standard User Fields To Be Synchronized area of the LDAP Directory window verify that the LDAP Attribute field for Directory URI is correct.
Disable High Availability in the IM&P cluster.
Note: From IM and Presence versions 10.x and later, the high availability option is rebranded as Presence Redundancy Groups in Cisco CallManager. Choose System > Presence Redundancy Groups > DefaultCUPSubcluster and uncheck Enable High Availability in order to disable high availability.
Stop these services in the IM&P server:
Cisco Presence Engine
Cisco SIP Proxy
Cisco XCP Router
Cisco Sync Agent
Cisco Client Profile Agent
Choose IM and Presence Administration > Presence > Settings > Advanced Configuration, click the IM Address Scheme radio button and choose Directory URI from the drop-down list.
Start the services.
Configure the parameters in this section in the jabber-config.xml file. In this example, the DirectoryURI field is mapped to the mail attribute in Active Directory.
Jabber for MAC/Mobile Clients Basic Directory Integration (BDI)