Client always using UDS for directory

[Gordon Ross]

I'm trying to configure Jabber for the clients to use an OpenLDAP server for directory. But no matter what I put in the UC Service, or the jabber-config.xml (Yes, I am remembering to restart the TFTP service after updating the file) the client (Both Mac & Windows) still use UDS rather than LDAP.

Any suggestions as to how to troubleshoot shot this? (The client Startup logs are around 4MB, so you really need something to look for)

GTG

[Jaime Valencia]

I'd start by looking at their local config.xml to see exactly what they're working with.

[Gordon Ross]

Which file? The local copy of jabber-config.xml? (It's the same as the one on the server, so the client is running the correct version)

GTG

[Jaime Valencia]

Exactly how are you testing you're using UDS and not LDAP??

Have you tried deleting the user´s cache?

[Gordon Ross]

Exactly how are you testing you're using UDS and not LDAP??

Searching for entries that are in LDAP but not in UDS, and also WireSharking the client machine.

Have you tried deleting the user´s cache?

You mean (In Windows) AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Config ? Yes.

GTG

[Stefania Oliviero]

I've this problem too.

I set OpenLDAP as DirectoryServerType and BDIUseANR=false, that is for Active Directory only, But with Wireshark I stil see that queries are made with ANR (Ambiguous Name Resolution)

Filter: (&(objectClass=contactPerson)(ANR=dal*))

I also reset tha cache

Any Ideas ?

[Amit Kumar]

here is what i would check;

in the call manager administration page; go to user management \  user settings\ service profile  \ and make sure that the following option under " directory integration" on the service profile is not checked;

"Use UDS for Contact Resolution".

- please rate if this helps.

[Gordon Ross]

This is what I've got: