Contact Search with UDS on J4W

[Ilya Shilov]

Hello, Community.

I have BE6K with:

CUCM System version: 10.0.1.11900-2 Unrestricted

and Cisco Jabber for Windows version 9.6.2, build 18852.

Voice calls, video calls, presence works just fine. Problem is on contact search on workstations outside windows domain.

LDAP is integrated with CUCM. I have about 100 users imported.

jabber-config.xml file on test workstation was filled with:

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
 <Directory>
   <DirectoryServerType>UDS</DirectoryServerType>
   <UdsPhotoUriWithToken>http://1.1.1.1/%%uid%%.jpg</UdsPhotoUriWithToken>
 </Directory>
</config>

1.1.1.1 - is fake IP address... I think it doesn't matter for my task.

This file was uploaded to CUCM, TFTP service - restarted. File is accessible with URL http://<cucmpub>:6970/jabber-config.xml

I deleted on workstation before tests:

%USERPROFILE%\AppData\Roaming\Cisco\Unified Communications\Jabber

%USERPROFILE%\AppData\Local\Cisco\Unified Communications\Jabber

Autodiscovery process works as it should on first J4W Client start. I restarted Client. CUCM is connected, IM&P is connected, Voicemail is connected... Contact Search shows no results.

Please help, what should I check.

[Jaime Valencia]

Where's the primary server name parameter configured??

[Ilya Shilov]

Hi Jaime,

thank you for you answer.

I have _cisco-uds._tcp.mydomain.name configured and it is accessible from workstation.

Also I have tried this jabber-config.xml:

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
 <Directory>
   <DirectoryServerType>UDS</DirectoryServerType>
   <PresenceDomain>mydomain.name</PresenceDomain>
   <BDIPresenceDomain>mydomain.name</BDIPresenceDomain>
   <UdsServer>192.168.19.3</UdsServer>
   <UdsPhotoUriWithToken>http://1.1.1.1/%%uid%%.jpg</UdsPhotoUriWithToken>
 </Directory>
</config>

It didn't change results.

[Jaime Valencia]

Still missing the primary server name there, and 

UdsServer

Is not a valid parameter, not sure where did you get that.

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_6/InstallConfig/JABW_BK_CDFE9752_00_installation-and-configuration/JABW_BK_CDFE9752_00_installation-and-configuration_chapter_0111.html

[Ilya Shilov]

I used https://supportforums.cisco.com/document/106926/jabber-config-file-generator to generate my configs.

Should I use <PrimaryServerName> parameter for UDS?

[Amit Kumar · Accepted solution]

you are not using a supported version of Jabber for windows ; as you mentioned above that the version in use is 9.6.2; as per the following link ; http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_6_2/JABW_BK_J4032C6F_00_jabber-for-windows-release-notes/JABW_BK_J4032C6F_00_jabber-for-windows-release-notes_chapter_01.html

this is not supported for UDS with contact resolution with J4W.

"

UDS Directory Source

Cisco Unified Communications Manager User Data Services (UDS) is not supported for directory integration in this release."

Test this with the latest 9.7 version of Jabber for windows; check this link ; http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/JABW_BK_CF8F083D_00_cisco-jabber-for-windows-97/JABW_BK_CF8F083D_00_cisco-jabber-for-windows-97_chapter_00.html#JABW_RF_N0C3239B_00

UDS On-Premises Directory Integration

Cisco Jabber for Windows now supports Cisco Unified Communications Manager User Data Service. In addition to being able to deploy Cisco Jabber using LDAP to connect to Active Directory, Jabber can now alternatively be deployed with Cisco Unified Communications Manager User Data Services (UDS) contact lookup service. Server scaling must be considered when using the UDS server. A Cisco Unified Communication node can support UDS contact service connections for 50% of the maximum device registrations supported by the server. For information about configuring UDS for directory integration, see the Directory Integration chapter of the Installation and Configuration Guide.

- Please rate if this helps.

[Ilya Shilov]

Yes, it works with 9.7.2!

Thank you for your response, Amit.