The jabber-config.xml file is an essential piece of configuration for the Jabber client. Sure, the client has the ability to operate just fine without this file. Video calling, deskphone control, instant messaging, etc. all work flawlessly. However, if you need to add any additional options, policies, or directory integrations, the jabber-config.xml file becomes necessary. Within the realm of the CCIE Collaboration certification, we are specifically concerned about two different configurations: UDS Directory Integration and SIP URI Dialing.
User Data Service (UDS) simply put, is the name for the End User database within Cisco Unified Communications Manager (CUCM). It contains all relevant information about that user, as would any other directory. UDS, however, is not enabled by default on the Jabber client. In fact, Jabber is geared towards integration with an LDAP source “out of the box”. This means that we must instruct the Jabber client to use UDS if we would like to be able to search the CUCM database to communicate with other users. Since this will have to be done by using the jabber-config.xml file, we must first determine how to create it. Thankfully, the Cisco documentation does not disappoint in this regard. From the Product/Technology Support page (http://www.cisco.com/cisco/web/psa/default.html?mode=prod), navigate to Collaboration Endpoints → Software Clients → Jabber for Windows → Install and Upgrade Guides → Cisco Jabber for Windows 9.7 Installation and Configuration Guide → Configure Cisco Jabber → Example Configuration. At this point, a wonderful example for the jabber-config.xml file format is displayed.
You can easily copy and paste the format of the configuration file to Notepad++ (which is available to you in the lab) and begin adding/removing the proper XML tags. But what are the proper tags? To find out, we must navigate to a different section of this document, called “Integrate with Directory Sources”. Once there, click the “UDS Integration” link to reveal the necessary configuration.
As you can see, this is a pretty self-contained configuration. The proper XML tags are available for use within our custom jabber-config.xml file. The first tag, “DirectoryServerType” simply specifies the type of integration that we should be using, which of course, is UDS. Believe or not, the other two XML tags, “UdsServer” and “UdsPhotoUriWithToken” are not necessary unless there are specific requirements. At this point, the jabber-config.xml file can be built to allow for UDS integration.
Next, to allow for SIP URI Dialing to take place, we must search for a parameter to satisfy the requirement. Within the “Configure Cisco Jabber” section of the same document, click the “Common Policies” link to reveal a list of available policies. In this list, you will find a parameter called “EnableSIPURIDialling”, which has a value of “true” or “false”. This parameter can be used within the “Policies” section of the jabber-config.xml file to enable URI dialing. The file can now be configured as shown below.
The last step is uploading the file, named exactly as jabber-config.xml, to the CUCM TFTP servers that are assigned to provide configuration files to the Jabber client. Remember to restart the Cisco TFTP Service in Cisco Unified Serviceability! With that, the Jabber client will now have ability to search the CUCM directory and dial Directory URIs accessible by the configured dial plan.
I hope this blog was helpful for you in your CCIE Collaboration preparation! As always, give us a call and speak with a training adviser if you’re interested in purchasing our workbooks, attending a class, or have any questions regarding your preparation. Thanks again for reading and good luck in your preparation!