Directory Lookup CUCI Lync - IP of LDAP server

Stefan Weixler · ‎02-15-2016

hey guys,

we are using Cisco UC Integration for Lync with deskphone mode. But I do not understand where the CUCI Client gets the IP address of LDAP server from?

The settings for the Service Profile in CUCM are as follows:

- Primary: <none>

- "Use UDS for Contact Resolution" is checked

- Username and password is the admin of CUCM

- "Recursive Search on All Search Bases" is checked

- Search Timeout: 5

In the jabber-config.xml is no entry of a LDAP Server.

Does the option "Use UDS for Contact Resolution" mean that the following DNS Records are queried?

_cisco-uds._tcp.example.com
_cuplogin._tcp.example.com
_collab-edge._tls.example.com

Maybe someone can explain me where the CUCI Client gets the information for the LDAP Server from.

kind regards

Stefan

Md Hasan · ‎02-15-2016

If the PC is joined to the domain, that will be its LDAP server to communicate with.

The UDS for contact resolution tries to make the search to Call manager instead of LDAP Server that the PC communicates. I would probably keep it unchecked as AD is much more flexible in directory information than CUCM.

Also jabber-config.xml will be needed with "PresenceDomain" if the user resolution is not working (the name shows up as user@domain instead of firstname last name). You may also see "user@".

The _cisco-uds is only to discover where the CUCM Server and is not related to UDS contact search. CUCI needs to be logged in with cucm userid/cred

HTH

Stefan Weixler · ‎02-17-2016

Hi,

thanks for your reply.

Do i understand it right once the CUCI is connected to a domain the client searches for LDAP Servers without any specific LDAP configuration in CUCM UC Services or jabber-config.xml?

Most of our users ids in CUCI are presented as follow: user-id@
Although the Directory lookups for a name works fine.

With the initial configuration of CUCI we enter the following: user-id@domain.com. Afterwards we log in only with the user-id. The domain is stored in the jabberlocalconfig.xml.

kind regards

Steafn