Table Of Contents
Using Media Gateway Control Protocol with the Cisco ICS 7750
MGCP Overview
Gateway Types
ISDN PRI Backhaul
Multicast Music-on-Hold
Configuring MGCP on an MRP or ASI Card
Connecting to an MRP or ASI Card
Connect to the System Alarm Processor Card
Telnet to a System Card
MGCP Configuration Commands
Configuring a TGW
Configuring an RGW
Configuring a System Card to Use MGCP with Cisco CallManager
Configuring Download of MGCP Voice Gateway Configuration Information from Cisco CallManager
Configuring MGCP T1 CAS
Configuring ISDN Signaling Backhaul
Blocking New Calls and Gracefully Terminating Existing Calls
Configuring Fax over MGCP
Enabling Multicast Music-on-Hold
Sample Configuration
Sample MRP Configuration
Sample Cisco CallManager Configuration
Creating an MGCP Gateway
Configuring FXO Ports
Configuring FXS Ports
Testing the Phones for Local Connectivity
Configuring a Route Pattern
Testing Calls over the PSTN
Verifying and Troubleshooting the MGCP Gateway
show and debug Commands to Verify the Configuration
show mgcp
show mgcp endpoint
show mgcp connection
show voice port slot_num/port_num
show mgcp statistics
show ccm-manager
debug mgcp [all | error | events | packets | parser]
Shutting Down and Enabling the Voice Ports
Caveats
Related Documentation
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Cisco TAC Web Site
Cisco TAC Escalation Center
Using Media Gateway Control Protocol with the Cisco ICS 7750
This document explains how to use Media Gateway Control Protocol (MGCP) with the Cisco Integrated Communications System 7750 (ICS 7750). This document contains the following sections:
•
MGCP Overview
•Configuring MGCP on an MRP or ASI Card
•Sample Configuration
•Verifying and Troubleshooting the MGCP Gateway
•Related Documentation
•Obtaining Documentation
•Obtaining Technical Assistance
MGCP Overview
MGCP enables the remote control and management of voice and data communications devices at the edge of multiservice IP packet networks.
As a communication protocol, MGCP overcomes the distributed configuration and administration problems inherent in the use of protocols such as the H.323 standard. Using a centralized architecture, MGCP greatly simplifies the configuration and administration of voice gateways that operate in multiservice IP packet networks.
In addition, MGCP supports the presence of multiple (redundant) call agents in a Voice over IP (VoIP) network, thereby eliminating the potential for a single point of failure in controlling the MGCP gateways in the network.
In effect, MGCP functions as a master/slave protocol to ensure that the MGCP voice gateways in a VoIP network properly receive and execute the configuration, control, and management commands that are issued to the gateways by Cisco CallManager.
MGCP is an extension of the earlier version of the protocol Simple Gateway Control Protocol (SGCP). MGCP supports SGCP functionality and provides several enhancements. Systems using SGCP can easily migrate to MGCP, and MGCP commands are available to enable the SGCP capabilities.
An MGCP gateway handles the translation between audio signals and the packet network. The gateways interact with a call agent (CA), also called a Media Gateway Controller (MGC), that performs signal and call processing on gateway calls. In MGCP configurations on the Cisco ICS 7750, the Cisco ICS 7750 acts as the gateway, and the CA is a Cisco CallManager server (version 3.1.2c or above).
MGCP uses endpoints and connections to construct a call. Endpoints are sources of or destinations for data. Endpoints can be either physical or logical locations in a device. Connections can be point-to-point or multipoint.
Like SGCP, MGCP uses User Datagram Protocol (UDP) for establishing audio connections over IP networks. However, MGCP also uses hairpinning to return a call to the Public Switched Telephone Network (PSTN) when the IP network is not available.
Creating a call connection involves a series of signals and events that describe the connection process. This information might include such indicators as the off-hook status, a ringing signal, or a signal to play an announcement. These events and signals are specific to the type of endpoint involved in the call.
MGCP groups these events and signals into packages. A trunk package, for example, is a group of events and signals relevant to a trunking gateway, whereas an announcement package groups events and signals for an announcement server. MGCP supports seven package types, as follows:
•Trunk
•Line
•Dual tone multifrequency (DTMF)
•Generic media
•Real-Time Transport Protocol (RTP)
•Announcement server
•Script
The trunk package and line package are supported by default on certain types of gateways. Although configuring a gateway with additional endpoint package information is optional, you may want to specify the packages for your endpoints to add to or to override the defaults.
MGCP provides the following benefits:
•Alternative dial plan for VoIP environments—MGCP enables centralized call control in VoIP networks.
•Configuration requirements removed for static VoIP network dial peers—When MGCP is used as the call agent in a VoIP environment, configuring of static VoIP network dial peers is not required, so the configuration is simplified. The MGCP call agent provides functions similar to those of VoIP network dial peers.
Note POTS dial peer configuration is still required.
•Migration paths—Systems using earlier versions of the protocol can migrate easily to MGCP.
•Support for multiple protocols and protection of investment—Cisco IOS Release 12.2(4)XT3 for the Cisco ICS 7750 supports concurrently the MGCP Version 0.1 and H.323 protocols. The Cisco ICS 7750 can use either of these popular protocols.
Gateway Types
MGCP on the Cisco ICS 7750 supports the following MGCP gateway types:
•Residential Gateway (RGW)—A residential gateway (RGW) provides an interface between analog (RJ-11) calls from a telephone and the VoIP network. RGW functionality supports analog plain old telephone service (POTS) calls for both SGCP and MGCP.
•Trunking Gateway (TGW)—A trunking gateway (TGW) provides an interface between trunks on the public switched telephone network (PSTN) and a VoIP network. A trunk can be a DS0, T1, or E1 line.
ISDN PRI Backhaul
ISDN PRI backhaul provides a method for transporting complete IP telephony signaling information from an ISDN PRI interface of a multiservice route processor (MRP) or analog station interface (ASI) system card to Cisco CallManager through a highly reliable TCP connection.
This feature works by terminating all the ISDN PRI Layer 2 (Q.921) signaling functions in the Cisco IOS code on the MGCP voice gateway while, at the same time, packaging all the ISDN PRI Layer 3 (Q.931) signaling information into packets for transmission to the Cisco CallManager through an IP tunnel over a highly reliable TCP connection. This methodology ensures the integrity of the Q.931 signaling information being passed through the network for managing IP telephony devices.
A rich set of user-side and network-side ISDN PRI calling functions is supported by the ISDN PRI backhaul feature. The gateway uses a single TCP connection for backhauling all the ISDN D channels to Cisco CallManager. The "SAP/Channel ID" parameter in the header of each message identifies individual D channels. In addition to carrying the backhaul traffic, the inherent TCP keepalive mechanism is also used to determine MGCP voice gateway connectivity to an available call agent.
The MGCP voice gateway also establishes a TCP link to the backup (secondary) Cisco CallManager server. In the event of Cisco CallManager switchover, the ISDN PRI backhaul functions are assumed by the secondary Cisco CallManager server. During this switchover, all active ISDN PRI calls are preserved, and the affected MGCP gateway is registered with the new Cisco CallManager server through a Restart-in-Progress (RSIP) message to ensure continued gateway operation.
Multicast Music-on-Hold
The multicast music-on-hold (MOH) feature enables you to subscribe to a music-streaming service when using an MRP or ASI system card as a Cisco IOS MGCP voice gateway. By means of a preconfigured multicast address on a gateway, the gateway can "listen for" Real-Time Transport Protocol (RTP) packets that are broadcast from a default router in the network; the gateway can relay the packets to designated voice interfaces in the network.
RTP is the Internet-standard protocol for transporting real-time data, including audio and video information, across a network. Thus, RTP is well suited for media on demand and for interactive services such as IP telephony.
The default router in the network for handling MOH functions must have the following enabled:
•Multicast routing
•A multicast routing protocol; for example, Protocol Independent Multicast (PIM) or Distance Vector Multicast Routing Protocol (DVMRP)
•An IP routing protocol; for example, Routing Information Protocol (RIP) or Open Shortest Path First (OSPF)
When you configure a multicast address on a voice interface of a gateway, the gateway sends an Internet Gateway Management Protocol (IGMP) "join" message to the default router, indicating to the default router that the gateway is to receive RTP multicast packets.
Thus, the MOH feature provides the functionality to stream music from an MOH server to the voice interfaces of on-net and off-net callers that have been placed on hold.
The integrated multicast capability of Cisco CallManager 3.1 is implemented through the H.323 signaling plane in Cisco CallManager.
In an MOH environment, whenever caller A places caller B on hold, Cisco CallManager requests the MOH server to stream RTP packets to the "on-hold" interface through the preconfigured multicast address. In this way, RTP packets can be relayed to appropriately configured voice interfaces in a VoIP network that have been placed on hold.
Multiple MOH servers can be present in the same network, but each server must have a different Class D IP address, and the address must be preconfigured in Cisco CallManager and the Cisco IOS MGCP voice gateways.
Configuring MGCP on an MRP or ASI Card
This section describes how to configure MGCP on an MRP or ASI card. The section addresses the following topics:
•Connecting to an MRP or ASI Card
•MGCP Configuration Commands
Connecting to an MRP or ASI Card
Before entering Cisco IOS commands on an MRP or ASI card, you must connect to it, using one of the following two methods:
•Connect to the System Alarm Processor Card
•Telnet to a System Card
Connect to the System Alarm Processor Card
To connect to the MRP via the system alarm processor (SAP), perform the following steps:
Step 1 If your PC is not already directly connected to the SAP card console port, connect the SAP card console port to an available COM port on your PC.
Step 2 On your PC, open a terminal emulation application (such as HyperTerminal). On PCs running Windows 2000, a typical HyperTerminal path is Start > Programs > Accessories > Communications > HyperTerminal.
Step 3 Choose File > New Connection.
Step 4 In the Connection Description dialog box, enter a name for the connection in the Name field, and select an icon to be associated with the connection.
Step 5 Click OK.
Step 6 In the Phone Number dialog box, click the drop-down arrow to view a list of choices for the Connect Using field. Choose the PC COM port that is connected to the SAP card.
Step 7 Click OK.
Step 8 In the Properties dialog box, click the drop-down arrow to view a list of choices for the Bits per Second field, and choose 9600.
Step 9 Click OK.
A terminal window opens.
Step 10 Press Ctrl-backslash (\).
A menu similar to the following is displayed:
A. System Alarm Processor
B. System Processing Engine
C. System Switch Processor
1. Slot 1: Multiservice Route Processor
2. Slot 2: Multiservice Route Processor
5. Slot 5:System Processing Engine
6. Slot 6:System Processing Engine
Make a selection to switch:
Step 11 Enter the number corresponding to the MRP or ASI that you want to access, and press Enter.
Step 12 You are now connected to the card you selected. Press Enter again to display the prompt.
Telnet to a System Card
If you know the IP address of an MRP or ASI card, you can open a Telnet session to access that system card. Follow these steps:
Step 1 Choose Start > Run.
Step 2 To open a Telnet session, enter the following command, where IP address is the IP address of the system card you want to access:
Step 3 Enter your login password.
MGCP Configuration Commands
To configure MGCP on a Cisco ICS 7750 MRP, perform the tasks in the following sections.
•Depending on the type of gateway (TGW or RGW) that you want to configure, perform one of the following tasks:
–Configuring a TGW
–Configuring an RGW
Note You can configure the Cisco ICS 7750 MRP as both a TGW and an RGW.
•You must also complete the following task:
–Configuring a System Card to Use MGCP with Cisco CallManager
•In addition, you may want to perform any of the following optional tasks:
–Configuring Download of MGCP Voice Gateway Configuration Information from Cisco CallManager
–Configuring MGCP T1 CAS
–Configuring ISDN Signaling Backhaul
–Blocking New Calls and Gracefully Terminating Existing Calls
–Configuring Fax over MGCP
–Enabling Multicast Music-on-Hold
Note Before configuring MGCP, you need to have previously run the ICSConfig initial configuration program on the Cisco ICS 7750, you need to have configured IP routing, and you need to have configured the voice ports on the MRP or ASI card. For information about ICSConfig, refer to the Cisco ICS 7750 Getting Started Guide. For information about configuring IP routing and voice ports on the MRP and ASI cards, refer to the Cisco ICS 7750 Software Configuration Guide.
Configuring a TGW
To configure a TGW, use the following commands, beginning in global configuration mode.
| |
Command
|
Purpose
|
Step 1
|
Router(config)# mgcp
|
Initiates the MGCP application.
|
Step 2
|
Router(config)# mgcp call-agent
[ipaddr|hostname] [port] service-type mgcp
|
Specifies the call agent's IP address or domain name, the port, and the gateway control service type. The keywords and arguments are as follows:
•ipaddr—Specifies the call agent's IP address.
•hostname—Specifies the call agent's host name, using the format host.domain.ext.
•port—Specifies the port for the call agent to use. Valid values are from 1025 through 65535.
•service-type—Specifies the type of gateway control service supported by the call agent. Valid values are mgcp and sgcp. For MGCP configurations, use mgcp.
|
Step 3
|
Router(config)# controller t1 number
|
Specifies the channel number of the T1 trunk to be used for digital calls.
|
Step 4
|
Router(config-controller)# ds0-group
ds0-group-no timeslots timeslot-list type
{e&m-delay-start | e&m-wink-start}
|
Specifies the DS0 time slots that make up a logical voice port on a T1 controller and specifies the signaling type.
The arguments and keywords are as follows:
•ds0-group-no—Specifies a value from 0 to 23 that identifies the DS0 group.
•timeslots timeslot-list—Specifies a single time-slot number, a single range of numbers, or multiple ranges of numbers separated by commas. For T1 signaling, allowable values are from 1 to 24. Examples are as follows:
–2
–1-15,17-24
–1-23
–2,4,6-12
•type
–e&m-delay-start—The originating endpoint sends an off-hook signal and then waits for an off-hook signal followed by an on-hook signal from the destination.
–e&m-wink-start—E&M Mercury Exchange Limited Channel Associated Signaling (MEL CAS) wink-start signaling support.
|
Step 5
|
Router(config-controller)# exit
|
Returns to global configuration mode.
|
Step 6
|
Router(config)# dial-peer voice tag {pots}
|
Enters dial-peer configuration mode and specifies a dial peer.
|
Step 7
|
Router(config-dial-peer)# application mgcpapp
|
Enables a specific application (in this case, MGCP) on a dial peer.
|
Step 8
|
Router(config-dial-peer)# port sub-unit/port
|
Selects the voice port used for the dial peer. The keywords are as follows:
•sub-unit—Specifies the sub-unit number of the voice port. Valid values are as follows:
–MRP or ASI81: 0 or 1.
–ASI160: 0.
•port—Specifies the port number. Valid values are:
–MRP or ASI81 in slot 1: 0 or 1.
–ASI81 in slot 0: 0 through 7.
–ASI160: 0 through 15.
|
Step 9
|
Router(config-controller)# exit
|
Exits controller configuration mode and returns to global configuration mode.
|
Step 10
|
Router(config)# mgcp restart-delay value
|
(Optional) Specifies the delay value sent in the RSIP graceful teardown method. The value range is from 0 to 600 seconds; the default is 0.
|
Step 11
|
Router(config)# mgcp package-capability
{s-package | dtmf-package | gm-package |
rtp-package | trunk-package}
|
(Optional) Specifies the event packages that are supported on the gateway. The set of supported packages varies with the type of gateway (TGW or RGW). The keywords are as follows:
•as-package—Specifies the announcement server package.
•dtmf-package—Specifies the DTMF package.
•gm-package—Specifies the generic media package.
•rtp-package—Specifies the RTP package.
•trunk-package (default)—Specifies the trunk package.
|
Step 12
|
Router(config)# mgcp default-package
{as-package | dtmf-package | gm-package |
rtp-package | trunk-package}
|
(Optional) Specifies the event package that should act as the default. Overrides the mgcp package-capability default package.
|
Step 13
|
Router(config)# mgcp dtmf-relay voip codec
{all | low-bit-rate} mode {cisco | nse |
out-of-band}
|
Selects the codec type and enables dual-tone multi-frequency (DTMF) relay.
voip—(required) Specifies Voice over IP calls.
codec—Specifies use of either a G.711 codec or a G.726 codec.
all—Specifies use of any codec.
low-bit-rate—Specifies any version of the G.729 low-bit-rate codecs.
cisco—Removes DTMF tone from the voice stream and sends FRF.11 with a special payload 121 for DTMF digits.
nse—Uses the NSE-based forwarding method.
out-of-band—Removes DTMF tone from the voice stream and does not send FRF.11.
|
Step 14
|
Router(config)# mgcp sdp simple
|
(Optional) Specifies use of a subset of the Session Definition Protocol (SDP). Cisco CallManager version 3.1.2c requires this subset to send data through the network. This command is optional for Cisco CallManager version 3.1.3a or later. The default is no mgcp sdp simple.
|
Step 15
|
Router(config)# mgcp fax t38 inhibit
|
(Optional) Prevents the MRP or ASI from sending T.38 fax gateway information to the CallManager. This command is required for operation with Cisco CallManager version 3.1.2c, but is optional for version 3.1.3a and later.
|
Step 16
|
Router(config)# no mgcp timer receive-rtcp
|
(Optional) Prevents a timeout, which results in the disconnecting of a call, from occurring after a 30-second period of silence in one direction of the call. (This can happen during long voice mail message calls, for example.)
|
Configuring an RGW
To configure an RGW, use the following commands, beginning in global configuration mode.
| |
Command
|
Purpose
|
Step 1
|
MRP(config)# mgcp
|
Initiates the MGCP application.
|
Step 2
|
MRP(config)# mgcp call-agent [ipaddr | hostname]
[port] [service-type mgcp] [version protocol-version]
|
Specifies the call agent IP address or domain name, the port, and the gateway control service type. The keywords and arguments are as follows:
•ipaddr—Specifies the call agent's IP address.
•hostname—Specifies the call agent's host name, using the format host.domain.ext.
•port—(Optional) Specifies the port for the call agent to use. Valid values are from 1025 through 65535. If no port number is specified, the default port number of 2427 is used for MGCP version 0.1, and port number 2727 is used for MGCP version 1.0.
•service-type—(Optional) Specifies the type of gateway control service supported by the call agent. Valid values are mgcp or sgcp. For MGCP configurations, use mgcp. If no service-type is specified, the default service-type of mgcp is used.
•protocol-version—(Optional) Specifies the version of the MGCP protocol used for MGCP configurations. Valid values are 0.1 and 1.0. If no protocol-version is specified, the default protocol-version of 0.1 is used.
|
Step 3
|
MRP(config)# dial-peer voice number pots
|
Sets up the dial peer for a voice port.
|
Step 4
|
MRP(config-dial-peer)# application MGCPAPP
|
Selects the MGCP application to run on the voice port.
|
Step 5
|
MRP(config-dial-peer)# port sub-unit/port
|
Selects the voice port used for the dial peer. The keywords are as follows:
•sub-unit—Specifies the sub-unit number of the voice port. Valid values are as follows:
–MRP or ASI81: 0 or 1.
–ASI160: 0.
•port—Specifies the port number. Valid values are:
–MRP or ASI81 in slot 1: 0 or 1.
–ASI81 in slot 0: 0 through 7.
–ASI160: 0 through 15.
|
Step 6
|
MRP(config-dial-peer)# exit
|
Exits dial peer configuration mode and returns to global configuration mode.
|
Step 7
|
MRP(config)# mgcp package-capability {line-package |
dtmf-package | gm-package | rtp-package}
|
(Optional) Specifies the event packages that are supported on the gateway. The keywords are as follows:
•line-package (default)—Specifies the line package.
•dtmf-package—Specifies the DTMF package.
•gm-package—Specifies the generic media package.
•rtp-package—Specifies the RTP package.
|
Step 8
|
MRP(config)# mgcp default-package [line-package |
dtmf-package | gm-package]
|
(Optional) Specifies the event package that should act as the default. Overrides the mgcp package-capability command.
|
Step 9
|
Router(config)# mgcp sdp simple
|
(Optional) Specifies use of a subset of the session description protocol (SDP). Cisco CallManager version 3.1.2c requires this subset to send data through the network. This command is optional for Cisco CallManager version 3.1.3a or later. The default is no mgcp sdp simple.
|
Step 10
|
Router(config)# mgcp fax t38 inhibit
|
(Optional) Prevents the MRP or ASI from sending T.38 fax gateway information to the CallManager. This command is required for operation with Cisco CallManager version 3.1.2c, but is optional for version 3.1.3a and later.
|
Step 11
|
Router(config)# no mgcp timer receive-rtcp
|
(Optional) Prevents a timeout, which results in the disconnecting of a call, from occurring after a 30-second period of silence in one direction of the call. (This can happen during long voice mail message calls, for example.)
|
Configuring a System Card to Use MGCP with Cisco CallManager
The Cisco ICS 7750 MRP and ASI cards have the capability of using MGCP with Cisco CallManager for administration and redundant call agent features. This capability requires additional configuration steps.
To configure a system card so that it can be controlled by Cisco CallManager using MGCP, use the following commands, beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
MRP(config)# ccm-manager MGCP
|
Enables support for Cisco CallManager within MGCP.
|
Step 2
|
MRP(config)# ccm-manager redundant host hostname1
hostname2
|
Identifies one or two backup Cisco CallManager servers. The arguments hostname1 and hostname2 specify the first and second backup servers, respectively, using the dotted decimal format (xxx.xxx.xxx.xxx).
|
Step 3
|
MRP(config)# ccm-manager switchback {graceful |
immediate | schedule-time hh:mm | uptime-delay
minutes}
|
Specifies how the gateway behaves if the primary server becomes unavailable and later becomes available again. The keywords and arguments are as follows:
•graceful—Completes all outstanding calls before returning the gateway to the control of the primary Cisco CallManager server.
•immediate—Returns the gateway to the control of the primary Cisco CallManager server without delay, as soon as the network connection to the server is reestablished.
•schedule-time hh:mm—Returns the gateway to the control of the primary Cisco CallManager server at the specified time, where hh:mm is the time according to a 24-hour clock. If the gateway reestablishes a network connection to the primary server after the configured time, the switchback will occur at the specified time on the following day.
•uptime-delay minutes—Returns the gateway to the control of the primary Cisco CallManager server when the primary server runs for a specified number of minutes after a network connection is reestablished to the primary server. Valid values are from 1 to 1440 (from 1 minute to 24 hours).
|
To force the MRP to use the backup Cisco CallManager server, use the following command, beginning in privileged EXEC mode:
Command
|
Purpose
|
MRP# ccm-manager switchover-to-backup
|
Redirects the MRP or ASI gateway to the backup Cisco CallManager server.
|
Configuring Download of MGCP Voice Gateway Configuration Information from Cisco CallManager
When using the Cisco ICS 7750 as a voice gateway in conjunction with MGCP and Cisco CallManager Version 3.1, you can complete the necessary configuration for a gateway on the Cisco CallManager server and download the configuration to that gateway through a TFTP server.
Before performing the steps in this section, you should complete the basic configuration of your MGCP voice gateway by using the initial configuration dialog and the command-line interface (CLI). Your gateway configuration, as well as that of other network devices, must provide connectivity between your target gateway and the TFTP server.
Note The IP host name should match the gateway name that is specified in the CallManager configuration.
After the required basic configuration of your MGCP voice gateway is completed and the gateway is reset, the configuration file, formatted in XML, is downloaded automatically from the Cisco CallManager server to your local gateway through a TFTP server. On receipt, the local gateway parses this file, converts it to Cisco IOS CLI commands, and uses it to update its active configuration.
After the initial download is completed, the local gateway saves some of the configuration file. If the gateway is restarted or reset and the specified TFTP server is not available, the gateway keeps trying to download the file and does not alter the current configuration.
Note Downloading MGCP gateway configuration information does not override any existing local configuration information. For this reason, you should remove any existing MGCP settings before proceeding with the following steps.
Note In this procedure, only "mgcp"- and "ccm-manager"-related configuration can be downloaded from the CallManager.
To enable the MGCP configuration download feature, use the following commands in EXEC configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router# ccm-manager config server {ip-address |
name}
|
Identifies the IP address of the Cisco CallManager TFTP serve and enables the download of the configuration information from the Cisco CallManager TFTP server to the MGCP voice gateway.
The arguments are as follows:
•ip-address—Specifies the IP address of the TFTP server.
•name—Specifies the DNS host name.
|
Step 2
|
Router# ccm-manager config
|
Enables configuration download from the CallManager.
|
Step 3
|
Router# copy running-config startup-config
|
Copies and saves the running gateway configuration information to NVRAM to prevent the information from being lost during gateway resets, power cycles, or power outages.
Note After completing the above steps, use the Cisco CallManager Administrator to reset the MGCP voice gateway.
|
Configuring MGCP T1 CAS
To configure T1 CAS for MGCP support, use the following commands, beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# controller {t1 | e1} slot/port
|
Enters controller configuration mode.
|
Step 2
|
Router(config-controller)# framing {esf | sf)
|
Specifies the framing type on a DS1 link for T1 and E1 PRI. The keywords are as follows:
•esf—Specifies Extended Superframe as the T1 frame type.
•sf—Specifies Super Frame as the T1 frame type. This is the default.
|
Step 3
|
Router(config-controller)# linecode {ami |
b8zs | hdb3}
|
Specifies the line encoding method for a DS1 link. The keywords are as follows:
•ami—Specifies alternate mark inversion (AMI) as the line code type. Valid for T1 or E1 controllers. This is the default for T1 lines.
•b8zs—Specifies B8ZS as the line code type. Valid for T1 controller only.
•hdb3—Specifies high-density bipolar 3 (hdb3) as the line code type. Valid for E1 controller only. This is the default for E1 lines.
|
Step 4
|
Router(config-controller)# ds0-group
ds0-group-no timeslots timeslot-list type
{e&m-delay-start | e&m-wink-start}
|
Specifies the DS0 time slots that make up a logical voice port on a T1 controller and to specifies the signaling type.
The arguments and keywords are as follows:
•ds0-group-no—Specifies a value from 0 to 23 that identifies the DS0 group.
•timeslots timeslot-list—Specifies a single time-slot number, a single range of numbers, or multiple ranges of numbers separated by commas. For T1 signaling, allowable values are from 1 to 24. Examples are as follows:
–2
–1-15,17-24
–1-23
–2,4,6-12
•type
–e&m-delay-start—The originating endpoint sends an off-hook signal and then waits for an off-hook signal followed by an on-hook signal from the destination.
–e&m-wink-start—E&M Mercury Exchange Limited Channel Associated Signaling (MEL CAS) wink-start signaling support.
|
Step 5
|
Router(config-controller)# exit
|
Returns to global configuration mode.
|
Step 6
|
Router(config)# dial-peer voice tag {pots}
|
Enters dial-peer configuration mode and specifies a dial peer.
|
Step 7
|
Router(config-dial-peer)# application mgcpapp
|
Enables a specific application (in this case, MGCP) on a dial peer.
|
Step 8
|
MRP(config-dial-peer)# port sub-unit/port
|
Selects the voice port used for the dial peer. The keywords are as follows:
•sub-unit—Specifies the sub-unit number of the voice port. Valid values are as follows:
–MRP or ASI81: 0 or 1.
–ASI160: 0.
•port—Specifies the port number. Valid values are:
–MRP or ASI81 in slot 1: 0 or 1.
–ASI81 in slot 0: 0 through 7.
–ASI160: 0 through 15.
|
Configuring ISDN Signaling Backhaul
To configure ISDN to backhaul Q.931 signaling, use the following commands, beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# controller {t1 | e1} slot/port
|
Enters controller configuration mode.
|
Step 2
|
Either
|
|
| |
Router(config-controller)# cablelength long
{0db | -7.5db | -15db | -22.5db}
|
Specifies a cable length longer than 600 feet for a T1 link. The cable length must conform to the actual cable length that you are using. For example, if you attempt to enter the cablelength short command on a long-haul T1 link, the command is rejected.
The keywords are as follows:
•0db—Specifies the decibel pulse level at 0 dB. This is the default pulse rate.
•-7.5db—Specifies the decibel pulse level at -7.5 dB.
•-15db—Specifies the decibel pulse level at -15 dB.
•-22.5db—Specifies the decibel pulse level at -22.5 dB.
|
| |
or
|
|
| |
Router(config-controller)# cablelength short {110ft | 220ft | 330ft | 440ft | 550ft | 600ft}
|
Specifies a cable length of 600 feet or less for a T1 link.
The keywords are as follows.
•110ft—Specifies a cable length from 0 to 110 feet.
•220ft—Specifies a cable length from 111 to 220 feet.
•330ft—Specifies a cable length from 221 to 330 feet.
•440ft—Specifies a cable length from 331 to 440 feet.
•550ft—Specifies a cable length from 441 to 550 feet.
•600ft—Specifies a cable length from 551 to 600 feet.
If you do not set the cable length, the system defaults to a setting of cablelength long 0 dB.
|
Step 3
|
Router(config-controller)# pri-group timeslots
list-of-timeslots service mgcp
|
Specifies MGCP as the control protocol used for backhaul. The controller time slots cannot be shared between backhaul and other Layer 3 protocols.
|
Step 4
|
Router(config-controller)# framing {esf | sf |
crc4 | no-crc4 | mp-crc4} [australia]
|
Specifies the framing type on a DS1 link for T1 and E1 PRI. The keywords are as follows:
•esf—Specifies Extended Superframe as the T1 frame type.
•sf—Specifies Super Frame as the T1 frame type. This is the default.
•crc4—Specifies CRC4 frame as the E1 frame type. This is the default for Australia.
•no-crc4—Specifies no CRC4 frame as the E1 frame type.
•australia—(Optional) Specifies the E1 frame type used in Australia.
|
Step 5
|
Router(config-controller)# linecode {ami |
b8zs | hdb3}
|
Specifies the line encoding method for a DS1 link. The keywords are as follows:
•ami—Specifies alternate mark inversion (AMI) as the line-code type. Valid for T1 or E1 controllers. This is the default for T1 lines.
•b8zs—Specifies B8ZS as the line-code type. Valid for T1 controller only.
•hdb3—Specifies high-density bipolar 3 (hdb3) as the line-code type. Valid for E1 controller only. This is the default for E1 lines.
|
Step 6
|
Router(config-controller)# exit
|
Returns to global configuration mode.
|
Step 7
|
Router(config)# interface serial
slot/port:timeslot number
|
Enters serial interface configuration mode.
The arguments and keywords are as follows:
•slot/port:—Specifies the slot number and port number where the channelized E1 or T1 controller is located.
•timeslot—Specifies, for ISDN, the D channel time slot, which is the 23 channel for T1, and the 15 channel for E1. PRI time slots range from 0 to 23 for channelized T1; PRI time slots range from 0 to 30 for channelized E1. On a dual port card, it is possible to run channelized on one port and primary rate on the other port.
Note The colon (:) is required.
•number—Specifies the channelized E1 or T1 controller number.
|
Step 8
|
Router(config-if)# isdn switch-type
[primary-4ess | primary-5ess | primary-dms100
| primary-ni | primary-net5 | primary-ntt |
primary-ts014]
|
Configures the ISDN switch type. This configuration can be done in global configuration mode or interface configuration mode.
The keywords are as follows:
•primary-4ess (Optional)—Specifies electronic switching system (ESS) 4.
•primary-5ess (Optional)—Specifies ESS 5 that works with T1.
•primary-dms-100 (Optional)—Specifies the DMS 100 switch that works with T1 and E1 PRI.
•primary-ni (Optional)—Specifies an NI switch that works with T1.
•primary-net5 (Optional)—Specifies a Net5 switch that works with E1.
•primary-ntt (Optional)—Specifies the Japanese T1 and E1 PRI switch.
•primary-ts014 (Optional)—Specifies the Australian T1 and E1 PRI switch.
|
Step 9
|
Router(config-if)# isdn bind-L3 ccm-manager
|
Configures ISDN to backhaul Q.931. Repeat Step 1 through Step 8 for each T1 or E1 interface that will use backhaul.
|
Step 10
|
Router(config-if)# isdn protocol-emulate
|
Specifies the ISDN protocol emulation. The default is the user-side ISDN protocol. The keywords are as follows:
•user—Specifies Layer 2 and Layer 3 port protocol operation as TE (port functions as QSIG slave).
•network—Specifies Layer 2 and Layer 3 port protocol operation as NT (port functions as QSIG master).
|
Blocking New Calls and Gracefully Terminating Existing Calls
You can block all new MGCP calls to the router and gracefully terminate all existing active calls, which means that an active call is not terminated until the caller hangs up. To block all new calls, use the following commands in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# mgcp block-newcalls
|
Prevents the gateway from accepting new calls.
|
Step 2
|
Router(config)# no mgcp block-newcalls
|
Restarts normal MGCP call operation.
|
Configuring Fax over MGCP
The Cisco ICS 7750 supports fax over IP using the MGCP protocol. There are two supported modes of fax over IP. The Cisco ICS 7750 can be configured to use either or both modes:
•Fax Relay
•Fax Pass-Through
Note In order to successfully transmit faxes between a Cisco ICS 7750 and another voice gateway, both the Cisco ICS 7750 and the other voice gateway must be configured to use the same mode. Configuring multiple modes on a single MRP or different modes on different MRPs or other routers in the network can cause fax calls to fail.If, for example, the Cisco ICS 7750 is configured to use both fax relay and fax pass-through modes, and the other voice gateway is configured to use fax relay only, the two gateways will be unable to transmit faxes to each other.
Fax Relay
In fax relay mode, the MRP terminates the T.30 fax signaling. Fax relay mode is the preferred method of transmitting fax traffic. Fax relay mode is enabled by default. The following commands can be used to disable fax relay or to determine whether fax relay is enabled:
Command
|
Purpose
|
MRP# no ccm-manager fax protocol cisco
|
Cisco fax relay over MGCP is enabled by default. You can disable it by using this command. If fax relay is disabled, the MRP will use fax pass-through by default.
|
To obtain information about the status of the configuration download feature, use the following privileged EXEC command on the MGCP voice gateway:
The system displays the current status of the download feature, as shown in the following example.
MGCP Domain Name: MRP-000196663c29
============================================================
Primary Registered 10.0.0.50
Current active Call Manager: 10.0.0.50
Backhaul/Redundant link port: 2428
Failover Interval: 30 seconds
Keepalive Interval: 15 seconds
Last keepalive sent: 1w4d (elapsed time: 00:00:06)
Last MGCP traffic time: 1w4d (elapsed time: 00:00:06)
Switchback mode: Graceful
MGCP Fallback mode: Not Selected
Last MGCP Fallback start time: 00:00:00
Last MGCP Fallback end time: 00:00:00
Remote IP Address: 10.7.4.50
PRI Ports being backhauled:
Configuration Error History:
Fax Pass-Through
In fax pass-through mode, the MRP does not distinguish a fax call from a voice call. The fax communication between the two fax machines is carried in band over a "voice" call in its entirety. To use fax pass-through mode, use the following commands.
Note To use fax pass-through mode on the Cisco ICS 7750, you must have Cisco CallManager version 3.1.3a or later. Fax pass-through mode cannot be used with Cisco CallManager version 3.1.2c or any earlier version.
Command
|
Purpose
|
MRP# mgcp modem passthrough voip mode nse
|
Enables peer-to-peer RTP NSE signaling to coordinate disabling of the echo canceller, voice activity detection (VAD), and codec switchover.
|
MRP# mgcp modem passthrough voip redundancy
|
Enables redundant packets to improve reliability by protecting against packet loss.
|
For more information about configuring fax relay or fax pass-through over MGCP on the Cisco ICS 7750, see the document Implementing Fax Over IP on Cisco Voice Gateways at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_access/fxmdmnt.htm
Note The above document lists H.323 as the only protocol available for fax over IP on the Cisco ICS 7750. Customers using Cisco IOS Version 12.2(4) XT3 can also configure Cisco fax relay and fax pass-through using the MGCP protocol.
Enabling Multicast Music-on-Hold
Cisco CallManager Version 3.1 supports putting callers on hold, with music supplied from a streaming multicast MOH server. This section describes how to enable the MOH feature on a Cisco ICS 7750 MGCP voice gateway so that it can support multicast streaming of music to callers who are on hold.
To configure multicast MOH on a Cisco ICS 7750 MGCP voice gateway, use the following command in global configuration mode:
Command
|
Purpose
|
Router(config)# ccm-manager music-on-hold
|
Enables music-on-hold.
|
Sample Configuration
This section guides you through a sample MGCP configuration. This section presents only the minimum commands required for building a working configuration for an MRP with two Foreign Exchange Office (FXO) ports and two Foreign Exchange Station (FXS) ports.
This section describes how to configure one FXO connection to the PSTN, as well as FXS connections to analog handsets and VoIP connectivity to Cisco 7960 IP Phones. After performing this sample configuration, you will be able to make calls to and from all the phones in this example, and you will be able to route calls over the PSTN from any phone in this example.
This section assumes that the reader is already familiar with the process of configuring Cisco IP Phones in CallManager. It also assumes that there is at least one IP Phone already active on the CallManager server.
Note Before performing this sample configuration, you need to have previously run the ICSConfig initial configuration program on the Cisco ICS 7750, you need to have configured IP routing on the MRP, and you need to have configured the voice ports on the MRP. For information about ICSConfig, refer to the Cisco ICS 7750 Getting Started Guide. For information about configuring IP routing and voice ports on the MRP, refer to the Cisco ICS 7750 Software Configuration Guide.
This section addresses the following topics:
•Sample MRP Configuration
•Sample Cisco CallManager Configuration
Sample MRP Configuration
The following procedure shows the minimum commands necessary for configuring the MRP for MGCP in the sample configuration.
Step 1 Configure the MRP to run MGCP as a signaling protocol.
Step 2 Configure the IP address (or DNS Name) for the CallManager server.
MRP(config)#mgcp call-agent 172.16.1.252
Step 3 Select the codec type and the DTMF relay function.
MRP(config)#mgcp dtmf-relay voip codec all mode out-of-band
Step 4 To enable support for Cisco CallManager within MGCP, enter the following command:
MRP(config)#ccm-manager mgcp
Step 5 Bind the MGCP application to the voice ports.
Note Use the show voice port command to determine the type of ports the MRP has and in what order they are installed.
MRP(config)#dial-peer voice 1 pots
MRP(config)#application MGCPAPP
MRP(config)#dial-peer voice 2 pots
MRP(config)#application MGCPAPP
MRP(config)#dial-peer voice 3 pots
MRP(config)#application MGCPAPP
MRP(config)#dial-peer voice 4 pots
MRP(config)#application MGCPAPP
Step 6 Make certain that the voice ports are enabled.
Note The shutdown and no shutdown commands affect both ports on a VIC. It is necessary to enter the command on only one of the ports.
MRP(config)#voice-port 0/0
MRP(config-voiceport)#no shut
Both ports are in service
MRP(config)#voice-port 1/0
MRP(config-voiceport)#no shut
Both ports are in service
The MRP is now ready to communicate with the CallManager server. It will periodically send out messages to attempt to establish a connection. When the CallManager server configuration is complete, the connection should automatically establish itself. You should not have to make any further changes on the MRP.
Caution All dial plan-related configuration elements are controlled by Cisco CallManager, and they should not be configured in the MGCP gateway for MGCP-managed endpoints (those with
application mgcpapp command in their dial-peer statement). You should not configure any of the following functions:
Under Dial Peers
destination-pattern
session-target
Under Voice Ports
connection { plar | tie line | trunk }
Sample Cisco CallManager Configuration
This section shows how to configure Cisco CallManager for the sample configuration described in the previous section. It includes the following sample procedures:
•Creating an MGCP Gateway
•Configuring FXO Ports
•Configuring FXS Ports
•Testing the Phones for Local Connectivity
•Configuring a Route Pattern
•Testing Calls over the PSTN
This example uses the Default Device Pool. In addition, all Locations are set to < None >, all Calling Search Spaces are set to < None >, and all Partitions are set to < None >. If your configuration uses non-default Device Pools, Locations, Calling Search Spaces, or Partitions you must understand the implications of these features before proceeding. For more information about Cisco CallManager, refer to the Cisco CallManager Administration Guide.
Note This section assumes that you already have IP Phones configured on your CallManager server.
Creating an MGCP Gateway
This sample procedure shows how to create an MRP-based MGCP gateway in Cisco CallManager.
Step 1 Open Netscape Communicator or Microsoft Internet Explorer.
Step 2 In the Location or Address field, enter the following URL, replacing <ipaddress> with the IP address of the SPE running Cisco CallManager:
http://<ipaddress>/ccmadmin
You are prompted for a user ID and password.
Step 3 In the User Name field, enter the User ID of your Administrator account.
Step 4 In the Password field, enter your Administrator account password.
Step 5 Click OK.
The Cisco CallManager Administration page appears.
Step 6 From the menu bar at the top of the page, select Device > Gateway.
The Find and List Gateways page appears, as shown in Figure 1.
Figure 1 Find and List Gateways Page
Step 7 Click Add a New Gateway.
The Add a New Gateway page appears, as shown in Figure 2.
Figure 2 Add a New Gateway Page
Step 8 In the Gateway Type field, select Cisco ICS77XX-MRP2XX.
Note This example uses the gateway type Cisco ICS77XX-MRP2XX. The Cisco ICS 7750 also supports gateway types Cisco ICS77XX-ASI160 and Cisco ICS77XX-ASI81, in case your configuration includes these ASI cards.
Step 9 Click Next.
The MGCP Configuration page appears, as shown in Figure 3.
Figure 3 MGCP Configuration Page
Step 10 In the MGCP Domain Name field, enter the actual host name you have assigned to the MRP—in this case, MRP_1.
Note The MGCP domain name is case sensitive.
Step 11 In the Description field, enter an optional description of this MGCP gateway.
Step 12 In the Cisco CallManager Group field, choose the Cisco CallManager group in which you want to create the MGCP gateway.
Step 13 In the Installed Voice Interface Cards fields, select the carrier modules installed in the MRP. VWIC-SLOT is the only option available for the MRP.
Step 14 Scroll down the page, and configure any other settings necessary to describe your configuration. In this example, the default settings were chosen.
Note For more information about the settings on this page, choose Help > For This Page from the main menu, or click the blue button labeled "i."
Step 15 Click Insert.
Configuring FXO Ports
This procedure continues the previous procedure and shows how to configure the FXO ports. The FXO ports connect to the PSTN. In this procedure, the type of port is determined and the attendant Directory Number (DN) is assigned.
Step 1 After Insert is clicked in the last step of the previous procedure, the MGCP Configuration page changes to include fields for the installed voice interface card (VIC) modules, as shown in Figure 4.
Figure 4 VIC Module Fields
Identify the VIC modules installed in slot 0, positions 0 and 1. In this example, they are a VIC-2FXO module and a VIC-2FXS module, respectively.
Step 2 Click Update to activate the changes.
The FXO and FXS ports appear next to the VIC module fields, as shown in Figure 5. These ports are also referred to as Endpoint Identifiers.
Figure 5 Endpoint Identifiers
Step 3 Click the FXO port labeled 0/0.
The Gateway Configuration appears.
Step 4 In the Port Type field, select the type of FXO port. In this example, Loop Start is selected.
Note If you are not certain which option to use, you can experiment, without causing the system any harm. If you are not able to make or receive calls over the FXO port after you complete the MRP and CallManager configuration tasks, you can create a new MGCP Member, using the Ground Start option. You must first delete the original port configuration (MGCP Member). This step is required because it is not possible to change the port type of an MGCP Member after it is created.
The Gateway Configuration page shows all the configuration options for the type of FXO port selected. For this example, Figure 6 shows the FXO Loop Start options.
Figure 6 Gateway Configuration Page - FXO Loop Start Options
Step 5 Configure the parameters necessary for your FXO gateway. An asterisk after a field name indicates that you must enter information in the field.
In Figure 6, Default was chosen in the Device Pool field. For the Port Direction field, Bothways was selected, to indicate that calls can be both originated and received through this FXO gateway. In the Attendant DN field, 7010 was entered, to indicate that extension 7010 should initially receive all incoming calls. All other fields were left with their default options.
Note For more information about the settings on this page, choose Help > For This Page from the main menu, or click the blue button labeled "i."
Step 6 Click Insert.
Step 7 Click Back to MGCP Configuration.
You are returned to the MGCP Configuration page.
Note If you have additional FXO ports to configure, you can configure them by repeating Step 3 through Step 7 for each port. In this sample configuration, the second FXO port is not configured.
Configuring FXS Ports
This procedure continues the previous procedure, "Creating an MGCP Gateway," and shows how to configure FXS ports. The FXS ports connect to the analog telephony devices, handsets in this example. In this procedure, the type of port is determined and the DN is assigned. At the end of this procedure, the MGCP gateway is reset to activate the changes.
Step 1 In the MGCP Configuration page, click the Endpoint Identifier for the first FXS port, the link "1/0" in this example.
The Gateway Configuration page appears, showing the FXS options, as shown in Figure 7.
Figure 7 Gateway Configuration Page - FXS Options
Step 2 Configure the parameters necessary for your FXS gateway. An asterisk after a field name indicates that you must enter information in the field.
In the example above, Default was chosen in the Device Pool field. All other fields were left with their default options.
Note For more information about the settings on this page, choose Help > For This Page from the main menu.
Step 3 Click Insert.
Next to the icon in the top left corner of the Gateway Configuration page are icons that indicate the various FXS ports on this module. Next to the port just configured, 1/0 in this example, a link to Add DN appears on the page. This option lets you add a directory number (extension) for the FXS port you just configured.
Step 4 Click Add DN.
The Directory Number Configuration page appears, as shown in Figure 8.
Figure 8 Directory Number Configuration Page
Step 5 Configure the parameters necessary for your directory number. An asterisk after a field name indicates that you must enter information in the field.
In the example shown in Figure 8, the directory number 7100 was entered in the Directory Number field, to assign extension 7100 to the phone connected to this port. All other fields were left with their default options.
Note For more information about the settings on this page, choose Help > For This Page from the main menu.
Step 6 Click Insert.
Step 7 A confirmation dialog box appears. Click OK.
Step 8 In the top left corner, click the icon for FXS port 1/1 to configure the second FXS port.
Step 9 Repeat Step 2 through Step 7 for the remaining FXS port. In this example, the directory number for FXS port 1/1 is 7101.
Note If you lose your place in the menu system, select Device > Gateway from the main CallManager menu at the top of the screen. Then select Find. All configured gateways will be listed on the screen.
You have now configured the two FXS ports for the analog handsets. Next you must reset the gateway to activate the changes.
Step 10 Click Back to MGCP Configuration.
Step 11 Click Reset Gateway.
The Reset Gateway dialog box appears, as shown in Figure 9.
Figure 9 Reset Gateway Dialog Box
Step 12 Click Restart.
Restarting the gateway applies all your configuration changes to the configured gateway.
Testing the Phones for Local Connectivity
When you finish configuring the MRP, it will send MGCP messages to the CallManager server to attempt to establish an MGCP relationship. If the configuration was successful, the CallManager server and the MRP should be ready to route local calls between any IP phones registered to the CallManager and the analog phones connected to the FXS ports that were configured in the previous procedure, "Configuring FXS Ports."
Step 1 You should now have dial tone on the analog phones connected to the FXS ports. Try dialing from FXS 1/0 to 1/1 (in this case, directory number 7100 and directory number 7101, respectively). You should be able to make and receive calls between these ports.
Step 2 You should also be able to dial any IP Phones that you already had configured from the analog phones that you configured. You should also be able to call the analog phones from the IP Phones. Try making calls to and from all the phones in your configuration.
If some of your phones cannot place or receive calls, look at the Partition, Calling Search Space (CSS), Device Pool, and Location configurations. You may have a configuration that does not allow all local phones to call each other. If this is the case, temporarily place one IP Phone and one analog phone (FXS port) in the same Partition, Device Pool, Location, and Calling Search Space; then try the test again.
Note If you have any problems, see the "Verifying and Troubleshooting the MGCP Gateway" section for more information on troubleshooting tasks.
When you have completed this task successfully, proceed to the next sample procedure, "Configuring a Route Pattern."
Configuring a Route Pattern
This sample procedure configures a simple route pattern to enable the phones to make calls via the PSTN. The standard North American Numbering Plan (NANP) pattern of "9.@" will be used.
Step 1 From the main Cisco CallManager menu, select Route Plan > Route Pattern.
The Find and List Route Patterns page appears.
Step 2 Click Add a New Route Pattern.
Step 3 The Route Pattern Configuration page appears, as shown in Figure 10.
Figure 10 Route Pattern Configuration Page
Step 4 In the Route Pattern field, enter 9.@ to indicate the standard route pattern for dial plans using the NANP. This route pattern is configured to provide dial tone (on by default).
Note The Route Pattern "9.!" is often used for installations outside the United States that cannot use the NANP.
Step 5 In the Gateway Router List field, choose the FXO gateway you configured in the earlier procedure.
Step 6 In the Discard Digits field, choose PreDot to indicate that the route pattern should drop everything up to and including the "." in the route pattern.
Note This example leaves all other fields at their default values. For more information on these fields and on how you might configure them for your installation, choose Help > For This Page from the main menu.
Step 7 Click Insert.
Testing Calls over the PSTN
You should now be able to route calls over the PSTN from any phone on the system by dialing a 9 and the phone number after you hear the dial tone. Perform the following steps to test calling:
Step 1 Try making a call to the PSTN from an analog phone.
Step 2 Try making a call to the PSTN from an IP phone.
Note If you have any problems, see the "Verifying and Troubleshooting the MGCP Gateway" section for more information on troubleshooting tasks.
Verifying and Troubleshooting the MGCP Gateway
This section explains some basic verification and debugging steps for the MGCP on the MRP. It contains information on the following topics:
•show and debug Commands to Verify the Configuration
•Shutting Down and Enabling the Voice Ports
•Caveats
show and debug Commands to Verify the Configuration
This section contains information on the following Cisco IOS commands:
•show mgcp
•show mgcp endpoint
•show mgcp connection
•show voice port slot_num/port_num
•show mgcp statistics
•show ccm-manager
•debug mgcp [all | error | events | packets | parser]
The following steps do not have to be performed in the order shown. The show commands are useful both for displaying the current status of the configuration and for verifying that the changes that you made have taken effect.
show mgcp
Use the show mgcp command to verify the status of the MRP's MGCP parameters. An example of the show mgcp output is shown below:
MGCP Admin State ACTIVE, Oper State ACTIVE - Cause Code NONE
MGCP call-agent: 1.9.3.155 2427 Initial protocol service is MGCP 0.1
MGCP block-newcalls DISABLED
MGCP send SGCP RSIP: forced/restart/graceful/disconnected DISABLED
MGCP quarantine mode discard/step
MGCP quarantine of persistent events is DISABLED
MGCP dtmf-relay voip codec all mode out-of-band
MGCP dtmf-relay for VoAAL2 disabled for all codec types
MGCP voip modem passthrough disabled
MGCP voaal2 modem passthrough disabled
MGCP voip modem relay: Disabled.
MGCP T.38 Named Signalling Event (NSE) response timer: 200
MGCP Network (IP/AAL2) Continuity Test timer: 200
MGCP 'RTP stream loss' timer disabled
MGCP maximum exponential request timeout 4000
MGCP rtp unreachable timeout 1000 action notify
MGCP gateway port: 2427, MGCP maximum waiting delay 3000
MGCP restart delay 0, MGCP vad DISABLED
MGCP system resource check DISABLED
MGCP xpc-codec: DISABLED, MGCP persistent hookflash: DISABLED
MGCP persistent offhook: ENABLED, MGCP persistent onhook: DISABLED
MGCP piggyback msg ENABLED, MGCP endpoint offset DISABLED
MGCP undotted-notation DISABLED
MGCP codec type g711ulaw, MGCP packetization period 20
MGCP JB threshold lwm 30, MGCP JB threshold hwm 150
MGCP LAT threshold lwm 150, MGCP LAT threshold hwm 300
MGCP PL threshold lwm 1000, MGCP PL threshold hwm 10000
MGCP CL threshold lwm 1000, MGCP CL threshold hwm 10000
MGCP playout mode is adaptive 60, 4, 200 in msec
MGCP media (RTP) dscp: cs5, MGCP signaling dscp: cs3
MGCP default package: line-package
MGCP supported packages: gm-package dtmf-package trunk-package line-package
hs-package rtp-package ms-package dt-package mt-package
MGCP Digit Map matching order: shortest match
SGCP Digit Map matching order: always left-to-right
MGCP VoAAL2 ignore-lco-codec DISABLED
MGCP T.38 Fax is DISABLED
MGCP T.38 Fax ECM is DISABLED
MGCP T.38 Fax NSF Override is DISABLED
MGCP T.38 Fax Low Speed Redundancy: 0
MGCP T.38 Fax High Speed Redundancy: 0
MGCP Upspeed payload type for G711ulaw: 0, G711alaw: 8
MGCP Dynamic payload type for G.726-16K codec
MGCP Dynamic payload type for G.726-24K codecMRP_1#
Table 1 lists and describes the show mgcp fields.
Table 1 Explanation of Fields in the show mgcp Command
Field
|
Description
|
MGCP Admin State...
|
The administrative and operational state of the MGCP daemon. The administrative state controls starting and stopping of the application, using the mgcp and mgcp block-newcalls commands. The operational state controls normal MGCP operations.
|
MGCP call-agent
|
The address of the call agent specified in the mgcp command.
|
MGCP block-newcalls enabled
|
The state of the mgcp block-newcalls command.
|
MGCP request timeout
|
The setting for the mgcp request timeout command.
|
MGCP request retries
|
The setting for the mgcp request retries command.
|
MGCP gateway port
|
The UDP port specification.
|
MGCP maximum waiting delay
|
The setting for the mgcp max-waiting-delay command.
|
MGCP restart delay
|
The setting for the mgcp restart-delay command.
|
MGCP VAD
|
The setting for the mgcp vad command.
|
MGCP codec type
|
The setting for the mgcp codec command.
|
MGCP packetization period
|
The packetization period parameter setting for the mgcp codec command.
|
MGCP JB threshold low water mark
|
The jitter buffer minimum threshold parameter setting for the mgcp quality-threshold command.
|
JB threshold high water mark
|
The jitter buffer maximum threshold parameter setting for the mgcp quality-threshold command
|
MGCP LAT threshold low water mark
|
The latency minimum threshold parameter setting for the mgcp quality-threshold command.
|
LAT threshold high water mark
|
The latency maximum threshold parameter setting for the mgcp quality-threshold command.
|
MGCP PL threshold low water mark
|
The packet loss minimum threshold parameter setting for the mgcp quality-threshold command.
|
PL threshold high water mark
|
The packet loss minimum threshold parameter setting for the mgcp quality-threshold command.
|
MGCP IP ToS low delay
|
The low-delay parameter setting for the mgcp ip-tos command.
|
MGCP IP ToS high throughput
|
The high-throughput parameter setting for the mgcp ip-tos command.
|
MGCP IP ToS high reliability
|
The high-reliability parameter setting for the mgcp ip-tos command.
|
MGCP IP ToS low cost
|
The low-cost parameter setting for the mgcp ip-tos command.
|
MGCP IP precedence
|
The precedence parameter setting for the mgcp ip-tos command.
|
MGCP default package type
|
The default-package parameter setting for the mgcp default-package command.
|
Supported MGCP packages
|
The packages supported in this session.
|
show mgcp endpoint
Use the show mgcp command to show the voice ports (endpoints) that are under MGCP control in the MRP. This command verifies which voice ports have been bound to the MGCP application. An example of the show mgcp endpoint output is shown below:
ENDPOINT-NAME V-PORT SIG-TYPE ADMIN
ENDPOINT-NAME V-PORT SIG-TYPE ADMIN
S0/ds1-1/1@UUT1 0/1:23 none up
S0/ds1-1/2@UUT1 0/1:23 none up
S0/ds1-1/3@UUT1 0/1:23 none up
S0/ds1-1/4@UUT1 0/1:23 none up
S0/ds1-1/5@UUT1 0/1:23 none up
S0/ds1-1/6@UUT1 0/1:23 none up
S0/ds1-1/7@UUT1 0/1:23 none up
S0/ds1-1/8@UUT1 0/1:23 none up
S0/ds1-1/9@UUT1 0/1:23 none up
S0/ds1-1/10@UUT1 0/1:23 none up
S0/ds1-1/11@UUT1 0/1:23 none up
S0/ds1-1/12@UUT1 0/1:23 none up
S0/ds1-1/13@UUT1 0/1:23 none up
S0/ds1-1/14@UUT1 0/1:23 none up
S0/ds1-1/15@UUT1 0/1:23 none up
S0/ds1-1/16@UUT1 0/1:23 none up
S0/ds1-1/17@UUT1 0/1:23 none up
S0/ds1-1/18@UUT1 0/1:23 none up
S0/ds1-1/19@UUT1 0/1:23 none up
S0/ds1-1/20@UUT1 0/1:23 none up
S0/ds1-1/21@UUT1 0/1:23 none up
S0/ds1-1/22@UUT1 0/1:23 none up
S0/ds1-1/23@UUT1 0/1:23 none up
show mgcp connection
Use the show mgcp connection command to display any active MGCP connections. An example of the show mgcp connection output, showing one active call, is provided below:
Endpoint Call_ID(C) Conn_ID(I) (P)ort (M)ode (S)tate (C)odec EC (R)esult[EA]
1. aaln/S0/SU1/0 C=A000000001000008,23,24 I=0xD P=16390,0 M=4 S=4,4 CO=1 EC=1 R=0,0
Total number of active calls 1
Table 2 lists and describes the show mgcp connection fields.
Table 2 Explanation of Fields in the show mgcp connection Command
Field
|
Description
|
Endpoint
|
The endpoint for each connection, shown in the analog endpoint naming convention of aaln (indicating "analog"), virtual slot 0, sub-unit x, and port y.
|
Call_ID(C)
|
The MGCP call ID sent by the call agent, the internal Call Control Application Programming Interface (CCAPI) call ID for this endpoint, and the peer call legs CCAPI call ID.
(CCAPI is an API that provides call control facilities to applications.)
|
Conn_ID(I)
|
The connection ID generated by the gateway and sent in the ACK message.
|
(P)ort
|
The ports used for this connection. The first port is the local UDP port. The second port is the remote UDP port
|
(M)ode
|
The call mode, where:
0---invalid value for mode.
1---the gateway should only send packets.
2---the gateway should only receive packets.
3---the gateway can send and receive packets.
4---the gateway should neither send nor receive packets.
5---the gateway should place the circuit in loopback mode.
6---the gateway should place the circuit in test mode.
7---the gateway should use the circuit for network access for data.
8---the gateway should place the connection in network loopback mode.
9---the gateway should place the connection in network continuity test mode.
10---the gateway should place the connection in conference mode.
All other values are used for internal debugging.
|
(S)tate
|
The call state. The values are used for internal debugging purposes.
|
(C)odec
|
The codec identifier. The values are used for internal debugging purposes.
|
(E)vent [SIFL]
|
Used for internal debugging.
|
(R)esult [EA]
|
Used for internal debugging.
|
show voice port slot_num/port_num
Use the show voice port command to verify the current status and configuration of the voice ports on the MRP.
The following is sample output from the show voice port command for an FXO voice port:
MRP_1#show voice port 0/0
Foreign Exchange Office 0/0 Slot is 0, Sub-unit is 0, Port is 0
Operation State is DORMANT
Administrative State is UP
No Interface Down Failure
Noise Regeneration is enabled
Non Linear Processing is enabled
Non Linear Mute is disabled
Non Linear Threshold is -21 dB
Music On Hold Threshold is Set to -38 dBm
Out Attenuation is Set to 3 dB
Echo Cancellation is enabled
Echo Cancellation NLP mute is disabled
Echo Cancellation NLP threshold is -21 dB
Echo Cancel Coverage is set to 8 ms
Playout-delay Mode is set to default
Playout-delay Nominal is set to 60 ms
Playout-delay Maximum is set to 200 ms
Playout-delay Minimum mode is set to default, value 40 ms
Playout-delay Fax is set to 300 ms
Connection Mode is normal
Connection Number is not set
Initial Time Out is set to 10 s
Interdigit Time Out is set to 10 s
Call Disconnect Time Out is set to 60 s
Ringing Time Out is set to 180 s
Wait Release Time Out is set to 30 s
Region Tone is set for US
Currently processing none
Maintenance Mode Set to None (not in mtc mode)
Number of signaling protocol errors are 0
Impedance is set to 600r Ohm
Station name None, Station number None
Voice card specific Info Follows:
Battery-Reversal is enabled
Number Of Rings is set to 1
Supervisory Disconnect is inactive
Answer Supervision is inactive
Ring Detect Status is inactive
Ring Ground Status is inactive
Tip Ground Status is inactive
Digit Duration Timing is set to 100 ms
InterDigit Duration Timing is set to 100 ms
Pulse Rate Timing is set to 10 pulses/second
InterDigit Pulse Duration Timing is set to 750 ms
Percent Break of Pulse is 60 percent
GuardOut timer is 2000 ms
The following is sample output from the show voice port command for an FXS voice port:
MRP_1#show voice port 1/0
Foreign Exchange Station 1/0 Slot is 0, Sub-unit is 1, Port is 0
Operation State is DORMANT
Administrative State is UP
No Interface Down Failure
Noise Regeneration is enabled
Non Linear Processing is enabled
Non Linear Mute is disabled
Non Linear Threshold is -21 dB
Music On Hold Threshold is Set to -38 dBm
Out Attenuation is Set to 3 dB
Echo Cancellation is enabled
Echo Cancellation NLP mute is disabled
Echo Cancellation NLP threshold is -21 dB
Echo Cancel Coverage is set to 8 ms
Playout-delay Mode is set to default
Playout-delay Nominal is set to 60 ms
Playout-delay Maximum is set to 200 ms
Playout-delay Minimum mode is set to default, value 40 ms
Playout-delay Fax is set to 300 ms
Connection Mode is normal
Connection Number is not set
Initial Time Out is set to 10 s
Interdigit Time Out is set to 10 s
Call Disconnect Time Out is set to 60 s
Ringing Time Out is set to 180 s
Wait Release Time Out is set to 30 s
Region Tone is set for US
Currently processing none
Maintenance Mode Set to None (not in mtc mode)
Number of signaling protocol errors are 0
Impedance is set to 600r Ohm
Station name None, Station number None
Voice card specific Info Follows:
Ring Active Status is inactive
Ring Ground Status is inactive
Tip Ground Status is inactive
Digit Duration Timing is set to 100 ms
InterDigit Duration Timing is set to 100 ms
No disconnect acknowledge
Ring Cadence is defined by CPTone Selection
Ring Cadence are [20 40] * 100 msec
Ringer Equivalence Number is set to 1
Table 3 lists and describes the show voice port fields.
Table 3 Explanation of Fields in the show voice port Command
Field
|
Description
|
Administrative State
|
Administrative state of the voice port.
|
Alias
|
User-supplied alias for this voice port.
|
Clear Wait Duration Timing
|
Time of inactive seizure signal to declare call cleared.
|
Connection Mode
|
Connection mode of the interface.
|
Connection Number
|
Full E.164 telephone number that is used to establish a connection with the trunk or PLAR mode.
|
Currently Processing
|
Type of call that is currently being processed: none, voice, or fax.
|
Delay Duration Timing
|
Maximum delay signal duration for delay dial signaling.
|
Delay Start Timing
|
Timing of generation of delayed start signal from detection of incoming seizure.
|
Dial Type
|
Out-dialing type of the voice port.
|
Digit Duration Timing
|
DTMF digit duration, in milliseconds.
|
E&M Type
|
Type of E&M interface.
|
Echo Cancel Coverage
|
Echo cancel coverage for this port.
|
Echo Cancellation
|
Whether or not echo cancellation is enabled for this port.
|
Hook Flash Duration Timing
|
Maximum length of hook flash signal.
|
Hook Status
|
Hook status of the FXO/FXS interface.
|
Impedance
|
Configured terminating impedance for the E&M interface.
|
In Gain
|
Amount of gain inserted at the receiver side of the interface.
|
In Seizure
|
Incoming seizure state of the E&M interface.
|
Initial Time Out
|
Amount of time that the system waits for an initial input digit from the caller.
|
InterDigit Duration Timing
|
DTMF interdigit duration, in milliseconds.
|
InterDigit Pulse Duration Timing
|
Pulse dialing interdigit timing, in milliseconds.
|
Interdigit Time Out
|
Amount of time that the system waits for a subsequent input digit from the caller.
|
Maintenance Mode
|
Maintenance mode of the voice-port.
|
Music On Hold Threshold
|
Configured Music-On-Hold Threshold value for this interface.
|
Noise Regeneration
|
Whether or not background noise should be played to fill silent gaps if VAD is activated.
|
Number of signaling protocol errors
|
Number of signaling protocol errors.
|
Non Linear Processing
|
Whether or not nonlinear processing is enabled for this port.
|
Operation State
|
Operation state of the port.
|
Operation Type
|
Operation of the E&M signal: 2-wire or 4-wire.
|
Out Attenuation
|
Amount of attenuation inserted at the transmit side of the interface.
|
Out Seizure
|
Outgoing seizure state of the E&M interface.
|
Port
|
Port number for this interface associated with the voice interface card.
|
Pulse Rate Timing
|
Pulse dialing rate, in pulses per second (pps).
|
Regional Tone
|
Configured regional tone for this interface.
|
Ring Active Status
|
Ring active indication.
|
Ring Frequency
|
Configured ring frequency for this interface.
|
Ring Ground Status
|
Ring ground indication.
|
Signal Type
|
Type of signaling for a voice port: loop-start or ground-start.
|
Slot
|
Slot used in the voice interface card for this port.
|
Sub-unit
|
Subunit used in the voice interface card for this port.
|
Tip Ground Status
|
Tip ground indication.
|
Type of VoicePort
|
Type of voice port: FXO or FXS.
|
The Interface Down Failure Cause
|
Text string describing why the interface is down,
|
Wink Duration Timing
|
Maximum wink duration for wink start signaling.
|
Wink Wait Duration Timing
|
Maximum wink wait duration for wink start signaling.
|
show mgcp statistics
Use the show mgcp statistics command to show statistical information related to MGCP activity on the MRP. An example of show mgcp statistics output is shown below:
UDP pkts rx 3791, tx 3830
Unrecognized rx pkts 0, MGCP message parsing errors 0
Duplicate MGCP ack tx 0, Invalid versions count 0
CreateConn rx 12, successful 12, failed 0
DeleteConn rx 12, successful 12, failed 0
ModifyConn rx 42, successful 42, failed 0
DeleteConn tx 0, successful 0, failed 0
NotifyRequest rx 8, successful 8, failed 0
AuditConnection rx 0, successful 0, failed 0
AuditEndpoint rx 20, successful 20, failed 0
RestartInProgress tx 6, successful 6, failed 0
Notify tx 3704, successful 3704, failed 0
IP address based Call Agents statistics:
IP address 172.16.1.252, Total msg rx 3791, successful 3791, failed 0
Table 4 lists and describes the show mgcp statistics fields.
Table 4 Explanation of Fields in the show mgcp statistics Command
Field
|
Description
|
UDP pkts
|
The number of UDP packets received (rx) and transmitted (tx).
|
Unrecognized rx pkts
|
The number of packets received that are of unknown type.
|
MGCP message parsing errors
|
The number of MGCP message parsing errors.
|
Duplicate MGCP ack tx
|
The number of duplicate MGCP ACK transmission messages.
|
Invalid versions count
|
The number of invalid versions.
|
CreateConn rx
|
The number of Create Connection messages received from the call agent by the media gateway. Messages received are classified as successful or failed.
|
DeleteConn rx
|
The number of Delete Connection messages received from the call agent by the media gateway. Messages received are classified as successful or failed.
|
ModifyConn rx
|
The number of Modify Connection messages received from the call agent by the media gateway. Messages received are classified as successful or failed.
|
DeleteConn tx
|
The number of Delete Connection messages sent by the call agent. Messages received are classified as successful or failed.
|
NotifyRequest rx
|
The number of Notify messages received by the call agent from the media gateway. Messages received are classified as successful or failed.
|
AuditConnection rx
|
The number of Audit Connection messages received from the call agent by the media gateway. Messages received are classified as successful or failed.
|
AuditEndpoint rx
|
The number of Audit Endpoint messages received from the call agent by the media gateway. Messages received are classified as successful or failed.
|
RestartInProgress tx
|
The number of Restart In Progress (RSIP) messages transmitted by the call agent. Messages received are classified as successful or failed.
|
Notify tx
|
The number of Notify messages transmitted by the call agent. Messages received are classified as successful or failed.
|
ACK tx
|
The number of acknowledgement messages transmitted by the call agent.
|
NACK tx
|
The number of negative acknowledgement messages transmitted by the call agent.
|
ACK rx
|
The number of acknowledgement messages received by the gateway.
|
NACK rx
|
The number of negative acknowledgement messages received by the gateway.
|
IP address
|
The IP address of the call agent.
|
Total msg rx
|
The total number of messages received by the gateway. Messages received are classified as successful or failed.
|
show ccm-manager
Use the show ccm-manager command to show the status and availability of the primary and backup Cisco CallManagers. An example of the show ccm-manager output is shown below:
============================================================
Primary Registered 1.9.3.155
First Backup Down 1.9.3.156
Current active Call Manager: 1.9.3.155
Backhaul/Redundant link port: 2428
Failover Interval: 30 seconds
Keepalive Interval: 15 seconds
Last keepalive sent: 00:06:11 (elapsed time: 00:00:15)
Last MGCP traffic time: 00:06:11 (elapsed time: 00:00:15)
Switchback mode: Graceful
MGCP Fallback mode: Not Selected
Last MGCP Fallback start time: 00:00:00
Last MGCP Fallback end time: 00:00:00
Remote IP Address: 1.9.3.155
PRI Ports being backhauled:
Configuration Error History:
Table 5 lists and describes the show ccm-manager fields.
Table 5 Explanation of Fields in the show ccm-manager Command
Field
|
Description
|
MGCP Domain Name
|
System used in the Internet for translating names of network nodes into IP addresses.
|
Total number of host
|
Number of Cisco CallManagers.
|
Priority
|
Priority of the Cisco CallManagers. Possible priorities are primary, first backup, and second backup.
|
Status
|
Current usage of the Cisco CallManager. Possible values are registered, idle, backup polling, and undefined.
|
Host
|
Host address of the Cisco CallManager.
|
Current active Call Manager
|
Active Cisco CallManager. Can be the primary, first backup, or second backup Cisco CallManager.
|
Current backup Call Manager
|
Backup Cisco CallManager currently being used. Empty when no backup is available.
|
Redundant link port
|
Port that the Cisco CallManager will use.
|
Failover Interval
|
Maximum amount of time that can elapse without the gateway receiving messages from the currently active Cisco Call Manager before the gateway switches to the backup Cisco Call Manager.
|
Keepalive Interval
|
If the gateway has not received any messages from the currently active Cisco CallManager within the specified amount of time, the gateway sends a keepalive message to the Cisco CallManager to be sure that the Cisco CallManager is OK.
|
Last keepalive sent
|
When the last keepalive message was sent.
|
Last MGCP traffic time
|
The last time that MGCP traffic was received by the Cisco CallManager.
|
Last switchover time
|
The last time that a switchover occurred.
|
Switchback mode
|
Displays the switchback mode configuration that determines when the primary Cisco CallManager will be used if it becomes available again while a backup Cisco CallManager is being used.
|
debug mgcp [all | error | events | packets | parser]
Use the debug commands when you are experiencing problems that you believe are not related to configuration errors or hardware problems. It is recommended that you keep an example of each debug command from a working configuration. These examples will be useful as a baseline for comparison when you experience problems.
Shutting Down and Enabling the Voice Ports
In some instances, it may be necessary to shut down and then reenable the voice ports on the MGCP gateway. If you are experiencing problems such as an inability to make calls over FXO ports, or the absence of dial tone on FXS ports, try the commands below.
MRP(config)#voice-port 0/0
MRP(config-voiceport)#shutdown
Both ports are out of service
08:18:22: %LINK-3-UPDOWN: Interface Foreign Exchange Office 0/0, changed status to down
08:18:22: %LINK-3-UPDOWN: Interface Foreign Exchange Office 0/1, changed status to down
MRP(config-voiceport)#no shutdown
Both ports are in service
08:18:34: %LINK-3-UPDOWN: Interface Foreign Exchange Office 0/0, changed status to up
08:18:34: %LINK-3-UPDOWN: Interface Foreign Exchange Office 0/1, changed status to up
MRP(config)#voice-port 1/0
MRP(config-voiceport)#shutdown
Both ports are out of service
08:22:32: %LINK-3-UPDOWN: Interface Foreign Exchange Station 1/0, changed status to down
08:22:32: %LINK-3-UPDOWN: Interface Foreign Exchange Station 1/1, changed status to down
MRP(config-voiceport)#no shutdown
Both ports are in service
08:22:39: %LINK-3-UPDOWN: Interface Foreign Exchange Station 1/0, changed status to up
08:22:39: %LINK-3-UPDOWN: Interface Foreign Exchange Station 1/1, changed status to up
Caveats
This section describes possibly unexpected behavior that may affect your MGCP configuration.
CSCdw10474
On all Cisco voice gateways, when a user configures a ds0-group on a T1 controller, and issues "shutdown / no shutdown" commands on the corresponding voice port while the controller is shut down (or not yet out of shutdown), then the channels associated with the voice port are in the PENDING state. When the controller is brought out of the shutdown state, the channels remain in the PENDING state. This causes calls to and from the gateway to fail.
There are two workarounds.
•Avoid putting the channels in the PENDING state by waiting between controller and voice port "no shutdown" commands, as in the following example:
Router(config)#controller T1 1/0
Router(config-controller)#ds0-group 0 time 1 - 24 type e&m-wink
Router(config-controller)#shut
Router(config-controller)#no shut
Wait for the controller to come out of shutdown, as indicated by
12:34:56: %CONTROLLER-5-UPDOWN: Controller T1 1/0, changed state to up
Then continue entering the following commands:
Router(config-controller)#voice-port 1/0:0
Router(config-voiceport)#shut
Router(config-voiceport)#no shut
Router(config-voiceport)#end
•If the channels are in the PENDING state, issuing "shutdown / no shutdown" commands on either the controller or the voice port returns the channels to normal operation, as shown below:
Router(config)#controller T1 1/0
Router(config-controller)# shut
Router(config-controller)#no shut
Router(config-voiceport)#end
Or:
Router(config)#voice-port 1/0:0
Router(config-voiceport)#shut
Router(config-voiceport)#no shut
Router(config-voiceport)#end
CSCdw51933
When making fax calls between an MRP or ASI configured for MGCP and an MRP or ASI (or other Cisco IOS router) configured for H.323, fax transmission may fail to complete if the MRPs or ASIs are configured for fax pass-through. Fax pass-through is not supported on H.323.
To correct the problem, configure both MRPs or ASIs for fax relay.
CSCdv76938
MGCP call setup might fail on the Cisco ICS 7750 MRP when Cisco CallManager version 3.1(2c) or earlier is used as the Call Agent.
There are two workarounds:
•Make sure that the following configurations are present on the MRP:
Also, make sure that the following configuration is not present:
mgcp modem passthrough voip mode nse
•Enable "Centralized MGCP configuration" by setting the following configurations (this is the suggested workaround for IOS versions 12.2.XN, 12.2(4)YF, 12.2(10)T and later):
ccm-manager config server a.b.c.d
where a.b.c.d is the IP address of the Cisco CallManager from which the configuration will be retrieved.
Related Documentation
For more information about configuring MCGP and other VoIP protocols using Cisco IOS, see the following documents:
•Cisco CallManager Administration Guide
•Cisco IOS Interface Command Reference, Release 12.2
•Cisco IOS IP Command Reference, Vol. 1 of 3: Addressing and Services, Release 12.2
•Cisco IOS Voice, Video, and Fax Command Reference, Release 12.2
•Cisco IOS Voice, Video, and Fax Configuration Guide, Release 12.2
For more information about the Cisco ICS 7750, you can access the most current Cisco ICS 7750 documentation at the following website:
http://www.cisco.com/univercd/cc/td/doc/product/voice/ics7750/index.htm.
Obtaining Documentation
The following sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following URL:
http://www.cisco.com
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
http://www.cisco.com/go/subscription
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Feedback at the top of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
http://www.cisco.com
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
http://www.cisco.com/tac
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
This document is to be used with the Cisco ICS 7750 Installation and Configuration Guide.
Using Media Gateway Control Protocol with the Cisco ICS 7750
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
Feedback
