How to assign jabber-config.xml to Jabber for Android

[Miquel Bover]

Hello team,

I have a CUCM version 10.5.2.10000-5, and I have assigned (and works fine) jabber-config.xml fulfilling the the CSF device "Cisco Support Field" with the "configurationFile=group_configuration_file_name.xml" string.

The problem is that in the CUCM, the Jabber Android device configuration have not the "Cisco Support Field".

Somebody knows how to assign jabber-config.xml to Jabber for Android device?

Best regards,

Miquel Bover

[Sankar Voleti · Accepted solution]

Miquel,

     Jabber mobile clients such as iPhone and Android do not have the support for device specific configuration file unlike Windows client. But they do request jabber-config.xml file (also referred to as global configuration file) from the TFTP server by default during the login.

Hope this helps.

-Sankar

[Miquel Bover]

Hello Gangabhavani,

Thank you for your answer, I knew that is not possible load a device specific configuration xml file for iPhone, see below Bug link:

Bug CSCut45027 - Correct the Jabber Deployment guide for Cisco Support field

https://tools.cisco.com/quickview/bug/CSCut45027

Description (partial)

Symptom:
Cisco Jabber iOS doesn't support the 'Cisco Support field' option available on the Device page. However, the deployment guide says it supported for mobile devices, this statement may misguide like it apply for Jabber iOS too. Need to correct the statement "Cisco Jabber for mobile devices" to  "Cisco jabber for mobile devices ( Except Jabber iOS)".

But I thought that is was possible for Android.

Let me explain my issue:

I have created a Global configuration xml file for Android, iPhone, and MAC (and have another device specific configuration for Windows whiche are working fine) , see below:

jabber-config.xml file:

<?xml version="1.0" encoding="utf-8"?>

<config version="1.0">

<Directory>

   <BDIEnableTLS>0</BDIEnableTLS>

   <ServerPort1>389</ServerPort1>

   <BDIConnectionUsername>Ciscoucm</BDIConnectionUsername>

   <BDIConnectionPassword>xxxxxxxx</BDIConnectionPassword>

</Directory>

</config>

It seems not be loaded or not working for Android and iPhone devices.

Is the xml file configured ok?

How can I check if the mobile devices loads the xml file right?

Best regards

[Sankar Voleti]

Looks like you are missing some of the BDI parameters that should exist in the file. Can you add these and try again?

<DirectoryServerType>BDI</DirectoryServerType>

<BDILDAPServerType>AD</BDILDAPServerType> (assuming you are not using OpenLdap)

<BDIPrimaryServerName>name of ldap goes here</BDIPrimaryServerName>

<BDISearchBase1>name of the search base</BDISearchBase1>

-Sankar

[Miquel Bover]

Hello Gangabhavani,

You were right, after modify the jabber-config.xml file it works fine, below you can see the xml file:

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
 <Directory>
   <DirectoryServerType>BDI</DirectoryServerType>
   <PrimaryServerName>10.31.48.101</PrimaryServerName>
   <BDIPrimaryServerName>10.31.48.101</BDIPrimaryServerName>
   <ServerPort1>389</ServerPort1>
   <BDIServerPort1>389</BDIServerPort1>
   <SecondaryServerName>10.31.48.102</SecondaryServerName>
   <BDISecondaryServerName>10.31.48.102</BDISecondaryServerName>
   <ServerPort2>389</ServerPort2>
   <BDIServerPort2>389</BDIServerPort2>
   <ConnectionUsername>user</ConnectionUsername>
   <BDIConnectionUsername>user</BDIConnectionUsername>
   <ConnectionPassword>xxxxxxxx</ConnectionPassword>
   <BDIConnectionPassword>xxxxxxxx</BDIConnectionPassword>
   <LDAPServerType>AD</LDAPServerType>
   <BDILDAPServerType>AD</BDILDAPServerType>
   <UseJabberCredentials>false</UseJabberCredentials>
   <BDIUseJabberCredentials>false</BDIUseJabberCredentials>
   <SearchBase1>dc=company,dc=local</SearchBase1>
   <BDISearchBase1>dc=company,dc=local</BDISearchBase1>
 </Directory>
</config>

Thank you!

Miquel Bover

[Fedor Solovev]

Hi, guys.

Just to add a comment - CUCM 11.5 has Cisco Support Field on BOT, TCT and TAB devices.