I've tried to register 2 VoiceGateways with the same configuration on our CCM-cluster. On both GW's the "ISDN bind-l3 ccm-manager" was missing at first so it didn't work. I've added the command on the E1 interfaces on both Gateways, made a copy to startup config (wr mem) and did a reload. After the reload one Gateway did register itself on the CCM but the other didn't.
Looking at the config showed me that on de GW that did register the command "ISDN bind-l3 ccm-manager" was still on the E1 interfaces. On the Gateway that didn't register the command had disappeared again! I've tried this several times but the command disappears everytime after a reload. Can anyone explain this and tell me how to make it work?
The ISDN status as Ajaz mentioned is fundamental to the gateway registering.
Typically the L2 ISDN status is shown as either MULTIPLE_FRAME_ESTABLISHED or TEI_ASSIGNED.
MULTIPLE_FRAME_ESTABLISHED indicates there is data link connectivity to the Telco ISDN switch. This is the state that you should see under normal operations. Any other state usually indicates a problem on the circuit.
TEI_ASSIGNED indicates that the router has lost connectivity to the Telco switch switch.
Also I have notice from the last 'show ccm-manager' that there are 13 failed TFTP attempts and that the MGCP domain name is different from a previous post.
Please can you confirm the hostname of your gateway, and also whether you have additionally specified a ip domain-name ???.
For example if your gateway hostname is VG1 and ip domain-name is domain.com, then your MGCP domain name should be VG1.domain.com and this should be the name you have configured for your MGCP endpoint in CCM.
If you have configured an IP address, then ensure that CCM is able to resolve VG1.domain.com.