Table Of Contents
MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Identifying Endpoints and Configuring the MGCP Application
Configuring Global MGCP Parameters
Configuring an MGCP Profile and Profile-Related MGCP Parameters
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
mgcp quarantine persistent-event disable
timeout tone network congestion
timeout tone ringback connection
timeout tone ringing distinctive
MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles
Feature History
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:
•
Supported Standards, MIBs, and RFCs
Feature Overview
This feature implements the following MGCP protocols on the supported Cisco media gateways:
•
•
•
Specific feature support within these protocols is summarized in Table 1. Terms in the table are defined as follows:
•
•
•
•
•
•
•
Table 1 Feature Support by Platform
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
•
•
•
•
Restrictions
NCS 1.0 is not supported on the Cisco 2600 series and the Cisco 2650.
Related Features and Technologies
•
•
Related Documents
•
•
•
•
•
•
•
•
•
•
•
Supported Platforms
•
•
•
•
•
•
•
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.
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:
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
•
•
MIBs
•
•
•
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
•
•
•
Prerequisites
Complete the following tasks before configuring this feature:
•
•
•
•
•
•
•
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
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
To identify endpoints and configure the MGCP application for use with analog CAS and POTS lines, use these commands, beginning in global configuration mode:
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:
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
•
•
E1 lines
•
•
•
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:
•
•
•
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:
•
•
•
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:
•
•
•
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:
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:
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:
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
To configure global MGCP parameters, complete these steps as needed, beginning in global configuration mode:
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
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
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 MAX1call agent ca1.example.com 4022 service-type mgcp version 1.0max1 retries 3max2 retries 5voice-port 2/1:1!mgcp profile MAX2call-agent ca2.example.com 50031 service-type mgcp version 0.1package persistent mt-packagevoice-port 2/0:1!mgcp profile defaultmax1 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:
Verifying the Configuration
Use these commands to verify configuration settings for all platforms and protocols:
Troubleshooting Tips
The following suggestions will help with troubleshooting:
•
–
–
–
•
•
Router# show rtp statisticsRTP Statistics info:No. CallId Xmit-pkts Xmit-bytes Rcvd-pkts Rcvd-bytes Lost pkts Jitter Latenc1 17492 0x8A 0x5640 0x8A 0x5640 0x0 0x0 0x0Router# show rtp statisticsRTP Statistics info:No. CallId Xmit-pkts Xmit-bytes Rcvd-pkts Rcvd-bytes Lost pkts Jitter Latenc1 17492 0xDA 0x8840 0xDB 0x88E0 0x0 0x160 0x0•
Router# show mgcpMGCP Admin State ACTIVE, Oper State ACTIVE - Cause Code NONEMGCP call-agent: 172.29.248.51 Initial protocol service is MGCP, v. 1.0...MGCP gateway port: 2727, MGCP maximum waiting delay 3000...Router# show mgcp profileMGCP Profile nycprofileDescription: NY branch office configurationCall-agent: 10.14.2.200 Initial protocol service is MGCP, v. 1.0...•
Router# show mgcp connectionEndpoint Call_ID(C) Conn_ID(I) (P)ort (M)ode (S)tate (C)odec (E)vent[SIFL] (R)esult[EA]1. S0/DS1-1/5 C=F123AB,5,6 I=0x3 P=16506,16602 M=3 S=4 C=1 E=2,0,0,2 R=0,02. S0/DS1-1/6 C=F123AB,7,8 I=0x4 P=16602,16506 M=3 S=4 C=1 E=0,0,0,0 R=0,0Router# show mgcp endpointT1/0 ds0-group 0 timeslots 1-24T1/1 ds0-group 0 timeslots 1-24T1/2 ds0-group 0 timeslots 1-24T1/3 ds0-group 0 timeslots 1-24•
•
•
•
•
Router# debug mgcp packets input-hexMedia Gateway Control Protocol input packets in hex value debugging is onMGCP Packet received -DLCX 49993 * MGCP 0.1MGCP Packet received in hex -44 4C 43 58 20 34 39 39 39 33 20 2A 20 4D 47 43 50 20 30 2E 31 Asend_mgcp_msg, MGCP Packet sent --->250 49993Configuration Examples
This section provides the following configuration examples:
•
•
•
•
•
•
•
Note
Cisco uBR925 Using RF Interface Example
This example shows how to set up a Cisco uBR925 as an MGCP residential gateway. The call agent is specified to the cable router (Cisco uBR925, Cisco CVA122, or Cisco CVA122E) by a Dynamic Host Configuration Protocol (DHCP) offer on a cable radio frequency (RF) network. On completion of the DHCP offer, the call agent is set in the MGCP profile on the cable modem. This setting is displayed with the show mgcp profile command. The router does not show the call agent in the CLI.
version 12.2no service single-slot-reload-enableno service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname hydepark!logging rate-limit console 10 except errors!!!clock timezone - 0 6ip subnet-zerono ip routingip domain-name example.comip name-server 10.0.0.229!ip ssh time-out 120ip ssh authentication-retries 3no ip dhcp-client network-discovery!!!!!!!interface Ethernet0ip address 192.168.0.11 255.255.0.0no ip route-cacheno ip mroute-cachebridge-group 59bridge-group 59 spanning-disabled!interface cable-modem0no ip route-cacheno ip mroute-cachecable-modem boot admin 2cable-modem boot oper 5bridge-group 59bridge-group 59 spanning-disabled!ip classlessno ip http serverno ip http cable-monitor!snmp-server manager!voice-port 0input gain -2output attenuation 0!voice-port 1input gain -2output attenuation 0!mgcp! Use this CLI with NCS 1.0mgcp endpoint offset!mgcp profile default!dial-peer voice 100 potsapplication MGCPAPPport 0!dial-peer voice 101 potsapplication MGCPAPPport 1!!line con 0line vty 0 4login!endCisco uBR925 Using Ethernet0 Interface Example
This example shows how to set up a Cisco uBR925 as a residential gateway:
version 12.2no service single-slot-reload-enableno service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname monticello!logging rate-limit console 10 except errors!!!clock timezone - 0 6ip subnet-zeroip domain-name example.comip name-server 10.0.0.229!ip ssh time-out 120ip ssh authentication-retries 3no ip dhcp-client network-discovery!!!!!interface Ethernet0ip address 192.168.0.11 255.255.0.0no ip route-cacheno ip mroute-cachebridge-group 59bridge-group 59 spanning-disabled!interface cable-modem0no ip route-cacheno ip mroute-cacheshutdowncable-modem boot admin 2cable-modem boot oper 5no cable-modem compliant bridgecable-modem voip clock-internalbridge-group 59bridge-group 59 spanning-disabled!!ip classlessno ip http serverno ip http cable-monitor!ip default-gateway 172.16.1.1!! We are using the cable modem without its RF interface. So! route IP traffic out the Ethernet0 interface.!ip route 0.0.0.0 0.0.0.0 Ethernet0!snmp-server manager!voice-port 0input gain -2output attenuation 0!voice-port 1input gain -2output attenuation 0!mgcp!! The ip address of call agent below can be a FQDN as well.mgcp call-agent 10.0.0.224 service-type ncs version 1.0! Use this CLI with NCS 1.0mgcp endpoint offset!mgcp profile default!dial-peer voice 100 potsapplication MGCPAPPport 0!dial-peer voice 101 potsapplication MGCPAPPport 1!!line con 0line vty 0 4login!endCisco CVA122 Using RF Interface Example
The call agent is specified to the cable router (Cisco uBR925, Cisco CVA122, or Cisco CVA122E) by a DHCP offer on a cable RF network. On completion of the DHCP offer, the call agent is set in the MGCP profile on the cable modem. This setting is displayed with the show mgcp profile command. The router does not show the call agent in the CLI.
version 12.2no service single-slot-reload-enableno service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryptionservice internal!hostname mtvernon!no logging bufferedlogging rate-limit console 10 except errors!!!clock timezone - -5ip subnet-zerono ip routingip domain-name example.comip name-server 10.0.0.229!no ip dhcp-client network-discovery!!!!!!!interface Ethernet0ip address 10.20.0.59 255.255.0.0no ip route-cacheno ip mroute-cacheshutdownbridge-group 59bridge-group 59 spanning-disabled!interface cable-modem0no ip route-cacheno ip mroute-cachecable-modem boot admin 2cable-modem boot oper 5bridge-group 59bridge-group 59 spanning-disabled!interface usb0ip address 10.20.0.59 255.255.0.0no ip route-cacheno ip mroute-cachearp timeout 0bridge-group 59bridge-group 59 spanning-disabled!ip classlessno ip http serverno ip http cable-monitor!access-list 1 deny 10.0.0.254access-list 1 permit anysnmp-server packetsize 4096snmp-server managercall rsvp-sync!voice-port 0input gain -2output attenuation 0timeouts interdigit 2!voice-port 1input gain -2output attenuation 0timeouts interdigit 2!mgcp!mgcp profile default!mgcp profile testcall-agent test service-type ncs version 1.0!dial-peer voice 100 potsapplication MGCPAPPport 0!dial-peer voice 101 potsapplication MGCPAPPport 1!!line con 0exec-timeout 0 0line vty 0 4exec-timeout 0 0login!endCisco 2600 as a Residential Gateway Example
This example shows a Cisco 2620 series router being configured as an analog residential gateway:
!!!version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname betty-2620!!!voice-port 1/0/0!voice-port 1/0/1!!dial-peer voice 1 potsapplication mgcpappdestination-pattern 100port 1/0/0!dial-peer voice 2 potsapplication mgcpappdestination-pattern 101port 1/0/1!!process-max-time 200!mgcp 4000mgcp call-agent 10.14.2.200 4000 service-type mgcp version 1.0mgcp sdp simpleno mgcp timer receive-rtcpmgcp sdp xpc-codecno mgcp piggyback messagemgcp endpoint offsetno mgcp persistent hook onno mgcp persistent hook flashmgcp request timeout 1000mgcp dtmf-relay codec all mode ciscomgcp max-waiting-delay 600000mgcp restart-delay 500mgcp codec g711ulaw packetization-period 10mgcp ip-tos rtp precedence 7mgcp quality-threshold lwm-jitter-buffer 59mgcp quality-threshold lwm-latency 199mgcp quality-threshold lwm-packet-loss 2mgcp playout adaptive 100 50 150mgcp package-capability dtmf-packagemgcp package-capability mf-packagemgcp package-capability rtp-packagemgcp package-capability as-packageisdn voice-call-failure 0srcp 2428cns event-service server!!!mgcp profile ciscocall-agent 10.14.2.200 4000 service-type mgcp version 1.0voice-port 0:1package persistent mt-packagetimeout tsmax 100timeout tdinit 30timeout tcrit 600timeout tpar 600timeout thist 60timeout tone mwi 600timeout tone ringback 600timeout tone ringback connection 600timeout tone network congestion 600timeout tone busy 600timeout tone dial 600timeout tone dial stutter 600timeout tone ringing 600timeout tone ringing distinctive 600timeout tone reorder 600timeout tone cot1 600timeout tone cot2 600max1 retries 10no max2 lookupmax2 retries 10!!interface Ethernet0/0ip address 10.14.12.9 255.0.0.0!interface Ethernet0/1no ip addressshutdown!ip classlessip route 0.0.0.0 0.0.0.0 10.14.0.1no cdp run!line con 0exec-timeout 0 0line aux 0line vty 0 4exec-timeout 0 0password testlogin!endCisco 3660 Platform as a Trunking Gateway Example
This example shows a Cisco 3660 that is being configured for CAS trunks. The association of endpoints with the MGCP application is made in the dial-peer configuration.
version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname charley-3660!!controller t1 1/0linecode b8zsclock source line secondary 1ds0-group 0 timeslots 1-24 type e&m-winkstart!controller t1 1/1linecode b8zsclock source line secondary 1ds0-group 0 timeslots 1-24 type e&m-winkstart!ip subnet-zero!voice-port 1/0:0dial-type mf!voice-port 1/1:0dial-type mf!dial-peer voice 1 potsapplication mgcpappdestination-pattern 100port 1/0:0!dial-peer voice 2 potsapplication mgcpappdestination-pattern 101port 1/1:0!mgcp 4000mgcp call-agent 10.14.2.200 4000 service-type mgcp version 1.0mgcp sdp simpleno mgcp timer receive-rtcpmgcp sdp xpc-codecno mgcp piggyback messagemgcp endpoint offsetmgcp persistent hook onmgcp persistent hook flashmgcp request timeout 1000mgcp dtmf-relay codec all mode ciscomgcp max-waiting-delay 600000mgcp restart-delay 500mgcp codec g711ulaw packetization-period 10mgcp ip-tos rtp precedence 7mgcp quality-threshold lwm-jitter-buffer 59mgcp quality-threshold lwm-latency 199mgcp quality-threshold lwm-packet-loss 2mgcp playout adaptive 100 50 150mgcp package-capability dtmf-packagemgcp package-capability mf-packagemgcp package-capability rtp-packagemgcp package-capability as-packageisdn voice-call-failure 0srcp 2428cns event-service server!mgcp profile ciscocall-agent 10.14.2.200 4000 service-type mgcp version 1.0voice-port 1/0:0package persistent mt-packagetimeout tsmax 100timeout tdinit 30timeout tcrit 600timeout tpar 600timeout thist 60timeout tone mwi 600timeout tone ringback 600timeout tone ringback connection 600timeout tone network congestion 600timeout tone busy 600timeout tone dial 600timeout tone dial stutter 600timeout tone ringing 600timeout tone ringing distinctive 600timeout tone reorder 600timeout tone cot1 600timeout tone cot2 600max1 retries 10no max2 lookupmax2 retries 10!!interface FastEthernet0/0ip address 10.14.12.12 255.0.0.0speed autoduplex auto!interface FastEthernet0/1no ip addressshutdownduplex autospeed auto!ip classlessip route 0.0.0.0 0.0.0.0 10.14.0.1no ip http server!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4exec-timeout 0 0password triallogin!endCisco MC3810 as a Residential Gateway Example
The following example shows a Cisco MC3810 being configured as a residential gateway:
!version 12.2no service padservice timestamps debug datetime msecservice timestamps log uptime!hostname harry!logging buffered!ip subnet-zeroip host buffalo 192.168.254.254!mgcpmgcp call-agent 10.14.90.1!voice-card 0codec complexity high!controller T1 0framing esflinecode b8zs!interface Ethernet0ip address 10.14.92.3 255.255.0.0!interface Serial0shutdown!interface Serial1no ip addressno ip route-cacheno ip mroute-cacheshutdown!interface FR-ATM20no ip addressshutdown!ip default-gateway 10.14.0.1ip route 192.168.254.0 255.255.255.0 10.14.0.1!!voice-port 1/1!dial-peer voice 1 potsapplication mgcpappport 1/1!!line con 0exec-timeout 0 0transport input noneline aux 0line 2 3line vty 0 4login!endCisco MC3810 as a VoAAL2 Gateway using AAL2 PVCs Example
This example shows a Cisco MC3810 beign configured as a VoAAL2 gateway using AAL2 PVCs:
!version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname stella-mc3810!network-clock base-rate 56kip subnet-zerono ip domain-lookupip host camel 192.168.254.254ip host buffalo 192.168.254.253!mgcpmgcp call-agent 10.14.117.4 service-type mgcp version 0.1mgcp dtmf-relay voip codec all mode nsemgcp dtmf-relay voaal2 codec allmgcp modem passthrough nsemgcp package-capability rtp-packagemgcp tse payload 100mgcp timer receive-rtcp 100mgcp timer net-cont-test 3000isdn voice-call-failure 0!!voice-card 0!controller T1 0mode atmframing esflinecode b8zs!interface Ethernet0ip address 10.14.121.1 255.255.0.0!interface Serial0no ip addressno ip mroute-cacheshutdownno fair-queue!interface Serial1no ip addressshutdown!interface ATM0no ip addressip mroute-cacheno atm ilmi-keepaliveinterface ATM0.2 point-to-pointpvc 2/200vbr-rt 760 760 100encapsulation aal2vcci 2!interface FR-ATM20no ip addressshutdown!router igrp 1redistribute connectednetwork 1.0.0.0!ip default-gateway 10.14.0.1no ip http serverip classlessip route 192.168.254.0 255.255.255.0 10.14.0.1!dialer-list 1 protocol ip permitdialer-list 1 protocol ipx permitvoice-port 1/1!voice-port 1/2shutdown!voice-port 1/6shutdown!dial-peer voice 1 potsapplication mgcpappport 1/1!!line con 0transport input noneline aux 0line 2 3line vty 0 4password lablogin!endCommand Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications or in the MGCP documentation listed in the "Related Documents" section.
New Commands
•
•
•
Modified Commands
•
•
call-agent
To define the call agent for a Media Gateway Controller Protocol (MGCP) profile, use the call-agent command in MGCP profile configuration mode. To return to the default values, use the no form of this command.
call-agent {dns-name | ip-address} [port] [service-type type] [version protocol-version]
no call-agent
Syntax Description
Defaults
The default call-agent UDP port is 2727 for MGCP 1.0, Network-based Call Signaling (NCS) 1.0, and Trunking Gateway Control Protocol (TGCP) 1.0.
The default call-agent UDP port is 2427 for MGCP 0.1 and Simple Gateway Control Protocol (SGCP).
The default service type and version is mgcp 0.1.
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
Call-agent configuration for an MGCP profile (with this command) and global call-agent configuration (with the mgcp call-agent command) are mutually exclusive; the first to be configured on an endpoint blocks configuration of the other on the same endpoint.
Identifying call agents by domain name system (DNS) name rather than IP address in the call-agent command provides call-agent redundancy, because a DNS name can have more than one IP address associated with it. If a call agent is identified by DNS name and a message from the gateway fails to reach the call agent, the max1 lookup and max2 lookup commands enable a search from the DNS lookup table for a backup call agent at a different IP address.
The port argument configures the call agent port number (the UDP port over which the gateway sends messages to the call agent). The reverse, or the gateway port number (the UDP port over which the gateway receives messages from the call agent) is configured by specifying a port number in the mgcp command.
The service type mgcp supports the RestartInProgress (RSIP) error messages sent by the gateway if mgcp sgcp restart notify is enabled. The service type sgcp ignores the RSIP messages.
Examples
The following example defines a call agent for the MGCP profile named tgcp_trunk:
Router(config)# mgcp profile tgcp_trunkRouter(config-mgcp-profile)# call-agent 10.13.93.3 2500 service-type tgcp version 1.0Related Commands
debug mgcp
To enable debug traces for MGCP errors, events, media, packets, and parser, use the debug mgcp privileged EXEC command. To disable debugging output, use the no form of this command.
debug mgcp [all | errors [endpoint endpoint-name] | events [endpoint endpoint-name] | media [endpoint endpoint-name] | packets [endpoint endpoint-name | input-hex] | parser]
no debug mgcp [all | errors | events | media | packets | parser]
Syntax Description
Defaults
Debug is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
There is always a performance penalty when using debug commands.
The endpoint keyword modifies the debug mgcp command to log only the events identified with the specified endpoints, for up to five endpoints. If you turn on debug without the endpoint option, all MGCP message traffic is displayed in the log, which can make the log very unreadable. Note that per-endpoint parser debug is not supported.
Examples
Following are sample outputs from the debug mgcp events, debug mgcp packets, and debug mgcp parser commands. The debug mgcp all command would show a compilation of the output from all these commands. The final example shows the output of the debug mgcp packet endpoint command.
The following example illustrates the output for the debug mgcp events command:
Router# debug mgcp eventsMedia Gateway Control Protocol events debugging is onRouter#1w1d: MGC stat - 172.19.184.65, total=44, succ=7, failed=211w1d: MGCP msg 11w1d: remove_old_under_specified_ack:1w1d: MGC stat - 172.19.184.65, total=44, succ=8, failed=211w1d: updating lport with 2427setup_ipsocket: laddr=172.29.248.193, lport=2427,faddr=172.19.184.65, fport=24271w1d: enqueue_ack: ackqhead=0, ackqtail=0, ackp=1DC1D38, msg=21A037CRouter#The following example illustrates the output for the debug mgcp packets command:
Router# debug mgcp packetsMedia Gateway Control Protocol packets debugging is onRouter# Media Gateway Control Protocol packets debugging is onRouter#1w1d: MGCP Packet received -DLCX 408631346 * MGCP 0.11w1d: send_mgcp_msg, MGCP Packet sent --->1w1d: 250 408631346<---The following example illustrates the output for the debug mgcp parser command:
Router# debug mgcp parserMedia Gateway Control Protocol parser debugging is onRouter#1w1d: -- mgcp_parse_packet() - call mgcp_parse_header- mgcp_parse_header()- Request Verb FOUND DLCX- mgcp_parse_packet() - out mgcp_parse_header- SUCCESS: mgcp_parse_packet()- MGCP Header parsing was OK- mgcp_val_mandatory_parms()- SUCCESS: mgcp_parse_packet()- END of Parsing1w1d: -- mgcp_build_packet()-1w1d: - mgcp_estimate_msg_buf_length() - 87 bytes needed for header- mgcp_estimate_msg_buf_length() - 87 bytes needed after checking parameter lines- mgcp_estimate_msg_buf_length() - 87 bytes needed after checking SDP lines- SUCCESS: MGCP message building OK- SUCCESS: END of buildingThe following example shows the debug output for MGCP packets on a single endpoint:
Router# debug mgcp packet endpoint aaln/s4/su0/1End point name for packet debug:aaln/s4/su0/1 (1)Router#*Mar 7 02:32:30.931:Slot = 4, Subunit = 0, Port = 1*Mar 7 02:32:30.931:Call record found*Mar 7 02:32:30.931:Enable packet end point debug for (aaln/s4/su0/1)Router# show debugMGCP:Media Gateway Control Protocol packets per end point debugging is onMGCP packet end point debug:[aaln/s4/su0/1]Router#*Mar 7 02:34:40.835:MGCP Packet received -DLCX 43364 aaln/s4/su0/1 MGCP 1.0*Mar 7 02:34:40.835:send_mgcp_msg, MGCP Packet sent --->*Mar 7 02:34:40.835:RSIP 856 aaln/s4/su0/1@3660-2 MGCP 1.0RM:disconnected.250 43364 already deleted connection<---*Mar 7 02:34:41.835:send_mgcp_msg, MGCP Packet sent --->*Mar 7 02:34:41.835:RSIP 856 aaln/s4/su0/1@3660-2 MGCP 1.0RM:disconnecteddefault (MGCP profile)
To configure an MGCP profile parameter to its default value, use the default command in MGCP profile configuration mode, or use the no form of the command for that profile parameter.
default command
Syntax Description
command
One of the MGCP profile commands. Valid choices are:
•
•
•
Defaults
This command has no default value.
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
The default (MGCP profile) command instructs the MGCP profile to use the default value of the specified command whenever the profile is called. This has the same effect as using the no form of the specified command, but the default command clearly specifies which commands are using their default values.
To use the default values for more than one command, enter each command on a separate line.
Examples
The following example shows how to configure the default values for three MGCP profile commands:
Router(config)# mgcp profile newyorkRouter(config-mgcp-profile)# default max1 retriesRouter(config-mgcp-profile)# default timeout tdinitRouter(config-mgcp-profile)# default timeout tone mwiRelated Commands
description (MGCP profile)
To provide a description of the MGCP profile that is being defined, use the description command in MGCP profile configuration mode.
description text
Syntax Description
Defaults
This command has no default value.
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
The description is printed in the output for the show mgcp profile command and others.
Examples
The following example shows a description for an MGCP profile:
Router(config)# mgcp profile newyorkRouter(config-mgcp-profile)# description This is the head sales office in New York.Related Commands
max1 lookup
To enable domain name system (DNS) lookup for a new call-agent address when the suspicion threshold value is reached, use the max1 lookup command in MGCP profile configuration mode. To disable lookup, use the no form of the command.
max1 lookup
no max1 lookup
Syntax Description
There are no keywords or arguments for this command.
Defaults
Lookup is enabled.
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
Call-agent redundancy can be provided when call agents are identified by DNS name rather than IP address in the call-agent command, because each DNS name can have more than one IP address associated with it.
When the active call agent does not respond to a message from the media gateway, the gateway becomes suspicious that the call agent is out of service. The gateway retransmits the message to the call agent for the number of times specified in the max1 retries command; this is known as the suspicion threshold. If there is no response and the max1 lookup command is enabled, the gateway examines the DNS lookup table to find the IP address of another call agent. If a second call agent is listed, the gateway retries the message to the second call agent until a response is received or the number of retries specified in the max1 retries command is reached. This process is repeated for each IP address in the DNS table until the final address is reached. For the final address, the number of retries is specified by the max2 retries command; this is known as the disconnect threshold. If the number of retries specified in the max2 retries command is reached and there is still no response and the max2 lookup command is enabled, the gateway performs one final DNS lookup. If any new IP addresses have been added, the gateway starts the retransmission process again. Otherwise, the gateway places the endpoint in a disconnected state.
Examples
The following example shows how to enable the DNS lookup procedure and set the suspicion retransmission counter value to 7:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# call-agent igloo.northpole.netRouter(config-mgcp-profile)# max1 lookupRouter(config-mgcp-profile)# max1 retries 7Related Commands
max1 retries
To set the Media Gateway Control Protocol (MGCP) suspicion threshold value, use the max1 retries command in MGCP profile configuration mode. To return the number of retries to the default, use the no form of the command.
max1 retries number
no max1 retries
Syntax Description
Defaults
The default number of attempts to resend messages is 5.
Command Modes
MGCP profile configuration
Command History
12.2(2)XA
This command was introduced. With the max2 retries command, it replaces the mgcp request retries command, which is no longer supported.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco AS5300 and Cisco AS5850 platform. The maximum number of retries was increased to 30.
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.
Usage Guidelines
This command is used when configuring values for an MGCP profile.
Call-agent redundancy can be provided when call agents are identified by domain name system (DNS) name rather than by IP address in the call-agent command, because each DNS name can have more than one IP address associated with it.
When the active call agent does not respond to a message from the media gateway, the gateway becomes suspicious that the call agent is out of service. The gateway retransmits the message to the call agent for the number of times specified in the max1 retries command; this is known as the suspicion threshold. If there is no response and the max1 lookup command is enabled, the gateway examines the DNS lookup table to find the IP address of another call agent. If a second call agent is listed, the gateway retries the message to the second call agent until a response is received or the number of retries specified in the max1 retries command is reached. This process is repeated for each IP address in the DNS table until the final address is reached. For the final address, the number of retries is specified by the max2 retries command; this is known as the disconnect threshold. If the number of retries specified in the max2 retries command is reached and there is still no response and the max2 lookup command is enabled, the gateway performs one final DNS lookup. If any new IP addresses have been added, the gateway starts the retransmission process again. Otherwise, the gateway places the endpoint in a disconnected state.
Examples
The following example shows how to enable the DNS lookup procedure and set the suspicion retransmission counter value to 7:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# call-agent igloo.northpole.netRouter(config-mgcp-profile)# max1 lookupRouter(config-mgcp-profile)# max1 retries 7Related Commands
max2 lookup
To enable domain name system (DNS) lookup for a new call-agent address after the disconnect threshold timeout value is reached, use the max2 lookup command in MGCP profile configuration mode. To disable DNS lookup, use the no form of the command.
max2 lookup
no max2 lookup
Syntax Description
There are no arguments or keywords for this command.
Defaults
Lookup is enabled.
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
Call-agent redundancy can be provided when call agents are identified by DNS name rather than IP address in the call-agent command, because each DNS name can have more than one IP address associated with it.
When the active call agent does not respond to a message from the media gateway, the gateway becomes suspicious that the call agent is out of service. The gateway retransmits the message to the call agent for the number of times specified in the max1 retries command; this is known as the suspicion threshold. If there is no response and the max1 lookup command is enabled, the gateway examines the DNS lookup table to find the IP address of another call agent. If a second call agent is listed, the gateway retries the message to the second call agent until a response is received or the number of retries specified in the max1 retries command is reached. This process is repeated for each IP address in the DNS table until the final address is reached. For the final address, the number of retries is specified by the max2 retries command; this is known as the disconnect threshold. If the number of retries specified in the max2 retries command is reached and there is still no response and the max2 lookup command is enabled, the gateway performs one final DNS lookup. If any new IP addresses have been added, the gateway starts the retransmission process again. Otherwise, the gateway places the endpoint in a disconnected state.
Examples
The following example shows how to enable the DNS lookup procedure and set the disconnect retransmission counter value to 9:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# call-agent ca1@exp.example.comRouter(config-mgcp-profile)# max2 lookupRouter(config-mgcp-profile)# max2 retries 9Related Commands
max2 retries
To set the Media Gateway Control Protocol (MGCP) disconnect threshold value, use the max2 retries command in MGCP profile configuration mode. To disable lookup or return the number of retries to the default, use the no form of the command.
max2 retries number
no max2 retries
Syntax Description
Defaults
The default number of attempts to resend messages is 7.
Command Modes
MGCP profile configuration
Command History
12.2(2)XA
This command was introduced. With the max1 retries command, it replaces the mgcp request retries command, which is no longer supported.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco AS5300 and Cisco AS5850 platform. The maximum number of retries was increased to 30.
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.
Usage Guidelines
This command is used when configuring values for an MGCP profile.
Call-agent redundancy can be provided when call agents are identified by domain name system (DNS) name rather than IP address in the call-agent command, because each DNS name can have more than one IP address associated with it.
When the active call agent does not respond to a message from the media gateway, the gateway becomes suspicious that the call agent is out of service. The gateway retransmits the message to the call agent for the number of times specified in the max1 retries command; this is known as the suspicion threshold. If there is no response and the max1 lookup command is enabled, the gateway examines the DNS lookup table to find the IP address of another call agent. If a second call agent is listed, the gateway retries the message to the second call agent until a response is received or the number of retries specified in the max1 retries command is reached. This process is repeated for each IP address in the DNS table until the final address is reached. For the final address, the number of retries is specified by the max2 retries command; this is known as the disconnect threshold. If the number of retries specified in the max2 retries command is reached and there is still no response and the max2 lookup command is enabled, the gateway performs one final DNS lookup. If any new IP addresses have been added, the gateway starts the retransmission process again. Otherwise, the gateway places the endpoint in a disconnected state.
Examples
The following example shows how to set the disconnect retransmission counter value to 9:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# call-agent igloo.northpole.netRouter(config-mgcp-profile)# max2 retries 9Related Commands
mgcp call-agent
To configure the address and protocol of the call agent for Media Gateway Control Protocol (MGCP) endpoints on a media gateway, use the mgcp call-agent global configuration command. To return to default values, use the no form of this command.
mgcp call-agent {dns-name | ip-address} [port] [service-type type] [version protocol-version]
no mgcp call-agent
Syntax Description
Defaults
The default call-agent UDP port is 2727 for MGCP 1.0, Network-based Call Signaling (NCS) 1.0, and Trunking Gateway Control Protocol (TGCP) 1.0.
The default call-agent UDP port is 2427 for MGCP 0.1 and Simple Gateway Control Protocol (SGCP).
The default service type and version is mgcp 0.1.
Command Modes
Global configuration
Command History
Usage Guidelines
Global call-agent configuration (with this command) and call-agent configuration for an MGCP profile (with the MGCP profile call-agent command) are mutually exclusive; the first to be configured on an endpoint blocks configuration of the other on the same endpoint.
Identifying call agents by domain name system (DNS) name rather than IP address in the call-agent command provides call-agent redundancy, because a DNS name can have more than one IP address associated with it. If a call agent is identified by DNS name and a message from the gateway fails to reach the call agent, the max1 lookup and max2 lookup commands enable a search from the DNS lookup table for a backup call agent at a different IP address.
The port argument configures the call-agent port number (the UDP port over which the gateway sends messages to the call agent). The reverse (the gateway port number, or the UDP port over which the gateway receives messages from the call agent) is configured by specifying a port number in the mgcp command. The default gateway port number is always 2427.
The service type mgcp supports the RestartInProgress (RSIP) error messages sent by the gateway if mgcp sgcp restart notify is enabled. The service type sgcp ignores the RSIP messages.
Examples
The following examples demonstrate various forms of the command:
Router(config)# mgcp call-agent 209.165.200.225 service-type mgcp version 1.0Router(config)# mgcp call-agent 209.165.200.225 5530 service-type tgcpRouter(config)# mgcp call-agent igloo.northpole.net service-type ncsRouter(config)# mgcp call-agent igloo.northpole.net 2009 service-type sgcp version 1.5Related Commands
mgcp endpoint offset
When using the Network-based Call Signaling (NCS) 1.0 profile of Media Gateway Control Protocol (MGCP), enable incrementing of the POTS or DS0 portion of an endpoint name with the mgcp endpoint offset global configuration command. To return the endpoint name to the default, use the no form of this command.
mgcp endpoint offset
no mgcp endpoint offset
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used with NCS 1.0 to increment the POTS or DS0 portion of an endpoint name by 1, to minimize potential interoperability problems with call agents (media gateway controllers).
NCS 1.0 mandates that the port number of an endpoint be based on 1, and port numbering on some gateway platforms is based on 0.
When this command is configured, it offsets all endpoint names on the gateway. For example, an endpoint with a port number of aaln/0 is offset to aaln/1, and a DS0 group number of 0/0:0 is offset to 0/0:1.
Examples
The following example shows the port number portion of an endpoint name being incremented:
Router(config)# mgcp endpoint offsetRelated Commands
mgcp persistent
To configure the sending of persistent events from the Media Gateway Control Protocol (MGCP) gateway to the call agent, use the mgcp persistent global configuration command. To return to the default values, use the no form of this command.
mgcp persistent {hookflash | offhook | onhook}
no mgcp persistent {hookflash | offhook | onhook}
Syntax Description
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.
Command Modes
Global configuration
Defaults
The hookflash detection option is disabled for persistence.
The offhook option is enabled for persistence.
The onhook option is disabled for persistence.
Command History
Usage Guidelines
Persistent events are those events that, once they are detected, are defined as reportable to the call agent whether or not the call agent has explicitly requested to be notified of their occurrence; that is, even if they are not included in the list of RequestedEvents that the gateway is asked to detect and report. Such events include, for example, fax tones, continuity tones, or on-hook transition; each event has an associated action for the gateway to take.
Use the mgcp persistent command for each type of persistent event that should override the default behavior.
Examples
The following example shows how to configure the gateway to send persistent on-hook events to the call agent:
Router(config)# mgcp persistent onhookRelated Commands
mgcp piggyback message
To enable piggyback messages, use the mgcp piggyback message global configuration command. To disable piggyback messages, use the no form of this command.
mgcp piggyback message
no mgcp piggyback message
Syntax Description
This command has no arguments or keywords.
Defaults
Piggyback messages are enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to disable piggyback messages for Media Gateway Control Protocol (MGCP) 1.0, Network-based Call Signaling (NCS), and Trunking Gateway Control Protocol (TGCP) when a network gateway cannot handle piggyback messages. Piggyback messaging is not available to Simple Gateway Control Protocol (SGCP) and MGCP 0.1.
The term piggyback message refers to a situation in which a gateway or a call agent sends more than one MGCP message in the same User Datagram Protocol (UDP) packets. The recipient processes the messages individually, in the order received. However, if a message must be retransmitted, the entire datagram is resent. The recipient must be capable of sorting out the messages and keeping track of which messages have been handled or acknowledged.
Piggybacking is used during retransmission of a message to send previously unacknowledged messages to the call agent. This maintains the order of events the call agent receives, and makes sure that RSIP (RestartInProgress) messages are always received first by a call agent.
Examples
The following example illustrates how to disable piggyback messages:
Router(config)# no mgcp piggyback messageRelated Commands
mgcp profile
To create and configure a Media Gateway Control Protocol (MGCP) profile to be associated with one or more MGCP endpoints or to configure the default MGCP profile, use the mgcp profile command in global configuration mode. To delete the profile, use the no form of this command.
mgcp profile {profile-name | default}
no mgcp profile {profile-name | default}
Syntax Description
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 that the default profile is to be configured.
Defaults
This command does not have a default value.
Command Modes
Global configuration
Command History
Usage Guidelines
An MGCP profile is a subset of endpoints on a media gateway. More than one MGCP profile can be configured on a gateway at the same time. The voice-port command in MGCP profile configuration mode associates endpoints with the profile.
There are two types of MGCP parameters, global and profile-related. The parameters that are configured in MGCP profile configuration mode are the profile-related parameters. However, endpoints do not need to belong to an MGCP profile. When endpoints are not associated with any MGCP profile, values for the profile-related MGCP parameters are provided by a default profile. Although all of the parameters for the default profile have default values, they also can be configured in the same way that an MGCP profile is configured, by simply using the keyword default instead of a profile name. The main difference between a default profile and a user-defined profile is that there is no voice-port or call-agent association in the default profile, but they are required in user-defined profiles. When configuring the default profile, do not configure the call-agent command or the voice-port command.
The mgcp profile command initiates MGCP profile configuration mode, in which you create an MGCP profile for an endpoint or a set of endpoints on a media gateway, and you set parameters for that profile or for the default profile. The following commands are available to configure MGCP profile-related parameters:
•
•
•
Examples
The following example illustrates an MGCP profile definition:
Router(config)# mgcp profile newyork Router(config-mgcp-profile)# call-agent 10.14.2.200 4000 service-type mgcp version 1.0Router(config-mgcp-profile)# voice-port 0:1Router(config-mgcp-profile)# package persistent mt-packageRouter(config-mgcp-profile)# timeout tsmax 100Router(config-mgcp-profile)# timeout tdinit 30Router(config-mgcp-profile)# timeout tcrit 600Router(config-mgcp-profile)# timeout tpar 600Router(config-mgcp-profile)# timeout thist 60Router(config-mgcp-profile)# timeout tone mwi 600Router(config-mgcp-profile)# timeout tone ringback 600Router(config-mgcp-profile)# timeout tone ringback connection 600Router(config-mgcp-profile)# timeout tone network congestion 600Router(config-mgcp-profile)# timeout tone busy 600Router(config-mgcp-profile)# timeout tone dial 600Router(config-mgcp-profile)# timeout tone dial stutter 600Router(config-mgcp-profile)# timeout tone ringing 600Router(config-mgcp-profile)# timeout tone ringing distinctive 600Router(config-mgcp-profile)# timeout tone reorder 600Router(config-mgcp-profile)# timeout tone cot1 600Router(config-mgcp-profile)# timeout tone cot2 600Router(config-mgcp-profile)# max1 retries 10Router(config-mgcp-profile)# no max2 lookupRouter(config-mgcp-profile)# max2 retries 10Router(config-mgcp-profile)# exitRelated Commands
mgcp quarantine mode
To configure Media Gateway Control Protocol (MGCP) event quarantine buffer handling mode, use the mgcp quarantine mode command in global configuration mode. To restore the default value, use the no form of the command.
mgcp quarantine mode {discard [loop | step] | process [loop | step] | loop | step}
no mgcp quarantine mode {discard [loop | step] | process [loop | step] | loop | step}
Syntax Description
Defaults
The default is discard and step.
Command Modes
Global configuration
Command History
Usage Guidelines
Quarantine events are defined as events that have been detected by the gateway before the arrival of the MGCP NotificationRequest command, but that have not yet been notified to the call agent. They are held in the quarantine buffer until receipt of the MGCP NotificationRequest command, when the gateway is expected to generate either one notification (step by step), or multiple notifications (loop), in response to this request (the default is exactly one), based on the configuration of mgcp quarantine mode.
This command supports backward compatibility with SGCP implementations running under the MGCP application. SGCP does not have a way to allow the call agent to control the quarantine mode. MGCP has this functionality.
When the gateway is in the notification state, the interdigit timer (Tcrit) is not started.
When the gateway receives an unsuccessful NotificationRequest, the current RequestEventList and SignalEventList are emptied. The ObservedEventList and quarantine buffer are also emptied.
Examples
The following example shows the processing of quarantined events being turned on and observed events being sent to the call agent:
Router(config)# mgcp quarantine mode processThe following example turns off processing of quarantined events:
Router(config)# no mgcp quarantine mode processThe following example sends observed events to the call agent in loop mode:
Router(config)# mgcp quarantine mode process loopRelated Commands
mgcp
Starts and allocates resources for the MGCP daemon.
Disables handling of persistent call events in the quarantine buffer.
mgcp quarantine persistent-event disable
To disable handling of persistent call events in the Media Gateway Control Protocol (MGCP) quarantine buffer, use the mgcp quarantine persistent-events disable command in global configuration mode. To restore the default value, use the no form of the command.
mgcp quarantine persistent-event disable
no mgcp quarantine persistent-event disable
Syntax Description
There are no arguments or keywords for this command.
Defaults
Persistent events are held in the events buffer.
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables the reporting of persistent events immediately to the call agent rather than holding the events in quarantine. Persistent events are events defined as reportable whether or not the call agent explicitly has requested to be notified of their occurrence. Quarantining means that the gateway observes events but does not report them to the call agent until the call agent indicates readiness to receive notifications. By default, all events, including persistent events, are quarantined when they are detected, even when the gateway is in a notification state. When the mgcp quarantine persistent-event disable command is configured, however, persistent events are reported to the call agent immediately by an MGCP Notify command.
Examples
The following example shows quarantine buffer handling of persistent events being turned off:
Router(config)# mgcp quarantine persistent-event disableRelated Commands
mgcp
Starts and allocates resources for the MGCP daemon.
Configures MGCP event quarantine buffer handling mode.
mgcp request retries
This command was added in Cisco IOS Release 12.1(1)T. Beginning in Cisco IOS Release 12.2(2)XA and Cisco IOS Release 12.2(4)T, this command no longer is supported. It has been replaced by the MGCP profile commands max1 retries and max2 retries.
mgcp request timeout
To specify how long the gateway waits for a call-agent response to a request before retransmitting the request, use the mgcp request timeout command in global configuration mode. To restore the default value, use the no form of this command.
mgcp request timeout {timeout-value | max maxtimeout-value}
no mgcp request timeout [max]
Syntax Description
Defaults
Default for timeout-value is 500 ms.
Default for maxtimeout-value is 4,000 ms.
Command Modes
Global configuration
Command History
Usage Guidelines
The request timeout value is the value used for the initial time period that a Media Gateway Control Protocol (MGCP) gateway waits for a response from the call agent before retransmitting the message. The interval doubles with each retransmission. The request timeout max value sets an upper limit on the timeout interval.
Examples
The following example shows a system being set to wait 40 milliseconds for a reply to the first request before retransmitting, and limits subsequent interval maximums to 10,000 milliseconds (10 seconds):
Router(config)# mgcp request timeout 40Router(config)# mgcp request timeout max 10000Related Commands
mgcp sdp
To specify parameters for Session Description Protocol (SDP) operation in Media Gateway Control Protocol (MGCP), use the mgcp sdp command in global configuration mode. To return to the default value, use the no form of this command.
mgcp sdp {notation undotted | simple | xpc-codec}
no mgcp sdp {notation undotted | simple | xpc-codec}
Syntax Description
Defaults
The notation undotted option is disabled by default.
The simple option is disabled by default.
The xpc-codec option is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
This command allows you to configure SDP fields to meet the requirements of your call agent.
notation undotted—The codec strings G.726-16 and G.729 are dotted notation, while G726-16 and G729 are undotted. The codec notation format is selected dynamically in the following order of preference:
1.
2.
3.
simple—When simple is enabled, the gateway does not generate the following SDP fields: o (origin and session identifier), s (session name), and t (session start time and stop time). Certain call agents require this modified SDP to send data through the network.
xpc-codec—In TGCP and NCS, a new field (X-pc-codec) has been defined in the SDP for codec negotiation. To be backward compatible with non-packet-cable SDPs, the initial generation of the X-pc-codec field is suppressed by default. However, if a received SDP contains this field, the X-pc-codec is read and generated in response, to continue with the codec negotiation.
Examples
The following example shows the simple mode being configured for SDP:
Router(config)# mgcp sdp simpleRelated Commands
package persistent
To configure the package type used when reporting persistent events for a multifrequency tone (MF) channel-associated signaling (CAS) endpoint type using a specific Media Gateway Control Protocol (MGCP) profile, use the package persistent command in MGCP profile configuration mode. To disable the persistent status, use the no form of the command.
package persistent package-name
no package persistent package-name
Syntax Description
Defaults
ms-package
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
This command is used only with MF trunks (gateway voice ports configured with the dial-type mf command in voice-port configuration mode). Because the same persistent event can be defined in different MGCP packages, you may need to configure the package persistent command to tell the gateway which package to use when reporting persistent events to the call agent for the endpoints in this MGCP profile. For example, a T1 may be configured as an MF trunk, but there is more than one MGCP package that applies to an MF trunk. An ans (call answer) event must be mapped to the appropriate package for call-agent notification. This command allows different T1s to be configured for different CAS protocols.
The MS package is used with certain private branch exchange (PBX) direct inward dial/direct outward dial (DID/DOD) trunks with wink-start or ground-start protocol, as indicated in RFC 3064 (MGCP CAS Packages).
The MT package is a subset of the MS package, and it is used with certain operator services on terminating MF trunks on trunking gateway endpoints, as described in PacketCable PSTN Gateway Call Signaling Protocol Specification (TGCP) PKT-SP-TGCP-D02-991028, December 1, 1999.
Examples
The following example shows event persistence being enabled for the MT package:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# package persistent mt-packageRelated Commands
show mgcp
To display Media Gateway Control Protocol (MGCP) configuration information, use the show mgcp command in privileged EXEC mode.
show mgcp [connection | endpoint | profile [profile-name] | statistics]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
Following are examples of the command formats and outputs for show mgcp, show mgcp connection, show mgcp statistics, show mgcp endpoint, and show mgcp profile.
Router# show mgcpMGCP Admin State ACTIVE, Oper State ACTIVE - Cause Code NONEMGCP call-agent: 172.18.195.147 2300 Initial protocol service is SGCP 1.5MGCP block-newcalls DISABLEDMGCP send RSIP for SGCP is ENABLEDMGCP quarantine mode discard/stepMGCP quarantine of persistent events is ENABLEDMGCP dtmf-relay for VoIP disabled for all codec typesMGCP dtmf-relay voaal2 codec allMGCP voip modem passthrough mode: NSE, codec: g711ulaw, redundancy: DISABLED,MGCP voaal2 modem passthrough mode: NSE, codec: g711ulawMGCP TSE payload: 100MGCP T.38 Named Signalling Event (NSE) response timer: 200MGCP Network (IP/AAL2) Continuity Test timer: 3000MGCP 'RTP stream loss' timer: 2MGCP request timeout 500MGCP maximum exponential request timeout 4000MGCP gateway port: 2427, MGCP maximum waiting delay 3000MGCP restart delay 0, MGCP vad DISABLEDMGCP xpc-codec: DISABLED, MGCP persistent hookflash: DISABLEDMGCP persistent offhook: ENABLED, MGCP persistent onhook: DISABLEDMGCP piggyback msg DISABLED, MGCP endpoint offset DISABLEDMGCP simple-sdp DISABLEDMGCP undotted-notation DISABLEDMGCP codec type g711ulaw, MGCP packetization period 20MGCP JB threshold lwm 30, MGCP JB threshold hwm 150MGCP LAT threshold lmw 150, MGCP LAT threshold hwm 300MGCP PL threshold lwm 1000, MGCP PL threshold hwm 10000MGCP CL threshold lwm 1000, MGCP CL threshold hwm 10000MGCP playout mode is adaptive 60, 4, 200 in msecMGCP IP ToS low delay disabled, MGCP IP ToS high throughput disabledMGCP IP ToS high reliability disabled, MGCP IP ToS low cost disabledMGCP IP RTP precedence 5, MGCP signaling precedence: 3MGCP default package: line-packageMGCP supported packages: gm-package dtmf-package trunk-package line-packagehs-package atm-package ms-package dt-package res-packamt-package
The following example shows the output for VoIP connections:
Router# show mgcp connectionEndpoint Call_ID(C) Conn_ID(I) (P)ort (M)ode (S)tate (C)odec (E)vent[SIFL] (R)esult[EA]1. S0/DS1-0/1 C=103,23,24 I=0x8 P=16586,16634 M=3 S=4,4 C=5 E=2,0,0,2 R=0,02. S0/DS1-0/2 C=103,25,26 I=0x9 P=16634,16586 M=3 S=4,4 C=5 E=0,0,0,0 R=0,03. S0/DS1-0/3 C=101,15,16 I=0x4 P=16506,16544 M=3 S=4,4 C=5 E=2,0,0,2 R=0,04. S0/DS1-0/4 C=101,17,18 I=0x5 P=16544,16506 M=3 S=4,4 C=5 E=0,0,0,0 R=0,05. S0/DS1-0/5 C=102,19,20 I=0,6 P=16572,16600 M=3 S=4,4 C=5 E=2,0,0,2 R=0,06. S0/DS1-0/6 C=102,21,22 I=0x7 P=16600,16572 M=3 S=4,4 C=5 E=0,0,0,0 R=0,0Total number of active calls 6
The following example shows output for VoAAL2 connections:
Router# show mgcp connectionEndpoint Call_ID(C) Conn_ID(I)(V)cci/cid (M)ode (S)tate (C)odec (E)vent[SIFL] (R)esult[EA]1.aaln/S1/1 C=1,11,12 I=0x2 V=2/10 M=3 S=4,4 C=1 E=3,0,0,3 R=0,0Total number of active calls 1
The following example shows output for VoIP and VoAAL2 statistics:
Router# show mgcp statisticsUDP pkts rx 8, tx 9Unrecognized rx pkts 0, MGCP message parsing errors 0Duplicate MGCP ack tx 0, Invalid versions count 0CreateConn rx 4, successful 0, failed 0DeleteConn rx 2, successful 2, failed 0ModifyConn rx 4, successful 4, failed 0DeleteConn tx 0, successful 0, failed 0NotifyRequest rx 0, successful 4, failed 0AuditConnection rx 0, successful 0, failed 0AuditEndpoint rx 0, successful 0, failed 0RestartInProgress tx 1, successful 1, failed 0Notify tx 0, successful 0, failed 0ACK tx 8, NACK tx 0ACK rx 0, NACK rx 0IP address based Call Agents statistics:IP address 10.24.167.3, Total msg rx 8, successful 8, failed 0
The following example shows how endpoints are configured:
Router# show mgcp endpointENDPOINT-NAME V-PORT SIG-TYPE ADMINds1-0/1@nytnk116 0:1 fxs-gs upds1-0/2@nytnk116 0:1 fxs-gs upds1-0/3@nytnk116 0:1 fxs-gs upds1-0/4@nytnk116 0:1 fxs-gs upds1-0/5@nytnk116 0:1 fxs-gs upds1-0/6@nytnk116 0:1 fxs-gs upds1-0/7@nytnk116 0:1 fxs-gs upds1-0/8@nytnk116 0:1 fxs-gs upds1-0/9@nytnk116 0:1 fxs-gs upds1-0/10@nytnk116 0:1 fxs-gs upds1-0/11@nytnk116 0:1 fxs-gs upds1-0/12@nytnk116 0:1 fxs-gs upds1-0/13@nytnk116 0:1 fxs-gs upds1-0/14@nytnk116 0:1 fxs-gs upds1-0/15@nytnk116 0:1 fxs-gs upds1-0/16@nytnk116 0:1 fxs-gs upds1-0/17@nytnk116 0:1 fxs-gs upds1-0/18@nytnk116 0:1 fxs-gs upds1-0/19@nytnk116 0:1 fxs-gs upds1-0/20@nytnk116 0:1 fxs-gs upds1-0/21@nytnk116 0:1 fxs-gs upds1-0/22@nytnk116 0:1 fxs-gs upds1-0/23@nytnk116 0:1 fxs-gs upds1-0/24@nytnk116 0:1 fxs-gs upInterface T1 1ENDPOINT-NAME V-PORT SIG-TYPE ADMINds1-1/1@nytnk116 1:1 e&m-imd upds1-1/2@nytnk116 1:1 e&m-imd upThe following example displays show mgcp profile output for the default profile:
Router# show mgcp profileMGCP Profile defaultDescription:NoneCall-agent:none Initial protocol service is unknownTsmax timeout is 20, Tdinit timeout is 15Tdmin timeout is 15, Tdmax timeout is 600Tcrit timeout is 4, Tpar timeout is 16Thist timeout is 30, MWI timeout is 16Ringback tone timeout is 180, Ringback tone on connection timeout is 180Network congestion tone timeout is 180, Busy tone timeout is 30Dial tone timeout is 16, Stutter dial tone timeout is 16Ringing tone timeout is 180, Distinctive ringing tone timeout is 180Continuity1 tone timeout is 3, Continuity2 tone timeout is 3Reorder tone timeout is 30, Persistent package is ms-packageMax1 DNS lookup:ENABLED, Max1 retries is 4Max2 DNS lookup:ENABLED, Max2 retries is 4MGCP Profile houstonDescription:NoneCall-agent:10.9.57.6 5003 Initial protocol service is MGCP 1.0Tsmax timeout is 20, Tdinit timeout is 15Tdmin timeout is 15, Tdmax timeout is 600Tcrit timeout is 4, Tpar timeout is 16Thist timeout is 30, MWI timeout is 16Ringback tone timeout is 180, Ringback tone on connection timeout is 180Network congestion tone timeout is 180, Busy tone timeout is 30Dial tone timeout is 16, Stutter dial tone timeout is 16Ringing tone timeout is 180, Distinctive ringing tone timeout is 180Continuity1 tone timeout is 3, Continuity2 tone timeout is 3Reorder tone timeout is 30, Persistent package is ms-packageMax1 DNS lookup:ENABLED, Max1 retries is 4Max2 DNS lookup:ENABLED, Max2 retries is 6Voice port:1
Related Commands
timeout tcrit
To configure the critical timeout value, T(critical), for the interdigit timer used in digit map matching, use the timeout tcrit command in MGCP profile configuration mode. To set the value to the default, use the no form of this command.
timeout tcrit tcrit-value
no timeout tcrit tcrit-value
Syntax Description
Defaults
4 seconds
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
The interdigit timer is used when matching a digit map, which is a representation of the number and type of digits that a gateway can expect to collect in a buffer, based on the network dial plan. The interdigit timer is started when the first digit is entered, and is restarted after each new digit is entered, until a digit map match or mismatch occurs.
The interdigit timer takes on one of two values, T(partial) or T(critical). When at least one more digit is required to make a match to any of the patterns in the digit map, the value of T(partial) is used for the timer. If a timer is all that is required to produce a match according to the digit map, T(critical) is used for the timer.
When the interdigit timer is used without a digit map, it takes on the value T(critical). It is started immediately and is simply cancelled (but not restarted) as soon as a digit is entered.
Examples
The following example shows how to set the T(critical) value to 15 seconds:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# timeout tcrit 15Related Commands
timeout tdinit
To configure the initial waiting delay value (Tdinit) for the disconnected procedure, use the timeout tdinit command in MGCP profile configuration mode. To set the value to the default, use the no form of this command.
timeout tdinit tdinit-value
no timeout tdinit tdinit-value
Syntax Description
Defaults
15 seconds
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
When a gateway recognizes that an endpoint has lost its communication with the call agent (has become disconnected), a timer known as the disconnected timer is initialized to a random value between 0 and the disconnected initial waiting delay (Tdinit), which is configured with timeout tdinit. The gateway then waits for one of three things: the end of this timer, the reception of a command from the call agent, or the detection of local user activity for the endpoint, such as an off-hook transition. When one of the first two cases occurs, the gateway initiates the disconnected procedure for that endpoint. In the third case, the detection of local user activity, a minimum waiting delay (Tdmin) also must have elapsed. This value is configured with timeout tdmin.
The disconnected procedure consists of the endpoint sending an RestartInProgress (RSIP) message to the call agent, stating that it was disconnected and is now trying to reestablish connectivity.
If the disconnected procedure is unsuccessful and the endpoint is still disconnected, the disconnected timer is doubled; this is repeated until the timer value reaches the maximum waiting delay (Tdmax), which is configured with timeout tdmax.
Examples
The following example shows how to set the initial waiting delay value to 25 seconds:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# timeout tdinit 25Related Commands
timeout tdmax
To configure the maximum timeout value for the disconnected procedure (Tdmax), use the timeout tdmax command in MGCP profile configuration mode. To set the value to the default, use the no form of this command.
timeout tdmax tdmax-value
no timeout tdmax tdmax-value
Syntax Description
tdmax-value
Specifies the maximum timeout value for the disconnected procedure (Tdmax), in seconds. Range is 300 to 600.
Defaults
600 seconds
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
When a gateway recognizes that an endpoint has lost its communication with the call agent (has become disconnected), a timer known as the disconnected timer is initialized to a random value between 0 and the disconnected initial waiting delay (Tdinit), which is configured with the timeout tdinit command. The gateway then waits for one of three things: the end of this timer, the reception of a command from the call agent, or the detection of local user activity for the endpoint, such as an off-hook transition. When one of the first two cases occurs, the gateway initiates the disconnected procedure for that endpoint. In the third case, the detection of local user activity, a minimum waiting delay (Tdmin) also must have elapsed. This value is configured with the timeout tdmin command.
The disconnected procedure consists of the endpoint sending an RSIP message to the call agent, stating that it was disconnected and is now trying to reestablish connectivity.
If the disconnected procedure is unsuccessful and the endpoint is still disconnected, the disconnected timer is doubled; this is repeated until the timer value reaches the maximum waiting delay (Tdmax), which is configured with the timeout tdmax command.
Examples
The following example shows the maximum timeout value (Tdmax) being set to 450 seconds:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# timeout tdmax 450Related Commands
timeout tdmin
To configure the minimum timeout value for the disconnected procedure (Tdmin), use the timeout tdmin command in MGCP profile configuration mode. To set the value to the default, use the no form of this command.
timeout tdmin tdmin-value
no timeout tdmin tdmin-value
Syntax Description
tdmin-value
Specifies the minimum timeout value for the disconnected procedure (Tdmin), in seconds. Range is 1 to 30.
Defaults
15 seconds
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
When a gateway recognizes that an endpoint has lost its communication with the call agent (has become disconnected), a timer known as the disconnected timer is initialized to a random value between 0 and the disconnected initial waiting delay (Tdinit), which is configured with the timeout tdinit command. The gateway then waits for one of three things: the end of this timer, the reception of a command from the call agent, or the detection of local user activity for the endpoint, such as an off-hook transition. When one of the first two cases occurs, the gateway initiates the disconnected procedure for that endpoint. In the third case, the detection of local user activity, a minimum waiting delay (Tdmin) also must have elapsed. This value is configured with the timeout tdmin command.
The disconnected procedure consists of the endpoint sending an RSIP message to the call agent, stating that it was disconnected and is now trying to reestablish connectivity.
If the disconnected procedure is unsuccessful and the endpoint is still disconnected, the disconnected timer is doubled; the process is repeated until the timer value reaches the maximum waiting delay (Tdmax), which is configured with the timeout tdmax command.
Examples
The following example shows how to set the minimum timeout value (Tdmin) to 20 seconds:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# timeout tdmin 20Related Commands
timeout thist
To configure the packet storage timeout value (Thist), use the timeout thist command in MGCP profile configuration mode. To set the value to the default, use the no form of this command.
timeout thist thist-value
no timeout thist thist-value
Syntax Description
Defaults
30 seconds
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
MGCP messages are carried over User Datagram Protocol (UDP), and are therefore subject to packet loss. When a response to a message is not received promptly, the sender retransmits the message. The gateway keeps in memory a list of the responses it has sent for the number of seconds in the Thist timeout value. The gateway also keeps a list of the messages currently being processed, with their transaction identifiers, to prevent processing or acknowledging the same message more than once.
Examples
The following example shows how to set the packet storage timeout value (Thist) to 15 seconds:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# timeout thist 15Related Commands
timeout tone busy
To configure the busy tone timeout value, use the timeout tone busy command in MGCP profile configuration mode. To set the value to the default, use the no form of this command.
timeout tone busy busytone-value
no timeout tone busy busytone-value
Syntax Description
Defaults
30 seconds
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
The gateway uses the busy tone timeout value when the call agent does not provide a timeout value associated with the request to generate a busy tone signal.
Examples
The following example shows how to set the busy tone timeout value to 45 seconds:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# timeout tone busy 45Related Commands
timeout tone cot1
To configure the continuity1 (cot1) tone timeout value, use the timeout tone cot1 command in MGCP profile configuration mode. To set the value to the default, use the no form of this command.
timeout tone cot1 cot1tone-value
no timeout tone cot1 cot1tone-value
Syntax Description
cot1tone-value
Specifies the continuity1 tone (cot1) tone timeout value, in seconds. Range is from 1 to 600.
Defaults
3 seconds
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
The gateway uses the continuity1 (cot1) tone timeout value when the call agent does not provide a timeout value associated with the request to generate a cot1 tone signal.
Continuity1 and continuity2 tone signals are used in Integrated Services Digital Networks User Part (ISUP) calls to determine that a call path has been established before connecting a call. The call agent is provisioned to know which test to apply to a given endpoint.
Examples
The following example shows how to set the continuity1 tone timeout value to 25 seconds:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# timeout tone cot1 25Related Commands
timeout tone cot2
To configure the continuity 2 (cot2) tone timeout value, use the timeout tone cot2 command in MGCP profile configuration mode. To set the value to the default, use the no form of this command.
timeout tone cot2 cot2tone-value
no timeout tone cot2 cot2tone-value
Syntax Description
cot2tone-value
Specifies the continuity2 (cot2) tone timeout value, in seconds. Range is from 1 to 600.
Defaults
3 seconds
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
The gateway uses the continuity2 (cot2) tone timeout value when the call agent does not provide a timeout value associated with the request to generate a cot2 tone signal.
Continuity1 and continuity2 tone signals are used in Integrated Services Digital Networks User Part (ISUP) calls to determine that a call path has been established before connecting a call. The call agent is provisioned to know which test to apply to a given endpoint.
Examples
The following example shows the continuity2 tone timeout value being set to 50 seconds:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# timeout tone cot2 50Related Commands
timeout tone dial
To configure the dial tone timeout value, use the timeout tone dial command in MGCP profile configuration mode. To set the value to the default, use the no form of this command.
timeout tone dial dialtone-value
no timeout tone dial dialtone-value
Syntax Description
Defaults
16 seconds
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
The gateway uses the dial tone timeout value when the call agent does not provide timeout values associated with the request to generate a dial tone signal.
Examples
The following example shows the dial tone timeout value being set to 25 seconds:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# timeout tone dial 25Related Commands
timeout tone dial stutter
To configure the stutter dial tone timeout value, use the timeout tone dial stutter command in MGCP profile configuration mode. To set the value to the default, use the no form of this command.
timeout tone dial stutter stutter-value
no timeout tone dial stutter stutter-value
Syntax Description
stutter-value
Specifies the timeout value for the stutter dial tone, in seconds. Range is from 1 to 600.
Defaults
16 seconds
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
The gateway uses the stutter dial tone timeout value when the call agent does not provide a timeout value associated with the request to generate a stutter dial tone signal.
Examples
The following example shows the stutter dial tone timeout value being set to 25 seconds:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# timeout tone dial stutter 25Related Commands
timeout tone mwi
To configure the timeout value for the message waiting indicator tone, use the timeout tone mwi command in MGCP profile configuration mode. To return to the default value, use the no form of this command.
timeout tone mwi mwitone-value
no timeout tone mwi mwitone-value
Syntax Description
Guest
