Maybe someone can confirm this:
When changing LDAP auth user search base DN in CUCM 10.5.2 this results in loss of CTI functionality in Cisco Jabber 10.6.x, when logging into Jabber after the change has been made.
Changing LDAP auth user search base DN back to its original value and restarting Cisco Jabber will make CTI work again.
More detailed information:
We are about to set up a new site office or more precise: a new subsidiary company. This subsidiary company will be located outside of the current search base in our AD.
Current user search base for LDAP authentication is:
The new location would be:
After this change has been made, the user is still able to login in Cisco Jabber as well as in CUCM Self Care site. I take this as confirmation that authentication is working with that new LDAP auth user search base.
The problem is: when the users will sign into their Cisco Jabber client at next opportunity, they will experience that CTI will not work anymore. The users are listed as "Active LDAP Synchronized User".
The corresponding error in Cisco Jabber is:
Deskphone - Unhealthy
Status: Not connected
Reason:Connection error. Ensure the server information in the Phone Services tab on the Options window is correct. Contact your system administrator for assistance.
When changing search base DN back to its original setting, CTI is working again when the user is logging in again.
This behaviour is reproducible and it doesn't matter whether you restart CTI Manager in Serviceability or not.
My undestanding, however, is: changing the user search base DN for LDAP auth to a higher entry should not affect CTI at all. The user DN should remain the same, which is confirmed by users being able to login in Cisco Jabber as well as in CUCM itself, for example the self care portal.
Is there a workaround possible? Or even a solution?