Cisco IOS Debug Command Reference, Release 12.3 T - Debug Commands: debug voip ivr through debug vpm all [Cisco IOS Software Releases 12.3 T]

Table Of Contents

debug voip ivr

debug voip ivr all

debug voip ivr applib

debug voip ivr callsetup

debug voip ivr digitcollect

debug voip ivr dynamic

debug voip ivr error

debug voip ivr redirect

debug voip ivr script

debug voip ivr settlement

debug voip ivr states

debug voip ivr supplementary-service

debug voip ivr tclcommands

debug voip profile fax

debug voip profile help

debug voip profile modem

debug voip profile voice

debug voip rawmsg

debug voip rtcp

debug voip rtp

debug voip settlement all

debug voip settlement enter

debug voip settlement error

debug voip settlement exit

debug voip settlement misc

debug voip settlement network

debug voip settlement security

debug voip settlement ssl

debug voip settlement transaction

debug voip tsp

debug voip vtsp

debug voip xcodemsp

debug vpdn

debug vpdn pppoe-data

debug vpdn pppoe-error

debug vpdn pppoe-events

debug vpdn pppoe-packet

debug vpm all

debug voip ivr

To display debugging messages for Voice over IP (VoIP) interactive voice response (IVR) interactions, use the debug voip ivr command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr type
no debug voip ivr type
Syntax Description

type

Type of debugging messages. The keywords are as follows:

•all—(Optional) Displays debugging messages for all types.

•applib—(Optional) Displays application programming interface (API) libraries being processed.

•callsetup—(Optional) Displays call setup being processed.

•digitcollect—(Optional) Displays digits collected during the call.

•dynamic—(Optional) Displays dynamic prompt play debug.

•error—(Optional) Displays errors.

•script—(Optional) Displays script debug.

•settlement—(Optional) Displays settlement activities.

•states—(Optional) Displays states.

•tclcommands—(Optional) Displays the Tool Command Language (TCL) commands used in the script.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

This command was implemented on the following platforms: Cisco 2600 series, Cisco 3620, Cisco 3660, Cisco AS5350, Cisco AS5400, Cisco AS5850, Cisco AS5300, Cisco AS5800, and Cisco MC3810.

Examples

The following is sample output from the debug voip ivr command with the applib keyword:
Router# debug voip ivr applib 
ivr:
 ivr app library debugging is on
!
Jan 10 17:42:04.180:AppManagerCCAPI_Interface:
Jan 10 17:42:04.180:AppNewLeg
Jan 10 17:42:04.180:AppPushLegORConnection:Pushing LEG[34   ][NULL
] Onto {HAN[TCL_HAND][NULL  ]   ( )}
Jan 10 17:42:04.180:Event CC_EV_CALL_SETUP_IND[29]:LEG[34
][TCL_HAND]
Jan 10 17:42:04.184:AppPushHandler:Pushing {HAN[DC_HAND ][NULL  ]
( )} Onto {HAN[TCL_HAND][NULL  ]   ( LEG[34   ][TCL_HAND] )}
Jan 10 17:42:04.184:AppPushLegORConnection:Pushing LEG[34
][TCL_HAND] Onto {HAN[DC_HAND ][TCL_HAND]   ( )}
Jan 10 17:42:04.184:$ mediaPlay():CallID 34
Jan 10 17:42:04.184:Event CC_EV_CALL_REPORT_DIGITS_DONE[45]:LEG[34
][DC_HAND ]
Jan 10 17:42:17.261:AppMediaCallback:CallID 34 received
           response 'MSW_RESPONSE_TYPE_PLAY'
           with reason 'MSW_REASON_GENERIC_SUCCESS'
Jan 10 17:42:17.261:Event APP_EV_MEDIA_CALLBACK[47]:LEG[34
][DC_HAND ]
Jan 10 17:42:18.209:%ISDN-6-DISCONNECT:Interface Serial0:0
disconnected from unknown , call lasted 13 seconds
The following is sample output from the debug voip ivr command with the callsetup keyword:
Router# debug voip ivr callsetup 
!
Jan 10 17:45:57.528:%SYS-5-CONFIG_I:Configured from console by lab on console
Jan 10 17:46:37.682:InitiateCallSetup:Incoming[66] AlertTime -1
Destinations(1) [ 3450070 ]
Jan 10 17:46:37.682:DNInitiate:Destination[3450070]
Jan 10 17:46:37.682:DNSetupPeer:
Jan 10 17:46:37.682:Destination SetupPeer cid(66), destPat(3450070),
match(2), prefix(), peer(61CB5CAC)
Jan 10 17:46:37.762:DNHandler:
(DN_SETTING[1])--(CC_EV_CALL_ALERT[11])--IGNORED-->>(DN_SETTING[1])
Jan 10 17:46:37.762:CS_Setting_ALERT:
Jan 10 17:46:37.762:CSPopLegAndWait:
Jan 10 17:46:37.762:CallSetupHandler:
 (CS_SETTING[0]) -----(CS_EV_ALERT[0])------->>>(CS_CONFINGALERT[4])
Jan 10 17:46:37.762:CS_ConfingAlert_CREATEDONE:
Jan 10 17:46:37.762:CallSetupHandler:
 (CS_CONFINGALERT[4])
-----(CS_EV_CREATEDONE[4])------->>>(CS_CONFEDALERT[5])
Jan 10 17:46:37.762:CallSetupHandler:
 (CS_CONFEDALERT[5])--(DN_SETTING[APP_EV_NULL])--IGNORED-->>>(CS_CONFEDALERT[5])
!
Jan 10 17:46:47.682:CallSetupHandler:
 (CS_CONFEDALERT[5])--(DN_SETTING[APP_EV_NULL])--IGNORED-->>>(CS_CONFEDALERT[5])
Jan 10 17:46:48.642:CS_ConfedAlert_CONNECTED:
Jan 10 17:46:48.642:CSDiscReturnAndEmptyLegALL:
Jan 10 17:46:48.642:DNCleanup:
Jan 10 17:46:48.642:DNSettlementCleanup:cid(66) trans=0, provider=0
Jan 10 17:46:48.642:CSReturnIFDone:CallSetup Returning(Status
CS_ACTIVE)
Jan 10 17:46:48.642:CallSetupHandler:
 (CS_CONFEDALERT[5]) -----(CS_EV_CONNECTED[1])------->>>(CS_CONFED[3])
Jan 10 17:46:48.646:CallSetupCleanup:
!
The following is sample output from the debug voip ivr command with the digitcollect keyword:
Router# debug voip ivr digitcollect 
ivr:
 ivr digit collect debugging is on
!
Jan 10 17:47:55.558:DigitCollect:DialPlan=FALSE AbortKey=* TermKey=#
NumPatts=1
       Enable=FALSE InterruptPrompt=TRUE maxDigits=11
Jan 10 17:47:55.558:act_DCRunning_RDone:callid=68 Enable succeeded.
!
Jan 10 17:48:04.006:DCHandlerFunc:PassingThrough
Jan 10 17:48:04.066:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:04.066:act_DCRunning_RDone:callid=68 Reporting disabled.
Jan 10 17:48:04.066:DigitCollectComplete:Status 5=DC_MATCHED_PATTERN.
Digits=1
Jan 10 17:48:04.070:DigitCollect:DialPlan=FALSE AbortKey=* TermKey=#
NumPatts=0
       Enable=FALSE InterruptPrompt=TRUE maxDigits=11
Jan 10 17:48:04.070:DCHandlerCleanup:
Jan 10 17:48:04.074:act_DCRunning_RDone:callid=68 Enable succeeded.
!
Jan 10 17:48:08.038:DCHandlerFunc:PassingThrough
Jan 10 17:48:09.246:DCHandlerFunc:PassingThrough
Jan 10 17:48:09.286:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:09.478:DCHandlerFunc:PassingThrough
Jan 10 17:48:09.506:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:10.739:DCHandlerFunc:PassingThrough
Jan 10 17:48:10.779:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:11.027:DCHandlerFunc:PassingThrough
Jan 10 17:48:11.067:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:11.687:DCHandlerFunc:PassingThrough
Jan 10 17:48:11.747:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:12.219:DCHandlerFunc:PassingThrough
Jan 10 17:48:12.279:act_DCRunning_Digit::pLeg 68 Digit 2
Jan 10 17:48:14.227:DCHandlerFunc:PassingThrough
Jan 10 17:48:14.287:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:14.779:DCHandlerFunc:PassingThrough
Jan 10 17:48:14.859:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:15.307:DCHandlerFunc:PassingThrough
Jan 10 17:48:15.359:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:15.719:DCHandlerFunc:PassingThrough
Jan 10 17:48:15.759:act_DCRunning_Digit::pLeg 68 Digit 2
Jan 10 17:48:16.219:DCHandlerFunc:PassingThrough
Jan 10 17:48:16.299:act_DCRunning_Digit::pLeg 68 Digit T
Jan 10 17:48:16.299:act_DCRunning_RDone:callid=68 Reporting disabled.
Jan 10 17:48:16.299:DigitCollectComplete:Status 5=DC_MATCHED_PATTERN.
Digits=1111121112
Jan 10 17:48:16.303:DCHandlerCleanup:
Jan 10 17:48:16.335:DigitCollect:DialPlan=TRUE AbortKey=* TermKey=#
NumPatts=0
       Enable=FALSE InterruptPrompt=TRUE maxDigits=0
Jan 10 17:48:16.339:act_DCRunning_RDone:callid=68 Enable succeeded.
The following is sample output from the debug voip ivr command with the script keyword:
Router# debug voip ivr script 
ivr:
 ivr script debugging is on
!
Jan 10 17:49:10.250:FSM Transtion:([1
]CALL_INIT,[29]ev_setup_indication)---([10]act_Setup)--->([4
]LANGSELECTION)
Jan 10 17:49:10.250:TotalLanguages= 2
!
Jan 10 17:49:16.662:FSM Transtion:([4
]LANGSELECTION,[55]ev_digitcollect_done)---([1 ]act_LangSelect)--->([5
]CARDSELECTION)
!
Jan 10 17:49:20.630:([5 ]CARDSELECT,[47]ev_media_d) ------> NOTHANDLED
Jan 10 17:49:26.770:FSM Transtion:([5
]CARDSELECTION,[55]ev_digitcollect_done)---([2
]act_GotCardNumber)--->([6 ]AUTHORIZE)
Jan 10 17:49:26.806:FSM Transtion:([6
]AUTHORIZE,[49]ev_authorize_done)---([8 ]act_FirstAuthorized)--->([7
]GETDEST)
Jan 10 17:49:26.806: aaa authorize Status=ao_000
!
Jan 10 17:49:33.395:([7 ]GETDEST  ,[47]ev_media_d) ------> NOTHANDLED
Jan 10 17:49:36.411:FSM Transtion:([7
]GETDEST,[55]ev_digitcollect_done)---([3 ]act_GotDest)--->([8
]SECONDAUTHORIZE)
Jan 10 17:49:36.451:FSM Transtion:([8
]SECONDAUTHORIZE,[49]ev_authorize_done)---([5
]act_SecondAuthorized)--->([10]PLACECALL)
Jan 10 17:49:36.451: aaa authorize Status=ao_000
Jan 10 17:49:42.179:FSM Transtion:
([10]PLACECALL,[47]ev_media_done)---([9
]act_CallSetup)--->([10]PLACECALL)
The following is sample output from the debug voip ivr with the tclcommands keyword:
Router# debug voip ivr tclcommands 
ivr tcl commands debugging is on
Jan 10 17:50:29.106:tcl_infotagCmd:infotag get leg_ani
Jan 10 17:50:29.106:tcl_getInfoCmd:get leg_ani
Jan 10 17:50:29.106:vtr_ci_incani:argc 2 argindex 2
Jan 10 17:50:29.106:tcl_infotagCmd:infotag set med_language 1
Jan 10 17:50:29.106:tcl_setInfoCmd:set med_language 1
Jan 10 17:50:29.106:vtw_ms_language:
Jan 10 17:50:29.106:tcl_legCmd:leg setupack leg_incoming
Jan 10 17:50:29.106:tcl_setupAckCmd:setupack leg_incoming
Jan 10 17:50:29.106:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:29.106:tcl_legCmd:leg proceeding leg_incoming
Jan 10 17:50:29.106:tcl_callProceedingCmd:proceeding leg_incoming
Jan 10 17:50:29.106:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:29.110:tcl_legCmd:leg connect leg_incoming
Jan 10 17:50:29.110:tcl_callConnectCmd:connect leg_incoming
Jan 10 17:50:29.110:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:29.110:tcl_legCmd:leg collectdigits leg_incoming param1
patterns
Jan 10 17:50:29.110:tcl_collectDigitsCmd:collectdigits leg_incoming
param1 patterns
Jan 10 17:50:29.110:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:29.110:tcl_mediaCmd:media play leg_incoming _welcome.au
%s1000 %c1 _lang_sel1.au %s1000 %c2 _lang_sel2.au
Jan 10 17:50:29.110:tcl_mediaPlayCmd:play leg_incoming _welcome.au
%s1000 %c1 _lang_sel1.au %s1000 %c2 _lang_sel2.au
Jan 10 17:50:29.110:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
!
Jan 10 17:50:35.506:tcl_infotagCmd:infotag get evt_status
Jan 10 17:50:35.506:tcl_getInfoCmd:get evt_status
Jan 10 17:50:35.506:vtr_ev_status:
Jan 10 17:50:35.510:tcl_infotagCmd:infotag get evt_dcdigits
Jan 10 17:50:35.510:tcl_getInfoCmd:get evt_dcdigits
Jan 10 17:50:35.510:vtr_ev_dcdigits:
Jan 10 17:50:35.510:DCDIGITS [1]
Jan 10 17:50:35.510:tcl_infotagCmd:infotag set med_language 1
Jan 10 17:50:35.510:tcl_setInfoCmd:set med_language 1
Jan 10 17:50:35.510:vtw_ms_language:
Jan 10 17:50:35.510:tcl_legCmd:leg collectdigits leg_incoming param1
Jan 10 17:50:35.510:tcl_collectDigitsCmd:collectdigits leg_incoming
param1
Jan 10 17:50:35.510:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:35.510:tcl_mediaCmd:media play leg_incoming
_enter_card_num.au
Jan 10 17:50:35.510:tcl_mediaPlayCmd:play leg_incoming
_enter_card_num.au
Jan 10 17:50:35.514:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
!
Jan 10 17:50:43.878:tcl_infotagCmd:infotag get evt_status
Jan 10 17:50:43.878:tcl_getInfoCmd:get evt_status
Jan 10 17:50:43.878:vtr_ev_status:
Jan 10 17:50:43.882:tcl_infotagCmd:infotag get evt_dcdigits
Jan 10 17:50:43.882:tcl_getInfoCmd:get evt_dcdigits
Jan 10 17:50:43.882:vtr_ev_dcdigits:
Jan 10 17:50:43.882:DCDIGITS [1111121112]
Jan 10 17:50:43.882:tcl_aaaCmd:aaa authorize 111112 1112 50073
leg_incoming
Jan 10 17:50:43.882:tcl_AuthorizeCmd:authorize 111112 1112 50073
leg_incoming
Jan 10 17:50:43.882:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:43.882:Authorize
Jan 10 17:50:43.882:  account=111112
Jan 10 17:50:43.882:  password=1112
Jan 10 17:50:43.882:  ani   =50073
Jan 10 17:50:43.882:  dnis  =
Jan 10 17:50:43.910:tcl_infotagCmd:infotag get evt_status
Jan 10 17:50:43.910:tcl_getInfoCmd:get evt_status
Jan 10 17:50:43.910:vtr_ev_status:
Jan 10 17:50:43.914:tcl_infotagCmd:infotag get aaa_avpair_exists
creditAmount
Jan 10 17:50:43.914:tcl_getInfoCmd:get aaa_avpair_exists creditAmount
Jan 10 17:50:43.914:vtr_ra_avpair_exists:
Jan 10 17:50:43.914:tcl_infotagCmd:infotag get aaa_avpair creditAmount
Jan 10 17:50:43.914:tcl_getInfoCmd:get aaa_avpair creditAmount
Jan 10 17:50:43.914:vtr_ra_avpair:
Jan 10 17:50:43.914:tcl_legCmd:leg collectdigits leg_incoming param2
Jan 10 17:50:43.914:tcl_collectDigitsCmd:collectdigits leg_incoming
param2
Jan 10 17:50:43.914:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:43.914:tcl_mediaCmd:media play leg_incoming _you_have.au
%a1000 %s1000 _enter_dest.au
Jan 10 17:50:43.914:tcl_mediaPlayCmd:play leg_incoming _you_have.au
%a1000 %s1000 _enter_dest.au
Jan 10 17:50:43.918:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
debug voip ivr all

To display both states and error debugging messages for interactive voice response (IVR) interactions, use the debug voip ivr all command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr all
no debug voip ivr all
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300 and Cisco AS5800; and on the Cisco MC3810 multiservice access concentrators.

Usage Guidelines

We recommend that you log output from the debug voip ivr all 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 shows sample debugging output from the debug voip ivr all command. The show debug command shows all of the enabled IVR debugging traces.
Router# debug voip ivr all 
All ivr debugging is on
Router#
Router# show debug
ivr:
  ivr errors debugging is on
  ivr state transitions debugging is on
  ivr settlement activities debugging is on
  ivr dynamic promptplaying debugging is on
  ivr script debugging is on
  ivr app library debugging is on
  ivr tcl commands debugging is on
  ivr digit collect debugging is on
  ivr call setup debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 03:15:57.831: //170/90241C6380DD/APPL:/AppManagerCCAPI_Interface:
*Mar 11 03:15:57.831: //-1//TCL2:/TclGetInterp: Script test
*Mar 11 03:15:57.831: //-1//APPL:/AppNewLeg:
*Mar 11 03:15:57.831: //-1//APPL:/AppSaveRawMsg:
*Mar 11 03:15:57.831: //170//APPL:LP:HN34330144:/AppPushLegORConnection: Pushing LEG[170    
][NULL    ][LEG_INCINIT(1)][
Cause(0)][UC=1 ] Onto {HAN[TCL_HAND][NULL    ]  ( )}
*Mar 11 03:15:57.835: //170//APPL:/AppProcessEvent: Event CC_EV_CALL_SETUP_IND[28]:
*Mar 11 03:15:57.835: //170//APPL:/AppProcessEvent: LEG[170    
][TCL_HAND][LEG_INCINIT(1)][Cause(0)][UC=1 ]
*Mar 11 03:15:57.835: //170//TCL2:/TclInterpHandler: CC_EV_CALL_SETUP_IND
*Mar 11 03:15:57.835: //170//TCL2:/TclInterpDriver:
*Mar 11 03:15:57.835: //170//TCL2:/TclEventPreprocessing:
*Mar 11 03:15:57.835: //-1//TCL2:/TclIncomingCallBlock:
*Mar 11 03:15:57.835: //170//TCL2:/SettlementValidateCall: target=, tokenp=0x0
*Mar 11 03:15:57.835: //170//TCL2:/MakeTransition: FSM Transtion: ([1 
]CALL_INIT,[28]ev_setup_indication)---([10]act_Set
up)--->([7 ]AUTHENTICATE)
*Mar 11 03:15:57.835: //170//TCL2:/tcl_legCmd: leg setupack leg_incoming
*Mar 11 03:15:57.835: //170//TCL2:/tcl_setupAckCmd: setupack leg_incoming
*Mar 11 03:15:57.835: //170//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 03:15:57.835: //170//TCL2:/vtd_lg_incoming: Legs [170 ]
*Mar 11 03:15:57.835: //170//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 03:15:57.839: //170//TCL2:/tcl_legCmd: leg proceeding leg_incoming
*Mar 11 03:15:57.839: //170//TCL2:/tcl_callProceedingCmd: proceeding leg_incoming
*Mar 11 03:15:57.839: //170//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 03:15:57.839: //170//TCL2:/vtd_lg_incoming: Legs [170 ]
*Mar 11 03:15:57.839: //170//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 03:15:57.839: //170//TCL2:/tcl_legCmd: leg connect leg_incoming
*Mar 11 03:15:57.839: //170//TCL2:/tcl_callConnectCmd: connect leg_incoming
*Mar 11 03:15:57.839: //170//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 03:15:57.839: //170//TCL2:/vtd_lg_incoming: Legs [170 ]
*Mar 11 03:15:57.839: //170//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 03:15:57.839: //170//TCL2:/tcl_infotagCmd: infotag get leg_ani
*Mar 11 03:15:57.839: //170//TCL2:/tcl_getInfoCmd: get leg_ani
*Mar 11 03:15:57.843: //170//TCL2:/vtr_lg_incani: argc 2 argindex 2
*Mar 11 03:15:57.843: //170//TCL2:/tcl_aaaCmd: aaa authenticate 300
*Mar 11 03:15:57.843: //170//TCL2:/tcl_AuthenticateCmd: authenticate 300
*Mar 11 03:15:57.843: //170//TCL2:/tcl_AuthenticateCmd: account=300, password=, 
methodList=, av-send=
*Mar 11 03:15:57.851: //-1//APPL:HN34330144:/AppProcessEvent: Event 
APP_EV_AUTHENTICATE_DONE[81]:
*Mar 11 03:15:57.851: //-1//APPL:HN34330144:/AppProcessEvent: HAN[TCL_HAN][NULL    
][FALSE] [UC=1 ]
*Mar 11 03:15:57.851: //-1//TCL2:HN34330144:/TclInterpHandler: APP_EV_AUTHENTICATE_DONE
*Mar 11 03:15:57.851: //-1//TCL2:HN34330144:/TclInterpDriver:
*Mar 11 03:15:57.851: //-1//TCL2:HN34330144:/TclEventPreprocessing:
*Mar 11 03:15:57.851: //-1//TCL2:HN34330144:/TclEventPreprocessing:
*Mar 11 03:15:57.851: TclEventPreprocessing: app_event->e.evAuthenticateDone.status = 0
*Mar 11 03:15:57.851: //-1//TCL2:HN34330144:/TclEventPreprocessing:
*Mar 11 03:15:57.851: TclEventPreprocessing: lastFailureCause = 0
Table 311 describes the significant fields shown in the display.

Table 311 debug voip ivr all Field Descriptions

Field

Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//170/

Identifies the CallEntry ID.

APPL:HN34330144:

Identifies the application.

TCL2:

Identifies the TCL IVR 2 module.

Related Commands

Command

Description

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr applib

Note The debug voip ivr applib command is replaced by the debug voip application core command. See the debug voip application core command for more information.

debug voip ivr callsetup

Note The debug voip ivr callset command is replaced by the debug voip application callset command. See the debug voip application callset command for more information.

debug voip ivr digitcollect

Note The debug voip ivr digitcollect command is replaced by the debug voip application digitcollect command. See the debug voip application digitcollect command for more information.

debug voip ivr dynamic

To display debugging messages for interactive voice response (IVR) dynamic prompt play, use the debug voip ivr dynamic command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr dynamic
no debug voip ivr dynamic
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300 and Cisco AS5800; and on the Cisco MC3810 multiservice access concentrators.

Usage Guidelines

We recommend that you log output from the debug voip ivr dynamic 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 is sample output from the debug voip ivr dynamic command:
Router# debug voip ivr dynamic
ivr dynamic promptplaying debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 02:39:28.007: //-1//DPM :DP12:/pc_mc_createDynamicS: calloc mcDynamicS_t
*Mar 11 02:39:28.007: //-1//DPM :DP12:/pc_mc_addToDynamicS: Doing : 
flash:enter_destination.au
*Mar 11 02:39:28.007: //-1//DPM :DP12:/pc_mc_addToDynamicS: Token : 
flash:enter_destination.au
*Mar 11 02:39:28.007: //-1//MCM :MC2:/mc_getFromUrlName: enter_destination.au on ram
*Mar 11 02:39:28.007: //-1//MCM :MC2:/mc_waitq_delete: nothing to delete
*Mar 11 02:39:28.007: //-1//DPM :LP:DP12:MC2:/dp_mcDQfromURL:
*Mar 11 02:39:28.007: $ $du_get_vpPromptName() OK###
*Mar 11 02:39:28.007: //-1//MCM :MR11:/mc_createDynamicReader:
*Mar 11 02:39:28.011: //118//MSM :/ms_associate: packet_size = 160 timestamp increment = 
160 packet_duration = 20 Coder= 5 vad = 0 
SampleRate = 8000
*Mar 11 02:39:28.011: //118//MSM :/ms_associate: >>ccAssociateStream()
*Mar 11 02:39:28.015: //-1//MCM :MR11:/mc_setup_reader_encaps:
*Mar 11 02:39:28.019: //-1//MCM :MR11:/mc_make_packets_DQ: mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:28.019: //-1//MCM :MR11:/mc_make_packets_DQ: mc_fill_pakList(): 
status_fillpak 1, /                      mcr->thisMcBytesPlay 
9600, mc:638E1FC8 name:enter_destination.au
*Mar 11 02:39:28.019: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:28.019: //118//MSM :/ms_start_play: 1w3d mgdTstart(rf)
*Mar 11 02:39:28.023: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.043: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.063: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.083: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.103: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.123: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.143: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.163: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.183: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.203: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.219: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 11200, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:28.219: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:28.219: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:28.223: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.243: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.263: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.283: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.303: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.323: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.343: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.363: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.383: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.403: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.419: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 12800, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:28.419: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:28.419: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:28.423: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.443: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.463: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.483: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.503: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.523: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.543: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.563: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.583: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.603: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.619: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 14400, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:28.619: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:28.619: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:28.623: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.643: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.663: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.683: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.703: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.723: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.743: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.763: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.783: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.803: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.819: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 16000, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:28.819: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:28.819: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:28.823: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.843: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.863: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.883: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.903: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.923: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.943: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.963: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.983: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.003: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.019: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 17600, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:29.019: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:29.019: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:29.023: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.043: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.063: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.083: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.103: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.123: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.143: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.163: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.183: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.203: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.227: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.231: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 19360, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:29.231: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:29.231: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:29.247: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.267: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.287: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.307: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.327: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.347: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.367: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.387: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.407: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.427: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.431: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 0, 
mcr->thisMcBytesPlay 19360, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:29.431: //-1//MCM :MR11:/mc_make_packets_DQ: count: 50
*Mar 11 02:39:29.431: //-1//MCM :MR11:/mc_make_packets_DQ: count: 50
*Mar 11 02:39:29.431: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:29.447: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.467: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.487: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.507: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.527: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.547: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.567: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.587: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.607: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.627: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.631: //-1//MCM :MR11:/mc_make_packets_DQ: No more on reader
*Mar 11 02:39:29.631: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:29.647: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.667: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.687: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.707: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.727: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.747: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.767: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.787: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.807: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.827: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.831: //-1//MCM :MR11:/mc_make_packets_DQ: No more on reader
*Mar 11 02:39:29.831: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:29.847: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.867: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.887: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.907: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.927: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.947: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.967: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.987: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.007: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.027: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.031: //-1//MCM :MR11:/mc_make_packets_DQ: No more on reader
*Mar 11 02:39:30.031: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:30.047: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.067: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.087: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.107: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.127: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.147: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.167: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.187: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.207: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.227: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.231: //-1//MCM :MR11:/mc_make_packets_DQ: No more on reader
*Mar 11 02:39:30.231: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:30.247: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.267: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.287: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.307: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.327: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.347: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.367: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.387: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.407: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.427: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.431: //-1//MCM :MR11:/mc_make_packets_DQ: No more on reader
*Mar 11 02:39:30.431: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:30.447: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.447: //118//MSM :/ms_process: $w$ intEvent MS_E_STOP_PLAY
*Mar 11 02:39:30.447: //118//MSM :/ms_stop_play: mgdTstop(rf) at 1w3d
*Mar 11 02:39:30.447: //-1//DPM :DP12:/dp_delete_mcDynamicS: >dequeue(mcDynamicQ)
*Mar 11 02:39:30.447: //-1//MCM :MC2:/mc_delete: mc=0x638E1FC8
*Mar 11 02:39:30.447: //-1//MCM :MC2:/mc_delete: refCount=1
*Mar 11 02:39:30.447: //-1//MCM :MC2:/mc_waitq_add: already in the waitq
*Mar 11 02:39:30.447: //-1//MCM :MC2:/mc_delete: prompt_wait=0 prompt_active=0
*Mar 11 02:39:30.447: //-1//DPM :DP12:/dp_delete_mcDynamicS: >free(p_mcDynamicS)
*Mar 11 02:39:30.447: //-1//MCM :MR11:/mc_delete_read: dequeue(pakList)
*Mar 11 02:39:30.447: //118//MSM :/ms_process: >>ms_delete_event(MS_E_int)
Router#
Router#!call answered
Router#
Router#!digits dialed
Router#
Router#!call terminated
Router#
Table 312 describes the significant fields shown in the display.

Table 312 debug voip ivr dynamic Field Descriptions

Field

Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//118/

Identifies the CallEntry ID.

PDM:

Identifies the IVR module name. This is the dynamic prompt module.

MCM:

Identifies the IVR module name. This is the media content module.

Related Commands

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr error

To display debugging messages for interactive voice response (IVR) errors, use the debug voip ivr error command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr error
no debug voip ivr error
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300 and Cisco AS5800; and on the Cisco MC3810 multiservice access concentrators.

Usage Guidelines

Messages appear only if an error has occurred.

We recommend that you log output from the debug voip ivr error 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

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr redirect

Note The debug voip ivr redirect command is replaced by the debug voip application redirect command. See the debug voip application redirect command for more information.

debug voip ivr script

To display debugging messages for interactive voice response (IVR) scripts, use the debug voip ivr script command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr script
no debug voip ivr script
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300 and Cisco AS5800; and on the Cisco MC3810 multiservice access concentrators.

Usage Guidelines

We recommend that you log output from the debug voip ivr script 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 is sample output from the debug voip ivr script command:
Router# debug voip ivr script
ivr script debugging is on
Router#
Router#!call initiated
Router#
Router#!call answered
Router#
*Mar 11 02:50:59.431: //-1//TCL2:HN341BC8B0:/tcl_PutsCmd:
 Unlimited Time
*Mar 11 02:50:59.431:
Router#
*Mar 11 02:51:28.343: //-1//TCL2:HN341C6A88:/tcl_PutsCmd:
 Unlimited Time
*Mar 11 02:51:28.343:
Router#
Router#!digits entered
Router#
Router#!call terminated
Router#
Table 313 describes the significant fields shown in the display.

Table 313 debug voip ivr script Field Descriptions

Field

Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

TCL2:

Identifies the TCL IVR 2 module.

Related Commands

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr settlement

To display debugging messages for interactive voice response (IVR) settlement activities, use the debug voip ivr settlement command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr settlement
no debug voip ivr settlement
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2

This command was introduced.

12.0(4)XH

The settlement keyword was added.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300 and Cisco AS5800; and on the Cisco MC3810 multiservice access concentrators.

Usage Guidelines

Settlement output logs activities related to settlement when a call is processed.

We recommend that you log output from the debug voip ivr settlement 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 is sample output from the debug voip ivr settlement command:
Router # debug voip ivr settlement
ivr settlement activities debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 03:02:20.819: //142//TCL2:/SettlementValidateCall: target=, tokenp=0x0
Router#
Router#!call answered
Router#
*Mar 11 03:02:40.979: //-1//TCL2:HN342689D0:/vtr_lg_cssettlement_time: 
credit_time=uninitialized
Router#
Router#!digits dialed
Router#
Router#!call terminated
Table 314 describes the significant fields shown in the display.

Table 314 debug voip ivr settlement Field Descriptions

Field

Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//142/

Identifies the CallEntry ID.

TCL2:

Identifies the TCL IVR 2 module.

Related Commands

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr states

To display debugging messages that supply information about the current status of the interactive voice response (IVR) script and the different events that occur in that state, use the debug voip ivr states command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr states
no debug voip ivr states
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300 and Cisco AS5800; and on the Cisco MC3810 multiservice access concentrators.

Usage Guidelines

State output supplies information about the current status of the IVR script and the different events that occur in that state.

We recommend that you log output from the debug voip ivr states 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 is sample output from the debug voip ivr states command:
Router# debug voip ivr states 
ivr state transitions debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 02:54:11.539: //-1//TCL2:/TclGetInterp: Script test
*Mar 11 02:54:11.539: //134//TCL2:/TclInterpHandler: CC_EV_CALL_SETUP_IND
*Mar 11 02:54:11.539: //134//TCL2:/TclInterpDriver:
*Mar 11 02:54:11.539: //134//TCL2:/TclEventPreprocessing:
*Mar 11 02:54:11.539: //-1//TCL2:/TclIncomingCallBlock:
*Mar 11 02:54:11.539: //134//TCL2:/MakeTransition: FSM Transtion: ([1 
]CALL_INIT,[28]ev_setup_indication)---([10]act_Set
up)--->([7 ]AUTHENTICATE)
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/TclInterpHandler: APP_EV_AUTHENTICATE_DONE
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/TclInterpDriver:
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/TclEventPreprocessing:
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/TclEventPreprocessing:
*Mar 11 02:54:11.551: TclEventPreprocessing: app_event->e.evAuthenticateDone.status = 0
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/TclEventPreprocessing:
*Mar 11 02:54:11.551: TclEventPreprocessing: lastFailureCause = 0
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/MakeTransition: FSM Transtion: ([7 
]AUTHENTICATE,[81]ev_authenticate_done)-
--([7 ]act_Authenticated)--->([9 ]GETDEST)
*Mar 11 02:54:11.555: //-1//DPM :DP19:/pc_mc_addToDynamicS: (1) flash:enter_destination.au
*Mar 11 02:54:11.555: //-1//MCM :/mc_createFromFileUrl: Getting a media content: 
name=enter_destination.au
    url=flash:enter_destination.au
    load fast, load in background, fetchtimeout=-1
*Mar 11 02:54:11.555: //-1//MSW :GS15:/msw_create: cbf=0x6134CCAC
*Mar 11 02:54:11.555: //-1//MSM :MS29:/ms_create: Iniz ply_timer
*Mar 11 02:54:11.555: //-1//MSW :GS15:/msw_synth_open: mediaStream 0x63AE2790 created
*Mar 11 02:54:11.555: //-1//MSW :GS15:/msw_synth_open: rtspStream 0x633AF070 created,
            status=RTSP_STATUS_SUCCESS, session_id=0x1D (29)
*Mar 11 02:54:11.559: //-1//MSM :MS30:/ms_create: Iniz ply_timer
*Mar 11 02:54:11.559: //-1//MSW :GS15:/msw_recrd_open:
*Mar 11 02:54:11.559: :msw_recrd_open mediaStream 0x638D31CC created
*Mar 11 02:54:11.559: //-1//MSW :GS15:/msw_recrd_open: rtspStream 0x633AF078 created,
            status=RTSP_STATUS_SUCCESS, session_id=0x1E (30)
*Mar 11 02:54:11.559: //-1//MSW :/msw_set_backup_server: server[0] = '',
                     genericStream=0x634505E8
*Mar 11 02:54:11.559: //-1//MSW :/msw_set_backup_server: server[1] = '',
                     genericStream=0x634505E8
*Mar 11 02:54:11.559: //-1//MSW :/msw_associate_call:
*Mar 11 02:54:11.559: msw_associate_call: callID=0x86(134),
                     genericStream=0x634505E8
*Mar 11 02:54:11.559: //134//MSW :/msw_get_stream_state:
*Mar 11 02:54:11.559: msw_get_stream_state: genericStream 0x634505E8 is in state 
MSW_S_IDLE
*Mar 11 02:54:11.559: //134//MSW :/msw_synth_start: current_stream_id=1, content 0x0, 
dynamicS 0x63A5DB80, current_state
=MSW_S_IDLE
*Mar 11 02:54:11.559: //134//MSW :/msu_synth_partial_play: Media Stream URL
*Mar 11 02:54:11.563: //134//MSM :LP:MS29:/ms_associateDone:
*Mar 11 02:54:11.563: //134//MSM :/ms_asDone_buginf: callID=0x86, pVdb=0x63A4D214, 
disposition=0, playFunc=0x6129C58C,
    codec=0x5=g711ulaw, vad=255, mediaType=6, streamAssocID=0
*Mar 11 02:54:11.567: //134//MSM :/ms_associateDone: First Buf Play at 1w3d of 
enter_destination.au
*Mar 11 02:54:11.567: //134//MSM :/ms_associateDone: 1w3d, Tstart(ply: iSndDly 0)
*Mar 11 02:54:11.571: //134//MSM :/ms_handle_stream_timer: >>ms_start_play()
*Mar 11 02:54:11.571: //134//MSM :/ms_start_play: 1w3d mgdTstop(ply)
*Mar 11 02:54:13.999: //134//MSM :/ms_stop_play: mgdTstop at 1w3d (cause MS_STOP_COMPLETE)
*Mar 11 02:54:13.999: //134//MSM :/ms_stop_play: Play Stopped at 1w3d
*Mar 11 02:54:13.999: //134//MSM :/ms_stop_play: calling CBF for stream_id 1
*Mar 11 02:54:13.999: //134//MSW :/msu_synth_ms_play_complete: context=0x634505EC, 
use_dynamic=1, dynamicElement=0x0,
            cause=MS_STOP_COMPLETE, stream_id=1, duration=2436, rate=0
*Mar 11 02:54:13.999: //134//MSW :/msu_call_app: app_cbf=0x6134CCAC
        Event = MSW_EV_SYNTHESIZER(1), Context 0x63A741B4, Type    
MSW_SYNTH_TYPE_SYNTHESIZE(2), Reason  
MSW_SYNTH_REASO
N_GENERIC_SUCCESS(13)
*Mar 11 02:54:13.999: //134//TCL2:/TclInterpHandler: MSW_EV_SYNTHESIZER
*Mar 11 02:54:13.999: //134//TCL2:/TclInterpDriver:
*Mar 11 02:54:14.003: //134//TCL2:/TclEventPreprocessing:
*Mar 11 02:54:14.003: //134//TCL2:/MakeTransition: FSM Transtion: ([9 
]GETDEST,[80]ev_media_done)---([-1]IGNORE)--->([9
]GETDEST)
*Mar 11 02:54:18.891: //-1//TCL2:HN341F1290:/TclInterpHandler: APP_EV_DIGITCOLLECT_DONE
*Mar 11 02:54:18.891: //-1//TCL2:HN341F1290:/TclInterpDriver:
*Mar 11 02:54:18.891: //-1//TCL2:HN341F1290:/TclEventPreprocessing:
*Mar 11 02:54:18.895: //-1//TCL2:HN341F1290:/MakeTransition: FSM Transtion: ([9 
]GETDEST,[88]ev_collectdigits_done)---([
8 ]act_PromptCollect_dest)--->([8 ]PLACECALL)
Router#
Router#!call answered
Router#
*Mar 11 02:54:35.327: //-1//TCL2:HN341F1290:/TclInterpHandler: APP_EV_CALLSETUP_DONE
*Mar 11 02:54:35.327: //-1//TCL2:HN341F1290:/TclInterpDriver:
*Mar 11 02:54:35.327: //-1//TCL2:HN341F1290:/TclEventPreprocessing:
*Mar 11 02:54:35.327: //-1//TCL2:HN341F1290:/MakeTransition: FSM Transtion: ([8 
]PLACECALL,[85]ev_setup_done)---([5 ]act
_CallSetupDone)--->([3 ]CALLACTIVE)
*Mar 11 02:54:35.335: //134//TCL2:/TclInterpHandler: CC_EV_VOICE_MODE_DONE
*Mar 11 02:54:35.335: //134//TCL2:/TclInterpDriver:
*Mar 11 02:54:35.335: //134//TCL2:/TclEventPreprocessing:
*Mar 11 02:54:35.335: //134//TCL2:/MakeTransition: FSM Transtion: ([3 
]CALLACTIVE,[56])---([-1]IGNORE)--->([3 ]CALLACTIV
E)
Router#
Router#!digits dialed
Router#
Router#!call terminated
Router#
*Mar 11 02:57:01.627: //134//TCL2:/TclInterpHandler: CC_EV_CALL_DISCONNECTED
*Mar 11 02:57:01.627: //134//TCL2:/TclInterpDriver:
*Mar 11 02:57:01.627: //134//TCL2:/TclEventPreprocessing:
*Mar 11 02:57:01.631: //134//TCL2:/MakeTransition: FSM Transtion: ([3 
]CALLACTIVE,[15]ev_disconnected)---([1 ]act_Cleanu
p)--->([4 ]CALLDISCONNECT)
*Mar 11 02:57:01.631: //-1//TCL2:HN341F1290:/TclCallProcess: Interp Done
*Mar 11 02:57:01.631: //134//TCL2:/TclInterpCleanup: Terminate TRUE Terminated 
FALSE{HAN[TCL_HAND][NULL    ]    ( LEG[13
4    ][TCL_HAND][LEG_INCCONNECTED(5)][Cause(16)][UC=1 ]CON[19     
][TCL_HAND][CONNECTION_CONFED(2)] [UC=1 
]LEG[137    ][
TCL_HAND][LEG_OUTINIT(6)][Cause(0)][UC=1 ])}
*Mar 11 02:57:01.631: //-1//TCL2:HN341F1290:/TclInterpHandler: CC_EV_CONF_DESTROY_DONE
*Mar 11 02:57:01.631: //134//TCL2:/TclInterpCleaner:
*Mar 11 02:57:01.659: //134//TCL2:/TclInterpHandler: CC_EV_CALL_DISCONNECT_DONE
*Mar 11 02:57:01.659: //134//TCL2:/TclInterpCleaner:
*Mar 11 02:57:01.659: //134//MSW :/msw_destroy:
*Mar 11 02:57:01.659: //-1//MSW :/msw_stop: genericStream=0x634505E8,
               reason=MSW_REASON_DISCONNECTED
*Mar 11 02:57:01.659: //-1//MSW :/msw_synth_stop: genericStream=0x634505E8,
               mediaStream=0x63AE2790, rtspStream=0x633AF070
               reason=MSW_SYNTH_REASON_DISCONNECTED, current_state=MSW_S_IDLE
*Mar 11 02:57:01.663: //134//MSW :/msw_synth_stop: Stream not currently active
*Mar 11 02:57:01.663: //-1//MSW :/msw_recrd_stop: genericStream=0x634505E8,
               mediaStream=0x638D31CC, rtspStream=0x633AF078
               reason=MSW_RECRD_REASON_DISCONNECTED current_state=MSW_S_IDLE
*Mar 11 02:57:01.663: //-1//MSW :/msw_recrd_stop: Stream not currently active
*Mar 11 02:57:01.663: //-1//MSW :/msw_recog_stop:
*Mar 11 02:57:01.663: msw_recog_stop: genericStream=0x634505E8,
               mrcpStream=0x63450B9C
               reason=MSW_RECOG_REASON_DISCONNECTED, current_state=MSW_S_IDLE
*Mar 11 02:57:01.663: //-1//MSW :/msw_synth_stop: genericStream=0x634505E8,
               mediaStream=0x63AE2790, rtspStream=0x633AF070
               reason=MSW_SYNTH_REASON_DISCONNECTED, current_state=MSW_S_IDLE
*Mar 11 02:57:01.663: //134//MSW :/msw_synth_stop: Stream not currently active
*Mar 11 02:57:01.663: //-1//MSW :/msw_recrd_stop: genericStream=0x634505E8,
               mediaStream=0x638D31CC, rtspStream=0x633AF078
               reason=MSW_RECRD_REASON_DISCONNECTED current_state=MSW_S_IDLE
*Mar 11 02:57:01.663: //-1//MSW :/msw_recrd_stop: Stream not currently active
*Mar 11 02:57:01.663: //-1//MSW :/msw_recog_stop:
*Mar 11 02:57:01.667: msw_recog_stop: genericStream=0x634505E8,
               mrcpStream=0x63450B9C
               reason=MSW_RECOG_REASON_DISCONNECTED, current_state=MSW_S_IDLE
*Mar 11 02:57:03.639: //137//TCL2:/TclInterpHandler: CC_EV_CALL_DISCONNECT_DONE
*Mar 11 02:57:03.639: //-1//TCL2:HN341F1290:/TclInterpCleaner:
*Mar 11 02:57:03.639: //-1//TCL2:HN341F1290:/TclCallProcess: Interp Done
*Mar 11 02:57:03.639: //-1//TCL2:HN341F1290:/TclInterpCleanup: Terminate TRUE Terminated 
TRUE{HAN[TCL_HAND][NULL    ]
( )}
*Mar 11 02:57:03.639: //-1//TCL2:HN341F1290:/TclFreeInterp:  {HAN[TCL_HAND][NULL ]   ( )}
Table 315 describes the significant fields shown in the display.

Table 315 debug voip ivr states Field Descriptions

Field

Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//134/

Identifies the CallEntry ID.

PDM:

Identifies the IVR module name. This is the dynamic prompt module.

MCM:

Identifies the IVR module name. This is the media content module.

MSW:

Identifies the IVR module name. This is the media service wrapper.

TCL2

Identifies the TCL IVR 2 module.

Related Commands

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr supplementary-service

Note The debug voip ivr supplementary-service command is replaced by the debug voip application supplementary-service command. See the debug voip application supplementary-service command for more information.

debug voip ivr tclcommands

To display debugging messages for the Toolkit Command Language (TCL) commands used in interactive voice response (IVR) scripts, use the debug voip ivr tclcommands command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr tclcommands
no debug voip ivr tclcommands
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300 and Cisco AS5800; and on the Cisco MC3810 multiservice access concentrators.

Usage Guidelines

We recommend that you log output from the debug voip ivr tclcommands 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 is sample output from the debug voip ivr tclcommands command:
Router# debug voip ivr tclcommands
ivr tcl commands debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 02:58:37.467: //138//TCL2:/tcl_legCmd: leg setupack leg_incoming
*Mar 11 02:58:37.467: //138//TCL2:/tcl_setupAckCmd: setupack leg_incoming
*Mar 11 02:58:37.467: //138//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 02:58:37.467: //138//TCL2:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:37.467: //138//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 02:58:37.467: //138//TCL2:/tcl_legCmd: leg proceeding leg_incoming
*Mar 11 02:58:37.467: //138//TCL2:/tcl_callProceedingCmd: proceeding leg_incoming
*Mar 11 02:58:37.467: //138//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 02:58:37.467: //138//TCL2:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:37.467: //138//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 02:58:37.467: //138//TCL2:/tcl_legCmd: leg connect leg_incoming
*Mar 11 02:58:37.471: //138//TCL2:/tcl_callConnectCmd: connect leg_incoming
*Mar 11 02:58:37.471: //138//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 02:58:37.471: //138//TCL2:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:37.471: //138//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 02:58:37.471: //138//TCL2:/tcl_infotagCmd: infotag get leg_ani
*Mar 11 02:58:37.471: //138//TCL2:/tcl_getInfoCmd: get leg_ani
*Mar 11 02:58:37.471: //138//TCL2:/vtr_lg_incani: argc 2 argindex 2
*Mar 11 02:58:37.471: //138//TCL2:/tcl_aaaCmd: aaa authenticate 300
*Mar 11 02:58:37.471: //138//TCL2:/tcl_AuthenticateCmd: authenticate 300
*Mar 11 02:58:37.471: //138//TCL2:/tcl_AuthenticateCmd: account=300, password=, 
methodList=, av-send=
*Mar 11 02:58:37.479: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get evt_status
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get evt_status
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/vtr_ev_status: argc 2 argindex 2
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get leg_isdid
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get leg_isdid
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/vtr_lg_incdid: argc 2 argindex 2
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get leg_dnis
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get leg_dnis
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/vtr_lg_incdnis: argc 2 argindex 2
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/tcl_legCmd: leg collectdigits leg_incoming 
param1
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/tcl_collectDigitsCmd: collectdigits 
leg_incoming param1
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/vtd_lg_incoming: argc 3
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/tcl_parseCallID_vartag: VARTAG Translation 
Leg Count=1
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/tcl_mediaCmd: media play leg_incoming 
flash:enter_destination.au
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/tcl_mediaPlayCmd: play leg_incoming 
flash:enter_destination.au
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/vtd_lg_incoming: argc 3
*Mar 11 02:58:37.491: //-1//TCL2:HN34232154:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:37.491: //-1//TCL2:HN34232154:/tcl_parseCallID_vartag: VARTAG Translation 
Leg Count=1
Router#
Router#
Router#
*Mar 11 02:58:45.003: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get evt_status
*Mar 11 02:58:45.003: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get evt_status
*Mar 11 02:58:45.003: //-1//TCL2:HN34232154:/vtr_ev_status: argc 2 argindex 2
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get evt_dcdigits
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get evt_dcdigits
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/vtr_ev_dcdigits: argc 2
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/vtr_ev_dcdigits: DCDIGITS [34998]
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/tcl_legCmd: leg setup 34998 callInfo 
leg_incoming
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/tcl_callSetupCmd: setup 34998 callInfo 
leg_incoming
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/vtd_lg_incoming: argc 4
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/tcl_parseCallID_vartag: VARTAG Translation 
Leg Count=1
Router#
Router#!call answered
Router#
*Mar 11 02:58:58.107: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get evt_status
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get evt_status
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/vtr_ev_status: argc 2 argindex 2
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get 
leg_settlement_time leg_outgoing
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get leg_settlement_time 
leg_outgoing
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/vtr_lg_cssettlement_time: argc 3 argindex 2
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/vtd_lg_outgoing: argc 3
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/vtd_lg_outgoing: Legs [141 ]
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/tcl_parseCallID_vartag: VARTAG Translation 
Leg Count=1
Router#
Router#!digits dialed
Router#
Router#!call terminated
Router#
*Mar 11 02:59:28.079: //138//TCL2:/tcl_callCmd: call close
*Mar 11 02:59:28.079: //138//TCL2:/tcl_closeCallCmd: close {HAN[TCL_HAND][NULL    ]     ( 
LEG[138    ][TCL_HAND][LEG_INC
CONNECTED(5)][Cause(16)][UC=1 ]CON[20     ][TCL_HAND][CONNECTION_CONFED(2)] [UC=1 ]LEG[141    
][TCL_HAND][LEG_OUTINIT(6)
][Cause(0)][UC=1 ])}
Table 316 describes the significant fields shown in the display.

Table 316 debug voip ivr tclcommands Field Descriptions

Field

Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//138/

Identifies the CallEntry ID.

TCL2

Identifies the TCL IVR 2 module.

Related Commands

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

voice call debug

Allows configuration of the voice call debug output.

debug voip profile fax

To enable a set of debug commands for fax applications, use the debug voip profile fax command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip profile fax [mail | relay [ application | signaling]]
no debug voip profile fax
Syntax Description

mail

Enables the following set of debugs for an onramp or offramp fax mail call:

•debug csm voice

•debug fax dmsp all

•debug fax fmsp all

•debug fax foip all

•debug fax mmoip aaa all

•debug fax mspi all

•debug fax mta all

•debug isdn q931

•debug voip application all

•debug voip application vxml all

•debug voip ccapi all

•debug voip dsm all

•debug voip dspapi all

•debug voip hpi all

•debug voip ivr all

•debug voip vtsp all

The following debug commands are enabled for access servers with MICA modem cards:

•debug fax fmsp all

•debug fax mmoip aaa

•debug fax mta all

•debug isdn q931

•debug voip application all

•debug voip application vxml all

•debug voip ccapi all

•debug voip dsm all

•debug voip dspapi all

•debug voip hpi all

•debug voip ivr all

•debug voip vtsp all

The following debug options are enabled for access servers with universal port dial feature cards:

•debug fax dmsp all

•debug fax fmsp all

•debug fax foip all

•debug fax mspi all

•debug voip application vxml all

•debug voip ivr all

relay

Enables the debug fax relay t30 all-level-1 and the sets specified by either the application or signaling keyword.

application

Enables the following set of debugs for fax relay applications:

•debug voip application all

•debug voip application vxml all

•debug voip ccapi all

•debug voip dialpeer all

•debug voip ivr all

signaling

Enables the following set of debugs for fax relay signaling:

•debug cch323 all

•debug ccsip error

•debug ccsip messages

•debug cdapi detail

•debug cdapi events

•debug csm voice

•debug gtd error

•debug gtd events

•debug h225 asn1

•debug h225 events

•debug h225 q931

•debug h245 events

•debug h245 asn1

•debug isdn q931

•debug mgcp errors

•debug mgcp events

•debug mgcp media

•debug mgcp packets

•debug mgcp voipcac

•debug rtpspi all

•debug voip ccapi all

•debug voip dsm all

•debug voip dspapi all

•debug voip hpi all

•debug voip rawmsg

•debug voip tsp all

•debug voip vtsp all

Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command was introduced.

Usage Guidelines

The debug voip profile fax command can be used to use a set of debug commands at one time. Because this command generates a large amount of messages, router performance can be affected.

Caution The debug voip profile fax command generates debug messages from many VoIP components. The number of messages can impact the performance of your router. This command should only be used during low traffic periods.

Examples

Output has been omitted due to its large volume.

Related Commands

Command

Description

debug voip profile help

Displays the sets of commands supported by the debug voip profile commands.

debug voip profile modem

Enables a set of debug commands for modem applications.

debug voip profile voice

Enables a set of debug commands for voice.

debug voip profile help

To display the sets of debug commands supported by the debug voip profile commands, use the debug voip profile help command in privileged EXEC mode.

debug voip profile help
Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command was introduced.

Usage Guidelines

The debug voip profile help command displays the sets of debug commands supported by the debug voip profile commands. It does not display any debug output.

Examples

The following is sample output from the debug voip profile help command:
Router# debug voip profile help 
"debug voip profile modem relay signaling" includes:
   debug csm voice
   debug isdn q931
   debug cdapi detail
   debug cdapi events
   debug voip dspapi all
   debug voip hpi all
   debug voip vtsp all
   debug voip tsp all
   debug voip ccapi all
   debug cch323 all
   debug ccsip error
   debug ccsip messages
   debug mgcp errors
   debug mgcp events
   debug mgcp media
   debug mgcp packets
   debug mgcp voipcac
   debug voip dsm all
"debug voip profile voice application" includes:
   debug voip dialpeer all
   debug voip ccapi all
   debug voip ivr all
   debug voip application all
   debug voip application vxml all
"debug voip profile [ voice | modem pass-through ] signaling" includes:
   debug csm voice
   debug isdn q931
   debug cdapi detail
   debug cdapi events
   debug h225 asn1
   debug h225 events
   debug h225 q931
   debug h245 events
   debug h245 asn1
   debug voip dspapi all
   debug voip hpi all
   debug voip vtsp all
   debug voip tsp all
   debug voip ccapi all
   debug cch323 all
   debug rtpspi all
   debug ccsip error
   debug ccsip messages
   debug mgcp errors
   debug mgcp events
   debug mgcp media
   debug mgcp packets
   debug mgcp voipcac
   debug voip rawmsg
   debug gtd error
   debug gtd events
   debug voip dsm all
"debug voip profile fax mail" includes:
   debug csm voice
   debug isdn q931
   debug voip dspapi all
   debug voip hpi all
   debug voip vtsp all
   debug voip ccapi all
   debug voip ivr all
   debug voip application all
   debug voip application vxml all
   debug fmail client
   debug fmail server
   debug fax mta all
   debug fax receive all
   debug fax send all
   debug text-to-fax
   debug tiff reader
   debug tiff writer
   debug fax mmoip aaa
   debug voip dsm all
"debug voip profile fax relay application" includes:
   debug voip dialpeer all
   debug voip ccapi all
   debug voip ivr all
   debug voip application all
   debug voip application vxml all
"debug voip profile fax relay signaling" includes:
   debug csm voice
   debug isdn q931
   debug cdapi detail
   debug cdapi events
   debug h225 asn1
   debug h225 events
   debug h225 q931
   debug h245 events
   debug h245 asn1
   debug voip dspapi all
   debug voip hpi all
   debug voip vtsp all
   debug voip tsp all
   debug voip ccapi all
   debug cch323 all
   debug rtpspi all
   debug ccsip error
   debug ccsip messages
   debug mgcp errors
   debug mgcp events
   debug mgcp media
   debug mgcp packets
   debug mgcp voipcac
   debug voip rawmsg
   debug gtd error
   debug gtd events
Related Commands

Command

Description

debug voip profile fax

Enables a set of debug commands for fax applications.

debug voip profile modem

Enables a set of debug commands for modem applications.

debug voip profile voice

Enables a set of debug commands for voice.

debug voip profile modem

To enable a set of debug commands for modem applications, use the debug voip profile modem command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip profile modem [pass-through signaling | relay signaling]
no debug voip profile modem
Syntax Description

pass-through signaling

Enables the following set of debugs for modem pass-through signaling:

•debug cch323 all

•debug ccsip error all

•debug ccsip messages

•debug cdapi detail

•debug cdapi events

•debug csm voice

•debug gtd error

•debug gtd events

•debug h225 asn1

•debug h225 events

•debug h225 q931

•debug isdn q931

•debug mgsp errors all

•debug mgcp events

•debug mgcp media

•debug mgcp packets

•debug mgcp voipcac

•debug rtpspi all

•debug voip ccapi all

•debug voip dsm all

•debug voip rawmsg

•debug voip tsp all

•debug voip vtsp all

•debug vpm all

relay signaling

Enables the following set of debugs for modem relay signaling:

•debug voip ccapi all

•debug voip vtsp all

•debug cch323 all

•debug ccsip error

•debug ccsip messages all

•debug mgcp all

•debug mgcp events

•debug mgcp media

•debug mgcp packets

•debug mgcp voipcac all

•debug isdn q931

Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command was introduced.

Usage Guidelines

The debug voip profile modem command can be used to use a set of debug commands at one time. Because this command causes a large amount of messages to be generated, router performance can be affected.

Caution The debug voip profile modem command generates debug messages from many VoIP components, which generates a large number of debug messages. The number of messages can affect the performance of your router. This command should only be used during low traffic periods.

Examples

Output has been omitted due to its large volume.

Related Commands

Command

Description

debug voip profile fax

Enables a set of debug commands for fax applications.

debug voip profile help

Displays the sets of commands supported by the debug voip profile commands.

debug voip profile voice

Enables a set of debug commands for voice.

debug voip profile voice

To enable a set of debug commands for voice, use the debug voip profile voice command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip profile voice [application | signaling]
no debug voip profile voice
Syntax Description

application

Enables the following set of debugs for voice applications:

•debug voip applib

•debug voip application vxml all

•debug voip ccapi all

•debug voip ivr all

signaling

Enables the following set of debugs for voice signaling:

•debug cch323 all

•debug ccsip error all

•debug ccsip messages

•debug cdapi detail

•debug cdapi events

•debug csm voice

•debug gtd error

•debug gtd events

•debug h225 asn1

•debug h225 events

•debug h225 q931

•debug isdn q931

•debug mgsp errors all

•debug mgcp events

•debug mgcp media

•debug mgcp packets

•debug mgcp voipcac

•debug rtpspi all

•debug voip ccapi all

•debug voip dsm all

•debug voip rawmsg

•debug voip tsp all

•debug voip vtsp all

•debug vpm all

Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command was introduced.

Usage Guidelines

The debug voip profile voice command can be used to use a set of debug commands at one time. Because this command causes a large amount of messages to be generated, router performance can be affected.

Caution The debug voip profile voice command generates debug messages from many VoIP components, which generates a large number of debug messages. The number of messages can impact the performance of your router. This command should only be used during low traffic periods.

Examples

Output has been omitted due to its large volume.

Related Commands

Command

Description

debug voip profile fax

Enables a set of debug commands for fax applications.

debug voip profile help

Displays the sets of commands supported by the debug voip profile commands.

debug voip profile modem

Enables a set of debug commands for modem applications.

debug voip rawmsg

To display the raw message owner, length, and pointer, use the debug voip rawmsg command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip rawmsg [detail]
no debug voip rawmsg [detail]
Syntax Description

detail

(Optional) Prints the contents of the raw message in hexadecimal.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(6)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300 and Cisco AS5800; and on the Cisco MC3810 multiservice access concentrators.

Usage Guidelines

We recommend that you log output from the debug voip rawmsg 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 is sample output from the debug voip rawmsg command:
Router# debug voip rawmsg
voip rawmsg debugging is on
Router#
*Mar  1 01:16:25.155: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al
loc from 1, Length 18 Body 638E0C5
These debug messages show that a raw message is allocated for this call. The pointer to the memory location for this raw message is 63075164.
*Mar  1 01:16:25.155: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL
OCATED: ptr is 63075164, owner is 1, length is 18, msg is 638E0C54, type is 0, p
rotocol id is 0
The call control API (CCAPI) gets a setup indicator. It has no information about the callid (-1) and GUID (xxxxxxxxxxxx).
*Mar  1 01:16:25.159: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:
*Mar  1 01:16:25.159: Raw Message MaMa is TSP owner is CCAPI, length is 77, ptr
is 63075164, type is 0, protocol id is 2
The SSAPP at this stage knows about the CallEntry ID (30) but not about GUID (xxxxxxxxx) or the dial-peer (-1).
*Mar  1 01:16:25.163: //30/xxxxxxxxxxxx/SSAPP:-1:-1/ssaCallSetupInd:
*Mar  1 01:16:25.163: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2
The SSAPP learns about the GUID (34C457CD802F) and also learns the incoming dial peer (10002).
*Mar  1 01:16:25.163: //30/34C457CD802F/SSAPP:10002:-1/ssaSetupPeer:
*Mar  1 01:16:25.163: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2
The CCAPI gets the call proceeding for CallEntry ID 30. CCAPI still does not have a GUID (xxxxxxxxxxx).
*Mar  1 01:16:25.163: //30/xxxxxxxxxxxx/CCAPI/ccCallProceeding:
A new raw message buffer is created and the previous one is released.
*Mar  1 01:16:25.163: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al
loc from 10, Length 77 Body 0
*Mar  1 01:16:25.167: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL
OCATED: ptr is 630751EC, owner is 10, length is 77, msg is 638E0F0C, type is 0,
protocol id is 0
*Mar  1 01:16:25.167: //30/34C457CD802F/SSAPP:10002:-1/ssaSetupPeer:
*Mar  1 01:16:25.167: ssaSetupPeer: Saved rawmsgpp 630751EC len 77
IAM,
GCI,34c457cd14f911cc802f95f5fabb6b0f?)??p?34999
*Mar  1 01:16:25.167: //30/xxxxxxxxxxxx/CCAPI/ccCallSetupRequest:
*Mar  1 01:16:25.167: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2
*Mar  1 01:16:25.167: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
*Mar  1 01:16:25.167: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2
The SSAPP gets a message indicating the digits were passed along the VoIP call leg to the terminating gateway. The CallEntry ID is 30, GUID is 34C457CD802F and the incoming dial peer is 10002.
*Mar  1 01:16:25.167: //30/34C457CD802F/SSAPP:10002:-1/ssaReportDigitsDone:
The old raw message 63075164 was freed. The new one is 630751EC.
*Mar  1 01:16:25.179: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo:
Router#Raw Message FREED: ptr is 63075164, owner is 3, length is 4D, msg is 638E
0DB0, type is 0, protocol id is 2
CCAPI got a call proceeding on the second call leg (31); it has no information about the GUID (xxxxxxxxx).
*Mar  1 01:16:25.223: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_proceeding:
CCAPI got a call alert on the second call leg (31); still no information about the GUID (xxxxxxxxx).
*Mar  1 01:16:25.227: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_alert:
The alert is sent to the first call leg (30), GUID 34C457CD802F.
*Mar  1 01:16:25.227: //30/34C457CD802F/SSAPP:10002:-1/ssaAlert:
*Mar  1 01:16:25.227: //30/xxxxxxxxxxxx/CCAPI/ccCallAlert:
The call is answered at this point and the CCAPI gets a call connect for the second call 
leg (CallEntry ID is 31; GUID is xxxxxxxxx).
*Mar  1 01:16:40.975: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_connected:
The call connect is sent to the first call leg (30), GUID 34C457CD802F.
*Mar  1 01:16:40.975: //30/34C457CD802F/SSAPP:10002:-1/ssaConnect:
*Mar  1 01:16:40.975: //30/xxxxxxxxxxxx/CCAPI/ccCallConnect:
The current raw message (ptr 630751EC) is released; a new one will be proclaimed when needed.
*Mar  1 01:16:40.975: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo: Raw Message FREE
D: ptr is 630751EC, owner is 10, length is 4D, msg is 638E0F0C, type is 0, 
protocol id is 2
A new raw message (ptr 63075274) is proclaimed.
*Mar  1 01:17:04.007: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al
loc from 1, Length 4 Body 638E1068
*Mar  1 01:17:04.007: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL
OCATED: ptr is 63075274, owner is 1, length is 4, msg is 638E1068, type is 0, protocol id 
is 0
The call terminates now. CCAPI detects a call disconnect from the first call leg (30) with no GUID (xxxxxxxxx).
*Mar  1 01:17:04.007: //30/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnected:
*Mar  1 01:17:04.007: Raw Message MaMa is TSP owner is CCAPI, length is 4, ptr i
s 63075274, type is 0, protocol id is 2
The disconnect is sent to the first call leg (30), GUID (34C457CD802F).
*Mar  1 01:17:04.011: //30/34C457CD802F/SSAPP:10002:14/ssaDisconnected:
*Mar  1 01:17:04.011: Raw Message MaMa is TSP owner is SSAPP, length is 4, ptr i
s 63075274, type is 0, protocol id is 2
The CCAPI disconnects both call legs (incoming 30 and outgoing 31).
*Mar  1 01:17:04.011: //30/xxxxxxxxxxxx/CCAPI/ccCallDisconnect:
*Mar  1 01:17:04.011: //31/xxxxxxxxxxxx/CCAPI/ccCallDisconnect:
*Mar  1 01:17:04.011: Raw Message MaMa is TSP owner is SSAPP, length is 4, ptr i
s 63075274, type is 0, protocol id is 2
The raw message is released.
*Mar  1 01:17:04.015: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo: Raw Message FREE
D: ptr is 63075274, owner is 3, length is 4, msg is 638E1068, type is 0, protocol id is 2
The following example shows output when you use the debug voip rawmsg detail command. This example shows that the CCAPI layer received an indication for call setup. The detailed raw message dumps the hex of the message. This output is used to track down data pointing to different variables within the software modules.
Router# debug voip rawmsg detail
*Mar  6 17:03:24.169://-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo:VoIP Raw Msg Al
loc from 5, Length 0 Body 0
*Mar  6 17:03:24.173://-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:
*Mar  6 17:03:24.173:Raw Message MaMa is CCAPI owner is CCAPI, length is 59, ptr is 
63045C14, type is 0, protocol id is 18
*Mar  6 17:03:24.173:Raw Message is :1C 39 9E 01 00 03 67 74 64 00 00 00 2E 49
 41 4D 2C 0D 0A 47 43 49 2C 35 33 39 61 30 35 39 64 31 39 36 62 31 31 63 63 38 3
9 30 63 39 30 37 65 31 65 31 37 35 61 34 37 0D 0A 0D 0A
Related Commands

Command

Description

debug cdapi

Displays information about the call distributor application programming interface.

debug tsp

Displays information about the telephony service provider.

voice call debug

Allows configuration of the voice call debug output.

debug voip rtcp

To enable debugging for Real-Time Transport Control Protocol (RTCP) packets, use the debug voip rtcp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip rtcp {error | packet | session}
no debug voip rtcp
Syntax Description

error

Prints out a trace for error cases.

packet

Provides debug output for RTCP packets.

session

Provides all session debug information.

Defaults

Debugging for RTCP packets is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)T

This command was introduced.

12.2(11)T

This command was implemented on the Cisco AS5300, Cisco AS5400, and Cisco AS5850.

12.2(15)T

This command was implemented on the Cisco 1751 and Cisco 1760.

Usage Guidelines

When used without a keyword, this command turns on debugging for all events. This command severely impacts performance; use with caution.

Examples

The following is sample output from the debug voip rtcp command:
Router# debug voip rtcp
1w0d: voip_rtcp_create_session: callID=37, dstCallID=36 laddr=172.19.169.85, lp0
1w0d: voip_rtcp_get_cname: cname=0.0.0@172.19.169.85
1w0d: voip_rtcp_send_event: event=EV_NEW
1w0d: voip_rtcp_new: rtcp_interval=1893
Router#
1w0d: voip_rtcp_send_event: event=EV_STATS
1w0d: voip_rtcp_stats_req: rtcp_interval=3448
1w0d: voip_rtcp_stats_req:delay=45 lost_packets=0 rtt=0 
Router#
1w0d: recv:
1w0d: SR: ssrc=0x1272A94D sr_ntp_h=0xAF44E045 sr_ntp_l=0xA6CE39C sr_timestamp=02
1w0d: SDES: ssrc=0x1272A94D name=1 len=19 data=0.0.0@172.19.169.77
1w0d: rtcp_round_trip_delay: ssrc=0x1D86A955
Router#
1w0d: voip_rtcp_send_event: event=EV_STATS
1w0d: voip_rtcp_stats_req: rtcp_interval=6394
1w0d: voip_rtcp_stats_req:delay=40 lost_packets=0 rtt=0 
1w0d: recv:
1w0d: SR: ssrc=0x1272A94D sr_ntp_h=0xAF44E047 sr_ntp_l=0xFFB007F6 sr_timestamp=6
1w0d: SDES: ssrc=0x1272A94D name=1 len=19 data=0.0.0@172.19.169.77
1w0d: rtcp_round_trip_delay: ssrc=0x1D86A955
Router#
1w0d: voip_rtcp_remove_ccb
1w0d: voip_rtcp_send_event: event=EV_DESTROY
1w0d: voip_rtcp_destroy_idle
1w0d: voip_rtcp_close_session
1w0d: Cleaning up sess=62F95F58, sp=19544, dp=17130
debug voip rtp

To enable debugging for Real-Time Transport Protocol (RTP) named event packets, use the debug voip rtp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip rtp {error | session [nse | multicast | conference | dtmf-relay | named-event] | packet remote-ip ipaddress remote-port portnum packetnum | packet callid idnum packetnum}
no debug voip rtp
Syntax Description

error

Prints out a trace for error cases.

session

Provides all session debug information. If used with a keyword, supplies more specific debug information according to the keywords used.

nse

(Optional) Provides debug information for named signaling events (NSEs).

multicast

(Optional) Provides debug information for multicast packets.

conference

(Optional) Provides debug information for conference packets.

dtmf-relay

(Optional) Provides debug information for dual-tone multifrequency (DTMF) packets.

named-event

(Optional) Provides debug information for named telephony event (NTE) packets.

packet remote-ip ipaddress remote-port portnum packetnum

Provides debug information for a remote IP address and port number. Using the packetnum argument specifies the number of packets to trace so that the display is not flooded.

packet callid idnum packetnum

Provides debug information for a specific call ID number (obtained by using the show voip rtp connections command). Using the packetnum argument specifies the number of packets to trace so that the display is not flooded.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XB

This command was introduced.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T.

12.2(11)T

This command was implemented on the Cisco AS5300, Cisco AS5400, and Cisco AS5850.

12.2(15)T

This command was implemented on the Cisco 1751 and Cisco 1760.

Usage Guidelines

This command severely impacts performance and should be used only for single-call debug capture. We do not recommend using this command when using fax relay because it can adversely affect fax relay.

Examples

The following example shows debugging output for the debug voip rtp session named-event command. The example is for a gateway that sends digits 1, 2, 3, then receives digits 9,8,7. The payload type, event ID, and additional packet payload are shown in each log.

The first three packets indicate the start of the tone (initial packet and two redundant). The last three packets indicate the end of the tone (initial packet and two redundant). The packets in between are refresh packets that are sent every 50 milliseconds (without redundancy).
Router# debug voip rtp session named-event
00:09:29:          Pt:99     Evt:1       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:03 01 90  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:03 03 20  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:03 04 B0  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:83 04 C8  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:83 04 C8  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:83 04 C8  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 01 90  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 03 20  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 04 B0  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:83 05 18  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:83 05 18  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:83 05 18  <<<Rcv>
00:09:29:          Pt:99     Evt:3       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:3       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:3       Pkt:03 00 00  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:03 01 90  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:03 03 20  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:03 04 B0  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:03 06 40  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:83 06 80  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:83 06 80  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:83 06 80  <<<Rcv>
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 01 90
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 03 20
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 04 B0
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 06 40
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:82 06 58
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:82 06 58
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:82 06 58
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 01 90
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 03 20
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 04 B0
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 06 40
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:82 06 90
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:82 06 90
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:82 06 90
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 01 90
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 03 20
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 04 B0
00:09:32:  <Snd>>> Pt:99     Evt:7       Pkt:02 06 40
00:09:32:  <Snd>>> Pt:99     Evt:7       Pkt:82 06 58
00:09:32:  <Snd>>> Pt:99     Evt:7       Pkt:82 06 58
00:09:32:  <Snd>>> Pt:99     Evt:7       Pkt:82 06 58
debug voip settlement all

To enable debugging in all settlement areas, use the debug voip settlement all command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip settlement all [enter | error | exit | misc | network | security | transaction]
no debug voip settlement all [enter | error | exit | misc | network | security | transaction]
Syntax Description

enter

(Optional) Displays all entrances.

error

(Optional) Displays information only if an error occurs.

exit

(Optional) Displays all exits.

misc

(Optional) Displays the details on the code flow of each transaction.

network

(Optional) Displays network connectivity data.

security

(Optional) Displays security and encryption errors.

transaction

(Optional) Displays transaction information.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XH1

This command was introduced.

Usage Guidelines

The debug voip settlement all command enables the following debug settlement commands:

•debug voip settlement enter

•debug voip settlement error

•debug voip settlement exit

•debug voip settlement misc

•debug voip settlement network

•debug voip settlement security

•debug voip settlement transaction

debug voip settlement enter

To show all the settlement function entrances, enter the debug voip settlement enter command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip settlement enter
no debug voip settlement enter
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XH1

This command was introduced.

Examples

The following is sample output from the debug voip settlement enter command:
Router# debug voip settlement enter 
00:43:40:OSP:ENTER:OSPPMimeMessageCreate()
00:43:40:OSP:ENTER:OSPPMimeMessageInit()
00:43:40:OSP:ENTER:OSPPMimeMessageSetContentAndLength()
00:43:40:OSP:ENTER:OSPPMimeMessageBuild()
00:43:40:OSP:ENTER:OSPPMimeDataFree()
00:43:40:OSP:ENTER:OSPPMimePartFree()
00:43:40:OSP:ENTER:OSPPMimePartFree()
00:43:40:OSP:ENTER:OSPPMsgInfoAssignRequestMsg()
00:43:40:OSP:ENTER:osppHttpSelectConnection
00:43:40:OSP:ENTER:OSPPSockCheckServicePoint() ospvConnected = <1>
00:43:40:OSP:ENTER:OSPPSockWaitTillReady()
00:43:40:OSP:ENTER:osppHttpBuildMsg()
00:43:40:OSP:ENTER:OSPPSSLSessionWrite()
00:43:40:OSP:ENTER:OSPPSockWrite()
00:43:40:OSP:ENTER:OSPPSockWaitTillReady() 
debug voip settlement error

To show all the settlement errors, enter the debug voip settlement error command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip settlement error
no debug voip settlement error
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XH1

This command was introduced.

Examples

The following is sample output from the debug voip settlement error command:
Router# debug voip settlement error
00:45:50:OSP:OSPPSockProcessRequest:http recv init header failed
00:45:50:OSP:osppHttpSetupAndMonitor:attempt#0 on http=0x6141A514, limit=1 error=14310
Usage Guidelines

Error Code Definitions
-1:OSP internal software error.           
16:A bad service was chosen.
17:An invalid parameter was passed to OSP.
9010:Attempted to access an invalid pointer. 
9020:A time related error occurred.
10010:OSP provider module failed initialization.
10020:OSP provider tried to access a NULL pointer.
10030:OSP provider could not fine transaction collection.
10040:OSP provider failed to obtain provider space.
10050:OSP provider tried to access an invalid handle.
10060:OSP provider has reached the maximum number of providers.
11010:OSP transaction tried to delete a transaction which was not allowed.
11020:OSP transaction tried a transaction which does not exist.
11030:OSP transaction tried to start a transaction, but data had already been delivered.
11040:OSP transaction could not identify the response given.
11050:OSP transaction failed to obtain transaction space.
11060:OSP transaction failed (possibly ran out) to allocate memory.
11070:OSP transaction tried to perform a transaction which is not allowed.
11080:OSP transaction found no more responses.
11090:OSP transaction could not find a specified value.
11100:OSP transaction did not have enough space to copy.
11110:OSP transaction - call id did not match destination.
11120:OSP transaction encountered an invalid entry.
11130:OSP transaction tried to use a token too soon.
11140:OSP transaction tried to use a token too late.
11150:OSP transaction - source is invalid.
11160:OSP transaction - destination is invalid.
11170:OSP transaction - calling number is invalid.
11180:OSP transaction - called number is invalid.
11190:OSP transaction - call id is invalid.
11200:OSP transaction - authentication id is invalid.
11210:OSP transaction - call id was not found
11220:OSP transaction - The IDS of the called number was invalid.
11230:OSP transaction - function not implemented.
11240:OSP transaction tried to access an invalid handle.
11250:OSP transaction returned an invalid return code.
11260:OSP transaction reported an invalid status code.
11270:OSP transaction encountered an invalid token.
11280:OSP transaction reported a status which could not be identified.
11290:OSP transaction in now valid after it was not found.
11300:OSP transaction could not find the specified destination.
11310:OSP transaction is valid until not found.
11320:OSP transaction - invalid signaling address.
11330:OSP transaction could not find the ID of the transmitter.
11340:OSP transaction could not find the source number.
11350:OSP transaction could not find the destination number.
11360:OSP transaction could not find the token.
11370:OSP transaction could not find the list.
11380:OSP transaction was not allowed to accumulate.
11390:OSP transaction - transaction usage was already reported.
11400:OSP transaction could not find statistics.
11410:OSP transaction failed to create new statistics.
11420:OSP transaction made an invalid calculation.
11430:OSP transaction was not allowed to get the destination.
11440:OSP transaction could not fine the authorization request.
11450:OSP transaction - invalid transmitter ID.
11460:OSP transaction could not find any data.
11470:OSP transaction found no new authorization requests.
12010:OSP security did not have enough space to copy.
12020:OSP security received and invalid argument.
12030:OSP security could not find the private key.
12040:OSP security encountered an un-implemented function.
12050:OSP security ran out of memory.
12060:OSP security received an invalid signal.
12065:OSP security could not initialize the SSL database.
12070:OSP security could not find space for the certificate.
12080:OSP security has no local certificate info defined.
12090:OSP security encountered a zero length certificate.
12100:OSP security encountered a certificate that is too big.
12110:OSP security encountered an invalid certificate.
12120:OSP security encountered a NULL certificate.
12130:OSP security has too many certificates.
12140:OSP security has no storage provided.
12150:OSP security has no private key.
12160:OSP security encountered an invalid context.
12170:OSP security was unable to allocate space.
12180:OSP security - CA certificates do not match.
12190:OSP security found no authority certificates
12200:OSP security - CA certificate index overflow.
13010:OSP error message - failed to allocate memory.
13110:OSP MIME error - buffer is too small.
13115:OSP MIME error - failed to allocate memory.
13120:OSP MIME error - could not find variable.
13125:OSP MIME error - no input was found.
13130:OSP MIME error - invalid argument.
13135:OSP MIME error - no more space.
13140:OSP MIME error - received an invalid type.
13145:OSP MIME error - received an invalid subtype.
13150:OSP MIME error - could not find the specified protocol.
13155:OSP MIME error - could not find MICALG.
13160:OSP MIME error - boundary was not found.
13165:OSP MIME error - content type was not found.
13170:OSP MIME error - message parts were not found.
13301:OSP XML error - received incomplete XML data.
13302:OSP XML error - bad encoding of XML data.
13303:OSP XML error - bad entity in XML data.
13304:OSP XML error - bad name in XML data.
13305:OSP XML error - bad tag in XML data.
13306:OSP XML error - bad attribute in XML data.
13307:OSP XML error - bad CID encoding in XML data.
13308:OSP XML error - bad element found in XML data.
13309:OSP XML error - no element found in XML data.
13310:OSP XML error - no attribute found in XML data.
13311:OSP XML error - OSP received invalid arguments.
13312:OSP XML error - failed to create a new buffer.
13313:OSP XML error - failed to get the size of a buffer.
13314:OSP XML error - failed to send the buffer.
13315:OSP XML error - failed to read a block from the buffer.
13316:OSP XML error - failed to allocate memory.
13317:OSP XML error - could not find the parent.
13318:OSP XML error - could not find the child.
13319:OSP XML error - data type not found in XML data.
13320:OSP XML error - failed to write a clock to the buffer.
13410:OSP data error - no call id preset.
13415:OSP data error - no token present.
13420:OSP data error - bad number presented.
13425:OSP data error - no destination found.
13430:OSP data error - no usage indicator present.
13435:OSP data error - no status present.
13440:OSP data error - no usage configured.
13445:OSP data error - no authentication indicator.
13450:OSP data error - no authentication request.
13455:OSP data error - no authentication response.
13460:OSP data error - no authentication configuration.
13465:OSP data error - no re-authentication request.
13470:OSP data error - no re-authentication response.
13475:OSP data error - invalid data type present.
13480:OSP data error - no usage information available.
13485:OSP data error - no token info present.
13490:OSP data error - invalid data present.
13500:OSP data error - no alternative info present.
13510:OSP data error - no statistics available.
13520:OSP data error - no delay present.
13610:OSP certificate error - memory allocation failed.
14010:OSP communications error - invalid communication size.
14020:OSP communications error - bad communication value.
14030:OSP communications error - parser error.
14040:OSP communications error - no more memory available.
14050:OSP communications error - communication channel currently in use.
14060:OSP communications error - invalid argument passed.
14070:OSP communications error - no service points present.
14080:OSP communications error - no service points available.
14085:OSP communications error - thread initialization failed.
14086:OSP communications error - communications is shutdown.
14110:OSP message queue error - no more memory available.
14120:OSP message queue error - failed to add a request.
14130:OSP message queue error - no event queue present.
14140:OSP message queue error - invalid arguments passed.
14210:OSP HTTP error - 100 - bad header.
14220:OSP HTTP error - 200 - bad header.
14221:OSP HTTP error - 400 - bad request.
14222:OSP HTTP error - bas service port present.
14223:OSP HTTP error - failed to add a request.
14230:OSP HTTP error - invalid queue present.
14240:OSP HTTP error - bad message received.
14250:OSP HTTP error - invalid argument passed.
14260:OSP HTTP error - memory allocation failed.
14270:OSP HTTP error - failed to create a new connection.
14280:OSP HTTP error - server error.
14290:OSP HTTP error - HTTP server is shutdown.
14292:OSP HTTP error - failed to create a new SSL connection.
14295:OSP HTTP error - failed to create a new SSL context.
14297:OSP HTTP error - service unavailable.
14300:OSP socket error - socket select failed.
14310:OSP socket error - socket receive failed.
14315:OSP socket error - socket send failed.
14320:OSP socket error - failed to allocate memory for the receive buffer.
14320:OSP socket error - socket reset.
14330:OSP socket error - failed to create the socket.
14340:OSP socket error - failed to close the socket.
14350:OSP socket error - failed to connect the socket.
14360:OSP socket error - failed to block I/O on the socket.
14370:OSP socket error - failed to disable nagle on the socket.
14400:OSP SSL error - failed to allocate memory.
14410:OSP SSL error - failed to initialize the context.
14420:OSP SSL error - failed to retrieve the version.
14430:OSP SSL error - failed to initialize the session.
14440:OSP SSL error - failed to attach the socket.
14450:OSP SSL error - handshake failed.
14460:OSP SSL error - failed to close SSL.
14470:OSP SSL error - failed to read from SSL.
14480:OSP SSL error - failed to write to SSL.
14490:OSP SSL error - could not get certificate.
14495:OSP SSL error - no root certificate found.
14496:OSP SSL error - failed to set the private key.
14497:OSP SSL error - failed to parse the private key.
14498:OSP SSL error - failed to add certificates.
14499:OSP SSL error - failed to add DN.
15410:OSP utility error - not enough space for copy.
15420:OSP utility error - no time stamp has been created.
15430:OSP utility error - value not found.
15440:OSP utility error - failed to allocate memory.
15450:OSP utility error - invalid argument passed.
15500:OSP buffer error - buffer is empty.
15510:OSP buffer error - buffer is incomplete.
15980:OSP POW error.
15990:OSP Operating system conditional variable timeout.
16010:OSP X509 error - serial number undefined.
16020:OSP X509 error - certificate undefined.
16030:OSP X509 error - invalid context.
16040:OSP X509 error - decoding error.
16050:OSP X509 error - unable to allocate space.
16060:OSP X509 error - invalid data present.
16070:OSP X509 error - certificate has expired.
16080:OSP X509 error - certificate not found.
17010:OSP PKCS1 error - tried to access invalid private key pointer
17020:OSP PKCS1 error - unable to allocate space.
17030:OSP PKCS1 error - invalid context found.
17040:OSP PKCS1 error - tried to access NULL pointer.
17050:OSP PKCS1 error - private key overflow.
18010:OSP PKCS7 error - signer missing.
18020:OSP PKCS7 error - invalid signature found.
18020:OSP PKCS7 error - unable to allocate space.
18030:OSP PKCS7 error - encoding error.
18040:OSP PKCS7 error - tried to access invalid pointer.
18050:OSP PKCS7 error - buffer overflow.
19010:OSP ASN1 error - tried to access NULL pointer.
19020:OSP ASN1 error - invalid element tag found.
19030:OSP ASN1 error - unexpected high tag found.
19040:OSP ASN1 error - invalid primitive tag found.
19050:OSP ASN1 error - unable to allocate space.
19060:OSP ASN1 error - invalid context found.
19070:OSP ASN1 error - invalid time found.
19080:OSP ASN1 error - parser error occurred.
19090:OSP ASN1 error - parsing complete.
19100:OSP ASN1 error - parsing defaulted.
19110:OSP ASN1 error - length overflow.
19120:OSP ASN1 error - unsupported tag found.
19130:OSP ASN1 error - object ID not found.
19140:OSP ASN1 error - object ID mismatch.
19150:OSP ASN1 error - unexpected int base.
19160:OSP ASN1 error - buffer overflow.
19170:OSP ASN1 error - invalid data reference ID found.
19180:OSP ASN1 error - no content value for element found.
19190:OSP ASN1 error - integer overflow.
20010:OSP Crypto error - invalid parameters found.
20020:OSP Crypto error - unable to allocate space.
20030:OSP Crypto error - could not verify signature.
20040:OSP Crypto error - implementation specific error.
20050:OSP Crypto error - tried to access invalid pointer.
20060:OSP Crypto error - not enough space to perform operation.
21010:OSP PKCS8 error - invalid private key pointer found.
21020:OSP PKCS8 error - unable to allocate space for operation.
21030:OSP PKCS8 error - invalid context found.
21040:OSP PKCS8 error - tried to access NULL pointer.
21050:OSP PKCS8 error - private key overflow.
22010:OSP Base 64 error - encode failed.
22020:OSP Base 64 error - decode failed.
22510:OSP audit error - failed to allocate memory.
156010:OSP RSN failure error - no data present.
156020:OSP RSN failure error - data is invalid. 
debug voip settlement exit

To show all the settlement function exits, enter the debug voip settlement exit command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip settlement exit
no debug voip settlement exit
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XH1

This command was introduced.

Examples

The following is sample output from the debug voip settlement exit command:
Router# debug voip settlement exit 
01:21:10:OSP:EXIT :OSPPMimeMessageInit()
01:21:10:OSP:EXIT :OSPPMimeMessageSetContentAndLength()
01:21:10:OSP:EXIT :OSPPMimeMessageBuild()
01:21:10:OSP:EXIT :OSPPMimePartFree()
01:21:10:OSP:EXIT :OSPPMimePartFree()
01:21:10:OSP:EXIT :OSPPMimeDataFree()
01:21:10:OSP:EXIT :OSPPMimeMessageCreate()
01:21:10:OSP:EXIT :OSPPMsgInfoAssignRequestMsg()
01:21:10:OSP:EXIT :osppHttpSelectConnection
01:21:10:OSP:EXIT :OSPPSockCheckServicePoint() isconnected(1)
01:21:10:OSP:EXIT :osppHttpBuildMsg()
01:21:10:OSP:EXIT :OSPPSockWrite() (0)
01:21:10:OSP:EXIT :OSPPSSLSessionWrite() (0)
01:21:10:OSP:EXIT :OSPPSSLSessionRead() (0)
01:21:10:OSP:EXIT :OSPPSSLSessionRead() (0)
01:21:10:OSP:EXIT :OSPPHttpParseHeader
01:21:10:OSP:EXIT :OSPPHttpParseHeader
01:21:10:OSP:EXIT :OSPPSSLSessionRead() (0)
01:21:10:OSP:EXIT :OSPPUtilMemCaseCmp()
debug voip settlement misc

To show the details on the code flow of each settlement transaction, enter the debug voip settlement misc command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip settlement misc
no debug voip settlement misc
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XH1

This command was introduced.

Examples

The following is sample output from the debug voip settlement misc command:
Router# debug voip settlement misc 
00:52:03:OSP:osp_authorize:callp=0x6142770C
00:52:03:OSP:OSPPTransactionRequestNew:ospvTrans=0x614278A8
00:52:03:OSP:osppCommMonitor:major:minor=(0x2:0x1)
00:52:03:OSP:HTTP connection:reused
00:52:03:OSP:osppHttpSetupAndMonitor:HTTP=0x6141A514, QUEUE_EVENT from eventQ=0x6141A87C, 
comm=0x613F16C4, msginfo=0x6142792C
00:52:03:OSP:osppHttpSetupAndMonitor:connected = <TRUE>
00:52:03:OSP:osppHttpSetupAndMonitor:HTTP=0x6141A514, build msginfo=0x6142792C, trans=0x2
00:52:04:OSP:osppHttpSetupAndMonitor:HTTP=0x6141A514, msg built and sent:error=0, 
msginfo=0x6142792C
00:52:04:OSP:osppHttpSetupAndMonitor:monitor exit. errorcode=0
00:52:04:OSP:osppHttpSetupAndMonitor:msginfo=0x6142792C, error=0, shutdown=0
00:52:04:OSP:OSPPMsgInfoProcessResponse:msginfo=0x6142792C, err=0, trans=0x614278A8, 
handle=2
00:52:04:OSP:OSPPMsgInfoChangeState:transp=0x614278A8, msgtype=12 current state=2
00:52:04:OSP:OSPPMsgInfoChangeState:transp=0x614278A8, new state=4
00:52:04:OSP:OSPPMsgInfoProcessResponse:msginfo=0x6142792C, context=0x6142770C, error=0
00:52:04:OSP:osp_get_destination:trans_handle=2, get_first=1, callinfop=0x614275E0
00:52:04:OSP:osp_get_destination:callinfop=0x614275E0 get dest=1.14.115.51, 
validafter=1999-01-20T02:04:32Z, validuntil=1999-01-20T02:14:32Z
00:52:04:OSP:osp_parse_destination:dest=1.14.115.51
00:52:04:OSP:osp_get_destination:callinfop=0x614275E0, error=0, ip_addr=1.14.115.51, 
credit=60
00:52:06:OSP:stop_settlement_ccapi_accounting:send report for callid=0x11, transhandle=2
00:52:06:OSP:osp_report_usage:transaction=2, duration=0, lostpkts=0, lostfrs=0, 
lostpktr=0, lostfrr=0
debug voip settlement network

To show all the messages exchanged between a router and a settlement provider, enter the debug voip settlement network command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip settlement network
no debug voip settlement network
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XH1

This command was introduced.

Usage Guidelines

Using the debug voip settlement network command shows messages, in detail, in HTTP and XML formats.

Examples

The following is sample output from the debug voip settlement network command:
Router# debug voip settlement network 
00:47:25:OSP:HTTP connection:reused
00:47:25:OSP:OSPPSockWaitTillReady:HTTPCONN=0x6141A514, fd=0
00:47:25:OSP:OSPPSockWaitTillReady:read=0, timeout=0, select=1
00:47:25:OSP:osppHttpBuildAndSend():http=0x6141A514 sending:
POST /scripts/simulator.dll?handler HTTP/1.1
Host:1.14.115.12
content-type:text/plain
Content-Length:439
Connection:Keep-Alive
Content-Type:text/plain
Content-Length:370
<?xml version="1.0"?><Message messageId="1" random="8896">
<AuthorisationRequest componentId="1">
<Timestamp>
1993-03-01T00:47:25Z</Timestamp>
<CallId>
<![CDATA[12]]></CallId>
<SourceInfo type="e164">
5551111</SourceInfo>
<DestinationInfo type="e164">
5552222</DestinationInfo>
<Service/>
<MaximumDestinations>
3</MaximumDestinations>
</AuthorisationRequest>
</Message>
00:47:25:OSP:OSPPSockWaitTillReady:HTTPCONN=0x6141A514, fd=0
00:47:25:OSP:OSPPSockWaitTillReady:read=0, timeout=1, select=1
00:47:25:OSP:OSPM_SEND:bytes_sent = 577
00:47:25:OSP:OSPPSockProcessRequest:SOCKFD=0, Expecting 100, got
00:47:25:OSP:OSPPSockWaitTillReady:HTTPCONN=0x6141A514, fd=0
00:47:25:OSP:OSPPSockWaitTillReady:read=1, timeout=1, select=1
00:47:25:OSP:OSPPSSLSessionRead() recving 1 bytes:
HTTP/1.1 100 Continue
Server:Microsoft-IIS/4.0
Date:Wed, 20 Jan 1999 02:01:54 GMT
00:47:25:OSP:OSPPSockProcessRequest:SOCKFD=0, Expecting 200, got
00:47:25:OSP:OSPPSockWaitTillReady:HTTPCONN=0x6141A514, fd=0
00:47:25:OSP:OSPPSockWaitTillReady:read=1, timeout=1, select=1
00:47:25:OSP:OSPPSSLSessionRead() recving 1 bytes:
HTTP/1.1 200 OK
Server:Microsoft-IIS/4.0
Date:Wed, 20 Jan 1999 02:01:54 GMT
Connection:Keep-Alive
Content-Type:multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; 
boundary=bar
Content-Length:1689
00:47:25:OSP:OSPPSockProcessRequest:SOCKFD=0, error=0, HTTP response
00:47:25:OSP:OSPPSockWaitTillReady:HTTPCONN=0x6141A514, fd=0
00:47:25:OSP:OSPPSockWaitTillReady:read=1, timeout=1, select=1
00:47:25:OSP:OSPPSSLSessionRead() recving 1689 bytes:
--bar
Content-Type:text/plain
Content-Length:1510
<?xml version="1.0"?><Message messageId="1" random="27285">
<AuthorisationResponse componentId="1">
<Timestamp>
1999-01-20T02:01:54Z</Timestamp>
<Status>
<Description>
success</Description>
<Code>
200</Code>
</Status>
<TransactionId>
101</TransactionId>
<Destination>
<AuthorityURL>
http://www.myauthority.com</AuthorityURL>
<CallId>
<![CDATA[12]]></CallId>
<DestinationInfo type="e164">
5552222</DestinationInfo>
<DestinationSignalAddress>
1.14.115.51</DestinationSignalAddress>
<Token encoding="base64">
PD94bWwgdmVyc2lvbj0xLjA/PjxNZXNzYWdlIG1lc3NhZ2VJZD0iMSIgcmFuZG9tPSIxODM0OSI+PFRva2VuSW5mbz
48U291cmNlSW5mbyB0eXBlPSJlMTY0Ij41NTUxMTExPC9Tb3VyY2VJbmZvPjxEZXN0aW5hdGlvbkluZm8gdHlwZT0i
ZTE2NCI+NTU1MjIyMjwvRGVzdGluYXRpb25JbmZvPjxDYWxsSWQ+PCFbQ0RBVEFbMV1dPjwvQ2FsbElkPjxWYWxpZE
FmdGVyPjE5OTgtMTItMDhUMjA6MDQ6MFo8L1ZhbGlkQWZ0ZXI+PFZhbGlkVW50aWw+MTk5OS0xMi0zMVQyMzo1OTo1
OVo8L1ZhbGlkVW50aWw+PFRyYW5zYWN0aW9uSWQ+MTAxPC9UcmFuc2FjdGlvbklkPjxVc2FnZURldGFpbD48QW1vdW
50PjE0NDAwPC9BbW91bnQ+PEluY3JlbWVudD4xPC9JbmNyZW1lbnQ+PFNlcnZpY2UvPjxVbml0PnM8L1VuaXQ+PC9V
c2FnZURldGFpbD48L1Rva2VuSW5mbz48L01lc3NhZ2U+</Token>
<UsageDetail>
<Amount>
60</Amount>
<Increment>
1</Increment>
<Service/>
<Unit>
s</Unit>
</UsageDetail>
<ValidAfter>
1999-01-20T01:59:54Z</ValidAfter>
<ValidUntil>
1999-01-20T02:09:54Z</ValidUntil>
</Destination>
<transnexus.com:DelayLimit critical="False">
1000</transnexus.com:DelayLimit>
<transnexus.com:DelayPreference critical="False">
1</transnexus.com:DelayPreference>
</AuthorisationResponse>
</Message>
--bar
Content-Type:application/pkcs7-signature
Content-Length:31
This is your response signature
--bar--
debug voip settlement security

To show all the tracing related to security, such as Secure Socket Layer (SSL) or Secure Multipurpose Internet Mail Extensions (S/MIME), enter the debug voip settlement security command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip settlement security
no debug voip settlement security
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XH1

This command was introduced.

Examples

Not available because of security issues.

debug voip settlement ssl

To display information about the Secure Socket Layer (SSL) connection, use the debug voip settlement ssl command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip settlement ssl
no debug voip settlement ssl
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T

This command was introduced.

Usage Guidelines

For complete information about the SSL connection, use the debug voip settlement ssl command if you see one of the following errors generated from the debug voip settlement error command.
14400:OSP SSL error - failed to allocate memory.
14410:OSP SSL error - failed to initialize the context.
14420:OSP SSL error - failed to retrieve the version.
14430:OSP SSL error - failed to initialize the session.
14440:OSP SSL error - failed to attach the socket.
14450:OSP SSL error - handshake failed.
14460:OSP SSL error - failed to close SSL.
14470:OSP SSL error - failed to read from SSL.
14480:OSP SSL error - failed to write to SSL.
14490:OSP SSL error - could not get certificate.
14495:OSP SSL error - no root certificate found.
14496:OSP SSL error - failed to set the private key.
14497:OSP SSL error - failed to parse the private key.
14498:OSP SSL error - failed to add certificates.
14499:OSP SSL error - failed to add DN.
Examples

The following example shows the debug output when the SSL is making a good connection to the Open Settlement Protocol server:
*May 15 11:53:42.871:OSP:
*May 15 11:53:42.871:OSPPSSLConnect:****** SSL HANDSHAKE SUCCEED !!**** retry=2
When the SSL connection is closed, the following message appears:
*May 15 11:57:42.541:OSP:osp_ssl_close:OSPPSSLClose succeed
The following are possible output trace messages:
osp_ssl_callback_add_session:session not found, add it.
osp_ssl_callback_add_session:session found, but not equal, delete old one
osp_ssl_callback_add_session:Copy new session data
osp_ssl_callback_add_session:session found and equal. no add
osp_ssl_callback_get_session:No Session exist
osp_ssl_callback_get_session:Session found, copy to sslref length=756
osp_ssl_callback_delete_session:session not found
These messages do not indicate an error but indicate the result of the operation.

To display actual error messages, enter the debug voip settlement error command.

debug voip settlement transaction

To see all the attributes of the transactions on the settlement gateway, use the debug voip settlement transaction in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip settlement transaction
no debug voip settlement transaction
Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XH1

This command was introduced.

Examples

The following is sample output from the originating gateway:
00:44:54:OSP:OSPPTransactionNew:trans=0, err=0
00:44:54:OSP:osp_authorize:authorizing trans=0, err=0
router>
00:45:05:OSP:stop_settlement_ccapi_accounting:send report for
callid=7, trans
=0, calling=5710868, called=15125551212, curr_Dest=1
00:45:05:OSP:OSPPTransactionDelete:deleting trans=0
The following is sample output from the terminating gateway:
00:44:40:OSP:OSPPTransactionNew:trans=0, err=0
00:44:40:OSP:osp_validate:validated trans=0, error=0, authorised=1
debug voip tsp

To display information about the telephony service provider (TSP), use the debug voip tsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip tsp [all | default | error [call [informational] | software [informational]] | event | function | individual range | inout | rose]
no debug voip tsp
Syntax Description

all

(Optional) Displays all TSP debugging messages.

default

(Optional) Displays TSP inout, error, and event debugging messages. This option also runs if no keywords are added.

error

(Optional) Displays TSP error messages.

call

(Optional) Displays TSP call-related debugs not generated by other TSP debug options.

informational

(Optional) Displays minor errors and major errors. Without the informational keyword, only major errors are displayed.

software

(Optional) Displays software processing errors.

event

(Optional) Displays TSP events.

function

(Optional) Displays TSP functions.

individual

(Optional) Enables individual TSP debugs.

range

For the individual keyword, the range is an integer value from 1 to 68. For specific range values, see Table 317.

inout

(Optional) Displays TSP function entry/exit debugs.

rose

(Optional) Enables the remote operations service element. This debug displays information about ISDN-related elements.

Table 317 TSP Individual Debug Values

Value

TSP Debug Function

1

INDIVIDUAL_TSP_DEBUG_TDM_HAIRPIN_CONNECT_001

2

INDIVIDUAL_TSP_DEBUG_TDM_HAIRPIN_DISCONNECT_002

3

INDIVIDUAL_TSP_DEBUG_CCRAWMSG_ENCAP_003

4

INDIVIDUAL_TSP_DEBUG_CDAPI_FORM_MSG_BASIC_SS_INFO_004

5

INDIVIDUAL_TSP_DEBUG_CDAPI_FORM_MSG_005

6

INDIVIDUAL_TSP_DEBUG_CDAPI_FORM_MSG_006

7

INDIVIDUAL_TSP_DEBUG_CDAPI_SEND_MSG_007

8

INDIVIDUAL_TSP_DEBUG_CDAPI_SEND_MSG_008

9

INDIVIDUAL_TSP_DEBUG_CDAPI_SEND_INFO_MSG_009

10

INDIVIDUAL_TSP_DEBUG_ALLOC_CDB_010

11

INDIVIDUAL_TSP_DEBUG_DEALLOC_CDB_011

12

INDIVIDUAL_TSP_DEBUG_CONNECT_IND_012

13

INDIVIDUAL_TSP_DEBUG_CONNECT_IND_EXIT_013

14

INDIVIDUAL_TSP_DEBUG_CONNECT_IND_EXIT_014

15

INDIVIDUAL_TSP_DEBUG_CONNECT_IND_EXIT_015

16

INDIVIDUAL_TSP_DEBUG_CONNECT_IND_EXIT_016

17

INDIVIDUAL_TSP_DEBUG_CONNECT_IND_EXIT_017

18

INDIVIDUAL_TSP_DEBUG_CDAPI_SETUP_ACK_018

19

INDIVIDUAL_TSP_DEBUG_CDAPI_PROCEEDING_019

20

INDIVIDUAL_TSP_DEBUG_CDAPI_ALERT_020

21

INDIVIDUAL_TSP_DEBUG_CDAPI_CONNECT_021

22

INDIVIDUAL_TSP_DEBUG_CDAPI_INFO_022

23

INDIVIDUAL_TSP_DEBUG_CDAPI_PROGRESS_023

24

INDIVIDUAL_TSP_DEBUG_CDAPI_FACILITY_024

25

INDIVIDUAL_TSP_DEBUG_CDAPI_FACILITY_025

26

INDIVIDUAL_TSP_DEBUG_CDAPI_PRE_CONN_DISC_REQ_026

27

INDIVIDUAL_TSP_DEBUG_CDAPI_DISC_PROG_IND_027

28

INDIVIDUAL_TSP_DEBUG_CDAPI_DISCONNECT_REQ_028

29

INDIVIDUAL_TSP_DEBUG_CDAPI_DISCONNECT_REQ_029

30

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_SS_RESP_030

31

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_INFO_IND_031

32

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_PROCEEDING_032

33

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_ALERT_033

34

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_ALERT_EXIT_034

35

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_ALERT_EXIT_035

36

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_PROGRESS_036

37

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_INFO_037

38

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_CONNECT_038

39

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_CONNECT_CONF_039

40

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_DISC_PROG_IND_040

41

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_PROG_IND_PROGRESS_041

42

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RELEASE_IND_042

43

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RELEASE_IND_EXIT_043

44

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RELEASE_COMP_044

45

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RELEASE_COMP_CLEAR_045

46

INDIVIDUAL_TSP_DEBUG_SETUP_REQ_EXIT_046

47

INDIVIDUAL_TSP_DEBUG_SETUP_REQ_EXIT_047

48

INDIVIDUAL_TSP_DEBUG_SETUP_REQ_EXIT_048

49

INDIVIDUAL_TSP_DEBUG_TSP_SET_TRANSFER_INFO_049

50

INDIVIDUAL_TSP_DEBUG_TSP_CALL_VOICE_CUT_THROUGH_050

51

INDIVIDUAL_TSP_DEBUG_TSP_CALL_VOICE_CUT_THROUGH_051

52

INDIVIDUAL_TSP_DEBUG_TSP_CALL_VOICE_CUT_THROUGH_052

53

INDIVIDUAL_TSP_DEBUG_TSP_CALL_VOICE_CUT_THROUGH_053

54

INDIVIDUAL_TSP_DEBUG_TSP_MAIN_054

55

INDIVIDUAL_TSP_DEBUG_DO_GLOBAL_END_TO_END_DISC_055

56

INDIVIDUAL_TSP_DEBUG_TSP_CDAPI_MSG_DUMP_056

57

INDIVIDUAL_TSP_DEBUG_TSP_COT_TIMER_START_057

58

INDIVIDUAL_TSP_DEBUG_TSP_COT_TIMER_STOP_058

59

INDIVIDUAL_TSP_DEBUG_TSP_COT_RESULT_059

60

INDIVIDUAL_TSP_DEBUG_TSP_COT_DONE_060

61

INDIVIDUAL_TSP_DEBUG_TSP_COT_TIMEOUT_061

62

INDIVIDUAL_TSP_DEBUG_TSP_COT_REQ_062

63

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_COT_SETUP_ACK_063

64

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RCV_COT_MSG_064

65

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RCV_COT_MSG_065

66

INDIVIDUAL_TSP_DEBUG_TSP_CDAPI_PUT_CAUSE_IE_066

67

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_SETUP_ACK_067

68

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RCV_MSG_068

Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug tsp command.

Examples

The following is sample output from the debug voip tsp command:
Router# debug voip tsp 
Apr  4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_voice_call_check:Query#9
   Overlap=FALSE, Called Number=222, Calling Number=4321
*Apr  4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9 
   Peer Search Type=Voice
*Apr  4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9 
   Matched Incoming Dialpeer With=Port, Peer=299
*Apr  4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9 
   DID=TRUE
*Apr  4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9 
   Incoming Dial-peer=SUCCESS
*Apr  4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9 
   Matched Outgoing Dialpeer=221
*Apr  4 2002 14:04:11.034 
UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_voice_call_check:Query#9 
   Call Type=VOICE, Result=ACCEPT
Table 318 describes the significant fields shown in the display.

Table 318 debug voip tsp dialpeer Field Descriptions

Field

Description

//-1/xxxxxxxxxxxx/TSP:():-1/FFFF/
tsp_voice_call_check:

The format of this message is
//callid/GUID/DMSP/function name:

•CallEntry ID is -1. This indicates that a call leg has not been identified.

•GUID is xxxxxxxxxxxx. This indicates that the call has not been specified.

•TSP:():-1/FFFF is the module name and module-specific parameters.

•The tsp_voice_call_check field shows that the accounting for an onramp fax is active.

Called Number=222, Calling Number=4321

Shows the calling and called numbers for the call.

Matched Incoming Dialpeer With=Port, Peer=299

Shows that the incoming dial peer was matched and identifies the dial peer.

DID=TRUE

Indicates that the call is a direct-inward dial (DID) call.

Matched Outgoing Dialpeer=221

Shows that the outgoing dial peer was matched and identifies the dial peer.

Related Commands

Command

Description

debug track

Displays information about the telephony service provider.

debug voip rawmsg

Displays the raw message owner, length, and pointer.

debug voip vtsp

To display information about the voice telephony service provider (VTSP), use the debug voip vtsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip vtsp [all | default | error | event | function | individual range | inout | session | tone]
no debug voip vtsp
Syntax Description

all

(Optional) Displays all VTSP debugging messages.

default

(Optional) Displays VTSP inout, error, and event debugging messages. This option also runs if no keywords are added.

error

(Optional) Displays VTSP error messages.

event

(Optional) Displays VTSP events.

function

(Optional) Displays VTSP functions.

individual

(Optional) Enables individual VTSP debugs.

range

For the individual keyword, the range is an integer value from 1 to 102. For specific range values, see Table 319.

inout

(Optional) Displays VTSP function entry/exit debugs.

session

(Optional) Traces how the router interacts with the digital signal processor (DSP) based on the signaling indications from the signaling stack and requests from the application.

tone

(Optional) Displays the VTSP messages showing the types of tones generated by the Voice over IP (VoIP) gateway.

Table 319 VTSP Individual Debug Values

Value

VTSP Debug Function

1

INDIVIDUAL_VTSP_DEBUG_SETUP_REQ_PEND_DEFER_001

2

INDIVIDUAL_VTSP_DEBUG_SETUP_REQ_WAIT_PEND_SUCCESS_002

3

INDIVIDUAL_VTSP_DEBUG_SETUP_REQ_WAIT_PEND_FAIL_003

4

INDIVIDUAL_VTSP_DEBUG_TDM_HPM_COMPLETE_004

5

INDIVIDUAL_VTSP_DEBUG_TDM_HPM_COMPLETE_EXIT_005

6

INDIVIDUAL_VTSP_DEBUG_TDM_HPM_CHECK_006

7

INDIVIDUAL_VTSP_DEBUG_TDM_HPM_CHECK_EXIT_007

8

INDIVIDUAL_VTSP_DEBUG_GENERATE_DISC_008

9

INDIVIDUAL_VTSP_DEBUG_GENERATE_DISC_EXIT_009

10

INDIVIDUAL_VTSP_DEBUG_SETUP_IND_ACK_010

11

INDIVIDUAL_VTSP_DEBUG_SETUP_IND_ACK_EXIT_011

12

INDIVIDUAL_VTSP_DEBUG_PROCEEDING_012

13

INDIVIDUAL_VTSP_DEBUG_PRE_CON_DISCONNECT_013

14

INDIVIDUAL_VTSP_DEBUG_PRE_CON_DISCONNECT_EXIT_014

15

INDIVIDUAL_VTSP_DEBUG_SET_DIGIT_TIMEOUTS_015

16

INDIVIDUAL_VTSP_DEBUG_CONNECT_016

17

INDIVIDUAL_VTSP_DEBUG_LOOPBACK_017

18

INDIVIDUAL_VTSP_DEBUG_RING_NOAN_TIMER_018

19

INDIVIDUAL_VTSP_DEBUG_ALERT_CONNECT_019

20

INDIVIDUAL_VTSP_DEBUG_PRE_CON_DISC_REL_EXIT_020

21

INDIVIDUAL_VTSP_DEBUG_HOST_DISC_CLEANUP_021

22

INDIVIDUAL_VTSP_DEBUG_HOST_DISC_CLEANUP_EXIT_022

23

INDIVIDUAL_VTSP_DEBUG_DISCONNECT_023

24

INDIVIDUAL_VTSP_DEBUG_DISCONNECT_EXIT_024

25

INDIVIDUAL_VTSP_DEBUG_DISCONNECT_EXIT_025

26

INDIVIDUAL_VTSP_DEBUG_CONNECT_DIAL_026

27

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_DIAL_027

28

INDIVIDUAL_VTSP_DEBUG_PRE_DISC_CAUSE_028

29

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_CONNECT_029

30

INDIVIDUAL_VTSP_DEBUG_SETUP_REQ_PEND_FAIL_030

31

INDIVIDUAL_VTSP_DEBUG_SETUP_REQ_DISC_031

32

INDIVIDUAL_VTSP_DEBUG_RELEASE_TIMEOUT_032

33

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_PROCEEDING_EXIT_033

34

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_PROCEEDING_EXIT_034

35

INDIVIDUAL_VTSP_DEBUG_PEND_RELEASE_IND_035

36

INDIVIDUAL_VTSP_DEBUG_PEND_RELEASE_IND_EXIT_036

37

INDIVIDUAL_VTSP_DEBUG_DISCONNECT_NO_DSP_CHAN_037

38

INDIVIDUAL_VTSP_DEBUG_DISCONNECT_NO_DSP_CHAN_EXIT_038

39

INDIVIDUAL_VTSP_DEBUG_CALL_FEATURE_IND_039

40

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_PROGRESS_040

41

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_ALERT_041

42

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_ALERT_EXIT_042

43

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_FIRST_PROGRESS_043

44

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_FIRST_PROGRESS_EXIT_044

45

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_FIRST_PROGRESS_EXIT_045

46

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_PROG_PROCEEDING_046

47

INDIVIDUAL_VTSP_DEBUG_PROCEEDING_R2_PEND_DIAL_047

48

INDIVIDUAL_VTSP_DEBUG_ALERT_R2_PEND_DIAL_048

49

INDIVIDUAL_VTSP_DEBUG_CONN_R2_PEND_DIAL_049

50

INDIVIDUAL_VTSP_DEBUG_SETUP_R2_PEND_DIAL_050

51

INDIVIDUAL_VTSP_DEBUG_R2_PEND_DIAL_ALL_051

52

INDIVIDUAL_VTSP_DEBUG_INFO_IND_052

53

INDIVIDUAL_VTSP_DEBUG_ALERT_053

54

INDIVIDUAL_VTSP_DEBUG_ALERT_EXIT_054

55

INDIVIDUAL_VTSP_DEBUG_PROGRESS_055

56

INDIVIDUAL_VTSP_DEBUG_DISC_PROG_IND_056

57

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_DISC_PI_IND_057

58

INDIVIDUAL_VTSP_DEBUG_INFO_058

59

INDIVIDUAL_VTSP_DEBUG_FEATURE_059

60

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_ALERT_NO_TIMEOUT_060

61

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_ALERT_NO_TIMEOUT_EXIT_061

62

INDIVIDUAL_VTSP_DEBUG_CALL_FEATURE_ENABLE_062

63

INDIVIDUAL_VTSP_DEBUG_XCCSM_COT_TEST_DONE_063

64

INDIVIDUAL_VTSP_DEBUG_XCCSM_COT_TEST_TIMEOUT_064

65

INDIVIDUAL_VTSP_DEBUG_XCCSM_COT_TEST_065

66

INDIVIDUAL_VTSP_DEBUG_CALL_FEATURE_066

67

INDIVIDUAL_VTSP_DEBUG_TCSM_COT_TEST_DONE_067

68

INDIVIDUAL_VTSP_DEBUG_TCSM_COT_TEST_TIMEOUT_068

69

INDIVIDUAL_VTSP_DEBUG_TCSM_ACT_COT_TEST_069

70

INDIVIDUAL_VTSP_DEBUG_PLAY_BUSY_TIMER_START_070

71

INDIVIDUAL_VTSP_DEBUG_PLAY_BUSY_TIMER_STOP_071

72

INDIVIDUAL_VTSP_DEBUG_RING_NOAN_TIMER_START_072

73

INDIVIDUAL_VTSP_DEBUG_RING_NOAN_TIMER_STOP_073

74

INDIVIDUAL_VTSP_DEBUG_VTSP_TIMER_074

75

INDIVIDUAL_VTSP_DEBUG_VTSP_TIMER_STOP_075

76

INDIVIDUAL_VTSP_DEBUG_VTSP_ALLOCATE_CDB_076

77

INDIVIDUAL_VTSP_DEBUG_VTSP_DO_CALL_SETUP_IND_077

78

INDIVIDUAL_VTSP_DEBUG_VTSP_DO_CALL_SETUP_IND_EXIT_078

79

INDIVIDUAL_VTSP_DEBUG_VTSP_REQUEST_CALL_079

80

INDIVIDUAL_VTSP_DEBUG_VTSP_REQUEST_CALL_EXIT_080

81

INDIVIDUAL_VTSP_DEBUG_VTSP_REALLOC_CDB_081

82

INDIVIDUAL_VTSP_DEBUG_VTSP_OG_CALL_REQ_EXIT_082

83

INDIVIDUAL_VTSP_DEBUG_VTSP_FREE_CDB_083

84

INDIVIDUAL_VTSP_DEBUG_TGRM_DISC_REL_084

85

INDIVIDUAL_VTSP_DEBUG_VTSP_CC_CALL_DISCONNECTED_085

86

INDIVIDUAL_VTSP_DEBUG_SIGO_BDROP_086

87

INDIVIDUAL_VTSP_DEBUG_SIGO_PRE_CON_DISCONNECT_087

88

INDIVIDUAL_VTSP_DEBUG_SIGO_PROCEEDING_088

89

INDIVIDUAL_VTSP_DEBUG_SIGO_GENERATE_DISC_089

90

INDIVIDUAL_VTSP_DEBUG_SIGO_ALERT_090

91

INDIVIDUAL_VTSP_DEBUG_SIGO_ALERT_CONNECT_091

92

INDIVIDUAL_VTSP_DEBUG_SIGO_SETUP_PEND_CONNECT_092

93

INDIVIDUAL_VTSP_DEBUG_DO_SIGO_CALL_SETUP_REQ_093

94

INDIVIDUAL_VTSP_DEBUG_DO_SIGO_CALL_SETUP_REQ_SESSION_094

95

INDIVIDUAL_VTSP_DEBUG_DSM_MEDIA_EVENT_CB_095

96

INDIVIDUAL_VTSP_DEBUG_DSM_PEER_EVENT_CB_096

97

INDIVIDUAL_VTSP_DEBUG_DSM_FEATURE_NOTIFY_CB_097

98

INDIVIDUAL_VTSP_DEBUG_DSM_BRIDGE_CHECK_CB_098

99

INDIVIDUAL_VTSP_DEBUG_DSM_BRIDGE_STATUS_EXIT_099

100

INDIVIDUAL_VTSP_DEBUG_DSM_SET_FAX_FEAT_EXIT_100

101

INDIVIDUAL_VTSP_DEBUG_DS_DO_DIAL_101

102

INDIVIDUAL_VTSP_DEBUG_DS_DIALING_DEFAULT_102

Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug vtsp command.

12.3(14)T

T.38 fax relay call statistics were made available to Call Detail Records (CDRs) through Vendor-Specific Attributes (VSAs) and added to the call log.

Examples

The following examples show output for variations of the debug voip vtsp command:

•debug voip vtsp event on the Terminating Gateway

•debug voip vtsp function on the Originating Gateway

•debug voip vtsp inout on the Originating Gateway

•debug voip vtsp tone on the Originating Gateway

•debug voip vtsp Displaying T.38 Fax Relay Statistics on the Originating Gateway

For these examples, the topology shown in Figure 5 is used.

Figure 5 Network Topology for debug voip vtsp Examples

debug voip vtsp event on the Terminating Gateway
Router# debug voip vtsp event 
voip vtsp event debugging is on
*May  1 20:03:47.703: //-1/xxxxxxxxxxxx/VTSP:(4/0/0):-1:-1:-1/vtsp_process_event:
   [state:INVALID STATE MACHINE, event:E_CC_SETUP_REQ]
At the setup request, the CallEntry ID and GUID are set. The remainder of the output follows the progress of the call.
*May  1 20:03:47.707: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event:
   [state:S_SETUP_REQUEST, event:E_TSP_PROCEEDING]
*May  1 20:03:47.707: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event:
   [state:S_SETUP_REQ_PROC, event:E_TSP_PROGRESS]
*May  1 20:03:49.955: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event:
   [state:S_SETUP_REQ_PROC, event:E_TSP_CONNECT]
*May  1 20:03:49.959: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event:
   [state:S_CONNECT, event:E_CC_FEATURE]
*May  1 20:04:14.851: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event:
   [state:S_CONNECT, event:E_CC_DISCONNECT]
*May  1 20:04:14.855: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event:
   [state:S_WAIT_STATS, event:E_VTSP_DSM_STATS_COMPLETE]
*May  1 20:04:15.759: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event:
   [state:S_WAIT_RELEASE, event:E_TSP_CALL_FEATURE_IND]
*May  1 20:04:15.811: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event:
   [state:S_WAIT_RELEASE, event:E_TSP_CALL_FEATURE_IND]
*May  1 20:04:15.811: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event:
   [state:S_WAIT_RELEASE, event:E_TSP_DISCONNECT_CONF]
*May  1 20:04:15.811: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:-1:-1/vtsp_process_event:
   [state:S_CLOSE_DSPRM, event:E_VTSP_DSM_CLOSE_COMPLETE]
debug voip vtsp function on the Originating Gateway
Router# debug voip vtsp function 
voip vtsp function debugging is on
*Apr 18 21:48:25.671: //-1/xxxxxxxxxxxx/VTSP:(2/1:23):-1:-1:-1/vtsp_do_call_setup_ind:
At the setup request, the CallEntry ID and GUID are set. The call setup functions are shown.
*Apr 18 21:48:25.671: 
//-1/D87794B9802B/VTSP:(2/1:23):0:-1:-1/vtsp_do_normal_call_setup_ind:
*Apr 18 21:48:25.671: //-1/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_indicate_call:
*Apr 18 21:48:25.675: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_insert_cdb:
*Apr 18 21:48:25.675: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_proceeding:
*Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_progress:
*Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_bridge_check_cb:
*Apr 18 21:48:25.687: 
//88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_bridge_check_cb:exit@1066
*Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_bridge_status_cb:
*Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_save_fax_config:
*Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_set_fax_feat_param:
*Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb:
*Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb:
*Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_feature_notify_cb:
*Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_reactivate_ringback:
*Apr 18 21:48:25.687: 
//88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_reactivate_ringback:exit@871
*Apr 18 21:48:27.451: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb:
At this point, the ringback to the caller has occurred and the next event shows a connection.
*Apr 18 21:48:28.635: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_connect:
*Apr 18 21:48:29.003: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb:
*Apr 18 21:48:34.059: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb:
*Apr 18 21:48:36.587: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_generate_disc:
*Apr 18 21:48:36.587: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_cc_call_disconnected:
*Apr 18 21:48:36.587: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_bridge_status_cb:
The next event shows the call disconnect. There are several VTSP functions that follow the call disconnection to release and terminate the call.
*Apr 18 21:48:36.587: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_disconnect:
*Apr 18 21:48:36.587: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_save_fax_config:
*Apr 18 21:48:36.587: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_set_fax_feat_param:
*Apr 18 21:48:36.595: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_dsm_dsp_stats_complete:
*Apr 18 21:48:36.595: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_wrelease_release:
*Apr 18 21:48:36.595: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_do_call_history:
*Apr 18 21:48:36.595: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_closed_cb:
*Apr 18 21:48:36.595: //88/D87794B9802B/VTSP:(2/1:23):0:-1:-1/act_terminate:
*Apr 18 21:48:36.595: //-1/D87794B9802B/VTSP:(2/1:23):0:-1:-1/vtsp_free_cdb:
debug voip vtsp inout on the Originating Gateway
Router# debug voip vtsp inout 
voip vtsp inout debugging is on
*Apr 18 21:48:59.239: //-1/xxxxxxxxxxxx/VTSP:(2/1:23):-1:-1:-1/vtsp_allocate_cdb:
   CDB=0x65289878
*Apr 18 21:48:59.239: //-1/xxxxxxxxxxxx/VTSP:(2/1:23):-1:-1:-1/vtsp_do_call_setup_ind:
   Event=E_TSP_SETUP_IND
   Progress Indication=0, CarrierIDCode=, Info Trans Capability=0, Source Carrier ID=, 
tg_label_flag=0
The following two events show the calling number, called number, and related parameters:
*Apr 18 21:48:59.239: //-1/xxxxxxxxxxxx/VTSP:(2/1:23):-1:-1:-1/vtsp_do_call_setup_ind:
   Calling Number=4085550111, TON=National, NPI=ISDN, Screening=User, Passed, 
Presentation=Allowed
   CLIR=FALSE, CLID Transparent=FALSE, Null Originating Calling Number=FALSE, Calling 
Translated=FALSE
*Apr 18 21:48:59.239: //-1/xxxxxxxxxxxx/VTSP:(2/1:23):-1:-1:-1/vtsp_do_call_setup_ind:
   Called Number=83103, TON=Unknown, NPI=Unknown
*Apr 18 21:48:59.239: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_insert_cdb:
*Apr 18 21:48:59.243: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_proceeding:
   Progress Indication=0
*Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_progress:
   Progress Indication=8
*Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_timer_stop:
   Timer Stop Time=538706
The following event shows fax parameters associated with the call:
*Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_dsm_save_fax_config:
   Fax Relay=DISABLED - 'fax rate disabled' set (dial-peer)
   Primary Fax Protocol=IGNORE_FAX_RELAY, Fallback Fax Protocol=IGNORE_FAX_RELAY
   Fax Parameters Set By=Dialpeer, Peer=3600
*Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb:
   Event=E_DSM_CC_CAPS_IND
*Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb:
   Event=E_DSM_CC_CAPS_ACK
*Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_dsm_feature_notify_cb:
   Feature ID=0, Feature Status=1
The following event shows the call connection:
*Apr 18 21:49:03.779: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_connect:
   Progress Indication=2
*Apr 18 21:49:03.779: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_ring_noan_timer_stop:
   Timer Stop Time=539158
Router#
The following event shows the call disconnect:
*Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_generate_disc:
   Cause Value=16
*Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_ring_noan_timer_stop:
   Timer Stop Time=541374
The following event shows that it was the calling party that initiated the call disconnect:
*Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_set_release_source:
   Release Direction=PSTN, Release Source=Calling Party-PSTN
*Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_timer:
   Timer Start Time=541374, Timer Value=15000(ms)
*Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_generate_disc:
   Return Code=0
*Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_disconnect:
   Cause Value=16, Previous Cause Value=16
*Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_ring_noan_timer_stop:
   Timer Stop Time=541374
*Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_dsm_save_fax_config:
   Fax Relay=DISABLED - 'fax rate disabled' set (dial-peer)
   Primary Fax Protocol=IGNORE_FAX_RELAY, Fallback Fax Protocol=IGNORE_FAX_RELAY
   Fax Parameters Set By=Dialpeer, Peer=3600
*Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_dsm_dsp_stats_complete:
*Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_timer:
   Timer Start Time=541375, Timer Value=60000(ms)
The following two events show the call being released and the timer stopping:
*Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_wrelease_release:
*Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_play_busy_timer_stop:
   Timer Stop Time=541375
*Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_timer_stop:
   Timer Stop Time=541375
*Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:-1:-1/act_terminate:
*Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:-1:-1/vtsp_timer_stop:
   Timer Stop Time=541375
*Apr 18 21:49:25.951: //-1/EC79A754802C/VTSP:(2/1:23):0:-1:-1/vtsp_free_cdb:
   CDB=0x65289878
Router#
debug voip vtsp tone on the Originating Gateway
Router# debug voip vtsp tone 
voip vtsp tone debugging is on
This output shows a wrong number dialed in the two-stage call to see the tone generated by the router.
*Apr 18 21:52:26.595: //98/657C0B9C8030/VTSP:(2/1:23):0:8:4/act_pre_con_disconnect:
   [Number Unobtainable]-Tone Played In Direction [Network]
debug voip vtsp Displaying T.38 Fax Relay Statistics on the Originating Gateway

This output shows the fax relay statistics.
Router# debug voip vtsp 
VTSP:
  debug voip vtsp event is ON (filter is OFF)
  debug voip vtsp error software is ON
  debug voip vtsp error call is ON (filter is OFF)
  debug voip vtsp inout is ON (filter is OFF)
May  7 21:37:35.322 UTC: //-1/xxxxxxxxxxxx/VTSP:(3/1:D):-1:-1:-1/vtsp_allocate_cdb:  
   CDB=0x63088050
May  7 21:37:35.322 UTC: //-1/xxxxxxxxxxxx/VTSP:(3/1:D):-1:-1:-1/vtsp_do_call_setup_ind:  
   Event=E_TSP_SETUP_IND
   Progress Indication=3, CarrierIDCode=, Info Trans Capability=16, Source Carrier ID=, 
tg_label_flag=0
May  7 21:37:35.322 UTC: //-1/xxxxxxxxxxxx/VTSP:(3/1:D):-1:-1:-1/vtsp_do_call_setup_ind:  
   Called Number=41021, TON=National, NPI=ISDN
May  7 21:37:35.326 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/vtsp_timer:  
   Timer Start Time=1019501, Timer Value=180000(ms)
May  7 21:37:35.326 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/vtsp_insert_cdb: 
May  7 21:37:35.326 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_SETUP_IND_PEND, event:E_VTSP_DSM_OPEN_SUCCESS]
May  7 21:37:35.326 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_setup_ind_pend_success: 
May  7 21:37:35.326 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_realloc_cdb:  
   CDB=0x63088050
May  7 21:37:35.326 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_insert_cdb: 
May  7 21:37:35.326 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer:  
   Timer Start Time=1019501, Timer Value=180000(ms)
May  7 21:37:35.330 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_SETUP_INDICATED, event:E_CC_PROCEEDING]
May  7 21:37:35.330 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_proceeding:  
   Progress Indication=0
May  7 21:37:35.330 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop:  
   Timer Stop Time=1019502
May  7 21:37:35.394 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_PROCEEDING, event:E_CC_ALERT]
May  7 21:37:35.394 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_alert:  
   Progress Indication=0, Signal Indication=1, Setup Progress Indication=3
May  7 21:37:35.394 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop:  
   Timer Stop Time=1019508
May  7 21:37:35.398 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_alert:  
   Progress Indication=0, Tone=
May  7 21:37:37.422 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_save_fax_config:  
   Fax Relay=ENABLED
   Primary Fax Protocol=T38_FAX_RELAY, Fallback Fax Protocol=NONE_FAX_RELAY
   Fax Parameters Set By=Dialpeer, Peer=2
May  7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_save_fax_config:  
   LS Red=0, HS Red=0
May  7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_ALERTING, event:E_CC_DO_CAPS_IND]
May  7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb:  
   Event=E_DSM_CC_CAPS_IND
May  7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_ALERTING, event:E_CC_CAPS_IND]
May  7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb:  
   Event=E_DSM_CC_CAPS_ACK
May  7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_ALERTING, event:E_CC_SERVICE_MSG]
May  7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_service_msg_down: 
May  7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop:  
   Timer Stop Time=1019711
May  7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_ALERTING, event:E_CC_CONNECT]
May  7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_alert_connect:  
   Progress Indication=0
May  7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_ring_noan_timer_stop:  
   Timer Stop Time=1019711
May  7 21:37:37.598 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_feature_notify_cb:  
   Feature ID=0, Feature Status=1
May  7 21:37:37.598 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_feature_notify_cb:  
   Feature ID=0, Feature Status=1
May  7 21:37:44.123 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb:  
   Event=E_DSM_CC_MC_LOCAL_DNLD_DONE
May  7 21:37:44.123 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb:  
   Event=E_DSM_CC_SET_FAX_MODE
May  7 21:37:44.123 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb:  
   Event=E_DSM_CC_MC_LOCAL_DNLD_DONE
May  7 21:37:44.123 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb:  
   Event=E_DSM_CC_SET_FAX_MODE
May  7 21:38:02.911 UTC: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x6040A40C 
reading 0x1
May  7 21:38:02.911 UTC: %ALIGN-3-TRACE: -Traceback= 6040A40C 60409198 603F8338 603F85F8 
613EA398 619B369C 619B40BC 613DFEE4
May  7 21:38:02.915 UTC: %ALIGN-3-TRACE: -Traceback= 6040A54C 60409198 603F8338 603F85F8 
613EA398 619B369C 619B40BC 613DFEE4
May  7 21:38:37.483 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_CONNECT, event:E_CC_CAPS_IND]
May  7 21:38:37.483 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb:  
   Event=E_DSM_CC_CAPS_ACK
May  7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_CONNECT, event:E_TSP_DISCONNECT_IND]
May  7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_generate_disc:  
   Cause Value=16
May  7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop:  
   Timer Stop Time=1025735
May  7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_ring_noan_timer_stop:  
   Timer Stop Time=1025735
May  7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_set_release_source:  
   Release Direction=PSTN, Release Source=Calling Party-PSTN
May  7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer:  
   Timer Start Time=1025735, Timer Value=15000(ms)
May  7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_generate_disc:  
   Return Code=0
May  7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_CONNECT, event:E_CC_DISCONNECT]
May  7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_disconnect:  
   Cause Value=16, Previous Cause Value=16
May  7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_ring_noan_timer_stop:  
   Timer Stop Time=1025735
May  7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_save_fax_config:  
   Fax Relay=ENABLED
   Primary Fax Protocol=T38_FAX_RELAY, Fallback Fax Protocol=NONE_FAX_RELAY
   Fax Parameters Set By=Dialpeer, Peer=2
May  7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_save_fax_config:  
   LS Red=0, HS Red=0
May  7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_WAIT_STATS, event:E_VTSP_DSM_STATS_COMPLETE]
May  7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_dsm_dsp_stats_complete: 
May  7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer:  
   Timer Start Time=1025738, Timer Value=60000(ms)
May  7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_WAIT_RELEASE, event:E_TSP_DISCONNECT_CONF]
May  7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_wrelease_release: 
May  7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_play_busy_timer_stop:  
   Timer Stop Time=1025738
May  7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop:  
   Timer Stop Time=1025738
May  7 21:38:37.695 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   [state:S_CLOSE_DSPRM, event:E_VTSP_DSM_STATS_COMPLETE]
May  7 21:38:37.695 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event:  
   Unexpected EVENT [E_VTSP_DSM_STATS_COMPLETE] Received For STATE [S_CLOSE_DSPRM];
   Previous STATE [0.17 ]
May  7 21:38:37.695 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/vtsp_process_event:  
   [state:S_CLOSE_DSPRM, event:E_VTSP_DSM_CLOSE_COMPLETE]
May  7 21:38:37.695 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/act_terminate: 
May  7 21:38:37.695 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/vtsp_timer_stop:  
   Timer Stop Time=1025738
May  7 21:38:37.695 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/vtsp_free_cdb:  
   CDB=0x63088050
Related Commands

Command

Description

debug voip dsm

Displays information about the DSM.

show debug

Displays which debug commands are enabled.

voice call debug

Allows configuration of the voice call debug output.

debug voip xcodemsp

To display debugging information from the Transcoding Media Service Processor and its related applications, use the debug voip xcodemsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip xcodemsp
no debug voip xcodemsp
Syntax Description

This command has no arguments or keywords.

Command Modes
Privileged EXEC
Command History

Release

Modification

12.3(8)T

This command was introduced.

Examples

The following is sample output from the debug voip xcodemsp command:
Router# debug voip xcodemsp 
XCODEMSP debugging is on
Router#
Router#
*Jul  8 18:36:53: xcmsp_call_setup_request: 
*Jul  8 18:36:53: xcmsp_call_setup_request: callID 20, rscID 1 srvcDef.srvc_id 2 
*Jul  8 18:36:53: xcmsp_bridge: 
*Jul  8 18:36:53: xc_add_streams: 
*Jul  8 18:36:53: xc_add_streams: stream id 1 added 
*Jul  8 18:36:53: xc_add_streams: stream id 2 added 
*Jul  8 18:36:53: xcmsp_bridge: 
*Jul  8 18:36:53: xc_add_streams: 
*Jul  8 18:36:53: xc_add_streams: stream id 5 added 
*Jul  8 18:36:53: xc_add_streams: stream id 6 added 
*Jul  8 18:36:53: xc_connect_bridges: 
*Jul  8 18:36:53: xcmsp_dsmp_response    
Router#
Router#
Router# show sccp connections 
sess_id    conn_id    stype mode     codec   ripaddr         rport sport
16777223   16777905   xcode sendrecv g711a   1.4.177.1       16628 18870
16777223   16777921   xcode sendrecv g729ab  1.4.177.5       31318 18146
Total number of active session(s) 1, and connection(s) 2
Router#
*Jul  8 18:37:22: xcmsp_bridge_drop: 
*Jul  8 18:37:22: xcmsp_bridge_drop: deleting stream id 5
*Jul  8 18:37:22: xcmsp_bridge_drop: deleting stream id 6
*Jul  8 18:37:22: xcmsp_dsmp_response
*Jul  8 18:37:22: xcmsp_dsmp_response: DSMP_DISCONNECTED
*Jul  8 18:37:22: xcmsp_bridge_drop: 
*Jul  8 18:37:22: xcmsp_bridge_drop: deleting stream id 1
*Jul  8 18:37:22: xcmsp_bridge_drop: deleting stream id 2 
*Jul  8 18:37:22: xcmsp_call_disconnect: 
debug vpdn

To troubleshoot Layer 2 Forwarding (L2F) or Layer 2 Tunnel Protocol (L2TP) virtual private dialup network (VPDN) tunneling events and infrastructure, use the debug vpdn command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug vpdn {call {event | fsm} | error | event [disconnect] | l2tp-sequencing | l2x-data | l2x-errors | l2x-events | l2x-packets | message | packet [detail | errors] | sss {error | event | fsm}}
no debug vpdn {call {event | fsm} | error | event [disconnect] | l2tp-sequencing | l2x-data | l2x-errors | l2x-events | l2x-packets | message | packet [detail | errors] | sss {error | event | fsm}}
Syntax Description

call event

Displays significant events in the VPDN call manager.

call fsm

Displays significant events in the VPDN call manager finite state machine (fsm).

error

Displays VPDN errors.

event

Displays VPDN events.

disconnect

(Optional) Displays VPDN disconnect events.

l2tp-sequencing

Displays significant events related to L2TP sequence numbers such as mismatches, resend queue flushes, and drops.

l2x-data

Displays errors that occur in data packets.

l2x-errors

Displays errors that occur in protocol-specific conditions.

l2x-events

Displays events resulting from protocol-specific conditions.

l2x-packets

Displays detailed information about control packets in protocol-specific conditions.

message

Displays VPDN interprocess messages.

packet

Displays information about VPDN packets.

detail

(Optional) Displays detailed packet information, including packet dumps.

errors

(Optional) Displays errors that occur in packet processing.

sss error

Displays debug information about VPDN Subscriber Service Switch (SSS) errors.

sss event

Displays debug information about VPDN SSS events.

sss fsm

Displays debug information about the VPDN SSS fsm.

Command Modes

Privileged EXEC

Command History

0S Release

Modification

12.0(23)S

This command was integrated into Cisco IOS Release 12.0(23)S.

S Release

Modification

12.2(22)S

This command was integrated into Cisco IOS Release 12.2(22)S.

T Release

Modification

11.2

This command was introduced.

12.0(5)T

Support was added for L2TP debugging messages. The l2tp-sequencing and errors keywords were added. The l2f-errors, l2f-events, and l2f-packets keywords were changed to l2x-errors, l2x-events, and l2x-packets.

12.2(4)T

Support was added for the message and call {event | fsm} keywords.

12.2(11)T

Support was added for the detail keyword.

12.2(13)T

Support was added for the sss {error | event | fsm} keywords.

Usage Guidelines

Note that the debug vpdn packet and debug vpdn packet detail commands generate several debug operations per packet. Depending on the L2TP traffic pattern, these commands may cause the CPU load to increase to a high level that impacts performance.

Examples

This section contains the following examples:

•Debugging VPDN Events on a NAS—Normal L2F Operations

•Debugging VPDN Events on the Tunnel Server—Normal L2F Operations

•Debugging VPDN Events on the NAS—Normal L2TP Operations

•Debugging VPDN Events on the Tunnel Server—Normal L2TP Operations

•Debugging Protocol-Specific Events on the NAS—Normal L2F Operations

•Debugging Protocol-Specific Events on the Tunnel Server—Normal L2F Operations

•Debugging Errors on the NAS—L2F Error Conditions

•Debugging L2F Control Packets for Complete Information

•Debugging an L2TPv3 Xconnect Session—Normal Operations

Debugging VPDN Events on a NAS—Normal L2F Operations

The network access server (NAS) has the following VPDN configuration:
vpdn-group 1
 request-dialin
  protocol l2f
  domain cisco.com
 initiate-to ip 172.17.33.125
username nas1 password nas1
The following is sample output from the debug vpdn event command on a NAS when an L2F tunnel is brought up and Challenge Handshake Authentication Protocol (CHAP) authentication of the tunnel succeeds:
Router# debug vpdn event
%LINK-3-UPDOWN: Interface Async6, changed state to up
*Mar 2 00:26:05.537: looking for tunnel -- cisco.com --
*Mar 2 00:26:05.545: Async6 VPN Forwarding...
*Mar 2 00:26:05.545: Async6 VPN Bind interface direction=1
*Mar 2 00:26:05.553: Async6 VPN vpn_forward_user user6@cisco.com is forwarded
%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to up
*Mar 2 00:26:06.289: L2F: Chap authentication succeeded for nas1.
The following is sample output from the debug vpdn event command on a NAS when the L2F tunnel is brought down normally:
Router# debug vpdn event
%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to down
%LINK-5-CHANGED: Interface Async6, changed state to reset
*Mar 2 00:27:18.865: Async6 VPN cleanup
*Mar 2 00:27:18.869: Async6 VPN reset
*Mar 2 00:27:18.873: Async6 VPN Unbind interface
%LINK-3-UPDOWN: Interface Async6, changed state to down
Table 320 describes the significant fields shown in the two previous displays. The output describes normal operations when an L2F tunnel is brought up or down on a NAS.

Table 320 debug vpdn event Field Descriptions for the NAS

Field

Description

Asynchronous interface coming up

%LINK-3-UPDOWN: Interface Async6, changed state to up

Asynchronous interface 6 came up.

looking for tunnel -- cisco.com --

Async6 VPN Forwarding...

Domain name is identified.

Async6 VPN Bind interface direction=1

Tunnel is bound to the interface. These are the direction values:

•1—From the NAS to the tunnel server

•2—From the tunnel server to the NAS

Async6 VPN vpn_forward_user user6@cisco.com is forwarded

Tunnel for the specified user and domain name is forwarded.

%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to up

Line protocol is up.

L2F: Chap authentication succeeded for nas1.

Tunnel was authenticated with the tunnel password nas1.

Virtual access interface coming down

%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to down

Normal operation when the virtual access interface is taken down.

Async6 VPN cleanup

Async6 VPN reset

Async6 VPN Unbind interface

Normal cleanup operations performed when the line or virtual access interface goes down.

Debugging VPDN Events on the Tunnel Server—Normal L2F Operations

The tunnel server has the following VPDN configuration, which uses nas1 as the tunnel name and the tunnel authentication name. The tunnel authentication name might be entered in a users file on an authentication, authorization, and accounting (AAA) server and used to define authentication requirements for the tunnel.
vpdn-group 1
 accept-dialin
  protocol l2f
  virtual-template 1
 terminate-from hostname nas1
The following is sample output from the debug vpdn event command on the tunnel server when an L2F tunnel is brought up successfully:
Router# debug vpdn event
L2F: Chap authentication succeeded for nas1.
Virtual-Access3 VPN Virtual interface created for user6@cisco.com
Virtual-Access3 VPN Set to Async interface
Virtual-Access3 VPN Clone from Vtemplate 1 block=1 filterPPP=0
%LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up
Virtual-Access3 VPN Bind interface direction=2
Virtual-Access3 VPN PPP LCP accepted sent & rcv CONFACK
%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to up
The following is sample output from the debug vpdn event command on a tunnel server when an L2F tunnel is brought down normally:
Router# debug vpdn event
%LINK-3-UPDOWN: Interface Virtual-Access3, changed state to down
Virtual-Access3 VPN cleanup
Virtual-Access3 VPN reset
Virtual-Access3 VPN Unbind interface
Virtual-Access3 VPN reset
%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to down
Table 321 describes the fields shown in two previous outputs. The output describes normal operations when an L2F tunnel is brought up or down on a tunnel server.

Table 321 debug vpdn event Field Descriptions for the Tunnel Server

Field

Description

Tunnel coming up

L2F: Chap authentication succeeded for nas1.

PPP CHAP authentication status for the tunnel named nas1.

Virtual-Access3 VPN Virtual interface created for user6@cisco.com

Virtual access interface was set up on the tunnel server for the user user6@cisco.com.

Virtual-Access3 VPN Set to Async interface

Virtual access interface 3 was set to asynchronous for character-by-character transmission.

Virtual-Access3 VPN Clone from Vtemplate 1 block=1 filterPPP=0

Virtual template 1 was applied to virtual access interface 3.

%LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up

Link status is set to up.

Virtual-Access3 VPN Bind interface direction=2

Tunnel is bound to the interface. These are the direction values:

•1—From the NAS to the tunnel server

•2—From the tunnel server to the NAS

Virtual-Access3 VPN PPP LCP accepted sent & rcv CONFACK

PPP link control protocol (LCP) configuration settings (negotiated between the remote client and the NAS) were copied to the tunnel server and acknowledged.

%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to up

Line protocol is up; the line can be used.

Tunnel coming down

%LINK-3-UPDOWN: Interface Virtual-Access3, changed state to down

Virtual access interface is coming down.

Virtual-Access3 VPN cleanup

Virtual-Access3 VPN reset

Virtual-Access3 VPN Unbind interface

Virtual-Access3 VPN reset

Router is performing normal cleanup operations when a virtual access interface used for an L2F tunnel comes down.

%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to down

Line protocol is down for virtual access interface 3; the line cannot be used.

Debugging VPDN Events on the NAS—Normal L2TP Operations

The following is sample output from the debug vpdn event command on the NAS when an L2TP tunnel is brought up successfully:
Router# debug vpdn event
20:19:17: L2TP: I SCCRQ from ts1 tnl 8
20:19:17: L2X: Never heard of ts1
20:19:17: Tnl 7 L2TP: New tunnel created for remote ts1, address 172.21.9.4
20:19:17: Tnl 7 L2TP: Got a challenge in SCCRQ, ts1
20:19:17: Tnl 7 L2TP: Tunnel state change from idle to wait-ctl-reply
20:19:17: Tnl 7 L2TP: Got a Challenge Response in SCCCN from ts1
20:19:17: Tnl 7 L2TP: Tunnel Authentication success
20:19:17: Tnl 7 L2TP: Tunnel state change from wait-ctl-reply to established
20:19:17: Tnl 7 L2TP: SM State established
20:19:17: Tnl/Cl 7/1 L2TP: Session FS enabled
20:19:17: Tnl/Cl 7/1 L2TP: Session state change from idle to wait-for-tunnel
20:19:17: Tnl/Cl 7/1 L2TP: New session created
20:19:17: Tnl/Cl 7/1 L2TP: O ICRP to ts1 8/1
20:19:17: Tnl/Cl 7/1 L2TP: Session state change from wait-for-tunnel to wait-connect
20:19:17: Tnl/Cl 7/1 L2TP: Session state change from wait-connect to established
20:19:17: Vi1 VPDN: Virtual interface created for bum1@cisco.com
20:19:17: Vi1 VPDN: Set to Async interface
20:19:17: Vi1 VPDN: Clone from Vtemplate 1 filterPPP=0 blocking
20:19:18: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up
20:19:18: Vi1 VPDN: Bind interface direction=2
20:19:18: Vi1 VPDN: PPP LCP accepting rcv CONFACK
20:19:19: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up

Debugging VPDN Events on the Tunnel Server—Normal L2TP Operations

The following is sample output from the debug vpdn event command on the tunnel server when an L2TP tunnel is brought up successfully:
Router# debug vpdn event
20:47:33: %LINK-3-UPDOWN: Interface Async7, changed state to up
20:47:35: As7 VPDN: Looking for tunnel -- cisco.com --
20:47:35: As7 VPDN: Get tunnel info for cisco.com with NAS nas1, IP 172.21.9.13
20:47:35: As7 VPDN: Forward to address 172.21.9.13
20:47:35: As7 VPDN: Forwarding...
20:47:35: As7 VPDN: Bind interface direction=1
20:47:35: Tnl/Cl 8/1 L2TP: Session FS enabled
20:47:35: Tnl/Cl 8/1 L2TP: Session state change from idle to wait-for-tunnel
20:47:35: As7 8/1 L2TP: Create session
20:47:35: Tnl 8 L2TP: SM State idle
20:47:35: Tnl 8 L2TP: Tunnel state change from idle to wait-ctl-reply
20:47:35: Tnl 8 L2TP: SM State wait-ctl-reply
20:47:35: As7 VPDN: bum1@cisco.com is forwarded
20:47:35: Tnl 8 L2TP: Got a challenge from remote peer, nas1
20:47:35: Tnl 8 L2TP: Got a response from remote peer, nas1
20:47:35: Tnl 8 L2TP: Tunnel Authentication success
20:47:35: Tnl 8 L2TP: Tunnel state change from wait-ctl-reply to established
20:47:35: Tnl 8 L2TP: SM State established
20:47:35: As7 8/1 L2TP: Session state change from wait-for-tunnel to wait-reply
20:47:35: As7 8/1 L2TP: Session state change from wait-reply to established
20:47:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async7, changed state to up
Debugging Protocol-Specific Events on the NAS—Normal L2F Operations

The following is sample output from the debug vpdn l2x-events command on the NAS when an L2F tunnel is brought up successfully:
Router# debug vpdn l2x-events
%LINK-3-UPDOWN: Interface Async6, changed state to up
*Mar 2 00:41:17.365: L2F Open UDP socket to 172.21.9.26
*Mar 2 00:41:17.385: L2F_CONF received
*Mar 2 00:41:17.389: L2F Removing resend packet (type 1)
*Mar 2 00:41:17.477: L2F_OPEN received
*Mar 2 00:41:17.489: L2F Removing resend packet (type 2)
*Mar 2 00:41:17.493: L2F building nas2gw_mid0
%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to up
*Mar 2 00:41:18.613: L2F_OPEN received
*Mar 2 00:41:18.625: L2F Got a MID management packet
*Mar 2 00:41:18.625: L2F Removing resend packet (type 2)
*Mar 2 00:41:18.629: L2F MID synced NAS/HG Clid=7/15 Mid=1 on Async6
The following is sample output from the debug vpdn l2x-events command on a NAS when an L2F tunnel is brought down normally:
Router# debug vpdn l2x-events
%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to down
%LINK-5-CHANGED: Interface Async6, changed state to reset
*Mar 2 00:42:29.213: L2F_CLOSE received
*Mar 2 00:42:29.217: L2F Destroying mid
*Mar 2 00:42:29.217: L2F Removing resend packet (type 3)
*Mar 2 00:42:29.221: L2F Tunnel is going down!
*Mar 2 00:42:29.221: L2F Initiating tunnel shutdown.
*Mar 2 00:42:29.225: L2F_CLOSE received
*Mar 2 00:42:29.229: L2F_CLOSE received
*Mar 2 00:42:29.229: L2F Got closing for tunnel 
*Mar 2 00:42:29.233: L2F Removing resend packet
*Mar 2 00:42:29.233: L2F Closed tunnel structure
%LINK-3-UPDOWN: Interface Async6, changed state to down
*Mar 2 00:42:31.793: L2F Closed tunnel structure
*Mar 2 00:42:31.793: L2F Deleted inactive tunnel
Table 322 describes the fields shown in the displays.

Table 322 debug vpdn l2x-events Field Descriptions—NAS

Field

Descriptions

Tunnel coming up

%LINK-3-UPDOWN: Interface Async6, changed state to up

Asynchronous interface came up normally.

L2F Open UDP socket to 172.21.9.26

L2F opened a User Datagram Protocol (UDP) socket to the tunnel server IP address.

L2F_CONF received

L2F_CONF signal was received. When sent from the tunnel server to the NAS, an L2F_CONF indicates the tunnel server's recognition of the tunnel creation request.

L2F Removing resend packet (type ...)

Removing the resend packet for the L2F management packet.

There are two resend packets that have different meanings in different states of the tunnel.

L2F_OPEN received

L2F_OPEN management message was received, indicating that the tunnel server accepted the NAS configuration of an L2F tunnel.

L2F building nas2gw_mid0

L2F is building a tunnel between the NAS and the tunnel server, using the Multiplex ID (MID) MID0.

%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to up

Line protocol came up. Indicates whether the software processes that handle the line protocol regard the interface as usable.

L2F_OPEN received

L2F_OPEN management message was received, indicating that the tunnel server accepted the NAS configuration of an L2F tunnel.

L2F Got a MID management packet

MID management packets are used to communicate between the NAS and the tunnel server.

L2F MID synced NAS/HG Clid=7/15 Mid=1 on Async6

L2F synchronized the Client IDs on the NAS and the tunnel server, respectively. A multiplex ID is assigned to identify this connection in the tunnel.

Tunnel coming down

%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to down

Line protocol came down. Indicates whether the software processes that handle the line protocol regard the interface as usable.

%LINK-5-CHANGED: Interface Async6, changed state to reset

Interface was marked as reset.

L2F_CLOSE received

NAS received a request to close the tunnel.

L2F Destroying mid

Connection identified by the MID is being taken down.

L2F Tunnel is going down!

Advisory message about impending tunnel shutdown.

L2F Initiating tunnel shutdown.

Tunnel shutdown has started.

L2F_CLOSE received

NAS received a request to close the tunnel.

L2F Got closing for tunnel

NAS began tunnel closing operations.

%LINK-3-UPDOWN: Interface Async6, changed state to down

Asynchronous interface was taken down.

L2F Closed tunnel structure

NAS closed the tunnel.

L2F Deleted inactive tunnel

Now-inactivated tunnel was deleted.

Debugging Protocol-Specific Events on the Tunnel Server—Normal L2F Operations

The following is sample output from the debug vpdn l2x-events command on a tunnel server when an L2F tunnel is created:
Router# debug vpdn l2x-events
L2F_CONF received
L2F Creating new tunnel for nas1
L2F Got a tunnel named nas1, responding
L2F Open UDP socket to 172.21.9.25
L2F_OPEN received
L2F Removing 