Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2665
Views
0
Helpful
5
Replies

VG224 registration issue with CUCM 6

layhlaing
Level 1
Level 1

‎05-17-2011 01:54 AM - edited ‎03-16-2019 05:00 AM

Hi,

Can someone advise me where the cause of the registration issue can possibly lies? We have Cisco VG224 which has the IP connectivity with CUCM 6 (also in the same Vlan). I get the following on show ccm-manager.

voip-010#sh ccm-manager
MGCP Domain Name: voip-010.corporateict.domain
Priority        Status                   Host
============================================================
Primary         Registering with CM      10.10.1.50
First Backup    Backup Ready             10.101.20.50
Second Backup   None

Current active Call Manager:    None
Backhaul/Redundant link port:   2428
Failover Interval:              30 seconds
Keepalive Interval:             15 seconds
Last keepalive sent:            05:41:04 UTC May 13 2011 (elapsed time: 4d02h)
Last MGCP traffic time:         08:35:48 UTC May 17 2011 (elapsed time: 00:00:20)
Last failover time:             08:35:18 UTC May 17 2011 from (10.10.1.50)
Last switchback time:           08:35:48 UTC May 17 2011 from (10.101.20.50)
Switchback mode:                Graceful
MGCP Fallback mode:             Not Selected
Last MGCP Fallback start time:  None
Last MGCP Fallback end time:    None
MGCP Download Tones:            Disabled
TFTP retry count to shut Ports: 2

Configuration Auto-Download Information
=======================================
No configurations downloaded
Current state: Waiting for commands
Configuration Download statistics:
        Download Attempted             : 1
          Download Successful          : 0
          Download Failed              : 1
          TFTP Download Failed         : 0
        Configuration Attempted        : 0
          Configuration Successful     : 0
          Configuration Failed(Parsing): 0
          Configuration Failed(config) : 0
Last config download command:
Configuration Error History:
TFTP File download failed

FAX mode: disable

TFTP service on CUCM is confirmed to be running but I am getting failed as shown in the output. Following is an extract of MGCP configuration in VG224:

hostname voip-010
ip domain name corporateict.domain
interface FastEthernet0/0
ip address 10.10.1.57 255.255.255.0
duplex auto
speed auto
ip default-gateway 10.10.1.1
ip route 0.0.0.0 0.0.0.0 10.10.1.1
voice-port 2/0
cptone AU
!
voice-port 2/1
cptone AU
!!!!!!!!!!!!!!
voice-port 2/23
cptone AU
!
ccm-manager redundant-host 10.101.20.50
ccm-manager mgcp
no ccm-manager fax protocol cisco
ccm-manager music-on-hold
ccm-manager config server 10.10.1.50
ccm-manager config
!
mgcp
mgcp call-agent 10.10.1.50 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
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 FastEthernet0/0
mgcp bind media source-interface FastEthernet0/0
!
mgcp profile default
!
dial-peer voice 1 pots
service mgcpapp
incoming called-number .
port 2/0
!
dial-peer voice 2 pots
service mgcpapp
incoming called-number .
port 2/1
!!!!!!!!!!!!!!!!!!!!!!!!!
dial-peer voice 24 pots
service mgcpapp
incoming called-number .
port 2/23
!

Thanks much in advance for your contribution.

Best regards,

Lay

Labels:
0 Helpful
5 Replies 5

paolo bevilacqua
Hall of Fame
Hall of Fame

‎05-17-2011 05:21 AM

You should use SCCP, not MGCP to control a VG224 from CUCM.

  • Specifically designed phones and their features.
  • More features.
  • Less trouble.
    0 Helpful

    Rob Huffman
    Hall of Fame
    Hall of Fame

    ‎05-17-2011 07:12 AM

    Hi Lay,

    MGCP Gateway registration problems are often related to Domain Name issues

    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00805a316c.shtml

    Cheers!

    Rob

    0 Helpful

    layhlaing
    Level 1
    Level 1
    In response to Rob Huffman

    ‎05-17-2011 06:59 PM

    Thanks Guys for your replies. Rob, I have tried restarting mgcp in VG224 and re-configuring domain name to ensure it matches with the one in CUCM. I have also restarted TFTP service in CUCM but still no difference.

    no mgcp

    mgcp

    hostname voip-010

    ip domain name corporateict.domain

    I have turned on "debug mgcp packet" and got the followings:

    voip-010#debug mgcp packet
    Media Gateway Control Protocol packet debugging for all end points is on
    voip-010#
    May 18 08:54:18.710: MGCP Packet sent to 10.10.1.50:2427--->
    RSIP 30552318 *@voip-010.corporateict.domain MGCP 0.1
    RM: graceful
    <---

    May 18 08:54:18.714: MGCP Packet sent to 10.101.20.50:2427--->
    RSIP 30552320 *@voip-010.corporateict.domain MGCP 0.1
    RM: restart
    <---

    May 18 08:54:18.714: MGCP Packet received from 10.10.1.50:2427--->
    200 30552318
    <---

    May 18 08:54:18.714: [S] mgcp_msg_ack:6152,Updating (*)=10.10.1.50
    May 18 08:54:18.714: *:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.714: aaln/S*/*:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.714: aaln/S2/*:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.714: aaln/S2/0:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/1:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/2:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/3:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/4:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/5:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/6:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/7:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/8:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/9:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/10:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/11:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/12:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/13:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/14:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/15:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/16:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/17:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/18:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/19:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/20:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/21:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/22:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.718: aaln/S2/23:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:54:18.762: MGCP Packet received from 10.101.20.50:2427--->
    500 30552320
    <---

    May 18 08:54:48.710: MGCP Packet sent to 10.101.20.50:2427--->
    RSIP 30552322 *@voip-010.corporateict.domain MGCP 0.1
    RM: forced
    <---

    May 18 08:54:48.714: MGCP Packet sent to 10.10.1.50:2427--->
    RSIP 30552324 *@voip-010.corporateict.domain MGCP 0.1
    RM: restart
    <---

    May 18 08:54:48.714: MGCP Packet received from 10.101.20.50:2427--->
    200 30552322
    <---

    May 18 08:54:48.714: [S] mgcp_msg_ack:6152,Updating (*)=10.101.20.50
    May 18 08:54:48.714: *:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.714: aaln/S*/*:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/*:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/0:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/1:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/2:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/3:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/4:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/5:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/6:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/7:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/8:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/9:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/10:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/11:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/12:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/13:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/14:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/15:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/16:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/17:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/18:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/19:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/20:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/21:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/22:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.718: aaln/S2/23:NO-MATCH, 10.10.1.50:2427, 10.101.20.50:2427
    May 18 08:54:48.766: MGCP Packet received from 10.10.1.50:2427--->
    500 30552324
    <---

    May 18 08:55:18.709: MGCP Packet sent to 10.10.1.50:2427--->
    RSIP 30552326 *@voip-010.corporateict.domain MGCP 0.1
    RM: graceful
    <---

    May 18 08:55:18.713: MGCP Packet sent to 10.101.20.50:2427--->
    RSIP 30552328 *@voip-010.corporateict.domain MGCP 0.1
    RM: restart
    <---

    May 18 08:55:18.713: MGCP Packet received from 10.10.1.50:2427--->
    200 30552326
    <---

    May 18 08:55:18.713: [S] mgcp_msg_ack:6152,Updating (*)=10.10.1.50
    May 18 08:55:18.713: *:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.713: aaln/S*/*:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.713: aaln/S2/*:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.713: aaln/S2/0:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/1:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/2:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/3:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/4:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/5:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/6:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/7:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/8:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/9:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/10:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/11:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/12:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/13:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/14:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/15:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/16:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/17:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/18:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/19:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/20:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/21:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/22:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.717: aaln/S2/23:NO-MATCH, 10.101.20.50:2427, 10.10.1.50:2427
    May 18 08:55:18.765: MGCP Packet received from 10.101.20.50:2427--->
    500 30552328
    <---

    We have an another VG224 at an another site, it registers to its CUCM. The same/similar configuration than the fact that I have

        ccm-manager config server 10.10.1.50
        ccm-manager config
    in this VG224. I understand it is required for the registration part. And, physically, we have only the first of 24 lines are connected. Do I need to configure/associate end-point for that first line in CUCM for VG224 to be registered?

    Thank you & regards,

    Lay

    0 Helpful

    voipis4me
    Level 1
    Level 1
    In response to layhlaing

    ‎06-28-2011 08:41 AM

    Make sure that the VG224 is registered to CUCM with the correct MAC address from the FastEthernet interface of the VG224.

    0 Helpful

    Tommer Catlin
    VIP Alumni
    VIP Alumni

    ‎06-28-2011 02:16 PM

    Id get rid of the domain name information and try via IP only and see if this works.  If CUCM can not resolve the hostname of the VG224, it will no register.  At least with IP, you know its not DNS related

    0 Helpful
    Customers Also Viewed These Support Documents