 Feedback
|
Table Of Contents
Network Access Server Package for Media Gateway Control Protocol
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring Dialer Interfaces and Routing
Verifying the Network Access Server Package for Media Gateway Control Protocol Feature
Dialer Interface and Routing Troubleshooting
Network Access Server Package for MGCP Example
Network Access Server Package for Media Gateway Control Protocol
Feature History
This document describes configuration of the Network Access Server Package for Media Gateway Control Protocol feature on the Cisco AS5350, Cisco AS5400, and AS5850 universal gateways in Cisco IOS Release 12.2(11)T. It includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
This feature adds support for the Network Access Server Package for Media Gateway Control Protocol package on the Cisco AS5350, Cisco AS5400, and Cisco AS5850 universal gateways. With this implementation, data calls can be terminated on a trunking media gateway that is serving as a network access server (NAS). Trunks on the NAS are controlled and managed by a call agent that supports Media Gateway Control Protocol (MGCP) for both voice and data calls. The call agent must support the MGCP NAS package.
These capabilities are enabled by the universal port functionality of the Cisco AS5350, Cisco AS5400, and Cisco AS5850, which allows these platforms to operate simultaneously as network access servers and voice gateways to deliver universal services on any port at any time. These universal services include dial access, real-time voice and fax, wireless data access, and unified communications.
The MGCP NAS package implements signals and events to create, modify, and tear down data calls. The events include signaling the arrival of an outbound call (IP to Public Switched Telephone Network [PSTN]) to the media gateway controller (call agent), reporting carrier loss and call authorization status, and receiving callback requests. The following types of calls can be terminated as data calls:
•
•
•
The NAS package provides MGCP capabilities for data calls on the Cisco AS5350, Cisco AS5400, and Cisco AS5850 that support all the dial-in and dial-out services, including the following:
•
•
•
•
Resource pool management can be used to manage dial ports when dialed number identification service (DNIS) preauthentication is enabled. The NAS returns an error with a preauthentication failure code to the call agent, which releases the call gracefully with a busy cause. Refer to the Cisco IOS Dial Technologies Configuration Guide, Release 12.2, for more information about dial-pool management, and the Cisco IOS Security Configuration Guide, Release 12.2, for more information about authentication, authorization, and accounting (AAA) preauthentication services.
Figure 1 shows a typical network topology for universal port media gateways.
Figure 1 Media Gateways Operating As Network Access Servers
Benefits
Key benefits of the Network Access Server Package for Media Gateway Control Protocol feature are derived from the presence of universal ports that are able to terminate both voice and data calls under control of the MGCP call agent. These benefits include the following:
•
–
–
–
•
–
•
•
Restrictions
•
Related Features and Technologies
For information about configuring MGCP 1.0, refer to the following document:
•
For information about MGCP 0.1, refer to the following publication:
•
Related Documents
•
•
•
•
•
•
•
•
•
•
•
•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/index.htm
Supported Platforms
•
•
•
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Availability of Cisco IOS Software Images
•
Note
Supported Standards, MIBs, and RFCs
Standards
•
MIBs
No new or modified MIBs are supported by this feature.
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
•
•
•
•
–
–
Configuration Tasks
With the Network Access Server Package for Media Gateway Control Protocol feature, the NAS supports both data and voice calls, which can be managed from a single call agent that supports MGCP with the NAS package. The NAS package provides the interface to a call agent (media gateway controller) for handling modem calls that terminate on the NAS and that originate from the PSTN, including callback requests. Results of AAA authorization and preauthorization requests from the NAS are reported to the call agent as notifications.
See the following sections for configuration tasks for the Network Access Server Package for Media Gateway Control Protocol feature. Each task in the list is identified as either required or optional.
•
•
•
•
Configuring the NAS for MGCP
In this task, MGCP is configured on the trunking gateway (NAS), and the NAS package is set as the default package. The steps that are listed are the minimum needed to configure MGCP on the NAS. For more commands and optional settings for MGCP, see the documents listed in the "Related Features and Technologies" section.
To configure the Network Access Server Package for Media Gateway Control Protocol feature, use the following commands in global configuration mode.
Configuring Controllers
In this task, in addition to the standard controller commands, you configure a T1 or E1 controller for external signaling control by MGCP. You can also set the AAA preauthentication timer to expire after a certain number of milliseconds have elapsed without a response from the AAA server and indicate whether the call should be accepted or rejected if no response occurs before the timer expires.
To configure a controller to use the Network Access Server Package for Media Gateway Control Protocol feature, use the following commands beginning in global configuration mode:
Configuring Dialer Interfaces and Routing
This set of tasks configures dial-on-demand routing (DDR) on a dialer interface that is under external call control by MGCP.
DDR refers to a collection of Cisco features that allows two or more Cisco routers to establish a dynamic connection over simple dial-up facilities to route packets and exchange routing updates on an as-needed basis. DDR is used for low-volume, periodic network connections over the PSTN or an ISDN. A connection is automatically established whenever interesting traffic is detected; during configuration you define what constitutes interesting traffic.
ISDN B channels, synchronous serial interfaces, and asynchronous interfaces can all be converted to dialer interfaces using dialer interface configuration commands.
DDR provides several functions. First, DDR spoofs, or pretends, that there are established configured routes to provide the image of full-time connectivity using the dialer interfaces. When the routing table forwards a packet to a dialer interface, DDR filters out the interesting packets for establishing, maintaining, and releasing switched connections. Internetworking is achieved over the DDR-maintained connection using PPP or other WAN encapsulation techniques.
The encapsulation methods available depend on the physical interface being used. Cisco supports PPP, High-Level Data Link Control (HDLC), Serial Line Internet Protocol (SLIP), and X.25 data-link encapsulations for DDR. PPP is the recommended encapsulation method because it supports multiple protocols and is used for synchronous, asynchronous, or ISDN connections. In addition, PPP performs address negotiation and authentication, and it is interoperable with different vendors.
There are two ways of setting up addressing on dialer interfaces:
•
•
DDR uses manually entered static network protocol routes. This eliminates the use of a routing protocol that broadcasts routing updates across the DDR connection, causing unnecessary connections.
Similar to the function provided by an Address Resolution Protocol (ARP) table, dialer map statements translate next-hop protocol addresses to telephone numbers. Without statically configured dialer maps, DDR call initiation cannot occur. When the routing table points at a dialer interface, and the next-hop address is not found in a dialer map, the packet is dropped.
Authentication in DDR network design provides two functions: security and dialer state. As most DDR networks connect to the PSTN, it is imperative that a strong security model be implemented to prevent unauthorized access to sensitive resources. Authentication also allows the DDR code to keep track of what sites are currently connected and provides for building of Multilink PPP bundles.
In summary, the following main tasks are involved in configuring the dialer interface and routing:
•
•
•
For more information, refer to the following documentation:
•
•
For MGCP NAS, configuration of dialer interfaces entails the use of the dialer extsig command in interface configuration mode, which enables the External Call Service Provider (XCSP) subsystem to provide an interface between the Cisco IOS software and the MGCP protocol. The XCSP subsystem enables services such as modem call setup and teardown for the dialer interface.
To configure the dialer interface and routing, use the following commands beginning in global configuration mode:
Step 1
Router(config)# interface dialer-name
Enters interface mode for the dialer interface.
Step 2
Router(config-if)# ip unnumbered interface-number
or
Router(config-if)# ip address ip-address subnet-mask [secondary]
Enables IP processing on the dialer interface, configures the dialer interface not to have an explicit IP address, and assigns the IP address of the loopback interface instead. This command helps conserve IP addresses.
The argument is as follows:
•
or
Sets a primary or secondary IP address for an interface.
The keywords and arguments are as follows:
•
•
•
Step 3
Router(config-if)# encapsulation ppp
Sets encapsulation type for PPP.
Step 4
Router(config-if)# dialer in-band [no-parity | odd-parity]
Specifies that dial-on-demand routing (DDR) is to be supported. The in-band keyword specifies that the same interface that sends the data performs call setup and teardown operations between the router and an external dialing device such as a modem.
The keywords are as follows:
•
•
By default, no parity is applied to the dialer string.
Step 5
Router(config-if)# dialer idle-timeout seconds [inbound | either]
Specifies the duration of idle time before a line is disconnected.
The keywords and arguments are as follows:
•
•
•
The default direction is outbound, and the default idle time is 120 seconds.
Step 6
Router(config-if)# dialer map protocol next-hop-address [name host-name] [dial-string[:isdn-subaddress]]
Configures a serial interface to make digital calls or to accept incoming calls from a specified location and to authenticate if so configured.
The keywords and arguments are as follows:
•
•
•
•
Step 7
Router(config-if)# dialer extsig
Specifies an interface for the initiation and termination of digital calls for external signaling protocols. Only one dialer with external signaling per NAS is permitted.
Step 8
Router(config-if)# dialer-group number
Controls access by configuring an interface to belong to a specific dialing group.
The argument is as follows:
•
Step 9
Router(config-if)# no cdp enable
Disables the Cisco Discovery Protocol (CDP) on the interface.
Step 10
Router(config-if)# ppp authentication chap
Enables Challenge Handshake Authentication Protocol (CHAP) authentication on the interface.
Step 11
Router(config-if)# exit
Exits interface configuration mode.
Step 12
Router(config)# dialer list number protocol protocol-name {permit | deny [list access-list-number | access-group]}
Defines a DDR dialer list for dialing by protocol or by a combination of a protocol and a previously defined access list. Each dialer interface can have only one dialer group, but the same dialer list can be assigned to multiple interfaces (using the dialer-group command).
The keywords and arguments are as follows:
•
•
•
•
Step 13
Router(config)# ip route prefix mask {ip-address | interface-type interface-number} [distance] [tag tag] [permanent]
Establishes a static route. Because you do not want dynamic routing protocols running across the DDR links, you manually configure static routes.
The keywords and arguments are as follows:
•
•
•
•
•
•
•
Verifying the Network Access Server Package for Media Gateway Control Protocol Feature
Use the following commands to verify configuration settings for all platforms and protocols:
Step 1
Router# show running-configStep 2
Router# show mgcp nas {dump slot port channel | info}
Troubleshooting Tips
For general troubleshooting information, refer to the following documents:
•
•
•
In addition, a number of show and debug commands are useful for troubleshooting the Network Access Server Package for Media Gateway Control Protocol feature. These commands are listed in the following sections:
•
MGCP Troubleshooting
The commands in this section help identify problems with MGCP operation and the MGCP application. In addition, information on configuring MGCP can be found in the following documents:
•
•
To display detailed information on the MGCP application and operations, use the following commands in privileged EXEC mode:
To debug MGCP calls, events, and operations, use the following commands in privileged EXEC mode:
Router# debug mgcp all
Enables all MGCP debugs. Refer to the debug mgcp command.
Router# debug mgcp events
Enables MGCP events debugging, which shows information such as the following: whether the router is detected, the MGCP event that initiates a call, and the reset of an controller that is being serviced by MGCP.
Router# debug mgcp packets
Enables debugging of MGCP packets. Useful for displaying contents of NTFY, CRCX, DLCX, and other packets.
Router# debug mgcp parser
Enables debugging of MGCP parser and builder. Useful to determine whether NTFY, CRCX, and other packets have the format that the router expects.
Router# debug mgcp nas
Enables debugging for MGCP data channels and events.
Router# debug xcsp {all | cot | event}
Enables reporting of the exchange of signaling information between the MGCP protocol stack and end applications, such as call switching module (CSM) and dialer. The keywords are as follows:
•
•
•
Router# debug cdapi {detail | events}
Displays real-time information about the call distributor application programming interface (CDAPI). The keywords are as follows:
•
•
Controller Troubleshooting
The commands in this section can be helpful in finding sources of problems with call connections and switching. The call switching module (CSM) associated with a controller contains digit collection logic that processes incoming calls for automatic number information (ANI) and dialed number identification service (DNIS) digits.
To display information on controller and CSM configuration and operation, use the following commands in privileged EXEC mode.
Dialer Interface and Routing Troubleshooting
This section contains commands for debugging and displaying information on DDR. Additional configuration and troubleshooting help can be found in the following documents:
•
•
•
•
To obtain information on dialer interfaces, routing configuration, and routing operations, use the following commands in privileged EXEC mode.
To debug dialer and authorization or to clear in-progress calls, use the following commands in privileged EXEC mode.
Configuration Examples
This section provides the following configuration example:
•
Network Access Server Package for MGCP Example
This example configures the Network Access Server Package for Media Gateway Control Protocol feature on a Cisco AS5400:
Note
!version 12.2no service single-slot-reload-enableservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname 54iwo!no boot startup-testlogging rate-limit console 10 except errors!resource-pool disable!resource-pool profile service user1sample!voice-fastpath enableip subnet-zeroip host 54ccxv 172.18.16.25!no ip dhcp-client network-discoveryisdn switch-type primary-ni!fax interface-type modemmta receive maximum-recipients 0!controller T1 7/0framing esfextsig mgcpguard-timer 10 on-expiry rejectlinecode b8zsds0-group 1 timeslots 1-24 type none service mgcp!controller T1 7/1framing esflinecode amipri-group timeslots 1-24!controller T1 7/2framing sflinecode ami!controller T1 7/3framing sflinecode ami!controller T1 7/4framing sflinecode ami!controller T1 7/5framing sflinecode ami!controller T1 7/6framing sflinecode ami!controller T1 7/7framing sflinecode ami!interface Loopback0ip address 172.16.0.3 255.255.255.0!interface FastEthernet0/0ip address 172.18.184.183 255.255.255.0duplex autospeed auto!interface FastEthernet0/1no ip addressshutdownduplex autospeed auto!interface Serial0/0no ip addressshutdownclockrate 2000000!interface Serial0/1no ip addressshutdownclockrate 2000000!interface Serial7/1:23no ip addressencapsulation pppdialer rotary-group 9dialer-group 1isdn switch-type primary-niisdn incoming-voice modemno cdp enable!interface Async1/00ip unnumbered Loopback0dialer in-banddialer map ip 172.23.0.1 234567dialer-group 1!interface Async1/01ip address 10.17.1.1 255.255.255.0encapsulation pppdialer in-banddialer map ip 10.17.1.2 22222dialer-group 1!interface Async1/02no ip address!interface Async1/03no ip address!interface Async1/04no ip address!interface Async1/05no ip address!interface Async3/102no ip address!interface Async3/103no ip address!interface Async3/104no ip address!interface Async3/105no ip address!interface Async3/106no ip address!interface Async3/107no ip address!interface Group-Async0no ip addressno group-range!interface Dialer1ip unnumbered Loopback0encapsulation pppdialer in-banddialer idle-timeout 222222dialer map ip 172.16.0.1 name 53bxbv 1000dialer extsigdialer-group 1no cdp enableppp authentication chapppp direction dedicated!interface Dialer9ip address 10.1.1.1 255.255.255.0encapsulation pppdialer in-banddialer map ip 10.1.1.2 23456dialer-group 1no cdp enable!ip classlessip route 0.0.0.0 0.0.0.0 172.18.184.1ip route 172.16.0.1 255.255.255.255 Dialer1ip route 172.23.0.1 255.255.255.255 Async1/00no ip http server!dialer-list 1 protocol ip permit!call rsvp-sync!voice-port 7/0:1!voice-port 7/1:D!mgcpmgcp call-agent 172.18.64.242 service-type mgcp version 1.0no mgcp timer receive-rtcp!mgcp profile defaultmax2 retries 5!line con 0exec-timeout 0 0logging synchronousline aux 0logging synchronousline vty 0 4password mangologinline 1/00 1/107no flush-at-activationmodem InOutline 3/00 3/107no flush-at-activationmodem InOut!scheduler allocate 10000 400endCommand Reference
This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
Modified Commands
debug mgcp
To enable debug traces for Media Gateway Control Protocol (MGCP) errors, events, media, packets, parser, and Call Admission Control (CAC), use the debug mgcp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp [all | errors [endpoint endpoint-name] | events [endpoint endpoint-name] | media [endpoint endpoint-name] | nas | packets [endpoint endpoint-name | input-hex] | parser | src | voipcac]
no debug mgcp [all | errors | events | media | nas | packets | parser | src | voipcac]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.1(1)T
This command was introduced.
12.1(3)T
Additional information was displayed for the gateways.
12.1(5)XM
The output was modified to display parameters for the MGCP CAS PBX and AAL2 PVC features.
12.2(2)T
This command was integrated into Cisco IOS Release 12.2(2)T.
12.2(2)XA
The media keyword was added. The endpoint endpoint-name keyword and argument were added as options for the errors, events, media, and packets keywords. The input-hex keyword option was added for the packets keyword.
12.2(2)XB
The nas keyword and the src and voipcac keywords were added. (Refer to MGCP VoIP Call Admission Control in Cisco IOS Release 12.2(2)XB.)
12.2(11)T
The command was integrated into Cisco IOS Release 12.2(11)T and it was implemented on the Cisco AS5850.
Usage Guidelines
There is always a performance penalty when using debug commands.
Examples
The following is sample output from the debug mgcp errors, debug mgcp events, debug mgcp media, debug mgcp nas, debug mgcp packets, debug mgcp parser, and debug mgcp src commands and keywords. The debug mgcp all command and keyword would show a compilation of all this output, including the debug mgcp voipcac command and keyword output. Note that using the debug mgcp all command and keyword may severely impact network performance.
The following example illustrates the output from the debug mgcp errors command and keyword:
Router# debug mgcp errorsUnknown network interface typeThe following example illustrates the output from the debug mgcp events command and keyword:
Router# debug mgcp eventsMedia Gateway Control Protocol events debugging is onRouter#1w1d: MGC stat - 172.19.184.65, total=44, succ=7, failed=211w1d: MGCP msg 11w1d: remove_old_under_specified_ack:1w1d: MGC stat - 172.19.184.65, total=44, succ=8, failed=211w1d: updating lport with 2427setup_ipsocket: laddr=172.29.248.193, lport=2427,faddr=172.19.184.65, fport=24271w1d: enqueue_ack: ackqhead=0, ackqtail=0, ackp=1DC1D38, msg=21A037CThe following example illustrates the output from the debug mgcp media command and keyword:
Router# debug mgcp mediaMedia Gateway Control Protocol media events debugging is onRouter#DYNAMIC payload typeDYNAMIC payload type*Jan 1 03:02:13.159:mgcp_verify_supp_reqdet_ev*Jan 1 03:02:13.159:mgcp_verify_supp_signal_ev*Jan 1 03:02:13.159:process_request_ev- callp 635368FC, voice_if 6353C1F8*Jan 1 03:02:13.159:process_detect_ev- callp 635368FC, voice_if 6353C1F8*Jan 1 03:02:13.159:process_signal_ev- callp 635368FC, voice_ifp 6353C1F8*Jan 1 03:02:13.159:mgcp_process_quarantine_mode- callp 635368FC, voice_if 6353C1F8*Jan 1 03:02:13.159:mgcp_process_quarantine_mode- new q mode:process=0, loop=0*Jan 1 03:02:13.179:process_deferred_request_events*Jan 1 03:02:13.479:mgcp_verify_supp_reqdet_ev*Jan 1 03:02:13.479:mgcp_verify_supp_signal_ev*Jan 1 03:02:13.479:process_request_ev- callp 6353BCCC, voice_if 638C3094*Jan 1 03:02:13.479:process_detect_ev- callp 6353BCCC, voice_if 638C3094*Jan 1 03:02:13.479:process_signal_ev- callp 6353BCCC, voice_ifp 638C3094*Jan 1 03:02:13.479:mgcp_process_quarantine_mode- callp 6353BCCC, voice_if 638C3094*Jan 1 03:02:13.479:mgcp_process_quarantine_mode- new q mode:process=0, loop=0*Jan 1 03:02:13.499:process_deferred_request_events*Jan 1 03:02:13.827:mgcp_verify_supp_reqdet_ev*Jan 1 03:02:13.827:mgcp_verify_supp_signal_ev*Jan 1 03:02:13.827:process_request_ev- callp 635368FC, voice_if 6353C1F8*Jan 1 03:02:13.827:process_detect_ev- callp 635368FC, voice_if 6353C1F8*Jan 1 03:02:13.827:process_signal_ev- callp 635368FC, voice_ifp 6353C1F8*Jan 1 03:02:13.827:mgcp_process_quarantine_mode- callp 635368FC, voice_if 6353C1F8*Jan 1 03:02:13.827:mgcp_process_quarantine_mode- new q mode:process=0, loop=0*Jan 1 03:02:13.831:process_deferred_request_events*Jan 1 03:02:23.163:mgcp_cr_and_init_evt_node:$$$ the node pointer 63520B14*Jan 1 03:02:23.163:mgcp_insert_node_to_preprocess_q:$$$enq to preprocess, qhead=63520B14, qtail=63520B14, count 1, evtptr=63520B14*Jan 1 03:02:23.479:mgcp_cr_and_init_evt_node:$$$ the node pointer 63520BA8*Jan 1 03:02:23.479:mgcp_insert_node_to_preprocess_q:$$$enq to preprocess, qhead=63520BA8, qtail=63520BA8, count 1, evtptr=63520BA8The following example displays output for the debug mgcp nas command and keyword, with the debug mgcp packets command and keyword enabled as well:
Router# debug mgcp nasMedia Gateway Control Protocol nas pkg events debugging is onRouter# debug mgcp packetsMedia Gateway Control Protocol packets debugging is onRouter#01:49:14:MGCP Packet received -CRCX 58 S7/DS1-0/23 MGCP 1.0X:57M:nas/dataC:3L:b:64, nas/bt:modem, nas/cdn:3000, nas/cgn:1000mgcp_parse_conn_mode :string past nas = datamgcp_chq_nas_pkg:Full string:nas/bt:modemmgcp_chq_nas_pkg:string past slash:btmgcp_chq_nas_pkg:string past colon:modemmgcp_chq_nas_pkg:Full string:nas/cdn:3000mgcp_chq_nas_pkg:string past slash:cdnmgcp_chq_nas_pkg:string past colon:3000mgcp_chq_nas_pkg:Full string:nas/cgn:1000c5400#mgcp_chq_nas_pkg:string past slash:cgnmgcp_chq_nas_pkg:string past colon:1000CHECK DATA CALL for S7/DS1-0/23mgcpapp_xcsp_get_chan_cb -Found - Channel state IdleCRCX Recvmgcpapp_endpt_is_data:endpt S7/DS1-0/23, slot 7, port 0 chan 23mgcpapp_data_call_hnd:mgcpapp_xcsp_get_chan_cb -Found - Channel state Idlebw=64, bearer=E1,cdn=3000,cgn=1000The following example illustrates the output from the debug mgcp packets command and keyword:
Router# debug mgcp packetsMedia Gateway Control Protocol packets debugging is onRouter#1w1d: MGCP Packet received -DLCX 408631346 * MGCP 0.11w1d: send_mgcp_msg, MGCP Packet sent --->1w1d: 250 408631346<---The following example illustrates the output from the debug mgcp parser command and keyword:
Router# debug mgcp parserMedia Gateway Control Protocol parser debugging is onRouter#1w1d: -- mgcp_parse_packet() - call mgcp_parse_header- mgcp_parse_header()- Request Verb FOUND DLCX- mgcp_parse_packet() - out mgcp_parse_header- SUCCESS: mgcp_parse_packet()- MGCP Header parsing was OK- mgcp_val_mandatory_parms()- SUCCESS: mgcp_parse_packet()- END of Parsing1w1d: -- mgcp_build_packet()-1w1d: - mgcp_estimate_msg_buf_length() - 87 bytes needed for header- mgcp_estimate_msg_buf_length() - 87 bytes needed after checking parameter lines- mgcp_estimate_msg_buf_length() - 87 bytes needed after checking SDP lines- SUCCESS: MGCP message building OK- SUCCESS: END of buildingThe following example illustrates the output from the debug mgcp src command and keyword:
Router# debug mgcp srcMedia Gateway Control Protocol System Resource Check CAC debugging is onRouter#00:14:08: setup_indication: Set incoming_call flag=TRUE in voice_if00:14:08: send_mgcp_msg, MGCP Packet sent --->00:14:08: NTFY 11 aaln/S1/1@Router MGCP 0.1N: emu@[1.4.173.1]:51665X: 35O: hd<---00:14:08: MGCP Packet received -200 11 hello00:14:08: MGCP Packet received -RQNT 42 aaln/S1/1 MGCP 0.1N: emu@[1.4.173.1]:51665X: 41R: D/[0-9*#T](d), huS: dlD: (911|xxxx)00:14:08: send_mgcp_msg, MGCP Packet sent --->00:14:08: 200 42 OK<---00:14:12: send_mgcp_msg, MGCP Packet sent --->00:14:12: NTFY 12 aaln/S1/1@Router MGCP 0.1N: emu@[1.4.173.1]:51665X: 41O: D/2222<---00:14:12: MGCP Packet received -200 12 phone-number ok00:14:12: MGCP Packet received -CRCX 44 aaln/S1/1 MGCP 0.1N: emu@[1.4.173.1]:51665C: 3X: 43R: hu(n)M: recvonlyL: a:G.711u,p:5,e:off,s:off00:14:12: mgcp_setup_conn_check_system_resource: System resource check successful00:14:12: mgcp_voice_crcx: System resource is available00:14:12: mgcp_set_call_counter_control: Incoming call with 1 network leg, flag=FALSE00:14:12: send_mgcp_msg, MGCP Packet sent --->00:14:12: 200 44I: 4v=0o=- 4 0 IN IP4 1.4.120.1s=Cisco SDP 0c=IN IP4 1.4.120.1t=0 0m=audio 16404 RTP/AVP 0<---00:14:13: MGCP Packet received -MDCX 48 aaln/S1/1 MGCP 0.1N: emu@[1.4.173.1]:51665C: 3I: 4X: 47M: recvonlyR: huL: a:G.711u,p:5,e:off,s:offv=0o=- 4 0 IN IP4 1.4.120.3s=Cisco SDP 0c=IN IP4 1.4.120.3t=0 0m=audio 16384 RTP/AVP 000:14:13: mgcp_modify_conn_check_system_resource: System resource check successful00:14:13: mgcp_modify_connection: System resource is available00:14:13: send_mgcp_msg, MGCP Packet sent --->00:14:13: 200 48 OK<---00:14:20: MGCP Packet received -MDCX 52 aaln/S1/1 MGCP 0.1N: emu@[1.4.173.1]:51665C: 3I: 4X: 51M: sendrecvR: huL: a:G.711u,p:5,e:off,s:off00:14:20: mgcp_modify_conn_check_system_resource: System resource check successful00:14:20: mgcp_modify_connection: System resource is available00:14:20: send_mgcp_msg, MGCP Packet sent --->00:14:20: 200 52 OK<---00:14:34: MGCP Packet received -DLCX 56 aaln/S1/1 MGCP 0.1X: 55N: emu@[1.4.173.1]:51665C: 3I: 4R: hu00:14:34: send_mgcp_msg, MGCP Packet sent --->00:14:34: 250 56P: PS=1382, OS=110180, PR=1378, OR=109936, PL=63484, JI=520, LA=2<---00:14:36: mgcp_reset_call_direction: Reseting incoming_call flag=FALSE in voice_if00:14:36: send_mgcp_msg, MGCP Packet sent --->00:14:36: NTFY 13 aaln/S1/1@tlkrgw1 MGCP 0.1N: emu@[1.4.173.1]:51665X: 55O: hu<---debug xcsp
To display the debug messages for the External Control Service Provider (XCSP) subsystem, use the debug xcsp command in privileged EXEC mode. To turn off debug mode, use the no form of this command.
debug xcsp {all | cot | event}
no debug xcsp {all | cot | event}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(2)XB
This command was introduced.
12.2(11)T
The command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco AS5850.
Usage Guidelines
This command is used with the Network Access Server Package for Media Gateway Control Protocol feature. The XCSP subsystem is not configured directly, but information about it may be useful in troubleshooting. The debug xcsp command is used to display the exchange of signaling information between the MGCP protocol stack and end applications such as call switching module (CSM) or dialer.
The cot keyword is not used with the Network Access Server Package for MGCP feature.
Examples
The following examples show output for the debug xcsp all command and keyword and the debug xcsp event command and keyword:
Router# debug xcsp allxcsp all debugging is onRouter# debug xcsp eventxcsp events debugging is on01:49:14:xcsp_call_msg:Event Call Indication , channel state = Idle forslot port channel 7c5400# 0 2301:49:14:xcsp_process_sig_fsm:state/event Idle / Call Indication01:49:14:xcsp_incall:01:49:14:xcsp_incall CONNECT_IND:cdn=3000 cgn=100001:49:14:xcsp:START guard TIMER01:49:14:xcsp_fsm:slot 7 port 0 chan 23 oldstate = Idle newstate= Connectionin progress mgcpapp_process_mgcp_msg PROCESSED NAS PACKAGE EVENT01:49:14:Received message on XCSP_CDAPI01:49:14:process_cdapi_msg :slot/port/channel 7/0/2301:49:14: process_cdapi_msg:new slot/port/channel 7/0/2301:49:14:c5400#Received CONN_RESP:callid=0x701601:49:14:process_cdapi:Event CONN_RESP, channel state = 8 for slot portchannel 7 0 2301:49:14:xcsp_process_sig_fsm:state/event Connection in progress / In Callacceptmgcpapp_xcsp_alert:mgcpapp_xcsp_get_chan_cb -Found - Channel state Connection in progress200 58 AlertI:630AED90<---:Ack send SUCCESSFUL01:49:14:xcsp_fsm:slot 7 pc5400#ort 0 chan 23 oldstate = Connection in progress newstate= Connection inprogress01:49:14:Received message on XCSP_CDAPI01:49:14:process_cdapi_msg :slot/port/channel 7/0/2301:49:14: process_cdapi_msg:new slot/port/channel 7/0/2301:49:14: Received CALL_CONN:callid=0x701601:49:14:process_cdapi:Event CONN_, channel state = 8 for slot port channel 70 2301:49:14:xcsp_process_sig_fsm:state/event Connection in progress / in callconnectmgcpapp_xcsp_connect:mgcpapp_xcc5400#sp_get_chan_cb -Found - Channel state In Use01:49:14:STOP TIMER01:49:14:xcsp_fsm:slot 7 port 0 chan 23 oldstate = Connection in progressnewstate=In Usec5400#01:50:23:Received message on XCSP_CDAPI01:50:23:process_cdapi_msg :slot/port/channel 7/0/2301:50:23: process_cdapi_msg:new slot/port/channel 7/0/2301:50:23: Received CALL_DISC_REQ:callid=0x701601:50:23:process_cdapi:Event DISC_CONN_REQ, channel state = 7 for slot portchannel 7 0 2301:50:23:xcsp_process_sig_fsm:state/event In Use / release Requestmgcpapp_xcsp_disconnectmgcpapp_xcsp_get_chan_cb -Fouc5400#nd - Channel state In Use01:50:23:send_mgcp_msg, MGCP Packet sent --->01:50:23:RSIP 1 *@c5400 MGCP 1.0RM:restart.DLCX 4 S7/DS1-0/23 MGCP 1.0C:3I:630AED90E:801 /NAS User request<---01:50:23:xcsp_fsm:slot 7 port 0 chan 23 oldstate = In Use newstate=OutRelease in progressxcsp_restart Serial7/0:22 vc = 22xcsp_restart Put idb Serial7/0:22 in down state01:50:23:MGCP Packet received -200 4 byeData call ack received callp=0x62AEEA70mgcpapp_xcspc5400#_ack_recv:mgcpapp_xcsp_get_chan_cb -Found - Channel state Out Release inprogressmgcpapp_xcsp_ack_recv ACK 200 rcvd:transaction id = 4 endpt=S7/DS1-0/2301:50:23:xcsp_call_msg:Event Release confirm , channel state = Out Release inprogress for slot port channel 7 0 2301:50:23:xcsp_process_sig_fsm:state/event Out Release in progress/ Releaseconfirm01:50:23:STOP TIMER01:50:23:xcsp_fsm:slot 7 port 0 chan 23 oldstate = Out Release in progressnewstate= IdleRelated Commands
Displays the status of a router port under the control of the XCSP subsystem.
Displays the status of a router slot under the control of the XCSP subsystem.
dialer extsig
To configure an interface to initiate and terminate calls using an external signaling protocol, use the dialer extsig command in interface configuration mode. To discontinue control of the interface by the external signaling protocol, use the no form of this command.
dialer extsig
no dialer extsig
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
12.2(2)XB
This command was introduced.
12.2(11)T
The command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco AS5850.
Usage Guidelines
This command is used with the Network Access Server Package for Media Gateway Control Protocol feature.
•
•
Examples
The following example shows output using the dialer extsig command after first specifying the dialer interface to be configured:
Router(config)# interface Dialer1Router(config-if)# dialer extsigRelated Commands
extsig mgcp
To configure external signaling control by Media Gateway Control Protocol (MGCP) for a T1 or E1 trunk controller card, use the extsig mgcp command in controller configuration mode. To discontinue MGCP control for this controller, use the no form of this command.
extsig mgcp
no extsig mgcp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Controller configuration
Command History
12.2(2)XB
This command was introduced.
12.2(11)T
The command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco AS5850.
Usage Guidelines
For T3 lines, each logical T1 trunk controller card needs to be configured using the extsig mgcp command.
Examples
The following example shows MGCP signaling control being configured for T1 controller 7/0:
controller T1 7/0framing esfextsig mgcpguard-timer 10 on-expiry rejectlinecode b8zsds0-group 1 timeslots 1-24 type none service mgcpRelated Commands
Configures an interface to initiate and terminate calls using an external signaling protocol.
guard-timer
To set a guard timer to accept or reject a call if the authentication, authorization, and accounting (AAA) server fails to respond to a preauthentication request, use the guard-timer command in controller configuration mode. To remove the guard-timer command from your configuration file, use the no form of this command.
guard-timer milliseconds [on-expiry {accept | reject}]
no guard-timer milliseconds [on-expiry {accept | reject}]
Syntax Description
Defaults
The call is rejected.
Command Modes
Controller configuration
Command History
12.2(2)XB
This command was introduced.
12.2(11)T
The command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco AS5850.
Usage Guidelines
Use the guard-timer command to set a guard timer for the number of milliseconds before a call is rejected if AAA has not responded to a preauthentication request when the timer expires. You can also set the guard timer to accept or reject a call if AAA fails to respond to a preauthentication request.
Examples
The following example shows how to set a guard timer to expire after 10 milliseconds and reject the call if AAA has not responded within that time.
controller t1 7/0guard-timer 10 on-expiry rejectRelated Commands
show mgcp
To display values for Media Gateway Control Protocol (MGCP) parameters, use the show mgcp command in privileged EXEC mode.
show mgcp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.1(1)T
The show mgcp command was introduced on the Cisco AS5300.
12.1(3)T
The show mgcp command output was updated to display additional gateway and platform information.
12.1(5)XM
The show mgcp command output was updated to display additional gateway and platform information.
12.2(2)T
The show mgcp command was implemented on the Cisco 7200 series and this command was integrated into Cisco IOS Release 12.2(2)T.
12.2(2)XA
The profile keyword was added to the show mgcp command.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(2)XB
The output for the show mgcp command was enhanced to display the status of MGCP System Resource Check (SRC) Call Admission Control (CAC) and Service Assurance Agent (SA Agent) CAC. (Refer to the Cisco IOS Release 12.2(2) XB online document MGCP VoIP Call Admission Control.)
In addition, the nas dump slot port chan and nas info keywords and arguments were added to the show mgcp command. Because the number of keywords increased, the command reference for the show mgcp command was separated into the following commands:
•
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.2(11)T
This command was implemented on the Cisco AS5850.
Usage Guidelines
The show mgcp command provides administrative high-level information about the values configured for MGCP parameters on the router. For more specific types of information, see the show mgcp connection, show mgcp endpoint, show mgcp nas, show mgcp profile, and show mgcp statistics commands.
Examples
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.18.195.147 2300 Initial protocol service is SGCP 1.5MGCP block-newcalls DISABLEDMGCP send RSIP for SGCP is ENABLEDMGCP quarantine mode discard/stepMGCP quarantine of persistent events is ENABLEDMGCP dtmf-relay for VoIP disabled for all codec typesMGCP dtmf-relay voaal2 codec allMGCP voip modem passthrough mode: NSE, codec: g711ulaw, redundancy: DISABLED,MGCP voaal2 modem passthrough mode: NSE, codec: g711ulawMGCP TSE payload: 100MGCP T.38 Named Signalling Event (NSE) response timer: 200MGCP Network (IP/AAL2) Continuity Test timer: 3000MGCP 'RTP stream loss' timer: 2MGCP request timeout 500MGCP maximum exponential request timeout 4000MGCP gateway port: 2427, MGCP maximum waiting delay 3000MGCP restart delay 0, MGCP vad DISABLEDMGCP rtrcac DISABLEDMGCP system resource check DISABLEDMGCP xpc-codec: DISABLED, MGCP persistent hookflash: DISABLEDMGCP persistent offhook: ENABLED, MGCP persistent onhook: DISABLEDMGCP piggyback msg DISABLED, MGCP endpoint offset DISABLEDMGCP simple-sdp DISABLEDMGCP undotted-notation DISABLEDMGCP codec type g711ulaw, MGCP packetization period 20MGCP JB threshold lwm 30, MGCP JB threshold hwm 150MGCP LAT threshold lmw 150, MGCP LAT threshold hwm 300MGCP PL threshold lwm 1000, MGCP PL threshold hwm 10000MGCP CL threshold lwm 1000, MGCP CL threshold hwm 10000MGCP playout mode is adaptive 60, 4, 200 in msecMGCP IP ToS low delay disabled, MGCP IP ToS high throughput disabledMGCP IP ToS high reliability disabled, MGCP IP ToS low cost disabledMGCP IP RTP precedence 5, MGCP signaling precedence: 3MGCP default package: line-packageMGCP supported packages: gm-package dtmf-package trunk-package line-packagehs-package atm-package ms-package dt-package res-packagemt-packageTable 1 describes the significant fields shown in the display.
Related Commands
show mgcp connection
To display information for active connections that are controlled by Media Gateway Control Protocol (MGCP), use the show mgcp connection command in privileged EXEC mode.
show mgcp connection
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.1(1)T
The show mgcp command was introduced on the Cisco AS5300.
12.1(3)T
The show mgcp command output was updated to display additional gateway and platform information.
12.1(5)XM
The show mgcp command output was updated to display additional gateway and platform information.
12.2(2)T
The show mgcp command was implemented on the Cisco 7200 series and this command was integrated into Cisco IOS Release 12.2(2)T.
12.2(2)XA
The profile keyword was added to the show mgcp command.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(2)XB
The output for the show mgcp command was enhanced to display the status of MGCP System Resource Check (SRC) Call Admission Control (CAC) and Service Assurance Agent (SA Agent) CAC. (Refer to the Cisco IOS Release 12.2(2) XB online document MGCP VoIP Call Admission Control.)
In addition, the nas dump slot port chan and nas info keywords and arguments were added to the show mgcp command. Because the number of keywords increased, the command reference for the show mgcp command was separated into the following commands:
•
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.2(11)T
This command was implemented on the Cisco AS5850.
The following is sample output from the show mgcp connection command for Voice over IP (VoIP) connections:
Router# show mgcp connectionEndpoint Call_ID(C) Conn_ID(I) (P)ort (M)ode (S)tate (C)odec (E)vent[SIFL] (R)esult[EA]1. S0/DS1-0/1 C=103,23,24 I=0x8 P=16586,16634 M=3 S=4,4 C=5 E=2,0,0,2 R=0,02. S0/DS1-0/2 C=103,25,26 I=0x9 P=16634,16586 M=3 S=4,4 C=5 E=0,0,0,0 R=0,03. S0/DS1-0/3 C=101,15,16 I=0x4 P=16506,16544 M=3 S=4,4 C=5 E=2,0,0,2 R=0,04. S0/DS1-0/4 C=101,17,18 I=0x5 P=16544,16506 M=3 S=4,4 C=5 E=0,0,0,0 R=0,05. S0/DS1-0/5 C=102,19,20 I=0,6 P=16572,16600 M=3 S=4,4 C=5 E=2,0,0,2 R=0,06. S0/DS1-0/6 C=102,21,22 I=0x7 P=16600,16572 M=3 S=4,4 C=5 E=0,0,0,0 R=0,0Total number of active calls 6Table 2 describes the significant fields shown in the display.
The following is sample output from the show mgcp connection command for VoAAL2 connections:
Router# show mgcp connectionEndpoint Call_ID(C) Conn_ID(I)(V)cci/cid (M)ode (S)tate (C)odec (E)vent[SIFL] (R)esult[EA]1.aaln/S1/1 C=1,11,12 I=0x2 V=2/10 M=3 S=4,4 C=1 E=3,0,0,3 R=0,0Total number of active calls 1Table 3 describes significant fields in the display.
Related Commands
show mgcp endpoint
To display information for endpoints controlled by Media Gateway Control Protocol (MGCP), use the show mgcp endpoint command in privileged EXEC mode.
show mgcp endpoint
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.1(1)T
The show mgcp command was introduced on the Cisco AS5300.
12.1(3)T
The show mgcp command output was updated to display additional gateway and platform information.
12.1(5)XM
The show mgcp command output was updated to display additional gateway and platform information.
12.2(2)T
The show mgcp command was implemented on the Cisco 7200 series and this command was integrated into Cisco IOS Release 12.2(2)T.
12.2(2)XA
The profile keyword was added to the show mgcp command.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(2)XB
The output for the show mgcp command was enhanced to display the status of MGCP System Resource Check (SRC) Call Admission Control (CAC) and Service Assurance Agent (SA Agent) CAC. (Refer to the Cisco IOS Release 12.2(2) XB online document MGCP VoIP Call Admission Control.)
In addition, the nas dump slot port chan and nas info keywords and arguments were added to the show mgcp command. Because the number of keywords increased, the command reference for the show mgcp command was separated into the following commands:
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.2(11)T
This command was implemented on the Cisco AS5850.
The following is sample output from the show mgcp endpoint command:
Router# show mgcp endpointENDPOINT-NAME V-PORT SIG-TYPE ADMINds1-0/1@nytnk116 0:1 fxs-gs upds1-0/2@nytnk116 0:1 fxs-gs upds1-0/3@nytnk116 0:1 fxs-gs upds1-0/4@nytnk116 0:1 fxs-gs upds1-0/5@nytnk116 0:1 fxs-gs upds1-0/6@nytnk116 0:1 fxs-gs upds1-0/7@nytnk116 0:1 fxs-gs upds1-0/8@nytnk116 0:1 fxs-gs upds1-0/9@nytnk116 0:1 fxs-gs upds1-0/10@nytnk116 0:1 fxs-gs upds1-0/11@nytnk116 0:1 fxs-gs upds1-0/12@nytnk116 0:1 fxs-gs upds1-0/13@nytnk116 0:1 fxs-gs upds1-0/14@nytnk116 0:1 fxs-gs upds1-0/15@nytnk116 0:1 fxs-gs upds1-0/16@nytnk116 0:1 fxs-gs upds1-0/17@nytnk116 0:1 fxs-gs upds1-0/18@nytnk116 0:1 fxs-gs upds1-0/19@nytnk116 0:1 fxs-gs upds1-0/20@nytnk116 0:1 fxs-gs upds1-0/21@nytnk116 0:1 fxs-gs upds1-0/22@nytnk116 0:1 fxs-gs upds1-0/23@nytnk116 0:1 fxs-gs upds1-0/24@nytnk116 0:1 fxs-gs upInterface T1 1ENDPOINT-NAME V-PORT SIG-TYPE ADMINds1-1/1@nytnk116 1:1 e&m-imd upds1-1/2@nytnk116 1:1 e&m-imd upTable 2 describes the significant fields shown in the display.
Related Commands
show mgcp nas
To display Media Gateway Control Protocol (MGCP) network access server (NAS) information for data ports, use the show mgcp nas command in privileged EXEC mode.
show mgcp nas {dump slot port channel | info}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.1(1)T
The show mgcp command was introduced on the Cisco AS5300.
12.1(3)T
The show mgcp command output was updated to display additional gateway and platform information.
12.1(5)XM
The show mgcp command output was updated to display additional gateway and platform information.
12.2(2)T
The show mgcp command was implemented on the Cisco 7200 series and this command was integrated into Cisco IOS Release 12.2(2)T.
12.2(2)XA
The profile keyword was added to the show mgcp command.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(2)XB
The output for the show mgcp command was enhanced to display the status of MGCP System Resource Check (SRC) Call Admission Control (CAC) and Service Assurance Agent (SA Agent) CAC. (Refer to the Cisco IOS Release 12.2(2) XB online document MGCP VoIP Call Admission Control.)
In addition, the nas dump slot port chan and nas info keywords and arguments were added to the show mgcp command. Because the number of keywords increased, the command reference for the show mgcp command was separated into the following commands:
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.2(11)T
This command was implemented on the Cisco AS5850.
Examples
The following is sample output from the show mgcp nas dump command:
Router# show mgcp nas dump 7 0 23Slot 7 state= UpPort 0 state= UpState Idle PortCb=0x630DE864 ss_id=0x0 handle=0x0bearer cap=Modem call_id= conn_id=Events req-4d21h:callp=0x62D137D4 - state=MGCP_CALL_IDLE - data_call NoEndpt name=S7/DS1-0/23Table 5 describes significant fields shown in the display.
The following is sample output from the show mgcp nas info command:
Router# show mgcp nas infoSlot 7 state= UpPort 0 state= UpID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID XX XX XXXX XX XX XX XXChannel State LegendNP=Not Present, OO=Out Of Service, ID=Idle, US=In UseCI=Connection in progress, RI=In Release in progressRO=Out Release in progress, DN=Down, SH=ShutdownXX=UnconfigurableTable 6 describes significant fields shown in the display.
Related Commands
show mgcp profile
To display information for Media Gateway Control Protocol (MGCP) profiles, use the show mgcp profile command in privileged EXEC mode.
show mgcp profile [profile-name]
Syntax Description
profile-name
(Optional) Name of MGCP profile for which information should be displayed; limited to 32 characters.
Defaults
If the optional profile-name argument is not used, the default profile will be displayed.
Command Modes
Privileged EXEC
Command History
12.1(1)T
The show mgcp command was introduced on the Cisco AS5300.
12.1(3)T
The show mgcp command output was updated to display additional gateway and platform information.
12.1(5)XM
The show mgcp command output was updated to display additional gateway and platform information.
12.2(2)T
The show mgcp command was implemented on the Cisco 7200 series and this command was integrated into Cisco IOS Release 12.2(2)T.
12.2(2)XA
The profile keyword was added to the show mgcp command.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(2)XB
The output for the show mgcp command was enhanced to display the status of MGCP System Resource Check (SRC) Call Admission Control (CAC) and Service Assurance Agent (SA Agent) CAC. (Refer to the Cisco IOS Release 12.2(2) XB online document MGCP VoIP Call Admission Control.)
In addition, the nas dump slot port chan and nas info keywords and arguments were added to the show mgcp command. Because the number of keywords increased, the command reference for the show mgcp command was separated into the following commands:
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.2(11)T
This command was implemented on the Cisco AS5850.
Examples
The following example shows show mgcp profile command output for the default profile and for a profile named "houston":
Router# show mgcp profileMGCP Profile defaultDescription:NoneCall-agent:none Initial protocol service is unknownTsmax timeout is 20, Tdinit timeout is 15Tdmin timeout is 15, Tdmax timeout is 600Tcrit timeout is 4, Tpar timeout is 16Thist timeout is 30, MWI timeout is 16Ringback tone timeout is 180, Ringback tone on connection timeout is 180Network congestion tone timeout is 180, Busy tone timeout is 30Dial tone timeout is 16, Stutter dial tone timeout is 16Ringing tone timeout is 180, Distinctive ringing tone timeout is 180Continuity1 tone timeout is 3, Continuity2 tone timeout is 3Reorder tone timeout is 30, Persistent package is ms-packageMax1 DNS lookup:ENABLED, Max1 retries is 4Max2 DNS lookup:ENABLED, Max2 retries is 4MGCP Profile houstonDescription:NoneCall-agent:10.9.57.6 5003 Initial protocol service is MGCP 1.0Tsmax timeout is 20, Tdinit timeout is 15Tdmin timeout is 15, Tdmax timeout is 600Tcrit timeout is 4, Tpar timeout is 16Thist timeout is 30, MWI timeout is 16Ringback tone timeout is 180, Ringback tone on connection timeout is 180Network congestion tone timeout is 180, Busy tone timeout is 30Dial tone timeout is 16, Stutter dial tone timeout is 16Ringing tone timeout is 180, Distinctive ringing tone timeout is 180Continuity1 tone timeout is 3, Continuity2 tone timeout is 3Reorder tone timeout is 30, Persistent package is ms-packageMax1 DNS lookup:ENABLED, Max1 retries is 4Max2 DNS lookup:ENABLED, Max2 retries is 6Voice port:1Table 7 describes the significant fields shown in the display.
Related Commands
show mgcp statistics
To display Media Gateway Control Protocol (MGCP) statistics regarding received and transmitted network messages, use the show mgcp statistics command in privileged EXEC mode.
show mgcp statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.1(1)T
The show mgcp command was introduced on the Cisco AS5300.
12.1(3)T
The show mgcp command output was updated to display additional gateway and platform information.
12.1(5)XM
The show mgcp command output was updated to display additional gateway and platform information.
12.2(2)T
The show mgcp command was implemented on the Cisco 7200 series and this command was integrated into Cisco IOS Release 12.2(2)T.
12.2(2)XA
The profile keyword was added to the show mgcp command.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(2)XB
The output for the show mgcp command was enhanced to display the status of MGCP System Resource Check (SRC) Call Admission Control (CAC) and Service Assurance Agent (SA Agent) CAC. (Refer to the Cisco IOS Release 12.2(2) XB online document MGCP VoIP Call Admission Control.)
In addition, the nas dump slot port chan and nas info keywords and arguments were added to the show mgcp command. Because the number of keywords increased, the command reference for the show mgcp command was separated into the following commands:
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.2(11)T
This command was implemented on the Cisco AS5850.
Examples
The following is sample output from the show mgcp statistics command for Voice over IP (VoIP) and Voice over AAL2 (VoAAL2) statistics:
Router# show mgcp statisticsUDP pkts rx 8, tx 9Unrecognized rx pkts 0, MGCP message parsing errors 0Duplicate MGCP ack tx 0, Invalid versions count 0CreateConn rx 4, successful 0, failed 0DeleteConn rx 2, successful 2, failed 0ModifyConn rx 4, successful 4, failed 0DeleteConn tx 0, successful 0, failed 0NotifyRequest rx 0, successful 4, failed 0AuditConnection rx 0, successful 0, failed 0AuditEndpoint rx 0, successful 0, failed 0RestartInProgress tx 1, successful 1, failed 0Notify tx 0, successful 0, failed 0ACK tx 8, NACK tx 0ACK rx 0, NACK rx 0IP address based Call Agents statistics:IP address 10.24.167.3, Total msg rx 8, successful 8, failed 0The following is an example of the MGCP VoIP SRC CAC portion of the show mgcp statistics command output for a gateway configured with MGCP VoIP SRC CAC:
Router# show mgcp statisticsMGCP System Resource Check Statistics:-------------------------------------Total CreateConn checked by SRC :0CreateConn accepted by SRC:0CreateConn rejected by SRC:0Total ModifyConn checked by SRC :0ModifyConn accepted by SRC:0ModifyConn rejected by SRC:0Reason Num. of requests rejected------ -------------------------cpu-5sec: 0cpu-avg: 0total-mem: 0io-mem: 0proc-mem: 0total-calls: 0Table 8 describes the significant fields shown in the display.
Related Commands
show xcsp port
To display the status of a router port under the control of the External Control Service Provider (XCSP) subsystem, use the show xcsp port command in privileged EXEC mode.
show xcsp port slot-num port-num
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(2)XB
This command was introduced.
12.2(11)T
The command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco AS5850.
Examples
The following is sample output for the show xcsp port command:
Router# show xcsp port 1 0Slot 1 configuredNumber of ports configured=1 slot state= Up===================================================Port 0 State= Up type = 5850 24 port T1Channel states0 Idle1 Idle2 Idle3 Idle4 Idle5 Idle6 Idle7 Idle8 Idle9 Idle10 Idle11 Idle12 Idle13 Idle14 Idle15 Idle16 Idle17 Idle18 Idle19 Idle20 Idle21 Idle22 Idle23 IdleTable 9 describes significant fields in the display.
Note
Table 9 show xcsp port Field Descriptions
Related Commands
show xcsp slot
To display the status of a router slot under the control of the External Control Service Provider (XCSP) subsystem, use the show xcsp slot command in privileged EXEC mode.
show xcsp slot slot-num
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(2)XB
This command was introduced.
12.2(11)T
The command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco AS5850.
Examples
The following is sample output from the show xcsp slot command:
Router# show xcsp slot 1Slot 1 configuredNumber of ports configured=1 slot state= UpTable 10 describes the significant fields in the display.
Table 10
show xcsp slot Field Descriptions
Related Commands
Glossary
AAA—authentication, authorization, and accounting. Security services for packet networks.
CSM—call switching module. Card that contains digit collection logic to process incoming calls for automatic number information (ANI) and dialed number identification service (DNIS) digits.
DDR—dial-on-demand routing.
IETF—Internet Engineering Task Force. Task force that consists of over 80 working groups responsible for developing Internet standards. The IETF operates under the auspices of the Internet Society.
ISP—Internet service provider.
MGCP—Media Gateway Control Protocol.
NAS—network access server. Communications processor that connects asynchronous devices to a LAN or WAN through network and terminal emulation software. Performs both synchronous and asynchronous routing of supported protocols.
PVC—permanent virtual circuit.
RSC—router switch controller.
SPVC—soft permanent virtual circuit.
SVC—switched virtual circuit.
VCC—virtual channel connection (used where it may be a PVC, SPVC, or SVC).
XCSP—External Call Service Provider. Subsystem that interoperates with external call protocols to provide services such as modem call setup and teardown.
