Interworking of Cisco MGCP Voice Gateways and Cisco CallManager Version 3.1
Available Languages
Table Of Contents
Interworking of Cisco MGCP Voice Gateways and Cisco CallManager Version 3.1
Media Gateway Control Protocol
Single-Point Configuration of MGCP Gateways in AVVID Networks
Benefits of Cisco VoIP Technology Using MGCP
Supported Standards, MIBs, and RFCs
Single-Point Configuration of MGCP Voice Gateways in AVVID Networks
Verifying the MGCP Gateway Configuration Settings
Configuring MGCP Control of Dial Peers and Voice Ports
Verifying the Dial Peer and Voice Port Configurations
Configuring MGCP Globally in a VoIP Network
Verifying the Global MGCP Configuration
Configuring MGCP Control of the Cisco CallManager
Verifying the Configuration of MGCP Control of the Cisco CallManager
Configuring ISDN Signaling Backhaul
Enabling MGCP Gateway Fallback Support
Enabling Multicast Music-on-Hold
Monitoring and Maintaining Cisco CallManager and MGCP
MGCP Control of Dial Peers and Voice Ports Configuration Example
MGCP Control and Cisco CallManager Configuration Examples
T1 CAS and PRI Backhaul Configuration Example
MGCP Gateway Fallback for H.323 T1 CAS Support Configuration Examples
MGCP Fallback to H.323 T1 CAS Configuration Example
MGCP Fallback to H.323 for ISDN T1 PRI Configuration Example
MGCP Fallback to H.323 for ISDN E1 PRI Configuration Example
Single-Point Configuration Example
Multicast Music-on-Hold Configuration Example
ccm-manager switchover-to-backup
Interworking of Cisco MGCP Voice Gateways and Cisco CallManager Version 3.1
Feature History
This document describes Cisco IOS support for the interworking of Cisco MGCP voice gateways and Cisco CallManager Version 3.1 in Cisco IOS Release 12.2(2)XN. This document also describes new command-line interface (CLI) commands that enable you to configure Cisco IP telephony devices for operation in a Voice over IP (VoIP) network.
This document contains the following sections:
•
Supported Standards, MIBs, and RFCs
•
Feature Overview
This section briefly describes the the hardware platforms, communications protocols, and the Cisco IOS software available to support IP telephony MGCP gateway functionality in a Cisco AVVID (Architecture for Voice, Video, and Integrated Data) network. It contains the following sections:
•
•
•
Cisco 2600 Series Routers
Cisco 2600 series routers are key members of the current Cisco data, voice, and video integration portfolio. This family of modular routers enables network managers and service providers to meet a broad range of needs in branch offices for end-to-end IP and Frame Relay based packet telephony solutions. A typical branch office could need the following:
•
•
•
•
•
•
When you use MGCP with a Cisco 2600 series router, all configuration elements associated with dial plans are controlled by the Cisco CallManager and need not be configured on the routers for MGCP-managed endpoints.
Cisco 3600 Series Routers
Cisco 3600 series routers are also key members of the Cisco data, voice, and video integration portfolio that constitute a family of modular, multiservice access platforms intended for use in medium- and large-sized offices and by smaller Internet service providers.
Compared to Cisco 2600 series routers, Cisco 3600 series routers generally provide higher port densities, greater performance, and greater expansion capabilities, while also taking advantage of the enhanced interoperability features offered through Cisco CallManager Version 3.1.
As with the Cisco 2600 series routers, when you use MGCP with a Cisco 3600 series router, all configuration elements associated with dial plans are controlled by the Cisco CallManager and need not be configured on the routers for MGCP-managed endpoints.
Cisco Voice Gateway 200
The Cisco VG200 is designed primarily for use in branch offices that do not require support for integrated WAN data traffic management.
The Cisco VG200 incorporates a single slot that can accommodate a voice network module for connecting an analog or digital interface to the Public Switched Telephone Network (PSTN). A voice network module can accommodate up to two voice interface cards (VICs); each card provides up to two ports.
The Cisco VG200 has a Fast Ethernet LAN port to facilitate connection to a VoIP network.
Media Gateway Control Protocol
MGCP is used in combination with a call agent (see the section "Cisco CallManager Version 3.1") to enable the remote control and management of voice and data communications devices at the edge of multiservice IP packet networks (see the "MGCP Voice Gateways" section).
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 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 Voice Gateways
Cisco MGCP voice gateways provide simple and inexpensive interfaces between LAN and WAN data networks and the PSTN. As illustrated in Figure 1, however, an intermediary device called a gateway is required to provide connectivity between the IP phones and softphones in a TCP/IP-based network and the plain old telephone service (POTS) phones in the PSTN.
Figure 1 Typical VoIP Network with an MGCP Voice Gateway
This combination of technologies and telephony services forms a larger functional domain that is commonly referred to as a VoIP network.
An MGCP voice gateway enables users of IP phones and PC-based softphones to exchange calls with users of POTS phones in the PSTN. The gateway enables this interaction by translating between the signals used in the PSTN (for connecting the communicating endpoints) and the information carried by IP packets (for transmitting traffic across a TCP/IP network).
An MGCP gateway derives most of its configuration information from Cisco CallManager. Initially, through Cisco IOS CLI commands, you configure the gateway to operate under MGCP control and, additionally, you identify the gateway to the Cisco CallManager server for gateway registration purposes. Once the MGCP gateway is registered with a Cisco CallManager server, the latter assumes control over establishing and tearing down connections between the IP endpoints in your VoIP network and the communicating endpoints in the PSTN connected by means of your VoIP network.
Using MGCP and Cisco CallManager, you can deploy a wide range of IP telephony solutions in a VoIP network with the following Cisco platforms functioning as MGCP voice gateways:
•
•
•
Typically, IOS gateways that act as MGCP voice gateways to Cisco CallManager include IP packet networks that handle the translation of signaling information used in setting up, maintaining, and tearing down voice circuits. The circuits pass through an integrated VoIP network as part of an overall, end-to-end communication path.
Cisco CallManager Version 3.1
Cisco CallManager Version 3.1 provides a central point of configuration, administration, and control for the MGCP voice gateways in a VoIP network. By means of MGCP, Cisco CallManager controls the setting up and tearing down of connections between the endpoints in a VoIP network, as well as controlling the communicating endpoints in the PSTN.
When using MGCP in combination with Cisco MGCP voice gateways, Cisco CallManager controls all the dial-plan related configuration elements. Such elements do not need to be configured on a gateway in order to manage the communicating endpoints.
The following features and services are supported by Cisco CallManager Version 3.1 and described briefly in the following sections:
•
ISDN PRI Backhaul and T1 CAS
ISDN PRI backhaul provides a method for transporting complete IP telephony signaling information from an ISDN PRI interface of an MGCP voice gateway 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. A single TCP connection is used by the gateway to backhaul 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.
T1 CAS is supported in non-backhaul fashion and supported CAS signaling types on the Cisco CallManager are E&M, wink-start, and E&M delay-dial. E1 CAS is not supported.
MGCP Gateway Fallback
MGCP gateway fallback is designed to improve the reliability of PSTN interfaces on MGCP voice gateways in a VoIP network. This feature provides basic call processing support on an MGCP voice gateway when it loses connectivity to all of the Cisco CallManager servers that are configured for the gateway. A prioritized list of Cisco CallManager servers is configured on the gateway, thus making each Cisco CallManager server potentially available for use as a backup call agent.
On startup, the MGCP voice gateway attempts to establish a TCP connection to the highest order Cisco CallManager server on the configured list. If successful, the gateway registers itself with the primary (highest priority) call agent.
If no call agent in this prioritized list is accessible, the gateway, in effect, "falls back" onto itself and uses its default H.323 session application (Version 2) to perform basic call-handling functions in support of the following types of interfaces on the gateway:
•
•
•
•
Under the control of Cisco CallManager Version 3.1, the following platforms as well as others can function in a VoIP network in support of the MGCP gateway fallback feature:
•
•
•
These platforms provide connectivity in a Cisco VoIP network to traditional telephone trunks linked to the PSTN.
In the setting of a remote branch office and a centralized CallManager cluster, the MGCP voice gateways in the remote site communicate through a WAN TCP connection to a host Cisco CallManager server in your VoIP network. The gateway maintains this connection by sending empty MGCP Notify (NTFY) keepalive messages to Cisco CallManager at 15-second intervals. If the active Cisco CallManager fails to acknowledge receipt of the keepalive message within 30 seconds, the gateway attempts to switch over to the next highest order Cisco CallManager server that is available.
If none of the Cisco CallManager servers respond, the gateway switches into fallback mode and reverts to its default H.323 session application for basic call control support of IP telephony activity in the network.
H.323 is a standardized communication protocol that enables dissimilar devices to communicate with each other using a common set of codecs, call setup and negotiating procedures, and basic data transport methods.
Figure 2 illustrates a typical VoIP network topology in which MGCP gateway fallback is supported.
Figure 2 Typical VoIP Network Topology Supporting the MGCP Gateway Fallback Feature
Cisco CallManager Version 3.1 provides the following functionality:
•
Figure 3 MGCP Gateway Fallback Transition to the Default H.323 Session Application
All active MGCP analog and T1 CAS calls are maintained during the fallback transition. Callers are unaware of the fallback transition, and these active MGCP calls are cleared only when the communicating callers hang up. Active MGCP PRI backhaul calls are released during fallback.
Any transient MGCP calls (that is, calls that are not in the connected state) are cleared at the onset of the fallback transition and must be attempted again later.
•
When the local MGCP gateway transitions into fallback mode, the default H.323 session application assumes responsibility for handling new calls. Only basic two-party voice calls are supported during the fallback period.
Except for ISDN T1 and E1 PRI calls, all the MGCP calls that are active at the time of fallback are preserved, while transient calls are released. When a user completes (hangs up) an active MGCP call, the MGCP application handles the on-hook event and clears all call resources.
•
When the fallback mode is in effect, the affected MGCP gateway repeatedly tries to open a TCP connection to a Cisco CallManager server in the prioritized list of call agents. This process continues until one of the Cisco CallManager servers in the prioritized list responds.
On response, the TCP open request from the MGCP gateway is honored, and the gateway reverts to MGCP mode and sends a Restart-in-Progress (RSIP) message to effect registration of the gateway with the responding Cisco CallManager.
Except for ISDN T1 and E1 PRI calls, all currently active calls that are initiated and set up during the fallback period are maintained by the default H.323 session application while transient calls are released. After rehome occurs, the new Cisco CallManager assumes responsibility for controlling new IP telephony activity.
Single-Point Configuration of MGCP Gateways in AVVID Networks
When you configure MGCP voice gateways and Cisco CallManager Version 3.1 in the Cisco Architecture for Voice, Video, and Integrated Data (AVVID) networks, you can use a centralized tftpboot directory on a host device in your network to automatically download most of the configuration. The same CallManager server can be concurrently configured as a TFTP server. The downloaded configuration information that the gateways require for operability in a VoIP network can be created and maintained in a unified database.
To enable this feature, you first configure MGCP in your VoIP network through the Cisco CallManager Administrator (the web-based graphical user interface [GUI] of Cisco CallManager). You can also use this facility to automatically issue Cisco IOS CLI configuration commands (in the form of XML files generated from the GUI) to designated MGCP voice gateways in your network. Such commands can be issued by Cisco CallManager to MGCP voice gateways at startup time or whenever a desired configuration change on an MGCP gateway needs to be made.
Each MGCP gateway type in your VoIP network has an associated gateway-specific configuration schema that is stored in the centralized tftpboot directory, from which a tailored XML file can be created (per the appropriate schema) and transmitted through TFTP to a designated MGCP voice gateway.
When the network administrator or other responsible individual at the console of the Cisco CallManager changes the configuration information in the database, a notification message is sent by Cisco CallManager to the affected MGCP voice gateways or IP phones in the network, instructing these devices to download a new XML configuration file.
Each such device incorporates an XML parser or configurator that interprets the XML file content according to its device-specific requirements. In the case of Cisco IOS based MGCP voice gateways, for example, the gateway translates the XML file content into specific Cisco IOS CLI commands for local execution.
When an MGCP voice gateway or IP phone is first started, it has already been preconfigured with or has obtained through Dynamic Host Configuration Protocol (DHCP) the following information, enabling the device to retrieve an XML file from the TFTP server:
•
–
–
•
•
•
With this configuration information available at startup, the MGCP gateway proceeds to download the XML file from the TFTP server. The gateway parses the XML file, converts the information to appropriate Cisco IOS CLI configuration commands, and configures itself to run in the VoIP environment. Finally, the gateway registers itself with Cisco CallManager through an RSIP message, thereby readying itself for service in the network.
When an MGCP gateway configuration in the tftpboot directory is changed using the Cisco CallManager Administrator GUI, the GUI user has the option to reset the gateway or to restart it. If either option is selected, the Cisco CallManager Administrator triggers a configuration update, which causes a special message to be sent to the MGCP gateway notifying it that a new configuration download is required. Thus, with the capabilities supported by this single-point configuration feature, you need not manually synchronize the configuration process between an MGCP voice gateway and the Cisco CallManager.
If a configuration change made using the Cisco CallManager Administrator is limited to a single interface on an MGCP voice gateway, an interface-specific XML configuration file is created, and an interface-specific download is indicated to the gateway. In this case, only the configuration information for that interface is affected, and only those IP telephony calls that pass through that interface are affected.
Multicast Music-on-Hold
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.
This 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.
The MOH feature enables you to subscribe to a music streaming service when using 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 and can relay the packets to designated voice interfaces in the network.
RTP is the Internet-standard protocol for transporting real-time data across a network, including audio and video information. Thus, RTP is well suited for media on demand and interactive services, such as IP telephony.
The default router in the network for handling multicast traffic must have the following enabled:
•
•
•
When you configure a multicast address on 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.
Benefits of Cisco VoIP Technology Using MGCP
Cisco VoIP telephony products enable live voice traffic to be carried over a multiservice IP packet data network by means of MGCP. Thus, voice and data traffic can be integrated for transmission across an IP network infrastructure. This combination of VoIP technology and networking resources yields the following user benefits:
•
•
•
•
Restrictions
•
•
•
Related Documents
•
•
•
•
•
•
Supported Platforms
•
•
•
You can configure any of these platforms to operate as MGCP voice gateways in a VoIP network, enabling you to take advantage of the new and enhanced gateway interoperability features now supported by Cisco CallManager Version 3.1 (see the "Cisco CallManager Version 3.1" section).
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
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
No new or modified RFCs are supported by this feature.
Prerequisites
•
•
–
–
–
–
•
•
Configuration Tasks
This section presents the following configuration tasks for enabling MGCP support for Cisco CallManager Version 3.1 and the Cisco IOS based MGCP voice gateways. Each task in the list is identified as either required or optional.
•
•
•
•
•
•
•
•
Single-Point Configuration of MGCP Voice Gateways in AVVID Networks
When using a Cisco IOS voice gateway in conjunction with MGCP and Cisco CallManager Version 3.1, you can complete the necessary configuration for a given 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 CLI. Your gateway configuration, as well as that of other network devices, must provide connectivity between your target gateway and the TFTP server.
Note
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 the configuration file. If the gateway is restarted or reset from the Cisco CallManager GUI and the specified TFTP server is not available, the gateway keeps trying to download the file and does not alter the current configuration.
Note
To enable the MGCP configuration download feature, use the following commands in EXEC configuration mode:
Router# ccm-manager config
Enables single-point configuration of MGCP voice gateway.
To obtain information about the status of the configuration download feature, use the following privileged EXEC command on the MGCP voice gateway:
Router# show ccm-manager config-downloadThe system displays the current status of the download feature, as shown in the following example.
Configuration Auto-download Information=======================================Current version-id: {1645327B-F59A-4417-8E01-7312C61216AE}Last config-downloaded:00:00:49Current state: Waiting for commandsConfiguration Download statistics:Download Attempted : 4Download Successful : 4Download Failed : 0Configuration Attempted : 1Configuration Successful : 1Configuration Failed(Parsing): 0Configuration Failed(config) : 0Last config download command: New Registration
Note
Verifying the MGCP Gateway Configuration Settings
To view the current MGCP gateway configuration parameters, use the show mgcp command in privileged EXEC mode. These settings determine how the gateway will behave in an MGCP environment. The following is sample output from the show mgcp command:
Router# show mgcpMGCP Admin State ACTIVE, Oper state ACTIVE - Cause Code NONEMGCP call-agent: 172.20.71.44 Initial protocol service is MGCP, v. 0.1MGCP block-newcalls DISABLEDMGCP send RSIP for SGCP is DISABLEDMGCP quarantine mode discard/stepMGCP quarantine of persistent events is ENABLEDMGCP dtmf-relay for VoIP disabled for all codec typesMGCP dtmf-relay for VoAAL2 disabled for all codec typesMGCP voip modem passthrough mode: CISCO, codec: g711ulaw, redundancy: DISABLEDMGCP voaal2 modem passthrough mode: NSE, codec: g711ulawMGCP TSE payload: 0MGCP Network (IP/AAL2) Continuity Test timer: 200MGCP 'RTP' stream loss' timer disabledMGCP request timeout 500, MGCP request retries 3MGCP gateway port: 2427, MGCP maximum waiting delay 3000MGCP restart delay 0, MGCP vad 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 lwm 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 msecMGCP IP ToS low delay disabled, MGCP IP ToS high throughput disabledMGCP IP ToS high reliability disabled, MGCP IP ToS low cost disabledIP RTP precedence 5, MGCP signaling precedence: 3MGCP default package: line-packageMGCP supported packages: gm-package dtmf-package trunk-package line-package hs-package ms-package dt-package gc-packageMGCP VoAAL2 ignore-lco-codec DISABLED>
Note
Configuring MGCP Control of Dial Peers and Voice Ports
Note
To configure dial peers and voice ports for communication with the Cisco CallManager under MGCP control, use the following commands beginning in global configuration mode:
The gateway is now ready to communicate with the Cisco CallManager under MGCP control. The gateway periodically sends out messages attempting to establish a connection to the Cisco CallManager.
When the Cisco CallManager configuration is complete, the connection with the Cisco CallManager should automatically be established. You should not have to perform any further configuration tasks.
Verifying the Dial Peer and Voice Port Configurations
To verify the configuration information for the dial peers, use the show dial-peer voice command in privileged EXEC mode. The following is sample output for a VoIP dial peer:
Router# show dial-peer voice 1000VoiceEncapPeer1000information type = voice,description = `',tag = 1000, destination-pattern = `',answer-address = `', preference=0,numbering Type = `unknown'group = 1000, Admin state is up, Operation state is down,incoming called-number = `', connections/maximum = 0/unlimited,DTMF Relay = disabled,huntstop = disabled,in bound application associated: 'mgcpapp'out bound application associated: ''dnis-map =permission :bothincoming COR list:maximum capabilityoutgoing COR list:minimum requirementtype = pots, prefix = `',forward-digits defaultsession-target = `', voice-port = `',direct-inward-dial = disabled,digit_strip = enabled,register E.164 number with GK = TRUEConnect Time = 0, Charged Units = 0,Successful Calls=0, Failed Calls=0, Incomplete Calls=0Accepted Calls = 0, Refused Calls = 0,Last Disconnect Cause is "",Last Disconnect Text is "",Last Setup Time = 0.
Note
To verify the configuration information for the voice ports, use the show voice port command in privileged EXEC mode. The following is sample output for a Cisco 3600 series router with a Foreign Exchange Station (FXS) analog voice port.
Router# show voice port 1/0/0Foreign Exchange Office 1/0/0 Slot is 1, Sub-unit is 0, Port is 0Type of VoicePort is FXOOperation State is DORMANTAdministrative State is UPNo Interface Down FailureDescription is not setNoise Regeneration is enabledNon Linear Processing is enabledNon Linear Mute is disabledNon Linear Threshold is -21 dBMusic On Hold Threshold is Set to -38 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 3 dBEcho Cancellation is enabledEcho Cancellation NLP mute is disabledEcho Cancellation NLP threshold is -21 dBEcho Cancel Coverage is set to 8 msPlayout-delay Mode is set to defaultPlayout-delay Nominal is set to 60 msPlayout-delay Maximum is set to 200 msPlayout-delay Minimum mode is set to default, value 40 msPlayout-delay Fax is set to 300 msConnection Mode is normalConnection Number is not setInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sCall Disconnect Time Out is set to 60 sRinging Time Out is set to 180 sWait Release Time Out is set to 30 sCompanding Type is u-lawRegion Tone is set for US! Analog information as follows:Currently processing noneMaintenance Mode Set to None (not in mtc mode)Number of signaling protocol errors are 0Impedance is set to 600r OhmStation name None, Station number None! Voice card specific information as follows:Signal Type is loopStartNumber Of Rings is set to 1Supervisory Disconnect is inactiveAnswer Supervision is inactiveHook Status is On HookRing Detect Status is inactiveRing Ground Status is inactiveTip Ground Status is inactiveDial Type is dtmfDigit Duration Timing is set to 100 msInterDigit Duration Timing is set to 100 msPulse Rate Timing is set to 10 pulses/secondInterDigit Pulse Duration Timing is set to 750 msPercent Break of Pulse is 60 percentGuardOut timer is 2000 ms
Note
Configuring MGCP Globally in a VoIP Network
To configure MGCP globally in a VoIP network, use the following commands in global configuration mode:
Verifying the Global MGCP Configuration
To display the global parameters configured on the router or gateway for MGCP, use the show mgcp command in privileged EXEC mode. The following is sample output from the command:
Router# show mgcpGCP Admin State ACTIVE, Oper State ACTIVE - Cause Code NONEMGCP call-agent: 10.0.0.21 2427 Initial protocol service is MGCP, v. 0.1MGCP block-newcalls DISABLEDMGCP send RSIP for SGCP is DISABLEDMGCP quarantine mode discard/stepMGCP quarantine of persistent events is ENABLEDMGCP dtmf-relay voip codec all mode out-of-bandMGCP dtmf-relay for VoAAL2 disabled for all codec typesMGCP voip modem passthrough mode: CISCO, codec: g711ulaw, redundancy: DISABLED,MGCP voaal2 modem passthrough mode: NSE, codec: g711ulawMGCP TSE payload: 0MGCP Network (IP/AAL2) Continuity Test timer: 200MGCP 'RTP stream loss' timer: 5MGCP request timeout 500, MGCP request retries 3MGCP rtp unreachable timeout 1000MGCP gateway port: 2427, MGCP maximum waiting delay 3000MGCP restart delay 0, MGCP vad 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 rtp-package ms-package dt-package sst-packagc-packageMGCP VoAAL2 ignore-lco-codec DISABLED
Note
Configuring MGCP Control of the Cisco CallManager
To configure MGCP control of the Cisco CallManager, use the following commands beginning in global configuration mode:
Verifying the Configuration of MGCP Control of the Cisco CallManager
To verify the configuration of MGCP control of the Cisco CallManager, use the show ccm-manager command in privileged EXEC mode. The following is sample output for this command:
c3660A# show ccm-managerMGCP Domain Name: c3660A.cisco.comTotal number of host: 2Priority Status Host===================================================Primary Registered 172.20.71.38First backup Backup Ready 172.20.71.44Second backup NoneCurrent active Call Manager: 172.20.71.38Backhaul/Redundant link port: 2428Failover Interval: 30 secondsKeepalive Interval: 15 secondsLast keepalive sent: 00:10:33 (elapsed time: 02:39:29)Last MGCP traffic time: 02:49:57 (elapsed time: 00:00:05)Last failover time 02:49:56 from (172.20.71.38)Switchback mode: ImmediateMGCP Fallback mode: Not SelectedLast MGCP Fallback start time: 00:00:00Last MGCP Fallback end time: 00:00:00PRI Backhaul Link info:Link Protocol: TCPRemote Port Number: 2428Remote IP Address: 172.20.71.38Current Link State: OPENStatistics:Packets recvd: 0Recv failures: 0Packets xmitted: 0Xmit failures: 0PRI Ports being backhauled:Slot 1, port 1Configuration Auto-Download Information==============================================No configurations downloadedCurrent state: Automatic Configuration Download feature is disabledConfiguration Error History:FAX mode: cisco
Note
Configuring MGCP T1 CAS
To configure T1 CAS for MGCP support, use the following commands beginning in global configuration mode:
Configuring ISDN Signaling Backhaul
To configure ISDN to backhaul Q.931 signaling, use the following commands beginning in global configuration mode:
Verifying the Backhaul Configurations
To verify the backhaul configurations, use the show isdn status command. In this example, the Layer 2 protocol is Q.921, and the Layer 3 protocol is CCM-MANAGER. This output verifies that the Layer 2 and Layer 3 protocols are configured to backhaul ISDN. If you are connected to a live line, you should see Layer 1 status as active and Layer 2 as MULTIPLE_FRAME_ESTABLISHED.
Router# show isdn status
*00:03:34.423 UTC Sat Jan 1 2000Global ISDN Switchtype = primary-net5ISDN Serial1:23 interfacedsl 0, interface ISDN Switchtype = primary-net5L2 Protocol = Q.921 L3 Protocol(s) = CCM-MANAGERLayer 1 Status:ACTIVELayer 2 Status:TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHEDLayer 3 Status:NLCB:callid=0x0, callref=0x0, state=31, ces=0 event=0x0NLCB:callid=0x0, callref=0x0, state=0, ces=1 event=0x00 Active Layer 3 Call(s)Activated dsl 0 CCBs = 0Number of active calls = 0Number of available B-channels = 23Total Allocated ISDN CCBs = 0The following is sample output from the show ccm-manager backhaul command. The output shows the PRI backhaul link information.
Router# show ccm-manager backhaul
PRI Backhaul Link info:
Link Protocol: TCP
Remote Port Number: 2428
Remote IP Address: 172.20.71.38
Current Link State: OPEN
Statistics:
Packets recvd: 0
Recv failures: 0
Packets xmitted: 21
Xmit failures: 0
PRI Ports being backhauled:
Slot 1, port 1
Note
Enabling MGCP Gateway Fallback Support
The MGCP gateway fallback feature operates as an H.323 gateway. The router takes over the functions of the Cisco CallManager if the link to the Cisco CallManager is lost, such as during an outage in a network segment that contains the Cisco CallManager server.
To enable gateway fallback support for an MGCP gateway, use the following command in global configuration mode:
Router(config)# ccm-manager fallback-mgcp
Enables fallback support for an MGCP voice gateway in a Cisco VoIP network.
Verifying the Status of the MGCP Gateway Fallback Feature
To verify MGCP gateway fallback status, use the show ccm-manager fallback-mgcp command in privileged EXEC mode. The following is sample output that shows MGCP fallback status and, if enabled, whether the feature is active or not (ON or OFF):
Router# show ccm-manager fallback-mgcpCurrent active Call Manager: 172.20.71.29MGCP Fallback mode: Enabled/OFFLast MGCP Fallback start time: 00:00:00Last MGCP Fallback end time: 00:00:00To display general configuration information about the Cisco CallManager, use the show ccm-manager command on the Cisco VG200, Cisco 2600 series routers, and Cisco 3600 series routers. The following is sample output that shows the Cisco CallManager configuration:
Router# show ccm-managerMGCP Domain Name: CiscoPriority Status Host============================================================Primary Registered 172.20.71.29First backup NoneSecond backup NoneCurrent active Call Manager: 172.20.71.29Backhaul/Redundant link port: 2428Failover Interval: 30 secondsKeepalive Interval: 15 secondsLast keepalive sent: 02:51:20 (elapsed time: 00:00:25)Last MGCP traffic time: 02:51:20 (elapsed time: 00:00:25)Last switchover time: NoneSwitchback mode: ImmediateMGCP Fallback mode: Enabled/OFFLast MGCP Fallback start time: 00:00:00Last MGCP Fallback end time: 00:00:00
Note
Enabling Multicast Music-on-Hold
Cisco CallManager Version 3.1 supports the capability to place callers on hold with music being supplied from a streaming multicast music-on-hold (MOH) server. This section describes how to enable the MOH feature on Cisco MGCP voice gateways so that they can support the multicast streaming of music to callers while on hold.
To configure multicast MOH on a Cisco MGCP voice gateway, use the following command in global configuration mode:
Verifying MOH Status
To verify the MOH status and display information about the current configuration, use the show ccm-manager music-on-hold command in privileged EXEC mode. The following is sample output from this command:
Router#show ccm-manager music-on-holdMulticast RTP Packets Call ID IncomingAddress Port In/Out Protocol Interface209.165.200.224 16256 3000/3000 1 IGMP fe0/0
Note
Monitoring and Maintaining Cisco CallManager and MGCP
To monitor and maintain Cisco CallManager and MGCP support, use the following commands in EXEC mode as needed:
Configuration Examples
This section provides the following configuration examples:
•
•
•
•
•
•
•
•
•
•
MGCP Control of Dial Peers and Voice Ports Configuration Example
The following example shows that voice port 0 on voice interface card 1 has been configured to run under MGCP control. This configuration includes two FXO ports and one FXS port that are configured to run under MGCP control. Slot and port numbering begin at 0.
dial-peer voice 1 potsapplication mgcpappport 1/0/0! FXO portdial-peer voice 2 potsapplication mgcpappport 1/0/1! FXO portdial-peer voice 3 potsapplication mgcpappport 1/1/0! FXS portdial-peer voice 4 potsapplication mgcpappport 1/1/1MGCP Control and Cisco CallManager Configuration Examples
The following example shows the configuration of a router to run MGCP control using the primary Cisco CallManager server:
mgcp! Configures the router to run MGCP.mgcp call-agent 10.0.0.201 service-type mgcp version 0.1! Defines the primary Cisco CallManager server.mgcp dtmf-relay voip codec all mode out-of-band! Enables VoIP calls without DTMF.The following example shows the configuration of the Cisco CallManager redundancy functions:
ccm-manager switchback graceful! After the last call ends, use the primary Cisco CallManager.ccm-manager redundant-host 10.0.0.21! Defines the redundant Cisco CallManager server (first backup).ccm-manager mgcp! Enables support for the Cisco CallManager within MGCP.T1 CAS and PRI Backhaul Configuration Example
The following example shows T1 CAS and PRI backhaul configured for an MGCP voice gateway:
Current configuration : 3533 bytes!version 12.2no parser cacheno service single-slot-reload-enableservice timestamps debug datetime localtimeservice timestamps log datetime localtimeno service password-encryption!hostname uut5-c3660!logging rate-limit console 10 except errors!username all!voice-card 3!voice-card 5!ip subnet-zero!ip domain-name tertis.com!no ip dhcp-client network-discoverymgcpmgcp call-agent 10.0.0.21 service-type mgcp version 0.1mgcp dtmf-relay voip codec all mode out-of-bandmgcp modem passthrough voip mode ciscomgcp modem passthrough voip codec g711alawmgcp modem passthrough voip redundancymgcp package-capability dtmf-packagemgcp package-capability mf-packagemgcp package-capability rtp-packagemgcp package-capability sst-packagemgcp default-package line-packagemgcp timer net-cont-test 3000isdn switch-type primary-nicall rsvp-sync!ccm-manager fallback-mgcpccm-manager redundant-host 10.0.0.21ccm-manager mgcpccm-manager music-on-holdfax interface-type vfcmta receive maximum-recipients 0!controller T1 3/0framing esfclock source internallinecode b8zsds0-group 0 timeslots 1 type e&m-wink-startds0-group 1 timeslots 2 type e&m-wink-startds0-group 2 timeslots 3 type e&m-wink-startds0-group 3 timeslots 4 type e&m-wink-startds0-group 4 timeslots 5 type e&m-wink-startds0-group 5 timeslots 6 type e&m-wink-start!controller T1 3/1framing esfclock source internallinecode b8zsds0-group 0 timeslots 1-12 type e&m-wink-start!controller E1 5/0pri-group timeslots 1-31 service mgcp!interface FastEthernet0/0ip address 10.0.0.21 255.255.255.224speed 10half-duplex!interface Ethernet2/0ip address 10.0.0.2 255.255.255.224half-duplex!interface Serial2/0ip address 10.0.0.1 255.255.255.224encapsulation frame-relayshutdownno fair-queueframe-relay interface-dlci 1005!interface Ethernet2/1no ip addressshutdownhalf-duplex!interface Serial5/0:15no ip addressno logging event link-statusisdn switch-type primary-ts014isdn incoming-voice voiceisdn T306 60000isdn bind-L3 ccm-managerno cdp enable!interface Ethernet6/0no ip addressshutdownhalf-duplex!ip classlessip route 10.0.0.4 255.255.255.224 Ethernet2/0ip http server!snmp-server manager!voice-port 1/0/0!voice-port 1/0/1!voice-port 3/0:0!voice-port 3/0:1!voice-port 3/0:2!voice-port 3/0:3!voice-port 3/0:4!voice-port 3/0:5!voice-port 3/1:0!voice-port 4/1/0!voice-port 4/1/1!voice-port 5/0:15!dial-peer cor custom!dial-peer voice 1 potsapplication mgcpappport 1/0/0!dial-peer voice 2 potsapplication mgcpappport 1/0/1!dial-peer voice 20 potsapplication mgcpappport 4/1/0!dial-peer voice 30 potsapplication mgcpappport 4/1/1!dial-peer voice 500 potsapplication mgcpappport 3/0:0!dial-peer voice 200 potsapplication mgcpappport 5/0:15!dial-peer voice 501 potsapplication mgcpappport 3/0:1!dial-peer voice 502 potsapplication mgcpappport 3/0:2!dial-peer voice 503 potsapplication mgcpappport 3/0:3!dial-peer voice 504 potsapplication mgcpappport 3/0:4!dial-peer voice 505 potsapplication mgcpappport 3/0:5!line con 0exec-timeout 0 0line aux 0exec-timeout 0 0line vty 0 4exec-timeout 0 0loginendMGCP Gateway Fallback for H.323 T1 CAS Support Configuration Examples
The following example shows a specific H.323 configuration on MGCP voice gateways for VoIP calls, when using the fallback feature:
dial-peer voice 555 voipapplication mgcpappdestination pattern 555...incoming-called-number 444...session-target ipv4:172.20.21.8codec g711ulaw
Note
The following example shows a specific H.323 configuration on MGCP voice gateways for T1 CAS with e&m-wink-start emulation type using the fallback feature:
ccm-manager switchback immediateccm-manager fallback-mgcpccm-manager mgcpcontroller T1 1/0framing esflinecode b8zsds0-group 1 timeslots 1-24 type e&m-wink-start!voice-port 1/0:1!dial-peer voice 1 potsapplication mgcpappdestination-pattern 91..........port 1/0:1The following example shows a specific H.323 configuration on MGCP voice gateways for FXS ports, using the fallback feature:
dial-peer voice 1 potsapplication mgcpappdestination-pattern 555-1212port 1/0/0The following example shows a specific H.323 configuration on MGCP voice gateways for FXO ports, using the fallback feature:
dial-peer voice 2 potsapplication mgcpappdestination-pattern 527....prefix 527port 1/1/1MGCP Fallback to H.323 T1 CAS Configuration Example
The following example shows a specific configuration for MGCP fallback to H.323 T1 CAS on a voice gateway:
Current configuration : 2181 bytes!version 12.2no service single-slot-reload-enableservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname Tertis-3640a!logging rate-limit console 10 except errors!memory-size iomem 25voice-card 3!ip subnet-zero!no ip domain-lookupip domain-name tertis.com!no ip dhcp-client network-discoveryframe-relay switchingmgcpmgcp call-agent 10.0.0.21 service-type mgcp version 0.1mgcp dtmf-relay voip codec all mode out-of-bandmgcp rtp unreachable timeout 1000mgcp package-capability rtp-packageno mgcp timer receive-rtcpcall rsvp-sync!ccm-manager switchback immediateccm-manager fallback-mgcpccm-manager redundant-host 10.0.0.21ccm-manager mgcp!controller T1 3/0framing esflinecode b8zsds0-group 1 timeslots 1 type e&m-wink-start!controller T1 3/1framing sflinecode ami!interface FastEthernet0/0ip address 10.0.0.21 255.255.255.224duplex autospeed auto!interface Serial0/0ip address 10.0.0.21 255.255.255.224encapsulation frame-relayno keepaliveframe-relay interface-dlci 300!interface Serial0/1no ip addressshutdownclockrate 2000000!interface Ethernet2/0ip address 10.0.0.21 255.255.255.224half-duplex!interface TokenRing2/0no ip addressshutdownring-speed 16!ip classlessip route 10.0.0.21 255.255.255.0 14.0.0.1ip route 10.0.0.21 255.255.255.0 14.0.0.1ip route 10.0.0.21 255.255.255.0 14.0.0.1ip route 10.0.0.21 255.255.255.0 14.0.0.1ip route 10.0.0.21 255.255.255.255 Ethernet2/0ip route 10.0.0.21 255.255.255.255 Ethernet2/0no ip http server!snmp-server manager!voice-port 1/0/0!voice-port 1/0/1!voice-port 1/1/0!voice-port 1/1/1!voice-port 3/0:1!dial-peer cor custom!dial-peer voice 44 potsapplication mgcpappdestination-pattern 4301port 1/1/0!dial-peer voice 55 potsapplication mgcpappdestination-pattern 4302port 1/1/1!dial-peer voice 85 voipdestination-pattern 805....session target ipv4:10.0.0.21codec g711ulaw!dial-peer voice 33 potsapplication mgcpappdestination-pattern 807....port 3/0:1!line con 0exec-timeout 0 0line aux 0line vty 0 4loginendMGCP Fallback to H.323 for ISDN T1 PRI Configuration Example
The following example shows a specific H.323 configuration on MGCP voice gateways for T1 PRI ports, using the fallback feature:
fallback-mgcpccm-manager redundant-host CM-Bccm-manager mgcpccm-manager music-on-holdccm-manager config server cm-a!controller T1 1/0framing esflinecode b8zspri-group timeslots 1-24 service mgcp!controller T1 1/1framing esflinecode b8zspri-group timeslots 1-24 service mgcp!interface Serial1/0:23no ip addressno logging event link-statusisdn switch-type primary-niisdn incoming-voice voiceisdn T306 30000isdn bind-l3 ccm-managerno cdp enable!interface Serial1/1:23no ip addressno logging event link-statusisdn switch-type primary-niisdn incoming-voice voiceisdn T306 30000isdn bind-l3 ccm-managerno cdp enable!dial-peer voice 9991023 potsapplication mgcpappdirect-inward-dialport 1/0:23!dial-peer voice 9991123 potsapplication mgcpappdirect-inward-dialport 1/1:23!dial-peer voice 1640001 potsdestination-pattern 16.....direct-inward-dialport 1/0:23!dial-peer voice 1740001 potsdestination-pattern 17.....direct-inward-dialport 1/1:23!
Note
MGCP Fallback to H.323 for ISDN E1 PRI Configuration Example
The following example shows a specific H.323 configuration on MGCP voice gateways for E1 PRI ports, using the fallback feature:
!ccm-manager fallback-mgcpccm-manager redundant-host CM-Bccm-manager mgcpccm-manager music-on-holdccm-manager config server cm-a!controller E1 1/0pri-group timeslots 1-31!controller E1 1/1pri-group timeslots 1-31!interface Serial1/0:15no ip addressno logging event link-statusisdn switch-type primary-net5isdn incoming-voice voiceisdn T310 30000no cdp enable!interface Serial1/1:15no ip addressno logging event link-statusisdn switch-type primary-net5isdn incoming-voice voiceisdn T310 30000no cdp enable!dial-peer voice 9991015 potsapplication mgcpappdirect-inward-dialport 1/0:15!dial-peer voice 9991115 potsapplication mgcpappdirect-inward-dialport 1/1:15!dial-peer voice 1840001 potsdescription vg200-e1 port 0destination-pattern 18.....direct-inward-dialport 1/0:15!dial-peer voice 1940001 potsdescription vg200-e1 port 1destination-pattern 19.....direct-inward-dialport 1/1:15!
Note
Single-Point Configuration Example
The following example shows a single-point configuration for an MGCP voice gateway:
version 12.2no parser cacheno service single-slot-reload-enableservice timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname vs-3640!logging rate-limit console 10 except errors!memory-size iomem 10voice-card 1!ip subnet-zero!ip domain-name tertis.com!no ip dhcp-client network-discoverymgcpmgcp call-agent 10.10.1.10 2427 service-type mgcp version 0.1mgcp dtmf-relay voip codec all mode out-of-bandmgcp rtp unreachable timeout 1000mgcp modem passthrough voip mode ciscomgcp package-capability rtp-packagemgcp package-capability sst-packageisdn switch-type primary-nicall rsvp-sync!ccm-manager configccm-manager switchback immediateccm-manager mgcpccm-manager music-on-holdccm-manager config server 10.10.1.10!controller T1 1/0framing esflinecode b8zsds0-group 1 timeslots 1-12 type e&m-wink-start!controller T1 1/1framing esflinecode b8zsds0-group 1 timeslots 1-12 type e&m-wink-start!interface Ethernet0/0ip address 10.0.0.21 255.255.255.0half-duplex!interface Ethernet0/1ip address 10.0.0.21 255.0.0.0half-duplex!ip classlessip route 10.0.0.21 255.255.255.255 Ethernet0/1ip http server!snmp-server manager!voice-port 1/0:1!voice-port 1/1:1!voice-port 2/0/0timing hookflash-out 50!voice-port 2/0/1timing hookflash-out 50!voice-port 2/1/0timing hookflash-out 50signal groundStart!voice-port 2/1/1timing hookflash-out 50signal groundStart!dial-peer cor custom!dial-peer voice 999200 potsapplication mgcpappport 2/0/0!dial-peer voice 999201 potsapplication mgcpappport 2/0/1!dial-peer voice 999210 potsapplication mgcpappport 2/1/0!dial-peer voice 999211 potsapplication mgcpappport 2/1/1!dial-peer voice 999101 potsapplication mgcpappport 1/0:1!dial-peer voice 999111 potsapplication mgcpappport 1/1:1!line con 0line aux 0line vty 0 4login!endMulticast Music-on-Hold Configuration Example
The following example shows multicast MOH configured for an MGCP voice gateway:
version 12.2no parser cacheno service single-slot-reload-enableservice timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname vs-3640!logging rate-limit console 10 except errors!memory-size iomem 10voice-card 1!ip subnet-zero!ip domain-name tertis.com!no ip dhcp-client network-discoverymgcpmgcp call-agent 10.0.0.21 2427 service-type mgcp version 0.1mgcp dtmf-relay voip codec all mode out-of-bandmgcp rtp unreachable timeout 1000mgcp modem passthrough voip mode ciscomgcp package-capability rtp-packagemgcp package-capability sst-packageno mgcp timer receive-rtcpcall rsvp-sync!ccm-manager redundant-host 10.0.0.21ccm-manager mgcpccm-manager music-on-holdccm-manager config server 10.0.0.21!controller T1 2/0framing sflinecode amids0-group 0 timeslots 1 type e&m-wink-start!controller T1 2/1framing sflinecode ami!interface FastEthernet0/0ip address 10.0.0.21 255.255.255.0no ip mroute-cacheduplex autospeed autono cdp enablevoice-port 1/0/0!voice-port 1/0/1!voice-port 2/0:0!dial-peer cor custom!dial-peer voice 125 potsapplication mgcpappport 1/0/0!dial-peer voice 150 potsapplication mgcpappport 2/0:0!line con 0exec-timeout 0 0line aux 0line vty 0 4login!no scheduler max-task-timescheduler allocate 4000 4000!endRunning Configuration Example
To display the running configuration, including any configuration changes recently made, use the show running-config command. The following sample output shows the current configuration:
Current configuration : 1244 bytes!version 12.2no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname 3660A!boot system flashboot system romboot system tftp 3660A 10.0.0.201no logging bufferedlogging rate-limit console 10 except errorsno logging consoleenable secret #####enable password #####!ip subnet-zerono ip fingerno ip domain-lookup!mgcpmgcp call-agent 10.0.0.201mgcp dtmf-relay codec all mode out-of-bandmgcp sdp simplecall rsvp-sync!ccm-manager switchback gracefulccm-manager redundant-host 10.0.0.50ccm-manager mgcp!interface FastEthernet0/0ip address 10.0.0.200 255.255.0.0no ip mroute-cachespeed autofull-duplex!ip default-gateway 10.0.0.1ip classlessno ip http server!snmp-server engineID local 000000090200000196983000snmp-server community public RO!voice-port 1/0/0!voice-port 1/0/1!voice-port 1/1/0!voice-port 1/1/1!dial-peer voice 1 potsapplication mgcpappport 1/0/0!dial-peer voice 2 potsapplication mgcpappport 1/0/1!dial-peer voice 3 potsapplication mgcpappport 1/1/0!dial-peer voice 4 potsapplication mgcpappport 1/1/1!line con 0transport input noneline aux 0line vty 0 4password wwlogin!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.
New Commands
•
Modified Commands
application
To enable a specific application on a dial peer, use the application command in dial peer configuration mode. To remove the application from the dial peer, use the no form of this command.
application application-name [out-bound]
no application application-name [out-bound]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Dial peer configuration
Command History
Usage Guidelines
Use this command to associate a predefined session application with an incoming POTS dial peer or an outgoing MMoIP dial peer. Calls using this incoming POTS dial peer or this outgoing MMoIP dial peer will be handed to the predefined specified session application.
The SGCP application and MGCP application can be applied only to POTS dial peers. Neither application uses dial peer hunting.
Note
Examples
The following example shows how to define an application and how to apply it to an outbound MMoIP dial peer for the fax onramp operation:
call application voice fax_on_vfc_onramp http://santa/username/clid_4digits_npw_3.tcldial-peer voice 3 mmoipapplication fax_on_vfc_onramp out-bounddestination-pattern 57108..session target mailto:$d$@mail-server.cisco.comThe following example shows how to apply the MGCP application to a dial peer:
dial-peer voice 1 potsapplication mgcpappRelated Commands
cablelength long
To increase the pulse of a signal at the receiver and decrease the pulse from the transmitter using pulse equalization and line build-out for a T1 cable, use the cablelength long command in controller configuration mode. To return the pulse equalization and line build-out values to their default settings, use the no form of this command.
cablelength long dbgain-value dbloss-value
no cablelength long
Syntax Description
Defaults
Receiver gain of 26 dB and transmitter loss of 0 dB.
Command Modes
Controller configuration mode
Command History
Usage Guidelines
A pulse equalizer regenerates a signal that has been attenuated and filtered by a cable loss. Pulse equalization does not produce a simple gain, but it filters the signal to compensate for complex cable loss. A gain26 receiver gain compensates for a long cable length equivalent to 26 dB of loss, while a gain36 compensates for 36 dB of loss.
The lengthening or building out of a line is used to control far-end crosstalk. Line build-out attenuates the stronger signal from the customer installation transmitter so that the transmitting and receiving signals have similar amplitudes. A signal difference of less than 7.5 dB is ideal. Line build-out does not produce simple flat loss (also known as resistive flat loss). Instead, it simulates a cable loss of 7.5 dB, 15 dB, or 22.5 dB so that the resulting signal is handled properly by the receiving equalizer at the other end.
On the Cisco 2600 and Cisco 3600 series routers, this command is supported on T1 long-haul links only. If you enter the cablelength long command on a DSX-1 (short haul) interface, the command is rejected.
The transmit attenuation value is best obtained by experimentation. If the signal received by the far-end equipment is too strong, reduce the transmit level by entering additional attenuation.
Examples
The following example specifies a pulse gain of 36 decibels and a decibel pulse rate of -7.5 decibels:
interface atm 0/2cablelength long gain36 -7.5dbRelated Commands
cablelength short
To set a cable length 655 feet or shorter for a DS1 link on the Cisco 2600 and 3600 series routers, use the cablelength short command in controller configuration mode. This command is supported on T1 controllers only. To delete the cablelength short value, use the no form of this command. To set cable lengths longer than 655 feet, use the cablelength long command.
cablelength short length
no cablelength short
Syntax Description
Defaults
There is no default value or behavior.
Command Modes
Controller configuration mode
Command History
Usage Guidelines
This command is supported on T1 short-haul links only. If you enter the cablelength short command on a long-haul interface, the command is rejected.
Examples
On a Cisco 2600 or 3600 series router, the following example specifies a cable length from 0 to 133 feet:
interface atm 0/2cablelength short 133
Related Commands
cablelength long
Increases the pulse of a signal at the receiver and decreases the pulse from the sender using pulse equalization and line build-out.
ccm-manager config
To configure the local Media Gateway Control Protocol (MGCP) voice gateway with a TFTP server IP address or logical name for download of the XML configuration file and to enable the download of the configuration, use the ccm-manager config command in global configuration mode. To disable the dial-peer and server configurations, use the no form of this command.
ccm-manager config {dialpeer-prefix | server {ip-address | name}}
no ccm-manager config {dialpeer-prefix | server {ip-address | name}}
Syntax Description
Defaults
The configuration download is disabled.
dialpeer-prefix: 999Command Modes
Global configuration
Command History
12.2(2)XN
This command was introduced on the Cisco 2600 series, Cisco 3600 series and the Cisco VG200.
Usage Guidelines
The ccm-manager config command is optional. If you separate the MGCP and H.323 dial peers under different dial-peer tags, ensure that the MGCP dial peers are configured before the H.323 dial peers. Direct-inward-dial (DID) is required for E1 PRI dial peers.
Examples
The following example shows the configuration on the command:
ccm-manager configIn the following example, the IP address of the TFTP server from which a configuration file is downloaded is identified:
ccm-manager config server 10.0.0.21! Enter configuration commands, one per line.ctrl zRelated Commands
ccm-manager fallback-mgcp
To enable the gateway fallback feature on a Media Gateway Control Protocol (MGCP) voice gateway, use the ccm-manager fallback-mgcp command in global configuration mode. To disable fallback on the MGCP voice gateway, use the no form of this command.
ccm-manager fallback-mgcp
no ccm-manager fallback-mgcp
Syntax Description
This command has no keywords or arguments.
Defaults
Enabled
Command Modes
Global configuration
Command History
12.2(2)XN
This command was introduced for the Cisco 2600 series routers, 3600 series routers, and the Cisco Voice Gateway 200 (Cisco VG200).
Usage Guidelines
The ccm-manager fallback-mgcp command must be enabled to cause the gateway to fall back. The mode and timing are set by default.
Examples
The following example enables the gateway fallback feature on an MGCP voice gateway.
ccm-manager fallback-mgcpRelated Commands
show ccm-manager fallback-mgcp
Displays the status of the MGCP gateway fallback feature.
ccm-manager mgcp
To enable the gateway to communicate with the Cisco CallManager (CCM) through the Media Gateway Control Protocol (MGCP) and to supply redundant control agent services, use the ccm-manager mgcp command in global configuration mode. To disable communication with the CCM and redundant control agent services, use the no form of this command.
ccm-manager mgcp
no ccm-manager mgcp
Syntax Description
This command has no keywords or arguments.
Defaults
The Cisco CallManager does not communicate with the gateway through MGCP.
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables the gateway to communicate with Cisco CallManager through MGCP. This command also enables control agent redundancy when a backup Cisco CallManager server is available.
Examples
In the following example, support for the Cisco CallManager and call agent redundancy is enabled within MGCP:
ccm-manager mgcpccm-manager redundant-host 10.0.0.22Related Commands
ccm-manager music-on-hold
To enable the multicast music-on-hold (MOH) feature on Media Gateway Control Protocol (MGCP) voice gateways, use the ccm-manager music-on-hold command in global configuration mode. To disable the MOH feature on the voice gateway, use the no form of this command.
ccm-manager music-on-hold
no ccm-manager music-on-hold
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
12.2(2)XN
This command was introduced for the Cisco 2600 series routers, 3600 series routers, and the Cisco Voice Gateway 200 (Cisco VG200).
Examples
The following example shows multicast MOH configured for an MGCP voice gateway:
mgcp call-agent 10.0.0.21 2427 service-type mgcp version 0.1mgcp dtmf-relay voip codec all mode out-of-bandmgcp rtp unreachable timeout 1000mgcp modem passthrough voip mode ciscomgcp package-capability rtp-packagemgcp package-capability sst-packageno mgcp timer receive-rtcpcall rsvp-sync!ccm-manager redundant-host 10.0.0.21ccm-manager mgcpccm-manager music-on-holdccm-manager config server 10.0.0.21!Related Commands
show ccm-manager music-on-hold
Displays the MOH information
debug ccm-manager music-on-hold events | packets
Displays debugging information for MOH.
ccm-manager redundant-host
To configure the IP address or the Domain Name System (DNS) name of up to two backup Cisco CallManager servers as call agents, use the ccm-manager redundant-host command in global configuration mode. To disable the backup CCM servers as call agents, use the no form of this command.
ccm-manager redundant-host {ip-address | DNS-name} [ip-address | DNS-name]
no ccm-manager redundant-host {ip-address | DNS-name} [ip-address | DNS-name]
Syntax Description
ip-address
Specifies the IP address of the backup Cisco CallManager server.
DNS-name
Specifies the DNS name of the backup Cisco CallManager server.
Defaults
If you do not configure a backup Cisco CallManager server, redundancy is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
You can configure up to two backup Cisco CallManager servers. The list of IP addresses or DNS names is an ordered and prioritized list. The Cisco CallManager server defined with the mgcp call-agent command has the highest priority (that is, it is the primary Cisco CallManager server). The gateway selects a Cisco CallManager server on the basis of the order of its appearance in this list.
Examples
In the following example, the IP address of the backup Cisco CallManager server is 10.0.0.21:
ccm-manager redundant-host 10.0.0.21Related Commands
ccm-manager switchback
To specify the time at which control is to be returned to the primary Cisco CallManager server once it becomes available, use the ccm-manager switchback command in global configuration mode. To disable the specified time at which the primary server takes control, use the no form of this command.
ccm-manager switchback {graceful | immediate | schedule-time hh:mm | uptime-delay minutes}
no ccm-manager switchback
Syntax Description
Defaults
A graceful return to the primary Cisco CallManager server is the default switchback action.
Command Modes
Global configuration
Command History
Usage Guidelines
This command effects a switchback to the higher priority Cisco CallManager server when it becomes available. In other words, call control reverts to the original (primary) Cisco CallManager server once service to that call agent has been restored.
Examples
In the following example, the primary Cisco CallManager server is used as soon as it becomes available:
ccm-manager switchback immediateRelated Commands
ccm-manager switchover-to-backup
To manually redirect the gateway to the backup Cisco CallManager (CCM) server, use the ccm-manager switchover-to-backup command in privileged EXEC mode.
ccm-manager switchover-to-backup
Syntax Description
This command has no arguments or keywords.
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
12.2(2)XN
This command was introduced on the Cisco 2600 series routers, 3600 series routers, and the Cisco Voice Gateway 200 (Cisco VG200).
Usage Guidelines
The switchover to the backup CCM server occurs immediately. This command does not switch the gateway to the backup Cisco CallManager server if you have the switchback command option set to immediate and the primary Cisco CallManager server is still running.
Examples
In the following example, the backup CCM server is used as soon as it becomes available:
ccm-manager switchover-to-backupRelated Commands
clock source
To configure the clock source of a DS1 link, enter the clock source command in interface configuration, controller configuration, or ATM interface configuration mode. To restore the default line setting, use the no form of this command.
clock source {line | internal | loop-timed}
no clock source
Syntax Description
Defaults
The default value is line.
Command Modes
Controller configuration mode
Command History
Usage Guidelines
This command sets clocking for individual T1/E1 links.
Make sure that you specify the clock source correctly for each link, even if you are planning to specify that a certain link will provide clocking for all the links in an IMA group. Because links may be taken in and out of service, requiring that the system select another link for common clocking, any link in an IMA group may provide the common clock.
If the ATM interface is part of an IMA group, you can use the loop-timed keyword to specify that the clock source is the same as the IMA group clock source.
Examples
On a Cisco 2600 or 3600 series router, the following example specifies an internal clock source for the link:
interface atm 0/2clock source internalRelated Commands
controller
To configure a T1 or E1 controller and enter controller configuration mode, use the controller command in global configuration mode.
controller {t1 | e1} slot/port
Syntax Description
t1
T1 controller.
e1
E1 controller.
slot/port
Backplane slot number and port number on the interface. See your hardware installation manual for the specific values and slot numbers.
Defaults
No T1 or E1 controller is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used in configurations where the router or access server is intended to communicate with a T1 or E1 fractional data line. Additional parameters for the T1 or E1 line must be configured for the controller before the T1 or E1 circuits can be configured using the interface command in global configuration mode.
Examples
The following example configures the MIP in slot 4, port 0 as a T1 controller:
controller t1 4/0The following example configures NIM 0 as a T1 controller:
controller t1 0Related Commands
debug ccm-manager
To display debugging information about the Cisco CallManager (CCM), use the debug ccm-manager command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ccm-manager {backhaul {events | errors} | config-download {all | errors | events | packets | xml} | errors | events | music-on-hold {errors | events | packets} | packets}
no debug ccm-manager
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug ccm-manager events command:
debug ccm-manager events*Feb 28 22:56:05.873: cmapp_mgcpapp_go_down: Setting mgc status to NO_RESPONSE*Feb 28 22:56:05.873: cmapp_host_fsm: New state DOWN for host 0 (172.20.71.38)*Feb 28 22:56:05.873: cmapp_mgr_process_ev_active_host_failed: Active host 0 (172.20.71.38) failed*Feb 28 22:56:05.873: cmapp_mgr_check_hostlist: Active host is 0 (172.20.71.38)*Feb 28 22:56:05.877: cmapp_mgr_switchover: New actv host will be 1 (172.20.71.44)*Feb 28 22:56:05.877: cmapp_host_fsm: Processing event GO_STANDBY for host 0 (172.20.71.38) in state DOWN*Feb 28 22:56:05.877: cmapp_open_new_link: Open link for [0]:172.20.71.38*Feb 28 22:56:05.877: cmbh_open_tcp_link: Opening TCP link with Rem IP 172.20.71.38, Local IP 172.20.71.19, port 2428*Feb 28 22:56:05.881: cmapp_open_new_link: Open initiated OK: Host 0 (172.20.71.38), session_id=8186DEE4*Feb 28 22:56:05.881: cmapp_start_open_link_tmr: Host 0 (172.20.71.38), tmr 0*Feb 28 22:56:05.881: cmapp_host_fsm: New state STANDBY_OPENING for host 0 (172.20.71.38)*Feb 28 22:56:05.881: cmapp_host_fsm: Processing event GO_ACTIVE for host 1 (172.20.71.44) in state STANDBY_READY*Feb 28 22:56:05.885: cmapp_mgr_send_rehome: new addr=172.20.71.44,port=2427*Feb 28 22:56:05.885: cmapp_host_fsm: New state REGISTERING for host 1 (172.20.71.44)Table 11 describes the significant fields shown in the display.
Related Commands
show ccm-manager
Displays a list of Cisco CallManager servers, their current status, and their availability.
debug mgcp
To enable debug traces for errors, events, packets, or the parser for MGCP modules, use the debug mgcp command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug mgcp [all | errors | events | packets | parser]
no debug mgcp [all | errors | events | packets | parser]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug mgcp all command:
debug mgcp allMedia Gateway Control Protocol all debugging is on.00:04:52: MGC stat - 00.0.0.10, total=120, succ=119, failed=000:04:52: MGCP Packet received -DLCX 422361185 S1/ds1-1/1 MGCP 0.1S: dt/relR: dt/supX: 18393659500:04:52: -- mgcp_parse_packet() - call mgcp_parse_header- mgcp_parse_header()- Request Verb FOUND DLCX- mgcp_parse_packet() - out mgcp_parse_headerSUCCESS: mgcp_parse_packet()-MGCP Header parsing was OK- mgcp_parse_parameter_lines(), code_str:: dt/rel, code_len:2, str:S: dt/rel- mgcp_parse_parameter_lines(str:S: dt/rel) -num_toks: 19- mgcp_parse_parameter_lines() check NULL str(dt/rel), in_ptr(S: dt/rel)- mgcp_parse_parameter_lines() return Parse function in mgcp_parm_rules_array[8]- mgcp_parse_sig_requests(in_ptr:dt/rel, len: 6)- mgcp_parse_sig_requests()- protocol is MGCP_V01 call get_package_name buf_ptr:dt/rel- mgcp_parse_sig_requests()- call get_event_name() buf_ptr:rel- mgcp_get_event_name()- event_type is MGCP_SIGNAL_EVT- mgcp_get_event_name looking for event string rel in event table00- mgcp_parse_req_event()- protocol is MGCP_V01 call get_package_name buf_ptr:dt/supMGC stat - 00.0.0.10, total=129, succ=128, failed=0:04:52: mgcp_need_to_parse_params: event = 69, param-is-optional = 0- mgcp_parse_sig_requests()-call mgcp-associate_pkg_evt()- mgcp_associate_pkg_evt- mgcp_parse_sig_requests()- mgcp-associate_pkg_evt(SUCC) buf_ptr:, len:0- mgcp_parse_sig_requests() - NOT mp_emb_syntax_checking- mgcp_parse_sig_requests() - add evt_node to rsd_- mgcp_parse_req_event()- call get_event_name()buf_ptr:sup- mgcp_get_event_name()- event_type is MGCP_REQUEST_EVT- mgcp_get_event_name looking for event string sup in event table00:04:52: mgcp_need_to_parse_params: event = 86, param-is-optional = 0- mgcp_associate_pkg_evt- mgcp_parse_req_event() -Check action: buf_ptr:[additional display text omitted]Related Commands
dial-peer voice
To enter dial-peer configuration mode and to specify the method of voice encapsulation, use the dial-peer voice command in global configuration mode. To disable a defined dial peer, use the no form of this command.
dial-peer voice tag {pots | voatm | vofr | voip}
no dial-peer voice tag {pots | voatm | vofr | voip}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the dial-peer voice global configuration command to switch to dial-peer configuration mode from global configuration mode and to define a particular dial peer. Use the exit command to exit dial-peer configuration mode and return to global configuration mode.
After you have created a dial peer, that dial peer remains defined and active until you delete that particular dial peer. To delete a dial peer, use the no form of this command. To disable a dial peer, use the no shutdown command in dial-peer configuration mode.
Examples
The following example shows how to access dial-peer configuration mode and configure a POTS peer identified as dial peer 10 and an MMoIP dial peer identified as dial peer 20:
dial-peer voice 10 potsdial-peer voice 20 mmoipThe following example deletes the MMoIP peer identified as dial peer 20:
no dial-peer voice 20 mmoipRelated Commands
ds0-group
To specify the DS0 time slots that make up a logical voice port on a T1 controller and to specify the signaling type by which the router communicates with the PBX or Public Switched Telephone Network (PSTN), use the ds0-group command in controller configuration mode. To remove the group and signaling setting, use the no form of this command.
ds0-group ds0-group-no timeslots timeslot-list type {e&m-delay-dial | e&m-fgd | e&m-immediate-start | e&m-wink-start | fgd-eana | fxo-ground-start | fxo-loop-start | fxs-ground-start | fxs-loop-start}
no ds0-group ds0-group-no
Syntax Description
Defaults
No DS0 group is defined.
Command Modes
Controller configuration
Command History
Usage Guidelines
The ds0-group command automatically creates a logical voice port that is numbered on Cisco 2600 series routers and Cisco 3600 series routers as: slot/port:ds0-group-no.
Although only one voice port is created for each group, applicable calls are routed to any channel in the group.
Examples
The following example shows ranges of T1 controller time slots configured for FXS ground-start and FXO loop-start signaling on a Cisco 2600 or 3600 series router:
T1 1/0framing esflinecode b8zsds0-group 1 timeslots 1-10 type fxs-ground-startds0-group 2 timeslots 11-24 type fxo-loop-startRelated Commands
codec
Specifies the voice coder rate of speech for a dial peer.
codec complexity
Specifies call density and codec complexity based on the codec standard you are using.
framing (E1/T1 controller)
To select the frame type for the E1 or T1 data line, use the framing command in controller configuration mode.
T1 Lines
framing {sf | esf}
E1 Lines
framing {crc4 | no-crc4} [australia]
Syntax Description
Defaults
Super frame is the default on a T1 line.
CRC4 frame is the default on an E1 line.
Command Modes
Controller configuration
Usage Guidelines
Use this command in configurations where the router or access server is intended to communicate with T1 or E1 fractional data lines. The service provider determines the framing type (sf, esf, or crc4) required for your T1/E1 circuit.
This command does not have a no form.
Examples
The following example selects extended Super Frame as the T1 frame type:
framing esfRelated Commands
cablelength
Specifies the distance of the cable from the routers to the network equipment.
linecode
Selects the linecode type for T1 or E1 line.
hostname
To specify or modify the host name for the network server, use the hostname global configuration command.
hostname name
Syntax Description
Defaults
The factory-assigned default host name is Router.
Command Modes
Global configuration
Command History
Usage Guidelines
The host name is used in prompts and default configuration filenames.
Do not expect case to be preserved. Upper- and lowercase characters look the same to many internet software applications. It may seem appropriate to capitalize a name the same way you might do in English, but conventions dictate that computer names appear all lowercase. For more information, refer to RFC 1178, Choosing a Name for Your Computer.
The name must also follow the rules for ARPANET host names. They must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, and hyphens. Names must be 63 characters or fewer. For more information, refer to RFC 1035, Domain Names—Implementation and Specification.
Examples
The following example changes the host name to "sandbox":
hostname sandboxRelated Commands
interface serial
To specify a serial interface created on a channelized E1 or channelized T1 controller (for ISDN PRI, channel-associated signalling, or robbed-bit signalling), use the interface serial command in global configuration mode.
interface serial slot/port:timeslot
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
You must explicitly specify a serial interface. The D channel is always the 23 channel for T1 and the 15 for E1.
Examples
The following example configures channel groups on time slots 1 to 11 and ISDN PRI on time slots 12 to 24 of T1 controller 0. Then the examples configures the first two channel groups as serial interfaces 0:0 and 0:1.
controller t1 0channel-group 0 timeslot 1-6channel-group 1 timeslot 7channel-group 2 timeslot 8channel-group 3 timeslot 9-11pri-group timeslots 12-24!interface serial 0:0ip address 172.18.13.2 255.255.255.0encapsulation ppp!interface serial 0:1ip address 172.18.13.3 255.255.255.0encapsulation pppThe following example configures ISDN PRI on T1 controller 4/1 and then configures the D channel on the resulting serial interface 4/1:23:
controller t1 4/1framing crc4linecode hdb3pri-group timeslots 1-24interface serial 4/1:23ip address 172.18.13.1 255.255.255.0encapsulation pppRelated Commands
isdn protocol-emulate
To configure the Layer 2 and Layer 3 port protocol of a BRI voice port or a PRI interface to emulate NT (network) or TE (user) functionality, use the isdn protocol-emulate command in interface configuration mode. To restore the default (user), use the no form of this command.
isdn protocol-emulate {user | network}
no isdn protocol-emulate
Syntax Description
user
Layer 2 and Layer 3 port protocol operation as TE (port functions as QSIG slave).
network
Layer 2 and Layer 3 port protocol operation as NT (port functions as QSIG master).
Defaults
Port functions as Q.SIG slave.
Command Modes
Interface configuration
Command History
Usage Guidelines
If you use the no isdn protocol-emulate command, the Layer 2 and Layer 3 protocol emulation defaults to user.
Examples
The following example configures the Layer 2 and Layer 3 function of T1 PRI interface 23 to act as the Q.SIG master (NT):
interface serial 1:23isdn protocol-emulate networkThe following example configures the Layer 2 and Layer 3 function of an E1 PRI interface to operate as Q.SIG slave (TE):
interface serial 1:15isdn protocol-emulate userRelated Commands
isdn switch-type (PRI)
To specify the central office switch type on the ISDN interface, or to configure the Cisco MC3810 PRI interface to support QSIG signalling, use the isdn switch-type command in global or interface configuration mode. To disable the switch or QSIG signalling on the ISDN interface, use the no form of this command.
isdn switch-type switch-type
no isdn switch-type switch-type
Syntax Description
switch-type
Service provider switch type; see Table 12 for a list of supported switches.
Defaults
The switch type defaults to none, which disables the switch on the ISDN interface.
Command Modes
Global configuration or interface configuration
Note
Command History
Usage Guidelines
You have a choice of configuring the isdn-switch-type command to support QSIG at either the global configuration level or at the interface configuration level. For example, if you have a QSIG connection on one line as well as on the BRI port, you can configure the ISDN switch type in one of the following combinations:
•
•
•
The voice-port codec command must be configured before any calls can be placed over the connection to the PINX. The default codec type is G729a.
To disable the switch on the ISDN interface, specify the isdn switch-type none command.
Table 12 lists supported PRI switch types by geographic area.
Note
Examples
The following example demonstrates the Multiple ISDN Switch Type Feature. The global ISDN switch type setting is basic-net3. The PRI interface (channelized T1 controller), is configured to use the isdn switch-type primary-net5 command.
isdn switch-type basic-net3!interface serial0:23isdn switch-type primary-net5ip address 172.21.24.85 255.255.255.0The following example configures T1 interface 23 to support Q.SIG signaling:
interface serial 1:23isdn switch-type primary-qsigRelated Commands
isdn bind-l3 ccm-manager
To bind Layer 3 of the ISDN PRI interface of the Media Gateway Control Protocol (MGCP) voice gateway to the Cisco CallManager for PRI Q.931 signaling backhaul support, use the isdn bind-L3 ccm-manager command in interface configuration mode. To disable the binding of the ISDN PRI Layer 3 interface of the MGCP, use the no form of this command.
isdn bind-l3 ccm-manager
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
12.2(2)XN
This command was introduced for the Cisco 2600 series routers, 3600 series routers, and the Cisco Voice Gateway 200 (Cisco VG200).
Usage Guidelines
This command enables the ISDN PRI backhaul on an MGCP-enabled voice gateway.
Examples
The following example shows the configuration of the PRI Layer 3:
isdn bind-l3 ccm-managerlinecode
To select the line-code type for T1 or E1 lines, use the linecode command in controller configuration mode.
linecode {ami | b8zs | hdb3}
Syntax Description
Defaults
The ami keyword is the default for T1 lines.
High-density bipolar 3 is the default for E1 lines.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command in configurations in which the router or access server must communicate with T1 fractional data lines. The T1 service provider determines which line-code type, either ami or b8zs, is required for your T1 circuit. Likewise, the E1 service provider determines which line-code type, either ami or hdb3, is required for your E1 circuit.
This command does not have a no form.
Examples
The following example specifies B8ZS as the line-code type:
linecode b8zsmgcp call-agent
To configure the IP address for the primary or default Cisco CallManager server and to designate the optional destination User Datagram Protocol (UDP) port number for the specified Cisco CallManager server, use the mgcp call-agent command in global configuration mode. To disable the specified Cisco CallManager server, use the no form of this command.
mgcp call-agent {ip-address | host-name} [port] [service-type type] [version version-number]
no mgcp call-agent
Syntax Description
Defaults
port: 2427
service-type: mgcp
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command on any platform and media gateway.
If you do not specify a UDP port from the command line, Media Gateway Control Protocol (MGCP) will use 2427 as the default call agent UDP port.
The service type mgcp supports the RSIP error messages sent by the gateway if mgcp restart notify command is enabled.
Examples
The following examples illustrate several formats for specifying the call agent and service type (use any one of these formats):
mgcp call-agent 255.255.255.225 5530 service-type mgcpmgcp call-agent igloo 2009 service-type mgcp version 0.1Related Commands
mgcp dtmf-relay
To ensure accurate forwarding of digits on compressed codecs, use the mgcp dtmf-relay command in global configuration mode. To disable the forwarding of digits on compressed codecs, use the no form of this command.
mgcp dtmf-relay voip codec {all | low-bit-rate} mode {cisco| nse | out-of-band}
no mgcp dtmf-relay voip
Syntax Description
Defaults
No DTMF relay for all codecs is specified.
Command Modes
Controller configuration
Command History
Usage Guidelines
Only VoIP supports the mode options for forwarding digits on codecs.
Examples
The following example shows how to configure a low-bit-rate codec using VoIP in NSE mode:
mgcp dtmf-relay voip codec low-bit-rate mode nsepri-group
To specify an ISDN PRI on a channelized T1 or E1 controller, use the pri-group command in controller configuration mode. To remove the ISDN PRI configuration, use the no form of this command.
pri-group timeslots timeslot-range
no pri-group
Syntax Description
timeslots timeslot-range
Specifies a single range of values. For T1, the allowable range is from 1 to 23. For E1, the allowable range is from 1 to 15.
Defaults
There is no ISDN-PRI group configured.
Command Modes
Controller configuration
Command History
Usage Guidelines
Before you enter the pri-group command, you must specify an ISDN-PRI switch type and an E1 or T1 controller.
Note
Examples
The following example configures ISDN-PRI on all time slots of controller E1 on a Cisco 2600 series router router:
controller E1 4/1pri-group timeslots 1-7,16Related Commands
isdn switch-type
Configures the Cisco 2600 series router router PRI interface to support QSIG signaling.
show ccm-manager
To display a list of Cisco CallManager servers and their current status and availability, use the show ccm-manager command in privileged EXEC mode.
show ccm-manager [backhaul | config-download | fallback-mgcp | hosts | music-on-hold | redundancy]
Syntax Description
Defaults
If you omit any keywords in this command, information related to all keywords is displayed by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to determine whether your primary or backup Cisco CallManager server is down, idle, or polling the backup Cisco CallManager server.
Examples
The following is sample output from the show ccm-manager command for displaying the status and availability of both the primary and the backup Cisco CallManager server.
show ccm-managerMGCP Domain Name: c3660A.cisco.comPriority Status Host============================================================Primary Registered IOS-38 (172.20.71.38)First Backup Backup Ready ios-44 (172.20.71.44)Second Backup NoneCurrent active Call Manager: 172.20.71.38Backhaul/Redundant link port: 2428Failover Interval: 30 secondsKeepalive Interval: 15 secondsLast keepalive sent: 03:06:24 (elapsed time: 00:00:06)Last MGCP traffic time: 03:06:24 (elapsed time: 00:00:06)Last failover time: 02:56:35 from (172.20.71.44)Switchback mode: GracefulMGCP Fallback mode: Enabled/OFFLast MGCP Fallback start time: 00:00:00Last MGCP Fallback end time: 00:00:00PRI Backhaul Link info:Link Protocol: TCPRemote Port Number: 2428Remote IP Address: 172.20.71.38Current Link State: OPENStatistics:Packets recvd: 1Recv failures: 0Packets xmitted: 3Xmit failures: 0PRI Ports being backhauled:Slot 1, port 1MGCP Download Tones: EnabledConfiguration Auto-Download Information=======================================Current version-id: {1645327B-F59A-4417-8E01-7312C61216AE}Last config-downloaded:00:00:49Current state: Waiting for commandsConfiguration Download statistics:Download Attempted : 6Download Successful : 6Download Failed : 0Configuration Attempted : 1Configuration Successful : 1Configuration Failed(Parsing): 0Configuration Failed(config) : 0Last config download command: New RegistrationConfiguration Error History:FAX mode: ciscoTable 13 describes the significant fields shown in the display.
The following is sample output from the show ccm-manager config command that displays :
show ccm-manager configConfiguration Auto-Download Information=======================================Current version-id:{4171F93A-D8FC-49D8-B1C4-CE33FA8095BF}Last config-downloaded:00:00:47Current state:Waiting for commandsConfiguration Download statistics:Download Attempted :6Download Successful :6Download Failed :0Configuration Attempted :1Configuration Successful :1Configuration Failed(Parsing):0Configuration Failed(config) :0Last config download command:New RegistrationTable 14 describes the significant fields shown in the display.
The following is sample output from the show ccm-manager fallback-mgcp command that displays:
show ccm-manager fallback-mgcpCurrent active Call Manager: 172.20.71.38MGCP Fallback mode: Enabled/OFFLast MGCP Fallback start time: 00:14:35Last MGCP Fallback end time: 00:17:25Table 15 describes the significant fields shown in the display.
The following is sample output from the show ccm-manager music-on-hold that displays:
show ccm-manager music-on-holdCurrent active multicast sessions :1Multicast RTP port Packets Call Codec IncomingAddress number in/out id Interface===================================================================172.20.71.38 2428 5/5 99 g711Table 16 describes the significant fields shown in the sample output above from the show ccm-manager music-on-hold command.
Related Commands
show dial-peer voice
To display configuration information for dial peers, use the show dial-peer voice command in privileged EXEC mode.
show dial-peer voice [number] [summary]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show dial-peer voice privileged EXEC command to display the configuration for all Voice over IP (VoIP) and plain old telephone service (POTS) dial peers configured for the router. To show configuration information for only one specific dial peer, use the argument number to identify the dial peer.
Examples
The following is sample output from the show dial-peer voice command for a POTS dial peer:
show dial-peer voice 1VoiceEncapPeer1tag = 1, dest-pat = `+1xxxxxxxxxx',answer-address = `',group = 0, Admin state is up, Operation state is downPermission is Both,session-target = `', voice port =Connect Time = 0, Charged Units = 0Successful Calls = 0, Failed Calls = 0Accepted Calls = 0, Refused Calls = 0Last Disconnect Cause is ""Last Disconnect Text is ""Last Setup Time = 0The following is sample output from the show dial-peer voice command for a VoIP dial peer:
show dial-peer voice 10VoiceOverIpPeer10tag = 10, dest-pat = `',incall-number = `+14087',group = 0, Admin state is up, Operation state is downPermission is Answer,session-protocol = cisco, req-qos = bestEffort,acc-qos = bestEffort,fax-rate = voice, codec = g729r8,Expect factor = 10,Icpif = 30, VAD = disabled, Poor QOV Trap = disabled,Connect Time = 0, Charged Units = 0Successful Calls = 0, Failed Calls = 0Accepted Calls = 0, Refused Calls = 0Last Disconnect Cause is ""Last Disconnect Text is ""Last Setup Time = 0Table 17 provides an alphabetical listing of the show dial-peer voice output fields and a description of each field.
Related Commands
show isdn status
To display the information about memory, Layer 2 and Layer 3 timers, and the status of PRI channels, use the show isdn command in EXEC mode.
show isdn status [dsl | serial number]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show isdn command with the status keyword when no calls are active for a Cisco 3600 with 8 BRIs and 1 E1 PRI:
show isdn statusGlobal ISDN Switchtype = basic-5essISDN BRI0 interfacedsl 0, interface ISDN Switchtype = basic-5essLayer 1 Status:ACTIVELayer 2 Status:TEI = 64, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHEDLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 0 CCBs = 0ISDN BRI1 interfacedsl 1, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 1 CCBs = 0ISDN BRI2 interfacedsl 2, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 2 CCBs = 0ISDN BRI3 interfacedsl 3, interface ISDN Switchtype = basic-5essLayer 1 Status:ACTIVELayer 2 Status:TEI = 75, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHEDLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 3 CCBs = 0ISDN BRI4 interfacedsl 4, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 4 CCBs = 0ISDN BRI5 interfacedsl 5, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 5 CCBs = 0ISDN BRI6 interfacedsl 6, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 6 CCBs = 0ISDN BRI7 interfacedsl 7, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 7 CCBs = 0ISDN Serial0:15 interfacedsl 8, interface ISDN Switchtype = primary-niLayer 1 Status:ACTIVELayer 2 Status:TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHEDLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 8 CCBs = 0Total Allocated ISDN CCBs = 0The following is sample output from the show isdn command with the status keyword, with one active call:
show isdn statusThe current ISDN Switchtype = nttISDN BRI0 interfaceLayer 1 Status:ACTIVELayer 2 Status:TEI = 64, State = MULTIPLE_FRAME_ESTABLISHEDLayer 3 Status:1 Active Layer 3 Call(s)Activated dsl 0 CCBs = 1CCB:callid=8003, callref=0, sapi=0, ces=1, B-chan=1Number of active calls = 1Number of available B-channels = 1Total Allocated ISDN CCBs = 1Table 18 describes the significant fields shown in the show isdn status display.
show mgcp
To display Media Gateway Control Protocol (MGCP) configuration information, use the show mgcp command in EXEC mode.
show mgcp [connection | endpoint | statistics]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show mgcp command:
show mgcpMGCP Admin State ACTIVE, Oper State ACTIVE - Cause Code NONEMGCP call-agent: 00.0.0.00 Initial protocol service is MGCP, v. 0.1MGCP block-newcalls DISABLEDMGCP send RSIP for SGCP is DISABLEDMGCP quarantine mode discard/stepMGCP quarantine of persistent events is ENABLEDMGCP dtmf-relay for VoIP disabled for all codec typesMGCP dtmf-relay for VoAAL2 disabled for all codec typesMGCP voip modem passthrough mode: NSE, codec: g711ulaw, redundancy: DISABLED,MGCP voaal2 modem passthrough mode: NSE, codec: g711ulawMGCP TSE payload: 100MGCP Network (IP/AAL2) Continuity Test timer: 200MGCP 'RTP stream loss' timer: 5MGCP request timeout 500, MGCP request retries 3MGCP gateway port: 2427, MGCP maximum waiting delay 3000MGCP restart delay 0, MGCP vad DISABLEDMGCP simple-sdp ENABLEDMGCP 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: gm-packageMGCP supported packages: gm-package dtmf-package mf-package trunk-packageline-package hs-package rtp-package ms-package dt-packagemo-packageMGCP VoAAL2 ignore-lco-codec DISABLEDTable 19 describes the significant fields shown in the display.
The following is sample output for Voice over IP (VoIP) connections:
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 6Table 20 describes the significant fields shown in the display.
The following is sample output for VoIP and VoAAL2 statistics:
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 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 0Table 21 describes the significant fields shown in the display.
The following example shows how endpoints are configured:
show mgcp endpointENDPOINT-NAME V-PORT SIG-TYPE ADMINds1-0/1@sblab116 0:1 fxs-gs upds1-0/2@sblab116 0:1 fxs-gs upds1-0/3@sblab116 0:1 fxs-gs upds1-0/4@sblab116 0:1 fxs-gs upds1-0/5@sblab116 0:1 fxs-gs upds1-0/6@sblab116 0:1 fxs-gs upds1-0/7@sblab116 0:1 fxs-gs upds1-0/8@sblab116 0:1 fxs-gs upds1-0/9@sblab116 0:1 fxs-gs upds1-0/10@sblab116 0:1 fxs-gs upds1-0/11@sblab116 0:1 fxs-gs upds1-0/12@sblab116 0:1 fxs-gs upds1-0/13@sblab116 0:1 fxs-gs upds1-0/14@sblab116 0:1 fxs-gs upds1-0/15@sblab116 0:1 fxs-gs upds1-0/16@sblab116 0:1 fxs-gs upds1-0/17@sblab116 0:1 fxs-gs upds1-0/18@sblab116 0:1 fxs-gs upds1-0/19@sblab116 0:1 fxs-gs upds1-0/20@sblab116 0:1 fxs-gs upds1-0/21@sblab116 0:1 fxs-gs upds1-0/22@sblab116 0:1 fxs-gs upds1-0/23@sblab116 0:1 fxs-gs upds1-0/24@sblab116 0:1 fxs-gs upTable 22 describes the significant fields shown in the display.
Related Commands
show voice port
To display configuration information about a specific voice port, use the show voice port command in EXEC mode.
Analog Voice Ports
show voice port [slot/subunit/port | summary]
Digital Voice Ports with T1 Packet Voice Trunk Network Modules
show voice port [slot/port:ds0-group | summary]
Syntax Description
Analog Voice Ports
Digital Voice Ports
Command Modes
EXEC
Command History
Usage Guidelines
Use the show voice port EXEC command to display configuration and VIC-specific information about a port.
This command applies to Voice over IP (VoIP), Voice over Frame Relay (VoFR), and Voice over ATM (VoATM).
The ds0-group command automatically creates a logical voice port that is numbered as follows on the Cisco 2600 and Cisco 3600 series routers: slot/port:ds0-group-no. Although only one voice port is created for each group, applicable calls are routed to any channel in the group.
Examples
The following is sample output from the show voice port command for an E&M analog voice port on a Cisco 3600:
show voice portE&M Slot is 1, Sub-unit is 0, Port is 0Type of VoicePort is E&MOperation State is unknownAdministrative State is unknownThe Interface Down Failure Cause is 0Alias is NULLNoise Regeneration is disabledNon Linear Processing is disabledMusic On Hold Threshold is Set to 0 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is disabledEcho Cancel Coverage is set to 16msConnection Mode is NormalConnection Number isInitial Time Out is set to 0 sInterdigit Time Out is set to 0 sAnalog Info Follows:Region Tone is set for northamericaCurrently processing noneMaintenance Mode Set to None (not in mtc mode)Number of signaling protocol errors are 0Voice card specific Info Follows:Signal Type is wink-startOperation Type is 2-wireImpedance is set to 600r OhmE&M Type is unknownDial Type is dtmfIn Seizure is inactiveOut Seizure is inactiveDigit Duration Timing is set to 0 msInterDigit Duration Timing is set to 0 msPulse Rate Timing is set to 0 pulses/secondInterDigit Pulse Duration Timing is set to 0 msClear Wait Duration Timing is set to 0 msWink Wait Duration Timing is set to 0 msWink Duration Timing is set to 0 msDelay Start Timing is set to 0 msDelay Duration Timing is set to 0 msThe following is sample output from the show voice port command for a Foreign Exchange Station (FXS) analog voice port on a Cisco 3600 series router:
show voice portForeign Exchange Station 1/0/0 Slot is 1, Sub-unit is 0, Port is 0Type of VoicePort is FXSOperation State is DORMANTAdministrative State is UPThe Interface Down Failure Cause is 0Alias is NULLNoise Regeneration is enabledNon Linear Processing is enabledMusic On Hold Threshold is Set to 0 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is enabledEcho Cancel Coverage is set to 16msConnection Mode is NormalConnection Number isInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sAnalog Info Follows:Region Tone is set for northamericaCurrently processing noneMaintenance Mode Set to None (not in mtc mode)Number of signaling protocol errors are 0Voice card specific Info Follows:Signal Type is loopStartRing Frequency is 25 HzHook Status is On HookRing Active Status is inactiveRing Ground Status is inactiveTip Ground Status is inactiveDigit Duration Timing is set to 100 msInterDigit Duration Timing is set to 100 msHook Flash Duration Timing is set to 600 msThe following is sample output from the show voice port command for an E&M digital voice port on a Cisco 3600 series router:
show voice portrecEive and transMit Slot is 1, Sub-unit is 0, Port is 1Type of VoicePort is E&MOperation State is DORMANTAdministrative State is UPNo Interface Down FailureDescription is not setNoise Regeneration is enabledNon Linear Processing is enabledMusic On Hold Threshold is Set to -38 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is enabledEcho Cancel Coverage is set to 8 msConnection Mode is normalConnection Number is not setInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sRegion Tone is set for USTable 23 describes the significant fields shown in the display.
voice-port
To enter voice-port configuration mode, use the voice-port command in global configuration mode.
voice-port {slot-number/subunit-number/port} | {slot/port:ds0-group-no}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the voice-port global configuration command to switch to voice-port configuration mode from global configuration mode. Use the exit command to exit voice-port configuration mode and return to global configuration mode.
Examples
The following example accesses voice-port configuration mode for port 0, located on subunit 0 on a voice interface card installed in slot 1 for the Cisco 3600 series:
voice-port 1/0/0Related Commands
dial-peer voice
Enters dial-peer configuration mode and specifies the method of voice encapsulation.
Glossary
call leg—A discrete segment of a call connection that lies between two points in the connection. An end-to-end call consists of four call legs, two from the perspective of the source access server and two from the perspective of the destination access server.
Cisco CallManager—The Cisco CallManager serves as the software-based call-processing agent for a Cisco IP telephony solution. The Cisco CallManager extends enterprise telephony features and functions to packet telephony network devices such as IP phones, media processing devices, VoIP gateways, and multimedia applications. The Cisco CallManager includes a suite of integrated voice applications that perform voice conferencing and manual attendant console functions.
Cisco CallManager server—The Cisco high-availability host platform on which Cisco CallManager software is preinstalled.
cluster—A set of Cisco CallManager servers that share the same MGCP voice gateway configuration database.
codec—A software algorithm that compresses and decompresses speech or audio signals.
dial peer—Defines the characteristics associated with a call leg. Dial peers are used to apply attributes to call legs and to identify the call origin and destination. In VoIP transmission, there are two types of dial peers: POTS and VoIP. You use the dial-peer voice command to define dial peers and to switch to dial-peer configuration mode.
DNS—Domain Name System. A system used in the Internet for translating names of network nodes into IP addresses.
DTMF—dual tone multifrequency. Frequencies in a touch tone telephone in which one high and one low tone is assigned to each touch tone button on a phone. DTMF digits can be detected by the voice ports after call setup is complete and are also trapped by the session application at either end of the connection and carried over the IP network encapsulated in Real Time Conferencing Protocol (RTCP) by means of the RTCP APP extension mechanism.
E&M—The "ear and mouth" interface (also called the "earth and magnet" interface or the "recEive and transMit" interface). Trunk circuits connect telephone switches to one another; they do not connect end-user equipment to the network. The most common form of analog trunk circuit is the E&M interface, which uses special signaling paths that are separate from the audio path of the trunk to convey information about calls. The signaling paths are known as the E-lead and the M-lead. E&M connections from routers to telephone switches or to PBXs are preferable to FXS/FXO connections, because E&M provides better call answer and disconnect supervision.
FXO—Foreign Exchange Office. A connection between a POTS telephone and a digital telephony switching system.
FXS—Foreign Exchange Station. A connection between a digital telephony switching system and a POTS telephone.
gateway—A special-purpose device that performs an application-layer conversion of information from one protocol stack to another. To connect an IP telephony device to the PSTN, you must use an intermediary device called a gateway. A VoIP gateway allows users of IP phones and PC-based softphones to exchange calls with users of POTS phones on the PSTN. The gateway translates between the signals used on the PSTN and the IP packets used to transmit data over a TCP/IP network.
H.323—A collection of protocols that define standard methods for interconnecting H.323 endpoints and POTS devices. It is a method for converting between voice and data transmission formats and for managing connections between telephony endpoints.
IP address—Internet protocol address. A 32-bit address assigned to hosts using TCP/IP. An IP address belongs to one of five classes (A, B, C, D, or E) and is written as 4 octets separated by periods (dotted decimal format). Each address consists of a network number, an optional subnetwork number, and a host number. The network and subnetwork numbers together are used for routing, and the host number is used to address an individual host within the network or subnetwork. A subnet mask is used to extract network and subnetwork information from the IP address. Also known as an Internet address. See also subnet mask.
MGCP—Media Gateway Control Protocol. MGCP enables external control and management of data communications equipment operating at the edge of multiservice packet networks (known as media gateways) by means of software programs. Such software programs are referred to as "call agents" or "media gateway controllers."
PBX—A digital or analog telephone switchboard located on the subscriber premises, typically with an attendant console, and used to connect private and public telephone networks. A PBX is a small, privately owned version of a larger central switching office. It is connected to one or more central offices by trunks and provides service to a number of individual phones. It can be used, for example, in a hotel, business, or government office. On a PBX, an outside line is normally accessed by dialing an access digit, such as 9.
POTS—plain old telephone service. A dial peer describing the characteristics of a traditional telephony network connection. POTS dial peers point to a particular voice port on a voice network device. To configure a POTS dial peer, you must configure the associated telephone number and the logical interface.
protocol—A set of rules or conventions that governs the format and relative timing of data movement in a communications network. There are three basic types of protocols: character-oriented, byte-oriented, and bit-oriented. The protocols for data communications cover such aspects as framing, error handling, transparency, and line control. Ethernet is an example of a LAN protocol.
PSTN—Public Switched Telephone Network. A generic term that refers to the wide variety of telephone networks and telephony services in existence worldwide.
SGCP—Simple Gateway Control Protocol. A protocol that controls VoIP gateways through an external element (called a call agent).
subnet mask—A 32-bit address mask used in IP addressing to indicate the bits of an IP address that are being used for the subnet address. A subnet mask is used to extract network and subnetwork information from the IP address.
T1—Trunk Level 1. A digital transmission link that has a total signaling speed of 1.544 Mbps. T1 uses time-division multiplexing (TDM) to divide the available bandwidth into 24 64-kbps time slots. T1 transmits through the telephone-switching network using AMI or B8ZS coding. T1 is a standard for digital transmission in North America. A T1 device combines the output of up to 24 regular telephone lines for transmission over a digital network. Also referred to as T-1.
TCP—A connection-oriented transport layer protocol that supports reliable full-duplex data transmission. TCP is a part of the TCP/IP protocol stack.
telephony—Telephony is the science of converting sound to electrical signals and transmitting the signals between widely separated endpoints.
UDP—User Datagram Protocol. A connectionless messaging protocol for delivering data packets. A simple protocol that exchanges datagrams without acknowledgments or guaranteed delivery, requiring that error processing and retransmission activity be handled by other protocols.
VoIP—Voice over IP. Enables users to conduct voice communications over a data network using the IP. VoIP can consolidate voice and data traffic for more efficient use of bandwidth, reducing toll charges and providing possible alternatives to expensive and proprietary PBX systems. VoIP dial peers point to specific VoIP devices. To configure a VoIP dial peer, you must configure the associated destination telephone number and a destination IP address.
Feedback