Problem with Click to dial and LDAP Authentication

[williamsmj7]

Hi All,

I'm trying to get the Cisco Click to Call application to work. If I disable LDAP authentication and point the application to one of my subscribers I can successfully connect with a password for my account setup on CUCM. If I reable LDAP and put my LDAP password into the application then the application gives me an error about invalid password when I try to dial and won't save any changes to server settings.

When LDAP is enabled if I goto https://myserver/webdialer/webdialer and login with LDAP credentials I can dial a number successfully.

Any ideas on how to trouble shoot this?

Thanks,

Mike Williams

[Justin Brenton]

Hi Mike ,

Here is a troubleshooting guide for CUCM 7. 

http://www.cisco.com/en/US/docs/voice_ip_comm/cupa/click_to_call/7.0/english/install/guide/C2C6chapter.html

HTH,

Justin

[williamsmj7]

Hi Justin,

I tried looking through that page with no luck.I found the following in one of the log files :-

2011-07-27 08:07:14,434 [1] INFO  - MakeCall: user(MYUSERNAME) to(88055) with profile(

MYUSERNAME

;Extension Mobility Phone;;True)

2011-07-27 08:07:17,655 [1] ERROR - make call failure through WD - AUTH_ERROR

2011-07-27 08:07:17,664 [1] DEBUG - entering WriteRecord - 88055

I'm guessing that the AUTH_ERROR is causing my problem but as I explained in my first post I can login to the webdialer with my LDAP password just fine.

Any other ideas greatly appricated?

Thanks,

Mike

[Justin Brenton]

Your definately having a authentication issue.  Is this pc joined to the domain? 

I'm thinking that you can do it through the web page because the server is already authenticated.  Your PC might not be authenticated to the domain and maybe causing issue's.  I would double check this. That's the only thing that comes to mind.

HTH,

Justin

[williamsmj7]

We are using edirectory so no domain as such.

I have to login manually with my LDAP details to the website which works.

The application has a login username and isn't setup to use the registry setting to carry over windows username anyway.

Thanks for your efforts, I'm guessing its just one thing that is going to have to stay broken :-(.

Mike

[Justin Brenton · Accepted solution]

Hi Michael,

Look like your not using a supported LDAP Server

LDAP Directory Support 

LDAP Directory Type	Cisco Unified CM 6.x	Cisco Unified CM 7.x	Cisco Unified CM 8.x
Microsoft AD 2000 Microsoft AD 2003 Microsoft AD 2008 Microsoft ADAM 2003 Microsoft LDS 2008	Yes	Yes Cisco Unified CM 7.1(3) or later release is required for Microsoft ADAM and LDS.	Yes But Microsoft AD 2000 is not supported with Unified CM 8.x.
Netscape 4.x	Yes	No longer supported1	No longer supported1
iPlanet 5.0	Yes	No longer supported1	No longer supported1
iPlanet 5.1 SunOne 5.2	Yes	Yes	Yes
SunOne 6.x	Yes	Yes	Yes
OpenLDAP 2.3.39 OpenLDAP 2.4	No	Yes2	Yes

¹ The directory vendor indicates that this solution has reached End of Life.

² This directory type is supported only with Cisco Unified CM 7.1(2) and later releases.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/directry.html

HTH,

Justin

[williamsmj7]

Hi Justin,

I understand that we are using an unsupported directory but it does actually work.

Turns out the fault was rather simpler than I expected.

See - https://supportforums.cisco.com/message/3229127

Bug ID - CSCtg93965

Turns out that the settings were saved initially when I setup the click to dial application but then when I went back to change the password after LDAP authentication enabled it wasn't updating my password and I didn't realise as it was starred out.

Thanks for your help.

Mike