05-26-2015 07:34 AM - edited 03-17-2019 05:12 PM
Hi all!
We have deploy a solution with jabber on-premise and we are facing with the following scenario:
In some laptops when we log in the service we see that we are going towards the LDAP server in order to retrieve de contacts, in other laptop the same user (same profile/same UC services) gets its contact from the UDS.
How can these be avoided?
Any help would be appreciated.
Thanks.
Solved! Go to Solution.
05-26-2015 09:13 AM
Hello,
You configuration is setted up to use UDS (have checked "Use UDS for contact resolution" in the service profile), and the jabber-config.xml file also setup UDS type.
In this case computers that use LDAP is because have not loaded the jabber-config.xml successfully or have not access to the UdsServer 10.250.80.1, EDI LDAP is default contact source used by Cisco Jabber for Windows.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_6/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide_chapter_01111.html#CJAB_TK_C6F8F451_00
You can verify the downloaded xml file to the below folder:
"%USERPROFILE%\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Config" (- Win 7)
"%SYSTEMROOT%\Documents and Settings\user_name\Application Data\Cisco\Unified Communications\Jabber\CSF\Config" (- XP)
You also can check the connectivity from the Jabber client to the TFTP Server and to the UDS server
HTH
05-26-2015 08:12 AM
Hello rperez1976,
Are all laptops in windows domain?
Have you configured a group xml file in any CSF device?
Please, can you share a UC Service and Service profile screen shoot
Best regards!
05-26-2015 08:42 AM
Hi Miquel Bover:
Some laptops are in windows domain other not.
No I dont configure a group xml file in any CSF device.(Also we get these problem with jabber deskphone mode).
Attach screenshots
Also attach the jabber config-file
<config version="1.0"><Policies>
<TelemetryCustomerID>net.masaveu</TelemetryCustomerID></Policies><Directory><DirectoryServerType>UDS</DirectoryServerType><PresenceDomain>masaveu.net</PresenceDomain><BDIPresenceDomain>masaveu.net</BDIPresenceDomain><UdsServer>10.250.80.1</UdsServer></Directory></config>
05-26-2015 09:13 AM
Hello,
You configuration is setted up to use UDS (have checked "Use UDS for contact resolution" in the service profile), and the jabber-config.xml file also setup UDS type.
In this case computers that use LDAP is because have not loaded the jabber-config.xml successfully or have not access to the UdsServer 10.250.80.1, EDI LDAP is default contact source used by Cisco Jabber for Windows.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_6/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide_chapter_01111.html#CJAB_TK_C6F8F451_00
You can verify the downloaded xml file to the below folder:
"%USERPROFILE%\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Config" (- Win 7)
"%SYSTEMROOT%\Documents and Settings\user_name\Application Data\Cisco\Unified Communications\Jabber\CSF\Config" (- XP)
You also can check the connectivity from the Jabber client to the TFTP Server and to the UDS server
HTH
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide