Sho CCM-Manager showing no active call manager

Unanswered Question

What is going on is I am trying to setup two pots lines to reach outside of our network. I am using call manager and the phones within our network are able to call each other. However, when we try to reach an outside line we get a busy signal.

I am using a Cisco - 3825 GW router. We have setup MGCP as the protocol. It seems that for some reason the router isn't getting to the call manager. when I type in "sho ccm-manager" it says current active Call Manager: None.

Is there something I need to do in the router to make these two talk?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
mchandak Wed, 12/12/2007 - 07:05

can you paste the ccm-manager and mgcp config from the router.

allan.thomas Wed, 12/12/2007 - 07:12

If you have configured all the appropriate ccm-manager commands as defined below, then the issue will attributed to reachability between the Voice-Gateway and CallManager.

Verify that you are able to reach the Voice-Gateway from CallManager.

ccm-manager redundant-host <2nd_ccm_ip_add>

ccm-manager mgcp

ccm-manager music-on-hold

ccm-manager config server

ccm-manager config

If you have ACLs configured on the gateway, ensure that these are not filtering MGCP.

Can you kindly post your config and a 'show mgcp'



mchandak Wed, 12/12/2007 - 08:22

show ccm-manager shows the Primary listed and that the GW is trying to register to CM with the IP "".

Please ensure that on CM, under the Voice Gateway, you are adding the Router with the domain name as ""

allan.thomas Wed, 12/12/2007 - 08:59

Firstly when you configure ccm-manager config, this initiates a download of the configuration for the respective endpoint FXO, PRI ISDN ?

Therefore all the subsequent mgcp commands are automatically added to configuration without any manual intervention required.

Please post your configuration in order to substaniate whether the appropriate ports have been configured, and also to verify the mgcp domain name.

Essentially the hostname and domain allocated to gateway have to exactly match in CCM. If they do not then you will be reliant on DNS in order to resolve the name in CCM to the IP address of the gateway.

For example if the hostname of the gateway is VG1 and the ip domain-name is, then the name you configure in CCM for the endpoint should be




This Discussion