In presence mode, the client cannot connect to the LDAP Servers.
If I connect to the CUCM account directly from Jabber iPAD, I can successfully search corporate contact and show contact photo. This problem is only when using presence integration.
On the presence server, all LDAP Profiles are used by CUPC and are working successfully on the CUPC Client.
I have tried to change from FQDN to IP and hostname for LDAP Servers with no success. I’m currently using FQDN and tcp/389.
From the log:
-- 2012-07-16 22:30:17.669 DEBUG - MXUserDefaults - get LDAP password, 0, The operation couldnâ€™t be completed. (SFHFKeychainUtilsErrorDomain error -2000.)
-- 2012-07-16 22:30:40.261 INFO - CXAccountManager::saveLDAPAccount, Primary: 0, server: 126.96.36.199, Port: 22835268, Searchbase: 298049424, Username: atealab\rune.heggelund
-- 2012-07-16 22:30:40.262 INFO - CXAccountManager::saveLDAPAccount, Primary: 0, server: 188.8.131.52, Port: 22835268, Searchbase: 298049424, Username: atealab\rune.heggelund
-- 2012-07-16 22:30:40.262 INFO - MXUserDefaults::saveLDAPAccount, account: rune.heggelund10.137.81.12
old thread, but...
...could you solve this issue?
I have the same: when Jabber for iPad is logged on on CUPS, then LDAP is not working. If I logon on CUCM, it works without problems. Where does Jabber for Ipad get the information about the LDAP-server from, when it is logged on at the CUPS-server?
Is it also done via CUCM?
I found a solution by myself:
When logged on on CUPS and not on CUCM , then Jabber for iPad does not use the settings from the device-configuration-page, but it uses settings done in the UC Service profile.
Here I had to configure my ActiveDirectory as Enhanced Directory and not as Directory to get it working.