Hi asifProblem related to the

Asif Khan · ‎11-20-2014

CuCM-9.1.1

CUPS - 9.1.1

Hi. we have Jabber installed on both MAC and Windows in our environment.

Discovery is provided through UDS and CUP SRV records. All clients have standard AD lookup.

We want to deploy a custom Jabber-config file which will provide settings for both win and Mac clients. Below is the file:

=============================================================================================

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


<PrimaryServerName >A.B.C.D</PrimaryServerName>
<ServerPort1>389</ServerPort1>
<UseWindowsCredentials>1</UseWindowsCredentials>
<SearchBase1>DC=ab,DC=company,DC=com</SearchBase1>
<BaseFilter>(&(objectClass=user)(!(cn=*admin*)))</BaseFilter>
<PhotoSource>thumbnailPhoto</PhotoSource>

        <BDILDAPServerType>AD</BDILDAPServerType>
        <BDIPrimaryServerName>A.B.C.D</BDIPrimaryServerName>
        <BDIServerPort1>389</BDIServerPort1>
        <BDISearchBase1>DC=ab,DC=Company,DC=com</BDISearchBase1>
        <BDIBaseFilter>(&(objectClass=user)(!(cn=*admin*)))</BDIBaseFilter>
  <BDIPhotoSource>thumbnailPhoto</BDIPhotoSource>
</Directory>
<Client>
<spell_check_enabled>true</spell_check_enabled>
</Client>
<options>
<Set_Status_Inactive_Timeout>3</Set_Status_Inactive_Timeout>
<ShowContactPictures>true</ShowContactPictures>
</options>
</config>

==============================================================================

Now the Mac client, some of them, show URI in the contacts, where as the Windows show AD name (Last, first).

I even placed the Jabber-config file in $Home/Library/Application Support/Cisco/Unified Communications/Jabber/CSF/Config, but it did not take effect. Users can only search by URI and not by name.

I have been looking up for the resolution but cant find much.

Second question, will the above script work for both Mac and windows client, or do we need a separate file. I asking because MAC files require "BDI" where as windows "EDI" (we do not want to use UDS). Also in the AD base filter, windows requires "&" where as Mac requires "&". how would this work in a single Jabber-config file?

Thanks!

Tapan Dutt · ‎11-30-2014

Hi asif

Problem related to the URI is not very clear, please can you share some snapshots of showing difference of what is seen on MAC Jabber and Windows Jabber.

BDI and EDI can co-exist in a single jabber-config.xml file.

Subtags starting with BDI will be parsed ONLY by Jabber Mobile and MAC clients and EDI will ONLY be parsed by Jabber windows. Take a look at the sample xml file below where in the EDI and BDI co-exist.

Also once you format the xml file you can always check the XML format for any erros on any of the publicly available XML validator links

<?xml version="1.0" encoding="utf-8"?>
<config version ="1.0">
<Directory>
<!—For Jabber windows—>
<UseWindowsCredentials>0</UseWindowsCredentials>
<PhotoURISubstitutionEnabled>True</PhotoURISubstitutionEnabled>
<PhotoURISubstitutionToken>sAMAccountName</PhotoURISubstitutionToken>
<PhotoURIWithToken>http://www.cisco.com/dir/photo/zoom/%%uid%%.jpg</PhotoURIWithToken>
<OtherPhone>telephoneNumber</OtherPhone>
<EmailAddress>mail</EmailAddress>
<LDAPServerType>AD</LDAPServerType>
<PrimaryServerName></PrimaryServerName>
<PresenceDomain></PresenceDomain>
<ServerPort1>389</ServerPort1>
<SearchBase1></SearchBase1>
<ConnectionUserDN></ConnectionUserDN>
<ConnectionUsername></ConnectionUsername>
<ConnectionPassword></ConnectionPassword>

<!—for Jabber iOS and Android—>
<BDILDAPServerType>AD</BDILDAPServerType>
<BDIPhotoURISubstitutionEnabled>True</BDIPhotoURISubstitutionEnabled>
<BDIPhotoURISubstitutionToken>sAMAccountName</BDIPhotoURISubstitutionToken>
<BDIPhotoURIWithToken>http://www.cisco.com/dir/photo/zoom/sAMAccountName.jpg</BDIPhotoURIWithToken>
<BDIPrimaryServerName></BDIPrimaryServerName>
<BDIPresenceDomain></BDIPresenceDomain>
<BDIServerPort1>389</BDIServerPort1>
<BDISearchBase1></BDISearchBase1>
<BDIConnectionUserDN></BDIConnectionUserDN>
<BDIConnectionUsername></BDIConnectionUsername>
<BDIConnectionPassword></BDIConnectionPassword>

<BDIUseANR>false</BDIUseANR>
<DirectoryUri>mail</DirectoryUri>
<EnableSIPURIDialling>true</EnableSIPURIDialling>

<—for UDS photo over edge—>
<UdsPhotoUriWithToken>http://www.cisco.com/dir/photo/zoom/%%uid%%.jpg</UdsPhotoUriWithToken>
</Directory>
</config>

Asif Khan · ‎12-01-2014

Hi Tapan,

I am attaching screen shots for both Mac and Windows.

See in Mac we can only search by SIP URI where as in Windows we can search using any attribute.

Also Mac search only returns SIP URI and no other information, where as the Windows search returns full user profile.

Thanks

Tapan Dutt · ‎12-01-2014

Thanks

The images attached makes the problem clear.

Your Jabber MAC client is not connected to your AD. Please check the AD connection from HELP menu of Jabber. Use the above shared sample XML file to configure BDI parameters for AD in XML file so that Jabber MAC client can find AD and connect,

Tapan

Asif Khan · ‎12-01-2014

Thanks for the reply Tappan.

I tried modifying the sample config (which I had tried earlier as well) but no good.

It seems like the client does not read the Jabber-config.xml file.

I have it in the right location: $Home/Library/Application Support/Cisco/Unified Communications/Jabber/CSF/Config

But it takes no action. even the client settings (like idle timeout) don't seem to take effect.

Any Ideas?

Thanks

Asif Khan · ‎12-03-2014

So I got it working.

The problem was the file encoding was not being recognized.

I just opened it in another text editor, saved it again, copied it and it started working.

weird.

Thanks for your help!

Tapan Dutt · ‎12-03-2014

Good Job Asif!

Tapan

Jabber for MAC showing URI contacts only