Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Jabber 9.0.1 saerch contact issue

Dear Networkers,

We are using Cisco Jabber for windows 9.0.1 with Cisco Unified Presence 8.6 and CUCM 8.6

We are using CUPC 8.6 also.

We can successfully login using Jabber. but we cannot retrieve contacts when searchng.

We have AD integration with CUCM (synchrinisation) and with CUPS done successfully. The wierd the wierd thing is that when we login using CUPC we can search contacts and add them.

Can you please advise ?


  • Jabber Clients
New Member

Re: Jabber 9.0.1 saerch contact issue


We had the same symptom when the windows workstations were not in the same domain than the ldap referenced by cups. We had to manually generate a config file as described in jabber config guide

If you are fully integrated into the same AD domain it should not occur.

I also confirm that a CUPC client on the same PC was working fine without any manual config so provisioning process is different b/w CUPC and jabber 9.



Cisco Employee

Jabber 9.0.1 saerch contact issue


To add to what Chris mentioned, you can also reference the following KB article for EDI deployment:

If you are at CUCm 8.6(2), you can also deploy UDS: Configure Cisco Jabber for Windows to use the directory service



New Member

Re: Jabber 9.0.1 saerch contact issue

I had same problem, you need to put the config file (attached) on the path C:\Users\yourname\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Config and be sure that you can access the presence server by name (dns or hosts file). Before you login you must to configure the presence server by name, not by IP.



Cisco Employee

Jabber 9.0.1 saerch contact issue

What field are you using to sync the users from ad?

If it's different from the default sAMAccountname, then you will need to configure it in the jabber-config file.

For futher details, you can check out the docs here:

This widget could not be displayed.