PDF(428.5 KB) View with Adobe Reader on a variety of devices
ePub(532.2 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(351.2 KB) View on Kindle device or Kindle app on multiple devices
Updated:September 28, 2018
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 how to map a directory attribute for use in Jabber and then test it without impact to any other user.
Cisco recommends that you have knowledge of:
Cisco Unified Communication Manager (CUCM)
The information in this document is based on these software versions:
Cisco Jabber for Windows 12.0
Cisco Unified Communications Manager 12.0
It is useful to have a test group configuration file on the Trivial File Transfer Protocol (TFTP) servers that can be assigned to a single user to test new configurations before you deploy them to the global jabber-config.xml file.
The first time this file is uploaded to the TFTP server, the TFTP service needs to be restarted.
In this example, you can see how to map the Other phone number on Jabber to the ipPhone Lightweight Directory Access Protocol (LDAP) attribute.
Steps to create the test configuration file:
Step 1. Using your favourite text editor, create a new file with the following content and save it as jabber-config-test.xml.
Note: the value ipPhone is case sensitive and needs to match the directory attribute name
Step 2. Upload the jabber-config-test.xml file to all TFTP servers in the cluster.
Step 3. Restart the TFTP service on all nodes in the cluster.
Step 4. Check that the new configuration file can be displayed in a web browser by navigating to one of the following URLs:
Step 5. Assign the new configuration file to the test user on the Cisco Support Field on the Cisco Services Framework (CSF) device as ConfigurationFile=jabber-config-test.xml.
Step 6. Reset the Jabber client for that user to force fresh configuration download.
On Jabber, click on the Call button for a user that has ipPhone attribute populated in LDAP and confirm the number is displayed in the Other field
Check that the new configuration file is displayed successfully in the web browser.
Check the attribute on LDAP to ensure it is populated.
Jabber logs show the test configuration file is retrieved correctly and that the value for OtherPhone is ipPhone.
DEBUG [0x00000dd0] [ents\ecc\src\config\PhoneConfig.cpp(861)] [csf.ecc] [csf::ecc::SoftphoneConfig::parseOutConfigurationFileName] - Detected that the "Cisco Support Field" has the following content: ConfigurationFile=jabber-config-test.xml