I'm seeking clarification on how MGCP gateways should be receiving their CUCM Groups. In CUCM admin, it allows you to configure CUCM groups. Also, on the MGCP gateway you can configure a call-agent and cucm redundant host. I automatically assumed that because you configure the CUCM groups via the CUCM GUI that it would push this information out to the MGCP gateway, and the gateway would use those CUCM's as it's primary, secondary, etc. Instead, I have a MGCP gateway that using the call-agent and redundant host as it's means of CUCM registration and fallback. Is this normal, or should the CUCM group information be apart of the XML file pushed out by the CUCM? Thanks
Partial MGCP gateway config:
ccm-manager fallback-mgcp
ccm-manager redundant-host x.x.16.46 x.x.252.3
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server x.x.252.3 x.x.252.4
ccm-manager config
!
mgcp
mgcp call-agent x.x.252.4 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
mgcp package-capability sst-package
mgcp package-capability pre-package
no mgcp package-capability res-package
no mgcp package-capability fxr-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp fax t38 inhibit
mgcp rtp payload-type g726r16 static
mgcp bind control source-interface Loopback0
mgcp bind media source-interface Loopback0
!
Show CCM from the same gateway:
router#sh ccm
MGCP Domain Name: router.company.com
Priority Status Host
============================================================
Primary Registered x.x.252.4
First Backup Backup Ready x.x.16.46
Second Backup Backup Ready x.x.252.3
Current active Call Manager: x.x.252.4
Backhaul/Redundant link port: 2428
Failover Interval: 30 seconds
Keepalive Interval: 15 seconds
Last keepalive sent: 14:00:10 UTC Sep 8 2011 (elapsed time: 00:00:04)
Last MGCP traffic time: 14:00:10 UTC Sep 8 2011 (elapsed time: 00:00:04)
Last failover time: 12:00:08 UTC Aug 24 2011 from (x.x.252.4)
Last switchback time: 12:15:20 UTC Aug 24 2011 from (x.x.16.46)
Switchback mode: Graceful
MGCP Fallback mode: Enabled/OFF
Last MGCP Fallback start time: 05:49:07 UTC Jun 9 2011
Last MGCP Fallback end time: 05:50:57 UTC Jun 9 2011
MGCP Download Tones: Disabled
TFTP retry count to shut Ports: 2
Backhaul Link info:
Link Protocol: TCP
Remote Port Number: 2428
Remote IP Address: x.x.252.4
Current Link State: OPEN
Statistics:
Packets recvd: 22356
Recv failures: 0
Packets xmitted: 23938
Xmit failures: 0
PRI Ports being backhauled:
Slot 0, VIC 0, port 0
Slot 0, VIC 0, port 1
Configuration Auto-Download Information
=======================================
Current version-id: 1297694791-f6fa1b95-a46f-43ef-acb6-1edf87d7d9dc
Last config-downloaded:00:00:00
Current state: Waiting for commands
Configuration Download statistics:
Download Attempted : 320
Download Successful : 320
Download Failed : 0
TFTP Download Failed : 166
Configuration Attempted : 203
Configuration Successful : 203
Configuration Failed(Parsing): 7
Configuration Failed(config) : 0
Last config download command: New Registration
FAX mode: cisco
Configuration Error History:
Router#
The CUCM Group configured on the gatway via the GUI:
Piscataway CUCM Group = CMG-Sub2-Sub1-Pub
CUCM Pri = CM_uspsw2-cucm-5 (x.x.16.46)
CUCM Sec = CM_usden3-cucm-4 (x.x.252.4)
CUCM Ter = CM_usden3-cucm-3 (x.x.252.3)
