|
|
Table Of Contents
debug vwic-mft firmware controller
debug vpm dsp
To show messages from the digital signal processor (DSP) on the voice port module VPM) to the router, use the debug vpm dsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpm dsp
no debug vpm dsp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The debug vpm dsp command shows messages from the DSP on the VPM to the router; this command can be useful if you suspect that the VPM is not functional. It is a simple way to check if the VPM is responding to off-hook indications and to evaluate timing for signaling messages from the interface.
Examples
The following output shows the DSP time stamp and the router time stamp for each event. For SIG_STATUS, the state value shows the state of the ABCD bits in the signaling message. This sample shows a call coming in on an FXO interface.
The router waits for ringing to terminate before accepting the call. State=0x0 indicates ringing; state 0x4 indicates not ringing.
ssm_dsp_message: SEND/RESP_SIG_STATUS: state=0x0 timestamp=58172 systime=40024ssm_dsp_message: SEND/RESP_SIG_STATUS: state=0x4 timestamp=59472 systime=40154ssm_dsp_message: SEND/RESP_SIG_STATUS: state=0x4 timestamp=59589 systime=40166The following output shows the digits collected:
vcsm_dsp_message: MSG_TX_DTMF_DIGIT: digit=4vcsm_dsp_message: MSG_TX_DTMF_DIGIT: digit=1vcsm_dsp_message: MSG_TX_DTMF_DIGIT: digit=0vcsm_dsp_message: MSG_TX_DTMF_DIGIT: digit=0vcsm_dsp_message: MSG_TX_DTMF_DIGIT: digit=0This shows the disconnect indication and the final call statistics reported by the DSP (which are then populated in the call history table):
ssm_dsp_message: SEND/RESP_SIG_STATUS: state=0xC timestamp=21214 systime=42882vcsm_dsp_message: MSG_TX_GET_TX_STAT: num_tx_pkts=1019 num_signaling_pkts=0 num_comfort_noise_pkts=0 transmit_durtation=24150 voice_transmit_duration=20380 fax_transmit_duration=0debug vpm error
To enable digital signal processor (DSP) error tracing in voice port modules (VPMs), use the debug vpm error command in privileged EXEC mode. To disable DSP error tracing, use the no form of this command.
debug vpm error
no debug vpm error
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco 2600, 3600, and MC3810 series devices.
12.1(2)T
This command was integrated into Cisco IOS Release 12.1(2)T.
Usage Guidelines
Execution of no debug all will turn off all port level debugging. You should turn off all debugging and then enter the debug commands you are interested in one by one. This will help avoid confusion about which ports you are actually debugging.
Examples
The following example shows debug vpm error messages for Cisco 2600 or Cisco 3600 series router or a Cisco MC3810 series concentrator:
Router# debug vpm error00:18:37:[1:0.1, FXSLS_NULL, E_DSP_SIG_0100] -> ERROR:INVALID INPUTRouter#The following example turns off debug vpm error debugging messages:
Router# no debug vpm errorRelated Commands
debug vpm all
Enables all VPM debugging.
debug vpm port
Limits the debug vpm error command to a specified port.
show debug
Displays which debug commands are enabled.
debug vpm port
To observe the behavior of the Holst state machine, use the debug vpm port command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpm port [slot-number | subunit-number | port]
no debug vpm port [slot-number | subunit-number | port]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is not supported on Cisco 7200 series routers or on the Cisco MC3810.
Use this command to limit the debug output to a particular port. The debug output can be quite voluminous for a single channel. A 12-port box might create problems. Use this debug command with any or all of the other debug modes.
Execution of no debug vpm all will turn off all port level debugging. We recommend that you turn off all debugging and then enter the debug commands you are interested in one by one. This process helps to avoid confusion about which ports you are actually debugging.
Examples
The following is sample output from the debug vpm port 1/1/0 command during trunk establishment after the no shutdown command has been executed on the voice port:
Router# debug vpm port 1/1/0*Mar 1 03:21:39.799: htsp_process_event: [1/1/0, 0.1 , 2]act_down_inserve*Mar 1 03:21:39.807: htsp_process_event: [1/1/0, 0.0 , 14]act_go_trunkhtsp_trunk_createhtsp_trunk_sig_linkfxols_trunk*Mar 1 03:21:39.807: htsp_process_event: [1/1/0, 1.0 , 1]trunk_offhookfxols_trunk_down*Mar 1 03:21:39.807: dsp_sig_encap_config: [1/1/0] packet_len=28 channel_id=128packet_id=42 transport_protocol=1 playout_delay=100 signaling_mode=0t_ssrc=0 r_ssrc=0 t_vpxcc=0 r_vpxcc=0*Mar 1 03:21:39.811: dsp_set_sig_state: [1/1/0] packet_len=12channel_id=128 packet_id=39 state=0xC timestamp=0x0*Mar 1 03:21:39.811: trunk_offhook: Trunk Retry Timer Enabled*Mar 1 03:22:13.095: htsp_process_event: [1/1/0, 1.1, 39]act_trunk_setuphtsp_setup_ind*Mar 1 03:22:13.095: htsp_process_event: [1/1/0, 1.2 , 8]*Mar 1 03:22:13.099: hdsprm_vtsp_codec_loaded_ok: G726 firmware needs download*Mar 1 03:22:13.103: dsp_download: p=0x60E73844 size=34182 (t=1213310):39 FA 6D*Mar 1 03:22:13.103: htsp_process_event: [1/1/0, 1.2 , 6]act_trunk_proc_connect*Mar 1 03:22:13.191: dsp_receive_packet: MSG_TX_RESTART_INDICATION: code=0 t=1213319*Mar 1 03:22:13.191: dsp_download: p=0x60EA8924 size=6224 (t=1213319): 8 55 AE*Mar 1 03:22:13.207: dsp_receive_packet: MSG_TX_RESTART_INDICATION: code=0 t=1213320*Mar 1 03:22:13.207: htsp_process_event: [1/1/0, 1.3 , 11] trunk_upfxols_trunk_up*Mar 1 03:22:13.207: dsp_set_sig_state: [1/1/0] packet_len=12channel_id=128 packet_id=39 state=0x4 timestamp=0x0*Mar 1 03:22:13.207: dsp_sig_encap_config: [1/1/0] packet_len=28 channel_id=128packet_id=42 transport_protocol=3 playout_delay=100 headerbytes = 0xA0Note in the above display that "transport_protocol = 3" indicates Voice-over-Frame Relay. Also note that the second line of the display indicates that a shutdown/no shutdown command sequence was executed on the voice port.
Related Commands
debug vpm signal
To collect debug information only for signaling events, use the debug vpm signal command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpm signal
no debug vpm signal
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The debug vpm signal command collects debug information only for signaling events. This command can also be useful in resolving problems with signaling to a PBX.
Examples
The following output shows that a ring is detected, and that the router waits for the ringing to stop before accepting the call:
ssm_process_event: [1/0/1, 0.2, 15] fxols_onhook_ringingssm_process_event: [1/0/1, 0.7, 19] fxols_ringing_notssm_process_event: [1/0/1, 0.3, 6]ssm_process_event: [1/0/1, 0.3, 19] fxols_offhook_clearThe following output shows that the call is connected:
ssm_process_event: [1/0/1, 0.3, 4] fxols_offhook_procssm_process_event: [1/0/1, 0.3, 8] fxols_proc_voicessm_process_event: [1/0/1, 0.3, 5] fxols_offhook_connectThe following output confirms a disconnect from the switch and release with higher layer code:
ssm_process_event: [1/0/1, 0.4, 27] fxols_offhook_discssm_process_event: [1/0/1, 0.4, 33] fxols_disc_confirmssm_process_event: [1/0/1, 0.4, 3] fxols_offhook_releasedebug vpm signaling
To see information about the voice port module signaling, use the debug vpm signaling command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpm signaling
no debug vpm signaling
Syntax Description
This command has no arguments or keywords
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
12.0(7)XK
This command was introduced.
12.1(2)T
This command was integrated into Release 12.1(2)T.
Examples
The following is sample output from the debug vpm signaling command:
Router# debug vpm signaling01:52:55: [1:1.1, S_TRUNK_BUSYOUT, E_HTSP_OUT_BUSYOUT]01:52:55: htsp_timer - 0 msec01:52:55: [1:1.1, S_TRUNK_PEND, E_HTSP_EVENT_TIMER]01:52:55: htsp_timer_stop htsp_setup_ind01:52:55: htsp_timer - 2000 msec01:52:55: [1:1.1, S_TRUNK_PROC, E_HTSP_SETUP_ACK]01:52:55: htsp_timer_stop01:52:55: htsp_timer - 20000 msec01:52:55: [1:6.6, S_TRUNK_PROC, E_HTSP_SETUP_ACK]01:52:55: htsp_timer_stop01:52:55: htsp_timer - 20000 msec01:52:55: [1:1.1, S_TRUNK_PROC, E_HTSP_VOICE_CUT_THROUGH]01:52:55: %HTSP-5-UPDOWN: Trunk port(channel) [1:1.1] is updebug vpm spi
To trace how the voice port module security parameter index (SPI) interfaces with the call control application programming interface (API), use the debug vpm spi command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpm spi
no debug vpm spi
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The debug vpm spi command traces how the voice port module SPI interfaces with the call control API. This debug command displays information about how each network indication and application request is handled.
This debug level shows the internal workings of the voice telephony call state machine.
Examples
The following output shows that the call is accepted and presented to a higher layer code:
dsp_set_sig_state: [1/0/1] packet_len=14 channel_id=129 packet_id=39 state=0xC timestamp=0x0vcsm_process_event: [1/0/1, 0.5, 1] act_up_setup_indThe following output shows that the higher layer code accepts the call, requests addressing information, and starts DTMF and dial-pulse collection. It also shows that the digit timer is started.
vcsm_process_event: [1/0/1, 0.6, 11] act_setup_ind_ackdsp_voice_mode: [1/0/1] packet_len=22 channel_id=1 packet_id=73 coding_type=1 voice_field_size=160 VAD_flag=0 echo_length=128 comfort_noise=1 fax_detect=1dsp_dtmf_mode: [1/0/1] packet_len=12 channel_id=1 packet_id=65 dtmf_or_mf=0dsp_CP_tone_on: [1/0/1] packet_len=32 channel_id=1 packet_id=72 tone_id=3 n_freq=2 freq_of_first=350 freq_of_second=440 amp_of_first=4000 amp_of_second=4000 direction=1 on_time_first=65535 off_time_first=0 on_time_second=65535 off_time_second=0dsp_digit_collect_on: [1/0/1] packet_len=22 channel_id=129 packet_id=35 min_inter_delay=550 max_inter_delay=3200 mim_make_time=18 max_make_time=75 min_brake_time=18 max_brake_time=75vcsm_timer: 46653The following output shows the collection of digits one by one until the higher level code indicates it has enough. The input timer is restarted with each digit and the device waits in idle mode for connection to proceed.
vcsm_process_event: [1/0/1, 0.7, 25] act_dcollect_digitdsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71vcsm_timer: 47055vcsm_process_event: [1/0/1, 0.7, 25] act_dcollect_digitdsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71vcsm_timer: 47079vcsm_process_event: [1/0/1, 0.7, 25] act_dcollect_digitdsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71vcsm_timer: 47173vcsm_process_event: [1/0/1, 0.7, 25] act_dcollect_digitdsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71vcsm_timer: 47197vcsm_process_event: [1/0/1, 0.7, 25] act_dcollect_digitdsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71vcsm_timer: 47217vcsm_process_event: [1/0/1, 0.7, 13] act_dcollect_procdsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71dsp_digit_collect_off: [1/0/1] packet_len=10 channel_id=129 packet_id=36dsp_idle_mode: [1/0/1] packet_len=10 channel_id=1 packet_id=68The following output shows that the network voice path cuts through:
vcsm_process_event: [1/0/1, 0.8, 15] act_bridgevcsm_process_event: [1/0/1, 0.8, 20] act_caps_indvcsm_process_event: [1/0/1, 0.8, 21] act_caps_ackdsp_voice_mode: [1/0/1] packet_len=22 channel_id=1 packet_id=73 coding_type=6 voice_field_size=20 VAD_flag=1 echo_length=128 comfort_noise=1 fax_detect=1The following output shows that the called-party end of the connection is connected:
vcsm_process_event: [1/0/1, 0.8, 8] act_connectThe following output shows the voice quality statistics collected periodically:
vcsm_process_event: [1/0/1, 0.13, 17]dsp_get_rx_stats: [1/0/1] packet_len=12 channel_id=1 packet_id=87 reset_flag=0vcsm_process_event: [1/0/1, 0.13, 28]vcsm_process_event: [1/0/1, 0.13, 29]vcsm_process_event: [1/0/1, 0.13, 32]vcsm_process_event: [1/0/1, 0.13, 17]dsp_get_rx_stats: [1/0/1] packet_len=12 channel_id=1 packet_id=87 reset_flag=0vcsm_process_event: [1/0/1, 0.13, 28]vcsm_process_event: [1/0/1, 0.13, 29]vcsm_process_event: [1/0/1, 0.13, 32]vcsm_process_event: [1/0/1, 0.13, 17]dsp_get_rx_stats: [1/0/1] packet_len=12 channel_id=1 packet_id=87 reset_flag=0vcsm_process_event: [1/0/1, 0.13, 28]vcsm_process_event: [1/0/1, 0.13, 29]vcsm_process_event: [1/0/1, 0.13, 32]The following output shows that the disconnection indication is passed to higher-level code. The call connection is torn down, and final call statistics are collected:
vcsm_process_event: [1/0/1, 0.13, 4] act_generate_discvcsm_process_event: [1/0/1, 0.13, 16] act_bdropdsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71vcsm_process_event: [1/0/1, 0.13, 18] act_disconnectdsp_get_levels: [1/0/1] packet_len=10 channel_id=1 packet_id=89vcsm_timer: 48762vcsm_process_event: [1/0/1, 0.15, 34] act_get_levelsdsp_get_tx_stats: [1/0/1] packet_len=12 channel_id=1 packet_id=86 reset_flag=1vcsm_process_event: [1/0/1, 0.15, 31] act_stats_completedsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71dsp_digit_collect_off: [1/0/1] packet_len=10 channel_id=129 packet_id=36dsp_idle_mode: [1/0/1] packet_len=10 channel_id=1 packet_id=68vcsm_timer: 48762dsp_set_sig_state: [1/0/1] packet_len=14 channel_id=129 packet_id=39 state=0x4 timestamp=0x0vcsm_process_event: [1/0/1, 0.16, 5] act_wrelease_releasedsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71dsp_idle_mode: [1/0/1] packet_len=10 channel_id=1 packet_id=68dsp_get_rx_stats: [1/0/1] packet_len=12 channel_id=1 packet_id=87 reset_flag=1debug vpm trunk_sc
To enable the display of trunk conditioning supervisory component trace information, use the debug vpm trunk_sc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpm trunk_sc
no debug vpm trunk_sc
Syntax Description
This command has no arguments or keywords.
Defaults
Trunk conditioning supervisory component trace information is not displayed.
Command Modes
Privileged EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco 2600, Cisco 3600, and Cisco MC3810 series devices.
12.1(2)T
This command was integrated into Cisco IOS Release 12.1(2)T.
Usage Guidelines
Use the debug vpm port command with the slot-number/subunit-number/port argument to limit the debug vpm trunk_sc debug output to a particular port. If you do not use the debug vpm port command, the debug vpm trunk_sc displays output for all ports.
Execution of the no debug all command will turn off all port level debugging. It is usually a good idea to turn off all debugging and then enter the debug commands you are interested in one by one. This process helps avoid confusion about which ports you are actually debugging.
Examples
The following example shows debug vpm trunk_sc messages for port 1/0/0 on a Cisco 2600 or Cisco 3600 series router:
Router# debug vpm trunk_scRouter# debug vpm port 1/0/0The following example shows debug vpm trunk_sc messages for port 1/1 on a Cisco MC3810 device:
Router# debug vpm trunk_scRouter# debug vpm port 1/1The following example turns off debug vpm trunk_sc debugging messages:
Router# no debug vpm trunk_scRelated Commands
debug vpm all
Enables all VPM debugging
debug vpm port
Limits the debug vpm trunk_sc command to a specified port.
show debug
Displays which debug commands are enabled.
debug vpm voaal2 all
To display type 1 (voice) and type 3 (control) ATM Adaptation Layer type 2 (AAL2) packets sent to and received from the domain-specific part (DSP), use the debug vpm voaal2 all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpm voaal2 all {all_dsp | from_dsp | to_dsp}
no debug vpm voaal2 all
Syntax Description
all_dsp
Displays messages to and from the DSP.
from_dsp
Displays messages from the DSP.
to_dsp
Displays messages to the DSP.
Defaults
Debugging for display of AAL2 packets is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Do not enter this debug command on a system carrying live traffic. Continuous display of AAL2 type 1 (voice) packets results in high CPU utilization and loss of console access to the system. Calls will be dropped and trunks may go down. For AAL2 debugging, use the debug vpm voaal2 type3 debug command and identify a specific type 3 (control) packet type.
Examples
The following is sample output from the debug vpm voaal2 all command, where the example selection is to display channel-associated switching (CAS) packets sent to and from the DSP:
Router# debug vpm voaal2 all all_dsp*Jan 9 20:10:36.965:TYPE 3, len = 8, cid = 34, uui = 24 :TO_DSP*Jan 9 20:10:36.965:CASredundancy = 3, timestamp = 10270, signal = 0- 22 13 12 E8 1E 0 E 15 -*Jan 9 20:10:41.617:TYPE 3, len = 8, cid = 34, uui = 24 :FROM_DSP*Jan 9 20:10:41.617:CASredundancy = 3, timestamp = 980, signal = 0- 22 13 12 C3 D4 0 F 87 -*Jan 9 20:10:41.965:TYPE 3, len = 8, cid = 34, uui = 24 :TO_DSP*Jan 9 20:10:41.965:CASredundancy = 3, timestamp = 10270, signal = 0- 22 13 12 E8 1E 0 E 15 -*Jan 9 20:10:46.621:TYPE 3, len = 8, cid = 34, uui = 24 :FROM_DSP*Jan 9 20:10:46.621:CASredundancy = 3, timestamp = 980, signal = 0- 22 13 12 C3 D4 0 F 87 -....*Jan 9 20:10:57.101:TYPE 1, len = 43, cid = 34, uui = 8- 22 9D 1 CC FCC73E 22 23 FE DF F8 DE 1C FF E5 12 22 43 EC 2E 9E CC DE A7 EF 14 E3 F1 2C2DBC 1B FC FE D7 E1 1F 2F ED 11 FC 1F -*Jan 9 20:10:57.105:TYPE 3, len = 9, cid = 34, uui = 24 :FROM_DSP*Jan 9 20:10:57.105:DIALED DIGITSredundancy = 0,timestamp = 940, digitcode = 1- 22 17 3 3 AC 1 1 8 E5 -*Jan 9 20:10:57.113:TYPE 1, len = 43, cid = 34, uui = 10- 22 9D 4B 3F1F11 FC CD CC BE B7 E2 F3 32 2E 1F F9 DA CC BF 12 F1 37 31 11 2C FE 9D DAD2E1 C7 4A 34 3F FA 21 AD CC 1F EE 16 E1 -*Jan 9 20:10:57.113:TYPE 3, len = 9, cid = 34, uui = 24 :FROM_DSP*Jan 9 20:10:57.113:DIALED DIGITSredundancy = 1,timestamp = 940, digitcode = 1- 22 17 3 43 AC 1 1 B 12 -*Jan 9 20:10:57.121:TYPE 1, len = 43, cid = 34, uui = 12- 22 9D 95 F11EE1 DF 1E 21 31 21 1D D9 EB BB DF 22 17 13 12 1F 58 FF ED ED E1 4D B7 3E3F21 F3 8E FD EF DF F4 12 E4 32 FE B4 D8 -Related Commands
debug vpm voaal2 type1
To display type 1 (voice) ATM Adaptation Layer type 2 (AAL2) packets sent to and received from the domain-specific part (DSP), use the debug vpm voaal2 type1 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpm voaal2 type1 {all_dsp | from_dsp | to_dsp}
no debug vpm voaal2 type1
Syntax Description
all_dsp
Displays messages to and from the DSP.
from_dsp
Displays messages from the DSP.
to_dsp
Displays messages to the DSP.
Defaults
Debugging for display of AAL2 packets is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Do not enter this debug command on a system carrying live traffic. Continuous display of AAL2 type 1 (voice) packets results in high CPU utilization and loss of console access to the system. Calls will be dropped and trunks may go down. For AAL2 debugging, use the debug vpm voaal2 type 3 command and identify a specific type 3 (control) packet type.
Examples
The following is sample output from the debug vpm voaal2 type1 command:
Note
The display of voice packets on a live system will continue indefinitely. The debugging output cannot be interrupted, because console access will be lost.
Router# debug vpm voaal2 type1 all_dspTYPE 1, len = 43, cid = 17, uui = 15- 11 9D E6 1B 52 9D 95 9B DB 1D 141C 5F 9C 95 9C EA 1C 15 1B 74 9C 94 9D 6B 1C 14 1D E4 9B 94 9D 5B 1B 141D D7 9B 94 9D 50 1B 14 -TYPE 1, len = 43, cid = 22, uui = 15- 16 9D ED 1D 14 1B 53 9D 94 9C DB1D 14 1C 5F 9C 95 9C EB 1C 14 1C 78 9D 94 9D 6F 1C 14 1E E4 9B 94 9D 5B1B 14 1D D7 9B 94 9E 52 -TYPE 1, len = 43, cid = 12, uui = 14- C 9D D1 29 AB 96 96 A9 2B 16 16 2AAA 96 96 AB 2A 16 17 2B A9 96 97 AC 28 16 17 2C A8 96 97 AD 27 15 17 2EA7 97 97 AE 26 16 17 -TYPE 1, len = 43, cid = 34, uui = 14- 22 9D DF D7 31 20 19 15 14 15 191E 2C 60 AF 9F 99 96 94 95 99 9F AD EC 2F 1F 1A 15 14 15 19 1F 2E ED AD9F 99 96 93 95 99 9F AF -TYPE 1, len = 43, cid = 12, uui = 15- C 9D F4 2F A5 96 97 AF 25 15 18 31A4 95 98 B3 23 15 18 33 A3 95 98 B5 22 15 18 37 A2 95 98 B7 21 15 18 39A0 95 99 BB 21 14 19 -TYPE 1, len = 43, cid = 34, uui = 15- 22 9D FA 5D 2D 1E 19 15 14 15 1A21 31 D9 AC 9E 98 95 94 95 9A A4 B3 52 2B 1D 18 14 14 16 1B 22 36 CA AA9D 98 94 94 96 9B A4 B6 -Related Commands
debug vpm voaal2 type3
To display type 3 (control) ATM Adaptation Layer type 2 (AAL2) packets sent to and received from the domain-specific part (DSP), use the debug vpm voaal2 type3 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpm voaal2 type3 {alarms | alltype3 | cas | dialed | faxrelay | state}{all_dsp | from_dsp | to_dsp}
no debug vpm voaal2 type3
Syntax Description
Defaults
Debugging for display of AAL2 packets is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This is the preferred debug command for displaying specific types of control packets. It is usually preferable to specify a particular type of control packet rather than use the alltype3 to avoid excessive output display and CPU utilization.
Examples
The following is sample output from the debug vpm voaal2 type3 command, where the example selection is to display messages to and from the DSP:
Router# debug vpm voaal2 type3 all_dsp00:43:02:TYPE 3, len = 8, cid = 58, uui = 24 :TO_DSP00:43:02:CASredundancy = 3, timestamp = 10484, signal = 0- 3A 13 18 E8 F4 0 C DA -00:43:02:TYPE 3, len = 8, cid = 93, uui = 24 :FROM_DSP00:43:02:CASredundancy = 3, timestamp = 6528, signal = 0- 5D 13 1E D9 80 0 F 33 -00:43:02:TYPE 3, len = 8, cid = 102, uui = 24 :FROM_DSP00:43:02:CASredundancy = 3, timestamp = 5988, signal = 0- 66 13 4 D7 64 0 F DF -00:43:02:TYPE 3, len = 8, cid = 194, uui = 24 :FROM_DSP00:43:02:CASredundancy = 3, timestamp = 6212, signal = 0- C2 13 10 D8 44 0 F AC -00:43:02:TYPE 3, len = 8, cid = 92, uui = 24 :FROM_DSPTYPE 3, len = 8, cid = 66, uui = 24 :TO_DSP:43:00:CASredundancy = 3, times signal = 0- 5C 13 5 D9 E4 0 C 1F -00:43:02:TYPE 3, len = 8, cid = 40, uui = 24 :TO_DSP00:43:02:CASredundancy = 3, timestamp = 8658, signal = 0- 28 13 7 E1 D2 0 E 79 -00:43:02:TYPE 3, len = 8, cid = 137, uui = 24 :FROM_DSP00:43:02:CASredundancy = 3, timestamp = 6836, signal = 0- 89 13 B DA B4 0 E 78 -Related Commands
debug vrrp all
To display debugging messages for Virtual Router Redundancy Protocol (VRRP) errors, events, and state transitions, use the debug vrrp all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vrrp all
no debug vrrp all
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output for the debug vrrp all command:
Router# debug vrrp all00:15:30: %IP-4-DUPADDR: Duplicate address 10.18.0.2 on Ethernet1/0, sourced by 0000.5e00.0101May 22 18:41:54.447: VRRP: Grp 1 Advertisement Primary address 10.18.0.2different from ours 10.18.0.1May 22 18:41:57.443: VRRP: Grp 1 Advertisement Primary address 10.18.0.2different from ours 10.18.0.1May 22 18:42:00.443: VRRP: Grp 1 Advertisement Primary address 10.18.0.2different from ours 10.18.0.1May 22 18:48:41.521: VRRP: Grp 1 Event - Advert higher or equal priorityMay 22 18:48:44.521: VRRP: Grp 1 Event - Advert higher or equal priorityMay 22 18:48:47.521: VRRP: Grp 1 Event - Advert higher or equal priorityMay 22 18:53:23.390: VRRP: Grp 1 changing to V_STATE_INITMay 22 18:54:26.143: VRRP: Grp 1 changing to V_STATE_BACKUPMay 22 18:54:35.755: VRRP: Grp 1 changing to V_STATE_MASTERMay 22 18:53:23.390: VRRP: Grp 1 changing to V_STATE_INITMay 22 18:54:26.143: VRRP: Grp 1 changing to V_STATE_BACKUPMay 22 18:54:35.755: VRRP: Grp 1 changing to V_STATE_MASTERRelated Commands
debug vrrp authentication
To display debugging messages for Virtual Router Redundancy Protocol (VRRP) Message Digest 5 (MD5) authentication, use the debug vrrp authentication command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vrrp authentication
no debug vrrp authentication
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following sample output shows that MD5 authentication is enabled on one router but not the other:
Router# debug vrrp authenticationVRRP: Grp 1 Advertisement from 172.24.1.1 has incorrect authentication type 0 expected 254The following sample output shows that the MD5 key IDs and key strings differ on each router:
Router# debug vrrp authenticationVRRP: Grp 1 recalculate MD5 digest: "3n};oHp87ЇC"VRRP: Grp 1 received MD5 digest: "_M_^uMiWo^|t?t2m"VRRP: Grp 1 Advertisement from 172.24.1.1 has FAILED MD5 authenticationThe following sample output shows that the text authentication strings differ on each router:
Router# debug vrrp authenticationVRRP: Grp 1 Advertisement from 172.24.1.1 has FAILED TEXT authenticationRelated Commands
debug vrrp error
To display debugging messages about Virtual Router Redundancy Protocol (VRRP) error conditions, use the debug vrrp error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vrrp error
no debug vrrp error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug vrrp error command:
Router# debug vrrp errorRouter#00:15:30: %IP-4-DUPADDR: Duplicate address 10.18.0.2 on Ethernet1/0, sourced by 0000.5e00.0101May 22 18:41:54.447: VRRP: Grp 1 Advertisement Primary address 10.18.0.2different from ours 10.18.0.1May 22 18:41:57.443: VRRP: Grp 1 Advertisement Primary address 10.18.0.2different from ours 10.18.0.1May 22 18:42:00.443: VRRP: Grp 1 Advertisement Primary address 10.18.0.2different from ours 10.18.0.1In the example, the error being observed is that the router has a virtual address of 10.18.0.1 for group 1, but it received a virtual address of 10.18.0.2 for group 1 from another router on the same LAN.
Related Commands
debug vrrp all
Displays debugging messages for VRRP errors, events, and state transitions.
debug vrrp events
To display debugging messages about Virtual Router Redundancy Protocol (VRRP) events that are occurring, use the debug vrrp events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vrrp events
no debug vrrp 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 vrrp events command:
Router# debug vrrp eventsMay 22 18:48:41.521: VRRP: Grp 1 Event - Advert higher or equal priorityMay 22 18:48:44.521: VRRP: Grp 1 Event - Advert higher or equal priorityMay 22 18:48:47.521: VRRP: Grp 1 Event - Advert higher or equal priorityIn the example, the event being observed is that the router received an advertisement from another router for group 1 that has a higher or equal priority to itself.
Related Commands
debug vrrp all
Displays debugging messages for VRRP errors, events, and state transitions.
debug vrrp packets
To display summary information about Virtual Router Redundancy Protocol (VRRP) packets being sent or received, use the debug vrrp packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vrrp packets
no debug vrrp packets
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug vrrp packets command. The output is on the master virtual router; the router for group 1 is sending an advertisement with a checksum of 6BE7.
Router# debug vrrp packetsVRRP Packets debugging is onMay 22 18:51:03.220: VRRP: Grp 1 sending Advertisement checksum 6BE7May 22 18:51:06.220: VRRP: Grp 1 sending Advertisement checksum 6BE7In the following example, the router with physical address 10.18.0.3 is advertising a priority of 105 for VRRP group 1:
Router# debug vrrp packetsVRRP Packets debugging is onMay 22 18:51:09.222: VRRP: Grp 1 Advertisement priority 105, ipaddr 10.18.0.3May 22 18:51:12.222: VRRP: Grp 1 Advertisement priority 105, ipaddr 10.18.0.3debug vrrp state
To display debugging messages about the state transitions occurring for Virtual Router Redundancy Protocol (VRRP) groups, use the debug vrrp state command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vrrp state
no debug vrrp state
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug vrrp state command:
Router# debug vrrp stateMay 22 18:53:23.390: VRRP: Grp 1 changing to V_STATE_INITMay 22 18:54:26.143: VRRP: Grp 1 changing to V_STATE_BACKUPMay 22 18:54:35.755: VRRP: Grp 1 changing to V_STATE_MASTERRelated Commands
debug vrrp all
Displays debugging messages for VRRP errors, events, and state transitions.
debug vsi api
To display information on events associated with the external ATM application programming interface (API) interface to the Virtual Switch Interface (VSI) master, use the debug vsi api command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vsi api
no debug vsi 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 vsi api command to monitor the communication between the VSI master and the XmplsATM component regarding interface changes and cross-connect requests.
Examples
The following is sample output from the debug vsi api command:
Router# debug vsi apiVSI_M: vsi_exatm_conn_req: 0x000C0200/1/35 -> 0x000C0100/1/50desired state up, status OKVSI_M: vsi_exatm_conn_resp: 0x000C0200/1/33 -> 0x000C0100/1/49curr state up, status OKTable 355 describes the significant fields shown in the display.
debug vsi errors
To display information about errors encountered by the Virtual Switch Interface (VSI) master, use the debug vsi errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vsi errors [interface interface [slave number]]
no debug vsi errors [interface interface [slave number]]
Syntax Description
interface interface
(Optional) Specifies the interface number.
slave number
(Optional) Specifies the slave number (beginning with 0).
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug vsi errors command to display information about errors encountered by the VSI master when parsing received messages, as well as information about unexpected conditions encountered by the VSI master.
If the interface parameter is specified, output is restricted to errors associated with the indicated VSI control interface. If the slave number is specified, output is further restricted to errors associated with the session with the indicated slave.
Note
Multiple commands that specify slave numbers allow multiple slaves to be debugged immediately. For example, the following commands display errors associated with sessions 0 and 1 on control interface atm2/0, but for no other sessions.
Router#debug vsi errors interface atm2/0 slave 0Router#debug vsi errors interface atm2/0 slave 1Some errors are not associated with any particular control interface or session. Messages associated with these errors are printed, regardless of the interface or slave options currently in effect.
Examples
The following is sample output from the debug vsi errors command:
Router# debug vsi errorsVSI Master: parse error (unexpected param-group contents) in GEN ERROR RSP rcvd on ATM2/0:0/51 (slave 0)errored section is at offset 16, for 2 bytes:01.01.00.a0 00.00.00.00 00.12.00.38 00.10.00.34*00.01*00.69 00.2c.00.00 01.01.00.80 00.00.00.0800.00.00.00 00.00.00.00 00.00.00.00 0f.a2.00.0a00.01.00.00 00.00.00.00 00.00.00.00 00.00.00.0000.00.00.00Table 356 describes the significant fields shown in the display.
debug vsi events
To display information about events that affect entire sessions, as well as events that affect only individual connections, use the debug vsi events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vsi events [interface interface [slave number]]
no debug vsi events [interface interface [slave number]]
Syntax Description
interface interface
(Optional) The interface number.
slave number
(Optional) The slave number (beginning with zero).
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug vsi events command to display information about events associated with the per-session state machines of the Virtual Switch Interface (VSI) master, as well as the per-connection state machines. If you specify an interface, the output is restricted to events associated with the indicated VSI control interface. If you specify the slave number, output is further restricted to events associated with the session with the indicated slave.
Note
Multiple commands that specify slave numbers allow multiple slaves to be debugged at once. For example, the following commands restrict output to events associated with sessions 0 and 1 on control interface atm2/0, but for no other sessions. Output associated with all per-connection events are displayed, regardless of the interface or slave options currently in effect.
Router#debug vsi events interface atm2/0 slave 0Router#debug vsi events interface atm2/0 slave 1Examples
The following is sample output from the debug vsi events command:
Router# debug vsi eventsVSI Master: conn 0xC0200/1/37->0xC0100/1/51:CONNECTING -> UPVSI Master(session 0 on ATM2/0):event CONN_CMT_RSP, state ESTABLISHED -> ESTABLISHEDVSI Master(session 0 on ATM2/0):event KEEPALIVE_TIMEOUT, state ESTABLISHED -> ESTABLISHEDVSI Master(session 0 on ATM2/0):event SW_GET_CNFG_RSP, state ESTABLISHED -> ESTABLISHEDdebug vsi packetsTable 357 describes the significant fields shown in the display.
debug vsi packets
To display a one-line summary of each Virtual Switch Interface (VSI) message sent and received by the label switch controller (LSC), use the debug vsi packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vsi packets [interface interface [slave number]]
no debug vsi packets [interface interface [slave number]]
Syntax Description
interface interface
(Optional) The interface number.
slave number
(Optional) The slave number (beginning with zero).
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you specify an interface, output is restricted to messages sent and received on the indicated VSI control interface. If you specify a slave number, output is further restricted to messages sent and received on the session with the indicated slave.
Note
Multiple commands that specify slave numbers allow multiple slaves to be debugged at once. For example, the following commands restrict output to messages received on atm2/0 for sessions 0 and 1, but for no other sessions.
Router# debug vsi packets interface atm2/0 slave 0Router# debug vsi packets interface atm2/0 slave 1Examples
The following is sample output from the debug vsi packets command:
Router# debug vsi packetsVSI master(session 0 on ATM2/0): sent msg SW GET CNFG CMD on 0/51VSI master(session 0 on ATM2/0): rcvd msg SW GET CNFG RSP on 0/51VSI master(session 0 on ATM2/0): sent msg SW GET CNFG CMD on 0/51VSI master(session 0 on ATM2/0): rcvd msg SW GET CNFG RSP on 0/51Table 358 describes the significant fields shown in the display.
debug vsi param-groups
To display the first 128 bytes of each Virtual Switch Interface (VSI) message sent and received by the Multiprotocol Label Switching (MPLS) label switch controller (LSC) (in hexadecimal form), use the debug vsi param-groups command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vsi param-groups [interface interface [slave number]]
no debug vsi param-groups [interface interface [slave number]]
Note
Syntax Description
interface interface
(Optional) The interface number.
slave number
(Optional) The slave number (beginning with zero).
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is most commonly used with the debug vsi packets command to monitor incoming and outgoing VSI messages.
If you specify an interface, output is restricted to messages sent and received on the indicated VSI control interface.
If you specify a slave, output is further restricted to messages sent and received on the session with the indicated slave.
Note
Multiple commands that specify slave numbers allow multiple slaves to be debugged at once. For example, the following commands restrict output for messages received on atm2/0 for sessions 0 and 1, but for no other sessions:
Router# debug vsi param-groups interface atm2/0 slave 0 Router# debug vsi param-groups interface atm2/0 slave 1Examples
The following is sample output from the debug vsi param-groups command:
Router# debug vsi param-groupsOutgoing VSI msg of 12 bytes (not including encap):01.02.00.80 00.00.95.c2 00.00.00.00Incoming VSI msg of 72 bytes (not including encap):01.02.00.81 00.00.95.c2 00.0f.00.3c 00.10.00.0800.01.00.00 00.00.00.00 01.00.00.08 00.00.00.0900.00.00.09 01.10.00.20 01.01.01.00 0c.08.80.0000.01.0f.a0 00.13.00.15 00.0c.01.00 00.00.00.0042.50.58.2d 56.53.49.31Outgoing VSI msg of 12 bytes (not including encap):01.02.00.80 00.00.95.c3 00.00.00.00Incoming VSI msg of 72 bytes (not including encap):01.02.00.81 00.00.95.c3 00.0f.00.3c 00.10.00.0800.01.00.00 00.00.00.00 01.00.00.08 00.00.00.0900.00.00.09 01.10.00.20 01.01.01.00 0c.08.80.0000.01.0f.a0 00.13.00.15 00.0c.01.00 00.00.00.0042.50.58.2d 56.53.49.31Table 359 describes the significant fields shown in the display.
debug vtemplate
To display cloning information for a virtual access interface from the time it is cloned from a virtual template to the time the virtual access interface comes down when the call ends, use the debug vtemplate command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vtemplate
no debug vtemplate
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug vtemplate command when a virtual access interface comes up. The virtual access interface is cloned from virtual template 1.
Router# debug vtemplateVTEMPLATE Reuse vaccess8, New Recycle queue size:50VTEMPLATE set default vaccess8 with no ip addressVirtual-Access8 VTEMPLATE hardware address 0000.0c09.ddfdVTEMPLATE vaccess8 has a new cloneblk vtemplate, now it has vtemplateVTEMPLATE undo default settings vaccess8VTEMPLATE ************* CLONE VACCESS8 *****************VTEMPLATE Clone from vtemplate1 to vaccess8interface Virtual-Access8no ip addressencap pppip unnumbered Ethernet0no ip mroute-cachefair-queue 64 256 0no cdp enableppp authentication chapend%LINK-3-UPDOWN: Interface Virtual-Access8, changed state to up%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access8, changed state to upThe following is sample output from the debug vtemplate command when a virtual access interface goes down. The virtual interface is uncloned and returns to the recycle queue.
Router# debug vtemplate%LINK-3-UPDOWN: Interface Virtual-Access8, changed state to downVTEMPLATE Free vaccess8%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access8, changed state to downVTEMPLATE clean up dirty vaccess queue, size:1VTEMPLATE Found a dirty vaccess8 clone with vtemplateVTEMPLATE ************ UNCLONE VACCESS8 **************VTEMPLATE Unclone to-be-freed vaccess8 command#7interface Virtual-Access8default ppp authentication chapdefault cdp enabledefault fair-queue 64 256 0default ip mroute-cachedefault ip unnumbered Ethernet0default encap pppdefault ip addressendVTEMPLATE set default vaccess8 with no ip addressVTEMPLATE remove cloneblk vtemplate from vaccess8 with vtemplateVTEMPLATE Add vaccess8 to recycle queue, size=51Table 360 describes the significant fields shown in the display.
debug vtemplate subinterface
To display debugging messages relating to virtual access subinterfaces, use the debug vtemplate subinterface command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vtemplate subinterface
no debug vtemplate subinterface
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.2(8)B
This command was introduced.
12.2(13)T
The command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
These debugging messages are displayed if the user configures virtual templates with commands that are incompatible with virtual access subinterfaces.
Examples
The following example displays virtual access subinterface debugging messages:
Router# debug vtemplate subinterfaceVirtual Template subinterface debugging is onRouter#Router#Sep 19 15:09:41.989:VT[Vt11]:Config prevents subinterface creationcarrier-delay 45ip rtp priority 2000 2010 500Table 361 describes the significant fields shown in the display.
Related Commands
debug vtsp
Note
To display the state of the gateway and the call events, use the debug vtsp command in privileged EXEC mode. To display the machine state during voice telephony service provider (VTSP) event processing, use the no form of the command.
debug vtsp {all | dsp | error | event | session | stats | tone | rtp}
no debug vtsp {all | dsp | error | event | session | stats | tone | rtp}
Note
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output for a Cisco AS5300 and Cisco 3640 when the debug vtsp all command is entered:
Cisco AS5300 Access Server
Router# debug vtsp all!Voice telephony call control all debugging is on!00:10:53: %SYS-5-CONFIG_I: Configured from console by console00:10:54: %SYS-5-CONFIG_I: Configured from console by console!00:11:09: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate:00:11:09: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate:00:11:09: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_call_setup_ind:00:11:09: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_fill_setup_ind:Cisco 3640 Router
3640-orig# debug vtsp all!Voice telephony call control all debugging is on!3640-orig# show debugVoice Telephony session debugging is onVoice Telephony dsp debugging is onVoice Telephony error debugging is on!20:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_apply_voiceport_xrule:20:58:16: vtsp_tsp_apply_voiceport_xrule: vtsp_sdb 0x63797720; called_number 0x6294E0F0 called_oct3 12820:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_apply_voiceport_xrule:20:58:16: vtsp_tsp_apply_voiceport_xrule: No called number translation rule configured20:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: .20:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: calling_number(original)=calling_number(xlated)=8880000 called_number(original)= called_number(xlated)=8881111 redirectNumber(original)= redirectNumber(xlated)=20:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_call_setup_ind: (sdb=0x63797720, tdm_info=0x0,tsp_info=0x63825254, calling_number=8880000 calling_oct3 = 0x0, called_number=8881111 called_oct3 = 0x80, oct3a=03640-orig#x80): peer_tag=7020:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_fill_setup_ind: ev.clg.clir is 0ev.clg.clid_transparent is 0ev.clg.null_orig_clg is 0ev.clg.calling_translated is false//-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:(3/0:23):-1:0:0/vtsp_do_call_setup_ind: Call ID=101123, guid=63EB9AC8Table 362 describes the significant fields shown in the display.
Related Commands
debug voip ccapi
Debugs the call control API.
voice call debug
Debugs a voice call by displaying a full GUID or header.
debug vtsp all
To show debugging information for all debug vtsp commands, use the debug vtsp all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vtsp all
no debug vtsp all
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug vtsp all command enables the following debug vtsp commands: debug vtsp session, debug vtsp error, and debug vtsp dsp. For more information or sample output, see the individual commands.
Execution of the no debug vtsp all command will turn off all VTSP-level debugging. You should turn off all debugging and then enter the debug commands you are interested in one by one. This process helps avoid confusion about which ports you are actually debugging.
Caution
Examples
The following example shows the debug vtsp all command on a Cisco 3640 modular access router:
Router# debug vtsp allVoice telephony call control all debugging is onAt this point, the VTSP is not aware of anything. The format of this message is
//callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number:•
•
•
•
•
•
*Mar 1 08:23:10.869: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate:The original and the translated calling number are the same (55555) and the original and the translated called number are the same (888545). These numbers are often the same because if a translation rule is applied, it will be on the dial peers or the ports, both of which comes later than these VTSP messages in the Cisco IOS code execution.
*Mar 1 08:23:10.869: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: calling_number(original)= calling_number(xlated)=55555 called_number(original)= called_number(xlated)=888545 redirectNumber(original)= redirectNumber(xlated)=The VTSP got a call setup indicator from the TSP layer with called number 888545 and calling number 55555. There is no awareness of the CallEntry ID (-1) or the GUID (xxxxxxxxxxxx).
*Mar 1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_call_setup_ind: (sdb=0x634C90EC, tdm_info=0x0, tsp_info=0x63083950, calling_number=55555 calling_oct3 = 0x80, called_number=888545 called_oct3 = 0x80, oct3a=0x0): peer_tag=10002*Mar 1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_fill_setup_ind: ev.clg.clir is 0ev.clg.clid_transparent is 0ev.clg.null_orig_clg is 0ev.clg.calling_translated is false*Mar 1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_call_setup_ind: .*Mar 1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_allocate_cdb: ,cdb 0x635FC480*Mar 1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_call_setup_ind:*Mar 1 08:23:10.873: source route labelAt this point, the VTSP is not aware of anything. The format of this message is
//callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number:•
•
•
•
•
•
*Mar 1 08:23:10.873: //-1/D2F6429A8A8A/VTSP:(1/0:23):-1:0:4/vtsp_do_call_setup_ind: Call ID=101002, guid=635FCB08The VTSP learns about the B channel (changed from -1 to 22), and the CallEntry ID is still unknown (-1).
*Mar 1 08:23:10.873: //-1/D2F6429A8A8A/VTSP:(1/0:23):22:0:4/vtsp_do_call_setup_ind: type=0, under_spec=1615186336, name=, id0=23, id1=0, id2=0, calling=55555,called=888545 subscriber=RegularLinevtsp_do_call_setup_ind: redirect DN = reason = -1*Mar 1 08:23:10.877: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_normal_call_setup_ind: .The VTSP learns the CallEntry ID. The format of this message is
//callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number:•
•
•
•
•
•
*Mar 1 08:23:10.877: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_insert_cdb:,cdb 0x635FC480, CallID=899*Mar 1 08:23:10.877: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_open_voice_and_set_params: .In the following outputs, VTSP sets some of the voice parameters for this call:
•
•
•
•
*Mar 1 08:23:10.877: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_proto_from_cdb: cap_modem_proto 0*Mar 1 08:23:10.881: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_playout_cdb:playout default*Mar 1 08:23:10.881: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_dsp_echo_canceller_control: echo_cancel: 1*Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_save_dialpeer_tag: tag = 10003*Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_report_digit_control: vtsp_report_digit_control: enable=0:*Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_report_digit_control: digit reporting disabled*Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_digit_timeouts: : vtsp_get_digit_timeoutsVTSP sends out a call-proceeding message to the POTS leg.
*Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event:vtsp:[1/0:23:899, S_SETUP_INDICATED, E_CC_PROCEEDING]*Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_proceeding: .*Mar 1 08:23:10.941: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_dialpeer_tag: tag = 10003*Mar 1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_dialpeer_tag: tag = 10003VTSP sends out an alerting to the POTS leg; the phone is ringing at this time.
*Mar 1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_PROCEEDING, E_CC_ALERT]*Mar 1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_alert: .*Mar 1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3019095*Mar 1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_dialpeer_tag: tag = 10003The phone gets answered here, a bridge is now set up between the two call legs.
*Mar 1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_ALERTING, E_CC_BRIDGE]*Mar 1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_bridge: .The call is now connected.
*Mar 1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_ALERTING, E_CC_CONNECT]*Mar 1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_alert_connect: .*Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_ring_noan_timer_stop: 3019877The VTSP received a capabilities indication event from the CCAPI. The VTSP needs to be aware of this because it handles the DSPs.
*Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_CAPS_IND]*Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: .*Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: RTPPT:NTE[101],NTEtx[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDTMF[121],FaxRelay[122],CASsig[ 123],ClearChan[125],PCMu[0],PCMa[8]Codec[4],TxDynamicPayload[0], RxDynamicPayload[0]*Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: dtmf relay: mode=32, codec=1*Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: passthrough: cap_modem_proto 0, cap_modem_codec 0, cap_modem_redundancy 0, payload100, modem_relay 0, gw-xid=0*Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: Encap 1, Vad 2, Codec 0x4, CodecBytes 20,FaxRate 2, FaxBytes 20, FaxNsf 0xAD0051SignalType 2DtmfRelay 32, Modem 0, SeqNumStart 0x1343*Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind:*Mar 1 08:23:18.777: FORKING Parameters are forking mask: 0, simple_forking_codec_mask: 0, complex_forking_codec_mask 0*Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: [ mode:0,init:60, min:40, max:200]The VTSP received events regarding capabilities acknowledged from the call control API (CCAPI).
*Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_CAPS_ACK]*Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ack: .*Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ack: passthrough: cap_modem_proto 0, cap_modem_codec 0, cap_modem_redundancy 0, payload100, modem_relay 0, gw-xid=0*Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ack: Named Telephone Event payload: rcv 101, tx 101*Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_switch_codec:*Mar 1 08:23:18.777: DTMF Relay in act_switch_codec is 32*Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_dsp_encap_config:*Mar 1 08:23:18.777: set_dsp_encap_config: logical ssrc 40*Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_proto_from_cdb: cap_modem_proto 0*Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_switch_codec: codec = 16*Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3019878*Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, SP_PENDING_CODEC_SWITCH, E_DSPRM_PEND_SUCCESS]*Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_pend_codec_success: .*Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3019878*Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_open_voice_and_set_params: .*Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_dsp_encap_config:*Mar 1 08:23:18.781: set_dsp_encap_config: logical ssrc 40*Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_proto_from_cdb: cap_modem_proto 0*Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_playout_cdb:playout default*Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_dsp_echo_canceller_control: echo_cancel: 1*Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_add_fork:*Mar 1 08:23:18.785: vtsp_add_fork*Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info:*Mar 1 08:23:18.785: vtsp_update_fork_info: add_fork=0*Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_xmit_info_node:*Mar 1 08:23:18.785: vtsp_get_xmit_info_node*Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info:*Mar 1 08:23:18.785: vtsp_update_fork_info xmit func is 60FC43F0, context is 635BC51Cpeer_call_id: 900, stream_count: 1, update_flag 0Router#*Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info:*Mar 1 08:23:18.785: The stream bit-mask is 1*Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info:*Mar 1 08:23:18.785: The stream type is 0*Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info:*Mar 1 08:23:18.785: The logical ssrc is 64 for stream 0*Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_stream_count:*Mar 1 08:23:18.785: g711_voice_count=0 g711_avt_count = 0g711_voice_avt_count = 0 complex_voice_count = 1complex_avt_count = 0 complex_voice_avt_count = 0A digit begin event was detected while in the connect state. Digit 1 is dialed outbound on the POTS legs.
*Mar 1 08:23:26.745: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_call_digit_begin: vtsp_call_digit_begin: digit=1, digit_begin_flags=0x0, rtp_timestamp=0, rtp_expiration=0*Mar 1 08:23:26.745: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_DIGIT_BEGIN]*Mar 1 08:23:26.745: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_digit_begin:act_digit_begin*Mar 1 08:23:27.045: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_call_digit_end: vtsp_call_digit_end: digit=1, duration=300A digit end event was detected while in the connect state. The total duration of the digit was 300 ms.
*Mar 1 08:23:27.045: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_DIGIT_END,]*Mar 1 08:23:27.045: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_digit_end: act_digit_endThe call is hung up at this point, VTSP receives a bridge drop event from the CCAPI.
*Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_BRIDGE_DROP]*Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_remove_stream_node:*Mar 1 08:23:39.393: vtsp_remove_stream_node*Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_xmit_info_node:*Mar 1 08:23:39.393: vtsp_get_xmit_info_node*Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_remove_stream_node:*Mar 1 08:23:39.393: Stream count is 1 in function vtsp_remove_stream_node*Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_bdrop: .*Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_is_record_active:*Mar 1 08:23:39.393: vtsp_is_record_active: falseVTSP gets a disconnect event from the CCAPI.
*Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_DISCONNECT]*Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_disconnect: .Following the disconnect event from the CCAPI, the timers are stopped.
*Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_ring_noan_timer_stop: 3021940*Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_pcm_tone_detect_timer_stop: 3021940*Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_pcm_switchover_timer_stop: 3021940*Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_cm_detect_timer_stop: 3021940*Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_relay_mode_timer_stop: 3021940*Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_relay_stats_timer_stop: 3021940*Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021940*Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_disconnect: cdb 0x635FC480, cause 0x10*Mar 1 08:23:39.401: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3021940Statistics are collected for the DSP.
*Mar 1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_WAIT_STATS, E_DSP_GET_ERROR]*Mar 1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_get_error: .*Mar 1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_print_error_stats: rx_dropped=0 tx_dropped=0*Mar 1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_print_error_stats: rx_control=55 tx_control=18 tx_control_dropped=0 dsp_mode_channel_1=0 dsp_mode_channel_2=0c[0]=0c[1]=2c[2]=6c[3]=87c[4]=83c[5]=84c[6]=106c[7]=78c[8]=0c[9]=32639 c[10]=32639c[11]=32639c[12]=32639c[13]=32639c[14]=32639c[15]=32639*Mar 1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021941*Mar 1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3021941*Mar 1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_WAIT_STATS, E_DSP_GET_LEVELS]*Mar 1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_get_levels: .*Mar 1 08:23:39.413: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_stats_complete: .*Mar 1 08:23:39.413: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021941*Mar 1 08:23:39.413: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_ring_noan_timer_stop: 3021941*Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3021942The VTSP received a disconnect confirmation from the TSP layer.
*Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_WAIT_RELEASE, E_TSP_DISCONNECT_CONF]*Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_wrelease_release: .*Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_play_busy_timer_stop:*Mar 1 08:23:39.417: vtsp_play_busy_timer_stop: 3021942*Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021942*Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history: .*Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history:*Mar 1 08:23:39.417: vtsp_do_call_history : src carrier id*Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history:*Mar 1 08:23:39.421: vtsp_do_call_history : tgt carrier id*Mar 1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history: CoderRate 16DSP resource manager updates the state.
*Mar 1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CLOSE_DSPRM, E_DSPRM_CLOSE_COMPLETE]*Mar 1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_terminate: .*Mar 1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_free_cdb: ,cdb 0x635FC4803Related Commands
debug vtsp dsp
To show messages from the digital signal processor (DSP) to the universal access server or router, use the debug vtsp dsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vtsp dsp
no debug vtsp dsp
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
On Cisco AS5300 Series Access Servers
The debug vtsp dsp command shows messages from the DSP on the voice feature card (VFC) to the router; this command can be useful if you suspect that the VFC is not functional. It is a simple way to check if the VFC is responding to off-hook indications.
On Cisco 2600, 3600, MC3810 Series
The debug vtsp dsp command shows messages from the DSP to the router.
Note
Examples
The following example shows the VTSP DSP usage on a Cisco 3640 modular access router:
Router# debug vtsp dspVoice telephony call control dsp debugging is onRouter#*Mar 1 01:05:18.539: //12/A76D98838014/VTSP:(1/0:23):22:14:2/vtsp_dsp_echo_canceller_control: echo_cancel: 1Table 363 describes the significant fields shown in the display.
Related Commands
debug vtsp error
To display processing errors in the voice telephony service provider (VTSP), use the debug vtsp error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vtsp error
no debug vtsp error
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug vtsp error command can be used to check for mismatches in interface capabilities.
Note
Related Commands
debug vtsp event
To display the state of the gateway and the call events, use the debug vtsp event command in privileged EXEC mode. To display the machine state during voice telephony service provider (VTSP) event processing, use the no form of this command.
debug vtsp event
no debug vtsp event
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug vtsp event command can be used to enable state machine debugging.
Note
Examples
The following shows sample output from the debug vtsp event command:
Router# debug vtsp eventVoice Telephony event debugging is onThe following events are seen when the call is set up.
*Mar 1 22:20:39.138: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_SETUP_INDICATED, event: E_CC_PROCEEDING]When the phone starts ringing, the ALERT event appears.
*Mar 1 22:20:39.202: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_PROCEEDING, event: E_CC_ALERT]Router#As soon as the call is answered, the bridge comes up and the CONNECT event appears.
*Mar 1 22:20:47.798: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_ALERTING, event: E_CC_BRIDGE]*Mar 1 22:20:47.802: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_ALERTING, event: E_CC_CONNECT]The capabilities are exchanged as soon as the connection occurs.
*Mar 1 22:20:47.802: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_CAPS_IND]*Mar 1 22:20:47.802: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_CAPS_ACK]*Mar 1 22:20:47.802: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:SP_PENDING_CODEC_SWITCH, event: E_DSPRM_PEND_SUCCESS]The following debug outputs are regularly seen as the call progresses. The outputs indicate that collection of Tx/Rx/Delay/Error statistics is occurring.
*Mar 1 22:20:49.470: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_REQ_PACK_STAT]*Mar 1 22:20:49.482: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_TX]*Mar 1 22:20:49.482: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_RX]*Mar 1 22:20:49.486: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_VP_DELAY]*Mar 1 22:20:49.486: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_VP_ERROR]*Mar 1 22:20:51.638: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_REQ_PACK_STAT]*Mar 1 22:20:51.638: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_TX]*Mar 1 22:20:51.638: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_RX]*Mar 1 22:20:51.642: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_VP_DELAY]*Mar 1 22:20:51.642: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_VP_ERROR]Router#When digits are passed during the conversation, the digit begin and digit end events are seen.
*Mar 1 22:21:01.542: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_DIGIT_BEGIN]*Mar 1 22:21:01.842: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_DIGIT_END,]*Mar 1 22:21:01.962: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_DIGIT_BEGIN]*Mar 1 22:21:02.262: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_DIGIT_END,]Router#Once the call is hung up from one side, the bridge_drop and the disconnect events appear.
*Mar 1 22:21:10.834: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_TSP_DISCONNECT_IND]*Mar 1 22:21:10.838: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_BRIDGE_DROP]*Mar 1 22:21:10.838: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_DISCONNECT]Following the disconnect event, the signaling state becomes S_WAIT_STATS, during which the DSP stats are collected.
*Mar 1 22:21:10.842: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_WAIT_STATS, event: E_DSP_GET_ERROR]*Mar 1 22:21:10.846: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_WAIT_STATS, event: E_DSP_GET_LEVELS]*Mar 1 22:21:10.854: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_WAIT_STATS, event: E_DSP_GET_TX]The conference is torn down and the DSP is released.
*Mar 1 22:21:10.854: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_WAIT_RELEASE, event: E_TSP_DISCONNECT_CONF]*Mar 1 22:21:10.858: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CLOSE_DSPRM, event: E_DSPRM_CLOSE_COMPLETE]Related Commands
debug vtsp port
To observe the behavior of the voice telephony service provider (VTSP) state machine on a specific voice port, use the debug vtsp port command in privileged EXEC mode. To disable debugging output, use the no form of this command.
For Cisco 2600 and Cisco 3600 Series with Analog Voice Ports
debug vtsp port slot/subunit/port
no debug vtsp port slot/subunit/port
For Cisco 2600 and Cisco 3600 Series with Digital Voice Ports (With T1 Packet Voice Trunk Network Modules)
debug vtsp port slot/port:ds0-group
no debug vtsp port slot/port:ds0-group
For Cisco MC3810 Series with Analog Voice Ports
debug vtsp port slot/port
no debug vtsp port slot/port
For Cisco MC3810 Series with Digital Voice Ports
debug vtsp port slot/port
no debug vtsp port slot/ds0-group
Syntax Description
For the Cisco 2600 and Cisco 3600 Series with Digital Voice Ports
For the Cisco MC3810 Series with Analog Voice Ports
For the Cisco MC3810 Series with Digital Voice Ports
Defaults
Debug VTSP commands are not limited to a specific port.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug vtsp port command to limit the debug output to a specific voice port. The debug output can be quite voluminous for a single channel. The entire VTSP debug output from a platform with 12 voice ports might create problems. Use this debug command with any or all of the other debug modes.
Execution of no debug vtsp all will turn off all VTSP-level debugging. It is usually a good idea to turn off all debugging and then enter the debug commands you are interested in one by one. This will help to avoid confusion about which ports you are actually debugging.
Note
Related Commands
debug vpm all
Enables all VPM debugging.
show debug
Displays which debug commands are enabled.
voice call debug
Allows configuration of the voice call debug output.
debug vtsp rtp
To show the voice telephony service provider (VTSP) Real-Time Protocol (RTP) packet debugging, use the debug vtsp rtp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vtsp rtp {both | from-dsp | to-dsp} payload payload-type codec
no debug vtsp rtp
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
We recommend that you log output from the debug vtsp rtp command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Examples
The following example shows the VTSP RTP debugging:
Router# debug vtsp rtp both pay allVoice telephony RTP Packet debugging enabled for payloads of all types of packets from and to DSPThe following line shows the payload from the DSP (telephony leg) to the IP leg:
*Mar 1 01:10:05.687: //20/4DD959B48020/VTSP:(1/0:23):22:14:2/vtsp_print_rtp_header: s=DSP d=VoIP payload 0x12 ssrc 0x40 sequence 0x19E3 timestamp 0xCCDCE092The following line shows the payload from the IP leg to the DSP (telephony leg):
*Mar 1 01:10:05.699: //20/4DD959B48020/VTSP:(1/0:23):22:14:2/vtsp_print_rtp_header: s=VoIP d=DSP payload 0x12 ssrc 0xAF0534E3 sequence 0x92A timestamp 0x6BE50Related Commands
debug vtsp dsp
Shows messages from the DSP.
voice call debug
Allows configuration of the voice call debug output.
debug vtsp send-nse
To trigger the voice telephony service provider (VTSP) software module to send a triple redundant network services engine (NSE), use the debug vtsp send-nse command in privileged EXEC mode. To disable this action, use the no form of this command.
debug vtsp send-nse
no debug vtsp send-nse
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
We recommend that you log output from the debug vtsp send-nse command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Related Commands
debug vtsp session
To trace how the router interacts with the digital signal processor (DSP) based on the signaling indications from the signaling stack and requests from the application, use the debug vtsp session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vtsp session
no debug vtsp session
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug vtsp session command traces how the router interacts with the DSP based on the signaling indications from the signaling stack and requests from the application. This debug command displays information about how each network indication and application request is handled, signaling indications, and DSP control messages.
This debug level shows the internal workings of the voice telephony call state machine.
Note
Examples
The following shows sample output from the debug vtsp session command:
Router# debug vtsp sessionVoice telephony call control session debugging is onAt this point, the VTSP is not aware of anything. The format of this message is
//callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number:•
•
•
•
•
•
*Mar 2 01:20:43.225: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: .The original and the translated calling number are the same (55555) and the original and the translated called number are the same (888545). These numbers are often the same because if a translation rule is applied, it will be on the dial peers or the ports both of which comes later than these VTSP messages in the Cisco IOS code execution.
*Mar 2 01:20:43.225: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: calling_number(original)= calling_number(xlated)=55555 called_number(original)= called_number(xlated)=888545 redirectNumber(original)= redirectNumber(xlated)=The VTSP got a call setup indicator from the TSP layer with called number 888545 and calling number 55555. There is no awareness of the CallEntry ID (-1) or the GUID (xxxxxxxxxxxx).
*Mar 2 01:20:43.225: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_call_setup_ind: (sdb=0x637AA6C0, tdm_info=0x0, tsp_info=0x630B6050, calling_number=55555 calling_oct3 = 0x80, called_number=888545 called_oct3 = 0x80, oct3a=0x0): peer_tag=10002*Mar 2 01:20:43.225: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_fill_setup_ind: ev.clg.clir is 0ev.clg.clid_transparent is 0ev.clg.null_orig_clg is 0ev.clg.calling_translated is false*Mar 2 01:20:43.229: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_call_setup_ind: .*Mar 2 01:20:43.229: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_allocate_cdb: ,cdb 0x637B2A68*Mar 2 01:20:43.229: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_call_setup_ind:*Mar 2 01:20:43.229: source route labelAt this point, the VTSP is not aware of the anything. The format of this message is
//callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number:•
•
•
•
•
•
*Mar 2 01:20:43.229: //-1/F90073EB8080/VTSP:(1/0:23):-1:0:2/vtsp_do_call_setup_ind: Call ID=98432, guid=637B43F4The VTSP learns that the B channel used changed from -1 to 22.
*Mar 2 01:20:43.229: //-1/F90073EB8080/VTSP:(1/0:23):22:0:2/vtsp_do_call_setup_ind: type=0, under_spec=1615186336, name=, id0=23, id1=0, id2=0, calling=55555,called=888545 subscriber=RegularLinevtsp_do_call_setup_ind: redirect DN = reason = -1*Mar 2 01:20:43.229: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_normal_call_setup_ind: .The VTSP learns the CallEntry ID. The format of this message is
//callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number:•
•
•
•
•
•
*Mar 2 01:20:43.233: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_insert_cdb: ,cdb 0x637B2A68, CallID=84*Mar 2 01:20:43.233: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_open_voice_and_set_params: .In the following outputs VTSP sets some of the voice parameters for this call:
•
•
•
•
*Mar 2 01:20:43.233: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_modem_proto_from_cdb: cap_modem_proto 0*Mar 2 01:20:43.233: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/set_playout_cdb: playout default*Mar 2 01:20:43.237: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_save_dialpeer_tag: tag = 10003*Mar 2 01:20:43.237: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_report_digit_control: vtsp_report_digit_control: enable=0:*Mar 2 01:20:43.237: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_report_digit_control: digit reporting disabled*Mar 2 01:20:43.237: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_get_digit_timeouts: : vtsp_get_digit_timeoutsThe VTSP sends out a call-proceeding message to the POTS leg.
*Mar 2 01:20:43.241: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_process_event: vtsp:[1/0:23:84, S_SETUP_INDICATED, E_CC_PROCEEDING]*Mar 2 01:20:43.241: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/act_proceeding: .Router#*Mar 2 01:20:43.297: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_get_dialpeer_tag: tag = 10003*Mar 2 01:20:43.301: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_get_dialpeer_tag: tag = 10003VTSP sends out an alerting to the POTS leg; the phone is ringing now.
*Mar 2 01:20:43.301: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_process_event: vtsp:[1/0:23:84, S_PROCEEDING, E_CC_ALERT]*Mar 2 01:20:43.301: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/act_alert: .*Mar 2 01:20:43.301: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_timer_stop: 9124331Router#*Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_get_dialpeer_tag: tag = 10003The phone gets answered here, and a bridge is now set up between the two call legs.
*Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_process_event: vtsp:[1/0:23:84, S_ALERTING, E_CC_BRIDGE]*Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/act_bridge: .The call is now connected.
*Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_process_event: vtsp:[1/0:23:84, S_ALERTING, E_CC_CONNECT]*Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/act_alert_connect: .*Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_ring_noan_timer_stop: 9125229Related Commands
debug vpm all
Enables all VPM debugging.
debug vtsp port
Limits VTSP debug output to a specific voice port.
show debug
Displays which debug commands are enabled.
debug vtsp stats
To debug periodic statistical-information-request messages sent and received from the digital signal processor (DSP) during a call, use the debug vtsp stats command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vtsp stats
no debug vtsp stats
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug vtsp stats command generates a collection of DSP statistics for generating Real-Time Transport Protocol (RTCP) packets and a collection of other statistical information.
Note
Related Commands
debug vtsp tone
To display debugging messages showing the types of tones generated by the Voice over IP (VoIP) gateway, use the debug vtsp tone command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vtsp tone
no debug vtsp tone
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
We recommend that you log output from the debug vtsp tone command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Related Commands
debug vtsp vofr subframe
To display the first 10 bytes (including header) of selected Voice over Frame Relay (VoFR) subframes for the interface, use the debug vtsp vofr subframe command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vtsp vofr subframe payload [from-dsp] [to-dsp]
no debug vtsp vofr subframe
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Each debug output displays the first 10 bytes of the FRF.11 subframe, including header bytes. The from-dsp and to-dsp options can be used to limit the debugs to a single direction. If not specified, debugs are displayed for subframes when they are received from the DSP and before they are sent to the DSP.
Use extreme caution in selecting payload options 0 and 6. These options may cause network instability.
Note
Related Commands
debug vwic-mft firmware controller
To display debug output from the multiflex (MFT) Voice/WAN interface card (VWIC) controller firmware, use the debug vwic-mft firmware controller command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vwic-mft firmware controller {t1 | e1} slot/port {alarm | all | config | fdl | loopback | register display | status}
no debug vwic-mft firmware controller {t1 | e1} slot/port {alarm | all | config | fdl | loopback | register display | status}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.3(6)
This command was introduced.
12.3(7)T
This command was integrated into Cisco IOS Release 12.3(7)T.
Usage Guidelines
Use the debug vwic-mft firmware controller command in privileged EXEC mode to provide firmware-level information for VWICs when information is required beyond the Cisco IOS T1 and E1 controller statistics. The physical-layer information generated by this command includes alarm conditions, line status, controller issues, and register settings, all of which can be used to help troubleshoot MFT VWIC problems.
All the debugging keywords, except register display, enable debugging on both ports of a 2-port card. For example, if T1 0/0 and T1 0/1 are two ports on a 2-port MFT card and any of the keywords except register display is enabled, debugging output will be generated for both ports because they share a common firmware system.
The Cisco 1- and 2-port T1/E1 multiflex VWICs support voice and data applications in Cisco 2600, Cisco 3600, and Cisco 3700 series multiservice routers. The multiflex VWIC combines WAN interface card and voice interface card functionality.
Caution
Examples
The following sample output displays firmware output about alarm messages for an MFT VWIC installed in slot 0.
Router# debug vwic-mft firmware controller e1 0/0 alarmvwic-mft firmware output messages for wic slot set to: AlarmRouter#*Mar 4 13:58:14.702: E1T1 0/1 FW: alm1:0e p:01 ALOS LOS LOF*Mar 4 13:58:15.194: E1T1 0/1 FW: CERR: 00*Mar 4 13:58:15.194: E1T1 0/1 FW: MERR: 00*Mar 4 13:58:15.194: E1T1 0/1 FW: FERR: 00
Note
Table 364 describes the significant fields shown in the display.
Related Commands
show controllers e1
Displays information about E1 links.
show controllers t1
Displays information about T1 links.
debug vxml
Note
To display debugging messages for VoiceXML features, use the debug vxml command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vxml [all | application | background | error | event | grammar | puts | ssml | trace | warning]
no debug vxml [all | application | background | error | event | grammar | puts | ssml | trace | warning]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The output of this command is affected by the debug condition application voice command. If the debug condition application voice command is configured and the <cisco-debug> element is enabled in the VoiceXML document, debugging output is limited to the VoiceXML application named in the debug condition application voice command.
The debug vxml command enables all VoiceXML debugging messages except those displayed by the grammar and ssml keywords. The debug vxml all command enables all VoiceXML debugging messages including grammar and SSML.
Caution
Examples
The following example shows output from the debug vxml application command:
Router# debug vxml applicationvxml application debugging is onRouter#1w5d: //-1//VAPP:/vapp_get_apphandler:1w5d: vapp_get_apphandler: Script callme1w5d: //-1//VAPP:/vapp_get_apphandler_core:1w5d: //-1/000000000000/VAPP:/vapp_InterpInitConfigParams:1w5d: //-1/000000000000/VAPP:/vapp_evt_handler: State VAPP_ACTIVE got event CC_D1w5d: //-1/000000000000/VAPP:/vapp_driver: pInterp[660E10FC]:1w5d: //-1/000000000000/VAPP:/vapp_driver: evtID: 28 vapp record state: 01w5d: //-1/000000000000/VAPP:/vapp_evt_setup:1w5d: //-1//VAPP:/vapp_incoming_caldoc-rtr54-01#lblock:1w5d: vapp_incoming_callblock:1w5d: //39/924083218026/VAPP:/vapp_load_or_run_script:1w5d: //39/924083218026/VAPP:/vapp_load_or_run_script:1w5d: The VXML Script with len=1450 starts:-------------------------------------<?xml version="1.0" encoding="iso-8859-1"?><vxml version="1.0"><property name="fetchtimeout" value="20s"/><var name="phone_num"/><form id="main"><noinput><prompt><audio src="flas1w5d: //39/924083218026/VAPP:/vapp_media_play:1w5d: //39/Router#924083218026/VAPP:/vapp_media_play: prompt=flash:welcome_test.au:1w5d: //39/924083218026/VAPP:/vapp_checksessionstate:1w5d: //39/924083218026/VAPP:/vapp_checkifdone:1w5d: //39/924083218026/VAPP:/vapp_evt_handler: State VAPP_ACTIVE got event CC_E1w5d: //39/924083218026/VAPP:/vapp_driver: pInterp[660E10FC]:1w5d: //39/924083218026/VAPP:/vapp_driver: evtID: 36 vapp record state: 01w5d: //39/924083218026/VAPP:/vapp_checksessionstate:1w5d: //39/924083218026/VAPP:/vapp_checkifdoRouter#ne:1w5d: //39/924083218026/VAPP:/vapp_evt_handler: State VAPP_ACTIVE got event MSWR1w5d: //39/924083218026/VAPP:/vapp_driver: pInterp[660E10FC]:1w5d: //39/924083218026/VAPP:/vapp_driver: evtID: 77 vapp record state: 01w5d: //39/924083218026/VAPP:/vapp_media_done: evID=77 status=0, protocol=0, st01w5d: //39/924083218026/VAPP:/vapp_media_play:1w5d: //39/924083218026/VAPP:/vapp_media_play: prompt=flash:enter_dest.au:1w5d: //39/924083218026/VAPP:/vapp_cRouter#hecksessionstate:1w5d: //39/924083218026/VAPP:/vapp_checkifdone:Router#1w5d: //39/924083218026/VAPP:/vapp_evt_handler: State VAPP_ACTIVE got event MSWR1w5d: //39/924083218026/VAPP:/vapp_driver: pInterp[660E10FC]:1w5d: //39/924083218026/VAPP:/vapp_driver: evtID: 77 vapp record state: 01w5d: //39/924083218026/VAPP:/vapp_media_done: evID=77 status=0, protocol=0, st01w5d: //39/924083218026/VAPP:/vapp_digit_collect:1w5d: //39/924083218026/VAPP:/vapp_checksessionstate:1w5d: //39/924083218026/VAPP:/vapp_checkifdone:Router#1w5d: //39/924083218026/VAPP:/vapp_evt_handler: State VAPP_ACTIVE got event APPE1w5d: //39/924083218026/VAPP:/vapp_driver: pInterp[660E10FC]:1w5d: //39/924083218026/VAPP:/vapp_driver: evtID: 87 vapp record state: 01w5d: //39/924083218026/VAPP:/vapp_digit_collection_done:1w5d: //39/924083218026/VAPP:/vapp_digit_collection_done: digits [5551234], sta]1w5d: //39/924083218026/VAPP:/vapp_gain_control_default:1w5d: //39/924083218026/VAPP:/vapp_placecall:Router#1w5d: //39/924083218026/VAPP:/vapp_checksessionstate:1w5d: //39/924083218026/VAPP:/vapp_checkifdone:Router#1w5d: //39/924083218026/VAPP:/vapp_evt_handler: State VAPP_ACTIVE got event APPE1w5d: //39/924083218026/VAPP:/vapp_driver: pInterp[660E10FC]:1w5d: //39/924083218026/VAPP:/vapp_driver: evtID: 84 vapp record state: 01w5d: //39/924083218026/VAPP:/vapp_evt_setupdone:1w5d: //39/924083218026/VAPP:/vapp_checksessionstate:1w5d: //39/924083218026/VAPP:/vapp_checkifdone:Router#1w5d: //39/924083218026/VAPP:/vapp_evt_handler: State VAPP_ACTIVE got event CC_D1w5d: //39/924083218026/VAPP:/vapp_driver: pInterp[660E10FC]:1w5d: //39/924083218026/VAPP:/vapp_driver: evtID: 15 vapp record state: 01w5d: //39/924083218026/VAPP:/vapp_call_disconnected:1w5d: //39/924083218026/VAPP:/vapp_connection_destroy:1w5d: //39/924083218026/VAPP:/vapp_checksessionstate:1w5d: //39/924083218026/VAPP:/vapp_checkifdone:1w5d: //39/924083218026/VAPP:/vapp_evt_handler: StaRouter#te VAPP_ACTIVE got event CC_EV_CONF_DESTROY_DONE1w5d: //39/924083218026/VAPP:/vapp_driver: pInterp[660E10FC]:1w5d: //39/924083218026/VAPP:/vapp_driver: evtID: 34 vapp record state: 01w5d: //39/924083218026/VAPP:/vapp_leg_disconnect:1w5d: //39/924083218026/VAPP:/vapp_checksessionstate:1w5d: //39/924083218026/VAPP:/vapp_checkifdone:1w5d: //39/924083218026/VAPP:/vapp_evt_handler: State VAPP_ACTIVE got event CC_E1w5d: //39/924083218026/VAPP:/vapp_driver: pInterp[660E10FC]Router#:1w5d: //39/924083218026/VAPP:/vapp_driver: evtID: 16 vapp record state: 01w5d: //39/924083218026/VAPP:/vapp_terminate:1w5d: //39/924083218026/VAPP:/vapp_session_exit_event_name: Exit Event vxml.sese1w5d: //39/924083218026/VAPP:/vapp_checksessionstate:1w5d: //39/924083218026/VAPP:/vapp_terminate_initiation:1w5d: //39/924083218026/VAPP:/vapp_checkifdone:1w5d: //39/924083218026/VAPP:/vapp_evt_handler: State VAPP_CLEANING got event CE1w5d: //39/924083218Router#026/VAPP:/vapp_cleaner:1w5d: //39/924083218026/VAPP:/vapp_checksessionstate:1w5d: //39/924083218026/VAPP:/vapp_checkifdone:1w5d: //39/924083218026/VAPP:/vapp_evt_handler: State VAPP_CLEANING got event AE1w5d: //39/924083218026/VAPP:/vapp_cleaner:1w5d: //39/924083218026/VAPP:/vapp_cleaner: VxmlDialogDone event=vxml.session.c01w5d: //39/924083218026/VAPP:/vapp_popifdone:1w5d: //39/924083218026/VAPP:/vapp_checkifdone:1w5d: //39/924083218026/VAPP:/vapp_Router#cleanup_apphandler:1w5d: vapp_cleanup_apphandler: Terminate FALSE Terminated TRUE{HAN[VXML_HAN][NU}1w5d: //39/924083218026/VAPP:/vapp_free_apphandler: {HAN[VXML_HAN][NULL ] }The following example shows output from the debug vxml background command:
Router# debug vxml backgroundvxml background messages debugging is onRouter#1w5d: //-1//VAPP:/vapp_init_apphandler:1w5d: //-1//VXML:/vxml_create: url=flash:call.vxml vapphandle=660E10FCRouter#1w5d: //-1//VAPP:/vapp_process: Interp DoneThe following examples show output from the debug vxml error command:
Router# debug vxml errorThis example output shows an error when the version header is missing:
*May 10 20:08:57.572://7/98119BD78008/VXML:/vxml_vxml_build:tftp://demo/scripts/test.vxml at line 2:<vxml version> required attribute missing*May 10 20:08:57.576://7/98119BD78008/VXML:/vxml_create:*May 10 20:08:57.576:code=ERROR vapp=VAPP_SUCCESS vxml=VXML_ERROR_INVALIDThis example output shows an error when a field item is not used according to the DTD:
*May 10 20:16:23.315://8/A1BCF458800B/VXML:/vxml_start_element_handler:tftp://demo/scripts/test.vx ml at line 4:Element <field> is not used according to DTD*May 10 20:16:23.315://8/A1BCF458800B/VXML:/vxml_create:*May 10 20:16:23.315:code=ERROR vapp=VAPP_SUCCESS vxml=VXML_ERROR_INVALIDThis example output shows an error when there is a tag mismatch:
*May 10 20:17:44.485://10/D21DEAB58011/VXML:/vxml_parse:tftp://demo/scripts/test.vxml at line 48:mismatched tag*May 10 20:17:44.485://10/D21DEAB58011/VXML:/vxml_create:*May 10 20:17:44.485:code=ERROR vapp=VAPP_SUCCESS vxml=VXML_ERROR_INVALIDThe following example shows output from the debug vxml event command:
Router# debug vxml eventvxml events debugging is onRouter#1w5d: //47/000000000000/VXML:/vxml_media_done: status 0 async_status 100000000Router#1w5d: //47/000000000000/VXML:/vxml_media_done: status 0 async_status 300000000Router#1w5d: //47/000000000000/VXML:/vxml_digit_collection_done: vxmlp 6534C7C8 status01w5d: //47/000000000000/VXML:/vxml_digit_collection_done: digits 55512341w5d: //47/000000000000/VXML:/vxml_digit_collection_done: name v0Router#1w5d: //47/000000000000/VXML:/vxml_placecall_done: duration=0 status=0 async_st0Router#1w5d: //47/000000000000/VXML:/vxml_user_hangup: duration 3 status=A async_statu0The following example shows output from the debug vxml grammar command:
Router# debug vxml grammarvxml xml grammar syntax checking debugging is onRouter#Feb 11 13:47:25.110: //-1//VAPP:/vapp_get_apphandler:*Feb 11 13:47:25.114: vapp_get_apphandler: Script help*Feb 11 13:47:25.114: //-1//VAPP:/vapp_get_apphandler_core:*Feb 11 13:47:25.114: //-1/000000000000/VAPP:/vapp_InterpInitConfigParams:*Feb 11 13:47:25.114: //-1//VAPP:/vapp_init_apphandler:*Feb 11 13:47:25.114: //-1/000000000000/VAPP:/vapp_evt_handler: State VAPP_ACTIVE got event CC_EV_CALL_SETUP_IND*Feb 11 13:47:25.114: //-1/000000000000/VAPP:/vapp_driver: pInterp[62DD481C]:*Feb 11 13:47:25.114: //-1/000000000000/VAPP:/vapp_driver: evtID: 28 vapp record state: 0*Feb 11 13:47:25.114: //-1/000000000000/VAPP:/vapp_evt_setup:*Feb 11 13:47:25.114: //-1//VAPP:/vapp_incoming_callblock:*Feb 11 13:47:25.114: vapp_incoming_callblock:*Feb 11 13:47:25.114: //7/9AC9CCF28008/VAPP:/vapp_load_or_run_script:*Feb 11 13:47:25.114: //7/9AC9CCF28008/VAPP:/vapp_load_or_run_script:*Feb 11 13:47:25.114: The VXML Script with len=741 starts:-------------------------------------<?xml version = "1.0"?><vxml version = "2.0"><property name="universals" value="all"/><form id="check_help"><field name="book"><grammar version="1.0" mode="voice" xml:lang="en-US">*Feb 11 13:47:25.114: //-1//VXML:/vxml_create: url=tftp://dirt/lshen/regression/help.vxml vapphandle=62DD481C*Feb 11 13:47:25.114: //-1//VXML:/vxml_mem_init:*Feb 11 13:47:25.118: //7/9AC9CCF28008/VXML:/vxml_rule_build: tftp://dirt/lshen/regression/help.vxml at line 8: attribute <rule> with invalid value (wrong_scope)*Feb 11 13:47:25.118: //7/9AC9CCF28008/VXML:/vxml_create:*Feb 11 13:47:25.118: code=ERROR vapp=VAPP_SUCCESS vxml=VXML_ERROR_INVALID*Feb 11 13:47:25.118: //-1//VXML:/vxml_mem_free:*Feb 11 13:47:25.118: //-1//VXML:/vxml_mem_free1:*Feb 11 13:47:25.118: //7/9AC9CCF28008/VAPP:/vapp_terminate:*Feb 11 13:47:25.118: //7/9AC9CCF28008/VAPP:/vapp_session_exit_event_name: Exit Event vxml.session.complete*Feb 11 13:47:25.118: //7/9AC9CCF28008/VAPP:/vapp_checksessionstate:*Feb 11 13:47:25.118: //7/9AC9CCF28008/VAPP:/vapp_terminate_initiation:*Feb 11 13:47:25.118: //7/9AC9CCF28008/VAPP:/vapp_checkifdone:*Feb 11 13:47:25.122: //7/9AC9CCF28008/VAPP:/vapp_evt_handler: State VAPP_CLEANING got event CC_EV_CALL_MODIFY_DONE*Feb 11 13:47:25.122: //7/9AC9CCF28008/VAPP:/vapp_cleaner:*Feb 11 13:47:25.122: //7/9AC9CCF28008/VAPP:/vapp_cleaner: Ignoring Event CC_EV_CALL_MODIFY_DONE(36) in Cleanup*Feb 11 13:47:25.122: //7/9AC9CCF28008/VAPP:/vapp_checksessionstate:*Feb 11 13:47:25.122: //7/9AC9CCF28008/VAPP:/vapp_checkifdone:*Feb 11 13:47:25.138: //7/9AC9CCF28008/VAPP:/vapp_evt_handler: State VAPP_CLEANING got event CC_EV_CALL_DISCONNECT_DONE*Feb 11 13:47:25.138: //7/9AC9CCF28008/VAPP:/vapp_cleaner:*Feb 11 13:47:25.138: //7/9AC9CCF28008/VAPP:/vapp_checksessionstate:*Feb 11 13:47:25.138: //7/9AC9CCF28008/VAPP:/vapp_checkifdone:*Feb 11 13:47:25.138: //7/9AC9CCF28008/VAPP:/vapp_evt_handler: State VAPP_CLEANING got event APP_EV_VXMLINTERP_DONE*Feb 11 13:47:25.138: //7/9AC9CCF28008/VAPP:/vapp_cleaner:*Feb 11 13:47:25.138: //7/9AC9CCF28008/VAPP:/vapp_cleaner: VxmlDialogDone event=vxml.session.complete, status 3*Feb 11 13:47:25.138: //7/9AC9CCF28008/VAPP:/vapp_popifdone:*Feb 11 13:47:25.138: //7/9AC9CCF28008/VAPP:/vapp_checkifdone:*Feb 11 13:47:25.138: //-1//VAPP:/vapp_process: Interp Done*Feb 11 13:47:25.138: //7/9AC9CCF28008/VAPP:/vapp_cleanup_apphandler:*Feb 11 13:47:25.138: vapp_cleanup_apphandler: Terminate FALSE Terminated TRUE{HAN[VXML_HAN][NULL ] ( )}*Feb 11 13:47:25.138: //7/9AC9CCF28008/VAPP:/vapp_free_apphandler: {HAN[VXML_HAN][NULL ] ( )}The following example shows output from the debug vxml ssml command:
Router# debug vxml ssmlRouter#vxml ssml syntax checking debugging is onFeb 11 13:55:28.994: //-1//VAPP:/vapp_get_apphandler:*Feb 11 13:55:28.994: vapp_get_apphandler: Script help*Feb 11 13:55:28.994: //-1//VAPP:/vapp_get_apphandler_core:*Feb 11 13:55:28.994: //-1/A93E3F8F800E/VAPP:/vapp_InterpInitConfigParams:*Feb 11 13:55:28.998: //-1//VAPP:/vapp_init_apphandler:*Feb 11 13:55:28.998: //-1/003E3F8F800E/VAPP:/vapp_evt_handler: State VAPP_ACTIVE got event CC_EV_CALL_SETUP_IND*Feb 11 13:55:28.998: //-1/003E3F8F800E/VAPP:/vapp_driver: pInterp[62DD481C]:*Feb 11 13:55:28.998: //-1/003E3F8F800E/VAPP:/vapp_driver: evtID: 28 vapp record state: 0*Feb 11 13:55:28.998: //-1/003E3F8F800E/VAPP:/vapp_evt_setup:*Feb 11 13:55:28.998: //-1//VAPP:/vapp_incoming_callblock:*Feb 11 13:55:28.998: vapp_incoming_callblock:*Feb 11 13:55:28.998: //10/BB2F243F8011/VAPP:/vapp_load_or_run_script:*Feb 11 13:55:28.998: //10/BB2F243F8011/VAPP:/vapp_load_or_run_script:*Feb 11 13:55:28.998: The VXML Script with len=760 starts:-------------------------------------<?xml version = "1.0"?><vxml version = "2.0"><property name="universals" value="all"/><form id="check_help"><field name="book"><grammar version="1.0" mode="voice" xml:lang="en-US">*Feb 11 13:55:28.998: //-1//VXML:/vxml_create: url=tftp://dirt/lshen/regression/help.vxml vapphandle=62DD481C*Feb 11 13:55:28.998: //-1//VXML:/vxml_mem_init:*Feb 11 13:55:29.002: //10/BB2F243F8011/VXML:/vxml_parse: tftp://dirt/lshen/regression/help.vxml at line 16: mismatched tag*Feb 11 13:55:29.002: //10/BB2F243F8011/VXML:/vxml_create:*Feb 11 13:55:29.002: code=ERROR vapp=VAPP_SUCCESS vxml=VXML_ERROR_INVALID*Feb 11 13:55:29.002: //-1//VXML:/vxml_mem_free:*Feb 11 13:55:29.002: //-1//VXML:/vxml_mem_free1:*Feb 11 13:55:29.002: //10/BB2F243F8011/VAPP:/vapp_terminate:*Feb 11 13:55:29.002: //10/BB2F243F8011/VAPP:/vapp_session_exit_event_name: Exit Event vxml.session.complete*Feb 11 13:55:29.002: //10/BB2F243F8011/VAPP:/vapp_checksessionstate:*Feb 11 13:55:29.002: //10/BB2F243F8011/VAPP:/vapp_terminate_initiation:*Feb 11 13:55:29.002: //10/BB2F243F8011/VAPP:/vapp_checkifdone:*Feb 11 13:55:29.006: //10/BB2F243F8011/VAPP:/vapp_evt_handler: State VAPP_CLEANING got event CC_EV_CALL_MODIFY_DONE*Feb 11 13:55:29.006: //10/BB2F243F8011/VAPP:/vapp_cleaner:*Feb 11 13:55:29.006: //10/BB2F243F8011/VAPP:/vapp_cleaner: Ignoring Event CC_EV_CALL_MODIFY_DONE(36) in Cleanup*Feb 11 13:55:29.006: //10/BB2F243F8011/VAPP:/vapp_checksessionstate:*Feb 11 13:55:29.006: //10/BB2F243F8011/VAPP:/vapp_checkifdone:*Feb 11 13:55:29.022: //10/BB2F243F8011/VAPP:/vapp_evt_handler: State VAPP_CLEANING got event CC_EV_CALL_DISCONNECT_DONE*Feb 11 13:55:29.022: //10/BB2F243F8011/VAPP:/vapp_cleaner:*Feb 11 13:55:29.022: //10/BB2F243F8011/VAPP:/vapp_checksessionstate:*Feb 11 13:55:29.022: //10/BB2F243F8011/VAPP:/vapp_checkifdone:*Feb 11 13:55:29.022: //10/BB2F243F8011/VAPP:/vapp_evt_handler: State VAPP_CLEANING got event APP_EV_VXMLINTERP_DONE*Feb 11 13:55:29.022: //10/BB2F243F8011/VAPP:/vapp_cleaner:*Feb 11 13:55:29.022: //10/BB2F243F8011/VAPP:/vapp_cleaner: VxmlDialogDone event=vxml.session.complete, status 3*Feb 11 13:55:29.022: //10/BB2F243F8011/VAPP:/vapp_popifdone:*Feb 11 13:55:29.022: //10/BB2F243F8011/VAPP:/vapp_checkifdone:*Feb 11 13:55:29.022: //-1//VAPP:/vapp_process: Interp Done*Feb 11 13:55:29.022: //10/BB2F243F8011/VAPP:/vapp_cleanup_apphandler:*Feb 11 13:55:29.022: vapp_cleanup_apphandler: Terminate FALSE Terminated TRUE{HAN[VXML_HAN][NULL ] ( )}*Feb 11 13:55:29.022: //10/BB2F243F8011/VAPP:/vapp_free_apphandler: {HAN[VXML_HAN][NULL ] ( )}The following example shows output from the debug vxml trace command:
Router# debug vxml tracevxml trace debugging is onRouter#1w5d: //-1//VXML:/vxml_mem_init:1w5d: //51/359408288031/VXML:/vxml_offramp_mailhdrs_get:1w5d: //51/359408288031/VXML:/vxml_start: vxmlhandle=65350A7C vapphandle=660E1001w5d: //51/359408288031/VXML:/vxml_vxml_proc:1w5d: <vxml> URI(abs):flash:call.vxml scheme=flash path=call.vxml base= URI(abs01w5d: <var>: namep=phone_num1w5d: //-1//VXML:/vxml_stand_alone: scope=document, application = document1w5d: //51/359Router#408288031/VXML:/vxml_form_proc:1w5d: <form>: id=main scope=dialog1w5d: vxml_form_init current scope: dialog1w5d: vxml_counter_reset:1w5d: vxml_counter_reset:1w5d: //51/359408288031/VXML:/vxml_formitem_select: Status=VXML_STATUS_OK,1w5d: //51/359408288031/VXML:/vxml_formitem_select: AsyncStatus=VXML_STATUS_OK1w5d: //51/359408288031/VXML:/vxml_block_proc:1w5d: <block>:1w5d: //51/359408288031/VXML:/vxml_item_attrs_proc: name=_in61w5d: //51/359408288031/VXML:/vxml_expr_eval: expRouter#r=dialog._in6='defined'1w5d: //51/359408288031/VXML:/vxml_prompt_proc:1w5d: <prompt>: bargein=0 count=1 typeaheadflush=01w5d: //51/359408288031/VXML:/vxml_audio_proc:1w5d: <audio>: URI(abs):flash:welcome_test.au scheme=flash path=welcome_tes01w5d: //51/359408288031/VXML:/vxml_vapp_media_play: bargein=0 timeout=0 typeahe01w5d: //51/359408288031/VXML:/vxml_vapp_media_play:1w5d: //51/359408288031/VXML:/vxml_vapp_meRouter#dia_play: audio=flash:welcome_test.au cachable=1 timeout201w5d: //51/359408288031/VXML:/vxml_leave_scope: scope=81w5d: //51/359408288031/VXML:/vxml_vapp_vcr_control_disable:1w5d: //51/359408288031/VXML:/vxml_start: vxmlhandle=65350A7C vapphandle=660E1001w5d: //51/359408288031/VXML:/vxml_vxml_proc:1w5d: <vxml> URI(abs):flash:call.vxml scheme=flash path=call.vxml base= URI(abs01w5d: //51/359408288031/VXML:/vxmRouter#l_block_proc:1w5d: <block>:1w5d: //51/359408288031/VXML:/vxml_item_attrs_proc: name=_in61w5d: //51/359408288031/VXML:/vxml_form_proc:1w5d: <form>: id=main scope=dialog1w5d: //51/359408288031/VXML:/vxml_formitem_select: Status=VXML_STATUS_OK,1w5d: //51/359408288031/VXML:/vxml_formitem_select: AsyncStatus=VXML_STATUS_OK1w5d: //51/359408288031/VXML:/vxml_field_proc:1w5d: <field>: type=number1w5d: //51/359408288031/VXML:/vxml_item_attrs_proc: name=get_phone_num modal=amRouter#pt_counter=11w5d: //51/359408288031/VXML:/vxml_prompt_proc:1w5d: <prompt>: bargein=1 count=1 typeaheadflush=01w5d: //51/359408288031/VXML:/vxml_audio_proc:1w5d: <audio>: URI(abs):flash:enter_dest.au scheme=flash path=enter_dest.au01w5d: //51/359408288031/VXML:/vxml_vapp_media_play: bargein=1 timeout=0 typeahe01w5d: //51/359408288031/VXML:/vxml_vapp_media_play:1w5d: //51/359408288031/VXML:/vxml_vapp_media_play: audioRouter#=flash:enter_dest.au cachable=1 timeout201w5d: //51/359408288031/VXML:/vxml_vapp_vcr_control_disable:1w5d: //51/359408288031/VXML:/vxml_vapp_digit_collect: termchar # maxDigits 0 t01w5d: //51/359408288031/VXML:/vxml_start: vxmlhandle=65350A7C vapphandle=660E1001w5d: //51/359408288031/VXML:/vxml_vxml_proc:1w5d: <vxml> URI(abs):flash:call.vxml scheme=flash path=call.vxml base= URI(abs1Router#.01w5d: //51/359408288031/VXML:/vxml_field_proc:1w5d: <field>: type=number1w5d: //51/359408288031/VXML:/vxml_item_attrs_proc: name=get_phone_num modal=a21w5d: //51/359408288031/VXML:/vxml_filled_proc:1w5d:1w5d: <filled>: mode=all1w5d: //51/359408288031/VXML:/vxml_assign_proc:1w5d: <assign>: namep=phone_num expr=get_phone_num1w5d: //51/359408288031/VXML:/vxml_goto_proc:1w5d: <goto>: caching=fast fetchhint=invalid fetchtimeout=20 URI:#transfer_mmRouter#entp=transfer_me1w5d: vxml_dialog_reset:1w5d: //51/359408288031/VXML:/vxml_leave_scope: scope=1101w5d: //51/359408288031/VXML:/vxml_leave_scope: scope=81w5d: //51/359408288031/VXML:/vxml_vxml_proc:1w5d: <vxml> URI(abs):flash:call.vxml scheme=flash path=call.vxml base= URI(abs01w5d: //51/359408288031/VXML:/vxml_form_proc:1w5d: <form>: id=transfer_me scope=dialog1w5d: vxml_form_init current scope: dialog1w5d: <var>: namep=mydRouter#ur1w5d: vxml_counter_reset:1w5d: //51/359408288031/VXML:/vxml_formitem_select: Status=VXML_STATUS_OK,1w5d: //51/359408288031/VXML:/vxml_formitem_select: AsyncStatus=VXML_STATUS_OK1w5d: //51/359408288031/VXML:/vxml_transfer_proc:1w5d: <transfer>:1w5d: //51/359408288031/VXML:/vxml_item_attrs_proc: name=mycall dest_expr='phoeRouter#ctreason=-11w5d: //51/359408288031/VXML:/vxml_vapp_placecall: dest 5551234 timeout 15 maxl01w5d: //51/359408288031/VXML:/vxml_vapp_gain_control_default:1w5d: //51/359408288031/VXML:/vxml_expr_eval: expr=dialog.mycall = 'far_end_dis'1w5d: //51/359408288031/VXML:/vxml_expr_eval: expr=dialog.mycall$.duration = 21w5d: //51/359408288031/VXML:/vxml_start: vxmlhandle=65350A7C vapphandle=660E1001w5d: //51/359408288031/VXML:/vxml_vxmlRouter#_proc:1w5d: <vxml> URI(abs):flash:call.vxml scheme=flash path=call.vxml base= URI(abs01w5d: //51/359408288031/VXML:/vxml_transfer_proc:1w5d: <transfer>:1w5d: //51/359408288031/VXML:/vxml_item_attrs_proc: name=mycall URI(abs):phone-Router#1, redirectreason=-11w5d: //51/359408288031/VXML:/vxml_form_proc:1w5d: <form>: id=transfer_me scope=dialog1w5d: //51/359408288031/VXML:/vxml_filled_proc:1w5d:1w5d: <filled>: mode=all1w5d: //51/359408288031/VXML:/vxml_assign_proc:1w5d: <assign>: namep=mydur expr=mycall$.duration1w5d: //51/359408288031/VXML:/vxml_if_proc:1w5d: <if>: cond=mycall == 'busy'1w5d: //51/359408288031/VXML:/vxml_leave_scope: scope=81w5d: //51/359408288031/VXML:/vxml_formitem_select: Status=VXML_STRouter#ATUS_OK,1w5d: //51/359408288031/VXML:/vxml_formitem_select: AsyncStatus=VXML_STATUS_OK1w5d: //51/359408288031/VXML:/vxml_formitem_select: the form is full1w5d: //51/359408288031/VXML:/vxml_vapp_terminate: vapp_status=0 ref_count 01w5d: //-1//VXML:/vxml_mem_free:1w5d: //-1//VXML:/vxml_mem_free1:Related Commands
debug warm-reboot
To display warm reload debug information, use the debug warm-reboot command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug warm-reboot
no debug warm-reboot
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the reload warm file url command when the debug warm-reboot command is enabled:
Router# debug warm-rebootRouter# reload warm file tftp://9.1.0.1/c7200-p-mz.portProceed with reload? [confirm]Loading c7200-p-mz.port from 9.1.0.1 (via Ethernet5/0):!!!00:05:43:ptr :63B978E000:05:43:magic :A45727200:05:43:ptr :63B9802000:05:43:magic :000:05:43:ptr :63B9838000:05:43:magic :000:05:43:ptr :63B983A000:05:43:magic :FEEDFACE00:05:43:uncomp_size :2749E7C00:05:43:comp_size :E966F000:05:43:comp_checksum :9BB3605300:05:43:uncomp_checksum :56F1754B!!![OK - 15323964 bytes]Decompressing the image :###00:06:22:Image checksum correct -1#68274321300:06:22:Compressed Image checksum correct### [OK]Number 0 source 0x63BD17C4Number 1 source 0x63C43AD0Number 2 source 0x63C83AFCNumber 3 source 0x63CC3B28...Number 156 source 0x66384074Number 157 source 0x663C40A0Number 158 source 0x664040CCwrb_copy_and_launch location = 0x664040CC00:06:39:Found elf header at the expected location00:06:39:Source elf_hdr->e_shnum = A00:06:39:Setting up to copy ELF section 100:06:39: to image_info section 000:06:39: sh_name = B00:06:39: sh_type = 100:06:39: sh_flags = 700:06:39: sh_addr = 8000800000:06:39: sh_offset = 6000:06:39: sh_size = 186C00000:06:39: sh_link = 000:06:39: sh_info = 000:06:39: sh_addralign = 2000:06:39: sh_entsize = 0...00:06:40:Setting up to copy ELF section 400:06:40: to image_info section A000:06:40: sh_name = 1F00:06:40: sh_type = 100:06:40: sh_flags = 1000000300:06:40: sh_addr = 8275038000:06:40: sh_offset = 27483E000:06:40: sh_size = 18A000:06:40: sh_link = 000:06:40: sh_info = 000:06:40: sh_addralign = 1000:06:40: sh_entsize = 000:06:40:cpu type :1900:06:40:image_info->entry_point = 8000800000:06:40:image_info->section_count = A100:06:40:image_info->monstack = 80007FC000:06:40:image_info->monra = BFC014E400:06:40:image_info->param0 = 200:06:40:image_info->param1 = 000:06:40:image_info->param2 = 8000599800:06:40:image_info->param3 = 8000800000:06:40:Section00:06:40:SectionDecompressed Image checksum correctRestricted Rights Legend...debug webvpn
To debug information for SSL VPN applications and network activity, use the debug webvpn command in privileged EXEC mode. To stop debugging messages from being processed and displayed, use the no form of this command.
debug webvpn [verbose] [aaa | acl | cifs | citrix [verbose] | cookie [verbose] | count | csd | data | dns | emweb [state] | entry context-name [source ip [network-mask] | user username] | http [authentication | trace | verbose] | package | sdps [level number] | sock [flow] | sso | timer | trie | tunnel [traffic acl-number | verbose] | url-disp | webservice [verbose]]
no debug webvpn [verbose] [aaa | acl | cifs | citrix [verbose] | cookie [verbose] | count | csd | data | dns | emweb [state] | entry context-name [source ip [network-mask] | user username] | http [authentication | trace | verbose] | package | sdps [level number] | sock [flow] | sso | timer | trie | tunnel [traffic acl-number | verbose] | url-disp | webservice [verbose]]
Syntax Description
Command Default
None
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command with caution on a production router or a networking device. Only enable debugging for individual components as necessary. This restriction is intended to prevent the console session from receiving large numbers of messages.
The no form of this command turns off feature debugging. It does not matter if the verbose keyword has been used or not.
If the no form of this command is used with the verbose keyword option for any keyword, all keyword and argument fields must be an exact match.
Examples
debug webvpn Command Output for Various SSL VPN Sessions
The following example displays debug webvpn output for various SSL VPN sessions:
Router# debug webvpn*Dec 23 07:47:41.368: WV: Entering APPL with Context: 0x64C5F270,Data buffer(buffer: 0x64C877D0, data: 0x4F27B638, len: 272,offset: 0, domain: 0)*Dec 23 07:47:41.368: WV: http request: /sslvpn with domain cookie*Dec 23 07:47:41.368: WV: Client side Chunk data written..buffer=0x64C877B0 total_len=189 bytes=189 tcb=0x6442FCE0*Dec 23 07:47:41.368: WV: sslvpn process rcvd context queue event*Dec 23 07:47:41.372: WV: sslvpn process rcvd context queue event*Dec 23 07:47:41.372: WV: Entering APPL with Context: 0x64C5F270,Data buffer(buffer: 0x64C877D0, data: 0x4F26D018, len: 277,offset: 0, domain: 0)*Dec 23 07:47:41.372: WV: http request: /webvpn.html with domain cookie*Dec 23 07:47:41.372: WV: [Q]Client side Chunk data written..buffer=0x64C877B0 total_len=2033 bytes=2033 tcb=0x6442FCE0*Dec 23 07:47:41.372: WV: Client side Chunk data written..buffer=0x64C87710 total_len=1117 bytes=1117 tcb=0x6442FCE0debug webvpn Command Output for a Specific User
The following example displays information for a specific user (user1 under the context "mycontext") and for a feature or function:
Router# debug webvpn entry mycontext_user_user1! The above line turns debugging on for user1.! The following line turns on debugging for a feature (or features) or function (or functions)—in this case; for authentication, authorization, and accounting (AAA).Router# debug webvpn aaa*Dec 23 07:56:41.351: WV-AAA: AAA authentication request sent for user: "user1"*Dec 23 07:56:41.351: WV-AAA: AAA Authentication Passed!*Dec 23 07:56:41.351: WV-AAA: User "user1" has logged in from "10.107.163.147" to gateway "sslvpn" context "mycontext"*Dec 23 07:59:01.535: WV-AAA: User "user1" has logged out from gateway "sslvpn" context "mycontext"debug webvpn Command Cookie and HTTP Output for a Group of Users
The following example displays cookie and HTTP information for a group of users under the context "mycontext" having a source IP range from 192.168.1.1. to 192.168.1.255:
Router# debug webvpn entry mycontext source 192.168.1.0 255.255.255.0! The above command line sets up debugging for the group.!The following command lines turn on debugging for cookie and HTTP information.Router# debug webvpn cookieRouter# debug webvpn httpThe actual output is as follows:
*Dec 23 08:10:11.191: WV-HTTP: Original client requestGET /webvpn.html HTTP/1.1*Dec 23 08:10:11.191: WV-HTTP: HTTP Header parsing complete*Dec 23 08:10:11.191: WV-HTTP: * HTTP request complete*Dec 23 08:10:11.191: WV-COOKIE: Enter VW context cookie check with Context:0x64C5F470,buffer: 0x64C87710, buffer->data: 0x4F26D018, buffer->len: 277,cookie: 0x4F26D10A, length: 33*Dec 23 08:10:11.191: WV-COOKIE: webvpn context cookie received is webvpncontext=00@mycontext*Dec 23 08:10:11.191: WV-COOKIE: context portion in context cookie is: mycontext*Dec 23 08:10:11.327: WV-HTTP: Original client requestGET /paramdef.js HTTP/1.1*Dec 23 08:10:11.327: WV-HTTP: HTTP Header parsing complete*Dec 23 08:10:11.327: WV-HTTP: * HTTP request completedebug webvpn Command SSO Output
The following output example displays information about SSO ticket creation, session setup, and response handling:
Router# debug webvpn sso*Jun 12 20:37:01.052: WV-SSO: Redirect to SSO web agent URL - http://example.examplecompany.com/vpnauth/*Jun 12 20:37:01.052: WV_SSO: Set session cookie with SSO redirect*Jun 12 20:37:01.056: WV-SSO: Set SSO auth flag*Jun 12 20:37:01.056: WV-SSO: Attach credentials - building auth ticket*Jun 12 20:37:01.060: WV-SSO: user: [user11], secret: [example123], version: [1.0], login time: [BCEFC86D], session key: [C077F97A], SHA1 hash : [B07D0A924DB33988D423AE9F937C1C5A66404819]*Jun 12 20:37:01.060: WV-SSO: auth_ticket : user11:1.0@C077F97A@BCEFC86D@B07D0A924DB33988D423AE9F937C1C5A66404819*Jun 12 20:37:01.060: WV-SSO: Base64 credentials for the auth_ticket: dXNlcjExOjEuMEBDMDc3Rjk3QUBCQ0VGQzg2REBCMDdEMEE5MjREQjMzOTg4RDQyM0FFOUY5MzdDMUM1QTY2NDA0OD E5*Jun 12 20:37:01.060: WV-SSO: Decoded credentials = user11:1.0@C077F97A@BCEFC86D@B07D0A924DB33988D423AE9F937C1C5A66404819*Jun 12 20:37:01.060: WV-SSO: Starting SSO request timer for 15-second*Jun 12 20:37:01.572: WV-SSO: SSO auth response rcvd - status[200]*Jun 12 20:37:01.572: WV-SSO: Parsed non-SM cookie: SMCHALLENGE*Jun 12 20:37:01.576: WV-SSO: Parsed SMSESSION cookie*Jun 12 20:37:01.576: WV-SSO: Sending logon page after SSO auth successdebug wlccp packet
To display the packets being delivered to and from the wireless domain services (WDS) device, use the debug wlccp packet command in privileged EXEC mode. To disable the packet display, use the no form of this command.
debug wlccp packet
no debug wlccp packet
Syntax Description
This command has no arguments of keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following command displays the packets delivered to and from the WDS device:
Router# debug wlccp packetRelated Commands
debug wlccp wds
To display wireless domain services (WDS) debugging messages, state messages, and failure statistics, use the debug wlccp wds command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug wlccp wds {authenticator | state | statistics}
no debug wlccp wds
Syntax Description
authenticator
MAC and Extensible Authentication Protocol (EAP) authentication.
state
WDS state and debugging messages.
statistics
WDS failure statistics.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following command displays WDS failure statistics:
Router# debug wlccp wds statisticsRelated Commands
Posted: Mon Jul 2 06:58:08 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
