|
|
Table Of Contents
debug voip ivr supplementary-service
debug voip settlement security
debug voip settlement transaction
debug voip ivr
Note
The debug voip ivr command is replaced by the debug voip application command. See the debug voip application command for more information.
debug voip ivr all
Note
debug voip ivr applib
Note
debug voip ivr callsetup
Note
debug voip ivr digitcollect
Note
debug voip ivr dynamic
Note
debug voip ivr error
Note
debug voip ivr redirect
Note
debug voip ivr script
Note
debug voip ivr settlement
Note
debug voip ivr states
Note
debug voip ivr supplementary-service
Note
debug voip ivr tclcommands
Note
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
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
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
Examples
Output has been omitted due to its large volume.
Related Commands
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
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 voicedebug isdn q931debug cdapi detaildebug cdapi eventsdebug voip dspapi alldebug voip hpi alldebug voip vtsp alldebug voip tsp alldebug voip ccapi alldebug cch323 alldebug ccsip errordebug ccsip messagesdebug mgcp errorsdebug mgcp eventsdebug mgcp mediadebug mgcp packetsdebug mgcp voipcacdebug voip dsm all"debug voip profile voice application" includes:debug voip dialpeer alldebug voip ccapi alldebug voip ivr alldebug voip application alldebug voip application vxml all"debug voip profile [ voice | modem pass-through ] signaling" includes:debug csm voicedebug isdn q931debug cdapi detaildebug cdapi eventsdebug h225 asn1debug h225 eventsdebug h225 q931debug h245 eventsdebug h245 asn1debug voip dspapi alldebug voip hpi alldebug voip vtsp alldebug voip tsp alldebug voip ccapi alldebug cch323 alldebug rtpspi alldebug ccsip errordebug ccsip messagesdebug mgcp errorsdebug mgcp eventsdebug mgcp mediadebug mgcp packetsdebug mgcp voipcacdebug voip rawmsgdebug gtd errordebug gtd eventsdebug voip dsm all"debug voip profile fax mail" includes:debug csm voicedebug isdn q931debug voip dspapi alldebug voip hpi alldebug voip vtsp alldebug voip ccapi alldebug voip ivr alldebug voip application alldebug voip application vxml alldebug fmail clientdebug fmail serverdebug fax mta alldebug fax receive alldebug fax send alldebug text-to-faxdebug tiff readerdebug tiff writerdebug fax mmoip aaadebug voip dsm all"debug voip profile fax relay application" includes:debug voip dialpeer alldebug voip ccapi alldebug voip ivr alldebug voip application alldebug voip application vxml all"debug voip profile fax relay signaling" includes:debug csm voicedebug isdn q931debug cdapi detaildebug cdapi eventsdebug h225 asn1debug h225 eventsdebug h225 q931debug h245 eventsdebug h245 asn1debug voip dspapi alldebug voip hpi alldebug voip vtsp alldebug voip tsp alldebug voip ccapi alldebug cch323 alldebug rtpspi alldebug ccsip errordebug ccsip messagesdebug mgcp errorsdebug mgcp eventsdebug mgcp mediadebug mgcp packetsdebug mgcp voipcacdebug voip rawmsgdebug gtd errordebug gtd eventsRelated Commands
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
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
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
Examples
Output has been omitted due to its large volume.
Related Commands
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
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
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
Examples
Output has been omitted due to its large volume.
Related Commands
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
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
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 rawmsgvoip rawmsg debugging is onRouter#*Mar 1 01:16:25.155: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Alloc from 1, Length 18 Body 638E0C5These 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 ALLOCATED: ptr is 63075164, owner is 1, length is 18, msg is 638E0C54, type is 0, protocol id is 0The 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, ptris 63075164, type is 0, protocol id is 2The 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, ptris 63075164, type is 0, protocol id is 2The 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, ptris 63075164, type is 0, protocol id is 2The 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 Alloc from 10, Length 77 Body 0*Mar 1 01:16:25.167: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALLOCATED: 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 77IAM,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, ptris 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, ptris 63075164, type is 0, protocol id is 2The 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 638E0DB0, type is 0, protocol id is 2CCAPI 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 FREED: ptr is 630751EC, owner is 10, length is 4D, msg is 638E0F0C, type is 0,protocol id is 2A new raw message (ptr 63075274) is proclaimed.
*Mar 1 01:17:04.007: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Alloc from 1, Length 4 Body 638E1068*Mar 1 01:17:04.007: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALLOCATED: ptr is 63075274, owner is 1, length is 4, msg is 638E1068, type is 0, protocol id is 0The 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 is 63075274, type is 0, protocol id is 2The 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 is 63075274, type is 0, protocol id is 2The 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 is 63075274, type is 0, protocol id is 2The raw message is released.
*Mar 1 01:17:04.015: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo: Raw Message FREED: ptr is 63075274, owner is 3, length is 4, msg is 638E1068, type is 0, protocol id is 2The 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 Alloc 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 4941 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 39 30 63 39 30 37 65 31 65 31 37 35 61 34 37 0D 0A 0D 0ARelated Commands
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
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 rtcp1w0d: voip_rtcp_create_session: callID=37, dstCallID=36 laddr=172.19.169.85, lp01w0d: voip_rtcp_get_cname: cname=0.0.0@172.19.169.851w0d: voip_rtcp_send_event: event=EV_NEW1w0d: voip_rtcp_new: rtcp_interval=1893Router#1w0d: voip_rtcp_send_event: event=EV_STATS1w0d: voip_rtcp_stats_req: rtcp_interval=34481w0d: voip_rtcp_stats_req:delay=45 lost_packets=0 rtt=0Router#1w0d: recv:1w0d: SR: ssrc=0x1272A94D sr_ntp_h=0xAF44E045 sr_ntp_l=0xA6CE39C sr_timestamp=021w0d: SDES: ssrc=0x1272A94D name=1 len=19 data=0.0.0@172.19.169.771w0d: rtcp_round_trip_delay: ssrc=0x1D86A955Router#1w0d: voip_rtcp_send_event: event=EV_STATS1w0d: voip_rtcp_stats_req: rtcp_interval=63941w0d: voip_rtcp_stats_req:delay=40 lost_packets=0 rtt=01w0d: recv:1w0d: SR: ssrc=0x1272A94D sr_ntp_h=0xAF44E047 sr_ntp_l=0xFFB007F6 sr_timestamp=61w0d: SDES: ssrc=0x1272A94D name=1 len=19 data=0.0.0@172.19.169.771w0d: rtcp_round_trip_delay: ssrc=0x1D86A955Router#1w0d: voip_rtcp_remove_ccb1w0d: voip_rtcp_send_event: event=EV_DESTROY1w0d: voip_rtcp_destroy_idle1w0d: voip_rtcp_close_session1w0d: Cleaning up sess=62F95F58, sp=19544, dp=17130debug 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 [conference | dtmf-relay | event | multicast | named-event [payload-type] | nse | text-relay] | packet [callid id-number packet-number | remote-ip ip-address remote-port port-number packet-number]}
no debug voip rtp
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command severely impacts performance and should be used only for single-call debug capture.
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-event00: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 0000:09:31: <Snd>>> Pt:99 Evt:9 Pkt:02 00 0000:09:31: <Snd>>> Pt:99 Evt:9 Pkt:02 00 0000:09:31: <Snd>>> Pt:99 Evt:9 Pkt:02 01 9000:09:31: <Snd>>> Pt:99 Evt:9 Pkt:02 03 2000:09:31: <Snd>>> Pt:99 Evt:9 Pkt:02 04 B000:09:31: <Snd>>> Pt:99 Evt:9 Pkt:02 06 4000:09:31: <Snd>>> Pt:99 Evt:9 Pkt:82 06 5800:09:31: <Snd>>> Pt:99 Evt:9 Pkt:82 06 5800:09:31: <Snd>>> Pt:99 Evt:9 Pkt:82 06 5800:09:31: <Snd>>> Pt:99 Evt:8 Pkt:02 00 0000:09:31: <Snd>>> Pt:99 Evt:8 Pkt:02 00 0000:09:31: <Snd>>> Pt:99 Evt:8 Pkt:02 00 0000:09:31: <Snd>>> Pt:99 Evt:8 Pkt:02 01 9000:09:31: <Snd>>> Pt:99 Evt:8 Pkt:02 03 2000:09:31: <Snd>>> Pt:99 Evt:8 Pkt:02 04 B000:09:31: <Snd>>> Pt:99 Evt:8 Pkt:02 06 4000:09:31: <Snd>>> Pt:99 Evt:8 Pkt:82 06 9000:09:31: <Snd>>> Pt:99 Evt:8 Pkt:82 06 9000:09:31: <Snd>>> Pt:99 Evt:8 Pkt:82 06 9000:09:31: <Snd>>> Pt:99 Evt:7 Pkt:02 00 0000:09:31: <Snd>>> Pt:99 Evt:7 Pkt:02 00 0000:09:31: <Snd>>> Pt:99 Evt:7 Pkt:02 00 0000:09:31: <Snd>>> Pt:99 Evt:7 Pkt:02 01 9000:09:31: <Snd>>> Pt:99 Evt:7 Pkt:02 03 2000:09:31: <Snd>>> Pt:99 Evt:7 Pkt:02 04 B000:09:32: <Snd>>> Pt:99 Evt:7 Pkt:02 06 4000:09:32: <Snd>>> Pt:99 Evt:7 Pkt:82 06 5800:09:32: <Snd>>> Pt:99 Evt:7 Pkt:82 06 5800:09:32: <Snd>>> Pt:99 Evt:7 Pkt:82 06 58The following example shows debugging output for the debug voip rtp session text-relay command:
Router# debug voip rtp session text-relayPt:119 Evt:0 4 247 37 128 Cnt:F7 4B <Snd>>>Related Commands
text relay protocol
Configures the system-wide protocol type for text packets transmitted between gateways.
text relay rtp
Configures the RTP payload type and redundancy level.
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
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug voip settlement all command enables the following debug settlement commands:
•
•
•
•
•
•
•
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
Examples
The following is sample output from the debug voip settlement enter command:
Router# debug voip settlement enter00: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:osppHttpSelectConnection00: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
Examples
The following is sample output from the debug voip settlement error command:
Router# debug voip settlement error00:45:50:OSP:OSPPSockProcessRequest:http recv init header failed00:45:50:OSP:osppHttpSetupAndMonitor:attempt#0 on http=0x6141A514, limit=1 error=14310Usage 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 found11220: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 certificates12200: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 pointer17020: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
Examples
The following is sample output from the debug voip settlement exit command:
Router# debug voip settlement exit01: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 :osppHttpSelectConnection01: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 :OSPPHttpParseHeader01:21:10:OSP:EXIT :OSPPHttpParseHeader01: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
Examples
The following is sample output from the debug voip settlement misc command:
Router# debug voip settlement misc00:52:03:OSP:osp_authorize:callp=0x6142770C00:52:03:OSP:OSPPTransactionRequestNew:ospvTrans=0x614278A800:52:03:OSP:osppCommMonitor:major:minor=(0x2:0x1)00:52:03:OSP:HTTP connection:reused00:52:03:OSP:osppHttpSetupAndMonitor:HTTP=0x6141A514, QUEUE_EVENT from eventQ=0x6141A87C, comm=0x613F16C4, msginfo=0x6142792C00:52:03:OSP:osppHttpSetupAndMonitor:connected = <TRUE>00:52:03:OSP:osppHttpSetupAndMonitor:HTTP=0x6141A514, build msginfo=0x6142792C, trans=0x200:52:04:OSP:osppHttpSetupAndMonitor:HTTP=0x6141A514, msg built and sent:error=0, msginfo=0x6142792C00:52:04:OSP:osppHttpSetupAndMonitor:monitor exit. errorcode=000:52:04:OSP:osppHttpSetupAndMonitor:msginfo=0x6142792C, error=0, shutdown=000:52:04:OSP:OSPPMsgInfoProcessResponse:msginfo=0x6142792C, err=0, trans=0x614278A8, handle=200:52:04:OSP:OSPPMsgInfoChangeState:transp=0x614278A8, msgtype=12 current state=200:52:04:OSP:OSPPMsgInfoChangeState:transp=0x614278A8, new state=400:52:04:OSP:OSPPMsgInfoProcessResponse:msginfo=0x6142792C, context=0x6142770C, error=000:52:04:OSP:osp_get_destination:trans_handle=2, get_first=1, callinfop=0x614275E000: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:32Z00:52:04:OSP:osp_parse_destination:dest=1.14.115.5100:52:04:OSP:osp_get_destination:callinfop=0x614275E0, error=0, ip_addr=1.14.115.51, credit=6000:52:06:OSP:stop_settlement_ccapi_accounting:send report for callid=0x11, transhandle=200:52:06:OSP:osp_report_usage:transaction=2, duration=0, lostpkts=0, lostfrs=0, lostpktr=0, lostfrr=0debug 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
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 network00:47:25:OSP:HTTP connection:reused00:47:25:OSP:OSPPSockWaitTillReady:HTTPCONN=0x6141A514, fd=000:47:25:OSP:OSPPSockWaitTillReady:read=0, timeout=0, select=100:47:25:OSP:osppHttpBuildAndSend():http=0x6141A514 sending:POST /scripts/simulator.dll?handler HTTP/1.1Host:1.14.115.12content-type:text/plainContent-Length:439Connection:Keep-AliveContent-Type:text/plainContent-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=000:47:25:OSP:OSPPSockWaitTillReady:read=0, timeout=1, select=100:47:25:OSP:OSPM_SEND:bytes_sent = 57700:47:25:OSP:OSPPSockProcessRequest:SOCKFD=0, Expecting 100, got00:47:25:OSP:OSPPSockWaitTillReady:HTTPCONN=0x6141A514, fd=000:47:25:OSP:OSPPSockWaitTillReady:read=1, timeout=1, select=100:47:25:OSP:OSPPSSLSessionRead() recving 1 bytes:HTTP/1.1 100 ContinueServer:Microsoft-IIS/4.0Date:Wed, 20 Jan 1999 02:01:54 GMT00:47:25:OSP:OSPPSockProcessRequest:SOCKFD=0, Expecting 200, got00:47:25:OSP:OSPPSockWaitTillReady:HTTPCONN=0x6141A514, fd=000:47:25:OSP:OSPPSockWaitTillReady:read=1, timeout=1, select=100:47:25:OSP:OSPPSSLSessionRead() recving 1 bytes:HTTP/1.1 200 OKServer:Microsoft-IIS/4.0Date:Wed, 20 Jan 1999 02:01:54 GMTConnection:Keep-AliveContent-Type:multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary=barContent-Length:168900:47:25:OSP:OSPPSockProcessRequest:SOCKFD=0, error=0, HTTP response00:47:25:OSP:OSPPSockWaitTillReady:HTTPCONN=0x6141A514, fd=000:47:25:OSP:OSPPSockWaitTillReady:read=1, timeout=1, select=100:47:25:OSP:OSPPSSLSessionRead() recving 1689 bytes:--barContent-Type:text/plainContent-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>--barContent-Type:application/pkcs7-signatureContent-Length:31This 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
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
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=2When the SSL connection is closed, the following message appears:
*May 15 11:57:42.541:OSP:osp_ssl_close:OSPPSSLClose succeedThe 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 oneosp_ssl_callback_add_session:Copy new session dataosp_ssl_callback_add_session:session found and equal. no addosp_ssl_callback_get_session:No Session existosp_ssl_callback_get_session:Session found, copy to sslref length=756osp_ssl_callback_delete_session:session not foundThese 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
Examples
The following is sample output from the originating gateway:
00:44:54:OSP:OSPPTransactionNew:trans=0, err=000:44:54:OSP:osp_authorize:authorizing trans=0, err=0router>00:45:05:OSP:stop_settlement_ccapi_accounting:send report forcallid=7, trans=0, calling=5710868, called=15125551212, curr_Dest=100:45:05:OSP:OSPPTransactionDelete:deleting trans=0The following is sample output from the terminating gateway:
00:44:40:OSP:OSPPTransactionNew:trans=0, err=000:44:40:OSP:osp_validate:validated trans=0, error=0, authorised=1debug 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 341.
inout
(Optional) Displays TSP function entry/exit debugs.
rose
(Optional) Enables the remote operations service element. This debug displays information about ISDN-related elements.
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug voip tsp command:
Router# debug voip tspApr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_voice_call_check:Query#9Overlap=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#9Peer Search Type=Voice*Apr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9Matched Incoming Dialpeer With=Port, Peer=299*Apr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9DID=TRUE*Apr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9Incoming Dial-peer=SUCCESS*Apr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9Matched Outgoing Dialpeer=221*Apr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_voice_call_check:Query#9Call Type=VOICE, Result=ACCEPTTable 342 describes the significant fields shown in the display.
Related Commands
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 343.
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.
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following examples show output for variations of the debug voip vtsp command:
•
•
•
•
•
For these examples, the topology shown in Figure 2 is used.
Figure 2 Network Topology for debug voip vtsp Examples
debug voip vtsp event on the Terminating Gateway
Router# debug voip vtsp eventvoip 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 functionvoip 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 inoutvoip 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_INDProgress Indication=0, CarrierIDCode=, Info Trans Capability=0, Source Carrier ID=, tg_label_flag=0The 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=AllowedCLIR=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=538706The 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_RELAYFax 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=1The 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=539158Router#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=541374The 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_RELAYFax 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=0x65289878Router#debug voip vtsp tone on the Originating Gateway
Router# debug voip vtsp tonevoip vtsp tone debugging is onThis 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 vtspVTSP:debug voip vtsp event is ON (filter is OFF)debug voip vtsp error software is ONdebug 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=0x63088050May 7 21:37:35.322 UTC: //-1/xxxxxxxxxxxx/VTSP:(3/1:D):-1:-1:-1/vtsp_do_call_setup_ind:Event=E_TSP_SETUP_INDProgress Indication=3, CarrierIDCode=, Info Trans Capability=16, Source Carrier ID=, tg_label_flag=0May 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=ISDNMay 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=0x63088050May 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=0May 7 21:37:35.330 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop:Timer Stop Time=1019502May 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=3May 7 21:37:35.394 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop:Timer Stop Time=1019508May 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=ENABLEDPrimary Fax Protocol=T38_FAX_RELAY, Fallback Fax Protocol=NONE_FAX_RELAYFax Parameters Set By=Dialpeer, Peer=2May 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=0May 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_INDMay 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_ACKMay 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=1019711May 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=0May 7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_ring_noan_timer_stop:Timer Stop Time=1019711May 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=1May 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=1May 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_DONEMay 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_MODEMay 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_DONEMay 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_MODEMay 7 21:38:02.911 UTC: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x6040A40C reading 0x1May 7 21:38:02.911 UTC: %ALIGN-3-TRACE: -Traceback= 6040A40C 60409198 603F8338 603F85F8 613EA398 619B369C 619B40BC 613DFEE4May 7 21:38:02.915 UTC: %ALIGN-3-TRACE: -Traceback= 6040A54C 60409198 603F8338 603F85F8 613EA398 619B369C 619B40BC 613DFEE4May 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_ACKMay 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=16May 7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop:Timer Stop Time=1025735May 7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_ring_noan_timer_stop:Timer Stop Time=1025735May 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-PSTNMay 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=0May 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=16May 7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_ring_noan_timer_stop:Timer Stop Time=1025735May 7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_save_fax_config:Fax Relay=ENABLEDPrimary Fax Protocol=T38_FAX_RELAY, Fallback Fax Protocol=NONE_FAX_RELAYFax Parameters Set By=Dialpeer, Peer=2May 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=0May 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=1025738May 7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop:Timer Stop Time=1025738May 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=1025738May 7 21:38:37.695 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/vtsp_free_cdb:CDB=0x63088050Related Commands
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 EXECCommand History
Examples
The following is sample output from the debug voip xcodemsp command:
Router# debug voip xcodemspXCODEMSP debugging is onRouter#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_responseRouter#Router#Router# show sccp connectionssess_id conn_id stype mode codec ripaddr rport sport16777223 16777905 xcode sendrecv g711a 1.4.177.1 16628 1887016777223 16777921 xcode sendrecv g729ab 1.4.177.5 31318 18146Total number of active session(s) 1, and connection(s) 2Router#*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
Command Modes
Privileged EXEC
Command History
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
The network access server (NAS) has the following VPDN configuration:
vpdn-group 1request-dialinprotocol l2fdomain cisco.cominitiate-to ip 172.17.33.125username nas1 password nas1The 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 downTable 344 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.
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 1accept-dialinprotocol l2fvirtual-template 1terminate-from hostname nas1The 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 eventL2F: Chap authentication succeeded for nas1.Virtual-Access3 VPN Virtual interface created for user6@cisco.comVirtual-Access3 VPN Set to Async interfaceVirtual-Access3 VPN Clone from Vtemplate 1 block=1 filterPPP=0%LINK-3-UPDOWN: Interface Virtual-Access3, changed state to upVirtual-Access3 VPN Bind interface direction=2Virtual-Access3 VPN PPP LCP accepted sent & rcv CONFACK%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to upThe 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 downVirtual-Access3 VPN cleanupVirtual-Access3 VPN resetVirtual-Access3 VPN Unbind interfaceVirtual-Access3 VPN reset%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to downTable 345 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.
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 event20:19:17: L2TP: I SCCRQ from ts1 tnl 820:19:17: L2X: Never heard of ts120:19:17: Tnl 7 L2TP: New tunnel created for remote ts1, address 172.21.9.420:19:17: Tnl 7 L2TP: Got a challenge in SCCRQ, ts120:19:17: Tnl 7 L2TP: Tunnel state change from idle to wait-ctl-reply20:19:17: Tnl 7 L2TP: Got a Challenge Response in SCCCN from ts120:19:17: Tnl 7 L2TP: Tunnel Authentication success20:19:17: Tnl 7 L2TP: Tunnel state change from wait-ctl-reply to established20:19:17: Tnl 7 L2TP: SM State established20:19:17: Tnl/Cl 7/1 L2TP: Session FS enabled20:19:17: Tnl/Cl 7/1 L2TP: Session state change from idle to wait-for-tunnel20:19:17: Tnl/Cl 7/1 L2TP: New session created20:19:17: Tnl/Cl 7/1 L2TP: O ICRP to ts1 8/120:19:17: Tnl/Cl 7/1 L2TP: Session state change from wait-for-tunnel to wait-connect20:19:17: Tnl/Cl 7/1 L2TP: Session state change from wait-connect to established20:19:17: Vi1 VPDN: Virtual interface created for bum1@cisco.com20:19:17: Vi1 VPDN: Set to Async interface20:19:17: Vi1 VPDN: Clone from Vtemplate 1 filterPPP=0 blocking20:19:18: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up20:19:18: Vi1 VPDN: Bind interface direction=220:19:18: Vi1 VPDN: PPP LCP accepting rcv CONFACK20: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 event20:47:33: %LINK-3-UPDOWN: Interface Async7, changed state to up20: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.1320:47:35: As7 VPDN: Forward to address 172.21.9.1320:47:35: As7 VPDN: Forwarding...20:47:35: As7 VPDN: Bind interface direction=120:47:35: Tnl/Cl 8/1 L2TP: Session FS enabled20:47:35: Tnl/Cl 8/1 L2TP: Session state change from idle to wait-for-tunnel20:47:35: As7 8/1 L2TP: Create session20:47:35: Tnl 8 L2TP: SM State idle20:47:35: Tnl 8 L2TP: Tunnel state change from idle to wait-ctl-reply20:47:35: Tnl 8 L2TP: SM State wait-ctl-reply20:47:35: As7 VPDN: bum1@cisco.com is forwarded20:47:35: Tnl 8 L2TP: Got a challenge from remote peer, nas120:47:35: Tnl 8 L2TP: Got a response from remote peer, nas120:47:35: Tnl 8 L2TP: Tunnel Authentication success20:47:35: Tnl 8 L2TP: Tunnel state change from wait-ctl-reply to established20:47:35: Tnl 8 L2TP: SM State established20:47:35: As7 8/1 L2TP: Session state change from wait-for-tunnel to wait-reply20:47:35: As7 8/1 L2TP: Session state change from wait-reply to established20:47:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async7, changed state to upDebugging 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 Async6The 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 tunnelTable 346 describes the fields shown in the displays.
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-eventsL2F_CONF receivedL2F Creating new tunnel for nas1L2F Got a tunnel named nas1, respondingL2F Open UDP socket to 172.21.9.25L2F_OPEN receivedL2F Removing resend packet (type 1)L2F_OPEN receivedL2F Got a MID management packet%LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to upThe following is sample output from the debug vpdn l2x-events command on a tunnel server when the L2F tunnel is brought down normally:
Router# debug vpdn l2x-eventsL2F_CLOSE receivedL2F Destroying midL2F Removing resend packet (type 3)L2F Tunnel is going down!L2F Initiating tunnel shutdown.%LINK-3-UPDOWN: Interface Virtual-Access1, changed state to downL2F_CLOSE receivedL2F Got closing for tunnelL2F Removing resend packetL2F Removing resend packetL2F Closed tunnel structureL2F Closed tunnel structureL2F Deleted inactive tunnel%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to downTable 347 describes the significant fields shown in the displays.
Debugging Errors on the NAS—L2F Error Conditions
The following is sample output from the debug vpdn errors command on a NAS when the L2F tunnel is not set up:
Router# debug vpdn errors%LINEPROTO-5-UPDOWN: Line protocol on Interface Async1, changed state to down%LINK-5-CHANGED: Interface Async1, changed state to reset%LINK-3-UPDOWN: Interface Async1, changed state to down%LINK-3-UPDOWN: Interface Async1, changed state to up%LINEPROTO-5-UPDOWN: Line protocol on Interface Async1, changed state to upVPDN tunnel management packet failed to authenticateVPDN tunnel management packet failed to authenticateTable 348 describes the significant fields shown in the display.
The following is sample output from the debug vpdn l2x-errors command:
Router# debug vpdn l2x-errors%LINK-3-UPDOWN: Interface Async1, changed state to upL2F Out of sequence packet 0 (expecting 0)L2F Tunnel authentication succeeded for cisco.comL2F Received a close request for a non-existent midL2F Out of sequence packet 0 (expecting 0)L2F packet has bogus1 key 1020868 D248BA0FL2F packet has bogus1 key 1020868 D248BA0FTable 349 describes the significant fields shown in the display.
Debugging L2F Control Packets for Complete Information
The following is sample output from the debug vpdn l2x-packets command on a NAS. This example displays a trace for a ping command:
Router# debug vpdn l2x-packetsL2F SENDING (17): D0 1 1 10 0 0 0 4 0 11 0 0 81 94 E1 A0 4L2F header flags: 53249 version 53249 protocol 1 sequence 16 mid 0 cid 4length 17 offset 0 key 1701976070L2F RECEIVED (17): D0 1 1 10 0 0 0 4 0 11 0 0 65 72 18 6 5L2F SENDING (17): D0 1 1 11 0 0 0 4 0 11 0 0 81 94 E1 A0 4L2F header flags: 53249 version 53249 protocol 1 sequence 17 mid 0 cid 4length 17 offset 0 key 1701976070L2F RECEIVED (17): D0 1 1 11 0 0 0 4 0 11 0 0 65 72 18 6 5L2F header flags: 57345 version 57345 protocol 2 sequence 0 mid 1 cid 4length 32 offset 0 key 1701976070L2F-IN Output to Async1 (16): FF 3 C0 21 9 F 0 C 0 1D 41 AD FF 11 46 87L2F-OUT (16): FF 3 C0 21 A F 0 C 0 1A C9 BD FF 11 46 87L2F header flags: 49153 version 49153 protocol 2 sequence 0 mid 1 cid 4length 32 offset 0 key -2120949344L2F-OUT (101): 21 45 0 0 64 0 10 0 0 FF 1 B9 85 1 0 0 3 1 0 0 1 8 0 62 B10 0 C A8 0 0 0 0 0 11 E E0 AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CDAB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD ABCD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CDL2F header flags: 49153 version 49153 protocol 2 sequence 0 mid 1 cid 4length 120 offset 3 key -2120949344L2F header flags: 49153 version 49153 protocol 2 sequence 0 mid 1 cid 4length 120 offset 3 key 1701976070L2F-IN Output to Async1 (101): 21 45 0 0 64 0 10 0 0 FF 1 B9 85 1 0 0 1 1 00 3 0 0 6A B1 0 0 C A8 0 0 0 0 0 11 E E0 AB CD AB CD AB CD AB CD AB CD AB CDAB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD ABCD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CDTable 350 describes the significant fields shown in the display.
Debugging an L2TPv3 Xconnect Session—Normal Operations
The following example shows output from the debug vpdn command for an L2TP version 3 (L2TPv3) xconnect session on an Ethernet interface:
Router# debug vpdn l2x-events23:31:18: L2X: l2tun session [1669204400], event [client request], old state [open], new state [open]23:31:18: L2X: L2TP: Received L2TUN message <Connect>23:31:18: Tnl/Sn58458/28568 L2TP: Session state change from idle to wait-for-tunnel23:31:18: Tnl/Sn58458/28568 L2TP: Create session23:31:18: Tnl58458 L2TP: SM State idle23:31:18: Tnl58458 L2TP: O SCCRQ23:31:18: Tnl58458 L2TP: Control channel retransmit delay set to 1 seconds23:31:18: Tnl58458 L2TP: Tunnel state change from idle to wait-ctl-reply23:31:18: Tnl58458 L2TP: SM State wait-ctl-reply23:31:18: Tnl58458 L2TP: I SCCRP from router23:31:18: Tnl58458 L2TP: Tunnel state change from wait-ctl-reply to established23:31:18: Tnl58458 L2TP: O SCCCN to router tnlid 801223:31:18: Tnl58458 L2TP: Control channel retransmit delay set to 1 seconds23:31:18: Tnl58458 L2TP: SM State established23:31:18: Tnl/Sn58458/28568 L2TP: O ICRQ to router 8012/023:31:18: Tnl/Sn58458/28568 L2TP: Session state change from wait-for-tunnel to wait-reply23:31:19: Tnl58458 L2TP: Control channel retransmit delay set to 1 seconds23:31:20: %LINK-3-UPDOWN: Interface Ethernet2/1, changed state to up23:31:21: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet2/1, changed state to up23:31:25: L2X: Sending L2TUN message <Connect OK>23:31:25: Tnl/Sn58458/28568 L2TP: O ICCN to router 8012/3514923:31:25: Tnl58458 L2TP: Control channel retransmit delay set to 1 seconds23:31:25: Tnl/Sn58458/28568 L2TP: Session state change from wait-reply to established23:31:25: L2X: l2tun session [1669204400], event [server response], old state [open], new state [open]23:31:26: Tnl58458 L2TP: Control channel retransmit delay set to 1 secondsRelated Commands
debug vpdn pppoe-data
Note
To display data packets of PPP over Ethernet (PPPoE) sessions, use the debug vpdn pppoe-data command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpdn pppoe-data
no debug vpdn pppoe-data
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.1(1)T
This command was introduced.
12.2(13)T
This command was replaced by the debug pppoe command.
Usage Guidelines
The debug vpdn pppoe-data command displays a large number of debug messages and should generally be used only on a debug chassis with a single active session.
Examples
The following is sample output from the debug vpdn pppoe-data command:
Router# debug vpdn pppoe-data6d20h:%LINK-3-UPDOWN:Interface Virtual-Access1, changed state to up6d20h:PPPoE:OUTcontiguous pak, size 19FF 03 C0 21 01 01 00 0F 03 05 C2 23 05 05 06 D3FF 2B DA6d20h:PPPoE:INparticle pak, size 1240C0 21 01 01 00 0A 05 06 39 53 A5 17 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 006d20h:PPPoE:OUTcontiguous pak, size 14FF 03 C0 21 02 01 00 0A 05 06 39 53 A5 176d20h:PPPoE:OUTcontiguous pak, size 19FF 03 C0 21 01 02 00 0F 03 05 C2 23 05 05 06 D3FF 2B DA6d20h:PPPoE:INparticle pak, size 1740C0 21 02 02 00 0F 03 05 C2 23 05 05 06 D3 FF 2BDA 00 80 C2 00 07 00 00 00 10 7B 01 2C D9 00 B0C2 EB 10 38 88 64 11 006d20h:PPPoE:OUTcontiguous pak, size 30FF 03 C2 23 01 06 00 1A 10 99 1E 6E 8F 8C F2 C6EE 91 0A B0 01 CB 89 68 13 47 61 6E 67 616d20h:PPPoE:INparticle pak, size 3840C2 23 02 06 00 24 10 E6 84 FF 3A A4 49 19 CE D7AC D7 D5 96 CC 23 B3 41 6B 61 73 68 40 63 69 7363 6F 2E 63 6F 6D 00 006d20h:PPPoE:OUTcontiguous pak, size 8FF 03 C2 23 03 06 00 046d20h:PPPoE:OUTcontiguous pak, size 14FF 03 80 21 01 01 00 0A 03 06 65 65 00 666d20h:PPPoE:INparticle pak, size 124080 21 01 01 00 0A 03 06 00 00 00 00 49 19 CE D7AC D7 D5 96 CC 23 B3 41 6B 61 73 68 40 63 69 7363 6F 2E 63 6F 6D 00 006d20h:PPPoE:OUTcontiguous pak, size 14FF 03 80 21 03 01 00 0A 03 06 65 65 00 676d20h:PPPoE:INparticle pak, size 124080 21 02 01 00 0A 03 06 65 65 00 66 00 04 AA AA03 00 80 C2 00 07 00 00 00 10 7B 01 2C D9 00 B0C2 EB 10 38 88 64 11 006d20h:PPPoE:INparticle pak, size 124080 21 01 02 00 0A 03 06 65 65 00 67 49 19 CE D7AC D7 D5 96 CC 23 B3 41 6B 61 73 68 40 63 69 7363 6F 2E 63 6F 6D 00 006d20h:PPPoE:OUTcontiguous pak, size 14FF 03 80 21 02 02 00 0A 03 06 65 65 00 676d20h:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access1,changed state to up6d20h:PPPoE:OUTcontiguous pak, size 16FF 03 C0 21 09 01 00 0C D3 FF 2B DA 4C 4D 49 A46d20h:PPPoE:INparticle pak, size 1440C0 21 0A 01 00 0C 39 53 A5 17 4C 4D 49 A4 AA AA03 00 80 C2 00 07 00 00 00 10 7B 01 2C D9 00 B0C2 EB 10 38 88 64 11 006d20h:PPPoE:INparticle pak, size 1440C0 21 09 01 00 0C 39 53 A5 17 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00Table 351 describes the significant fields shown in the display.
Related Commands
debug vpdn pppoe-error
Note
To display PPP over Ethernet (PPPoE) protocol errors that prevent a session from being established or errors that cause an established sessions to be closed, use the debug vpdn pppoe-error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpdn pppoe-error
no debug vpdn pppoe-error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.1(1)T
This command was introduced.
12.2(13)T
This command was replaced by the debug pppoe command.
Examples
The following is a full list of error messages displayed by the debug vpdn pppoe-error command:
PPPOE:pppoe_acsys_err cannot grow packetPPPoE:Cannot find PPPoE infoPPPoE:Bad MAC address:00b0c2eb1038PPPOE:PADI has no service name tagPPPoE:pppoe_handle_padi cannot add AC name/Cookie.PPPoE:pppoe_handle_padi cannot grow packetPPPoE:pppoe_handle_padi encap failedPPPoE cannot create virtual access.PPPoE cannot allocate session structure.PPPoE cannot store session element in tunnel.PPPoE cannot allocate tunnel structure.PPPoE cannot store tunnelPPPoE:VA221:No Session, Packet DiscardedPPPOE:Tried to shutdown a null sessionPPPoE:Session already open, closingPPPoE:Bad cookie:src_addr=00b0c2eb1038PPPoE:Max session count on mac elem exceeded:mac=00b0c2eb1038PPPoE:Max session count on vc exceeded:vc=3/77PPPoE:Bad MAC address - dropping packetPPPoE:Bad version or type - dropping packetTable 352 describes the significant fields shown in the display.
Related Commands
debug vpdn pppoe-events
Note
To display PPP over Ethernet (PPPoE) protocol messages about events that are part of normal session establishment or shutdown, use the debug vpdn pppoe-events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpdn pppoe-events
no debug vpdn pppoe-events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.1(1)T
This command was introduced.
12.2(13)T
This command was replaced by the debug pppoe command.
Examples
The following is sample output from the debug vpdn pppoe-events command:
1w5d:IN PADI from PPPoE tunnel1w5d:OUT PADO from PPPoE tunnel1w5d:IN PADR from PPPoE tunnel1w5d:PPPoE:VPN session created.1w5d:%LINK-3-UPDOWN:Interface Virtual-Access2, changed state to up1w5d:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access2, changed state to upTable 353 describes the significant fields shown in the display.
Related Commands
debug vpdn pppoe-packet
Note
To display each PPP over Ethernet (PPPoE) protocol packet exchanged, use the debug vpdn pppoe-packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpdn pppoe-packet
no debug vpdn pppoe-packet
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.1(1)T
This command was introduced.
12.2(13)T
This command was replaced by the debug pppoe command.
Usage Guidelines
The debug vpdn pppoe-packet command displays a large number of debug messages and should generally only be used on a debug chassis with a single active session.
Examples
The following is sample output from the debug vpdn pppoe-packet command:
PPPoE control packets debugging is on1w5d:PPPoE:discovery packetcontiguous pak, size 74FF FF FF FF FF FF 00 10 7B 01 2C D9 88 63 11 0900 00 00 04 01 01 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...1w5d:OUT PADO from PPPoE tunnelcontiguous pak, size 7400 01 09 00 AA AA 03 00 80 C2 00 07 00 00 00 107B 01 2C D9 00 90 AB 13 BC A8 88 63 11 07 00 0000 20 01 01 00 00 01 02 00 04 41 67 6E 69 01 ...1w5d:PPPoE:discovery packetcontiguous pak, size 7400 90 AB 13 BC A8 00 10 7B 01 2C D9 88 63 11 1900 00 00 20 01 01 00 00 01 02 00 04 41 67 6E 6901 04 00 10 B7 4B 86 5B 90 A5 EF 11 64 A9 BA ...Table 354 describes the significant fields shown in the display.
Related Commands
debug vpm all
To enable all voice port module (VPM) debugging, use the debug vpm all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug vpm all
no debug vpm all
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug vpm all command to enable the complete set of VPM debugging commands: debug vpm dsp, debug vpm error, debug vpm port, debug vpm spi, and debug vpm trunk_sc.
Execution of no debug all will turn off all port level debugging. It is usually a good idea to turn off all debugging and then enter the debug commands you are interested in one by one. This will help to avoid confusion about which ports you are actually debugging.
Examples
For sample outputs, refer to the documentation of the other debup vpm commands.
Related Commands
Posted: Mon Jul 2 06:58:21 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
