-
Cisco IOS Debug Command Reference
-
Introduction
-
Using Debug Commands
-
Conditionally Triggered Debugging
-
debug aaa accounting through debug auto-config
-
debug backhaul-session-manager session through debug channel packets
-
debug clns esis events through debug dbconn tcp
-
debug decnet adj through debug events
-
debug fax dmsp through debug gvrp
-
debug h225 asn1 through debug ip ftp
-
debug ip http all through debug ip rsvp
-
debug ip rtp header-compression through debug ipv6 icmp
-
debug ipv6 inspect through debug local-ack state
-
debug management event through debug mpls ldp bindings
-
debug mpls ldp checkpoint through debug mwi relay events
-
debug ncia circuit through debug pxf tbridge
-
debug qllc error through debug snmp sync
-
debug sntp adjust through debug tag-switching xtagatm vc
-
debug tag-template event through debug voip application vxml
-
debug voip avlist through debug vpm signaling
-
debug vpm spi through voice call debug
-
X.25 Cause and Diagnostic Codes
-
ISDN Switch Types, Codes, and Values
-
Table Of Contents
debug backhaul-session-manager session
debug backhaul-session-manager set
debug call rsvp-sync func-trace
debug cce dp named-db urlfilter
debug cdma pdsn accounting flow
debug cdma pdsn accounting time-of-day
debug cdma pdsn resource-manager
debug cdma pdsn service-selection
debug cellular messages management
debug cellular messages virt-con
debug backhaul-session-manager session
To debug all the available sessions or a specified session, use the debug backhaul-session-manager session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug backhaul-session-manager session {state | xport} {all | session-id}
no debug backhaul-session-manager session {state | xport} {all | session-id}
CautionUse caution when enabling this debug command in a live system. It produces significant amounts of output, which could lead to a disruption of service.
Syntax Description
Defaults
Debugging for backhaul-session-manager session is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is output for the debug backhaul-session-manager session all command:
Router# debug backhaul-session-manager session allRouter# debug_bsm_command:DEBUG_BSM_SESSION_ALL23:49:14:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:49:14:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:49:14:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:14:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:14:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:19:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:49:19:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:49:19:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:19:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:19:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:24:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:49:24:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:49:24:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:24:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:24:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:29:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:49:29:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:49:29:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:29:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:29:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:34:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:49:34:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:49:34:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:34:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:34:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:34:SESSION:XPORT:sig rcvd. session = 33, connid = 0x80BA14EC, sig = 1 (CONN-FAILED)23:49:34:SESSION:STATE:(33) old-state:OPEN, new-state:CLOSE_WAITThe following example displays output for the debug backhaul-session-manager session state all command:
Router# debug backhaul-session-manager session state allRouter# debug_bsm_command:DEBUG_BSM_SESSION_STATE_ALL23:50:54:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:50:54:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:50:54:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:50:54:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOSThe following example displays output for the debug backhaul-session-manager session xport all command:
Router# debug backhaul-session-manager session xport allRouter# debug_bsm_command:DEBUG_BSM_SESSION_XPORT23:51:39:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:51:42:SESSION:XPORT:sig rcvd. session = 33, connid = 0x80BA14EC, sig = 5 (CONN-RESET)23:51:44:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)Related Commands
debug backhaul-session-manager set
Traces state changes and receives messages and events for all available session-sets or a specified session-set.
debug backhaul-session-manager set
To trace state changes and receive messages and events for all the available session sets or a specified session set, use the debug backhaul-session-manager set command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug backhaul-session-manager set {all | name set-name}
no debug backhaul-session-manager set {all | name set-name}
Syntax Description
Defaults
Debugging for backhaul session sets is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is output for the debug backhaul-session-manager set command for all available session sets:
Router# debug backhaul-session-manager set allRouter# debug_bsm_command:DEBUG_BSM_SET_ALLFunction set_proc_event() is calledSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_OOSActive-Grp :NONESession-Grp :g-11Old State :Group-NoneNew State :Group-NoneEvent rcvd :EVT_GRP_INSBSM:Event BSM_SET_UP is sent to userSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_ACTIVE_ISActive-Grp :g-11Session-Grp :g-11Old State :Group-NoneNew State :Group-ActiveEvent rcvd :BSM_ACTIVE_TYPEThe following is output for the debug backhaul-session-manager set name set1 command:
Router# debug backhaul-session-manager set name set1Router# debug_bsm_command:DEBUG_BSM_SET_NAMERouter# Function set_proc_event() is calledSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_OOSActive-Grp :NONESession-Grp :g-11Old State :Group-NoneNew State :Group-NoneEvent rcvd :EVT_GRP_INSRouter#BSM:Event BSM_SET_UP is sent to userSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_ACTIVE_ISActive-Grp :g-11Session-Grp :g-11Old State :Group-NoneNew State :Group-ActiveEvent rcvd :BSM_ACTIVE_TYPERelated Commands
debug backhaul-session-manager session
Debugs all available sessions or a specified session.
debug backup
To monitor the transitions of an interface going down then back up, use the debug backup command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug backup
no debug backup
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug backup command is useful for monitoring dual X.25 interfaces configured as primary and backup in a Telco data communication network (DCN).
Examples
The following example shows how to start the debug backup command:
Router# debug backupRelated Commands
backup active interface
Activates primary and backup lines on specific X.25 interfaces.
show backup
Displays interface backup status.
debug bert
To display information on the bit error rate testing (BERT) feature, use the debug bert command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bert
no debug bert
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bert command output is used primarily by Cisco technical support representatives. The debug bert command displays debugging messages for specific areas of executed code.
Examples
The following is output from the debug bert command:
Router# debug bertBit Error Rate Testing debugging is onRouter# no debug bertBit Error Rate Testing debugging is offRelated Commands
debug bfd
To display debugging messages about Bidirectional Forwarding Detection (BFD), use the debug bfd command in privileged EXEC mode. To disable debugging output, use the no form of this command.
Cisco IOS Release 12.2(18)SXE, 12.4(4)T, and 12.2(33)SRA
debug bfd {event | packet [ip-address]}
no debug bfd {event | packet [ip-address]}
Cisco IOS Release 12.0(31)S
debug bfd {event | packet [ip-address] | ipc-error | ipc-event | oir-error | oir-event}
no debug bfd {event | packet [ip-address] | ipc-error | ipc-event | oir-error | oir-event}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bfd command can be used to troubleshoot the BFD feature.
Note
Examples
The following example shows output from the debug bfd packet command. The IP address has been specified in order to limit the packet information to one interface:
Router# debug bfd packet 172.16.10.5BFD packet debugging is on*Jan 26 14:47:37.645: Tx*IP: dst 172.16.10.1, plen 24. BFD: diag 2, St/D/P/F (1/0/0/0), mult 5, len 24, loc/rem discr 1 1, tx 1000000, rx 1000000 100000, timer 1000 ms, #103*Jan 26 14:47:37.645: %OSPF-5-ADJCHG: Process 10, Nbr 172.16.10.12 on Ethernet1/4 from FULL to DOWN, Neighbor Down: BFD node down*Jan 26 14:47:50.685: %OSPF-5-ADJCHG: Process 10, Nbr 172.16.10.12 on Ethernet1/4 from LOADING to FULL, Loading Done*Jan 26 14:48:00.905: Rx IP: src 172.16.10.1, plen 24. BFD: diag 0, St/D/P/F (1/0/0/0), mult 4, len 24, loc/rem discr 2 1, tx 1000000, rx 1000000 100000, timer 4000 ms, #50*Jan 26 14:48:00.905: Tx IP: dst 172.16.10.1, plen 24. BFD: diag 2, St/D/P/F (2/0/0/0), mult 5, len 24, loc/rem discr 1 2, tx 1000000, rx 1000000 100000, timer 1000 ms, #131*Jan 26 14:48:00.905: Rx IP: src 172.16.10.1, plen 24. BFD: diag 0, St/D/P/F (3/0/0/0), mult 4, len 24, loc/rem discr 2 1, tx 1000000, rx 1000000 100000, timer 4000 ms, #51*Jan 26 14:48:00.905: Tx IP: dst 172.16.10.1, plen 24. BFD: diag 0, St/D/P/F (3/0/0/0), mult 5, len 24, loc/rem discr 1 2, tx 1000000, rx 1000000 100000, timer 1000 ms, #132The following example shows output from the debug bfd event command when an interface between two BFD neighbor routers fails and then comes back online:
Router# debug bfd event22:53:48: BFD: bfd_neighbor - action:DESTROY, proc:1024, idb:FastEthernet0/1, neighbor:172.16.10.222:53:48: BFD: bfd_neighbor - action:DESTROY, proc:512, idb:FastEthernet0/1, neighbor:172.16.10.222:53:49: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event DETECT TIMER EXPIRED, state UP -> FAILING...22:56:35: BFD: bfd_neighbor - action:CREATE, proc:1024, idb:FastEthernet0/1, neighbor:172.16.10.222:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 0, state FAILING -> DOWN22:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 0, state DOWN -> INIT22:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 1, state INIT -> UPTable 36 describes the significant fields shown in the display.
The following example shows output from the debug bfd packet command when an interface between two BFD neighbor routers fails and then comes back online. The diagnostic code changes from 0 (No Diagnostic) to 1 (Control Detection Time Expired) because no BFD control packets could be sent (and therefore detected by the BFD peer) after the interface fails. When the interface comes back online, the diagnostic code changes back to 0 to signify that BFD packets can be sent and received by the BFD peers.
Router# debug bfd packet23:03:25: Rx IP: src 172.16.10.2, plen 24. BFD: diag 0, H/D/P/F (0/0/0/0), mult 3, len 24, loc/rem discr 5 1, tx 1000000, rx 10000723:03:25: Tx IP: dst 172.16.10.2, plen 24. BFD: diag 1, H/D/P/F (0/0/0/0), mult 5, len 24, loc/rem discr 1 5, tx 1000000, rx 100000823:03:25: Tx IP: dst 172.16.10.2, plen 24. BFD: diag 1, H/D/P/F (1/0/0/0), mult 5, len 24, loc/rem discr 1 5, tx 1000000, rx 1000009Table 37 describes the significant fields shown in the display.
debug bgp ipv6 dampening
To display debugging messages for IPv6 Border Gateway Protocol (BGP) dampening, use the debug bgp ipv6 dampening command in privileged EXEC mode. To disable debugging messages for IPv6 BGP dampening, use the no form of this command.
debug bgp ipv6 {unicast | multicast} dampening [prefix-list prefix-list-name]
no debug bgp ipv6 {unicast | multicast} dampening [prefix-list prefix-list-name]
Syntax Description
unicast
Specifies IPv6 unicast address prefixes.
multicast
Specifies IPv6 multicast address prefixes.
prefix-list prefix-list-name
(Optional) Name of an IPv6 prefix list.
Command Default
Debugging for IPv6 BGP dampening packets is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bgp ipv6 dampening command is similar to the debug ip bgp dampening command, except that it is IPv6-specific.
Use the prefix-list keyword and an argument to filter BGP IPv6 dampening debug information through an IPv6 prefix list.
Note
Examples
The following is sample output from the debug bgp ipv6 dampening command:
Router# debug bgp ipv6 dampening00:13:28:BGP(1):charge penalty for 2000:0:0:1::/64 path 2 1 with halflife-time 15 reuse/suppress 750/200000:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty is 100000:13:28:BGP(1):charge penalty for 2000:0:0:1:1::/80 path 2 1 with halflife-time 15 reuse/suppress 750/200000:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty is 100000:13:28:BGP(1):charge penalty for 2000:0:0:5::/64 path 2 1 with halflife-time 15 reuse/suppress 750/200000:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty is 100000:16:03:BGP(1):charge penalty for 2000:0:0:1::/64 path 2 1 with halflife-time 15 reuse/suppress 750/200000:16:03:BGP(1):flapped 2 times since 00:02:35. New penalty is 189200:18:28:BGP(1):suppress 2000:0:0:1:1::/80 path 2 1 for 00:27:30 (penalty 2671)00:18:28:halflife-time 15, reuse/suppress 750/200000:18:28:BGP(1):suppress 2000:0:0:1::/64 path 2 1 for 00:27:20 (penalty 2664)00:18:28:halflife-time 15, reuse/suppress 750/2000The following example shows output for the debug bgp ipv6 dampening command filtered through the prefix list named marketing:
Router# debug bgp ipv6 dampening prefix-list marketing00:16:08:BGP(1):charge penalty for 2001:0DB8::/64 path 30 with halflife-time 15 reuse/suppress 750/200000:16:08:BGP(1):flapped 1 times since 00:00:00. New penalty is 10Table 38 describes the fields shown in the display.
Related Commands
debug bgp ipv6 updates
To display debugging messages for IPv6 Border Gateway Protocol (BGP) update packets, use the debug bgp ipv6 updates command in privileged EXEC mode. To disable debugging messages for IPv6 BGP update packets, use the no form of this command.
debug bgp ipv6 {unicast | multicast} updates [ipv6-address] [prefix-list prefix-list-name] [in | out]
no debug bgp ipv6 {unicast | multicast} updates [ipv6-address] [prefix-list prefix-list-name] [in | out]
Syntax Description
Command Default
Debugging for IPv6 BGP update packets is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bgp ipv6 updates command is similar to the debug ip bgp updates command, except that it is IPv6-specific.
Use the prefix-list keyword to filter BGP IPv6 updates debugging information through an IPv6 prefix list.
Note
Examples
The following is sample output from the debug bgp ipv6 updates command:
Router# debug bgp ipv6 updates14:04:17:BGP(1):2000:0:0:2::2 computing updates, afi 1, neighbor version 0, table version 1, starting at ::14:04:17:BGP(1):2000:0:0:2::2 update run completed, afi 1, ran for 0ms, neighbor version 0, start version 1, throttled to 114:04:19:BGP(1):sourced route for 2000:0:0:2::1/64 path #0 changed (weight 32768)14:04:19:BGP(1):2000:0:0:2::1/64 route sourced locally14:04:19:BGP(1):2000:0:0:2:1::/80 route sourced locally14:04:19:BGP(1):2000:0:0:3::2/64 route sourced locally14:04:19:BGP(1):2000:0:0:4::2/64 route sourced locally14:04:22:BGP(1):2000:0:0:2::2 computing updates, afi 1, neighbor version 1, table version 6, starting at ::14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (format) 2000:0:0:2::1/64, next 2000:0:0:2::1, metric 0, path14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (format) 2000:0:0:2:1::/80, next 2000:0:0:2::1, metric 0, path14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (prepend, chgflags:0x208) 2000:0:0:3::2/64, next 2000:0:0:2::1, metric 0, path14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (prepend, chgflags:0x208) 2000:0:0:4::2/64, next 2000:0:0:2::1, metric 0, pathThe following is sample output from the debug bgp ipv6 updates command filtered through the prefix list named sales:
Router# debug bgp ipv6 updates prefix-list sales00:18:26:BGP(1):2000:8493:1::2 send UPDATE (prepend, chgflags:0x208) 7878:7878::/64, next 2001:0DB8::36C, metric 0, pathTable 39 describes the significant fields shown in the display.
Related Commands
debug bgp ipv6 dampening
Displays debugging messages for IPv6 BGP dampening packets.
debug bgp nsap
To enable the display of Border Gateway Protocol (BGP) debugging information specific to the network service access point (NSAP) address family, use the debug bgp nsap command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bgp nsap
no debug bgp nsap
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging of BGP NSAP address-family code is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bgp nsap command is similar to the debug ip bgp command, except that it is specific to the NSAP address family.
Note
Examples
The following example shows output for the debug bgp nsap command. The BGP(4) identifies that BGP version 4 is operational.
Router# debug bgp nsap00:46:46: BGP(4): removing CLNS route to 49.010100:46:46: BGP(4): removing CLNS route to 49.030300:46:46: BGP(4): removing CLNS route to 49.040400:46:46: BGP(4): 10.1.2.1 removing CLNS route 49.0101.1111.1111.1111.1111.00 toeBGP-neighbor00:46:46: BGP(4): 10.2.4.4 removing CLNS route 49.0303.4444.4444.4444.4444.00 toeBGP-neighbor00:46:59: BGP(4): Applying map to find origin for prefix 49.0202.222200:46:59: BGP(4): Applying map to find origin for prefix 49.0202.3333Related Commands
debug bgp nsap dampening
Displays debug messages for BGP NSAP prefix dampening events.
debug bgp nsap updates
Displays debug messages for BGP NSAP prefix update packets.
debug bgp nsap dampening
To display debug messages for Border Gateway Protocol (BGP) network service access point (NSAP) prefix address dampening, use the debug bgp nsap dampening command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bgp nsap dampening [filter-list access-list-number]
no debug bgp nsap dampening [filter-list access-list-number]
Syntax Description
filter-list access-list-number
(Optional) Displays debug messages for BGP NSAP dampening events that match the access list. The acceptable access list number range is from 1 to 199.
Command Default
Debugging for BGP NSAP dampening events is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bgp nsap dampening command is similar to the debug ip bgp dampening command, except that it is specific to the NSAP address family.
Note
Examples
The following example shows output for the debug bgp nsap dampening command:
Router# debug bgp nsap dampening16:21:34: BGP(4): Dampening route-map modified.Only one line of output is displayed unless the bgp dampening command is configured with a route map in NSAP address family configuration mode. The following example shows output for the debug bgp nsap dampening command when a route map is configured:
20:07:19: BGP(4): charge penalty for 49.0404 path 65202 65404 with halflife-time 15reuse/suppress 750/200020:07:19: BGP(4): flapped 1 times since 00:00:00. New penalty is 100020:08:59: BGP(4): charge penalty for 49.0404 path 65202 65404 with halflife-time 15reuse/suppress 750/200020:08:59: BGP(4): flapped 2 times since 00:01:39. New penalty is 192820:10:04: BGP(4): charge penalty for 49.0404 path 65202 65404 with halflife-time 15reuse/suppress 750/200020:10:04: BGP(4): flapped 3 times since 00:02:44. New penalty is 283920:10:48: BGP(4): suppress 49.0404 path 65202 65404 for 00:28:10 (penalty 2752)20:10:48: halflife-time 15, reuse/suppress 750/2000Table 40 describes the significant fields shown in the display.
Related Commands
debug bgp nsap
Displays debug messages for BGP NSAP packets.
debug bgp nsap updates
Displays debug messages for BGP NSAP update events.
debug bgp nsap updates
To display debug messages for Border Gateway Protocol (BGP) network service access point (NSAP) prefix address update packets, use the debug bgp nsap updates command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bgp nsap updates [ip-address] [in | out] [filter-set clns-filter-set-name]
no debug bgp nsap updates [ip-address] [in | out] [filter-set clns-filter-set-name]
Syntax Description
Command Default
Debugging for BGP NSAP prefix update packets is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bgp nsap updates command is similar to the debug ip bgp updates command, except that it is specific to the NSAP address family.
Use the ip-address argument to display the BGP update debug messages for a specific BGP neighbor. Use the clns-filter-set-name argument to display the BGP update debug messages for a specific NSAP prefix.
Note
Examples
The following example shows output for the debug bgp nsap updates command:
Router# debug bgp nsap updates02:13:45: BGP(4): 10.0.3.4 send UPDATE (format) 49.0101, next 49.0303.3333.3333.3333.3333.00, metric 0, path 65202 6510102:13:45: BGP(4): 10.0.3.4 send UPDATE (format) 49.0202, next 49.0303.3333.3333.3333.3333.00, metric 0, path 6520202:13:45: BGP(4): 10.0.3.4 send UPDATE (format) 49.0303, next 49.0303.3333.3333.3333.3333.00, metric 0, path02:13:45: BGP(4): 10.0.2.2 send UPDATE (format) 49.0404, next 49.0303.3333.3333.3333.3333.00, metric 0, path 65404Table 41 describes the significant fields shown in the display.
Related Commands
debug bgp nsap
Displays debug messages for BGP NSAP packets.
debug bgp nsap dampening
Displays debug messages for BGP NSAP prefix dampening events.
debug bgp vpnv6 unicast
To display Border Gateway Protocol (BGP) virtual private network (VPN) debugging output, use the debug bgp vpnv6 unicast command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bgp vpnv6 unicast
no debug bgp vpnv6
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug bgp vpnv6 unicast command to help troubleshoot the BGP VPN.
Note
Examples
The following example enables BGP debugging output for IPv6 VPN instances:
Router# debug bgp vpnv6 unicastdebug bri-interface
To display debugging information on ISDN BRI routing activity, use the debug bri-interface command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bri-interface
no debug bri-interface
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The debug bri-interface command indicates whether the ISDN code is enabling and disabling the B channels when attempting an outgoing call. This command is available for the low-end router products that have a multi-BRI network interface module installed.
Caution
Examples
The following is sample output from the debug bri-interface command:
Router# debug bri-interfaceBRI: write_sid: wrote 1B for subunit 0, slot 1.BRI: write_sid: wrote 15 for subunit 0, slot 1.BRI: write_sid: wrote 17 for subunit 0, slot 1.BRI: write_sid: wrote 6 for subunit 0, slot 1.BRI: write_sid: wrote 8 for subunit 0, slot 1.BRI: write_sid: wrote 11 for subunit 0, slot 1.BRI: write_sid: wrote 13 for subunit 0, slot 1.BRI: write_sid: wrote 29 for subunit 0, slot 1.BRI: write_sid: wrote 1B for subunit 0, slot 1.BRI: write_sid: wrote 15 for subunit 0, slot 1.BRI: write_sid: wrote 17 for subunit 0, slot 1.BRI: write_sid: wrote 20 for subunit 0, slot 1.BRI: Starting Power Up timer for unit = 0.BRI: write_sid: wrote 3 for subunit 0, slot 1.BRI: Starting T3 timer after expiry of PUP timeout for unit = 0, current state is F4.BRI: write_sid: wrote FF for subunit 0, slot 1.BRI: Activation for unit = 0, current state is F7.BRI: enable channel B1BRI: write_sid: wrote 14 for subunit 0, slot 1.%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up.!!!BRI: disable channel B1BRI: write_sid: wrote 15 for subunit 0, slot 1.%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to down%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to down%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0: B-Channel 1, changed state to downThe following line indicates that an internal command was written to the interface controller. The subunit identifies the first interface in the slot.
BRI: write_sid: wrote 1B for subunit 0, slot 1.The following line indicates that the power-up timer was started for the named unit:
BRI: Starting Power Up timer for unit = 0.The following lines indicate that the channel or the protocol on the interface changed state:
%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up.!!!%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0: B-Channel 1, changed state to downThe following line indicates that the channel was disabled:
BRI: disable channel B1Lines of output not described are for use by support staff only.
Related Commands
debug bsc event
To display all events occurring in the Binary Synchronous Communications (Bisync) feature, use the debug bsc event command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bsc event [number]
no debug bsc event [number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
This command traces all interfaces configured with a bsc protocol-group number command.
Examples
The following is sample output from the debug bsc event command:
Router# debug bsc eventBSC: Serial2 POLLEE-FSM inp:E_LineFail old_st:CU_Down new_st:TCU_EOFileBSC: Serial2 POLLEE-FSM inp:E_LineFail old_st:CU_Down new_st:TCU_EOFileBSC: Serial2 POLLEE-FSM inp:E_LineFail old_st:CU_Down new_st:TCU_EOFile0:04:32: BSC: Serial2 :SDI-rx: 9 bytesBSC: Serial2 POLLEE-FSM inp:E_RxEtx old_st:CU_Down new_st:TCU_EOFile0:04:32: BSC: Serial2 :SDI-rx: 5 bytesBSC: Serial2 POLLEE-FSM inp:E_RxEnq old_st:CU_Down new_st:TCU_EOFileBSC: Serial2 POLLEE-FSM inp:E_Timeout old_st:CU_Down new_st:TCU_InFileBSC: Serial2 POLLEE-FSM inp:E_Timeout old_st:CU_Idle new_st:TCU_InFile%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2, changed state to up%LINK-3-UPDOWN: Interface Serial2, changed state to upBSC: Serial2 POLLEE-FSM inp:E_Timeout old_st:CU_Idle new_st:TCU_InFile0:04:35: BSC: Serial2 :SDI-rx: 9 bytesBSC: Serial2 POLLEE-FSM inp:E_RxEtx old_st:CU_Idle new_st:TCU_InFile0:04:35: BSC: Serial2 :SDI-rx: 5 bytesBSC: Serial2 POLLEE-FSM inp:E_RxEnq old_st:CU_Idle new_st:TCU_InFile0:04:35: BSC: Serial2 :NDI-rx: 3 bytesRelated Commands
debug bsc packet
Displays all frames traveling through the Bisync feature.
debug bstun events
Displays BSTUN connection events and status.
debug bsc packet
To display all frames traveling through the Binary Synchronous Communications (Bisync) feature, use the debug bsc packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bsc packet [group number] [buffer-size bytes]
no debug bsc packet [group number] [buffer-size bytes]
Syntax Description
group number
(Optional) Group number.
buffer-size bytes
(Optional) Number of bytes displayed per packet (defaults to 20).
Defaults
The default number of bytes displayed is 20.
Command Modes
Privileged EXEC
Usage Guidelines
This command traces all interfaces configured with a bsc protocol-group number command.
Examples
The following is sample output from the debug bsc packet command:
Router# debug bsc packet0:23:33: BSC: Serial2 :NDI-rx : 27 bytes 401A400227F5C31140C11D60C8C5D3D3D51D40130:23:33: BSC: Serial2 :SDI-tx : 12 bytes 00323237FF3232606040402D0:23:33: BSC: Serial2 :SDI-rx : 2 bytes 10700:23:33: BSC: Serial2 :SDI-tx : 27 bytes 401A400227F5C31140C11D60C8C5D3D3D51D40130:23:33: BSC: Serial2 :SDI-rx : 2 bytes 10610:23:33: BSC: Serial2 :SDI-tx : 5 bytes 00323237FFRelated Commands
debug bsc event
Displays all events occurring in the Bisync feature.
debug bstun events
Displays BSTUN connection events and status.
debug bstun events
To display BSTUN connection events and status, use the debug bstun events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bstun events [number]
no debug bstun events [number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
When you enable the debug bstun events command, messages showing connection establishment and other overall status messages are displayed.
You can use the debug bstun events command to assist you in determining whether the BSTUN peers are configured correctly and are communicating. For example, if you enable the debug bstun packet command and you do not see any packets, you may want to enable event debugging.
Note
Examples
The following is sample output from the debug bstun events command of keepalive messages working correctly. If the routers are configured correctly, at least one router will show reply messages.
Router# debug bstun eventsBSTUN: Received Version Reply opcode from (all[2])_172.16.12.2/1976 at 1360BSTUN: Received Version Request opcode from (all[2])_172.16.12.2/1976 at 1379BSTUN: Received Version Reply opcode from (all[2])_172.16.12.2/1976 at 1390
Note
The following is sample output from the debug bstun events output of an event trace in which the wrong TCP address has been specified for the remote peer. These are non-keepalive related messages.
Router# debug bstun eventsBSTUN: Change state for peer (C1[1])172.16.12.22/1976 (closed->opening)BSTUN: Change state for peer (C1[1])172.16.12.22/1976 (opening->open wait)%BSTUN-6-OPENING: CONN: opening peer (C1[1])172.16.12.22/1976, 3BSTUN: tcpd sender in wrong state, dropping packetBSTUN: tcpd sender in wrong state, dropping packetBSTUN: tcpd sender in wrong state, dropping packetRelated Commands
debug bstun packet
To display packet information on packets traveling through the BSTUN links, use the debug bstun packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bstun packet [group number] [buffer-size bytes]
no debug bstun packet [group number] [buffer-size bytes]
Syntax Description
group number
(Optional) BSTUN group number.
buffer-size bytes
(Optional) Number of bytes displayed per packet (defaults to 20).
Defaults
The default number of bytes displayed is 20.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug bstun packet command:
Router# debug bstun packetBSTUN bsc-local-ack: 0:00:00 Serial2 SDI: Addr: 40 Data: 02C1C1C1C1C1C1C1C1C1BSTUN bsc-local-ack: 0:00:00 Serial2 SDI: Addr: 40 Data: 02C1C1C1C1C1C1C1C1C1BSTUN bsc-local-ack: 0:00:06 Serial2 NDI: Addr: 40 Data: 0227F5C31140C11D60C8Related Commands
debug bundle errors
To enable the display of information on bundle errors, use the debug bundle errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bundle errors
no debug bundle errors
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to enable the display of error information for a bundle, such as reports of inconsistent mapping in the bundle.
Related Commands
debug bundle events
To enable display of bundle events when use occurs, use the debug bundle events command in privileged EXEC mode. To disable the display, use the no form of this command.
debug bundle events
no debug bundle events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to enable the display of bundle events, such as occurrences of VC bumping, when bundles were brought up, when they were taken down, and so forth.
Related Commands
debug callback
To display callback events when the router is using a modem and a chat script to call back on a terminal line, use the debug callback command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug callback
no debug callback
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
This command is useful for debugging chat scripts on PPP and AppleTalk Remote Access Protocol (ARAP) lines that use callback mechanisms. The output provided by the debug callback command shows you how the call is progressing when used with the debug ppp or debug arap commands.
Examples
The following is sample output from the debug callback command:
Router# debug callbackTTY7 Callback process initiated, user: exec_test dialstring 123456TTY7 Callback forced wait = 4 secondsTTY7 Exec Callback Successful - await exec/autoselect pickupTTY7: Callback in effectRelated Commands
debug cable env
Displays ARAP events.
debug ppp
Displays information on traffic and exchanges in an internetwork implementing the PPP.
debug call fallback detail
To display details of the call fallback, use the debug call fallback detail command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call fallback detail
no debug call fallback detail
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Every time a call request is received, the debug call fallback detail command displays in the command-line interface (CLI) cache lookup and call acceptance/rejection information. Use this command to monitor call requests as they enter the call fallback subsystem.
If you have a large amount of calls in your router, enabling this command can cause delays in your routing functions as the debug statistics are constantly compiled and sent to your terminal. Also, debug messages on your terminal may make for difficult CLI configuring.
Examples
The following example depicts a call coming in to 10.1.1.4 with codec g729r8. Because there is no cache entry for this destination, a probe is sent and values are inserted into the cache. A lookup is performed again, entry is found, and a fallback decision is made to admit the call.
Router# debug call fallback detailWhen cache is empty:debug call fallback detail:2d19h:fb_lookup_cache:10.1.1.4, codec:g729r82d19h:fb_lookup_cache:No entry found.2d19h:fb_check:no entry exists, enqueueing probe info... 10.1.1.4, codec:g729r82d19h:fb_main:Got FB_APP_INQ event2d19h:fb_main:Dequeued prob info: 10.1.1.4, codec:g729r82d19h:fb_lookup_cache:10.1.1.4, codec:g729r82d19h:fb_lookup_cache:No entry found.2d19h:fb_cache_insert:insert:10.1.1.4, codec:g729r82d19h:fb_cache_insert:returning entry:10.1.1.4, codec:g729r82d19h:fb_initiate_probe:Creating probe... 10.1.1.4, codec:g729r82d19h:fb_initiate_probe:Created and started on probe #13, 10.1.1.4, codec:g729r82d19h:fb_lookup_cache:10.1.1.4, codec:g729r82d19h:fb_lookup_cache:Found entry.2d19h:fb_check:returned FB_CHECK_TRUE, 10.1.1.4, codec:g729r82d19h:fb_main:calling callback function with:TRUEThe following example depicts a call coming in to 10.1.1.4 with codec g729r8. A lookup is performed, entry is found, and a fallback decision is made to admit the call.
Router# debug call fallback detailWhen cache is full:2d19h:fb_lookup_cache:10.1.1.4, codec:g729r82d19h:fb_lookup_cache:Found entry.2d19h:fb_check:returned FB_CHECK_TRUE, 10.1.1.4, codec:g729r82d19h:fb_main:calling callback function with:TRUEdebug call fallback probe
To display details of the call fallback probes, use the debug call fallback probe command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call fallback probe
no debug call fallback probe
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Every time a probe is received, the debug call fallback probe command displays in the command-line interface (CLI) network traffic information collected by the probe. Use this command to monitor the network traffic information the probes carry as they enter the call fallback subsystem and log cache entries.
If you have frequent return of probes to your router, enabling this command can cause delays in your routing functions as the debug statistics are constantly compiled and sent to your terminal. Also, debug messages on your terminal may make for difficult CLI configuring.
Examples
The following example depicts a call coming in to 10.1.1.4 and codec type g729r8. Because there is no cache entry for this IP address, a g729r8 probe is initiated. The probe consists of 20 packet returns with an average delay of 43 milliseconds. The "jitter out" is jitter from source to destination router and "jitter in" is jitter from destination to source router. The delay, loss, and Calculated Planning Impairment Factor (ICPIF) values following g113_calc_icpif are the instantaneous values, whereas those values following "New smoothed values" are the values after applying the smoothing with weight 65.
Router# debug call fallback probe2d19h:fb_initiate_probe:Probe payload is 322d19h:fb_main:NumOfRTT=20, RTTSum=120, loss=0, delay=43, jitter in=0, jitter out=0-> 10.1.1.4, codec:g729r82d19h:g113_calc_icpif(delay (w/codec delay)=43, loss=0, expect_factor=10) Icpif=02d19h:fb_main:Probe timer expired, 10.1.1.4, codec:g729r82d19h:fb_main:NumOfRTT=20, RTTSum=120, loss=0, delay=43, jitter in=0, jitter out=0-> 10.1.1.4, codec:g729r82d19h:g113_calc_icpif(delay (w/codec delay)=43, loss=0, expect_factor=10) Icpif=02d19h:fb_main:New smoothed values:inst_weight=65, ICPIF=0, Delay=43, Loss=0 -> 10.1.1.4, codec:g729r8debug call filter detail
To display details of the debug trace inside the generic call filter module (GCFM), use the debug call filter detail command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call filter detail
no debug call filter detail
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following sample output from the debug call filter detail command shows the detailed activity of the GCFM, which is the internal module that controls the debug filtering.
Router# debug call filter detail5d18h: gcfm_call_get_hash_address: hashtable index = 3455d18h: gcfm_call_search_hash:no found5d18h: gcfm_init_call_record:5d18h: gcfm_init_percall_matchlist:5d18h: === list 1: service_state=2, callp's: 05d18h: gcfm_call_get_hash_address: hashtable index = 3455d18h: gcfm_call_enlist: count before this enlist 0 on 624D60005d18h: gcfm_call_enlist: tail is empty guid=C2E4C789-214A-11D4-804C-000A8A389BA85d18h: gcfm_call_get_hash_address: hashtable index = 3455d18h: gcfm_call_search_hash: search requested guid=C2E4C789-214A-11D4-804C-000A8A389BA8 vs the entry guid=C2E4C789-214A-11D4-804C-000A8A389BA85d18h: gcfm_call_search_hash: found5d18h: gcfm_update_percall_condlist_context:5d18h: gcfm_update_percall_condlist_context: check cond = 25d18h: gcfm_copy_match_cond:5d18h: gcfm_update_cond_through_matchlist:5d18h: gcfm_check_percond_with_matchlist: check match-list 15d18h: gcfm_matchlist_percond_check:5d18h: gcfm_matchlist_percond_check: check cond=25d18h: gcfm_matchlist_percond_check: compare 42300 to configured 423005d18h: gcfm_check_cond_tel_number:5d18h: gcfm_check_cond_tel_number: matched5d18h: gcfm_matchlist_percond_check: checked result is 15d18h: gcfm_is_bitfield_identical:5d18h: gcfm_update_cond_through_matchlist: service=1, percallmatchlist tag=1,current_status = 1, service_filter=05d18h: gcfm_percall_notify_condition: not linked call recordTable 42 describes the significant fields shown in the display.
Related Commands
debug call filter inout
To display the debug trace inside the generic call filter module (GCFM), use the debug call filter inout command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call filter inout
no debug call filter inout
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following sample output from the debug call filter inout command shows the incoming and outgoing activity of the GCFM, which is the internal module that controls the debug filtering.
Router# debug call filter inout5d18h: gcfm_generate_guid: component ISDN gets guid5d18h: gcfm_percall_register: component ISDN5d18h: gcfm_percall_register: component ISDN return selected=05d18h: gcfm_percall_notify_condition: component ISDN for sync=15d18h: gcfm_percall_notify_condition: component ISDN successfully selected = 05d18h: gcfm_check_percall_status: component TGRM5d18h: gcfm_check_percall_status: component TGRM return selected=05d18h: gcfm_check_percall_status: component TGRM5d18h: gcfm_check_percall_status: component TGRM return selected=05d18h: gcfm_percall_register: component VTSP5d18h: gcfm_percall_register: component VTSP for return selected value 05d18h: gcfm_percall_notify_condition: component VTSP for sync=15d18h: gcfm_percall_notify_condition: component VTSP successfully selected = 05d18h: gcfm_percall_register: component CCAPI5d18h: gcfm_percall_register: component CCAPI for return selected value 05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=05d18h: gcfm_percall_register: component VOICE-IVR-V25d18h: gcfm_percall_register: component VOICE-IVR-V2 for return selected value 05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=05d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_percall_register: component CCAPI5d18h: gcfm_percall_register: component CCAPI for return selected value 05d18h: gcfm_percall_register: component VOICE-IVR-V25d18h: gcfm_percall_register: component VOICE-IVR-V2 for return selected value 05d18h: gcfm_percall_notify_condition: component VOICE-IVR-V2 for sync=15d18h: gcfm_percall_notify_condition: component VOICE-Router#IVR-V2 successfully selected = 15d18h: gcfm_percall_register: component H3235d18h: gcfm_percall_register: component H323 for return selected value 15d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=15d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=15d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=15d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=15d18h: gcfm_clear_condition: component VOICE-IVR-V25d18h: gcfm_clear_condition: component VOICE-IVR-V2 successfully5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=05d18h: gcfm_percall_deregister: component CCAPI5d18h: gcfm_percall_deregister: component CCAPI successfully5d18h: gcfm_percall_deregister: component H3235d18h: gcfm_percall_deregister: component H323 successfully5d18h: gcfm_percall_deregister: component ISDN5d18h: gcfm_percall_deregister: component ISDN successfully5d18h: gcfm_percall_deregister: component VOICE-IVR-V25d18h: gcfm_percall_deregister: component VOICE-IVR-V2 successfully5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=05d18h: gcfm_percall_deregister: component CCAPI5d18h: gcfm_percall_deregister: component CCAPI successfully5d18h: gcfm_percall_deregister: component VTSP5d18h: gcfm_percall_deregister: component VTSP successfully5d18h: gcfm_percall_deregister: component VOICE-IVR-V25d18h: gcfm_terminate_track_guid: component VOICE-IVR-V2 terminate, success5d18h: gcfm_percall_deregister: component VOICE-IVR-V2 successfullyTable 43 describes the significant fields shown in the display.
Related Commands
debug call-mgmt
To display debugging information for call accounting, including modem and time slot usage, for active and recent calls, use the debug call-mgmt command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call-mgmt
no debug call-mgmt
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output after the debug call-mgmt command has been enabled:
Router# debug call-mgmtCall Management debugging is onRouter#Dec 26 13:57:27.710: msg_to_calls_mgmt: msg type CPM_NEW_CALL_CSM_CONNECT receivedDec 26 13:57:27.714: In actv_c_proc_message,access type CPM_INSERT_NEW_CALL,call type CPM_ISDN_ANALOG:CSM completed connecting a new modem call...Dec 26 13:57:45.906: msg_to_calls_mgmt: msg type CPM_NEW_CALL_ISDN_CONNECT receivedDec 26 13:57:45.906: In actv_c_proc_message,access type CPM_INSERT_NEW_CALL,call type CPM_ISDN_ANALOG:Added a new ISDN analog call to the active-calls listCC-Slot#7, DSX1-Ctrlr#17, DS0-Timeslot#1Mdm-Slot#1, Mdm-Port#3, TTY#219...Dec 26 13:58:25.682: Call mgmt per minute statistics:active list length: 1history list length: 3Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 1Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 2Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 3Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 4Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 5Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 6Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 7Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 8Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 9Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 10Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 11Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 12Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 13Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 14Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 15Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 16Dec 26 13:58:25.686: 1 timeslots active at slot 7, ctrlr 17Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 18Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 19Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 20Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 21Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 22Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 23Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 24Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 25Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 26Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 27Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 28Router# clear int as1/03Dec 26 13:58:26.538: msg_to_calls_mgmt: msg type CPM_VOICE_CALL_REJ_NO_MOD_AVAIL receivedDec 26 13:58:26.538: In actv_c_proc_message,access type CPM_REMOVE_DISC_CALL,call type CPM_ISDN_ANALOG:Removed a disconnected ISDN analog callCC-Slot#7, DSX1-Ctrlr#17, DS0-Timeslot#1Dec 26 13:58:26.538: Mdm-Slot#1, Mdm-Port#3, TTY#219Table 44 describes the significant fields shown in the display.
debug call rsvp-sync events
To display events that occur during Resource Reservation Protocol (RSVP) setup, use the debug call rsvp-sync events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call rsvp-sync events
no debug call rsvp-sync events
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
It is highly recommended that you log the output from the debug call rsvp-sync events command to a buffer, rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Examples
The following example shows a portion of sample output for a call initiating RSVP when using the debug call rsvp-sync events command:
00:03:25: Parameters: localip: 10.19.101.117 :localport: 1666000:03:25: Parameters: remoteip: 10.19.101.116 :remoteport: 1756800:03:25: QoS Primitive Event for Call id 0x1 : QoS Listen00:03:25: Lookup to be done on hashkey 0x1 in hash table 0x61FC249800:03:25: Hashed entry 0x1 in call table 0x61FC249800:03:25: Entry Not found00:03:25: Parameters: localip: 10.19.101.11700:03:25: remoteip: 10.19.101.11600:03:25: QoSpcb : 0x61FC34D800:03:25: Response Status : 0Starting timer for call with CallId 0x1 for 10000 secs00:03:25: Handling QoS Primitive QoS Listen00:03:25: Establishing RSVP RESV state : rsvp_request_reservation()00:03:25: For streams from 10.19.101.116:17568 to 10.19.101.117:1666000:03:25: RSVP Confirmation required00:03:25: QoS Primitive Event for Call id 0x1 : QoS Resv00:03:25: Lookup to be done on hashkey 0x1 in hash table 0x61FC249800:03:25: Hashed entry 0x1 in call table 0x61FC249800:03:25: Initiating RVSP PATH messages to be Sent : reg_invoke_rsvp_advertise_sender()00:03:25: Advertizing for streams to 10.19.101.116:17568 from 10.19.101.117:1666000:03:25: RESV notification event received is : 200:03:25: Received RESVCONFIRM00:03:25: RESV CONFIRM message received from 10.19.101.116 for RESV setup from 10.19.101.11700:03:25: RESV event received is : 000:03:25: RESV message received from 10.19.101.116:17568 for streams from 10.19.101.117:1666000:03:25: RESERVATIONS ESTABLISHED : CallId: 1 Stop timer and notify Session Protocol of Success (ie. if notification requested)00:03:25: Invoking spQoSresvCallback with SuccessRelated Commands
debug call rsvp-sync func-trace
To display messages about software functions called by Resource Reservation Protocol (RSVP), use the debug call rsvp-sync func-trace command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call rsvp-sync func-trace
no debug call rsvp-sync func-trace
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
It is highly recommended that you log the output from the debug call rsvp-sync func-trace command to a buffer, rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Examples
The following example shows a portion of sample output for a call initiating RSVP when using the debug call rsvp-sync func-trace command in conjunction with the debug call rsvp-sync events command:
00:03:41: Entering Function QoS_Listen00:03:41: Parameters:localip:10.10.101.116 :localport:1756800:03:41:remoteip:10.10.101.117 :remoteport:000:03:41: Entering Function qos_dequeue_event00:03:41: Entering Function process_queue_event00:03:41: QoS Primitive Event for Call id 0x2 :QoS Listen00:03:41: Entering Function get_pcb00:03:41: Entering Function hash_tbl_lookup00:03:41:Lookup to be done on hashkey 0x2 in hash table 0x61FAECD800:03:41: Entering Function hash_func00:03:41:Hashed entry 0x2 in call table 0x61FAECD800:03:41:Entry Not found00:03:41: Entering Function qos_dequeue_pcb00:03:41: Entering Function qos_initialize_pcb00:03:41: Parameters:localip:10.10.101.11600:03:41: remoteip:10.10.101.11700:03:41: QoSpcb :0x61FAFD1800:03:41: Response Status :000:03:41: Entering Function hash_tbl_insert_entry00:03:41: Entering Function hash_func00:03:41: Handling QoS Primitive QoS Listen00:03:41: Entering Function qos_dequeue_hash_port_entry00:03:41: Entering Function qos_port_tbl_insert_entry00:03:41: Entering Function hash_func00:03:41: Doing RSVP Listen :rsvp_add_ip_listen_api()Related Commands
debug call threshold
To see details of the trigger actions, use the debug call threshold command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call threshold module
no debug call threshold
Syntax Description
module
The module argument can be one of the following:
•
•
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug call threshold core command:Router# debug call threshold coreRSCCAC Core info debugging is onThe following is sample output from the debug call threshold detail command:
Router# debug call threshold detailAll RSCCAC info debugging is ondebug call treatment action
To debug the call treatment actions, use the debug call treatment action command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call treatment action
no debug call treatment action
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Examples
Debug actions are performed on calls by call treatment. The following sample output shows that call treatment is turned on:
Router# debug call treatment actionCall treatment action debugging is ondebug capf-server
To collect debug information about the CAPF server, use the debug capf-server command in privileged EXEC mode. To disable collection of debug information, use the no form of this command.
debug capf-server {all | error | events | messages}
no debug capf-server
Syntax Description
all
Collect all CAPF information available.
error
Collect only information about CAPF errors.
events
Collect only information about CAPF status events.
messages
Collect only CAPF system messages.
Command Default
Collection of CAPF debug information is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is used with Cisco Unified CallManager Express phone authentication.
Examples
The following example shows debug messages for the CAPF server.
Router# debug capf-server all001891: .Jul 21 18:17:07.014: %IPPHONE-6-UNREGISTER_NORMAL: ephone-1:SEP000E325C9A43 IP:10.10.10.194 Socket:3 DeviceType:Phone has unregistered normally.001892: .Jul 21 18:17:20.495: New Connection from phone, socket 1001893: .Jul 21 18:17:20.495: Created New Handshake Process001894: .Jul 21 18:17:20.499: SSL Handshake Error -6983001895: .Jul 21 18:17:21.499: SSL Handshake Error -6983001896: .Jul 21 18:17:22.555: SSL Handshake Successful001897: .Jul 21 18:17:22.555: ephone_capf_send_auth_req:001898: .Jul 21 18:17:22.555: ephone_capf_ssl_write: 12 bytes001899: .Jul 21 18:17:22.711: ephone_capf_ssl_read: Read 35 bytes001900: .Jul 21 18:17:22.711: ephone_capf_handle_phone_msg: msgtype 2001901: .Jul 21 18:17:22.711: ephone_capf_process_auth_res_msg: SEP000E325C9A43 AuthMode 2001902: .Jul 21 18:17:22.711: ephone_capf_send_delete_cert_req_msg: SEP000E325C9A43001903: .Jul 21 18:17:22.711: ephone_capf_ssl_write: 8 bytes001904: .Jul 21 18:17:23.891: ephone_capf_ssl_read: Read 12 bytes001905: .Jul 21 18:17:23.891: ephone_capf_handle_phone_msg: msgtype 14001906: .Jul 21 18:17:23.891: certificate delete successful for SEP000E325C9A43001907: .Jul 21 18:17:24.695: ephone_capf_release_session: SEP000E325C9A43001908: .Jul 21 18:17:24.695: ephone_capf_send_end_session_msg: SEP000E325C9A43001909: .Jul 21 18:17:24.695: ephone_capf_ssl_write: 12 bytes001910: .Jul 21 18:17:25.095: %IPPHONE-6-REG_ALARM: 22: Name=SEP000E325C9A43 Load=7.2(2.0) Last=Reset-Reset001911: .Jul 21 18:17:25.099: %IPPHONE-6-REGISTER: ephone-1:SEP000E325C9A43 IP:10.10.10.194 Socket:2 DeviceType:Phone has registered.001912: .Jul 21 18:18:05.171: %IPPHONE-6-UNREGISTER_NORMAL: ephone-1:SEP000E325C9A43 IP:1.1.1.127 Socket:2 DeviceType:Phone has unregistered normally.001913: .Jul 21 18:18:18.288: New Connection from phone, socket 1001914: .Jul 21 18:18:18.288: Created New Handshake Process001915: .Jul 21 18:18:18.292: SSL Handshake Error -6983001916: .Jul 21 18:18:19.292: SSL Handshake Error -6983001917: .Jul 21 18:18:20.348: SSL Handshake Successful001918: .Jul 21 18:18:20.348: ephone_capf_send_auth_req:001919: .Jul 21 18:18:20.348: ephone_capf_ssl_write: 12 bytes^Z001920: .Jul 21 18:18:20.492: ephone_capf_ssl_read: Read 35 bytes001921: .Jul 21 18:18:20.492: ephone_capf_handle_phone_msg: msgtype 2001922: .Jul 21 18:18:20.492: ephone_capf_process_auth_res_msg: SEP000E325C9A43 AuthMode 2001923: .Jul 21 18:18:20.492: ephone_capf_send_PhKeyGenReq_msg: SEP000E325C9A43 KeySize 1024001924: .Jul 21 18:18:20.492: ephone_capf_ssl_write: 13 bytes001925: .Jul 21 18:18:20.540: ephone_capf_ssl_read: Read 8 bytes001926: .Jul 21 18:18:20.540: ephone_capf_handle_phone_msg: msgtype 17001927: .Jul 21 18:18:20.540: ephone_capf_process_req_in_progress: SEP000E325C9A43 delay 0sh001928: .Jul 21 18:18:21.924: %SYS-5-CONFIG_I: Configured from console by user1 on consoledebug cas
To debug channel-associated signaling (CAS) messages and to debug the establishment of a time-division multiplexing (TDM) connection between a DS0 and a digital modem, use the debug cas command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cas slot slot number port port number
no debug cas slot slot number port port number
Syntax Description
slot slot number
Slot and slot number. Valid values are 0 and 1.
port port number
Port and port number. Valid values are 0 and 1.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When the NM-xCE1T1PRI network module is used with an NM-xDM and a DS0-group is configured under the controller, you can use the debug cas command to debug CAS signaling messages and the establishment of a TDM connection between a DS0 and a digital modem. Use the debug cas command to identify and troubleshoot call connection problems on a T1/E1 interface. With this command, you can trace the complete sequence of incoming and outgoing calls.
Examples
The following shows an example session to enable debugging CAS and generate troubleshooting output:
Router# show debugRouter# debug cas slot 1 port 0CAS debugging is onRouter#debug-cas is on at slot(1) dsx1(0)Router# show debugCAS debugging is onThe following example shows output for the first outgoing call:
Router# p 1.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:*Mar 2 00:17:45: dsx1_alloc_cas_channel: channel 0 dsx1_timeslot1(0/0): TX SEIZURE (ABCD=0001)(0/0): RX SEIZURE_ACK (ABCD=1101)(0/1):RX_IDLE (ABCD=1001)(0/2): RX_IDLE (ABCD=1001)(0/3): RX_IDLE(ABCD=1001)(0/4): RX_IDLE (ABCD=1001)(0/5): RX_IDLE (ABCD=1001)(0/6):RX_IDLE (ABCD=1001)(0/7): RX_IDLE (ABCD=1001)(0/8): RX_IDLE(ABCD=1001)(0/9): RX_IDLE (ABCD=1001)(0/10): RX_IDLE (ABCD=1001)(0/11):RX_IDLE (ABCD=1001)(0/12): RX_IDLE (ABCD=1001)(0/13): RX_IDLE(ABCD=1001)(0/14): RX_IDLE (ABCD=1001)(0/16): RX_IDLE (ABCD=1001)(0/17):RX_IDLE (ABCD=1001)(0/18): RX_IDLE (ABCD=1001)(0/19): RX_IDLE(ABCD=1001)(0/20): RX_IDLE (ABCD=1001)(0/21): RX_IDLE(ABCD=1001).(0/22): RX_IDLE (ABCD=1001)(0/23): RX_IDLE(ABCD=1001)(0/24): RX_IDLE (ABCD=1001)(0/25): RX_IDLE (ABCD=1001)(0/26):RX_IDLE (ABCD=1001)(0/27): RX_IDLE (ABCD=1001)(0/28): RX_IDLE(ABCD=1001)(0/29): RX_IDLE (ABCD=1001)(0/30): RX_IDLE(ABCD=1001)...(0/0): RX ANSWERED (ABCD=0101).Success rate is 0 percent (0/5)Router#*Mar 2 00:18:13.333: %LINK-3-UPDOWN: Interface Async94, changed state to up*Mar 2 00:18:13.333: %DIALER-6-BIND: Interface As94 bound to profile Di1*Mar 2 00:18:14.577: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async94, changed state to upRouter# p 1.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 160/180/236 msThe following example shows that the call is cleared on the router:
Router# clear int dialer 1Router#(0/0): TX IDLE (ABCD=1001)(0/0): RX IDLE (ABCD=1001)*Mar 2 00:18:28.617: %LINK-5-CHANGED: Interface Async94, changed state to reset*Mar 2 00:18:28.617: %DIALER-6-UNBIND: Interface As94 unbound from profile Di1*Mar 2 00:18:29.617: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async94, changed state to downet2-c3745-1#*Mar 2 00:18:33.617: %LINK-3-UPDOWN: Interface Async94, changed state to downThe following example shows a subsequent outbound CAS call:
Router# p 1.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:*Mar 2 00:18:40: dsx1_alloc_cas_channel: channel 5 dsx1_timeslot6(0/5): TX SEIZURE (ABCD=0001)(0/5): RX SEIZURE_ACK(ABCD=1101)....(0/5): RX ANSWERED (ABCD=0101).Success rate is 0 percent (0/5)Router#*Mar 2 00:19:08.841: %LINK-3-UPDOWN: Interface Async93, changed state to up*Mar 2 00:19:08.841: %DIALER-6-BIND: Interface As93 bound to profile Di1*Mar 2 00:19:10.033: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async93, changed state to upRouter# p 1.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 160/167/176msThe following example shows the call cleared by the switch:
Router#(0/5): TX IDLE (ABCD=1001)(0/5): RX IDLE (ABCD=1001)*Mar 2 00:19:26.249: %LINK-5-CHANGED: Interface Async93, changed state to reset*Mar 2 00:19:26.249: %DIALER-6-UNBIND: Interface As93 unbound from profile Di1*Mar 2 00:19:27.249: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async93, changed state to downRouter#*Mar 2 00:19:31.249: %LINK-3-UPDOWN: Interface Async93, changed state to downThe following example shows an incoming CAS call:
Router#(0/0): RX SEIZURE (ABCD=0001)*Mar 2 00:22:40: dsx1_alloc_cas_channel: channel 0 dsx1_timeslot1(0/0): TX SEIZURE_ACK (ABCD=1101)(0/0): TX ANSWERED (ABCD=0101)Router#*Mar 2 00:23:06.249: %LINK-3-UPDOWN: Interface Async83, changed state to up*Mar 2 00:23:06.249: %DIALER-6-BIND: Interface As83 bound to profile Di1*Mar 2 00:23:07.653: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async83, changed state to upRelated Commands
show debug
Displays information about the types of debugging that are enabled for your router.
debug ccaal2 session
To display the ccaal2 function calls during call setup and teardown, use the debug ccaal2 session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccaal2 session
no debug ccaal2 session
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging for ATM Adaptation Layer type 2 (AAL2) sessions is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command when troubleshooting an AAL2 trunk setup or teardown problem.
Examples
The following example shows sample output from the debug ccaal2 session command for a forced shutdown of a voice port:
Router# debug ccaal2 sessionCCAAL2 Session debugging is onRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# voice-port 2/0:0Router(config-voiceport)# shutdown00:32:45:ccaal2_call_disconnect:peer tag 000:32:45:ccaal2_evhandle_call_disconnect:Entered00:32:45:ccaal2_call_cleanup:freeccb 1, call_disconnected 100:32:45:starting incoming timer:Setting accept_incoming to FALSE and00:32:45:timer 2:(0x622F6270)starts - delay (70000)00:32:45:ccaal2_call_cleanup:Generating Call record00:32:45:cause=81 tcause=81 cause_text=unspecified00:32:45:ccaal2_call_cleanup:ccb 0x63FF1700, vdbPtr 0x62DFF2E0freeccb_flag=1, call_disconnected_flag=100:32:45:%LINK-3-UPDOWN:Interface recEive and transMit2/0:0(1),changed state to Administrative ShutdownThe following example shows sample output from the debug ccaal2 session command for a trunk setup on a voice port:
Router# debug ccaal2 sessionRouter(config-voiceport)# no shutdownRouter(config-voiceport)#00:35:28:%LINK-3-UPDOWN:Interface recEive and transMit2/0:0(1),changed state to up00:35:35:ccaal2_call_setup_request:Entered00:35:35:ccaal2_evhandle_call_setup_request:Entered00:35:35:ccaal2_initialize_ccb:preferred_codec set(-1)(0)00:35:35:ccaal2_evhandle_call_setup_request:preferred_codecset(5)(40). VAD is 100:35:35:ccaal2_call_setup_trunk:subchannel linkingsuccessfulccaal2_receive:xmitFunc is NULL00:35:35:ccaal2_caps_ind:PeerTag = 4900:35:35: codec(preferred) = 1, fax_rate = 2, vad = 200:35:35: cid = 56, config_bitmask = 258, codec_bytes = 40,signal_type=800:35:36:%HTSP-5-UPDOWN:Trunk port(channel) [2/0:0(1)] is upRouter(config-voiceport)#Related Commands
debug cce dp named-db urlfilter
To enable debug information of the Common Classification Engine Data-Plane (CCE DP) URL Filtering Classification module, use the debug cce dp named-db urlfilter command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cce dp named-db urlfilter
no debug cce dp named-db urlfilter
Syntax Description
This command has no keywords or arguments.
Command Default
No debugging information is generated for the the CCE DP URL Filtering Classification module.
Command Modes
Privileged EXEC (#)
Command History
12.4(15)XZ
This command was introduced.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Examples
The following is sample output from the debug cce dp named-db urlfilter command at the time that a URL request to the untrusted domain www.example.com was made:
Router# debug cce dp named-db urlfilterCCE DP Named DB URLF functionality debugging is onRouter#*Apr 4 10:38:08.043: CCE* FUNC: cce_dp_named_db_urlf_pkt_classify -- Didn't get token*Apr 4 10:38:08.043: CCE* FUNC: cce_dp_urlf_truncate_url -- Truncating URL upto script before sending to the trend for classification*Apr 4 10:38:08.043: CCE* FUNC: urlf_trend_find_cache_entry -- The host tree in bucket 1248 is empty*Apr 4 10:38:08.043: CCE* FUNC: cce_dp_named_db_urlf_pkt_classify -- Didn't find in cache*Apr 4 10:38:08.051: CCE FUNC: urlf_trend_store_response -- Host node with given domainname not found.*Apr 4 10:38:08.051: CCE FUNC: urlf_trend_store_response -- Create domain type cache entry.*Apr 4 10:38:08.051: CCE FUNC: cache_size_limit_check -- New cache size=73, existing cache size=0, cache size limit=131072000*Apr 4 10:38:08.051: CCE FUNC: create_domain_cache_entry -- Domain cache entry 0x65EE0ED0 created.*Apr 4 10:38:08.051: CCE FUNC: create_and_insert_domain_cache_entry --*Apr 4 10:38:08.051: Domain cache entry 0x65EE0ED0 created and inserted into host tree with root=0x65EE0ED0, root left=0x0, root right=0x0; new node left=0x0, new node right=0x0*Apr 4 10:38:08.051: CCE FUNC: cce_dp_named_db_urlf_gen_match_token -- pushing match-info token - class 0xC000000E; filter 45; category 21*Apr 4 10:38:08.051: CCE FUNC: cce_dp_named_db_urlf_non_pkt_classify -- Class 0x65C5D484 matched*Apr 4 17:38:08.051: %URLF-4-URL_BLOCKED: Access denied URL 'http://www.example.com/', client 1.0.0.118:3056 server 192.168.0.30:8080*Apr 4 10:38:08.055: CCE* FUNC: cce_dp_named_db_urlf_pkt_classify -- Didn't get token*Apr 4 10:38:08.055: CCE FUNC: cce_dp_named_db_urlf_pkt_classify -- Didn't get tokendebug ccfrf11 session
To display the ccfrf11 function calls during call setup and teardown, use the debug ccfrf11 session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccfrf11 session
no debug ccfrf11 session
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display debug information about the various FRF.11 VoFR service provider interface (SPI) functions. Note that this debug command does not display any information regarding the proprietary Cisco switched-VoFR SPI.
This debug is useful only when the session protocol is "frf11-trunk."
Examples
The following is sample output from the debug ccfrf11 session command:
Router# debug ccfrf11 sessionINCOMING CALL SETUP (port setup for answer-mode):*Mar 6 18:04:07.693:ccfrf11_process_timers:scb (0x60EB6040) timer (0x60EB6098) expired*Mar 6 18:04:07.693:Setting accept_incoming to TRUE*Mar 6 18:04:11.213:ccfrf11_incoming_request:peer tag 800:callingNumber=+2602100,calledNumber=+3622110*Mar 6 18:04:11.213:ccfrf11_initialize_ccb:preffered_codec set(-1)(0)*Mar 6 18:04:11.213:ccfrf11_evhandle_incoming_call_setup_request:calling +2602100,called +3622110 Incoming Tag 800*Mar 6 18:04:11.217:ccfrf11_caps_ind:PeerTag = 800*Mar 6 18:04:11.217: codec(preferred) = 4, fax_rate = 2, vad = 2*Mar 6 18:04:11.217: cid = 30, config_bitmask = 0, codec_bytes = 20, signal_type=2*Mar 6 18:04:11.217: required_bandwidth 8192*Mar 6 18:04:11.217:ccfrf11_caps_ind:Bandwidth reservation of 8192 bytes succeeded.*Mar 6 18:04:11.221:ccfrf11_evhandle_call_connect:EnteredCALL SETUP (MASTER):5d22h:ccfrf11_call_setup_request:Entered5d22h:ccfrf11_evhandle_call_setup_request:Entered5d22h:ccfrf11_initialize_ccb:preffered_codec set(-1)(0)5d22h:ccfrf11_evhandle_call_setup_request:preffered_codec set(9)(24)5d22h:ccfrf11_call_setup_trunk:subchannel linking successful5d22h:ccfrf11_caps_ind:PeerTag = 8105d22h: codec(preferred) = 512, fax_rate = 2, vad = 25d22h: cid = 30, config_bitmask = 1, codec_bytes = 24, signal_type=25d22h: required_bandwidth 65005d22h:ccfrf11_caps_ind:Bandwidth reservation of 6500 bytes succeeded.CALL TEARDOWN:*Mar 6 18:09:14.805:ccfrf11_call_disconnect:peer tag 0*Mar 6 18:09:14.805:ccfrf11_evhandle_call_disconnect:Entered*Mar 6 18:09:14.805:ccfrf11_call_cleanup:freeccb 1, call_disconnected 1*Mar 6 18:09:14.805:ccfrf11_call_cleanup:Setting accept_incoming to FALSE and startingincoming timer*Mar 6 18:09:14.809:timer 2:(0x60EB6098)starts - delay (70000)*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Alive timer stopped*Mar 6 18:09:14.809:timer 1:(0x60F64104) stops*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Generating Call record*Mar 6 18:09:14.809:cause=10 tcause=10 cause_text="normal call clearing."*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Releasing 8192 bytes of reserved bandwidth*Mar 6 18:09:14.809:ccfrf11_call_cleanup:ccb 0x60F6404C, vdbPtr 0x610DB7A4freeccb_flag=1, call_disconnected_flag=1Related Commands
debug cch323
To provide debugging output for various components within the H.323 subsystem, use the debug cch323 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cch323 {all | error | h225 | h245 | nxe | ras | rawmsg | session}
no debug cch323
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug cch323 Command with the all Keyword
When used with the debug cch323 command, the all keyword provides debug output for various components within the H.323 subsystem.
The debug cch323 command used with the all keyword enables the following debug cch323 commands:
Caution
The debug cch323 Command with the error Keyword
When used with the debug cch323 command, the error keyword allows you to trace errors encountered in the H.323 subsystem.
Note
The debug cch323 Command with the h225 Keyword
When used with the debug cch323 command, the h225 keyword allows you to trace the state transition of the H.225 state machine on the basis of the processed event.
The definitions of the different states of the H.225 state machine follow:
•
•
•
•
•
•
•
•
The definitions of the different events of the H.225 state machine follow:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The debug cch323 Command with the h245 Keyword
When used with the debug cch323 command, the h245 keyword allows you to trace the state transition of the H.245 state machine on the basis of the processed event.
The H.245 state machines include the following three state machines:
•
•
•
The state definitions follow:
•
•
•
•
•
•
•
•
•
The event definitions follow:
•
•
•
•
•
•
•
•
•
•
•
•
The debug cch323 Command with the nxe Keyword
When used with the debug cch323 command, the nxe keyword allows you to display the Annex E events that have been transmitted and received.
The debug cch323 Command with the ras Keyword
When used with the debug cch323 command, the ras keyword allows you to trace the state transition of the RAS state machine based on the processed events.
RAS operates in two state machines. One global state machine controls the overall RAS operation of the gateway. The other state machine is a per-call state machine that controls the active calls.
The definitions of the different states of the RAS state machine follow:
•
•
•
•
•
•
•
•
The definitions of the different events of the RAS state machine follow:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The debug cch323 Command with the rawmsg Keyword
When used with the debug cch323 command, the rawmsg keyword allows you to troubleshoot raw message buffer problems.
Caution
The debug cch323 Command with the session Keyword
Used with the debug cch323 command, the session keyword allows you to trace general H.323 events.
Caution
Examples
The debug cch323 Command with the all Keyword Example
The debug cch323 all command and keyword combination provides output for the following keywords: error, h225, h245, nxe, ras, rawmsg, and session. Examples of output for each keyword follow.
The debug cch323 Command with the error Keyword Example
The following is sample output from a typical debug cch323 error request on a Cisco 3640 router:
Router# debug cch323 errorcch323_h225_receiver:received msg of unknown type 5The debug cch323 Command with the h225 Keyword Example
The following is sample output from a typical debug cch323 h225 request on a Cisco 3640 router:
Router# debug cch323 h22520:59:17:Set new event H225_EVENT_SETUP20:59:17:H225 FSM:received event H225_EVENT_SETUP while at state H225_IDLE20:59:17:Changing from H225_IDLE state to H225_SETUP state20:59:17:cch323_h225_receiver:received msg of type SETUPCFM_CHOSEN20:59:17:H225 FSM:received event H225_EVENT_SETUP_CFM_IND while at stateH225_SETUP20:59:17:Changing from H225_SETUP state to H225_ACTIVE state20:59:17:Set new event H225_EVENT_H245_SUCCESS20:59:17:H225 FSM:received event H225_EVENT_H245_SUCCESS while at stateH225_ACTIVE20:59:20:Set new event H225_EVENT_RELEASE20:59:20:H225 FSM:received event H225_EVENT_RELEASE while at stateH225_ACTIVE20:59:20:Changing from H225_ACTIVE state to H225_WAIT_FOR_DRQ state20:59:20:Set new event H225_EVENT_RAS_SUCCESS20:59:20:H225 FSM:received event H225_EVENT_RAS_SUCCESS while at stateH225_WAIT_FOR_DRQ20:59:20:Changing from H225_WAIT_FOR_DRQ state to H225_IDLE stateTable 45 describes the significant fields shown in the display.
The debug cch323 Command with the h245 Keyword Example
The following is sample output from a typical debug cch323 h245 request on a Cisco 3640 router:
Router# debug cch323 h24520:58:23:Changing to new event H245_EVENT_MSD20:58:23:H245 MS FSM:received event H245_EVENT_MSD while at stateH245_MS_NONE20:58:23:changing from H245_MS_NONE state to H245_MS_WAIT state20:58:23:Changing to new event H245_EVENT_CAP20:58:23:H245 CAP FSM:received event H245_EVENT_CAP while at stateH245_CAP_NONE20:58:23:changing from H245_CAP_NONE state to H245_CAP_WAIT state20:58:23:cch323_h245_receiver:received msg of typeM_H245_MS_DETERMINE_INDICATION20:58:23:Changing to new event H245_EVENT_MS_IND20:58:23:H245 MS FSM:received event H245_EVENT_MS_IND while at stateH245_MS_WAIT20:58:23:cch323_h245_receiver:received msg of typeM_H245_CAP_TRANSFER_INDICATION20:58:23:Changing to new event H245_EVENT_CAP_IND20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_IND while at stateH245_CAP_WAIT20:58:23:cch323_h245_receiver:received msg of typeM_H245_MS_DETERMINE_CONFIRM20:58:23:Changing to new event H245_EVENT_MS_CFM20:58:23:H245 MS FSM:received event H245_EVENT_MS_CFM while at stateH245_MS_WAIT20:58:23:changing from H245_MS_WAIT state to H245_MS_DONE state0:58:23:cch323_h245_receiver:received msg of type M_H245_CAP_TRANSFER_CONFIRM20:58:23:Changing to new event H245_EVENT_CAP_CFM20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_CFM while at stateH245_CAP_WAIT20:58:23:changing from H245_CAP_WAIT state to H245_CAP_DONE state20:58:23:Changing to new event H245_EVENT_OLC20:58:23:H245 OLC FSM:received event H245_EVENT_OLC while at stateH245_OLC_NONE20:58:23:changing from H245_OLC_NONE state to H245_OLC_WAIT state20:58:23:cch323_h245_receiver:received msg of typeM_H245_UCHAN_ESTABLISH_INDICATION20:58:23:Changing to new event H245_EVENT_OLC_IND20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_IND while at stateH245_OLC_WAIT20:58:23:cch323_h245_receiver:received msg of type M_H245_UCHAN_ESTAB_ACK20:58:23:Changing to new event H245_EVENT_OLC_CFM20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_CFM while at stateH245_OLC_WAIT20:58:23:changing from H245_OLC_WAIT state to H245_OLC_DONE stateTable 46 describes the significant fields shown in the display.
The debug cch323 Command with the nxe Keyword Example
The following is sample output from a debug cch323 nxe request:
Router# debug cch323 nxe00:15:54:nxe_handle_usrmsg_to_remote:User Message size is 22700:15:54:nxe_msg_send_possible:Msg put in the active Q for CRV [3, direction flag 0]00:15:54:nxe_send_msg:H323chan returns bytes sent=241, the actual len=241, to IPaddr[0xA4D4A02], Port [2517]00:15:54:nxe_handle_usrmsg_to_remote:Usr Msg sent for IPaddr [0xA4D4A02], Port [2517], CRV[3, direction flag 0]00:15:54:nxe_parse_msg_from_remote:Msg received from IP [0xA4D4A02], Port [2517]00:15:54:nxe_parse_msg_from_remote:Value of PDU flags = 0x200:15:54:nxe_parse_payload:Transport msg type, Payload flag = 0x000:15:54:nxe_receive_ack:Ack received for 1 pdus00:15:54:nxe_receive_ack:Ack received for seqnum=13 from IPAddr [0xA4D4A02], Port [2517]00:15:54:nxe_parse_msg_from_remote:Msg received from IP [0xA4D4A02], Port [2517]00:15:54:nxe_parse_msg_from_remote:Value of PDU flags = 0x300:15:54:nxe_parse_payload:Static msg type, Payload flag = 0xA000:15:54:nxe_parse_x_static:Rx H225 msg from IPaddr [0xA4D4A02], Port [2517], CRV [3,direction flag 0]00:15:54:nxe_make_ackmsg:NXE ACK Msg made to ack seqnum=1400:15:54:nxe_send_msg:H323chan returns bytes sent=16, the actual len=16, to IPaddr[0xA4D4A02], Port [2517]00:15:54:nxe_parse_msg_from_remote:Ack sent for Destination IPaddr [0xA4D4A02], Port[2517]00:15:54:nxe_parse_msg_from_remote:Msg received from IP [0xA4D4A02], Port [2517]00:15:54:nxe_parse_msg_from_remote:Value of PDU flags = 0x300:15:54:nxe_parse_payload:Static msg type, Payload flag = 0xA000:15:54:nxe_parse_x_static:Rx H225 msg from IPaddr [0xA4D4A02], Port [2517], CRV [3,direction flag 0]The debug cch323 Command with the ras Keyword Example
The following is sample output from a typical debug cch323 ras request on a Cisco 3640 router:
Router# debug cch323 ras20:58:49:Changing to new event CCH323_RAS_EVENT_SEND_RRQcch323_run_ras_sm:received event CCH323_RAS_EVENT_SEND_RRQ while at CCH323_RAS_STATE_IDLE statecch323_run_ras_sm:changing to CCH323_RAS_STATE_RRQ statecch323_ras_receiver:received msg of type RCF_CHOSENcch323_run_ras_sm:received event CCH323_RAS_EVENT_RCF while at CCH323_RAS_STATE_RRQ statecch323_run_ras_sm:changing to CCH323_RAS_STATE_IDLE state20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_NEWCALL while at CCH323_RAS_STATE_IDLE state20:58:59:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ARQcch323_ras_receiver:received msg of type ACF_CHOSEN20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_ACF while atCCH323_RAS_STATE_ARQ state20:58:59:cch323_percall_ras_sm:changing to new stateCCH323_RAS_STATE_ACTIVE20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_CALLDISC whileat CCH323_RAS_STATE_ACTIVE state20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_DRQcch323_ras_receiver:received msg of type DCF_CHOSEN20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_DCF while atCCH323_RAS_STATE_DRQ state20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_IDLE20:59:04:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_IRR while atCCH323_RAS_STATE_ACTIVE state20:59:04:cch323_percall_ras_sm:changing to new stateCCH323_RAS_STATE_ACTIVETable 47 describes the significant fields shown in the display.
The debug cch323 Command with the rawmsg Keyword Example
The following is sample output from a typical debug cch323 rawmsg request on a Cisco 3640 router:
Router# debug cch323 rawmsg00:32:04:cch323_h225_progress_ind:raw message is 4 bytes:1E 02 81 8800:32:22:cch323_h225_release_ind:raw message is 80 bytes:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000:32:22:cch323_h225_release_notify:raw message is 80 bytes:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00The debug cch323 Command with the session Keyword Examples
Following are two examples of output using the debug cch323 session command and keyword combination. The first example is for a call setup on an originating gateway. The second example is for a call setup on a terminating gateway.
The following is sample output from a typical debug cch323 session request for a call setup on an originating gateway:
Router# debug cch323 session00:33:49:cch323_call_setup:gw_id=1, callID=1600:33:49:cch323_get_new_ccb:ccb (0x81D12D2C) is in use00:33:49:cch323_call_setup:inserted ccbcch323_get_peer_info:faxrate[21]proto[2]bitmask[10002]t38_inhibit[0]global_fax[0]00:33:49:Not using Voice Class Codec00:33:49:cch323_get_peer_info:preffered_codec set to G729IETF with Bytes = 2000:33:49:cch323_get_peer_info:peer:81FC0D14, peer->voice_peer_tag:12D, ccb:81D12D2C00:33:49:Call_setup Playout Mode:0,Init 60, Min 40, Max 20000:33:49:No account/pin number available00:33:49:cch323_call_setup_normal:for callID 1000:33:49:timer (0x81D130D4)starts - delay (15000)00:33:49:cch323_ct_main:SOCK 1 Event 0x100:33:49:timer(0x81D130D4) stops00:33:49:Near-end Pref Codecs = G.729 IETF00:33:49: generic_open_logical_channel:codec is g72900:33:49:cch323_generic_open_logical_channel:Filling in qosCapability field to 000:33:49:timer (0x81D130D4)starts - delay (15000)00:33:49:cch323_ct_main:SOCK 1 Event 0x100:33:49:cch323_ct_main:SOCK 1 Event 0x100:33:49: [1]towner_data=0x81D13C88, len=105, msgPtr=0x81D0760800:33:49:cch323_gw_process_read_socket:received msg for H.22500:33:49:timer(0x81D130D4) stops00:33:49:timer (0x81D130D4)starts - delay (180000)00:33:49:Codec:loc(16), rem(16),Bytes:loc(20), Fwd(20), Rev(20)00:33:49:cch323_rtp_open_notify:00:33:50:cch323_ct_main:SOCK 1 Event 0x100:33:50: [1]towner_data=0x81D13C88, len=71, msgPtr=0x81F1F2E000:33:50:cch323_gw_process_read_socket:received msg for H.22500:33:50:cch323_caps_ind:cap_modem_proto:0, cap_modem_codec:0, cap_modem_redundancy:0 payload 10000:33:50:cch323_caps_ind:Load DSP with Negotiated codec(16) g729r8, Bytes=2000:33:50:cch323_caps_ind:set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICEThe following is sample output from a typical debug cch323 session request for a call setup on a terminating gateway:
Router# debug cch323 session00:23:27:cch323_ct_main:SOCK 0 Event 0x100:23:27:cch323_ct_main:SOCK 1 Event 0x100:23:27: [1]towner_data=0x81F9CA9C, len=179, msgPtr=0x81D15C6C00:23:27:cch323_gw_process_read_socket:received msg for H.22500:23:27:cch323_h225_receiver CCB not existing already00:23:27:cch323_get_new_ccb:ccb (0x81F90184) is in use00:23:27:cch323_h225_receiver Got a new CCB for call id -211546756400:23:27:cch323_h225_setup_ind00:23:27:Not using Voice Class Codec00:23:27:cch323_set_peer:peer:81FB3228, peer->voice_peer_tag:12C, ccb:81F9018400:23:27:Near-end Pref Codecs = G.729 IETF00:23:27:Codec:loc(16), rem(16),Bytes:loc(20), Fwd(20), Rev(20)00:23:27:cch323_build_fastStart_cap_response:Retrieved qosCapability of 000:23:27:cch323_build_fastStart_cap_response:In Response Filling in qosCapability field to 000:23:27:Not using Voice Class CodecRelated Commands
debug cch323 capacity
To track the call capacity of the gatekeeper, use the debug cch323 capacity command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cch323 capacity
no debug cch323 capacity
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug cch323 capacity command to track the maximum and current call capacity values in the Registration, Admission, and Status (RAS) Protocol messages and to debug capacity-related problems while sending RAS messages. This command is entered on the gateway to monitor the call capacity of the gatekeeper.
The command lists the values for current and maximum call capacity provided by the trunk group capacity resource manager if and when the H.323 Service Provider Interface (SPI) requests the information for all or specific groups of circuits.
Examples
The following is sample output from the debug cch323 capacity command:
Router# debug cch323 capacityCall Capacity Information tracing is enabled5d00h: cch323_process_carrier_update: Registered = 1,Event = 1,Reason = 15d00h: cch323_process_carrier_update: CarrierId = CARRIERA_NEWENGLAND5d00h: cch323_fill_crm_CallCapacities: Reason = 1, GroupID = CARRIERA_NEWENGLAND5d00h: Capacity Details: Maximum Channels in Group: 23Max. Voice Calls(In) : 23, Max. Voice Calls(Out): 23Active Voice Calls(In): 5, Active Voice Calls(Out): 7Max. Voice Calls(to GK): 23, Avail. Voice Calls(to GK): 11The gatekeeper displays this output when trunk groups are added, deleted, or modified or when circuits in a trunk group are deactivated or activated (similar to ISDN layer 2 down/up).
5d00h: cch323_process_carrier_update: Registered = 1,Event = 1,Reason = 15d00h: cch323_process_carrier_update: CarrierId = CARRIERA_NEWENGLANDTable 48 describes the significant fields shown in the display.
The gatekeeper displays this output whenever call capacity information is sent to the gatekeeper.
5d00h: cch323_fill_crm_CallCapacities: Reason = 1, GroupID = CARRIERA_NEWENGLAND5d00h: Capacity Details: Maximum Channels in Group: 23Max. Voice Calls(In) : 23, Max. Voice Calls(Out): 23Active Voice Calls(In): 5, Active Voice Calls(Out): 7Max. Voice Calls(to GK): 23, Avail. Voice Calls(to GK): 11Table 49 describes the significant fields shown in the display.
Related Commands
debug cch323 h225
To provide the trace of the state transition of the H.225 state machine based on the processed events, use the debug cch323 h225 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cch323 h225
no debug cch323 h225
Syntax Description
This command has no keywords or arguments.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
State Descriptions
The state definitions of the different states of the H.225 state machine are as follows:
•
•
•
•
•
•
•
•
Events Description
The event definitions of the different events of the H.225 state machine are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Examples
The following is sample output from the debug cch323 h225 command:
Router# debug cch323 h22520:59:17:Set new event H225_EVENT_SETUP20:59:17:H225 FSM:received event H225_EVENT_SETUP while at state H225_IDLE20:59:17:Changing from H225_IDLE state to H225_SETUP state20:59:17:cch323_h225_receiver:received msg of type SETUPCFM_CHOSEN20:59:17:H225 FSM:received event H225_EVENT_SETUP_CFM_IND while at stateH225_SETUP20:59:17:Changing from H225_SETUP state to H225_ACTIVE state20:59:17:Set new event H225_EVENT_H245_SUCCESS20:59:17:H225 FSM:received event H225_EVENT_H245_SUCCESS while at stateH225_ACTIVE20:59:20:Set new event H225_EVENT_RELEASE20:59:20:H225 FSM:received event H225_EVENT_RELEASE while at stateH225_ACTIVE20:59:20:Changing from H225_ACTIVE state to H225_WAIT_FOR_DRQ state20:59:20:Set new event H225_EVENT_RAS_SUCCESS20:59:20:H225 FSM:received event H225_EVENT_RAS_SUCCESS while at stateH225_WAIT_FOR_DRQ20:59:20:Changing from H225_WAIT_FOR_DRQ state to H225_IDLE statedebug cch323 h245
To provide the trace of the state transition of the H.245 state machine based on the processed events, use the debug cch323 h245 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cch323 h245
no debug cch323 h245
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The H.245 state machines include the following three state machines:
•
•
•
State Definitions
The definitions are as follows:
•
•
•
•
•
•
•
•
•
Event definitions
•
•
•
•
•
•
•
•
•
•
•
•
Examples
The following is sample output from the debug cch323 h245 command:
Router# debug cch323 h24520:58:23:Changing to new event H245_EVENT_MSD20:58:23:H245 MS FSM:received event H245_EVENT_MSD while at stateH245_MS_NONE20:58:23:changing from H245_MS_NONE state to H245_MS_WAIT state20:58:23:Changing to new event H245_EVENT_CAP20:58:23:H245 CAP FSM:received event H245_EVENT_CAP while at stateH245_CAP_NONE20:58:23:changing from H245_CAP_NONE state to H245_CAP_WAIT state20:58:23:cch323_h245_receiver:received msg of typeM_H245_MS_DETERMINE_INDICATION20:58:23:Changing to new event H245_EVENT_MS_IND20:58:23:H245 MS FSM:received event H245_EVENT_MS_IND while at stateH245_MS_WAIT20:58:23:cch323_h245_receiver:received msg of typeM_H245_CAP_TRANSFER_INDICATION20:58:23:Changing to new event H245_EVENT_CAP_IND20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_IND while at stateH245_CAP_WAIT20:58:23:cch323_h245_receiver:received msg of typeM_H245_MS_DETERMINE_CONFIRM20:58:23:Changing to new event H245_EVENT_MS_CFM20:58:23:H245 MS FSM:received event H245_EVENT_MS_CFM while at stateH245_MS_WAIT20:58:23:changing from H245_MS_WAIT state to H245_MS_DONE state0:58:23:cch323_h245_receiver:received msg of type M_H245_CAP_TRANSFER_CONFIRM20:58:23:Changing to new event H245_EVENT_CAP_CFM20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_CFM while at stateH245_CAP_WAIT20:58:23:changing from H245_CAP_WAIT state to H245_CAP_DONE state20:58:23:Changing to new event H245_EVENT_OLC20:58:23:H245 OLC FSM:received event H245_EVENT_OLC while at stateH245_OLC_NONE20:58:23:changing from H245_OLC_NONE state to H245_OLC_WAIT state20:58:23:cch323_h245_receiver:received msg of typeM_H245_UCHAN_ESTABLISH_INDICATION20:58:23:Changing to new event H245_EVENT_OLC_IND20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_IND while at stateH245_OLC_WAIT20:58:23:cch323_h245_receiver:received msg of type M_H245_UCHAN_ESTAB_ACK20:58:23:Changing to new event H245_EVENT_OLC_CFM20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_CFM while at stateH245_OLC_WAIT20:58:23:changing from H245_OLC_WAIT state to H245_OLC_DONE statedebug cch323 preauth
To enable diagnostic reporting of authentication, authorization, and accounting (AAA) call preauthentication for H.323 calls, use the debug cch323 preauth command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cch323 preauth
no debug cch323 preauth
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is debugging output for a single H.323 call:
Router# debug cch323 preauthCCH323 preauth tracing is enabledcch323_is_preauth_reqd is TRUEJan 23 18:39:56.393: In cch323_send_preauth_req for preauth_id = -1Jan 23 18:39:56.393: Entering rpms_proc_print_preauth_reqJan 23 18:39:56.393: Request = 0Jan 23 18:39:56.393: Preauth id = 86514Jan 23 18:39:56.393: EndPt Type = 1Jan 23 18:39:56.393: EndPt = 192.168.81.102Jan 23 18:39:56.393: Resource Service = 1Jan 23 18:39:56.393: Call_origin = answerJan 23 18:39:56.393: Call_type = voipJan 23 18:39:56.393: Calling_num = 2230001Jan 23 18:39:56.393: Called_num = 1#1130001Jan 23 18:39:56.393: Protocol = 0Jan 23 18:39:56.393: cch323_insert_preauth_tree:Created node with preauth_id = 86514 ,ccb 6852D5BC , node 651F87FCJan 23 18:39:56.393:rpms_proc_create_node:Created node with preauth_id = 86514Jan 23 18:39:56.393:rpms_proc_send_aaa_req:uid got is 466725Jan 23 18:39:56.397:rpms_proc_preauth_response:Context is for preauth_id 86514, aaa_uid 466725Jan 23 18:39:56.397: Entering Function cch323_rpms_proc_callback_funcJan 23 18:39:56.397:cch323_rpms_proc_callback_func:PREAUTH_SUCCESS for preauth id 86514 aaa_uid 466725 auth_serv 1688218168Jan 23 18:39:56.397:rpms_proc_preauth_response:Deleting Tree node for preauth id 86514 uid 466725Jan 23 18:39:56.397:cch323_get_ccb_and_delete_from_preauth_tree:Preauth_id=86514cch323_get_ccb_and_delete_from_preauth_tree:651F87FC node and 6852D5BC ccbTable 50 describes the significant fields shown in the display.
debug cch323 ras
To provide the trace of the state transition of the Registration, Admission, and Status (RAS) Protocol state machine based on the processed events, use the debug cch323 ras command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cch323 ras
no debug cch323 ras
Syntax Description
This command has no keywords or arguments.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
RAS operates in two state machines. One global state machine controls the overall RAS operation of the Gateway. The other state machine is a per call state machine that controls the active calls.
State definitions
The state definitions of the different states of the RAS state machine follow:
•
•
•
•
•
•
•
•
Event Definitions
These are the event definitions of the different states of the RAS state machine:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Examples
The following is sample output from the debug cch323 preauth command:
Router# debug cch323 preauth20:58:49:Changing to new event CCH323_RAS_EVENT_SEND_RRQcch323_run_ras_sm:received event CCH323_RAS_EVENT_SEND_RRQ while at CCH323_RAS_STATE_IDLE statecch323_run_ras_sm:changing to CCH323_RAS_STATE_RRQ statecch323_ras_receiver:received msg of type RCF_CHOSENcch323_run_ras_sm:received event CCH323_RAS_EVENT_RCF while at CCH323_RAS_STATE_RRQ statecch323_run_ras_sm:changing to CCH323_RAS_STATE_IDLE state20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_NEWCALL while at CCH323_RAS_STATE_IDLE state20:58:59:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ARQcch323_ras_receiver:received msg of type ACF_CHOSEN20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_ACF while atCCH323_RAS_STATE_ARQ state20:58:59:cch323_percall_ras_sm:changing to new stateCCH323_RAS_STATE_ACTIVE20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_CALLDISC whileat CCH323_RAS_STATE_ACTIVE state20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_DRQcch323_ras_receiver:received msg of type DCF_CHOSEN20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_DCF while atCCH323_RAS_STATE_DRQ state20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_IDLE20:59:04:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_IRR while atCCH323_RAS_STATE_ACTIVE state20:59:04:cch323_percall_ras_sm:changing to new stateCCH323_RAS_STATE_ACTIVEdebug cch323 video
To provide debugging output for video components within the H.323 subsystem, use the debug cch323 video command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cch323 video
no debug cch323 video
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to enable a debugging trace for the video component in an H.323 network.
Examples
Originating Gateway Example
The following is sample output of the debugging log for an originating Cisco Unified CallManager Express (Cisco Unified CME) gateway after the debug cch323 video command was enabled:
Router# show logSyslog logging: enabled (11 messages dropped, 487 messages rate-limited,0 flushes, 0 overruns, xml disabled, filtering disabled)Console logging: disabledMonitor logging: level debugging, 0 messages logged, xml disabled,filtering disabledBuffer logging: level debugging, 1144 messages logged, xml disabled,filtering disabledLogging Exception size (4096 bytes)Count and timestamp logging messages: disabledTrap logging: level informational, 1084 message lines loggedLog Buffer (6000000 bytes):Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_peer_info: EntryJun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_peer_info: Have peerJun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_set_pref_codec_list: First preferred codec(bytes)=16(20)Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_peer_info: Flow Mode set to FLOW_THROUGHJun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_caps_chn_info: No peer leg setup paramsJun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_caps_chn_info: Setting CCH323_SS_NTFY_VIDEO_INFOJun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_set_h323_control_options_outgoing: h245 sm mode = 8463Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_set_h323_control_options_outgoing: h323_ctl=0x20Jun 13 09:19:42.010: //103030/C7838B198002/H323/cch323_rotary_validate: No peer_ccb availableTerminating Gateway Example
The following is sample output of the debugging log for a terminating Cisco Unified Survivable Remote Site Telephony (Cisco Unified SRST) gateway after the debug cch323 video command was enabled:
Router# show logSyslog logging: enabled (11 messages dropped, 466 messages rate-limited,0 flushes, 0 overruns, xml disabled, filtering disabled)Console logging: disabledMonitor logging: level debugging, 0 messages logged, xml disabled,filtering disabledBuffer logging: level debugging, 829 messages logged, xml disabled,filtering disabledLogging Exception size (4096 bytes)Count and timestamp logging messages: disabledTrap logging: level informational, 771 message lines loggedLog Buffer (200000 bytes):Jun 13 09:19:42.011: //103034/C7838B198002/H323/setup_ind: Receive bearer cap infoXRate 24, rateMult 12Jun 13 09:19:42.011: //103034/C7838B198002/H323/cch323_set_h245_state_mc_mode_incoming: h245 state m/c mode=0x10F, h323_ctl=0x2FJun 13 09:19:42.015: //-1/xxxxxxxxxxxx/H323/cch245_event_handler: callID=103034Jun 13 09:19:42.019: //-1/xxxxxxxxxxxx/H323/cch245_event_handler: Event CC_EV_H245_SET_MODE: data ptr=0x465D5760Jun 13 09:19:42.019: //-1/xxxxxxxxxxxx/H323/cch323_set_mode: callID=103034, flow Mode=1 spi_mode=0x6Jun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_do_call_proceeding: set_mode NOT called yet...saved deferred CALL_PROCJun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_h245_connection_sm: state=0, event=0, ccb=4461B518, listen state=0Jun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_process_set_mode: Setting inbound leg mode flags to 0x10F, flow-mode to FLOW_THROUGHJun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_process_set_mode: Sending deferred CALL_PROCJun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_do_call_proceeding: set_mode called so we can proceed with CALLPROCJun 13 09:19:42.027: //103034/C7838B198002/H323/cch323_h245_connection_sm: state=1, event=2, ccb=4461B518, listen state=1Jun 13 09:19:42.027: //103034/C7838B198002/H323/cch323_send_cap_request: Setting mode to VIDEO MODEJun 13 09:19:42.031: //103034/C7838B198002/H323/cch323_h245_cap_ind: Masks au=0xC data=0x2 uinp=0x32Related Commands
debug ccm-manager
To display debugging information about Cisco CallManager, use the debug ccm-manager command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccm-manager {backhaul {errors | events | packets} | config-download {all | errors | events | packets | tone | xml} | errors | events | music-on-hold {errors | events | packets} | packets}
no debug ccm-manager
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug ccm-manager events command:
Router# debug ccm-manager events*Feb 28 22:56:05.873: cmapp_mgcpapp_go_down: Setting mgc status to NO_RESPONSE*Feb 28 22:56:05.873: cmapp_host_fsm: New state DOWN for host 0 (172.20.71.38)*Feb 28 22:56:05.873: cmapp_mgr_process_ev_active_host_failed: Active host 0 (172.20.71.38) failed*Feb 28 22:56:05.873: cmapp_mgr_check_hostlist: Active host is 0 (172.20.71.38)*Feb 28 22:56:05.877: cmapp_mgr_switchover: New actv host will be 1 (172.20.71.44)*Feb 28 22:56:05.877: cmapp_host_fsm: Processing event GO_STANDBY for host 0 (172.20.71.38) in state DOWN*Feb 28 22:56:05.877: cmapp_open_new_link: Open link for [0]:172.20.71.38*Feb 28 22:56:05.877: cmbh_open_tcp_link: Opening TCP link with Rem IP 172.20.71.38, Local IP 172.20.71.19, port 2428*Feb 28 22:56:05.881: cmapp_open_new_link: Open initiated OK: Host 0 (172.20.71.38), session_id=8186DEE4*Feb 28 22:56:05.881: cmapp_start_open_link_tmr: Host 0 (172.20.71.38), tmr 0*Feb 28 22:56:05.881: cmapp_host_fsm: New state STANDBY_OPENING for host 0 (172.20.71.38)*Feb 28 22:56:05.881: cmapp_host_fsm: Processing event GO_ACTIVE for host 1 (172.20.71.44) in state STANDBY_READY*Feb 28 22:56:05.885: cmapp_mgr_send_rehome: new addr=172.20.71.44,port=2427*Feb 28 22:56:05.885: cmapp_host_fsm: New state REGISTERING for host 1 (172.20.71.44)You can use the debug ccm-manager config-download tone command to verify the parameters assigned to each locale. The following sample output shows the locale name United Kingdom and lists all the dual-tone parameters for that region:
Router# debug ccm-manager config-download tone00:09:07:cmapp_prefix_process_tag_tones:00:09:07: cmapp_process_tag_trkLocaleName: region = United Kingdom00:09:07: cmapp_process_tag_pulse_ratio: pulse ratio = 4000:09:07: cmapp_process_tag_dtmf_llevel: low frequency level = 6543800:09:07: cmapp_process_tag_dtmf_hlevel: high frequency level = 6546300:09:07: cmapp_process_tag_special_oper: operation = uLaw00:09:07: cmapp_prefix_process_tag_lpig:00:09:07: cmapp_process_tag_fxs: ignore LPIG for fxs00:09:07: cmapp_process_tag_fxo: ignore LPIG for fxo00:09:07: cmapp_process_tag_digital: ignore LPIG for digital00:09:07: cmapp_prefix_process_tag_lpog:00:09:07: cmapp_process_tag_fxs: ignore LPOG for fxsBoth ports are in service00:09:07: cmapp_process_tag_fxo: ignore LPOG for fxo00:09:07: cmapp_process_tag_digital: ignore LPOG for digital00:09:07: cmapp_prefix_process_tag_tonetable_info:00:09:07:cmapp_prefix_process_tag_dualtone: TID=[0:CPTONE_BUSY]00:09:07: cmapp_process_tag_nf: number of frequencies = 100:09:07: cmapp_process_tag_dr: direction = 000:09:07: cmapp_process_tag_fof: frequency 1 = 40000:09:07: cmapp_process_tag_fos: frequency 2 = 000:09:07: cmapp_process_tag_fot: frequency 3 = 000:09:07: cmapp_process_tag_fo4: frequency 4 = 000:09:07: cmapp_prefix_process_tag_aof_level:00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -20000:09:07: cmapp_process_tag_fxo: amplitude of 1st = -20000:09:07: cmapp_process_tag_digital: amplitude of 1st = -24000:09:07: cmapp_prefix_process_tag_aos_level:00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = 000:09:07: cmapp_process_tag_fxo: amplitude of 2nd = 000:09:07: cmapp_process_tag_digital: amplitude of 2nd = 000:09:07: cmapp_prefix_process_tag_aot_level:00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 000:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 000:09:07: cmapp_process_tag_digital: amplitude of 3rd = 000:09:07: cmapp_prefix_process_tag_ao4_level:00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 000:09:07: cmapp_process_tag_fxo: amplitude of 4th = 000:09:07: cmapp_process_tag_digital: amplitude of 4th = 000:09:07: cmapp_process_tag_ontf: frequency 1 on time = 37500:09:07: cmapp_process_tag_oftf: frequency 1 off time = 37500:09:07: cmapp_process_tag_onts: frequency 2 on time = 000:09:07: cmapp_process_tag_ofts: frequency 2 off time = 000:09:07: cmapp_process_tag_ontt: frequency 3 on time = 000:09:07: cmapp_process_tag_oftt: frequency 3 off time = 000:09:07: cmapp_process_tag_ont4: frequency 4 on time = 000:09:07: cmapp_process_tag_oft4: frequency 4 off time = 000:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 000:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 000:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 000:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 000:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 000:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 000:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 000:09:07: cmapp_process_tag_rct2: cadence 2 repeat count = 000:09:07: cmapp_process_tag_rct3: cadence 3 repeat count = 000:09:07: cmapp_process_tag_rct4: cadence 4 repeat count = 000:09:07:cmapp_prefix_process_tag_dualtone: TID=[1:CPTONE_RING_BACK]00:09:07: cmapp_process_tag_nf: number of frequencies = 200:09:07: cmapp_process_tag_dr: direction = 000:09:07: cmapp_process_tag_fof: frequency 1 = 40000:09:07: cmapp_process_tag_fos: frequency 2 = 45000:09:07: cmapp_process_tag_fot: frequency 3 = 000:09:07: cmapp_process_tag_fo4: frequency 4 = 000:09:07: cmapp_prefix_process_tag_aof_level:00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -19000:09:07: cmapp_process_tag_fxo: amplitude of 1st = -19000:09:07: cmapp_process_tag_digital: amplitude of 1st = -19000:09:07: cmapp_prefix_process_tag_aos_level:00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = -19000:09:07: cmapp_process_tag_fxo: amplitude of 2nd = -19000:09:07: cmapp_process_tag_digital: amplitude of 2nd = -19000:09:07: cmapp_prefix_process_tag_aot_level:00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 000:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 000:09:07: cmapp_process_tag_digital: amplitude of 3rd = 000:09:07: cmapp_prefix_process_tag_ao4_level:00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 000:09:07: cmapp_process_tag_fxo: amplitude of 4th = 000:09:07: cmapp_process_tag_digital: amplitude of 4th = 000:09:07: cmapp_process_tag_ontf: frequency 1 on time = 40000:09:07: cmapp_process_tag_oftf: frequency 1 off time = 20000:09:07: cmapp_process_tag_onts: frequency 2 on time = 40000:09:07: cmapp_process_tag_ofts: frequency 2 off time = 200000:09:07: cmapp_process_tag_ontt: frequency 3 on time = 000:09:07: cmapp_process_tag_oftt: frequency 3 off time = 000:09:07: cmapp_process_tag_ont4: frequency 4 on time = 000:09:07: cmapp_process_tag_oft4: frequency 4 off time = 000:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 000:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 000:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 000:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 000:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 000:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 000:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 000:09:07: cmapp_process_tag_rct2: cadence 2 repeat count = 000:09:07: cmapp_process_tag_rct3: cadence 3 repeat count = 000:09:07: cmapp_process_tag_rct4: cadence 4 repeat count = 000:09:07:cmapp_prefix_process_tag_dualtone: TID=[2:CPTONE_CONGESTION]00:09:07: cmapp_process_tag_nf: number of frequencies = 100:09:07: cmapp_process_tag_dr: direction = 000:09:07: cmapp_process_tag_fof: frequency 1 = 40000:09:07: cmapp_process_tag_fos: frequency 2 = 000:09:07: cmapp_process_tag_fot: frequency 3 = 000:09:07: cmapp_process_tag_fo4: frequency 4 = 000:09:07: cmapp_prefix_process_tag_aof_level:00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -20000:09:07: cmapp_process_tag_fxo: amplitude of 1st = -20000:09:07: cmapp_process_tag_digital: amplitude of 1st = -20000:09:07: cmapp_prefix_process_tag_aos_level:00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = 000:09:07: cmapp_process_tag_fxo: amplitude of 2nd = 000:09:07: cmapp_process_tag_digital: amplitude of 2nd = 000:09:07: cmapp_prefix_process_tag_aot_level:00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 000:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 000:09:07: cmapp_process_tag_digital: amplitude of 3rd = 000:09:07: cmapp_prefix_process_tag_ao4_level:00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 000:09:07: cmapp_process_tag_fxo: amplitude of 4th = 000:09:07: cmapp_process_tag_digital: amplitude of 4th = 000:09:07: cmapp_process_tag_ontf: frequency 1 on time = 40000:09:07: cmapp_process_tag_oftf: frequency 1 off time = 35000:09:07: cmapp_process_tag_onts: frequency 2 on time = 22500:09:07: cmapp_process_tag_ofts: frequency 2 off time = 52500:09:07: cmapp_process_tag_ontt: frequency 3 on time = 000:09:07: cmapp_process_tag_oftt: frequency 3 off time = 000:09:07: cmapp_process_tag_ont4: frequency 4 on time = 000:09:07: cmapp_process_tag_oft4: frequency 4 off time = 000:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 000:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 000:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 000:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 000:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 000:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 000:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 000:09:07: cmapp_process_tag_rct2: cadence 2 repeat count = 000:09:07: cmapp_process_tag_rct3: cadence 3 repeat count = 000:09:07: cmapp_process_tag_rct4: cadence 4 repeat count = 0! endThe following is sample output from the debug ccm-manager config-download all command for an error case in which the configuration file cannot be accessed for a Skinny Client Control Protocol (SCCP) download:
*Jan 9 07:28:33.499: cmapp_xml_process_timer:*Jan 9 07:28:33.499: cmapp_xml_find_ep_by_name: Checking for ep_name [*]*Jan 9 07:28:33.499: cmapp_xml_exec_fsm: Endpoint is [*]*Jan 9 07:28:33.499: cmapp_xml_exec_fsm: endpoint = * state = CMAPP_XML_FILE_DNLD, event = CMAPP_XML_EVT_FILE_DNLD_TIMER*Jan 9 07:28:33.499: cmapp_xml_file_retry_timer_expired: state = CMAPP_XML_FILE_DNLD, event = CMAPP_XML_EVT_FILE_DNLD_TIMER*Jan 9 07:29:14.499: cmapp_xml_tftp_download_file: Unable to read file tftp://10.6.6.31/Router.cisco.com.cnf.xml, rc=-2*Jan 9 07:29:14.499: cmapp_xml_get_xml_file: Could not read file tftp://10.6.6.31/Router.cisco.com.cnf.xml, len = 0*Jan 9 07:29:14.499: cmapp_xml_tftp_download_file: Unable to read file tftp:///Router.cisco.com.cnf.xml, rc=-2*Jan 9 07:29:14.499: cmapp_xml_get_xml_file: Could not read file tftp:///Router.cisco.com.cnf.xml, len = 0*Jan 9 07:29:14.499: cmapp_xml_tftp_download_file: Unable to read file tftp:///Router.cisco.com.cnf.xml, rc=-2*Jan 9 07:29:14.499: cmapp_xml_get_xml_file: Could not read file tftp:///Router.cisco.com.cnf.xml, len = 0*Jan 9 07:29:14.499: cmapp_xml_exec_fsm: New state = CMAPP_XML_FILE_DNLD, ep = 6544CFA8The following is sample output from the debug ccm-manager config-download all command for a successful SCCP download:
*Jan 9 09:44:45.543: cmapp_sccp_config:*Jan 9 09:44:45.543: cmapp_sccp_reset_curcfg:*Jan 9 09:44:45.543: cmapp_sccp_init_curcfg:*Jan 9 09:44:45.543: cmapp_sccp_download_gw_config_file:*Jan 9 09:44:45.543: cmapp_sccp_get_gw_name:*Jan 9 09:44:45.543: cmapp_sccp_get_gw_name: XML file name generated->SKIGW0C85226910.cnf.xml*Jan 9 09:44:45.543: cmapp_sccp_get_xml_file_via_tftp:*Jan 9 09:44:45.543: cmapp_sccp_tftp_download_file:*Jan 9 09:44:45.543: cmapp_sccp_tftp_get_file_size:*Jan 9 09:44:45.563: cmapp_sccp_get_buffer:*Jan 9 09:44:45.575: cmapp_sccp_tftp_download_file: File (tftp://10.2.6.101/SKIGW0C85226910.cnf.xml) read 8162 bytes*Jan 9 09:44:45.575: cmapp_sccp_get_xml_file_via_tftp: Read file tftp://10.2.6.101/SKIGW0C85226910.cnf.xml, len = 8162*Jan 9 09:44:45.575: cmapp_parse_gw_xml_file:*Jan 9 09:44:45.579: cmapp_sccp_gw_chardata_handler: ccm found, priority=0The following lines show the conversion of XML data into router configuration information for the endpoint:
*Jan 9 09:44:45.579: cmapp_sccp_gw_start_element_handler: Unit has been set to 1*Jan 9 09:44:45.579: cmapp_sccp_gw_start_element_handler: Subunit has been set to 0*Jan 9 09:44:45.579: cmapp_sccp_gw_start_element_handler: Endpoint has been set to 0*Jan 9 09:44:45.579: cmapp_sccp_gw_start_element_handler: Endpoint has been set to 1*Jan 9 09:44:45.579: cmapp_sccp_gw_start_element_handler: Endpoint has been set to 2*Jan 9 09:44:45.579: cmapp_sccp_gw_start_element_handler: Endpoint has been set to 3*Jan 9 09:44:45.579: cmapp_sccp_gw_start_element_handler: Subunit has been set to 1*Jan 9 09:44:45.579: cmapp_sccp_gw_start_element_handler: Endpoint has been set to 0*Jan 9 09:44:45.579: cmapp_sccp_gw_start_element_handler: Endpoint has been set to 1*Jan 9 09:44:45.579: cmapp_sccp_gw_start_element_handler: Unit has been set to 2Table 51 describes the significant fields shown in the displays.
Related Commands
show ccm-manager
Displays a list of Cisco CallManager servers, their current status, and their availability.
debug ccsip all
To enable all Session Initiation Protocol (SIP)-related debugging, use the debug ccsip all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccsip all
no debug ccsip all
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ccsip all command enables the following SIP debug commands:
•
•
•
•
•
Examples
The following example displays debug output from one side of the call:
Router# debug ccsip allAll SIP call tracing enabledRouter1#*Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_NONE, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_NONE)*Mar 6 14:10:42: Queued event from SIP SPI : SIPSPI_EV_CC_CALL_SETUP*Mar 6 14:10:42: CCSIP-SPI-CONTROL: act_idle_call_setup*Mar 6 14:10:42: act_idle_call_setup:Not using Voice Class Codec*Mar 6 14:10:42: act_idle_call_setup: preferred_codec set[0] type :g711ulaw bytes: 160*Mar 6 14:10:42: Queued event from SIP SPI : SIPSPI_EV_CREATE_CONNECTION*Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_IDLE, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_CONNECTING)*Mar 6 14:10:42: REQUEST CONNECTION TO IP:166.34.245.231 PORT:5060*Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_IDLE, SUBSTATE_CONNECTING) to (STATE_IDLE, SUBSTATE_CONNECTING)*Mar 6 14:10:42: CCSIP-SPI-CONTROL: act_idle_connection_created*Mar 6 14:10:42: CCSIP-SPI-CONTROL: act_idle_connection_created: Connid(1) created to 166.34.245.231:5060, local_port 54113*Mar 6 14:10:42: sipSPIAddLocalContact*Mar 6 14:10:42: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE*Mar 6 14:10:42: CCSIP-SPI-CONTROL: sip_stats_method*Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_IDLE, SUBSTATE_CONNECTING) to (STATE_SENT_INVITE, SUBSTATE_NONE)*Mar 6 14:10:42: Sent:INVITE sip:3660210@166.34.245.231;user=phone;phone-context=unknown SIP/2.0Via: SIP/2.0/UDP 166.34.245.230:54113From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Sat, 06 Mar 1993 19:10:42 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Cisco-Guid: 2881152943-2184249548-0-483039712User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEMax-Forwards: 6Timestamp: 731427042Contact: <sip:3660110@166.34.245.230:5060;user=phone>Expires: 180Content-Type: application/sdpContent-Length: 137v=0o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230s=SIP Callt=0 0c=IN IP4 166.34.245.230m=audio 20208 RTP/AVP 0*Mar 6 14:10:42: Received:SIP/2.0 100 TryingVia: SIP/2.0/UDP 166.34.245.230:54113From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Mon, 08 Mar 1993 22:36:40 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Timestamp: 731427042Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEContent-Length: 0*Mar 6 14:10:42: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060*Mar 6 14:10:42: CCSIP-SPI-CONTROL: act_sentinvite_new_message*Mar 6 14:10:42: CCSIP-SPI-CONTROL: sipSPICheckResponse*Mar 6 14:10:42: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 6 14:10:42: Roundtrip delay 4 milliseconds for method INVITE*Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_SENT_INVITE, SUBSTATE_NONE) to (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING)*Mar 6 14:10:42: Received:SIP/2.0 180 RingingVia: SIP/2.0/UDP 166.34.245.230:54113From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Mon, 08 Mar 1993 22:36:40 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Timestamp: 731427042Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEContent-Type: application/sdpContent-Length: 137v=0o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231s=SIP Callt=0 0c=IN IP4 166.34.245.231m=audio 20038 RTP/AVP 0*Mar 6 14:10:42: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060*Mar 6 14:10:42: CCSIP-SPI-CONTROL: act_recdproc_new_message*Mar 6 14:10:42: CCSIP-SPI-CONTROL: sipSPICheckResponse*Mar 6 14:10:42: CCSIP-SPI-CONTROL: sipSPICheckResponse : Updating session description*Mar 6 14:10:42: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 6 14:10:42: Roundtrip delay 8 milliseconds for method INVITE*Mar 6 14:10:42: HandleSIP1xxRinging: SDP MediaTypes negotiation successful!Negotiated Codec : g711ulaw , bytes :160Inband Alerting : 0*Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING) to (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_ALERTING)*Mar 6 14:10:46: Received:SIP/2.0 200 OKVia: SIP/2.0/UDP 166.34.245.230:54113From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7FDate: Mon, 08 Mar 1993 22:36:40 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Timestamp: 731427042Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledContact: <sip:3660210@166.34.245.231:5060;user=phone>CSeq: 101 INVITEContent-Type: application/sdpContent-Length: 137v=0o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231s=SIP Callt=0 0c=IN IP4 166.34.245.231m=audio 20038 RTP/AVP 0*Mar 6 14:10:46: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060*Mar 6 14:10:46: CCSIP-SPI-CONTROL: act_recdproc_new_message*Mar 6 14:10:46: CCSIP-SPI-CONTROL: sipSPICheckResponse*Mar 6 14:10:46: CCSIP-SPI-CONTROL: sipSPICheckResponse : Updating session description*Mar 6 14:10:46: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 6 14:10:46: Roundtrip delay 3536 milliseconds for method INVITE*Mar 6 14:10:46: CCSIP-SPI-CONTROL: act_recdproc_new_message: SDP MediaTypes negotiation successful!Negotiated Codec : g711ulaw , bytes :160*Mar 6 14:10:46: CCSIP-SPI-CONTROL: sipSPIReconnectConnection*Mar 6 14:10:46: Queued event from SIP SPI : SIPSPI_EV_RECONNECT_CONNECTION*Mar 6 14:10:46: CCSIP-SPI-CONTROL: recv_200_OK_for_invite*Mar 6 14:10:46: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE*Mar 6 14:10:46: CCSIP-SPI-CONTROL: sip_stats_method*Mar 6 14:10:46: 0x624CFEF8 : State change from (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_ALERTING) to (STATE_ACTIVE, SUBSTATE_NONE)*Mar 6 14:10:46: The Call Setup Information is :Call Control Block (CCB) : 0x624CFEF8State of The Call : STATE_ACTIVETCP Sockets Used : NOCalling Number : 3660110Called Number : 3660210Negotiated Codec : g711ulawSource IP Address (Media): 166.34.245.230Source IP Port (Media): 20208Destn IP Address (Media): 166.34.245.231Destn IP Port (Media): 20038Destn SIP Addr (Control) : 166.34.245.231Destn SIP Port (Control) : 5060Destination Name : 166.34.245.231*Mar 6 14:10:46: HandleUdpReconnection: Udp socket connected for fd: 1 with 166.34.245.231:5060*Mar 6 14:10:46: Sent:ACK sip:3660210@166.34.245.231:5060;user=phone SIP/2.0Via: SIP/2.0/UDP 166.34.245.230:54113From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7FDate: Sat, 06 Mar 1993 19:10:42 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Max-Forwards: 6Content-Type: application/sdpContent-Length: 137CSeq: 101 ACKv=0o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230s=SIP Callt=0 0c=IN IP4 166.34.245.230m=audio 20208 RTP/AVP 0*Mar 6 14:10:46: CCSIP-SPI-CONTROL: ccsip_caps_ind*Mar 6 14:10:46: ccsip_caps_ind: Load DSP with codec (5) g711ulaw, Bytes=160*Mar 6 14:10:46: ccsip_caps_ind: set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE*Mar 6 14:10:46: CCSIP-SPI-CONTROL: ccsip_caps_ack*Mar 6 14:10:50: Received:BYE sip:3660110@166.34.245.230:5060;user=phone SIP/2.0Via: SIP/2.0/UDP 166.34.245.231:54835From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7FTo: "3660110" <sip:3660110@166.34.245.230>Date: Mon, 08 Mar 1993 22:36:44 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledMax-Forwards: 6Timestamp: 731612207CSeq: 101 BYEContent-Length: 0*Mar 6 14:10:50: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:54835*Mar 6 14:10:50: CCSIP-SPI-CONTROL: act_active_new_message*Mar 6 14:10:50: CCSIP-SPI-CONTROL: sact_active_new_message_request*Mar 6 14:10:50: CCSIP-SPI-CONTROL: sip_stats_method*Mar 6 14:10:50: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE*Mar 6 14:10:50: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 6 14:10:50: CCSIP-SPI-CONTROL: sipSPIInitiateCallDisconnect : Initiate call disconnect(16) for outgoing call*Mar 6 14:10:50: 0x624CFEF8 : State change from (STATE_ACTIVE, SUBSTATE_NONE) to (STATE_DISCONNECTING, SUBSTATE_NONE)*Mar 6 14:10:50: Sent:SIP/2.0 200 OKVia: SIP/2.0/UDP 166.34.245.231:54835From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7FTo: "3660110" <sip:3660110@166.34.245.230>Date: Sat, 06 Mar 1993 19:10:50 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledTimestamp: 731612207Content-Length: 0CSeq: 101 BYE*Mar 6 14:10:50: Queued event From SIP SPI to CCAPI/DNS : SIPSPI_EV_CC_CALL_DISCONNECT*Mar 6 14:10:50: CCSIP-SPI-CONTROL: act_disconnecting_disconnect*Mar 6 14:10:50: CCSIP-SPI-CONTROL: sipSPICallCleanup*Mar 6 14:10:50: Queued event from SIP SPI : SIPSPI_EV_CLOSE_CONNECTION*Mar 6 14:10:50: CLOSE CONNECTION TO CONNID:1*Mar 6 14:10:50: sipSPIIcpifUpdate :CallState: 4 Playout: 1755 DiscTime:48305031 ConnTime 48304651*Mar 6 14:10:50: 0x624CFEF8 : State change from (STATE_DISCONNECTING, SUBSTATE_NONE) to (STATE_DEAD, SUBSTATE_NONE)*Mar 6 14:10:50: The Call Setup Information is :Call Control Block (CCB) : 0x624CFEF8State of The Call : STATE_DEADTCP Sockets Used : NOCalling Number : 3660110Called Number : 3660210Negotiated Codec : g711ulawSource IP Address (Media): 166.34.245.230Source IP Port (Media): 20208Destn IP Address (Media): 166.34.245.231Destn IP Port (Media): 20038Destn SIP Addr (Control) : 166.34.245.231Destn SIP Port (Control) : 5060Destination Name : 166.34.245.231*Mar 6 14:10:50:Disconnect Cause (CC) : 16Disconnect Cause (SIP) : 200*Mar 6 14:10:50: udpsock_close_connect: Socket fd: 1 closed for connid 1 with remote port: 5060The following example displays debut output from the other side of the call:
Router# debug ccsip allAll SIP call tracing enabled3660-2#*Mar 8 17:36:40: Received:INVITE sip:3660210@166.34.245.231;user=phone;phone-context=unknown SIP/2.0Via: SIP/2.0/UDP 166.34.245.230:54113From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Sat, 06 Mar 1993 19:10:42 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Cisco-Guid: 2881152943-2184249548-0-483039712User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEMax-Forwards: 6Timestamp: 731427042Contact: <sip:3660110@166.34.245.230:5060;user=phone>Expires: 180Content-Type: application/sdpContent-Length: 137v=0o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230s=SIP Callt=0 0c=IN IP4 166.34.245.230m=audio 20208 RTP/AVP 0*Mar 8 17:36:40: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:54113*Mar 8 17:36:40: CCSIP-SPI-CONTROL: sipSPISipIncomingCall*Mar 8 17:36:40: 0x624D8CCC : State change from (STATE_NONE, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_NONE)*Mar 8 17:36:40: CCSIP-SPI-CONTROL: act_idle_new_message*Mar 8 17:36:40: CCSIP-SPI-CONTROL: sact_idle_new_message_invite*Mar 8 17:36:40: CCSIP-SPI-CONTROL: sip_stats_method*Mar 8 17:36:40: sact_idle_new_message_invite:Not Using Voice Class Codec*Mar 8 17:36:40: sact_idle_new_message_invite: Preferred codec[0] type: g711ulaw Bytes :160*Mar 8 17:36:40: sact_idle_new_message_invite: Media Negotiation successful for anincoming call*Mar 8 17:36:40: sact_idle_new_message_invite: Negotiated Codec : g711ulaw, bytes :160Preferred Codec : g711ulaw, bytes :160*Mar 8 17:36:40: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE*Mar 8 17:36:40: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 8 17:36:40: Num of Contact Locations 1 3660110 166.34.245.230 5060*Mar 8 17:36:40: 0x624D8CCC : State change from (STATE_IDLE, SUBSTATE_NONE) to (STATE_RECD_INVITE, SUBSTATE_RECD_INVITE_CALL_SETUP)*Mar 8 17:36:40: Sent:SIP/2.0 100 TryingVia: SIP/2.0/UDP 166.34.245.230:54113From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Mon, 08 Mar 1993 22:36:40 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Timestamp: 731427042Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEContent-Length: 0*Mar 8 17:36:40: Queued event From SIP SPI to CCAPI/DNS : SIPSPI_EV_CC_CALL_PROCEEDING*Mar 8 17:36:40: CCSIP-SPI-CONTROL: act_recdinvite_proceeding*Mar 8 17:36:40: Queued event From SIP SPI to CCAPI/DNS : SIPSPI_EV_CC_CALL_ALERTING*Mar 8 17:36:40: CCSIP-SPI-CONTROL: ccsip_caps_ind*Mar 8 17:36:40: ccsip_caps_ind: codec(negotiated) = 5(Bytes 160)*Mar 8 17:36:40: ccsip_caps_ind: Load DSP with codec (5) g711ulaw, Bytes=160*Mar 8 17:36:40: ccsip_caps_ind: set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE*Mar 8 17:36:40: CCSIP-SPI-CONTROL: ccsip_caps_ack*Mar 8 17:36:40: CCSIP-SPI-CONTROL: act_recdinvite_alerting*Mar 8 17:36:40: 180 Ringing with SDP - not likely*Mar 8 17:36:40: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE*Mar 8 17:36:40: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 8 17:36:40: 0x624D8CCC : State change from (STATE_RECD_INVITE, SUBSTATE_RECD_INVITE_CALL_SETUP) to (STATE_SENT_ALERTING, SUBSTATE_NONE)*Mar 8 17:36:40: Sent:SIP/2.0 180 RingingVia: SIP/2.0/UDP 166.34.245.230:54113From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Mon, 08 Mar 1993 22:36:40 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Timestamp: 731427042Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEContent-Type: application/sdpContent-Length: 137v=0o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231s=SIP Callt=0 0c=IN IP4 166.34.245.231m=audio 20038 RTP/AVP 0*Mar 8 17:36:44: Queued event From SIP SPI to CCAPI/DNS : SIPSPI_EV_CC_CALL_CONNECT*Mar 8 17:36:44: CCSIP-SPI-CONTROL: act_sentalert_connect*Mar 8 17:36:44: sipSPIAddLocalContact*Mar 8 17:36:44: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE*Mar 8 17:36:44: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 8 17:36:44: 0x624D8CCC : State change from (STATE_SENT_ALERTING, SUBSTATE_NONE) to (STATE_SENT_SUCCESS, SUBSTATE_NONE)*Mar 8 17:36:44: Sent:SIP/2.0 200 OKVia: SIP/2.0/UDP 166.34.245.230:54113From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7FDate: Mon, 08 Mar 1993 22:36:40 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Timestamp: 731427042Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledContact: <sip:3660210@166.34.245.231:5060;user=phone>CSeq: 101 INVITEContent-Type: application/sdpContent-Length: 137v=0o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231s=SIP Callt=0 0c=IN IP4 166.34.245.231m=audio 20038 RTP/AVP 0*Mar 8 17:36:44: Received:ACK sip:3660210@166.34.245.231:5060;user=phone SIP/2.0Via: SIP/2.0/UDP 166.34.245.230:54113From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7FDate: Sat, 06 Mar 1993 19:10:42 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Max-Forwards: 6Content-Type: application/sdpContent-Length: 137CSeq: 101 ACKv=0o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230s=SIP Callt=0 0c=IN IP4 166.34.245.230m=audio 20208 RTP/AVP 0*Mar 8 17:36:44: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:54113*Mar 8 17:36:44: CCSIP-SPI-CONTROL: act_sentsucc_new_message*Mar 8 17:36:44: CCSIP-SPI-CONTROL: sip_stats_method*Mar 8 17:36:44: 0x624D8CCC : State change from (STATE_SENT_SUCCESS, SUBSTATE_NONE) to (STATE_ACTIVE, SUBSTATE_NONE)*Mar 8 17:36:44: The Call Setup Information is :Call Control Block (CCB) : 0x624D8CCCState of The Call : STATE_ACTIVETCP Sockets Used : NOCalling Number : 3660110Called Number : 3660210Negotiated Codec : g711ulawSource IP Address (Media): 166.34.245.231Source IP Port (Media): 20038Destn IP Address (Media): 166.34.245.230Destn IP Port (Media): 20208Destn SIP Addr (Control) : 166.34.245.230Destn SIP Port (Control) : 5060Destination Name : 166.34.245.230*Mar 8 17:36:47: Queued event From SIP SPI to CCAPI/DNS : SIPSPI_EV_CC_CALL_DISCONNECT*Mar 8 17:36:47: CCSIP-SPI-CONTROL: act_active_disconnect*Mar 8 17:36:47: Queued event from SIP SPI : SIPSPI_EV_CREATE_CONNECTION*Mar 8 17:36:47: 0x624D8CCC : State change from (STATE_ACTIVE, SUBSTATE_NONE) to (STATE_ACTIVE, SUBSTATE_CONNECTING)*Mar 8 17:36:47: REQUEST CONNECTION TO IP:166.34.245.230 PORT:5060*Mar 8 17:36:47: 0x624D8CCC : State change from (STATE_ACTIVE, SUBSTATE_CONNECTING) to (STATE_ACTIVE, SUBSTATE_CONNECTING)*Mar 8 17:36:47: CCSIP-SPI-CONTROL: act_active_connection_created*Mar 8 17:36:47: CCSIP-SPI-CONTROL: sipSPICheckSocketConnection*Mar 8 17:36:47: CCSIP-SPI-CONTROL: sipSPICheckSocketConnection: Connid(1) created to 166.34.245.230:5060, local_port 54835*Mar 8 17:36:47: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE*Mar 8 17:36:47: CCSIP-SPI-CONTROL: sip_stats_method*Mar 8 17:36:47: 0x624D8CCC : State change from (STATE_ACTIVE, SUBSTATE_CONNECTING) to (STATE_DISCONNECTING, SUBSTATE_NONE)*Mar 8 17:36:47: Sent:BYE sip:3660110@166.34.245.230:5060;user=phone SIP/2.0Via: SIP/2.0/UDP 166.34.245.231:54835From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7FTo: "3660110" <sip:3660110@166.34.245.230>Date: Mon, 08 Mar 1993 22:36:44 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledMax-Forwards: 6Timestamp: 731612207CSeq: 101 BYEContent-Length: 0*Mar 8 17:36:47: Received:SIP/2.0 200 OKVia: SIP/2.0/UDP 166.34.245.231:54835From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7FTo: "3660110" <sip:3660110@166.34.245.230>Date: Sat, 06 Mar 1993 19:10:50 GMTCall-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledTimestamp: 731612207Content-Length: 0CSeq: 101 BYE*Mar 8 17:36:47: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:54113*Mar 8 17:36:47: CCSIP-SPI-CONTROL: act_disconnecting_new_message*Mar 8 17:36:47: CCSIP-SPI-CONTROL: sact_disconnecting_new_message_response*Mar 8 17:36:47: CCSIP-SPI-CONTROL: sipSPICheckResponse*Mar 8 17:36:47: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 8 17:36:47: Roundtrip delay 4 milliseconds for method BYE*Mar 8 17:36:47: CCSIP-SPI-CONTROL: sipSPICallCleanup*Mar 8 17:36:47: Queued event from SIP SPI : SIPSPI_EV_CLOSE_CONNECTION*Mar 8 17:36:47: CLOSE CONNECTION TO CONNID:1*Mar 8 17:36:47: sipSPIIcpifUpdate :CallState: 4 Playout: 1265 DiscTime:66820800 ConnTime 66820420*Mar 8 17:36:47: 0x624D8CCC : State change from (STATE_DISCONNECTING, SUBSTATE_NONE) to (STATE_DEAD, SUBSTATE_NONE)*Mar 8 17:36:47: The Call Setup Information is :Call Control Block (CCB) : 0x624D8CCCState of The Call : STATE_DEADTCP Sockets Used : NOCalling Number : 3660110Called Number : 3660210Negotiated Codec : g711ulawSource IP Address (Media): 166.34.245.231Source IP Port (Media): 20038Destn IP Address (Media): 166.34.245.230Destn IP Port (Media): 20208Destn SIP Addr (Control) : 166.34.245.230Destn SIP Port (Control) : 5060Destination Name : 166.34.245.230*Mar 8 17:36:47:Disconnect Cause (CC) : 16Disconnect Cause (SIP) : 200*Mar 8 17:36:47: udpsock_close_connect: Socket fd: 1 closed for connid 1 with remote port: 5060Related Commands
debug ccsip calls
To show all Session Initiation Protocol (SIP) Service Provider Interface (SPI) call tracing, use the debug ccsip calls command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccsip calls
no debug ccsip calls
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command traces the SIP call details as they are updated in the SIP call control block.
Examples
The following example displays debug output from one side of the call:
Router1# debug ccsip callsSIP Call statistics tracing is enabledRouter1#*Mar 6 14:12:33: The Call Setup Information is :Call Control Block (CCB) : 0x624D078CState of The Call : STATE_ACTIVETCP Sockets Used : NOCalling Number : 3660110Called Number : 3660210Negotiated Codec : g711ulawSource IP Address (Media): 166.34.245.230Source IP Port (Media): 20644Destn IP Address (Media): 166.34.245.231Destn IP Port (Media): 20500Destn SIP Addr (Control) : 166.34.245.231Destn SIP Port (Control) : 5060Destination Name : 166.34.245.231*Mar 6 14:12:40: The Call Setup Information is :Call Control Block (CCB) : 0x624D078CState of The Call : STATE_DEADTCP Sockets Used : NOCalling Number : 3660110Called Number : 3660210Negotiated Codec : g711ulawSource IP Address (Media): 166.34.245.230Source IP Port (Media): 20644Destn IP Address (Media): 166.34.245.231Destn IP Port (Media): 20500Destn SIP Addr (Control) : 166.34.245.231Destn SIP Port (Control) : 5060Destination Name : 166.34.245.231*Mar 6 14:12:40:Disconnect Cause (CC) : 16Disconnect Cause (SIP) : 200The following example displays debug output from the other side of the call:
Router2# debug ccsip callsSIP Call statistics tracing is enabledRouter2#*Mar 8 17:38:31: The Call Setup Information is :Call Control Block (CCB) : 0x624D9560State of The Call : STATE_ACTIVETCP Sockets Used : NOCalling Number : 3660110Called Number : 3660210Negotiated Codec : g711ulawSource IP Address (Media): 166.34.245.231Source IP Port (Media): 20500Destn IP Address (Media): 166.34.245.230Destn IP Port (Media): 20644Destn SIP Addr (Control) : 166.34.245.230Destn SIP Port (Control) : 5060Destination Name : 166.34.245.230*Mar 8 17:38:38: The Call Setup Information is:Call Control Block (CCB) : 0x624D9560State of The Call : STATE_DEADTCP Sockets Used : NOCalling Number : 3660110Called Number : 3660210Negotiated Codec : g711ulawSource IP Address (Media): 166.34.245.231Source IP Port (Media): 20500Destn IP Address (Media): 166.34.245.230Destn IP Port (Media): 20644Destn SIP Addr (Control) : 166.34.245.230Destn SIP Port (Control) : 5060Destination Name : 166.34.245.230*Mar 8 17:38:38:Disconnect Cause (CC) : 16Disconnect Cause (SIP) : 200Related Commands
debug ccsip dhcp
To display debugging related information on Session Initiation Protocol (SIP) and Dynamic Host Configuration Protocol (DHCP) interaction, when SIP parameters are provisoned by DHCP, use the debug ccsip dhcp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccsip dhcp
no debug ccsip dhcp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
12.4(22)YB
This command was introduced.
15.0(1)M
This command was integrated in Cisco IOS Release 15.0(1)M.
Usage Guidelines
The debug ccsip dhcp command can be enabled by executing the command itself or by issuing the debug ccsip all command.
Examples
The following example displays debug output from the debug ccsip dhcp command:
Router# debug ccsip dhcpNov 18 17:20:48.881: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_register_configured_dest_patterns: No destination patterns to RegisterNov 18 17:20:48.881: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_spi_register_free_rcb: Freeing rcbNov 18 17:20:48.881: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_register_reset_dns_cache: CCSIP_REGISTER:: Primary registrar DNS resolved addr resetNov 18 17:21:00.965: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/config_credential_trigger_reg: Query DHCP for provisioned info upon credential dhcp configNov 18 17:21:00.965: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/sipua_query_dhcp_reg_info: DHCP provisioned option 125 availableNov 18 17:21:00.965: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: parsing data in option 125 of length 73Nov 18 17:21:00.965: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: enterprise ID 210Nov 18 17:21:00.965: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: total option data length 80Nov 18 17:21:00.965: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: sub-option type 201 of length 6Nov 18 17:21:00.965: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_subopt_macaddr: MAC addr 1234567890ABNov 18 17:21:00.969:Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: sub-option type 202 of length 6Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_subopt_contract_num: pilot # 777777Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: sub-option type 203 of length 6Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_subopt_addn_num: secondary # 222222 (index 0)Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: sub-option type 203 of length 6Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_subopt_addn_num: secondary # 333333 (index 1)Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: sub-option type 203 of length 6Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_subopt_addn_num: secondary # 444444 (index 2)Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: sub-option type 203 of length 6Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_subopt_addn_num: secondary # 555555 (index 3)Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: sub-option type 203 of length 6Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_subopt_addn_num: secondary # 666666 (index 4)Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: sub-option type 204 of length 14Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_subopt_domain: domain sublen 5Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_subopt_domain: domain sublen 3Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_subopt_domain: domain dns:cisco.comNov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/ccsip_gw_parse_dhcp_opt125: parsing of DHCP option 125 succeededNov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/SIP-DHCP/sipua_query_dhcp_reg_info: DHCP provisioned SIP server addr: 9.13.2.36Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_register_cred_user: Sending msg type 2 to register process from parser for user 777777Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_spi_register_process_e164_registration: CCSIP_REGISTER:: e164 number (777777)Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_register_search_e164_table: ****No entry found in E164 TableNov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/Info/sipSPIAddContextToTable: Added context(0x476FD758) with key=[1061] to tableNov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/Info/sipSPIGetOutboundHostAndDestHostPrivate: CCSIP: target_host : cisco.com target_port : 5060Nov 18 17:21:00.969: //-1/000000000000/SIP/Info/sipSPIValidateAndCopyOutboundHost: CCSIP: copy target_host to outbound_hostNov 18 17:21:00.969: //-1/000000000000/SIP/State/sipSPIChangeState: 0x476FD758 : State change from (STATE_NONE, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_NONE)Nov 18 17:21:00.969: //-1/000000000000/SIP/Info/ccsip_spi_registrar_add_expires_header: Inside ccsip_spi_registrar_add_expires_header for ExpiresNov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/Event/sipSPIEventInfo: Queued event from SIP SPI : SIPSPI_EV_OUTBOUND_REGISTERNov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_register_add_to_e164_table: ****Added to E164 TableNov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event: ccsip_spi_get_msg_type returned: 3 for event 40Nov 18 17:21:00.969: //-1/000000000000/SIP/Info/act_idle_outgoing_register: In act_idle_outgoing_registerNov 18 17:21:00.969: //1034/000000000000/SIP/Info/act_idle_outgoing_register: Send REGISTER to cisco.com:5060Nov 18 17:21:00.969: //1034/000000000000/SIP/Info/sipSPIUaddCcbToUACTable: ****Adding to UAC table.Nov 18 17:21:00.969: //1034/000000000000/SIP/Info/sipSPIUaddCcbToTable: Added to table. ccb=0x476FD758 key=1AF6E28A-B4CC11DD-81078B9C-6E99E02BNov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/Event/sipSPIEventInfo: Queued event from SIP SPI : SIPSPI_EV_DNS_RESOLVENov 18 17:21:00.969: //1034/000000000000/SIP/State/sipSPIChangeState: 0x476FD758 : State change from (STATE_IDLE, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_SENT_DNS)Nov 18 17:21:00.969: //1034/000000000000/SIP/State/sipSPIChangeState: 0x476FD758 : State change from (STATE_IDLE, SUBSTATE_SENT_DNS) to (SIP_STATE_OUTGOING_REGISTER, SUBSTATE_SENT_DNS)Nov 18 17:21:00.969: //-1/xxxxxxxxxxxx/SIP/Info/sip_dns_type_srv_query: TYPE SRV query for _sip._udp.cisco.com and type:1Nov 18 17:21:00.977: //-1/xxxxxxxxxxxx/SIP/Info/sip_dns_type_a_aaaa_query: DNS query for cisco.com and type:1Nov 18 17:21:00.977: //-1/xxxxxxxxxxxx/SIP/Info/sip_dns_type_a_query: TYPE A query successful for cisco.comNov 18 17:21:00.977: //-1/xxxxxxxxxxxx/SIP/Info/sip_dns_type_a_aaaa_query: IP Address of cisco.com is:Nov 18 17:21:00.977: //-1/xxxxxxxxxxxx/SIP/Info/sip_dns_type_a_aaaa_query: 9.13.2.36Nov 18 17:21:00.977: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event: ccsip_spi_get_msg_type returned: 2 for event 43Nov 18 17:21:00.977: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_register_set_dns_resolved_address: CCSIP_REGISTER:: Primary registrar DNS resolved addr set to 0.0.0.1:151847460Nov 18 17:21:00.977: //-1/xxxxxxxxxxxx/SIP/Info/ccsipRegisterStartExpiresTimer: Starting timer for pattern for 3600 secondsNov 18 17:21:00.977: //1034/000000000000/SIP/State/sipSPIChangeState: 0x476FD758 : State change from (SIP_STATE_OUTGOING_REGISTER, SUBSTATE_SENT_DNS) to (SIP_STATE_OUTGOING_REGISTER, SUBSTATE_NONE)Nov 18 17:21:00.977: //-1/xxxxxxxxxxxx/SIP/Info/sipSPISetDateHeader: Clock Time Zone is UTC, same as GMT: Using GMTNov 18 17:21:00.981: //1034/000000000000/SIP/Info/sipSPISendRegister: Associated container=0x46794ACC to RegisterNov 18 17:21:00.981: //1034/000000000000/SIP/Transport/sipSPISendRegister: Sending REGISTER to the transport layerNov 18 17:21:00.981: //1034/000000000000/SIP/Transport/sipSPIGetSwitchTransportFlag: Return the Dial peer configuration, Switch Transport is FALSENov 18 17:21:00.981: //1034/000000000000/SIP/Transport/sipSPITransportSendMessage: msg=0x4707F998, addr=9.13.2.36, port=5060, sentBy_port=0, is_req=1, transport=1, switch=0, callBack=0x415A53B0Nov 18 17:21:00.981: //1034/000000000000/SIP/Transport/sipSPITransportSendMessage: Proceedable for sending msg immediatelyNov 18 17:21:00.981: //1034/000000000000/SIP/Transport/sipTransportLogicSendMsg: switch transport is 0Nov 18 17:21:00.981: //1034/000000000000/SIP/Transport/sipTransportLogicSendMsg: Set to send the msg=0x4707F998Nov 18 17:21:00.981: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportPostSendMessage: Posting send for msg=0x4707F998, addr=9.13.2.36, port=5060, connId=2 for UDPNov 18 17:21:00.981: //1034/000000000000/SIP/State/sipSPIChangeState: 0x476FD758 : State change from (SIP_STATE_OUTGOING_REGISTER, SUBSTATE_NONE) to (SIP_STATE_OUTGOING_REGISTER, SUBSTATE_NONE)Nov 18 17:21:00.981: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:REGISTER sip:cisco.com:5060 SIP/2.0Date: Tue, 18 Nov 2008 17:21:00 GMTFrom: <sip:777777@cisco.com>;tag=34FBAED8-131Supported: pathTimestamp: 1227028860Content-Length: 0User-Agent: Cisco-SIPGateway/IOS-12.xTo: <sip:777777@cisco.com>Contact: <sip:777777@9.13.8.183:5060>Expires: 3600Call-ID: 1AF6E28A-B4CC11DD-81078B9C-6E99E02BVia: SIP/2.0/UDP 9.13.8.183:5060;branch=z9hG4bK3F522D9CSeq: 2 REGISTERMax-Forwards: 70Nov 18 17:21:00.981: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpIPv4SocketReads: Msg enqueued for SPI with IP addr: [9.13.2.36]:56305Nov 18 17:21:00.981: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event: ccsip_spi_get_msg_type returned: 2 for event 1Nov 18 17:21:00.981: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x00000000Nov 18 17:21:00.985: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor: Checking Invite DialogNov 18 17:21:00.985: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 100 TryingVia: SIP/2.0/UDP 9.13.8.183:5060;received=9.13.8.183;branch=z9hG4bK3F522D9Call-ID: 1AF6E28A-B4CC11DD-81078B9C-6E99E02BFrom: <sip:777777@cisco.com>;tag=34FBAED8-131To: <sip:777777@cisco.com>CSeq: 2 REGISTERContent-Length: 0Nov 18 17:21:01.077: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpIPv4SocketReads: Msg enqueued for SPI with IP addr: [9.13.2.36]:56306Nov 18 17:21:01.077: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event: ccsip_spi_get_msg_type returned: 2 for event 1Nov 18 17:21:01.077: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x00000000Nov 18 17:21:01.077: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor: Checking Invite DialogNov 18 17:21:01.077: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 200 OKVia: SIP/2.0/UDP 9.13.8.183:5060;received=9.13.8.183;branch=z9hG4bK3F522D9Call-ID: 1AF6E28A-B4CC11DD-81078B9C-6E99E02BFrom: <sip:777777@cisco.com>;tag=34FBAED8-131To: <sip:777777@cisco.com>CSeq: 2 REGISTERContact: <sip:777777@9.13.8.183:5060>;expires=3600Content-Length: 0Nov 18 17:21:01.077: //1034/000000000000/SIP/Info/ccsip_gw_register_process_response: No P-Assoicated-URI present in Register ResponseNov 18 17:21:01.077: //-1/xxxxxxxxxxxx/SIP/Info/ccsipRegisterStartExpiresTimer: Starting timer for pattern 777777 for 2880 secondsNov 18 17:21:01.077: //-1/xxxxxxxxxxxx/SIP/Info/sipSPIDeleteContextFromTable: Context for key=[1061] removed.Nov 18 17:21:01.077: //1034/000000000000/SIP/Info/sipSPIUdeleteCcbFromUACTable: ****Deleting from UAC table.Nov 18 17:21:01.077: //1034/000000000000/SIP/Info/sipSPIUdeleteCcbFromTable: Deleting from table. ccb=0x476FD758 key=1AF6E28A-B4CC11DD-81078B9C-6E99E02BNov 18 17:21:01.077: //1034/000000000000/SIP/Info/sipSPIFlushEventBufferQueue: There are 0 events on the internal queue that are going to be free'dNov 18 17:21:01.077: //1034/000000000000/SIP/Info/ccsip_qos_cleanup: EntryNov 18 17:21:01.077: //1034/000000000000/SIP/Info/sipSPI_ipip_free_codec_profile: Codec Profiles FreedNov 18 17:21:01.077: //1034/000000000000/SIP/Info/sipSPIUfreeOneCCB: Freeing ccb 476FD758Nov 18 17:21:01.081: //-1/xxxxxxxxxxxx/SIP/Info/sipSPIGetContextFromTable: NO context for key[1061]Nov 18 17:21:02.761: %SYS-5-CONFIG_I: Configured from console by consoleCUBE-DHCP-CLIENT1#Related Commands
debug ccsip error
To show Session Initiation Protocol (SIP) Service Provider Interface (SPI) errors, use the debug ccsip error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccsip error
no debug ccip error
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command traces all error messages generated from errors encountered by the SIP subsystem.
Examples
The following example displays debug output from one side of the call:
Router1# debug ccsip errorSIP Call error tracing is enabledRouter1#*Mar 6 14:16:41: CCSIP-SPI-CONTROL: act_idle_call_setup*Mar 6 14:16:41: act_idle_call_setup:Not using Voice Class Codec*Mar 6 14:16:41: act_idle_call_setup: preferred_codec set[0] type :g711ulaw bytes: 160*Mar 6 14:16:41: REQUEST CONNECTION TO IP:166.34.245.231 PORT:5060*Mar 6 14:16:41: CCSIP-SPI-CONTROL: act_idle_connection_created*Mar 6 14:16:41: CCSIP-SPI-CONTROL: act_idle_connection_created: Connid(1) created to 166.34.245.231:5060, local_port 55674*Mar 6 14:16:41: sipSPIAddLocalContact*Mar 6 14:16:41: CCSIP-SPI-CONTROL: sip_stats_method*Mar 6 14:16:41: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060*Mar 6 14:16:41: CCSIP-SPI-CONTROL: act_sentinvite_new_message*Mar 6 14:16:41: CCSIP-SPI-CONTROL: sipSPICheckResponse*Mar 6 14:16:41: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 6 14:16:41: Roundtrip delay 4 milliseconds for method INVITE*Mar 6 14:16:41: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060*Mar 6 14:16:41: CCSIP-SPI-CONTROL: act_recdproc_new_message*Mar 6 14:16:41: CCSIP-SPI-CONTROL: sipSPICheckResponse*Mar 6 14:16:41: CCSIP-SPI-CONTROL: sipSPICheckResponse : Updating session description*Mar 6 14:16:41: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 6 14:16:41: Roundtrip delay 8 milliseconds for method INVITE*Mar 6 14:16:41: HandleSIP1xxRinging: SDP MediaTypes negotiation successful!Negotiated Codec : g711ulaw , bytes :160Inband Alerting : 0*Mar 6 14:16:45: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060*Mar 6 14:16:45: CCSIP-SPI-CONTROL: act_recdproc_new_message*Mar 6 14:16:45: CCSIP-SPI-CONTROL: sipSPICheckResponse*Mar 6 14:16:45: CCSIP-SPI-CONTROL: sipSPICheckResponse : Updating session description*Mar 6 14:16:45: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 6 14:16:45: Roundtrip delay 3844 milliseconds for method INVITE*Mar 6 14:16:45: CCSIP-SPI-CONTROL: act_recdproc_new_message: SDP MediaTypes negotiation successful!Negotiated Codec : g711ulaw , bytes :160*Mar 6 14:16:45: CCSIP-SPI-CONTROL: sipSPIReconnectConnection*Mar 6 14:16:45: CCSIP-SPI-CONTROL: recv_200_OK_for_invite*Mar 6 14:16:45: CCSIP-SPI-CONTROL: sip_stats_method*Mar 6 14:16:45: HandleUdpReconnection: Udp socket connected for fd: 1 with 166.34.245.231:5060*Mar 6 14:16:45: CCSIP-SPI-CONTROL: ccsip_caps_ind*Mar 6 14:16:45: ccsip_caps_ind: Load DSP with codec (5) g711ulaw, Bytes=160*Mar 6 14:16:45: ccsip_caps_ind: set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE*Mar 6 14:16:45: CCSIP-SPI-CONTROL: ccsip_caps_ack*Mar 6 14:16:49: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:56101*Mar 6 14:16:49: CCSIP-SPI-CONTROL: act_active_new_message*Mar 6 14:16:49: CCSIP-SPI-CONTROL: sact_active_new_message_request*Mar 6 14:16:49: CCSIP-SPI-CONTROL: sip_stats_method*Mar 6 14:16:49: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 6 14:16:49: CCSIP-SPI-CONTROL: sipSPIInitiateCallDisconnect : Initiate call disconnect(16) for outgoing call*Mar 6 14:16:49: CCSIP-SPI-CONTROL: act_disconnecting_disconnect*Mar 6 14:16:49: CCSIP-SPI-CONTROL: sipSPICallCleanup*Mar 6 14:16:49: CLOSE CONNECTION TO CONNID:1*Mar 6 14:16:49: sipSPIIcpifUpdate :CallState: 4 Playout: 2945 DiscTime:48340988 ConnTime 48340525*Mar 6 14:16:49: udpsock_close_connect: Socket fd: 1 closed for connid 1 with remote port: 5060The following example displays debug output from the other side of the call:
Router2# debug ccsip errorSIP Call error tracing is enabledRouter2#*Mar 8 17:42:39: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:55674*Mar 8 17:42:39: CCSIP-SPI-CONTROL: sipSPISipIncomingCall*Mar 8 17:42:39: CCSIP-SPI-CONTROL: act_idle_new_message*Mar 8 17:42:39: CCSIP-SPI-CONTROL: sact_idle_new_message_invite*Mar 8 17:42:39: CCSIP-SPI-CONTROL: sip_stats_method*Mar 8 17:42:39: sact_idle_new_message_invite:Not Using Voice Class Codec*Mar 8 17:42:39: sact_idle_new_message_invite: Preferred codec[0] type: g711ulaw Bytes :160*Mar 8 17:42:39: sact_idle_new_message_invite: Media Negotiation successful for anincoming call*Mar 8 17:42:39: sact_idle_new_message_invite: Negotiated Codec : g711ulaw, bytes :160Preferred Codec : g711ulaw, bytes :160*Mar 8 17:42:39: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 8 17:42:39: Num of Contact Locations 1 3660110 166.34.245.230 5060*Mar 8 17:42:39: CCSIP-SPI-CONTROL: act_recdinvite_proceeding*Mar 8 17:42:39: CCSIP-SPI-CONTROL: ccsip_caps_ind*Mar 8 17:42:39: ccsip_caps_ind: codec(negotiated) = 5(Bytes 160)*Mar 8 17:42:39: ccsip_caps_ind: Load DSP with codec (5) g711ulaw, Bytes=160*Mar 8 17:42:39: ccsip_caps_ind: set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE*Mar 8 17:42:39: CCSIP-SPI-CONTROL: ccsip_caps_ack*Mar 8 17:42:39: CCSIP-SPI-CONTROL: act_recdinvite_alerting*Mar 8 17:42:39: 180 Ringing with SDP - not likely*Mar 8 17:42:39: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 8 17:42:42: CCSIP-SPI-CONTROL: act_sentalert_connect*Mar 8 17:42:42: sipSPIAddLocalContact*Mar 8 17:42:42: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 8 17:42:42: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:55674*Mar 8 17:42:42: CCSIP-SPI-CONTROL: act_sentsucc_new_message*Mar 8 17:42:42: CCSIP-SPI-CONTROL: sip_stats_method*Mar 8 17:42:47: CCSIP-SPI-CONTROL: act_active_disconnect*Mar 8 17:42:47: REQUEST CONNECTION TO IP:166.34.245.230 PORT:5060*Mar 8 17:42:47: CCSIP-SPI-CONTROL: act_active_connection_created*Mar 8 17:42:47: CCSIP-SPI-CONTROL: sipSPICheckSocketConnection*Mar 8 17:42:47: CCSIP-SPI-CONTROL: sipSPICheckSocketConnection: Connid(1) created to 166.34.245.230:5060, local_port 56101*Mar 8 17:42:47: CCSIP-SPI-CONTROL: sip_stats_method*Mar 8 17:42:47: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:55674*Mar 8 17:42:47: CCSIP-SPI-CONTROL: act_disconnecting_new_message*Mar 8 17:42:47: CCSIP-SPI-CONTROL: sact_disconnecting_new_message_response*Mar 8 17:42:47: CCSIP-SPI-CONTROL: sipSPICheckResponse*Mar 8 17:42:47: CCSIP-SPI-CONTROL: sip_stats_status_code*Mar 8 17:42:47: Roundtrip delay 0 milliseconds for method BYE*Mar 8 17:42:47: CCSIP-SPI-CONTROL: sipSPICallCleanup*Mar 8 17:42:47: CLOSE CONNECTION TO CONNID:1*Mar 8 17:42:47: sipSPIIcpifUpdate :CallState: 4 Playout: 1255 DiscTime:66856757 ConnTime 66856294*Mar 8 17:42:47: udpsock_close_connect: Socket fd: 1 closed for connid 1 with remote port: 5060Related Commands
debug ccsip events
To enable tracing of events that are specific to service provider interface (SPI), use the debug ccsip events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccsip events
no debug ccsip events
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command previously traced all events posted to Session Initiation Protocol (SIP) SPI from all interfaces and also provided general SIP SPI information. Beginning with Cisco IOS Release 12.2(15)T, the debug ccsip events command displays only debugging information specifically related to SIP SPI events. Media stream and SIP SPI information is now reported in the debug ccsip media and debug ccsip info command output.
Note
Examples
The following is sample output from the debug ccsip events command for a Cisco 3660:
Router# debug ccsip eventsSIP Call events tracing is enabledRouter#Nov 15 18:20:25.779: Queued event from SIP SPI : SIPSPI_EV_CC_CALL_SETUPNov 15 18:20:25.779: Queued event from SIP SPI : SIPSPI_EV_CREATE_CONNECTIONNov 15 18:20:25.783: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGENov 15 18:20:25.815: Queued event from SIP SPI : SIPSPI_EV_CREATE_CONNECTIONNov 15 18:20:25.819: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGENov 15 18:20:28.339: Queued event from SIP SPI : SIPSPI_EV_CLOSE_CONNECTIONNov 15 18:20:28.339: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGENov 15 18:20:50.844: Queued event from SIP SPI : SIPSPI_EV_CLOSE_CONNECTIONNov 15 18:20:50.844: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGENov 15 18:20:50.848: Queued event from SIP SPI : SIPSPI_EV_CC_CALL_DISCONNECTRelated Commands
debug ccsip all
Enables all SIP-related debugging.
debug ccsip info
Enables tracing of general SIP SPI information.
debug ccsip media
Enables tracing of SIP call media streams.
debug ccsip info
To enable tracing of general service provider interface (SPI) information, use the debug ccsip info command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccsip info
no debug ccsip info
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Beginning in Cisco IOS Release 12.2(15)T, the debug ccsip info command is a separate option that displays general SIP SPI information for debug purposes. In past releases, this output was part of the debug ccsip events command.
Note
Examples
The following is sample output from the debug ccsip info command for a Cisco 3660:
Router# debug ccsip infoSIP Call info tracing is enabledRouter#Nov 15 18:19:22.670: ****Adding to UAC tableNov 15 18:19:22.670: adding call id E to tableNov 15 18:19:22.670: CCSIP-SPI-CONTROL: act_idle_call_setupNov 15 18:19:22.670: act_idle_call_setup:Not using Voice Class CodecNov 15 18:19:22.670: act_idle_call_setup: preferred_codec set[0] type :g729r8 bytes: 20Nov 15 18:19:22.670: sipSPICopyPeerDataToCCB: From CLI: Modem NSE payload = 100, Passthrough = 0,Modem relay = 0, Gw-Xid = 1SPRT latency 200, SPRT Retries = 12, Dict Size = 1024String Len = 32, Compress dir = 3Nov 15 18:19:22.670: ****Deleting from UAC tableNov 15 18:19:22.670: ****Adding to UAC tableNov 15 18:19:22.670: sipSPIUsetBillingProfile: sipCallId for billing records = 20A40C3B-D92C11D5-8015E1CC-C91F3F10@12.18.195.49Nov 15 18:19:22.674: CCSIP-SPI-CONTROL: act_idle_connection_createdNov 15 18:19:22.674: CCSIP-SPI-CONTROL: act_idle_connection_created: Connid(1) created to 172.18.193.190:5060, local_port 56981Nov 15 18:19:22.674: CCSIP-SPI-CONTROL: sipSPIOutgoingCallSDPNov 15 18:19:22.674: convert_codec_bytes_to_ptime: Values :Codec: g729r8 codecbytes :20, ptime: 10Nov 15 18:19:22.674: sip_generate_sdp_xcaps_list: Modem Relay disabled. X-cap not neededNov 15 18:19:22.674: sipSPIAddLocalContactNov 15 18:19:22.674: sip_stats_methodNov 15 18:19:22.690: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 172.18.193.190:5060Nov 15 18:19:22.690: CCSIP-SPI-CONTROL: act_sentinvite_new_messageNov 15 18:19:22.690: CCSIP-SPI-CONTROL: sipSPICheckResponseNov 15 18:19:22.690: sip_stats_status_codeNov 15 18:19:22.690: Roundtrip delay 16 milliseconds for method INVITENov 15 18:19:22.706: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 172.18.193.190:5060Nov 15 18:19:22.706: CCSIP-SPI-CONTROL: act_recdproc_new_messageNov 15 18:19:22.706: CCSIP-SPI-CONTROL: sipSPICheckResponseNov 15 18:19:22.706: sip_stats_status_codeNov 15 18:19:22.706: Roundtrip delay 32 milliseconds for method INVITENov 15 18:19:22.706: sipSPIGetSdpBody : Parse incoming session descriptionNov 15 18:19:22.706: HandleSIP1xxSessionProgress: Content-Disposition received in 18x response:session;handling=requiredNov 15 18:19:22.706: sipSPIDoMediaNegotiation: number of m lines is 1Nov 15 18:19:22.706: sipSPIDoAudioNegotiation: Codec (g729r8) Negotiation Successful on Static PayloadNov 15 18:19:22.706: sipSPIDoPtimeNegotiation: One ptime attribute found - value:10Nov 15 18:19:22.706: convert_ptime_to_codec_bytes: Values :Codec: g729r8 ptime :10, codecbytes: 20Nov 15 18:19:22.710: convert_codec_bytes_to_ptime: Values :Codec: g729r8 codecbytes :20, ptime: 10Nov 15 18:19:22.710: sipSPIDoDTMFRelayNegotiation: m-line index 1Nov 15 18:19:22.710: sipSPIDoDTMFRelayNegotiation: Requested DTMF-RELAY option(s) not found in Preferred DTMF-RELAY option list!Nov 15 18:19:22.710: sip_sdp_get_modem_relay_cap_params:Nov 15 18:19:22.710: sip_sdp_get_modem_relay_cap_params: NSE payload from X-cap = 0Nov 15 18:19:22.710: sip_do_nse_negotiation: NSE Payload 100 found in SDPNov 15 18:19:22.710: sip_do_nse_negotiation: Remote NSE payload = local one = 100, Use itNov 15 18:19:22.710: sip_select_modem_relay_params: X-tmr not present in SDP. Disable modem relayNov 15 18:19:22.710: sipSPIDoQoSNegotiation - SDP body with media descriptionNov 15 18:19:22.710: ccsip_process_response_contact_record_routeNov 15 18:19:22.710: CCSIP-SPI-CONTROL: ccsip_bridge: confID = 4, srcCallID = 14, dstCallID = 13Nov 15 18:19:22.710: sipSPIUupdateCcCallIds: old src/dest ccCallids: -1/-1, new src/dest ccCallids: 14/13Nov 15 18:19:22.710: sipSPIUupdateCcCallIds: old streamcallid=-1, new streamcallid=14Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: ccsip_caps_indNov 15 18:19:22.710: ccsip_get_rtcp_session_parameters: CURRENT VALUES: stream_callid=14, current_seq_num=0x1B1BNov 15 18:19:22.710: ccsip_get_rtcp_session_parameters: NEW VALUES: stream_callid=14, current_seq_num=0x180CNov 15 18:19:22.710: ccsip_caps_ind: Load DSP with negotiated codec : g729r8, Bytes=20Nov 15 18:19:22.710: ccsip_caps_ind: set forking flag to 0x0Nov 15 18:19:22.710: sipSPISetDTMFRelayMode: set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE_AND_OOBNov 15 18:19:22.710: sip_set_modem_caps: Negotiation already Done. Set negotiated Modem capsNov 15 18:19:22.710: sip_set_modem_caps: Modem Relay & Passthru both disabledNov 15 18:19:22.710: sip_set_modem_caps: nse payload = 100, ptru mode = 0, ptru-codec=0, redundancy=0, xid=0, relay=0, sprt-retry=12, latecncy=200, compres-dir=3, dict=1024, strnlen=32Nov 15 18:19:22.710: ccsip_caps_ind: Load DSP with codec : g729r8, Bytes=20Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: ccsip_caps_ackNov 15 18:19:22.710: ccsip_caps_ack: set forking flag to 0x60FD1EACNov 15 18:19:22.710: CCSIP-SPI-CONTROL: act_recdproc_connection_createdNov 15 18:19:22.710: CCSIP-SPI-CONTROL: sipSPICheckSocketConnection: Connid(2) created to 172.18.193.190:5060, local_port 51663Nov 15 18:19:22.714: sip_stats_methodNov 15 18:19:22.722: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 172.18.193.190:5060Nov 15 18:19:22.722: CCSIP-SPI-CONTROL: act_recdproc_new_messageNov 15 18:19:22.722: CCSIP-SPI-CONTROL: sipSPICheckResponseNov 15 18:19:22.722: sip_stats_status_codeNov 15 18:19:22.722: Roundtrip delay 48 milliseconds for method PRACKNov 15 18:19:24.706: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 172.18.193.190:5060Nov 15 18:19:24.706: CCSIP-SPI-CONTROL: act_recdproc_new_messageNov 15 18:19:24.706: CCSIP-SPI-CONTROL: sipSPICheckResponseNov 15 18:19:24.706: sip_stats_status_codeNov 15 18:19:24.706: Roundtrip delay 2032 milliseconds for method PRACKNov 15 18:19:24.706: sipSPIGetSdpBody : Parse incoming session descriptionNov 15 18:19:24.710: CCSIP-SPI-CONTROL: sipSPIUACSessionTimerNov 15 18:19:24.710: CCSIP-SPI-CONTROL: act_recdproc_continue_200_processingNov 15 18:19:24.710: CCSIP-SPI-CONTROL: act_recdproc_continue_200_processing: *** This ccb is the parentNov 15 18:19:24.710: sipSPICompareRespMediaInfoNov 15 18:19:24.710: sipSPIDoMediaNegotiation: number of m lines is 1Nov 15 18:19:24.710: sipSPIDoAudioNegotiation: Codec (g729r8) Negotiation Successful on Static PayloadNov 15 18:19:24.710: sipSPIDoPtimeNegotiation: One ptime attribute found - value:10Nov 15 18:19:24.710: convert_ptime_to_codec_bytes: Values :Codec: g729r8 ptime :10, codecbytes: 20Nov 15 18:19:24.710: convert_codec_bytes_to_ptime: Values :Codec: g729r8 codecbytes :20, ptime: 10Nov 15 18:19:24.710: sipSPIDoDTMFRelayNegotiation: m-line index 1Nov 15 18:19:24.710: sipSPIDoDTMFRelayNegotiation: Requested DTMF-RELAY option(s) not found in Preferred DTMF-RELAY option list!Nov 15 18:19:24.710: sip_sdp_get_modem_relay_cap_params:Nov 15 18:19:24.710: sip_sdp_get_modem_relay_cap_params: NSE payload from X-cap = 0Nov 15 18:19:24.710: sip_do_nse_negotiation: NSE Payload 100 found in SDPNov 15 18:19:24.710: sip_do_nse_negotiation: Remote NSE payload = local one = 100, Use itNov 15 18:19:24.710: sip_select_modem_relay_params: X-tmr not present in SDP. Disable modem relayNov 15 18:19:24.710: sipSPIProcessMediaChangesNov 15 18:19:24.710: ccsip_process_response_contact_record_routeNov 15 18:19:24.710: CCSIP-SPI-CONTROL: sipSPIProcess200OKforinviteNov 15 18:19:24.710: sip_stats_methodNov 15 18:19:24.710: udpsock_close_connect: Socket fd: 1 closed for connid 1 with remote port: 5060Nov 15 18:19:37.479: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 172.18.193.190:52180Nov 15 18:19:37.483: ****Found CCB in UAC tableNov 15 18:19:37.483: CCSIP-SPI-CONTROL: act_active_new_messageNov 15 18:19:37.483: CCSIP-SPI-CONTROL: sact_active_new_message_requestNov 15 18:19:37.483: sip_stats_methodNov 15 18:19:37.483: sip_stats_status_codeNov 15 18:19:37.483: CCSIP-SPI-CONTROL: sipSPIInitiateCallDisconnect : Initiate call disconnect(16) for outgoing callNov 15 18:19:37.483: udpsock_close_connect: Socket fd: 2 closed for connid 2 with remote port: 5060Nov 15 18:19:37.483: CCSIP-SPI-CONTROL: act_disconnecting_disconnectNov 15 18:19:37.483: CCSIP-SPI-CONTROL: sipSPICallCleanupNov 15 18:19:37.483: sipSPIIcpifUpdate :CallState: 4 Playout: 10230 DiscTime:1745148 ConnTime 1743871Nov 15 18:19:37.483: ****Deleting from UAC tableNov 15 18:19:37.483: Removing call id ENov 15 18:19:37.483: freeing ccb 63330954Related Commands
debug ccsip media
To enable tracing of Session Initiation Protocol (SIP) call media streams, use the debug ccsip media command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccsip media
no debug ccsip media
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Beginning in Cisco IOS Release 12.2(15)T, the debug ccsip media command is a separate option that displays debugging information specific to SIP media stream processing. In past releases, this output was part of the debug ccsip events command.
Note
Examples
The following is sample output from the debug ccsip media command for a Cisco 3660:
Router# debug ccsip mediaSIP Call media tracing is enabledRouter#Nov 15 18:19:53.835: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49Nov 15 18:19:53.835: sipSPIReserveRtpPort: reserved port 16500 for stream 1Nov 15 18:19:53.867: sipSPIReplaceSDPNov 15 18:19:53.871: sipSPICopySdpInfoNov 15 18:19:53.871: sipSPIUpdCallWithSdpInfo:Preferred Codec : g729r8, bytes :20Preferred DTMF relay : inband-voicePreferred NTE payload : 101Early Media : NoDelayed Media : NoBridge Done : NoNew Media : NoDSP DNLD Reqd : NoNov 15 18:19:53.871: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49Nov 15 18:19:53.871: sipSPIUpdCallWithSdpInfo:M-line Index : 1State : STREAM_ADDING (3)Callid : -1Negotiated Codec : g729r8, bytes :20Negotiated DTMF relay : inband-voiceNegotiated NTE payload : 0Media Srce Addr/Port : 172.18.195.49:16500Media Dest Addr/Port : 172.18.193.190:19148Nov 15 18:19:53.871: sipSPIProcessRtpSessionsNov 15 18:19:53.871: sipSPIAddStream: Adding stream 1 (callid 16) to the VOIP RTP libraryNov 15 18:19:53.871: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49Nov 15 18:19:53.871: sipSPIUpdateRtcpSession: for m-line 1Nov 15 18:19:53.871: sipSPIUpdateRtcpSession: rtcp_session infoladdr = 172.18.195.49, lport = 16500, raddr = 172.18.193.190, rport=19148Nov 15 18:19:53.871: sipSPIUpdateRtcpSession: No rtp session, creating a new oneNov 15 18:19:53.871: sipSPISetStreamInfo: num_streams = 1Nov 15 18:19:53.871: sipSPISetStreamInfo: adding stream type 0 from mline 1Nov 15 18:19:53.871: sipSPISetStreamInfo: caps.stream_count=1, caps.stream[0].stream_type=0x1, caps.stream_list.xmitFunc=voip_rtp_xmit, caps.stream_list.context=0x634F1F2C (gccb)Nov 15 18:19:55.555: sipSPICompareSDPNov 15 18:19:55.555: sipSPICompareStreams: stream 1 dest_port: old=19148 new=19148Nov 15 18:19:55.555: sipSPICompareStreams: Flags set for stream 1: RTP_CHANGE=No CAPS_CHANGE=NoNov 15 18:19:55.555: sipSPICompareSDP: Flags set for call: NEW_MEDIA=No DSPDNLD_REQD=NoNov 15 18:19:55.555: sipSPIReplaceSDPNov 15 18:19:55.555: sipSPICopySdpInfoNov 15 18:19:55.555: sipSPIUpdCallWithSdpInfo:Preferred Codec : g729r8, bytes :20Preferred DTMF relay : inband-voicePreferred NTE payload : 101Early Media : NoDelayed Media : NoBridge Done : YesNew Media : NoDSP DNLD Reqd : NoNov 15 18:19:55.555: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49Nov 15 18:19:55.555: sipSPIUpdCallWithSdpInfo:M-line Index : 1State : STREAM_ACTIVE (3)Callid : 16Negotiated Codec : g729r8, bytes :20Negotiated DTMF relay : inband-voiceNegotiated NTE payload : 0Media Srce Addr/Port : 172.18.195.49:16500Media Dest Addr/Port : 172.18.193.190:19148Related Commands
debug ccsip messages
To show all Session Initiation Protocol (SIP) Service Provider Interface (SPI) message tracing, use the debug ccsip messages command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccsip messages
no debug ccsip messages
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command traces the Session Initiation Protocol (SIP) messages exchanged between the SIP UA client (UAC) and the access server.
Examples
The following example shows debug output from one side of the call:
Router1# debug ccsip messagesSIP Call messages tracing is enabledRouter1#*Mar 6 14:19:14: Sent:INVITE sip:3660210@166.34.245.231;user=phone;phone-context=unknown SIP/2.0Via: SIP/2.0/UDP 166.34.245.230:55820From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Sat, 06 Mar 1993 19:19:14 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Cisco-Guid: 2881152943-2184249568-0-483551624User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEMax-Forwards: 6Timestamp: 731427554Contact: <sip:3660110@166.34.245.230:5060;user=phone>Expires: 180Content-Type: application/sdpContent-Length: 138v=0o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230s=SIP Callt=0 0c=IN IP4 166.34.245.230m=audio 20762 RTP/AVP 0*Mar 6 14:19:14: Received:SIP/2.0 100 TryingVia: SIP/2.0/UDP 166.34.245.230:55820From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Mon, 08 Mar 1993 22:45:12 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Timestamp: 731427554Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEContent-Length: 0*Mar 6 14:19:14: Received:SIP/2.0 180 RingingVia: SIP/2.0/UDP 166.34.245.230:55820From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Mon, 08 Mar 1993 22:45:12 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Timestamp: 731427554Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEContent-Type: application/sdpContent-Length: 138v=0o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231s=SIP Callt=0 0c=IN IP4 166.34.245.231m=audio 20224 RTP/AVP 0*Mar 6 14:19:16: Received:SIP/2.0 200 OKVia: SIP/2.0/UDP 166.34.245.230:55820From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357Date: Mon, 08 Mar 1993 22:45:12 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Timestamp: 731427554Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledContact: <sip:3660210@166.34.245.231:5060;user=phone>CSeq: 101 INVITEContent-Type: application/sdpContent-Length: 138v=0o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231s=SIP Callt=0 0c=IN IP4 166.34.245.231m=audio 20224 RTP/AVP 0*Mar 6 14:19:16: Sent:ACK sip:3660210@166.34.245.231:5060;user=phone SIP/2.0Via: SIP/2.0/UDP 166.34.245.230:55820From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357Date: Sat, 06 Mar 1993 19:19:14 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Max-Forwards: 6Content-Type: application/sdpContent-Length: 138CSeq: 101 ACKv=0o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230s=SIP Callt=0 0c=IN IP4 166.34.245.230m=audio 20762 RTP/AVP 0*Mar 6 14:19:19: Received:BYE sip:3660110@166.34.245.230:5060;user=phone SIP/2.0Via: SIP/2.0/UDP 166.34.245.231:53600From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357To: "3660110" <sip:3660110@166.34.245.230>Date: Mon, 08 Mar 1993 22:45:14 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledMax-Forwards: 6Timestamp: 731612717CSeq: 101 BYEContent-Length: 0*Mar 6 14:19:19: Sent:SIP/2.0 200 OKVia: SIP/2.0/UDP 166.34.245.231:53600From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357To: "3660110" <sip:3660110@166.34.245.230>Date: Sat, 06 Mar 1993 19:19:19 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledTimestamp: 731612717Content-Length: 0CSeq: 101 BYEThe following example show debug output from the other side of the call:
Router2# debug ccsip messagesSIP Call messages tracing is enabledRouter2#*Mar 8 17:45:12: Received:INVITE sip:3660210@166.34.245.231;user=phone;phone-context=unknown SIP/2.0Via: SIP/2.0/UDP 166.34.245.230:55820From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Sat, 06 Mar 1993 19:19:14 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Cisco-Guid: 2881152943-2184249568-0-483551624User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEMax-Forwards: 6Timestamp: 731427554Contact: <sip:3660110@166.34.245.230:5060;user=phone>Expires: 180Content-Type: application/sdpContent-Length: 138v=0o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230s=SIP Callt=0 0c=IN IP4 166.34.245.230m=audio 20762 RTP/AVP 0*Mar 8 17:45:12: Sent:SIP/2.0 100 TryingVia: SIP/2.0/UDP 166.34.245.230:55820From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Mon, 08 Mar 1993 22:45:12 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Timestamp: 731427554Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEContent-Length: 0*Mar 8 17:45:12: Sent:SIP/2.0 180 RingingVia: SIP/2.0/UDP 166.34.245.230:55820From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>Date: Mon, 08 Mar 1993 22:45:12 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Timestamp: 731427554Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledCSeq: 101 INVITEContent-Type: application/sdpContent-Length: 138v=0o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231s=SIP Callt=0 0c=IN IP4 166.34.245.231m=audio 20224 RTP/AVP 0*Mar 8 17:45:14: Sent:SIP/2.0 200 OKVia: SIP/2.0/UDP 166.34.245.230:55820From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357Date: Mon, 08 Mar 1993 22:45:12 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Timestamp: 731427554Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledContact: <sip:3660210@166.34.245.231:5060;user=phone>CSeq: 101 INVITEContent-Type: application/sdpContent-Length: 138v=0o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231s=SIP Callt=0 0c=IN IP4 166.34.245.231m=audio 20224 RTP/AVP 0*Mar 8 17:45:14: Received:ACK sip:3660210@166.34.245.231:5060;user=phone SIP/2.0Via: SIP/2.0/UDP 166.34.245.230:55820From: "3660110" <sip:3660110@166.34.245.230>To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357Date: Sat, 06 Mar 1993 19:19:14 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Max-Forwards: 6Content-Type: application/sdpContent-Length: 138CSeq: 101 ACKv=0o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230s=SIP Callt=0 0c=IN IP4 166.34.245.230m=audio 20762 RTP/AVP 0*Mar 8 17:45:17: Sent:BYE sip:3660110@166.34.245.230:5060;user=phone SIP/2.0Via: SIP/2.0/UDP 166.34.245.231:53600From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357To: "3660110" <sip:3660110@166.34.245.230>Date: Mon, 08 Mar 1993 22:45:14 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledMax-Forwards: 6Timestamp: 731612717CSeq: 101 BYEContent-Length: 0*Mar 8 17:45:17: Received:SIP/2.0 200 OKVia: SIP/2.0/UDP 166.34.245.231:53600From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357To: "3660110" <sip:3660110@166.34.245.230>Date: Sat, 06 Mar 1993 19:19:19 GMTCall-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabledTimestamp: 731612717Content-Length: 0CSeq: 101 BYERelated Commands
debug ccsip preauth
To enable diagnostic reporting of authentication, authorization, and accounting (AAA) preauthentication for Session Initiation Protocol (SIP) calls, use the debug ccsip preauth command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccsip preauth
no debug ccsip preauth
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example shows debug output for a single SIP call:
Router# debug ccsip preauthSIP Call preauth tracing is enabledJan 23 18:43:17.898::Preauth RequiredJan 23 18:43:17.898: In sipSPISendPreauthReq for preauth_id = 86515, ccb = 67AF4E10Jan 23 18:43:17.898: Entering rpms_proc_print_preauth_reqJan 23 18:43:17.898: Request = 0Jan 23 18:43:17.898: Preauth id = 86515Jan 23 18:43:17.898: EndPt Type = 1Jan 23 18:43:17.898: EndPt = 192.168.80.70Jan 23 18:43:17.898: Resource Service = 1Jan 23 18:43:17.898: Call_origin = answerJan 23 18:43:17.898: Call_type = voipJan 23 18:43:17.898: Calling_num = 2270001Jan 23 18:43:17.898: Called_num = 1170001Jan 23 18:43:17.898: Protocol = 1Jan 23 18:43:17.898:sipSPISendPreauthReq:Created node with preauth_id = 86515, ccb 67AF4E10 , node 6709C280Jan 23 18:43:17.898:rpms_proc_create_node:Created node with preauth_id = 86515Jan 23 18:43:17.898:rpms_proc_send_aaa_req:uid got is 466728Jan 23 18:43:17.902:rpms_proc_preauth_response:Context is for preauth_id 86515, aaa_uid 466728Jan 23 18:43:17.902:rpms_proc_preauth_response:Deleting Tree node for preauth id 86515 uid 466728Jan 23 18:43:17.902:sipSPIGetNodeForPreauth:Preauth_id=86515Jan 23 18:43:17.902: ccsip_spi_process_preauth_event:67AF4E10 ccb & 6709C280 nodeJan 23 18:43:17.902: In act_preauth_response:67AF4E10 ccbJan 23 18:43:17.902: act_preauth_response:Deleting node 6709C280 from treeTable 52 describes the significant fields shown in the display.
debug ccsip states
To show all Session Initiation Protocol (SIP) Service Provider Interface (SPI) state tracing, use the debug ccsip states command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccsip states
no debug ccsip states
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command traces the state machine changes of SIP SPI and displays the state transitions.
Examples
The following example shows all SIP SPI state tracing:
Router1# debug ccsip statesSIP Call states tracing is enabledRouter1#*Jan 2 18:34:37.793:0x6220C634 :State change from (STATE_NONE, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_NONE)*Jan 2 18:34:37.797:0x6220C634 :State change from (STATE_IDLE, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_CONNECTING)*Jan 2 18:34:37.797:0x6220C634 :State change from (STATE_IDLE, SUBSTATE_CONNECTING) to (STATE_IDLE, SUBSTATE_CONNECTING)*Jan 2 18:34:37.801:0x6220C634 :State change from (STATE_IDLE, SUBSTATE_CONNECTING) to (STATE_SENT_INVITE, SUBSTATE_NONE)*Jan 2 18:34:37.809:0x6220C634 :State change from (STATE_SENT_INVITE, SUBSTATE_NONE) to (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING)*Jan 2 18:34:37.853:0x6220C634 :State change from (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING) to (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_ALERTING)*Jan 2 18:34:38.261:0x6220C634 :State change from (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_ALERTING) to (STATE_ACTIVE, SUBSTATE_NONE)*Jan 2 18:35:09.860:0x6220C634 :State change from (STATE_ACTIVE, SUBSTATE_NONE) to (STATE_DISCONNECTING, SUBSTATE_NONE)*Jan 2 18:35:09.868:0x6220C634 :State change from (STATE_DISCONNECTING, SUBSTATE_NONE) to (STATE_DEAD, SUBSTATE_NONE)*Jan 2 18:28:38.404: Queued event from SIP SPI :SIPSPI_EV_CLOSE_CONNECTIONRelated Commands
debug ccsip transport
To enable tracing of the Session Initiation Protocol (SIP) transport handler and the TCP or User Datagram Protocol (UDP) process, use the debug ccsip transport command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccsip transport
no debug ccsip transport
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the debug ccsip transport command to debug issues related to connection and transport usage and to see the flow of the messages being sent or received.
Examples
The following is sample output from the debug ccsip transport command for a Cisco 3660:
Router# debug ccsip transport...1w1d: //18/8E16980D800A/SIP/Transport/sipSPISendInvite: Sending Invite to the transport layer1w1d: //18/8E16980D800A/SIP/Transport/sipSPIGetSwitchTransportFlag: Return the Global configuration, Switch Transport is TRUE1w1d: //18/8E16980D800A/SIP/Transport/sipSPITransportSendMessage: msg=0x64082D50, addr=172.18.194.183, port=5060, sentBy_port=0, is_req=1, transport=1, switch=1, callBack=0x614FAB581w1d: //18/8E16980D800A/SIP/Transport/sipSPITransportSendMessage: Proceedable for sending msg immediately1w1d: //18/8E16980D800A/SIP/Transport/sipTransportLogicSendMsg: switch transport is 11w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportGetInterfaceMtuSize: MTU size for remote address 172.18.194.183 is 5001w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportVerifyMsgForMTUThreshold: Interface MTU Size 500, Msg Size 10961w1d: //18/8E16980D800A/SIP/Transport/sipTransportLogicSendMsg: Switching msg=0x64082D50 transport UDP->TCP1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportSetAgeingTimer: Aging timer initiated for holder=0x64084058,addr=172.18.194.1831w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipCreateConnHolder: Created new holder=0x64084058, addr=172.18.194.1831w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportPostRequestConnection: Posting TCP conn create request for addr=172.18.194.183, port=5060, context=0x64128D5C1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportSetConnWaitTimer: Wait timer set for connection=0x64129BF4,addr=172.18.194.183, port=50601w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipCreateConnInstance: Created new initiated conn=0x64129BF4, connid=-1, addr=172.18.194.183, port=5060, transport=tcp1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipConnectionManagerProcessConnCreated: gConnTab=0x64128D5C, addr=172.18.194.183, port=5060, connid=1, transport=tcp1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipInstanceHandleConnectionCreated: Moving connection=0x64129BF4, connid=1state to pending1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWConnectionCreated: context=0x64128D5C1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipConnectionManagerProcessConnCreated: gConnTab=0x64128D5C, addr=172.18.194.183, port=5060, connid=1, transport=tcp1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportPostSendMessage: Posting send for msg=0x64082D50, addr=172.18.194.183, port=5060, connId=1 for TCP...Table 53 describes the significant fields shown in the display.
Related Commands
debug ccswvoice vo-debug
To display detailed debugging information related to ccswvoice function calls during call setup and teardown, use the debug ccswvoice vo-debug command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccswvoice vo-debug
no debug ccswvoice vo-debug
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command when attempting to troubleshoot a Vo call that uses the "cisco-switched" session protocol. This command provides the same information as the debug ccswvoice vo-session command, but includes additional debugging information relating to the calls.
Examples
The following shows sample output from the debug ccswvoice vo-debug command:
Router# debug ccswvoice vo-debug2w2d: ccswvoice: callID 529927 pvcid -1 cid -1 state NULL event O/G SETUP2w2d: ccswvoice_out_callinit_setup: callID 529927 using pvcid 1 cid 152w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state O/G INIT event I/C PROC2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state O/G PROC event I/C ALERTccfrf11_caps_ind: codec(preferred) = 12w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state O/G ALERT event I/C CONN2w2d: ccswvoice_bridge_drop: dropping bridge calls src 529927 dst 529926 pvcid 1 cid 15 state ACTIVE2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state ACTIVE event O/G REL2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state RELEASE event I/C RELCOMP2w2d: ccswvo_store_call_history_entry: cause=10 tcause=10 cause_text=normal call clearing.Related Commands
debug ccswvoice vo-session
Displays the first 10 bytes (including header) of selected VoFR subframes for the interface.
debug ccswvoice vofr-debug
To display the ccswvoice function calls during call setup and teardown, use the debug ccswvoice vofr-debug command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccswvoice vofr-debug
no debug ccswvoice vofr-debug
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command when troubleshooting a VoFR call that uses the "cisco-switched" session protocol. This command provides the same information as the debug ccswvoice vofr-session command, but includes additional debugging information relating to the calls.
Examples
The following shows sample output from the debug ccswvoice vofr-debug command:
Router# debug ccswvoice vofr-debugCALL TEARDOWN:3640_vofr(config-voiceport)#*Mar 1 03:02:08.719:ccswvofr_bridge_drop:dropping bridge calls src 17 dst 16 dlci 100cid 9 state ACTIVE*Mar 1 03:02:08.727:ccswvofr:callID 17 dlci 100 cid 9 state ACTIVE event O/G REL*Mar 1 03:02:08.735:ccswvofr:callID 17 dlci 100 cid 9 state RELEASE event I/C RELCOMP*Mar 1 03:02:08.735:ccswvofr_store_call_history_entry:cause=22 tcause=22cause_text=no circuit.3640_vofr(config-voiceport)#CALL SETUP (outgoing):*Mar 1 03:03:22.651:ccswvofr:callID 23 dlci -1 cid -1 state NULL event O/G SETUP*Mar 1 03:03:22.651:ccswvofr_out_callinit_setup:callID 23 using dlci 100 cid 10*Mar 1 03:03:22.659:ccswvofr:callID 23 dlci 100 cid 10 state O/G INIT event I/C PROC*Mar 1 03:03:22.667:ccswvofr:callID 23 dlci 100 cid 10 state O/G PROC event I/C CONNccfrf11_caps_ind:codec(preferred) = 0Related Commands
debug ccswvoice vofr-session
To display the ccswvoice function calls during call setup and teardown, use the debug ccswvoice vofr-session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccswvoice vofr-session
no debug ccswvoice vofr-session
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to show the state transitions of the cisco-switched-vofr state machine as a call is processed, and when attempting to troubleshoot a VoFR call that uses the "cisco-switched" session protocol.
Examples
The following shows sample output from the debug ccswvoice vofr-session command:
Router# debug ccswvoice vofr-sessionCALL TEARDOWN:3640_vofr(config-voiceport)#*Mar 1 02:58:13.203:ccswvofr:callID 14 dlci 100 cid 8 state ACTIVE event O/G REL*Mar 1 02:58:13.215:ccswvofr:callID 14 dlci 100 cid 8 state RELEASE event I/C RELCOMP3640_vofr(config-voiceport)#CALL SETUP (outgoing):*Mar 1 02:59:46.551:ccswvofr:callID 17 dlci -1 cid -1 state NULL event O/G SETUP*Mar 1 02:59:46.559:ccswvofr:callID 17 dlci 100 cid 9 state O/G INIT event I/C PROC*Mar 1 02:59:46.567:ccswvofr:callID 17 dlci 100 cid 9 state O/G PROC event I/C CONN3640_vofr(config-voiceport)#Related Commands
debug ccswvoice vo-session
To display the first 10 bytes (including header) of selected VoFR subframes for the interface, use the debug ccswvoice vo-session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccswvoice vo-session
no debug ccswvoice vo-session
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to show the state transitions of the cisco-switched-vo state machine as a call is processed. This command should be used when attempting to troubleshoot a Vo call that uses the "cisco-switched" session protocol.
Examples
The following shows sample output from the debug ccswvoice vo-session command:
Router# debug ccswvoice vo-session2w2d: ccswvoice: callID 529919 pvcid -1 cid -1 state NULL event O/G SETUP2w2d: ccswvoice: callID 529919 pvcid 1 cid 11 state O/G INIT event I/C PROC2w2d: ccswvoice: callID 529919 pvcid 1 cid 11 state O/G PROC event I/C ALERT2w2d: ccswvoice: callID 529919 pvcid 1 cid 11 state O/G ALERT event I/C CONN2w2d: ccswvoice: callID 529919 pvcid 1 cid 11 state ACTIVE event O/G REL2w2d: ccswvoice: callID 529919 pvcid 1 cid 11 state RELEASE event I/C RELCOMPRelated Commands
debug ccswvoice vo-debug
Displays detailed debugging information related to ccswvoice function calls during call setup and teardown.
debug cdapi
To display information about the Call Distributor Application Programming Interface (CDAPI), use the debug cdapi command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdapi {detail | events}
no debug cdapi {detail | events}
Syntax Description
Defaults
Debugging output is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The detail keyword is useful for determining if messages are being lost (or not freed). It is also useful for determining the size of the raw messages passed between CDAPI and other applications to ensure that the correct number of bytes is being passed.
The events keyword is useful for determining if certain ISDN messages are not being received by an application and if calls are not being directed to an application.
The following bandwidths are supported:
•
•
Examples
The following Media Gateway Control Protocol (MGCP) packet received example shows V.110 call debugging output for the debug cdapi detail command. In this example, the modem is not yet in STEADY_STATE.
Router# debug cdapi detailSep 26 19:12:25.327:MGCP Packet received from 10.0.44.109:2427-CRCX 6318 s7/ds1-0/24 MGCP 1.0C:111M:nas/dataL:b:64, nas/bt:v.110, nas/cdn:234567R:nas/au, nas/ax,nas/of, nas/crqX:101Sep 26 19:12:25.327:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0Sep 26 19:12:25.327:CDAPI Se7/1:23:cdapi_add_entry_callRoutingTbl() -Sep 26 19:12:25.327: Added entry for call 0x7017 for application CSMSep 26 19:12:25.331:CDAPI:cdapi_create_msg():CDAPI Pool Count:958,router# Raw Length = 0Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:959Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:960Sep 26 19:12:25.331:send_mgcp_msg, MGCP Packet sent to 10.0.44.109:2427 --->Sep 26 19:12:25.331:200 6318 AlertI:64524608Sep 26 19:12:25.339:CDAPI:cdapi_crearouter#te_msg():CDAPI Pool Count:959, Raw Length = 0Sep 26 19:12:25.339:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0Sep 26 19:12:25.339:CDAPI:cdapi_free_msg():CDAPI Pool Count:960router#Sep 26 19:12:33.223:MGCP Packet received from 10.0.44.109:2427-DLCX 6319 s7/ds1-0/24 MGCP 1.0Sep 26 19:12:33.223:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0Sep 26 19:12:33.223:CDAPI:cdapi_create_msg():CDAPI Pool Count:958, Raw Length = 0Sep 26 19:12:33.223:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0Sep 26 19:12:33.223:CDAPI:cdapi_free_msg():CDAPI Pool Count:959Sep 26 19:12:33.227:CDAPI:cdapi_create_msg():CDAPI Pool Count:958, Rawrouter# Length = 0Sep 26 19:12:33.227:CDAPI Se7/1:23:cdapi_del_entry_callRoutingTbl() -Sep 26 19:12:33.227: Deleted entry for call 0x7017Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():CDAPI Pool Count:959Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():CDAPI Pool Count:960Sep 26 19:12:33.227:send_mgcp_msg, MGCP Packet sentrouter#to 10.0.44.109:2427 --->Sep 26 19:12:33.227:200 6319 OKThe following partial example shows V.120 call debugging output for the debug cdapi detail command:
Router# debug cdapi detailMay 14 19:12:25.327:MGCP Packet received from 10.0.44.109:2427-CRCX 6318 s7/ds1-0/24 MGCP 1.0C:111M:nas/dataL:b:64, nas/bt:v.120, nas/cdn:234567R:nas/au, nas/ax,nas/of, nas/crqX:101May 14 19:12:25.327:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0May 14 19:12:25.327:CDAPI Se7/1:23:cdapi_add_entry_callRoutingTbl() -May 14 19:12:25.327: Added entry for call 0x7017 for application CSMMay 14 19:12:25.331:CDAPI:cdapi_create_msg():CDAPI Pool Count:958,router# Raw Length = 0May 14 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0May 14 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:959May 14 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0May 14 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:960May 14 19:12:25.331:send_mgcp_msg, MGCP Packet sent to 10.0.44.109:2427 --->...The following MGCP packet received example shows V.120 call debugging output for the debug cdapi events command:
Router# debug cdapi eventsSep 26 19:14:39.027:MGCP Packet received from 10.0.44.109:2427-CRCX 6322 s7/ds1-0/24 MGCP 1.0C:111M:nas/dataL:b:64, nas/bt:v.120, nas/cdn:234567R:nas/au, nas/ax,nas/of, nas/crqX:101Sep 26 19:14:39.027:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONNECT_IND to CSM call = 0x7017Sep 26 19:14:39.027: From Appl/Stack = XCSPSep 26 19:14:39.027: Call Type = V.120Sep 26 19:14:39.027: B Channel = 23Sep 26 19:14:39.027: dslId = 0Sep 26 19:14:39.027: Idb = 0Seprouter#26 19:14:39.027: BChanIdb = 64519A14Sep 26 19:14:39.027: Handle = 63CB8DF4Sep 26 19:14:39.027: RPA = 6388506CSep 26 19:14:39.027: Cause = 0Sep 26 19:14:39.027: ApplCause = 0Sep 26 19:14:39.027: ApplSpecData = 0Sep 26 19:14:39.027: Calling Party Number =Sep 26 19:14:39.027: Called Party Number = 234567Sep 26 19:14:39.027: Overlap = 0Sep 26 19:14:39.027:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONNECT_RESP to XCSP call = 0x7017Sep 26 19:14:39.027: From Applrouter#/Stack = CSMSep 26 19:14:39.027: Call Type = MODEMSep 26 19:14:39.027: B Channel = 23Sep 26 19:14:39.027: dslId = 0Sep 26 19:14:39.027: Idb = 0Sep 26 19:14:39.027: BChanIdb = 64519A14Sep 26 19:14:39.027: Handle = 63CB8DF4Sep 26 19:14:39.027: RPA = 0Sep 26 19:14:39.027: Cause = 0Sep 26 19:14:39.027: ApplCause = 0Sep 26 19:14:39.027: ApplSpecData = 0Sep 26 19:14:39.027: Overlap = 0Sep 26 19:14:39.031:send_mgcp_msg, MGCP Parouter#cket sent to 10.0.44.109:2427 --->Sep 26 19:14:39.031:200 6322 AlertI:64524608Sep 26 19:14:39.039:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONN_ACT_REQ to XCSP call = 0x7017Sep 26 19:14:39.039: From Appl/Stack = CSMSep 26 19:14:39.039: Call Type = MODEMSep 26 19:14:39.039: B Channel = 23Sep 26 19:14:39.039: dslId = 0Sep 26 19:14:39.039: Idb = 0Sep 26 19:14:39.039: BChanIdb = 64519A14Sep 26 19:14:39.039: Handle = 63CB8DF4Sep 26 19:14:39.039: Rrouter#PA = 0Sep 26 19:14:39.039: Cause = 0Sep 26 19:14:39.039: ApplCause = 0Sep 26 19:14:39.039: ApplSpecData = 0Sep 26 19:14:39.039: Overlap = 0router#Sep 26 19:14:48.959:MGCP Packet received from 10.0.44.109:2427-DLCX 6323 s7/ds1-0/24 MGCP 1.0Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_DISCONNECT_IND to CSM call = 0x7017Sep 26 19:14:48.963: From Appl/Stack = XCSPSep 26 19:14:48.963: Call Type = V.120Sep 26 19:14:48.963: B Channel = 23Sep 26 19:14:48.963: dslId = 0Sep 26 19:14:48.963: Idb = 0Sep 26 19:14:48.963: BChanIdb = 64519A14Sep 26 19:14:48.963: Handle = 63CB8DF4Sep 26 19:14router#:48.963: RPA = 6388506CSep 26 19:14:48.963: Cause = 0Sep 26 19:14:48.963: ApplCause = 0Sep 26 19:14:48.963: ApplSpecData = 0Sep 26 19:14:48.963: Overlap = 0Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_SUBTYPE_RELEASE_REQ to XCSP call = 0x7017Sep 26 19:14:48.963: From Appl/Stack = CSMSep 26 19:14:48.963: Call Type = MODEMSep 26 19:14:48.963: B Channel = 23Sep 26 19:14:48.963: dslId = 0Sep 26 19:14:48.963: Idb = 0Sep 26 19:14:48router#.963: BChanIdb = 64519A14Sep 26 19:14:48.963: Handle = 63CB8DF4Sep 26 19:14:48.963: RPA = 0Sep 26 19:14:48.963: Cause = 0Sep 26 19:14:48.963: ApplCause = 1Sep 26 19:14:48.963: ApplSpecData = 0Sep 26 19:14:48.963: Overlap = 0Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_SUBTYPE_REL_COMP_IND to CSM call = 0x7017Sep 26 19:14:48.963: From Appl/Stack = XCSPSep 26 19:14:48.963: Call Type = V.120Sep 26 19:14:48.963: B Channel = 23Sep 26 19:router#14:48.963: dslId = 0Sep 26 19:14:48.963: Idb = 0Sep 26 19:14:48.963: BChanIdb = 64519A14Sep 26 19:14:48.963: Handle = 63CB8DF4Sep 26 19:14:48.963: RPA = 6388506CSep 26 19:14:48.963: Cause = 0Sep 26 19:14:48.963: ApplCause = 0Sep 26 19:14:48.963: ApplSpecData = 0Sep 26 19:14:48.963: Overlap = 0Sep 26 19:14:48.963:send_mgcp_msg, MGCP Packet sent to 10.0.44.109:2427 --->Sep 26 19:14:48.963:200 6323 OKTable 54 describes the significant fields shown in the displays.
Related Commands
debug mgcp packet
Displays the MGCP signaling message received and sent to the called agent.
debug voip rawmsg
Displays the raw message owner, length, and pointer.
debug cdma pdsn a10 ahdlc
To display debug messages for Asynchronous High-Level Data Link Control (AHDLC), use the debug cdma pdsn a10 ahdlc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn a10 ahdlc [errors | events ]
no debug cdma pdsn a10 ahdlc [errors | events ]
Syntax Description
errors
(Optional) Displays details of AHDLC packets in error.
events
(Optional) Displays AHDLC events.
Defaults
If the command is entered without any optional keywords, all of the types of debug information are enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cdma pdsn a10 ahdlc command:
Router# debug cdma pdsn a10 ahdlc errorsahdlc error packet display debugging is onRouter# debug cdma pdsn a10 ahdlc eventsahdlc events display debugging is onRouter#*Jan 1 00:18:30:%LINK-3-UPDOWN:Interface Virtual-Access1, changed state to up*Jan 1 00:18:30:*****OPEN AHDLC******Jan 1 00:18:30: ahdlc_mgr_channel_create*Jan 1 00:18:30: ahdlc_mgr_allocate_available_channel:*Jan 1 00:18:30:ahdlc:tell h/w open channel 9 from engine 0debug cdma pdsn a10 gre
To display debug messages for A10 Generic Routing Encapsulation (GRE) interface errors, events, and packets, use the debug cdma pdsn a10 gre command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn a10 gre [errors | events | packets] [tunnel-key key]
no debug cdma pdsn a10 gre [errors | events | packets]
Syntax Description
Defaults
If the command is entered without any optional keywords, all of the types of debug information are enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cdma pdsn a10 gre events tunnel-key command:
Router# debug cdma pdsn a10 gre events tunnel-key 1Router# show debugCDMA:CDMA PDSN A10 GRE events debugging is on for tunnel key 1PDSN#*Mar 1 04:00:57.847:CDMA-GRE:CDMA-Ix1 (GRE/CDMA) created with src 5.0.0.2 dst 0.0.0.0*Mar 1 04:00:57.847:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1*Mar 1 04:00:59.863:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1*Mar 1 04:00:59.863:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1*Mar 1 04:01:01.879:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1*Mar 1 04:01:01.879:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1*Mar 1 04:01:03.899:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1*Mar 1 04:01:03.899:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1debug cdma pdsn a10 ppp
To display debug messages for A10 Point-to-Point protocol (PPP) interface errors, events, and packets, use the debug cdma pdsn a10 ppp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn a10 ppp [errors | events | packets]
no debug cdma pdsn a10 ppp [errors | events | packets]
Syntax Description
errors
(Optional) Displays A10 PPP errors.
events
(Optional) Displays A10 PPP events.
packets
(Optional) Displays transmitted or received A10 PPP packets.
Defaults
If the command is entered without any optional keywords, all of the types of debug information are enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cdma pdsn a10 ppp command:
Router# debug cdma pdsn a10 ppp errorsCDMA PDSN A10 errors debugging is onRouter# debug cdma pdsn a10 ppp eventsCDMA PDSN A10 events debugging is onRouter# debug cdma pdsn a10 ppp packetsCDMA PDSN A10 packet debugging is onRouter# show debug*Jan 1 00:13:09:CDMA-PPP:create_va tunnel=CDMA-Ix1 virtual-template template=Virtual-Template2 ip_enabled=1*Jan 1 00:13:09:CDMA-PPP:create_va va=Virtual-Access1*Jan 1 00:13:09:CDMA-PPP:clone va=Virtual-Access1 subif_state=1 hwidb->state=0*Jan 1 00:13:09: linestate=1 ppp_lineup=0*Jan 1 00:13:09:%LINK-3-UPDOWN:Interface Virtual-Access1, changed state to up*Jan 1 00:13:09:CDMA-PPP:clone va=Virtual-Access1 subif_state=1 hwidb->state=4*Jan 1 00:13:09: linestate=0 ppp_lineup=0*Jan 1 00:13:09:*****OPEN AHDLC*****debug cdma pdsn a11
To display debug messages for A11 interface errors, events, and packets, use the debug cdma pdsn a11 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn a11 [errors | events | packets ] [mnid]
no debug cdma pdsn a11 [errors | events | packets ]
Syntax Description
Defaults
If the command is entered without any optional keywords, all of the types of debug information are enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cdma pdsn a11 commands:
Router# debug cdma pdsn a11 errorsCDMA PDSN A11 errors debugging is onRouter# show debug1d21h:CDMA-RP:(in) rp_msgs, code=1, status=01d21h:CDMA-RP:(enqueue req) type=1 homeagent=5.0.0.2 coaddr=4.0.0.11d21h: id=0xBEF750F0-0xBA53E0F lifetime=655351d21h:CDMA-RP:len=8, 00-00-00-00-00-00-00-F1 convert to 00000000000001(14 digits), type=IMSI1d21h:CDMA-RP:(req) process_rp_req, homeagent=5.0.0.2 coaddr=4.0.0.11d21h: lifetime=65535 id=BEF750F0-BA53E0Fimsi=000000000000011d21h:CDMA-RP:(req) rp_req_create, 5.0.0.2-4.0.0.1-1 imsi=000000000000011d21h:CDMA-RP:(out) rp_reply session=5.0.0.2-4.0.0.1-1, lifetime=655351d21h:CDMA-RP:(out) setup_rp_out_msg, ha=5.0.0.2 coa=4.0.0.1 key=11d21h:%LINK-3-UPDOWN:Interface Virtual-Access2000, changed state to up1d21h:CDMA-RP:ipmobile_visitor add/delete=1, mn=8.0.2.132, ha=7.0.0.21d21h:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access2000,changed state to upRouter# debug cdma pdsn a11 packets eventsRouter# show debugCDMA:CDMA PDSN A11 packet debugging is on for mnid 000000000000001CDMA PDSN A11 events debugging is on for mnid 000000000000001Router#*Mar 1 03:15:32.507:CDMA-RP:len=8, 01-00-00-00-00-00-00-10 convert to 000000000000001 (15 digits), type=IMSI*Mar 1 03:15:32.511:CDMA-RP:extension type=38, len=0*Mar 1 03:15:32.511:CDMA-RP:extension type=38, len=0*Mar 1 03:15:32.511:CDMA-RP:extension type=38, len=0*Mar 1 03:15:32.511:CDMA-RP:extension type=32, len=20*Mar 1 03:15:32.511: 00 00 01 00 EE 1F FC 43 0A 7D F9 36 29 C2 BA 28*Mar 1 03:15:32.511: 5A 64 D5 9C*Mar 1 03:15:32.511:CDMA-RP:(req) process_rp_req, homeagent=5.0.0.2 coaddr=4.0.0.1*Mar 1 03:15:32.511: lifetime=1800 id=AF3BFE55-69A109D IMSI=000000000000001*Mar 1 03:15:32.511:CDMA-RP:(req) rp_req_create, ha=5.0.0.2, coa=4.0.0.1, key=1 IMSI=000000000000001*Mar 1 03:15:32.511:CDMA-RP:(out) rp_reply session=5.0.0.2-4.0.0.1-1, lifetime=1800*Mar 1 03:15:32.511:CDMA-RP:(out) Setup RP out message, ha=5.0.0.2 coa=4.0.0.1 key=1*Mar 1 03:15:38.555:CDMA-RP:simple ip visitor added, mn=9.2.0.1, ha=0.0.0.0Router#*Mar 1 03:15:54.755:CDMA-RP:len=8, 01-00-00-00-00-00-00-10 convert to 000000000000001 (15 digits), type=IMSI*Mar 1 03:15:54.755:CDMA-RP:extension type=38, len=0*Mar 1 03:15:54.755:CDMA-RP:extension type=32, len=20*Mar 1 03:15:54.755: 00 00 01 00 EA 9C C6 4C BA B9 F9 B6 DD C4 19 76*Mar 1 03:15:54.755: 51 5A 56 45*Mar 1 03:15:54.755:CDMA-RP:(req) process_rp_req, homeagent=5.0.0.2 coaddr=4.0.0.1*Mar 1 03:15:54.755: lifetime=0 id=AF3BFE6B-4616E475 IMSI=000000000000001*Mar 1 03:15:54.755:CDMA-RP:(req) rp_req_lifetime_zero 5.0.0.2-4.0.0.1-1*Mar 1 03:15:54.755: IMSI=000000000000001*Mar 1 03:15:54.755:CDMA-RP:(out) rp_reply session=5.0.0.2-4.0.0.1-1, lifetime=0*Mar 1 03:15:54.755:CDMA-RP:(out) Setup RP out message, ha=5.0.0.2 coa=4.0.0.1 key=1Router# debug cdma pdsn a11 event mnid 000000000000001Router# show debugCDMA:CDMA PDSN A11 events debugging is on for mnid 000000000000001Router#*Mar 1 03:09:34.339:CDMA-RP:len=8, 01-00-00-00-00-00-00-10 convert to 000000000000001 (15 digits), type=IMSI*Mar 1 03:09:34.339:CDMA-RP:(req) process_rp_req, homeagent=5.0.0.2 coaddr=4.0.0.1*Mar 1 03:09:34.339: lifetime=1800 id=AF3BFCEE-DC9FC751 IMSI=000000000000001*Mar 1 03:09:34.339:CDMA-RP:(req) rp_req_create, ha=5.0.0.2, coa=4.0.0.1, key=1 IMSI=000000000000001*Mar 1 03:09:34.339:CDMA-RP:(out) rp_reply session=5.0.0.2-4.0.0.1-1, lifetime=1800*Mar 1 03:09:34.339:CDMA-RP:(out) Setup RP out message, ha=5.0.0.2 coa=4.0.0.1 key=1*Mar 1 03:09:40.379:CDMA-RP:simple ip visitor added, mn=9.2.0.1, ha=0.0.0.0Router#close the sessionRouter#*Mar 1 03:10:00.575:CDMA-RP:len=8, 01-00-00-00-00-00-00-10 convert to 000000000000001 (15 digits), type=IMSI*Mar 1 03:10:00.575:CDMA-RP:(req) process_rp_req, homeagent=5.0.0.2 coaddr=4.0.0.1*Mar 1 03:10:00.575: lifetime=0 id=AF3BFD09-18040319 IMSI=000000000000001*Mar 1 03:10:00.575:CDMA-RP:(req) rp_req_lifetime_zero 5.0.0.2-4.0.0.1-1*Mar 1 03:10:00.575: IMSI=000000000000001*Mar 1 03:10:00.575:CDMA-RP:(out) rp_reply session=5.0.0.2-4.0.0.1-1, lifetime=0*Mar 1 03:10:00.575:CDMA-RP:(out) Setup RP out message, ha=5.0.0.2 coa=4.0.0.1 key=1Router# debug cdma pdsn a11 packet mnid 000000000000001Router# show debugCDMA:CDMA PDSN A11 packet debugging is on for mnid 000000000000001Router#*Mar 1 03:13:37.803:CDMA-RP:extension type=38, len=0*Mar 1 03:13:37.803:CDMA-RP:extension type=38, len=0*Mar 1 03:13:37.803:CDMA-RP:extension type=38, len=0*Mar 1 03:13:37.803:CDMA-RP:extension type=32, len=20*Mar 1 03:13:37.803: 00 00 01 00 A8 5B 30 0D 4E 2B 83 FE 18 C6 9D C2*Mar 1 03:13:37.803: 15 BF 5B 57*Mar 1 03:13:51.575:CDMA-RP:extension type=38, len=0*Mar 1 03:13:51.575:CDMA-RP:extension type=32, len=20*Mar 1 03:13:51.575: 00 00 01 00 58 77 E5 59 67 B5 62 15 17 52 83 6D*Mar 1 03:13:51.579: DC 0A B0 5Bdebug cdma pdsn accounting
To display debug messages for accounting events, use the debug cdma pdsn accounting command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn accounting
no cdma pdsn accounting
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cdma pdsn accounting command:
Router# debug cdma pdsn accountingCDMA PDSN accounting debugging is onRouter#*Jan 1 00:15:32:CDMA/ACCT:null vaccess in session_start*Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[9]*Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[44] len:[3] 01 Processing Y1*Jan 1 00:15:32:CDMA/ACCT: Setup airlink record received*Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[12]*Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[41] len:[6] 00 00 00 02 CDMA/ACCT: Processing Y2*Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[9]*Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[42] len:[3] 12 CDMA/ACCT: Processing Y3*Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1F] len:[17] 30 30 30 30 30 30 30 30 30 30 30 30 30 30 32 Processing A1*Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[12]*Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[9] len:[6] 04 04 04 05 Processing D3*Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[14]*Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[10] len:[8] 00 00 04 04 04 05 Processing D4*Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[9]*Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[44] len:[3] 02 Processing Y1*Jan 1 00:15:32:CDMA/ACCT: Start airlink record received*Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[12]*Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[41] len:[6] 00 00 00 02 CDMA/ACCT: Processing Y2*Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[9]*Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[42] len:[3] 13 CDMA/ACCT: Processing Y3*Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[10]*Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[11] len:[4] 00 02 Processing E1*Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[10]*Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[12] len:[4] 00 F1 Processing F1debug cdma pdsn accounting flow
To display debug messages for accounting flow, use the debug cdma pdsn accounting flow command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn accounting flow
no debug cdma pdsn accounting flow
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cdma pdsn accounting flow command:
Router# debug cdma pdsn accounting flowCDMA PDSN flow based accounting debugging is onpdsn-6500#01:59:40:CDMA-SM:cdma_pdsn_flow_acct_upstream sess id 1 flow type 0 bytes 100 addr 20.20.20.101:59:40:CDMA-SM:cdma_pdsn_flow_acct_downstream sess id 1 flow type 0 bytes 100 addr 20.20.20.1debug cdma pdsn accounting time-of-day
To display the timer value, use the debug cdma pdsn accounting time-of-day command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn accounting time-of-day
no debug cdma pdsn accounting time-of-day
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cdma pdsn accounting time-of-day command:
Router# debug cdma pdsn accounting time-of-dayCDMA PDSN accounting time-of-day debugging is onFeb 15 19:13:23.634:CDMA-TOD:Current timer expiring in 22 secondsFeb 15 19:13:24.194:%SYS-5-CONFIG_I:Configured from console by consoleRouter#Feb 15 19:13:45.635:CDMA-TOD:Timer expired...Rearming timerFeb 15 19:13:45.635:CDMA-TOD:Gathering session infoFeb 15 19:13:45.635:CDMA-TOD:Found 0 sessionsdebug cdma pdsn cluster
To display the error messages, event messages, and packets received, use the debug cdma pdsn cluster command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn cluster {message [error | events | packets] redundancy [error | events | packets ]}
no debug cdma pdsn cluster {message [error | events | packets] redundancy [error | events | packets ]}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This debug is only allowed on PDSN c6-mz images, and helps to monitor prepaid information.
Examples
The following is sample output from the debug cdma pdsn cluster command:
Router# debug cdma pdsn cluster ?message Debug PDSN cluster controller messagesredundancy Debug PDSN cluster controller redundancydebug cdma pdsn ipv6
To display IPV6 error or event messages, use the debug cdma pdsn IPV6 command in privileged EXEC mode. To disable debug messages, use the no form of this command.
debug cdma pdsn ipv6
no debug cdma pdsn ipv6
Syntax Description
There are no arguments or keywords for this command.
Defaults
No default behavior or values.
Command History
Usage Guidelines
The following example illustrates the debug cdma pdsn ipv6 command:
Router# debug cdma pdsn ipv6debug cdma pdsn prepaid
To display debug messages about prepaid flow, use the debug cdma pdsn prepaid command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn prepaid
no debug cdma pdsn prepaid
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This debug is only allowed on PDSN c6-mz images, and helps to monitor prepaid information.
Examples
The following is sample output from the debug cdma pdsn prepaid command:
Router# debug cdma pdsn prepaid*Mar 1 00:09:38.391: CDMA-PREPAID: Initialized the authorization request*Mar 1 00:09:38.391: CDMA-PREPAID: Added username into A-V list*Mar 1 00:09:38.391: CDMA-PREPAID: Added CLID into A-V list*Mar 1 00:09:38.391: CDMA-PREPAID: Added session id for prepaid*Mar 1 00:09:38.391: CDMA-PREPAID: Added correlation id into A-V list*Mar 1 00:09:38.391: CDMA-PREPAID: Added auth reason for prepaid into A-V list*Mar 1 00:09:38.391: CDMA-PREPAID: Added USER_ID for prepaid*Mar 1 00:09:38.391: CDMA-PREPAID: Added service id for prepaid*Mar 1 00:09:38.391: CDMA-PREPAID: Built prepaid VSAs*Mar 1 00:09:38.391: CDMA-PREPAID: Sent the request to AAA*Mar 1 00:09:38.391: CDMA-PREPAID: Auth_reason: CRB_RSP_PEND_INITIAL_QUOTA*Mar 1 00:09:38.395: CDMA-PREPAID: Received prepaid response: status 2*Mar 1 00:09:38.395: CDMA-PREPAID: AAA authorised parms being processed*Mar 1 00:09:38.395: CDMA-PREPAID: Attr in Grp Prof: crb-entity-type*Mar 1 00:09:38.395: (0x4B000000) CDMA/PREPAID: AAA_AT_CRB_ENTITY_TYPE*Mar 1 00:09:38.395: (0x4B000000) CDMA/PREPAID: entity type returns 1*Mar 1 00:09:38.395: CDMA-PREPAID: Attr in Grp Prof: crb-duration*Mar 1 00:09:38.395: (0x4B000000) CDMA/PREPAID: AAA_AT_CRB_DURATION*Mar 1 00:09:38.395: (0x4B000000) CDMA/PREPAID: duration returns 120*Mar 1 00:09:38.395: CDMA-PREPAID: Retrieved attributes successfully*Mar 1 00:09:38.395: CDMA-PREPAID: Reset duration to 120, mn 9.3.0.1*Mar 1 00:09:38.395: CDMA-PREPAID: : Started duration timer for 120 secdebug cdma pdsn qos
To display debug messages about quality of service features, use the debug cdma pdsn qos command in privileged EXEC mode. To disable debug messages, use the no form of this command.
debug cdma pdsn qos
no debug cdma pdsn qos
Syntax Description
There are no arguments or keywords for this command.
Defaults
There are no default values for this command.
Command History
Examples
There are currently no sample outputs for this command.
debug cdma pdsn resource-manager
To display debug messages that help you monitor the resource-manager information, use the debug cdma pdsn resource-manager command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn resource-manager [error | events]
no debug cdma pdsn resource-manager [error | events]
Syntax Description
errors
Displays Packet Data Service node (PDSN) resource manager errors.
events
Displays PDSN resource manager events.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cdma pds resource-manager command:
Router# debug cdma pdsn resource-managererrors CDMA PDSN resource manager errorsevents CDMA PDSN resource manager eventsdebug cdma pdsn selection
To display debug messages for the intelligent Packet Data Serving Node (PDSN) selection feature, use the debug cdma pdsn selection command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn selection {errors | events | packets}
no debug cdma pdsn selection {errors | events | packets}
Syntax Description
errors
Displays PDSN selection errors.
events
Displays PDSN selection events.
packets
Displays transmitted or received packets.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cdma pdsn selection command with the keyword events specified:
Router# debug cdma pdsn selection eventsCDMA PDSN selection events debugging is onRouter#00:27:46: CDMA-PSL: Message(IN) pdsn 51.4.2.40 interface 70.4.2.4000:27:46: Keepalive 1000:27:46: Count 000:27:46: Capacity 1600000:27:46: Weight 000:27:46: Hostname 11 7206-PDSN-200:27:46: CDMA-PSL: Reset keepalive, pdsn 51.4.2.40 current 10 new 1000:27:46: CDMA-PSL: Message processed, pdsn 51.4.2.40 tsize 0 pendings 000:27:47: CDMA-PSL: Send KEEPALIVE, len 3200:27:47: CDMA-PSL: Message(OUT) dest 224.0.0.1100:27:47: Keepalive 1000:27:47: Count 100:27:47: Capacity 1600000:27:47: Weight 000:27:47: Hostname 11 7206-PDSN-100:27:47: CDMA-PSL: RRQ sent, s=70.4.1.40 (FastEthernet0/1), d=224.0.0.11debug cdma pdsn service-selection
To display debug messages for service selection, use the debug cdma pdsn service-selection command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn service-selection
no debug cdma pdsn service-selection
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cdma pdsn service-selection command:
Router# debug cdma pdsn service-selectionCDMA PDSN service provisioning debugging is onRouter#1d02h:%LINK-3-UPDOWN:Interface Virtual-Access3, changed state to up1d02h:Vi3 CDMA-SP:user_class=1, ms_ipaddr_req=1, apply_acl=01d02h:Vi3 CDMA-SP:Adding simple ip flow, user=bsip, mn=6.0.0.2,1d02h:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access3,changed state to updebug cdma pdsn session
To display debug messages for Session Manager errors, events, and packets, use the debug cdma pdsn session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdma pdsn session [errors | events ]
no debug cdma pdsn session [errors | events ]
Syntax Description
Defaults
If the command is entered without any optional keywords, all of the types of debug information are enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cdma pdsn session command:
Router# debug cdma pdsn session eventsCDMA PDSN session events debugging is onRouter# debug cdma pdsn session errorsCDMA PDSN session errors debugging is onRouter# show debugCDMA:CDMA PDSN session events debugging is onCDMA PDSN session errors debugging is onRouter#*Jan 1 00:22:27:CDMA-SM:create_session 5.5.5.5-4.4.4.5-2*Jan 1 00:22:27:CDMA-SM:create_tunnel 5.5.5.5-4.4.4.5*Jan 1 00:22:27:%LINK-3-UPDOWN:Interface Virtual-Access1, changed state to up*Jan 1 00:22:29:CDMA-SM:create_flow mn=0.0.0.0, ha=8.8.8.8 nai=l2tp2@cisco.com*Jan 1 00:22:30:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access1, changed state to updebug cdp
To enable debugging of the Cisco Discovery Protocol (CDP), use the debug cdp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdp {packets | adjacency | events}
no debug cdp {packets | adjacency | events}
Syntax Description
packets
Enables packet-related debugging output.
adjacency
Enables adjacency-related debugging output.
events
Enables output related to error messages, such as detecting a bad checksum.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use debug cdp commands to display information about CDP packet activity, activity between CDP neighbors, and various CDP events.
Examples
The following is sample output from the debug cdp packets, debug cdp adjacency, and debug cdp events commands:
Router# debug cdp packetsCDP packet info debugging is onRouter# debug cdp adjacencyCDP neighbor info debugging is onRouter# debug cdp eventsCDP events debugging is onCDP-PA: Packet sent out on Ethernet0CDP-PA: Packet received from gray.cisco.com on interface Ethernet0CDP-AD: Deleted table entry for violet.cisco.com, interface Ethernet0CDP-AD: Interface Ethernet2 coming upCDP-EV: Encapsulation on interface Serial2 failedRelated Commands
cdp tlv
Configures location support in CDP.
show cdp tlv
Displays information about CDP TLVs.
debug cdp ip
To enable debug output for the IP routing information that is carried and processed by the Cisco Discovery Protocol (CDP), use the debug cdp ip command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cdp ip
no debug cdp ip
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
CDP is a media- and protocol-independent device-discovery protocol that runs on all Cisco routers.
You can use the debug cdp ip command to determine the IP network prefixes CDP is advertising and whether CDP is correctly receiving this information from neighboring routers.
Use the debug cdp ip command with the debug ip routing command to debug problems that occur when on-demand routing (ODR) routes are not installed in the routing table at a hub router. You can also use the debug cdp ip command with the debug cdp packet and debug cdp adjacency commands along with encapsulation-specific debug commands to debug problems that occur in the receipt of CDP IP information.
Examples
The following is sample output from the debug cdp ip command. This example shows the transmission of IP-specific information in a CDP update. In this case, three network prefixes are being sent, each with a different network mask.
Router# debug cdp ipCDP-IP: Writing prefix 172.1.69.232.112/28CDP-IP: Writing prefix 172.19.89.0/24CDP-IP: Writing prefix 11.0.0.0/8In addition to these messages, you might see the following messages:
•
CDP-IP: Updating prefix 172.16.1.0/24 in routing table•
CDP-IP: IP TLV length (3) invalid•
CDP-IP: Reading prefix 172.16.1.0/24 source 10.0.0.1 via Ethernet0/0Related Commands
debug ip routing
Displays information on RIP routing table updates and route cache updates.
debug cef
To enable the display of information about Cisco Express Forwarding events, use the debug cef command in privileged EXEC mode. To disable the display of Cisco Express Forwarding events, use the no form of this command.
debug cef {all | assert | background | broker | consistency-check | elog | epoch | fib [attached export | subblock] | hardware {notification | queries} | hash | high-availability | interest | interface | iprm | issu | loadinfo | memory | non-ip | path [extension | list | scope ]] | subtree context | switching background | table | xdr}
no debug cef {all | assert | background | broker | consistency-check | elog | epoch | fib [attached export | subblock] | hardware {notification | queries} | hash | high-availability | interest | interface | iprm | issu | loadinfo | memory | non-ip | path [extension | list | scope ]] | subtree context | switching background | table | xdr}
Syntax Description
Defaults
Debugging information about Cisco Express Forwarding events is not displayed.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Because debugging output is assigned high priority in the CPU process, you should use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, you should use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.
Examples
The following is sample output from the debug cef all command:
Router# debug cef all06:23:38: HW-API: Counter poll: Label[label=implicit-null]06:23:38: HW-API: Counter poll: Label[label=implicit-null]06:23:38: HW-API: Counter poll: Label[label=implicit-null]06:23:43: FIBbg: Timer 'FIB checkers: IPv4 scan-rib-ios scanner' expired, calling 0x40FA03FC, context 0x00010003)06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-rib-ios scanner' withdelay 6000006:23:43: FIBbg: Timer 'FIB checkers: IPv4 scan-ios-rib scanner' expired, calling 0x40FA03FC, context 0x00010004)06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-ios-rib scanner' withdelay 6000006:23:43: FIBbg: Timer 'FIB checkers: IPv6 scan-ios-rib scanner' expired, calling 0x40FA03FC, context 0x00020004)06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv6 scan-ios-rib scanner' withdelay 6000006:23:43: FIBbg: Timer 'FIB checkers: IPv4 scan-rp-lc scanner' expired, calling0x40FA03FC, context 0x00010002)06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-rp-lc scanner' with delay 6000006:23:43: FIBbg: Timer 'FIB checkers: IPv6 scan-rp-lc scanner' expired, calling0x40FA03FC, context 0x00020002)06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv6 scan-rp-lc scanner' with delay 6000006:23:48: HW-API: Counter poll: Label[label=implicit-null]06:23:48: HW-API: Counter poll: Label[label=implicit-null]06:23:48: HW-API: Counter poll: Label[label=implicit-null]06:23:58: HW-API: Counter poll: Label[label=implicit-null]06:24:06: FIBtable: IPv4: Event modified, 0.0.0.0/0, vrf Default, 1 path, flags0042000506:24:06: FIBpath: Configuring IPv4 path 444B2AB0 from rib (idb=NULL, gw=9.1.41.1, gw_table=0, rr=1) and host prefix 0.0.0.006:24:06: FIBpath: Configured recursive-nexthop 9.1.41.1[0] 444B2AB0 path06:24:06: FIBfib: [v4-0.0.0.0/0 (44AAC750)] Mod type - null06:24:06: FIBtable: IPv4: Event up, default, 0.0.0.0/0, vrf Default, 1 path, flags 0042000506:24:06: FIBtable: IPv4: Adding route for 0.0.0.0/0 but route already exists. Trying modify.06:24:06: FIBpath: Configuring IPv4 path 444B2AA0 from rib (idb=NULL, gw=9.1.41.1, gw_table=0, rr=1) and host prefix 0.0.0.0sh ip06:24:06: FIBpath: Configured recursive-nexthop 9.1.41.1[0] 444B2AA0 path06:24:06: FIBfib: [v4-0.0.0.0/0 (44AAC750)] Mod type - null vrf06:24:07: FIBbg: Timer 'FIB checkers: IPv4 scan-hw-sw scanner' expired, calling0x40FA03FC, context 0x00010005)06:24:07: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-hw-sw scanner' with delay 6000006:24:07: FIBbg: Timer 'FIB checkers: IPv4 scan-sw-hw scanner' expired, calling0x40FA03FC, context 0x00010006)06:24:07: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-sw-hw scanner' with delay 60000Name Default RD Interfacesred 1:1 Ethernet4/0/5Related Commands
debug cellular driver
To debug the Cisco IOS driver for the cellular interface, use the debug cellular driver command in EXEC mode.
debug cellular slot/wic_slot/port driver {crcdump | errdump | errors}
Syntax Description
slot/wic_slot/port
Numeric values that indicate the router slot, WAN interface card (WIC) slot, and port.
crcdump
CRC error details.
errdump
Other error details.
errors
Errors debugging.
Command Default
None
Command Modes
EXEC (#)
Command History
Usage Guidelines
Use this command for debugging purposes only.
Related Commands
debug cellular firmware
To see the Cisco IOS firmware information, use the debug cellular firmware command in EXEC mode.
debug cellular slot/wic_slot/port firmware
Syntax Description
slot/wic_slot/port
Numeric values that indicate the router slot, WAN interface card (WIC) slot, and port.
Command Default
None
Command Modes
EXEC
Command History
Usage Guidelines
Use this command for debugging purposes only.
Related Commands
debug cellular messages all
To print all Cisco IOS driver debug messages, use the debug cellular messages all command in EXEC mode.
debug cellular slot/wic_slot/port messages all
Syntax Description
slot/wic_slot/port
Numeric values that indicate the router slot, WAN interface card (WIC) slot, and port.
Command Default
None
Command Modes
EXEC
Command History
Usage Guidelines
Use this command for debugging purposes only.
Related Commands
debug cellular messages async
To debug cellular async, use the debug cellular messages async command in EXEC mode.
debug cellular slot/wic_slot/port messages async
Syntax Description
slot/wic_slot/port
Numeric values that indicate the router slot, WAN interface card (WIC) slot, and port.
Command Default
None
Command Modes
EXEC (#)
Command History
Usage Guidelines
Use this command for debugging purposes only.
Related Commands
debug cellular messages data
To print Cisco IOS data path debug messages, use the debug cellular messages data command in EXEC mode.
show cellular slot/wic_slot/port messages data
Syntax Description
slot/wic_slot/port
Numeric values that indicate the router slot, WAN interface card (WIC) slot, and port.
Command Default
None
Command Modes
EXEC
Command History
Usage Guidelines
Use this command for debugging purposes only.
Related Commands
debug cellular messages dm
To print Diagnostics Monitor (DM) messages from the Qualcomm CDMA chipset, use the debug cellular messages dm command in EXEC mode.
debug cellular slot/wic_slot/port messages dm
Syntax Description
slot/wic_slot/port
Numeric values that indicate the router slot, WAN interface card (WIC) slot, and port.
Command Default
There is no default for this command.
Command Modes
EXEC
Command History
Usage Guidelines
Use this command for debugging purposes only.
Related Commands
debug cellular messages management
To print management path messages, such as CnS, use the debug cellular messages management command in EXEC mode.
debug cellular slot/wic_slot/port messages management
Syntax Description
slot/wic_slot/port
Numeric values that indicate the router slot, WAN interface card (WIC) slot, and port.
Command Default
None
Command Modes
EXEC
Command History
Usage Guidelines
Use this command for debugging purposes only.
Related Commands
debug cellular messages virt-con
To redirect the Nios II console driver messages to display them in the Cisco IOS router console environment, use the debug cellular virt-con command in EXEC mode.
debug cellular slot/wic_slot/port virt-con {clear | disable | dump-data-structs | log | monitor | wrapper-on | wrapper-off}
Syntax Description
Command Default
There is no default for this command.
Command Modes
EXEC (#)
Command History
Usage Guidelines
Use this command for debugging purposes only.
Related Commands
debug cem ls errors
To debug connection errors or null data structures, use the debug cem ls errors command in privileged EXEC mode. To disable this form of debugging, use the no form of this command.
debug cem ls errors
no debug cem ls errors
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the show debug command to see debug information.
Examples
The following command turns on CEM local switching error debugging:
Router# debug cem ls errorsRelated Commands
debug cem ls events
Enables debugging of events relating to CEM local switching.
debug cem ls events
To debug CEM local switching events, use the debug cem ls events command in privileged EXEC mode. To disable this form of debugging, use the no form of this command.
debug cem ls events
no debug cem ls events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the show debug command to see debug information.
Examples
The following command turns on debugging for CEM local switching events.
Router# debug cem ls eventsRelated Commands
debug cem ls errors
Enables debugging of connection errors or null data structures.
debug ces-conn
To display information from circuit emulation service (CES) clients, use the debug ces-conn command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ces-conn [all | errors | events]
no debug ces-conn
Syntax Description
all
(Optional) Displays all error and event information.
errors
(Optional) Displays only error information.
events
(Optional) Displays only event information.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example shows debug output for a CES connection:
Router# debug ces-conn allCES all debugging is onRouter#Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# connect conn1 t1 3/0 1 atm1/0 1/100Router(config-ces-conn)# exitRouter(config)#*Mar 6 18:32:27:CES_CLIENT:vc QoS parameters are PCR = 590, CDV =5000, CAS_ENABLED = 1,partial fill = 0, multiplier = 8,cbr rate = 64,clock recovery = 0,service_type = 3, error method = 0,sdt_size = 196,billing count = 0*Mar 6 18:32:27:CES_CLIENT:attempt 1 to activate segment>debug cfm
'To enable debugging of the data path of Ethernet connectivity fault management (CFM) on Cisco Catalyst 6500 series switches, use the debug cfm command in privileged EXEC mode. To disable the debugging function, use the no form of this command.
debug cfm {all | api | cfmpal | common |db | isr}
no debug cfm {all | api | cfmpal | common |db | isr}
Syntax Description
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SXI2
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
The output from this command is a log of activity.
Use this command to troubleshoot Ethernet CFM on Cisco Catalyst 6500 series switches.
Examples
The following example shows output of the debug cfm all command:
Router# debug cfm allCFM DB events debugging is onCFM Ingress ISR events debugging is onCFMPAL events debugging is onCFM API events debugging is onCFM RP/SP COMMON events debugging is onCFM packets debugging is ondebug channel events
To display processing events on Cisco 7000 series routers that occur on the channel adapter interfaces of all installed adapters, use the debug channel events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug channel events
no debug channel events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays CMCC adapter events that occur on the Channel Interface Processor (CIP) or Channel Port Adapter (CPA) and is useful for diagnosing problems in an IBM channel attach network. It provides an overall picture of the stability of the network. In a stable network, the debug channel events command does not return any information. If the command generates numerous messages, the messages can indicate the possible source of the problems. To observe the statistic message (cip_love_letter) sent every 10 seconds, use the debug channel love command.
When configuring or making changes to a router or interface that supports IBM channel attach, enable the debug channel events command. Doing so alerts you to the progress of the changes or to any errors that might result. Also use this command periodically when you suspect network problems.
Examples
The following sample output is from the debug channel events command:
Router# debug channel eventsChannel3/0: cip_reset(), state administratively downChannel3/0: cip_reset(), state upChannel3/0: sending nodeidChannel3/0: sending command for vc 0, CLAW path C700, device C0The following line indicates that the CIP is being reset to an administrative down state:
Channel3/0: cip_reset(), state administratively downThe following line indicates that the CIP is being reset to an administrative up state:
Channel3/0: cip_reset(), state upThe following line indicates that the node ID is being sent to the CIP. This information is the same as the "Local Node" information under the show extended channel slot/port subchannels command. The CIP needs to send this information to the host mainframe.
Channel3/0: sending nodeidThe following line indicates that a Common Link Access for Workstations (CLAW) subchannel command is being sent from the Route Processor (RP) to the CIP. The value vc 0 indicates that the CIP will use virtual circuit number 0 with this device. The virtual circuit number also shows up when you use the debug channel packets command.
Channel3/0: sending command for vc 0, CLAW path C700, device C0The following is a sample output that is generated by the debug channel events command when a CMPC+ IP TG connection is activated with the host:
1d05h:Channel4/2:Received route UP for tg (768)1d05h:Adding STATIC ROUTE for vc:768The following is a sample output from the debug channel events command when a CMPC+ IP TG connection is deactivated:
1d05h:Channel4/2:Received route DOWN for tg (768)1d05h:Deleting STATIC ROUTE for vc:768Related Commands
debug channel ilan
Displays CIP love letter events.
debug channel packets
Displays per-packet debugging output.
debug channel ilan
To display messages relating to configuration and bridging using Cisco Mainframe Channel Connection (CMCC) internal LANs and to help debug source-route bridging (SRB) problems related to CMCC internal LANs, use the debug channel ilan command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug channel ilan
no debug channel ilan
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug channel ilan command displays events related to CMCC internal LANs. This command is useful for debugging problems associated with CMCC internal LAN configuration. It is also useful for debugging problems related to SRB packet flows through internal LANs.
Examples
The following is sample output from the debug channel ilan command:
Router# debug channel ilanChannel internal LANs debugging is onThe following line indicates that a packet destined for the CMCC via a configured internal MAC adapter configured on an internal LAN was dropped because the Logical Link Control (LLC) end station in Cisco IOS software did not exist:
CIP ILAN(Channel3/2-Token): Packet dropped - NULL LLCThe following line indicates that a packet destined for the CMCC via a configured internal MAC adapter configured on an internal LAN was dropped because the CMCC had not yet acknowledged the internal MAC adapter configuration command:
Channel3/2: ILAN Token-Ring 3 - CIP internal MAC adapter not acknowledged DMAC(4000.7000.0001) SMAC(0c00.8123.0023)Related Commands
debug channel love
To display Channel Interface Processor (CIP) love letter events, use the debug channel love command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug channel love
no debug channel love
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
This command displays CIP love letter events (an operating status or configuration message) that occur on the CIP interface processor and is useful for diagnosing problems in an IBM channel attach network. It provides an overall picture of the stability of the network. In a stable network, the debug channel love command returns a statistic message (cip_love_letter) that is sent every 10 seconds. This command is valid for the Cisco 7000 series routers only.
Examples
The following is sample output from the debug channel love command:
Router# debug channel loveChannel3/1: love letter received, bytes 3308Channel3/0: love letter received, bytes 3336cip_love_letter: received ll, but no cip_infoThe following line indicates that data was received on the CIP:
Channel3/1: love letter received, bytes 3308The following line indicates that the interface is enabled, but there is no configuration for it. It does not normally indicate a problem, just that the Route Processor (RP) got statistics from the CIP but has no place to store them.
cip_love_letter: received ll, but no cip_infoRelated Commands
debug channel events
Displays processing that occurs on the channel adapter interfaces of all installed adapters.
debug channel packets
Displays per-packet debugging output.
debug channel packets
To display per-packet debugging output, use the debug channel packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug channel packets
no debug channel packets
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The debug channel packets command displays all process-level Channel Interface Processor (CIP) packets for both outbound and inbound packets. The output reports information when a packet is received or a transmission is attempted. You will need to disable fast switching and autonomous switching to obtain debugging output. This command is useful for determining whether packets are received or sent correctly.
This command is valid for the Cisco 7000 series routers only.
Examples
The following is sample output from the debug channel packets command:
Router# debug channel packets(Channel3/0)-out size = 104, vc = 0000, type = 0800, src 172.24.0.11, dst 172.24.1.58(Channel3/0)-in size = 48, vc = 0000, type = 0800, src 172.24.1.58, dst 172.24.15.197(Channel3/0)-in size = 48, vc = 0000, type = 0800, src 172.24.1.58, dst 172.24.15.197(Channel3/0)-out size = 71, vc = 0000, type = 0800, src 172.24.15.197, dst 172.24.1.58(Channel3/0)-in size = 44, vc = 0000, type = 0800, src 172.24.1.58, dst 172.24.15.197Table 55 describes the significant fields shown in the display.
