URL Authetntication problem with directory lookup

[dudecrush]

Hi All. My Call Manager layout is pretty simple: 1 pub and 1 sub running v6.1.3.3190, a Unity 5.1 voicemail system, and a v 2.0.3.1000 E911 server.

About 7 mo. ago, we created an LDAP directory lookup for the phones under the Enterprise Parameters settings. As of last week, it stopped working. When users press the directory button on their phone, they get an "Authentication Required" prompt on their phones asking for a username and password. We're not getting the password prompt with the URL directories link, so the culprit must be the the authentication URL link, which is the publisher:

http://10.128.xxx.xxx:8080/ccmcip/authenticate.jsp.

When I put that link in a browser, I got the standard HTTP 500 error: "The server encountered an internal error () that prevented it from fulfilling this request." I restarted a few of the softphones, but that didn't work. I then restarted the Tomcat service, but that didn't do anything either.

Can anyone point me in the right direction?

 

[whykap]

Where is that LDAP located? Locally on the server or is it pointing to another server that is running IIS?

 

[dudecrush]

The actual LDAP lookup is done on a different server.

 

[whykap]

Ok. so in enterprise parameters you point ccm to another LDAP directory on a separate server. It worked before but now it does not.
Things to look for:
Is there an xml file on that server that is for the ccm server? If so make sure something has not changed on it (even if you think it has not, you need to check it as this is avery probable cause).

The issue is since you are getting an http error the ccm server is not authenticating correctly. This is definately a change that occured on the LDAP server. An xml script change is the first thing I would look at, as it has been an issue for me in the past.

 

[dudecrush]

whykap - I think you're on the right track. I removed the directories URL field and reset a softphone. I no longer got prompted for authentication, so it's coming from the LDAP server. I actually checked the path in IIS on that LDAP server, and the directory.xml file is missing. I don't manage that server, so I have no idea where it went. I'm working with our web designer to figure that out.