02-28-2013 10:45 AM - edited 03-19-2019 06:21 AM
Our CUCM 8.6 is currently integrated with LDAP, this was done before I started with the company, I'm working on getting the CUC integrated as well, but I keep getting the following error message:
Error while Connecting to ldap://xx.xx.xx.xx:389, null
I took the exact same settings that was used on the cucm (the LDAP syncs fine with CUCM)
LDAP Configuration name: ActiveDirectory
LDAP Manager Distinguished Name: ldapquery@xyz.net
LDAP Password: *******
LDAP User Search Base: DC=xyz,DC=net
User ID: sAMAccountName
Middle Name: middleName
Manage ID: manager
phone number: ipPhone
First name: givenName
Last Name: sn
Department: department
Mail ID: mail
User ID: sAMAccountName
Middle Name: middleName
Manage ID: manager
phone number: ipPhone
First name: givenName
Last Name: sn
Department: department
Mail ID: mail
Any ideas what could be causing that error? I've ran into this before somewhere but was able to figure out that it was something with the way I had put in the OU..This time I'm really I have not idea, especially since I took the settings from the LDAP setup in CUCM.
02-28-2013 11:05 AM
From CUC you have connectivity with the LDAP Server?
Take a look on this discussion it might help you
Regards
Leonardo Santana
What are you using for a Search Base string?
What are you using for a Search Base string?
What are you using for a Search Base string?
02-28-2013 11:55 AM
Is DirSync service running on CUC?
Are you sure the CUCM synch is still working? Simply test would be to login to CUCM, go to LDAP directory and press Save button there, if it comes back with sucessful update it works, if it came back with the same error it does not.
Can you post screen shots of from both systems for comparison?
Chris
02-28-2013 12:49 PM
Hi Chris,
Yes I'm sure the sync is still working, I've went into CUCM and did a full sync and it was successful, I also hit save and that was successful as well, that was the first thing I did just to make sure it was working, I was thinking like you that maybe it wasn't working properly ...I'll take some screen shots and post shortly
Fred
Here's a screenshot of both CUCM and CUC
Message was edited by: Fred Rawlings
03-01-2013 07:29 AM
Well after going on some docs, I found that ldapquery password was missing a character....All is well now, I was able to configure and update successfully.
03-01-2013 07:47 AM
Thanks for letting us know Fred.
HTH, please rata all useful posts!
Chris
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