Cisco IOS Debug Command Reference, Release 12.3 T - Debug Commands: debug cch323 through debug channel packets [Cisco IOS Software Releases 12.3 T]

Table Of Contents

debug cch323

debug cch323 capacity

debug cch323 h225

debug cch323 h245

debug cch323 preauth

debug cch323 ras

debug ccm-manager

debug ccsip all

debug ccsip calls

debug ccsip error

debug ccsip events

debug ccsip info

debug ccsip media

debug ccsip messages

debug ccsip preauth

debug ccsip states

debug ccsip transport

debug ccswvoice vo-debug

debug ccswvoice vofr-debug

debug ccswvoice vofr-session

debug ccswvoice vo-session

debug cdapi

debug cdma pdsn a10 ahdlc

debug cdma pdsn a10 gre

debug cdma pdsn a10 ppp

debug cdma pdsn a11

debug cdma pdsn accounting

debug cdma pdsn accounting flow

debug cdma pdsn accounting time-of-day

debug cdma pdsn cluster

debug cdma pdsn prepaid

debug cdma pdsn resource-manager

debug cdma pdsn selection

debug cdma pdsn service-selection

debug cdma pdsn session

debug cdp

debug cdp ip

debug ces-conn

debug channel events

debug channel ilan

debug channel love

debug channel packets

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

all

Enables all debug cch323 commands.

error

Traces errors encountered in the H.323 subsystem and can be used to help troubleshoot problems with H.323 calls.

h225

Traces the state transition of the H.225 state machine on the basis of the processed event.

h245

Traces the state transition of the H.245 state machine on the basis of the processed events.

nxe

Displays Annex E events that have been transmitted and received.

ras

Traces the state transition of the Registration, Admission, and Status (RAS) state machine on the basis of the processed events.

rawmsg

Troubleshoots raw message buffer problems.

session

Traces general H.323 events and can be used to troubleshoot H.323 problems.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2

The debug cch323 command and the following keywords were introduced: h225, h245, and ras.

12.2(2)XA

The nxe keyword was added.

12.2(4)T

The following keywords were introduced: all, error, rawmsg, and session. The nxe keyword was integrated into Cisco IOS Release 12.2(4)T on all Cisco H.323 platforms. This command does not support the Cisco access server platforms in this release.

12.2(2)XB1

This command was implemented on the Cisco AS5850.

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:

error

Enables a CCH323 Service Provider Interface (SPI) trace.

h225

Enables an H225 state machine debugging trace.

h245

Enables an H245 state machine debugging trace.

nxe

Enables an Annex E debugging trace.

ras

Enables a RAS state machine debugging trace.

rawmsg

Enables a CCH323 RAWMSG debugging trace.

session

Enables a Session debugging trace.

Caution Using the debug cch323 all command could slow your system and flood the TTY if there is significant call traffic.

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 There is little or no output from this command when there is a stable H.323 network.

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:

•H225_IDLE—This is the initial state of the H.225 state machine. The H.225 state machine is in this state before issuing a call setup request (for the outbound IP call case) or when ready to receive an incoming IP call.

•H225_SETUP—This is the call setup state. The state machine changes to this state after sending out a call setup request or after receiving an incoming call indication.

•H225_ALERT—This is the call alerting state. The state machine changes to this state after sending the alerting message or after receiving an alerting message from the peer.

•H225_CALLPROC—This is the call proceeding state.

•H225_ACTIVE—This is the call connected state. In this state, the call is active. The state machine changes to this state after sending the connect message to the peer or after receiving the connect message from the peer.

•H225_WAIT_FOR_ARQ—This is the state in which the H.225 state machine is waiting for the completion of the Admission Request (ARQ) process from the RAS state machine.

•H225_WAIT_FOR_DRQ—This is the state in which the H.225 state machine is waiting for the completion of the Disengage Request (DRQ) process from the RAS state machine.

•H225_WAIT_FOR_H245—This is the state in which the H.225 state machine is waiting for the success or failure from the H.245 state machine.

The definitions of the different events of the H.225 state machine follow:

•H225_EVENT_NONE—There is no event.

•H225_EVENT_ALERT—This event instructs the H.225 state machine to send an alert message to the peer.

•H225_EVENT_ALERT_IND—This event indicates to the H.225 state machine that an alert message arrived from the peer.

•H225_EVENT_CALLPROC—This event instructs the H.225 state machine to send a call proceeding message to the peer.

•H225_EVENT_CALLPROC_IND—This event indicates to the H.225 state machine that a call proceeding message has been received from the peer.

•H225_EVENT_REJECT—This event instructs the H.225 state machine to reject the call setup request from the peer.

•H225_EVENT_REJECT_IND—This event indicates to the H.225 state machine that a call setup request to the peer has been rejected.

•H225_EVENT_RELEASE—This event instructs the H.225 state machine to send a release complete message to the peer.

•H225_EVENT_RELEASE_IND—This event indicates to the H.225 state machine that a release complete message has been received from the peer.

•H225_EVENT_SETUP—This event instructs the H.225 state machine to send a setup message to the peer.

•H225_EVENT_SETUP_IND—This event indicates to the H.225 state machine that a setup message has been received from the peer.

•H225_EVENT_SETUP_CFM—This event instructs the H.225 state machine to send a connect message to the peer.

•H225_EVENT_SETUP_CFM_IND—This event indicates to the H.225 state machine that a connect message arrived from the peer.

•H225_EVENT_RAS_SUCCESS—This event indicates to the H.225 state machine that the pending RAS operation succeeded.

•H225_EVENT_RAS_FAILED—This event indicates to the H.225 state machine that the pending RAS operation failed.

•H225_EVENT_H245_SUCCESS—This event indicates to the H.225 state machine that the pending H.245 operation succeeded.

•H225_EVENT_H245_FAILED—This event indicates to the H.225 state machine that the pending H.245 operation failed.

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:

•Master slave determination (MSD) state machine

•Capability exchange (CAP) state machine

•Open logical channel (OLC) state machine

The state definitions follow:

•H245_MS_NONE—This is the initial state of the MSD state machine.

•H245_MS_WAIT—In this state, an MSD message is sent, and the device is waiting for the reply.

•H245_MS_DONE— The result is in.

•H245_CAP_NONE—This is the initial state of the CAP state machine.

•H245_CAP_WAIT—In this state, a CAP message is sent, and the device is waiting for the reply.

•H245_CAP_DONE—The result is in.

•H245_OLC_NONE—This is the initial state of the OLC state machine.

•H245_OLC_WAIT—In this state, an OLC message is sent, and the device is waiting for the reply.

•H245_OLC_DONE—The result is in.

The event definitions follow:

•H245_EVENT_MSD—Send MSD message.

•H245_EVENT_MS_CFM—Send MSD acknowledge message.

•H245_EVENT_MS_REJ—Send MSD reject message.

•H245_EVENT_MS_IND—Received MSD message.

•H245_EVENT_CAP—Send CAP message.

•H245_EVENT_CAP_CFM—Send CAP acknowledge message.

•H245_EVENT_CAP_REJ—Send CAP reject message.

•H245_EVENT_CAP_IND—Received CAP message.

•H245_EVENT_OLC—Send OLC message.

•H245_EVENT_OLC_CFM—Send OLC acknowledge message.

•H245_EVENT_OLC_REJ—Send OLC reject message.

•H245_EVENT_OLC_IND—Received OLC message.

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:

•CCH323_RAS_STATE_NONE—This is the initial state of the RAS state machine.

•CCH323_RAS_STATE_GRQ—The state machine is in the Gatekeeper Request (GRQ) state. In this state, the gateway is discovering a gatekeeper.

•CCH323_RAS_STATE_RRQ—The state machine is in the Registration Request (RRQ) state. In this state, the gateway is registering with a gatekeeper.

•CCH323_RAS_STATE_IDLE—The global state machine is in the idle state.

•CCH323_RAS_STATE_URQ—The state machine is in the Unregistration Request (URQ) state. In this state, the gateway is in the process of unregistering with a gatekeeper.

•CCH323_RAS_STATE_ARQ—The per-call state machine is in the process of admitting a new call.

•CCH323_RAS_STATE_ACTIVE—The per-call state machine is in the call active state.

•CCH323_RAS_STATE_DRQ—The per-call state machine is in the process of disengaging an active call.

The definitions of the different events of the RAS state machine follow:

•CCH323_RAS_EVENT_NONE—Nothing.

•CCH323_RAS_EVENT_GWUP—Gateway is coming up.

•CCH323_RAS_EVENT_GWDWN—Gateway is going down.

•CCH323_RAS_EVENT_NEWCALL—New call.

•CCH323_RAS_EVENT_CALLDISC—Call disconnect.

•CCH323_RAS_EVENT_GCF—Received Gatekeeper Confirmation (GCF).

•CCH323_RAS_EVENT_GRJ—Received Gatekeeper Rejection (GRJ).

•CCH323_RAS_EVENT_ACF—Received Admission Confirmation (ACF).

•CCH323_RAS_EVENT_ARJ—Received Admission Reject (ARJ).

•CCH323_RAS_EVENT_SEND_RRQ—Send Registration Request (RRQ).

•CCH323_RAS_EVENT_RCF—Received Registration Confirmation (RCF).

•CCH323_RAS_EVENT_RRJ—Received Registration Rejection (RRJ).

•CCH323_RAS_EVENT_SEND_URQ—Send Unregistration Request (URQ).

•CCH323_RAS_EVENT_URQ—Received URQ.

•CCH323_RAS_EVENT_UCF—Received Unregister Confirmation (UCF).

•CCH323_RAS_EVENT_SEND_UCF—Send UCF.

•CCH323_RAS_EVENT_URJ—Received Unregister Reject (URJ).

•CCH323_RAS_EVENT_BCF—Received Bandwidth Confirm (BCF).

•CCH323_RAS_EVENT_BRJ—Received Bandwidth Rejection (BRJ).

•CCH323_RAS_EVENT_DRQ—Received Disengage Request (DRQ).

•CCH323_RAS_EVENT_DCF—Received Disengage Confirm (DCF).

•CCH323_RAS_EVENT_SEND_DCF—Send DCF.

•CCH323_RAS_EVENT_DRJ—Received Disengage Reject (DRJ).

•CCH323_RAS_EVENT_IRQ—Received Interrupt Request (IRQ).

•CCH323_RAS_EVENT_IRR—Send Information Request (IRR).

•CCH323_RAS_EVENT_TIMEOUT—Message timeout.

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 Using the debug cch323 command with the rawmsg keyword could slow your system and flood the TTY if there is significant call traffic.

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 Using the debug cch323 session command could slow your system and flood the TTY if there is significant call traffic.

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 error
cch323_h225_receiver:received msg of unknown type 5
The 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 h225
20:59:17:Set new event H225_EVENT_SETUP
20:59:17:H225 FSM:received event H225_EVENT_SETUP while at state H225_IDLE
20:59:17:Changing from H225_IDLE state to H225_SETUP state
20:59:17:cch323_h225_receiver:received msg of type SETUPCFM_CHOSEN
20:59:17:H225 FSM:received event H225_EVENT_SETUP_CFM_IND while at state 
H225_SETUP
20:59:17:Changing from H225_SETUP state to H225_ACTIVE state
20:59:17:Set new event H225_EVENT_H245_SUCCESS
20:59:17:H225 FSM:received event H225_EVENT_H245_SUCCESS while at state 
H225_ACTIVE
20:59:20:Set new event H225_EVENT_RELEASE
20:59:20:H225 FSM:received event H225_EVENT_RELEASE while at state 
H225_ACTIVE
20:59:20:Changing from H225_ACTIVE state to H225_WAIT_FOR_DRQ state
20:59:20:Set new event H225_EVENT_RAS_SUCCESS
20:59:20:H225 FSM:received event H225_EVENT_RAS_SUCCESS while at state 
H225_WAIT_FOR_DRQ
20:59:20:Changing from H225_WAIT_FOR_DRQ state to H225_IDLE state
Table 36 describes the significant fields shown in the display.

Table 36 debug cch323 h225 Field Descriptions

Field

Description

H225_EVENT_SETUP

This event instructs the H.225 state machine to send a setup message to the peer.

H225_IDLE

The initial state of the H.225 state machine. The H.225 state machine is in this state before issuing a call setup request (for the outbound IP call case) or when ready to receive an incoming IP call.

H225_SETUP

The call setup state. The state machine changes to this state after sending out a call setup request or after receiving an incoming call indication.

SETUPCFM_CHOSEN

The H225 connect message that has been received from a remote H323 endpoint.

H225_EVENT_SETUP_CFM_IND

This event indicates to the H.225 state machine that a connect message arrived from the peer.

H225_ACTIVE

The call connected state. In this state, the call is active. The state machine changes to this state after sending the connect message to the peer or after receiving the connect message from the peer.

H225_EVENT_H425_SUCCESS

This event indicates to the H.225 state machine that the pending H.245 operation succeeded.

H225_EVENT_RELEASE

This event instructs the H.225 state machine to send a release complete message to the peer.

H225_WAIT_FOR_DRQ

The state in which the H.225 state machine is waiting for the completion of the DRQ process from the RAS state machine.

H225_EVENT_RAS_SUCCESS

This event indicates to the H.225 state machine that the pending RAS operation succeeded.

H225 FSM

The finite state machine.

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 h245
20:58:23:Changing to new event H245_EVENT_MSD
20:58:23:H245 MS FSM:received event H245_EVENT_MSD while at state 
H245_MS_NONE
20:58:23:changing from H245_MS_NONE state to H245_MS_WAIT state
20:58:23:Changing to new event H245_EVENT_CAP
20:58:23:H245 CAP FSM:received event H245_EVENT_CAP while at state 
H245_CAP_NONE
20:58:23:changing from H245_CAP_NONE state to H245_CAP_WAIT state
20:58:23:cch323_h245_receiver:received msg of type 
M_H245_MS_DETERMINE_INDICATION
20:58:23:Changing to new event H245_EVENT_MS_IND
20:58:23:H245 MS FSM:received event H245_EVENT_MS_IND while at state 
H245_MS_WAIT
20:58:23:cch323_h245_receiver:received msg of type 
M_H245_CAP_TRANSFER_INDICATION
20:58:23:Changing to new event H245_EVENT_CAP_IND
20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_IND while at state 
H245_CAP_WAIT
20:58:23:cch323_h245_receiver:received msg of type 
M_H245_MS_DETERMINE_CONFIRM
20:58:23:Changing to new event H245_EVENT_MS_CFM
20:58:23:H245 MS FSM:received event H245_EVENT_MS_CFM while at state 
H245_MS_WAIT
20:58:23:changing from H245_MS_WAIT state to H245_MS_DONE state
0:58:23:cch323_h245_receiver:received msg of type M_H245_CAP_TRANSFER_CONFIRM
20:58:23:Changing to new event H245_EVENT_CAP_CFM
20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_CFM while at state 
H245_CAP_WAIT
20:58:23:changing from H245_CAP_WAIT state to H245_CAP_DONE state
20:58:23:Changing to new event H245_EVENT_OLC
20:58:23:H245 OLC FSM:received event H245_EVENT_OLC while at state
H245_OLC_NONE
20:58:23:changing from H245_OLC_NONE state to H245_OLC_WAIT state
20:58:23:cch323_h245_receiver:received msg of type 
M_H245_UCHAN_ESTABLISH_INDICATION
20:58:23:Changing to new event H245_EVENT_OLC_IND
20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_IND while at state 
H245_OLC_WAIT
20:58:23:cch323_h245_receiver:received msg of type M_H245_UCHAN_ESTAB_ACK
20:58:23:Changing to new event H245_EVENT_OLC_CFM
20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_CFM while at state 
H245_OLC_WAIT
20:58:23:changing from H245_OLC_WAIT state to H245_OLC_DONE state
Table 37 describes the significant fields shown in the display.

Table 37 debug cch323 h245 Field Descriptions

Field

Description

H245_EVENT_MSD

Send MSD event message to the state machine.

H245 MS FSM

An H225 master slave determination finite state machine.

H245_MS_NONE

The initial state of the MSD state machine.

H245_MS_WAIT

In this state, a MSD message is sent, and the device is waiting for the reply.

H245_EVENT_CAP

Send CAP event message.

H245 CAP FSM

This is the H245 terminal CAP finite state machine.

H245_CAP_NONE

The initial state of the CAP state machine.

H245_CAP_WAIT

In this state, a CAP message is sent, and the device is waiting for the reply.

M_H245_MS_DETERMINE _INDICATION

The MSD message that has been received by an H245 terminal from a remote H323 endpoint.

H245_EVENT_MS_IND

Received MSD event message.

M_H245_CAP_TRANSFER_INDICATION

A CAP message that has been received by the H245 terminal from an H323 remote endpoint.

H245_EVENT_CAP_IND

Received CAP event message.

M_H245_MS_DETERMINE_CONFIRM

A confirmation message that the H245 master slave termination message was sent.

H245_EVENT_MS_CFM

Send MSD acknowledge event message.

H245_MS_DONE

The result is in.

M_H245_CAP_TRANSFER_CONFIRM

An indication to the H245 terminal that the CAP message was sent.

H245_EVENT_CAP_CFM

Send CAP acknowledge event message.

H245_CAP_DONE

The result is in.

H245_EVENT_OLC

Send OLC event message.

H245_OLC_NONE

The initial state of the OLC state machine.

H245_OLC_WAIT

In this state, an OLC message is sent, and the device is waiting for the reply.

M_H245_UCHAN_ESTABLISH_INDICATION

The OLC message received by an H245 terminal from a remote H323 endpoint.

H245_EVENT_OLC_IND

Received OLC event message.

M_H245_UCHAN_ESTAB_ACK

The OLC message acknowledgment received by an H245 terminal from a remote H323 endpoint.

H245_EVENT_OLC_CFM

Send OLC acknowledge event message.

H245 OLC FSM

The OLC finite state machine of the H245 terminal.

H245_EVENT_OLC_CFM

Send OLC acknowledge event message.

H245_OLC_DONE

The result is in.

The debug cch323 Command with the nxe Keyword Example

The following is sample output from a debug cch323 nxe request:
Router# debug cch323 nxe
00:15:54:nxe_handle_usrmsg_to_remote:User Message size is 227
00: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 = 0x2
00:15:54:nxe_parse_payload:Transport msg type, Payload flag = 0x0
00:15:54:nxe_receive_ack:Ack received for 1 pdus
00: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 = 0x3
00:15:54:nxe_parse_payload:Static msg type, Payload flag = 0xA0
00: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=14
00: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 = 0x3
00:15:54:nxe_parse_payload:Static msg type, Payload flag = 0xA0
00: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 ras
20:58:49:Changing to new event CCH323_RAS_EVENT_SEND_RRQ
cch323_run_ras_sm:received event CCH323_RAS_EVENT_SEND_RRQ while at CCH323_RAS_STATE_IDLE 
state
cch323_run_ras_sm:changing to CCH323_RAS_STATE_RRQ state
cch323_ras_receiver:received msg of type RCF_CHOSEN
cch323_run_ras_sm:received event CCH323_RAS_EVENT_RCF while at CCH323_RAS_STATE_RRQ state
cch323_run_ras_sm:changing to CCH323_RAS_STATE_IDLE state
20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_NEWCALL while at 
CCH323_RAS_STATE_IDLE state
20:58:59:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ARQ
cch323_ras_receiver:received msg of type ACF_CHOSEN
20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_ACF while at 
CCH323_RAS_STATE_ARQ state
20:58:59:cch323_percall_ras_sm:changing to new state 
CCH323_RAS_STATE_ACTIVE
20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_CALLDISC while
at CCH323_RAS_STATE_ACTIVE state
20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_DRQ
cch323_ras_receiver:received msg of type DCF_CHOSEN
20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_DCF while at
CCH323_RAS_STATE_DRQ state
20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_IDLE
20:59:04:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_IRR while at 
CCH323_RAS_STATE_ACTIVE state
20:59:04:cch323_percall_ras_sm:changing to new state 
CCH323_RAS_STATE_ACTIVE
Table 38 describes the significant fields shown in the display.

Table 38 debug cch323 ras Field Descriptions

Field

Description

CCH323_RAS_EVENT_SEND_RRQ

Send RRQ event message.

CCH323_RAS_STATE_IDLE

The global state machine is in the idle state.

CCH323_RAS_STATE_RRQ

The state machine is in the RRQ state. In this state, the gateway is registering with a gatekeeper.

RCF_CHOSEN

A registration confirm message that has been received from a gatekeeper.

CCH323_RAS_EVENT_RCF

Received RCF event message.

CCH323_RAS_EVENT_NEWCALL

New call event.

CCH323_RAS_STATE_ARQ

The per-call state machine is in the process of admitting a new call.

ACF_CHOSEN

ACF message that has been received from a gatekeeper.

CCH323_RAS_EVENT_ACF

Received ACF event message.

CCH323_RAS_STATE_ACTIVE

The per-call state machine is in the call active state.

CCH323_RAS_EVENT_CALLDISC

Call disconnect event message.

CCH323_RAS_STATE_DRQ

The per-call state machine is in the process of disengaging an active call.

DCF_CHOSEN

The disengage confirm message that has been received from a gatekeeper.

CCH323_RAS_EVENT_DCF

Received DCF event message.

CCH323_RAS_EVENT_IRR

Send IRR event message.

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 rawmsg
00:32:04:cch323_h225_progress_ind:raw message is 4 bytes:1E 02 81 88
00: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 00
00: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 00
The 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 session
00:33:49:cch323_call_setup:gw_id=1, callID=16
00:33:49:cch323_get_new_ccb:ccb (0x81D12D2C) is in use
00:33:49:cch323_call_setup:inserted ccb
cch323_get_peer_info:faxrate[21]proto[2]bitmask[10002]t38_inhibit[0]global_fax[0]
00:33:49:Not using Voice Class Codec
00:33:49:cch323_get_peer_info:preffered_codec set to G729IETF with Bytes = 20
00:33:49:cch323_get_peer_info:peer:81FC0D14, peer->voice_peer_tag:12D, ccb:81D12D2C
00:33:49:Call_setup Playout Mode:0,Init 60, Min 40, Max 200
00:33:49:No account/pin number available
00:33:49:cch323_call_setup_normal:for callID 10
00:33:49:timer (0x81D130D4)starts - delay (15000)
00:33:49:cch323_ct_main:SOCK 1 Event 0x1
00:33:49:timer(0x81D130D4) stops
00:33:49:Near-end Pref Codecs = G.729 IETF
00:33:49: generic_open_logical_channel:codec is g729
00:33:49:cch323_generic_open_logical_channel:Filling in qosCapability field to 0
00:33:49:timer (0x81D130D4)starts - delay (15000)
00:33:49:cch323_ct_main:SOCK 1 Event 0x1
00:33:49:cch323_ct_main:SOCK 1 Event 0x1
00:33:49:      [1]towner_data=0x81D13C88, len=105, msgPtr=0x81D07608
00:33:49:cch323_gw_process_read_socket:received msg for H.225
00:33:49:timer(0x81D130D4) stops
00: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 0x1
00:33:50:      [1]towner_data=0x81D13C88, len=71, msgPtr=0x81F1F2E0
00:33:50:cch323_gw_process_read_socket:received msg for H.225
00:33:50:cch323_caps_ind:cap_modem_proto:0, cap_modem_codec:0, cap_modem_redundancy:0 
payload 100
00:33:50:cch323_caps_ind:Load DSP with Negotiated codec(16) g729r8, Bytes=20
00:33:50:cch323_caps_ind:set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE
The following is sample output from a typical debug cch323 session request for a call setup on a terminating gateway:
Router# debug cch323 session
00:23:27:cch323_ct_main:SOCK 0 Event 0x1
00:23:27:cch323_ct_main:SOCK 1 Event 0x1
00:23:27:      [1]towner_data=0x81F9CA9C, len=179, msgPtr=0x81D15C6C
00:23:27:cch323_gw_process_read_socket:received msg for H.225
00:23:27:cch323_h225_receiver CCB not existing already
00:23:27:cch323_get_new_ccb:ccb (0x81F90184) is in use
00:23:27:cch323_h225_receiver Got a new CCB for call id -2115467564
00:23:27:cch323_h225_setup_ind
00:23:27:Not using Voice Class Codec
00:23:27:cch323_set_peer:peer:81FB3228, peer->voice_peer_tag:12C, ccb:81F90184
00:23:27:Near-end Pref Codecs = G.729 IETF
00: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 0
00:23:27:cch323_build_fastStart_cap_response:In Response Filling in qosCapability field 
to 0
00:23:27:Not using Voice Class Codec
Related Commands

Command

Description

clear h323 gateway

Clears the H.323 gateway counters.

debug h323-annexg

Displays all pertinent AnnexG messages that have been transmitted and received.

debug voip rawmsg

Displays the raw message owner, length, and pointer.

show h323 gateway

Displays statistics for H.323 gateway messages that have been sent and received and displays the reasons for which H.323 calls have been disconnected.

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

Release

Modification

12.2(11)T

This command was introduced.

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 capacity
Call Capacity Information tracing is enabled
5d00h: cch323_process_carrier_update: Registered = 1,Event = 1,Reason = 1 
5d00h: cch323_process_carrier_update: CarrierId = CARRIERA_NEWENGLAND
5d00h: cch323_fill_crm_CallCapacities: Reason = 1, GroupID = CARRIERA_NEWENGLAND
5d00h: Capacity Details:           Maximum Channels in Group:    23
      Max. Voice Calls(In) :     23,     Max. Voice Calls(Out):    23
      Active Voice Calls(In):     5,     Active Voice Calls(Out):    7
      Max. Voice Calls(to GK):   23,     Avail. Voice Calls(to GK):   11
The 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 = 1 
5d00h: cch323_process_carrier_update: CarrierId = CARRIERA_NEWENGLAND
Table 39 describes the significant fields shown in the display.

Table 39 debug cch323 capacity Update Field Descriptions

Field

Description

Registered

Gateway registration:

•0=Gateway is not registered to the gatekeeper

•1=Gateway is registered to the gatekeeper at the time of the change

Event

Carriers updated:

•0=All carriers updated

•1=Single carrier updated

Reason

Reason for the update notification:

•0=CURRENT_CAPACITY_UPDATE

•1=MAX_CAPACITY_UPDATE

•2=BOTH_CAPACITY_UPDATE

CarrierID

ID of the trunk group or carrier to which the change applies.

The gatekeeper displays this output whenever call capacity information is sent to the gatekeeper.
5d00h: cch323_fill_crm_CallCapacities: Reason = 1, GroupID = CARRIERA_NEWENGLAND
5d00h: Capacity Details:           Maximum Channels in Group:    23
      Max. Voice Calls(In) :     23,     Max. Voice Calls(Out):    23
      Active Voice Calls(In):     5,     Active Voice Calls(Out):    7
      Max. Voice Calls(to GK):   23,     Avail. Voice Calls(to GK):   11
Table 40 describes the significant fields shown in the display.

Table 40 debug cch323 capacity Call Capacity Field Descriptions

Field

Description

GroupID

The circuit's carrier identification (ID) or trunk group label.

Maximum Channels in Group

Maximum number of physical (or configured) circuits.

Max. Voice Calls(In)

Maximum number of allowed incoming voice and data calls.

Max. Voice Calls(Out)

Maximum number of allowed outgoing voice and data calls.

Active Voice Calls(In)

Current number of active incoming voice and data calls.

Active Voice Calls(Out)

Current number of active outgoing voice and data calls.

Max. Voice Calls(to GK)

Maximum call capacity value to be sent to the gatekeeper in the RAS message.

Avail. Voice Calls(to GK)

Available call capacity value to be sent to the gatekeeper in the RAS message.

Related Commands

Command

Description

endpoint circuit-id h323id

Associates a carrier with a non-Cisco endpoint.

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

Release

Modification

11.3(6)NA2

This command was introduced.

12.2(2)XB1

This command was implemented on the Cisco AS5850.

12.2(11)T

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

Usage Guidelines

State Descriptions

The state definitions of the different states of the H.225 state machine are as follows:

•H225_IDLE—This is the initial state of the H.225 state machine. The H.225 state machine is in this state before issuing a call setup request (for the outbound IP call case) or ready to receive an incoming IP call.

•H225_SETUP—This is the call setup state. The state machine transitions to this state after sending out a call setup request, or after the reception of an incoming call indication.

•H225_ALERT—This is the call alerting state. The state machine transitions to this state after sending the alerting message or after the reception of an alerting message from the peer.

•H225_CALLPROC—This is the call proceeding state.

•H225_ACTIVE—This is the Call connected state. In this state, the call is active. The state machine transitions to this state after sending the connect message to the peer or after the reception of the connect message from the peer.

•H225_WAIT_FOR_ARQ—This is the state where the H.225 state machine is waiting for the completion of the ARQ process from the Registration, Admission, and Status Protocol (RAS) state machine.

•H225_WAIT_FOR_DRQ—This is the state where the H.225 state machine is waiting for the completion of the DRQ process from the RAS state machine.

•H225_WAIT_FOR_H245—This is the state where the H.225 state machine is waiting for the success or failure from the H.245 state machine.

Events Description

The event definitions of the different events of the H.225 state machine are as follows:

•H225_EVENT_NONE— No event.

•H225_EVENT_ALERT—This event indicates the H.225 state machine to send an alerting message to the peer.

•H225_EVENT_ALERT_IND—This event indicates the H.225 state machine that an alerting message is received from the peer.

•H225_EVENT_CALLPROC—This event indicates the H.225 state machine to send a call proceeding message to the peer.

•H225_EVENT_CALLPROC_IND—This event indicates the H.225 state machine that a call proceeding message is received from the peer.

•H225_EVENT_REJECT—This event indicates the H.225 state machine to reject the call setup request from the peer.

•H225_EVENT_REJECT_IND—This event indicates the H.225 state machine that a call setup request to the peer is rejected.

•H225_EVENT_RELEASE—This event indicates the H.225 state machine to send a release complete message to the peer.

•H225_EVENT_RELEASE_IND—This event indicates the H.225 state machine that a release complete message is received from the peer.

•H225_EVENT_SETUP—This event indicates the H.225 state machine to send a setup message to the peer.

•H225_EVENT_SETUP_IND—This event indicates the H.225 state machine that a setup message is received from the peer.

•H225_EVENT_SETUP_CFM—This event indicates the H.225 state machine to send a connect message to the peer.

•H225_EVENT_SETUP_CFM_IND—This event indicates the H.225 state machine that a connect message from the peer.

•H225_EVENT_RAS_SUCCESS—This event indicates the H.225 state machine that the pending RAS operation is successful.

•H225_EVENT_RAS_FAILED—This event indicates the H.225 state machine that the pending RAS operation failed.

•H225_EVENT_H245_SUCCESS—This event indicates the H.225 state machine that the pending H.245 operation is successful.

•H225_EVENT_H245_FAILED—This event indicates the H.225 state machine that the pending H.245 operation failed.

Examples

The following is sample output from the debug cch323 h225 command:
Router# debug cch323 h225
20:59:17:Set new event H225_EVENT_SETUP
20:59:17:H225 FSM:received event H225_EVENT_SETUP while at state H225_IDLE
20:59:17:Changing from H225_IDLE state to H225_SETUP state
20:59:17:cch323_h225_receiver:received msg of type SETUPCFM_CHOSEN
20:59:17:H225 FSM:received event H225_EVENT_SETUP_CFM_IND while at state 
H225_SETUP
20:59:17:Changing from H225_SETUP state to H225_ACTIVE state
20:59:17:Set new event H225_EVENT_H245_SUCCESS
20:59:17:H225 FSM:received event H225_EVENT_H245_SUCCESS while at state 
H225_ACTIVE
20:59:20:Set new event H225_EVENT_RELEASE
20:59:20:H225 FSM:received event H225_EVENT_RELEASE while at state 
H225_ACTIVE
20:59:20:Changing from H225_ACTIVE state to H225_WAIT_FOR_DRQ state
20:59:20:Set new event H225_EVENT_RAS_SUCCESS
20:59:20:H225 FSM:received event H225_EVENT_RAS_SUCCESS while at state 
H225_WAIT_FOR_DRQ
20:59:20:Changing from H225_WAIT_FOR_DRQ state to H225_IDLE state
debug 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

Release

Modification

11.3(6)NA2

This command was introduced.

12.2(2)XB1

This command was implemented on the Cisco AS5850.

12.2(11)T

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

Usage Guidelines

The H.245 state machines include the following three state machines:

•Master SlaveDetermination (MSD) state machine

•Capability Exchange (CAP) state machine

•Open Logical Channel (OLC) state machine

State Definitions

The definitions are as follows:

•H245_MS_NONE— This is the initial state of the master slave determination state machine.

•H245_MS_WAIT—In this state, a Master Slave Determination message is sent, waiting for the reply.

•H245_MS_DONE— The result is in.

•H245_CAP_NONE—This is the initial state of the capabilities exchange state machine.

•H245_CAP_WAIT—In this state, a cap exchange message is sent, waiting for reply.

•H245_CAP_DONE—The result is in.

•H245_OLC_NONE—This is the initial state of the open logical channel state machine.

•H245_OLC_WAIT: OLC message sent, waiting for reply.

•H245_OLC_DONE: OLC done.

Event definitions

•H245_EVENT_MSD—Send MSD message

•H245_EVENT_MS_CFM—Send MSD acknowledge message

•H245_EVENT_MS_REJ—Send MSD reject message

•H245_EVENT_MS_IND— Received MSD message

•H245_EVENT_CAP—Send CAP message

•H245_EVENT_CAP_CFM—Send CAP acknowledge message

•H245_EVENT_CAP_REJ—Send CAP reject

•H245_EVENT_CAP_IND—Received CAP message

•H245_EVENT_OLC—Send OLC message

•H245_EVENT_OLC_CFM—Send OLC acknowledge message

•H245_EVENT_OLC_REJ—Send OLC reject message

•H245_EVENT_OLC_IND—Received OLC message

Examples

The following is sample output from the debug cch323 h245 command:
Router# debug cch323 h245
20:58:23:Changing to new event H245_EVENT_MSD
20:58:23:H245 MS FSM:received event H245_EVENT_MSD while at state 
H245_MS_NONE
20:58:23:changing from H245_MS_NONE state to H245_MS_WAIT state
20:58:23:Changing to new event H245_EVENT_CAP
20:58:23:H245 CAP FSM:received event H245_EVENT_CAP while at state 
H245_CAP_NONE
20:58:23:changing from H245_CAP_NONE state to H245_CAP_WAIT state
20:58:23:cch323_h245_receiver:received msg of type 
M_H245_MS_DETERMINE_INDICATION
20:58:23:Changing to new event H245_EVENT_MS_IND
20:58:23:H245 MS FSM:received event H245_EVENT_MS_IND while at state 
H245_MS_WAIT
20:58:23:cch323_h245_receiver:received msg of type 
M_H245_CAP_TRANSFER_INDICATION
20:58:23:Changing to new event H245_EVENT_CAP_IND
20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_IND while at state 
H245_CAP_WAIT
20:58:23:cch323_h245_receiver:received msg of type 
M_H245_MS_DETERMINE_CONFIRM
20:58:23:Changing to new event H245_EVENT_MS_CFM
20:58:23:H245 MS FSM:received event H245_EVENT_MS_CFM while at state 
H245_MS_WAIT
20:58:23:changing from H245_MS_WAIT state to H245_MS_DONE state
0:58:23:cch323_h245_receiver:received msg of type M_H245_CAP_TRANSFER_CONFIRM
20:58:23:Changing to new event H245_EVENT_CAP_CFM
20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_CFM while at state 
H245_CAP_WAIT
20:58:23:changing from H245_CAP_WAIT state to H245_CAP_DONE state
20:58:23:Changing to new event H245_EVENT_OLC
20:58:23:H245 OLC FSM:received event H245_EVENT_OLC while at state
H245_OLC_NONE
20:58:23:changing from H245_OLC_NONE state to H245_OLC_WAIT state
20:58:23:cch323_h245_receiver:received msg of type 
M_H245_UCHAN_ESTABLISH_INDICATION
20:58:23:Changing to new event H245_EVENT_OLC_IND
20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_IND while at state 
H245_OLC_WAIT
20:58:23:cch323_h245_receiver:received msg of type M_H245_UCHAN_ESTAB_ACK
20:58:23:Changing to new event H245_EVENT_OLC_CFM
20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_CFM while at state 
H245_OLC_WAIT
20:58:23:changing from H245_OLC_WAIT state to H245_OLC_DONE state
debug 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

Release

Modification

12.2(11)T

This command was introduced.

Examples

The following is debugging output for a single H.323 call:
Router# debug cch323 preauth
CCH323 preauth tracing is enabled
cch323_is_preauth_reqd is TRUE
Jan 23 18:39:56.393: In cch323_send_preauth_req for preauth_id = -1
Jan 23 18:39:56.393: Entering rpms_proc_print_preauth_req 
Jan 23 18:39:56.393: Request = 0
Jan 23 18:39:56.393: Preauth id = 86514
Jan 23 18:39:56.393: EndPt Type  = 1
Jan 23 18:39:56.393: EndPt = 192.168.81.102
Jan 23 18:39:56.393: Resource Service = 1
Jan 23 18:39:56.393: Call_origin = answer
Jan 23 18:39:56.393: Call_type = voip
Jan 23 18:39:56.393: Calling_num = 2230001
Jan 23 18:39:56.393: Called_num = 1#1130001
Jan 23 18:39:56.393: Protocol  = 0
Jan 23 18:39:56.393: cch323_insert_preauth_tree:Created node with preauth_id = 86514 ,ccb 
6852D5BC , node 651F87FC
Jan 23 18:39:56.393:rpms_proc_create_node:Created node with preauth_id = 86514 
Jan 23 18:39:56.393:rpms_proc_send_aaa_req:uid got is 466725
Jan 23 18:39:56.397:rpms_proc_preauth_response:Context is for preauth_id 86514, aaa_uid 
466725
Jan 23 18:39:56.397: Entering Function cch323_rpms_proc_callback_func
Jan 23 18:39:56.397:cch323_rpms_proc_callback_func:PREAUTH_SUCCESS for preauth id 86514 
aaa_uid 466725 auth_serv 1688218168
Jan 23 18:39:56.397:rpms_proc_preauth_response:Deleting Tree node for preauth id 86514 uid 
466725
Jan 23 18:39:56.397:cch323_get_ccb_and_delete_from_preauth_tree:Preauth_id=86514
cch323_get_ccb_and_delete_from_preauth_tree:651F87FC node and 6852D5BC ccb
Table 41 describes the significant fields shown in the display.

Table 41 debug cch323 preauth Field Descriptions

Field

Description

Request

Request Type—0 for preauthentication, 1 for disconnect.

Preauth id

Identifier for the preauthentication request.

EndPt Type

Call Origin End Point Type—1 for IP address, 2 for IZCT value.

EndPt

Call Origin End Point Value—An IP address or IZCT value.

Resource Service

Resource Service Type—1 for Reservation, 2 for Query.

Call_origin

Answer.

Call_type

Voice over IP (VoIP).

Calling_num

Calling Party Number (CLID).

Called_num

Called Party Number (DNIS).

Protocol

0 for H.323, 1 for SIP.

function reports

Various identifiers and status reports for executed functions.

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

Release

Modification

11.3(6)NA2

This command was introduced.

12.2(2)XB1

This command was implemented on the Cisco AS5850.

12.2(11)T

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

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:

•CCH323_RAS_STATE_NONE—This is the initial state of the RAS state machine.

•CCH323_RAS_STATE_GRQ—The state machine is in the Gatekeeper Request (GRQ) state. In this state, the gateway is in the process of discovering a gatekeeper.

•CCH323_RAS_STATE_RRQ—The state machine is in the Registration Request (RRQ) state. In this state, the gateway is in the process of registering with a gatekeeper.

•CCH323_RAS_STATE_IDLE—The global state machine is in the idle state.

•CCH323_RAS_STATE_URQ—The state machine is in the Unregistration Request (URQ) state. In this state, the gateway is in the process of unregistering with a gatekeeper.

•CCH323_RAS_STATE_ARQ—The per call state machine is in the process of admitting a new call.

•CCH323_RAS_STATE_ACTIVE—The per call state machine is in the call active state.

•CCH323_RAS_STATE_DRQ—The per call state machine is in the process of disengaging an active call.

Event Definitions

These are the event definitions of the different states of the RAS state machine:

•CCH323_RAS_EVENT_NONE—Nothing.

•CCH323_RAS_EVENT_GWUP—Gateway is coming up.

•CCH323_RAS_EVENT_GWDWN—Gateway is going down.

•CCH323_RAS_EVENT_NEWCALL—New call.

•CCH323_RAS_EVENT_CALLDISC—Call disconnect.

•CCH323_RAS_EVENT_GCF—Received Gatekeeper Confirmation (GCF).

•CCH323_RAS_EVENT_GRJ—Received Gatekeeper Rejection (GRJ).

•CCH323_RAS_EVENT_ACF—Received Admission Confirmation (ACF).

•CCH323_RAS_EVENT_ARJ—Received Admission Rejection (ARJ).

•CCH323_RAS_EVENT_SEND_RRQ—Send Registration Request (RRQ).

•CCH323_RAS_EVENT_RCF—Received Registration Confirmation (RCF).

•CCH323_RAS_EVENT_RRJ—Received Registration Rejection (RRJ).

•CCH323_RAS_EVENT_SEND_URQ—Send URQ.

•CCH323_RAS_EVENT_URQ—Received URQ.

•CCH323_RAS_EVENT_UCF—Received Unregister Confirmation (UCF).

•CCH323_RAS_EVENT_SEND_UCF—Send Unregister Confirmation (UCF).

•CCH323_RAS_EVENT_URJ—Received Unregister Reject (URJ).

•CCH323_RAS_EVENT_BCF—Received Bandwidth Confirm (BCF).

•CCH323_RAS_EVENT_BRJ—Received Bandwidth Rejection (BRJ).

•CCH323_RAS_EVENT_DRQ—Received Disengage Request (DRQ).

•CCH323_RAS_EVENT_DCF—Received Disengage Confirm (DCF).

•CCH323_RAS_EVENT_SEND_DCF—Send Disengage Confirm (DCF).

•CCH323_RAS_EVENT_DRJ—Received Disengage Reject (DRJ).

•CCH323_RAS_EVENT_IRQ—Received Interrupt Request (IRQ).

•CCH323_RAS_EVENT_IRR—Send Information Request (IRR).

•CCH323_RAS_EVENT_TIMEOUT—Message timeout.

Examples

The following is sample output from the debug cch323 preauth command:
Router# debug cch323 preauth
20:58:49:Changing to new event CCH323_RAS_EVENT_SEND_RRQ
cch323_run_ras_sm:received event CCH323_RAS_EVENT_SEND_RRQ while at CCH323_RAS_STATE_IDLE 
state
cch323_run_ras_sm:changing to CCH323_RAS_STATE_RRQ state
cch323_ras_receiver:received msg of type RCF_CHOSEN
cch323_run_ras_sm:received event CCH323_RAS_EVENT_RCF while at CCH323_RAS_STATE_RRQ state
cch323_run_ras_sm:changing to CCH323_RAS_STATE_IDLE state
20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_NEWCALL while at 
CCH323_RAS_STATE_IDLE state
20:58:59:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ARQ
cch323_ras_receiver:received msg of type ACF_CHOSEN
20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_ACF while at 
CCH323_RAS_STATE_ARQ state
20:58:59:cch323_percall_ras_sm:changing to new state 
CCH323_RAS_STATE_ACTIVE
20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_CALLDISC while
at CCH323_RAS_STATE_ACTIVE state
20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_DRQ
cch323_ras_receiver:received msg of type DCF_CHOSEN
20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_DCF while at
CCH323_RAS_STATE_DRQ state
20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_IDLE
20:59:04:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_IRR while at 
CCH323_RAS_STATE_ACTIVE state
20:59:04:cch323_percall_ras_sm:changing to new state 
CCH323_RAS_STATE_ACTIVE
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

backhaul

Enables debugging of the Cisco CallManager backhaul. The keywords are as follows:

•errors—Displays Cisco CallManager backhaul errors.

•events—Displays Cisco CallManager backhaul events.

•packets—Displays Cisco CallManager packets.

config-download

Enables debugging of the Cisco CallManager configuration download. The keywords are as follows:

•all—Displays all Cisco CallManager configuration parameters.

•errors—Displays Cisco CallManager configuration errors.

•events—Displays Cisco CallManager configuration events.

•packets—Displays Cisco CallManager configuration packets.

•tone—Displays Cisco CallManager downloaded custom tones.

•xml—Displays the Cisco CallManager configuration XML parser.

errors

Displays errors related to Cisco CallManager.

events

Displays Cisco CallManager events, such as when the primary Cisco CallManager server fails and control is switched to the backup Cisco CallManager server.

music-on-hold

Displays music on hold (MOH). The keywords are as follows:

•errors—Displays MOH errors.

•events—Displays MOH events.

•packets—Displays MOH packets.

packets

Displays Cisco CallManager packets.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced for Cisco CallManager Version 3.0 and the Cisco VG200.

12.2(2)XA

This command was implemented on Cisco 2600 series and Cisco 3600 series routers.

12.2(2)XN

Support for enhanced MGCP voice gateway interoperability was added to Cisco CallManager Version 3.1 for the Cisco 2600 series, Cisco 3600 series, and Cisco VG200.

12.2(11)T

This command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco IAD2420 series.

12.2(15)XJ

The tone keyword was added for the following platforms: Cisco 2610XM, Cisco 611XM, Cisco 2620XM, Cisco 2621XM, Cisco 2650XM, Cisco 2651XM, Cisco 2691, Cisco 3640A, Cisco 3660, Cisco 3725, and Cisco 3745.

12.3(4)T

The tone keyword was added.

12.3(14)T

New output was added relating to the SCCP protocol.

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 tone
00:09:07:
cmapp_prefix_process_tag_tones:
00:09:07: cmapp_process_tag_trkLocaleName: region = United Kingdom
00:09:07: cmapp_process_tag_pulse_ratio: pulse ratio = 40
00:09:07: cmapp_process_tag_dtmf_llevel: low frequency level = 65438
00:09:07: cmapp_process_tag_dtmf_hlevel: high frequency level = 65463
00:09:07: cmapp_process_tag_special_oper: operation = uLaw
00:09:07: cmapp_prefix_process_tag_lpig: 
00:09:07: cmapp_process_tag_fxs: ignore LPIG for fxs
00:09:07: cmapp_process_tag_fxo: ignore LPIG for fxo
00:09:07: cmapp_process_tag_digital: ignore LPIG for digital
00:09:07: cmapp_prefix_process_tag_lpog: 
00:09:07: cmapp_process_tag_fxs: ignore LPOG for fxsBoth ports are in service
00:09:07: cmapp_process_tag_fxo: ignore LPOG for fxo
00:09:07: cmapp_process_tag_digital: ignore LPOG for digital
00: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 = 1
00:09:07: cmapp_process_tag_dr: direction = 0
00:09:07: cmapp_process_tag_fof: frequency 1 = 400
00:09:07: cmapp_process_tag_fos: frequency 2 = 0
00:09:07: cmapp_process_tag_fot: frequency 3 = 0
00:09:07: cmapp_process_tag_fo4: frequency 4 = 0
00:09:07: cmapp_prefix_process_tag_aof_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -200
00:09:07: cmapp_process_tag_fxo: amplitude of 1st = -200
00:09:07: cmapp_process_tag_digital: amplitude of 1st = -240
00:09:07: cmapp_prefix_process_tag_aos_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 2nd = 0
00:09:07: cmapp_process_tag_digital: amplitude of 2nd = 0
00:09:07: cmapp_prefix_process_tag_aot_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 0
00:09:07: cmapp_process_tag_digital: amplitude of 3rd = 0
00:09:07: cmapp_prefix_process_tag_ao4_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 4th = 0
00:09:07: cmapp_process_tag_digital: amplitude of 4th = 0
00:09:07: cmapp_process_tag_ontf: frequency 1 on time = 375
00:09:07: cmapp_process_tag_oftf: frequency 1 off time = 375
00:09:07: cmapp_process_tag_onts: frequency 2 on time = 0
00:09:07: cmapp_process_tag_ofts: frequency 2 off time = 0
00:09:07: cmapp_process_tag_ontt: frequency 3 on time = 0
00:09:07: cmapp_process_tag_oftt: frequency 3 off time = 0
00:09:07: cmapp_process_tag_ont4: frequency 4 on time = 0
00:09:07: cmapp_process_tag_oft4: frequency 4 off time = 0
00:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 0
00:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 0
00:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 0
00:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 0
00:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 0
00:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 0
00:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 0
00:09:07: cmapp_process_tag_rct2: cadence 2 repeat count = 0
00:09:07: cmapp_process_tag_rct3: cadence 3 repeat count = 0
00:09:07: cmapp_process_tag_rct4: cadence 4 repeat count = 0
00:09:07: 
cmapp_prefix_process_tag_dualtone: TID=[1:CPTONE_RING_BACK]
00:09:07: cmapp_process_tag_nf: number of frequencies = 2
00:09:07: cmapp_process_tag_dr: direction = 0
00:09:07: cmapp_process_tag_fof: frequency 1 = 400
00:09:07: cmapp_process_tag_fos: frequency 2 = 450
00:09:07: cmapp_process_tag_fot: frequency 3 = 0
00:09:07: cmapp_process_tag_fo4: frequency 4 = 0
00:09:07: cmapp_prefix_process_tag_aof_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -190
00:09:07: cmapp_process_tag_fxo: amplitude of 1st = -190
00:09:07: cmapp_process_tag_digital: amplitude of 1st = -190
00:09:07: cmapp_prefix_process_tag_aos_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = -190
00:09:07: cmapp_process_tag_fxo: amplitude of 2nd = -190
00:09:07: cmapp_process_tag_digital: amplitude of 2nd = -190
00:09:07: cmapp_prefix_process_tag_aot_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 0
00:09:07: cmapp_process_tag_digital: amplitude of 3rd = 0
00:09:07: cmapp_prefix_process_tag_ao4_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 4th = 0
00:09:07: cmapp_process_tag_digital: amplitude of 4th = 0
00:09:07: cmapp_process_tag_ontf: frequency 1 on time = 400
00:09:07: cmapp_process_tag_oftf: frequency 1 off time = 200
00:09:07: cmapp_process_tag_onts: frequency 2 on time = 400
00:09:07: cmapp_process_tag_ofts: frequency 2 off time = 2000
00:09:07: cmapp_process_tag_ontt: frequency 3 on time = 0
00:09:07: cmapp_process_tag_oftt: frequency 3 off time = 0
00:09:07: cmapp_process_tag_ont4: frequency 4 on time = 0
00:09:07: cmapp_process_tag_oft4: frequency 4 off time = 0
00:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 0
00:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 0
00:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 0
00:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 0
00:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 0
00:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 0
00:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 0
00:09:07: cmapp_process_tag_rct2: cadence 2 repeat count = 0
00:09:07: cmapp_process_tag_rct3: cadence 3 repeat count = 0
00:09:07: cmapp_process_tag_rct4: cadence 4 repeat count = 0
00:09:07: 
cmapp_prefix_process_tag_dualtone: TID=[2:CPTONE_CONGESTION]
00:09:07: cmapp_process_tag_nf: number of frequencies = 1
00:09:07: cmapp_process_tag_dr: direction = 0
00:09:07: cmapp_process_tag_fof: frequency 1 = 400
00:09:07: cmapp_process_tag_fos: frequency 2 = 0
00:09:07: cmapp_process_tag_fot: frequency 3 = 0
00:09:07: cmapp_process_tag_fo4: frequency 4 = 0
00:09:07: cmapp_prefix_process_tag_aof_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -200
00:09:07: cmapp_process_tag_fxo: amplitude of 1st = -200
00:09:07: cmapp_process_tag_digital: amplitude of 1st = -200
00:09:07: cmapp_prefix_process_tag_aos_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 2nd = 0
00:09:07: cmapp_process_tag_digital: amplitude of 2nd = 0
00:09:07: cmapp_prefix_process_tag_aot_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 0
00:09:07: cmapp_process_tag_digital: amplitude of 3rd = 0
00:09:07: cmapp_prefix_process_tag_ao4_level: 
00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 4th = 0
00:09:07: cmapp_process_tag_digital: amplitude of 4th = 0
00:09:07: cmapp_process_tag_ontf: frequency 1 on time = 400
00:09:07: cmapp_process_tag_oftf: frequency 1 off time = 350
00:09:07: cmapp_process_tag_onts: frequency 2 on time = 225
00:09:07: cmapp_process_tag_ofts: frequency 2 off time = 525
00:09:07: cmapp_process_tag_ontt: frequency 3 on time = 0
00:09:07: cmapp_process_tag_oftt: frequency 3 off time = 0
00:09:07: cmapp_process_tag_ont4: frequency 4 on time = 0
00:09:07: cmapp_process_tag_oft4: frequency 4 off time = 0
00:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 0
00:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 0
00:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 0
00:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 0
00:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 0
00:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 0
00:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 0
00:09:07: cmapp_process_tag_rct2: cadence 2 repeat count = 0
00:09:07: cmapp_process_tag_rct3: cadence 3 repeat count = 0
00:09:07: cmapp_process_tag_rct4: cadence 4 repeat count = 0
! end
The 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 = 6544CFA8 
The 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=0
The 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 2
Table 42 describes the significant fields shown in the displays.

Table 42 debug ccm-manager Field Descriptions

Field

Description

nn:nn:nn:

Timestamp time in hours (military format), minutes, and seconds that indicates when the Cisco CallManager event occurred.

cmapp_ error message:

The Cisco CallManager routine in which the error event occurred.

LocaleName

Region name, such as United Kingdom.

low frequency level

DTMF low frequency.

high frequency level

DTMF high frequency.

operation

Special operations, such as uLaw.
Related Commands

Command

Description

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

12.1(1)T

This command was introduced.

12.1.(3)T

The output of this command was changed.

12.2(2)XA

Support was added for the Cisco AS5350 and Cisco AS5400 universal gateways.

12.2(2)XB1

This command was implemented on the Cisco AS5850 universal gateway.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T and implemented on Cisco 7200 series routers.

12.2(11)T

This command was integrated into Cisco IOS Release 12.2(11)T. Support for the Cisco AS5300 universal access server, Cisco AS5350, Cisco AS5400, and Cisco AS5850 universal gateway is not included in this release.

Usage Guidelines

The debug ccsip all command enables the following SIP debug commands:

•debug ccsip events

•debug ccsip error

•debug ccsip states

•debug ccsip messages

•debug ccsip calls

Examples

The following example displays debug output from one side of the call:
Router# debug ccsip all
All SIP call tracing enabled
Router1#
*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.0
Via: SIP/2.0/UDP  166.34.245.230:54113
From: "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 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Cisco-Guid: 2881152943-2184249548-0-483039712
User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Max-Forwards: 6
Timestamp: 731427042
Contact: <sip:3660110@166.34.245.230:5060;user=phone>
Expires: 180
Content-Type: application/sdp
Content-Length: 137
v=0
o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230
s=SIP Call
t=0 0
c=IN IP4 166.34.245.230
m=audio 20208 RTP/AVP 0
*Mar  6 14:10:42: Received: 
SIP/2.0 100 Trying
Via: SIP/2.0/UDP  166.34.245.230:54113
From: "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 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Timestamp: 731427042
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Content-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 Ringing
Via: SIP/2.0/UDP  166.34.245.230:54113
From: "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 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Timestamp: 731427042
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Content-Type: application/sdp
Content-Length: 137
v=0
o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231
s=SIP Call
t=0 0
c=IN IP4 166.34.245.231
m=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 :160
Inband 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 OK
Via: SIP/2.0/UDP  166.34.245.230:54113
From: "3660110" <sip:3660110@166.34.245.230>
To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7F
Date: Mon, 08 Mar 1993 22:36:40 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Timestamp: 731427042
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Contact: <sip:3660210@166.34.245.231:5060;user=phone>
CSeq: 101 INVITE
Content-Type: application/sdp
Content-Length: 137
v=0
o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231
s=SIP Call
t=0 0
c=IN IP4 166.34.245.231
m=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) : 0x624CFEF8
         State of The Call        : STATE_ACTIVE
         TCP Sockets Used         : NO
         Calling Number           : 3660110
         Called Number            : 3660210
         Negotiated Codec         : g711ulaw
         Source IP Address (Media): 166.34.245.230
         Source IP Port    (Media): 20208
         Destn  IP Address (Media): 166.34.245.231
         Destn  IP Port    (Media): 20038
         Destn SIP Addr (Control) : 166.34.245.231
         Destn SIP Port (Control) : 5060
         Destination 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.0
Via: SIP/2.0/UDP  166.34.245.230:54113
From: "3660110" <sip:3660110@166.34.245.230>
To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7F
Date: Sat, 06 Mar 1993 19:10:42 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Max-Forwards: 6
Content-Type: application/sdp
Content-Length: 137
CSeq: 101 ACK
v=0
o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230
s=SIP Call
t=0 0
c=IN IP4 166.34.245.230
m=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.0
Via: SIP/2.0/UDP  166.34.245.231:54835
From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7F
To: "3660110" <sip:3660110@166.34.245.230>
Date: Mon, 08 Mar 1993 22:36:44 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Max-Forwards: 6
Timestamp: 731612207
CSeq: 101 BYE
Content-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 OK
Via: SIP/2.0/UDP  166.34.245.231:54835
From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7F
To: "3660110" <sip:3660110@166.34.245.230>
Date: Sat, 06 Mar 1993 19:10:50 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Timestamp: 731612207
Content-Length: 0
CSeq: 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) : 0x624CFEF8
         State of The Call        : STATE_DEAD
         TCP Sockets Used         : NO
         Calling Number           : 3660110
         Called Number            : 3660210
         Negotiated Codec         : g711ulaw
         Source IP Address (Media): 166.34.245.230
         Source IP Port    (Media): 20208
         Destn  IP Address (Media): 166.34.245.231
         Destn  IP Port    (Media): 20038
         Destn SIP Addr (Control) : 166.34.245.231
         Destn SIP Port (Control) : 5060
         Destination Name         : 166.34.245.231
*Mar  6 14:10:50: 
        Disconnect Cause (CC)    : 16
        Disconnect Cause (SIP)   : 200
*Mar  6 14:10:50: udpsock_close_connect: Socket fd: 1 closed for connid 1 with remote 
port: 5060
The following example displays debut output from the other side of the call:
Router# debug ccsip all
All SIP call tracing enabled
3660-2#
*Mar  8 17:36:40: Received: 
INVITE sip:3660210@166.34.245.231;user=phone;phone-context=unknown SIP/2.0
Via: SIP/2.0/UDP  166.34.245.230:54113
From: "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 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Cisco-Guid: 2881152943-2184249548-0-483039712
User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Max-Forwards: 6
Timestamp: 731427042
Contact: <sip:3660110@166.34.245.230:5060;user=phone>
Expires: 180
Content-Type: application/sdp
Content-Length: 137
v=0
o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230
s=SIP Call
t=0 0
c=IN IP4 166.34.245.230
m=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 an
incoming call
*Mar  8 17:36:40: sact_idle_new_message_invite: Negotiated Codec      : g711ulaw, bytes 
:160
Preferred 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 Trying
Via: SIP/2.0/UDP  166.34.245.230:54113
From: "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 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Timestamp: 731427042
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Content-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 Ringing
Via: SIP/2.0/UDP  166.34.245.230:54113
From: "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 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Timestamp: 731427042
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Content-Type: application/sdp
Content-Length: 137
v=0
o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231
s=SIP Call
t=0 0
c=IN IP4 166.34.245.231
m=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 OK
Via: SIP/2.0/UDP  166.34.245.230:54113
From: "3660110" <sip:3660110@166.34.245.230>
To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7F
Date: Mon, 08 Mar 1993 22:36:40 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Timestamp: 731427042
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Contact: <sip:3660210@166.34.245.231:5060;user=phone>
CSeq: 101 INVITE
Content-Type: application/sdp
Content-Length: 137
v=0
o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231
s=SIP Call
t=0 0
c=IN IP4 166.34.245.231
m=audio 20038 RTP/AVP 0
*Mar  8 17:36:44: Received: 
ACK sip:3660210@166.34.245.231:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP  166.34.245.230:54113
From: "3660110" <sip:3660110@166.34.245.230>
To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7F
Date: Sat, 06 Mar 1993 19:10:42 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Max-Forwards: 6
Content-Type: application/sdp
Content-Length: 137
CSeq: 101 ACK
v=0
o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230
s=SIP Call
t=0 0
c=IN IP4 166.34.245.230
m=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) : 0x624D8CCC
         State of The Call        : STATE_ACTIVE
         TCP Sockets Used         : NO
         Calling Number           : 3660110
         Called Number            : 3660210
         Negotiated Codec         : g711ulaw
         Source IP Address (Media): 166.34.245.231
         Source IP Port    (Media): 20038
         Destn  IP Address (Media): 166.34.245.230
         Destn  IP Port    (Media): 20208
         Destn SIP Addr (Control) : 166.34.245.230
         Destn SIP Port (Control) : 5060
         Destination 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.0
Via: SIP/2.0/UDP  166.34.245.231:54835
From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7F
To: "3660110" <sip:3660110@166.34.245.230>
Date: Mon, 08 Mar 1993 22:36:44 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Max-Forwards: 6
Timestamp: 731612207
CSeq: 101 BYE
Content-Length: 0
*Mar  8 17:36:47: Received: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP  166.34.245.231:54835
From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27D3FCA8-C7F
To: "3660110" <sip:3660110@166.34.245.230>
Date: Sat, 06 Mar 1993 19:10:50 GMT
Call-ID: ABBAE7AF-823100CE-0-1CCAA69C@172.18.192.194
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Timestamp: 731612207
Content-Length: 0
CSeq: 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) : 0x624D8CCC
         State of The Call        : STATE_DEAD
         TCP Sockets Used         : NO
         Calling Number           : 3660110
         Called Number            : 3660210
         Negotiated Codec         : g711ulaw
         Source IP Address (Media): 166.34.245.231
         Source IP Port    (Media): 20038
         Destn  IP Address (Media): 166.34.245.230
         Destn  IP Port    (Media): 20208
         Destn SIP Addr (Control) : 166.34.245.230
         Destn SIP Port (Control) : 5060
         Destination Name         : 166.34.245.230
*Mar  8 17:36:47: 
        Disconnect Cause (CC)    : 16
        Disconnect Cause (SIP)   : 200
*Mar  8 17:36:47: udpsock_close_connect: Socket fd: 1 closed for connid 1 with remote 
port: 5060
Related Commands

Command

Description

debug ccsip calls

Shows all SIP SPI call tracing.

debug ccsip error

Shows SIP SPI errors.

debug ccsip events

Shows all SIP SPI events tracing.

debug ccsip info

Shows all SIP SPI message tracing.

debug ccsip states

Shows all SIP SPI state tracing.

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

12.1(1)T

This command was introduced.

12.1(3)T

The output of this command was changed.

12.2(2)XA

Support was added for the Cisco AS5350 and Cisco AS5400 universal gateways.

12.2(2)XB1

This command was introduced on the Cisco AS5850 universal gateway.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T and implemented on Cisco 7200 series routers.

12.2(11)T

This command was integrated into Cisco IOS Release 12.2(11)T. Support for the Cisco AS5300 universal access server, Cisco AS5350, Cisco AS5400, and Cisco AS5850 universal gateway is not included in this release.

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 calls
SIP Call statistics tracing is enabled
Router1#
*Mar  6 14:12:33: The Call Setup Information is :
        Call Control Block (CCB) : 0x624D078C
         State of The Call        : STATE_ACTIVE
         TCP Sockets Used         : NO
         Calling Number           : 3660110
         Called Number            : 3660210
         Negotiated Codec         : g711ulaw
         Source IP Address (Media): 166.34.245.230
         Source IP Port    (Media): 20644
         Destn  IP Address (Media): 166.34.245.231
         Destn  IP Port    (Media): 20500
         Destn SIP Addr (Control) : 166.34.245.231
         Destn SIP Port (Control) : 5060
         Destination Name         : 166.34.245.231
*Mar  6 14:12:40: The Call Setup Information is :
        Call Control Block (CCB) : 0x624D078C
         State of The Call        : STATE_DEAD
         TCP Sockets Used         : NO
         Calling Number           : 3660110
         Called Number            : 3660210
         Negotiated Codec         : g711ulaw
         Source IP Address (Media): 166.34.245.230
         Source IP Port    (Media): 20644
         Destn  IP Address (Media): 166.34.245.231
         Destn  IP Port    (Media): 20500
         Destn SIP Addr (Control) : 166.34.245.231
         Destn SIP Port (Control) : 5060
         Destination Name         : 166.34.245.231
*Mar  6 14:12:40: 
        Disconnect Cause (CC)    : 16
        Disconnect Cause (SIP)   : 200
The following example displays debug output from the other side of the call:
Router2# debug ccsip calls
SIP Call statistics tracing is enabled
Router2#
*Mar  8 17:38:31: The Call Setup Information is :
        Call Control Block (CCB) : 0x624D9560
         State of The Call        : STATE_ACTIVE
         TCP Sockets Used         : NO
         Calling Number           : 3660110
         Called Number            : 3660210
         Negotiated Codec         : g711ulaw
         Source IP Address (Media): 166.34.245.231
         Source IP Port    (Media): 20500
         Destn  IP Address (Media): 166.34.245.230
         Destn  IP Port    (Media): 20644
         Destn SIP Addr (Control) : 166.34.245.230
         Destn SIP Port (Control) : 5060
         Destination Name         : 166.34.245.230
*Mar  8 17:38:38: The Call Setup Information is:
        Call Control Block (CCB) : 0x624D9560
         State of The Call        : STATE_DEAD
         TCP Sockets Used         : NO
         Calling Number           : 3660110
         Called Number            : 3660210
         Negotiated Codec         : g711ulaw
         Source IP Address (Media): 166.34.245.231
         Source IP Port    (Media): 20500
         Destn  IP Address (Media): 166.34.245.230
         Destn  IP Port    (Media): 20644
         Destn SIP Addr (Control) : 166.34.245.230
         Destn SIP Port (Control) : 5060
         Destination Name         : 166.34.245.230
*Mar  8 17:38:38: 
        Disconnect Cause (CC)    : 16
        Disconnect Cause (SIP)   : 200
Related Commands

Command

Description

debug ccsip all

Enables all SIP-related debugging.

debug ccsip error

Shows SIP SPI errors.

debug ccsip events

Shows all SIP SPI events tracing.

debug ccsip info

Shows all SIP SPI message tracing.

debug ccsip states

Shows all SIP SPI state tracing.

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

12.1(1)T

This command was introduced.

12.2(2)XA

Support was added for the Cisco AS5350 and Cisco AS5400 universal gateways.

12.2(2)XB1

This command was implemented on the Cisco AS5850 universal gateway.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T and implemented on Cisco 7200 series routers.

12.2(11)T

This command was integrated into Cisco IOS Release 12.2(11)T. Support for the Cisco AS5300 universal access server, Cisco AS5350, Cisco AS5400, and Cisco AS5850 universal gateway is not included in this release.

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 error
SIP Call error tracing is enabled
Router1#
*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 :160
Inband 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: 5060
The following example displays debug output from the other side of the call:
Router2# debug ccsip error
SIP Call error tracing is enabled
Router2#
*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 an
incoming call
*Mar  8 17:42:39: sact_idle_new_message_invite: Negotiated Codec      : g711ulaw, bytes 
:160
Preferred 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: 5060
Related Commands

Command

Description

debug ccsip all

Enables all SIP-related debugging.

debug ccsip calls

Shows all SIP SPI call tracing.

debug ccsip events

Shows all SIP SPI events tracing.

debug ccsip info

Shows all SIP SPI message tracing.

debug ccsip states

Shows all SIP SPI state tracing.

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

12.1(1)T

This command was introduced.

12.2(2)XA

Support was added for the Cisco AS5350 and Cisco AS5400 universal gateways.

12.2(2)XB1

This command was introduced on the Cisco AS5850 universal gateway.

12.2(11)T

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

12.2(15)T

Much of the information formerly found in the output of the debug ccsip events command is now reported in the output of the debug ccsip info and debug ccsip media commands. The debug ccsip events command now displays only the debugging information specifically related to SIP events.

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 This command is intended for use by Cisco technicians only.

Examples

The following is sample output from the debug ccsip events command for a Cisco 3660:
Router# debug ccsip events
SIP Call events tracing is enabled 
Router# 
Nov 15 18:20:25.779: Queued event from SIP SPI : SIPSPI_EV_CC_CALL_SETUP 
Nov 15 18:20:25.779: Queued event from SIP SPI : SIPSPI_EV_CREATE_CONNECTION 
Nov 15 18:20:25.783: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE 
Nov 15 18:20:25.815: Queued event from SIP SPI : SIPSPI_EV_CREATE_CONNECTION 
Nov 15 18:20:25.819: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE 
Nov 15 18:20:28.339: Queued event from SIP SPI : SIPSPI_EV_CLOSE_CONNECTION 
Nov 15 18:20:28.339: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE 
Nov 15 18:20:50.844: Queued event from SIP SPI : SIPSPI_EV_CLOSE_CONNECTION 
Nov 15 18:20:50.844: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE 
Nov 15 18:20:50.848: Queued event from SIP SPI : SIPSPI_EV_CC_CALL_DISCONNECT 
Related Commands

Command

Description

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

Release

Modification

12.2(15)T

This command was introduced.

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 This command is intended for use by Cisco technicians only.

Examples

The following is sample output from the debug ccsip info command for a Cisco 3660:
Router# debug ccsip info 
SIP Call info tracing is enabled 
Router# 
Nov 15 18:19:22.670: ****Adding to UAC table
Nov 15 18:19:22.670: adding call id E to table
Nov 15 18:19:22.670: CCSIP-SPI-CONTROL: act_idle_call_setup 
Nov 15 18:19:22.670: act_idle_call_setup:Not using Voice Class Codec
Nov 15 18:19:22.670: act_idle_call_setup: preferred_codec set[0] type :g729r8 bytes: 20 
Nov 15 18:19:22.670: sipSPICopyPeerDataToCCB: From CLI: Modem NSE payload = 100, 
Passthrough = 0,Modem relay = 0, Gw-Xid = 1 
SPRT latency 200, SPRT Retries = 12, Dict Size = 1024 
String Len = 32, Compress dir = 3 
Nov 15 18:19:22.670: ****Deleting from UAC table
Nov 15 18:19:22.670: ****Adding to UAC table
Nov 15 18:19:22.670: sipSPIUsetBillingProfile: sipCallId for billing records = 
20A40C3B-D92C11D5-8015E1CC-C91F3F10@12.18.195.49 
Nov 15 18:19:22.674: CCSIP-SPI-CONTROL: act_idle_connection_created 
Nov 15 18:19:22.674: CCSIP-SPI-CONTROL: act_idle_connection_created: Connid(1) created to 
172.18.193.190:5060, local_port 56981 
Nov 15 18:19:22.674: CCSIP-SPI-CONTROL: sipSPIOutgoingCallSDP 
Nov 15 18:19:22.674: convert_codec_bytes_to_ptime: Values :Codec: g729r8 codecbytes :20, 
ptime: 10
Nov 15 18:19:22.674: sip_generate_sdp_xcaps_list: Modem Relay disabled. X-cap not needed
Nov 15 18:19:22.674: sipSPIAddLocalContact 
Nov 15 18:19:22.674: sip_stats_method 
Nov 15 18:19:22.690: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 
172.18.193.190:5060 
Nov 15 18:19:22.690: CCSIP-SPI-CONTROL: act_sentinvite_new_message 
Nov 15 18:19:22.690: CCSIP-SPI-CONTROL: sipSPICheckResponse 
Nov 15 18:19:22.690: sip_stats_status_code 
Nov 15 18:19:22.690: Roundtrip delay 16 milliseconds for method INVITE
Nov 15 18:19:22.706: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 
172.18.193.190:5060 
Nov 15 18:19:22.706: CCSIP-SPI-CONTROL: act_recdproc_new_message 
Nov 15 18:19:22.706: CCSIP-SPI-CONTROL: sipSPICheckResponse 
Nov 15 18:19:22.706: sip_stats_status_code 
Nov 15 18:19:22.706: Roundtrip delay 32 milliseconds for method INVITE
Nov 15 18:19:22.706: sipSPIGetSdpBody : Parse incoming session description 
Nov 15 18:19:22.706: HandleSIP1xxSessionProgress: Content-Disposition received in 18x 
response:session;handling=required 
Nov 15 18:19:22.706: sipSPIDoMediaNegotiation: number of m lines is 1 
Nov 15 18:19:22.706: sipSPIDoAudioNegotiation: Codec (g729r8) Negotiation Successful on 
Static Payload
Nov 15 18:19:22.706: sipSPIDoPtimeNegotiation: One ptime attribute found - value:10 
Nov 15 18:19:22.706: convert_ptime_to_codec_bytes: Values :Codec: g729r8 ptime :10, 
codecbytes: 20
Nov 15 18:19:22.710: convert_codec_bytes_to_ptime: Values :Codec: g729r8 codecbytes :20, 
ptime: 10
Nov 15 18:19:22.710: sipSPIDoDTMFRelayNegotiation: m-line index 1 
Nov 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 = 0 
Nov 15 18:19:22.710: sip_do_nse_negotiation: NSE Payload 100 found in SDP 
Nov 15 18:19:22.710: sip_do_nse_negotiation: Remote NSE payload = local one = 100, Use it 
Nov 15 18:19:22.710: sip_select_modem_relay_params: X-tmr not present in SDP. Disable 
modem relay 
Nov 15 18:19:22.710: sipSPIDoQoSNegotiation - SDP body with media description 
Nov 15 18:19:22.710: ccsip_process_response_contact_record_route 
Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: ccsip_bridge: confID = 4, srcCallID = 14, 
dstCallID = 13 
Nov 15 18:19:22.710: sipSPIUupdateCcCallIds: old src/dest ccCallids: -1/-1, new src/dest 
ccCallids: 14/13 
Nov 15 18:19:22.710: sipSPIUupdateCcCallIds: old streamcallid=-1, new streamcallid=14 
Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: ccsip_caps_ind 
Nov 15 18:19:22.710: ccsip_get_rtcp_session_parameters: CURRENT VALUES: stream_callid=14, 
current_seq_num=0x1B1B 
Nov 15 18:19:22.710: ccsip_get_rtcp_session_parameters: NEW VALUES: stream_callid=14, 
current_seq_num=0x180C 
Nov 15 18:19:22.710: ccsip_caps_ind: Load DSP with negotiated codec : g729r8, Bytes=20 
Nov 15 18:19:22.710: ccsip_caps_ind: set forking flag to 0x0 
Nov 15 18:19:22.710: sipSPISetDTMFRelayMode: set DSP for dtmf-relay = 
CC_CAP_DTMF_RELAY_INBAND_VOICE_AND_OOB 
Nov 15 18:19:22.710: sip_set_modem_caps: Negotiation already Done. Set negotiated Modem 
caps 
Nov 15 18:19:22.710: sip_set_modem_caps: Modem Relay & Passthru both disabled 
Nov 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=32 
Nov 15 18:19:22.710: ccsip_caps_ind: Load DSP with codec : g729r8, Bytes=20 
Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: ccsip_caps_ack 
Nov 15 18:19:22.710: ccsip_caps_ack: set forking flag to 0x60FD1EAC 
Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: act_recdproc_connection_created 
Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: sipSPICheckSocketConnection: Connid(2) created to 
172.18.193.190:5060, local_port 51663 
Nov 15 18:19:22.714: sip_stats_method 
Nov 15 18:19:22.722: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 
172.18.193.190:5060 
Nov 15 18:19:22.722: CCSIP-SPI-CONTROL: act_recdproc_new_message 
Nov 15 18:19:22.722: CCSIP-SPI-CONTROL: sipSPICheckResponse 
Nov 15 18:19:22.722: sip_stats_status_code 
Nov 15 18:19:22.722: Roundtrip delay 48 milliseconds for method PRACK
Nov 15 18:19:24.706: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 
172.18.193.190:5060 
Nov 15 18:19:24.706: CCSIP-SPI-CONTROL: act_recdproc_new_message 
Nov 15 18:19:24.706: CCSIP-SPI-CONTROL: sipSPICheckResponse 
Nov 15 18:19:24.706: sip_stats_status_code 
Nov 15 18:19:24.706: Roundtrip delay 2032 milliseconds for method PRACK
Nov 15 18:19:24.706: sipSPIGetSdpBody : Parse incoming session description 
Nov 15 18:19:24.710: CCSIP-SPI-CONTROL: sipSPIUACSessionTimer 
Nov 15 18:19:24.710: CCSIP-SPI-CONTROL: act_recdproc_continue_200_processing 
Nov 15 18:19:24.710: CCSIP-SPI-CONTROL: act_recdproc_continue_200_processing: *** This ccb 
is the parent
Nov 15 18:19:24.710: sipSPICompareRespMediaInfo 
Nov 15 18:19:24.710: sipSPIDoMediaNegotiation: number of m lines is 1 
Nov 15 18:19:24.710: sipSPIDoAudioNegotiation: Codec (g729r8) Negotiation Successful on 
Static Payload
Nov 15 18:19:24.710: sipSPIDoPtimeNegotiation: One ptime attribute found - value:10 
Nov 15 18:19:24.710: convert_ptime_to_codec_bytes: Values :Codec: g729r8 ptime :10, 
codecbytes: 20
Nov 15 18:19:24.710: convert_codec_bytes_to_ptime: Values :Codec: g729r8 codecbytes :20, 
ptime: 10
Nov 15 18:19:24.710: sipSPIDoDTMFRelayNegotiation: m-line index 1 
Nov 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 = 0 
Nov 15 18:19:24.710: sip_do_nse_negotiation: NSE Payload 100 found in SDP 
Nov 15 18:19:24.710: sip_do_nse_negotiation: Remote NSE payload = local one = 100, Use it 
Nov 15 18:19:24.710: sip_select_modem_relay_params: X-tmr not present in SDP. Disable 
modem relay 
Nov 15 18:19:24.710: sipSPIProcessMediaChanges 
Nov 15 18:19:24.710: ccsip_process_response_contact_record_route 
Nov 15 18:19:24.710: CCSIP-SPI-CONTROL: sipSPIProcess200OKforinvite 
Nov 15 18:19:24.710: sip_stats_method 
Nov 15 18:19:24.710: udpsock_close_connect: Socket fd: 1 closed for connid 1 with remote 
port: 5060 
Nov 15 18:19:37.479: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 
172.18.193.190:52180 
Nov 15 18:19:37.483: ****Found CCB in UAC table
Nov 15 18:19:37.483: CCSIP-SPI-CONTROL: act_active_new_message 
Nov 15 18:19:37.483: CCSIP-SPI-CONTROL: sact_active_new_message_request 
Nov 15 18:19:37.483: sip_stats_method 
Nov 15 18:19:37.483: sip_stats_status_code 
Nov 15 18:19:37.483: CCSIP-SPI-CONTROL: sipSPIInitiateCallDisconnect : Initiate call 
disconnect(16) for outgoing call 
Nov 15 18:19:37.483: udpsock_close_connect: Socket fd: 2 closed for connid 2 with remote 
port: 5060 
Nov 15 18:19:37.483: CCSIP-SPI-CONTROL: act_disconnecting_disconnect 
Nov 15 18:19:37.483: CCSIP-SPI-CONTROL: sipSPICallCleanup 
Nov 15 18:19:37.483: sipSPIIcpifUpdate :CallState: 4 Playout: 10230 DiscTime:1745148 
ConnTime 1743871
Nov 15 18:19:37.483: ****Deleting from UAC table
Nov 15 18:19:37.483: Removing call id E
Nov 15 18:19:37.483: freeing ccb 63330954
Related Commands

Command

Description

debug ccsip all

Enables all SIP-related debugging.

debug ccsip events

Enables tracing of events that are specific to SIP SPI.

debug ccsip media

Enables tracing of SIP call media streams.

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

Release

Modification

12.2(15)T

This command was introduced.

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 This command is intended for use by Cisco technicians only.

Examples

The following is sample output from the debug ccsip media command for a Cisco 3660:
Router# debug ccsip media 
SIP Call media tracing is enabled 
Router# 
Nov 15 18:19:53.835: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49 
Nov 15 18:19:53.835: sipSPIReserveRtpPort: reserved port 16500 for stream 1 
Nov 15 18:19:53.867: sipSPIReplaceSDP 
Nov 15 18:19:53.871: sipSPICopySdpInfo 
Nov 15 18:19:53.871: sipSPIUpdCallWithSdpInfo: 
Preferred Codec : g729r8, bytes :20 
Preferred DTMF relay : inband-voice 
Preferred NTE payload : 101 
Early Media : No 
Delayed Media : No 
Bridge Done : No 
New Media : No 
DSP DNLD Reqd : No
Nov 15 18:19:53.871: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49 
Nov 15 18:19:53.871: sipSPIUpdCallWithSdpInfo: 
M-line Index : 1 
State : STREAM_ADDING (3) 
Callid : -1 
Negotiated Codec : g729r8, bytes :20 
Negotiated DTMF relay : inband-voice 
Negotiated NTE payload : 0 
Media Srce Addr/Port : 172.18.195.49:16500 
Media Dest Addr/Port : 172.18.193.190:19148
Nov 15 18:19:53.871: sipSPIProcessRtpSessions 
Nov 15 18:19:53.871: sipSPIAddStream: Adding stream 1 (callid 16) to the VOIP RTP library 
Nov 15 18:19:53.871: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49 
Nov 15 18:19:53.871: sipSPIUpdateRtcpSession: for m-line 1 
Nov 15 18:19:53.871: sipSPIUpdateRtcpSession: rtcp_session info 
laddr = 172.18.195.49, lport = 16500, raddr = 172.18.193.190, rport=19148 
Nov 15 18:19:53.871: sipSPIUpdateRtcpSession: No rtp session, creating a new one
Nov 15 18:19:53.871: sipSPISetStreamInfo: num_streams = 1 
Nov 15 18:19:53.871: sipSPISetStreamInfo: adding stream type 0 from mline 1 
Nov 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: sipSPICompareSDP 
Nov 15 18:19:55.555: sipSPICompareStreams: stream 1 dest_port: old=19148 new=19148 
Nov 15 18:19:55.555: sipSPICompareStreams: Flags set for stream 1: RTP_CHANGE=No 
CAPS_CHANGE=No 
Nov 15 18:19:55.555: sipSPICompareSDP: Flags set for call: NEW_MEDIA=No DSPDNLD_REQD=No 
Nov 15 18:19:55.555: sipSPIReplaceSDP 
Nov 15 18:19:55.555: sipSPICopySdpInfo 
Nov 15 18:19:55.555: sipSPIUpdCallWithSdpInfo: 
Preferred Codec : g729r8, bytes :20 
Preferred DTMF relay : inband-voice 
Preferred NTE payload : 101 
Early Media : No 
Delayed Media : No 
Bridge Done : Yes 
New Media : No 
DSP DNLD Reqd : No
Nov 15 18:19:55.555: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49 
Nov 15 18:19:55.555: sipSPIUpdCallWithSdpInfo: 
M-line Index : 1 
State : STREAM_ACTIVE (3) 
Callid : 16 
Negotiated Codec : g729r8, bytes :20 
Negotiated DTMF relay : inband-voice 
Negotiated NTE payload : 0 
Media Srce Addr/Port : 172.18.195.49:16500 
Media Dest Addr/Port : 172.18.193.190:19148
Related Commands

Command

Description

debug ccsip all

Enables all SIP-related debugging.

debug ccsip events

Enables tracing of events that are specific to SIP SPI.

debug ccsip info

Enables tracing of general SIP SPI events.

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

12.1(1)T

This command was introduced.

12.1.(3)T

The output of this command was changed.

12.2(2)XA

Support was added for the Cisco AS5350 and Cisco AS5400 universal gateways.

12.2(2)XB1

This command was implemented on the Cisco AS5850 universal gateway.

12.2(8)T

This command was implemented on Cisco 7200 series routers.

12.2(11)T

This command was integrated into Cisco IOS Release 12.2(11)T. Support for the Cisco AS5300 universal access server, Cisco AS5350, Cisco AS5400, and Cisco AS5850 universal gateway is not included in this release.

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 messages
SIP Call messages tracing is enabled
Router1#
*Mar  6 14:19:14: Sent: 
INVITE sip:3660210@166.34.245.231;user=phone;phone-context=unknown SIP/2.0
Via: SIP/2.0/UDP  166.34.245.230:55820
From: "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 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Cisco-Guid: 2881152943-2184249568-0-483551624
User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Max-Forwards: 6
Timestamp: 731427554
Contact: <sip:3660110@166.34.245.230:5060;user=phone>
Expires: 180
Content-Type: application/sdp
Content-Length: 138
v=0
o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230
s=SIP Call
t=0 0
c=IN IP4 166.34.245.230
m=audio 20762 RTP/AVP 0
*Mar  6 14:19:14: Received: 
SIP/2.0 100 Trying
Via: SIP/2.0/UDP  166.34.245.230:55820
From: "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 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Timestamp: 731427554
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Content-Length: 0
*Mar  6 14:19:14: Received: 
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP  166.34.245.230:55820
From: "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 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Timestamp: 731427554
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Content-Type: application/sdp
Content-Length: 138
v=0
o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231
s=SIP Call
t=0 0
c=IN IP4 166.34.245.231
m=audio 20224 RTP/AVP 0
*Mar  6 14:19:16: Received: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP  166.34.245.230:55820
From: "3660110" <sip:3660110@166.34.245.230>
To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357
Date: Mon, 08 Mar 1993 22:45:12 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Timestamp: 731427554
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Contact: <sip:3660210@166.34.245.231:5060;user=phone>
CSeq: 101 INVITE
Content-Type: application/sdp
Content-Length: 138
v=0
o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231
s=SIP Call
t=0 0
c=IN IP4 166.34.245.231
m=audio 20224 RTP/AVP 0
*Mar  6 14:19:16: Sent: 
ACK sip:3660210@166.34.245.231:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP  166.34.245.230:55820
From: "3660110" <sip:3660110@166.34.245.230>
To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357
Date: Sat, 06 Mar 1993 19:19:14 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Max-Forwards: 6
Content-Type: application/sdp
Content-Length: 138
CSeq: 101 ACK
v=0
o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230
s=SIP Call
t=0 0
c=IN IP4 166.34.245.230
m=audio 20762 RTP/AVP 0
*Mar  6 14:19:19: Received: 
BYE sip:3660110@166.34.245.230:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP  166.34.245.231:53600
From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357
To: "3660110" <sip:3660110@166.34.245.230>
Date: Mon, 08 Mar 1993 22:45:14 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Max-Forwards: 6
Timestamp: 731612717
CSeq: 101 BYE
Content-Length: 0
*Mar  6 14:19:19: Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP  166.34.245.231:53600
From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357
To: "3660110" <sip:3660110@166.34.245.230>
Date: Sat, 06 Mar 1993 19:19:19 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Timestamp: 731612717
Content-Length: 0
CSeq: 101 BYE
The following example show debug output from the other side of the call:
Router2# debug ccsip messages
SIP Call messages tracing is enabled
Router2#
*Mar  8 17:45:12: Received: 
INVITE sip:3660210@166.34.245.231;user=phone;phone-context=unknown SIP/2.0
Via: SIP/2.0/UDP  166.34.245.230:55820
From: "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 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Cisco-Guid: 2881152943-2184249568-0-483551624
User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Max-Forwards: 6
Timestamp: 731427554
Contact: <sip:3660110@166.34.245.230:5060;user=phone>
Expires: 180
Content-Type: application/sdp
Content-Length: 138
v=0
o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230
s=SIP Call
t=0 0
c=IN IP4 166.34.245.230
m=audio 20762 RTP/AVP 0
*Mar  8 17:45:12: Sent: 
SIP/2.0 100 Trying
Via: SIP/2.0/UDP  166.34.245.230:55820
From: "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 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Timestamp: 731427554
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Content-Length: 0
*Mar  8 17:45:12: Sent: 
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP  166.34.245.230:55820
From: "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 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Timestamp: 731427554
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
CSeq: 101 INVITE
Content-Type: application/sdp
Content-Length: 138
v=0
o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231
s=SIP Call
t=0 0
c=IN IP4 166.34.245.231
m=audio 20224 RTP/AVP 0
*Mar  8 17:45:14: Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP  166.34.245.230:55820
From: "3660110" <sip:3660110@166.34.245.230>
To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357
Date: Mon, 08 Mar 1993 22:45:12 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Timestamp: 731427554
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Contact: <sip:3660210@166.34.245.231:5060;user=phone>
CSeq: 101 INVITE
Content-Type: application/sdp
Content-Length: 138
v=0
o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231
s=SIP Call
t=0 0
c=IN IP4 166.34.245.231
m=audio 20224 RTP/AVP 0
*Mar  8 17:45:14: Received: 
ACK sip:3660210@166.34.245.231:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP  166.34.245.230:55820
From: "3660110" <sip:3660110@166.34.245.230>
To: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357
Date: Sat, 06 Mar 1993 19:19:14 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Max-Forwards: 6
Content-Type: application/sdp
Content-Length: 138
CSeq: 101 ACK
v=0
o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230
s=SIP Call
t=0 0
c=IN IP4 166.34.245.230
m=audio 20762 RTP/AVP 0
*Mar  8 17:45:17: Sent: 
BYE sip:3660110@166.34.245.230:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP  166.34.245.231:53600
From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357
To: "3660110" <sip:3660110@166.34.245.230>
Date: Mon, 08 Mar 1993 22:45:14 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Max-Forwards: 6
Timestamp: 731612717
CSeq: 101 BYE
Content-Length: 0
*Mar  8 17:45:17: Received: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP  166.34.245.231:53600
From: <sip:3660210@166.34.245.231;user=phone;phone-context=unknown>;tag=27DBC6D8-1357
To: "3660110" <sip:3660110@166.34.245.230>
Date: Sat, 06 Mar 1993 19:19:19 GMT
Call-ID: ABBAE7AF-823100E2-0-1CD274BC@172.18.192.194
Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
Timestamp: 731612717
Content-Length: 0
CSeq: 101 BYE
Related Commands

debug ccsip all

Enables all SIP-related debugging.

debug ccsip calls

Shows all SIP SPI call tracing.

debug ccsip error

Shows SIP SPI errors.

debug ccsip events

Shows all SIP SPI events tracing.

debug ccsip states

Shows all SIP SPI state tracing.

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

Release

Modification

12.2(11)T

This command was introduced.

Examples

The following example shows debug output for a single SIP call:
Router# debug ccsip preauth
SIP Call preauth tracing is enabled
Jan 23 18:43:17.898::Preauth Required
Jan 23 18:43:17.898: In sipSPISendPreauthReq for preauth_id = 86515, ccb = 67AF4E10
Jan 23 18:43:17.898: Entering rpms_proc_print_preauth_req 
Jan 23 18:43:17.898: Request = 0
Jan 23 18:43:17.898: Preauth id = 86515
Jan 23 18:43:17.898: EndPt Type  = 1
Jan 23 18:43:17.898: EndPt = 192.168.80.70
Jan 23 18:43:17.898: Resource Service = 1
Jan 23 18:43:17.898: Call_origin = answer
Jan 23 18:43:17.898: Call_type = voip
Jan 23 18:43:17.898: Calling_num = 2270001
Jan 23 18:43:17.898: Called_num = 1170001
Jan 23 18:43:17.898: Protocol  = 1
Jan 23 18:43:17.898:sipSPISendPreauthReq:Created node with preauth_id = 86515, ccb 
67AF4E10 , node 6709C280
Jan 23 18:43:17.898:rpms_proc_create_node:Created node with preauth_id = 86515 
Jan 23 18:43:17.898:rpms_proc_send_aaa_req:uid got is 466728
Jan 23 18:43:17.902:rpms_proc_preauth_response:Context is for preauth_id 86515, aaa_uid 
466728
Jan 23 18:43:17.902:rpms_proc_preauth_response:Deleting Tree node for preauth id 86515 uid 
466728
Jan 23 18:43:17.902:sipSPIGetNodeForPreauth:Preauth_id=86515
Jan 23 18:43:17.902: ccsip_spi_process_preauth_event:67AF4E10 ccb & 6709C280 node
Jan 23 18:43:17.902: In act_preauth_response:67AF4E10 ccb
Jan 23 18:43:17.902: act_preauth_response:Deleting node 6709C280 from tree 
Table 43 describes the significant fields shown in the display.

Table 43 debug ccsip preauth Field Descriptions

Field

Description

Request

Request Type—0 for preauthentication, 1 for disconnect.

Preauth id

Identifier for the preauthentication request.

EndPt Type

Call Origin End Point Type—1 for IP address, 2 for Interzone ClearToken (IZCT) value.

EndPt

Call Origin End Point Value—An IP address or IZCT value.

Resource Service

Resource Service Type—1 for Reservation, 2 for Query.

Call_origin

Answer.

Call_type

Voice over IP (VoIP).

Calling_num

Calling Party Number (CLID).

Called_num

Called Party Number (DNIS).

Protocol

0 for H.323, 1 for SIP.

function reports

Various identifiers and status reports for executed functions.

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

12.1(1)T

This command was introduced.

12.2(2)XA

Support was added for the Cisco AS5350 and Cisco AS5400 universal gateways.

12.2(2)XB1

This command was implemented on the Cisco AS5850 universal gateway.

12.2(8)T

This command was implemented on Cisco 7200 series routers.

12.2(11)T

This command was integrated into Cisco IOS Release 12.2(11)T. Support for the Cisco AS5300 universal access server, Cisco AS5350, Cisco AS5400, and Cisco AS5850 universal gateway is not included in this release.

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 states
SIP Call states tracing is enabled
Router1#
*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_CONNECTION
Related Commands

Command

Description

debug ccsip all

Enables all SIP-related debugging.

debug ccsip calls

Shows all SIP SPI call tracing.

debug ccsip error

Shows SIP SPI errors.

debug ccsip events

Shows all SIP SPI events tracing.

debug ccsip info

Shows all SIP SPI message tracing.

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

12.3(8)T

This command was introduced.

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 
layer
1w1d: //18/8E16980D800A/SIP/Transport/sipSPIGetSwitchTransportFlag: Return the Global 
configuration, Switch Transport is TRUE
1w1d: //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=0x614FAB58
1w1d: //18/8E16980D800A/SIP/Transport/sipSPITransportSendMessage: Proceedable for sending 
msg immediately
1w1d: //18/8E16980D800A/SIP/Transport/sipTransportLogicSendMsg: switch transport is 1
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportGetInterfaceMtuSize: MTU size for remote 
address 172.18.194.183 is 500
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportVerifyMsgForMTUThreshold: Interface MTU 
Size 500, Msg Size 1096
1w1d: //18/8E16980D800A/SIP/Transport/sipTransportLogicSendMsg: Switching msg=0x64082D50 
transport UDP->TCP
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportSetAgeingTimer: Aging timer initiated 
for holder=0x64084058,addr=172.18.194.183
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipCreateConnHolder: Created new holder=0x64084058, 
addr=172.18.194.183
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportPostRequestConnection: Posting TCP conn 
create request for addr=172.18.194.183, port=5060, context=0x64128D5C
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportSetConnWaitTimer: Wait timer set for 
connection=0x64129BF4,addr=172.18.194.183, port=5060
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipCreateConnInstance: Created new initiated 
conn=0x64129BF4, connid=-1, addr=172.18.194.183, port=5060, transport=tcp
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipConnectionManagerProcessConnCreated: 
gConnTab=0x64128D5C, addr=172.18.194.183, port=5060, connid=1, transport=tcp
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipInstanceHandleConnectionCreated: Moving 
connection=0x64129BF4, connid=1state to pending
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWConnectionCreated: 
context=0x64128D5C
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipConnectionManagerProcessConnCreated: 
gConnTab=0x64128D5C, addr=172.18.194.183, port=5060, connid=1, transport=tcp
1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportPostSendMessage: Posting send for 
msg=0x64082D50, addr=172.18.194.183, port=5060, connId=1 for TCP
.
.
.
Table 44 describes the significant fields shown in the display.

Table 44 debug ccsip transport Field Descriptions

Field

Description

Sending Invite to the transport layer

Indicates that the SIP signaling state machine has invoked transport layer operations such as transport arbitration logic and the connection management interface.

switch transport is 1

Indicates that the gateway has been provisioned to enable the transport switching functionality based on the message size. 1 is true and 0 is false.

MTU size for remote address

Indicates that the bound outgoing Ethernet interface that sends the message to the given remote address is configured for an MTU size of the indicated value.

Interface MTU Size 500, Msg Size 1096

Indicates that the size of the message is larger than the size of the MTU; thus transport switching (from UDP to TCP) should be enabled.

Switching msg=... transport UDP->TCP

Indicates that transport switching from UDP to TCP is occurring for the handled message because of the large size of the message.

Aging timer initiated for holder

Indicates that the connection algorithm is started; that is, the counter begins to age out the TCP or UDP connection if inactivity occurs.

Posting TCP conn create request

Indicates a request for a TCP connection from a lower TCP process.

sipSPITransportSendMessage:msg=0x64082D50, addr=...transport=1, switch=1, callBack=0x614FAB58

Indicates all the transport related attributes that the SIP signaling state machine originally gives to the transport layer to send out the message. The attributes are:

•transport: 1 for UDP; 2 for TCP.

•switch (switching transport enabled or disabled for large messages): 1 for enabled; 0 for disabled.

Posting send for msg=0x64082D50, addr=...for TCP

Indicates that all transport and connection related operations are complete. The message is sent out on the network targeted to the given address, port, and transport.

Related Commands

Command

Description

debug ccsip all

Enables all SIP-related debugging.

debug ccsip info

Enables tracing of general SIP SPI information.

transport switch

Enables switching between UDP and TCP transport mechanisms globally for large SIP messages.

voice-class sip transport switch

Enables switching between UDP and TCP transport mechanisms for large SIP messages for a specific dial peer.

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

Release

Modification

11.3(1)MA

This command was introduced on the Cisco MC3810 networking device.

12.0(7)XK

This command was implemented on the Cisco 3600 series router.

12.1(2)T

This command was integrated into Cisco IOS Release 12.1(2)T.

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-debug
2w2d: ccswvoice: callID 529927 pvcid -1 cid -1 state NULL event O/G SETUP
2w2d: ccswvoice_out_callinit_setup: callID 529927 using pvcid 1 cid 15
2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state O/G INIT event I/C PROC
2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state O/G PROC event I/C 
ALERTccfrf11_caps_ind: codec(preferred) = 1
2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state O/G ALERT event I/C CONN
2w2d: ccswvoice_bridge_drop: dropping bridge calls src 529927 dst 529926 pvcid 1 cid 15 
state ACTIVE
2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state ACTIVE event O/G REL
2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state RELEASE event I/C RELCOMP
2w2d: ccswvo_store_call_history_entry: cause=10 tcause=10    cause_text=normal call 
clearing.
Related Commands

Command

Description

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

Release

Modification

12.0(3)XG

This command was introduced on the Cisco 2600 and Cisco 3600 series routers.

12.0(4)T

This command was integrated into Cisco IOS Release 12.0(4)T.

12.0(7)XK

This command was implemented on the Cisco MC3810 networking device.

12.1(2)T

This command was integrated into Cisco IOS Release 12.1(2)T.

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-debug
CALL TEARDOWN:
3640_vofr(config-voiceport)#
*Mar  1 03:02:08.719:ccswvofr_bridge_drop:dropping bridge calls src 17 dst 16 dlci 100
      cid 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=22 
      cause_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 CONN
ccfrf11_caps_ind:codec(preferred) = 0
Related Commands

Command

Description

debug cch323

Displays the ccfrf11 function calls during call setup and teardown.

debug ccsw voice vo-debug

Displays the ccswvoice function calls during call setup and teardown.

debug vtsp session

Displays the first 10 bytes (including header) of selected VoFR subframes for the interface.

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

Release

Modification

12.0(3)XG

This command was introduced on the Cisco 2600 and Cisco 3600 series routers.

12.0(4)T

This command was integrated into Cisco IOS Release 12.0(4)T.

12.0(7)XK

This command was implemented on the Cisco MC3810 networking device.

12.1(2)T

This command was integrated into Cisco IOS Release 12.1(2)T.

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-session
CALL 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 RELCOMP
3640_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 CONN
3640_vofr(config-voiceport)#
Related Commands

Command

Description

debug cch323

Displays the ccfrf11 function calls during call setup and teardown.

debug call rsvp-sync events

Displays events that occur during RSVP setup.

debug vtsp session

Displays the first 10 bytes (including header) of selected VoFR subframes for the interface.

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

Release

Modification

11.3(1)MA

This command was introduced on the Cisco MC3810 networking device.

12.0(7)XK

This command was implemented on the Cisco 3600 series router.

12.1(2)T

This command was integrated into Cisco IOS Release 12.1(2)T.

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-session
2w2d: ccswvoice: callID 529919 pvcid -1 cid -1 state NULL event O/G SETUP
2w2d: ccswvoice: callID 529919 pvcid 1 cid 11 state O/G INIT event I/C PROC
2w2d: ccswvoice: callID 529919 pvcid 1 cid 11 state O/G PROC event I/C ALERT
2w2d: ccswvoice: callID 529919 pvcid 1 cid 11 state O/G ALERT event I/C CONN
2w2d: ccswvoice: callID 529919 pvcid 1 cid 11 state ACTIVE event O/G REL
2w2d: ccswvoice: callID 529919 pvcid 1 cid 11 state RELEASE event I/C RELCOMP
Related Commands

Command

Description

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

detail

Displays when applications register or become unregistered with CDAPI, when calls are added or deleted from the CDAPI routing table, and when CDAPI messages are created and freed.

events

Displays the events passing between CDAPI and an application or signalling stack.

Defaults

Debugging output is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(6)T

This command was introduced.

12.1(5)XM2

This command was implemented on the Cisco AS5350 and Cisco AS5400.

12.3(2)T

This command was integrated into Cisco IOS Release 12.3(2)T. This command was enhanced to show V.110 call types.

12.3(4)T

This command was enhanced to show V.120 call types.

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:

•56 kbps

•64 kbps

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 detail
Sep 26 19:12:25.327:MGCP Packet received from 10.0.44.109:2427-
CRCX 6318 s7/ds1-0/24 MGCP 1.0
C:111
M:nas/data
L:b:64, nas/bt:v.110, nas/cdn:234567
R:nas/au, nas/ax,nas/of, nas/crq
X:101
Sep 26 19:12:25.327:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0
Sep 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 CSM
Sep 26 19:12:25.331:CDAPI:cdapi_create_msg():CDAPI Pool Count:958,
router# Raw Length = 0
Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:959
Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:960
Sep 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  Alert
I:64524608
Sep 26 19:12:25.339:CDAPI:cdapi_crea
router#te_msg():CDAPI Pool Count:959, Raw Length = 0
Sep 26 19:12:25.339:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:25.339:CDAPI:cdapi_free_msg():CDAPI Pool Count:960
router#
Sep 26 19:12:33.223:MGCP Packet received from 10.0.44.109:2427-
DLCX 6319 s7/ds1-0/24 MGCP 1.0
Sep 26 19:12:33.223:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0
Sep 26 19:12:33.223:CDAPI:cdapi_create_msg():CDAPI Pool Count:958, Raw Length = 0
Sep 26 19:12:33.223:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:33.223:CDAPI:cdapi_free_msg():CDAPI Pool Count:959
Sep 26 19:12:33.227:CDAPI:cdapi_create_msg():CDAPI Pool Count:958, Raw
router# Length = 0
Sep 26 19:12:33.227:CDAPI Se7/1:23:cdapi_del_entry_callRoutingTbl() -
Sep 26 19:12:33.227:   Deleted entry for call 0x7017
Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():CDAPI Pool Count:959
Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():CDAPI Pool Count:960
Sep 26 19:12:33.227:send_mgcp_msg, MGCP Packet sent
router#to 10.0.44.109:2427 --->
Sep 26 19:12:33.227:200 6319 OK
The following partial example shows V.120 call debugging output for the debug cdapi detail command:
Router# debug cdapi detail
May 14 19:12:25.327:MGCP Packet received from 10.0.44.109:2427-
CRCX 6318 s7/ds1-0/24 MGCP 1.0
C:111
M:nas/data
L:b:64, nas/bt:v.120, nas/cdn:234567
R:nas/au, nas/ax,nas/of, nas/crq
X:101
May 14 19:12:25.327:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0
May 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 CSM
May 14 19:12:25.331:CDAPI:cdapi_create_msg():CDAPI Pool Count:958,
router# Raw Length = 0
May 14 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
May 14 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:959
May 14 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
May 14 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:960
May 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 events
Sep 26 19:14:39.027:MGCP Packet received from 10.0.44.109:2427-
CRCX 6322 s7/ds1-0/24 MGCP 1.0
C:111
M:nas/data
L:b:64, nas/bt:v.120, nas/cdn:234567
R:nas/au, nas/ax,nas/of, nas/crq
X:101
Sep 26 19:14:39.027:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONNECT_IND to CSM call = 0x7017
Sep 26 19:14:39.027:   From Appl/Stack = XCSP
Sep 26 19:14:39.027:   Call Type    = V.120
Sep 26 19:14:39.027:   B Channel    = 23
Sep 26 19:14:39.027:   dslId        = 0
Sep 26 19:14:39.027:   Idb          = 0
Sep
router#26 19:14:39.027:   BChanIdb  = 64519A14
Sep 26 19:14:39.027:   Handle       = 63CB8DF4
Sep 26 19:14:39.027:   RPA          = 6388506C
Sep 26 19:14:39.027:   Cause        = 0
Sep 26 19:14:39.027:   ApplCause    = 0
Sep 26 19:14:39.027:   ApplSpecData = 0
Sep 26 19:14:39.027:   Calling Party Number =
Sep 26 19:14:39.027:   Called Party Number = 234567
Sep 26 19:14:39.027:   Overlap = 0
Sep 26 19:14:39.027:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONNECT_RESP to XCSP call = 0x7017
Sep 26 19:14:39.027:   From Appl
router#/Stack = CSM
Sep 26 19:14:39.027:   Call Type    = MODEM
Sep 26 19:14:39.027:   B Channel    = 23
Sep 26 19:14:39.027:   dslId        = 0
Sep 26 19:14:39.027:   Idb          = 0
Sep 26 19:14:39.027:   BChanIdb     = 64519A14
Sep 26 19:14:39.027:   Handle       = 63CB8DF4
Sep 26 19:14:39.027:   RPA          = 0
Sep 26 19:14:39.027:   Cause        = 0
Sep 26 19:14:39.027:   ApplCause    = 0
Sep 26 19:14:39.027:   ApplSpecData = 0
Sep 26 19:14:39.027:   Overlap = 0
Sep 26 19:14:39.031:send_mgcp_msg, MGCP Pa
router#cket sent to 10.0.44.109:2427 --->
Sep 26 19:14:39.031:200 6322  Alert
I:64524608
Sep 26 19:14:39.039:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONN_ACT_REQ to XCSP call = 0x7017
Sep 26 19:14:39.039:   From Appl/Stack = CSM
Sep 26 19:14:39.039:   Call Type    = MODEM
Sep 26 19:14:39.039:   B Channel    = 23
Sep 26 19:14:39.039:   dslId        = 0
Sep 26 19:14:39.039:   Idb          = 0
Sep 26 19:14:39.039:   BChanIdb     = 64519A14
Sep 26 19:14:39.039:   Handle       = 63CB8DF4
Sep 26 19:14:39.039:   R
router#PA          = 0
Sep 26 19:14:39.039:   Cause        = 0
Sep 26 19:14:39.039:   ApplCause    = 0
Sep 26 19:14:39.039:   ApplSpecData = 0
Sep 26 19:14:39.039:   Overlap = 0
router#
Sep 26 19:14:48.959:MGCP Packet received from 10.0.44.109:2427-
DLCX 6323 s7/ds1-0/24 MGCP 1.0
Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_DISCONNECT_IND to CSM call = 0x7017
Sep 26 19:14:48.963:   From Appl/Stack = XCSP
Sep 26 19:14:48.963:   Call Type    = V.120
Sep 26 19:14:48.963:   B Channel    = 23
Sep 26 19:14:48.963:   dslId        = 0
Sep 26 19:14:48.963:   Idb          = 0
Sep 26 19:14:48.963:   BChanIdb     = 64519A14
Sep 26 19:14:48.963:   Handle       = 63CB8DF4
Sep 26 19:14
router#:48.963:        RPA          = 6388506C
Sep 26 19:14:48.963:   Cause        = 0
Sep 26 19:14:48.963:   ApplCause    = 0
Sep 26 19:14:48.963:   ApplSpecData = 0
Sep 26 19:14:48.963:   Overlap = 0
Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_SUBTYPE_RELEASE_REQ to XCSP call = 
0x7017
Sep 26 19:14:48.963:   From Appl/Stack = CSM
Sep 26 19:14:48.963:   Call Type    = MODEM
Sep 26 19:14:48.963:   B Channel    = 23
Sep 26 19:14:48.963:   dslId        = 0
Sep 26 19:14:48.963:   Idb          = 0
Sep 26 19:14:48
router#.963:           BChanIdb     = 64519A14
Sep 26 19:14:48.963:   Handle       = 63CB8DF4
Sep 26 19:14:48.963:   RPA          = 0
Sep 26 19:14:48.963:   Cause        = 0
Sep 26 19:14:48.963:   ApplCause    = 1
Sep 26 19:14:48.963:   ApplSpecData = 0
Sep 26 19:14:48.963:   Overlap = 0
Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_SUBTYPE_REL_COMP_IND to CSM call = 
0x7017
Sep 26 19:14:48.963:   From Appl/Stack = XCSP
Sep 26 19:14:48.963:   Call Type    = V.120
Sep 26 19:14:48.963:   B Channel    = 23
Sep 26 19:
router#14:48.963:      dslId        = 0
Sep 26 19:14:48.963:   Idb          = 0
Sep 26 19:14:48.963:   BChanIdb     = 64519A14
Sep 26 19:14:48.963:   Handle       = 63CB8DF4
Sep 26 19:14:48.963:   RPA          = 6388506C
Sep 26 19:14:48.963:   Cause        = 0
Sep 26 19:14:48.963:   ApplCause    = 0
Sep 26 19:14:48.963:   ApplSpecData = 0
Sep 26 19:14:48.963:   Overlap = 0
Sep 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 OK
Table 45 describes the significant fields shown in the displays.

Table 45 debug cdapi Field Descriptions

Field

Description

L:b:64, nas/bt

The bearer type parameter includes v.110 and v.120 for V.110 and V.120 calls.

Call Type

Call types are V.110, V.120, and modem.

Related Commands

Command

Description

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

Release

Modification

12.2(2)XC

This command was introduced.

12.2(8)BY

Keywords were made optional.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T.

Examples

The following is sample output from the debug cdma pdsn a10 ahdlc command:
Router# debug cdma pdsn a10 ahdlc errors 
ahdlc error packet display debugging is on
Router# debug cdma pdsn a10 ahdlc events
ahdlc events display debugging is on
Router#
*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 0
debug 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

errors

(Optional) Displays A10 GRE errors.

events

(Optional) Displays A10 GRE events.

packets

(Optional) Displays transmitted or received A10 GRE packets.

tunnel-key key

(Optional) Specifies the GRE key.

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

Release

Modification

12.1(3)XS

This command was introduced.

12.2(8)BY

The tunnel-key keyword was added and the existing keywords were made optional.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T.

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 1 
Router# show debug
CDMA:
  CDMA PDSN A10 GRE events debugging is on for tunnel key 1
PDSN#
*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-1
debug 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

Release

Modification

12.1(3)XS

This command was introduced.

12.2(8)BY

Keywords were made optional.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T.

Examples

The following is sample output from the debug cdma pdsn a10 ppp command:
Router# debug cdma pdsn a10 ppp errors
CDMA PDSN A10 errors debugging is on
Router# debug cdma pdsn a10 ppp events 
CDMA PDSN A10 events debugging is on
Router# debug cdma pdsn a10 ppp packets 
CDMA PDSN A10 packet debugging is on
Router# 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

errors

(Optional) Displays A11 protocol errors.

events

(Optional) Displays A11 events.

packets

(Optional) Displays transmitted or received packets.

mnid

(Optional) Specifies the ID of the mobile station.

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

Release

Modification

12.1(3)XS

This command was introduced.

12.2(8)BY

The mnid argument was added and the existing keywords were made optional.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T.

Examples

The following is sample output from the debug cdma pdsn a11 commands:
Router# debug cdma pdsn a11 errors
CDMA PDSN A11 errors debugging is on
Router# show debug
1d21h:CDMA-RP:(in) rp_msgs, code=1, status=0
1d21h:CDMA-RP:(enqueue req) type=1 homeagent=5.0.0.2 coaddr=4.0.0.1
1d21h:                   id=0xBEF750F0-0xBA53E0F lifetime=65535
1d21h:CDMA-RP:len=8, 00-00-00-00-00-00-00-F1 convert to 00000000000001
(14 digits), type=IMSI
1d21h:CDMA-RP:(req) process_rp_req, homeagent=5.0.0.2 coaddr=4.0.0.1
1d21h:               lifetime=65535 id=BEF750F0-BA53E0F
imsi=00000000000001
1d21h:CDMA-RP:(req) rp_req_create, 5.0.0.2-4.0.0.1-1 imsi=00000000000001
1d21h:CDMA-RP:(out) rp_reply session=5.0.0.2-4.0.0.1-1, lifetime=65535
1d21h:CDMA-RP:(out) setup_rp_out_msg, ha=5.0.0.2 coa=4.0.0.1 key=1
1d21h:%LINK-3-UPDOWN:Interface Virtual-Access2000, changed state to up
1d21h:CDMA-RP:ipmobile_visitor add/delete=1, mn=8.0.2.132, ha=7.0.0.2
1d21h:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access2000,
changed state to up
Router# debug cdma pdsn a11 packets events
Router# show debug
CDMA:
  CDMA PDSN A11 packet debugging is on for mnid 000000000000001
  CDMA PDSN A11 events debugging is on for mnid 000000000000001
Router#
*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.0
Router#
*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=1
Router# debug cdma pdsn a11 event mnid 000000000000001
Router# show debug
CDMA:
  CDMA PDSN A11 events debugging is on for mnid 000000000000001
Router#
*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.0
Router#
close the session
Router#
*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=1
Router# debug cdma pdsn a11 packet mnid 000000000000001 
Router# show debug 
CDMA:
  CDMA PDSN A11 packet debugging is on for mnid 000000000000001
Router#
*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 5B
debug 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

Release

Modification

12.1(3)XS

This command was introduced.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T.

Examples

The following is sample output from the debug cdma pdsn accounting command:
Router# debug cdma pdsn accounting 
CDMA PDSN accounting debugging is on
Router#
*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 F1
debug 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

Release

Modification

12.2(2)XC

This command was introduced.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T.

Examples

The following is sample output from the debug cdma pdsn accounting flow command:
Router# debug cdma pdsn accounting flow 
CDMA PDSN flow based accounting debugging is on
pdsn-6500#
01:59:40:CDMA-SM:cdma_pdsn_flow_acct_upstream sess id 1 flow type 0 bytes 100 addr 
20.20.20.1
01:59:40:CDMA-SM:cdma_pdsn_flow_acct_downstream sess id 1 flow type 0 bytes 100 addr 
20.20.20.1
debug 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

Release

Modification

12.1(3)XS

This command was introduced.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T.

Examples

The following is sample output from the debug cdma pdsn accounting time-of-day command:
Router# debug cdma pdsn accounting time-of-day 
CDMA PDSN accounting time-of-day debugging is on
Feb 15 19:13:23.634:CDMA-TOD:Current timer expiring in 22 seconds
Feb 15 19:13:24.194:%SYS-5-CONFIG_I:Configured from console by console
Router#
Feb 15 19:13:45.635:CDMA-TOD:Timer expired...Rearming timer
Feb 15 19:13:45.635:CDMA-TOD:Gathering session info
Feb 15 19:13:45.635:CDMA-TOD:Found 0 sessions 
debug 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

message

Displays cluster messages for errors, events and packets received.

redundancy

Displays redundancy information for errors, events, and sent or received packets.

error

Displays either cluster or redundancy error messages.

events

Displays either all cluster or all redundancy events.

packets

Displays all transmitted or received cluster or redundancy packets.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XS

This command was introduced.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T.

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 messages
  redundancy  Debug PDSN cluster controller redundancy
debug 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

Release

Modification

12.2(8)BY

This command was introduced.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T.

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 sec
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.