I understand that the Call Manager may be configured to find a Gatekeeper through "Automatic Discovery", rather than having to explicitly configure a known Gatekeeper's IP address. Since being able to use Automatic Discovery may prove very useful in terms of providing Gatekeeper resilience, we would like to use it, but have not been able to find out how this may be configured within the Call Manager.
That said, we have tried altering the Parameter with no success:
GatekeeperControlRegistrationType : Denotes H.323 Gatekeeper Control > Registration Type
I am not aware of a configuration command for Gatekeeper discovery through CM Version 3.1. Gatekeepers are either identified specifically for a Gateway or through anonomous device configuration (one per CM at this time).
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...