MGCP Gateway Unregistered CCM 6.1

Answered Question
Mar 13th, 2008
User Badges:

Hi

In our CCM 6.1 enviroment we have a problem with the MGCP gateway. When you look in the CCM you see that it is Unregistered.


Screendump CCM:

Product = Cisco MGCP E1 Port

Gateway = SGS-HR-GW1

Device Protocol = Digital Access PRI

Registration = Unregistered

IP Address = 10.7.0.20

End-Point Name = S0/SU0/[email protected]-HR-GW1


But when you look on the gateway it looks okay for me:

+++++++++++++++++++++++++++++++

SGS-HR-GW1#sh ccm

MGCP Domain Name: SGS-HR-GW1

Priority Status Host

============================================================

Primary Registered SGS-fn (10.7.0.10)

First Backup None

Second Backup None


SGS-HR-GW1#sh mgcp

MGCP Admin State ACTIVE, Oper State ACTIVE - Cause Code NONE

MGCP call-agent: SGS-fn 2427 Initial protocol service is MGCP 0.1


+++++++++++++++++++++++++++++

Is there a config faillure ?

The problem starts with changing the IP address of the gateway, so I bring it back to the old IP address but the problem is still there.


Regards , Rene

Correct Answer by Jaime Valencia about 9 years 2 weeks ago

the sh ccm on a GW does not necessarily means the GW is registered, it only means the signaling at port 2428 is working fine. that is the keepalive port


verify that the MGCP call agent statements is looking at the right server, that the domain name under CCM is the hostname + domain (if configured)


try a no mgcp / mgcp

try deleting and readding the GW under the CCM config


HTH


javalenc


if this helps, please rate

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
Jaime Valencia Thu, 03/13/2008 - 12:03
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    2011

the sh ccm on a GW does not necessarily means the GW is registered, it only means the signaling at port 2428 is working fine. that is the keepalive port


verify that the MGCP call agent statements is looking at the right server, that the domain name under CCM is the hostname + domain (if configured)


try a no mgcp / mgcp

try deleting and readding the GW under the CCM config


HTH


javalenc


if this helps, please rate

r.vanschendel Fri, 03/14/2008 - 05:36
User Badges:

***deleting and readding the GW under the CCM config***


that was the solution.


Thank you very much.

auppal Thu, 03/13/2008 - 19:34
User Badges:
  • Cisco Employee,

this looks like a domain name mismatch. Can you attach deb mgcp pack and bounce the mgcp and collect the logs

Actions

This Discussion