You add the gatekeepr as a device in call manager, if you want to allow calls to come in from this gatekeeper then you check allow anonymous calls. You can set a tech prefix to register with in this screen as well. CCM will register to the gatekeeper as a gateway and you set the gatekeeper to route calls via tech or zone prefix accordingly. Then when a call comes into gateway:
I believe the CCM, when configured properly, will process the call admission control on behalf of the GW. in other words, the GW sends a SETUP to the CCM, the CCM realizes this GW is configured uder the authority of a GK, so the CCM sends an ARQ to the GK and expects an ACF with other control parameters such as the bandwidth to use and the destination signaling IP. This, of course, follows a successful registration of the GW to the GK by the CCM. it's a bit convoluted, and i think cisco usually recommends you bypass the CCM in these cases, i.e., configure the GW to statically peer with other H323-capable endpoints. i think the prime role of the CCM is to smooth out the integration of skinny clients into the VoIP network, without the need of chaging the pre-established protocols such as H323.
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...