Cisco IOS Debug Command Reference, Release 12.3 - Debug Commands: debug packet through debug redundancy [Cisco IOS Software Releases 12.3 Mainline]

Table Of Contents

debug packet

debug pad

debug piafs events

debug pots

debug pots csm

debug ppp

debug pppatm

debug ppp bap

debug ppp multilink events

debug ppp multilink fragments

debug pppoe

debug priority

debug proxy h323 statistics

debug pvcd

debug qllc error

debug qllc event

debug qllc packet

debug qllc state

debug qllc timer

debug qllc x25

debug radius

debug ras

debug redundancy

debug packet

To display per-packet debugging output, use the debug packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug packet [interface number [vcd vcd-number] | vc vpi/vci | vc-name]
no debug packet [interface number [vcd vcd-number] | vc vpi/vci | vc-name]
Syntax Description

interface number

(Optional) interface or subinterface number.

vcd vcd-number

(Optional) Number of the virtual circuit designator (VCD).

vc vpi/vci

(Optional) Virtual path identifier (VPI) and virtual channel identifier (VCI) numbers of the VC.

vc-name

(Optional) Name of the PVC or SVC.

Defaults

Debugging for packets is disabled by default.

Command Modes

Privileged EXEC

Command History

Release

Modification

9.21

This command was introduced.

12.2(13)T

Support for Apollo Domain and Banyan VINES was removed.

Usage Guidelines

The debug packet command displays all process-level packets for both outbound and inbound packets. This command is useful for determining whether packets are being received and sent correctly. The output reports information online when a packet is received or a transmission is attempted.

For sent packets, the information is displayed only after the protocol data unit (PDU) is entirely encapsulated and a next hop VC is found. If information is not displayed, the address translation probably failed during encapsulation. When a next hop VC is found, the packet is displayed exactly as it will be presented on the wire. Having a display indicates that the packets are properly encapsulated for transmission.

For received packets, information is displayed for all incoming frames. The display can show whether the sending station properly encapsulates the frames. Because all incoming frames are displayed, this information is useful when performing back-to-back testing and corrupted frames cannot be dropped by an intermediary switch.

The debug packet command also displays the initial bytes of the actual PDU in hexadecimal. This information can be decoded only by qualified support or engineering personnel.

Caution Because the debug packet command generates a substantial amount of output for every packet processed, use it only when traffic on the network is low so other activity on the system is not adversely affected.

Examples

The following is sample output from the debug packet command:
Router# debug packet
2/0.5(I): VCD:0x9 VCI:0x23 Type:0x0 SAP:AAAA CTL:03 OUI:000000 TYPE:0800 Length0x70
4500 002E 0000 0000 0209 92ED 836C A26E FFFF FFFF 1108 006D 0001 0000 0000
A5CC 6CA2 0000 000A 0000 6411 76FF 0100 6C08 00FF FFFF 0003 E805 DCFF 0105
Table 191 describes the significant fields shown in the display.

Table 191 debug packet Field Descriptions

Field

Description

2/0.5

Indicates the subinterface that generated this packet.

(I)

Indicates a receive packet. (O) indicates an output packet.

VCD: 0xn

Indicates the virtual circuit associated with this packet, where n is some value.

DM: 0xnnnn

Indicates the descriptor mode bits on output only, where nnnn is a hexadecimal value.

TYPE:n

Displays the encapsulation type for this packet.

Length:n

Displays the total length of the packet including the headers.

The following two lines of output are the binary data, which are the contents of the protocol data unit (PDU) before encapsulation:
4500 002E 0000 0000 0209 92ED 836C A26E FFFF FFFF 1108 006D 0001 0000 0000
A5CC 6CA2 0000 000A 0000 6411 76FF 0100 6C08 00FF FFFF 0003 E805 DCFF 0105
The following is sample output from the debug packet command:
Router# debug packet
Ethernet0: Unknown ARPA, src 0000.0c00.6fa4, dst ffff.ffff.ffff, type 0x0a0
data 00000c00f23a00000c00ab45, len 60
Serial3: Unknown HDLC, size 64, type 0xaaaa, flags 0x0F00
Serial2: Unknown PPP, size 128
Serial7: Unknown FRAME-RELAY, size 174, type 0x5865, DLCI 7a
Serial0: compressed TCP/IP packet dropped
Table 192 describes the significant fields shown in the display.

Table 192 debug packet Field Descriptions

Field

Description

Ethernet0

Name of the Ethernet interface that received the packet.

Unknown

Network could not classify this packet. Examples include packets with unknown link types.

ARPA

Packet uses ARPA-style encapsulation. Possible encapsulation styles vary depending on the media command mode (MCM) and encapsulation style.

Ethernet (MCM)—Encapsulation Style:

•ARP

•ETHERTALK

•ISO1

•ISO3

•LLC2

•NOVELL-ETHER

•SNAP

FDDI (MCM)—Encapsulation Style:

•ISO1

•ISO3

•LLC2

•SNAP

Frame Relay—Encapsulation Style:

•BRIDGE

•FRAME-RELAY

ARPA
(continued)

Serial (MCM)—Encapsulation Style:

•BFEX25

•BRIDGE

•DDN-X25

•DDNX25-DCE

•ETHERTALK

•FRAME-RELAY

•HDLC

•HDH

•LAPB

•LAPBDCE

•MULTI-LAPB

•PPP

•SDLC-PRIMARY

•SDLC-SECONDARY

•SLIP

•SMDS

•STUN

•X25

•X25-DCE

Token Ring (MCM)—Encapsulation Style:

•3COM-TR

•ISO1

•ISO3

•MAC

•LLC2

•NOVELL-TR

•SNAP

•VINES-TR

src 0000.0c00.6fa4

MAC address of the node generating the packet.

dst.ffff.ffff.ffff

MAC address of the destination node for the packet.

type 0x0a0

Packet type.

data...

First 12 bytes of the datagram following the MAC header.

len 60

Length of the message (in bytes) that the interface received from the wire.

size 64

Length of the message (in bytes) that the interface received from the wire. Equivalent to the len field.

flags 0x0F00

HDLC or PP flags field.

DLCI 7a

The DLCI number on Frame Relay.

compressed TCP/IP packet dropped

TCP header compression is enabled on an interface and the packet is not HDLC or X25.

debug pad

To display debugging messages for all packet assembler/disassembler (PAD) connections, use the debug pad command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug pad
no debug pad
Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0

This command was introduced in a release prior to Cisco IOS Release 12.0.

Examples

Use the debug pad command to gather information to forward to the Cisco Technical Assistance Center (TAC) to assist in troubleshooting a problem that involves PAD connections.

The following example shows output of the debug pad and debug x25 event commands for an incoming PAD call destined for a terminal line. The incoming PAD call is rejected by the terminal line because the selected network closed user group (CUG) has not been subscribed to by the caller:
Router# debug pad
Router# debug x25 event
Serial1/1:X.25 I R1 Call (16) 8 lci 8
  From (7):2001534 To (9):200261150
  Facilities:(2)
    Closed User Group (basic):99
  Call User Data (4):0x01000000 (pad)
pad_svc_announce:destination matched 1
PAD:incoming call to 200261150 on line 130 CUD length 4
!PAD130:Incoming Call packet, Closed User Group (CUG) service protection, selected network 
CUG not subscribed
PAD:CUG service protection Cause:11 Diag:65
Serial1/1:X.25 O R1 Clear (5) 8 lci 8
  Cause 0, Diag 65 (DTE originated/Facility code not allowed)
Serial1/1:X.25 I R1 Clear Confirm (3) 8 lci 8
The following example shows the output of the debug pad command for an outgoing PAD call initiated from a terminal line with a subscribed CUG that bars outgoing access:
!PAD130:Outgoing Call packet, Closed User Group - CUG service validation, selected CUG 
!bars outgoing access
PAD130:Closing connection to .  In 0/0, out 0/0
debug piafs events

To check the debugging messages for Personal Handyphone Internet Access Forum Standard (PIAFS) calls, use the debug piafs events command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug piafs events
no debug piafs events
Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(8)T

This command was introduced on Cisco 803, Cisco 804, and Cisco 813 routers.

Usage Guidelines

The debug piafs events command provides debugging information for the PIAFS calls on the router, including the inband negotiation process.

Examples

The debug piafs events command was configured to provide the following information for PIAFS calls:
Router# debug piafs events
02:16:39:PIAFS events debugging is on
02:16:167516180371:PIAFS: RX <- CDAPI :cdapi_route_call Request
02:16:167517398148:PIAFS: RX <- CDAPI :CDAPI_MSG_CONNECT_IND
02:16:171798691839:PIAFS: TX -> CDAPI :CDAPI_MSG_SUBTYPE_ALERT_REQ
02:16:167503724545:PIAFS: TX -> CDAPI :CDAPI_MSG_CONNECT_RESP
02:16:167503765504:PIAFS: TX -> CDAPI :CDAPI_MSG_CONN_ACTIVE_REQ
02:16:167503724544:PIAFS: RX <- CDAPI :CDAPI_MSG_CONN_ACTIVE_IND
02:16:171798691839:PIAFS:Network allotted Channel :B1
02:16:167503765504:PIAFS:Enabling QMC in PIAFS mode for B1
02:16:171798691839:PIAFS:piafs_driver_enable_settings()
02:16:167503765504:PIAFS:The speed is :64
02:16:167503724544:PIAFS:Starting 64 kbps PIAFS Incoming
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:13 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:Updating conf resp num
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:1 RSN:1 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:14 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:2 RSN:2 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:15 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:3 RSN:3 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:16 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:4 RSN:4 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:17 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:5 RSN:5 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:18 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:6 RSN:6 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:19 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:7 RSN:7 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:Piafs layer up & Main FSM set to DATA
02:16:39:PIAFS:Compression v42bis enabled
02:16:39:PIAFS:V42BIS:v42bis_init()
02:16:39:PIAFS:V42BIS:v42bis_init()
02:16:39:PIAFS:V42BIS:Negotiated Values for P1, P2 are - 4096 , 250
02:16:39:PIAFS:Incoming call invoking ISDN_CALL_CONNECT
02:16:39:%LINK-3-UPDOWN:Interface BRI0:1, changed state to up
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:piafs_setmap() tx_map FFFFFFFF
02:16:39:PIAFS:piafs_setmap() rx_map 0
02:16:41:PIAFS:PPP:Autoselect sample 7E
02:16:41:PIAFS:PPP:Autoselect sample 7EFF
02:16:41:PIAFS:PPP:Autoselect sample 7EFF7D
02:16:41:PIAFS:PPP:Autoselect sample 7EFF7D23
02:16:41:PIAFS:piafs_setmap() tx_map FFFFFFFF
02:16:41:PIAFS:piafs_setmap() rx_map 0
02:16:42:PIAFS:piafs_setmap() tx_map A0000
02:16:42:PIAFS:piafs_setmap() rx_map 0
Table 193 describes the significant fields shown in the display.

Table 193 debug piafs events Field Descriptions

Field

Description

RX <- CDAPI :cdapi_route_call Request

The call distributor application programming interface (CDAPI) in the router receives an ISDN call request from the switch.

RX <- CDAPI :CDAPI_MSG_CONNECT_IND

The CDAPI in the router receives a connection indicator message from the switch.

TX -> CDAPI :CDAPI_MSG_SUBTYPE_ALERT_REQ

The CDAPI in the router transmits an alert request to the switch.

TX -> CDAPI :CDAPI_MSG_CONNECT_RESP

The CDAPI in the router transmits a connect response message to the switch.

TX -> CDAPI :CDAPI_MSG_CONN_ACTIVE_REQ

The CDAPI in the router transmits a connection active request to the switch.

RX <-CDAPI:CDAPI_MSG_CONN_ACTIVE_IND

The CDAPI in the router receives a connection active indicator from the switch.

Enabling QMC in PIAFS mode for B1

QMC (global multichannel parameters) are being enabled in PIAFS mode for the B1 channel.

piafs_driver_enable_settings()

The PIAFS driver is enabling the settings.

Starting 64 kbps PIAFS Incoming

The speed of the transmission in kbps. In this case, the speed is 64 kbps.

RX <- NEGO_SYNC_REQUEST[GSN: RSN: CRSN: SISN:]

The router receives a PIAFS negotiation synchronization request frame from the peer PIAFS device. The frame contains the following: general sequence number (GSN), reception sequence number (RSN), confirmation response sequence number (CRSN), and synchronization initiation sequence number (SISN).

Updating conf resp num

The confirmation response number is being updated.

TX -> NEGO_SYNC_RECEPTION[GSN: RSN: CRSN: SISN: ]

The router transmits a PIAFS negotiation synchronization reception message to the peer PIAFS device. The message includes the GSN, RSN, CRSN, and SISN.

RX <- CONTROL_REQUEST

The router receives a PIAFS control request frame that includes communication parameters.

Rx Parameters

The communication parameters are as follows.

  Data Protocol

The version of the data protocol.

  Control Protocol

The version of the control protocol.

  RTF value

Round-trip frame value.

  Compression

The compression standard.

  Frame Length

The length of the frame, in bytes.

  Frame Number

The number of packets per frame.

TX -> CONTROL_RECEPTION

The router transmits a PIAFS control reception frame.

ACKed all the Rx control parameters

The control reception frame acknowledges all the communication parameters that were received from the peer.

Piafs layer up & Main FSM set to DATA

The PIAFS protocol is active on the router. The router is ready to receive data from the peer device.

Compression v42bis enabled

The compression protocol v42bis is enabled.

V42BIS:v42bis_init()

The v42bis compression protocol has been initiated.

V42BIS:Negotiated Values for P1, P2 are - 4096 , 250

In this example, P1 is the total count of encoded words when v42bis compression is enabled. P2 is the maximum letter line length for the V42bis compression.

Incoming call invoking ISDN_CALL_CONNECT

An incoming ISDN call connection message is received.

PPP

The PPP layer on the router becomes active and starts to process the PPP frame from the peer PIAFS device.

debug pots

To display information on the telephone interfaces, use the debug pots command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug pots {driver | csm} [1 | 2]
no debug pots {driver | csm} [1 | 2]
Syntax Description

driver

Displays driver debug information.

csm

Displays Content Switching Module (CSM) debug information.

1

(Optional) Displays information for telephone port 1 only.

2

(Optional) Displays information for telephone port 2 only.

Command Modes

Privileged EXEC

Usage Guidelines

The debug pots command displays driver and CSM debug information for telephone ports 1 and 2.

Examples

The following is a sample display from the debug pots driver 1 command. This sample display indicates that the telephone port driver is not receiving caller ID information from the ISDN line. Therefore, the analog caller ID device attached to the telephone port does not display caller ID information.
Router# debug pots driver 1
00:01:51:POTS DRIVER port=1 activate ringer: cadence=0 callerId=Unknown
00:01:51:POTS DRIVER port=1 state=Idle drv_event=RING_EVENT
00:01:51:POTS DRIVER port=1 enter_ringing
00:01:51:POTS DRIVER port=1 cmd=19
00:01:51:POTS DRIVER port=1 activate disconnect
00:01:51:POTS DRIVER port=1 state=Ringing drv_event=DISCONNECT_EVENT
00:01:51:POTS DRIVER port=1 cmd=1A
00:01:51:POTS DRIVER port=1 enter_idle
00:01:51:POTS DRIVER port=1 ts connect: 0 0
00:01:51:POTS DRIVER port=1 cmd=D
00:01:51:POTS DRIVER port=1 report onhook
00:01:51:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:01:51:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
00:01:51:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:01:51:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
00:01:53:POTS DRIVER port=1 activate ringer: cadence=0 callerId=Unknown
00:01:53:POTS DRIVER port=1 state=Idle drv_event=RING_EVENT
00:01:53:POTS DRIVER port=1 enter_ringing
00:01:53:POTS DRIVER port=1 cmd=19
00:01:55:POTS DRIVER port=1 cmd=1A
00:02:49:POTS DRIVER port=1 state=Ringing drv_event=OFFHOOK_EVENT
00:02:49:POTS DRIVER port=1 cmd=1A
00:02:49:POTS DRIVER port=1 enter_suspend
00:02:49:POTS DRIVER port=1 cmd=A
00:02:49:POTS DRIVER port=1 report offhook
00:02:49:POTS DRIVER port=1 activate connect: endpt=1 calltype=TWO_PARTY_CALL
00:02:49:POTS DRIVER port=1 state=Suspend drv_event=CONNECT_EVENT
00:02:49:POTS DRIVER port=1 enter_connect: endpt=1 calltype=0
00:02:49:POTS DRIVER port=1 cmd=A
00:02:49:POTS DRIVER port=1 ts connect: 1 0
00:02:49:POTS DRIVER port=1 activate connect: endpt=1 calltype=TWO_PARTY_CALL
00:02:49:POTS DRIVER port=1 state=Connect drv_event=CONNECT_EVENT
00:02:49:POTS DRIVER port=1 enter_connect: endpt=1 calltype=0
00:02:49:POTS DRIVER port=1 cmd=A
00:02:49:POTS DRIVER port=1 ts connect: 1 0
00:02:55:POTS DRIVER port=1 state=Connect drv_event=ONHOOK_EVENT
00:02:55:POTS DRIVER port=1 enter_idle
00:02:55:POTS DRIVER port=1 ts connect: 0 0
00:02:55:POTS DRIVER port=1 cmd=D
00:02:55:POTS DRIVER port=1 report onhook
00:02:55:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:02:55:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
00:02:55:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:02:55:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
The following is sample display from the debug pots csm 1 command. This sample display indicates that a dial peer contains an invalid destination pattern (555-1111).
Router# debug pots csm 1
01:57:28:EVENT_FROM_ISDN:dchanidb=0x66CB38, call_id=0x11, ces=0x2 bchan=0x0, event=0x1, 
cause=0x0
01:57:28:Dial peer not found, route call to port 1
01:57:28:CSM_PROC_IDLE:CSM_EVENT_ISDN_CALL, call_id=0x11, port=1
01:57:28:Calling number `5551111'
01:57:40:CSM_PROC_RINGING:CSM_EVENT_VDEV_OFFHOOK, call_id=0x11, port=1
01:57:40:EVENT_FROM_ISDN:dchan_idb=0x66CB38, call_id=0x11, ces=0x2 bchan=0x0, event=0x4, 
cause=0x0
01:57:40:CSM_PROC_CONNECTING:CSM_EVENT_ISDN_CONNECTED, call_id=0x11, port=1
01:57:47:CSM_PROC_CONNECTING:CSM_EVENT_VDEV_ONHOOK, call_id=0x11, port=1
01:57:201863503872: %ISDN-6-DISCONNECT:Interface BRI0:1 disconnected from unknown, call 
lasted 5485 seconds
01:57:47: %ISDN-6-DISCONNECT:Interface BRI0:1 disconnected from unknown, call lasted 5485 
seconds
01:57:47:EVENT_FROM_ISDN:dchan _idb=0x66CB38, call_id=0x11, ces=0x2 bchan=0xFFFFFFFF, 
event=0x0, cause=0x1
01:57:47:CSM_PROC_NEAR_END_DISCONNECT:CSM_
debug pots csm

To activate events from which an application can determine and display the status and progress of calls to and from Plain Old Telephone Service (POTS) ports, use the debug pots csm command in privileged EXEC mode.

debug pots csm
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1.(2)XF

This command was introduced on the Cisco 800 series routers.

Examples

To see debugging messages, enter the logging console global configuration mode command as follows:
Router(config)# logging console 
Router(config)# exit
Debugging messages are displayed in one of two formats that are relevant to the POTS dial feature:
hh:mm:ss: CSM_STATE: CSM_EVENT, call id = ??, port = ?
or
hh:mm:ss: EVENT_FROM_ISDN:dchan_idb=0x???????, call_id=0x????, ces=? bchan=0x????????, 
event=0x?, cause=0x??
Table 194 describes the significant fields shown in the display.

Table 194 debug pots csm Field Descriptions

Command Elements

Description

hh:mm:ss

Timestamp (in hours, minutes, and seconds).

CSM_STATE

One of the call CSM states listed in Table 195.

CSM_EVENT

One of the CSM events listed in Table 196.

call id

Hexadecimal value from 0x00 to 0xFF.

port

Telephone port 1 or 2.

EVENT_FROM_ISDN

A CSM event. Table 196 shows a list of CSM events.

dchan_idb

Internal data structure address.

ces

Connection end point suffix used by ISDN.

bchan

Channel used by the call. A value of 0xFFFFFFFF indicates that a channel is not assigned.

event

A hexadecimal value that is translated into a CSM event. Table 197 shows a list of events and the corresponding CSM events.

cause

A hexadecimal value that is given to call-progressing events. Table 198 shows a list of cause values and definitions.

Table 195 shows the values for CSM states.

Table 195 CSM States

CSM State

Description

CSM_IDLE_STATE

Telephone on the hook.

CSM_RINGING

Telephone ringing.

CSM_SETUP

Setup for outgoing call in progress.

CSM_DIALING

Dialing number of outgoing call.

CSM_IVR_DIALING

Interactive voice response (IVR) for Japanese telephone dialing.

CSM_CONNECTING

Waiting for carrier to connect the call.

CSM_CONNECTED

Call connected.

CSM_DISCONNECTING

Waiting for carrier to disconnect the call.

CSM_NEAR_END_DISCONNECTING

Waiting for carrier to disconnect the call.

CSM_HARD_HOLD

Call on hard hold.

CSM_CONSULTATION_HOLD

Call on consultation hold.

CSM_WAIT_FOR_HOLD

Waiting for carrier to put call on hard hold.

CSM_WAIT_FOR_CONSULTATION_HOLD

Waiting for carrier to put call on consultation hold.

CSM_CONFERENCE

Waiting for carrier to complete call conference.

CSM_TRANSFER

Waiting for carrier to transfer call.

CSM_APPLIC_DIALING

Call initiated from Cisco IOS command-line interface (CLI).

Table 196 shows the values for CSM events.

Table 196 CSM Events

CSM Events

Description

CSM_EVENT_INTER_DIGIT_TIMEOUT

Time waiting for dial digits has expired.

CSM_EVENT_TIMEOUT

Near- or far-end disconnect timeout.

CSM_EVENT_ISDN_CALL

Incoming call.

CSM_EVENT_ISDN_CONNECTED

Call connected.

CSM_EVENT_ISDN_DISCONNECT

Far end disconnected.

CSM_EVENT_ISDN_DISCONNECTED

Call disconnected.

CSM_EVENT_ISDN_SETUP

Outgoing call requested.

CSM_EVENT_ISDN_SETUP_ACK

Outgoing call accepted.

CSM_EVENT_ISDN_PROC

Call proceeding and dialing completed.

CSM_EVENT_ISDN_CALL_PROGRESSING

Call being received in band tone.

CSM_EVENT_ISDN_HARD_HOLD

Call on hard hold.

CSM_EVENT_ISDN_HARD_HOLD_REJ

Hold attempt rejected.

CSM_EVENT_ISDN_CHOLD

Call on consultation hold.

CSM_EVENT_ISDN_CHOLD_REJ

Consultation hold attempt rejected.

CSM_EVENT_ISDN_RETRIEVED

Call retrieved.

CSM_EVENT_ISDN_RETRIEVE_REJ

Call retrieval attempt rejected.

CSM_EVENT_ISDN_TRANSFERRED

Call transferred.

CSM_EVENT_ISDN_TRANSFER_REJ

Call transfer attempt rejected.

CSM_EVENT_ISDN_CONFERENCE

Call conference started.

CSM_EVENT_ISDN_CONFERENCE_REJ

Call conference attempt rejected.

CSM_EVENT_ISDN_IF_DOWN

ISDN interface down.

CSM_EVENT_ISDN_INFORMATION

ISDN information element received (used by NTT IVR application).

CSM_EVENT_VDEV_OFFHOOK

Telephone off the hook.

CSM_EVENT_VDEV_ONHOOK

Telephone on the hook.

CSM_EVENT_VDEV_FLASHHOOK

Telephone hook switch has flashed.

CSM_EVENT_VDEV_DIGIT

DTMF digit has been detected.

CSM_EVENT_VDEV_APPLICATION_CALL

Call initiated from Cisco IOS CLI.

Table 197 shows the values for events that are translated into CSM events.

Table 197 Event Values

Hexadecimal Value

Event

CSM Event

0x0

DEV_IDLE

CSM_EVENT_ISDN_DISCONNECTED

0x1

DEV_INCALL

CSM_EVENT_ISDN_CALL

0x2

DEV_SETUP_ACK

CSM_EVENT_ISDN_SETUP_ACK

0x3

DEV_CALL_PROC

CSM_EVENT_ISDN_PROC

0x4

DEV_CONNECTED

CSM_EVENT_ISDN_CONNECTED

0x5

DEV_CALL_PROGRESSING

CSM_EVENT_ISDN_CALL_PROGRESSING

0x6

DEV_HOLD_ACK

CSM_EVENT_ISDN_HARD_HOLD

0x7

DEV_HOLD_REJECT

CSM_EVENT_ISDN_HARD_HOLD_REJ

0x8

DEV_CHOLD_ACK

CSM_EVENT_ISDN_CHOLD

0x9

DEV_CHOLD_REJECT

CSM_EVENT_ISDN_CHOLD_REJ

0xa

DEV_RETRIEVE_ACK

CSM_EVENT_ISDN_RETRIEVED

0xb

DEV_RETRIEVE_REJECT

CSM_EVENT_ISDN_RETRIEVE_REJ

0xc

DEV_CONFR_ACK

CSM_EVENT_ISDN_CONFERENCE

0xd

DEV_CONFR_REJECT

CSM_EVENT_ISDN_CONFERENCE_REJ

0xe

DEV_TRANS_ACK

CSM_EVENT_ISDN_TRANSFERRED

0xf

DEV_TRANS_REJECT

CSM_EVENT_ISDN_TRANSFER_REJ

Table 198 shows cause values that are assigned only to call-progressing events.

Table 198 Cause Values

Hexadecimal Value

Cause Definitions

0x01

UNASSIGNED_NUMBER

0x02

NO_ROUTE

0x03

NO_ROUTE_DEST

0x04

NO_PREFIX

0x06

CHANNEL_UNACCEPTABLE

0x07

CALL_AWARDED

0x08

CALL_PROC_OR_ERROR

0x09

PREFIX_DIALED_ERROR

0x0a

PREFIX_NOT_DIALED

0x0b

EXCESSIVE_DIGITS

0x0d

SERVICE_DENIED

0x10

NORMAL_CLEARING

0x11

USER_BUSY

0x12

NO_USER_RESPONDING

0x13

NO_USER_ANSWER

0x15

CALL_REJECTED

0x16

NUMBER_CHANGED

0x1a

NON_SELECTED_CLEARING

0x1b

DEST_OUT_OF_ORDER

0x1c

INVALID_NUMBER_FORMAT

0x1d

FACILITY_REJECTED

0x1e

RESP_TO_STAT_ENQ

0x1f

UNSPECIFIED_CAUSE

0x22

NO_CIRCUIT_AVAILABLE

0x26

NETWORK_OUT_OF_ORDER

0x29

TEMPORARY_FAILURE

0x2a

NETWORK_CONGESTION

0x2b

ACCESS_INFO_DISCARDED

0x2c

REQ_CHANNEL_NOT_AVAIL

0x2d

PRE_EMPTED

0x2f

RESOURCES_UNAVAILABLE

0x32

FACILITY_NOT_SUBSCRIBED

0x33

BEARER_CAP_INCOMPAT

0x34

OUTGOING_CALL_BARRED

0x36

INCOMING_CALL_BARRED

0x39

BEARER_CAP_NOT_AUTH

0x3a

BEAR_CAP_NOT_AVAIL

0x3b

CALL_RESTRICTION

0x3c

REJECTED_TERMINAL

0x3e

SERVICE_NOT_ALLOWED

0x3f

SERVICE_NOT_AVAIL

0x41

CAP_NOT_IMPLEMENTED

0x42

CHAN_NOT_IMPLEMENTED

0x45

FACILITY_NOT_IMPLEMENT

0x46

BEARER_CAP_RESTRICTED

0x4f

SERV_OPT_NOT_IMPLEMENT

0x51

INVALID_CALL_REF

0x52

CHAN_DOES_NOT_EXIST

0x53

SUSPENDED_CALL_EXISTS

0x54

NO_CALL_SUSPENDED

0x55

CALL_ID_IN_USE

0x56

CALL_ID_CLEARED

0x58

INCOMPATIBLE_DEST

0x5a

SEGMENTATION_ERROR

0x5b

INVALID_TRANSIT_NETWORK

0x5c

CS_PARAMETER_NOT_VALID

0x5f

INVALID_MSG_UNSPEC

0x60

MANDATORY_IE_MISSING

0x61

NONEXISTENT_MSG

0x62

WRONG_MESSAGE

0x63

BAD_INFO_ELEM

0x64

INVALID_ELEM_CONTENTS

0x65

WRONG_MSG_FOR_STATE

0x66

TIMER_EXPIRY

0x67

MANDATORY_IE_LEN_ERR

0x6f

PROTOCOL_ERROR

0x7f

INTERWORKING_UNSPEC

Examples

This section provides debug output examples for three call scenarios, displaying the sequence of events that occur during a POTS dial call or POTS disconnect call.

Call Scenario 1

In this example call scenario, port 1 is on the hook, the application dial is set to call 4085552221, and the far-end successfully connects.
Router# debug pots csm
Router# test pots 1 dial 4085552221#
Router#
The following output shows an event indicating that port 1 is being used by the dial application:
01:58:27: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1
The following output shows events indicating that the CSM is receiving the application digits of the number to dial:
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
The following output shows that the telephone connected to port 1 is off the hook:
01:58:39: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1
The following output shows a call-proceeding event pair indicating that the router ISDN software has sent the dialed digits to the ISDN switch:
01:58:40: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0x0, 
event=0x3, cause=0x0 
01:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 
0x8004, port = 1
The following output shows the call-progressing event pair indicating that the telephone at the far end is ringing:
01:58:40: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, 
event=0x5, cause=0x0
01:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8004, port 
= 1
The following output shows a call-connecting event pair indicating that the telephone at the far end has answered:
01:58:48: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, 
event=0x4, cause=0x0
01:58:48: CSM_PROC_CONNECTING: CSM_EVENT_ISDN_CONNECTED, call id = 0x8004, port = 1
The following output shows a call-progressing event pair indicating that the telephone at the far end has hung up and that the calling telephone is receiving an in-band tone from the ISDN switch:
01:58:55: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, 
event=0x5, cause=0x10
01:58:55: CSM_PROC_CONNECTED: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8004, port = 1
The following output shows that the telephone connected to port 1 has hung up:
01:58:57: CSM_PROC_CONNECTED: CSM_EVENT_VDEV_ONHOOK, call id = 0x8004, port = 1
The following output shows an event pair indicating that the call has been terminated:
01:58:57: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, 
event=0x0, cause=0x0
01:58:57: CSM_PROC_NEAR_END_DISCONNECT: CSM_EVENT_ISDN_DISCONNECTED, call id =