[cisco-voip] Cisco Callmanager AD integration

[Ryan Ratliff]

The Cisco OU should be in the directory already so there is no need  
to re-create it.   You can either re-run the plugin to change the DC  
CM uses, edit the files and registry manually to change this, or edit  
the hosts file on your CM servers so that when it tries to connect to  
the dead DC it finds the IP address of the second one.  The last  
option will only work if you set it up originally to use the hostname  
rather than IP address.

The files to modify are:
c:\dcdsrvr\directoryconfiguration.ini
c:\dcdsrvr\config\umdirectoryconfiguration.ini

In the registry:
HKLM\Software\Cisco Systems, Inc.\Directory Configuration

In all 3 places change the LDAPUrl to point to the desired destination.

Be sure to make backups of any files you modify, especially the  
registry.

Any services that rely on ldap will need to be restarted.  At a  
minimum IIS (and WWW) to get your corporate directory working.  EM  
(Tomcat) also uses ldap as well as CTI and TCD.

-Ryan

On Apr 2, 2007, at 12:59 PM, Gary L. Pate wrote:

Today I had a DC server fail that is the AD server used when the CCM  
was setup and integrated with AD. We had a secondary DC server  
functioning, but the CCM server did not recognize it. I know when  
running the AD plugin, it asked for the AD server name and port  
number. When that AD server fails, is there anyway to have a  
redundant AD server or does the plugin have to be reinstalled and the  
Cisco OU recreated on the new DC server?



Gary



_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip