Unfortunately, we found ourselves unable to follow the procedure with our production service, since it was not supported by Cisco. In a previous Cool Solutions AppNote I described how I was able to demonstrate that it was, in fact, possible to integrate Cisco Call Manager 4 with eDirectory, with only a few modifications to the documented procedure for Netscape, et al (SunOne/iPlanet). Unfortunately, we found that Cisco does not support eDirectory as one of the allowed LDAP targets, which include only Microsoft AD, SunOne, Netscape, and iPlanet.

Our goal was one-place management of telephone numbers, preferably in eDirectory, and authentication to a user's telephone management web page using the standard LDAP login name and password. When we deployed Cisco Call manager version 4 as our IP Telephony solution, directory integration was high on our agenda. This AppNote describes a mechanism for integrating Cisco Unified Call Managers 5 and 6 directly with Novell eDirectory and explores some of the pitfalls to avoid in doing so. However, one similarity with Call Manager 4 is that directory integration is only offered against Microsoft Active Directory or SunOne/iPlanet - Novell eDirectory is specifically excluded. Integration with a corporate directory through a one way non-invasive LDAP download is possible, as is authentication against that directory to enable a user to access his telephone management web pages. They differ substantially from Call Manager 4 in that they no longer have their own internal X500 directory, with user information being stored within the same database as the devices.

Cisco Unified Call Manager versions 5 and 6 are the latest IP telephony products from Cisco.

Cisco call manager 6 iso