Showing results for 
Search instead for 
Did you mean: 
Walkthrough Wednesdays

Jabber Config File Generator


Please find the attached HTML document, download and open it on your PC.  This provides an easy to use form where you simply answer a few questions and it will render the proper jabber-config.xml file for you to copy/paste.  There is built in logic to verify you are entering in the correct information for the deployment selected, as well as valid XML characters.


The XML file structure is rendered in JavaScript, so you'll still need to copy/paste the contents into a text file and upload the file to your CUCM server, but you can rest assured that the configuration is correct and valid by using this form.


Update 2015-07-09: Updated with 11.0 keys, testing new automated method to mine key values from public facing documentation, new UI. Feedback on the new UI is welcome

Update 2015-03-12: Update default selection for new keys.

Update 2015-02-18: Added more keys from 10.6.

Update 2015-01-28: Update for 10.6 keys.

Update 2014-12-17: Update value generation when using reserved characters (&/&) so that only substitution takes place once.

Update 2014-11-19: Reworked the Jabber-Plugin additions, relaxed hostname verification, more import enhancements, updated missing keys in 10.5, corrected default value selection.

Update 2014-10-22: Updated CSS, corrected a few default values to match updated documentation and user comments in this forum, enhanced import function, added optional Telemetry Suggestion from existing data.

Update 2014-10-09: Added text import of existing jabber-config.xml file to pre-populate the form (works in FireFox & Chrome, IE not tested).  Removed SHA Hash generation of TelemetryCustomerID field.

Update 2014-08-29: Added 10.5 J4W keys which should apply to the other 10.5 releases as well, with additional logic to aid with some of the more complex key configuration.

Update 2014-05-12: Modified UI slightly, also corrected problem with checkbox inputs

Update 2014-05-09: Updated logic to include PhoneMode keys for versions past 9.2; although not all clients support PhoneMode yet.

Update 2014-04-24: Corrected misspelled keys, and validation errors.

Update 2014-04-21: Added J4W 9.7 specific fields, as well as simplifying data entry for BDI fields.  If using BDI, simply make sure you've selected OSX, iOS, or Android, and the script will copy whatever fields you have entered for the EDI integration, and automatically create the BDI specific keys for you.

Update 2014-01-02: Added partial Mac 9.2 specific fields for BDI, Windows 9.6 specific fields.

Update 2013-07-25: Modified Search Base validation logic to include the default CN in addition to OU's

Update 2013-05-17: Added 9.2 specific fields.

Update 2012-12-29: Added 9.1 specific fields and implented version switching for it to work with both 9.0, 9.1, and any future version dependent fields

Update 2012-08-16: resolution to CSCua39052 in Jabber 9.0(4) resolved the Base Filter open/close bracket problem.  Updated validation tests to reflect this change.  As such, this script will only work for Jabber 9.0(4) and later when using a custom Base Filter; if using Jabber prior to 9.0(4), simply remove the last closing bracket in the Base Filter tag before uploading to TFTP.

Cisco Employee

Thanks you for this great and wonderfull tool


Which argument/line will enable the Remote and Mobile Access in version 9.6?



Hi there,

just to let you notice that the tool, when enabling URI Dialing, writes:


that is not working, as Jabber is expecting:



Anyway it's a very nice tool.



Community Member

Great tool, has saved me hours!

Does anyone know if it is possible to force these settings on the clients?

So far, I can see that the Jabber client uses the settings in here the first time, but then if a user changes a setting, like the inactive time, it stays at the user setting, not what is in the jabber-config.xml.





Community Member


This is most helpfull. Could you possibly update this to include the new client parameter "Persistent_Chat_Enabled"?


Bhasker Mistry

Hi Szelenka,

Just had a look at the tool, look pretty useful. I am in the process of integrating CUCILync in 9.2.1 and looks like this also require the creation of a jabber-config.xml file any chance it can be tailored to be used for this?



Did you ever find out if this works for the CUCILync 9.2 client?


Jabber for Mac v9.6 fixed the SSL issues from v9.2.1 & 9.2.2.  So now I've removed the keywords BDIConnectionUsername & BDIConnectionPassword, and let it use a given user's jabber credentials for their directory lookups.






Not sure if I had to, but I also added this part to the top at some point in time. At the state of Jabber development at the time at least I think, it eliminated the user having to enter any hostnames during Jabber setup.

Cisco Employee

It will work with CUCILync.  The only thing that is in CUCILync, that is not in this script are the "Internet Explorer Pop-up" parameters used for the toast notifications.

Matthew Miktus

This is very helpful - thank you.


is there any way to re-name the fields listed under "Directory Attribute Mapping?"  i.e. instead of saying Home or Other, having it say Work2 or Pager?



It works fantastic! thanks

Cisco Employee

The key names are hard coded to those values "Home", "Other", etc.  This allows the client to know which keys to lookup consistently.  However, you can change the value of these keys to whatever attribute exists in the directory.

Matthew Miktus

understood. however, mapping a pager# to "other" and a secondary work phone# to "home" and not having the ability to change this is a pain point to some of my customers.


Bhasker Mistry

I used the generator to script out the directory parameters but had to manually add phone (TFTP, CTI etc) ) and voicemail parameters, would be great if this could be added to the script.


Thanks for updating this generator. FYI, I notice that when I use Exclude Service Discovery option, it will only generate