MGCP Gateway Setup

Posted: June 21, 2010 in Gateways, MGCP
Tags: ,

MGCP Configuration Using Trombone Feature:

To register an MGCP gateway to call manager, follow these steps:

  • Do a show inventory OR show diag to check the position of E1/T1
  • Enable the E1/T1 by using command – card type T1 0 0 OR card type T1 0 1 (whatever the case may be)
  • Do show ver to check what gateway is it
  • isdn switch-type primary-ni
  • network-clock-particpate wic 0
  • network-clock-select 1 E1 0/0/0
  • Go to CCM and add MGCP gateway as per type
  • Make sure the name and domain are exactly the same as they are on gateway
  • If domain is cisco.com and the name of the router is R1 then under domain you would enter “R1.cisco.com”
  • Select the module in Slot 0 or Slot 1 as found out from earlier commands
  • Select the VWIC in proper subunit – Save the config
  • Select Device protocol as “Digital Access PRI”
  • Select Device pool
  • Call classification: offnet
  • Significant digits: 4 (as per internal extensions) – if you are not using any translation rules otherwise you can select all here
  • All checked – Display IE delivery, Redirecting Number IE Delivery – Outbound, Redirecting Number IE Delivery – Inbound
  • Check Linecode and Framing as per your requirements – ammend if required
  • Save the config
  • Go to the gateway and use the following commands for trombone feature:

ccm-manager config server 10.10.210.11
ccm-manager config

These commands will enable MGCP with following auto-generated commands:

controller T1 0/0/0
framing esf
linecode b8zs
pri-group timeslots 1-24 service mgcp

ccm-manager redundant-host 10.10.210.10
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 10.10.210.11
ccm-manager config
!
mgcp
mgcp call-agent 10.10.210.11 2427 service-type mgcp version 0.1
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 timer receive-rtcp
mgcp sdp simple
mgcp rtp payload-type g726r16 static
mgcp profile default
!
!

You will still need  to bind the interfaces to your Voice VLAN or Loopback as follows:

mgcp bind control source-interface FastEthernet0/0.20
mgcp bind media source-interface FastEthernet0/0.20

Also use the following command for DTMF-RELAY:

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

Under Serial interface, use the following commands will be auto-generated but you still need bchan command:

interface Serial0/0/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
isdn bind-l3 ccm-manager
isdn bchan-number-order ascending
no cdp enable
!

Do a ‘no shut’ at Voice port:

Voice-port 0/0/0:23
no shut
!

Do a show isdn status and check if L2 and L3 is up. L3 must show “MULTIPLE_FRAME_ESTABLISHED”.

HQ#show isdn status
Global ISDN Switchtype = primary-ni
%Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 0. Layer 3 output may not apply
ISDN Serial0/0/0:23 interface
dsl 0, interface ISDN Switchtype = primary-ni
L2 Protocol = Q.921 0x0000 L3 Protocol(s) = CCM MANAGER 0x0003
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 0 CCBs = 0
The Free Channel Mask: 0x8000003F
Number of L2 Discards = 0, L2 Session ID = 3
Total Allocated ISDN CCBs = 0
R1#show voice port summa
IN OUT
PORT CH SIG-TYPE ADMIN OPER STATUS STATUS EC
=============== == ============ ===== ==== ======== ======== ==
0/0/0:23 01 xcc-voice up none none none y
0/0/0:23 02 xcc-voice up none none none y
0/0/0:23 03 xcc-voice up none none none y
0/0/0:23 04 xcc-voice up none none none y
0/0/0:23 05 xcc-voice up none none none y
0/0/0:23 06 xcc-voice up none none none y
—————————-OUTPUT OMITTED————————————-

If for any reason it is not showing Frame established and instead showing “TEI_ASSIGNED” then do the following:

int ser0/0/0:23
no isdn bind-l3 ccm-manager
isdn bind-l3 ccm-manager

This will bring the L3 interface up and you will see at the gateway:

Jun 28 22:40:31.591: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:23, TEI 0 changed to up

Also if you miss the “service mgcp” command during manual setup under controller then you won’t be able to bind L3 to ccm-manager.

MGCP Configuration CLI:

The minimum commands needed to configure MGCP are as follows:

!
ccm-manager fallback-mgcp
ccm-manager redundant-host 10.10.10.1
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 10.10.10.2
!
mgcp
mgcp call-agent 10.10.10.2 service-type mgcp version 0.1
mgcp bind control source-interface GigabitEthernet0/0.102
mgcp bind media source-interface GigabitEthernet0/0.102
!

Verification:

Check the status of CCM registration as:

HQ#sh ccm
MGCP Domain Name: HQ.cisco.com
Priority        Status                   Host
============================================================
Primary         Registered               10.10.210.11
First Backup    Backup Ready             10.10.210.10
Second Backup   None

Current active Call Manager:    10.10.210.11
Backhaul/Redundant link port:   2428
Failover Interval:              30 seconds
Keepalive Interval:             15 seconds
Last keepalive sent:            22:42:36 UTC Jun 28 2010 (elapsed time: 00:00:03)
Last MGCP traffic time:         22:42:36 UTC Jun 28 2010 (elapsed time: 00:00:03)
Last failover time:             None
Last switchback time:           None
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

Backhaul Link info:
Link Protocol:      TCP
Remote Port Number: 2428
Remote IP Address:  10.10.210.11
Current Link State: OPEN
Statistics:
Packets recvd:   12
Recv failures:   4
Packets xmitted: 11
Xmit failures:   0
PRI Ports being backhauled:
Slot 0, VIC 0, port 0
Configuration Auto-Download Information
=======================================
Current version-id: 1277766378-c7f9fddc-ae90-4306-bfb5-439bb5a2fcb6
Last config-downloaded:00:00:00
Current state: Waiting for commands
Configuration Download statistics:
Download Attempted             : 2
Download Successful          : 2
Download Failed              : 0
TFTP Download Failed         : 0
Configuration Attempted        : 1
Configuration Successful     : 1
Configuration Failed(Parsing): 0
Configuration Failed(config) : 0
Last config download command: New Registration
FAX mode: cisco
Configuration Error History:

HQ#sh mgcp
MGCP Admin State ACTIVE, Oper State ACTIVE – Cause Code NONE
MGCP call-agent: 10.10.210.11 2427 Initial protocol service is MGCP 0.1
MGCP validate call-agent source-ipaddr DISABLED
MGCP validate domain name DISABLED
MGCP block-newcalls DISABLED
MGCP send SGCP RSIP: forced/restart/graceful/disconnected DISABLED
MGCP quarantine mode discard/step
MGCP quarantine of persistent events is ENABLED
MGCP dtmf-relay voip codec all mode out-of-band
MGCP dtmf-relay for voAAL2 is SDP controlled
MGCP voip modem passthrough mode: NSE, codec: g711ulaw, redundancy: DISABLED,

(output omitted)

For debugging of Layer 2 use debug isdn q921 which must show Receiver Ready messages:

Jun 28 22:45:13.071: ISDN Se0/0/0:23 Q921: User TX -> RRp sapi=0 tei=0 nr=0
Jun 28 22:45:13.075: ISDN Se0/0/0:23 Q921: User RX <- RRf sapi=0 tei=0 nr=0

For debugging of Layer 3 call flow use debug isdn q931.

NOTE:  You may come across when your gateway is not registering to CUCM as per your ‘source-address’ or may be it is not registering at all. Issue the following command at the gateway

#no mgcp
#mgcp

The above two command are very important if you have manually configured MGCP (not using trombone) as ‘resetting’ the gateway at Call manager will not reset the gateway unless you issue the above command. If it’s configured by using trombone then ‘resetting’ at call manager will reset the gateway and mgcp as well. If you make any changes on gateway or call manager which is related to call routing then its always a good practice to reset the gateway as well.

How to check the E1/T1 card type and its position:

It is very important to find out correct card type and its slot position before you configure the gateway. Lets take an example:

HQ#sh diag
Slot 0:
C2811 Motherboard with 2FE and integrated VPN Port adapter, 2 ports
Port adapter is analyzed
Port adapter insertion time unknown
Onboard VPN             : v2.3.3
EEPROM contents at hardware discovery:
PCB Serial Number        : FOC11193CJH
Hardware Revision        : 1.0
Top Assy. Part Number    : 800-26920-03
Board Revision           : A0
Deviation Number         : 0
Fab Version              : 03
RMA Test History         : 00
RMA Number               : 0-0-0-0
RMA History              : 00
Processor type           : 87
Hardware date code       : 20070513
Chassis Serial Number    : FTX1123F0A5
Chassis MAC Address      : 001b.d504.2708
MAC Address block size   : 24
CLEI Code                : COM7C00ARA
Product (FRU) Number     : CISCO2811
Part Number              : 73-10258-04
Version Identifier       : V04
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF C1 8B 46 4F 43 31 31 31 39 33 43 4A 48 40
0x10: 03 E7 41 01 00 C0 46 03 20 00 69 28 03 42 41 30
0x20: 88 00 00 00 00 02 03 03 00 81 00 00 00 00 04 00
0x30: 09 87 83 01 32 40 71 C2 8B 46 54 58 31 31 32 33
0x40: 46 30 41 35 C3 06 00 1B D5 04 27 08 43 00 18 C6
0x50: 8A 43 4F 4D 37 43 30 30 41 52 41 CB 8F 43 49 53
0x60: 43 4F 32 38 31 31 20 20 20 20 20 20 82 49 28 12
0x70: 04 89 56 30 34 20 D9 02 40 C1 FF FF FF FF FF FF

PVDM Slot 0:
16-channel (G.711) Voice/Fax PVDMII DSP SIMM PVDM daughter card
Hardware Revision        : 4.0
Part Number              : 73-8538-05
Board Revision           : B0
Deviation Number         : 0
Fab Version              : 04
PCB Serial Number        : FOC11194QU1
RMA Test History         : 00
RMA Number               : 0-0-0-0
RMA History              : 00
Processor type           : 00
Product (FRU) Number     : PVDM2-16
Version Identifier       : V01
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 03 EF 41 04 00 82 49 21 5A 05 42 42 30
0x10: 88 00 00 00 00 02 04 C1 8B 46 4F 43 31 31 31 39
0x20: 34 51 55 31 03 00 81 00 00 00 00 04 00 09 00 CB
0x30: 88 50 56 44 4D 32 2D 31 36 89 56 30 31 20 D9 02
0x40: 40 C1 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

PVDM Slot 1:
16-channel (G.711) Voice/Fax PVDMII DSP SIMM PVDM daughter card
Hardware Revision        : 4.0
Part Number              : 73-8538-05
Board Revision           : C0
Deviation Number         : 0
Fab Version              : 04
PCB Serial Number        : FOC124757LW
RMA Test History         : 00
RMA Number               : 0-0-0-0
RMA History              : 00
Processor type           : 00
Product (FRU) Number     : PVDM2-16
Version Identifier       : V01
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 03 EF 41 04 00 82 49 21 5A 05 42 43 30
0x10: 88 00 00 00 00 02 04 C1 8B 46 4F 43 31 32 34 37
0x20: 35 37 4C 57 03 00 81 00 00 00 00 04 00 09 00 CB
0x30: 88 50 56 44 4D 32 2D 31 36 89 56 30 31 20 D9 02
0x40: 40 C1 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

WIC Slot 0:
T1 (2 port) Multi-Flex Trunk WAN daughter card

Hardware revision 1.0           Board revision C0
Serial number     35872274      Part number    800-04477-04
Version Identifier     V01      FRU Part Number     VWIC-2MFT-T1
Test history      0x0           RMA number     00-00-00
Connector type    PCI
EEPROM format version 1
EEPROM contents (hex):
0x20: 01 22 01 00 02 23 5E 12 50 11 7D 04 00 00 00 00
0x30: 60 00 00 00 07 07 09 00 FF FF FF FF FF FF FF FF

As you can see that Slot 0 is motherboard and the WIC card is at Sub Slot 0 of Slot 0 making its position 0 0.

So the card type command will be card type T1 0 0.

Another way of finding it as follows:

HQ#sh inventory
NAME: “2811 chassis”, DESCR: “2811 chassis”
PID: CISCO2811         , VID: V04 , SN: FTX1123F0A5

NAME: “Two port T1 voice interface daughtercard on Slot 0 SubSlot 0”, DESCR: “Two port T1 voice interface daughtercard” PID: VWIC-2MFT-T1      , VID: V01, SN: 35872274

NAME: “PVDMII DSP SIMM with one DSP on Slot 0 SubSlot 4”, DESCR: “PVDMII DSP SIMM with one DSP”
PID: PVDM2-16          , VID: V01 , SN: FOC11194QU1

NAME: “PVDMII DSP SIMM with one DSP on Slot 0 SubSlot 5”, DESCR: “PVDMII DSP SIMM with one DSP”
PID: PVDM2-16          , VID: V01 , SN: FOC124757LW

Advertisements
Comments
  1. i wanna ask , in asia(India) how we configure isdn pri as E1 CCS or T1 CAS if we want to terminate it at gateway?

  2. asharsidd says:

    Do a show inventory to find the E1 card slot position then configure it as follows

    card type E1 0 0

    then
    isdn switch-type primary-net5 (this is for europe ask your telco about this)

    controller E1 0/0
    pri-group timeslots 1-31 mgcp

  3. Hi
    I can not find the Device protocol which allow to select in CUCM 7.x. Please

  4. asharsidd says:

    Hi Nguyen, Please check you have selected the right VWIC and interface type. Do a show inventory to verify what is on the router. Thanks

  5. sandykt444 says:

    I have a doubt sir, if you can help me out…
    In my lab, i have a CUCM and two MGCP gatways….. one is local gateway and one is remote gateway. I configured Fallback-mgcp in remote gateway. Both the gateways are connected with PSTN and WAN.
    i) I want all the calls go through PSTN but it goes through WAN, in my network signalling and calling goes through WAN.
    ii) When i disconnect/ Connect Wan, the active calls disconnect as the my E1 re-register using Fallback-Mgcp, But I break down the connectivity between the CUCM and my Local MGCP gatway then the active calls dont disconnect. why that so? This local gatway is also having a E1 port which is registered to CUCM so it needs to go down? so what can be the issue??

  6. asharsidd says:

    Hi Sandykt444, that is because MGCP gateway is a survivable endpoint and will preserve a call in case of Call manager failure. Read more here:

    https://voiceonbits.com/2010/06/22/mgcp-call-preservation/

    Your remote gateway is actually falling back to H323 in case of WAN failure hence call will not be preserved.

    HTH

  7. I have to thank you for the efforts you’ve put in penning this website.
    I am hoping to check out the same high-grade content from
    you in the future as well. In fact, your creative writing abilities has
    motivated me to get my own, personal website now 😉

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s