MGCP with CCM5 Registration Problem

Unanswered Question
Apr 2nd, 2009

Dear sir,

I have CCM ver.5 and 2811 gateway connected through VPN tunnel (Easy VPN).

I advertised LAN network on the remote gateway and its reachable through the Call-Manager, but we couldn't advertise the WAN (VPN tunnel IP) because its variable..

So we can't ping (normal Ping) to the call-manager from the gateway but we can ping using the extended ping with LAN IP address as the source.

The MGCP is down and can't reach the call manger, but if we can change the MGCP source interface I think this will solve the issue.

Can you help to solve this problem.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
islam.irshaid Thu, 04/02/2009 - 09:24


i added them but still facing problem.

please find attached, debug mgcp , show run , show ccm.

Thnaks in advance for your help

Nicholas Matthews Thu, 04/02/2009 - 10:22

You have a connectivity issue.

Either these packets aren't getting there, aren't allowed through the VPN, or the responses for them aren't getting back through the VPN.

Please make sure that UDP 2427 and TCP 2428 are allowed on your VPN.


islam.irshaid Sun, 05/03/2009 - 03:27


I double checked the connectivity, it seems good ,UDP and TCP are opened

can anyone help me ?

Thanks all

Adrian Saavedra Sun, 05/03/2009 - 09:27


Did you configure your router in the CM as

Best regards,

- Adrián.

Adrian Saavedra Mon, 05/04/2009 - 06:57


From the debug, I saw this:

*May 4 05:52:27.675: MGCP Packet received from>

510 240884367


510 is a MGCP Response Code. Means that transaction could not be executed because a protocol error was detected.

Could you share us your MGCP configuration in CM?

Best regards.

Adrian Saavedra Tue, 05/05/2009 - 05:39


If a domain name is configured on the MGCP gateway, the domain name for the gateway configuration on Cisco CallManager must be the same. In your gateway you have hostname Hulul-Amman and ip domain, but in CM you have only Hulul-Amman.

If the domain names for the MGCP gateway and the gateway configuration on Cisco CallManager do not match, perform one of these actions:

* Change the domain name on either the MGCP gateway or Cisco CallManager so that they both have the same domain name.

* If either hostname or domain name is changed on the MGCP gateway, issue these two global commands in sequence on the MGCP gateway in order to implement the new hostname or domain name:

no mgcp


Try to reset the gateway voice ports if you encounter issues with the Cisco IOS gateway registration or operation:

router(config)#voice-port 0/0/0


router(config-voiceport)#no shutdown

router(config)#voice-port 0/0/1


router(config-voiceport)#no shutdown

Check if your gateway endpoints show registered in CM.

Hope it helps.

Best regards.

islam.irshaid Tue, 05/05/2009 - 05:51

Thanks for you.

Please note that I made some edits and trial before on the Gateway regarding the domain name and it's the same , Hulul-Amman.

i made everything and the problem still come into view

Adrian Saavedra Tue, 05/05/2009 - 06:03


Then it's better to open a TAC case. TAC Engineer will request CM Traces for analysis.

Best regards.

Nicholas Matthews Tue, 05/05/2009 - 10:47

The debugs show that your gateway has

but the screenshot doesn't.

Regardless, the debugs also show that the MGCP gateway isn't getting any responses. Check your routing.


iptuser55 Wed, 05/06/2009 - 01:00

Have you checked this bug due to the 510 error message

CSCsi19351 Bug Details

CM calls to FXO MGCP GW fails with 510 protocol error if no dialed digit ?


This Discussion