Cisco Jabber and your XML file

Greetings! I know not many people read this blog. Primarily because I’ve rarely posted anything. I am starting to get some traction putting a few things up here and essentially it’s for my own use. For years I’ve benefited from other notes and blogs from other engineers. I think it’s time I started contributing. Smile


Cisco Jabber for Windows, Mac, iPhone, iPad and Android. You want to support all of these devices on your Cisco Collaboration system? You’re in for a special treat. Each different client has it’s own configuration parameters. Some of the clients need device level configuration. Some of the other devices need the jabber-config.xml file.

Specifically Jabber for Mac 8.6.6 seems to have some issues using the jabber-config.xml. Users are getting SSL prompts and directory lookup issues with Jabber for Mac 8.6.6. It is good to note here that Jabber for Mac 9.2 is in beta and should be released this month. Jabber for Mac 9.2 really fixes a lot of issues and hopefully will be available very soon.

I’ve been pushing for years that corporations move to a UPN login method. Meaning “” when logging into their PC, their Microsoft domain, and applications. As a general rule of thumb a users Microsoft UPN equals their primary SMTP.. and this should equal primary SIP URI.

“UPN=SMTP=SIPURI” – essentially these three values define the domain the user is in. These values are also unique across all your domains to contact your user.

Below you’ll see my sample XML that is using an integration with Cisco IM and Presence and Cisco Communications Manager 9.1.1b. This integration uses “mail” mapping to the user logon name.

The XML file needed is for obvious reasons. The Jabber client downloads this file from the Communications Manager TFTP service. I have an open TAC case to work with the LDAP connection issues and I’ll post back here with results.

If you’re looking for a decent tool to help generate your jabber-config.xml file; check out this link –

Sample jabber-config.xml:

<?xml version=”1.0″ encoding=”utf-8″?>
<config version=”1.0″>

4 thoughts on “Cisco Jabber and your XML file

  1. Hi there! I know this is kinda off topic however , I’d figured I’d ask.
    Would you be interested in exchanging links or maybe guest writing a blog article or vice-versa?
    My website addresses a lot of the same topics as yours and I believe we could greatly benefit from each other.
    If you are interested feel free to shoot me an e-mail.
    I look forward to hearing from you! Fantastic blog by the way!

    • Never really thought about my blog as “fantastic”. I have a lot more material I need to write about. I’m kind of in a niche IT market and my ramblings only attract a small subset of the IT geek population.

  2. By any chance have you worked with multiple domains? I can get the search field working for the EDI clients (Windows), but not for the BDI (MAC) clients.

    • Are you talking multiple Active Directory domains? The trick there is you need to aggregate all of the directory information into AD LDS and then connect Communications Manager to your LDS instance. Tricky and complicated but the only real way to do it. They are making improvements for multi-forest capabilities in version 10.0 and 10.5 Communications Manager.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.