Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
The MGCP gateway does not register with Cisco CallManager or another call agent
There are a number of reasons that a Media Gateway Control Protocol (MGCP) gateway does not register with Cisco CallManager or another call agent:
Configuration problems, such as a mismatch of endpoint names
Incompatibilities between MGCP versions
Cisco 2600 and 3600 routers support MGCP if they run Cisco IOS Software Release 12.1(3)T or later. The release and version that is required is based on the features that are needed. The Cisco CallManager server must run version 3.0(5)a or later. The router configuration is the same for all types of routers. The Cisco CallManager configuration is also the same for all types of routers.
The VG200 is supported by Cisco IOS Software Release 12.1(5)XM1 and later. Although the VG200 is supported in earlier releases of Cisco CallManager, version 3.0(5)a or later is recommended.
In order to resolve this issue, complete these steps:
In order for the gateway to register with Cisco CallManager, use the minimum configuration required:
mgcp mgcp call-agent CallManager IP Address ccm-manager mgcp
If the gateway is configured as shown and it still does not register, make sure there is IP connectivity to Cisco CallManager. The easiest way to do this is to issue the ping command from the gateway with the IP address of Cisco CallManager.
Note: If the host name of the gateway is changed, the MGCP domain name changes as well, which makes the gateway unable to register with Cisco CallManager. Make sure that if the host name of the gateway is changed, the MGCP domain name that is configured in Cisco CallManager is also updated.
Refer to Chapter 6: Voice Gateways of the Troubleshooting Cisco IP Telephony Cisco Press book [ISBN: 1-58705-075-7] for more information on the configuration and resolution of MGCP with Cisco CallManager.