Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CallMgr 5.1 cannot register its MGCP gateway.

I have configured the MGCP gateway and the Call manager to support that gateway.

I had debugged the registration output on that gateway, there was a traffic between them..but the status for that gateway and its FXO cards in the call manager is "registration : rejected".

any help please.

thanks all.

25 REPLIES
Gold

Re: CallMgr 5.1 cannot register its MGCP gateway.

You need to ensure that the Domain Name configured on CallManager is in the format "hostname.domainname" as setup on the Router. For example the hostname on the router is mgcp1 and the domainname is cisco.com, then the domain name on CM should be mgcp1.cisco.com

Hope this helps.

New Member

Re: CallMgr 5.1 cannot register its MGCP gateway.

Thank you Mchandak for your cooperation,

I had applied the correct domain name on Call manager.

the same problem resists, my debugging output on the gateway shows that the endpoints are unknow (FXO ports) as you can see below :

*Nov 30 18:10:23.291: MGCP Packet sent to 10.10.1.101:2427---> 500 36 Endpt Unknown

*Nov 30 18:11:23.375: MGCP Packet sent to 10.10.1.100:2427--->

NTFY 330649111 *@MGCP-VGW.its2.com MGCP 0.1

X: 0

O:

<---

As you can see the aristek '*' in the output, no end point name appears.

Silver

Re: CallMgr 5.1 cannot register its MGCP gateway.

Try either rebooting your voice gateway or entering "no mgcp", wait a couple of seconds and then enter "mgcp" again.

Have you configured the correct VWIC and FXS cards etc on the CallManager voice gateway pages? This can often cause registration issues.

New Member

Re: CallMgr 5.1 cannot register its MGCP gateway.

yes, I have confiured all the FXO cards on my call manager as a loop start type.

same problem persists.

Silver

Re: CallMgr 5.1 cannot register its MGCP gateway.

Sorry, what I ment was do you have the correct part-codes configured in the callmanager voice gateway config pages i.e slot 0 VWIC2-1MFT-E1/T1 - is that the correct card sitting in slot 0 on your voice router?

Also, have you tried rebooting the router or disabling and re-enabling MGCP?

New Member

Re: CallMgr 5.1 cannot register its MGCP gateway.

Actually I have configured the right product No. in router's slot 0 (NM-4VWIC)where WIC slot 0 has VIC2-4FXO.

also I tried rebooting and rebooting the MGCP process but with same behaviour.

Gold

Re: CallMgr 5.1 cannot register its MGCP gateway.

Can you attach the snapshot of the GW config along with the MGCP debugs from the GW.

New Member

Re: CallMgr 5.1 cannot register its MGCP gateway.

I have configured the following on the gateway:

ccm-manager redundant-host 10.10.1.101

ccm-manager mgcp

!

mgcp

mgcp call-agent 10.10.1.100 service-type mgcp version 0.1

mgcp dtmf-relay voip codec all mode out-of-band

mgcp sdp simple

for Debugging :

########################3

*Nov 30 18:11:23.375: MGCP Packet sent to 10.10.1.100:2427--->

NTFY 330649111 *@MGCP-VGW.its2.com MGCP 0.1

X: 0

O:

<---

*Dec 1 01:41:48.414: MGCP Packet sent to 10.10.1.100:2427--->

RSIP 587630804 *@MGCP-VGW.its2.com MGCP 0.1

RM: graceful

<---

*Dec 1 01:41:48.414: MGCP Packet sent to 10.10.1.101:2427--->

RSIP 587630806 *@MGCP-VGW.its2.com MGCP 0.1

RM: restart

<---

*Dec 1 01:41:48.418: MGCP Packet received from 10.10.1.100:2427--->

200 587630804

<---

*Dec 1 01:41:48.426: MGCP Packet received from 10.10.1.101:2427--->

500 587630806

---- the above part is repeated continously---

after I have restarted the FXO port the follwoing messages appear.

RSIP 587630828 *@MGCP-VGW.its2.com MGCP 0.1

RM: graceful

<---

*Dec 1 01:44:48.414: MGCP Packet sent to 10.10.1.101:2427--->

RSIP 587630830 *@MGCP-VGW.its2.com MGCP 0.1

RM: restart

<---

*Dec 1 01:44:48.414: MGCP Packet received from 10.10.1.100:2427--->

200 587630828

<---

*Dec 1 01:44:48.422: MGCP Packet received from 10.10.1.101:2427--->

200 587630830

<---

*Dec 1 01:44:48.426: MGCP Packet received from 10.10.1.101:2427--->

RQNT 48 AALN/S0/SU0/0@MGCP-VGW.its2.com MGCP 0.1

X: 0

R: L/hd

Q: process,loop

<---

*Dec 1 01:44:48.426: MGCP Packet sent to 10.10.1.101:2427--->

500 48 Endpt Unknown

<---

*Dec 1 01:44:48.426: MGCP Packet sent to 10.10.1.101:2427--->

NTFY 587630832 *@MGCP-VGW.its2.com MGCP 0.1

X: 0

O:

<---

*Dec 1 01:44:48.430: MGCP Packet received from 10.10.1.101:2427--->

200 587630832

<---

*Dec 1 01:45:03.426: MGCP Packet sent to 10.10.1.101:2427--->

NTFY 587630833 *@MGCP-VGW.its2.com MGCP 0.1

X: 0

O:

<---

*Dec 1 01:45:03.426: MGCP Packet received from 10.10.1.101:2427--->

200 587630833

<---

*Dec 1 01:45:18.426: MGCP Packet sent to 10.10.1.101:2427--->

NTFY 587630834 *@MGCP-VGW.its2.com MGCP 0.1

X: 0

O:

<---

*Dec 1 01:45:18.426: MGCP Packet received from 10.10.1.101:2427--->

200 587630834

<---

*Dec 1 01:45:33.418: MGCP Packet sent to 10.10.1.101:2427--->

RSIP 587630835 *@MGCP-VGW.its2.com MGCP 0.1

RM: graceful

<---

*Dec 1 01:45:33.422: MGCP Packet received from 10.10.1.101:2427--->

200 587630835

<---

######################

you can see after I have restarted the FXO card from the CallMgr, its name appears on the output then a promt says 'endpt unknown '

thank you for your kind cooperation.

Gold

Re: CallMgr 5.1 cannot register its MGCP gateway.

Do we have the output of show diag and snapshot of the CM configuration. As for some reason both dont seem to match.

Bronze

Re: CallMgr 5.1 cannot register its MGCP gateway.

Do you have "application mgcpapp" under the voice ports? As an exampel:

dial-peer voice 100 pots

application mgcpapp

port 2/0/0

!

dial-peer voice 999200 pots

application mgcpapp

port 2/0/0

!

dial-peer voice 999201 pots

application mgcpapp

port 2/0/1

New Member

Re: CallMgr 5.1 cannot register its MGCP gateway.

Hi,

In some instances I have seen "service mgcpapp" under the dial-peer.

What is the difference between "application mgcpapp" and "service mgcpapp" under the dial-peer voice 10 pots?

Are both serving the same purpose?

Thanks,

Pete

Bronze

Re: CallMgr 5.1 cannot register its MGCP gateway.

If I am not mistaken the "service mgcpapp" enables the mgcp service over the pots lines while "application mgcpapp" is used when the CCM is in fallback mode and means if the gateway loses the link to CCM then that dial-peer should be taken over the default.

New Member

Re: CallMgr 5.1 cannot register its MGCP gateway.

Actually No, what has been configured is as prevoius conservation shows:

ccm-manager redundant-host 10.10.1.101

ccm-manager mgcp

mgcp

mgcp call-agent 10.10.1.100

mgcp dtmf-relay voip codec all mode out-of-band

mgcp sdp simple

mgcp profile default

Gold

Re: CallMgr 5.1 cannot register its MGCP gateway.

If the voice ports are not configured on the router, you should. Also, the configuration should be,

ccm-manager config server

And you want to do a configuration download from CM, then you can add the following line as well

ccm-managaer config

New Member

Re: CallMgr 5.1 cannot register its MGCP gateway.

Output for shjow diag (ouput related to EEPROM contents (hex) is not completed )

WIC Slot 0:

2nd generation - FXO Voice daughter card (4 port)

Hardware Revision : 5.0

Top Assy. Part Number : 800-21589-02

Board Revision : A0

Deviation Number : 8-7894

Fab Version : 04

PCB Serial Number : FOC11020SQZ

RMA Test History : 00

RMA Number : 0-0-0-0

RMA History : 00

Product (FRU) Number : VIC2-4FXO

Version Identifier : V01

CLEI Code : CNUIAPRAAA

EEPROM format version 4

EEPROM contents (hex):

0x00: 04 FF 40 00 4C 41 05 00 C0 46 03 20

WIC Slot 3:

2nd generation - FXO Voice daughter card (4 port)

Hardware Revision : 5.0

Top Assy. Part Number : 800-21589-02

Board Revision : A0

Deviation Number : 8-7894

Fab Version : 04

PCB Serial Number : FOC11020SPS

RMA Test History : 00

RMA Number : 0-0-0-0

RMA History : 00

Product (FRU) Number : VIC2-4FXO

Version Identifier : V01

CLEI Code : CNUIAPRAAA

EEPROM format version 4

EEPROM contents (hex):

0x00: 04 FF 40 00 4C 41 05 00 C0 46 03 20

As attached, I have only tested in port 0/0/0

Re: CallMgr 5.1 cannot register its MGCP gateway.

I have come across similiar issues with MGCP and FXO modules not registering quite frequently, and therefore recommend H323 in such circumstances.

However that is subject to opinion. In the past I have had to increase the echo-cancellation-coverage on the MGCP endpoint to 24ms, after which the port registers.

Try increasing the echo-cancellation-coverage in CallManager on the endpoint to 24ms and see whether this helps.

Regards

Allan.

VIP Super Bronze

Re: CallMgr 5.1 cannot register its MGCP gateway.

can you ping the FQDN of the gateway from the callmanager either from

1. CLI---utils network ping (gateway name)

2. Using the CCMAdmin Page, go to navigation---callmanager OS..and ping from there..

Do you have a DNS withing your network to resolve the gateway hostname?

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Re: CallMgr 5.1 cannot register its MGCP gateway.

I have configured the DNS servers during the initial installation.

I tried to ping the router's hostname form the CLI, the result was Unknown host, no record for that hostname in DNS servers.

anyway, if I add a record for that hostname then I will need to unite the dns name and servers on both call managers and voice gateway.

VIP Super Bronze

Re: CallMgr 5.1 cannot register its MGCP gateway.

This is where your problem is. In previous version of callmanager you can easily edit the etc/host file on the callmanager and add the gateway hostname to it.

However in CCM 5.1 you need to have a DNS server that can resolve names for CCM. So add the gateway name in the DNS server and try and ping it from the CCM again.

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Re: CallMgr 5.1 cannot register its MGCP gateway.

Configure the endpoint with an IP address instead of the hostname, this remove the dependency on DNS and give a indication as whether this is the root of your problem

When you configure your MGCP endpoint with a Hostname make sure that it matches the gateway. For example the gateway hostname is VGRTR01 and the configured ip domain-name is domain.com. Then the hostname on the endpoint should be VGRTR01.domain.com.

I have configure MGCP gateways with hostnames on 5.x and they register successfully prior to adding them into DNS. Changing to an IP address as mentioned will prove whether this is your problem.

As I have said in a previous post configure the echo-cancellation-coverage to 24ms for the FXO endpoints and see if they register then. I had exactly the same problem with them not registering and remain rejected until I changed them to 24ms from 8ms.

Regards

Allan.

VIP Super Bronze

Re: CallMgr 5.1 cannot register its MGCP gateway.

Allan, thanks for throwing more light on this. However I want to ask...In CCM 4.x, its either you have a DNS or you edit the etc/host file else CCM will not be able to resolve the gateway hostname.

If DNS is not used in CCM 5.x, How does Callmanager know what IP address to resolve to?

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Re: CallMgr 5.1 cannot register its MGCP gateway.

The following information regarding configure MGCP IOS gateways was taken from the following 5.1 Admin Guid:-

http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00808badbd.html#wp1311705

MGCP Gateway Configuration Settings

When configuring the MGCP hostname it appears only pertinanent to configure DNS if the hostname used for the MGCP hostname differs to the gateway.

Enter a name of up to 50 characters that identifies the Cisco MGCP gateway.

Use the Domain Name Service (DNS) host name if it is configured to resolve correctly; otherwise, use the host name as defined on the Cisco MGCP gateway.

If you are using the host name as it is configured on the IOS gateway, the name that you enter here must match exactly.

For example, if the hostname is configured on the gateway to resolve to vg200-1 and the IP domain name is not configured, enter the hostname in this field (in this case, vg200-1).

If the hostname is configured on the gateway as vg200-1 and the IP domain name is configured on the gateway as cisco.com, enter vg200-1.cisco.com in this field.

Hope this helps.

Allan.

VIP Super Bronze

Re: CallMgr 5.1 cannot register its MGCP gateway.

Great! Thanks Alan, I appreciate this. In essence CCM 5.1 does not rely on DNS services for MGCP Gateways!

Thanks

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Re: CallMgr 5.1 cannot register its MGCP gateway.

No problem, it certainly appears that way.

I had the same confusion when I first installed 5.0x, you would expect to edit the host file.

Regards

Allan.

New Member

Re: CallMgr 5.1 cannot register its MGCP gateway.

Thanks Allan,

I appreciate your support and cooperation, I will test that and I will reply back to you.

Mo

331
Views
0
Helpful
25
Replies
CreatePlease login to create content