-
Cisco IOS Debug Command Reference
-
Introduction
-
Using Debug Commands
-
Conditionally Triggered Debugging
-
debug aaa accounting through debug auto-config
-
debug backhaul-session-manager session through debug channel packets
-
debug clns esis events through debug dbconn tcp
-
debug decnet adj through debug events
-
debug fax dmsp through debug gvrp
-
debug h225 asn1 through debug ip ftp
-
debug ip http all through debug ip rsvp
-
debug ip rtp header-compression through debug ipv6 icmp
-
debug ipv6 inspect through debug local-ack state
-
debug management event through debug mpls ldp bindings
-
debug mpls ldp checkpoint through debug mwi relay events
-
debug ncia circuit through debug pxf tbridge
-
debug qllc error through debug snmp sync
-
debug sntp adjust through debug tag-switching xtagatm vc
-
debug tag-template event through debug voip application vxml
-
debug voip avlist through debug vpm signaling
-
debug vpm spi through voice call debug
-
X.25 Cause and Diagnostic Codes
-
ISDN Switch Types, Codes, and Values
-
Table Of Contents
debug media resource provisioning all
debug media resource provisioning errors
debug media resource provisioning events
debug mpls checkpoint label-binding
debug mpls l2transport checkpoint
debug mpls l2transport fast-reroute
debug mpls l2transport signaling
debug management event mib
To monitor the activities of the Event MIB in real time on your routing device, use the debug management event mib command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug management event mib
no debug management event mib
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging output is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The debug management event mib command prints messages to the screen whenever the Event MIB evaluates a specified trigger. These messages are given in real-time, and are intended to be used by technical support engineers for troubleshooting purposes. Definitions for the OID (object identifier) fields can be found in the EVENT-MIB.my file, available for download from the Cisco MIB website on http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
Examples
The following is sample output from the debug management event mib command:
Router# debug management event mibEvent Process Bool: Owner aseem, Trigger 01Event Bool process: invoke eventEvent Bool process: no wildcardingEvent: OID ifEntry.10.3Event getValue abs: 69847284Event Bool process: Trigger Fired !mteSetNotifyObjects:Event execOnFiring: sending notificationEvent: OID ifEntry.10.1Event add_objects: Owner , TriggerEvent add_objects: Owner aseem, Trigger sethiEvent Found Owner: aseemEvent Found Name: sethiEvent: OID ifEntry.10.1Event: sending trap with 7 OIDsEvent: OID mteHotTrigger.0Event: OID mteHotTargetName.0Event: OID mteHotContextName.0Event: OID ifEntry.10.3Event: OID mteHotValue.0Event: OID ifEntry.10.1Event: OID ifEntry.10.1Event mteDoSets: setting oidEvent mteDoSets: non-wildcarded oidEvent: OID ciscoSyslogMIB.1.2.1.0Event Thresh Process: Owner aseem, Trigger 01Event Thresh process: invoke rising eventEvent Thresh process: invoke falling eventEvent Thresh process: no wildcardingEvent: OID ifEntry.10.3Event getValue abs: 69847284Event Existence Process: Owner aseem, Trigger 01Event Exist process: invoke eventEvent Exist process: no wildcardingEvent: OID ifEntry.10.3Event getValue abs: 69847284Event Check ExistTrigger for AbsentEvent Check ExistTrigger for ChangedRouter# no debug management event mibRelated Commands
show management event
Displays the SNMP Event values that have been configured on your routing device through the use of the Event MIB.
debug management expression
To monitor the activities of the Expression MIB in real time on your routing device, use the debug management expression command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug management expression {evaluator | mib | parser}
debug management expression {evaluator | mib | parser}
Syntax Description
evaluator
Specifies the Expression MIB evaluator.
mib
Specifies the Expression MIB SNMP operations.
parser
Specifies the Expression MIB parsing.
Command Default
By default, debugging is disabled.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example shows how to enable debugging options for Expression MIB:
Router# debug management expression mibExpression MIB SNMP operations debugging is onRelated Commands
show management expression
Displays the SNMP Expression values that have been configured on your routing device through the use of the Expression MIB.
debug mdss
To display the run-time errors and sequence of events for the multicast distributed switching services (MDSS), use the debug mdss command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mdss {all | error | event}
no debug mdss {all | error | event}
Syntax Description
all
Displays both errors and sequence of events for MDSS.
error
Displays the run-time errors for MDSS.
event
Displays the run-time sequence of events for MDSS.
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows output using the debug mdss command with the all keyword:
Router# debug mdss allmdss all debugging is onRouter# clear ip mroute *Router#01:31:03: MDSS: got MDFS_CLEARALL01:31:03: MDSS: --> mdss_flush_all_sc01:31:03: MDSS: enqueue a FE_GLOBAL_DELETE01:31:03: MDSS: got MDFS_MROUTE_ADD for (0.0.0.0, 224.0.1.40)01:31:03: MDSS: --> mdss_free_scmdb_cache01:31:03: MDSS: got MDFS_MROUTE_ADD for (0.0.0.0, 239.255.158.197)01:31:03: MDSS: got MDFS_MROUTE_ADD for (192.1.21.6, 239.255.158.197)01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,Vlan21) +Vlan2201:31:03: MDSS: -- mdss_add_oif01:31:03: MDSS: enqueue a FE_OIF_ADD (192.1.21.6, 239.255.158.197,Vlan21) +Vlan2201:31:03: MDSS: mdb (192.1.21.6, 239.255.158.197) fast_flags |MCACHE_MTU01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,Vlan21) +Vlan2301:31:03: MDSS: -- mdss_add_oif01:31:03: MDSS: enqueue a FE_OIF_ADD (192.1.21.6, 239.255.158.197,Vlan21) +Vlan2301:31:03: MDSS: mdb (192.1.21.6, 239.255.158.197) fast_flags |MCACHE_MTU01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,Vlan21) +Vlan2401:31:03: MDSS: -- mdss_add_oif01:31:03: MDSS: enqueue a FE_OIF_ADD (192.1.21.6, 239.255.158.197,Vlan21) +Vlan2401:31:03: MDSS: mdb (192.1.21.6, 239.255.158.197) fast_flags |MCACHE_MTU01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,Vlan21) +Vlan2501:31:03: MDSS: -- mdss_add_oif01:31:03: MDSS: enqueue a FE_OIF_ADD (192.1.21.6, 239.255.158.197,Vlan21) +Vlan2501:31:03: MDSS: mdb (192.1.21.6, 239.255.158.197) fast_flags |MCACHE_MTU01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,Vlan21) +Vlan2601:31:03: MDSS: -- mdss_add_oif01:31:03: MDSS: enqueue a FE_OIF_ADD (192.1.21.6, 239.255.158.197,Vlan21) +Vlan2601:31:03: MDSS: mdb (192.1.21.6, 239.255.158.197) fast_flags |MCACHE_MTU01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,uVlan21) +Vlan27Related Commands
debug media resource provisioning all
To display debugging messages related to all media resource provisioning, use the debug media resource provisioning all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug media resource provisioning all
no debug media resource provisioning all
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug media resource provisioning all command:
Router# debug media resource provisioning all...Media resource provisioning all debugging is on.Disabling profile will disconnect active CONFERENCING calls,do you want to continue ? [yes/no]*Jul 8 18:46:36: rpm_if_profile_exist ::profile id 10, service TRANSCODING*Jul 8 18:46:36: rpm_get_rscid_profile_info Profile with profile id :10, service :TRANSCODING does not exist*Jul 8 18:46:36: rpm_if_profile_exist ::profile id 10, service CONFERENCING*Jul 8 18:46:36: rpm_if_profile_exist ::profile id 10, service TRANSCODING*Jul 8 18:46:36: rpm_get_rscid_profile_info Profile with profile id :10, service :TRANSCODING does not exist*Jul 8 18:46:36: rpm_if_profile_exist ::profile id 10, service CONFERENCINGMust be yes or noRouter(config-dspfarm-profile)#Router(config-dspfarm-profile)#Router(config-dspfarm-profile)#Router(config-dspfarm-profile)# no shutdownRouter(config-dspfarm-profile)#*Jul 8 18:46:42: rpm_user_enable_profile ::profile id 10, service CONFERENCING*Jul 8 18:46:44:%DSPRM-5-UPDOWN:DSP 10 in slot 1, changed state to up*Jul 8 18:46:44: rpm_rscprv_update ::provider_id 1 rsc_id 2 rsc_grp_state 4num_channel_delta 0*Jul 8 18:46:44: rpm_rscprv_update resource update from resource provider 1 is successfulRouter(config-dspfarm-profile)#Router(config-dspfarm-profile)# exitRouter(config)# exitRelated Commands
debug media resource provisioning errors
To display debugging messages related to media resource provisioning errors, use the debug media resource provisioning errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug media resource provisioning errors
no debug media resource provisioning errors
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the debug media resource provisioning errors command:
Router# debug media resource provisioning errorsMedia resource provisioning errors debugging is onRouter# no debug media resource provisioning errorsMedia resource provisioning errors debugging is offRelated Commands
debug media resource provisioning events
To display debugging messages related to media resource provisioning events, use the debug media resource provisioning events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug media resource provisioning events
no debug media resource provisioning events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the debug media resource provisioning events command:
Router# debug media resource provisioning eventsMedia resource provisioning events debugging is onRouter# no debug media resource provisioning eventsMedia resource provisioning events debugging is offRouter#Related Commands
debug mediacard
To display Digital Signal Processor Resource Manager (DSPRM) debugging information, use the debug mediacard command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mediacard {all | errors | events | message}
no debug mediacard {all | errors | events | message}
Syntax Description
all
Debugs DSPRM errors, events, and messages.
errors
Debugs DSPRM errors.
events
Debugs DSPRM events.
message
Debugs DSPRM messages.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug mediacard errors command to debug active calls. You should use the debug mediacard all command during minimum traffic periods only; using the debug mediacard all command during active calls can significantly impact system performance.
Examples
The following is sample output from the debug mediacard command:
Router# debug mediacard messagesMedia Card service messages debugging is on*Mar 1 07:45:06.362: > CREATE_CONFERENCE (0x1) , pktLen 56, confId 1, instId 17483, seqNo 27983, Payload (24 bytes): confType 3, agcMode 1, spkrUpdateReportMode 1, maxActSpkr 3*Mar 1 07:45:06.362: > CREATE_CHANNEL (0x64) , pktLen 100, confId 1, instId 26625, seqNo 27984, Payload (68 bytes): rxCodecType 1, suppressRx 1, rxCNG 2, rxPLC 2, rxVAD 2, rxToneDet 1, rxSpkrPriority 1, rxInactiveTimeOut 7200, rxPacketSize 20, rxRTPPayloadType 0*Mar 1 07:45:06.362: txCodecType 2, suppressTx 1, txVAD 1, AGC 1, txSSRC 167860472, txPacketSize 20, txRTPPayloadType 0*Mar 1 07:45:06.362: < CREATE_CONFERENCE_ACK (0x4001) , pktLen 116, confId 1,instId 0, seqNo 27983, Payload (84 bytes): status 0 (Normal Completion), param13, param2 0*Mar 1 07:45:06.362: < CREATE_CHANNEL_ACK (0x4064) , pktLen 116, confId 1, instId 26625, seqNo 27984, Payload (84 bytes): status 0 (Normal Completion), param10, param2 0*Mar 1 07:45:06.362: > CREATE_CONFERENCE (0x1) , pktLen 56, confId 2, instIdAll possible debugging has been turned offMTP#26625, seqNo 27985, Payload (24 bytes): confType 3, agcMode 1, spkrUpdateReportMode 1, maxActSpkr 3*Mar 1 07:45:06.362: > CREATE_CHANNEL (0x64) , pktLen 100, confId 2, instId 26626, seqNo 27986, Payload (68 bytes): rxCodecType 2, suppressRx 1, rxCNG 2, rxPLC 2, rxVAD 2, rxToneDet 1, rxSpkrPriority 1, rxInactiveTimeOut 7200, rxPacketSize 20, rxRTPPayloadType 0*Mar 1 07:45:06.366: txCodecType 1, suppressTx 1, txVAD 1, AGC 1, txSSRC 167858296, txPacketSize 20, txRTPPayloadType 0*Mar 1 07:45:06.366: < CREATE_CONFERENCE_ACK (0x4001) , pktLen 116, confId 2,instId 0, seqNo 27985, Payload (84 bytes): status 0 (Normal Completion), param13, param2 0Router# debug mediacard eventsMedia Card service events debugging is on*Mar 1 07:47:53.926: ms_ac_open_rtp_sockets: loc_ipaddr = 10.1.80.24 loc_mac<0003.feac.c842> rem_ip<0.0.0.0> rem_port<0>*Mar 1 07:47:53.926: ms_ac_get_unique_udp_port: rtcp_socket = 6255F490*Mar 1 07:47:53.926: ms_ac_get_unique_udp_port: SLOT3 Port<3450> is assigned!*Mar 1 07:47:53.926: ms_ac_open_local_rtp: rtpinfo 64382A3C, local_port =23930*Mar 1 07:47:53.926: ms_ac_rtp_enq: Sent msg 101 to DSPFARM*Mar 1 07:47:53.926: ms_ac_open_remote_rtp: rtpinfo 64382A3C, loc_ipaddr = 10.1.80.24 loc_udp_prt <23930> ,loc_mac<0003.feac.c842>*Mar 1 07:47:53.926: ms_ac_open_remote_rtp: remote_ipaddr = 10.1.2.15 remote_udp_prt <17932>*Mar 1 07:47:53.926: ms_ac_nexthop_macaddr idb<630BDFCC> nexthop<10.1.80.1>*Mar 1 07:47:53.926: ms_ac_nexthop_macaddr ptr<6301F5AC> through<GigabitEthernet1/0> nexthop<10.1.80.1>*Mar 1 07:47:53.926: ms_ac_after_found_mac <10.1.2.15>'s mac <00d0.002a.7400> found*Mar 1 07:47:53.926: ms_ac_check_xcode_rem_ip: rtpinfo <64382A3C> other_rtpinfo<0>*Mar 1 07:47:53.926: ms_ac_rtp_enq: Sent msg 103 to DSPFARM*Mar 1 07:47:53.942: ms_ac_open_rtp_sockets: loc_ipaddr = 10.1.80.24 loc_mac<0003.feac.c842> rem_ip<0.0.0.0> rem_port<0>*Mar 1 07:47:53.942: ms_ac_get_unique_udp_port: rtcp_socket = 6256C9B4*Mar 1 07:47:53.942: ms_ac_get_unique_udp_port: SLOT3 Port<1778> is assigned!*Mar 1 07:47:53.942: ms_ac_open_local_rtp: rtpinfo 6438353C, local_port =22258*Mar 1 07:47:53.942: ms_ac_rtp_enq: Sent msg 101 to DSPFARM*Mar 1 07:47:53.942: ac_validate_xcode_params: codeDec<2> codeEnc<1> decDur<20>encDur<20>*Mar 1 07:47:53.942: ac_open_xcode_channel: codeDec<1> codeEnc<2> decDur<20> encDur<20> VADen<0> prf_id<4>*Mar 1 07:47:53.942: reserve_xcode_resource: reserve xcode resource:codecDec<1>codecEnc<2>*Mar 1 07:47:53.942: alRelated Commands
debug memory
To enable debugging on memory, use the debug memory command in privileged EXEC mode. To disable memory debugging, use the no form of this command.
debug memory [rmi]
no debug memory
Syntax Description
Command Default
Memory debugging is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The debug memory command is used when debugging memory manager operations such as allocating and reallocating memory.
Examples
The following example shows how to enable memory debugging:
Router# debug memoryMemory debugging is onThe following example shows how to enable memory RMI debugging:
Router# debug memory rmiMemory RMI debugging is onRelated 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
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
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 is sample output from the debug mgcp errors command and keyword:
Router# debug mgcp errorsUnknown network interface typeThe following is sample 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 is sample 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 is sample 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 is sample 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 is sample 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 is sample 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 mgcp all
To enable all debug traces for Media Gateway Control Protocol (MGCP), use the debug mgcp all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp all [tracelevel {critical | moderate | verbose}]
no debug mgcp all
Syntax Description
Command Default
MGCP debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command enables the following MGCP debug commands:
•
debug mgcp endptdb
•
•
•
•
•
•
•
•
•
•
•
Caution
Examples
The following is sample output from the debug mgcp all command:
Router# debug mgcp allThis may severely impact network performance. Continue[confirm]Media Gateway Control Protocol all debugging is on, trace-level VerboseRouter#*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(240):[lvl=1]MGC stat - 192.168.1.200, total=8, succ=5, failed=1*Sep 10 17:20:24.408: MGCP Packet received from 192.168.1.200:7979--->CRCX 6 aaln/S2/SU1/1 MGCP 1.0M: recvonlyC: 1<---*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_mgcp_msg(3318):[lvl=0] : <NEW MGCP MSG From CA>*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(316):[lvl=0]call mgcp_parse_header*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(320):[lvl=0]out mgcp_parse_header*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(360):[lvl=1]SUCCESS: - MGCP Header parsing was OK*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_parameter_lines(725):[lvl=1]return parse function in mgcp_parm_rules_array[6].*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4762):[lvl=0](in_ptr: recvonly)*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4780):[lvl=0]tmp_ptr:(recvonly)*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4816):[lvl=0]tmp_ptr:(recvonly)*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4822):[lvl=0]match recvonly recvonly*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4830):[lvl=0]case MODE_RECVONLY*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4894):[lvl=0]SUCCESS: Connection Mode parsing is OK*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_parameter_lines(725):[lvl=1]return parse function in mgcp_parm_rules_array[1].*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(840):[lvl=0]in_ptr: 1*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(883):[lvl=1]SUCCESS: Call ID string(1) parsing is OK*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_mandatory_parms(12428):[lvl=0]Entered*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_comp_mp_parms(14923):[lvl=0]Entered*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_comp_mp_parms(14928):[lvl=1] - lcon_opt_ptr could not be obtained*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(378):[lvl=2]SUCCESS: END of Parsing*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_a(1339):[lvl=0]aaln/S2/SU1/1*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_slot(1632):[lvl=0]2/SU1/1*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]2/SU1/1*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_slot(1641):[lvl=0] : ifn 0x665449A8, slot:2*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_su(1773):[lvl=0]1/1*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1/1*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_port(1807):[lvl=0]1*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_endpt_offset(2590):[lvl=0]endpt NULL*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_by_ifn(1326):[lvl=0]Entered*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1145):[lvl=0]Entered*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_compute_key(196):[lvl=0]type 2 slot 0002 subunit 0001*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1157):[lvl=0]computed key 0x2081FF01Related Commands
debug mgcp endpoint
To enable debug traces for a specific Media Gateway Control Protocol (MGCP) endpoint, use the debug mgcp endpoint command in privileged EXEC mode. To disable debugging output for the endpoint, use the no form of this command.
debug mgcp endpoint endpoint-name {all [tracelevel {critical | moderate | verbose}] | errors | events [tracelevel {critical | moderate | verbose}] | media [tracelevel {critical | moderate | verbose}] | packets}
no debug mgcp endpoint endpoint-name {all | errors | events | media | packets}
Syntax Description
Command Default
Debugging for specific endpoints is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command enables debugging for a specific MGCP endpoint. You can enable the same type of debugging globally for all endpoints by using the debug mgcp all, debug mgcp errors, debug mgcp events, debug mgcp media, or debug mgcp packets commands.
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
This command sets the trace level for the specific endpoint. You can set the trace level globally for all MGCP debug commands and endpoints by using the debug mgcp tracelevel-default command. Setting the endpoint-specific trace level takes precedence over the global trace-level.
Note
Examples
The following is sample output from the debug mgcp endpoint command:
Router# debug mgcp endpoint aaln/S2/SU1/1 events tracelevel criticalMedia Gateway Control Protocol events debugging for endpoint aaln/S2/SU1/1 is on, trace-level CriticalRouter#*Sep 10 17:46:13.100: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_idle_crcx(4875):[lvl=2]callp(0x63E313E0), current state CALL_IDLE, event EV_CREATE_CONN*Sep 10 17:46:13.100: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_CONNECTING, event EV_CREATE_CONN*Sep 10 17:46:13.104: //8/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_call_pre_conference(223):[lvl=2]call p(0x63E311D0), current state CALL_CONNECTING, event EV_CALL_CONNECT*Sep 10 17:46:13.104: //8/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_call_connect(7331):[lvl=2]callp(0x63 E311D0), current state CALL_CONNECTING, event EV_CALL_CONNECT*Sep 10 17:46:13.104: //8/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E311D0), new state CALL_CONFERENCING, event EV_CALL_CONNECT*Sep 10 17:46:13.104: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_call_proceeding(6306):[lvl=2]callp( 0x63E313E0), current state CALL_CONNECTING, event EV_CALL_PROCEED*Sep 10 17:46:13.104: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_call_connect(7331):[lvl=2]callp(0x6 3E313E0), current state CALL_CONNECTING, event EV_CALL_PROCEED*Sep 10 17:46:13.104: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_CONFERENCING, event EV_CALL_PROCEED*Sep 10 17:46:13.108: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_ignore_ccapi_ev(4316):[lvl=2]callp( 0x63E313E0), current state CALL_CONFERENCING, event EV_CONF_RDY*Sep 10 17:46:13.108: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_CONFERENCING, event EV_CONF_RDY*Sep 10 17:46:13.108: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_call_modified(7710):[lvl=2]callp(0x 63E313E0), current state CALL_CONFERENCING, event EV_MODIFY_DONE*Sep 10 17:46:13.108: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_CONFERENCING, event EV_MODIFY_DONE*Sep 10 17:46:13.108: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_voice_mode_done(7994):[lvl=2]callp( 0x63E313E0), current state CALL_CONFERENCING, event EV_VOICE_MODE_DONE, minor ev(d): 138, minor ev*Sep 10 17:46:13.112: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_ACTIVE, event EV_VOICE_MODE_DONE*Sep 10 17:46:23.104: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_ACTIVE, event EV_MEDIA_EVTRelated Commands
debug mgcp endptdb
To enable debug traces for all Media Gateway Control Protocol (MGCP) endpoints, use the debug mgcp endptdb command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp endptdb [tracelevel {critical | moderate | verbose}]
no debug mgcp endptdb
Syntax Description
Command Default
MGCP debugging for endpoints is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command enables debugging globally for all MGCP endpoints. You can limit debugging to a specific endpoint by using the debug mgcp endpoint command.
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
Examples
The following is sample output from the debug mgcp endptdb command used with the debug mgcp packets command:
Router# debug mgcp packetsMedia Gateway Control Protocol packets debugging for all endpoints is onRouter# debug mgcp endptdbMedia Gateway Control Protocol endpoint database debugging for all endpoints is on, trace-level VerboseRouter#*Sep 10 11:39:16.467: MGCP Packet received from 192.168.1.200:7979--->CRCX 27 aaln/S2/SU1/1 MGCP 1.0M: recvonlyC: 1<---*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_a(1339):[lvl=0]aaln/S2/SU1/1*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_slot(1632):[lvl=0]2/SU1/1*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]2/SU1/1*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_slot(1641):[lvl=0] : ifn 0x665449A8, slot:2*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_su(1773):[lvl=0]1/1*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1/1*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_port(1807):[lvl=0]1*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_by_ifn(1326):[lvl=0]Entered*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1145):[lvl=0]Entered*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_compute_key(196):[lvl=0]type 2 slot 0002 subunit 0001*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1157):[lvl=0]computed key 0x2081FF01*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_state(3758):[lvl=0]endpt aaln/S2/SU1/1*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_default_get_state(3779):[lvl=0]endpt aaln/S2/SU1/1*Sep 10 11:39:16.479: MGCP Packet sent to 192.168.1.200:7979--->200 27 OKI: Dv=0c=IN IP4 192.168.1.79m=audio 16870 RTP/AVP 0 8 99 101 102 2 15 103 4 104 105 106 107 18 100a=rtpmap:99 G.729a/8000a=rtpmap:101 G.726-16/8000a=rtpmap:102 G.726-24/8000a=rtpmap:103 G.723.1-H/8000a=rtpmap:104 G.723.1-L/8000a=rtpmap:105 G.729b/8000a=rtpmap:106 G.723.1a-H/8000a=rtpmap:107 G.723.1a-L/8000a=rtpmap:100 X-NSE/8000a=fmtp:100 200-202a=X-sqn:0a=X-cap: 1 audio RTP/AVP 100a=X-cpar: a=rtpmap:100 X-NSE/8000a=X-cpar: a=fmtp:100 200-202a=X-cap: 2 image udptl t38<---Related Commands
debug mgcp errors
To enable debug traces for Media Gateway Control Protocol (MGCP) errors, use the debug mgcp errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp errors
no debug mgcp errors
Syntax Description
This command has no arguments or keywords.
Command Default
MGCP error debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command enables error debugging globally for all MGCP endpoints. You can limit debugging to a specific endpoint by using the debug mgcp endpoint command.
Examples
The following is sample output from the debug mgcp errors command:
Router# debug mgcp errors*Oct 16 12:09:05.538: MGC stat - 10.208.237.83, total=1029, succ=998, failed=0- mgcp_parse_header()- Request Verb FOUND AUEP- mgcp_parse_request_header()- MGCP_V10, start check for profile- mgcp_parse_header: mgcp_parse_request_header returns status: 0*Oct 16 12:09:05.538: MGCP Packet received from 10.208.237.83-AUEP 9634549 S0/DS1-0/1@AS5300 MGCP 1.0F: I*Oct 16 12:09:05.542: -- mgcp_parse_packet() - call mgcp_parse_header- mgcp_parse_header()- Request Verb FOUND AUEP- mgcp_parse_request_header()- MGCP_V10, start check for profile- mgcp_parse_header: mgcp_parse_request_header returns status: 0- mgcp_parse_packet() - out mgcp_parse_header- SUCCESS: mgcp_parse_packet()-MGCP Header parsing was OK- mgcp_parse_parameter_lines(), code_str:: I, code_len:2, str:F: I- mgcp_parse_parameter_lines(str:F: I) -num_toks: 28- mgcp_parse_parameter_lines() check NULL str(I), in_ptr(F: I)- mgcp_parse_parameter_lines() return Parse function in mgcp_parm_rules_array[14]- mgcp_parse_req_info(I) is called- mgcp_parse_req_info() - tmp_ptr:(I)- SUCCESS: Request Info parameter line (F:) parsing OK- mgcp_val_mandatory_parms()Related Commands
debug mgcp events
To enable debug traces for Media Gateway Control Protocol (MGCP) events, use the debug mgcp events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp events [tracelevel {critical | moderate | verbose}]
no debug mgcp events
Syntax Description
Command Default
MGCP events debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command enables events debugging globally for all MGCP endpoints. You can limit debugging to a specific endpoint by using the debug mgcp endpoint command.
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
Examples
The following is sample output from the debug mgcp events command:
Router# debug mgcp eventsMedia Gateway Control Protocol events debugging for all endpoints is on, trace-level VerboseRouter#*Sep 10 09:22:41.276: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_stw_call_back(316):[lvl=0]timer type 1*Sep 10 09:22:41.276: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_timers(1431):[lvl=0]timer of type 1 expired.*Sep 10 09:22:41.276: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_remove_old_ack(712):[lvl=1]Removing ack: (trans ID 15) : 250 15 OKP: PS=0, OS=0, PR=0, OR=0, PL=0, JI=0, LA=0*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(240):[lvl=1]MGC stat - 192.168.1.200, total=18, succ=14, failed=2*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_mgcp_msg(3318):[lvl=0] : <NEW MGCP MSG From CA>*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_endpt_offset(2590):[lvl=0]endpt NULL*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcpapp_setup_per_call_data(2487):[lvl=1]mgcpap p_setup_per_call_data: callp: 63E313E0, vdbptr: 65822AF8, state: CALL_IDLE*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_notified_entity(439):[lvl=0]Entered*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_notified_entity(458):[lvl=1]ne callagenthost:7979, ne addr 192.168.1.200:7979*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/xlate_mgcp_ev(921):[lvl=1]hdr_type 1*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcpapp_process_mgcp_event(2615):[lvl=1]Process ing Incoming Message [CRCX 16]*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcpapp_invoke_mgcp_sm(2559):[lvl=1]Msg In-Progress(Active) [INVVERB 0], await_ev=0, queued=0x00000000*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_process_deferred_queue(3362):[lvl=0]Entere d*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_store_endpt_and_ntfy_entity_name(4464):[lvl=0]Entered*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_invoke_app_sm(535):[lvl=0]MGCP:calling FSM- callp(63E313E0)*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_idle_crcx(4875):[lvl=2]callp(0x63E313E0), current state CALL_IDLE, event EV_CREATE_CONN*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_init_modem_relay_params(103):[lvl=0]modem-relay-enabled=0, mr-gw-xid=0*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_compute_debugsy_hdr(274):[lvl=0]Building Debugsy header*Sep 10 09:22:42.300: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_compute_debugsy_hdr(383):[lvl=0]GU ID[C537F3F38008] assigned to call_id[-1], endpt[aaln/S2/SU1/1], mgcp_call_id[n/a], conn_id[0]*Sep 10 09:22:42.300: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_idle_crcx(4961):[lvl=0]calls mgcp_allocate_if()*Sep 10 09:22:42.300: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_idle_crcx(5006):[lvl=1]get capability*Sep 10 09:22:42.300: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_compute_debugsy_hdr(274):[lvl=0]Bu ilding Debugsy header*Sep 10 09:22:42.304: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_compute_debugsy_hdr(383):[lvl=0]GU ID[C537F3F38008] assigned to call_id[-1], endpt[aaln/S2/SU1/1], mgcp_call_id[1], conn_id[0]*Sep 10 09:22:42.304: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_idle_crcx(5093):[lvl=0]Default aal2 vc = 1 1-pvc,2-svc*Sep 10 09:22:42.304: //-1/xxxxxxxxxxxx/MGCP/mgcp_init_vox_if_record(6781):[lvl=0]reusing records. conn_type: 2, vox if_type: 1*Sep 10 09:22:42.304: //-1/xxxxxxxxxxxx/MGCP/mgcp_compute_debugsy_hdr(274):[lvl=0]Building Debugsy headerRelated Commands
debug mgcp gcfm
To enable generic call filter module (GCFM) debug traces for Media Gateway Control Protocol (MGCP), use the debug mgcp gcfm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp gcfm [tracelevel {critical | moderate | verbose}]
no debug mgcp gcfm
Syntax Description
Command Default
MGCP GCFM debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command enables GCFM debugging globally for all MGCP endpoints.
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
Examples
The following is sample output from the debug mgcp gcfm command:
Router# debug mgcp gcfmMedia Gateway Control Protocol gcfm debugging for all endpoints is on, trace-level VerboseRouter#*Sep 10 09:24:52.692: //-1/12F030978009/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_gcfm_percall_register(315):[lvl=2] GCFM Inactive*Sep 10 09:24:52.692: //-1/12F030978009/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_gcfm_percall_register(315):[lvl=2]G CFM InactiveRouter#Related Commands
debug mgcp inout
To enable debug traces for all Media Gateway Control Protocol (MGCP) entry and exit endpoints, use the debug mgcp inout command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp inout [tracelevel {critical | moderate | verbose}]
no debug mgcp inout
Syntax Description
Command Default
Debugging of MGCP entry and exit endpoints is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
Examples
The following is sample output from the debug mgcp inout command:
Router# debug mgcp inoutMedia Gateway Control Protocol inout debugging for all endpoints is on, trace-level VerboseRouter#*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(240):[lvl=1]MGC stat - 192.168.1.200, total=22, succ=18, failed=2*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(316):[lvl=0]call mgcp_parse_header*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4762):[lvl=0](in_ptr: recvonly)*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4894):[lvl=0]SUCCESS: Connection Mode parsing is OK*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(840):[lvl=0]in_ptr: 1*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(883):[lvl=1]SUCCESS: Call ID string(1) parsing is OK*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_mandatory_parms(12428):[lvl=0]Entered*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_a(1339):[lvl=0]aaln/S2/SU1/1*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_slot(1632):[lvl=0]2/SU1/1*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]2/SU1/1*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_su(1773):[lvl=0]1/1*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1/1*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_port(1807):[lvl=0]1*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_endpt_offset(2590):[lvl=0]endpt NULL*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_by_ifn(1326):[lvl=0]Entered*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1145):[lvl=0]Entered*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_compute_key(196):[lvl=0]type 2 slot 0002 subunit 0001*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_state(3758):[lvl=0]endpt aaln/S2/SU1/1*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_default_get_state(3779):[lvl=0]endpt aaln/S2/SU1/1*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_notified_entity(439):[lvl=0]Entered*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_notified_entity(458):[lvl=1]ne callagenthost:7979, ne addr 192.168.1.200:7979*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xlate_mgcp_ev(921):[lvl=1]hdr_type 1*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcpapp_invoke_mgcp_sm(2559):[lvl=1]Msg In-Progress(Active) [INVVERB 0], await_ev=0, queued=0x00000000*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_process_deferred_queue(3362):[lvl=0]Entere d*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_store_endpt_and_ntfy_entity_name(4464):[lvl=0]Entered*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_idle_crcx(4875):[lvl=2]callp(0x63E313E0), current state CALL_IDLE, event EV_CREATE_CONN*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_init_modem_relay_params(103):[lvl=0]modem-relay-enabled=0, mr-gw-xid=0*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_compute_debugsy_hdr(274):[lvl=0]Building Debugsy header*Sep 10 09:26:37.784: //-1/5193F3E0800A/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_compute_debugsy_hdr(383):[lvl=0]GU ID[5193F3E0800A] assigned to call_id[-1], endpt[aaln/S2/SU1/1], mgcp_call_id[n/a], conn_id[0]*Sep 10 09:26:37.784: //-1/5193F3E0800A/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_verify_supp_reqdet_ev(10645):[lvl= 0]Entered*Sep 10 09:26:37.784: //-1/5193F3E0800A/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_verify_supp_signal_ev(10685):[lvl= 0]Entered*Sep 10 09:26:37.784: //-1/5193F3E0800A/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_compute_debugsy_hdr(274):[lvl=0]Bu ilding Debugsy headerRelated Commands
debug mgcp media
To enable debug traces for Media Gateway Control Protocol (MGCP) tone and signal events, use the debug mgcp media command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp media [tracelevel {critical | moderate | verbose}]
no debug mgcp media
Syntax Description
Command Default
MGCP media debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command enables media debugging globally for all MGCP endpoints. You can limit debugging to a specific endpoint by using the debug mgcp endpoint command.
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
Examples
The following is sample output from the debug mgcp media command:
Router# debug mgcp mediaMedia Gateway Control Protocol media events debugging for all endpoints is on, trace-level VerboseRouter#*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_verify_supp_reqdet_ev(10645):[lvl= 0]Entered*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_verify_supp_signal_ev(10685):[lvl= 0]Entered*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/process_request_ev(5800):[lvl=1]callp 63E313E0, voice_if 6663CA38*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/process_detect_ev(6007):[lvl=0]callp 63E313E0, voice_if 6663CA38*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/process_signal_ev(5500):[lvl=0]callp 63E313E0, voice_ifp 6663CA38*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_process_quarantine_mode(6096):[lvl =0]callp 63E313E0, voice_if 6663CA38*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_process_quarantine_mode(6149):[lvl =0]Q mode not found, Reset default values*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_process_quarantine_mode(6168):[lvl =1]Q mode: process=0, loop=0*Sep 10 09:27:48.936: //19/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_process_pending_t38_port_switch(16 49):[lvl=1]conn_recp->conn_id: 0x0*Sep 10 09:27:48.940: //19/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/process_deferred_request_events(5724):[ lvl=0]EnteredRelated Commands
debug mgcp nas
To enable network access server (NAS) (data) events for Media Gateway Control Protocol (MGCP), use the debug mgcp nas command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp nas [tracelevel {critical | moderate | verbose}]
no debug mgcp nas
Syntax Description
Command Default
MGCP NAS event debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
Examples
The following is sample output for the debug mgcp nas command with the debug mgcp packets command also enabled:
Router# debug mgcp nasMedia Gateway Control Protocol nas pkg events debugging for all endpoints is on, trace-level VerboseRouter# debug mgcp packetsMedia Gateway Control Protocol packets debugging for all endpoints is onRouter#*Sep 10 11:51:41.863: MGCP Packet received from 192.168.1.200:7979--->CRCX 34 aaln/S2/SU1/1 MGCP 1.0X:57M: nas/dataC:3L:b:64, nas/bt:modem, nas/cdn:3000, nas/cgn:1000C: 1<---*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(779):[lvl=0]Full string: nas/bt:modem*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(791):[lvl=1]string past slash: bt*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(792):[lvl=1]string past colon: modem*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(779):[lvl=0]Full string: nas/cdn:3000*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(791):[lvl=1]string past slash: cdn*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(792):[lvl=1]string past colon: 3000*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(779):[lvl=0]Full string: nas/cgn:1000*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(791):[lvl=1]string past slash: cgn*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(792):[lvl=1]string past colon: 1000Related Commands
debug mgcp packets
To enable debug traces for Media Gateway Control Protocol (MGCP) packets, use the debug mgcp packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp packets [input-hex]
no debug mgcp packets [input-hex]
Syntax Description
Command Default
MGCP packets debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command enables packet debugging globally for all MGCP endpoints. You can limit debugging to a specific endpoint by using the debug mgcp endpoint command.
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
Examples
The following is sample output from the debug mgcp packets command:
Router# debug mgcp packetsMedia Gateway Control Protocol packets debugging for all endpoints is onRouter#*Sep 10 11:57:26.795: MGCP Packet received from 192.168.1.200:7979--->CRCX 38 aaln/S2/SU1/1 MGCP 1.0M: recvonlyC: 1<---*Sep 10 11:57:26.795: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcpapp_invoke_mgcp_sm(2569):[lvl=0]CHECK DATA CALL for aaln/S2/SU1/1*Sep 10 11:57:26.807: MGCP Packet sent to 192.168.1.200:7979--->200 38 OKI: 10v=0c=IN IP4 192.168.1.79m=audio 18876 RTP/AVP 0 8 99 101 102 2 15 103 4 104 105 106 107 18 100a=rtpmap:99 G.729a/8000a=rtpmap:101 G.726-16/8000a=rtpmap:102 G.726-24/8000a=rtpmap:103 G.723.1-H/8000a=rtpmap:104 G.723.1-L/8000a=rtpmap:105 G.729b/8000a=rtpmap:106 G.723.1a-H/8000a=rtpmap:107 G.723.1a-L/8000a=rtpmap:100 X-NSE/8000a=fmtp:100 200-202a=X-sqn:0a=X-cap: 1 audio RTP/AVP 100a=X-cpar: a=rtpmap:100 X-NSE/8000a=X-cpar: a=fmtp:100 200-202a=X-cap: 2 image udptl t38<---Related Commands
debug mgcp parser
To enable debug traces for the Media Gateway Control Protocol (MGCP) parser and builder, use the debug mgcp parser command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp parser [tracelevel {critical | moderate | verbose}]
no debug mgcp parser
Syntax Description
Command Default
MGCP parser and builder debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
Examples
The following is sample output from the debug mgcp parser command:
Router# debug mgcp parserMedia Gateway Control Protocol parser debugging for all endpoints is on, trace-level VerboseRouter#*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(316):[lvl=0]call mgcp_parse_header*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(320):[lvl=0]out mgcp_parse_header*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(360):[lvl=1]SUCCESS: - MGCP Header parsing was OK*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_parameter_lines(725):[lvl=1]return parse function in mgcp_parm_rules_array[6].*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4762):[lvl=0](in_ptr: recvonly)*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4780):[lvl=0]tmp_ptr:(recvonly)*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4816):[lvl=0]tmp_ptr:(recvonly)*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4822):[lvl=0]match recvonly recvonly*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4830):[lvl=0]case MODE_RECVONLY*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4894):[lvl=0]SUCCESS: Connection Mode parsing is OK*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_parameter_lines(725):[lvl=1]return parse function in mgcp_parm_rules_array[1].*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(840):[lvl=0]in_ptr: 1*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(883):[lvl=1]SUCCESS: Call ID string(1) parsing is OK*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_mandatory_parms(12428):[lvl=0]Entered*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_comp_mp_parms(14923):[lvl=0]Entered*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_comp_mp_parms(14928):[lvl=1] - lcon_opt_ptr could not be obtained*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(378):[lvl=2]SUCCESS: END of Parsing*Sep 10 11:58:51.283: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_validate_version_with_call_agent_s erv_type(8322):[lvl=1]req_msg_version: 5, config_version: 5*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_validate_net_type(6601):[lvl=1] lcnw_valid=0, lc_con_valid=0*Sep 10 11:58:51.287: //-1/xxxxxxxxxxxx/MGCP/mgcp_validate_net_type(6710):[lvl=1]Network type/conection type valid = 1. connection type = 1 [1->RTP, 2->AAL1_SDT, 4->AAL2]*Sep 10 11:58:51.287: //-1/xxxxxxxxxxxx/MGCP/mgcp_get_qos(2665):[lvl=1]MGCP msg qos value=0*Sep 10 11:58:51.287: //-1/xxxxxxxxxxxx/MGCP/mgcp_init_dyn_payload_types(2899):[lvl=1]used payload type map = 2F400003*Sep 10 11:58:51.287: //-1/xxxxxxxxxxxx/MGCP/get_voip_peer_info(7155):[lvl=1]No SDP connection info*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(897):[lvl=1]num supprt codec=14*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(1061):[lvl=0]glob codec=1 (syn=1)*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(1063):[lvl=0]supp list=*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(1067):[lvl=0] 1*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(1067):[lvl=0],2*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(1067):[lvl=0],7Related Commands
debug mgcp src
To enable debug traces for the System Resource Check (SRC) Call Admission Control (CAC) process for Media Gateway Control Protocol (MGCP), use the debug mgcp src command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp src [tracelevel {critical | moderate | verbose}]
no debug mgcp src
Syntax Description
Command Default
MGCP SRC debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
Examples
The following is sample output from the debug mgcp src command:
Router# debug mgcp srcMedia Gateway Control Protocol System Resource Check CAC debugging for all endpoints is on, trace-level VerboseRouter#*Sep 10 12:01:14.403: //-1/EADF209C8013/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_set_call_counter_control(8163):[lvl =1]Outgoing call with 1 network leg, flag=TRUE*Sep 10 12:03:01.051: //35/EADF209C8013/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_reset_call_direction(8184):[lvl=1] Reseting incoming_call flag=FALSE in voice_ifRelated Commands
debug mgcp state
To enable state traces for Media Gateway Control Protocol (MGCP), use the debug mgcp state command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp state [tracelevel {critical | moderate | verbose}]
no debug mgcp state
Syntax Description
Command Default
MGCP state debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
Examples
The following is sample output from the debug mgcp state command:
Router# debug mgcp stateMedia Gateway Control Protocol state transition debugging for all endpoints is on, trace-level VerboseRouter#*Sep 10 12:08:02.755: //39/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_set_call_state(7562):[lvl=2]callp( 0x63E313E0) old state=CALL_IDLE new state=CALL_CONNECTING*Sep 10 12:08:02.755: //40/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_set_call_state(7562):[lvl=2]callp(0 x63E311D0) old state=CALL_IDLE new state=CALL_CONNECTING*Sep 10 12:08:02.755: //39/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_set_call_state(7562):[lvl=2]callp( 0x63E313E0) old state=CALL_CONNECTING new state=CALL_CONNECTING*Sep 10 12:08:02.759: //40/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_set_call_state(7562):[lvl=2]callp(0 x63E311D0) old state=CALL_CONNECTING new state=CALL_CONFERENCING*Sep 10 12:08:02.759: //39/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_set_call_state(7562):[lvl=2]callp( 0x63E313E0) old state=CALL_CONNECTING new state=CALL_CONFERENCING*Sep 10 12:08:02.759: //40/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_set_call_state(7562):[lvl=2]callp(0 x63E311D0) old state=CALL_CONFERENCING new state=CALL_CONFERENCING*Sep 10 12:08:02.763: //39/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_set_call_state(7562):[lvl=2]callp( 0x63E313E0) old state=CALL_CONFERENCING new state=CALL_ACTIVE*Sep 10 12:08:02.763: //40/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_set_call_state(7562):[lvl=2]callp(0 x63E311D0) old state=CALL_CONFERENCING new state=CALL_ACTIVERelated Commands
debug mgcp tracelevel-default
To set the trace level globally for all Media Gateway Control Protocol (MGCP) debug traces, use the debug mgcp tracelevel-default command in privileged EXEC mode. To reset the trace level to the default value, use the no form of this command.
debug mgcp tracelevel-default {critical | moderate | verbose}
no debug mgcp tracelevel-default {critical | moderate | verbose}
Syntax Description
critical
Only high priority debug information is displayed.
moderate
Medium and high priority debug information is displayed.
verbose
All debug information is displayed. This is the default value.
Command Default
The default trace level for all MGCP debug commands is verbose.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
This command sets the trace level globally for all MGCP debug commands and endpoints. You can set the trace level independently for a specific endpoint by using the debug mgcp endpoint command. The endpoint-specific trace level takes precedence over the global trace-level set with this command.
Note
Examples
The following example sets the default trace level to critical for all MGCP debug traces:
Router# debug mgcp tracelevel-default criticalRouter# debug mgcp eventsMedia Gateway Control Protocol events debugging for all endpoints is on, trace-level CriticalRouter# debug mgcp stateMedia Gateway Control Protocol state transition debugging for all endpoints is on, trace-level CriticalNotice that if the default trace level is then changed, as in the following example, the new trace level applies only to any MGCP debug commands that are issued after the default trace level is changed.
Router# debug mgcp tracelevel-default verboseRouter# debug mgcp voipcacMedia Gateway Control Protocol VoIPCAC debugging for all endpoints is on, trace-level VerboseRouter# show debugMGCP:Media Gateway Control Protocol events debugging is on, trace level CriticalMedia Gateway Control Protocol VoIPCAC debugging is on, trace level VerboseMedia Gateway Control Protocol state transition debugging is on, trace level CriticalRelated Commands
debug mgcp voipcac
To enable debug traces for the Voice over IP (VoIP) Call Admission Control (CAC) process at the Media Gateway Control Protocol (MGCP) application layer, use the debug mgcp voipcac command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mgcp voipcac [tracelevel {critical | moderate | verbose}]
no debug mgcp voipcac
Syntax Description
Command Default
MGCP VoIP CAC debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.
Examples
The following is sample output from the debug mgcp voipcac command:
Router# debug mgcp voipcacMedia Gateway Control Protocol VoIPCAC debugging for all endpoints is on, trace-level VerboseRouter#*Sep 10 12:04:47.747: //-1/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_idle_crcx(5251):[lvl=0]Check for HP and QOS combination*Sep 10 12:04:47.751: //-1/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_idle_crcx(5451):[lvl=0]CAC success*Sep 10 12:04:47.751: //-1/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/set_up_voip_call_leg(3918):[lvl=0]get voice interface*Sep 10 12:04:47.751: //-1/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/set_up_voip_call_leg(4441):[lvl=0]Initia lize VoIP CAC record stored inVoIP interface struct*Sep 10 12:04:47.751: //38/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_connect_peer_vox_call_leg(1546):[lv l=0]set_up_voip_call_leg returns OK*Sep 10 12:04:47.759: //37/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/process_signal_request_list(5608):[lvl= 0]EnteredRelated Commands
debug mls rp
To display various Internetwork Packet Exchange (IPX) Multilayer Switching (MLS) debugging elements, use the debug mls rp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mls rp {error | events | ipx | locator | packets | all}
no debug mls rp {error | events | ipx | locator | packets | all}
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following shows sample output from the debug mls rp ipx command:
Router# debug mls rp ipxIPX MLS debugging is onRouter# conf tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# int vlan 22Router(config-if)# no ipx access-group out05:44:37:FCP:flowmask changed to destinationRelated Commands
debug dss ipx event
Displays debugging messages for route change events that affect IPX MLS.
debug mls rp ip multicast
To display information about Multilayer Switching Protocol (MLSP), use the debug mls rp ip multicast command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mls rp ip multicast {all | error | events | packets}
no debub mls rp ip multicast {all | error | events | packets}
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Only one of the keywords is required.
Examples
The following example shows output from the debug mls rp ip multicast command using the error keyword:
Router# debug mls rp ip multicast errormlsm error debugging is onchtang-7200#06:06:45: MLSMERR: scb is INACTIVE, free INSTALL_FE06:06:46: MLSM: --> mlsm_proc_sc_ins_req(10.0.0.1, 224.2.2.3, 10)The following example shows output from the debug mls rp ip multicast command using the event keyword:
Router# debug mls rp ip multicast eventmlsm events debugging is onRouter#3d23h: MSCP: incoming shortcut flow statistic from Fa2/0.113d23h: MLSM: Flow_stat: (192.1.10.6, 239.255.158.197), byte :537792packet:84033d23h: MLSM: byte delta:7680 packet delta:120, time delta: 103d23h: MSCP: incoming shortcut flow statistic from Fa2/0.113d23h: MLSM: Flow_stat: (192.1.10.6, 239.255.158.197), byte :545472packet:85233d23h: MLSM: byte delta:7680 packet delta:120, time delta: 103d23h: MSCP: Router transmits keepalive_msg on Fa2/0.113d23h: MSCP: incoming shortcut keepalive ACK from Fa2/0.113d23h: MLSM: Include-list: (192.1.2.1 -> 0.0.0.0)3d23h: MSCP: incoming shortcut flow statistic from Fa2/0.113d23h: MLSM: Flow_stat: (192.1.10.6, 239.255.158.197), byte :553152packet:8643The following example shows output from the debug mls rp ip multicast command using the packet keyword:
Router# debug mls rp ip multicast packetmlsm packets debugging is onRouter#Router#Router#Router#**23h: MSCP(I): 01 00 0c cc cc cc 00 e0 1e 7c fe 5f 00 30 aa aa...LLL.`.|~_.0..23h: MSCP(I): 03 00 00 0c 01 07 01 05 00 28 01 02 0a c7 00 10.........(...G..23h: MSCP(I): a6 0b b4 ff 00 00 c0 01 0a 06 ef ff 9e c5 00 00&.4...@...o..E3d23h: MSCP(I): 00 00 00 09 42 c0 00 00 00 00 00 00 25 0b....B@......%.3d23h:**23h: MSCP(O): 01 00 0c 00 00 00 aa 00 04 00 01 04 00 00 aa aa......*.......LL23h: MSCP(O): 03 00 00 0c 00 16 00 00 00 00 01 00 0c cc cc cc.............L..23h: MSCP(O): aa 00 04 00 01 04 00 24 aa aa 03 00 00 0c 01 07*......$**......23h: MSCP(O): 01 06 00 1c c0 01 02 01 aa 00 04 00 01 04 00 00....@...*.....3d23h: MSCP(O): 00 0b 00 00 00 00 00 00 01 01 0a 62 ...........b3d23h:**23h: MSCP(I): 01 00 0c cc cc cc 00 e0 1e 7c fe 5f 00 24 aa aa...LLL.`.|~_.$..23h: MSCP(I): 03 00 00 0c 01 07 01 86 00 1c 01 02 0a c7 00 10.............G..23h: MSCP(I): a6 0b b4 ff 00 00 00 0b 00 00 c0 01 02 01 00 00..4.......@...3d23h: MSCP(I): 00 003d23h:Related Commands
debug mmoip aaa
Note
To display output that relates to authentication, authorization, and accounting (AAA) services with store-and-forward fax, use the debug mmoip aaa command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mmoip aaa
no debug mmoip aaa
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following output shows how the debug mmoip aaa command provides information about AAA for the on-ramp or off-ramp gateways:
Router# debug mmoip aaa5d10h:fax_aaa_begin_authentication:User-Name = mmoip-b.cisco.com5d10h:fax_aaa_begin_authentication:fax_account_id_origin = GATEWAY_ID5d10h:fax_aaa_end_authentication_callback:Authentication successfulThe following output shows how the debug mmoip aaa command provides information about AAA for the off-ramp gateway:
Router# debug mmoip aaa5d10h:fax_aaa_start_accounting:User-Name = mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:Calling-Station-Id = gmercuri@mail-server.cisco.com5d10h:fax_aaa_start_accounting:Called-Station-Id = fax=571-0839@mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:fax_account_id_origin = GATEWAY_IDmmoip-b#ax_aaa_start_accounting:fax_msg_id = <37117AF3.3D98300E@mail-server.cisco.com>5d10h:fax_aaa_start_accounting:fax_pages = 25d10h:fax_aaa_start_accounting:fax_coverpage_flag = TRUE5d10h:fax_aaa_start_accounting:fax_connect_speed = 14400bps5d10h:fax_aaa_start_accounting:fax_recipient_count = 15d10h:fax_aaa_start_accounting:fax_auth_status = USER SUCCESS5d10h:fax_aaa_start_accounting:gateway_id = mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:call_type = Fax Send5d10h:fax_aaa_start_accounting:port_used = slot:0 vfc port:05d10h:fax_aaa_do_offramp_accounting tty(6), Stopping accounting5d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveTransmitBytes = 180385d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveTransmitPackets = 14The following output shows how the debug mmoip aaa command provides information about AAA for the on-ramp gateway:
Router# debug mmoip aaa5d10h:fax_aaa_start_accounting:User-Name = mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:Calling-Station-Id = FAX=408@mail-from-hostname.com5d10h:fax_aaa_start_accounting:Called-Station-Id = FAX=5710839@mail-server.cisco.com5d10h:fax_aaa_start_accounting:fax_account_id_origin = GATEWAY_ID5d10h:fax_aaa_start_accounting:fax_msg_id = 00391997233216263@mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:fax_pages = 25d10h:fax_aaa_start_accounting:fax_connect_speed = 14400bps5d10h:fax_aaa_start_accounting:fax_auth_status = USER SUCCESS5d10h:fax_aaa_start_accounting:email_server_address = 1.14.116.15d10h:fax_aaa_start_accounting:email_server_ack_flag = TRUE5d10h:fax_aaa_start_accounting:gateway_id = mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:call_type = Fax Receive5d10h:fax_aaa_start_accounting:port_used = Cisco Powered Fax System slot:1 port:45d10h:fax_aaa_do_onramp_accounting tty(5), Stopping accounting5d10h:fax_aaa_stop_accounting:endb->cact->generic.callActiveTransmitBytes = 266875d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveReceiveBytes = 185585d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveReceivePackets = 14debug mmoip send email
To test connectivity between the T.37 on-ramp gateway and the e-mail server by sending a test e-mail to a specified e-mail address, use the debug mmoip send email command in privileged EXEC mode.
debug mmoip send email string
Syntax Description
Defaults
This command is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The debug mmoip send email command is used to test connectivity between the on-ramp gateway and the e-mail server. Basically, this debug command sends an e-mail message to the recipient specified in the e-mail address string. There is no specific output associated with the debug mmoip send email command; to see how the on-ramp gateway and e-mail server interact when processing the test e-mail message, enable the debug fmail client command.
The following example tests connectivity between the on-ramp gateway and the e-mail server by sending a test e-mail message to mailuser@mail-server.com:
Router# debug fmail clientRouter# debug mmoip send email mailuser@mail-server.com01:22:59:faxmail_client_send_test:Sending the test message toilya@mail-server.com from testing@mmoip-a.cisco.com...01:22:59:faxmail_client_send_test:Opening client engine.01:22:59:faxmail_client_send_test:Sending 59 bytes ...01:22:59:faxmail_client_send_test:Done sending test email.Related Commands
debug fmail client
Displays e-mail parameters (such as Mail from and Envelope to and Envelope from) and the progress of the SMTP client.
debug mmoip send fax
To send a T.37 off-ramp test fax, use the debug mmoip send fax command in privileged EXEC mode.
debug mmoip send fax string
Syntax Description
Defaults
This command is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The debug mmoip send fax command is used to test connectivity between the off-ramp gateway and a recipient fax device. Basically, this debug command sends a test fax transmission to the recipient specified in the telephone number string. There is no specific output associated with the debug mmoip send fax command.
The following example sends a test fax message to the telephone number 5550839:
Router# debug mmoip send fax 5550839The following output shows that the off-ramp gateway is placing a fax call:
01:28:18:ftsp_offramp_match_digits:phone number to translate:555083901:28:18: destPat(5......), matched(1), prefix() peer_tag(1)01:28:18:ftsp_offramp_match_digits:target:71083901:28:18:fap_offcm:tty(4), Got dial message00:00:00.000:AT&F\Q0S7=255Class 2 modem tracing begins, including modem initialization.
00:00:00.008:AA00:00:00.068:TT00:00:00.128:&F\Q0S7=25500:00:00.128:OK00:00:00.128:E0V100:00:00.140:ATE0OK00:00:00.140:AT+FCLASS=200:00:00.148:OK00:00:00.148:+FDCC=..;+FBOR=00:00:00.168:AT+FLID00:00:00.180:OK00:00:00.180:ATDTW710839The following output shows that the fax transmission is complete; in this particular example, there was a transmission error, and the modem timed out.01:28:25:ftsp_setup_for_oc:tty4, callid=0xA01:28:25:ftsp_setup_for_oc ctl=0, cas grp=-1, snmp_ix=3001:28:25:ftsp_off_ramp_active_call_init tty4 callid=0xA, snmp_ix=3001:29:18:fap_offpmt:tty(4), TxPhaseA:modem timeout01:29:18:%FTSP-6-FAX_DISCONNECT:Transmission erdebug mmoip transfer
To send output of the Tag Image File Format (TIFF) writer to a TFTP server, use the debug mmoip transfer command in privileged EXEC mode.
debug mmoip transfer prefix-filename tftp-server-name
Syntax Description
prefix-filename
Name of the TIFF file. The format for the TIFF filename is "telephone-number.TIFF."
tftp-server-name
TFTP server to which the output from the TIFF writer is sent.
Defaults
Sending output of the TIFF writer to a TFTP server is disabled.
Command Modes
Privileged EXEC
Command History
Examples
The debug mmoip transfer command sends the content of the fax data received to the TFTP server named by the tftp-server-name variable into the file identified by the prefix-filename variable. Each page of the fax transmission is a separate file, designated by the letter "p", followed by the page number.
For example, the following command transfers the received fax content to a TFTP server named "keyer". The first page of the transmission goes to the file named "/tftpboot/test/testp1.tiff", the second page goes to the file named "/tftpboot/test/testp2.tiff" and so on.
Router# debug mmoip transfer /tftpboot/test/test keyerThe named files must exist on the TFTP server and be writable in order for the debug operation to be successful.
debug modem
To observe modem line activity on an access server, use the debug modem command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem
no debug modem
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug modem command. The output shows when the modem line changes state.
Router# debug modem15:25:51: TTY4: DSR came up15:25:51: tty4: Modem: IDLE->READY15:25:51: TTY4: Autoselect started15:27:51: TTY4: Autoselect failed15:27:51: TTY4: Line reset15:27:51: TTY4: Modem: READY->HANGUP15:27:52: TTY4: dropping DTR, hanging up15:27:52: tty4: Modem: HANGUP->IDLE15:27:57: TTY4: restoring DTR15:27:58: TTY4: DSR came updebug modem csm
To debug the Call Switching Module (CSM), used to connect calls on the modem, use the debug modem csm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem csm [slot/port | group group-number]
no debug modem csm [slot/port | group group-number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
Use the debug modem csm command to troubleshoot call switching problems. With this command, you can trace the complete sequence of switching incoming and outgoing calls.
Examples
The following is sample output from the debug modem csm command. In this example, a call enters the modem (incoming) on slot 1, port 0:
Router(config)# service timestamps debug uptimeRouter(config)# endRouter# debug modem csm00:04:09: ccpri_ratetoteup bear rate is 1000:04:09: CSM_MODEM_ALLOCATE: slot 1 and port 0 is allocated.00:04:09: MODEM_REPORT(0001): DEV_INCALL at slot 1 and port 000:04:09: CSM_PROC_IDLE: CSM_EVENT_ISDN_CALL at slot 1, port 000:04:11: CSM_RING_INDICATION_PROC: RI is on00:04:13: CSM_RING_INDICATION_PROC: RI is off00:04:15: CSM_PROC_IC1_RING: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 000:04:15: MODEM_REPORT(0001): DEV_CONNECTED at slot 1 and port 000:04:15: CSM_PROC_IC2_WAIT_FOR_CARRIER: CSM_EVENT_ISDN_CONNECTED at slot 1, port 0The following is sample output from the debug modem csm command when call is dialed from the modem into the network (outgoing) from slot 1, port 2:
Router# debug modem csmatdt1666520200:11:21: CSM_PROC_IDLE: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 200:11:21: T1_MAIL_FROM_NEAT: DC_READY_RSP: mid = 1, slot = 0, unit = 000:11:21: CSM_PROC_OC1_REQUEST_DIGIT: CSM_EVENT_DIGIT_COLLECT_READY at slot 1, port 200:11:24: T1_MAIL_FROM_NEAT: DC_FIRST_DIGIT_RSP: mid = 1, slot = 0, unit = 000:11:24: CSM_PROC_OC2_COLLECT_1ST_DIGIT: CSM_EVENT_GET_1ST_DIGIT at slot 1, port 200:11:27: T1_MAIL_FROM_NEAT: DC_ALL_DIGIT_RSP: mid = 1, slot = 0, unit = 000:11:27: CSM_PROC_OC3_COLLECT_ALL_DIGIT: CSM_EVENT_GET_ALL_DIGITS (16665202) at slot 1, port 200:11:27: ccpri_ratetoteup bear rate is 1000:11:27: MODEM_REPORT(A000): DEV_CALL_PROC at slot 1 and port 200:11:27: CSM_PROC_OC4_DIALING: CSM_EVENT_ISDN_BCHAN_ASSIGNED at slot 1, port 200:11:31: MODEM_REPORT(A000): DEV_CONNECTED at slot 1 and port 200:11:31: CSM_PROC_OC5_WAIT_FOR_CARRIER: CSM_EVENT_ISDN_CONNECTED at slot 1, port 2CONNECT 19200/REL - MNPThe following is sample output from the debug modem csm command for an incoming call:
Router# debug modem csmRouter#1.19.36.7 2001Trying 1.19.36.7, 2001 ... Openatdt111222333444555666*Apr 7 12:39:42.475: Mica Modem(1/0): Rcvd Dial String(111222333444555666)*Apr 7 12:39:42.475: CSM_PROC_IDLE: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 0*Apr 7 12:39:42.479: CSM_RX_CAS_EVENT_FROM_NEAT:(A001): EVENT_CHANNEL_LOCK at slot 1 and port 0*Apr 7 12:39:42.479: CSM_PROC_OC4_DIALING: CSM_EVENT_DSX0_BCHAN_ASSIGNED at slot 1, port 0*Apr 7 12:39:42.479: Mica Modem(1/0): Configure(0x1)*Apr 7 12:39:42.479: Mica Modem(1/0): Configure(0x5)*Apr 7 12:39:42.479: Mica Modem(1/0): Call Setup*Apr 7 12:39:42.479: neat msg at slot 0: (1/0): Tx LOOP_CLOSURE (ABCD=1101)*Apr 7 12:39:42.491: neat msg at slot 0: (0/0): Rx LOOP_CLOSURE (ABCD=1101)*Apr 7 12:39:42.531: VDEV_ALLOCATE: slot 1 and port 3 is allocated.*Apr 7 12:39:42.531: CSM_RX_CAS_EVENT_FROM_NEAT:(0004): EVENT_CALL_DIAL_IN at slot 1 and port 3*Apr 7 12:39:42.531: CSM_PROC_IDLE: CSM_EVENT_DSX0_CALL at slot 1, port 3*Apr 7 12:39:42.531: Mica Modem(1/3): Configure(0x0)*Apr 7 12:39:42.531: Mica Modem(1/3): Configure(0x5)*Apr 7 12:39:42.531: Mica Modem(1/3): Call Setup*Apr 7 12:39:42.595: Mica Modem(1/0): State Transition to Call Setup*Apr 7 12:39:42.655: Mica Modem(1/3): State Transition to Call Setup*Apr 7 12:39:42.655: Mica Modem(1/3): Went offhook*Apr 7 12:39:42.655: CSM_PROC_IC1_RING: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 3*Apr 7 12:39:42.671: neat msg at slot 0: (0/0): Tx LOOP_CLOSURE (ABCD=1101)*Apr 7 12:39:42.691: neat msg at slot 0: (1/0): Rx LOOP_CLOSURE (ABCD=1101)*Apr 7 12:39:42.731: CSM_RX_CAS_EVENT_FROM_NEAT:(A001): EVENT_START_TX_TONE at slot 1 and port 0*Apr 7 12:39:42.731: CSM_PROC_OC4_DIALING: CSM_EVENT_DSX0_START_TX_TONE at slot 1, port 0*Apr 7 12:39:42.731: Mica Modem(1/0): Generate digits:called_party_num= len=1*Apr 7 12:39:42.835: Mica Modem(1/3): Rcvd Digit detected(#)*Apr 7 12:39:42.835: CSM_PROC_IC2_COLLECT_ADDR_INFO: CSM_EVENT_KP_DIGIT_COLLECTED (DNIS=, ANI=) at slot 1, port 3*Apr 7 12:39:42.855: neat msg at slot 0: (0/0): Tx LOOP_OPEN (ABCD=0101)*Apr 7 12:39:42.871: neat msg at slot 0: (1/0): Rx LOOP_OPEN (ABCD=0101)*Apr 7 12:39:42.899: Mica Modem(1/0): Rcvd Digits Generated*Apr 7 12:39:42.911: CSM_RX_CAS_EVENT_FROM_NEAT:(A001): EVENT_END_TX_TONE at slot 1 and port 0*Apr 7 12:39:42.911: CSM_PROC_OC4_DIALING: CSM_EVENT_DSX0_END_TX_TONE at slot 1, port 0*Apr 7 12:39:42.911: Mica Modem(1/0): Generate digits:called_party_num=A len=1*Apr 7 12:39:43.019: Mica Modem(1/0): Rcvd Digits Generated*Apr 7 12:39:43.019: CSM_PROC_OC4_DIALING: CSM_EVENT_TONE_GENERATED at slot 1, port 0*Apr 7 12:39:43.019: Mica Modem(1/3): Rcvd Digit detected(A)*Apr 7 12:39:43.335: CSM_RX_CAS_EVENT_FROM_NEAT:(A001): EVENT_START_TX_TONE at slot 1 and port 0*Apr 7 12:39:43.335: CSM_PROC_OC4_DIALING: CSM_EVENT_DSX0_START_TX_TONE at slot 1, port 0*Apr 7 12:39:43.335: Mica Modem(1/0): Generate digits:called_party_num=111222333444555666 len=19*Apr 7 12:39:43.439: Mica Modem(1/3): Rcvd Digit detected(1)*Apr 7 12:39:43.559: Mica Modem(1/3): Rcvd Digit detected(1)*Apr 7 12:39:43.619: Mica Modem(1/3): Rcvd Digit detected(1)*Apr 7 12:39:43.743: Mica Modem(1/3): Rcvd Digit detected(2)*Apr 7 12:39:43.859: Mica Modem(1/3): Rcvd Digit detected(2)*Apr 7 12:39:43.919: Mica Modem(1/3): Rcvd Digit detected(2)*Apr 7 12:39:44.043: Mica Modem(1/3): Rcvd Digit detected(3)*Apr 7 12:39:44.163: Mica Modem(1/3): Rcvd Digit detected(3)*Apr 7 12:39:44.223: Mica Modem(1/3): Rcvd Digit detected(3)*Apr 7 12:39:44.339: Mica Modem(1/3): Rcvd Digit detected(4)*Apr 7 12:39:44.459: Mica Modem(1/3): Rcvd Digit detected(4)*Apr 7 12:39:44.523: Mica Modem(1/3): Rcvd Digit detected(4)*Apr 7 12:39:44.639: Mica Modem(1/3): Rcvd Digit detected(5)*Apr 7 12:39:44.763: Mica Modem(1/3): Rcvd Digit detected(5)*Apr 7 12:39:44.883: Mica Modem(1/3): Rcvd Digit detected(5)*Apr 7 12:39:44.943: Mica Modem(1/3): Rcvd Digit detected(6)*Apr 7 12:39:45.063: Mica Modem(1/3): Rcvd Digit detected(6)*Apr 7 12:39:45.183: Mica Modem(1/3): Rcvd Digit detected(6)*Apr 7 12:39:45.243: Mica Modem(1/3): Rcvd Digit detected(B)*Apr 7 12:39:45.243: CSM_PROC_IC2_COLLECT_ADDR_INFO: CSM_EVENT_DNIS_COLLECTED (DNIS=111222333444555666, ANI=) at slot 1, port 3*Apr 7 12:39:45.363: Mica Modem(1/0): Rcvd Digits Generated*Apr 7 12:39:45.891: neat msg at slot 0: (0/0): Tx LOOP_CLOSURE (ABCD=1101)*Apr 7 12:39:45.907: neat msg at slot 0: (1/0): Rx LOOP_CLOSURE (ABCD=1101)*Apr 7 12:39:46.115: neat msg at slot 0: (0/0): Tx LOOP_OPEN (ABCD=0101)*Apr 7 12:39:46.131: neat msg at slot 0: (1/0): Rx LOOP_OPEN (ABCD=0101)*Apr 7 12:39:46.175: CSM_RX_CAS_EVENT_FROM_NEAT:(A001): EVENT_START_TX_TONE at slot 1 and port 0*Apr 7 12:39:46.175: CSM_PROC_OC4_DIALING: CSM_EVENT_DSX0_START_TX_TONE at slot 1, port 0*Apr 7 12:39:46.175: Mica Modem(1/0): Generate digits:called_party_num= len=3*Apr 7 12:39:46.267: Mica Modem(1/3): Rcvd Digit detected(#)*Apr 7 12:39:46.387: Mica Modem(1/3): Rcvd Digit detected(A)*Apr 7 12:39:46.447: Mica Modem(1/3): Rcvd Digit detected(B)*Apr 7 12:39:46.447: CSM_PROC_IC2_COLLECT_ADDR_INFO: CSM_EVENT_ADDR_INFO_COLLECTED (DNIS=111222333444555666, ANI=) at slot 1, port 3*Apr 7 12:39:46.507: Mica Modem(1/0): Rcvd Digits Generated*Apr 7 12:39:46.507: CSM_PROC_OC4_DIALING: CSM_EVENT_ADDR_INFO_COLLECTED at slot 1, port 0*Apr 7 12:39:47.127: CSM_RX_CAS_EVENT_FROM_NEAT:(0004): EVENT_CHANNEL_CONNECTED at slot 1 and port 3*Apr 7 12:39:47.127: CSM_PROC_IC4_WAIT_FOR_CARRIER: CSM_EVENT_DSX0_CONNECTED at slot 1, port 3*Apr 7 12:39:47.127: Mica Modem(1/3): Link Initiate*Apr 7 12:39:47.131: neat msg at slot 0: (0/0): Tx LOOP_CLOSURE (ABCD=1101)*Apr 7 12:39:47.147: neat msg at slot 0: (1/0): Rx LOOP_CLOSURE (ABCD=1101)*Apr 7 12:39:47.191: CSM_RX_CAS_EVENT_FROM_NEAT:(A001): EVENT_CHANNEL_CONNECTED at slot 1 and port 0*Apr 7 12:39:47.191: CSM_PROC_OC5_WAIT_FOR_CARRIER: CSM_EVENT_DSX0_CONNECTED at slot 1, port 0*Apr 7 12:39:47.191: Mica Modem(1/0): Link Initiate*Apr 7 12:39:47.227: Mica Modem(1/3): State Transition to Connect*Apr 7 12:39:47.287: Mica Modem(1/0): State Transition to Connect*Apr 7 12:39:49.103: Mica Modem(1/0): State Transition to Link*Apr 7 12:39:52.103: Mica Modem(1/3): State Transition to Link*Apr 7 12:40:00.927: Mica Modem(1/3): State Transition to Trainup*Apr 7 12:40:00.991: Mica Modem(1/0): State Transition to Trainup*Apr 7 12:40:02.615: Mica Modem(1/0): State Transition to EC Negotiating*Apr 7 12:40:02.615: Mica Modem(1/3): State Transition to EC NegotiatingCONNECT 31200 /V.42/V.42bisRouter>*Apr 7 12:40:05.983: Mica Modem(1/0): State Transition to Steady State*Apr 7 12:40:05.983: Mica Modem(1/3): State Transition to Steady State+++OKath*Apr 7 12:40:09.167: Mica Modem(1/0): State Transition to Steady State Escape*Apr 7 12:40:10.795: Mica Modem(1/0): State Transition to Terminating*Apr 7 12:40:10.795: Mica Modem(1/3): State Transition to Terminating*Apr 7 12:40:11.755: Mica Modem(1/3): State Transition to Idle*Apr 7 12:40:11.755: Mica Modem(1/3): Went onhook*Apr 7 12:40:11.755: CSM_PROC_IC5_OC6_CONNECTED: CSM_EVENT_MODEM_ONHOOK at slot 1, port 3*Apr 7 12:40:11.755: VDEV_DEALLOCATE: slot 1 and port 3 is deallocated*Apr 7 12:40:11.759: neat msg at slot 0: (0/0): Tx LOOP_OPEN (ABCD=0101)*Apr 7 12:40:11.767: neat msg at slot 0: (1/0): Rx LOOP_OPEN (ABCD=0101)*Apr 7 12:40:12.087: neat msg at slot 0: (1/0): Tx LOOP_OPEN (ABCD=0101)*Apr 7 12:40:12.091: neat msg at slot 0: (0/0): Rx LOOP_OPEN (ABCD=0101)*Apr 7 12:40:12.111: CSM_RX_CAS_EVENT_FROM_NEAT:(A001): EVENT_CALL_IDLE at slot 1 and port 0*Apr 7 12:40:12.111: CSM_PROC_IC5_OC6_CONNECTED: CSM_EVENT_DSX0_DISCONNECTED at slot 1, port 0*Apr 7 12:40:12.111: Mica Modem(1/0): Link Terminate(0x6)*Apr 7 12:40:12.779: Mica Modem(1/3): State Transition to Terminating*Apr 7 12:40:12.839: Mica Modem(1/3): State Transition to Idle*Apr 7 12:40:13.495: Mica Modem(1/0): State Transition to Idle*Apr 7 12:40:13.495: Mica Modem(1/0): Went onhook*Apr 7 12:40:13.495: CSM_PROC_IC6_OC8_DISCONNECTING: CSM_EVENT_MODEM_ONHOOK at slot 1, port 0*Apr 7 12:40:13.495: VDEV_DEALLOCATE: slot 1 and port 0 is deallocatedRouter#discClosing connection to 1.19.36.7 [confirm]Router#*Apr 7 12:40:18.783: Mica Modem(1/0): State Transition to Terminating*Apr 7 12:40:18.843: Mica Modem(1/0): State Transition to IdleRouter#The MICA technologies modem goes through the following internal link states when the call comes in:
•
•
•
•
•
•
•
The following section describes the CSM activity for an incoming call.
When a voice call comes in, CSM is informed of the incoming call. This allocates the modem and sends the Call Setup message to the MICA modem. The Call_Proc message is sent through D channel. The modem sends an offhook message to CSM by sending the state change to Call Setup. The D channel then sends a CONNECT message. When the CONNECT_ACK message is received, the Link initiate message is sent to the MICA modem and it negotiates the connection with the remote modem. In the following debug examples, a modem on slot 1, port 13 is allocated. It goes through its internal states before it is in Steady State and answers the call.
Router# debug modem csmModem Management Call Switching Module debugging is on*May 13 15:01:00.609: MODEM_REPORT:dchan_idb=0x60D437F8, call_id=0xE, ces=0x1bchan=0x12, event=0x1, cause=0x0*May 13 15:01:00.609: VDEV_ALLOCATE: slot 1 and port 13 is allocated.*May 13 15:01:00.609: MODEM_REPORT(000E): DEV_INCALL at slot 1 and port 13*May 13 15:01:00.609: CSM_PROC_IDLE: CSM_EVENT_ISDN_CALL at slot 1, port 13*May 13 15:01:00.609: Mica Modem(1/13): Configure(0x0)*May 13 15:01:00.609: Mica Modem(1/13): Configure(0x0)*May 13 15:01:00.609: Mica Modem(1/13): Configure(0x6)*May 13 15:01:00.609: Mica Modem(1/13): Call Setup*May 13 15:01:00.661: Mica Modem(1/13): State Transition to Call Setup*May 13 15:01:00.661: Mica Modem(1/13): Went offhook*May 13 15:01:00.661: CSM_PROC_IC1_RING: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 13*May 13 15:01:00.661: MODEM_REPORT:dchan_idb=0x60D437F8, call_id=0xE, ces=0x1bchan=0x12, event=0x4, cause=0x0*May 13 15:01:00.661: MODEM_REPORT(000E): DEV_CONNECTED at slot 1 and port 13*May 13 15:01:00.665: CSM_PROC_IC3_WAIT_FOR_CARRIER:CSM_EVENT_ISDN_CONNECTED at slot 1, port 13*May 13 15:01:00.665: Mica Modem(1/13): Link Initiate*May 13 15:01:00.693: Mica Modem(1/13): State Transition to Connect*May 13 15:01:01.109: Mica Modem(1/13): State Transition to Link*May 13 15:01:09.433: Mica Modem(1/13): State Transition to Trainup*May 13 15:01:11.541: Mica Modem(1/13): State Transition to EC Negotiating*May 13 15:01:12.501: Mica Modem(1/13): State Transition to Steady StateThe following section describes the status of CSM when a call is connected.
The show modem csm x/y command is similar to AS5200 access server. For an active incoming analog call, the modem_status and csm_status should be VDEV_STATUS_ACTIVE_CALL and CSM_IC4_CONNECTED, respectively.
Router# show modem csm 1/13MODEM_INFO: slot 1, port 13, unit 0, modem_mask=0x0000, modem_port_offset=0tty_hwidb=0x60D0BCE0, modem_tty=0x60B6FE7C, oobp_info=0x00000000,modem_pool=0x60ADC998modem_status(0x0002):VDEV_STATUS_ACTIVE_CALL.csm_state(0x0204)=CSM_IC4_CONNECTED, csm_event_proc=0x600C6968, currentcall thru PRI lineinvalid_event_count=0, wdt_timeout_count=0wdt_timestamp_started is not activatedwait_for_dialing:False, wait_for_bchan:Falsepri_chnl=TDM_PRI_STREAM(s0, u0, c18), modem_chnl=TDM_MODEM_STREAM(s1, c13)dchan_idb_start_index=0, dchan_idb_index=0, call_id=0x000E, bchan_num=18csm_event=CSM_EVENT_ISDN_CONNECTED, cause=0x0000ring_indicator=0, oh_state=0, oh_int_enable=0, modem_reset_reg=0ring_no_answer=0, ic_failure=0, ic_complete=1dial_failure=0, oc_failure=0, oc_complete=0oc_busy=0, oc_no_dial_tone=0, oc_dial_timeout=0remote_link_disc=0, stat_busyout=0, stat_modem_reset=0oobp_failure=0call_duration_started=1d02h, call_duration_ended=00:00:00,total_call_duration=00:00:00The calling party phone number = 4085552400The called party phone number = 4085551400total_free_rbs_timeslot = 0, total_busy_rbs_timeslot = 0,total_dynamic_busy_rbs_timeslot = 0, total_static_busy_rbs_timeslot = 0,min_free_modem_threshold = 6The following section describes the CSM activity for an outgoing call.
For MICA modems, the dial tone is not required to initiate an outbound call. Unlike in the AS5200, the digit collection step is not required. The dialed digit string is sent to the CSM in the outgoing request to the CSM. CSM signals the D channel to generate an outbound voice call, and the B channel assigned is connected to the modem and the CSM.
The modem is ordered to connect to the remote side with a CONNECT message, and by sending a link initiate message, the modem starts to train.
Router# debug modem csmModem Management Call Switching Module debugging is onRouter# debug isdn q931ISDN Q931 packets debugging is on*May 15 12:48:42.377: Mica Modem(1/0): Rcvd Dial String(5552400)*May 15 12:48:42.377: CSM_PROC_IDLE: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 0*May 15 12:48:42.377: CSM_PROC_OC3_COLLECT_ALL_DIGIT:CSM_EVENT_GET_ALL_DIGITS at slot 1, port 0*May 15 12:48:42.377: CSM_PROC_OC3_COLLECT_ALL_DIGIT: called party num:(5552400) at slot 1, port 0*May 15 12:48:42.381: process_pri_call making a voice_call.*May 15 12:48:42.381: ISDN Se0:23: TX -> SETUP pd = 8 callref = 0x0011*May 15 12:48:42.381: Bearer Capability i = 0x8090A2*May 15 12:48:42.381: Channel ID i = 0xE1808397*May 15 12:48:42.381: Called Party Number i = 0xA1, '5552400'*May 15 12:48:42.429: ISDN Se0:23: RX <- CALL_PROC pd = 8 callref = 0x8011*May 15 12:48:42.429: Channel ID i = 0xA98397*May 15 12:48:42.429: MODEM_REPORT:dchan_idb=0x60D437F8, call_id=0xA011, ces=0x1bchan=0x16, event=0x3, cause=0x0*May 15 12:48:42.429: MODEM_REPORT(A011): DEV_CALL_PROC at slot 1 and port 0*May 15 12:48:42.429: CSM_PROC_OC4_DIALING: CSM_EVENT_ISDN_BCHAN_ASSIGNEDat slot 1, port 0*May 15 12:48:42.429: Mica Modem(1/0): Configure(0x1)*May 15 12:48:42.429: Mica Modem(1/0): Configure(0x0)*May 15 12:48:42.429: Mica Modem(1/0): Configure(0x6)*May 15 12:48:42.429: Mica Modem(1/0): Call Setup*May 15 12:48:42.489: Mica Modem(1/0): State Transition to Call Setup*May 15 12:48:42.589: ISDN Se0:23: RX <- ALERTING pd = 8 callref = 0x8011*May 15 12:48:43.337: ISDN Se0:23: RX <- CONNECT pd = 8 callref = 0x8011*May 15 12:48:43.341: MODEM_REPORT:dchan_idb=0x60D437F8, call_id=0xA011, ces=0x1bchan=0x16, event=0x4, cause=0x0*May 15 12:48:43.341: MODEM_REPORT(A011): DEV_CONNECTED at slot 1 and port 0*May 15 12:48:43.341: CSM_PROC_OC5_WAIT_FOR_CARRIER:CSM_EVENT_ISDN_CONNECTED at slot 1, port 0*May 15 12:48:43.341: Mica Modem(1/0): Link Initiate*May 15 12:48:43.341: ISDN Se0:23: TX -> CONNECT_ACK pd = 8 callref = 0x0011*May 15 12:48:43.385: Mica Modem(1/0): State Transition to Connect*May 15 12:48:43.849: Mica Modem(1/0): State Transition to Link*May 15 12:48:52.665: Mica Modem(1/0): State Transition to Trainup*May 15 12:48:54.661: Mica Modem(1/0): State Transition to EC Negotiating*May 15 12:48:54.917: Mica Modem(1/0): State Transition to Steady StateRelated Commands
debug modem dsip
To display output for modem control messages that are received or sent to the router, use the debug modem dsip command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem dsip {tty-range | group | shelf/slot/port}
no debug modem dsip {tty-range | group | shelf/slot/port}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug modem dsip command displays each Distributed System Interconnect Protocol (DSIP) message that relates to a modem and is sent from or received at the router shelf. This command can be applied to a single modem or a group of modems.
Examples
The following examples show a display of the available debug modem command options and debug modem dsip command options:
Router# debug modem ?dsip Modem DSIP activitymaintenance Modem maintenance activityoob Modem out of band activitytrace Call Trace Uploadtraffic Modem data traffic<cr>Router# debug modem dsip ?<0-935> First Modem TTY Numbergroup Modem group informationx/y/z Shelf/Slot/Port for Internal Modems<cr>The following example indicates that a Real Time Server (RTS) status message was received from the router shelf, and an ACK message was sent back:
Router# debug modem dsip00:11:02: RSMODEM_SEND-1/2/06: MODEM_RING_INDICATION_MSG cci1 si0 ms0 mm65535,0 dc000:11:02: RSMODEM_sRCV-1/2/06:l12,MODEM_CALL_ACK_MSG:00:11:02: RSMODEM_SEND-1/2/06: MODEM_CALL_ACCEPT_MSG00:11:11: RSMODEM_sRCV-2:l0,MODEM_POLL_MSG: 0 16 0 7 0 146 0 36 2100:11:18: RSMODEM_sRCV-1/2/06:l12,MODEM_SET_DCD_STATE_MSG: 100:11:19: RSMODEM_SEND-1/2/06: MODEM_RTS_STATUS_MSG 100:11:19: RSMODEM_dRCV-2:l1258607996,MODEM_RTS_STATUS_MSG: 0 6 0 23 0 0 0 0 000:11:23: RSMODEM_sRCV-2:l0,MODEM_POLL_MSG: 0 16 0 7 0 146 0 150 2100:12:31: RSMODEM_sRCV-1/2/06:l12,MODEM_SET_DCD_STATE_MSG: 000:12:31: RSMODEM_SEND-1/2/06: MODEM_CALL_HANGUP_MSG00:12:31: RSMODEM_sRCV-1/2/06:l12,MODEM_ONHOOK_MSG:00:12:32: RSMODEM_SEND-1/2/06: MODEM_RTS_STATUS_MSG 100:12:32: RSMODEM_SEND-1/2/06: MODEM_SET_DTR_STATE_MSG 000:12:32: RSMODEM_dRCV-2:l1258659676,MODEM_RTS_STATUS_MSG: 0 6 0 16 0 0 0 0 000:12:32: RSMODEM_SEND-1/2/06: MODEM_RTS_STATUS_MSG 100:12:32: RSMODEM_dRCV-2:l1258600700,MODEM_RTS_STATUS_MSG: 0 6 0 13 0 0 0 0 000:12:33: RSMODEM_SEND-1/2/06: MODEM_SET_DTR_STATE_MSG 000:12:33: RSMODEM_SEND-1/2/06: MODEM_RTS_STATUS_MSG 100:12:33: RSMODEM_dRCV-2:l1258662108,MODEM_RTS_STATUS_MSG: 0 6 0 16 0 0 0 0 000:12:35: RSMODEM_sRCV-2:l0,MODEM_POLL_MSG: 0 16 0 7 0 146 1 34 2200:12:38: RSMODEM_SEND-1/2/06: MODEM_SET_DTR_STATE_MSG 100:12:47: RSMODEM_sRCV-2:l0,MODEM_POLL_MSG: 0 16 0 7 0 146 0 12 22Table 212 describes the significant fields shown in the display.
Related Commands
debug modem oob
To debug the out-of-band port used to poll modem events on the modem, use the debug modem oob command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem oob [slot/modem-port | group group-number]
no debug modem oob [slot/modem-port | group group-number]
Syntax Description
slot/modem-port
(Optional) The slot and modem port number.
group group-number
(Optional) The modem group.
Command Modes
Privileged EXEC
Usage Guidelines
The message types and sequence numbers that appear in the debugging output are initiated by the Modem Out-of-Band Protocol and used by service personnel for debugging purposes.
Caution
Examples
The following is sample output from the debug modem oob command. This example debugs the out-of-band port on modem 2/0, which creates modem startup messages between the network management software and the modem.
Router# debug modem oob 2/0MODEM(2/0): One message sent --Message type:3, Sequence number:0MODEM(2/0): Modem DC session data replyMODEM(2/0): One message sent --Message type:83, Sequence number:1MODEM(2/0): DC session event =MODEM(2/0): One message sent --Message type:82, Sequence number:2MODEM(2/0): No status changes since last polledMODEM(2/0): One message sent --Message type:3, Sequence number:3MODEM(2/0): Modem DC session data replyMODEM(2/0): One message sent --Message type:83, Sequence number:4debug modem relay errors
To view modem relay network errors, use the debug modem relay errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] errors
no debug modem relay [call-identifier call-setup-time call-index] errors
Syntax Description
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
In a stable modem relay network, the debug modem relay errors command produces little output.
Examples
The following is sample output from the debug modem relay errors command. The output shows the sequence number of the packet, time stamp, direction, layer, and payload bytes, followed by each byte of the payload in hexadecimal.
Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 28 tm 11944 OUT ERR, pb=12, payload: 00 06 00 00 00 00 00 07 00 00 01 DE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 29 tm 11944 OUT ERR, pb=12, payload: 00 06 00 00 00 00 00 04 00 00 00 BE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 30 tm 11944 OUT ERR, pb=12, payload: 00 06 00 00 00 00 00 05 FF FF FF FDRelated Commands
debug hpi all
Displays gateway DSP modem relay termination codes.
debug modem relay events
Displays events that may cause failure of the modem relay network.
debug modem relay events
To view the events that may cause failure of the modem relay network, use the debug modem relay events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] events
no debug modem relay [call-identifier call-setup-time call-index] events
Syntax Description
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
In a stable modem relay network, the debug modem relay events command produces little output.
Examples
The following is sample output from the debug modem relay events command. The output shows the sequence number of the packet, time stamp, direction, layer, and payload bytes, followed by each byte of the payload in hexadecimal.
Router# debug modem relay eventsJan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 28 tm 11944 OUT EVNT, pb=12, payload: 00 06 00 00 00 00 00 07 00 00 01 DE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 29 tm 11944 OUT EVNT, pb=12, payload: 00 06 00 00 00 00 00 04 00 00 00 BE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 30 tm 11944 OUT EVNT, pb=12, payload: 00 06 00 00 00 00 00 05 FF FF FF FDRelated Commands
debug hpi all
Displays gateway DSP modem relay termination codes.
debug modem relay errors
Displays modem relay network errors.
debug modem relay packetizer
To view events occurring in the modem relay packetizer module, use the debug modem relay packetizer command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] packetizer
no debug modem relay [call-identifier call-setup-time call-index] packetizer
Syntax Description
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Disable console logging and use buffered logging before using the debug modem relay packetizer command. Using the debug modem relay packetizer command generates a large volume of debugs, which can affect router performance.
Examples
The following is sample output from the debug modem relay packetizer command. The output shows the sequence number of the packet, time stamp, direction, layer, and payload bytes, followed by each byte of the payload in hexadecimal.
Router# debug modem relay packetizerJan 11 05:33:33.715:ModemRelay pkt[0:D:11]. sqn 8 tm 47610 IN PKTZR, pb=7, payload: 82 38 00 18 03 01 87*Jan 11 05:33:33.727:ModemRelay pkt[0:D:11]. sqn 9 tm 47616 OUT PKTZR, pb=7, payload: 82 20 00 18 03 01 47*Jan 11 05:33:35.719:ModemRelay pkt[0:D:11]. sqn 10 tm 49614 IN PKTZR, pb=7, payload: 82 39 00 18 03 01 87Related Commands
debug hpi all
Displays gateway DSP modem relay termination codes.
debug modem relay errors
Displays modem relay network errors.
debug modem relay physical
To view modem relay physical layer packets, use the debug modem relay physical command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] physical
no debug modem relay [call-identifier call-setup-time call-index] physical
Syntax Description
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Disable console logging and use buffered logging before using the debug modem relay physical command. Using the debug modem relay physical command generates a large volume of debugs, which can affect router performance.
Examples
The following is sample output from the debug modem relay physical command. The output shows the sequence number of the packet, time stamp, direction, layer, and payload bytes, followed by each byte of the payload in hexadecimal.
Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 28 tm 11944 OUT PHYS, pb=12, payload: 00 06 00 00 00 00 00 07 00 00 01 DE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 29 tm 11944 OUT PHYS, pb=12, payload: 00 06 00 00 00 00 00 04 00 00 00 BE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 30 tm 11944 OUT PHYS, pb=12, payload: 00 06 00 00 00 00 00 05 FF FF FF FDRelated Commands
debug hpi all
Displays gateway DSP modem relay termination codes.
debug modem relay errors
Displays modem relay network errors.
debug modem relay sprt
To view modem relay Simple Packet Relay Transport (SPRT) protocol packets, use the debug modem relay sprt command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] sprt
no debug modem relay [call-identifier call-setup-time call-index] sprt
Syntax Description
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Disable console logging and use buffered logging before using the debug modem relay sprt command. Using the debug modem relay sprt command generates a large volume of debugs, which can affect router performance.
Examples
The following is sample output from the debug modem relay sprt command. The output shows the sequence number of the packet, time stamp, direction, layer, and payload bytes, followed by each byte of the payload in hexadecimal.
Jan 11 05:37:16.151:ModemRelay pkt[0:D:11]. sqn 34 tm 7910 OUT SPRT, pb=4, payload: 02 00 03 71*Jan 11 05:37:16.295:ModemRelay pkt[0:D:11]. sqn 35 tm 8048 IN SPRT, pb=13, payload: 02 00 01 F1 F7 7E FD F5 90 F3 3E 90 55*Jan 11 05:37:16.303:ModemRelay pkt[0:D:11]. sqn 36 tm 8060 IN SPRT, pb=6, payload: 02 00 01 41 04 00Related Commands
debug hpi all
Displays gateway DSP modem relay termination codes.
debug modem relay errors
Displays modem relay network errors.
debug modem relay udp
To view events occurring in the User Datagram Protocol (UDP) stack, use the debug modem relay udp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] udp
no debug modem relay [call-identifier call-setup-time call-index] udp
Syntax Description
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Disable console logging and use buffered logging before using the debug modem relay udp command. Using the debug modem relay udp command generates a large volume of debugs, which can affect router performance.
Examples
The following is sample output from the debug modem relay udp command. The output shows three UDP packets related to modem relay. In the sample output, OUT or IN represent packet direction, and UDP indicates the specific layer that reported the packet.
Jan 1 03:39:29.407:ModemRelay pkt[0:D (4)]. sqn 61 tm 3060 OUT UDP, pb=6, payload: 80 00 00 00 00 00*Jan 1 03:39:29.471:ModemRelay pkt[0:D (4)]. sqn 62 tm 3120 IN UDP, pb=6, payload: 40 00 00 00 00 00*Jan 1 03:39:29.471:ModemRelay pkt[0:D (4)]. sqn 63 tm 3120 IN UDP, pb=6, payload: 80 00 00 00 00 00Related Commands
debug hpi all
Displays gateway DSP modem relay termination codes.
debug modem relay errors
Displays modem relay network errors.
debug modem relay v14
To observe events occurring in the V.14 layer, use the debug modem relay v14 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] v14
no debug modem relay [call-identifier call-setup-time call-index] v14
Syntax Description
Command Default
No debugging output is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug modem relay v14 command to debug V.14 layer modem relay calls. Using this command generates a large volume of debugs, which can affect router performance; disable console logging and use buffered logging before using the debug modem relay v14 command. In most instances you will use this command only at the request of Cisco Technical Assistance Center (TAC).
Examples
The following is sample output from the debug modem relay v14 command. The output shows the sequence number of the packet time stamp, direction, layer, and payload bytes, followed by each byte of the payload in hexadecimal.
Router# debug modem relay v14*Aug 10 22:51:37.496: ModemRelay pkt[1/1:1]. sqn 15649 tm 48766 OUT V14, pb=18, payload: 08 BC 4C 51 CE 1A 69 ED D6 65 62 8C 7F D3 9A 82 5A 7A*Aug 10 22:51:38.216: ModemRelay pkt[1/1:1]. sqn 15650 tm 48778 IN V14, pb=22, payload: 9A 9C 7F 57 2D D7 4C 98 E8 EC FC 73 69 F2 FF A3 E8 B0 A4 58 BB AE*Aug 10 22:51:38.216: ModemRelay pkt[1/1:1]. sqn 15651 tm 48790 OUT V14, pb=18, payload: 64 F9 73 D3 AB 11 61 ED 1E 5D 51 8D B1 9F CA 49 BF F4*Aug 10 22:51:38.216: ModemRelay pkt[1/1:1]. sqn 15652 tm 48796 IN V14, pb=21, payload: C1 77 90 12 F8 37 E8 7A 64 8D 0E 61 58 7E E4 E8 87 E0 B4 83 C7 A4 60 7A 64 8B 09 B9 80 2E E5 2E 94 65 79 C2 A8 E9 6F D9 6C 3BRelated Commands
debug hpi all
Displays gateway DSP modem relay termination codes.
debug modem relay errors
Displays modem relay network errors.
debug modem relay v42
To view events occurring in the V.42 layer, use the debug modem relay v42 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] v42
no debug modem relay [call-identifier call-setup-time call-index] v42
Syntax Description
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Disable console logging and use buffered logging before using the debug modem relay v42 command. Using the debug modem relay v42 command generates a large volume of debugs, which can affect router performance.
Examples
The following is sample output from the debug modem relay v42 command. The output shows the sequence number of the packet, timestamp, direction, layer, and payload-bytes, followed by each byte of the payload in hexadecimal.
Jan 11 05:42:08.715:ModemRelay pkt[0:D:13]. sqn 3 tm 10104 OUT V42, pb=43, payload: 03 AF 82 80 00 13 03 03 8A 89 00 05 02 03 E0 06 02 03 E0 07 01 08 08 01 08 F0 00 0F 00 03 56 34 32 01 01 03 02 02 04 00 03 01 20*Jan 11 05:42:08.847:ModemRelay pkt[0:D:13]. sqn 4 tm 10236 IN V42, pb=2, payload: 03 7FRelated Commands
debug hpi all
Displays gateway DSP modem relay termination codes.
debug modem relay errors
Displays modem relay network errors.
debug modem trace
To debug a call trace on the modem to determine why calls are terminated, use the debug modem trace command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem trace [normal | abnormal | all] [slot/modem-port | group group-number]
no debug modem trace [normal | abnormal | all] [slot/modem-port | group group-number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
The debug modem trace command applies only to manageable modems. For additional information, use the show modem command.
Examples
The following is sample output from the debug modem trace abnormal command:
Router# debug modem trace abnormal 1/14Modem 1/14 Abnormal End of Connection Trace. Caller 123-4567Start-up Response: AS5200 Modem, Firmware 1.0Control Reply: 0x7C01DC session response: brasil firmware 1.0RS232 event:DSR=On, DCD=On, RI=Off, TST=Offchanges: RTS=No change, DTR=No change, CTS=No changechanges: DSR=No change, DCD=No change, RI=No change, TST=No changeModem State event: ConnectedConnection event: Speed = 19200, Modulation = VFCDirection = Originate, Protocol = reliable/LAPM, Compression = V42bisDTR event: DTR OnModem Activity event: Data ActiveModem Analog signal event: TX = -10, RX = -24, Signal to noise = -32End connection event: Duration = 10:34-11:43,Number of xmit char = 67, Number of rcvd char = 88, Reason: Watchdog Time-out.Related Commands
debug modem traffic
To display output for framed, unframed, and asynchronous data sent received from the modem cards, use the debug modem traffic command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem traffic
no debug modem traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug modem traffic command displays output for framed, unframed, and asynchronous data sent or received by the modem cards.
Examples
The following example displays information about unframed or framed data sent to or received from the modem cards:
Router# debug modem trafficMODEM-RAW-TX:modem = 6/5/00, length = 1, data = 0x61, 0xFF, 0x7D, 0x23MODEM-RAW-RX:modem = 6/5/00, length = 1, data = 0x61, 0x0, 0x0, 0x0The information indicates unframed asynchronous data transmission and reception involving the modem on shelf 6, slot 5, port 00.
The following example displays framed asynchronous data transmission and reception involving the modem on shelf 6, slot 5, port 00:
Router# debug modem trafficMODEM-FRAMED-TX:modem = 6/5/00, length = 8, data = 0xFF, 0x3, 0x82MODEM-FRAMED-RX:modem = 6/5/00, length = 14, data = 0xFF, 0x3, 0x80Related Commands
debug modem dsip
Displays output for modem control messages that are received or sent to the router.
debug mpls adjacency
To display changes to label switching entries in the adjacency database, use the debug mpls adjacency command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls adjacency
no debug mpls adjacency
Usage Guidelines
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug mpls adjacency command to monitor when entries are updated in or added to the adjacency database.
Examples
The following is sample output from the debug mpls adjacency command:
Router# debug mpls adjacencyTAG ADJ: add 10.10.0.1, Ethernet0/0/0TAG ADJ: update 10.10.0.1, Ethernet0/0/0Table 213 describes the significant fields shown in the sample display.
debug mpls atm-cos
Note
To display ATM label virtual circuit (VC) bind or request activity that is based on the configuration of a Quality of Service (QoS) map, use the debug mpls atm-cos command in privileged EXEC mode. To disable this feature, use the no form of this command.
debug mpls atm-cos [bind | request]
no debug mpls atm-cos [bind | request]
Syntax Description
bind
(Optional) Specifies debug information about bind responses for a VC path.
request
(Optional) Specifies debug information about bind requests for a VC path.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following command sequence demonstrates how to obtain sample output from the debug mpls atm-cos command.
First, display the Multiprotocol Label Switching (MPLS) forwarding table to see which prefixes are associated with a single label VC (LVC), as shown below:
Router# show mpls forwardingLocal Outgoing Prefix Bytes tag Outgoing Next Hoptag tag or VC or Tunnel Id switched interface26 28 10.17.17.17/32 0 PO6/0 point2point27 Pop tag 10.11.11.11/32 1560 PO6/0 point2point28 27 10.16.16.16/32 0 PO6/0 point2point29 30 10.92.0.0/8 0 PO6/0 point2point30 Pop tag 10.95.0.0/8 2600 PO6/0 point2point31 2/34 10.10.10.10/32 0 AT2/0.1 point2point32 Pop tag 10.14.14.14/32 0 Fa5/0 10.91.0.133 Pop tag 10.90.0.0/8 0 Fa5/0 10.91.0.134 Pop tag 10.96.0.0/8 0 Fa5/0 10.91.0.12/36 10.96.0.0/8 0 AT2/0.1 point2point35 35 10.93.0.0/8 0 PO6/0 point2point36 36 10.12.12.12/32 0 PO6/0 point2point37 37 10.15.15.15/32 0 PO6/0 point2point38 37 10.18.18.18/32 0 Fa5/0 10.91.0.139 39 10.97.0.0/8 540 PO6/0 point2point40 40 10.98.0.0/8 0 PO6/0 point2pointSecond, enable debugging of request and bind events, as shown in the command sequence below:
Router# debug mpls atm-cos ?bind Bind response for VC pathrequest Requests for VC binds pathRouter# debug mpls atm-cos requestATM TAGCOS VC requests debugging is onRouter# debug mpls atm-cos bindATM TAGCOS Bind response debugging is onThird, configure an MPLS ATM subinterface for multi-VC mode. The corresponding request and bind events are displayed, as shown below:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface a2/0.1Router(config-subif)# mpls atm multi-vcRouter(config-subif)# endRouter#19:59:14:%SYS-5-CONFIG_I:Configured from console by consoleRouter#19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, available19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, standard19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, premium19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, control19:59:24:TAGCOS-REQ:vc request 10.96.0.0/8, available19:59:24:TAGCOS-REQ:vc request 10.96.0.0/8, standard19:59:24:TAGCOS-REQ:vc request 10.96.0.0/8, premium19:59:24:TAGCOS-REQ:vc request 10.96.0.0/8, controlTAGCOS-REQ/TCATM:10.11.11.11/32,len=4352,band=1099528405504,class=0x700TAGCOS-REQ/TCATM:10.12.12.12/32,len=4352,band=2199040033280,class=0x700TAGCOS-REQ/TCATM:10.13.13.13/32,len=4352,band=3298551661056,class=0x700TAGCOS-REQ/TCATM:10.14.14.14/32,len=4352,band=4398063288832,class=0x700TAGCOS-REQ/TCATM:10.15.15.15/32,len=4352,band=5497574916608,class=0x700TAGCOS-REQ/TCATM:10.16.16.16/32,len=4352,band=6597086544384,class=0x700TAGCOS-REQ/TCATM:10.17.17.17/32,len=4352,band=7696598172160,class=0x700TAGCOS-REQ/TCATM:10.18.18.18/32,len=4352,band=8796109799936,class=0x700TAGCOS-REQ/TCATM:10.90.0.0/8,len=768,band=3940649674539009,class=0x2TAGCOS-REQ/TCATM:10.91.0.0/8,len=768,band=3940649674604545,class=0x2TAGCOS-REQ/TCATM:10.92.0.0/8,len=768,band=3940649674670081,class=0x2TAGCOS-REQ/TCATM:10.93.0.0/8,len=768,band=3940649674735617,class=0x2TAGCOS-REQ/TCATM:10.94.0.0/8,len=768,band=3940649674801153,class=0x2TAGCOS-REQ/TCATM:10.95.0.0/8,len=768,band=3940649674866689,class=0x2TAGCOS-REQ/TCATM:10.97.0.0/8,len=768,band=3940649674932225,class=0x2TAGCOS-REQ/TCATM:10.98.0.0/8,len=768,band=3940649674997761,class=0x2TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=41 - control 41,41,41,41TAGCOS-BIND:binding_ok 10.10.10.10/32, Inform TFIB pidx=0, in_tag=31, idx=0x80000000TAGCOS-BIND:binding_ok 10.96.0.0/8,VCD=42 - control 42,42,42,42TAGCOS-BIND:binding_ok 10.96.0.0/8, Inform TFIB pidx=1, in_tag=34, idx=0x80000001TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=43 - premium 43,43,43,41TAGCOS-BIND:binding_ok 10.96.0.0/8,VCD=44 - premium 44,44,44,42TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=45 - standard 45,45,43,41TAGCOS-BIND:binding_ok 10.96.0.0/8,VCD=46 - standard 46,46,44,42TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=47 - available 47,45,43,41TAGCOS-BIND:binding_ok 10.96.0.0/8,VCD=48 - available 48,46,44,42debug mpls atm-ldp api
Note
To display information about the virtual channel identifier (VCI) allocation of label virtual circuits (LVCs), label-free requests, and cross-connect requests, use the debug mpls atm-ldp api command in privileged EXEC mode. To disable this feature, use the no form of this command.
debug mpls atm-ldp api
no debug mpls atm-ldp api
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the debug mpls atm-ldp api command in conjunction with the debug mpls atm-ldp routes and debug mpls atm-ldp states command to display more complete information about an LVC.
Examples
The following shows sample output from the debug mpls atm-ldp api command:
Router# debug mpls atm-ldp apiTailend Router Free label Req 167.50.0.0 on ATM0/0.2 VPI/VCI 1/674TAGATM_API: received label free requestinterface: ATM0/0.2 dir: in vpi: 1 vci: 674TAGATM_API: completed label freeinterface: ATM0/0.2 vpi: 1 vci: 674result: TAGATM_OKTable 214 describes the significant fields shown in the display.
Related Commands
debug mpls atm-ldp states
Displays information about LVC state transitions as they occur.
debug mpls atm-ldp failure
To display failure information about the LC-ATM, use the debug mpls atm-ldp failure command in privileged EXEC mode. To disable this feature, use the no form of the command.
debug mpls atm-ldp failure
no debug mpls atm-ldp failure
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug mpls atm-ldp failure command to display failure information about the LC-ATM. This command is useful for determining failure cases. This command displays only failure information, unlike the debug mpls atm-ldp api command, which displays all API events.
Examples
This section shows sample output from the debug mpls atm-ldp failure command.
The following failure message displays during a race condition where the LC-ATM attempts to allocate label virtual circuits (LVCs) on an interface where MPLS has been disabled:
Router# debug mpls atm-ldp failureTAGATM_API_FAILURE: allocate_tag_req on ATM1/0/0 tagsw not enabledThe following failure message displays when the LC-ATM fails to deallocate the output leg LVC of a cross connect:
Router# debug mpls atm-ldp failureTAGATM_API_FAILURE: connDeAllocateHalfLeg returned false interface: ATM1/0/0vpi: 1 vci: 48The following failure message displays when a cross connect cannot be installed on the switching fabric. The result code is also provided.
Router# debug mpls atm-ldp failureTAGATM_API_FAILURE: setup_xconn_req InstallSvcXconn failed resultThe following message displays when attempts to establish a cross connect fail. The result describes the reason for the failure.
Router# debug mpls atm-ldp failureTCATM-4-XCONNECT_FAILED: 10.254.13.237/32 for ATM0/1/2 ATM1/0/0TAGATM_API: x-conn setup request completedinput interface: ATM0/1/2 vpi: 1 vci: 48output interface: ATM1/0/0 vpi: 2 vci: 2038result = TAGATM_FAILXconnect setup response for 10.254.13.215: failure, 8The following message displays when attempts to remove a cross connect fail. The result describes why the cross connect cannot be removed.
Router# debug mpls atm-ldp failureTCATM-4-XCONNECT_REMOVE_FAILED: Remove XConnect API failed for ATM1/0/12 1/894-> ATM1/0/13 1/528TAGATM_API: x-conn remove request completedinput interface: ATM1/0/12 vpi: 1 vci: 894output interface: ATM1/0/13 vpi: 1 vci: 528result = TAGATM_FAILRelated Commands
debug mpls atm-ldp routes
Note
To display information about the state of the routes for which virtual circuit identifier (VCI) requests are being made, use the debug mpls atm-ldp routes command in privileged EXEC mode. To disable this feature, use the no form of this command.
debug mpls atm-ldp routes
no debug mpls atm-ldp routes
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
When there are many routes and system activities (that is, shutting down interfaces, learning new routes, and so forth), the debug mpls atm-ldp routes command displays extensive information that might interfere with system timing. Most commonly, this interference affects normal label distribution protocol (LDP) operation. To avoid this problem, you can increase the LDP hold time by means of the mpls ldp holdtime command.
Examples
The following shows sample output from the debug mpls atm-ldp routes command:
Router# debug mpls atm-ldp routesCleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0tcatmFindRouteTags,153.7.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0AddNewRoute,153.7.0.0/16,idb=ATM0/0.2CleanupRoutes,153.7.0.0/16CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0tcatmFindRouteTags,153.8.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0AddNewRoute,153.8.0.0/16,idb=ATM0/0.2CleanupRoutes,153.8.0.0/16CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0tcatmFindRouteTags,153.9.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0AddNewRoute,153.9.0.0/16,idb=ATM0/0.2CleanupRoutes,153.9.0.0/16CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0tcatmFindRouteTags,153.10.0.0/16,idb
