-
Cisco IOS Debug Command Reference, Release 12.3 T
-
Debug: Introduction
-
Using Debug Commands
-
Conditionally Triggered Debugging
-
Debug Commands: debug aaa accounting through debug appn nof
-
Debug Commands: debug appn pc through debug bundle events
-
Debug Commands: debug cable env through debug ccfrf11 session
-
Debug Commands: debug cch323 through debug channel packets
-
Debug Commands: debug clns esis events through debug crypto pki messages
-
Debug Commands: debug crypto pki server through debug dlsw
-
Debug Commands: debug dmsp doc-to-fax through debug events
-
Debug Commands: debug fax dmsp through debug gprs radius
-
Debug Commands: debug h225 through debug ip drp
-
Debug Commands: debug ip dvmrp through debug ip mrouting limit
-
Debug Commands: debug ip msdp through debug ip scp
-
Debug Commands: debug ip sctp api through debug ipc rpc
-
Debug Commands: debug ipv6 cef drop through debug l2relay packets
-
Debug Commands: debug lane client through debug mmoip transfer
-
Debug Commands: debug modem through debug mpls ldp targeted-neighbors
-
Debug Commands: debug mpls ldp transport connections through debug mpls xtagatm vc
-
Debug Commands: debug mpoa client through debug oer master process
-
Debug Commands: debug packet through debug redundancy
-
Debug Commands: debug redundancy as5850 through debug rudpv1
-
Debug Commands: debug saa apm through debug source error
-
Debug Commands: debug source event through debug tacacs events
-
Debug Commands: debug tag-switching atm-cos through debug tag-switching xtagatm vc
-
Debug Commands: debug targ events through debug video vicm
-
Debug Commands: debug vlan packet through debug voip ipipgw
-
Debug Commands: debug voip ivr through debug vpm all
-
Debug Commands: debug vpm dsp through debug wlccp wds
-
Debug Commands: debug x25 through voice call debug
-
Debug: X.25 Cause and Diagnostic Codes
-
Debug: ISDN Switch Types, Codes, and Values
-
Table Of Contents
debug x25
To display information about all X.25 traffic or a specific X.25 service class, use the debug x25 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug x25 [only | cmns | xot] [events | all] [dump]
no debug x25 [only | cmns] [events | all] [dump]
Syntax Description
Defaults
All traffic is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
CautionThe X.25 debug commands can generate large amounts of debugging output. If logging of debug output to the router console is enabled (the default condition), this output may fill the console buffer, preventing the router from processing packets until the contents of the console buffer have been printed.
The debug x25, debug x25 interface, debug x25 vc, and debug x25 xot commands all generate the same basic output. The debug x25 interface, debug x25 vc, and debug x25 xot commands narrow the scope of the debug x25 output to specific virtual circuits or types of traffic.
This command is particularly useful for diagnosing problems encountered when placing calls. The debug x25 all output includes data, control messages, and flow control packets for all virtual circuits of the router.
All debug x25 commands can take either the events or the all keyword. The keyword all is the default and causes all packets meeting the other debug criteria to be reported. The keyword events omits reports of any Data or RR flow control packets; the normal flow of data and RR packets is commonly large and less interesting to the user, so event reporting can significantly decrease the processor load induced by debug reporting.
Use the dump keyword to display the entire contents, including user data, of X.25 packets. The encoded X.25 packet contents are displayed after the standard packet description. The output includes the offset into the packet and the display of the data in both hexadecimal and ASCII formats.
Caution
Examples
The following is sample output from the debug x25 command, displaying output concerning the functions X.25 restart, call setup, data exchange, and clear:
Router# debug x25Serial0: X.25 I R/Inactive Restart (5) 8 lci 0Cause 7, Diag 0 (Network operational/No additional information)Serial0: X.25 O R3 Restart Confirm (3) 8 lci 0Serial0: X.25 I P1 Call (15) 8 lci 1From(6): 170091 To(6): 170090Facilities: (0)Call User Data (4): 0xCC000000 (ip)Serial0: X.25 O P3 Call Confirm (3) 8 lci 1Serial0: X.25 I D1 Data (103) 8 lci 1 PS 0 PR 0Serial0: X.25 O D1 Data (103) 8 lci 1 PS 0 PR 1Serial0: X.25 I P4 Clear (5) 8 lci 1Cause 9, Diag 122 (Out of order/Maintenance action)Serial0: X.25 O P7 Clear Confirm (3) 8 lci 1debug x25 events for DNS-Based X.25 Routing: Example
The following example of the debug x25 command with the events keyword shows output related to the DNS-Based X.25 Routing feature. It shows messages concerning access to the DNS server. In the example, nine alternate addresses for one XOT path are entered into the DNS server database. All nine addresses are returned to the host cache of the router by the DNS server. However, only six addresses will be used during the XOT switch attempt because this is the limit that XOT allows.
Router# debug x25 events00:18:25:Serial1:X.25 I R1 Call (11) 8 lci 102400:18:25: From (0): To (4):44400:18:25: Facilities:(0)00:18:25: Call User Data (4):0x01000000 (pad)00:18:25:X.25 host name sent for DNS lookup is "444"00:18:26:%3-TRUNCATE_ALT_XOT_DNS_DEST:Truncating excess XOT addresses (3)returned by DNS00:18:26:DNS got X.25 host mapping for "444" via network00:18:32:[10.1.1.8 (pending)]:XOT open failed (Connection timed out; remote host not responding)00:18:38:[10.1.1.7 (pending)]:XOT open failed (Connection timed out; remote host not responding)00:18:44:[10.1.1.6 (pending)]:XOT open failed (Connection timed out; remote host not responding)00:18:50:[10.1.1.5 (pending)]:XOT open failed (Connection timed out; remote host not responding)00:18:56:[10.1.1.4 (pending)]:XOT open failed (Connection timed out; remote host not responding)00:20:04:[10.1.1.3,1998/10.1.1.3,11007]:XOT O P2 Call (17) 8 lci 100:20:04: From (0): To (4):44400:20:04: Facilities:(6)00:20:04: Packet sizes:128 12800:20:04: Window sizes:2 200:20:04: Call User Data (4):0x01000000 (pad)00:20:04:[10.1.1.3,1998/10.1.1.3,11007]:XOT I P2 Call Confirm (11) 8 lci 100:20:04: From (0): To (0):00:20:04: Facilities:(6)00:20:04: Packet sizes:128 12800:20:04: Window sizes:2 200:20:04:Serial1:X.25 O R1 Call Confirm (5) 8 lci 102400:20:04: From (0): To (0):00:20:04: Facilities:(0)Record Boundary Preservation: Examples
The following examples show output for the x25 debug command with the events keyword when record boundary preservation (RBP) has been configured using the x25 map rbp local command.
The following display shows establishment of connection:
X25 RBP:Incoming connection for port 9999 from 10.0.155.30 port 11001Serial0/1:X.25 O R1 Call (10) 8 lci 64From (5):13133 To (5):12131Facilities:(0)Serial0/1:X.25 I R1 Call Confirm (3) 8 lci 64The following display shows that the X.25 call was cleared by the X.25 host:
Serial0/1:X.25 I R1 Clear (5) 8 lci 64Cause 0, Diag 122 (DTE originated/Maintenance action)X25 RBP:X.25 circuit clearedSerial0/1:X.25 O R1 Clear Confirm (3) 8 lci 64The following display shows that the TCP session has terminated:
[10.0.155.30,11000/10.0.155.33,9999]:TCP receive error, End of data transferX25 RBP:End of data transferSerial0/1:X.25 O R1 Clear (5) 8 lci 64Cause 9, Diag 122 (Out of order/Maintenance action)Serial0/1:X.25 I R1 Clear Confirm (3) 8 lci 64The following examples show output of the x25 debug command with the events keyword when RBP has been configured using the x25 pvc rbp local command.
The following display shows data on the permanent virtual circuit (PVC) before the TCP session has been established:
X25 RBP:Data on unconnected PVCSerial1/0:X.25 O D1 Reset (5) 8 lci 1Cause 0, Diag 113 (DTE originated/Remote network problem)Serial1/0:X.25 I D2 Reset Confirm (3) 8 lci 1The following display shows establishment of connection:
X25 RBP:Incoming connection for port 9998 from 2.30.0.30 port 11002Serial1/0:X.25 O D1 Reset (5) 8 lci 1Cause 0, Diag 0 (DTE originated/No additional information)Serial1/0:X.25 I D2 Reset Confirm (3) 8 lci 1The following display shows termination of connection when the X.25 PVC was reset:
Serial1/0:X.25 I D1 Reset (5) 8 lci 1Cause 15, Diag 122 (Network operational (PVC)/Maintenance action)X25 RBP:Reset packet receivedSerial1/0:X.25 O D3 Reset Confirm (3) 8 lci 1The following display shows that the TCP session has terminated:
[2.30.0.30,11003/2.30.0.33,9998]:TCP receive error, End of data transferX25 RBP:End of data transferSerial1/0:X.25 O D1 Reset (5) 8 lci 1Cause 0, Diag 113 (DTE originated/Remote network problem)Serial1/0:X.25 I D2 Reset Confirm (3) 8 lci 1The following examples show output of the x25 debug command with the events keyword when RBP has been configured using the x25 map rbp remote command.
The following display shows that the X.25 call was cleared:
Serial0/1:X.25 I R1 Clear (5) 8 lci 1024Cause 0, Diag 122 (DTE originated/Maintenance action)X25 RBP:X.25 circuit clearedSerial0/1:X.25 O R1 Clear Confirm (3) 8 lci 1024The following display shows that the X.25 call was reset:
Serial0/1:X.25 I D1 Reset (5) 8 lci 1024Cause 0, Diag 122 (DTE originated/Maintenance action)X25 RBP:Reset packet receivedSerial0/1:X.25 O R1 Clear (5) 8 lci 1024Cause 9, Diag 122 (Out of order/Maintenance action)Serial0/1:X.25 I R1 Clear Confirm (3) 8 lci 1024The following examples show output of the x25 debug command with the events keyword when RBP has been configured using the x25 pvc rbp remote command.
The following display shows that the X.25 PVC has been reset:
Serial0/0:X.25 I D1 Reset (5) 8 lci 1Cause 0, Diag 122 (DTE originated/Maintenance action)X25 RBP:Reset packet receivedSerial0/0:X.25 O D2 Reset Confirm (3) 8 lci 1The following display shows that the connection was terminated when the X.25 interface was restarted:
Serial0/0:X.25 I R1 Restart (5) 8 lci 0Cause 0, Diag 122 (DTE originated/Maintenance action)X25 RBP:X.25 PVC inactiveSerial0/0:X.25 O R2 Restart Confirm (3) 8 lci 0Serial0/0:X.25 O D1 Reset (5) 8 lci 1Cause 1, Diag 113 (Out of order (PVC)/Remote network problem)Serial0/0:X.25 I D3 Reset Confirm (3) 8 lci 1debug x25 dump Example
The following is sample output for the debug x25 dump command. The encoded X.25 packet contents are displayed after the standard packet description. The output includes the offset into the packet and the display of the data in both hexadecimal and ASCII formats.
Router# debug x25 dumpSerial1: X.25 O R/Inactive Restart (5) 8 lci 0Cause 0, Diag 0 (DTE originated/No additional information)0: 1000FB00 00 ..{..Serial1: X.25 I R2 Restart (5) 8 lci 0Cause 7, Diag 0 (Network operational/No additional information)0: 1000FB ..{3: 0700 ..Serial1: X.25 I R1 Call (13) 8 lci 1From (4): 2501 To (4): 2502Facilities: (0)Call User Data (4): 0xCC000000 (ip)0: 10010B 44250225 0100CC00 ...D%.%..L.11: 0000 ..Serial1: X.25 O R1 Call Confirm (3) 8 lci 10: 10010F ...Serial1: X.25 I D1 Data (103) 8 lci 1 PS 0 PR 00: 100100 45000064 00000000 ...E..d....11: FF01A764 0A190001 0A190002 0800CBFB ..'d..........K{27: 0B1E22CA 00000000 00028464 ABCDABCD .."J.......d+M+M43: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M59: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M75: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M91: ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+MSerial1: X.25 O D1 Data (103) 8 lci 1 PS 0 PR 10: 100120 45000064 00000000 .. E..d....11: FF01A764 0A190002 0A190001 0000D3FB ..'d..........S{27: 0B1E22CA 00000000 00028464 ABCDABCD .."J.......d+M+M43: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M59: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M75: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M91: ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+MSerial1: X.25 I R1 Clear (5) 8 lci 1Cause 9, Diag 122 (Out of order/Maintenance action)0: 100113 097A ....zSerial1: X.25 O R1 Clear Confirm (3) 8 lci 10: 100117 .Table 337 describes significant fields shown in the displays.
Related Commands
debug x25 annexg
To display information about Annex G (X.25 over Frame Relay) events, use the debug x25 annexg command. To disable debugging output, use the no form of this command.
debug x25 annexg
no debug x25 annexg
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
It is generally recommended that the debug x25 annexg command be used only when specifically requested by Cisco TAC to obtain information about a problem with an Annex G configuration. The messages displayed by the debug x25 annexg command are meant to aid in the diagnosing of internal errors.
Caution
Examples
The following shows sample output from the debug x25 annexg command for a Frame Relay data-link connection identifier (DLCI) configured for Annex G operation:
Router# debug x25 annexgJul 31 05:23:20.316:annexg_process_events:DLCI 18 attached to interface Serial2/0:0 is ACTIVEJul 31 05:23:20.316:annexg_ctxt_create:Creating X.25 context over Serial2/0:0 (DLCI:18 using X.25 profile:OMC), type 10, len 2, addr 00 12Jul 31 05:23:20.316:annexg_create_lower_layer:Se2/0:0 DLCI 18, payload 1606, overhead 2Jul 31 05:23:20.320:annexg_restart_tx:sending pak to Serial2/0:0Jul 31 05:23:23.320:annexg_restart_tx:sending pak to Serial2/0:0Table 338 describes significant fields shown in the display.
Related Commands
debug x25 aodi
To display information about an interface running PPP over an X.25 session, use the debug x25 aodi command. To disable debugging output, use the no form of this command.
debug x25 aodi
no debug x25 aodi
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug x25 aodi command to display interface PPP events running over an X.25 session and to debug X.25 connections between a client and server configured for Always On/Dynamic ISDN (AO/DI).
Examples
The following examples show the normal sequence of events for both the AO/DI client and the server sides:
Client Side
Router# debug x25 aodiPPP-X25: Virtual-Access1: Initiating AODI call requestPPP-X25: Bringing UP X.25 AODI VCPPP-X25: AODI Client Call Confirm Event ReceivedPPP-X25: Cloning interface for AODI is Di1PPP-X25: Queuing AODI Client Map EventPPP-X25: Event:AODI Client MapPPP-X25: Created interface Vi2 for AODI servicePPP-X25: Attaching primary link Vi2 to Di1PPP-X25: Cloning Vi2 for AODI service using Di1PPP-X25: Vi2: Setting the PPP call direction as OUTPPP-X25: Vi2: Setting vectors for RFC1598 operation on BRI3/0:0 VC 0PPP-X25: Vi2: Setting the interface default bandwidth to 10 KbpsPPP-X25: Virtual-Access2: Initiating AODI call requestPPP-X25: Bringing UP X.25 AODI VCPPP-X25: AODI Client Call Confirm Event ReceivedServer Side
Router# debug x25 aodiPPP-X25: AODI Call Request Event ReceivedPPP-X25: Event:AODI Incoming Call RequestPPP-X25: Created interface Vi1 for AODI servicePPP-X25: Attaching primary link Vi1 to Di1PPP-X25: Cloning Vi1 for AODI service using Di1PPP-X25: Vi1: Setting vectors for RFC1598 operation on BRI3/0:0 VC 1PPP-X25: Vi1: Setting the interface default bandwidth to 10 KbpsPPP-X25: Binding X.25 VC 1 on BRI3/0:0 to Vi1debug x25 interface
To display information about the specific X.25, Annex G or Connection Mode Network Service (CMN) contexts or virtual circuits that occur on the identified interface, use the debug x25 interface command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug x25 interface {serial-interface | cmns-interface [mac mac-address]} [vc number] [events | all] [dump]
no debug x25 interface {serial-interface | cmns-interface [mac mac-address]} [vc number] [events | all] [dump]
Syntax Description
Defaults
All traffic is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Caution
The debug x25, debug x25 interface, debug x25 vc, and debug x25 xot commands all generate the same basic output. The debug x25 interface, debug x25 vc, and debug x25 xot commands narrow the scope of the debug x25 output to specific virtual circuits or types of traffic.
The debug x25 interface command is useful for diagnosing problems encountered with a single X.25 or CMNS host or virtual circuit.
The keyword all is the default and causes all packets meeting the other debug criteria to be reported. The keyword events omits reports of any Data or RR flow control packets; the normal flow of data and RR packets is commonly large and less interesting to the user, so event reporting can significantly decrease the processor load induced by debug reporting.
Use the dump keyword to display the entire contents, including user data, of X.25 packets. The encoded X.25 packet contents are displayed after the standard packet description. The output includes the offset into the packet and the display of the data in both hexadecimal and ASCII formats.
Caution
Examples
The following is sample output from the debug x25 interface command:
Router# debug x25 interface serial 0X.25 packet debugging is onX.25 packet debugging is restricted to interface serial0Serial0: X.25 I R/Inactive Restart (5) 8 lci 0Cause 7, Diag 0 (Network operational/No additional information)Serial0: X.25 O R3 Restart Confirm (3) 8 lci 0Serial0: X.25 I P1 Call (15) 8 lci 1From(6): 170091 To(6): 170090Facilities: (0)Call User Data (4): 0xCC000000 (ip)Serial0: X.25 O P3 Call Confirm (3) 8 lci 1Serial0: X.25 I D1 Data (103) 8 lci 1 PS 0 PR 0Serial0: X.25 O D1 Data (103) 8 lci 1 PS 0 PR 1Serial0: X.25 I P4 Clear (5) 8 lci 1Cause 9, Diag 122 (Out of order/Maintenance action)Serial0: X.25 O P7 Clear Confirm (3) 8 lci 1Table 339 describes the significant fields shown in the display.
Related Commands
debug x25 vc
To display information about traffic for all virtual circuits that have a given number, use the debug x25 vc command. To disable debugging output, use the no form of this command.
debug x25 vc number [events | all] [dump]
no debug x25 vc number [events | all] [dump]
Syntax Description
Defaults
All traffic is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Caution
The debug x25, debug x25 interface, debug x25 vc, and debug x25 xot commands all generate the same basic output. The debug x25 interface, debug x25 vc, and debug x25 xot commands narrow the scope of the debug x25 output to specific virtual circuits or types of traffic.
Because no interface is specified by the debug x25 vc command, traffic on any virtual circuit that has the specified number is reported.
Virtual circuit (VC) zero (vc 0) cannot be specified. It is used for X.25 service messages, such as RESTART packets, not virtual circuit traffic. Service messages can be monitored only when no virtual circuit filter is used.
Use the dump keyword to display the entire contents, including user data, of X.25 packets. The encoded X.25 packet contents are displayed after the standard packet description. The output includes the offset into the packet and the display of the data in both hexadecimal and ASCII formats.
Caution
Examples
The following shows sample output from the debug x25 vc command:
Router# debug x25 vc 1 eventsX.25 special event debugging is onX.25 debug output restricted to VC number 1Router# show debugX.25 (filtered for VC 1):X.25 special event debugging is on*Jun 18 20:22:29.735 UTC:Serial0:X.25 O R1 Call (13) 8 lci 1*Jun 18 20:22:29.735 UTC: From (4):2501 To (4):2502*Jun 18 20:22:29.735 UTC: Facilities:(0)*Jun 18 20:22:29.735 UTC: Call User Data (4):0xCC000000 (ip)*Jun 18 20:22:29.739 UTC:Serial0:X.25 I R1 Call Confirm (3) 8 lci 1*Jun 18 20:22:36.651 UTC:Serial0:X.25 O R1 Clear (5) 8 lci 1*Jun 18 20:22:36.651 UTC: Cause 9, Diag 122 (Out of order/Maintenance action)*Jun 18 20:22:36.655 UTC:Serial0:X.25 I R1 Clear Confirm (3) 8 lci 1Table 340 describes significant fields shown in the display.
Related Commands
debug x25 xot
To display information about traffic to or from a specific X.25 over TCP (XOT) host, use the debug x25 xot command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug x25 xot [remote ip-address [port number]] [local ip-address [port number]] [events | all] [dump]
no debug x25 xot [remote ip-address [port number]] [local ip-address [port number]] [events | all] [dump]
Syntax Description
Defaults
All traffic is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Caution
The debug x25, debug x25 interface, debug x25 vc, and debug x25 xot commands all generate the same basic output. The debug x25 interface, debug x25 vc, and debug x25 xot commands narrow the scope of the debug x25 output to specific virtual circuits or types of traffic.
The debug x25 xot output allows you to restrict the debug output reporting to XOT traffic for one or both hosts or host/port combinations. Because each XOT virtual circuit uses a unique TCP connection, an XOT debug request that specifies both host addresses and ports will report traffic only for that virtual circuit. Also, you can restrict reporting to sessions initiated by the local or remote router by specifying 1998 for the remote or local port. (XOT connections are received on port 1998.)
Use the dump keyword to display the entire contents, including user data, of X.25 packets. The encoded X.25 packet contents are displayed after the standard packet description. The output includes the offset into the packet and the display of the data in both hexadecimal and ASCII formats.
Caution
Examples
The following shows sample output from the debug x25 xot command:
Router# debug x25 xotX.25 packet debugging is onX.25 debug output restricted to protocol XOTRouter# show debugX.25 (filtered for XOT):X.25 packet debugging is on*Jun 18 20:32:34.699 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I P/Inactive Call (19) 8 lci 1*Jun 18 20:32:34.699 UTC: From (4):2501 To (4):2502*Jun 18 20:32:34.699 UTC: Facilities:(6)*Jun 18 20:32:34.699 UTC: Packet sizes:128 128*Jun 18 20:32:34.699 UTC: Window sizes:2 2*Jun 18 20:32:34.699 UTC: Call User Data (4):0xCC000000 (ip)*Jun 18 20:32:34.707 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O P3 Call Confirm (11) 8 lci 1*Jun 18 20:32:34.707 UTC: From (0): To (0):*Jun 18 20:32:34.707 UTC: Facilities:(6)*Jun 18 20:32:34.707 UTC: Packet sizes:128 128*Jun 18 20:32:34.707 UTC: Window sizes:2 2*Jun 18 20:32:34.715 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I D1 Data (103) 8 lci 1 PS 0 PR 0*Jun 18 20:32:34.723 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O D1 Data (103) 8 lci 1 PS 0 PR 1*Jun 18 20:32:34.731 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I D1 Data (103) 8 lci 1 PS 1 PR 1*Jun 18 20:32:34.739 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O D1 Data (103) 8 lci 1 PS 1 PR 2*Jun 18 20:32:34.747 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I D1 Data (103) 8 lci 1 PS 2 PR 2*Jun 18 20:32:34.755 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O D1 Data (103) 8 lci 1 PS 2 PR 3*Jun 18 20:32:34.763 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I D1 Data (103) 8 lci 1 PS 3 PR 3*Jun 18 20:32:34.771 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O D1 Data (103) 8 lci 1 PS 3 PR 4*Jun 18 20:32:34.779 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I D1 Data (103) 8 lci 1 PS 4 PR 4*Jun 18 20:32:34.787 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O D1 Data (103) 8 lci 1 PS 4 PR 5Table 341 describes the significant fields shown in the display.
Related Commands
debug x28
To monitor error information and X.28 connection activity, use the debug x28 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug x28
no debug x28
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output while the packet assembler/disassembler (PAD) initiates an X.28 outgoing call:
Router# debug x28X28 MODE debugging is onRouter# x28*03:30:43: X.28 mode session started03:30:43: X28 escape is exit03:30:43: Speed for console & vty lines :9600*call 123456COM03:39:04: address ="123456", cud="[none]" 03:39:04: Setting X.3 Parameters for this call...1:1 2:1 3:126 4:0 5:1 6:2 7:2 8:0 9:0 10:0 11:14 12:1 13:0 14:0 15:0 16:127 17:24 18:18 19:2 20:0 21:0 22:0Router> exitCLR CONF**03:40:50: Session ended* exitRouter#*03:40:51: Exiting X.28 modedebug xcctsp all
To debug External Call Control Telephony Service Provider (TSP) information, use the debug xcctsp all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug xcctsp all
no debug xcctsp all
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Examples
See the following examples to turn on and off external call control debugging:
AS5300-TGW# debug xcctsp allExternal call control all debugging is onAS5300-TGW# no debug xcctsp allExternal call control all debugging is offAS5300-TGW#Related Commands
debug xcctsp error
Enables debugging on external call control errors.
debug xcctsp session
Enables debugging on external call control sessions.
debug xcctsp error
To debug External Call Control Telephony Service Provider (TSP) error information, use the debug xcctsp error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug xcctsp error
no debug xcctsp error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was integrated on the Cisco uBR924 cable modem.
Examples
See the following examples to turn on and off error-level debugging:
AS5300-TGW# debug xcctsp errorExternal call control error debugging is onAS5300-TGW# no debug xcctsp errorExternal call control error debugging is offRelated Commands
debug xcctsp all
Enables debugging on all external call control levels.
debug xcctsp session
Enables debugging on external call control sessions.
debug xcctsp session
To debug External Call Control Telephony Service Provider (TSP) session information, use the debug xcctsp session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug xcctsp session
no debug xcctsp session
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was integrated on the Cisco uBR924 cable modem.
Examples
See the following examples to turn on and off session-level debugging:
AS5300-TGW# debug xcctsp sessionExternal call control session debugging is onAS5300-TGW# no debug xcctsp sessionExternal call control session debugging is offAS5300-TGW#Related Commands
debug xcctsp all
Enables debugging on external call control levels.
debug xcctsp error
Enables debugging on external call control errors.
debug xconnect
To debug a problem related to the Xconnect configuration, use the debug xconnect command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug xconnect {error | event}
no debug xconnect {error | event}
Syntax Description
error
Displays errors related to an Xconnect configuration.
event
Displays events related to an Xconnect configuration processing.
Command Modes
Privileged EXEC
Command History
12.0(23)S
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
Usage Guidelines
Use this command to display debugging information about Xconnect sessions.
Examples
The following shows sample output from the debug xconnect command for an Xconnect session on an Ethernet interface:
Router# debug xconnect00:01:16: XC AUTH [Et2/1, 5]: Event: start xconnect authorization, state changed from IDLE to AUTHORIZING00:01:16: XC AUTH [Et2/1, 5]: Event: found xconnect authorization, state changed from AUTHORIZING to DONE00:01:16: XC AUTH [Et2/1, 5]: Event: free xconnect authorization request, state changed from DONE to ENDRelated Commands
debug xcsp
To display the debugging messages for the External Control Service Provider (XCSP) subsystem, use the debug xcsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug xcsp {all | cot | event}
no debug xcsp {all | cot | event}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.2(2)XB
This command was introduced.
12.2(11)T
The command was integrated into Cisco IOS Release 12.2(11)T for the Cisco AS5850.
Usage Guidelines
This command is used with the Network Access Server Package for MGCP. The XCSP subsystem is not configured directly, but information about it may be useful in troubleshooting. The debug xcsp command is used to display the exchange of signaling information between the MGCP protocol stack and end applications such as call switching module (CSM) or dialer.
The cot keyword is not used with the Network Access Server Package for MGCP feature.
Examples
The following shows sample output from the debug xcsp all command and keyword and the debug xcsp event command and keyword:
Router# debug xcsp allxcsp all debugging is onRouter# debug xcsp eventxcsp events debugging is on01:49:14:xcsp_call_msg:Event Call Indication , channel state = Idle forslot port channel 7c5400# 0 2301:49:14:xcsp_process_sig_fsm:state/event Idle / Call Indication01:49:14:xcsp_incall:01:49:14:xcsp_incall CONNECT_IND:cdn=3000 cgn=100001:49:14:xcsp:START guard TIMER01:49:14:xcsp_fsm:slot 7 port 0 chan 23 oldstate = Idle newstate= Connectionin progress mgcpapp_process_mgcp_msg PROCESSED NAS PACKAGE EVENT01:49:14:Received message on XCSP_CDAPI01:49:14:process_cdapi_msg :slot/port/channel 7/0/2301:49:14: process_cdapi_msg:new slot/port/channel 7/0/2301:49:14:c5400#Received CONN_RESP:callid=0x701601:49:14:process_cdapi:Event CONN_RESP, channel state = 8 for slot portchannel 7 0 2301:49:14:xcsp_process_sig_fsm:state/event Connection in progress / In Callacceptmgcpapp_xcsp_alert:mgcpapp_xcsp_get_chan_cb -Found - Channel state Connection in progress200 58 AlertI:630AED90<---:Ack send SUCCESSFUL01:49:14:xcsp_fsm:slot 7 pc5400#ort 0 chan 23 oldstate = Connection in progress newstate= Connection inprogress01:49:14:Received message on XCSP_CDAPI01:49:14:process_cdapi_msg :slot/port/channel 7/0/2301:49:14: process_cdapi_msg:new slot/port/channel 7/0/2301:49:14: Received CALL_CONN:callid=0x701601:49:14:process_cdapi:Event CONN_, channel state = 8 for slot port channel 70 2301:49:14:xcsp_process_sig_fsm:state/event Connection in progress / in callconnectmgcpapp_xcsp_connect:mgcpapp_xcc5400#sp_get_chan_cb -Found - Channel state In Use01:49:14:STOP TIMER01:49:14:xcsp_fsm:slot 7 port 0 chan 23 oldstate = Connection in progressnewstate=In Usec5400#01:50:23:Received message on XCSP_CDAPI01:50:23:process_cdapi_msg :slot/port/channel 7/0/2301:50:23: process_cdapi_msg:new slot/port/channel 7/0/2301:50:23: Received CALL_DISC_REQ:callid=0x701601:50:23:process_cdapi:Event DISC_CONN_REQ, channel state = 7 for slot portchannel 7 0 2301:50:23:xcsp_process_sig_fsm:state/event In Use / release Requestmgcpapp_xcsp_disconnectmgcpapp_xcsp_get_chan_cb -Fouc5400#nd - Channel state In Use01:50:23:send_mgcp_msg, MGCP Packet sent --->01:50:23:RSIP 1 *@c5400 MGCP 1.0RM:restartDLCX 4 S7/DS1-0/23 MGCP 1.0C:3I:630AED90E:801 /NAS User request01:50:23:xcsp_fsm:slot 7 port 0 chan 23 oldstate = In Use newstate=OutRelease in progressxcsp_restart Serial7/0:22 vc = 22xcsp_restart Put idb Serial7/0:22 in down state01:50:23:MGCP Packet received -200 4 byeData call ack received callp=0x62AEEA70mgcpapp_xcspc5400#_ack_recv:mgcpapp_xcsp_get_chan_cb -Found - Channel state Out Release inprogressmgcpapp_xcsp_ack_recv ACK 200 rcvd:transaction id = 4 endpt=S7/DS1-0/2301:50:23:xcsp_call_msg:Event Release confirm , channel state = Out Release inprogress for slot port channel 7 0 2301:50:23:xcsp_process_sig_fsm:state/event Out Release in progress/ Releaseconfirm01:50:23:STOP TIMER01:50:23:xcsp_fsm:slot 7 port 0 chan 23 oldstate = Out Release in progressnewstate= IdleRelated Commands
debug xdsl application
To monitor the xDSL if the digital subscriber line (DSL) does not come up, use the debug xdsl application command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug xdsl application
no debug xdsl application
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug xdsl application command details what occurs during the Cisco IOS SHDSL process events and signal-to-noise ratio sampling of the SHDSL chip. This information can be used more for software debugging in analyzing the internal events.
Examples
The following is sample output from the debug xdsl application command:
Router# debug xdsl applicationxDSL application debugging is onRouter#The following lines show that the application is starting on the router and waiting for a response:
00:47:40: DSL 0/0 process_get_wakeup00:47:41: DSL 0/0 process_get_wakeup00:47:42: DSL 0/0 process_get_wakeup00:47:43: DSL 0/0 process_get_wakeup00:47:44: DSL 0/0 process_get_wakeup00:47:45: DSL 0/0 process_get_wakeup00:47:46: DSL 0/0 process_get_wakeup00:47:47: DSL 0/0 process_get_wakeup00:47:48: DSL 0/0 process_get_wakeup00:47:49: DSL 0/0 process_get_wakeup00:47:49: DSL 0/0 process_get_wakeupThe following lines show that the controller link comes up:
00:47:49: DSL 0/0 xdsl_background_process: XDSL link up boolean event received00:47:49: DSL 0/0 controller Link up! line rate: 1600 KbpsThe following lines show that the DSL controller comes up:
00:47:49: DSL 0/0 xdsl_controller_reset: cdb-state=up00:47:49: %CONTROLLER-5-UPDOWN: Controller DSL 0/0, changed state to up00:47:49: Dslsar data rate 160000:47:49: DSL 0/0 TipRing 1, Xmit_Power Val 75, xmit_power 7.500:47:49: DSL 0/0 Mode 2, BW 1600, power_base_value 135, power_backoff 600:47:50: DSL 0/0 process_get_wakeup00:47:51: DSL 0/0 process_get_wakeup00:47:52: DSL 0/0 process_get_wakeup00:47:53: DSL 0/0 process_get_wakeup00:47:54: DSL 0/0 process_get_wakeup00:47:55: DSL 0/0 process_get_wakeup00:47:56: DSL 0/0 process_get_wakeupThe following lines show signal-to-noise ratio sampling:
00:47:56: DSL 0/0 SNR Sampling: 42 dB00:47:57: DSL 0/0 process_get_wakeup00:47:57: DSL 0/0 SNR Sampling: 41 dB00:47:58: DSL 0/0 process_get_wakeup00:47:58: DSL 0/0 SNR Sampling: 40 dB00:47:59: DSL 0/0 process_get_wakeup00:47:59: DSL 0/0 SNR Sampling: 40 dB00:48:00: DSL 0/0 process_get_wakeup00:48:00: DSL 0/0 SNR Sampling: 39 dB00:48:01: DSL 0/0 process_get_wakeup00:48:01: DSL 0/0 SNR Sampling: 39 dB00:48:02: DSL 0/0 process_get_wakeup00:48:02: DSL 0/0 SNR Sampling: 38 dB00:48:03: DSL 0/0 process_get_wakeup00:48:03: DSL 0/0 SNR Sampling: 38 dB00:48:04: DSL 0/0 process_get_wakeup00:48:04: DSL 0/0 SNR Sampling: 38 dB00:48:05: DSL 0/0 process_get_wakeup00:48:05: DSL 0/0 SNR Sampling: 37 dB00:48:06: DSL 0/0 process_get_wakeup00:48:06: DSL 0/0 SNR Sampling: 37 dB00:48:07: DSL 0/0 process_get_wakeup00:48:07: DSL 0/0 SNR Sampling: 36 dBThe following lines show that the link comes up:
00:48:07: %LINK-3-UPDOWN: Interface ATM0/0, changed state to up00:48:08: DSL 0/0 process_get_wakeup00:48:08: DSL 0/0 SNR Sampling: 36 dBThe following lines show that the line protocol comes up:
00:48:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/0, changed state to up00:48:09: DSL 0/0 process_get_wakeup00:48:09: DSL 0/0 SNR Sampling: 36 dB00:48:10: DSL 0/0 process_get_wakeup00:48:10: DSL 0/0 SNR Sampling: 36 dB00:48:11: DSL 0/0 process_get_wakeup00:48:11: DSL 0/0 SNR Sampling: 35 dB00:48:12: DSL 0/0 process_get_wakeup00:48:12: DSL 0/0 SNR Sampling: 36 dB00:48:13: DSL 0/0 process_get_wakeup00:48:13: DSL 0/0 SNR Sampling: 36 dB00:48:14: DSL 0/0 process_get_wakeup00:48:14: DSL 0/0 SNR Sampling: 36 dB00:48:15: DSL 0/0 process_get_wakeup00:48:15: DSL 0/0 SNR Sampling: 36 dB00:48:16: DSL 0/0 process_get_wakeup00:48:16: DSL 0/0 SNR Sampling: 36 dB00:48:17: DSL 0/0 process_get_wakeup00:48:17: DSL 0/0 SNR Sampling: 35 dB00:48:18: DSL 0/0 process_get_wakeup00:48:18: DSL 0/0 SNR Sampling: 35 dB00:48:19: DSL 0/0 process_get_wakeupRelated Commands
debug xdsl driver
To display what is happening when the drivers are downloaded and installed, use the debug xdsl driver command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug xdsl driver
no debug xdsl driver
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug xdsl driver command to monitor what is happening when downloading the firmware. This debugging command displays the Globespan DSL Driver details and provides framer interrupt information and line training failure information. This information can help you understand the problems faced while downloading the firmware, why the line went down, and so forth.
Examples
The following is sample output from the debug xdsl driver command:
Router# debug xdsl driverxDSL driver debugging is onThe following lines show that the DSP interrupt download is running:
*Mar 12 08:01:04.772: DSL 0/2 dsp interrupt-download next block for line-0*Mar 12 08:01:04.780: DSL 0/2 framer intr_status 0xC0*Mar 12 08:01:05.072: DSL 0/2 dsp interrupt-download next block for line-0*Mar 12 08:01:05.080: DSL 0/2 framer intr_status 0xC0*Mar 12 08:01:06.484: DSL 0/2 dsp interrupt-download next block for line-0*Mar 12 08:01:06.492: DSL 0/2 framer intr_status 0xC0*Mar 12 08:01:08.092: DSL 0/2 dsp interrupt-download next block for line-0*Mar 12 08:01:08.096: DSL 0/2 framer intr_status 0xC0*Mar 12 08:01:19.180: DSL 0/2 dsp interrupt-download next block for line-0*Mar 12 08:01:19.184: DSL 0/2 framer intr_status 0xC0*Mar 12 08:01:19.480: DSL 0/2 dsp interrupt-download next block for line-0*Mar 12 08:01:19.484: DSL 0/2 framer intr_status 0xC0*Mar 12 08:01:19.680: DSL 0/2 dsp interrupt-download next block for line-0The following lines show that the DSP interrupt has been disabled and that the framer interrupt has been enabled:
*Mar 12 08:01:19.680: DSL 0/2 DSP interrupt disabled*Mar 12 08:01:19.680: DSL 0/2 Download completed for line-0*Mar 12 08:01:19.680: DSL 0/2 Framer interrupt enabled*Mar 12 08:01:19.680: DSL 0/2 framer intr_status 0xC0*Mar 12 08:01:19.680: DSL 0/2 controller Link up! line rate: 2304 KbpsThe following lines show that the digital subscriber line (DSL) controller has come up on slot 0 and port 2:
*Mar 12 08:01:19.680: %CONTROLLER-5-UPDOWN: Controller DSL 0/2, changed state to up*Mar 12 08:01:19.680: Dslsar data rate 2304*Mar 12 08:01:22.528: %LINK-3-UPDOWN: Interface ATM0/2, changed state to up*Mar 12 08:01:23.528: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/2, changed state to upThe following lines show that the framer interrupt status is running:
*Mar 12 08:01:23.812: DSL 0/2 framer intr_status 0xC4*Mar 12 08:01:23.816: DSL 0/2 framer intr_status 0xC4*Mar 12 08:01:23.904: DSL 0/2 framer intr_status 0xC1*Mar 12 08:01:28.612: DSL 0/2 framer intr_status 0xC4*Mar 12 08:01:28.616: DSL 0/2 framer intr_status 0xC4*Mar 12 08:01:28.708: DSL 0/2 framer intr_status 0xC1*Mar 12 08:01:28.804: DSL 0/2 framer intr_status 0xC1*Mar 12 08:01:33.412: DSL 0/2 framer intr_status 0xC4*Mar 12 08:01:33.420: DSL 0/2 framer intr_status 0xC4*Mar 12 08:01:33.508: DSL 0/2 framer intr_status 0xC1*Mar 12 08:01:33.604: DSL 0/2 framer intr_status 0xC1*Mar 12 08:01:33.700: DSL 0/2 framer intr_status 0xC1*Mar 12 08:01:38.212: DSL 0/2 framer intr_status 0xC4*Mar 12 08:01:38.220: DSL 0/2 framer intr_status 0xC4*Mar 12 08:01:38.308: DSL 0/2 framer intr_status 0xC1Related Commands
debug xdsl eoc
To display the flow of the embedded operations channel (EOC) messages received, processed, and transmitted, use the debug xdsl eoc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug xdsl eoc
no debug xdsl eoc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug xdsl eoc command:
Router# debug xdsl eocxDSL EOC debugging is onRouter#The following lines show the embedded operations channel message being received and copied to the buffer. The xdsl_background_process is performed. The data_transparency_remove is performed.
00:02:55: Incoming EOC received00:02:55: Copy the EOC to buffer00:02:55: Incoming EOC received00:02:55: Copy the EOC to buffer00:02:55: End of EOC received, Notify task00:02:55: xdsl_background_process:00:02:55: Rx EOC remove transparency:: 12 C A 6300:02:55: data_transparency_remove: Done, eoc packet size = 4The following lines show that the packet of the embedded operations channel messages was received and verified as good. The data_transparency_add is performed.
00:02:55: Good eoc packet received00:02:55: incoming request eocmsgid: 1200:02:55: Tx Converted EOC message:: 21 8C 0 28 0 0 0 0 0 0 0 1 1 71300:02:55: data_transparency_add: eoc packet size - before 15, after 15The following lines show another embedded operations channel message coming in and copied to the buffer. The xdsl_background_process is run on this message as before.
00:02:55: size of eoc status response :: 1300:02:56: Incoming EOC received00:02:56: Copy the EOC to buffer00:02:56: Incoming EOC received00:02:56: Copy the EOC to buffer00:02:56: End of EOC received, Notify task00:02:56: xdsl_background_process:00:02:56: Rx EOC remove transparency:: 12 C A 6300:02:56: data_transparency_remove: Done, eoc packet size = 4Related Commands
debug xdsl error
To display the errors of xDSL process and firmware, use the debug xdsl error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug xdsl error
no debug xdsl error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug xdsl error command to display the errors during driver initialization and any Globespan firmware API failures.
Examples
The following is sample output from the debug xdsl error command. When the debug is enabled, a message indicates that DSL error debugging is on.
Router# debug xdsl errorxDSL error debugging is onRouter#Related Commands
voice call debug
To debug a voice call, use the voice call debug command in global configuration mode. To display a full globally unique identifier (GUID) or header as explained in the "Usage Guidelines" section, use the no form of this command.
voice call debug full-guid | short-header
no voice call debug full-guid | short-header
Syntax Description
Defaults
The short 6-byte header is displayed.
Command Modes
Global configuration
Command History
Usage Guidelines
The user can control the contents of the standardized header. The display options for the header are as follows:
•
•
•
The format of the GUID headers is as follows:
//CallEntryID/GUID/Module-Dependent-List/Function-name:.The format of the short header is as follows:
//CallEntryID/Function-name:.When the voice call debug short-header command is entered, the header is displayed with no GUID or module-specific parameters. When the no voice call debug short-header command is entered, the header, the 6-byte GUID, and module-dependent parameter output are displayed. The default option is to display the 6-byte GUID trace.
Note
Examples
The following is sample output from the voice call debug command when the full-guid keyword is specified:
Router# voice call debug full-guid!00:05:12: //1/0E2C8A90-BC00-11D5-8002-DACCFDCEF87D/VTSP:(0:D):0:0:4385/vtsp_insert_cdb: 00:05:12: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: 00:05:12: //1/0E2C8A90-BC00-11D5-8002-DACCFDCEF87D/VTSP:(0:D):0:0:4385/vtsp_open_voice_and _set_params:00:05:12: //1/0E2C8A90-BC00-11D5-8002-DACCFDCEF87D/VTSP:(0:D):0:0:4385/vtsp_modem_proto_fr om_cdb:00:05:12: //1/0E2C8A90-BC00-11D5-8002-DACCFDCEF87D/VTSP:(0:D):0:0:4385/set_playout_cdb: 00:05:12: //1/0E2C8A90-BC00-11D5-8002-DACCFDCEF87D/VTSP:(0:D):0:0:4385/vtsp_dsp_echo_cance ller_control:The "//-1/" output indicates that CallEntryID for the call control API (CCAPI) module is not available.
Table 342 describes the significant fields shown in the display.
The following is sample output from the voice call debug command when the short-header keyword is specified:
Router(config)# voice call debug short-header!00:05:12: //1/vtsp_insert_cdb:00:05:12: //-1/cc_incr_if_call_volume:00:05:12: //1/vtsp_open_voice_and_set_params:00:05:12: //1/vtsp_modem_proto_from_cdb:00:05:12: //1/set_playout_cdb:00:05:12: //1/vtsp_dsp_echo_canceller_control:The output "//-1/" indicates that CallEntryID for CCAPI is not available.
Related Commands
