Upload Jabber Config File to TFTP Server

Use the Jabber Config File Generator to generate the correct XML file. The generator can be found at: https://supportforums.cisco.com/docs/DOC-25778.

For the directory search to work, upload the XML file jabber-config.xml.

  • Download the Jabber Config File Generator.
  • Additional features such as URI dialing and others are enabled with this file generator as well.
<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
 <Options>
   <Set_Status_Away_On_Inactive>false</Set_Status_Away_On_Inactive>
 </Options>
 <Directory>
   <ConnectionType>1</ConnectionType>
   <PrimaryServerName>10.1.5.14</PrimaryServerName>
   <BDIPrimaryServerName>10.1.5.14</BDIPrimaryServerName>
   <ServerPort1>389</ServerPort1>
   <BDIServerPort1>389</BDIServerPort1>
   <UseWindowsCredentials>0</UseWindowsCredentials>
   <ConnectionUsername>Administrator@collab10x.cisco.com</ConnectionUsername>
   <BDIConnectionUsername>Administrator@collab10x.cisco.com</BDIConnectionUsername>
   <ConnectionPassword>Cisco1234</ConnectionPassword>
   <BDIConnectionPassword>Cisco1234</BDIConnectionPassword>
</Directory>
</config>

The generator renders the proper jabber-config.xml file for you after you answer a few questions in an easy-to-use form. Then, you can simply copy and paste the result into an XML file. The generator has built-in logic, which verifies that you are entering the correct information for the deployment selected, as well as valid XML characters.

The figure shows an example XML file with the Jabber Config File Generator-generated content. The example XML file connects to a Microsoft Active Directory server with the IP address 10.1.5.14 and the port 389. The user name is Administrator@collab10x.cisco.com, and the password is Cisco1234. Because the network services are discovered, you do no need to specify a Cisco Unified Communications Manager IP address. In previous Cisco Unified Communications IM and Presence Service versions, the Cisco Unified Communications IM and Presence Service node was contacted first. With Cisco Unified Communications IM and Presence Service Release 10.x, the Cisco Jabber client contacts Cisco Unified Communications Manager first and receives the necessary information from the device-specific configuration file and the jabber-config.xml file.

The XML file structure is rendered in JavaScript, so you still need to paste the contents into a text file (saved as an XML file) and upload the file to the Cisco Unified Communications Manager TFTP server, using exactly the same name jabber-config.xml. Without this XML file, the Cisco Jabber for Windows client will not support the directory search for end users. Other features, such as URI dialing, are also enabled in the Jabber Config File Generator.

Advertisements

Author: drbabbers

ccieme.wordpress.com - my personal journey to ccie