Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco IOS Software Releases 12.2 T

MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles

Downloads

Table Of Contents

MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles

Feature Overview

Feature Definition

MGCP Model

Benefits

Restrictions

Related Features and Technologies

Related Documents

Supported Platforms

Supported Standards, MIBs, and RFCs

Prerequisites

Configuration Tasks

Identifying Endpoints and Configuring the MGCP Application

Configuring Global MGCP Parameters

Configuring an MGCP Profile and Profile-Related MGCP Parameters

Verifying the Configuration

Troubleshooting Tips

Configuration Examples

Cisco uBR925 Using RF Interface Example

Cisco uBR925 Using Ethernet0 Interface Example

Cisco CVA122 Using RF Interface Example

Cisco 2600 as a Residential Gateway Example

Cisco 3660 Platform as a Trunking Gateway Example

Cisco MC3810 as a Residential Gateway Example

Cisco MC3810 as a VoAAL2 Gateway using AAL2 PVCs Example

Command Reference

call-agent

debug mgcp

default (MGCP profile)

description (MGCP profile)

max1 lookup

max1 retries

max2 lookup

max2 retries

mgcp call-agent

mgcp endpoint offset

mgcp persistent

mgcp piggyback message

mgcp profile

mgcp quarantine mode

mgcp quarantine persistent-event disable

mgcp request retries

mgcp request timeout

mgcp sdp

package persistent

show mgcp

timeout tcrit

timeout tdinit

timeout tdmax

timeout tdmin

timeout thist

timeout tone busy

timeout tone cot1

timeout tone cot2

timeout tone dial

timeout tone dial stutter

timeout tone mwi

timeout tone network congestion

timeout tone reorder

timeout tone ringback

timeout tone ringback connection

timeout tone ringing

timeout tone ringing distinctive

timeout tpar

timeout tsmax

voice-port (MGCP profile)

Glossary


MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles

Feature History

Release
Modification

12.2(2)XA1

MGCP 1.0, NCS 1.0, and TGCP 1.0 is supported on these platforms in 12.2(2)XA:

•Cisco CVA122

•Cisco uBR925

•Cisco AS5300

12.2(4)T

MGCP 1.0, NCS 1.0, and TGCP 1.0 is supported on these platforms in 12.2(4)T:

•Cisco CVA122 and Cisco CVA122E

•Cisco uBR925

•Cisco 2600 series and Cisco 2650

•Cisco 3660

•Cisco MC3810

Note The Cisco AS5300 is not supported in 12.2(4)T.

AAL2 PVC support was introduced for MGCP 1.0 on the Cisco MC3810.

Certain gateway features were integrated into MGCP 1.0.

12.2(11)T

This feature was integrated into Cisco IOS Release 12.2(11)T and support was added for the Cisco AS5300 and Cisco AS5850 platform. In addition, the following values were modified:

•In the max1 retries and max2 retries commands, the maximum number of retries has changed from 10 to 30.

•In the timeout thist command, the maximum value for the Thist timer has changed from 60 seconds to 1100 seconds.

•In the timeout tsmax command, the maximum value for the Tsmax timer has changed from 100 seconds to 1000 seconds.

12.2(13)T

This feature was integrated into Cisco IOS Release 12.2(13)T and support was added for the Cisco 7200 platform.


This document describes the MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles feature in Cisco IOS Releases 12.2(11)T and 12.2(13)T. It explains the configuration of Media Gateway Control Protocol (MGCP) 1.0, PacketCableTM Network-based Call Signaling (NCS) 1.0, and PacketCableTM Trunking Gateway Control Protocol (TGCP) 1.0 on Cisco IOS media gateways, and contains these sections:

•Feature Overview

•Supported Platforms

•Supported Standards, MIBs, and RFCs

•Prerequisites

•Configuration Tasks

•Configuration Examples

•Command Reference

•Glossary

Feature Overview

This feature implements the following MGCP protocols on the supported Cisco media gateways:

•MGCP 1.0 (RFC 2705)

•Network-based Call Signaling (NCS) 1.0, the MGCP 1.0 profile for residential gateways (RGWs)

•Trunking Gateway Control Protocol (TGCP) 1.0, the MGCP 1.0 profile for trunking gateways (TGWs)

Specific feature support within these protocols is summarized in Table 1. Terms in the table are defined as follows:

•VoIP—Includes signaling methods under Voice over IP.

•AAL2 PVC—Includes signaling methods under ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC).

•Basic/Extended RGW—Includes a collection of residential gateway features supporting channel-associated signaling (CAS). Digital CAS (recEive and transMit, or E&M) interfaces and analog (Foreign Exchange Office [FXO], Foreign Exchange Station [FXS], and E&M) interfaces are supported on platforms with the appropriate voice hardware.

•ISUP—Supports ISDN user part signaling for SS7 trunks.

•FGD-OS—Supports Feature Group D Operator Services signaling over T1 or E1 trunks.

•Incoming CAS—Supports digital CAS interfaces for digital incoming multifrequency tones (MF) CAS wink-start trunks in which an operator at an Operator Services Console can initiate the Operator Interrupt and Busy Line Verify (OI and BLV) functions.

•CAS PBX—Includes CAS private branch exchange (PBX) trunks, digit maps, CAS events, and quarantine buffer software. These features are supported on digital CAS interfaces.

Table 1 Feature Support by Platform

 
VoIP
AAL2 PVC
 
MGCP 1.0
TGCP1.0
NCS1.0
MGCP 1.0
Cisco CVA122 and Cisco CVA122E

Basic/Extended RGW

--

Basic/Extended RGW

--

Cisco uBR925

Basic/Extended RGW

--

Basic/Extended RGW

--

Cisco 2600 series and Cisco 2650

Basic/Extended RGW

--

--

--

Cisco 3660

ISUP, FGD-OS, Incoming CAS

ISUP, FGD-OS, Incoming CAS

--

--

Cisco MC3810

Basic/Extended RGW,
CAS-PBX

--

--

Basic/Extended RGW,
CAS-PBX

Feature Definition

MGCP1.0 is a protocol for the control of Voice over IP (VoIP) calls by external call-control elements known as media gateway controllers (MGCs) or call agents (CAs). It is described in the informational RFC 2705, published by the Internet Society.

PacketCable is an industry-wide initiative for developing interoperability standards for multimedia services over cable facilities using packet technology. PacketCable developed the NCS and TGCP protocols, which contain extensions and modifications to MGCP while preserving basic MGCP architecture and constructs. NCS is designed for use with analog, single-line user equipment on residential gateways, while TGCP is intended for use in VoIP-to-PSTN trunking gateways in a cable environment. To meet European cable requirements and equipment characteristics, the EuroPacketCable working group has adapted PacketCable standards under the name IP Cablecom.

MGCP Model

MGCP bases its call control and intelligence in centralized call agents, also called media gateway controllers. The call agents issue commands to simple, low-cost endpoints, which are housed in media gateways (MGs), and the call agents also receive event reports from the gateways. MGCP messages between call agents and media gateways are sent with Internet Protocol over User Datagram Protocol (IP/UDP).

The MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles feature provides protocols for RGWs and TGWs, which sit at the border of the packet network to provide an interface between traditional, circuit-based voice services and the packet network. Residential gateways offer a small number of analog line interfaces, while trunking gateways generally manage a large number of digital trunk circuits.

Two basic MGCP constructs are endpoints and connections. An endpoint is a source or sink for call data (RTP/IP) that is flowing through the gateway. A common type of endpoint is found at the physical interface between the POTS (plain old telephone service) or Public Switched Telephone Network (PSTN) service and the gateway; this type of endpoint might be an analog voice port or a digital DS0 group. There are other types of endpoints as well, and some are logical rather than physical. An endpoint is identified by a two-part endpoint name that contains the name of the entity on which it exists (for example, an access server or router) and the local name by which it is known (for example, a port identifier).

A connection is a temporary allocation of resources that enables a call to be completed. One or more connections is necessary to complete a call. Connections have names that identify them with the call to which they belong. Connections can be one-to-one or multipoint. Calls and connections are initiated, modified, and deleted on instructions from call agents.

Call agents manage call flow through standard MGCP commands that are sent to the endpoints under their control. The commands are delivered in standard ASCII text, and may contain session descriptions transmitted in Session Description Protocol (SDP), a text-based protocol. These messages are sent over IP/UDP.

Call agents keep track of endpoint and connection status through the gateway's reporting of standard events that are detected from endpoints and connections. Call agents also direct gateways to apply certain standard signals when a POTS or PSTN connection expects them. For example, when someone picks up a telephone handset, an off-hook event is detected on an endpoint on the residential gateway to which the telephone is connected. The gateway reports the event to a call agent, which orders the gateway to apply the dial-tone signal to the endpoint reporting the off-hook event. The person picking up the handset hears dial tone.

Related events and signals are grouped into standard packages that apply to particular types of endpoints. For instance, the off-hook event is found in the line package, which is associated with analog-line endpoints, which in turn are associated with residential gateways. Standard events, signals, and packages are defined in the NCS, TGCP, and MGCP standards and RFCs listed in the "Supported Standards, MIBs, and RFCs" section.

Figure 1 shows a hypothetical MGCP network with both residential and trunking gateways. The residential gateway has telephone sets connected to the gateway's FXS voice ports. MGCP or NCS over IP/UDP is used for call control and reporting to the call agent, while Real-Time Transport Protocol (RTP) is used to transmit the actual voice data.

Figure 1 also shows two trunking gateways with T1 (or E1) connections to the PSTN. Incoming time-division multiplexing (TDM) data is sent through the gateway into the packet network using RTP. MGCP or TGCP over IP/UDP is used for call control and reporting to the call agent. Signaling System 7 (SS7) data travels a different route, however, bypassing the trunking gateway entirely in favor of a specialized signaling gateway, where the signaling data is transformed to ISUP/IP format and relayed to the call agent. Communication between two signaling gateways in the same packet network can be done with Integrated Services Digital Networks User Part over Internet Protocol (ISUP/IP), H.323, or Session Initiation Protocol (SIP).

Figure 1 MGCP Network Model

Benefits

•MGCP 1.0 provides flexible interoperability with a wide variety of call agents, thus enabling a wide range of solutions.

•MGCP 1.0 contains many improvements over its previous release (MGCP 0.1).

•NCS 1.0 and TGCP 1.0 allow participation in packet cable solutions.

•The ability to interoperate with H.323 and SIP control agents allows leverage of the feature sets available in the different protocols and provides the ability to migrate smoothly from one protocol to another.

Restrictions

NCS 1.0 is not supported on the Cisco 2600 series and the Cisco 2650.

Related Features and Technologies

•Voice over IP (VoIP) (all platforms)

•VoAAL2-PVC (Cisco MC3810 only)

Related Documents

•Cisco IOS Voice, Video, and Fax Configuration Guide, Release 12.2

•Cisco IOS Voice, Video, and Fax Command Reference, Release 12.2

•Cisco IOS Wide-Area Networking Configuration Guide, Release 12.2

•MGCP CAS PBX and AAL2 PVC, Cisco IOS Release 12.2(2)T

•MGCP Basic CLASS and Operator Services, Cisco IOS Release 12.2(2)T

•Media Gateway Control Protocol Residential Gateway Support, Cisco IOS Release 12.1(3)T

•Cisco CVA120 series product documentation

•Cisco uBR925 product documentation

•Cisco 2600 series product documentation

•Cisco 3600 series product documentation

•Cisco MC3810 product documentation

Supported Platforms

•Cisco 2600 series and Cisco 2650

•Cisco 3660

•Cisco CVA122 and Cisco CVA122E

•Cisco MC3810

•Cisco AS5300

•Cisco AS5850

•Cisco uBR925

Table 2 Cisco IOS Release and Platform Support for this Feature

Platform
12.2(2)XA1
12.2(4)T
12.2(11)T

Cisco 2600 series and Cisco 2650

Not supported

X

X

Cisco 3660

Not supported

X

X

Cisco CVA122

X

X

X

Cisco CVA122E

Not supported

X

X

Cisco MC3810

Not supported

X

X

Cisco AS5300

X

Not supported

X

Cisco AS5850

Not supported

Not supported

X

Cisco uBR925

X

X

X


Determining Platform Support Through Cisco Feature Navigator

Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.

Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.

To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions at http://www.cisco.com/register.

Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:

http://www.cisco.com/go/fn

Availability of Cisco IOS Software Images

Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.

Supported Standards, MIBs, and RFCs

Standards

•PacketCable. Network-Based Call Signaling (NCS) Protocol Specification PKT-SP-EC-MGCP-I02-991201, December 1, 1999

•PacketCable. PSTN Gateway Call Signaling Protocol Specification (TGCP) PKT-SP-TGCP-D02-991028, December 1, 1999

MIBs

•XGCP MIB

•RTP MIB

•Dial Control MIB

To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

RFCs

•RFC 2327: SDP: Session Description Protocol, April 1998

•Informational RFC 2705: Media Gateway Control Protocol (MGCP) version 1.0, October, 1999

•Informational RFC 3064: MGCP CAS Packages, February 2001

Prerequisites

Complete the following tasks before configuring this feature:

•Ensure that the minimum software requirements are met. For all platforms: Cisco IOS Release 12.2(11)T, or a later release.

•Configure IP routing. Refer to the Cisco IOS IP Configuration Guide, Release 12.2.

•Configure voice ports. Refer to the Cisco IOS Voice, Video, and Fax Configuration Guide, Release 12.2.

•Configure Voice over IP. Refer to the Cisco IOS Voice, Video, and Fax Configuration Guide, Release 12.2.

•Configure Voice over ATM AAL2 PVC (optional step that applies to Cisco MC3810 only). Refer to "Configuring ATM" in the Cisco IOS Wide-Area Networking Configuration Guide, Release 12.2. The router that is intending to use the VoAAL2 features must have hardware support for VoAAL2.

•Set up the call agent or agents. Refer to the documentation that accompanies the call agents used in your network configuration.

•Set up the cable modems, if any. Refer to the documentation for the cable product as listed in the "Related Documents" section.

Configuration Tasks

The three tasks listed below configure the MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles feature on a media gateway. The first task names the voice ports or DS1 groups that are serving as MGCP endpoints. This task also associates the ports with an MGCP service type or application and starts the MGCP daemon.

The last two tasks allow you to configure MGCP parameters to meet your requirements. Each MGCP parameter is either a global parameter or a profile-related parameter. When you configure a global MGCP parameter value, it applies to all the MGCP endpoints on the gateway. When you configure a profile-related MGCP parameter value, it applies only to the endpoints associated with the MGCP profile that you are configuring at that moment (an MGCP profile is a user-defined subset of all the MGCP endpoints on the gateway). There is also a predefined MGCP profile named default that you can use to configure profile-related parameters for endpoints that do not belong to a user-defined MGCP profile.

See the following sections for configuration tasks for the MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles feature. Each task in the list is identified as either required or optional:

•Identifying Endpoints and Configuring the MGCP Application (required)

•Configuring Global MGCP Parameters (optional)

•Configuring an MGCP Profile and Profile-Related MGCP Parameters (optional)

Identifying Endpoints and Configuring the MGCP Application

This task is required. Voice ports or DS0 groups that are acting as MGCP endpoints must be identified and associated with the MGCP application. The commands to identify MGCP endpoints depend on the type of endpoint that you are configuring.

To identify endpoints and configure the MGCP application, use the commands in the appropriate table, beginning in global configuration mode:

•Analog CAS and POTS lines

•Digital CAS Trunks

•ISUP Signaling Trunks

•FGD-OS Trunks

•Digital VoATM with AAL2 PVC

Analog CAS and POTS lines

To identify endpoints and configure the MGCP application for use with analog CAS and POTS lines, use these commands, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# dial-peer voice tag pots

Enters dial-peer configuration mode and specifies the method of voice encapsulation.

Step 2 

Router(config-dial-peer)# application mgcpapp

Enables the MGCP application on this dial peer.

Step 3 

Router(config-dial-peer)# port port-number

Associates a dial peer with a specific voice port.

Step 4 

Router(config-dial-peer)# exit

Exits dial-peer configuration mode.

Step 5 

Router(config)# mgcp [gw-port]

Initiates the MGCP daemon. The optional port number argument allows you to specify the UDP port over which the gateway receives messages from the call agent (the gateway MGCP port number).

The default UDP port number for gateways is 2427.

Digital CAS Trunks

To identify endpoints and configure the MGCP application for use with digital CAS trunks, use these commands, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# controller {t1 | e1} cntlr-number

Configures a T1 or E1 controller and enters controller configuration mode for the digital CAS port.

Step 2 

Router(config-controller)# mode cas

(Required for Cisco MC3810 only) Configures the T1 or E1 controller to support CAS mode.

Step 3 

T1 lines

Router(config-controller)# framing {sf | esf}

E1 lines

Router(config-controller)# framing {crc4 | no-crc4} [australia]


Selects frame type for T1 or E1 line.

The keywords and arguments are as follows:

T1 lines

•sf—Super Frame

•esf —Extended Super Frame

E1 lines

•crc4—Provides four bits of error protection.

•no-crc4—Disables crc4.

•australia—(Optional) Specifies the E1 frame type used in Australia.

The default for T1 is sf.

The default for E1 is crc4.

Step 4 

T1 lines

Router(config-controller)# linecode {ami | b8zs}

E1 lines

Router(config-controller)# linecode {ami | hdb3}

Specifies the line encoding to use.

The keywords and arguments are as follows:

•ami—Specifies the alternate mark inversion (AMI) line code type. (T1 and E1)

•b8zs—Specifies the binary 8-zero substitution (B8ZS) line code type. (T1 only)

•hdb3—Specifies the high-density bipolar 3 (HDB3) line code type. (E1 only)

The default for T1 is ami.

The default for E1 is hdb3.

Step 5 

Router(config-controller)# ds0-group channel-number timeslots range type type

Specifies the DS0 time slots that make up a logical voice port on a T1 or E1 controller and specifies the signaling type by which the router connects to the PBX or PSTN. Use command-line interface (CLI) help (enter ? after type) or see the Cisco IOS Voice, Video, and Fax Configuration Guide, Release 12.2, for valid signaling types.

Step 6 

Router(config-controller)# exit

Exits controller configuration mode.

Step 7 

Cisco 2600 and 3600 Series

Router(config)# voice-port slot/port:ds0-group-no

Cisco MC3810

Router(config)# voice-port slot:ds0-group-no

Enters voice-port configuration mode. The arguments are defined as follows:

•slot—Specifies the router location where the network module is installed. This is the same number as the controller for the T1/E1 voice port.

•port—Indicates the voice interface card location.

•ds0-group-no—Specifies the logical voice port that was created with the ds0-group controller command.

Step 8 

Router(config-voiceport)# dial-type {dtmf | mf | pulse}

(Required for MF trunks) Specifies the type of out-dialing for voice port interfaces. The keywords are as follows:

•dtmf—Dual tone multifrequency (DTMF) touch-tone dialing. This is the default.

•mf—Multifrequency tone dialing.

•pulse—Pulse (rotary) dialing.

The default is dtmf.

Step 9 

Router(config-voiceport)# exit

Exits voice-port configuration mode.

Step 10 

Router(config)# dial peer voice tag pots

Enters dial-peer configuration mode and specifies the method of voice encapsulation.

Step 11 

Router(config-dial-peer)# application mgcpapp

Enables the MGCP application on this dial peer.

Step 12 

Router(config-dial-peer)# port port-number

Associates a dial peer with a specific voice port.

Step 13 

Router(config-dial-peer)# exit

Exits dial-peer configuration mode.

Step 14 

Router(config)# mgcp [gw-port]

Initiates the MGCP daemon. The optional port number argument allows you to specify the UDP port over which the gateway receives messages from the call agent (the gateway MGCP port number).

The default UDP port number for gateways is 2427.

ISUP Signaling Trunks

To identify endpoints and configure the MGCP application for use with ISUP signaling trunks, use these commands, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# controller {t1 | e1} cntlr-number

Configures a T1 or E1 controller and enters controller configuration mode for the ISUP trunk port.

Step 2 

Router(config-controller)# ds0-group channel-number timeslots range type none service mgcp

Specifies the DS0 time slots that make up a logical voice port on a T1 or E1 controller and specifies the signaling type by which the router connects to the PBX or PSTN.

Specify the type none and service mgcp options to identify this voice port as an MGCP endpoint.

Step 3 

Router(config-controller)# exit

Exits controller configuration mode.

Step 4 

Router(config)# mgcp [gw-port]

Initiates the MGCP daemon. The optional port number argument allows you to specify the UDP port over which the gateway receives messages from the call agent (the gateway MGCP port number).

The default UDP port number for gateways is 2427.

FGD-OS Trunks

To identify endpoints and configure the MGCP application for use with Feature Group D Operator Services (FGD-OS) signaling over T1 or E1 trunks, use these commands, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# controller {t1 | e1} cntlr-number

Configures a T1 or E1 controller and enters controller configuration mode for the FGD-OS trunk port.

Step 2 

Router(config-controller)# ds0-group channel-number timeslots range type fgd-os service mgcp

Specifies the DS0 time slots that make up a logical voice port on a T1 or E1 controller and specifies the signaling type by which the router connects to the PBX or PSTN.

Specify the type fgd-os option for FGD-OS signaling, and the service mgcp option to identify this voice port as an MGCP endpoint.

Step 3 

Router(config-controller)# exit

Exits controller configuration mode.

Step 4 

Router(config)# mgcp [gw-port]

Initiates the MGCP daemon. The optional port number argument allows you to specify the UDP port over which the gateway receives messages from the call agent (the gateway MGCP port number).

The default UDP port number for gateways is 2427.

Digital VoATM with AAL2 PVC

To identify endpoints and configure the MGCP application for use with digital VoATM with AAL2 PVC, use these commands, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# controller {t1 | e1} cntlr-number

Enters dial-peer configuration mode and specifies the method of voice encapsulation.

Step 2 

Router(config-controller)# mode atm

Specifies that the controller will support ATM encapsulation and create ATM interface 0.

When the controller is set to ATM mode, the following takes place:

•Controller framing is automatically set to Extended Superframe (ESF).

•The line code is automatically set to B8ZS.

Step 3 

T1 lines

Router(config-controller)# framing {sf | esf}

E1 lines

Router(config-controller)# framing {crc4 | no-crc4} [australia]


Selects frame type for T1 or E1 line.

The keywords and arguments are as follows:

T1 lines

•sf—Super Frame

•esf —Extended Super Frame

E1 lines

•crc4—Provides 4 bits of error protection.

•no-crc4—Disables crc4.

•australia—(Optional) Specifies the E1 frame type used in Australia.

The default for T1 is sf.

The default for E1 is crc4.

Step 4 

T1 lines

Router(config-controller)# linecode {ami | b8zs}

E1 lines

Router(config-controller)# linecode {ami | hdb3}

Specifies the line encoding to use.

The keywords and arguments are as follows:

•ami—Specifies the alternate mark inversion (AMI) line code type. (T1 and E1)

•b8zs—Specifies the binary 8-zero substitution (B8ZS) line code type. (T1 only)

•hdb3—Specifies the high-density bipolar 3 (HDB3) line code type. (E1 only)

The default for T1 is ami.

The default for E1 is hdb3.

Step 5 

Router(config-controller)# exit

Exits controller configuration mode.

Step 6 

Router(config)# dial peer voice tag pots

Enters dial-peer configuration mode and specifies the method of voice encapsulation.

Step 7 

Router(config-dial-peer)# application mgcpapp

Enables the MGCP application on this dial peer.

Step 8 

Router(config-dial-peer)# port port-number

Associates a dial peer with a specific voice port.

Step 9 

Router(config-dial-peer)# exit

Exits dial-peer configuration mode.

Step 10 

Router(config)# mgcp [gw-port]

Initiates the MGCP daemon. The optional port number argument allows you to specify the UDP port over which the gateway receives messages from the call agent (the gateway MGCP port number).

The default UDP port number for gateways is 2427.

Configuring Global MGCP Parameters

This optional task configures global MGCP parameters on the gateway so that you can set these values to conform to the requirements of the call agent, trunks, or lines that are being used with this gateway. The global parameter values that you configure are associated with every MGCP endpoint that you have identified on this gateway.

In addition to the global MGCP parameters, there are other MGCP parameters that apply only to MGCP profiles on the gateway. For configuration of profile-related parameters, see the "Configuring an MGCP Profile and Profile-Related MGCP Parameters" section.

Note The only parameter that is common to both profile and global configurations is the call agent parameter, which is configured with the call-agent command for MGCP profile configuration and with the mgcp call-agent command for the global configuration. These commands are mutually exclusive; whichever command you configure first blocks configuration of the other. For example, if the MGCP profile call-agent command is configured on an endpoint, then you are not allowed to configure the global mgcp call-agent command.

To configure global MGCP parameters, complete these steps as needed, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# mgcp call-agent {dns-name | ip-address} [port] [service-type type] [version protocol-version]

Configures parameters for communicating with the call agent (media gateway controller). The keywords and arguments are as follows:

•dns-name—Fully qualified domain name (including host portion) for the call agent.

•ip-address—IP address of the call agent.

•port—UDP port number over which the gateway sends messages to the call agent. Range is from 1025 to 65,535. The default is 2727 for MGCP 1.0, NCS 1.0, and TGCP 1.0. The default is 2427 for MGCP 0.1 and SGCP.

•service-type type—Protocol service type. Valid values are mgcp, ncs, sgcp, and tgcp.

•version version—Protocol version. Valid values are:

–For service-type mgcp: 0.1, 1.0

–For service-type ncs: 1.0

–For service-type sgcp: 1.1, 1.5

–For service-type tgcp: 1.0

Note You can define a call agent globally with the mgcp call-agent command, or locally for each MGCP profile with the call-agent command, but not both. Whichever command you configure first blocks configuration of the other.

Step 2 

Router(config)# mgcp sdp simple

Specifies that a subset of the SDP fields should be used.

Step 3 

Router(config)# mgcp sdp xpc-codec

Enables codec negotiation in the SDP.

Step 4 

Router(config)# mgcp codec type [packetization-period value]

Selects the default codec type and its optional packetization period value. The keywords and arguments are as follows:

•type—Specifies the types of codec supported. Valid codecs are G711alaw, G711ulaw, G723ar53, G723ar63, G723r53, G723r63, G729ar8, G729br8, and G729r8.

•packetization-period value—This parameter is useful when the preferred compression algorithm and packetization period parameter is not provided by the Media Gateway Controller. The value range depends on the type of codec selected. For example, the range for G729r8 is 10 to 220 in increments of 10. For G711ulaw, the range is 10 to 20 in increments of 10. For G723ur53, the range is 30 to 330 in increments of 10.

Step 5 

Router(config)# no mgcp timer receive-rtcp

Disables the timer used by a gateway to disconnect a VoIP call when the IP connectivity is lost with the remote gateway. The timer is known as the RTP Control Protocol (RTCP) transmission interval timer.

Step 6 

Router(config)# no mgcp piggyback message

Disables piggyback messages.

Step 7 

Router(config)# mgcp endpoint offset

Increments the voice-port or DS0-group portion of the endpoint name for NCS 1.0.

Step 8 

Router(config)# mgcp persistent {hookflash | offhook | onhook}

Enables call-agent notification of the specified type of event. The keywords are as follows:

•hookflash—Sends persistent hookflash events to the call agent.

•offhook—Sends persistent off-hook events to the call agent.

•onhook—Sends persistent on-hook events to the call agent.

Step 9 

Router(config)# mgcp request timeout {timeout-value | max maxtimeout-value}

Specifies how long the gateway waits for a call-agent response to a request before retransmitting the request. The keywords and arguments are as follows:

•timeout-value—Specifies the number of milliseconds to wait for a response to the initial request. Valid range is 1 to 10,000 (10 seconds). The default is 500 (.5 seconds).

•max maxtimeout-value—Specifies the maximum number of milliseconds to wait for a response in subsequent requests. Valid range is 1,000 to 20,000 (20 seconds). The default is 4,000 (4 seconds).

Step 10 

Router(config)# mgcp dtmf-relay voip codec {all | low-bit-rate} mode {cisco | nse | out-of-band}

Ensures accurate forwarding of digits with a compressed codec. The keywords are as follows:

•all—Any codec.

•low-bit-rate—Any version of the G.729 low-bit-rate codecs.

•cisco—Removes the DTMF tone from the voice stream and sends FRF.11 with a special payload 121 for the DTMF digits.

•nse—Uses the NSE-based forwarding method.

•out-of-band—Removes the DTMF tone from the voice stream and does not send FRF.11.

Step 11 

Router(config)# mgcp max-waiting-delay value

Specifies the number of milliseconds to wait after a restart before connecting with the call agent. The range is 0 to 600,000 milliseconds (600 seconds). The default is 3,000.

If used, these values should be staggered among gateways to avoid having large numbers of gateways connecting with the call agent at the same time after a mass restart.

Step 12 

Router(config)# mgcp restart-delay value

Sets the delay value sent in the RestartInProgress (RSIP) graceful teardown. The valid range is from 0 to 600 seconds. The default is 0 seconds.

Step 13 

Router(config)# mgcp vad

Enables voice activity detection (VAD) as a default for MGCP calls. The default is that VAD is disabled.

Step 14 

Router(config)# mgcp ip-tos {high-reliability | high-throughput | low-cost | low-delay | rtp precedence value | signaling precedence value}

Enables the IP type of service (ToS) for MGCP-controlled connections. The keywords and arguments are as follows:

•high-reliability, high-throughput, low-cost, low-delay—Indicates type of TOS to enable.

•rtp precedence—Specifies the IP precedence value for MGCP-controlled RTP packets. Valid values are from 0 to 7. The default RTP precedence value is 5.

•signaling precedence—Specifies the IP precedence value for MGCP UDP and RTCP signaling packets. Valid values are from 0 to 7. The default signaling precedence value is 3.

Step 15 

Router(config)# mgcp quality-threshold {hwm-cell-loss value | hwm-jitter-buffer value | hwm-latency value | hwm-packet-loss value | lwm-cell-loss value | lwm-jitter-buffer value | lwm-latency value | lwm-packet-loss value}

Sets the jitter buffer size threshold, latency threshold, and packet-loss threshold parameters. The keywords and arguments are as follows:

•hwm-cell-loss value—Available when the ATM package is enabled. Specifies the high-water-mark cell loss count. Valid range is 5,000 to 25,000 milliseconds. The default is 10,000.

•hwm-jitter-buffer value—High-water-mark jitter buffer size. Valid range is from 100 to 200 milliseconds. The default is 150.

•hwm-latency value—High-water-mark latency value. Valid range is from 250 to 400 milliseconds. The default is 300.

•hwm-packet-loss value—High-water-mark packet-loss value. Valid range is from 5,000 to 25,000 milliseconds. The default is 10,000.

•lwm-cell-loss value—Available when the ATM package is enabled. Specifies the low-water-mark cell loss count. Valid range is from 1 to 3,000 milliseconds. The default is 1,000.

•lwm-jitter-buffer value—Low-water-mark jitter buffer size. Valid range is from 4 to 60 milliseconds. The default is 30.

•lwm-latency value—Low-water-mark latency value. Valid range is from 125 to 200 milliseconds. The default is 150.

•lwm-packet-loss value—Low-water-mark packet-loss value. Valid range is from 1 to 3000 milliseconds. The default is 1000.

Step 16 

Router(config)# mgcp playout {adaptive init-value min-value max-value | fixed init-value}

Configures the jitter buffer packet size in milliseconds for MGCP calls, using either an adaptive range or a fixed value. The default is adaptive 60 4 200. The keywords and arguments are as follows:

•adaptive init-value min-value max-value— Specifies a user-defined variable range (in milliseconds) for the jitter buffer packet size. The range for each value is 4 to 250. The default values are: init-value 60, min-value 4, and max-value 200. Note that init-value must fall between min-value and max-value.

•fixed init-value—Specifies a fixed size (in milliseconds) for the jitter buffer packet size. Valid values are from 4 to 250.

Step 17 

Router(config)# mgcp package-capability [package-type]

Specifies an MGCP package to be supported on this gateway. Configure one package at a time and repeat this command to configure support for more than one package.

For residential gateways, the choices are dtmf-package, gm-package, line-package, and rtp-package. The default is line-package.

For trunking gateways, the choices are as-package, dtmf-package, gm-package, mf-package, nas-package, rtp-package, script-package, and trunk-package. The default is trunk-package.

Step 18 

Router(config)# mgcp default package [package-type]

Defines the package to be used as the default when no package is named with an event.

For residential gateways, the choices are dtmf-package, gm-package, line-package, and rtp-package. The default is line-package.

For trunking gateways, the choices are as-package, dt-package, dtmf-package, gm-package, mf-package, mo-package, ms-package, nas-package, rtp-package, script-package, and trunk-package. The default is trunk-package.

Configuring an MGCP Profile and Profile-Related MGCP Parameters

This optional task creates a named, user-defined MGCP profile that consists of a subset of all the MGCP endpoints on this gateway. More than one MGCP profile can be configured on a gateway. Each MGCP profile is associated with a call agent and one or more endpoints. When multiple MGCP profiles are configured, endpoints on a single media gateway can be controlled by different call agents. When each endpoint comes on line, an RSIP (RestartInProgress) message notifies the appropriate call agent of the endpoint's presence.

Note When partitioning a gateway for multiple call-agent control, the call agents must be coordinated so that there are no overlapping transaction identification numbers.

In addition, this task allows you to configure profile-related MGCP parameters to conform to the requirements of the call agent, trunks, or lines that are being used with the profile's endpoints. These parameters are called profile-related MGCP parameters because they are associated with a particular MGCP profile, or subset of endpoints, and they are configured in MGCP profile configuration mode. Other parameters are considered global MGCP parameters; when they are configured, they apply to all the endpoints on a gateway. Global MGCP parameters are discussed in the "Configuring Global MGCP Parameters" section.

The parameters for an MGCP profile are configured in a special MGCP profile configuration mode that you enter with the mgcp profile command. One or more endpoints are associated with the profile by using the voice-port command in MGCP profile configuration mode.

Note The only parameter that can be configured in both profile configuration mode and in global configuration mode is call agent, which is configured with the call-agent command for MGCP profiles, and with the mgcp call-agent command for global configurations. These commands are mutually exclusive; whichever command you configure first blocks configuration of the other. For example, if the MGCP profile call-agent command is configured on an endpoint, then you are not allowed to configure the global mgcp call-agent command.

You do not have to define MGCP profiles to configure profile-related parameters. For endpoints that are not associated with a user-defined MGCP profile, the values for profile-related parameters are provided by a predefined profile with the name default. The default profile is configured in the same way that a user-defined MGCP profile is configured, except that the keyword default is used in place of a profile name in the mgcp profile command. The default profile has no association with voice ports or a call agent (the call agent for these endpoints is defined by the global mgcp call-agent command).

In the excerpt below from a show running-config command output, two MGCP profiles are defined: MAX1 and MAX2. Each profile is associated with a different call agent and a different voice port. The MAX1 profile is configured with a value of 3 for the max1 retries parameter and 5 for max2 retries. The MAX2 profile uses the values in the default profile for those parameters. In the MAX2 profile, the MT package is configured as a persistent package. The max1 retries parameter for the default profile is configured with a value of 2. The max2 retries parameter is not configured, so the value used is the default value, which is 7. The MAX2 profile has a value of 2 for the max1 retries parameter and 7 for max2 retries. 

.

.

.

!

mgcp profile MAX1

 call agent ca1.example.com 4022 service-type mgcp version 1.0

 max1 retries 3

 max2 retries 5

 voice-port 2/1:1

!

mgcp profile MAX2

 call-agent ca2.example.com 50031 service-type mgcp version 0.1

 package persistent mt-package

 voice-port 2/0:1

!

mgcp profile default

 max1 retries 2

.

.

.

To configure parameters for a user-defined MGCP profile or for the default profile, use the following commands as appropriate, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# mgcp profile {profile-name | default}

Initiates MGCP profile mode, in which you create and configure a named MGCP profile associated with one or more endpoints, or configure the default profile. The keyword and argument are as follows:

•profile-name—Provides an identifying name for the user-defined profile to be configured. The name can be a maximum of 32 characters.

•default—Specifies the default profile is to be configured.

Step 2 

Router(config-mgcp-profile)# description {text}

Provides a description for the profile.

Step 3 

Router(config-mgcp-profile)# call-agent {dns-name | ip-address} [port] [service-type type] [version protocol-version]

Defines the call agent's DNS name or IP address, UDP port number, service type, and protocol version. (Not used when configuring the default profile.) The keywords and arguments are as follows:

•dns-name—Fully qualified domain name (including host portion) for the call agent.

•ip-address—IP address of the call agent.

•port—UDP port number over which the gateway sends messages to the call agent. Range is from 1025 to 65535. The default is 2727 for MGCP 1.0, NCS 1.0, and TGCP 1.0, and 2427 for MGCP 0.1 and SGCP.

•service-type type—Protocol service type. Valid values are mgcp, ncs, sgcp, and tgcp.

•version version—Protocol version. Valid values are:

–For service-type mgcp: 0.1, 1.0

–For service-type ncs: 1.0

–For service-type sgcp: 1.1, 1.5

–For service-type tgcp: 1.0

Note You can define a call agent globally with the mgcp call-agent command, or locally for each MGCP profile with the call-agent command, but not both. Whichever command you configure first blocks configuration of the other.

Step 4 

Router(config-mgcp-profile)# voice-port port-number

Provides the voice port number or DS0 group number for the endpoint to be associated with this MGCP profile. Repeat this command to add more than one endpoint to the profile. (Not used when configuring the default profile.)

Step 5 

Router(config-mgcp-profile)# default {command}

Restores the parameter represented by command to its default value.

Step 6