cc/td/doc/product/software/ios124/124tcr
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

debug vlan packet

debug vmi

debug voice aaa asnl

debug voice all

debug voice cp

debug voice dsp crash-dump

debug voice eecm

debug voice enum

debug voice protocol

debug voice register errors

debug voice register events

debug voice signaling

debug voice source-group

debug voice statistics

debug voice tdsm

debug voice translation

debug voice uri

debug voice vofr

debug voip aaa

debug voip ais

debug voip application

debug voip application stcapp all

debug voip application stcapp buffer-history

debug voip application stcapp error

debug voip application stcapp events

debug voip application stcapp functions

debug voip application stcapp port

debug voip application vxml

debug voip avlist

debug voip ccapi

debug voip ccapi error

debug voip ccapi inout

debug voip confmsp

debug voip dcapi

debug voip dialpeer

debug voip dsm

debug voip dsmp

debug voip dspapi

debug voip eddri

debug voip enum

debug voip event-log

debug voip hpi

debug voip ipipgw


debug vlan packet

To display general information on virtual LAN (VLAN) packets that the router received but is not configured to support, use the debug vlan packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug vlan packet

no debug vlan packet

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

The debug vlan packet command displays only packets with a VLAN identifier that the router is not configured to support. This command allows you to identify other VLAN traffic on the network. Virtual LAN packets that the router is configured to route or switch are counted and indicated when you use the show vlans command.

Examples

The following is sample output from the debug vlan packet output. In this example, a VLAN packet with a VLAN ID of 1000 was received on FDDI interface 0 and this interface was not configured to route or switch this VLAN packet:

Router# debug vlan packet

vLAN: IEEE 802.10 packet bearing vLAN ID 1000 received on interface
Fddi0 which is not configured to route/switch ID 1000.

debug vmi

To display debugging output for virtual multipoint interfaces (VMIs), use the debug vmi command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug vmi {error | multicast | neighbor | packet | pppoe}

no debug vmi {error | multicast | neighbor | packet | pppoe}

Syntax Description

error

Displays errors received on the interface.

multicast

Displays information about multicast packets going in or out on the interface.

neighbor

Displays information about neighbor relationships causing the VMI interface to go up or down.

packet

Displays information about packets going in or out on the VMI interface.

pppoe

Displays information about the flows between PPPoE and the VMI interface that trigger the creation of a neighbor relationship.


Command Default

Debugging is disabled by default.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.4(15)XF

This command was introduced to support Mobile Adhoc Networking.

12.4(15)T

This command was integrated into Cisco IOS Release 12.4(15)T.


Examples

Debug Output with VMI Interface Working Propoerly

The following is sample output from the debug vmi command when the VMI interface is working correctly:

Router# debug vmi neighbor

Jan 6 07:01:54.601: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Jan 6 07:01:54.605: vmi_create_neighbor: event=VMI_PPPOE_IPV4_UP, addr=10.3.3.2
Jan 6 07:01:54.605: vmi_create_neighbor: V4-- nbr=0, key=::4.3.3.2
Jan 6 07:01:54.605: vmi_create_neighbor: V6-- nbr=0, key=::
Jan 6 07:01:54.605: vmi_create_neighbor: VMI_PPPOE_IPV4_UP -- neighbor addr=0
Jan 6 07:01:54.605: vmi_nbr_add: Begin. nbr=8381D104 nbr->IPv6linkPtr = 0, nbr->IPv4linkPtr = 0
Jan 6 07:01:54.605: VMI: Begin dump of Neighbor RBTree
Jan 6 07:01:54.605: VMI: vmiLink_t(838368E0),key=::10.3.3.2,V4
Jan 6 07:01:54.605: VMI: nbr addresses: :: 10.3.3.2
Jan 6 07:01:54.605: mtu=1484,insertAttempts=0 0,neighbor_up_deferred=FALSE
Jan 6 07:01:54.605: VMI: NO L2 STRUCT FOUND
Jan 6 07:01:54.605: VMI: End dump of Neighbor RBTree
Jan 6 07:01:54.609: vmi1 new nbr ::/10.3.3.2
Jan 6 07:01:54.609: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state to up
Jan 6 07:01:54.609: vmi_create_route_tbl_entry: Interface up on vmi1
Jan 6 07:01:54.609: vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.2
Jan 6 07:01:54.609: vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.2
Jan 6 07:01:54.617: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.2 (vmi1) is up: new adjacency
Jan 6 07:01:55.601: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up

Debug Output for Periodic Status Update

The following is sample output from the debug vmi command for a periodic status update:

Router# debug vmi neighbor

Jan 6 07:02:24.609: vmi_nbr_calculate_load: load=0, nbr ::/10.3.3.2
Jan 6 07:02:24.609: cur_tx_bytes = 776, old_tx_bytes = 0, tx_delta = 776
Jan 6 07:02:24.609: msec_clock_diff = 30004, clock_diff = 30, rate = 102400000
Jan 6 07:02:24.609: max_traffic = 2207566340

Debug Output Showing Loss of a Neighbor Node

The following is sample output from the debug vmi command when the loss of a neighbor is reported:

Router# debug vmi neighbor

Jan 6 07:02:33.781: vmi_destroy_neighbor: Delete route 10.3.3.2 returned RC_IPROUTEDEL_DB
Jan 6 07:02:33.781: vmi_destroy_neighbor: VMI_IPV4 nbr=8381D104
Jan 6 07:02:33.781: vmi_nbr_delete: deleting V4 linkPtr=838368E0, nbr=8381D104
Jan 6 07:02:33.781: vmiFreeNeighbor: Freeing nbr=8381D104
Jan 6 07:02:33.781: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state to down
Jan 6 07:02:33.781: vmi_hwif_goingdown: called for vmi1
Jan 6 07:02:33.781: vmi_hwif_goingdown: No corresponding VMI interface found for vmi1
Jan 6 07:02:33.785: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.2 (vmi1) is down: igrp2 peer state - DOWN
Jan 6 07:02:33.793: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Jan 6 07:02:34.793: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
Jan 6 07:02:35.785: %LINK-5-CHANGED: Interface vmi1, changed state to administratively down


The following example shows the status of a VMI peer relationship:

Router# debug vmi neighbor

Jan 6 07:03:37.737: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Jan 6 07:03:37.769: vmi_create_neighbor: event=VMI_PPPOE_IPV4_UP, addr=10.3.3.1
Jan 6 07:03:37.769: vmi_create_neighbor: V4-- nbr=0, key=::10.3.3.1
Jan 6 07:03:37.769: vmi_create_neighbor: V6-- nbr=0, key=::
Jan 6 07:03:37.769: vmi_create_neighbor: VMI_PPPOE_IPV4_UP -- neighbor addr=0
Jan 6 07:03:37.769: vmi_nbr_add: Begin. nbr=7004A304 nbr->IPv6linkPtr = 0, nbr->IPv4linkPtr = 0
Jan 6 07:03:37.769: VMI: Begin dump of Neighbor RBTree
Jan 6 07:03:37.769: VMI: vmiLink_t(70EF96A8),key=::10.3.3.1,V4
Jan 6 07:03:37.769: VMI: nbr addresses: :: 10.3.3.1
Jan 6 07:03:37.769: mtu=1484,insertAttempts=0 0,neighbor_up_deferred=FALSE
Jan 6 07:03:37.769: VMI: NO L2 STRUCT FOUND
Jan 6 07:03:37.769: VMI: End dump of Neighbor RBTree
Jan 6 07:03:37.769: vmi1 new nbr ::/10.3.3.1
Jan 6 07:03:37.769: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state to up
Jan 6 07:03:37.769: vmi_create_route_tbl_entry: Interface up on vmi1
Jan 6 07:03:37.769: vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.1
Jan 6 07:03:37.769: vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.1
Jan 6 07:03:37.781: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.1 (vmi1) is up: new adjacency
Jan 6 07:03:38.737: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
Jan 6 07:04:07.769: vmi_nbr_calculate_load: load=0, nbr ::/10.3.3.1
Jan 6 07:04:07.769: cur_tx_bytes = 640, old_tx_bytes = 0, tx_delta = 640
Jan 6 07:04:07.769: msec_clock_diff = 30000, clock_diff = 30, rate = 102400000
Jan 6 07:04:07.769: max_traffic = 57600

Jan 6 07:04:16.953: vmi_destroy_neighbor: Delete route 10.3.3.1 returned RC_IPROUTEDEL_DB
Jan 6 07:04:16.953: vmi_destroy_neighbor: VMI_IPV4 nbr=7004A304
Jan 6 07:04:16.953: vmi_nbr_delete: deleting V4 linkPtr=70EF96A8, nbr=7004A304
Jan 6 07:04:16.953: vmiFreeNeighbor: Freeing nbr=7004A304
Jan 6 07:04:16.953: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state to down
Jan 6 07:04:16.957: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.1 (vmi1) is down: igrp2 peer state - DOWN
Jan 6 07:04:16.961: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Jan 6 07:04:17.953: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down

Related Commands

Command
Description

eigrp interface

Sets a threshold value to minimize hysteresis in a router-to-radio configuration.

interface vmi

Creates a virtual multipoint interface (VMI) that can be configured and applied dynamically.

mode bypass

Enables Virtual Multipoint Interfaces (VMI) to support multicast traffic

physical interface

Creates a physical subinterface to be associated with the Virtual Multipoint Interfaces (VMI) on a router


debug voice aaa asnl

To display debugging messages for gateway authentication, authorization, and accounting (AAA) Application Subscribe/Notify Layer (ASNL), use the debug voice aaa asnl command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice aaa asnl

no debug voice aaa asnl

Syntax Description

This command has no arguments or keywords.

Defaults

Debugging of AAA ASNL is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(4)T

This command was introduced.


Usage Guidelines

The debug voice aaa asnl command is a subset of the debug voice aaa command. It displays only events and error information related to the Accounting Server Connectivity Failure and Recovery Detection feature.

Examples

The following output is displayed when the debug voice aaa asnl command is entered:

Router# debug voice aaa asnl

01:39:15:voip_aaa_accounting_pthru_send:Method List Name:ml1, aaa_av_list 0x62D69FCC, acct_rec_type 3
01:39:15:voip_aaa_search_mlist_node_by_name:Method List Name:ml15
01:39:15:voip_aaa_accounting_pthru_send:Accounting Probe UID=1, adb = 629977A0
01:39:15:voip_aaa_accounting_pthru_send(1):increment num_acct_sent counter

Table 325 describes the significant fields shown in the display.

Table 325 debug voice aaa asnl Field Descriptions 

Field
Description

acct_rec_type

Accounting record type: START (1), UPDATE (2), STOP (3), ACCT_ON (4).

Accounting Probe UID

ID of the accounting probe record.

Method List Name

Method list name.


debug voice all

To display debugging information for all components of the Voice Call Manager, use the debug voice all command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice all [slot/port]

no debug voice all [slot/port]

Syntax Description

slot/port

(Optional) The slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed. If the slot and port are not entered, debugging information for all voice ports is displayed.


Command Modes

Privileged EXEC

Usage Guidelines

This command is valid on the Cisco MC3810 only.

Examples

The debug voice all command output provides debug output for all the debug commands for the Voice Call Manager compiled into one display. For sample output of the individual commands, see the sample displays for the debug voice cp, debug voice eecm, debug voice protocol, debug voice signaling, and debug voice tdsm commands.

Related Commands

Command
Description

debug voice eecm

Displays debugging information for the Voice End-to-End Call Manager.

debug voice protocol

Displays debugging information for the Voice Line Protocol State machine.

debug voice signaling

Displays debugging information for the voice port signaling.

debug voice tdsm

Displays debugging information for the voice tandem switch.

debug voice ccapi

Debugs the call control API.


debug voice cp

To display debugging information for the Voice Call Processing State Machine, use the debug voice cp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice cp [slot/port]

no debug voice cp [slot/port]

Syntax Description

slot/port

(Optional) The slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.


Command Modes

Privileged EXEC

Usage Guidelines

This command is valid on the Cisco MC3810 only.

Examples

The following is sample output from the debug voice cp command:

Router# debug voice cp 1/1

Voice Call Processing State Machine debugging is on

1/1: CPD( ), idle gets event seize_ind
1/1: CPD( ), idle gets event dsp_ready
1/1: CPD( ), idle ==> collect
1/1: CPD(in), collect gets event digit
1/1: CPD(in), collect gets event digit
1/1: CPD(in), collect gets event digit
1/1: CPD(in), collect gets event digit
1/1: CPD(in), collect gets event addr_done
1/1: CPD(in), collect ==> request
1/1: CPD(in), request gets event call_proceeding
1/1: CPD(in), request ==> in_wait_answer
1/1: CPD(in), in_wait_answer gets event call_accept
1/1: CPD(in), in_wait_answer gets event call_answered
1/1: CPD(in), in_wait_answer ==> connected
1/1: CPD(in), connected gets event peer_onhook
1/1: CPD(in), connected ==> disconnect_wait
1/1: CPD(in), disconnect_wait gets event idle_ind
1/1: CPD(in), disconnect_wait ==> idle

Related Commands

Command
Description

debug voice all

Displays debugging information for all components of the Voice Call Manager.

debug voice eecm

Displays debugging information for the Voice End-to-End Call Manager.

debug voice protocol

Displays debugging information for the Voice Line protocol State machine.

debug voice signaling

Displays debugging information for the voice port signaling.

debug voice tdsm

Displays debugging information for the voice tandem switch.


debug voice dsp crash-dump

To display debugging information for the crash dump feature, use the debug voice dsp crash-dump command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice dsp crash-dump [details | keepalives]

no debug voice dsp crash-dump [details | keepalives]

Syntax Description

details

(Optional) Displays debugging information for the crash dump feature details. There is no debug output until there is one DSP crash. When the crash dump feature is turned on, the detailed debug messages are displayed.

keepalives

(Optional) Displays debugging information for the crash dump feature keepalives. Confirms that a crash dump file has been written to the specified destination.


Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(4)T

This command was introduced.


Usage Guidelines

DSP resource management (DSPRM) sends a debug message to the console that confirms that a crash dump file has been written to the specified destination.


Caution Enabling this debug feature adds extra time for the DSP to recover. The keepalive and detail keywords produce large volumes of output and should not be used except under the direction of a Cisco engineer.

You can also use the undebug all command to disable debugging output.

Examples

The following example shows a debug message that confirms that a crash dump file has been written to the specified destination. The stack is displayed on the console, and the DSPware version, complexity (image set), and Cisco IOS software version is also displayed.

Router# debug voice dsp crash-dump keepalives

*Mar 8 03:42:19.505:Got back DSP status 0x12 0x0 for dsp 9 slot 1
*Mar 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 10 slot 1
*Mar 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 11 slot 1
*Mar 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 12 slot 1
*Mar 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 13 slot 1
*Mar 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 14 slot 1
*Mar 8 03:42:21.509:status cleared done, dsp 9 slot 1
*Mar 8 03:42:21.513:status cleared done, dsp 10 slot 1
*Mar 8 03:42:21.513:status cleared done, dsp 11 slot 1
*Mar 8 03:42:21.513:status cleared done, dsp 12 slot 1
*Mar 8 03:42:21.513:status cleared done, dsp 13 slot 1

*Mar 8 03:42:21.513:status cleared done, dsp 14 slot 1

The following command disables all the debugging output on the screen to stop the output from the debug voice dsp crash-dump keepalives command:

Router# undebug all

The following example shows the debug voice dsp crash-dump details command entry when no DSP crash is present. There is no debugging output until there is one DSP crash. When the crash dump feature is turned on, the detailed debug messages are displayed.

Router# debug voice dsp crash-dump details

Related Commands

Command
Description

show voice dsp crash-dump

Displays voice dsp crash dump information.

voice dsp crash-dump

Enables the crash dump feature and specifies the destination file and the file limit.


debug voice eecm

To display debugging information for the Voice End-to-End Call Manager, use the debug voice eecm command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice eecm [slot/port]

no debug voice eecm [slot/port]

Syntax Description

slot/port

(Optional) Slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.


Command Modes

Privileged EXEC

Usage Guidelines

This command is valid on the Cisco MC3810 only.

Examples

The following is sample output from the debug voice eecm command:

Router# debug voice eecm

1/1: EECM(in), ST_NULL EV_ALLOC_DSP
1/1: EECM(in), ST_DIGIT_COLLECT EV_PARSE_DIGIT 3
1/1: EECM(in), ST_DIGIT_COLLECT EV_PARSE_DIGIT 7
1/1: EECM(in), ST_DIGIT_COLLECT EV_PARSE_DIGIT 0
1/1: EECM(in), ST_DIGIT_COLLECT EV_PARSE_DIGIT 2
1/1: EECM(in), ST_ADDRESS_DONE EV_OUT_SETUP
-1/-1: EECM(out), ST_NULL EV_IN_SETUP
1/1: EECM(in), ST_OUT_REQUEST EV_IN_PROCEED
1/2: EECM(out), ST_SEIZE EV_ALLOC_DSP
1/2: EECM(out), ST_SEIZE EV_OUT_ALERT
1/1: EECM(in), ST_OUT_REQUEST EV_IN_ALERT
1/1: EECM(in), ST_OUT_REQUEST EV_OUT_ALERT_ACK
1/2 EECM(out), ST_IN_PENDING EV_OUT_CONNECT
1/1: EECM(in), ST_WAIT_FOR_ANSWER EV_IN_CONNECT
1/2: EECM(out), ST_ACTIVE EV_OUT_REL
1/1: EECM(in), ST_ACTIVE EV_IN_REL
1/1: EECM(in), ST_DISCONN_PENDING EV_OUT_REL_ACK

Related Commands

Command
Description

debug voice all

Displays debugging information for all components of the Voice Call Manager.

debug voice protocol

Displays debugging information for the Voice Line protocol State machine.

debug voice signaling

Displays debugging information for the voice port signaling.

debug voice tdsm

Displays debugging information for the voice tandem switch.

debug voice ccapi

Debugs the call control API.


debug voice enum

To view voice telephone number mapping (ENUM) information, use the debug voice enum command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice enum {detail | summary}

no debug voice enum {detail | summary}

Syntax Description

detail

Displays detailed output.

summary

Displays summary output.


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(11)T

This command was introduced.


Usage Guidelines

Disable console logging and use buffered logging before using the debug voice enum command. Using the debug voice enum command generates a large volume of debugs, which can affect router performance.

Examples

The following is sample output from the debug voice enum detail command. The output shows the match number as 5108891234, ENUM table as 10. Rule 1 in table 10 matched the pattern and after applying the replacement rule, the resulting string is 5108891234. The ENUM query is sent out for the domain 4.3.2.1.9.8.8.0.1.5.e164.cisco.com. The output then shows the matching Naming Authority Pointer (NAPTR) records obtained in the response. The records are then processed and the final URLs (contact lists) are shown toward the end.

Router# debug voice enum detail

enum_resolve_domain:match_num 5108891234 table_indx 10
enum_resolve_domain:rule 1 result string 5108891234
generate_enum_search_string :search string 4.3.2.1.9.8.8.0.1.5.e164.cisco.com
enum_dns_query:name = 4.3.2.1.9.8.8.0.1.5.e164.cisco.com type = 35, ns_server = 0
order 100 pref 10 service sip+E2U flag U
regexp /^.*$/sip:5108891234@1.8.50.14/ replacement
order 200 pref 10 service h323+E2U flag U
regexp /^.*$/h323:5555@1.5.1.1/ replacement
num_elem = 2
NAPTR Record :order 100 pref 10 service sip+E2U
flags U regexp /^.*$/sip:5108891234@1.8.50.14/
replacement
NAPTR Record :order 200 pref 10 service h323+E2U
flags U regexp /^.*$/h323:5555@1.5.1.1/
replacement
decode_naptr_record :re_string ^.*$
decode_naptr_record :re_substitution_string sip:5108891234@1.8.50.14
decode_naptr_record :re_flags_string
U_FLAG case, stopping query
new_e164_user sip:5108891234@1.8.50.14
decode_naptr_record :re_string ^.*$
decode_naptr_re
tahoe13#cord :re_substitution_string h323:5555@1.5.1.1
decode_naptr_record :re_flags_string
U_FLAG case, stopping query
new_e164_user h323:5555@1.5.1.1
contact_list :
sip:5108891234@1.8.50.14
contact_list :
h323:5555@1.5.1.1
enum_resolve_domain:contact_list 64558450

A sample output of the debug voice enum summary command is shown below.

The output shows the matching number, the ENUM table used and the rule in the table that matched the number along with the resulting string. Note that this output is a subset of the output from debug voice enum detail command.

Router# debug voice enum summary

enum_resolve_domain:match_num 5108891234 table_indx 10
enum_resolve_domain:rule 1 result string 5108891234

Table 326 provides an alphabetical listing of the debug voice enum command fields and a description of each field.

Table 326 debug voice enum Field Descriptions 

Field
Description

contact_list

Final list of URLs that the gateway will try to contact as an attempt to place the call.

flag

Flag value of a NAPTR record as defined in RFC 2915.

match_num

Number to be used for matching against the ENUM match table.

name

Fully qualified domain name sent out to DNS server.

ns_server

Address of the DNS server. If 0, the Domain Name System (DNS) server configured on the gateway is used.

num_elem

Number of records received in the response.

order

Order in the record, as defined in RFC 2915.

pref

Preference of the record, as defined in RFC 2915.

regexp

Regular expression of the record, as defined in RFC 2915.

replacement

Replacement string of the record, as defined in RFC 2915.

re_flags_string

Flag indicating whether matching and replacement should be case sensitive:

i = Case insensitive

otherwise = Case sensitive

re_string

The first part of the regexp, delimited by "/". This is used to match the incoming string. Refer to RFC 2915.

re_substitution_string

The second part of regexp, delimited by "/".

result string

String that results when match_num is taken through the ENUM match table for a match. This string will be used to form a fully qualified domain name (FQDN).

rule

Rule number that matched match_num in the enum match table.

search string

String sent out to the DNS server.

service

Service field of the NAPTR record. Refer to RFC 2915.

table_indx

Index of the ENUM match table picked for this call.

type

Type of record requested in the query:

35 = NAPTR
33 = DNS Service (SRV)


Related Commands

Command
Description

rule (ENUM configuration)

Defines the rule pattern for an ENUM match table.

show voice enum-match-table

Displays the ENUM match table rules.

test enum

Tests the ENUM match table rules.

voice enum-match-table

Initiates the ENUM match table definition.


debug voice protocol

To display debugging information for the Voice Line protocol State machine, use the debug voice protocol command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice protocol [slot/port]

no debug voice protocol [slot/port]

Syntax Description

slot/port

(Optional) Slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.


Command Modes

Privileged EXEC

Command History

This command is valid on the Cisco MC3810 only.

Usage Guidelines

In the debugging display, the following abbreviations are used for the different signaling protocols:

LFXS—FXS trunk loop start protocol

LFXO—FXO trunk loop start protocol

GFXS—FXS trunk ground start protocol

GFXO—FXO trunk ground start protocol

E&M—E&M trunk protocol

Examples

The following is sample output from the debug voice protocol command:

Router# debug voice protocol

Voice Line protocol State machine debugging is on

1/1: LFXS( ), idle gets event offhook
1/1: LFXS( ), idle ==> seize
1/1: LFXS(in), seize gets event ready
1/1: LFXS(in), seize ==> dial_tone
1/1: LFXS(in), dial_tone gets event digit
1/1: LFXS(in), dial_tone ==> collect
1/1: LFXS(in), collect gets event digit
1/1: LFXS(in), collect gets event digit
1/1: LFXS(in), collect gets event digit
1/1: LFXS(in), collect gets event addr_done
1/1: LFXS(in), collect ==> call_progress
1/2: LFXS( ), idle gets event seize
1/2: LFXS( ), idle ==> ringing
1/2: LFXS(out), ringing gets event dial_tone
1/2: LFXS(out), ringing gets event offhook
1/2: LFXS(out), ringing ==> connected
1/1: LFXS(in), call_progress gets event answer
1/1: LFXS(in), call_progress ==> connected
1/2: LFXS(out), connected gets event onhook
1/2: LFXS(out), connected ==> disconnect_wait
1/2: LFXS(out), disconnected_wait gets event disconnect
1/2: LFXS(out), disconnect_wait ==> cpc
1/1: LFXS(in), connected gets event disconnect
1/2: LFXS(out), connected ==> cpc
1/2: LFXS(out), cpc gets event offhook
1/2: LFXS(out), cpc gets event timer1
1/2: LFXS(out), cpc ==> cpc_recover
1/2: LFXS(out), cpc gets event timer1
1/2: LFXS(out), cpc_recover ==> offhook_wait
1/1: LFXS(in), offhook_wait gets event onhook
1/1: LFXS(in), offhook_wait ==> idle
1/2: LFXS(out), offhook_wait gets event onhook
1/2: LFXS(out), offhook_wait ==> idle

Related Commands

Command
Description

debug voice all

Displays debugging information for the voice tandem switch.

debug voice eecm

Displays debugging information for the Voice End-to-End Call Manager.

debug voice signaling

Displays debugging information for the voice port signaling.

debug voice tdsm

Displays debugging information for the voice tandem switch.

debug voice ccapi

Debugs the call control API.


debug voice register errors

To display debug information on voice register module errors during registration in a Cisco Unified CallManager Express (Cisco Unified CME) or Cisco Unified Session Initiation Protocol (SIP) Survivable Remote Site Telephony (SRST) environment, use the debug voice register errors command in privileged EXEC mode. To disable debugging, use the no form of the command.

debug voice register errors

no debug voice register errors

Syntax Description

This command has no arguments or keywords.

Command Default

Debugging is not enabled

Command Modes

Privileged EXEC

Command History

Cisco IOS Release
Modification

12.2(15)ZJ

This command was introduced for Cisco SIP SRST 3.0.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T for Cisco SIP SRST 3.0.

12.4(4)T

This command was added to Cisco Unified CME 3.4 and Cisco SIP SRST 3.4.


Usage Guidelines

Registration errors include failure to match pools or any internal errors that happen during registration.

Examples

Cisco Unified CME

The following is sample output for this command for a registration request with authentication enabled:

.
.
.
*May 6 18:07:26.971: VOICE_REG_POOL: Register request for (4901) from (10.5.49.83)
*May 6 18:07:26.971: VOICE_REG_POOL: key(9499C07A000036A3) added to nonce table
*May 6 18:07:26.975: VOICE_REG_POOL: Contact doesn't match any pools
*May 6 18:07:26.975: //4/89D7750A8005/SIP/Error/ccsip_spi_register_incoming_registration: Registration Authorization failed with authorization header=
.
.
.

If there are no voice register pools configured for a particular registration request, the message "Contact doesn't match any pools" is displayed.

When authentication is enabled and if the phone requesting registration cannot be authenticated, the message "Registration Authorization failed with authorization header" is displayed.

Cisco Unified SIP SRST

The following is sample output from this command:

Router# debug voice register errors

*Apr 22 11:52:54.523 PDT: VOICE_REG_POOL: Contact doesn't match any pools
*Apr 22 11:52:54.539 PDT: VOICE_REG_POOL: Register request for (33015) from (10.2.152.39)
*Apr 22 11:52:54.539 PDT: VOICE_REG_POOL: Contact doesn't match any pools.
*Apr 22 11:52:54.559 PDT: VOICE_REG_POOL: Register request for (33017) from (10.2.152.39)
*Apr 22 11:53:04.559 PDT: VOICE_REG_POOL: Maximum registration threshold for pool(3) hit

If there are no voice register pools configured for a particular registration request, the message "Contact doesn't match any pools" is displayed.

If the max registrations command is configured, when registration requests reach the maximum limit, the "Maximum registration threshold for pool (x) hit" message is displayed for the particular pool.

Table 327 describes the significant fields shown in the display.

Table 327 debug voice register errors Field Descriptions 

Field
Description

Contact (doesn't match any pools)

Contact refers to the location of the SIP devices and the IP address.

key (MAC address)

Unique MAC address of a locally available individual SIP phone used to support a degree of authentication in Cisco Unified CME.

Register request for (telephone number) from (IP address).

The unique key for each registration is the telephone number.

Registration Authorization (failed with authorization header)

Registration Authorization message is displayed when the authenticate command is configured in Cisco Unified CME.


Related Commands

Command
Description

debug voice register events

Displays debug information on voice register module events during SIP phone registrations in a Cisco Unified CME or Cisco Unified SIP SRST environment.


debug voice register events

To display debug information on voice register module events during Session Initiation Protocol (SIP) phone registrations in a Cisco Unified CallManager Express (Cisco Unified CME) or Cisco Unified SIP Survivable Remote Site Telephony (SRST) environment, use the debug voice register events command in privileged EXEC mode. To disable debugging, use the no form of this command.

debug voice register events

no debug voice register events

Syntax Description

This command has no arguments or keywords.

Command Default

Debugging is not enabled

Command Modes

Privileged EXEC

Command History

Cisco IOS Release
Modification

12.2(15)ZJ

This command was introduced for Cisco SIP SRST 3.0.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T for Cisco SIP SRST 3.0.

12.4(4)T

This command was added to Cisco CME 3.4 and Cisco SIP SRST 3.4.


Usage Guidelines

Using the debug voice register events command should suffice to display registration activity.

Registration activity includes matching of pools, registration creation, and automatic creation of dial peers.

For more details and error conditions, you can use the debug voice register errors command.

Cisco Unified CME

The following example shows output from this command:

*May 6 18:07:27.223: VOICE_REG_POOL: Register request for (4901) from (10.5.49.83)
*May 6 18:07:27.223: VOICE_REG_POOL: Contact matches pool 1 number list 1
*May 6 18:07:27.223: VOICE_REG_POOL: key(4901) contact(10.5.49.83) add to contact table
*May 6 18:07:27.223: VOICE_REG_POOL: No entry for (4901) found in contact table
*May 6 18:07:27.223: VOICE_REG_POOL: key(4901) contact(10.5.49.83) added to contact tableVOICE_REG_POOL pool->tag(1), dn->tag(1), submask(1)
*May 6 18:07:27.223: VOICE_REG_POOL: Creating param container for dial-peer 40001.
*May 6 18:07:27.223: VOICE_REG_POOL: Created dial-peer entry of type 0
*May 6 18:07:27.223: VOICE_REG_POOL: Registration successful for 4901, registration id is 2
.
.
.

The phone number 4901 associated with voice register pool 1, voice register dn 1, registered successfully. A dynamic normal (type 0) VoIP dial peer has been created for entry 4901. The dial peer can be verified using the show voice register dial-peers and show sip-ua status registrar commands.

Cisco Unified SIP SRST

The following is sample output from this command:

Router# debug voice register events

Apr 22 10:50:21.731 PDT: VOICE_REG_POOL: Contact matches pool 1
Apr 22 10:50:21.731 PDT: VOICE_REG_POOL: key(91011) contact(192.168.0.2) add to contact table
Apr 22 10:50:21.731 PDT: VOICE_REG_POOL: key(91011) exists in contact table
Apr 22 10:50:21.731 PDT: VOICE_REG_POOL: contact(192.168.0.2) exists in contact table, ref updated
Apr 22 10:50:21.731 PDT: VOICE_REG_POOL: Created dial-peer entry of type 1
Apr 22 10:50:21.731 PDT: VOICE_REG_POOL: Registration successful for 91011, registration id is 257

The phone number 91011 registered successfully, and type 1 is reported in the debug, which means that there is a preexisting VoIP dial peer.

Apr 22 10:50:38.119 PDT: VOICE_REG_POOL: Register request for (91021) from (192.168.0.3)
Apr 22 10:50:38.119 PDT: VOICE_REG_POOL: Contact matches pool 2
Apr 22 10:50:38.123 PDT: VOICE_REG_POOL: key(91021) contact(192.168.0.3) add to contact table
Apr 22 10:50:38.123 PDT: VOICE_REG_POOL: key(91021) exists in contact table
Apr 22 10:50:38.123 PDT: VOICE_REG_POOL: contact(192.168.0.3) exists in contact table, ref updated
Apr 22 10:50:38.123 PDT: VOICE_REG_POOL: Created dial-peer entry of type 1
Apr 22 10:50:38.123 PDT: VOICE_REG_POOL: Registration successful for 91021, registration id is 258

A dynamic VoIP dial peer has been created for entry 91021. The dial peer can be verified using the show voice register dial-peers and show sip-ua status registrar commands.

Apr 22 10:51:08.971 PDT: VOICE_REG_POOL: Register request for (95021) from (10.2.161.50)
Apr 22 10:51:08.971 PDT: VOICE_REG_POOL: Contact matches pool 3
Apr 22 10:51:08.971 PDT: VOICE_REG_POOL: key(95021) contact(10.2.161.50) add to contact table
Apr 22 10:51:08.971 PDT: VOICE_REG_POOL: No entry for (95021) found in contact table
Apr 22 10:51:08.975 PDT: VOICE_REG_POOL: key(95021) contact(10.2.161.50) added to contact table
Apr 22 10:51:08.979 PDT: VOICE_REG_POOL: Created dial-peer entry of type 0
Apr 22 10:51:08.979 PDT: VOICE_REG_POOL: Registration successful for 95021, registration id is 259
Apr 22 10:51:09.019 PDT: VOICE_REG_POOL: Register request for (95012) from (10.2.161.50)
Apr 22 10:51:09.019 PDT: VOICE_REG_POOL: Contact matches pool 3
Apr 22 10:51:09.019 PDT: VOICE_REG_POOL: key(95012) contact(10.2.161.50) add to contact table
Apr 22 10:51:09.019 PDT: VOICE_REG_POOL: No entry for (95012) found in contact table
Apr 22 10:51:09.023 PDT: VOICE_REG_POOL: key(95012) contact(10.2.161.50) added to contact table
Apr 22 10:51:09.027 PDT: VOICE_REG_POOL: Created dial-peer entry of type 0
Apr 22 10:51:09.027 PDT: VOICE_REG_POOL: Registration successful for 95012, registration id is 260
Apr 22 10:51:09.071 PDT: VOICE_REG_POOL: Register request for (95011) from (10.2.161.50)
Apr 22 10:51:09.071 PDT: VOICE_REG_POOL: Contact matches pool 3
Apr 22 10:51:09.071 PDT: VOICE_REG_POOL: key(95011) contact(10.2.161.50) add to contact table
Apr 22 10:51:09.071 PDT: VOICE_REG_POOL: No entry for (95011) found in contact table
Apr 22 10:51:09.075 PDT: VOICE_REG_POOL: key(95011) contact(10.2.161.50) added to contact table
Apr 22 10:51:09.079 PDT: VOICE_REG_POOL: Created dial-peer entry of type 0
Apr 22 10:51:09.079 PDT: VOICE_REG_POOL: Registration successful for 95011, registration id is 261
Apr 22 10:51:09.123 PDT: VOICE_REG_POOL: Register request for (95500) from (10.2.161.50)
Apr 22 10:51:09.123 PDT: VOICE_REG_POOL: Contact matches pool 3
Apr 22 10:51:09.123 PDT: VOICE_REG_POOL: key(95500) contact(10.2.161.50) add to contact table
Apr 22 10:51:09.123 PDT: VOICE_REG_POOL: No entry for (95500) found in contact table
Apr 22 10:51:09.127 PDT: VOICE_REG_POOL: key(95500) contact(10.2.161.50) added to contact table
Apr 22 10:51:09.131 PDT: VOICE_REG_POOL: Created dial-peer entry of type 0
Apr 22 10:51:09.131 PDT: VOICE_REG_POOL: Registration successful for 95500, registration id is 262
*Apr 22 11:52:54.523 PDT: VOICE_REG_POOL: Contact doesn't match any pools
*Apr 22 11:52:54.539 PDT: VOICE_REG_POOL: Register request for (33015) from (10.2.152.39)
*Apr 22 11:52:54.539 PDT: VOICE_REG_POOL: Contact doesn't match any pools
*Apr 22 11:52:54.559 PDT: VOICE_REG_POOL: Register request for (33017) from (10.2.152.39)

Table 328 describes the significant fields shown in the display.

Table 328 debug voice register events Field Descriptions 

Field
Description

Contact

Indicates the location of the SIP devices and may indicate the IP address.

contact table

The table that maintains the location of the SIP devices.

key

The phone number is used as the unique key to maintain registrations of SIP devices.

multiple contact

More than one registration matches the same phone number.

no entry

The incoming registration was not found.

type 0

Normal dial peer.

type 1

Existing normal dial peer.

type 2

Proxy dial peer.

type 3

Existing proxy dial peer.

type 4

Dial-plan dial peer.

type 5

Existing dial-plan dial peer.

type 6

Alias dial peer.

type 7

Existing alias dial peer.

un-registration successful

The incoming unregister was successful.

Register request/registration id number

The internal unique number for each registration; useful for debugging particular registrations.


Related Commands

Command
Description

debug voice register errors

Displays debug information on voice register module errors during registration in a Cisco Unified  CME or Cisco Unified SIP SRST environment.

show sip-ua status registrar

Displays all the SIP endpoints that are currently registered with the contact address.

show voice register dial-peers

Displays details of Cisco Unified SIP SRST configuration and of all dynamically created VoIP dial peers.


debug voice signaling

To display debugging information for the voice port signaling, use the debug voice signaling command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice signaling [slot/port]

no debug voice signaling [slot/port]

Syntax Description

slot/port

(Optional) Slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.


Command Modes

Privileged EXEC

Usage Guidelines

This command is valid on the Cisco MC3810 only.

Examples

The following is sample output from the debug voice signaling command:

Router# debug voice signaling

1/1: TIU, report_local_hook=1
1/2: TIU, set ring cadence=1
1/2: TIU, ringer on
1/2: TIU, ringer off
1/2: TIU, ringer on
1/2: TIU, report_local_hook=1
1/2: TIU, turning off ringer due to SW ringtrip
1/2: TIU, ringer off
1/2: TIU, set ring cadence=0
1/2: TIU, ringer off
1/2: TIU, set reverse battery=1
1/2: TIU, set reverse battery=1
1/1: TIU, report_local_hook=0
1/2: TIU, set reverse battery=0
1/2: TIU, set loop disabled=1
1/1: TIU, set reverse battery=0
1/1: TIU, set loop disabled=1
1/2: TIU, report_local_hook=1
1/1: TIU, report_lead_gnd grounded=1
1/1: TIU, report_lead_gnd grounded=0
1/2: TIU, set loop disabled=0
1/1: TIU, set loop disabled=0
1/1: TIU, report_local_hook=0
1/2: TIU, report_local_hook=0
1/1: TIU, report_local_hook=1
1/2: TIU, report_local_hook=1
1/1: TIU, report_local_hook=0
1/2: TIU, report_local_hook=0
1/1: TIU, set reverse battery=0
1/2: TIU, set reverse battery=0

Related Commands

Command
Description

debug voice all

Displays debugging information for all components of the Voice Call Manager.

debug voice eecm

Displays debugging information for the Voice End-to-End Call Manager.

debug voice protocol

Displays debugging information for the Voice Line protocol State machine.

debug voice tdsm

Display debugging information for the voice tandem switch.

debug voice ccapi

Debugs the call control API.


debug voice source-group

To view voice source group information, use the debug voice source-group command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice source-group

no debug voice source-group

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(11)T

This command was introduced.


Usage Guidelines

Disable console logging and use buffered logging before using the debug voice source-group command. Using the debug voice source-group command generates a large volume of debugs, which can affect router performance.

Examples

A sample output of the debug voice source-group command is shown below.

The output shows that the hash table key for source ip group is 1.

00:30:49:SIPG:sipg_get() - idString=0x63BE1C28, hashkey=1
00:30:49:SIPG:sipg_find_key - hashkey=1,idstring=0x63BE1C28

Table 329 describes the significant fields shown in the display.

Table 329 debug voice source-group Field Descriptions 

Field
Description

hashkey

Hash table index of the source IP group.

idString

Value of the pointer to the source IP group name, which is used to make sure that it is not null.


Related Commands

Command
Description

carrier-id (voice source group)

Specifies the carrier handling incoming source VoIP calls (for carrier ID routing).

show voice source-group

Displays the details of one or more source IP groups.

test source-group

Tests the definition of a source IP group.

translation-profile (source group)

Associates a translation profile with the source IP group.

trunk-group-label (voice source group)

Specifies the trunk group handling incoming source VoIP calls (for trunk group label routing).

voice source-group

Initiates the source IP group definition.


debug voice statistics

To enable debugging of voice statistics, use the debug voice statistics command in privileged EXEC mode. To disable the debugging, use the no form of this command.

debug voice statistics {csr | core | accounting}

no debug voice statistics {csr | core | accounting}

Syntax Description

csr

Signaling voice call statistics records collection is debugged.

core

Generic statistics collection is debugged.

accounting

Voice accounting CSR collection is debugged.


Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(4)T

This command was introduced.


Examples

The following example shows the collection of records that is occurring in between intervals:

Router# debug voice statistics accounting

vstats_timer_handle_interval_event():Between Intervals!

04:52:37: vstats_acct_interval_end: interval_tag = 4
04:52:37: vstats_acct_interval_end: pushing out, tag=3
04:52:37: vstats_acct_clean_history_stats:
04:52:37: vstats_acct_clean_history_stats: stats (tag=3) not to be deleted
04:52:37: vstats_acct_clean_history_stats: stats (tag=2) not to be deleted
04:52:37: vstats_acct_create_empty_stats:
04:52:37: vstats_acct_create_new_rec_list:
04:52:37: vstats_acct_create_new_rec_list: add acct rec: methodlist=h323, acct-criteria=2
04:52:37: vstats_acct_create_new_rec:
04:52:37: vstats_acct_add_rec_entry:
04:52:37: vstats_acct_add_stats_entry:
04:52:37: vstat_push_driver_file_open():Cannot open
ftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z.
errno=65540=Unknown error 65540
vstat_push_drv_activate_ftp_file_tx():open file
(ftp://sgcp:sgcp@jeremy-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z)=(ftp://sgcp:sg
cp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z)failed!
vstats_push_api_push_formatted_text():Start CMD error!

The following example shows a voice call going through the gateway:

Router# debug voice statistics csr

04:55:07: EM: Notify the producer not to produce
04:55:07: RADIUS(00000019): Storing nasport 0 in rad_db
04:55:07: RADIUS(00000019): Config NAS IP: 0.0.0.0
04:55:07: RADIUS(00000019): sending
04:55:07: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.203
04:55:07: RADIUS(00000019): Send Accounting-Request to 1.6.10.203:1646 id 21645/49,len 496
04:55:07: RADIUS: authenticator C5 B8 AA 2E C3 AF 02 93 - 45 0B AE E5 B6 B2 99 1F
04:55:07: RADIUS: Acct-Session-Id [44] 10 "00000020"
04:55:07: RADIUS: Vendor, Cisco [26] 57
04:55:07: RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:30.994 UTC
          Thu Feb 13 2003"
04:55:07: RADIUS: Vendor, Cisco [26] 27
04:55:07: RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW."
04:55:07: RADIUS: Vendor, Cisco [26] 56
04:55:07: RADIUS:  Conf-Id             [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002
          B935C142"
04:55:07: RADIUS: Vendor, Cisco [26] 31
04:55:07: RADIUS:  h323-call-origin  [26] 25 "h323-call-origin=answer"
04:55:07: RADIUS: Vendor, Cisco [26] 32
04:55:07: RADIUS: h323-call-type [27] 26 "h323-call-type=Telephony"
04:55:07: RADIUS: Vendor, Cisco [26] 65
04:55:07: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7
          800E0002 B935C142"
04:55:07: RADIUS: Vendor, Cisco [26] 30
04:55:07: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"
04:55:07: RADIUS: Vendor, Cisco       [26] 35
04:55:07: RADIUS: Cisco AVpair [1] 29 "gw-rxd-cdn=ton:0,npi:0,#:11"
04:55:07: RADIUS: Vendor, Cisco [26] 32
04:55:07: RADIUS: Cisco AVpair [1] 26 "calling-party-category=9"
04:55:07: RADIUS: Vendor, Cisco [26] 33
04:55:07: RADIUS: Cisco AVpair [1] 27 "transmission-medium-req=0"
04:55:07: RADIUS: User-Name [1] 4 "22"
04:55:07: RADIUS: Acct-Status-Type [40] 6 Start [1]
04:55:07: RADIUS: NAS-Port-Type [61] 6 Async [0]
04:55:07: RADIUS: Vendor, Cisco [26] 20
04:55:07: RADIUS: cisco-nas-port [2] 14 "ISDN 6/0:D:1"
04:55:07: RADIUS: NAS-Port [5] 6 0
04:55:07: RADIUS: Calling-Station-Id [31] 4 "22"
04:55:07: RADIUS: Called-Station-Id [30] 4 "11"
04:55:07: RADIUS: Service-Type [6] 6 Login [1]
04:55:07: RADIUS: NAS-IP-Address [4] 6 1.6.43.101
04:55:07: RADIUS: Acct-Delay-Time [41] 6 0
04:55:07: RADIUS(0000001A): Config NAS IP: 0.0.0.0
04:55:07: RADIUS(0000001A): sending
04:55:07: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.203
04:55:07: RADIUS(0000001A): Send Accounting-Request to 1.6.10.203:1646 id 21645/50, len427
04:55:07: RADIUS: authenticator E4 98 06 8C 48 63 4F AA - 56 4F 40 12 33 F0 F5 99
04:55:07: RADIUS: Acct-Session-Id [44] 10 "00000021"
04:55:07: RADIUS:  Vendor, Cisco [26] 57
04:55:07: RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:31.006 UTC
          Thu Feb 13 2003"
04:55:07: RADIUS: Vendor, Cisco [26] 27
04:55:07: RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW."
04:55:07: RADIUS: Vendor, Cisco [26] 56
04:55:07: RADIUS: Conf-Id [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002
          B935C142"
04:55:07: RADIUS: Vendor, Cisco [26] 34
04:55:07: RADIUS: h323-call-origin [26] 28 "h323-call-origin=originate"
04:55:07: RADIUS: Vendor, Cisco [26] 27
04:55:07: RADIUS: h323-call-type [27] 21 "h323-call-type=VoIP"
04:55:07: RADIUS: Vendor, Cisco [26] 65
04:55:07: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7
          800E0002 B935C142"
04:55:07: RADIUS: Vendor, Cisco [26] 30
04:55:07: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"
04:55:07: RADIUS: Vendor, Cisco [26] 30
04:55:07: RADIUS: Cisco AVpair [1] 24 "session-protocol=cisco"
04:55:07: RADIUS: Vendor, Cisco [26] 35
04:55:07: RADIUS: Cisco AVpair [1] 29 "gw-rxd-cdn=ton:0,npi:0,#:11"
04:55:07: RADIUS: User-Name [1] 4 "22"
04:55:07: RADIUS: Acct-Status-Type [40] 6 Start [1]
04:55:07: RADIUS: Calling-Station-Id [31] 4 "22"
04:55:07: RADIUS: Called-Station-Id [30] 4 "11"
04:55:07: RADIUS: Service-Type [6] 6 Login [1]

04:55:07: RADIUS: NAS-IP-Address [4] 6 1.6.43.101
04:55:07: RADIUS: Acct-Delay-Time [41] 6 0
04:55:07: EM: No consumer registered for event type NEWINFO
04:55:07: EM: Notify the producer not to produce
04:55:07: EM: No consumer registered for event type NEWINFO
04:55:07: EM: Notify the producer not to produce
04:55:08: RADIUS: no sg in radius-timers: ctx 0x65BAB1BC sg 0x0000
04:55:08: RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/50
04:55:08: RADIUS: acct-delay-time for 403963FC (at 403965A1) now 1
04:55:09: RADIUS: no sg in radius-timers: ctx 0x65ADB8EC sg 0x0000
04:55:09: RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/49
04:55:09: RADIUS: acct-delay-time for 40389BFC (at 40389DE6) now 1
04:55:10: RADIUS: no sg in radius-timers: ctx 0x65BAB1BC sg 0x0000
04:55:10: RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/51
04:55:10: RADIUS: acct-delay-time for 403963FC (at 403965A1) now 2
04:55:10: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.8.159.105
04:55:10: RADIUS: Received from id 21645/53 1.8.159.105:1645, Accounting-response, len 20
04:55:10: RADIUS: authenticator 57 EF DD 90 0F 88 76 EA - A5 3D A7 44 0D 90 66 16
04:55:10: vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x1
04:55:10: acct_rsp_status=1 callid= 26, incoming=0, leg=2
04:55:10: vstats_acct_rsp_handler: last acct msg not sent yet. methodlist: h323
04:55:10: RADIUS: no sg in radius-timers: ctx 0x65ADB8EC sg 0x0000
04:55:10: RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/52
04:55:10: RADIUS: acct-delay-time for 40389BFC (at 40389DE6) now 2
04:55:10: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.8.159.105
04:55:10: RADIUS: Received from id 21645/54 1.8.159.105:1645, Accounting-response, len 20
04:55:10: RADIUS: authenticator 97 88 6C BA DA 22 E7 5E - 73 EC 21 C6 36 1B 93 18
04:55:10: vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x1
04:55:10: acct_rsp_status=callid= 25, incoming=1, leg=1
04:55:10: vstats_acct_rsp_handler: last acct msg not sent yet. methodlist: h323
04:55:13: RADIUS(0000001A): Config NAS IP: 0.0.0.0
04:55:13: RADIUS(0000001A): sending
04:55:13: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.203
04:55:13: RADIUS(0000001A): Send Accounting-Request to 1.6.10.203:1646 id 21645/55, len885
04:55:13: RADIUS: authenticator F8 4F F1 30 7E 8B 5B 46 - EF AE 17 2D 5C BA 36 E5
04:55:13: RADIUS: Acct-Session-Id [44]  10 "00000021"
04:55:13: RADIUS: Vendor, Cisco [26] 57
04:55:13: RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:31.006 UTC
          Thu Feb 13 2003"
04:55:13: RADIUS: Vendor, Cisco [26] 27
04:55:13: RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW."
04:55:13: RADIUS: Vendor, Cisco [26] 56
04:55:13: RADIUS: Conf-Id [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002
          B935C142"
04:55:13: RADIUS: Vendor, Cisco [26] 34
04:55:13: RADIUS: h323-call-origin [26] 28 "h323-call-origin=originate"
04:55:13: RADIUS: Vendor, Cisco [26] 27
04:55:13: RADIUS: h323-call-type [27] 21 "h323-call-type=VoIP"
04:55:13: RADIUS: Vendor, Cisco [26] 65
04:55:13: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7
          800E0002 B935C142"
04:55:13: RADIUS: Vendor, Cisco [26] 30
04:55:13: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"
04:55:13: RADIUS: Vendor, Cisco       [26] 30
04:55:13: RADIUS: Cisco AVpair [1] 24 "session-protocol=cisco"
04:55:13: RADIUS: Vendor, Cisco [26] 35
04:55:13: RADIUS: Cisco AVpair [1] 29 "gw-rxd-cdn=ton:0,npi:0,#:11"
04:55:13: RADIUS: Vendor, Cisco [26] 59
04:55:13: RADIUS: h323-connect-time [28] 53 "h323-connect-time=*16:22:31.046 UTC
          Thu Feb 13 2003"
04:55:13: RADIUS: Acct-Input-Octets [42] 6 2241
04:55:13: RADIUS: Acct-Output-Octets [43] 6 81

04:55:13: RADIUS: Acct-Input-Packets [47] 6 113
04:55:13: RADIUS: Acct-Output-Packets [48] 6 5
04:55:13: RADIUS: Acct-Session-Time [46] 6 5
04:55:13: RADIUS: Vendor, Cisco [26] 62
04:55:13: RADIUS: h323-disconnect-tim[29] 56 "h323-disconnect-time=*16:22:36.070 UTC
          Thu Feb 13 2003"
04:55:13: RADIUS: Vendor, Cisco [26] 32
04:55:13: RADIUS: h323-disconnect-cau[30] 26 "h323-disconnect-cause=10"
04:55:13: RADIUS: Vendor, Cisco [26] 38
04:55:13: RADIUS: h323-remote-address[23] 32 "h323-remote-address=14.0.0.110"
04:55:13: RADIUS: Vendor, Cisco [26] 24
04:55:13: RADIUS: Cisco AVpair [1] 18 "release-source=1"
04:55:13: RADIUS: Vendor, Cisco [26] 29
04:55:13: RADIUS: h323-voice-quality [31] 23 "h323-voice-quality=-1"
04:55:13: RADIUS: Vendor, Cisco [26] 57
04:55:13: RADIUS: Cisco AVpair [1] 51 "alert-timepoint=*16:22:31.030 UTC
          Thu Feb 13 2003"
04:55:13: RADIUS: Vendor, Cisco [26] 39
04:55:13: RADIUS: Cisco AVpair [1] 33 "remote-media-address=14.0.0.110"
04:55:13: RADIUS: Vendor, Cisco [26] 44
04:55:13: RADIUS: Cisco AVpair [1] 38 "gw-final-xlated-cdn=ton:0,npi:0,#:11"
04:55:13: RADIUS: Vendor, Cisco [26] 44
04:55:13: RADIUS: Cisco AVpair [1] 38 "gw-final-xlated-cgn=ton:0,npi:1,#:22"
04:55:13: RADIUS: User-Name [1] 4 "22"
04:55:13: RADIUS: Acct-Status-Type [40] 6 Stop [2]
04:55:13: RADIUS: Calling-Station-Id [31] 4 "22"
04:55:13: RADIUS: Called-Station-Id [30] 4 "11"
04:55:13: RADIUS: Service-Type [6] 6 Login [1]
04:55:13: RADIUS: NAS-IP-Address [4] 6 1.6.43.101
04:55:13: RADIUS: Acct-Delay-Time [41] 6 0
04:55:13: RADIUS(00000019): Using existing nas_port 0
04:55:13: RADIUS(00000019):Config NAS IP: 0.0.0.0
04:55:13: RADIUS(00000019):sending
04:55:13: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.203
04:55:13: RADIUS(00000019): Send Accounting-Request to 1.6.10.203:1646 id 21645/56, len766
04:55:13: RADIUS: authenticator 61 60 EB 92 29 5C DE B4 - CE 40 1C AB E3 A1 C8 F7
04:55:13: RADIUS: Acct-Session-Id [44] 10 "00000020"
04:55:13: RADIUS: Vendor, Cisco [26] 57
04:55:13: RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:30.994 UTC Thu
          Feb 13 2003"
04:55:13: RADIUS: Vendor, Cisco [26] 27
04:55:13: RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW."
04:55:13: RADIUS: Vendor, Cisco [26] 56
04:55:13: RADIUS: Conf-Id [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002
          B935C142"
04:55:13: RADIUS: Vendor, Cisco [26] 31
04:55:13: RADIUS: h323-call-origin [26] 25 "h323-call-origin=answer"
04:55:13: RADIUS: Vendor, Cisco [26] 32
04:55:13: RADIUS: h323-call-type [27] 26 "h323-call-type=Telephony"
04:55:13: RADIUS: Vendor, Cisco [26] 65
04:55:13: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7
          800E0002 B935C142"
04:55:13: RADIUS: Vendor, Cisco [26] 30
04:55:13: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"
04:55:13: RADIUS: Vendor, Cisco [26] 35
04:55:13: RADIUS: Cisco AVpair [1] 29 "gw-rxd-cdn=ton:0,npi:0,#:11"
04:55:13: RADIUS: Vendor, Cisco [26]  32
04:55:13: RADIUS: Cisco AVpair [1] 26 "calling-party-category=9"
04:55:13: RADIUS: Vendor, Cisco [26] 33
04:55:13: RADIUS: Cisco AVpair [1] 27 "transmission-medium-req=0"
04:55:13: RADIUS: Vendor, Cisco [26] 59
04:55:13: RADIUS: h323-connect-time [28] 53 "h323-connect-time=*16:22:31.046 UTC Thu
          Feb 13 2003"
04:55:13: RADIUS: Acct-Input-Octets [42] 6 81
04:55:13: RADIUS: Acct-Output-Octets [43] 6 2241

04:55:13: RADIUS: Acct-Input-Packets [47] 6 5
04:55:13: RADIUS: Acct-Output-Packets [48] 6 113
04:55:13: RADIUS: Acct-Session-Time [46] 6 5
04:55:13: RADIUS: Vendor, Cisco [26] 62
04:55:13: RADIUS: h323-disconnect-tim[29] 56 "h323-disconnect-time=*16:22:36.064 UTC
          Thu Feb 13 2003"
04:55:13: RADIUS: Vendor, Cisco [26] 32
04:55:13: RADIUS: h323-disconnect-cau[30] 26 "h323-disconnect-cause=10"
04:55:13: RADIUS: Vendor, Cisco [26] 35
04:55:13: RADIUS: Cisco AVpair [1] 29 "h323-ivr-out=Tariff:Unknown"
04:55:13: RADIUS: Vendor, Cisco [26] 24
04:55:13: RADIUS: Cisco AVpair [1] 18 "release-source=1"
04:55:13: RADIUS: Vendor, Cisco [26] 28
04:55:13: RADIUS: h323-voice-quality [31] 22 "h323-voice-quality=0"
04:55:13: RADIUS: User-Name [1] 4 "22"
04:55:13: RADIUS: Acct-Status-Type [40] 6 Stop [2]
04:55:13: RADIUS: NAS-Port-Type [61] 6 Async [0]
04:55:13: RADIUS: Vendor, Cisco [26] 20
04:55:13: RADIUS: cisco-nas-port [2] 14 "ISDN 6/0:D:1"
04:55:13: RADIUS: NAS-Port [5] 6 0
04:55:13: RADIUS: Calling-Station-Id [31] 4 "22"
04:55:13: RADIUS: Called-Station-Id [30] 4 "11"
04:55:13: RADIUS: Service-Type [6] 6 Login [1]
04:55:13: RADIUS: NAS-IP-Addres       [4] 6 1.6.43.101
04:55:13: RADIUS: Acct-Delay-Time [41] 6 0
04:55:14: RADIUS: no sg in radius-timers: ctx 0x65BAB070 sg 0x0000
04:55:14: RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/55
04:55:14: RADIUS: acct-delay-time for 40553934 (at 40553CA3) now 1
04:55:14: RADIUS: no sg in radius-timers: ctx 0x65BA8284 sg 0x0000
04:55:14: RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/56
04:55:14: RADIUS: acct-delay-time for 405546C4 (at 405549BC) now 1
04:55:15: RADIUS: no sg in radius-timers: ctx 0x65BAB070 sg 0x0000
04:55:15: RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/57
04:55:15: RADIUS: acct-delay-time for 40553934 (at 40553CA3) now 2
04:55:15: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.8.159.105
04:55:15: RADIUS: no sg in radius-timers: ctx 0x65BA8284 sg 0x0000
04:55:15: RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/58
04:55:15: RADIUS: acct-delay-time for 405546C4 (at 405549BC) now 2
04:55:15: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 10.8.159.105
04:55:15: RADIUS: Received from id 21645/59 1.8.159.105:1645, Accounting-response, len 20
04:55:15: RADIUS: authenticator B1 C4 5E FC DB FA 74 A4 - 05 E2 34 52 1A 11 26 06
04:55:15: vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x4
04:55:15: acct_rsp_status=1 callid= 26, incoming=0, leg=2
04:55:15: vstats_acct_rsp_handler: increment since-reset counter
04:55:15: vstats_acct_rsp_handler: increment interval counter
04:55:15: RADIUS: Received from id 21645/60 10.8.159.105:1645, Accounting-response, len 20
04:55:15: RADIUS: authenticator 0E 70 74 2F E5 D8 EE 98 - B9 C0 DA 66 74 ED 84 77
04:55:15: vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x4
04:55:15: acct_rsp_status=1 callid= 25, incoming=1, leg=1
04:55:15: vstats_acct_rsp_handler: increment since-reset counter
04:55:15: vstats_acct_rsp_handler: increment interval counter

The following example shows the collection of records that is in between intervals:

Router# debug voice statistics accounting

Translating "abc-pc"...domain server (255.255.255.255)
vstats_timer_handle_interval_event():Between Intervals!

04:57:37: vstats_acct_interval_end: interval_tag = 5
04:57:37: vstats_acct_interval_end: pushing out, tag=4
04:57:37: vstats_acct_clean_history_stats:
04:57:37: vstats_acct_clean_history_stats: stats (tag=4) not to be deleted
04:57:37: vstats_acct_clean_history_stats: stats (tag=3) not to be deleted
04:57:37: vstats_acct_clean_history_stats: stats (tag=2) not to be deleted
04:57:37: vstats_acct_create_empty_stats:
04:57:37: vstats_acct_create_new_rec_list:
04:57:37: vstats_acct_create_new_rec_list: add acct rec: methodlist=h323, acct-criteria=2
04:57:37: vstats_acct_create_new_rec:
04:57:37: vstats_acct_add_rec_entry:
04:57:37: vstats_acct_add_stats_entry:
04:57:37: vstat_push_driver_file_open():Can not open
ftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162500Z.
errno=65540=Unknown error 65540
vstat_push_drv_activate_ftp_file_tx():open file
(ftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162500Z)=(ftp://sgcp:sgcp@
abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162500Z) failed!
vstats_push_api_push_formatted_text():Start CMD error!

Related Commands

Command
Description

debug event-manager

Enables debugging of the event manager.


debug voice tdsm

To display debugging information for the voice tandem switch, use the debug voice tdsm command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice tdsm [slot/port]

no debug voice tdsm [slot/port]

Syntax Description

slot/port

(Optional) Slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.


Command Modes

Privileged EXEC

Usage Guidelines

This command is valid on the Cisco MC3810 only.

Examples

The following is sample output from the debug voice tdsm command:

Router# debug voice tdsm

Voice tandem switch debugging is on

-1/-1: TDSM(out), ref= -1, state NULL gets event OUT_SETUP
1/1: TDSM(in), ref=6, state CALL_INITIATED gets event IN_CALLPROC
1/1: TDSM(in), ref=6, state OUTG_CALLPROC gets event IN_ALERTING
1/1: TDSM(in), ref=6, state CALL_DELIVERED gets event IN_CONNECT
1/1: TDSM(out),ref=6, state CALL_ACTIVE send out conn. ack
1/1: TDSM(out),ref=6, state CALL_ACTIVE send out release, cause LOCAL_ONHOOK
1/1: TDSM(in), ref=6, state RELEASE_REQ gets event IN_REL_COMP, cause REMOTE_ONHOOK
-1/-1: TDSM(in), ref=-1, state NULL gets event IN_SETUP
-1/-1: TDSM(out), ref=6, state INC_CALLPROC gets event OUT_ALERTING
1/1: TDSM(out),ref=6, state CALL_RECEIVED gets event OUT_CONNECT
1/1: TDSM(in), ref-6, state CONNECT_REQ gets event IN_CONN_ACK
1/1: TDSM(out),ref-6, state CALL_ACTIVE send out release, cause LOCAL_ONHOOK
1/1: TDSM(in), ref=6, state RELEASE_REQ gets event IN_REL_COMP, cause REMOTE_ONHOOK
-1/-1:TDSM(out), ref=-1, state NULL gets event OUT_SETUP
1/1: TDSM(in), ref=7, state CALL_INITIATED gets event IN_CALLPROC
1/1: TDSM(in), ref=7, state OUTG_CALLPROC gets event IN_ALERTING
1/1: TDSM(in), ref=7, state CALL_DELIVERED gets event IN_CONNECT
1/1: TDSM(out),ref=7, state CALL_ACTIVE send out conn.ack
1/1: TDSM(out),ref=7, state CALL_ACTIVE send out release, cause LOCAL_ONHOOK
-1/-1: TDSM(in), ref=-1, state NULL gets event IN_SETUP
-1/-1: TDSM(out), ref=7, state INC_CALLPROC gets event OUT_ALERTING
1/1: TDSM(out),ref=7. state CALL_RECEIVED gets event OUT_CONNECT
1/1: TDSM(in), ref=7, state CONNECT_REQ gets event IN_CONN_ACK
1/1: TDSM(in), ref=7, state CALL_ACTIVE send out release, cause LOCAL_ONHOOK
1/1: TDSM(in), ref=7, state RELEASE_REQ gets event IN_REL_COMP, cause REMOTE_ONHOOK
-1/-1: TDSM(out), ref=-1, state NULL gets event OUT_SETUP
1/1: TDSM(in), ref=8, state CALL_INITIATED gets event IN_CALLPROC
1/1: TDSM(in), ref=8, state OUTG_CALLPROC gets event IN_ALERTINGbug all

Related Commands

Command
Description

debug voice all

Displays debugging information for all components of the Voice Call Manager.

debug voice eecm

Displays debugging information for the Voice End-to-End Call Manager.

debug voice protocol

Displays debugging information for the Voice Line protocol State machine.

debug voice signaling

Displays debugging information for the voice port signaling.

debug voice ccapi

Debugs the call control API.


debug voice translation

To view voice translation rule information, use the debug voice translation command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice translation

no debug voice translation

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(11)T

This command was introduced.


Usage Guidelines

Disable console logging and use buffered logging before using the debug voice translation command. Using the debug voice translation command generates a large volume of debugs, which can affect router performance.

Examples

Sample output from the debug voice translation command is shown below. The output shows the details of the original number following "regxrule_profile_translate".

Following "regxrule_profile_match", the output shows that rule 1 in the translation rule 1001 was a match; then the details of the SED substitution are shown.

Then the output shows the details of the translated number following "regxrule_profile_translate".

In this example, because there was no called number or redirect number translation configured on the translation profile, corresponding errors were generated with a message that no match was found.

Following "regxrule_dp_translate", the output indicates that there is no translation profile for outgoing direction, then it prints the numbers sent to the outgoing SPI.

Router#
00:51:56:regxrule_get_profile_from_trunkgroup:Voice port 0x64143DA8 does not belong to any trunk group
00:51:56:regxrule_get_profile_from_trunkgroup:Voice port 0x64143DA8 does not belong to any trunk group
00:51:56:regxrule_stack_pop_RegXruleNumInfo:stack=0x63DECAF4; count=1
00:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=0
00:51:56:regxrule_profile_translate:number=4088880101 type=unknown plan=unknown numbertype=calling
00:51:56:regxrule_profile_match:Matched with rule 1 in ruleset 1001
00:51:56:regxrule_profile_match:Matched with rule 1 in ruleset 1001
00:51:56:sed_subst:Successful substitution; pattern=4088880101 matchPattern=^.* replacePattern=5551212 replaced pattern=5551212
00:51:56:regxrule_subst_num_type:Match Type = none, Replace Type = none Input Type = unknown
00:51:56:regxrule_subst_num_plan:Match Plan = none, Replace Plan = none Input Plan = unknown
00:51:56:regxrule_profile_translate:xlt_number=5551212 xlt_type=unknown xlt_plan=unknown
00:51:56:regxrule_profile_translate:number= type=UNKNOWN plan=UNKNOWN numbertype=redirect-called
00:51:56:regxrule_get_RegXrule:Invalid translation ruleset tag=0
00:51:56:regxrule_profile_match:Error:ruleset for redirect-called number not found
00:51:56:regxrule_profile_translate:No match:number= type=UNKNOWN plan=UNKNOWN
00:51:56:regxrule_profile_translate:number=5108880101 type=unknown plan=unknown numbertype=called
00:51:56:regxrule_get_RegXrule:Invalid translation ruleset tag=0
00:51:56:regxrule_profile_match:Error:ruleset for called number not found
00:51:56:regxrule_profile_translate:No match:number=5108880101 type=unknown plan=unknown
00:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=1
00:51:56:regxrule_dp_translate:No profile found in peer 5108888 for outgoing direction
00:51:56:regxrule_dp_translate:calling_number=5551212 calling_octet=0x0
called_number=5108880101 called_octet=0x80
redirect_number= redirect_type=4294967295 redirect_plan=4294967295
00:51:56:regxrule_stack_pop_RegXruleNumInfo:stack=0x63DECAF4; count=2
00:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=1

Table 330 provides an alphabetical listing of the debug voice translation command fields and a description of each field.

Table 330 debug voice translation Field Descriptions 

Field
Description

called_number

Called number dialed number identification service (DNIS).

called_octet

Octect3 of called IE.

calling_number

Calling number automatic number identifier (ANI).

calling_octect

Octect3 of calling IE.

count

Number of elements in the translation stack.

Input Plan

Numbering plan of the input.

Input Type

Numbering type of the input.

matchPattern

Regular exp used for matching.

Match Plan

Numbering plan in the translation rule.

Match Type

Numbering type in the translation rule.

number

Incoming number for translation.

numbertype

Type of number: calling, called, or redirect.

pattern

Input string to the regular expression for matching.

plan

Numbering plan.

redirect_number

Redirect number.

redirect_plan

Numbering plan in the redirect number.

redirect_type

Numbering type in the redirect number.

replaced pattern

Final string after applying replacement rule of translation rule.

replacePattern

Replacement pattern in the translation rule.

Replace Plan

Replacement numbering plan in the translation rule.

Replace Type

Replacement numbering type in the translation rule.

stack

Value of the translation rule stack.

tag

Tag of the translation rule.

type

Numbering type in the translation rule.

xlt_number

Number after translation.

xlt_plan

Numbering plan after translation.

xlt_type

Numbering type after translation.


Related Commands

Command
Description

rule (voice translation-rule)

Defines the translation rule parameters for matching and replacing call number patterns.

show voice translation-rule

Displays a voice translation rule.

test voice translation-rule

Tests a voice translation rule.

voice translation-rule

Initiates the translation rule definition.


debug voice uri

To display debugging messages for uniform resource identifier (URI) voice classes, use the debug voice uri command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice uri

no debug voice uri

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(4)T

This command was introduced.


Usage Guidelines

Use this command to see which URI voice class and dial peer is matched for a Session Initiation Protocol (SIP) or telephone (TEL) URI.

Examples

The following examples show output from the debug voice uri command. Comments are imbedded in the examples.

Router# debug voice uri

Output Showing Failed Match of Voice URI Class

The following output displays when an outbound dial peer match fails for the URL sip:9991234@sip.tgw.com?Subject=sip_e164_headers_plus.tcl&AccountInfo=12345&Priority=Urgent

*Jul 11 05:20:44.759:vuri_match_class:tag (767)

The first dial peer in the list is 767, which contains the destination uri 767 command. 767 is a TELURI class, so it does not match the above URL.

*Jul 11 05:20:44.759:vuri_match_class:tag (766)

The next dial peer, 766, contains the destination uri 766 command.

*Jul 11 05:20:44.759:vuri_match_class_sip:sip:9991234@sip.tgw.com?Subject=sip_e164_headers_plus.tc l&AccountInfo=12345&Priority=Urgent did not match pattern

766 is a SIP URI class and contains only the pattern command. The regex does not match the pattern, so there is no match.

*Jul 11 05:20:44.759:vuri_match_class:tag (999)

The next dial peer, 999, contains the destination uri 999 command.

*Jul 11 05:20:44.759:vuri_match_class_sip:Match with phone context
*Jul 11 05:20:44.759:vuri_match_class_sip:input ()

If the phone context command is not present in the URI class, it is skipped.

*Jul 11 05:20:44.759:vuri_match_class_sip:Match with host
*Jul 11 05:20:44.759:vuri_match_class_sip:input (sip.tgw.com)

If the host command is not present in the URI class, it is skipped.

*Jul 11 05:20:44.759:vuri_match_class_sip:Match with user-id
*Jul 11 05:20:44.759:vuri_match_class_sip:input (9991234)

Try to match with the user-id portion of the URL, which is 9991234.

*Jul 11 05:20:44.759:vuri_match_class_sip:Match failed

The configured pattern, however, is "driver" and it is not a match.

Output Showing Successful Match of Voice URI Class

The following debugging output is displayed when an outbound dial peer match is done for the URL sip:driver@cisco.com:

*Jul 11 06:06:30.119:vuri_match_class:tag (767)

The first dial peer in the list is 767 and it contains the destination uri 767 command. 767 is a TEL URI class, so it does not match with the above URL.

*Jul 11 06:06:30.119:vuri_match_class:tag (766)

The next dial peer, 766, contains the destination uri 766 command. Verify if the URL matches URI class 766.

*Jul 11 06:06:30.119:vuri_match_class_sip:sip:driver@cisco.com did not match pattern

The URL does not match with the pattern command.

*Jul 11 06:06:30.119:vuri_match_class:tag (999)

The next dial peer, 999, contains the destination uri 999 command.

*Jul 11 06:06:30.119:vuri_match_class_sip:Match with phone context
*Jul 11 06:06:30.119:vuri_match_class_sip:input ()

If the phone context command is not configured, it is skipped.

*Jul 11 06:06:30.119:vuri_match_class_sip:Match with host
*Jul 11 06:06:30.119:vuri_match_class_sip:input (cisco.com)

If the host command is not configured under the class, it is skipped.

*Jul 11 06:06:30.119:vuri_match_class_sip:Match with user-id
*Jul 11 06:06:30.119:vuri_match_class_sip:input (driver)

If the user-id command is not configured, the user-id portion from the URL is "driver."

*Jul 11 06:06:30.119:vuri_match_class_sip:driver matched; match length (6)

There is a match with the configured pattern. The number of characters that matched is 6.

Related Commands

Command
Description

destination uri

Specifies the voice class used to match the dial peer to the destination URI for an outgoing call.

incoming uri

Specifies the voice class that a VoIP dial peer uses to match the URI of an incoming call.

show dialplan incall uri

Displays which dial peer is matched for a specific URI in an incoming call.

show dialplan uri

Displays which outbound dial peer is matched for a specific destination URI.

voice class uri

Creates or modifies a voice class for matching dial peers to a SIP or TEL URI.


debug voice vofr

To show Cisco trunk and FRF.11 trunk call setup attempts and to show which dial peer is used in the call setup, use the debug voice vofr command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voice vofr

no debug voice vofr

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.


Usage Guidelines

This command applies to Cisco trunks and FRF.11 trunks only; it does not apply to switched calls.

This command applies to VoFR, VoATM, and VoHDLC dial peers on the Cisco MC3810 device.

Examples

The following example shows sample output from the debug voice vofr command for a Cisco trunk:

Router# debug voice vofr

1d05h: 1/1:VOFR, unconf ==> pending_start
1d05h: 1/1:VOFR,create VOFR
1d05h: 1/1:VOFR,search dial-peer 7100 preference 0
1d05h: 1/1:VOFR, pending_start ==> start
1d05h: 1/1:VOFR,
1d05h:voice_configure_perm_svc:
1d05h:dial-peer 7100 codec = G729A payload size = 30 vad = off dtmf relay = on
seq num = off
1d05h:voice-port 1/1 codec = G729A payload size = 30 vad = off dtmf relay = on
seq num = off
1d05h: 1/1:VOFR,SIGNAL-TYPE = cept
1d05h:init_frf11 tcid 0 master 0 signaltype 2
1d05h:Going Out Of Service on tcid 0 with sig state 0001
1d05h: 1/1:VOFR, start get event idle
1d05h: 1/1:VOFR, start get event
1d05h: 1/1:VOFR, start get event set up
1d05h: 1/1:VOFR, start ==> pending_connect
1d05h: 1/1:VOFR, pending_connect get event connect
1d05h: 1/1:VOFR, pending_connect ==> connect
1d05h: 1/1:VOFR,SIGNAL-TYPE = cept
1d05h:init_frf11 tcid 0 master 1 signaltype 2
1d05h:start_vofr_polling on port 0 signaltype 2

The following example shows sample output from the debug voice vofr command for an FRF.11 trunk:

Router# debug voice vofr

1d05h: 1/1:VOFR,search dial-peer 7200 preference 2
1d05h: 1/1:VOFR,SIGNAL-TYPE = cept
1d05h:Launch Voice Trunk:signal-type 2
1d05h:calculated bandwidth = 10, coding = 6, size = 30
1d05h:%Voice-port 1/1 is down.
1d05h: 1/1:VOFR, pending_start get event idle
1d05h:Codec Type = 6 Payload Size = 30 Seq# off
1d05h:%Voice-port 1/1 is up.
1d05h:init_frf11 tcid 0 master 1 signaltype 2
1d05h:status OK :cid = 100
1d05h: 1/1:VOFR,
1d05h:start FRF11
1d05h: 1/1:VOFR, pending_start ==> frf11
1d05h: 1/1:VOFR,SIGNAL-TYPE = cept

Related Commands

Command
Description

debug ccfrf11 session

Displays the ccfrf11 function calls during call setup and teardown.

debug ccsip all

Displays the ccswvoice function calls during call setup and teardown.

debug ccswvoice vofr-session

Displays the ccswvoice function calls during call setup and teardown.

debug frame-relay fragment

Displays information related to Frame Relay fragmentation on a PVC.

debug vpm error

Displays the behavior of the Holst state machine.

debug vtsp port

Displays the behavior of the VTSP state machine.

debug vtsp vofr subframe

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


debug voip aaa

To enable debugging messages for gateway authentication, authorization, and accounting (AAA) to be sent to the system console, use the debug voip aaa command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip aaa

no debug voip aaa

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)XB

This command was implemented on the Cisco AS5850 in the Cisco IOS Release 12.2(2)XB.

12.2(11)T

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


Examples

The following is sample output from the debug voip aaa command:

Router# debug voip aaa

VoIP AAA debugging is enabled

Router# show debug

voip aaa:
voip aaa debugging is on

debug voip ais

To enable debugging of the application information system (AIS) database, use the debug voip ais command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ais

no debug voip ais

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(8)T

This command was introduced.


Examples

The following is sample output from the debug voip ais command:

Router# debug voip ais

voip AIS debugging is on
Router#
*Jul 18 22:18:30.947: ais_appinst_create_record: new app inst record is created for sid=10, app_name=generic, stats:avail, elog:avail
*Jul 18 22:18:30.947: ais_appinst_insert_record_to_active: app inst sid=A is inserted to active tree
*Jul 18 22:18:30.963: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au
*Jul 18 22:18:30.963: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245
*Jul 18 22:18:30.963: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC)
Router#
*Jul 18 22:18:46.468: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au
*Jul 18 22:18:46.468: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245
*Jul 18 22:18:46.468: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC)
Router#
*Jul 18 22:18:51.520: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au
*Jul 18 22:18:51.520: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245
*Jul 18 22:18:51.520: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC)
Router#
*Jul 18 22:18:56.573: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au
*Jul 18 22:18:56.573: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245
*Jul 18 22:18:56.573: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC)
Router#
*Jul 18 22:19:01.625: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au
*Jul 18 22:19:01.625: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245
*Jul 18 22:19:01.625: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC)
*Jul 18 22:19:01.949: propagate_history_stats: stats for app inst 10 is propagated to application (generic) and gateway level
*Jul 18 22:19:01.949: ais_appinst_move_record_active_to_history: session record (sid=A) is moved to history repository

Related Commands

Command
Description

call application event-log

Enables event logging for voice application instances.

call application stats

Enables statistics collection for voice applications.

debug voip event-log

Enables debugging of the event log module.


debug voip application

To display all application debug messages, use the debug voip application command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip application [accounting | all | callfeature | callsetup | core | datastruct | digitcollect | error | linking | media [packet | state] | oodrefer | redirect | script | session | settlement | states | supplementary-service | tclcommands]

no debug voip application [accounting | all | callfeature | callsetup | core | datastruct | digitcollect | error | linking | media [packet | state] | oodrefer | redirect | script | session | settlement | states | supplementary-service | tclcommands]

Syntax Description

accounting

(Optional) Displays Voice over IP (VoIP) accounting messages.

all

(Optional) Displays all application debug messages.

callfeature

(Optional) Displays call feature debugs.

callsetup

(Optional) Displays the call setup being processed.

core

(Optional) Displays debug messages for the Application Framework (AFW) core libraries.

datastruct

(Optional) Displays debug messages for AFW data structures.

digitcollect

(Optional) Displays digits collected during the call.

error

(Optional) Displays application errors.

linking

(Optional) Displays script linking debugs.

media

(Optional) Displays debug traces for application media events.

oodrefer

(Optional) Displays debug messages for the Out-of-Dialog REFER (OOD-R) feature.

redirect

(Optional) Displays call redirection handler debugs.

script

(Optional) Displays script debugs.

session

(Optional) Displays default session application debugs.

settlement

(Optional) Displays debug messages for application settlement activities.

states

(Optional) Displays debug traces for application states.

supplementary-service

(Optional) Provides application layer tracing related to the processing of supplementary services requests.

tclcommands

(Optional) Displays debug messages for Tool Command Language (Tcl) commands used in application scripts.


Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(15)ZJT

This command was introduced.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T. This command replaces the debug voip ivr applib, debug voip ivr callsetup, debug voip ivr digitcollect, debug voip ivr redirect, and debug voip ivr supplementary-service commands.

12.3(7)T

Reporting of H.450 capabilities was introduced.

12.4(4)T

The callfeature keyword was added.

12.4(4)XC

The accounting keyword was added.

12.4(9)T

The accounting keyword was integrated into Cisco IOS Release 12.4(9)T

12.4(11)XJ

The oodrefer keyword was added.

12.4(15)T

The oodrefer keyword was integrated into Cisco IOS Release 12.4(15)T.


Usage Guidelines

If you do not use any keywords, the debug voip application command displays application programming interface (API) libraries being processed.

The debug voip application all command differs from the debug voip ivr all command. The debug voip application all command enables all application framework debugs. The debug voip ivr all command enables both Application Framework Session debugs and interactive voice response (IVR) debugs.

Examples

The following is sample output from the debug voip application callsetup command:

Router# debug voip application callsetup

ivr call setup debugging is on
Router#
*Mar 7 22:08:40.032://7//APPL:/afsSettlementValidateCall:target=, tokenp=0x0
*Mar 7 22:08:41.864://-1//PCM :LP:HN23A698CC:HN23A691A4:/InitiateCallSetup:Mode 1 RedirectMode 6 Incoming leg[-1] AlertTime -1 Destinations(1) [ 405 ]
*Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/InitiateCallSetup:Destination 0 guid :231D511B.1A5F11CC.800BB191.E9DE175D
*Mar 7 22:08:41.868: incoming_guid :00000000.00000000.00000000.00000000
*Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNInitiate:Destination[405]
*Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNMatchDialPeer:
*Mar 7 22:08:41.868: src carrier id:, tgt carrier id:
*Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNQueuePeers:Matched peers(1)
*Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNSetupPeer: Destination 0x6221092C
*Mar 7 22:08:41.872://-1//PCM :HN23A698D0:/DNSetupPeer:dialpeer tags for Rotary = 400
*Mar 7 22:08:41.872://-1//PCM :HN23A698D0:/DNSetupPeer:
*Mar 7 22:08:41.872:Destination SetupPeer cid(-1), destPat(405), match(2), prefix(), peer(630D95B0)
*Mar 7 22:08:41.872://-1//PCM :HN23A698D0:/DNSettlementMatrixCheck:retcode=1 cid(-1) trans=0x0, provider=0 No settle-call present
*Mar 7 22:08:41.940://8//PCM :/DNHandler:(DN_SETTING[2])--(CC_EV_CALL_PROCEEDING[25])--IGNORED-->>(DN_SETTING[2])
*Mar 7 22:08:41.940://8//PCM :/CS_Setting_PROCEED:
*Mar 7 22:08:41.940://8//PCM :/CSPopLegAndWait:
*Mar 7 22:08:41.940://8//PCM :/CallSetupHandler:(CS_SETTING[0]) -----(CS_EV_PROCEEDING[3])------->>>(CS_SETTING[0])
*Mar 7 22:08:41.948://-1//PCM :HN23A698CC:/CSInterceptEvent:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_SETTING)
*Mar 7 22:08:41.948://8//PCM :/CSInterceptEvent:(CS_SETTING[0]) intercepting CS_EV_PROGRESS leg 8 (Mask=12)
*Mar 7 22:08:41.948://-1//PCM :HN23A698CC:/CSInterceptEvent:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_SETTING)
*Mar 7 22:08:41.952://-1//PCM :HN23A698CC:/CallSetupContinueEvent:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_SETTING)
*Mar 7 22:08:41.956://8//PCM :/CS_CutProgress:
*Mar 7 22:08:41.956://8//PCM :/CSPopLegAndWait:
*Mar 7 22:08:41.956://8//PCM :/CallSetupContinueEvent:(CS_SETTING[0]) -----(CS_EV_PROGRESS[15])------->>>(CS_CONFEDALERT[5])
*Mar 7 22:08:41.956://-1//PCM :HN23A698CC:/CallSetupHandleQueueEvents:
*Mar 7 22:08:41.956://8//PCM :/CallSetupContinueEvent: *** Leaving function ***CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_CONFEDALERT)
*Mar 7 22:08:43.864://8//PCM :/CS_ConfedAlert_CONNECTED:no of Destinations:1
*Mar 7 22:08:43.864://-1//PCM :HN23A698CC:/CSDiscReturnAndEmptyLegALL:
*Mar 7 22:08:43.864://8//PCM :/CSPopLegAndWait:
*Mar 7 22:08:43.864://-1//PCM :HN23A698CC:/CSReturnIFDone:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_CONFED)
*Mar 7 22:08:43.864:CallSetupDump:CallSetup[0x6320B998] State:CS_CONFED[3] #Handler=1 #Waits=1#Objects=2
*Mar 7 22:08:43.864:All Destinations:
*Mar 7 22:08:43.864:DestinationDump:Destination[0x6221092C]:DN_SETTING[2] Holding[0] Leg[8]
*Mar 7 22:08:43.864:settlement_in_use:0 settlement_transaction:0x0 settlement_provider:0 settlement_type:0 settlement_callvalid:1 busyRotary:0
*Mar 7 22:08:43.864:WaitList of Destinations:{HAN[DN_HAND ][CS_HAND ] ( )}
*Mar 7 22:08:43.868:Handler Tree{HAN[CS_HAND ][AFS_HAND] ( HAN[DN_HAND][CS_HAND ][FALSE] [UC=1 ]LEG[8 ][CS_HAND ][LEG_OUTCONNECTED(8)][Cause(0)][UC=1 ])}
*Mar 7 22:08:43.868:{HAN[DN_HAND ][CS_HAND ] ( )}
*Mar 7 22:08:43.868:
*Mar 7 22:08:43.868:Handler Tree Trace
*Mar 7 22:08:43.868://-1//PCM :HN23A698D0:/DNCleanup:Terminate=TRUE Status DN_SUCCESS Leg[8]
*Mar 7 22:08:43.868://-1//PCM :HN23A698D0:/DNSettlementCleanup:cid(-1) trans=0x0, provider=0
*Mar 7 22:08:43.868://-1//PCM :HN23A698D0:/DNSetFree:
*Mar 7 22:08:43.868://-1//PCM :HN23A698CC:/CSReturnIFDone:CallSetup[0x6320B998] handlercount=0 #Waits=0 #Objects=1 (CS_CONFED)
*Mar 7 22:08:43.872://-1//PCM :HN23A698CC:/CSReturnIFDone: decoupled extern connection
*Mar 7 22:08:43.872://-1//PCM :HN23A698CC:/CSReturnIFDone:CallSetup Returning(ls_000 Status CS_ACTIVE)
*Mar 7 22:08:43.872://8//PCM :/CallSetupHandler:(CS_CONFEDALERT[5]) -----(CS_EV_CONNECTED[5])------->>>(CS_CONFED[3])
*Mar 7 22:08:43.872://-1//PCM :HN23A698CC:/CallSetupCleanup:Terminate=FALSE
*Mar 7 22:08:43.876://-1//PCM :HN23A698CC:/CallSetupCleanup:State CS_CONFED

The following is sample output from the debug voip application digitcollect command:

Router# debug voip application digitcollect

ivr digit collect debugging is on
Router#
*Mar 7 22:09:08.108://9//DCM :/DigitCollect:DialPlan=TRUE AbortKey= TermKey=# NumPatts=0
Enable=FALSE InterruptPrompt=FALSE maxDigits=0 DialPlanTerm=FALSE
*Mar 7 22:09:08.108://9//APPL:/AppTypeAheadGetDigit:no chars in buffer.
*Mar 7 22:09:08.112://9//DCM :/act_DCRunning_RDone:callid=9 Enable succeeded.enable=0 matchDialplan=1 numPatterns=0matchDialplanTerm=0
*Mar 7 22:09:11.428://9//APPL:/AppVcrControlEvent:VCR Control, not enabled.---
*Mar 7 22:09:11.428://9//APPL:/AppTypeAheadEvent:Passing, not enabled.---
*Mar 7 22:09:11.428://9//DCM :/act_DCRunning_Digit::pLeg 9 Digit 4 Tone Mode 0
*Mar 7 22:09:11.428://9//DCM :/DCTreatDigit:
*Mar 7 22:09:11.428://-1//DCM :HN23A6FF50:/DCTreatDigit:
*Mar 7 22:09:11.428: src carrier id:, tgt carrier id:
*Mar 7 22:09:11.428://-1//DCM :HN23A6FF50:/DCTreatDigit:Match single infotype
*Mar 7 22:09:11.676://9//APPL:/AppVcrControlEvent:VCR Control, not enabled.---
*Mar 7 22:09:11.676://9//APPL:/AppTypeAheadEvent:Passing, not enabled.---
*Mar 7 22:09:11.676://9//DCM :/act_DCRunning_Digit::pLeg 9 Digit 0 Tone Mode 0
*Mar 7 22:09:11.676://9//DCM :/DCTreatDigit:
*Mar 7 22:09:11.680://-1//DCM :HN23A6FF50:/DCTreatDigit:
*Mar 7 22:09:11.680: src carrier id:, tgt carrier id:
*Mar 7 22:09:11.680://-1//DCM :HN23A6FF50:/DCTreatDigit:Match single infotype
*Mar 7 22:09:11.908://9//APPL:/AppVcrControlEvent:VCR Control, not enabled.---
*Mar 7 22:09:11.908://9//APPL:/AppTypeAheadEvent:Passing, not enabled.---
*Mar 7 22:09:11.908://9//DCM :/act_DCRunning_Digit::pLeg 9 Digit 5 Tone Mode 0
*Mar 7 22:09:11.908://9//DCM :/DCTreatDigit:
*Mar 7 22:09:11.908://-1//DCM :HN23A6FF50:/DCTreatDigit:
*Mar 7 22:09:11.908: src carrier id:, tgt carrier id:
*Mar 7 22:09:11.908://-1//DCM :HN23A6FF50:/DCTreatDigit:Match single infotype
*Mar 7 22:09:11.912://9//DCM :/act_DCRunning_RDone:callid=9 Reporting disabled.
*Mar 7 22:09:11.912://-1//DCM :HN23A6FF50:/DigitCollectComplete:Status 4=DC_MATCHED_DIALPLAN. Digits=405
*Mar 7 22:09:11.916://-1//DCM :HN23A6FF50:/DCHandlerCleanup:

The following is sample output from the debug voip application session command:

Router# debug voip application session

applib session debugging is on
*Apr 4 23:57:08.054://-1//APPL:HN04B2BC78:LG35:/AFS_CALLSETUPIND:Calling #(4155550154), Called #(52984), peer_tag(1)
*Apr 4 23:57:08.054://-1//APPL:HN04B2BC78:LG35:/afsSetupCall:Called #(52984)
*Apr 4 23:57:08.058://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CALLINIT)--(CC_EV_CALL_SETUP_IND)- ->>(CONTACTINGDEST)
*Apr 4 23:57:08.466://-1//APPL:HN04B2BC78:LG36:/AFS_ContactingDest_ALERT:
*Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:LG36:/AFS_ContactingDest_ALERT:inID(35), outID(36), outbnd peer_tag(6), prog_ind(8)
*Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:LG36:/afsMsgHandler:(CONTACTINGDEST)--(CC_EV_CALL_ALERT )-->>(CONFINGALERT)
*Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:CN11:/AFS_ConfingAlert_CREATEDONE: {HAN[AFS_HAND][NULL ] ( LEG[35 ][AFS_HAND][LEG_INCALERTING(4)][Cause(0)][UC=1 ]HAN[CS_HAND][AFS_HAND][FALSE] [UC=1 ]LEG[36 ][CS_HAND ][LEG_OUTINIT(6)][Cause(0)][UC=1 ]CON[11 ][AFS_HAND][CONNECTION_CONFED(2)] [UC=1 ])}
*Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:CN11:/afsMsgHandler:(CONFINGALERT)--(CC_EV_CONF_CREATE_ DONE)-->>(CONFEDALERT)
*Apr 4 23:57:08.478://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CONFEDALERT)--(CC_EV_VOICE_MODE_DO NE)-->>(CONFEDALERT)
*Apr 4 23:57:24.162://-1//APPL:HN04B2BC78:HN04B2BC78:/AFS_ConfedAlert_SETUPDONE:
*Apr 4 23:57:24.162://-1//APPL:HN04B2BC78:HN04B2BC78:/afsAppHandlerCleanup:CS_HAND
*Apr 4 23:57:24.162://-1//APPL:HN04B2BC78:/afsMsgHandler:(CONFEDALERT)--(APP_EV_CALLSETUP_DONE)-- >>(CALLACTIVE)
*Apr 4 23:57:24.182://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CALLACTIVE)--(CC_EV_VOICE_MODE_DON E)-->>(CALLACTIVE)
*Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:LG35:/AFS_DISCONNECT:
*Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CALLACTIVE)--(CC_EV_CALL_DISCONNEC TED)-->>(CALLDISCONNECT)
*Apr 4 23:57:34.838://-1//APPL:/afsCallProcess: [HANDLERDONE_EVENT_END]
*Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:/afsHNDCleanup:Terminate TRUE Terminated FALSE{HAN[AFS_HAND][NULL ] ( LEG[35 ][AFS_HAND][LEG_INCCONNECTED(5)][Cause(16)][UC=1 ]LEG[36 ][AFS_HAND][LEG_OUTCONNECTED(8)][Cause(0)][UC=1 ]CON[11 ][AFS_HAND][CONNECTION_CONFED(2)] [UC=1 ])}
*Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:CN11:/afsMsgHandler:(CC_EV_CONF_DESTROY_DONE)
*Apr 4 23:57:34.854://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CC_EV_CALL_DISCONNECT_DONE)
*Apr 4 23:57:34.862://-1//APPL:HN04B2BC78:LG36:/afsMsgHandler:(CC_EV_CALL_DISCONNECT_DONE)
*Apr 4 23:57:34.862://-1//APPL:/afsCallProcess: [HANDLERDONE_EVENT_END]
*Apr 4 23:57:34.862://-1//APPL:HN04B2BC78:/afsHNDCleanup:Terminate TRUE Terminated TRUE{HAN[AFS_HAND][NULL ] ( )}
*Apr 4 23:57:34.862://-1//APPL:HN04B32530:/afsFreeHND:Hndlr returned to the free queue

The following sample output shows an inbound call on a system with H.450.2, H.450.3, and H.450.12 capabilities enabled:

Router# debug voip application supplementary-service

supplementary service debugging is on
Jan 21 01:12:21.433://-1//APPL:/SSProcessH450CommonInfoEvent: CI_INFORM featureList=0xC0000000 featureValue[0][0] featureControl=0x0

Jan 21 01:12:21.433://-1//APPL:/AppStoreCommonInfoToLeg:Leg peer_tag=8100
Jan 21 01:12:21.433://-1//APPL:/AppStoreCommonInfoToLeg:Received ciInform, store ss_support=0xE000 to leg.
Jan 21 01:12:21.433://-1//APPL:/AppPrepareCommonInfo:Not voip dialpeer, no common info sent.
Jan 21 01:12:21.437://-1//APPL:/AppPrepareCommonInfoRequestReceived:Leg peer_tag=8100
Jan 21 01:12:21.437://-1//APPL:/AppPrepareCommonInfo:Global H450_2=1 H450_3=1 H450_12_ADV=1 H450_12_USAGE=1
Jan 21 01:12:21.437://-1//APPL:/AppPrepareCommonInfoContent:SS_CI ss_evt=18 featureList=0xC0000000 featureValues=[0][0][0][0] featureControl=0x0

Table 331 describes the significant fields shown in the displays above.

Table 331 debug voip application Field Descriptions 

Field
Description

Called #

Called # may not appear in the initial /AFS_CALLSETUPIND message; it appears later in the /afsSetupCall message.

peer_tag

Dial peer tag.

/afsFreeHND

Verifies that the application completed properly.

H450_2

A value of 0 indicates that H.450.2 capabilities are disabled.
A value of 1 indicates that H.450.2 capabilities are enabled.

H450_3

A value of 0 indicates that H.450.3 capabilities are disabled.
A value of 1 indicates that H.450.3 capabilities are enabled.

H450_12_ADV= 0 and H450_12_USAGE = 0

H.450.12 capabilities are disabled.

H450_12_ADV= 1 and H450_12_USAGE = 0

H.450.12 capabilities are enabled in advertise-only mode.

H450_12_ADV= 1 and H450_12_USAGE = 1

H.450.12 capabilities are enabled.


The following is sample output from the debug voip application accounting command:

Router# debug voip application accounting

*Jan 6 19:34:22.535: //-1//Dest:/DestSetup:
*Jan 6 19:34:22.535: :DestSetup iw inc guid is 0-0-0-0
*Jan 6 19:34:22.535: //-1//Dest:/DestSetup:
*Jan 6 19:34:22.535: :DestSetup iw guid is 45AB9E05-7E2211DA-8088D216-195F6285
*Jan 6 19:34:22.535: :DestSetup iw guid is 45AB9E05-7E2211DA-8088D216-195F6285
*Jan 6 19:34:22.539: //-1//Dest:/DestSetup:
*Jan 6 19:34:22.539: :DestSetup setup inc guid is 0-0-0-0
*Jan 6 19:34:22.539: //-1//Dest:/DestSetup:
*Jan 6 19:34:22.539: :DestSetup setup guid is 45AB9E05-7E2211DA-8088D216-195F6285
*Jan 6 19:34:45.667: //-1//Dest:/DestSetup:
*Jan 6 19:34:45.667: :DestSetup iw inc guid is 0-0-0-0
*Jan 6 19:34:45.667: //-1//Dest:/DestSetup:
*Jan 6 19:34:45.671: :DestSetup iw guid is 527B07DA-7E2211DA-808DD216-195F6285
*Jan 6 19:34:45.671: :DestSetup iw guid is 527B07DA-7E2211DA-808DD216-195F6285
*Jan 6 19:34:45.671: //-1//Dest:/DestSetup:
*Jan 6 19:34:45.671: :DestSetup setup inc guid is 0-0-0-0
*Jan 6 19:34:45.671: //-1//Dest:/DestSetup:
*Jan 6 19:34:45.671: :DestSetup setup guid is 527B07DA-7E2211DA-808DD216-195F6285
*Jan 6 19:35:04.975: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 45AB9E05 7E2211DA 8088D216 195F6285, SetupTime *19:34:22.535 UTC Fri Jan 6 2006, PeerAddress 1011011007, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime *19:34:25.135 UTC Fri Jan 6 2006, DisconnectTime *19:35:04.975 UTC Fri Jan 6 2006, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0
*Jan 6 19:35:04.991: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 527B07DA 7E2211DA 808DD216 195F6285, SetupTime *19:34:43.861 UTC Fri Jan 6 2006, PeerAddress 1011011007, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime *19:34:46.451 UTC Fri Jan 6 2006, DisconnectTime *19:35:04.991 UTC Fri Jan 6 2006, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0
*Jan 6 19:36:05.627: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 45AB9E05 7E2211DA 8088D216 195F6285, SetupTime *19:34:22.377 UTC Fri Jan 6 2006, PeerAddress 1011011006, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime *19:34:25.137 UTC Fri Jan 6 2006, DisconnectTime *19:36:05.627 UTC Fri Jan 6 2006, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0
*Jan 6 19:36:05.631: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 527B07DA 7E2211DA 808DD216 195F6285, SetupTime *19:34:45.671 UTC Fri Jan 6 2006, PeerAddress 1011011008, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime *19:34:46.451 UTC Fri Jan 6 2006, DisconnectTime *19:36:05.631 UTC Fri Jan 6 2006, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0
*Jan 6 19:36:12.287: %IPPHONE-6-UNREGISTER_NORMAL: ephone-6:SEP111100011006 IP:10.3.32.56 Socket:1 DeviceType:Phone has unregistered normally.
*Jan 6 19:36:12.287: %IPPHONE-6-UNREGISTER_NORMAL: ephone-7:SEP111100011007 IP:10.3.32.56 Socket:2 DeviceType:Phone has unregistered normally.
*Jan 6 19:36:12.295: %IPPHONE-6-UNREGISTER_NORMAL: ephone-8:SEP111100011008 IP:10.3.32.56 Socket:3 DeviceType:Phone has unregistered normally.
*Jan 6 19:36:13.227: %SYS-5-CONFIG_I: Configured from console by console

The following is sample output from the debug voip application oodrefer command:

Router# debug voip application oodrefer

Aug 22 18:16:21.625: //-1//AFW_:/C_ServiceThirdParty_Event_Handle:
Aug 22 18:16:21.625: //-1//AFW_:/AFW_ThirdPartyCC_New:
Aug 22 18:16:21.625: //-1//AFW_:EE461DC520000:/C_PackageThirdPartyCC_NewReq: ThirdPartyCC module listened by TclModule_45F39E28_0_91076048
Aug 22 18:16:21.625: //-1//AFW_:EE461DC520000:/OCOpen_SetupRequest: Refer Dest1: 1011, Refer Dest2: 1001; ReferBy User: root
Aug 22 18:16:21.693: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_1:
Aug 22 18:16:21.693: //-1//AFW_:/Third_Party_CC_Send_Notify: Third_Party_CC_Send_Notify: sending notify respStatus=2, final=FALSE, failureCause=16
Aug 22 18:16:21.693: //-1//AFW_:/Third_Party_CC_Send_Notify: AppNotify successful!
Aug 22 18:16:26.225: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_1:
Aug 22 18:16:26.229: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_1:
Aug 22 18:16:26.249: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_2:
Aug 22 18:16:29.341: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_2:
Aug 22 18:16:29.341: //-1//AFW_:/Third_Party_CC_Send_Notify: Third_Party_CC_Send_Notify: sending notify respStatus=4, final=TRUE, failureCause=16
Aug 22 18:16:29.341: //-1//AFW_:/Third_Party_CC_Send_Notify: AppNotify successful!
Aug 22 18:16:29.349: //-1//AFW_:EE461DC520000:/OCHandle_Handoff: BAG contains:
Aug 22 18:16:29.349: LEG[895 ][LEG_INCCONNECTED(5)][Cause(0)]
Aug 22 18:16:29.349: CON[7 ][CONNECTION_CONFED(2)] {LEG[895 ][LEG_INCCONNECTED(5)][Cause(0)],LEG[896 ][LEG_OUTCONNECTED(10)][Cause(0)]}
Aug 22 18:16:29.349: LEG[896 ][LEG_OUTCONNECTED(10)][Cause(0)]
Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/OCAnyState_IgnoreEvent: Event Ignored
Aug 22 18:16:29.365: //-1//AFW_:/C_ServiceThirdParty_Event_Handle:
Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/C_ServiceThirdParty_Event_Handle: Received event APP_EV_NOTIFY_DONE[174] in Main Loop
Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/OCAnyState_IgnoreEvent: Event Ignored
Aug 22 18:16:29.365: //-1//AFW_:/C_ServiceThirdParty_Event_Handle:
Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/C_ServiceThirdParty_Event_Handle: Received event APP_EV_NOTIFY_DONE[174] in Main Loop
Aug 22 18:16:29.369: //-1//AFW_:EE461DC520000:/OCHandle_SubscribeCleanup:
Aug 22 18:16:29.369: //-1//AFW_:EE461DC520000:/Third_Party_CC_Cleaner:
Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/OCClosing_AnyEvent:
Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/Third_Party_CC_Cleaner:
Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/OCClosing_AnyEvent:
Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/Third_Party_CC_Cleaner:

Related Commands

Command
Description

debug voip ivr all

Displays all IVR and application framework messages.

supplementary-service h450.2 (dial-peer)

Enables H.450.2 capabilities for call transfers for an individual dial peer.

supplementary-service h450.2 (voice-service)

Globally enables H.450.2 capabilities for call transfers.

supplementary-service h450.3 (dial-peer)

Enables H.450.3 capabilities for call forwarding for an individual dial peer.

supplementary-service h450.3 (voice-service)

Globally enables H.450.3 capabilities for call forwarding.

supplementary-service h450.12 (dial-peer)

Enables H.450.12 capabilities for an individual dial peer.

supplementary-service h450.12 (voice-service)

Globally enables H.450.12 capabilities.


debug voip application stcapp all

To display debugging information for the components of the SCCP Telephony Control Application (STCAPP), use the debug voip application stcapp all command in privileged EXEC mode. To disable debugging display, use the no form of this command.

debug voip application stcapp all

no debug voip application stcapp all

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(14)T

This command was introduced.

12.4(4)T

Command output was enhanced to display codec capabilities for modem transport.


Usage Guidelines

The debug voip application stcapp all command provides debugging output for all the STCAPP debug commands compiled into one display.

Examples

The following is sample output from the debug voip application stcapp all command showing device modem transport capability:

Router# debug voip application stcapp all

*Jan 11 12:24:18.443: stcapp_start
*Jan 11 12:24:18.443: stcapp process started
*Jan 11 12:24:18.443: stcapp_init_symphony
*Jan 11 12:24:18.443: CCAPI successfully initialized
*Jan 11 12:24:18.443: stcapp_init_rtp
*Jan 11 12:24:18.443: stcapp_vp_shut
*Jan 11 12:24:18.443: stcapp_port_up_down
*Jan 11 12:24:18.443: RTP successfully brought in service
*Jan 11 12:24:18.443: stcapp_create_dcbs_from_dialpeers
*Jan 11 12:24:18.447: 1/1/0: stcapp_create_device
*Jan 11 12:24:18.447: 1/1/0: Endpoint base name generated->AN0D65D8DD40280
*Jan 11 12:24:18.447: 1/1/0: New dialpeer id: 999110
*Jan 11 12:24:18.447: 1/1/0: Analog device is ready to be registered

The following lines show the codec subtype, which indicates the modem transport method; 0=None, 1=V.150.1 (modem relay), and 2=VBD (modem pass-through):

*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=5 (g711ulaw) subtype=2
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=1 (g729ar8) subtype=2
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=5 (g711ulaw) subtype=1
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=1 (g729ar8) subtype=1
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=5 (g711ulaw) subtype=0
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=6 (g711alaw) subtype=0
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=1 (g729ar8) subtype=0
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=2 (g726r16) subtype=0
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=3 (g726r24) subtype=0
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=4 (g726r32) subtype=0
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=7 (g728) subtype=0
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=8 (g723r63) subtype=0
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=9 (g723r53) subtype=0
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=12 (g729br8) subtype=0
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=14 (g723ar63) subtype=0
*Jan 11 12:24:18.447: 1/1/0: reg caps including codec=15 (g723ar53) subtype=0
*Jan 11 12:24:18.447: 1/1/0: Device: AN0D65D8DD40280 Id: 7 successfully registered with CM
*Jan 11 12:24:18.455: ==> Received event:STCAPP_DC_EV_DEVICE_REGISTER_DONE
*Jan 11 12:24:18.455: 1/1/0: Device State:OOS
*Jan 11 12:24:18.455: 1/1/0: stcapp_dev_default_eh
*Jan 11 12:24:18.455: 1/1/0: New State = INIT
*Jan 11 12:24:18.455: ==> Received event:STCAPP_DC_EV_DEVICE_CAP_REQ
*Jan 11 12:24:18.455: 1/1/0: Device State:INIT
*Jan 11 12:24:18.455: 1/1/0: stcapp_cap_req_eh
*Jan 11 12:24:18.455: 1/1/0: Sending dcDeviceHeadsetStatus for devID:7
*Jan 11 12:24:18.455: 1/1/0: Sending dcDeviceButtonTemplateReq for devID:7
*Jan 11 12:24:18.455: 1/1/0: No state change
*Jan 11 12:24:18.647: ==> Received event:STCAPP_DC_EV_DEVICE_BUTTON_TEMP_RES
*Jan 11 12:24:18.647: 1/1/0: Device State:INIT
*Jan 11 12:24:18.647: 1/1/0: stcapp_button_templ_res_eh
*Jan 11 12:24:18.647: 1/1/0: Sending dcDeviceLineStatReq for devID:7
*Jan 11 12:24:18.647: 1/1/0: No state change
*Jan 11 12:24:18.647: ==> Received event:STCAPP_DC_EV_DEVICE_FORWARD_STAT_RES
*Jan 11 12:24:18.647: 1/1/0: Device State:INIT
*Jan 11 12:24:18.647: 1/1/0: stcapp_forward_stat_res_eh
*Jan 11 12:24:18.647: 1/1/0: lineNumber: 1
*Jan 11 12:24:18.647: 1/1/0: forwardAllActive: 0
*Jan 11 12:24:18.647: 1/1/0: forwardBusyActive: 0
*Jan 11 12:24:18.647: 1/1/0: forwardNoAnswerActive: 0
*Jan 11 12:24:18.651: 1/1/0: ForwardAllDirNumber:
*Jan 11 12:24:18.651: 1/1/0: No state change
*Jan 11 12:24:18.651: ==> Received event:STCAPP_DC_EV_DEVICE_LINE_STAT_RES
*Jan 11 12:24:18.651: 1/1/0: Device State:INIT
*Jan 11 12:24:18.455: 1/1/0: stcapp_cap_req_eh
*Jan 11 12:24:18.455: 1/1/0: Sending dcDeviceHeadsetStatus for devID:7
*Jan 11 12:24:18.455: 1/1/0: Sending dcDeviceButtonTemplateReq for devID:7
*Jan 11 12:24:18.455: 1/1/0: No state change
*Jan 11 12:24:18.647: ==> Received event:STCAPP_DC_EV_DEVICE_BUTTON_TEMP_RES
*Jan 11 12:24:18.647: 1/1/0: Device State:INIT
*Jan 11 12:24:18.647: 1/1/0: stcapp_button_templ_res_eh
*Jan 11 12:24:18.647: 1/1/0: Sending dcDeviceLineStatReq for devID:7
*Jan 11 12:24:18.647: 1/1/0: No state change
*Jan 11 12:24:18.647: ==> Received event:STCAPP_DC_EV_DEVICE_FORWARD_STAT_RES
*Jan 11 12:24:18.647: 1/1/0: Device State:INIT
*Jan 11 12:24:18.647: 1/1/0: stcapp_forward_stat_res_eh
*Jan 11 12:24:18.647: 1/1/0: lineNumber: 1
*Jan 11 12:24:18.647: 1/1/0: forwardAllActive: 0
*Jan 11 12:24:18.647: 1/1/0: forwardBusyActive: 0
*Jan 11 12:24:18.647: 1/1/0: forwardNoAnswerActive: 0
*Jan 11 12:24:18.651: 1/1/0: ForwardAllDirNumber:
*Jan 11 12:24:18.651: 1/1/0: No state change
*Jan 11 12:24:18.651: ==> Received event:STCAPP_DC_EV_DEVICE_LINE_STAT_RES
*Jan 11 12:24:18.651: 1/1/0: Device State:INIT
*Jan 11 12:24:18.651: 1/1/0: stcapp_line_stat_eh
*Jan 11 12:24:18.651: 1/1/0: lineNumber: 1
*Jan 11 12:24:18.651: 1/1/0: lineDirNumber: 5902
*Jan 11 12:24:18.651: 1/1/0: display name: 5902
*Jan 11 12:24:18.651: 1/1/0: Sending dcDeviceRegAvailableLines for devID:7
*Jan 11 12:24:18.651: 1/1/0: Sending dcDeviceDateTimeReq for devID:7
*Jan 11 12:24:18.651: 1/1/0: No state change
*Jan 11 12:24:18.823: ==> Received event:STCAPP_DC_EV_DEVICE_DEFINE_DATE_TIME_RES
*Jan 11 12:24:18.827: 1/1/0: Device State:INIT
*Jan 11 12:24:18.827: 1/1/0: stcapp_define_date_time_eh
*Jan 11 12:24:18.827: 1/1/0: New State = IS
*Jan 11 12:24:18.827: ==> Received event:STCAPP_DC_EV_DEVICE_DISPLAY_PROMPT_STATUS
*Jan 11 12:24:18.827: 1/1/0: Device State:IS
*Jan 11 12:24:18.827: 1/1/0: stcapp_display_prompt_status_eh
*Jan 11 12:24:18.827: 1/1/0: lineNumber: 0
*Jan 11 12:24:18.827: 1/1/0: call reference: 0
*Jan 11 12:24:18.827: 1/1/0: promptStatus: Your current options
*Jan 11 12:24:18.827: 1/1/0: device control type: 3
*Jan 11 12:24:18.827: 1/1/0: No state change
The following is sample output from the debug voip application stcapp all command during call setup.

The following lines show the voice gateway beginning call setup:

*Jan 9 06:48:06.947: ==> Received event:STCAPP_CC_EV_CALL_SETUP_IND (evId:CC_EV_CALL_SETUP_IND) for CallId: 5
*Jan 9 06:48:06.947: 1/0/0: Call State:IDLE
*Jan 9 06:48:06.947: 1/0/0: stcapp_setup_ind_eh
*Jan 9 06:48:06.947: 1/0/0: Acquired CCB 0x66F12558 for device id:4
*Jan 9 06:48:06.947: 1/0/0: Voice Setup: callID:5, vdb_ptr:66CA57B4

The voice gateway notifies the Cisco CallManager of the endpoint device (phone) in the offhook condition:

*Jan 9 06:48:06.947: 1/0/0: Sending StationOffHook to CallManager
*Jan 9 06:48:06.947: 1/0/0: Sending ccCallSetupAck to Symphony for voice call id:5
*Jan 9 06:48:06.947: 1/0/0: New State = OFFHOOK
*Jan 9 06:48:06.955: 1/0/0: No line (line=0) found... most likely old Call Ref: event STCAPP_DC_EV_DEVICE_SET_RINGER

The following lines show that the Cisco CallManager acknowledged the offhook condition:

*Jan 9 06:48:06.955: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_OFFHOOK (evID:DC_EV_DEVICE_CALL_STATE_OFFHOOK)
*Jan 9 06:48:06.955: 1/0/0: Call State:OFFHOOK
*Jan 9 06:48:06.955: 1/0/0: stcapp_cs_offhook_eh
*Jan 9 06:48:06.955: 1/0/0: No state change

The voice gateway receives the Cisco CallManager notification to send dial tone to the phone:

*Jan 9 06:48:06.955: ==> Received event:STCAPP_DC_EV_DEVICE_START_TONE (evID:DC_EV_DEVICE_START_TONE)
*Jan 9 06:48:06.955: 1/0/0: Call State:OFFHOOK
*Jan 9 06:48:06.955: 1/0/0: stcapp_start_tone_eh

The voice gateway generates dial tone and prepares to collect dialed digits:

*Jan 9 06:48:06.955: 1/0/0: Sending ccGenerateTone(8(0x8))
*Jan 9 06:48:06.955: 1/0/0: Sending ccCallReportDigits
*Jan 9 06:48:06.955: 1/0/0: No state change

Related Commands

Command
Description

debug voip application stcapp error

Displays STCAPP error log contents.

debug voip application stcapp events

Traces STCAPP call flow events.

debug voip application stcapp functions

Displays STCAPP entry and exit function calls for all voice ports.

debug voip application stcapp port

Displays debugging information for the components of the STCAPP for a specified port.


debug voip application stcapp buffer-history

To enable event logging for SCCP Telephony Control Application (STCAPP) analog voice ports, use the debug voip application stcapp buffer-history command in privileged EXEC mode. To disable event logging, use the no form of this command.

debug voip application stcapp buffer-history {all | port port}

no debug voip application stcapp buffer-history {all | port port}

Syntax Description

all

Enables logging for all analog voice ports.

port port

Enables logging for only the specified analog voice port.

Note Port syntax is platform-dependent; type ? to determine.


Command Modes

Privileged EXEC

Command History

Release
Modification

12.4(2)T

This command was introduced.


Usage Guidelines

This command enables logging of call flow events and device events, including registering and unregistering. You can use the event log to help troubleshoot performance problems and isolate faults related to analog endpoints. To display the records in the event log, use the show sctapp buffer-history command.

A maximum of 2000 records are saved for each analog port. The event log uses a circular buffer that stores the 2000 most recent records. To clear the buffer, you can disable logging with the no debug voip application stcapp buffer-history command. The event log uses approximately 64 KB of memory for each port, or approximately 1.5 MB of memory if logging is enabled for all 24 ports.


Note The debug voip application stcapp all command has no impact on event logging. Enabling or disabling STCAPP debug output is separate from the event logging feature.


Examples

The following example enables event logging for analog port 2/3. To display the events, you must use the show sctapp buffer-history command.

Router# debug voip application stcapp buffer-history port 2/3

stcapp buffer-history logging for port 2/3 is on

Related Commands

Command
Description

debug voip application stcapp all

Displays debug output for all the debug commands for the STCAPP compiled into one display.

debug voip application stcapp error

Displays STCAPP error log contents.

debug voip application stcapp events

Traces STCAPP call flow events.

debug voip application stcapp functions

Displays STCAPP entry and exit function calls for all voice ports.

debug voip application stcapp port

Displays STCAPP debug output for a specific port.

show stcapp buffer-history

Displays event logs for STCAPP analog voice ports.


debug voip application stcapp error

To troubleshoot the SCCP Telephony Control Application (STCAPP) error log contents, use the debug voip application stcapp error command in privileged EXEC mode. To disable STCAPP error debugging, use the no form of this command.

debug voip application stcapp error

no debug voip application stcapp error

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(14)T

This command was introduced.


Usage Guidelines

The debug voip application stcapp error command traces application error logs. STCAPP error logs are generated during normal call processing, when there are insufficient resources, or when there are problems in the underlying application code. This command shows error events or unexpected behavior in system software. Usually no events are generated.

Examples

The following example shows the error log contents when STCAPP debugging is enabled:

Router# debug voip application stcapp error

STCAPP error debugging is on
Router#
*Jan 9 06:54:07.583: stcapp_process_queue_events:ERROR:STCAPP_DCB_ACCESS_ERR from state machine

Related Commands

Command
Description

debug voip application stcapp all

Displays debug output for all the debug commands for the STCAPP compiled into one display.

debug voip application stcapp events

Traces STCAPP call flow events.

debug voip application stcapp functions

Displays STCAPP entry and exit function calls for all voice ports.

debug voip application stcapp port

Displays debug information for the components of the STCAPP for a specified port.


debug voip application stcapp events

To trace SCCP Telephony Control Application (STCAPP) call flow events, use the debug voip application stcapp events command in privileged EXEC mode. To disable STCAPP event call traces, use the no form of this command.

debug voip application stcapp events

no debug voip application stcapp events

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(14)T

This command was introduced.


Usage Guidelines

Use this command to debug call flow events for all ports controlled by the STCAPP.

Examples

The following example displays call teardown and disconnect events:

Router# debug voip application stcapp events

The following lines show the application running on the voice gateway receiving notice to stop dial tone generation, following the onhook condition of the endpoint device (phone):

*Jan 9 06:48:55.011: ==> Received event:STCAPP_DC_EV_DEVICE_STOP_TONE (evID:DC_EV_DEVICE_STOP_TONE)
*Jan 9 06:48:55.011: 1/0/1: Call State:REM_ONHOOK_PEND
*Jan 9 06:48:55.011: 1/0/1: stcapp_stop_tone_eh
*Jan 9 06:48:55.011: 1/0/1: Sending ccGenerateTone(NULL)
*Jan 9 06:48:55.015: 1/0/1: No state change

The application takes no additional action to process the uninteresting event.

*Jan 9 06:48:55.015: ==> Received event:STCAPP_DC_EV_DEVICE_START_TONE (evID:DC_EV_DEVICE_START_TONE)
*Jan 9 06:48:55.015: 1/0/1: Call State:REM_ONHOOK_PEND
*Jan 9 06:48:55.015: 1/0/1: Uninteresting event

The application receives the call disconnect notice and proceeds to tear down the telephony call leg.

*Jan 9 06:48:58.903: ==> Received event:STCAPP_CC_EV_CALL_DISCONNECTED (evId:CC_EV_CALL_DISCONNECTED) for CallId: 6
*Jan 9 06:48:58.903: 1/0/1: Call State:REM_ONHOOK_PEND
*Jan 9 06:48:58.903: 1/0/1: stcapp_loc_onhook_eh
*Jan 9 06:48:58.903: 1/0/1: Sending StationOnHook to CallManager
*Jan 9 06:48:58.903: 1/0/1: stcapp_call_cleanup
*Jan 9 06:48:58.903: 1/0/1: stcapp_set_ring_mode
*Jan 9 06:48:58.903: 1/0/1: SCCP ring mode:1
*Jan 9 06:48:58.903: 1/0/1: Invoking Feature:33. Mode:0 for callid:6
*Jan 9 06:48:58.903: 1/0/1: stcapp_disconnect_call_leg
*Jan 9 06:48:58.903: 1/0/1: Sending ccCallDisconnect for call id:6
*Jan 9 06:48:58.903: 1/0/1: CCB 0x65CF3EC4 unlinked
*Jan 9 06:48:58.903: 1/0/1: New State = IDLE

Related Commands

Command
Description

debug voip application stcapp all

Displays debug output for all the debug commands for the STCAPP compiled into one display.

debug voip application stcapp error

Displays STCAPP error log contents.

debug voip application stcapp functions

Displays STCAPP entry and exit function calls for all voice ports.

debug voip application stcapp port

Displays debug information for the components of the STCAPP for a specified port.


debug voip application stcapp functions

To debug SCCP Telephony Control Application (STCAPP) functions, use the debug voip application stcapp functions command in privileged EXEC mode. To disable STCAPP function debugging, use the no form of this command.

debug voip application stcapp functions

no debug voip application stcapp functions

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(14)T

This command was introduced.


Usage Guidelines

Use this command to display STCAPP entry and exit function calls for all voice ports.

Examples

The following example displays function calls for STCAPP ports 1/0/0 and 1/0/1:

Router# debug voip application stcapp functions

STCAPP function debugging is on
*Jan 9 06:55:27.583: 1/0/0: stcapp_setup_ind_eh
*Jan 9 06:55:27.591: 1/0/0: stcapp_cs_offhook_eh
*Jan 9 06:55:27.591: 1/0/0: stcapp_start_tone_eh
*Jan 9 06:55:27.591: 1/0/0: stcapp_report_digits_done_eh
*Jan 9 06:55:28.923: 1/0/0: stcapp_digit_end_eh
*Jan 9 06:55:28.927: 1/0/0: stcapp_stop_tone_eh
*Jan 9 06:55:29.063: 1/0/0: stcapp_digit_end_eh
*Jan 9 06:55:29.203: 1/0/0: stcapp_digit_end_eh
*Jan 9 06:55:29.343: 1/0/0: stcapp_digit_end_eh
*Jan 9 06:55:29.355: 1/0/0: stcapp_cs_proceed_eh
*Jan 9 06:55:29.359: 1/0/0: stcapp_proceed_call_info_eh
*Jan 9 06:55:29.359: 1/0/0: stcapp_start_tone_eh
*Jan 9 06:55:29.359: 1/0/0: stcapp_proceed_call_info_eh
*Jan 9 06:55:29.359: 1/0/1: stcapp_cs_ringin_eh
*Jan 9 06:55:29.359: 1/0/1: stcapp_call_info_eh

Related Commands

Command
Description

debug voip application stcapp all

Displays debug output for all the debug commands for the STCAPP compiled into one display.

debug voip application stcapp error

Displays STCAPP error log contents.

debug voip application stcapp events

Traces STCAPP call flow events.

debug voip application stcapp port

Displays debug information for the components of the STCAPP for a specified port.


debug voip application stcapp port

To enable SCCP Telephony Control Application (STCAPP) debugging for a specific port, use the debug voip application stcapp port command in privileged EXEC mode. To disable specific STCAPP port debugging, use the no form of this command.

debug voip application stcapp port port-number

no debug voip application stcapp port port-number

Syntax Description

port-number

Number of the port on the interface. See the appropriate platform manual or online help for port numbers on your networking device.


Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(14)T

This command was introduced.

12.4(4)T

Command output was enhanced to display the modem transport method.


Usage Guidelines

Use this command to display debugging information for the components of the STCAPP for a specific port.

Examples

The following example displays information on a modem-relay call:

Router# debug voip application stcapp port 1/1/0
*Jan 11 12:37:48.631: ==> Received event:STCAPP_CC_EV_CALL_SETUP_IND (evId:CC_EV_CALL_SETUP_IND) for CallId: 326
*Jan 11 12:37:48.631: 1/1/0: Call State:IDLE
*Jan 11 12:37:48.631: 1/1/0: stcapp_setup_ind_eh
*Jan 11 12:37:48.631: 1/1/0: stcapp_get_ccb
*Jan 11 12:37:48.631: 1/1/0: dcb->lcb[line_inst - 1].num_ccbs=0
*Jan 11 12:37:48.631: 1/1/0: Acquired CCB 0x65D932B8 for device id:7
*Jan 11 12:37:48.631: 1/1/0: num_ccbs++, num_ccbs=1
*Jan 11 12:37:48.631: 1/1/0: Voice Setup: callID:326, vdb_ptr:666581AC
*Jan 11 12:37:48.631: 1/1/0: Sending StationOffHook to CallManager
*Jan 11 12:37:48.631: 1/1/0: Sending ccCallSetupAck to Symphony for voice call id:326
*Jan 11 12:37:48.631: 1/1/0: New State = OFFHOOK
*Jan 11 12:37:48.643: 1/1/0: No line (line=0) found... most likely old Call Ref: event STCAPP_DC_EV_DEVICE_SET_RINGER
*Jan 11 12:37:48.643: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_OFFHOOK (evID:DC_EV_DEVICE_CALL_STATE_OFFHOOK)
*Jan 11 12:37:48.643: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:48.643: 1/1/0: stcapp_cs_offhook_eh
*Jan 11 12:37:48.643: 1/1/0: call_ref=16777250
*Jan 11 12:37:48.643: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:48.643: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:48.643: 1/1/0: Using call_ref 0 to get ccb=0x65D932B8
*Jan 11 12:37:48.643: 1/1/0: No state change
*Jan 11 12:37:48.643: ==> Received event:STCAPP_DC_EV_DEVICE_DISPLAY_PROMPT_STATUS
*Jan 11 12:37:48.643: 1/1/0: Device State:IS
*Jan 11 12:37:48.643: 1/1/0: stcapp_display_prompt_status_eh
*Jan 11 12:37:48.643: 1/1/0: lineNumber: 1
*Jan 11 12:37:48.643: 1/1/0: call reference: 16777250
*Jan 11 12:37:48.643: 1/1/0: promptStatus: Enter Number
*Jan 11 12:37:48.643: 1/1/0: No state change
*Jan 11 12:37:48.643: ==> Received event:STCAPP_DC_EV_DEVICE_START_TONE (evID:DC_EV_DEVICE_START_TONE)
*Jan 11 12:37:48.643: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:48.643: 1/1/0: stcapp_start_tone_eh
*Jan 11 12:37:48.643: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:48.643: 1/1/0: call_ref=16777250, ccb=0x65D932B8, tone=8(0x8)
*Jan 11 12:37:48.643: 1/1/0: Sending ccGenerateTone(8(0x8))
*Jan 11 12:37:48.643: 1/1/0: Sending ccCallReportDigits
*Jan 11 12:37:48.643: 1/1/0: No state change
*Jan 11 12:37:48.643: ==> Received event:STCAPP_CC_EV_CALL_REPORT_DIGITS_DONE (evId:CC_EV_CALL_REPORT_DIGITS_DONE) for CallId: 326
*Jan 11 12:37:48.647: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:48.647: 1/1/0: stcapp_report_digits_done_eh
*Jan 11 12:37:48.647: 1/1/0: No state change
*Jan 11 12:37:52.643: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_BEGIN (evId:CC_EV_CALL_DIGIT_BEGIN) for CallId: 326
*Jan 11 12:37:52.643: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:52.643: 1/1/0: Uninteresting event
*Jan 11 12:37:52.683: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_END (evId:CC_EV_CALL_DIGIT_END) for CallId: 326
*Jan 11 12:37:52.683: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:52.683: 1/1/0: stcapp_digit_end_eh
*Jan 11 12:37:52.683: 1/1/0: Digit received is (5)
*Jan 11 12:37:52.683: 1/1/0: Sending StationKeypadButton(5) to CallManager
*Jan 11 12:37:52.683: 1/1/0: No state change
*Jan 11 12:37:52.687: ==> Received event:STCAPP_DC_EV_DEVICE_STOP_TONE (evID:DC_EV_DEVICE_STOP_TONE)
*Jan 11 12:37:52.687: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:52.687: 1/1/0: stcapp_stop_tone_eh
*Jan 11 12:37:52.687: 1/1/0: call_ref=16777250
*Jan 11 12:37:52.687: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:52.687: 1/1/0: Sending ccGenerateTone(NULL)
*Jan 11 12:37:52.687: 1/1/0: No state change
*Jan 11 12:37:52.775: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_BEGIN (evId:CC_EV_CALL_DIGIT_BEGIN) for CallId: 326
*Jan 11 12:37:52.775: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:52.775: 1/1/0: Uninteresting event
*Jan 11 12:37:52.823: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_END (evId:CC_EV_CALL_DIGIT_END) for CallId: 326
*Jan 11 12:37:52.823: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:52.823: 1/1/0: stcapp_digit_end_eh
*Jan 11 12:37:52.823: 1/1/0: Digit received is (8)
*Jan 11 12:37:52.823: 1/1/0: Sending StationKeypadButton(8) to CallManager
*Jan 11 12:37:52.823: 1/1/0: No state change
*Jan 11 12:37:52.923: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_BEGIN (evId:CC_EV_CALL_DIGIT_BEGIN) for CallId: 326
*Jan 11 12:37:52.923: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:52.923: 1/1/0: Uninteresting event
*Jan 11 12:37:52.963: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_END (evId:CC_EV_CALL_DIGIT_END) for CallId: 326
*Jan 11 12:37:52.963: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:52.963: 1/1/0: stcapp_digit_end_eh
*Jan 11 12:37:52.963: 1/1/0: Digit received is (0)
*Jan 11 12:37:52.963: 1/1/0: Sending StationKeypadButton(0) to CallManager
*Jan 11 12:37:52.963: 1/1/0: No state change
*Jan 11 12:37:53.063: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_BEGIN (evId:CC_EV_CALL_DIGIT_BEGIN) for CallId: 326
*Jan 11 12:37:53.063: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:53.063: 1/1/0: Uninteresting event
*Jan 11 12:37:53.103: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_END (evId:CC_EV_CALL_DIGIT_END) for CallId: 326
*Jan 11 12:37:53.103: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:53.103: 1/1/0: stcapp_digit_end_eh
*Jan 11 12:37:53.103: 1/1/0: Digit received is (2)
*Jan 11 12:37:53.103: 1/1/0: Sending StationKeypadButton(2) to CallManager
*Jan 11 12:37:53.103: 1/1/0: No state change
*Jan 11 12:37:53.235: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_PROCEED (evID:DC_EV_DEVICE_CALL_STATE_PROCEED)
*Jan 11 12:37:53.235: 1/1/0: Call State:OFFHOOK
*Jan 11 12:37:53.235: 1/1/0: stcapp_cs_proceed_eh
*Jan 11 12:37:53.235: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:53.235: 1/1/0: Sending ccCallProceeding for voice call id:326
*Jan 11 12:37:53.235: 1/1/0: Stopping the initial and inter digit timer!
*Jan 11 12:37:53.235: 1/1/0: New State = PROCEEDING
*Jan 11 12:37:53.235: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_INFO (evID:DC_EV_DEVICE_CALL_INFO)
*Jan 11 12:37:53.235: 1/1/0: Call State:PROCEEDING
*Jan 11 12:37:53.235: 1/1/0: stcapp_proceed_call_info_eh
*Jan 11 12:37:53.235: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:53.239: 1/1/0: No state change
*Jan 11 12:37:53.239: ==> Received event:STCAPP_DC_EV_DEVICE_START_TONE (evID:DC_EV_DEVICE_START_TONE)
*Jan 11 12:37:53.239: 1/1/0: Call State:PROCEEDING
*Jan 11 12:37:53.239: 1/1/0: stcapp_start_tone_eh
*Jan 11 12:37:53.239: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:53.239: 1/1/0: call_ref=16777250, ccb=0x65D932B8, tone=1(0x1)
*Jan 11 12:37:53.239: 1/1/0: Sending ccCallAlert(signal:1) for voice call id:326
*Jan 11 12:37:53.239: 1/1/0: No state change
*Jan 11 12:37:53.239: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_RINGOUT (evID:DC_EV_DEVICE_CALL_STATE_RINGOUT)
*Jan 11 12:37:53.239: 1/1/0: Call State:PROCEEDING
*Jan 11 12:37:53.239: 1/1/0: stcapp_set_call_state_eh
*Jan 11 12:37:53.239: 1/1/0: call_ref=16777250, call_state=2
*Jan 11 12:37:53.239: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:53.239: 1/1/0: No state change
*Jan 11 12:37:53.239: ==> Received event:STCAPP_DC_EV_DEVICE_DISPLAY_PROMPT_STATUS
*Jan 11 12:37:53.239: 1/1/0: Device State:IS
*Jan 11 12:37:53.239: 1/1/0: stcapp_display_prompt_status_eh
*Jan 11 12:37:53.239: 1/1/0: lineNumber: 1
*Jan 11 12:37:53.239: 1/1/0: call reference: 16777250
*Jan 11 12:37:53.239: 1/1/0: promptStatus: Ring Out
*Jan 11 12:37:53.239: 1/1/0: No state change
*Jan 11 12:37:53.239: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_INFO (evID:DC_EV_DEVICE_CALL_INFO)
*Jan 11 12:37:53.239: 1/1/0: Call State:PROCEEDING
*Jan 11 12:37:53.239: 1/1/0: stcapp_proceed_call_info_eh
*Jan 11 12:37:53.239: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:53.239: 1/1/0: No state change
*Jan 11 12:37:56.635: ==> Received event:STCAPP_DC_EV_DEVICE_STOP_TONE (evID:DC_EV_DEVICE_STOP_TONE)
*Jan 11 12:37:56.635: 1/1/0: Call State:PROCEEDING
*Jan 11 12:37:56.635: 1/1/0: stcapp_stop_tone_eh
*Jan 11 12:37:56.635: 1/1/0: call_ref=16777250
*Jan 11 12:37:56.635: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:56.639: 1/1/0: Sending ccGenerateTone(NULL)
*Jan 11 12:37:56.639: 1/1/0: No state change
*Jan 11 12:37:56.639: ==> Received event:STCAPP_DC_EV_MEDIA_OPEN_RCV_CHNL (evID:DC_EV_MEDIA_OPEN_RCV_CHNL)
*Jan 11 12:37:56.639: 1/1/0: Call State:PROCEEDING
*Jan 11 12:37:56.639: 1/1/0: stcapp_open_rcv_chnl_eh
*Jan 11 12:37:56.639: 1/1/0: call_ref=16777250
*Jan 11 12:37:56.639: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:56.639: 1/1/0: stcapp_set_up_voip_leg
*Jan 11 12:37:56.639: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:56.639: 1/1/0: Codec: 5 ptime :20, codecbytes: 160

The following line indicates the modem transport method that will be used:

*Jan 11 12:37:56.639: 1/1/0: CCM directive -> enabling modem relay

The following lines show modem-relay parameters:


*Jan 11 12:37:56.639: 1/1/0: MR parms: sprt_retries=10, sprt_latency=250, sprt_rx_v14_pb_hold_time=32, sprt_tx_v14_hold_time=12, sprt_tx_v14_hold_count=22, gw_xid=1, dictsize=1024, stringlen=16, compressdir=3, sse_red_interval=16, sse_red_pkt_count=2, sse_t1=2100, sse_retries=5
*Jan 11 12:37:56.639: 1/1/0: Info provided to RTPSPI - sess_mode 2, desired_qos 0, codec 5, pkt_period 20, lr_port 17180
*Jan 11 12:37:56.639: 1/1/0: Sending ccIFCallSetupRequest for voip leg
*Jan 11 12:37:56.639: 1/1/0: ccIFCallSetRequest returned voip call id:327
*Jan 11 12:37:56.639: 1/1/0: Sending dcDeviceOpenReceiveChannelAck
*Jan 11 12:37:56.639: 1/1/0: ORChnlAck Info: codec:5, loc_port:17180, chnl_id:16777521
*Jan 11 12:37:56.639: 1/1/0: New State = CONNECTING
*Jan 11 12:37:56.643: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_CONNECTED (evID:DC_EV_DEVICE_CALL_STATE_CONNECTED)
*Jan 11 12:37:56.643: 1/1/0: Call State:CONNECTING
*Jan 11 12:37:56.643: 1/1/0: stcapp_set_call_state_eh
*Jan 11 12:37:56.643: 1/1/0: call_ref=16777250, call_state=6
*Jan 11 12:37:56.643: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:56.643: 1/1/0: No state change
*Jan 11 12:37:56.643: ==> Received event:STCAPP_DC_EV_DEVICE_DISPLAY_PROMPT_STATUS
*Jan 11 12:37:56.643: 1/1/0: Device State:IS
*Jan 11 12:37:56.643: 1/1/0: stcapp_display_prompt_status_eh
*Jan 11 12:37:56.643: 1/1/0: lineNumber: 1
*Jan 11 12:37:56.643: 1/1/0: call reference: 16777250
*Jan 11 12:37:56.643: 1/1/0: promptStatus: Connected
*Jan 11 12:37:56.643: 1/1/0: No state change
*Jan 11 12:37:56.643: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_INFO (evID:DC_EV_DEVICE_CALL_INFO)
*Jan 11 12:37:56.643: 1/1/0: Call State:CONNECTING
*Jan 11 12:37:56.643: 1/1/0: stcapp_conn_call_info_eh
*Jan 11 12:37:56.647: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:56.647: 1/1/0: stcapp_call_info_eh::caller_name=
*Jan 11 12:37:56.647: 1/1/0: Irrelevant CALL_INFO message is ignore!
*Jan 11 12:37:56.647: 1/1/0: No state change
*Jan 11 12:37:56.647: ==> Received event:STCAPP_DC_EV_DEVICE_STOP_TONE (evID:DC_EV_DEVICE_STOP_TONE)
*Jan 11 12:37:56.647: 1/1/0: Call State:CONNECTING
*Jan 11 12:37:56.647: 1/1/0: stcapp_stop_tone_eh
*Jan 11 12:37:56.647: 1/1/0: call_ref=16777250
*Jan 11 12:37:56.647: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:56.647: 1/1/0: Sending ccGenerateTone(NULL)
*Jan 11 12:37:56.647: 1/1/0: No state change
*Jan 11 12:37:56.647: ==> Received event:STCAPP_DC_EV_MEDIA_OPEN_XMT_CHNL (evID:DC_EV_MEDIA_OPEN_XMT_CHNL)
*Jan 11 12:37:56.647: 1/1/0: Call State:CONNECTING
*Jan 11 12:37:56.647: 1/1/0: stcapp_start_media_eh
*Jan 11 12:37:56.647: 1/1/0: call_ref=16777250
*Jan 11 12:37:56.647: 1/1/0: stcapp_get_ccb_ptr
*Jan 11 12:37:56.647: 1/1/0: New State = ACTIVE_PENDING
*Jan 11 12:37:56.647: ==> Received event:STCAPP_CC_EV_CALL_CONNECTED (evId:CC_EV_CALL_CONNECTED) for CallId: 327
*Jan 11 12:37:56.647: 1/1/0: Call State:ACTIVE_PENDING
*Jan 11 12:37:56.647: 1/1/0: stcapp_call_connected_eh
*Jan 11 12:37:56.647: 1/1/0: stcapp_create_conference
*Jan 11 12:37:56.647: 1/1/0: Sending ccConferenceCreate to Symphony
*Jan 11 12:37:56.651: 1/1/0: Conference created. voice call id:326, voip call id:327
*Jan 11 12:37:56.651: 1/1/0: No state change
*Jan 11 12:37:56.651: ==> Received event:STCAPP_CC_EV_CONF_CREATE_DONE (evId:CC_EV_CONF_CREATE_DONE) for CallId: 326
*Jan 11 12:37:56.651: 1/1/0: Call State:ACTIVE_PENDING
*Jan 11 12:37:56.651: 1/1/0: stcapp_active_pending_eh
*Jan 11 12:37:56.651: 1/1/0: Sending ccCallModify for voice call id:326
*Jan 11 12:37:56.651: 1/1/0: codec=5, vad=0
*Jan 11 12:37:56.651: 1/1/0: Stopping the initial and inter digit timer!
*Jan 11 12:37:56.651: 1/1/0: Sending ccCallModify for voip call id:327
*Jan 11 12:37:56.651: 1/1/0: Updated SMT info to RTPSPI - sess_mode:3,desired_qos:0, codec:5, pkt_period:20,rem_port:18968 vad:0 ip_tos:4
*Jan 11 12:37:56.655: 1/1/0: No state change
*Jan 11 12:37:56.655: ==> Received event:STCAPP_CC_EV_VOICE_MODE_DONE (evId:CC_EV_VOICE_MODE_DONE) for CallId: 326
*Jan 11 12:37:56.655: 1/1/0: Call State:ACTIVE_PENDING
*Jan 11 12:37:56.655: 1/1/0: Uninteresting event
*Jan 11 12:37:56.655: ==> Received event:STCAPP_CC_EV_CALL_REPORT_DIGITS_DONE (evId:CC_EV_CALL_REPORT_DIGITS_DONE) for CallId: 326
*Jan 11 12:37:56.655: 1/1/0: Call State:ACTIVE_PENDING
*Jan 11 12:37:56.655: 1/1/0: Uninteresting event
*Jan 11 12:37:56.655: ==> Received event:STCAPP_CC_EV_CALL_MODIFY_DONE (evId:CC_EV_CALL_MODIFY_DONE) for CallId: 326
*Jan 11 12:37:56.655: 1/1/0: Call State:ACTIVE_PENDING
*Jan 11 12:37:56.655: 1/1/0: stcapp_default_eh
*Jan 11 12:37:56.655: 1/1/0: call_ref=0, call_state=0
*Jan 11 12:37:56.655: 1/1/0: New State = ACTIVE
*Jan 11 12:37:56.655: ==> Received event:STCAPP_CC_EV_CALL_MODIFY_DONE (evId:CC_EV_CALL_MODIFY_DONE) for CallId: 327
*Jan 11 12:37:56.655: 1/1/0: Call State:ACTIVE
*Jan 11 12:37:56.655: 1/1/0: Uninteresting event
*Jan 11 12:37:59.963: ==> Received event:STCAPP_CC_EV_CALL_FEATURE_OFFHOOK (evId:CC_EV_CALL_FEATURE) for CallId: 326
*Jan 11 12:37:59.963: 1/1/0: Call State:ACTIVE
*Jan 11 12:37:59.963: 1/1/0: stcapp_call_feature_eh
*Jan 11 12:37:59.963: 1/1/0: lcb->num_ccbs = 1
*Jan 11 12:37:59.963: 1/1/0: No CC_FEATURE match!
*Jan 11 12:37:59.967: 1/1/0: No state change... call remaining

The following example displays information on STCAPP controlled foreign exchange station (FXS) port 1/0/1 during call setup:

Router# debug voip application stcapp port 1/0/1

stcapp port debugging is on

The following lines show the voice gateway receiving notification from the Cisco CallManager of an incoming call:

*Jan 9 06:57:24.403: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_RINGIN (evID:DC_EV_DEVICE_CALL_STATE_RINGIN)
*Jan 9 06:57:24.403: 1/0/1: Call State:IDLE
*Jan 9 06:57:24.403: 1/0/1: stcapp_cs_ringin_eh
*Jan 9 06:57:24.407: 1/0/1: Acquired CCB 0x66C0A428 for device id:3

The next lines show the new call processing state for the port:

*Jan 9 06:57:24.407: 1/0/1: New State = RINGIN
*Jan 9 06:57:24.407: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_INFO (evID:DC_EV_DEVICE_CALL_INFO)
*Jan 9 06:57:24.407: 1/0/1: Call State:RINGIN
*Jan 9 06:57:24.407: 1/0/1: stcapp_call_info_eh

The next lines show the application sending a call setup request for the telephony leg:

*Jan 9 06:57:24.407: 1/0/1: stcapp_set_up_voice_leg
*Jan 9 06:57:24.407: 1/0/1: Sending ccIFCallSetupRequest for voice leg
*Jan 9 06:57:24.407: 1/0/1: ccIFCallSetRequest returned voice call id:22. CdPN:7702CgPN:7701
*Jan 9 06:57:24.407: 1/0/1: No state change

The next lines show the application invoking the ringing state:

*Jan 9 06:57:24.407: ==> Received event:STCAPP_DC_EV_DEVICE_SET_RINGER (evID:DC_EV_DEVICE_SET_RINGER)
*Jan 9 06:57:24.407: 1/0/1: Call State:RINGIN
*Jan 9 06:57:24.407: 1/0/1: stcapp_set_ringer_eh
*Jan 9 06:57:24.407: 1/0/1: stcapp_set_ring_mode
*Jan 9 06:57:24.407: 1/0/1: SCCP ring mode:2
*Jan 9 06:57:24.407: 1/0/1: Invoking Feature:12. Mode:0 for callid:22
*Jan 9 06:57:24.407: 1/0/1: No state change

Related Commands

Command
Description

debug voip application stcapp all

Displays debug output for all the debug commands for the STCAPP compiled into one display.

debug voip application stcapp error

Displays STCAPP error log contents.

debug voip application stcapp events

Traces STCAPP call flow events.

debug voip application stcapp functions

Displays STCAPP entry and exit function calls for all voice ports.


debug voip application vxml

To troubleshoot a VoiceXML application, use the debug voip application vxml command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip application vxml [all | application | background | default | error [call [informational] | software [informational]] | event | function | grammar | gtd | inout | log | puts | ssml | trace | warning]

no debug voip application vxml

Syntax Description

all

(Optional) Displays all VoiceXML debugging messages.

application

(Optional) Displays VoiceXML application states information.

background

(Optional) Displays VoiceXML background messages.

default

(Optional) Displays output for all of the following keywords:

application

background

error

event

gtd

inout

puts

trace

warning

This option is also available if no keywords are added.

error

(Optional) Displays VoiceXML errors.

call

(Optional) Displays call processing errors.

informational

(Optional) Displays minor errors and major errors. Without the informational keyword, only major errors are displayed.

software

(Optional) Displays software errors.

event

(Optional) Displays VoiceXML asynchronous events.

function

(Optional) Displays VoiceXML functions.

grammar

(Optional) Enables syntax checking of XML grammar by the VoiceXML interpreter and displays syntax debugging messages.

gtd

(Optional) Displays VoiceXML generic transparency descriptors.

inout

(Optional) Displays VoiceXML in/out functions.

log

(Optional) Displays the results of the VoiceXML <log> tag.

puts

(Optional) Displays the results of VoiceXML <cisco-puts> and <cisco-putvar> tags.

Note In Cisco IOS Release 12.4(6th)T and later releases, the puts keyword is obsolete. Use the log keyword instead.

ssml

(Optional) Enables syntax checking of Speech Synthesis Markup Language (SSML) by the VoiceXML interpreter and displays syntax debugging messages.

trace

(Optional) Displays a trace of all activities for the current VoiceXML document.

warning

(Optional) Displays VoiceXML warning messages.


Command Default

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(8)T

This command replaces the debug vxml command.

12.4(15)T

The puts keyword was obsoleted. The log keyword was added to replace it.


Usage Guidelines

If this debug encounters a fetch failure when using an HTTP interface, an error.badfetch.http.response code message is displayed. The values for the response code are shown in Table 332.

Table 332 error.badfetch.http Response Codes

Response Code
Description

0

No response from HTTP server

400

Bad request

401

Unauthorized

402

Payment required

403

Forbidden

404

Not found

405

Method not allowed

406

Not acceptable

407

Proxy authentication required

408

Request timeout

409

Conflict

410

Gone

411

Length required

412

Precondition failed

413

Request entity too large

414

Request-URI too large

415

Unsupported media type

416

Requested range not satisfiable

417

Expectation failed

500

Internal server error

501

Not implemented

502

Bad gateway

503

Service unavailable

504

Gateway timeout

505

Version not supported


Examples

The following is sample output from the debug voip application vxml all command if there is an HTTP badfetch error call:

Router# debug voip application vxml all

Aug 7 04:53:03.003: //-1/000000000000/VAPP:/vapp_evt_handler:
State VAPP_ACTIVE got event CC_EV_CALL_SETUP_IND
Aug 7 04:53:03.003: //-1/000000000000/VAPP:/vapp_driver:
pInterp[6383BA48]:
Aug 7 04:53:03.003: //-1/000000000000/VAPP:/vapp_driver:
evtID: 29 vapp record state: 0
Aug 7 04:53:03.003: //-1/000000000000/VAPP:/vapp_evt_setup:

Aug 7 04:53:03.003: //-1//VAPP:/vapp_incoming_callblock:
Aug 7 04:53:03.003: vapp_incoming_callblock:

Before the incoming call block data comes in, the CallEntry ID is -1, which indicates that the call leg had not been identified. In the next excerpt, the call leg is shown as 1 and the GUID is also assigned.

Aug 7 04:53:03.003: //1/71E56a9AF8002/VAPP:/vapp_evt_setup:
VXML call. GTD should be saved
Aug 7 04:53:03.003: //1/71E569AF8002/VAPP:/vapp_load_or_run_script:
Aug 7 04:53:03.003: //1/71E569AF8002/VAPP:/vapp_load_or_run_script:

The next excerpt show script-specific information.

Aug 7 04:53:03.007: The VXML Script with len=1519 starts:
-------------------------------------
<?xml version="3.0" encoding="iso-8859-1"?>
<vxml version="3.0">

<form id = "transfer_me">
<catch event="telephone.disconnect.transfer">
</catch>

<var name="phone_num" expr="5550100"/>
<v

The CallEntry ID becomes 0 in the following excerpt, which indicates that the output is from the application server, not a call leg.

Aug 7 04:53:03.007: //0//VXML:/vxml_start_element_handler: Enter
Aug 7 04:53:03.007: //0//VXML:/vxml_start_element_handler: Exit
Aug 7 04:53:03.007: //0//VXML:/vxml_character_data: Enter
Aug 7 04:53:03.007: //0//VXML:/vxml_character_data:
at line 888: length <=0, exit
.
.
.
Aug 7 04:53:03.051: //0//VXML:/vxml_end_element_handler: Enter
Aug 7 04:53:03.051: //0//VXML:/vxml_end_element_handler: Exit
Aug 7 04:53:03.051: //0//VXML:/vxml_parse:
Aug 7 04:53:03.051: vxml_parse: XML_Parse success err=0
Aug 7 04:53:03.051: //0//VXML:/vxml_session_delete:
Aug 7 04:53:03.051: vxml_session_delete:mem_mgr_mempool_free: mempool=NULL
Aug 7 04:53:03.051: //-1//VXML:/vxml_create:
enter url=tftp://dirt/jkuo/vxml/xfer.nosound.vxml tree_handle=63282BDC
return_handle_add=63C84F80

In the following excerpt, the call with the GUID 71E569AF8002 is again being tracked as the application session is initiated.

Aug 7 04:53:03.083: //1/71E569AF8002/VXML:/vxml_offramp_mailhdrs_get:
Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_create_gtd_sess_vars:
Created object chain for com.cisco.signal.gtdlist
Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_jse_add_gtd_obj_to_list:
Sig-event name = setup_indication, gtd-len = 140, gtd-buf =
IAM,
PRN,isdn*,,,
USI,rate,c,s,c,1
USI,lay1,ulaw
TMR,00
CPN,34,,4,52950
CPC,09
FCI,,,,,,,y,
GCI,71e569af6b5511d4800200014232e6a8


Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_jse_add_gtd_obj_to_list:
gtd_obj for sig-event [setup_indication] added to session/shadow
var array [0x63826914]
Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_create: Exit
Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_start:
vxmlhandle=6372E9BC vapphandle=6383BA48 status=0 async_status=0
Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_vxml_proc:
<vxml> URI(abs):tftp://dirt/jkuo/vxml/xfer.nosound.vxml
scheme=tftp
host=dirt
path=/jkuo/vxml/xfer.nosound.vxml
base= URI(abs):tftp://dirt/jkuo/vxml/xfer.nosound.vxml
scheme=tftp
host=dirt
path=/jkuo/vxml/xfer.nosound.vxml lang=none version=3.0
Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_form_proc:
Aug 7 04:53:03.087: <form>: id=transfer_me scope=dialog

In the following excerpt, the phone number of the caller is shown:

Aug 7 04:53:03.087: vxml_form_init current scope: dialog
<var>: namep=phone_num expr=5550100
Aug 7 04:53:03.091: //1/71E569AF8002/VXML:/vxml_expr_eval:
expr=var phone_num=5550100
<var>: namep=mydur
Aug 7 04:53:03.095: //1/71E569AF8002/VXML:/vxml_expr_eval:
expr=var mydur
vxml_counter_reset:
Aug 7 04:53:03.095: //1/71E569AF8002/VXML:/vxml_formitem_select:
Status=VXML_STATUS_OK,
Aug 7 04:53:03.095: //1/71E569AF8002/VXML:/vxml_formitem_select:
AsyncStatus=VXML_STATUS_OK
Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_transfer_proc:
<transfer>:

In the following excerpts, the attributes of the incoming phone call are shown:

Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_item_attrs_proc:
name=mycall dest_expr='phone://'+ phone_num bridge=1 connecttimeout=50 maxtime=50 desttype=-1 destplan=-1 anitype=-1 aniplan=-1 anipi=-1, anisi=-1 rdn_exprp='phone://' + 4085550111 rdntype=2 rdnplan=1 rdnpi=0, rdnsi=3, redirectreason=0

The next several excerpts show the initialization and playing of audio prompts. When troubleshooting voice applications, ensure that all your assigned prompts play when required.

Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_play_prompts: Enter
Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_prompt_proc: Enter
Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_prompt_proc:
<prompt>:(default_prompt) bargein=1 count=1 typeaheadflush=0
Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_audio_proc: Enter
Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_audio_proc:
<audio>: URI(abs):http://px1-sun/nosound.au
scheme=http
host=px1-sun
path=/nosound.au caching=fast fetchhint=invalid fetchtimeout=0
Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_audio_proc: Exit
Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_vapp_media_play:
bargein=1 timeout=0 typeaheadflush=0 vcr=0 rate=0
Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_vapp_media_play:
str=http://px1-sun/nosound.au cachable=1 timeout0
Aug 7 04:53:03.099: //1/71E569AF8002/VAPP:/vapp_media_play:
Aug 7 04:53:03.099: //1/71E569AF8002/VAPP:/vapp_media_play:
prompt=http://px1-sun/nosound.au:
Aug 7 04:53:03.687: //1/71E569AF8002/VXML:/vxml_vapp_media_play: Exit
Aug 7 04:53:03.687: //1/71E569AF8002/VXML:/vxml_prompt_proc: Exit
Aug 7 04:53:03.687: //1/71E569AF8002/VXML:/vxml_play_prompts: Exit

The next several excerpts indicate that something is wrong with the XML form to which data is being written:

Aug 7 04:53:03.699: //1/71E569AF8002/VXML:/vxml_transfer_proc:
GTD not present in <transfer>
Aug 7 04:53:03.699: //1/71E569AF8002/VXML:/vxml_transfer_proc: Exit
Aug 7 04:53:03.699: //1/71E569AF8002/VXML:/vxml_elem_proc:
at line 8521: Status not OK, exit
Aug 7 04:53:03.703: //1/71E569AF8002/VXML:/vxml_formitem_select:
at line 4651: Status not OK, exit
Aug 7 04:53:03.703: //1/71E569AF8002/VXML:/vxml_form_proc:
at line 4791: Status not OK, exit
Aug 7 04:53:03.703: //1/71E569AF8002/VXML:/vxml_elem_proc:
at line 8521: Status not OK, exit
Aug 7 04:53:03.703: //1/71E569AF8002/VXML:/vxml_vxml_proc:
at line 8703: Status not OK, exit
Aug 7 04:53:03.703: //1/71E569AF8002/VXML:/vxml_load_immediate_done:
sidp->status=180000000
Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_checksessionstate:
Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_checkifdone:
Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_driver: Exit
Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_evt_handler:
State VAPP_ACTIVE got event CC_EV_CALL_MODIFY_DONE
Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_driver:
pInterp[6383BA48]:
Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_driver:
evtID: 37 vapp record state: 0
Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_checksessionstate:
Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_checkifdone:
Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_driver: Exit
Aug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_evt_handler:
State VAPP_ACTIVE got event MSW_EV_SYNTHESIZER
Aug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_driver:
pInterp[6383BA48]:
Aug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_driver:
evtID: 84 vapp record state: 0
Aug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_play_done:
evID=84 reason=8, protocol=2, status_code=404, dur=-1, rate=0
Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_media_done:
status 2 async_status 180000000 duration=-1 rate=0
Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_save_lastprompt_info:
Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_bind_lastprompt:
Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_vapp_vcr_control_disable:
Aug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_notify_play_done:
Aug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_notify_play_done: Exit

After checking the status of the application, the router finds a badfetch error, which indicates that a VoiceXML form was not found. See Table 332 for a description of error.badfetch.http response codes.

Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_media_done:
CALL_ERROR: : fail with vapp error 2, protocol_status_code=404
Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_media_done:
CALL_ERROR: : *** error.badfetch.http.404 event is thrown
Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_event_driver:
Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_event_proc:
<event>: event=error.badfetch.http.404 status=0
Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_default_event_handler:
use default event handler
Aug 7 04:53:03.739: //1/71E569AF8002/VAPP:/vapp_session_exit_event_name:
Exit Event error.badfetch.http.404
Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_load_immediate_done:
sidp->status=10
Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_start:
vxmlhandle=6372E9BC vapphandle=6383BA48 status=0 async_status=10
Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_vapp_terminate:
vapp_status=0 ref_count 0
Aug 7 04:53:03.739: //1/71E569AF8002/VAPP:/vapp_terminate:
Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_destroy: Enter
Aug 7 04:53:03.739: //-1//VXML:/vxml_gtd_delete_callback:
New ref-count = 0

Related Commands

Command
Description

debug condition application voice

Displays debugging messages for only the specified VoiceXML application.

debug http client

Displays debugging messages for the HTTP client.

debug voip ivr

Displays debugging messages for VoIP IVR interactions.


debug voip avlist

To troubleshoot the attribute value list (AVLIST) contents, use the debug voip avlist command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip avlist [all | default | detail | error [call [informational] | software [informational]] | inout]

no debug voip avlist

Syntax Description

all

(Optional) Displays all AVLIST debugging messages.

default

(Optional) Displays AVLIST error and inout information. This option also runs if no keywords are added.

detail

(Optional) Displays AVLIST background messages.

error

(Optional) Displays AVLIST error messages.

call

(Optional) Displays call processing errors.

informational

(Optional) Displays minor errors and major errors. Without the informational keyword, only major errors are displayed.

software

(Optional) Displays software errors.

inout

(Optional) Displays AVLIST in/out functions.


Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(8)T

This command was introduced.


Usage Guidelines

The debug voip avlist command does not support call debug filtering.

Examples

Output is primarily used by TAC.

debug voip ccapi

To troubleshoot the call control application programming interface (CCAPI) contents, use the debug voip ccapi command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ccapi [all | default | detail | error [call [informational] | software [informational]] | individual range | inout | function | protoheaders | service]

no debug voip ccapi

Syntax Description

all

(Optional) Displays all CCAPI debugging messages.

default

(Optional) Displays CCAPI error and inout information. This option also runs if no keywords are added.

detail

(Optional) Displays CCAPI background messages.

error

(Optional) Displays CCAPI error messages. The debug voip ccapi error command traces the error logs in the call control API. Error logs are generated during normal call processing, if there are insufficient resources, or if there are problems in the underlying network-specific code, the higher call session application, or the call control API itself.

This debug command shows error events or unexpected behavior in system software. Usually no events will be generated.

call

(Optional) Displays call processing errors.

informational

(Optional) Displays minor errors and major errors. Without the informational keyword, only major errors are displayed.

software

(Optional) Displays software errors.

individual

(Optional) Enables individual CCAPI debug outputs.

range

For the individual keyword, the range is an integer value from 1 to 146. For specific range values, see Table 333.

inout

(Optional) Displays CCAPI in/out functions. The debug voip ccapi inout command traces the execution path through the call control API, which serves as the interface between the call session application and the underlying network-specific software. You can use the output from this command to understand how calls are being handled by the router.

This command shows how a call flows through the system. Using this debug level, you can see the call setup and teardown operations performed on both the telephony and network call legs.

function

(Optional) Displays CCAPI function tracing.

protoheaders

(Optional) Displays CCAPI protocol headers passing information.

service

(Optional) Logs debug messages that are not call related.


Table 333 CCAPI Individual Debug Values 

Value
CCAPI Debug Function

1

CC_IDMSG_API_DISPLAY_IES

2

CC_IDMSG_SETUP_IND_COMM_2

3

CC_IDMSG_SETUP_IND_COMM_3

4

CC_IDMSG_SETUP_IND_COMM_4

5

CC_IDMSG_ALERT_IND_5

6

CC_IDMSG_ALERT_IND_6

7

CC_IDMSG_CONNECT_IND_7

8

CC_IDMSG_CONNECT_IND_8

9

CC_IDMSG_RECONNECT_IND_9

10

CC_IDMSG_DISCONNECTED_IND_10

11

CC_IDMSG_DISCONNECTED_IND_11

12

CC_IDMSG_DISCONNECTED_IND_12

13

CC_IDMSG_DISCONNECT_DONE_IND_13

14

CC_IDMSG_DISCONNECT_DONE_IND_14

15

CC_IDMSG_DISCONNECT_DONE_IND_15

16

CC_IDMSG_PRE_DISC_CAUSE_16

17

CC_IDMSG_PRE_DISC_CAUSE_17

18

CC_IDMSG_DIGIT_BEGIN_IND_18

19

CC_IDMSG_DIGIT_END_IND_19

20

CC_IDMSG_DIGIT_END_IND_20

21

CC_IDMSG_DIGIT_END_NO_TERM_21

22

CC_IDMSG_TONE_IND_22

23

CC_IDMSG_FEATURE_IND_23

24

CC_IDMSG_MODIFY_DONE_IND_24

25

CC_IDMSG_MODIFY_MODE_DONE_IND_25

26

CC_IDMSG_INBAND_MSG_RCVD_IND_26

27

CC_IDMSG_INBAND_MSG_DONE_IND_27

28

CC_IDMSG_UPD_CALL_INFO_IND_28

29

CC_IDMSG_GEN_NTK_ALERT_EVENT_29

30

CC_IDMSG_VOICE_MODE_EVENT_30

31

CC_IDMSG_VOICE_MODE_EVENT_31

32

CC_IDMSG_DIALING_COMPLETE_IND_32

33

CC_IDMSG_DIGITS_DONE_IND_33

34

CC_IDMSG_DIGITS_DONE_IND_34

35

CC_IDMSG_VBD_XMIT_DONE_IND_35

36

CC_IDMSG_FWD_SETUP_IND_36

37

CC_IDMSG_RSVP_DONE_IND_37

38

CC_IDMSG_AUDIT_RSP_IND_38

39

CC_IDMSG_XFR_STATUS_IND_39

40

CC_IDMSG_XFR_STATUS_IND_40

41

CC_IDMSG_XFR_DONE_IND_41

42

CC_IDMSG_XFR_DONE_IND_42

43

CC_IDMSG_XFR_DONE_IND_43

44

CC_IDMSG_TGT_CID_ACTIVE_RCD_44

45

CC_IDMSG_MODIFY_MEDIA_IND_45

46

CC_IDMSG_MODIFY_MEDIA_ACK_IND_46

47

CC_IDMSG_MODIFY_MEDIA_REJ_IND_47

48

CC_IDMSG_MODEM_CALL_START_IND_48

49

CC_IDMSG_MODEM_CALL_DONE_IND_49

50

CC_IDMSG_ACCT_STATUS_IND_50

51

CC_IDMSG_NW_STATUS_IND_51

52

CC_IDMSG_DESTINFO_IND_52

53

CC_IDMSG_LOOPBACK_DONE_IND_53

54

CC_IDMSG_RT_PACKET_STATS_IND_54

55

CC_IDMSG_CUT_PROGRESS_IND_55

56

CC_IDMSG_CUT_PROGRESS_IND_56

57

CC_IDMSG_PROCEEDING_IND_57

58

CC_IDMSG_FACILITY_IND_58

59

CC_IDMSG_INFO_IND_59

60

CC_IDMSG_PROGRESS_IND_60

61

CC_IDMSG_USERINFO_IND_61

62

CC_IDMSG_DISC_PROG_IND_62

63

CC_IDMSG_DISC_PROG_IND_63

64

CC_IDMSG_PING_DONE_IND_64

65

CC_IDMSG_COT_TEST_DONE_IND_65

66

CC_IDMSG_PROCESS_DONE_IND_66

67

CC_IDMSG_ASSOCIATED_IND_67

68

CC_IDMSG_SUSPEND_IND_68

69

CC_IDMSG_SUSPEND_ACK_IND_69

70

CC_IDMSG_SUSPEND_REJ_IND_70

71

CC_IDMSG_RESUME_IND_71

72

CC_IDMSG_RESUME_ACK_IND_72

73

CC_IDMSG_RESUME_REJ_IND_73

74

CC_IDMSG_IF_SETUP_REQ_PRIV_74

75

CC_IDMSG_IF_SETUP_REQ_PRIV_75

76

CC_IDMSG_IF_ALLOCATE_DSP_76

77

CC_IDMSG_CONNECT_77

78

CC_IDMSG_CONNECT_78

79

CC_IDMSG_PING_79

80

CC_IDMSG_DISCONNECT_80

81

CC_IDMSG_DISCONNECT_81

82

CC_IDMSG_DISCONNECT_82

83

CC_IDMSG_ALERT_83

84

CC_IDMSG_ALERT_84

85

CC_IDMSG_CUT_PROGRESS_85

86

CC_IDMSG_CUT_PROGRESS_86

87

CC_IDMSG_CUT_PROGRESS_87

88

CC_IDMSG_DISC_PROG_88

89

CC_IDMSG_DISC_PROG_89

90

CC_IDMSG_SET_PEER_90

91

CC_IDMSG_SET_PEER_91

92

CC_IDMSG_PROCEEDING_92

93

CC_IDMSG_SETUP_REQ_93

94

CC_IDMSG_SETUP_REQ_94

95

CC_IDMSG_SETUP_REQ_95

96

CC_IDMSG_SETUP_REQ_96

97

CC_IDMSG_SETUP_REQ_97

98

CC_IDMSG_SETUP_REQ_98

99

CC_IDMSG_SETUP_REQ_99

100

CC_IDMSG_SETUP_REQ_100

101

CC_IDMSG_SETUP_REQ_101

102

CC_IDMSG_SETUP_ACK_102

103

CC_IDMSG_FACILITY_103

104

CC_IDMSG_TRANSFER_REQ_104

105

CC_IDMSG_GET_CONSULT_ID_105

106

CC_IDMSG_FORWARD_TO_106

107

CC_IDMSG_INFO_107

108

CC_IDMSG_NOTIFY_108

109

CC_IDMSG_PROGRESS_109

110

CC_IDMSG_PRE_DISC_110

111

CC_IDMSG_PRE_DISC_111

112

CC_IDMSG_USER_INFO_112

113

CC_IDMSG_MODIFY_113

114

CC_IDMSG_DIGIT_114

115

CC_IDMSG_DIGIT_DIAL_115

116

CC_IDMSG_DIGIT_DIAL_STOP_116

117

CC_IDMSG_FEATURE_117

118

CC_IDMSG_FEATURE_ENABLE_118

119

CC_IDMSG_ASSOCIATE_STREAM_119

120

CC_IDMSG_ASSOCIATE_STREAM_120

121

CC_IDMSG_DISASSOCIATE_STREAM_121

122

CC_IDMSG_DISASSOCIATE_STREAM_122

123

CC_IDMSG_GENERATE_TONE_INFO_123

124

CC_IDMSG_SET_DIGIT_TIMEOUTS_124

125

CC_IDMSG_SET_DIGIT_TIMEOUTS_125

126

CC_IDMSG_SUSPEND_126

127

CC_IDMSG_SUSPEND_ACK_127

128

CC_IDMSG_SUSPEND_REJ_128

129

CC_IDMSG_RESUME_129

130

CC_IDMSG_RESUME_ACK_130

131

CC_IDMSG_RESUME_REJ_131

132

CC_IDMSG_UPDATE_REDIRECT_NUM_132

133

CC_IDMSG_BABBLER_AUDIT_133

134

CC_IDMSG_CONFERENCE_CREATE_134

135

CC_IDMSG_CONFERENCE_CREATE_135

136

CC_IDMSG_CONFERENCE_CREATE_136

137

CC_IDMSG_CONFERENCE_DESTROY_137

138

CC_IDMSG_CONFERENCE_DESTROY_138

139

CC_IDMSG_CONFERENCE_DESTROY_139

140

CC_IDMSG_LOOPBACK_140

141

CC_IDMSG_COT_TEST_141

142

CC_IDMSG_HANDOFF_142

143

CC_IDMSG_APP_RETURN_143

144

CC_IDMSG_T38_FAX_START_144

145

CC_IDMSG_T38_FAX_DONE_145

146

CC_IDMSG_CALL_PREEMPT_IND_146


Command Default

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

11.3(6)NA2

This command was introduced.

12.2(11)T

This command was implemented on the following platforms: Cisco 2600 series, Cisco 3620, Cisco 3660, Cisco AS5350, Cisco AS5400, Cisco AS5850, Cisco AS5300, Cisco AS5800, and Cisco MC3810.

12.3(8)T

The all, default, detail, call, informational, software, individual, function, protoheaders, and service keywords were added.

12.4(4)XC

The range for the individual keyword was extended to 146, to include logs for call preemption indication information.

12.4(9)T

This command was integrated into Cisco IOS Release 12.4(9)T.


Examples

The following examples show output for variations of the debug voip ccapi command:

debug voip ccapi detail on the Originating Gateway: Example

debug voip ccapi detail on the Terminating Gateway: Example

debug voip ccapi inout on the Originating Gateway: Example

debug voip ccapi service on the Terminating Gateway: Example

debug voip ccapi individual 146 on the Originating Gateway: Example

For these examples, the topology shown in Figure 1 is used.

Figure 1 Network Topology for debug voip ccapi Output Examples

debug voip ccapi detail on the Originating Gateway: Example

Router# debug voip ccapi detail

voip ccapi detail debugging is on
Router#
*Apr 18 20:35:35.779: //-1/ABCE697D8005/CCAPI/cc_api_call_setup_ind_common:
Interface Type=13, Protocol=0
*Apr 18 20:35:35.779: //-1/ABCE697D8005/CCAPI/ccCheckClipClir:
Calling Party Number Is User Provided
*Apr 18 20:35:35.779: //11/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=TRUE)
*Apr 18 20:35:35.779: //11/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
Total Call Count=1

The following event shows that the CallEntry ID 11 is used for the incoming call leg.

*Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry:
Incoming=TRUE, Call Id=11
*Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_setupind_registration_lookup:
Matching Parameters; Called Number=83103, Call Transfer Consult Id=
*Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_setupind_registration_lookup:
No Matching Node
*Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/ccCheckClipClir:
Calling Party Number Is User Provided
*Apr 18 20:35:35.779: //12/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=FALSE)

The following event shows that the incoming call leg with CallEntry ID 11 is bound to the outgoing call leg with CallEntry ID 12.

*Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_peer_bind:
Bind=TRUE, Binder Call Id=11, Bindee Call Id=12

The next event shows that CallEntry ID 12 is used for the outgoing call leg.

*Apr 18 20:35:35.779: //12/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry:
Incoming=FALSE, Call Id=12
*Apr 18 20:35:35.779: //-1/xxxxxxxxxxxx/CCAPI/cc_api_supported_data:
data_mode=0x10082

The next event shows an IP address for a remote device on the outgoing call leg, which indicates that this is the VoIP call leg.

*Apr 18 20:35:35.779: //12/ABCE697D8005/CCAPI/cc_incr_if_call_volume:
Remote IP Address=172.16.13.81, Hwidb=FastEthernet0/0
*Apr 18 20:35:35.779: //12/ABCE697D8005/CCAPI/cc_incr_if_call_volume:
Total Call Count=1, Voip Call Count=1, MMoip Call Count=0
*Apr 18 20:35:35.795: //11/ABCE697D8005/CCAPI/ccCallGetContext:
Context=0x652C0168, Call Id=11
*Apr 18 20:36:31.419: //11/ABCE697D8005/CCAPI/ccCallDisconnect:
Start Calling Accounting;
Call Entry(Incoming=TRUE)
*Apr 18 20:36:31.419: //11/ABCE697D8005/CCAPI/ccCallDisconnect:
Cause Value=16, Call Entry(Disconnect Cause=16)
*Apr 18 20:36:31.419: //11/ABCE697D8005/CCAPI/ccCallDisconnect:
Call Entry(Disconnect Cause=16)

At this point, the CallEntry ID changes as the call accounting process begins. The accounting data is sent over the outgoing call leg. The GUID, which identifies the unique call, remains the same.

*Apr 18 20:36:31.419: //12/ABCE697D8005/CCAPI/ccCallDisconnect:
Start Calling Accounting;
Call Entry(Incoming=FALSE)
*Apr 18 20:36:31.419: //12/ABCE697D8005/CCAPI/ccCallDisconnect:
Cause Value=16, Call Entry(Disconnect Cause=0)

The change of the CallEntry ID indicates that the call is using the incoming call leg, which is the POTS call leg in this case.

*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/ccCallGetVoipFlag:
Data Bitmask=0x1, Call Id=11
*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/ccCallGetVoipFlag:
Flag=FALSE
*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry:
Incoming=TRUE
*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry:
ccFreeRawMsgInfo=0x63FF8198
*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry:
Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=TRUE)
*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry:
Total Call Count=0
*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry:
Deleting profileTable[0x64F44700]

The next line shows the impairment calculation. This is the only CCAPI debug command that shows impairment.

*Apr 18 20:36:31.423: //-1/ABCE697D8005/CCAPI/g113_calculate_impairment:
(delay=91(ms), loss=0%), Io=0 Iq=0 Idte=0 Idd=2 Ie=10 Itot=12
*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/ccCallGetVoipFlag:
Data Bitmask=0x1, Call Id=12
*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/ccCallGetVoipFlag:
Flag=FALSE
*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_decr_if_call_volume:
Remote IP Address=172.16.13.81, Hwidb=FastEthernet0/0
*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_decr_if_call_volume:
Total Call Count=0, Voip Call Count=0, MMoip Call Count=0
*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry:
Incoming=FALSE
*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_delete_call_entry:
Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=FALSE)
*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_delete_call_entry:
Deleting profileTable[0x652E3310]
*Apr 18 20:36:31.427: //12/xxxxxxxxxxxx/CCAPI/cc_get_call_entry:
Call Entry Is Not Found

debug voip ccapi detail on the Terminating Gateway: Example

Router# debug voip ccapi detail

voip ccapi detail debugging is on
Router#
*May 1 18:58:26.251: //-1/xxxxxxxxxxxx/CCAPI/cc_api_supported_data:
data_mode=0x10082
*May 1 18:58:26.255: //8/xxxxxxxxxxxx/CCAPI/cc_get_call_entry:
Call Entry Is Not Found
*May 1 18:58:26.255: //-1/ABCE697D8005/CCAPI/cc_api_call_setup_ind_common:
Interface Type=0, Protocol=1
*May 1 18:58:26.255: //-1/ABCE697D8005/CCAPI/ccCheckClipClir:
Calling Party Number Is User Provided

The following line shows the attributes of the calling number:

*May 1 18:58:26.255: //-1/ABCE697D8005/CCAPI/cc_api_call_setup_ind_common:
After Number Translation Checking:
Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),
Called Number=3600(TON=Unknown, NPI=Unknown)
*May 1 18:58:26.255: //8/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=TRUE)
*May 1 18:58:26.255: //8/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
Total Call Count=1
*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry:
Incoming=TRUE, Call Id=8

The following line shows the IP address of the originating gateway:

*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_incr_if_call_volume:
Remote IP Address=172.16.13.175, Hwidb=FastEthernet0/0
*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_incr_if_call_volume:
Total Call Count=1, Voip Call Count=1, MMoip Call Count=0
*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_setupind_registration_lookup:
Matching Parameters; Called Number=3600, Call Transfer Consult Id=
*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_setupind_registration_lookup:
No Matching Node
*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/ccCheckClipClir:
Calling Party Number Is User Provided
*May 1 18:58:26.259: //9/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=FALSE)
*May 1 18:58:26.259: //8/ABCE697D8005/CCAPI/cc_peer_bind:
Bind=TRUE, Binder Call Id=8, Bindee Call Id=9
*May 1 18:58:26.259: //9/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry:
Incoming=FALSE, Call Id=9
*May 1 18:58:26.259: //9/ABCE697D8005/CCAPI/cc_set_voice_port_value:
CC_IF_TELEPHONY: Echo=0, Playout=0
*May 1 18:58:26.263: //9/ABCE697D8005/CCAPI/ccCallGetContext:
Context=0x64B6BB5C, Call Id=9
*May 1 18:59:21.871: //8/ABCE697D8005/CCAPI/ccCallDisconnect:
Start Calling Accounting;
Call Entry(Incoming=TRUE)
*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallDisconnect:
Cause Value=16, Call Entry(Disconnect Cause=16)
*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallDisconnect:
Call Entry(Disconnect Cause=16)
*May 1 18:59:21.875: //9/ABCE697D8005/CCAPI/ccCallDisconnect:
Start Calling Accounting;
Call Entry(Incoming=FALSE)
*May 1 18:59:21.875: //9/ABCE697D8005/CCAPI/ccCallDisconnect:
Cause Value=16, Call Entry(Disconnect Cause=0)

The next line shows the impairment calculation. This is the only CCAPI debug command that shows impairment.

*May 1 18:59:21.875: //-1/ABCE697D8005/CCAPI/g113_calculate_impairment:
(delay=99(ms), loss=0%), Io=0 Iq=0 Idte=0 Idd=2 Ie=10 Itot=12
*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallGetVoipFlag:
Data Bitmask=0x1, Call Id=8
*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallGetVoipFlag:
Flag=FALSE
*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_decr_if_call_volume:
Remote IP Address=172.16.13.175, Hwidb=FastEthernet0/0
*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_decr_if_call_volume:
Total Call Count=0, Voip Call Count=0, MMoip Call Count=0
*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry:
Incoming=TRUE
*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_call_entry:
ccFreeRawMsgInfo=0x644EB850
Router#
*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_call_entry:
Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=TRUE)
*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_call_entry:
Total Call Count=0
*May 1 18:59:21.879: //8/ABCE697D8005/CCAPI/cc_delete_call_entry:
Deleting profileTable[0x64B78600]
*May 1 18:59:21.879: //8/xxxxxxxxxxxx/CCAPI/cc_get_call_entry:
Call Entry Is Not Found
*May 1 18:59:21.879: //8/xxxxxxxxxxxx/CCAPI/cc_get_call_entry:
Call Entry Is Not Found
Router#
*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/ccCallGetVoipFlag:
Data Bitmask=0x1, Call Id=9
*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/ccCallGetVoipFlag:
Flag=FALSE
*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_api_call_disconnect_done:
Prefix Is Not Defined From Peer; Peer=3600, Called Number=3600
*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry:
Incoming=FALSE
*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_delete_call_entry:
Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=FALSE)
*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_delete_call_entry:
Deleting profileTable[0x6453F228]

debug voip ccapi inout on the Originating Gateway: Example

Router# debug voip ccapi inout

voip ccapi inout debugging is on
Router#
*Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/cc_api_display_ie_subfields:
cc_api_call_setup_ind_common:
acme-username=
----- ccCallInfo IE subfields -----
   acme-ani=4085550111
   acme-anitype=2
   acme-aniplan=1
   acme-anipi=0
   acme-anisi=1
dest=83103
   acme-desttype=0
   acme-destplan=0
   acme-rdn=
   acme-rdntype=-1
   acme-rdnplan=-1
   acme-rdnpi=-1
   acme-rdnsi=-1
   acme-redirectreason=-1

The following lines show information about the calling and called numbers. The network presentation indicator (NPI) shows the type of transmission. The Incoming Dial-Peer field shows that the incoming dial peer has been matched.

*Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/cc_api_call_setup_ind_common:
Interface=0x64F26F10, Call Info(
Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),
Called Number=83103(TON=Unknown, NPI=Unknown),
Calling Translated=FALSE, Subsriber Type Str=RegularLine, FinalDestinationFlag=TRUE,
Incoming Dial-peer=1, Progress Indication=NULL(0), Calling IE Present=TRUE,
Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=-1
*Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/ccCheckClipClir:
In: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed)
*Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/ccCheckClipClir:
Out: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed)

In the following event, the call leg is established. The CallEntry ID field changes from -1 to 19.

*Apr 18 20:42:19.347: //19/9C5A9CA88009/CCAPI/cc_api_call_setup_ind_common:
Set Up Event Sent;
Call Info(Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),
Called Number=83103(TON=Unknown, NPI=Unknown))
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/cc_process_call_setup_ind:
Event=0x63FF4730
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetContext:
Context=0x652A9858
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/cc_process_call_setup_ind:
>>>>CCAPI handed cid 19 with tag 1 to app "Default"
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallProceeding:
Progress Indication=NULL(0)
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetupRequest:
Destination=, Calling IE Present=TRUE, Mode=0,
Outgoing Dial-peer=3600, Params=0x652AA4A8, Progress Indication=NULL(0)
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCheckClipClir:
In: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed)
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCheckClipClir:
Out: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed)
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetupRequest:
Destination Pattern=360., Called Number=3600, Digit Strip=FALSE
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetupRequest:
Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),
Called Number=3600(TON=Unknown, NPI=Unknown),
Redirect Number=, Display Info=
Account Number=, Final Destination Flag=TRUE,
Guid=9C5A9CA8-5243-11D6-8009-00059A3A15A0, Outgoing Dial-peer=3600
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/cc_api_display_ie_subfields:
ccCallSetupRequest:
cisco-username=
----- ccCallInfo IE subfields -----
cisco-ani=4085550111
cisco-anitype=2
cisco-aniplan=1
cisco-anipi=0
cisco-anisi=1
dest=3600
cisco-desttype=0
cisco-destplan=0
cisco-rdn=
cisco-rdntype=-1
cisco-rdnplan=-1
cisco-rdnpi=-1
cisco-rdnsi=-1
cisco-redirectreason=-1

In the following lines, the outgoing dial peer is matched:

*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccIFCallSetupRequestPrivate:
Interface=0x63EAF24C, Interface Type=1, Destination=, Mode=0x0,
Call Params(Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),
Called Number=3600(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
Subsriber Type Str=RegularLine, FinalDestinationFlag=TRUE, Outgoing Dial-peer=3600, Call Count On=FALSE,
Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
*Apr 18 20:42:19.351: //20/9C5A9CA88009/CCAPI/ccIFCallSetupRequestPrivate:
SPI Call Setup Request Is Success; Interface Type=1, FlowMode=1
*Apr 18 20:42:19.351: //20/9C5A9CA88009/CCAPI/ccCallSetContext:
Context=0x652AA458
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccSaveDialpeerTag:
Outgoing Dial-peer=3600
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccSaveDialpeerTag:
Outgoing Dial-peer=3600
*Apr 18 20:42:19.367: //20/9C5A9CA88009/CCAPI/cc_api_call_proceeding:
Interface=0x652F6388, Progress Indication=NULL(0)

The following lines show call progress. The progress and signal indications are shown.

*Apr 18 20:42:19.371: //20/9C5A9CA88009/CCAPI/cc_api_call_cut_progress:
Interface=0x652F6388, Progress Indication=INBAND(8), Signal Indication=SIGNAL RINGBACK(1),
Cause Value=0
*Apr 18 20:42:19.371: //20/9C5A9CA88009/CCAPI/cc_api_call_cut_progress:
Call Entry(Responsed=TRUE)
*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccCallCutProgress:
Progress Indication=INBAND(8), Signal Indication=SIGNAL RINGBACK(1), Cause Value=0
Voice Call Send Alert=FALSE, Call Entry(AlertSent=FALSE)
*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccCallCutProgress:
Call Entry(Responsed=TRUE)

The following lines show the tone generation information:

*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccGenerateToneInfo:
Stop Tone On Digit=FALSE, Tone=Null,
Tone Direction=Network, Params=0x0, Call Id=19
*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccConferenceCreate:
Conference Id=0x652F723C, Call Id1=19, Call Id2=20, Tag=0x0
*Apr 18 20:42:19.371: //20/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
Conference Id=0x6, Source Interface=0x63EAF24C, Source Call Id=20,
Destination Call Id=19, Disposition=0x0, Tag=0x0
*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccConferenceCreate:
Call Entry(Conference Id=0x6, Destination Call Id=20)
*Apr 18 20:42:19.371: //20/9C5A9CA88009/CCAPI/ccConferenceCreate:
Call Entry(Conference Id=0x6, Destination Call Id=19)
*Apr 18 20:42:19.371: //19/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19,
Destination Call Id=20, Disposition=0x0, Tag=0x0
*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_generic_bridge_done:
Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19,
Destination Call Id=20, Disposition=0x0, Tag=0x0
*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_api_caps_ind:
Destination Interface=0x63EAF24C, Destination Call Id=20, Source Call Id=19,
Caps(Codec=0x2887F, Fax Rate=0xBF, Vad=0x3,
Modem=0x2, Codec Bytes=0, Signal Type=3)
*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_api_caps_ind:
Caps(Playout Mode=1, Playout Initial=60(ms), Playout Min=40(ms),
Playout Max=300(ms), Fax Nom=300(ms))
*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_process_notify_bridge_done:
Conference Id=0x6, Call Id1=19, Call Id2=20
*Apr 18 20:42:19.375: //20/9C5A9CA88009/CCAPI/cc_api_caps_ind:
Destination Interface=0x64F26F10, Destination Call Id=19, Source Call Id=20,
Caps(Codec=0x4, Fax Rate=0x1, Vad=0x2,
Modem=0x2, Codec Bytes=20, Signal Type=2)
*Apr 18 20:42:19.375: //20/9C5A9CA88009/CCAPI/cc_api_caps_ind:
Caps(Playout Mode=1, Playout Initial=60(ms), Playout Min=40(ms),
Playout Max=300(ms), Fax Nom=300(ms))

The following lines show codec information:

*Apr 18 20:42:19.375: //20/9C5A9CA88009/CCAPI/cc_api_caps_ack:
Destination Interface=0x64F26F10, Destination Call Id=19, Source Call Id=20,
Caps(Codec=g729r8(0x4), Fax Rate=FAX_RATE_NONE(0x1), Vad=ON(0x2),
Modem=ON(0x2), Codec Bytes=20, Signal Type=2, Seq Num Start=6872)
*Apr 18 20:42:19.375: //19/9C5A9CA88009/CCAPI/cc_api_caps_ack:
Destination Interface=0x63EAF24C, Destination Call Id=20, Source Call Id=19,
Caps(Codec=g729r8(0x4), Fax Rate=FAX_RATE_NONE(0x1), Vad=ON(0x2),
Modem=ON(0x2), Codec Bytes=20, Signal Type=2, Seq Num Start=6872)
*Apr 18 20:42:19.375: //19/9C5A9CA88009/CCAPI/cc_api_voice_mode_event:
Call Id=19
*Apr 18 20:42:19.375: //19/9C5A9CA88009/CCAPI/cc_api_voice_mode_event:
Call Entry(Context=0x652A9858)

The following lines show progress indication information. In this case, the event shows that the destination is not ISDN.

*Apr 18 20:42:26.855: //20/9C5A9CA88009/CCAPI/cc_api_call_connected:
Interface=0x652F6388, Data Bitmask=0x0, Progress Indication=DESTINATION IS NON ISDN(2),
Connection Handle=0
*Apr 18 20:42:26.855: //20/9C5A9CA88009/CCAPI/cc_api_call_connected:
Call Entry(Connected=TRUE, Responsed=TRUE, Retry Count=0)
*Apr 18 20:42:26.855: //19/9C5A9CA88009/CCAPI/ccCallConnect:
Progress Indication=DESTINATION IS NON ISDN(2), Data Bitmask=0x0
*Apr 18 20:42:26.855: //19/9C5A9CA88009/CCAPI/ccCallConnect:
Call Entry(Connected=TRUE, Responsed=TRUE)
*Apr 18 20:42:26.855: //20/9C5A9CA88009/CCAPI/ccSaveDialpeerTag:
Incoming Dial-peer=1
*Apr 18 20:42:26.859: //19/9C5A9CA88009/CCAPI/ccSaveDialpeerTag:
Outgoing Dial-peer=3600
*Apr 18 20:42:26.859: //20/9C5A9CA88009/CCAPI/ccCallFeature:
Feature Type=24, Call Id=20

This event shows that the call is disconnected.

*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnected:
Cause Value=16, Interface=0x64F26F10, Call Id=19
*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnected:
Call Entry(Responsed=TRUE, Cause Value=16, Retry Count=0)
*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/ccConferenceDestroy:
Conference Id=0x6, Tag=0x0
*Apr 18 20:43:16.795: //20/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done:
Conference Id=0x6, Source Interface=0x63EAF24C, Source Call Id=20,
Destination Call Id=19, Disposition=0x0, Tag=0x0
*Apr 18 20:43:16.795: //19/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done:
Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19,
Destination Call Id=20, Disposition=0x0, Tag=0x0
*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_generic_bridge_done:
Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19,
Destination Call Id=20, Disposition=0x0, Tag=0x0
*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/ccCallDisconnect:
Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=16)
*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/ccCallDisconnect:
Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16)
*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_api_get_transfer_info:
Transfer Number Is Null
*Apr 18 20:43:16.795: //20/9C5A9CA88009/CCAPI/ccCallDisconnect:
Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)
*Apr 18 20:43:16.795: //20/9C5A9CA88009/CCAPI/ccCallDisconnect:
Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16)
*Apr 18 20:43:16.795: //20/9C5A9CA88009/CCAPI/cc_api_get_transfer_info:
Transfer Number Is Null
*Apr 18 20:43:16.803: //20/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done:
Disposition=0, Interface=0x652F6388, Tag=0x0, Call Id=20,
Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry Count=0)
*Apr 18 20:43:16.803: //20/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done:
Call Disconnect Event Sent
*Apr 18 20:43:16.803: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done:
Disposition=0, Interface=0x64F26F10, Tag=0x0, Call Id=19,
Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry Count=0)
*Apr 18 20:43:16.803: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done:
Call Disconnect Event Sent

debug voip ccapi service on the Terminating Gateway: Example

Router# debug voip ccapi service

voip ccapi service debugging is on
*May 1 19:08:41.803: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
Searching Node;
Called Number=3600, Call Transfer Consult Id=

This debug shows noncall related events. In this case, information about the timer is shown.

*May 1 19:08:48.027: //-1/xxxxxxxxxxxx/CCAPI/cc_handle_periodic_timer:
Calling The Callback, ccTimerctx=0x63B368C0
*May 1 19:08:48.027: //-1/xxxxxxxxxxxx/CCAPI/ccTimerStart:
ccTimerctx=0x63B368C0
*May 1 19:10:08.615: //-1/xxxxxxxxxxxx/CCAPI/cc_api_icpif:
ExpectFactor=0xA

debug voip ccapi individual 146 on the Originating Gateway: Example

This debug shows the preemption tone timer getting initiated.

*Aug 24 18:28:16.919: //18958/B37648B6AF48/CCAPI/cc_api_call_preempt_ind:
PreemptionToneTimer=10(s)

debug voip ccapi error

To trace error logs in the call control application programming interface (CCAPI), use the debug voip ccapi error command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ccapi error

no debug voip ccapi error

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(11)T

This command was implemented on the following platforms: Cisco 2600 series, Cisco 3620, Cisco 3660, Cisco AS5350, Cisco AS5400, Cisco AS5850, Cisco AS5300, Cisco AS5800, and Cisco MC3810.


Usage Guidelines

The debug voip ccapi error command traces the error logs in the call control API. Error logs are generated during normal call processing, when there are insufficient resources, or when there are problems in the underlying network-specific code, the higher call session application, or the call control API itself.

This debug command shows error events or unexpected behavior in system software. In most cases, no events will be generated.


Note We recommend that you log output from the debug voip ccapi error command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.


Related Commands

Command
Description

debug voip ccapi inout

Traces the execution path through the CCAPI.

voice call debug

Allows configuration of the voice call debug output.


debug voip ccapi inout

To trace the execution path through the call control application programming interface (CCAPI), use the debug voip ccapi inout command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ccapi inout

no debug voip ccapi inout

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(11)T

This command was implemented on the following platforms: Cisco 2600 series, Cisco 3620, Cisco 3660, Cisco AS5350, Cisco AS5400, Cisco AS5850, Cisco AS5300, Cisco AS5800, and Cisco MC3810.


Usage Guidelines

The debug voip ccapi inout command traces the execution path through the call control API, which serves as the interface between the call session application and the underlying network-specific software. You can use the output from this command to understand how calls are being handled by the voice gateway.

This command shows how a call flows through the system. Using this debug level, you can see the call setup and teardown operations performed on both the telephony and network call legs.


Note We recommend that you log output from the debug voip ccapi inout command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.


Examples

The following example shows the call setup indicated and accepted by the voice gateway:

Router# debug voip ccapi inout

*Mar 1 15:35:53.588: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructTDUsrContainer:
usrContainer[0x638C1BF0], magic[FACE0FFF]
*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilAddDataToUsrContainer:
container=0x638C1BF0, tagID=6, dataSize=16, instID=-1,modifier=1
*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject:
tdObject[0x638BC1AC], nxtElem[0x0], magic[0xFACE0FFF] tagID[6], dataLen[16],
modif[1]
*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToContainer:
Adding tdObject[0x638BC1AC] instID[-1] into container[0x638C1BF0]
*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilAddDataToUsrContainer:
container=0x638C1BF0, tagID=5, dataSize=276, instID=-1,modifier=1
*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject:
tdObject[0x63401148], nxtElem[0x0], magic[0xFACE0FFF] tagID[5], dataLen[276],
modif[1]
*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToContainer:
Adding tdObject[0x63401148] instID[-1] into container[0x638C1BF0]

In the following lines, the call control API (CCAPI) receives the call setup. The called number is 34999, and the calling number is 55555. The calling number matches dial peer 10002.

*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/cc_api_display_ie_subfields:
*Mar 1 15:35:53.592: cc_api_call_setup_ind:
*Mar 1 15:35:53.592: cisco-username=
*Mar 1 15:35:53.596: ----- ccCallInfo IE subfields -----
*Mar 1 15:35:53.596: cisco-ani=55555
*Mar 1 15:35:53.596: cisco-anitype=0
*Mar 1 15:35:53.596: cisco-aniplan=0
*Mar 1 15:35:53.596: cisco-anipi=0
*Mar 1 15:35:53.596: cisco-anisi=0
*Mar 1 15:35:53.596: dest=34999
*Mar 1 15:35:53.596: cisco-desttype=0
*Mar 1 15:35:53.596: cisco-destplan=0
*Mar 1 15:35:53.596: cisco-rdn=
*Mar 1 15:35:53.596: cisco-rdntype=-1
*Mar 1 15:35:53.596: cisco-rdnplan=-1
*Mar 1 15:35:53.596: cisco-rdnpi=-1
*Mar 1 15:35:53.596: cisco-rdnsi=-1
*Mar 1 15:35:53.596: cisco-redirectreason=-1
*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:
(vdbPtr=0x637EC1E0, callInfo={called=34999,called_oct3=0x80,calling=55555,calling_oct3=0x80,calling_oct3a=0x0, calling_xlated=false,subscriber_type_str=RegularLine,fdest=1,
peer_tag=10002, prog_ind=0,callingIE_present 1, src_route_label=, tgt_route_label= clid_transparent=0},callID=0x637B4278)

*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:
*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: type 13 , prot 0
*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 1 15:35:53.596: ccCheckClipClir: calling number is: "55555", calling oct3a is: 0x0
*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 1 15:35:53.596: Calling Party number is User Provided
*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 1 15:35:53.596: Leaving ccCheckClipClir
calling number is: "55555"
calling oct3 is: 0x80
calling oct3a is: 0x0

In the next line, 44 is the CallEntry ID.

*Mar 1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: Increment call volume: 0

*Mar 1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: current call volume: 1
*Mar 1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: entry's incoming TRUE.
*Mar 1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: is_incoming is TRUE
*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructHashProfileTab: profileTable[0x6380E11C], numBuckets[11], numEntries[0]
*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtProfileTableBuildManager: Invoking necessary profileTable updaters...
*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContainer: Updating profileTable[0x6380E11C] with objects in container[0x638C1BF0]
*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContainer: obtained key[5] for the tag[6]
*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToProfileBucket: profileTable[0x6380E11C], tdObject[0x638BC1AC]
*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContainer: obtained key[0] for the tag[5]
*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToProfileBucket: profileTable[0x6380E11C], tdObject[0x63401148]
*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtProfileTableBuildManager:
*Mar 1 15:35:53.600: ccTDUtilDumpAllElemInProfileTab: profileTable[0x6380E11C],
numBuckets[11], numEntries[2]
*Mar 1 15:35:53.600: Bucket { 0 } ------>0x63401148[0x0,t-5,l-276,d-0x63401168,
m-1,u-56153,g-FACE0FFF]
*Mar 1 15:35:53.604:
*Mar 1 15:35:53.604: Bucket { 5 } ------>0x638BC1AC[0x0,t-6,l-16,d-0x638BC1CC,m-1,u-56153,g-FACE0FFF]
*Mar 1 15:35:53.604:
*Mar 1 15:35:53.604: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructTDUsrContainer: Container[0x638C1BF0]
*Mar 1 15:35:53.604: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: not the VoIP or MMoIP
*Mar 1 15:35:53.608: //-1/xxxxxxxxxxxx/CCAPI/cc_process_call_setup_ind: (event=
0x63073AA0)

In the next line, 45F2AAE28044 is the GUID. The tag 10002 entry shows that the incoming dial peer matched the CallEntry ID.

*Mar 1 15:35:53.608: //44/45F2AAE28044/CCAPI/cc_process_call_setup_ind: >>>>CCAPI handed cid 44 with tag 10002 to app "DEFAULT"
*Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(24=CC_EV_CALL_SETUP_IND), cid(44), disp(0)
*Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(SSA_EV_CALL_SETUP_IND), cid(44), disp(0)
*Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/ssaCallSetupInd:

The next line shows CallEntry ID in hexadecimal form, 0x2C (44 in decimal). The CallID and GUID numbers have been identified. The incoming dial-peer is 10002.

*Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/CCAPI/ccCallSetContext: (callID=0x2C, context=0x634A430C)

*Mar 1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: cid(44), st(SSA_CS_MAPPING),oldst(0), ev(24)ev->e.evCallSetupInd.nCallInfo.finalDestFlag
= 1
*Mar 1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: src route label=, tgt route label= tg_label_flag 0x0
*Mar 1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: finalDest cllng(55555), clled(34999) tgt_route_label()tg_label_flag 0x0
*Mar 1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: cid(44),
st(SSA_CS_CALL_SETTING),oldst(0), ev(24)dpMatchPeersMoreArg result= 0

For CallEntry ID 44, two dial-peer tags (10001 and 20002) were matched with called number 34999.

*Mar 1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaDebugPeers: ssaSetupPe
er cid(44) peer list: tag(10001) called number (34999) tag(20002) called number
(34999)
*Mar 1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaSetupPeer: dialpeer tags in rotary= 10001 20002

The next line shows that 5 digits were matched for this dial peer and no prefix was added. The encapType (2) entry indicates a VoIP call.

*Mar 1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaSetupPeer: cid(44), de
stPat(34999), matched(5), prefix(), peer(637B0984), peer->encapType (2)
*Mar 1 15:35:53.612: //-1/xxxxxxxxxxxx/CCAPI/cc_can_gateway: Call legs: In=6, O
ut=1

The next line shows the voice gateway sending out a call-proceeding message to the incoming call leg with progress indicator of 0x0.

*Mar 1 15:35:53.612: //44/xxxxxxxxxxxx/CCAPI/ccCallProceeding: (callID=0x2C, pr
og_ind=0x0)

The next line shows the voice gateway sending out the call-setup request to the outgoing call leg. The dial-peer is 10001 with the incoming CallEntry ID being 0x2C.

*Mar 1 15:35:53.612: //44/xxxxxxxxxxxx/CCAPI/ccCallSetupRequest: (Inbound call
= 0x2C, outbound peer =10001, dest=,
params=0x63085D80 mode=0, *callID=0x63086314, prog_ind = 0callingIE_pres
ent 1)

*Mar 1 15:35:53.612: //44/45F2AAE28044/CCAPI/ccCallSetupRequest:
*Mar 1 15:35:53.612: ccCallSetupRequest numbering_type 0x80
*Mar 1 15:35:53.612: //44/45F2AAE28044/CCAPI/ccCallSetupRequest:
*Mar 1 15:35:53.616: ccCallSetupRequest: calling number is:55555

*Mar 1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: calling oct3a
is:0x0

*Mar 1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 1 15:35:53.616: ccCheckClipClir: calling number is: "55555", calling oct3a
is: 0x0
*Mar 1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 1 15:35:53.616: Calling Party number is User Provided
*Mar 1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 1 15:35:53.616: Leaving ccCheckClipClir
calling number is: "55555"
calling oct3 is: 0x80
calling oct3a is: 0x0
*Mar 1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: after ccCheckC
lipClir - calling oct3a is:0x0

The next line shows that all digits are passed.

*Mar 1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: dest pattern 3
4999, called 34999, digit_strip 0
*Mar 1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest:
*Mar 1 15:35:53.616: callingNumber=55555, calledNumber=34999, redirectNumber= d
isplay_info= calling_oct3a=0
*Mar 1 15:35:53.616: accountNumber=, finalDestFlag=1,
guid=45f2.aae2.1571.11cc.8044.95f5.fabb.6b0f
*Mar 1 15:35:53.616: peer_tag=10001
*Mar 1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/cc_api_display_ie_subfields:
*Mar 1 15:35:53.616: ccCallSetupRequest:
*Mar 1 15:35:53.616: cisco-username=
*Mar 1 15:35:53.616: ----- ccCallInfo IE subfields -----
*Mar 1 15:35:53.616: cisco-ani=55555
*Mar 1 15:35:53.616: cisco-anitype=0
*Mar 1 15:35:53.616: cisco-aniplan=0
*Mar 1 15:35:53.616: cisco-anipi=0
*Mar 1 15:35:53.616: cisco-anisi=0
*Mar 1 15:35:53.620: dest=34999
*Mar 1 15:35:53.620: cisco-desttype=0
*Mar 1 15:35:53.620: cisco-destplan=0
*Mar 1 15:35:53.620: cisco-rdn=
*Mar 1 15:35:53.620: cisco-rdntype=-1
*Mar 1 15:35:53.620: cisco-rdnplan=-1
*Mar 1 15:35:53.620: cisco-rdnpi=-1
*Mar 1 15:35:53.620: cisco-rdnsi=-1
*Mar 1 15:35:53.620: cisco-redirectreason=-1

*Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: (vdbP
tr=0x62EC61A4, dest=, callParams={called=34999,called_oct3=0x80, calling=55555,calling_oct3=0x80, calling_oct3a= 0x0, calling_xlated=false, subscriber_type_str
=RegularLine, fdest=1, voice_peer_tag=10001},mode=0x0)
*Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
*Mar 1 15:35:53.620: ccIFCallSetupRequestPrivate: src route label tgt route label tg_label_flag 0x0
*Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: vdbPtr type = 1
*Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
*Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: (vdbPtr=0x62EC61A4, dest=, callParams={called=34999, called_oct3 0x80, calling=55555,calling_oct3 0x80, calling_oct3a 0x0, calling_xlated=false, fdest=1, voice_pee
r_tag=10001}, mode=0x0, xltrc=-5)
*Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:

In the next line, outgoing CallEntry ID 45 is bound to the same GUID 45F2AAE28044.
*Mar 1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: not incoming
entry

*Mar 1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: entry's incoming FALSE.
*Mar 1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: is_incoming
is FALSE
*Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag: (callID=0x2C, dialpeer_tag=10001)
*Mar 1 15:35:53.624: //45/xxxxxxxxxxxx/CCAPI/ccCallSetContext: (callID=0x2D, context=0x634A537C) 0x2D (decimal 45 is the second call leg ID).
*Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/ccCallReportDigits: (callID=0x2C,
enable=0x0)

The voice gateway informs the incoming call leg that digits were forwarded.

*Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/cc_api_call_report_digits_done: (vdbPtr=0x637EC1E0, callID=0x2C, disp=0)
*Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(54=CC_EV_CALL_
REPORT_DIGITS_DONE), cid(44), disp(0)
*Mar 1 15:35:53.624: //44/45F2AAE28044/SS
Router#APP:10002:-1/ssaTraceSct: cid(44)st(SSA_CS_CALL_SETTING)ev(SSA_EV_CALL_RE
PORT_DIGITS_DONE)
oldst(SSA_CS_MAPPING)cfid(-1)csize(0)in(1)fDest(1)
*Mar 1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaTraceSct: -cid2(45)st2
(SSA_CS_CALL_SETTING)oldst2(SSA_CS_MAPPING)
*Mar 1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaDebugPeers: ssaReportDigitsDone cid(44) peer list: tag(20002) called number (34999)
*Mar 1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaReportDigitsDone: call
id=44 Reporting disabled.
*Mar 1 15:35:53.628: //-1/xxxxxxxxxxxx/CCAPI/cc_api_supported_data: data_mode=0x10082
*Mar 1 15:35:53.628: //45/xxxxxxxxxxxx/CCAPI/cc_api_get_ic_leg_obtained_numbers: callID=0x2D

The next two lines shows the IP address of the terminating gateway and that the terminating gateway is reached through Ethernet port 0/0.

*Mar 1 15:35:53.628: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: remote IP
is 171.69.85.111
*Mar 1 15:35:53.632: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: hwidb is Ethernet0/0
*Mar 1 15:35:53.632: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: create entry in list: 1
*Mar 1 15:35:53.636: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetInstanceCount: For tagI
D[1] of callID[45]
*Mar 1 15:35:53.636: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessManager: No profileTable set for callID[45]
*Mar 1 15:35:53.636: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetInstanceCount: For tagID[2] of callID[45]
*Mar 1 15:35:53.636: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessManager: No profileTable set for callID[45]

The next line shows that the voice gateway received a call proceeding message from the terminating gateway, and then the following line shows that the voice gateway received a call alert from the terminating gateway.

*Mar 1 15:35:53.740: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_proceeding: (vdbPtr=0x62EC61A4, callID=0x2D,
prog_ind=0x0)
*Mar 1 15:35:53.740: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_alert: (vdbPtr=0x62EC61A4, callID=0x2D, prog_ind=0x0, sig_ind=0x1)
*Mar 1 15:35:53.744: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(21=CC_EV_CALL_PROCEEDING), cid(45), disp(0)
*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS
_CALL_SETTING)ev(SSA_EV_CALL_PROCEEDING)
oldst(SSA_CS_MAPPING)cfid(-1)csize(0)in(0)fDest(0)
*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA_CS_CALL_SETTING)oldst2(SSA_CS_CALL_SETTING)
*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaCallProc:
*Mar 1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C)
*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaIgnore: cid(45), st(SSA_CS
_CALL_SETTING),oldst(1), ev(21)
*Mar 1 15:35:53.744: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(7=CC_EV_CALL_ALERT), cid(45), disp(0)
*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS
_CALL_SETTING)ev(SSA_EV_CALL_ALERT)
oldst(SSA_CS_CALL_SETTING)cfid(-1)csize(0)in(0)fDest(0)
*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA
_CS_CALL_SETTING)oldst2(SSA_CS_CALL_SETTING)
*Mar 1 15:35:53.744: //44/45F2AAE28044/SSAPP:10002:-1/ssaAlert:
*Mar 1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C)
Router#

The voice gateway forwarded a call alert to the originating gateway.

*Mar 1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccCallAlert: (callID=0x2C, prog_ind=0x0, sig_ind=0x1)
Router#

The phone is answered at the called number.

Router#!call answered
Router#

The voice gateway receives a connect message from the terminating gateway.

*Mar 1 15:36:05.016: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_connected: (vdbPtr=0x6
2EC61A4, callID=0x2D), prog_ind = 0

*Mar 1 15:36:05.016: //45/45F2AAE28044/CCAPI/cc_api_call_connected: setting callEntry->connected to TRUE

The next line shows that the call accounting starts. The leg_type=False message means this is for an outgoing call. The line that follows shows that AAA accounting is not configured.

*Mar 1 15:36:05.016: //45/45F2AAE28044/CCAPI/cc_api_call_connected: calling accounting start for callID=45 leg_type=0
*Mar 1 15:36:05.020: //45/xxxxxxxxxxxx/CCAPI/ccCallSetAAA_Accounting: callID=0x
2D, accounting=0
*Mar 1 15:36:05.020: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(8=CC_EV_CALL_CONNECTED), cid(45), disp(0)
*Mar 1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS
_ALERT_RCVD)ev(SSA_EV_CALL_CONNECTED)
oldst(SSA_CS_CALL_SETTING)cfid(-1)csize(0)in(0)fDest(0)
*Mar 1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA
_CS_ALERT_RCVD)oldst2(SSA_CS_CALL_SETTING)
*Mar 1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaConnect:
*Mar 1 15:36:05.020: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C)

The next lines show a conference being set up between the two call legs 0x2C and 0x2D. Bridge complete messages are sent to both the terminating and originating gateways.

*Mar 1 15:36:05.020: //44/xxxxxxxxxxxx/CCAPI/ccConferenceCreate: (confID=0x6308
6424, callID1=0x2C, callID2=0x2D, tag=0x0)

*Mar 1 15:36:05.020: //45/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done: (confID=0x15,
srcIF=0x62EC61A4, srcCallID=0x2D, dstCallID=0x2C, disposition=0, tag=0x0)
*Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done: (confID=0x15,
srcIF=0x637EC1E0, srcCallID=0x2C, dstCallID=0x2D, disposition=0, tag=0x0)

Here, the voice gateway sets up negotiating capability with the originating telephony leg.

*Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (dstVdbPtr=0x62EC
61A4, dstCallId=0x2D, srcCallId=0x2C,
caps={codec=0x2887F, fax_rate=0xBF, vad=0x3, modem=0x2
codec_bytes=0, signal_type=3})
*Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (Playout: mode 0,
initial 60,min 40, max 300)
*Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(29=CC_EV_CONF_
CREATE_DONE), cid(44), disp(0)
*Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: cid(44)st(SSA_CS_CONFERENCING)ev(SSA_EV_CONF_CREATE_DONE)
oldst(SSA_CS_CALL_SETTING)cfid(21)csize(2)in(1)fDest(1)
*Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2
(SSA_CS_CONFERENCING)oldst2(SSA_CS_ALERT_RCVD)
*Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaConfCreateDone:
*Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/ccCallConnect: (callID=0x2C), prog
_ind = 0
*Mar 1 15:36:05.024: //44/45F2AAE28044/CCAPI/ccCallConnect: setting callEntry->
connected to TRUE

*Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaDebugPeers: ssaFlushPeerTagQueue cid(44) peer list: tag(20002) called number (34999)
*Mar 1 15:36:05.028: //-1/xxxxxxxxxxxx/CCAPI/cc_process_notify_bridge_done: (event=0x63067FC0)

The voice gateway sets up negotiating capability with the terminating VoIP leg.

*Mar 1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (dstVdbPtr=0x637E
C1E0, dstCallId=0x2C, srcCallId=0x2D,
caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0
codec_bytes=20, signal_type=2})
*Mar 1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (Playout: mode 0,
initial 60,min 40, max 300)

The capabilities are acknowledged for both call legs.

*Mar 1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ack: (dstVdbPtr=0x637E
C1E0, dstCallId=0x2C, srcCallId=0x2D,
caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0
codec_bytes=20, signal_type=2, seq_num_start=2944})
*Mar 1 15:36:05.028: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ack: (dstVdbPtr=0x62EC
61A4, dstCallId=0x2D, srcCallId=0x2C,
caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0
codec_bytes=20, signal_type=2, seq_num_start=2944})

*Mar 1 15:36:05.032: //44/xxxxxxxxxxxx/CCAPI/cc_api_voice_mode_event: callID=0x2C
*Mar 1 15:36:05.032: //44/45F2AAE28044/CCAPI/cc_api_voice_mode_event: Call Pointer =634A430C
*Mar 1 15:36:05.032: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(52=CC_EV_VOICE
_MODE_DONE), cid(44), disp(0)
*Mar 1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct:
Router#

Router# cid(44)st(SSA_CS_ACTIVE)ev(SSA_EV_VOICE_MODE_DONE)
oldst(SSA_CS_CONFERENCING)cfid(21)csize(2)in(1)fDest(1)
*Mar 1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2
(SSA_CS_ACTIVE)oldst2(SSA_CS_ALERT_RCVD)
*Mar 1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaIgnore: cid(44), st(SS
A_CS_ACTIVE),oldst(5), ev(52)
Router#
Router#! digit punched
Router#

The phone at the terminating gateway enters digit 1.

*Mar 1 15:36:11.204: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,
digit=1, digit_begin_flags=0x0, rtp_timestamp=0x0
rtp_expiration=0x0, dest_mask=0x2)
*Mar 1 15:36:11.504: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: (dstVdbPtr=
0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,
digit=1,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), digit_tone_mode=0

The phone at the terminating gateway enters digit 2.

*Mar 1 15:36:11.604: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin: (dstVdbPt
r=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,
digit=2, digit_begin_flags=0x0, rtp_timestamp=0x0
rtp_expiration=0x0, dest_mask=0x2)
*Mar 1 15:36:11.904: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: (dstVdbPtr=
0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,
digit=2,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), digit_tone_mode=0
Router#
Router#
*Mar 1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/cc_handle_periodic_timer: Calling
the callback, ccTimerctx - 0x628B6330
*Mar 1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/ccTimerStart: ccTimerctx - 0x628B6330
Router#
Router# !call hung up The user at the terminating gateway hangs up the call.
Router#

The voice gateway receives a disconnect message from the terminating gateway. The cause code is 0x10 which is normal call clearing.

*Mar 1 15:36:22.916: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnected: (vdbPtr=
0x62EC61A4, callID=0x2D, cause=0x10)
*Mar 1 15:36:22.920: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(11=CC_EV_CALL_
DISCONNECTED), cid(45), disp(0)
*Mar 1 15:36:22.920: //45/45F2AAE28044/SSAPP:0:21/ssaTraceSct: cid(45)st(SSA_CS
_ACTIVE)ev(SSA_EV_CALL_DISCONNECTED)
oldst(SSA_CS_ALERT_RCVD)cfid(21)csize(2)in(0)fDest(0)
*Mar 1 15:36:22.920: //45/45F2AAE28044/SSAPP:0:21/ssaTraceSct: -cid2(44)st2(SSA
_CS_ACTIVE)oldst2(SSA_CS_ACTIVE)
*Mar 1 15:36:22.920: ssa: Disconnected cid(45) state(5) cause(0x10)

The voice gateway begins tearing down the conference and dropping the bridge.

*Mar 1 15:36:22.920: //-1/xxxxxxxxxxxx/CCAPI/ccConferenceDestroy: (confID=0x15,
tag=0x0)
*Mar 1 15:36:22.920: //45/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done: (confID=0
x15, srcIF=0x62EC61A4, srcCallID=0x2D, dstCallID=0x2C, disposition=0 tag=0x0)
*Mar 1 15:36:22.920: //44/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done: (confID=0
x15, srcIF=0x637EC1E0, srcCallID=0x2C, dstCallID=0x2D, disposition=0 tag=0x0)
*Mar 1 15:36:22.924: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(30=CC_EV_CONF_
DESTROY_DONE), cid(44), disp(0)
*Mar 1 15:36:22.924: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: cid(44)st(SSA_CS_CONF_DESTROYING)ev(SSA_EV_CONF_DESTROY_DONE)
oldst(SSA_CS_ACTIVE)cfid(21)csize(2)in(1)fDest(1)
*Mar 1 15:36:22.924: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2
(SSA_CS_CONF_DESTROYING)oldst2(SSA_CS_ACTIVE)
*Mar 1 15:36:22.924: //45/45F2AAE28044/SSAPP:0:-1/ssaConfDestroyDone:
*Mar 1 15:36:22.924: //44/xxxxxxxxxxxx/CCAPI/ccCallDisconnect: (callID=0x2C, cause=0x10 tag=0x0)

The voice gateway stops call accounting on the incoming call, indicated by the leg_type=True message. The cause code is then set for the originating leg.

*Mar 1 15:36:22.924: //44/45F2AAE28044/CCAPI/ccCallDisconnect: calling accounting start for callID=44 leg_type=1
*Mar 1 15:36:22.924: //44/45F2AAE28044/CCAPI/ccCallDisconnect: existing_cause =
0x0, new_cause = 0x10
*Mar 1 15:36:22.924: //44/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info: (callID=0x2C)
*Mar 1 15:36:22.924: //45/xxxxxxxxxxxx/CCAPI/ccCallDisconnect: (callID=0x2D, cause=0x10 tag=0x0)

The voice gateway stops call accounting for the outgoing call, indicated by the leg_type=False message. The cause code is verified for the terminating leg.

*Mar 1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: calling accounting start for callID=45 leg_type=0
*Mar 1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: existing_cause =
0x10, new_cause = 0x10
*Mar 1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: using the existing_cause 0x10
*Mar 1 15:36:22.928: //45/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info: (callID=0x2D)
*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_api_icpif: expect factor = 0
*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/g113_calculate_impairment: (delay=79,
loss=0), Io=0 Iq=0 Idte=0 Idd=0 Ie=10 Itot=10
*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: the remote
IP is 171.69.85.111
*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: hwidb is Ethernet0/0
*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: reduce callnum of entry: 0, voip: 0, mmoip: 0
*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: remove an entry
*Mar 1 15:36:22.932: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnect_done: (vdbPtr=0x62EC61A4, callID=0x2D, disp=0, tag=0x0)
*Mar 1 15:36:22.932: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessManager: No profileTable set for callID[45]
*Mar 1 15:36:22.936: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetDataByRef: No tdObject
found in profileTable for tagID[6] of callID[45]
*Mar 1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: not incoming
entry
*Mar 1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: entry's incoming FALSE.
*Mar 1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: is_incoming
is FALSE
*Mar 1 15:36:22.940: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(12=CC_EV_CALL_
DISCONNECT_DONE), cid(45), disp(0)
*Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS
_DISCONNECTING)ev(SSA_EV_CALL_DISCONNECT_DONE)
oldst(SSA_CS_ACTIVE)cfid(-1)csize(2)in(0)fDest(0)
*Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA
_CS_DISCONNECTING)oldst2(SSA_CS_CONF_DESTROYING)
*Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaDisconnectDone:
*Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaAAA_CheckAccounting: accounting generation enabled
*Mar 1 15:36:22.940: //45/xxxxxxxxxxxx/CCAPI/ccCallSetAAA_Accounting: callID=0x2D, accounting=0
*Mar 1 15:36:22.944: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: not the VoIP or MMoIP
*Mar 1 15:36:22.948: //44/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnect_done: (vdbPtr=0x637EC1E0, callID=0x2C, disp=0, tag=0x0)
*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: ccFreeRawMsg
Info(0x6307595C)
*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: Decrement call volume counter 1
*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: current call volume: 0
*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: entry's incoming TRUE.
*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: is_incoming
is TRUE
*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: Deleting profileTable[0x6380E11C]
*Mar 1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructTDHashProfileTab: Destructor Profile Table (0x6380E11C)
*Mar 1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructInstanceTDObject: tdObject[0x63401148] tagID[5]
*Mar 1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructInstanceTDObject: tdObject[0x638BC1AC] tagID[6]
*Mar 1 15:36:22.956: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(12=CC_EV_CALL_
DISCONNECT_DONE), cid(44), disp(0)
*Mar 1 15:36:22.956: //44/45F2AAE28044/SSAPP:10002:-1/ssaTraceSct: cid(44)st(SSA_CS_DISCONNECTING)ev(SSA_EV_CALL_DISCONNECT_DONE)
oldst(SSA_CS_CONF_DESTROYING)cfid(-1)csize(1)in(1)fDest(1)
Router#
*Mar 1 15:36:22.956: //44/45F2AAE28044/SSAPP:10002:-1/ssaDisconnectDone:

Related Commands

Command
Description

debug voip ccapi error

Traces error logs in the CCAPI.

voice call debug

Allows configuration of the voice call debug output.


debug voip confmsp

To display debugging information from the Conference Media Service Provider (CONFMSP) and its related applications, use the debug voip confmsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip confmsp

no debug voip confmsp

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(8)T

This command was introduced.


Examples

The following is sample output from the debug voip confmsp command:

Router# debug voip confmsp

CONFMSP debugging is on
.
.
.
00:06:44:confmsp_setup_request:callID (6),
00:06:44:confmsp_setup_request:conf structure (63DD27E4) created,
00:06:44:confmsp_bridge:confID(4), callIDs(6,5) xmitFunc 61D46D4C, dstIF 64912880
00:06:44:confmsp_bridge:confID(4), callIDs(6,5) event queued
00:06:44:confmsp_act_bridge: state = CONFMSP_STATE_SETUP, event=EV_CONFMSP_BRIDGING
00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1
00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1
00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_SETUP,
event:EV_CONFMSP_BRIDGING, next_state:CONFMSP_STATE_CONNECT_CONFEREE
00:06:44:confmsp_get_dsmp_req_status:condition to be returned FALSE
00:06:44:confmsp_connect_response:found conf (63DD27E4) dsmp ret is 1
00:06:44:confmsp_act_bridge_success: state = CONFMSP_STATE_CONNECT_CONFEREE,
event=EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS confmsp_caps_ind:context = 65241B34
00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECT_CONFEREE,
event:EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_CONNECTED
00:06:44:confmsp_bridge:confID(5), callIDs(6,7) xmitFunc 61D46D4C, dstIF 64912880
00:06:44:confmsp_bridge:confID(5), callIDs(6,7) event queued
00:06:44:confmsp_act_bridge: state = CONFMSP_STATE_SETUP, event=EV_CONFMSP_BRIDGING
00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1
00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1
00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_SETUP,
event:EV_CONFMSP_BRIDGING, next_state:CONFMSP_STATE_CONNECT_CONFEREE
00:06:44:confmsp_get_dsmp_req_status:condition to be returned FALSE
00:06:44:confmsp_connect_response:found conf (6358A338) dsmp ret is 1
00:06:44:confmsp_act_bridge_success: state = CONFMSP_STATE_CONNECT_CONFEREE,
event=EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS confmsp_caps_ind:context = 63588E70
00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECT_CONFEREE,
event:EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_CONNECTED
00:06:44:confmsp_bridge:confID(6), callIDs(6,8) xmitFunc 61D46D4C, dstIF 64912880
00:06:44:confmsp_bridge:confID(6), callIDs(6,8) event queued
00:06:44:confmsp_act_bridge: state = CONFMSP_STATE_SETUP, event=EV_CONFMSP_BRIDGING
00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1
00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1
00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_SETUP,
event:EV_CONFMSP_BRIDGING, next_state:CONFMSP_STATE_CONNECT_CONFEREE
00:06:44:confmsp_get_dsmp_req_status:condition to be returned FALSE
00:06:44:confmsp_connect_response:found conf (6358CE50) dsmp ret is 1
00:06:44:confmsp_act_bridge_success: state = CONFMSP_STATE_CONNECT_CONFEREE,
event=EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS confmsp_caps_ind:context = 63DD2524
00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECT_CONFEREE,
event:EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_CONNECTED
00:07:28:confmsp_bdrop:confID(4), callIDs(6,5)
00:07:28:confmsp_bdrop:confID(4), callIDs(6,5) event queued
00:07:28:confmsp_act_bdrop: state = CONFMSP_STATE_CONNECTED, event=EV_CONFMSP_BRIDGEDROP
00:07:28:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECTED,
event:EV_CONFMSP_BRIDGEDROP, next_state:CONFMSP_STATE_DISCONNECT_CONFEREE
00:07:28:confmsp_get_dsmp_req_status:condition to be returned FALSE
00:07:28:confmsp_disconnect_response:found conf (63DD27E4)
00:07:28:confmsp_connect_response:found conf (63DD27E4) dsmp ret is 10
00:07:28:confmsp_act_bdrop_success: state = CONFMSP_STATE_DISCONNECT_CONFEREE,
event=EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS
00:07:28:CNFSM:cur_container:confmsp container,
cur_state:CONFMSP_STATE_DISCONNECT_CONFEREE,
event:EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_BRIDGE_DROPPED
00:07:28:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED,
event:CNFSM_LAMBDA_EVENT, next_state:CNFSM_NO_STATE_CHANGE
00:07:29:confmsp_bdrop:confID(6), callIDs(6,8)
00:07:29:confmsp_bdrop:confID(6), callIDs(6,8) event queued
00:07:29:confmsp_bdrop:confID(5), callIDs(6,7)
00:07:29:confmsp_bdrop:confID(5), callIDs(6,7) event queued
00:07:29:confmsp_act_bdrop: state = CONFMSP_STATE_CONNECTED, event=EV_CONFMSP_BRIDGEDROP
00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECTED,
event:EV_CONFMSP_BRIDGEDROP, next_state:CONFMSP_STATE_DISCONNECT_CONFEREE
00:07:29:confmsp_get_dsmp_req_status:condition to be returned FALSE
00:07:29:confmsp_act_bdrop: state = CONFMSP_STATE_CONNECTED, event=EV_CONFMSP_BRIDGEDROP
00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECTED,
event:EV_CONFMSP_BRIDGEDROP, next_state:CONFMSP_STATE_DISCONNECT_CONFEREE
00:07:29:confmsp_get_dsmp_req_status:condition to be returned FALSE
00:07:29:confmsp_disconnect_response:found conf (6358CE50)
00:07:29:confmsp_connect_response:found conf (6358CE50) dsmp ret is 10
00:07:29:confmsp_act_bdrop_success: state = CONFMSP_STATE_DISCONNECT_CONFEREE,
event=EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS
00:07:29:CNFSM:cur_container:confmsp container,
cur_state:CONFMSP_STATE_DISCONNECT_CONFEREE,
event:EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_BRIDGE_DROPPED
00:07:29:confmsp_act_terminate: state = CONFMSP_STATE_BRIDGE_DROPPED,
event=CNFSM_LAMBDA_EVENT
00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED,
event:CNFSM_LAMBDA_EVENT, next_state:CNFSM_NULL_STATE
00:07:29:confmsp_free_conf:freeing 6358CE50
00:07:29:confmsp_disconnect_response:found conf (6358A338)
00:07:29:confmsp_connect_response:found conf (6358A338) dsmp ret is 10
00:07:29:confmsp_act_bdrop_success: state = CONFMSP_STATE_DISCONNECT_CONFEREE,
event=EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS
00:07:29:CNFSM:cur_container:confmsp container,
cur_state:CONFMSP_STATE_DISCONNECT_CONFEREE,
event:EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_BRIDGE_DROPPED
00:07:29:confmsp_act_terminate: state = CONFMSP_STATE_BRIDGE_DROPPED,
event=CNFSM_LAMBDA_EVENT
00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED,
event:CNFSM_LAMBDA_EVENT, next_state:CNFSM_NULL_STATE
00:07:29:confmsp_free_conf:freeing 6358A338
00:07:29:confmsp_disconnect:callID (6)
00:07:29:confmsp_disconnect:callID (6) event queued
00:07:29:confmsp_act_disconnected: state = CONFMSP_STATE_BRIDGE_DROPPED,
event=EV_CONFMSP_DISCONNECT
00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED,
event:EV_CONFMSP_DISCONNECT, next_state:CNFSM_NULL_STATE
00:07:29:confmsp_free_conf:freeing 63DD27E4

debug voip dcapi

To debug the device control application programming interface (DCAPI), use the debug voip dcapi command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip dcapi [error | inout]

no debug voip dcapi [error | inout]

Syntax Description

error

(Optional) Displays error logs in the DCAPI.

inout

(Optional) Displays the execution path through the DCAPI.


Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(14)T

This command was introduced.


Usage Guidelines

The debug voip dcapi error command traces the error logs in the DCAPI, which is the software layer that interfaces the SCCP Telephony Control Application (STCAPP) with the Cisco CallManager using the Skinny Client Control Protocol (SCCP). Error logs are generated during normal call processing when there are insufficient resources, or when there are problems in the device control API. This debug command shows error events or unexpected behavior in system software.

The debug voip dcapi inout command shows how a call executes through the software. This command traces the execution path through the DCAPI during communications with the SCCP service provider interface (SPI) and the call control API (CCAPI) that controls the physical voice port. You can use the output from this command to understand how devices are being handled by the APIs and to see the call setup and teardown operations performed on the telephony call leg.

Examples

Following is sample output from the debug voip dcapi inout command during call setup:

Router# debug voip dcapi inout

*Jan 27 16:26:23.957: dc_api_device_set_ringer_res: Set Ringer message success
*Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_stop_tone_res:
*Jan 27 16:26:23.957: dc_api_device_stop_tone_res: Stop Tone message success
*Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_media_open_rcv_channel:
*Jan 27 16:26:23.957: dc_api_media_open_rcv_channel: evt DC_EV_MEDIA_OPEN_RCV_CHNL is successsfully enqueued to app
*Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_stop_tone_res:
*Jan 27 16:26:23.957: dc_api_device_stop_tone_res: Stop Tone message success
*Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_call_state_res:
*Jan 27 16:26:23.957: dc_api_device_call_state_res: Call State message success
*Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_call_info_res:

Table 334 describes the significant fields shown in the display.

Table 334 debug voip dcapi Field Descriptions

Field
Description

nn:nn:nn:

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

dc_api_message:

The DCAPI event in which the SCCP SPI translation occurred.



Related Commands

Command
Description

debug voip application stcapp events

Debugs STCAPP events.

debug voip application stcapp functions

Debugs STCAPP functions.


debug voip dialpeer

To display information about the voice dial peers, use the debug voip dialpeer command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip dialpeer [all | default | detail | error [call [informational] | software [informational]] | function | inout]

no debug voip dialpeer

Syntax Description

all

(Optional) Displays all dialpeer debugging messages.

default

(Optional) Displays dialpeer inout and error debugging messages. This option also runs if no keywords are added.

detail

(Optional) Displays detailed dialpeer information.

error

(Optional) Displays dialpeer error messages.

call

(Optional) Displays call processing errors.

informational

(Optional) Displays minor errors and major errors. Without the informational keyword, only major errors are displayed.

software

(Optional) Displays software processing errors.

function

(Optional) Displays dialpeer functions.

inout

(Optional) Displays dialpeer in/out functions.


Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(8)T

This command replaces the debug dialpeer command.


Usage Guidelines

Disable console logging and use buffered logging before using the debug voip dialpeer command. Using the debug voip dialpeer command generates a large volume of debugging messages, which can affect router performance.

Examples

The following examples show output for variations of the debug voip dialpeer command:

debug voip dialpeer detail on the Originating Gateway

debug voip dialpeer inout on the Terminating Gateway

For these examples, the topology shown in Figure 2 is used.

Figure 2 Network Topology for debug voip dialpeer Output Examples

debug voip dialpeer detail on the Originating Gateway

Router# debug voip dialpeer detail

voip dialpeer detail debugging is on
Router#

The following event identifies the called number:

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=83103
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=83103, Expanded String=83103, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

The following event identifies the incoming dial peer and shows that it has been matched:

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Incoming Dial-peer=1 Is Matched
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=83103
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=83103, Expanded String=83103, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_FAX
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Result=-1
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ANSWER; Calling Number=4085550111
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=4085550111T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_FAX
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Result=-1
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ORIGINATE; Calling Number=4085550111
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=4085550111T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_FAX
*Apr 18 21:07:35.295: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Result=-1

The following event shows the number expansion. This is the only dial peer debug command that shows the number expansion.

*Apr 18 21:07:35.295: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=83103, Expanded String=3600, Calling Number=
Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH

The next few lines show matching for the outgoing dial peer. These lines show the matching sequence if the first match is not available.

*Apr 18 21:07:35.295: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Outgoing Dial-peer=3600 Is Matched
*Apr 18 21:07:35.295: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Outgoing Dial-peer=36 Is Matched
*Apr 18 21:07:35.295: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Outgoing Dial-peer=360 Is Matched
*Apr 18 21:07:35.295: //-1/23ED4B1B8010/DPM/dpMatchCore:
Dial String=83103, Expanded String=3600, Calling Number=
Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH

debug voip dialpeer inout on the Terminating Gateway

Router# debug voip dialpeer inout

voip dialpeer inout debugging is on

The following event shows the calling and called numbers:

*May 1 19:32:11.731: //-1/6372E2598012/DPM/dpAssociateIncomingPeerCore:
Calling Number=4085550111, Called Number=3600, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH

The following event shows the incoming dial peer:

*May 1 19:32:11.731: //-1/6372E2598012/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=100
*May 1 19:32:11.731: //-1/6372E2598012/DPM/dpAssociateIncomingPeerCore:
Calling Number=4085550111, Called Number=3600, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*May 1 19:32:11.731: //-1/6372E2598012/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=100
*May 1 19:32:11.735: //-1/6372E2598012/DPM/dpMatchPeersCore:
Calling Number=, Called Number=3600, Peer Info Type=DIALPEER_INFO_SPEECH
*May 1 19:32:11.735: //-1/6372E2598012/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=3600
*May 1 19:32:11.735: //-1/6372E2598012/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
*May 1 19:32:11.735: //-1/6372E2598012/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)

The following event shows the matched dial peers in the order of priority:

List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=3600
2: Dial-peer Tag=36

Related Commands

Command
Description

call-block (dial peer)

Enables blocking of incoming calls on the dial peer.

carrier-id (dial-peer)

Identifies the carrier handling the incoming call.

session target (ENUM)

Specifies the ENUM search table for the target session.

show dial-peer voice

Displays the configuration of the dial peer.

translation-profile (dial-peer)

Assigns a translation profile to the dial peer.

trunkgroup (dial-peer)

Assigns a trunk group to the dial peer.

trunk-group-label (dial-peer)

Identifies the trunk group handling the incoming call.


debug voip dsm

To troubleshoot the DSP stream manager (DSM) subsystem, use the debug voip dsm command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip dsm [all | dsp | error | rtp | session | stats | tone | vofr]

no debug voip dsm

Syntax Description

all

(Optional) Displays all DSM debugging messages.

dsp

(Optional) Enables a digital signal processor (DSP) message trace.

error

(Optional) Displays DSM error messages.

rtp

(Optional) Enables Real-Time Protocol (RTP) debugging on DSM.

session

(Optional) Enables session debugging.

stats

(Optional) Displays DSM statistics.

tone

(Optional) Displays tone debugging.

vofr

(Optional) Enables Voice over Frame Relay (VoFR) debugging on the VPM.


Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(8)T

This command replaces the debug vtsp dsp command.

12.3(14)T

The vofr keyword is no longer available in Cisco IOS Release 12.3(14)T.


Usage Guidelines

To debug VoIP calls, use this command in conjunction with debug voip vtsp command and debug voip dsmp commands. All the related information for media processing is now available by using Distributed Stream Media Processor (DSMP). DSM is responsible for creating streams and issuing connections between them.

Examples

The following examples show output for variations of the debug voip dsm command:

debug voip dsm session on the Originating Gateway

debug voip dsm stats on the Terminating Gateway

debug voip dsm Session of a VoIP Call in Transition to Connected State and in Transition from Connected to Disconnected State

For these examples, the topology shown in Figure 3 is used.

Figure 3 Network Topology for debug voip dsm Examples

debug voip dsm session on the Originating Gateway

Router# debug voip dsm session

DSP Stream Manager session debugging is on
*Apr 18 21:15:39.679: //-1/44A507668015/DSM:(2/1:23):0:0:0/dsm_start_basic_sm: .
*Apr 18 21:15:39.679: //-1/44A507668015/DSM:(2/1:23):0:8:4/dsm_start_basic_sm: dsp resource manager opened. ret 4
*Apr 18 21:15:39.679: //-1/44A507668015/DSM:(2/1:23):0:8:4/dsm_open_voice_and_set_params: .
*Apr 18 21:15:39.679: //-1/44A507668015/DSM:(2/1:23):0:8:4/set_playout_dmgr: playout default

The following event shows the echo cancellation setting:

*Apr 18 21:15:39.679: //-1/44A507668015/DSM:(2/1:23):0:8:4/dsm_dsp_echo_canceller_control: echo_cancel: 1
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsp_stream_mgr_play_tone: .
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_INIT E:E_DSM_CC_GEN_TONE]
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_gen_tone: Tone is not on, ignoring
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_INIT]
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_INIT E:E_DSM_CC_BRIDGE]
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_bridge: .

The following event indicates that modem relay is not supported on the specified port, which is port 2/1:23:

*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_bridge: Modem Relay NOT Supported on this end-point/voice-port.
disabling it...
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGING]
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGING E:E_DSM_CC_CAPS_IND]
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: .
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: RTP PT:NTE[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDT
121],FaxRelay[122],CASsig[123],ClearChan[125],PCMu[0],PCMa[8]Codec[4], TxDynamicPayload[0], RxDynamicPayload[0]
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: dtmf relay: mode=1, codec=1
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: Modem Relay NOT Supported on this end-point/voice-port
disabling it...
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: passthrough: cap_modem_proto 4,cap_modem_codec 1, cap_
em_redundancy 0, payload 103, modem_relay 0, gw-xid 0
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_debug_caps_encap: Encap 1, Vad 2, Codec 0x4, CodecBytes 20,
FaxRate 1, FaxBytes 20, FaxNsf 0xAD0051
SignalType 2
DtmfRelay 1, Modem 2, SeqNumStart 0x5A1
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: FORKING Parameters are forking mask: 0, simple_forking
dec_mask: 0, complex_forking_codec_mask 0
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: playout: [ mode:1,init:60, min:40, max:200]. data_mode
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGING]
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGING E:E_DSM_CC_CAPS_ACK]
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ack: .
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ack: passthrough: cap_modem_proto 4, cap_modem_codec 1, cap
dem_redundancy 0, payload 103, modem_relay 0, gw-xid 0
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ack: Named Telephone Event payload rcv 101, tx 101
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_switch_codec: Required codec is 16, current dsp codec is -1
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_switch_codec: codec = 16
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_PENDING_CODEC_SWITCH]
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_PENDING_CODEC_SWITCH E:E_DSM_DS_PEND_SUCCESS]
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_pend_codec_success: .
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_open_voice_and_set_params:
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/set_playout_dmgr: playout default

The following event shows the echo cancellation setting:

*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_dsp_echo_canceller_control: echo_cancel: 1

The following event shows that the codec has changed:

*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_setup_stream_after_switch_codec_succ: codec change success
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_add_fork: .
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_fork_info: add_fork=0
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_get_xmit_info_node: .
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_fork_info: xmit func is 61A7CDC4, context is 64F42DA0 peer_c
_id: 44, stream_count: 1, update_flag 0
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_fork_info: The stream bit-mask is 1
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_fork_info: The stream type is 0
*Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_fork_info: The logical ssrc is 64 for stream 0
*Apr 18 21:15:39.699: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_stream_count:
*Apr 18 21:15:39.699: g711_voice_count=0 g711_avt_count = 0
g711_voice_avt_count = 0 complex_voice_count = 1
complex_avt_count = 0 complex_voice_avt_count = 0
*Apr 18 21:15:39.699: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGED]

debug voip dsm stats on the Terminating Gateway

Router# debug voip dsm stats

DSP Stream Manager stats debugging is on

The following event shows that the DSM is requesting statistics:

*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGED E:E_DSM_CC_REQ_PACK_STAT]
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_cc_stats_req: .
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_cc_stats_req: -1->dmgr=0x645461E0, stats_reqs=0

The following events show statistics for DSM transmission, reception, delay, and errors:

*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGED]
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGED E:E_DSM_DSP_GET_TX]
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: .
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: -4->dmgr=0x645461E0,stats_reqs=3

*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGED]
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGED E:E_DSM_DSP_GET_RX]
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: .
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: -4->dmgr=0x645461E0,stats_reqs=2

*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGED]
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGED E:E_DSM_DSP_GET_VP_DELAY]
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: .
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: -4->dmgr=0x645461E0,stats_reqs=1

*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGED]
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGED E:E_DSM_DSP_GET_VP_ERROR]
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: .
Router#
*May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: -4->dmgr=0x645461E0,stats_reqs=0

debug voip dsm Session of a VoIP Call in Transition to Connected State and in Transition from Connected to Disconnected State

The following is sample output from the debug voip dsm command, with Cisco IOS Release 12.3(14)T software, when a VoIP call is in transition to the connected state:

Router# debug voip dsm

*Jun 8 20:10:33.205: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_create: .
*Jun 8 20:10:33.209: //28/6F1FA7868003/DSM:(2/0:23):-1/set_echo_canceller_data: echo_cancel: 1
*Jun 8 20:10:33.209: //28/6F1FA7868003/DSM:(2/0:23):-1/set_echo_canceller_data: echo_flags: 55, echo_len: 512
*Jun 8 20:10:33.217: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_reserve_resource_cb: .
*Jun 8 20:10:33.217: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_set_elog_enable: .
*Jun 8 20:10:33.477: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_reinit_platform_info: .
*Jun 8 20:10:33.477: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_reserve_resource_cb: .
*Jun 8 20:10:33.485: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_bridge: .
*Jun 8 20:10:33.485: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_bridge:
*Jun 8 20:10:33.485: dsp_stream_mgr_bridge, src_call_id 28, dst_call_id 27
*Jun 8 20:10:33.485: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_bridge: creating packet streams
*Jun 8 20:10:33.489: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_insert_conn_array_entry: dmgr->connArr.count = 2
*Jun 8 20:10:33.489: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_do_caps_ind: .
*Jun 8 20:10:33.493: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_cap_ind_ack: src_call_id = 28, dst_call_id = 27, is_cap_ack = 1
*Jun 8 20:10:33.493: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_cap_ind_ack: src_call_id = 28, dst_call_id = 27, is_cap_ack = 0
*Jun 8 20:10:33.493: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_ind_negotiation: Caps in caps indication:
*Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: playout: [ mode:1,init:60, min:40, max:250]. data_mode:0
*Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: RTP PT:NTE[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDTMF[121],FaxRelay[122],CASsig[123],ClearC han[125],PCMu[0],PCMa[8]Codec[4], TxDynamicPayload[0], RxDynamicPayload[0]
*Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: passthrough: cap_modem_proto 4,cap_modem_codec 1, cap_modem_redundancy 1, payload 100, modem_relay 0, gw-xid 0
*Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_debug_caps_encap: Encap 1, Vad 2, Codec 0x4, CodecBytes 20,
FaxRate 2, FaxBytes 20, FaxNsf 0xAD0051
SignalType 2
DtmfRelay 1, Modem 2, SeqNumStart 0x0
*Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_ind_negotiation: Caps after caps negotiation:
*Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: playout: [ mode:1,init:60, min:40, max:250]. data_mode:0
*Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: RTP PT:NTE[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDTMF[121],FaxRelay[122],CASsig[123],ClearC han[125],PCMu[0],PCMa[8]Codec[4], TxDynamicPayload[0], RxDynamicPayload[0]
*Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: passthrough: cap_modem_proto 4,cap_modem_codec 1, cap_modem_redundancy 1, payload 100, modem_relay 0, gw-xid 0
*Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_debug_caps_encap: Encap 1, Vad 2, Codec 0x4, CodecBytes 20,
FaxRate 2, FaxBytes 20, FaxNsf 0xAD0051
SignalType 2
DtmfRelay 1, Modem 2, SeqNumStart 0x0
*Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_cap_ind_ack: packet streams already created during bridging
*Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_ind_negotiation: Caps in caps indication:
*Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: playout: [ mode:1,init:60, min:40, max:250]. data_mode:0
*Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: RTP PT:NTE[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDTMF[121],FaxRelay[122],CASsig[123],ClearC han[125],PCMu[0],PCMa[8]Codec[4], TxDynamicPayload[0], RxDynamicPayload[0]
*Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: passthrough: cap_modem_proto 4,cap_modem_codec 1, cap_modem_redundancy 1, payload 100, modem_relay 0, gw-xid 0
*Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_debug_caps_encap: Encap 1, Vad 2, Codec 0x4, CodecBytes 20,
FaxRate 2, FaxBytes 20, FaxNsf 0xAD0051
SignalType 2
DtmfRelay 1, Modem 2, SeqNumStart 0x0
*Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_ind_negotiation: Caps after caps negotiation:
*Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: playout: [ mode:1,init:60, min:40, max:250]. data_mode:0
*Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: RTP PT:NTE[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDTMF[121],FaxRelay[122],CASsig[123],ClearC han[125],PCMu[0],PCMa[8]Codec[4], TxDynamicPayload[0], RxDynamicPayload[0]
*Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: passthrough: cap_modem_proto 4,cap_modem_codec 1, cap_modem_redundancy 1, payload 100, modem_relay 0, gw-xid 0
*Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_debug_caps_encap: Encap 1, Vad 2, Codec 0x4, CodecBytes 20,
FaxRate 2, FaxBytes 20, FaxNsf 0xAD0051
SignalType 2
DtmfRelay 1, Modem 2, SeqNumStart 0x0
*Jun 8 20:10:33.509: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_connect_cb: .
*Jun 8 20:10:36.229: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_req_stats: .
*Jun 8 20:10:36.233: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_stats_cb: .
*Jun 8 20:10:38.265: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_req_stats: .
*Jun 8 20:10:38.269: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_stats_cb: .
*Jun 8 20:10:43.481: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_req_stats: .
*Jun 8 20:10:43.489: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_stats_cb: .

The following is sample output from the debug voip dsm command, with Cisco IOS Release 12.3(14)T software, when a VoIP call is in transition from connected to the disconnected state:

Router# debug voip dsm

*Jun 8 20:12:14.701: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_req_stats: .

*Jun 8 20:12:14.705: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_stats_cb: .

*Jun 8 20:12:18.721: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_bridge_drop:

*Jun 8 20:12:18.721: dsp_stream_mgr_bridge_drop, src_call_id 28, dst_call_id 27

*Jun 8 20:12:18.721: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_delete_conn_array_entry: dmgr->connArr.count = 0

*Jun 8 20:12:18.737: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_stats_cb: .

*Jun 8 20:12:18.765: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_destroy: .

*Jun 8 20:12:18.765: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmapi_accept_modem_passthrough_session: : dmgr: 6561C520, active sessions 0, max sessions: 16 rejected sessions till now: 0

*Jun 8 20:12:18.769: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_reserve_resource_cb: .

Related Commands

Command
Description

debug voip dsmp

Displays debugging information from the DSMP and its related applications.

debug voip vtsp

Displays information about the VTSP.


debug voip dsmp

To display debugging information from the Distributed Stream Media Processor (DSMP) and its related applications, use the debug voip dsmp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip dsmp [all | default | error | event | function | individual | inout | rtp | session | stats | tone | vofr]

no debug voip dsmp

Syntax Description

all

(Optional) Enables all DSMP debugging (except stats).

default

(Optional) Activates inout, error, and event debugging.

error

(Optional) Enables DSMP error debugging.

event

(Optional) Enables state machine debugging.

function

(Optional) Enables procedure tracing.

individual

(Optional) Enables individual DSMP debugging.

inout

(Optional) Enables subsystem inout debugging.

rtp

(Optional) Enables Real-Time Protocol (RTP) debugging on DSMP.

session

(Optional) Enables session debugging.

stats

(Optional) Enables DSMP statistics debugging.

tone

(Optional) Enables tone debugging.

vofr

(Optional) Enables Voice over Frame Relay (VoFR) debugging on the VPM.


Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(8)T

This command was introduced.

12.3(14)T

The all, default, error, event, function, individual, inout, rtp, session, stats, tone, and vofr keywords were added to the command.


Usage Guidelines

To debug VoIP calls, use this command in conjunction with debug voip vtsp command and debug voip dsm commands. All the related information for media processing is now available by using DSMP. DSM is responsible for creating streams and issuing connections between them.

Examples

The following is sample output from the debug voip dsmp command for transcoding call:

Router# debug voip dsmp

Syslog logging:enabled (11 messages dropped, 2 messages rate-limited,
0 flushes, 0 overruns, xml disabled, filtering disabled)
Console logging:disabled
Monitor logging:level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging:level debugging, 236 messages logged, xml disabled,
filtering disabled
Logging Exception size (4096 bytes)
Count and timestamp logging messages:disabled
Trap logging:level informational, 25 message lines logged
Log Buffer (3000000 bytes):
00:10:18:dsmpAddStream::
00:10:18:dsmpAddStream::
00:10:18:dsmpAddStream::
00:10:18:dsmpAddStream::
00:10:18:dsmpConnectXcodeBinderReq
00:10:18:dsmp_process_event:
00:10:18:dsmp_process_event:evt->requestType = E_DSMP_CC_XCODE_REQ
00:10:18:dsmpxc_act_alloc_rsc::state = S_DSMPXC_INITIAL event = E_DSMP_CC_XCODE_REQ
00:10:18:dsp_ret = 4 (if failed, cause = 0)
00:10:18:dsp_intf = 0x63DD21D8
00:10:18:dsmp_set_state_var:message to DSP
successful,ret::4
00:10:18:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_INITIAL,
event:E_DSMP_CC_XCODE_REQ, next_state:S_DSMPXC_RSC_ALLOCING
00:10:18:dsmp_is_ret_succ::
00:10:18:dsmpxc_act_init_rsc::state = S_DSMPXC_RSC_ALLOCING event = CNFSM_LAMBDA_EVENT
00:10:18:dsmp_set_state_var:message to DSP
successful,ret::4
00:10:18:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_RSC_ALLOCING,
event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_RSC_INITING
00:10:18:dsmp_is_ret_succ::
00:10:18:dsmpxc_act_open_rsc::state = S_DSMPXC_RSC_INITING event = CNFSM_LAMBDA_EVENT
00:10:18:dsmp_set_state_var:message to DSP
successful,ret::4
00:10:18:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_RSC_INITING,
event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_RSC_OPENING
00:10:18:dsmp_is_ret_succ::
00:10:18:dsmpxc_act_program_rsc::state = S_DSMPXC_RSC_OPENING event = CNFSM_LAMBDA_EVENT
00:10:18:dsmp_set_state_var:message to DSP
successful,ret::4
00:10:18:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_RSC_OPENING,
event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_XCODE_PEND
00:10:18:CNFSM:new_container:xcoding_container
00:10:18:dsmp_is_ret_succ::
00:10:18:dsmpxc_act_succ_conn_req::state = S_DSMPXC_XCODE_PEND event = CNFSM_LAMBDA_EVENT
00:10:18:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE_PEND,
event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_XCODE
00:10:18:no_stream_in_session

Router# clear log

Clear logging buffer [confirm]
Router#

Router# clear logsh logg

Syslog logging:enabled (11 messages dropped, 2 messages rate-limited,
0 flushes, 0 overruns, xml disabled, filtering disabled)
Console logging:disabled
Monitor logging:level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging:level debugging, 274 messages logged, xml disabled,
filtering disabled
Logging Exception size (4096 bytes)
Count and timestamp logging messages:disabled
Trap logging:level informational, 25 message lines logged
Log Buffer (3000000 bytes):
00:10:50:dsmpDeleteStream
00:10:50:dsmpDeleteStream
00:10:50:dsmpDeleteStream
00:10:50:dsmpDeleteStream
00:10:50:dsmp_process_event:
00:10:50:dsmp_process_event:evt->requestType = E_DSMP_CC_DELETE_STREAM
00:10:50:dsmpxc_act_delete_stream::state = S_DSMPXC_XCODE event = E_DSMP_CC_DELETE_STREAM
00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE,
event:E_DSMP_CC_DELETE_STREAM, next_state:CNFSM_NO_STATE_CHANGE
00:10:50:no_stream_in_session
00:10:50:dsmp_process_event:evt->requestType = E_DSMP_CC_DELETE_STREAM
00:10:50:dsmpxc_act_delete_stream::state = S_DSMPXC_XCODE event = E_DSMP_CC_DELETE_STREAM
00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE,
event:E_DSMP_CC_DELETE_STREAM, next_state:CNFSM_NO_STATE_CHANGE
00:10:50:no_stream_in_session
00:10:50:dsmp_process_event:evt->requestType = E_DSMP_CC_DELETE_STREAM
00:10:50:dsmpxc_act_delete_stream::state = S_DSMPXC_XCODE event = E_DSMP_CC_DELETE_STREAM
00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE,
event:E_DSMP_CC_DELETE_STREAM, next_state:CNFSM_NO_STATE_CHANGE
00:10:50:no_stream_in_session
00:10:50:dsmp_process_event:evt->requestType = E_DSMP_CC_DELETE_STREAM
00:10:50: dsmpxc_act_delete_stream::state = S_DSMPXC_XCODE event = E_DSMP_CC_DELETE_STREAM
00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE,
event:E_DSMP_CC_DELETE_STREAM, next_state:CNFSM_NO_STATE_CHANGE
00:10:50:no_stream_in_session
00:10:50:dsmpxc_act_stop_rsc::state = S_DSMPXC_XCODE event = CNFSM_LAMBDA_EVENT
00:10:50:dsmp_set_state_var:message to DSP
successful,ret::4
00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE,
event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_CLOSING
00:10:50:dsmp_is_ret_succ::
00:10:50:dsmpxc_act_dealloc_rsc::state = S_DSMPXC_CLOSING event = CNFSM_LAMBDA_EVENT
00:10:50:dsmp_set_state_var:message to DSP
successful,ret::4
00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_CLOSING,
event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_STILL_CLOSING
00:10:50:CNFSM:new_container:xcoder_container
00:10:50:dsmp_is_ret_succ::
00:10:50:dsmpxc_act_start_timer::state = S_DSMPXC_STILL_CLOSING event = CNFSM_LAMBDA_EVENT
00:10:50:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_STILL_CLOSING,
event:CNFSM_LAMBDA_EVENT, next_state:CNFSM_NO_STATE_CHANGE
00:10:50:dsmp_process_event:evt->requestType = E_DSMP_DSPRM_CLOSE_COMPLETE
00:10:50:dsmpxc_act_terminate::state = S_DSMPXC_STILL_CLOSING event =
E_DSMP_DSPRM_CLOSE_COMPLETE
00:10:50:dsmpxc_act_terminate Removing the program based stream = 1
00:10:50:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_STILL_CLOSING,
event:E_DSMP_DSPRM_CLOSE_COMPLETE, next_state:CNFSM_NULL_STATE
00:10:50:dsmp_free_session
00:10:50:dsmp_process_event:

The following is sample output from the debug voip dsmp command, with Cisco IOS Release 12.3(14)T software, when a VoIP call is in transition to the connected state:

Router# debug voip dsmp

*May 22 04:12:17.775: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: callID = 24, confID = -1, streamType = TDM, streamDir = INPUT, ownerContext = 0x0000000C, codec = 0x0, fax_modem_type =0, XmitFn = 0x00000000, multicastStreamDtmfType = 0
*May 22 04:12:17.775: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: streamID = 2
*May 22 04:12:17.779: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: callID = 24, confID = -1, streamType = TDM, streamDir = OUTPUT, ownerContext = 0x0000000C, codec = 0x0, fax_modem_type =0, XmitFn = 0x00000000, multicastStreamDtmfType = 0
*May 22 04:12:17.779: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: streamID = 3
*May 22 04:12:17.779: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpReserveGwResource: sIdLegInput1 = 2, sIdLegOutput1 = 3, requesterCallID = 24, respFunc = 0x61CD1EE0
*May 22 04:12:17.787: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_new_or_existing_gw_session: created a new session = 0x657EEE20
*May 22 04:12:17.787: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_enlist_stream: Stream 2 is enlisted, total = 1
*May 22 04:12:17.787: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_enlist_stream: Stream 3 is enlisted, total = 2
*May 22 04:12:17.787: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_exec:
[state:S_DSMP_INITIAL, event:E_DSMP_CC_RESERVE_RESOURCE_REQ]
*May 22 04:12:17.791: CNFSM: cur_container:rsc_main_container, cur_state:S_DSMP_INITIAL, event:E_DSMP_CC_RESERVE_RESOURCE_REQ
*May 22 04:12:17.791: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_gw_act_alloc_rsc:
*May 22 04:12:17.791: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_decide_pgm_based_stm:
*May 22 04:12:17.791: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful
*May 22 04:12:17.791: CNFSM: new_container:rsc_allocating_container
*May 22 04:12:17.791: CNFSM: next_state:S_DSMP_RSC_ALLOCATING
*May 22 04:12:17.791: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_alloc_succ:
*May 22 04:12:17.791: CNFSM: next_state:S_DSMP_RSC_ALLOCATED
*May 22 04:12:18.047: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpReserveGwResource: sIdLegInput1 = 2, sIdLegOutput1 = 3, requesterCallID = 24, respFunc = 0x61CD1EE0
*May 22 04:12:18.047: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_RESERVE_RESOURCE_REQ]
*May 22 04:12:18.051: CNFSM: cur_container:rsc_allocating_container, cur_state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_RESERVE_RESOURCE_REQ
*May 22 04:12:18.051: CNFSM: new_container:rsc_main_container
*May 22 04:12:18.051: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_reopen:
*May 22 04:12:18.051: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful
*May 22 04:12:18.051: CNFSM: history stored state: S_DSMP_RSC_ALLOCATED, container: rsc_allocating_container
*May 22 04:12:18.051: CNFSM: updated current container: rsc_main_container
*May 22 04:12:18.051: CNFSM: next_state:S_DSMP_RSC_REOPENING
*May 22 04:12:18.051: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_alloc_succ:
*May 22 04:12:18.051: CNFSM: restoring history state: S_DSMP_RSC_ALLOCATED
*May 22 04:12:18.055: CNFSM: restoring history container: rsc_allocating_container
*May 22 04:12:18.055: CNFSM: new_container:rsc_allocating_container
*May 22 04:12:18.055: CNFSM: next_state:S_DSMP_RSC_ALLOCATED
*May 22 04:12:18.055: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpStopPlay: sIdLegOutput = 3
*May 22 04:12:18.059: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_STOP_PLAY_REQ]
*May 22 04:12:18.059: CNFSM: cur_container:rsc_allocating_container, cur_state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_STOP_PLAY_REQ
*May 22 04:12:18.059: CNFSM: new_container:rsc_main_container
*May 22 04:12:18.059: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_ignore:
*May 22 04:12:18.059: CNFSM: next_state:CNFSM_NO_STATE_CHANGE
*May 22 04:12:18.063: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: callID = 23, confID = 12, streamType = PACKET, streamDir = INPUT, ownerContext = 0x0000000C, codec = 0x1, fax_modem_type =0, XmitFn = 0x6158E1F8, multicastStreamDtmfType = -1
*May 22 04:12:18.067: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: streamID = 1
*May 22 04:12:18.067: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: callID = 23, confID = 12, streamType = PACKET, streamDir = OUTPUT, ownerContext = 0x0000000C, codec = 0x1, fax_modem_type =0, XmitFn = 0x6158E1F8, multicastStreamDtmfType = -1
*May 22 04:12:18.067: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: streamID = 4
*May 22 04:12:18.071: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpUpdateRtpMode: sId = 1, callID = 24, mode = 1
*May 22 04:12:18.071: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpModifyReq: sIdLegInput = 1, sIdLegOutput = 4, callID = 24
*May 22 04:12:18.075: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpConnectGwBinderReq:
sIdLegInputTdm1=2, sIdLegOutputPak1=4, sIdLegInputPak2=1, sIdLegOutputTdm2=3, Call Id=24
*May 22 04:12:18.075: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpModifyReq: sIdLegInput = 2, sIdLegOutput = 3, callID = 24FORKING Parameters are forking mask: 7, simple_forking_codec_mask: 327679, complex_forking_codec_mask 327679
*May 22 04:12:18.075: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_process_event: No session is associated to the streams.
*May 22 04:12:18.075: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_caps:
*May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_packet_stream_caps:
*May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
*May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
CALL_ERROR; DSMP Session Is NULL
*May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:exit@2908
*May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
*May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
CALL_ERROR; DSMP Session Is NULL
*May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:exit@2908
*May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
*May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
CALL_ERROR; DSMP Session Is NULL
*May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:exit@2908
*May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
*May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
CALL_ERROR; DSMP Session Is NULL
*May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:exit@2908
*May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_packet_stream_caps:
*May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps:
*May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps:exit@385
*May 22 04:12:18.087: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps:
*May 22 04:12:18.087: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps:exit@385
*May 22 04:12:18.087: //-1/F401BFC88006/DSMP:():-1/dsmp_enlist_stream: Stream 1 is enlisted, total = 3
*May 22 04:12:18.087: //-1/F401BFC88006/DSMP:():-1/dsmp_enlist_stream: Stream 4 is enlisted, total = 4
*May 22 04:12:18.087: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_CONNECT_REQ]
*May 22 04:12:18.091: CNFSM: cur_container:rsc_allocating_container, cur_state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_CONNECT_REQ
*May 22 04:12:18.091: //-1/F401BFC88006/DSMP:():-1/dsmp_is_req_not_in_proc_dsp_ready:
*May 22 04:12:18.091: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_init:
*May 22 04:12:18.091: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful
*May 22 04:12:18.091: CNFSM: history stored state: S_DSMP_RSC_ALLOCATED, container: rsc_allocating_container
*May 22 04:12:18.091: CNFSM: new_container:rsc_main_container
*May 22 04:12:18.095: CNFSM: next_state:S_DSMP_RSC_INITING
*May 22 04:12:18.095: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_decide_pgm_based_stm:
*May 22 04:12:18.095: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_init_succ: pgm_base_stm_id = 1, service_id = 26, codec =4
*May 22 04:12:18.095: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful
*May 22 04:12:18.099: CNFSM: next_state:S_DSMP_RSC_OPENING
*May 22 04:12:18.099: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_open_succ:
*May 22 04:12:18.099: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
*May 22 04:12:18.099: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_static_params:
*May 22 04:12:18.099: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_static_params: servic_type=1 base stream=1 tdm_caps=0x6557E454 pkt_caps=0x6557EC3C
*May 22 04:12:18.099: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_static_params:
*May 22 04:12:18.103: ip_tones = 0, pstn_tones = 0
*May 22 04:12:18.103: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_conf_static_params: voice detection disabled
*May 22 04:12:18.103: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_conf_static_params: silence detection disabled
*May 22 04:12:18.103: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful
*May 22 04:12:18.107: CNFSM: next_state:S_DSMP_RSC_STATIC_CONF
*May 22 04:12:18.107: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_start_service:
*May 22 04:12:18.107: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful
*May 22 04:12:18.107: CNFSM: next_state:S_DSMP_RSC_STARTING
*May 22 04:12:18.107: //-1/F401BFC88006/DSMP:():-1/dsmp_act_rsc_start_succ:
*May 22 04:12:18.107: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_dynamic_params:
*May 22 04:12:18.111: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_dynamic_params: servic_type=1 base stream=1
*May 22 04:12:18.111: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
*May 22 04:12:18.111: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
*May 22 04:12:18.111: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:
*May 22 04:12:18.111: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_detector_params:
*May 22 04:12:18.115: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful
*May 22 04:12:18.115: CNFSM: next_state:S_DSMP_RSC_DYNAMIC_CONF
*May 22 04:12:18.115: CNFSM: new_container:rsc_running_container
*May 22 04:12:18.115: CNFSM: next_state:S_DSMP_MCAST_CHECK
*May 22 04:12:18.115: //-1/F401BFC88006/DSMP:():-1/dsmp_is_mcast:
*May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_mcast:exit@1487
*May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_not_mcast:
*May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_mcast:
*May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_mcast:exit@1487
*May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_not_mcast:exit@1500
*May 22 04:12:18.119: CNFSM: next_state:S_DSMP_DTMF_FSK_MODE_CHECK
*May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_fsk_or_dtmf:
*May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_diagnostic:
*May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_diagnostic:exit@1587
*May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_not_dtmf_fsk:
*May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_fsk_or_dtmf:
*May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_diagnostic:
*May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_diagnostic:exit@1587
*May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_not_dtmf_fsk:exit@1600
*May 22 04:12:18.127: CNFSM: next_state:S_DSMP_NOT_DTMF_FSK
*May 22 04:12:18.127: //-1/F401BFC88006/DSMP:():-1/dsmp_is_simple_voice:
*May 22 04:12:18.127: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_get_stm_service_type:
*May 22 04:12:18.127: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_simple_voice_start:
*May 22 04:12:18.127: //-1/F401BFC88006/DSMP:():-1/dsmp_connect_req_done:
*May 22 04:12:18.127: //-1/F401BFC88006/DSMP:():-1/dsmp_enlist_connection: Connection is added, enlisted LegIn: 2, enlisted LegOut: 4
*May 22 04:12:18.131: //-1/F401BFC88006/DSMP:():-1/dsmp_enlist_connection: Connection is added, enlisted LegIn: 1, enlisted LegOut: 3
*May 22 04:12:18.131: CNFSM: new_container:simple_voice_container
*May 22 04:12:18.131: CNFSM: next_state:S_DSMP_VC_RUNNING
*May 22 04:12:18.131: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_MODIFY_REQ]
*May 22 04:12:18.135: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_MODIFY_REQ
*May 22 04:12:18.135: CNFSM: new_container:rsc_running_container
*May 22 04:12:18.135: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_save_modify_caps:
*May 22 04:12:18.135: //-1/F401BFC88006/DSMP:():-1/dsmp_save_modify_caps:
*May 22 04:12:18.135: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_packet_stream_caps:
*May 22 04:12:18.139: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_packet_stream_caps:
*May 22 04:12:18.139: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps:
*May 22 04:12:18.139: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps:
*May 22 04:12:18.139: //-1/F401BFC88006/DSMP:():-1/dsmp_save_stream_detectors:
*May 22 04:12:18.139: CNFSM: history stored state: S_DSMP_VC_RUNNING, container: simple_voice_container
*May 22 04:12:18.139: CNFSM: updated current container: rsc_running_container
*May 22 04:12:18.143: CNFSM: next_state:S_DSMP_MODIFY_CAPS_SAVED
*May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_is_modify_to_modem_passthru:
*May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_is_static_params_changed:
*May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_is_modify_to_modem_passthru:
*May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_is_dynamic_params_changed:
*May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_is_modify_to_modem_passthru:
*May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_dynamic_params_changed:
*May 22 04:12:18.147: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_dynamic_params:
*May 22 04:12:18.147: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_dynamic_params: servic_type=1 base stream=1
*May 22 04:12:18.147: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_detector_params:
*May 22 04:12:18.147: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_conf_detector_params: fax: 1
*May 22 04:12:18.147: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_conf_detector_params: modem: 1
*May 22 04:12:18.151: CNFSM: restoring history state: S_DSMP_VC_RUNNING
*May 22 04:12:18.151: CNFSM: restoring history container: simple_voice_container
*May 22 04:12:18.151: CNFSM: new_container:simple_voice_container
*May 22 04:12:18.151: CNFSM: next_state:S_DSMP_VC_RUNNING
*May 22 04:12:18.163: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpUpdateRtpMode: sId = 1, callID = 24, mode = 3
*May 22 04:12:18.163: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpUpdateRtpMode: sId = 1, callID = 24, mode = 3
*May 22 04:12:30.947: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpUpdateRtpMode: sId = 1, callID = 24, mode = 3

The following is sample output from the debug voip dsmp command, with Cisco IOS Release 12.3(14)T software, when a VoIP call is in transition from connected to the disconnected state:

Router# debug voip dsmp
*May 22 04:12:30.951: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpDisconnectGwBinder: sIdLegInputTdm1 = 2, sIdLegOutputPak1 = 4, sIdLegInputPak2 = 1, sIdLegOutputTdm2 = 3 requesterCallID = 24
*May 22 04:12:30.951: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpDeleteStream: streamID = 1, callID = 23, ownerContext = 0x00000000
*May 22 04:12:30.951: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpDeleteStream: streamID = 4, callID = 23, ownerContext = 0x00000000
*May 22 04:12:30.951: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_DISCONNECT]
*May 22 04:12:30.955: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_DISCONNECT
*May 22 04:12:30.955: CNFSM: new_container:rsc_running_container
*May 22 04:12:30.955: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_cc_disconnect:
*May 22 04:12:30.955: //-1/F401BFC88006/DSMP:():-1/dsmp_delist_connection: Connection is delisted, delisted LegIn: 2, delisted LegOut: 4, total conn_count is = 1
*May 22 04:12:30.955: //-1/F401BFC88006/DSMP:():-1/dsmp_delist_connection: Connection is delisted, delisted LegIn: 1, delisted LegOut: 3, total conn_count is = 0
*May 22 04:12:30.955: CNFSM: next_state:CNFSM_NO_STATE_CHANGE
*May 22 04:12:30.955: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM]
*May 22 04:12:30.959: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM
*May 22 04:12:30.959: CNFSM: new_container:rsc_running_container
*May 22 04:12:30.959: CNFSM: new_container:rsc_main_container
*May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/dsmp_not_last_stream:
*May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/dsmp_is_last_stream:
*May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_not_last_stream:
*May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB:
*May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams:
*May 22 04:12:30.959: CNFSM: next_state:CNFSM_NO_STATE_CHANGE
*May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM]
*May 22 04:12:30.959: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM
*May 22 04:12:30.963: CNFSM: new_container:rsc_running_container
*May 22 04:12:30.963: CNFSM: new_container:rsc_main_container
*May 22 04:12:30.963: //-1/F401BFC88006/DSMP:():-1/dsmp_not_last_stream:
*May 22 04:12:30.963: //-1/F401BFC88006/DSMP:():-1/dsmp_is_last_stream:
*May 22 04:12:30.963: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_not_last_stream:
*May 22 04:12:30.963: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB:
*May 22 04:12:30.963: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams:
*May 22 04:12:30.963: CNFSM: next_state:CNFSM_NO_STATE_CHANGE
*May 22 04:12:30.967: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpStopPlay: sIdLegOutput = 3
*May 22 04:12:30.975: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_STOP_PLAY_REQ]
*May 22 04:12:30.975: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_STOP_PLAY_REQ
*May 22 04:12:30.975: CNFSM: new_container:rsc_running_container
*May 22 04:12:30.975: CNFSM: new_container:rsc_main_container
*May 22 04:12:30.975: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_ignore:
*May 22 04:12:30.975: CNFSM: next_state:CNFSM_NO_STATE_CHANGE
*May 22 04:12:31.011: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpStopPlay: sIdLegOutput = 3
*May 22 04:12:31.011: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpDeleteStream: streamID = 2, callID = 24, ownerContext = 0x0000000C
*May 22 04:12:31.011: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpDeleteStream: streamID = 3, callID = 24, ownerContext = 0x0000000C
*May 22 04:12:31.015: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_STOP_PLAY_REQ]
*May 22 04:12:31.015: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_STOP_PLAY_REQ
*May 22 04:12:31.015: CNFSM: new_container:rsc_running_container
*May 22 04:12:31.015: CNFSM: new_container:rsc_main_container
*May 22 04:12:31.015: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_ignore:
*May 22 04:12:31.015: CNFSM: next_state:CNFSM_NO_STATE_CHANGE
*May 22 04:12:31.015: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM]
*May 22 04:12:31.015: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM
*May 22 04:12:31.019: CNFSM: new_container:rsc_running_container
*May 22 04:12:31.019: CNFSM: new_container:rsc_main_container
*May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/dsmp_not_last_stream:
*May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/dsmp_is_last_stream:
*May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_not_last_stream:
*May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB:
*May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams:
*May 22 04:12:31.019: CNFSM: next_state:CNFSM_NO_STATE_CHANGE
*May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM]
*May 22 04:12:31.019: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM
*May 22 04:12:31.019: CNFSM: new_container:rsc_running_container
*May 22 04:12:31.023: CNFSM: new_container:rsc_main_container
*May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/dsmp_not_last_stream:
*May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/dsmp_is_last_stream:
*May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/dsmp_is_last_stream:
*May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_stop:
*May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB:
*May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams:
*May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful
*May 22 04:12:31.023: CNFSM: history stored state: S_DSMP_VC_RUNNING, container: simple_voice_container
*May 22 04:12:31.023: CNFSM: updated current container: rsc_main_container
*May 22 04:12:31.027: CNFSM: new_container:rsc_closing_container
*May 22 04:12:31.027: CNFSM: next_state:S_DSMP_RSC_STOPPING
*May 22 04:12:31.027: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_stopping_close:
*May 22 04:12:31.027: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful
*May 22 04:12:31.027: CNFSM: next_state:S_DSMP_DSPMGR_CLOSING
*May 22 04:12:31.027: //-1/F401BFC88006/DSMP:():-1/dsmp_exec:
[state:S_DSMP_DSPMGR_CLOSING, event:E_DSMP_DSPRM_CLOSE_COMPLETE]
*May 22 04:12:31.027: CNFSM: cur_container:rsc_closing_container, cur_state:S_DSMP_DSPMGR_CLOSING, event:E_DSMP_DSPRM_CLOSE_COMPLETE
*May 22 04:12:31.027: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_dspmgr_closing_complete:
*May 22 04:12:31.031: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB:
*May 22 04:12:31.031: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams:
*May 22 04:12:31.031: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB:
*May 22 04:12:31.031: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams:
*May 22 04:12:31.031: CNFSM: next_state:CNFSM_NULL_STATE
*May 22 04:12:31.031: //-1/F401BFC88006/DSMP:():-1/dsmp_free_session:

Related Commands

Command
Description

debug voip dsm

Displays debugging information from the DSM subsystem.

debug voip vtsp

Displays information about the VTSP.


debug voip dspapi

To troubleshoot the digital signal processor (DSP) application programming interface (API), use the debug voip dspapi command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip dspapi [all | command | default | detail | error [call [informational] | software [informational]] | function | inout | notification | response]

no debug voip dspapi

Syntax Description

all

(Optional) Displays all DSP API debugging messages.

command

(Optional) Displays DSP API commands.

default

(Optional) Displays DSP API detail, error, and inout debugging messages. This option also runs if no keywords are added.

detail

(Optional) Displays detailed information about commands sent to the DSP. This command is used in conjunction with other debug voip dspapi commands to show additional details when you use the command, notification, and response keywords.

error

(Optional) Displays DSP API errors.

call

(Optional) Displays call processing errors.

informational

(Optional) Displays minor errors and major errors. Without the informational keyword, only major errors are displayed.

software

(Optional) Displays software processing errors.

function

(Optional) Displays DSP API functions.

inout

(Optional) Displays output for the command, notification, and response keywords.

notification

(Optional) Displays DSP API notification messages.

response

(Optional) Displays DSP API response messages.


Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(8)T

This command replaces the debug dspapi command.

12.3(14)T

T.38 fax relay call statistics were made available to Call Detail Records (CDRs) through Vendor-Specific Attributes (VSAs) and added to the call log.


Usage Guidelines

DSP API message events used to communicate with DSPs are intended for use with Connexant (NextPort) and Texas Instruments (54x) DSPs.


Caution This command severely impacts performance and should be used only for single-call debug capture.

Examples

The following examples show output for variations of the debug voip dspapi command:

debug voip dspapi Command on the Originating Gateway

debug voip dspapi inout on the Terminating Gateway

debug voip dspapi Command Displaying T.38 fax Relay Statistics on the Terminating Gateway

For these examples, the topology shown in Figure 4 is used.

Figure 4 Network Topology for debug voip dspapi Examples

debug voip dspapi Command on the Originating Gateway

Router# debug voip dspapi command

voip dspapi command debugging is ON

Router#
*Apr 18 21:33:48.347: //-1/CD89F6A78020/DSPAPI/[2/1:23]/dsp_init:
*Apr 18 21:33:48.347: //-1/CD89F6A78020/DSPAPI/[2/1:23]/dsp_voice_config_params:
*Apr 18 21:33:48.347: 9 parameters

The following lines show encapsulation settings, jitter, inband signaling, echo cancellation, gain, and other quality of service (QoS) settings:

[0] ENCAP RTP: Tx SSRC=0, Rx SSRC=0, Tx VPXCC=0, Rx VPXCC=0
IFP payload type=122, SID support=1, TSE payload=101, Sequence number start=0
Redundancy=0, ClearChannel payload type=0, Fax payload type=0
Alaw PCM switchover=0, MuLAW PCM switchover=0
DTMF payload type=0, NTE receive payload type=101
Dynamic payload=0, Codec=g711ulaw
[1] PO_JITTER: mode=2 initial=60(ms) max=200(ms) min=40(ms) fax_nom=300(ms)
[2] INBAND_SIG: mode=0x1 enable
[3] ECHO_CANCEL: Flags=0x37, Echo length=64(ms)
[4] IDLE_CODE_DET: Enable=0, Code=0x0, Duration=6000(ms)
[5] GAIN: Input=0.0(dB), Output=0.0(dB)
[6] CNG: 1
[7] INFO_FIELD_SIZE: 160 bytes
[8] DIGIT_RELAY: 2
*Apr 18 21:33:48.359: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_voice_get_capabilities:
*Apr 18 21:33:48.359: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_stop_service:
NONE (0)
*Apr 18 21:33:48.359: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_open_service:
G729IETF (25)
*Apr 18 21:33:48.359: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_voice_config_params:

The following lines show settings for encapsulation, packet suppression, and voice activity detection (VAD):

*Apr 18 21:33:48.359: 3 parameters
[0] ENCAP RTP: Tx SSRC=64, Rx SSRC=0, Tx VPXCC=0, Rx VPXCC=0
IFP payload type=122, SID support=19, TSE payload=101, Sequence number start=3238
Redundancy=0, ClearChannel payload type=125, Fax payload type=122
Alaw PCM switchover=8, MuLAW PCM switchover=0
DTMF payload type=121, NTE receive payload type=101
Dynamic payload=0, Codec=g729r8
[1] PAK_SUPPRESS: 0
[2] VAD: Enable=1, Threshold=-38(dBm)
.
.
.
*Apr 18 21:33:48.363: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_start_service:
G729IETF (25)
*Apr 18 21:33:48.363: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_voice_config_params:
*Apr 18 21:33:48.363: 1 parameter
[0] VAD: Enable=1, Threshold=-38(dBm)
*Apr 18 21:33:50.867: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_query_info:
Request ID=1, Reset Flag=FALSE Q:PO_Delay PO_Error TX RX
.
.
.
*Apr 18 21:34:15.031: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_query_info:
Request ID=5, Reset Flag=TRUE Q:Error
*Apr 18 21:34:15.031: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_query_info:
Request ID=5, Reset Flag=TRUE Q:Levels
*Apr 18 21:34:15.031: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_inband_tone_off:
*Apr 18 21:34:15.031: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_stop_service:
G729IETF (25)
*Apr 18 21:34:15.031: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_close_service:
G729IETF (25)

debug voip dspapi inout on the Terminating Gateway

Router# debug voip dspapi inout

voip dspapi inout debugging is ON

*May 1 19:59:15.579: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_init:
*May 1 19:59:15.579: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_voice_config_params:
*May 1 19:59:15.579: 9 parameters

The following lines show encapsulation settings, jitter, inband signalling, echo cancellation, gain, and other quality of service (QoS) settings:

[0] ENCAP RTP: Tx SSRC=0, Rx SSRC=0, Tx VPXCC=0, Rx VPXCC=0
IFP payload type=122, SID support=1, TSE payload=101, Sequence number start=0
Redundancy=0, ClearChannel payload type=0, Fax payload type=0
Alaw PCM switchover=0, MuLAW PCM switchover=0
DTMF payload type=0, NTE receive payload type=101
Dynamic payload=0, Codec=g711ulaw
[1] PO_JITTER: mode=2 initial=60(ms) max=200(ms) min=40(ms) fax_nom=300(ms)
[2] INBAND_SIG: mode=0x1 enable
[3] ECHO_CANCEL: Flags=0x17, Echo length=8(ms)
[4] IDLE_CODE_DET: Enable=0, Code=0x0, Duration=6000(ms)
[5] GAIN: Input=0.0(dB), Output=-6550.6(dB)
[6] CNG: 1
[7] INFO_FIELD_SIZE: 160 bytes
[8] DIGIT_RELAY: 2
.
.
*May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_voice_get_capabilities:
*May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_stop_service:
NONE (0)
*May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_open_service:
G729IETF (25)
*May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_voice_config_params:
*May 1 19:59:15.587: 3 parameters
[0] ENCAP RTP: Tx SSRC=0, Rx SSRC=0, Tx VPXCC=0, Rx VPXCC=0
IFP payload type=122, SID support=19, TSE payload=101, Sequence number start=2977
Redundancy=0, ClearChannel payload type=125, Fax payload type=122
Alaw PCM switchover=8, MuLAW PCM switchover=0
DTMF payload type=121, NTE receive payload type=101
Dynamic payload=0, Codec=g729r8
[1] PAK_SUPPRESS: 0
[2] VAD: Enable=1, Threshold=-38(dBm)
*May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_idle_service:
G729IETF (25)
*May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_voice_config_params:
*May 1 19:59:15.587: 3 parameters
[0] INFO_FIELD_SIZE: 20 bytes
[1] ENCAP RTP: Tx SSRC=64, Rx SSRC=0, Tx VPXCC=0, Rx VPXCC=0
IFP payload type=122, SID support=19, TSE payload=101, Sequence number start=2977
Redundancy=0, ClearChannel payload type=125, Fax payload type=122
Alaw PCM switchover=8, MuLAW PCM switchover=0
DTMF payload type=121, NTE receive payload type=101
Dynamic payload=0, Codec=g729r8
[2] DIGIT_RELAY: 2
*May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_start_service:
G729IETF (25)
*May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_voice_config_params:
*May 1 19:59:15.587: 1 parameter
[0] VAD: Enable=1, Threshold=-38(dBm)
*May 1 19:59:15.591: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_inband_tone_on:
Tone ID=1, Direction=2, Num frequencies=2
Frequency(hz): a=440 b=480, Amplitude(dB): a=-16.0 b=-16.0
Cadence1(ms): ON=2000 OFF=4000
Cadence2(ms): ON=0 OFF=0
Cadence3(ms): ON=0 OFF=0
Cadence4(ms): ON=0 OFF=0
Frequency(hz): a2=25667 b2=51816 a3=0 b3=1 a4=24596 b4=52484
ITO option group: 1
*May 1 19:59:17.195: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_inband_tone_off:
01:19:04: %PS-3-MULTFAIL: There is more than one failure with the Power System 1; please resolve problems immediately

The following statistics repeat for each DSP query. The transmit (tx) and receive (rx) statistics show number of packets, comfort noise settings, duration, and packet status.

*May 1 19:59:18.051: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_query_info:
Request ID=1, Reset Flag=FALSE Q:PO_Delay PO_Error TX RX
*May 1 19:59:18.051: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_tx_stats:
Request ID=1, Packets: Voice=113, Signaling=0, ComfortNoise=1
TX duration=2460(ms): Voice=2260(ms), FAX=0(ms)
*May 1 19:59:18.051: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_rx_stats:
Request ID=1, Packets: Voice=33, Signalling=0, ComfortNoise=1
RX duration=840(ms): Voice=640(ms), FAX=0(ms)
Packets: Bad Sequence=0, Bad Protocol=0, Late=0, Early=1
*May 1 19:59:18.051: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_playout_delay_stats:
Request ID=1, Current=70(ms), MIN=70(ms), MAX=70(ms)
Clock offset=80(ms), Inter arrival jitter=67082420(ms)
*May 1 19:59:18.051: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_playout_error_stats:
Request ID=1
Concealment: Predictive=0(ms), Interpolative=0(ms), Silence=0(ms)
Retro Memory update=0(ms), Buffer overflow=10(ms)
Talkspurt endpoint detection errors=0
*May 1 19:59:19.827: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_query_info:
Request ID=1, Reset Flag=FALSE Q:PO_Delay PO_Error TX RX
.
.
.

debug voip dspapi Command Displaying T.38 fax Relay Statistics on the Terminating Gateway

This output shows the fax relay statistics.

Router# debug voip dspapi

voip dspapi debugging is ON
.
.
.
May 7 21:32:16.472 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_playout_error_stats:
Request ID=1
Concealment: Predictive=0(ms), Interpolative=0(ms), Silence=0(ms)
Retro Memory update=0(na)(ms), Buffer overflow=0(ms)
Talkspurt endpoint detection errors=0
May 7 21:32:18.996 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_query_info:
Request ID=1, Reset Flag=FALSE Q:PO_Delay PO_Error TX RX
May 7 21:32:18.996 UTC: np_vsmgr_dispatch_voice_rsp(1/3): VOICE_LINK_INFO_RSP_NTF Received
May 7 21:32:18.996 UTC: request_id = 0x01, request_type = 0x0F
May 7 21:32:18.996 UTC: VOICE_TRANSMIT_STATS(1/3): num_voice_packets 36 num_sig_packets 0 num_cn_packets 1 transmit_duration AD2 end_point_detection 0
May 7 21:32:18.996 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_tx_stats:
Request ID=1, Packets: Voice=54, Signaling=0, ComfortNoise=1
TX duration=2770(ms): Voice=0(ms), FAX=0(na)(ms)
May 7 21:32:18.996 UTC: VOICE_RECEIVE_STATS(1/3): num_voice_packets 20 num_sig_packets 0 num_cn_packets 2 receive_duration AD2 voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0
May 7 21:32:18.996 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_rx_stats:
Request ID=1, Packets: Voice=32, Signalling=0, ComfortNoise=2
RX duration=2770(ms): Voice=0(ms), FAX=0(na)(ms)
Packets: Bad Sequence=0, Bad Protocol=0, Late=0, Early=0
May 7 21:32:18.996 UTC: VOICE_PLAYOUT_DELAY_STATS(1/3): curr_playout_delay 5A min_playout_delay 5A max_playout_delay 5A clock offset 2F07E72
May 7 21:32:19.000 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_playout_delay_stats:
Request ID=1, Current=90(ms), MIN=90(ms), MAX=90(ms)
Clock offset=49315442(ms), Inter arrival jitter=0(na)(ms)
May 7 21:32:19.000 UTC: VOICE_PLAYOUT_ERROR(1/3): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0
May 7 21:32:19.000 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_playout_error_stats:
Request ID=1
Concealment: Predictive=0(ms), Interpolative=0(ms), Silence=0(ms)
Retro Memory update=0(na)(ms), Buffer overflow=0(ms)
Talkspurt endpoint detection errors=0
May 7 21:32:21.456 UTC: VOICE_DET_STATUS_CHANGE_NTF(1/3): detector mask: 1 timestamp 51709BF8
May 7 21:32:21.456 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_voice_det_status_change:
Status=1, Timestamp=1366334456, Tone ID=0, Trigger=TRUE
May 7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_voice_config_params:
May 7 21:32:21.464 UTC: 1 parameter
[0] PAK_SUPPRESS: 1
May 7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_stop_service:
G729IETF (26)
May 7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_config_params:
1 parameters
May 7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_open_service:
FAX_RELAY (27)
May 7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_is_call_pending:
Call is not PENDING
May 7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_set_call_pending:
Set PENDING state
May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_query_link_info:
Request ID=0, Group ID=1
May 7 21:32:21.504 UTC: vsm(1/3): np_vsmgr_voice_state_change() - state IDLE
May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_is_call_pending:
Call is PENDING
May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_reset_call_pending:
Reset PENDING state
May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_call_status:
Status=PENDING_SUCCESS
May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_config_params:
11 parameters
May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_start_service:
FAX_RELAY (27)
May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_set_call_pending:
Set PENDING state
May 7 21:32:22.556 UTC: vsm(1/3): np_vsmgr_voice_state_change() - state ACTIVE
May 7 21:32:22.556 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_is_call_pending:
Call is PENDING
May 7 21:32:22.556 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_reset_call_pending:
Reset PENDING state
May 7 21:32:22.556 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_call_status:
Status=PENDING_SUCCESS
May 7 21:32:22.564 UTC: FAX_RELAY_LINK_INFO_RSP_NTF: slot 1 port 3 timestamp 76082770 fr-entered (20ms)
May 7 21:32:22.564 UTC: chan_id [3/1:D (8)] np_vsmgr_fax_relay_link_info_response:
May 7 21:32:29.712 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode:
T30 msg : 0x4
May 7 21:32:30.436 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode:
T30 msg : 0x2
May 7 21:32:30.784 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode:
T30 msg : 0x1
May 7 21:32:33.936 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode:
T30 msg : 0x42
May 7 21:32:34.280 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode:
T30 msg : 0x41
May 7 21:32:39.676 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode:
T30 msg : 0x21
May 7 21:32:39.676 UTC: np_fax_relay_t30_decode : Rx Direction
May 7 21:32:39.736 UTC: FARELAY_INIT_HS_MOD : 0x8
May 7 21:33:10.385 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode:
T30 msg : 0x7D
May 7 21:33:13.073 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode:
T30 msg : 0x31
May 7 21:33:15.217 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode:
T30 msg : 0x5F
May 7 21:33:16.073 UTC: FAX_RELAY_DET_STATUS_CHANGE: slot: 1 port: 3 detector mask 0x2
May 7 21:33:16.073 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_det_status:
Status=2, Timestamp=716372818
May 7 21:33:16.073 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_query_info:
Request ID=5, Reset Flag=FALSE Q:FaxRelay
May 7 21:33:16.097 UTC: FAX_RELAY_DATA_PUMP_STATS(1/3) - valid:0x3FFC1F55 state_code:0x1 level:0x18 phase_jitter:0x0 freq_offset:0x0 eqm:0x7FFE jit_depth:0x38B jit_buf_ov:0x0 tx_paks:0x5A rx_pkts:0x62C inv_pkts:0x0 oos_pkts:0x0 hs_mod:0x8 init_hs_mod:0x8 tx_pgs:0x0 rx_pgs:0x1 ecm:0x1 nsf_country:0x0 nsf_manuf_len:0x20 nsf_manuf:0031B8EE80C48511DD0D0000DDDD0000DDDD000000000000000022ED00B0A400 encap:0x1 pkt_loss_con:0x0
May 7 21:33:16.097 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_stats:
Request ID=5, MAX jitter depth=907, MAX net RX qdepth=0(na)
Jitter buffer overflow=0, Net RX qoverflow=0(na)
Packets: TX=90 TX drops=0(na)
Packets: RX=1580 RX loss=0(na), RX invalid=0, RX OOSequence=0
HS modulation=8, Pages: TX=0 RX=1
MAX TX In qdepth=0(na), MAX RX Out qdepth=0(na)
MAX HS buffer usage=0(na), TX In qoverflow=0(na), RX Out qoverflow=0(na)
FAX: State=1, level=24, Phase jitter=0, Frequency offset=0, EQM=32766
Initial HS modulation=8, Fax Direction=2, ECM Enabled=1
NSF Countery Code=0, nsf_manuf_code[32]=0031
Encapsulation Protocol=1, Pkt Loss Conceal=0
May 7 21:33:16.101 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_stop_service:
FAX_RELAY (27)
May 7 21:33:16.101 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_open_service:
G729IETF (26)
May 7 21:33:16.101 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_is_call_pending:
Call is not PENDING
May 7 21:33:16.101 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_set_call_pending:
Set PENDING state
May 7 21:33:16.985 UTC: FAX_RELAY_LINK_INFO_RSP_NTF: slot 1 port 3 timestamp 76518179 fr-end
May 7 21:33:17.001 UTC: vsm(1/3): np_vsmgr_voice_state_change() - state IDLE
May 7 21:33:17.001 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_is_call_pending:
Call is PENDING
May 7 21:33:17.001 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_reset_call_pending:
Reset PENDING state
May 7 21:33:17.001 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_call_status:
Status=PENDING_SUCCESS
May 7 21:33:17.001 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_voice_config_params:
May 7 21:33:17.001 UTC: 4 parameters
.
.
.

Related Commands

Command
Description

debug voip hpi

Enables debugging for HPI message events.


debug voip eddri

To turn on debugging for the event dispatcher and data repository interface (EDDRI), use the debug voip eddri command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip eddri {event | timers | prefix | all}

no debug voip eddri {event | timers | prefix | all}

Syntax Description

event

Turns on debugging for EDDRI events.

timers

Turns on debugging for EDDRI timers.

prefix

Turns on debugging for the prefix database.

all

Turns on debugging all EDDRI activities.


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(1)

This command was introduced.


Usage Guidelines

There is always a performance penalty when using debug commands.

The EDDRI notifies TGREP when an attribute changes on some subsystems. EDDRI interacts with the dial peer subsystem, the trunk group subsystems, call control API (CCAPI) subsystem and the customer relationship management (CRM) subsystem to notify changes in particular attributes. EDDRI is responsible for creating the prefix database.

Examples

The following example shows sample output from the debug voip eddri command:

21:00:53: eddri_interesting_ac_pt: new AC_curr 22 FD_curr -5 SD_curr -5
21:00:53: eddri_interesting_ac_pt: percent trigger diff 4
21:00:53: eddri_interesting_ac_pt: Interesting Point
21:00:53: eddri_send_prefix_event_to_clients : reason 0x40 num_prefix 1

With the send prefix event the available circuits value and the triggers for reporting are updated.

21:00:53: eddri_send_prefix_event_to_clients attr 0xFF ev_id 1 qid 0x64209230 reason 0x40
eddri_dequeue_event : dequeue event

21:00:53: eddri_interesting_ac_pt : tc 23 IAC 22 lwm 5 hwm 50 pct_trigger 2 oneMinusW 933
21:00:53: eddri_interesting_ac_pt: old AC_curr 23 FD_curr 0 SD_curr 0
21:00:53: eddri_interesting_ac_pt: new AC_curr 22 FD_curr -5 SD_curr -5
21:00:53: eddri_interesting_ac_pt: percent trigger diff 4
21:00:53: eddri_interesting_ac_pt: Interesting Point
21:00:53: eddri_send_prefix_event_to_clients : reason 0x40 num_prefix 1

Related Commands

Command
Description

debug tgrep error

Turns on debugging for any errors in functioning.

debug tgrep events

Turns on debugging for main events occurring throughout the subsystem.

debug tgrep fsm

Turns on debugging for FSM activity.

debug tgrep io

Turns on debugging for detailed socket level activities.

debug tgrep messages

Turns on debugging for the movement of TGREP messages.

debug tgrep msgdump

Turns on debugging for the dump of the details of TGREP messages.

debug tgrep timer-event

Turns on debugging for events that are related to the timer.

debug tgrep timers

Turns on debugging for timer activity.

debug tgrep tripr

Turns on debugging for the TRIP Reporter.

show voice eddri prefix

Shows applicable prefixes for the EDDRI.


debug voip enum

To view Voice over IP (VoIP) telephone number mapping (ENUM) information, use the debug voip enum command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip enum {detail | summary}

no debug voip enum {detail | summary}

Syntax Description

detail

Displays detailed output.

summary

Displays summary output.


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(11)T

This command was introduced.


Usage Guidelines

Disable console logging and use buffered logging before using the debug voip enum command. Using the debug voip enum command generates a large volume of debugs, which can affect router performance.

Examples

The following shows sample output from the debug voip enum detail command:

The output shows the match number as 5108891234, enum table as 10. Rule 1 in table 10 matched the pattern and after applying the replacement rule, the resulting string is 5108891234. The enum query is sent out for the domain 4.3.2.1.9.8.8.0.1.5.e164.cisco.com. The output then shows the matching Naming Authority Pointer (NAPTR) records obtained in the response. The records are then processed and the final URLs (contact lists) are shown toward the end.

Router# debug voip enum detail

enum_resolve_domain:match_num 5108891234 table_indx 10
enum_resolve_domain:rule 1 result string 5108891234
generate_enum_search_string :search string 4.3.2.1.9.8.8.0.1.5.e164.cisco.com
enum_dns_query:name = 4.3.2.1.9.8.8.0.1.5.e164.cisco.com type = 35, ns_server = 0
order 100 pref 10 service sip+E2U flag U
regexp /^.*$/sip:5108891234@1.8.50.14/ replacement
order 200 pref 10 service h323+E2U flag U
regexp /^.*$/h323:5555@1.5.1.1/ replacement
num_elem = 2
NAPTR Record :order 100 pref 10 service sip+E2U
flags U regexp /^.*$/sip:5108891234@1.8.50.14/
replacement
NAPTR Record :order 200 pref 10 service h323+E2U
flags U regexp /^.*$/h323:5555@1.5.1.1/
replacement
decode_naptr_record :re_string ^.*$
decode_naptr_record :re_substitution_string sip:5108891234@1.8.50.14
decode_naptr_record :re_flags_string
U_FLAG case, stopping query
new_e164_user sip:5108891234@1.8.50.14
decode_naptr_record :re_string ^.*$
decode_naptr_re
tahoe13#cord :re_substitution_string h323:5555@1.5.1.1
decode_naptr_record :re_flags_string
U_FLAG case, stopping query
new_e164_user h323:5555@1.5.1.1
contact_list :
sip:5108891234@1.8.50.14
contact_list :
h323:5555@1.5.1.1
enum_resolve_domain:contact_list 64558450

A sample output of the debug voip enum summary command is shown below.

The output shows the matching number, the enum table used and the rule in the table that matched the number along with the resulting string. Note that this output is a subset of the output from debug voip enum detail command.

Router# debug voip enum summary

enum_resolve_domain:match_num 5108891234 table_indx 10
enum_resolve_domain:rule 1 result string 5108891234

Table 335 provides an alphabetical listing of the debug voip enum command fields and a description of each field.

Table 335 debug voip enum Field Descriptions 

Field
Description

contact_list

Final list of URLs that the gateway will try to contact as an attempt to place the call.

flag

Flag value of a NAPTR record as defined in RFC 2915.

match_num

Number to be used for matching against the enum match table.

name

Fully qualified domain name sent out to Domain Name System (DNS) server

ns_server

Address of the DNS server. If 0, the DNS server configured on the gateway is used.

num_elem

Number of records received in the response.

order

Order in the record, as defined in RFC 2915.

pref

Preference of the record, as defined in RFC 2915.

regexp

Regular expression of the record, as defined in RFC 2915.

replacement

Replacement string of the record, as defined in RFC 2915.

re_flags_string

Flag indicating whether matching and replacement should be case sensitive:

i = Case insensitive

otherwise = Case sensitive

re_string

The first part of the regexp, delimited by "/". This is used to match the incoming string. Refer to RFC 2915.

re_substitution_string

The second part of regexp, delimited by "/".

result string

String that results when match_num is taken through the enum match table for a match. This string will be used to form a FQDN.

rule

Rule number that matched match_num in the enum match table.

search string

String sent out to the DNS server.

service

Service field of the NAPTR record. Refer to RFC 2915.

table_indx

Index of the enum match table picked for this call.

type

Type of record requested in the query:

35 = NAPTR
33 = DNS Service (SRV)


Related Commands

Command
Description

rule (ENUM configuration)

Defines the rule pattern for an ENUM match table.

show voice enum-match-table

Displays the ENUM match table rules.

test enum

Tests the ENUM match table rules.

voice enum-match-table

Initiates the ENUM match table definition.


debug voip event-log

To enable debugging of the event log module, use the debug voip event-log command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip event-log

no debug voip event-log

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(8)T

This command was introduced.


Examples

The following is sample output from the debug voip event-log command:

Router# debug voip event-log

voip event-log debugging is on
Router#
*Jul 18 22:22:45.417: voice_elog_open: ctx_id=1F, size=4, url=
*Jul 18 22:22:45.417: lock_elog, ctx_id=1F, refcnt=1
*Jul 18 22:22:45.417: voice_elog_write:
*Jul 18 22:22:45.417: elog_write_local: message (len=143) written to elog:
1F:1058566965:584:INFO: Call setup indication received, called = 4085550198, calling = 52927, echo canceller = enable, direct inward dialing 3953 bytes left
*Jul 18 22:22:45.417: voice_elog_write:
*Jul 18 22:22:45.417: elog_write_local: message (len=38) written to elog:
1F:1058566965:585:INFO: Dialpeer = 1 3915 bytes left
*Jul 18 22:22:45.421: voice_elog_open: ctx_id=B, size=4, url=
*Jul 18 22:22:45.421: lock_elog, ctx_id=B, refcnt=1
*Jul 18 22:22:45.421: voice_elog_write:
*Jul 18 22:22:45.421: elog_write_local: message (len=114) written to elog:
B:1058566965:586:INFO: Session started for App-type = generic, URL = tftp://demo/scripts/master/generic.vxml 3982 bytes left
*Jul 18 22:22:45.421: voice_elog_write:
*Jul 18 22:22:45.421: elog_write_local: message (len=69) written to elog:
B:1058566965:587:INFO: Incoming Telephony call received, LegID = 1F 3913 bytes left
*Jul 18 22:22:45.421: voice_elog_write:
*Jul 18 22:22:45.421: elog_write_local: message (len=89) written to elog:
B:1058566965:588:INFO: LegID = 1F: Calling = 4085550198, called = 52927, dial peer = 1 3824 bytes left
*Jul 18 22:22:45.421: voice_elog_write:
*Jul 18 22:22:45.421: elog_write_local: message (len=66) written to elog:
B:1058566965:589:INFO: LegID = 1F: Leg State = LEG_INCCONNECTED 3758 bytes left
*Jul 18 22:22:45.433: voice_elog_write:
*Jul 18 22:22:45.437: elog_write_local: message (len=42) written to elog:
1F:1058566965:590:INFO: Digit collection 3873 bytes left
*Jul 18 22:22:45.437: voice_elog_write:
*Jul 18 22:22:45.437: elog_write_local: message (len=57) written to elog:
1F:1058566965:591:INFO: Call connected using codec None 3816 bytes left
*Jul 18 22:22:45.437: voice_elog_write:
*Jul 18 22:22:45.437: elog_write_local: message (len=85) written to elog:
B:1058566965:592:INFO: Playing prompt #1: tftp://172.19.139.245/audio/ch_welcome.au 3673 bytes left
Router#
*Jul 18 22:22:55.942: voice_elog_write:
*Jul 18 22:22:55.942: elog_write_local: message (len=51) written to elog:
B:1058566975:593:ERR : Prompt play setup failure. 3622 bytes left
*Jul 18 22:22:55.942: voice_elog_write:
*Jul 18 22:22:55.942: elog_write_local: message (len=65) written to elog:
B:1058566975:594:INFO: Script received event = "error.badfetch" 3557 bytes left
*Jul 18 22:22:56.918: voice_elog_write:
*Jul 18 22:22:56.918: elog_write_local: message (len=98) written to elog: 1F:1058
Router#
566976:595:INFO: Inform application call disconnected (cause = normal call clearing (16)) 3718 bytes left
*Jul 18 22:22:56.918: voice_elog_write:
*Jul 18 22:22:56.918: elog_write_local: message (len=78) written to elog:
B:1058566976:596:INFO: Script received event = "telephone.disconnect.hangup"
3479 bytes left
*Jul 18 22:22:56.922: voice_elog_write:
*Jul 18 22:22:56.922: elog_write_local: message (len=89) written to elog:
B:1058566976:597:INFO: LegID = 1F: Call disconnected, cause = normal call clearing (16) 3390 bytes left
*Jul 18 22:22:56.922: voice_elog_write:
*Jul 18 22:22:56.922: elog_write_local: message (len=79) written to elog:
1F:1058566976:598:INFO: Call disconnected (cause = normal call clearing (16))
3639 bytes left
*Jul 18 22:22:56.930: voice_elog_write:
*Jul 18 22:22:56.930: elog_write_local: message (len=39) written to elog:
1F:1058566976:599:INFO: Call released
3600 bytes left
*Jul 18 22:22:56.930: voice_elog_close, ctx_id=1F voice_elog_close, ctx_id=19
*Jul 18 22:22:56.930: unlock_elog, ctx_id=19, refcnt=0
*Jul 18 22:22:56.930: delete_elog, ctx_id=19
*Jul 18 22:22:56.930: voice_elog_write:
*Jul 18 22:22:56.930: elog_write_local: message (len=59) written to elog:
B:1058566976:600:INFO: Session done, terminating cause = 3331 bytes left
*Jul 18 22:22:56.930: voice_elog_close, ctx_id=B

Related Commands

Command
Description

call application event-log

Enables event logging for voice application instances.

debug voip ais

Enables debugging of the AIS database.


debug voip hpi

To enable debugging for Host Port Interface (HPI) message events, use the debug voip hpi command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip hpi [all | command | default | detail | error [call [informational] | software [informational]] | function | inout | notification | response | stats | checker]

no debug voip hpi

Syntax Description

all

(Optional) Displays all HPI debugging messages.

command

(Optional) Displays commands that are being sent to the 54x DSP.

default

(Optional) Displays HPI detail, error, and inout debugging messages and also runs if no keywords are added.

detail

(Optional) Displays detailed information about commands for the HPI. This command is used in conjunction with other debug voip hpi commands to show additional details when you use the command, notification, and response keywords.

error

(Optional) Displays HPI error messages.

call

(Optional) Displays call processing errors.

informational

(Optional) Displays minor and major errors. Without the informational keyword, only major errors are displayed.

software

(Optional) Displays software processing errors.

function

(Optional) Displays HPI functions.

inout

(Optional) Displays the output for the command, notification, response, and stats keywords.

notification

(Optional) Displays notification messages that are sent from the 54x DSP (for example, tone detection notification).

response

(Optional) Displays responses to commands that are sent by the 54x DSP (for example, responses to statistic requests).

stats

(Optional) Displays HPI statistics.

checker

(Optional) Displays HPI checker operations.


Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(8)T

This command replaces the debug hpi command.

12.3(14)T

The checker keyword was added.


Usage Guidelines

This command enables debugging for HPI message events, which are used to communicate with digital signal processors (DSPs).

Use the debug voip hpi all command to view gateway DSP modem relay termination codes. The DSP-to-host messages for the modem relay termination indicate to the host the modem relay session termination time, physical or link layer, and other probable causes for disconnection. On receiving this indication from the DSP, the host can disconnect the call or place the channel in the modem passthrough state.

Examples

The following is sample output from the debug voip hpi all command for an incoming ISDN call:

Router# debug voip hpi all

01:28:44: //-1/xxxxxxxxxxxx/HPI/[]/hpi_dspmgr_open:

The following event shows that the HPI has identified the call, as shown by the GUID, but the call leg has not been specified, as shown by the -1 value in the CallEntry ID:

01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_dspmgr_open:
Allocated DSP resource: dsp_intf=0x64AF0EEC hpi_cdb=0x64ACED34 ret=1
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_dspmgr_open:
Exit Line # 9411
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_init:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_init:
Open channel
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_init:
Packet details:
Packet Length (16), Channel Id (1), Packet Id (74)
ALawULawSelect=A Law Associated SignalingChannel (128)
Timeslot=0 SerialPort=0
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_voice_config_params:

For each packet-related event, information about the packet is shown following the event. The following two events show the Real-Time Protocol (RTP) packet:

01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_encap_config:
RTP information
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_encap_config:
Packet details:
Packet Length (38), Channel Id (1), Packet Id (92) TransportProtocol=2
t_ssrc=0x00 r_ssrc=0x00 t_vpxcc=0x0 r_vpxcc=0x0
sid_support=0 tse_payload=101 seq_num=0x0 redundancy=0
cc_payload_type=0 fax_payload_type=0 alaw_pcm_switchover=0
mulaw_pcm_switchover=0 dtmf_payload_type=0 nte_rcv_payload_type=101
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_set_playout_config:
Packet details:
Packet Length (18), Channel Id (1), Packet Id (76)
Mode=1, Initial=60, Min=40, Max=200, fax_nom=300
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_inband_sig:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_fax_enable:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_fax_enable:
Enable FAX
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_fax_enable:
Packet details:
Packet Length (8), Channel Id (1), Packet Id (67)
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_echo_cancel:
Packet details:
Packet Length (14), Channel Id (1), Packet Id (66)
flags=0x00000B00, Threshold=-21, SuppressorCoverage=7
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_idle_code_det:
Packet details:
Packet Length (14), Channel Id (1), Packet Id (116)
Enable (FALSE), Code=0x00000000, Duration (6000 ms)
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_set_gain:
Packet details:
Packet Length (12), Channel Id (1), Packet Id (91)
Gain: In=0, Out=0
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_cng_config:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_info_field_size_config:
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_digit_relay_config:
Exit Line # 4162
01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_dspmgr_update_callid:

At this point, the HPI identifies the call leg, as shown by the CallEntry ID changing from -1 to 11.

01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_voice_get_capabilities:
Exit Line # 5073
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_stop_service:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_idle_service:
Packet details:
Packet Length (8), Channel Id (1), Packet Id (68)
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_open_service:
Setting codec g729r8
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_set_codec:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_dsprm_callback:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_voice_config_params:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_digit_relay_config:
Exit Line # 4162

The RTP packet is shown again, but now more information is available, such as payload types. The packet ID identifies this as the same RTP packet shown earlier.

01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_encap_config:
RTP information
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_encap_config:
Packet details:
Packet Length (38), Channel Id (1), Packet Id (92) TransportProtocol=2
t_ssrc=0x040 r_ssrc=0x00 t_vpxcc=0x0 r_vpxcc=0x0
sid_support=1 tse_payload=101 seq_num=0x13D3 redundancy=0
cc_payload_type=125 fax_payload_type=122 alaw_pcm_switchover=8
mulaw_pcm_switchover=0 dtmf_payload_type=121 nte_rcv_payload_type=101
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_pak_suppress:
Stop packet suppression
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_pak_suppress:
Packet details:
Packet Length (10), Channel Id (1), Packet Id (106)
Mode=1
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_vad_enable:
Packet details:
Packet Length (18), Channel Id (1), Packet Id (78)
VAD=1 (ON): Threshold=-38, VADTime=250 Aggressive=0, Noise=-62
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_init:
Open channel
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_init:
Packet details:
Packet Length (16), Channel Id (1), Packet Id (74)
ALawULawSelect=A Law Associated SignalingChannel (128)
Timeslot=0 SerialPort=0
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_voice_config_params:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_encap_config:
RTP information
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_encap_config:
Packet details:
Packet Length (38), Channel Id (1), Packet Id (92) TransportProtocol=2
t_ssrc=0x040 r_ssrc=0x00 t_vpxcc=0x0 r_vpxcc=0x0
sid_support=1 tse_payload=101 seq_num=0x13D3 redundancy=0
cc_payload_type=125 fax_payload_type=122 alaw_pcm_switchover=8
mulaw_pcm_switchover=0 dtmf_payload_type=121 nte_rcv_payload_type=101
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_set_playout_config:
Packet details:
Packet Length (18), Channel Id (1), Packet Id (76)
Mode=1, Initial=60, Min=40, Max=200, fax_nom=300
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_inband_sig:

In the following several events, fax is enabled. Packets for echo cancellation, gain, voice activity detection (VAD), and other parameters appear.

01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_fax_enable:
Enable FAX
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_fax_enable:
Packet details:
Packet Length (8), Channel Id (1), Packet Id (67)
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_echo_cancel:
Packet details:
Packet Length (14), Channel Id (1), Packet Id (66)
flags=0x00000B00, Threshold=-21, SuppressorCoverage=7
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_idle_code_det:
Packet details:
Packet Length (14), Channel Id (1), Packet Id (116)
Enable (FALSE), Code=0x00000000, Duration (6000 ms)
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_set_gain:
Packet details:
Packet Length (12), Channel Id (1), Packet Id (91)
Gain: In=0, Out=0
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_cng_config:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_info_field_size_config:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_digit_relay_config:
Exit Line # 4162
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_start_service:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_voice_mode:
Packet details:
Packet Length (28), Channel Id (1), Packet Id (73)
CodingType=20, Voice FieldSize (20), VAD Flag (250),
EchoLength=512, ComfortNoise=1, inband_detect=0x00000001,
DigitRelay=2, AGC Flag=0, ECAN TestGroup=0,
ECAN TestNumber=0, DynamicPayload=0
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_idle_code_det:
Packet details:
Packet Length (14), Channel Id (1), Packet Id (116)
Enable (FALSE), Code=0x00000000, Duration (6000 ms)
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_start_service:
Exit Line # 2816
01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_send_data_to_dsp:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_info:

Transmit and receive events are shown, along with packet information.

01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_tx:
Packet details:
Packet Length (10), Channel Id (1), Packet Id (86)
ResetFlag (0x00000000)
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_rx:
Packet details:
Packet Length (10), Channel Id (1), Packet Id (87)
ResetFlag (0x00000000)
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_pd:
Playout delay
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_pd:
Packet details:
Packet Length (10), Channel Id (1), Packet Id (83)
ResetFlag (0x00000000)
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_pe:
Playout error
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_pe:
Packet details:
Packet Length (10), Channel Id (1), Packet Id (84)
ResetFlag (0x00000000)
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_info:
Exit Line # 6578
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_message:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:

Statistics for each of the events are displayed.

01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_query_tx:
Got TX stats
Packet details:
Packet Length (36), Channel Id (1), Packet Id (199)
TX Packets (87), Signaling Packets (0) ComfortNoise Packets (0)
Transmit Duration (1750)
Voice Transmit Duration (1750), FAX Transmit Duration (0)
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_message:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_query_rx:
Got RX stats
Packet details:
Packet Length (120), Channel Id (1), Packet Id (200)
RX Packets (5): Signaling (0), ComfortNoise (1)
Receive Duration (1750): Voice (70) FAX (0)
Packet Counts: OOSequence (0), Bad header (0), Late (1), Early (0)
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_message:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_query_pd:
Got Playout Delay stats...
Packet details:
Packet Length (24), Channel Id (1), Packet Id (196)
RX Delay: CurrentEstimate=69 Low WaterMark (69) High WaterMark (70)
Clock Offset (-279863943)
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_message:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:
01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_query_pe:
Got Playout Error stats
Packet details:
Packet Length (32), Channel Id (1), Packet Id (197)
Predictive Concealment Duration (0)
Interpolative Concealment Duration (0)
Silence Concealment Duration (0)
Retroactive Memory Update (0)
Buffer overflow discard duration (10)
Talkspurt Detection Errors (0)

The following sample output from the debug voip hpi checker command helps verify the operations of the HPI checker:

Router# debug voip hpi checker

*May 19 06:30:53.532: hpi [] DSP [0/0x0] S_HPI_CLOSED(0) E_HPI_DSPRM_OPEN/SET_CODEC(54)
*May 19 06:30:53.532: hpi [] DSP [0/0x0] -> S_HPI_CLOSED(0)
*May 19 06:30:53.620: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_CLOSED(0) E_HPI_DSP_OPEN_VOICE_CHANNEL(11)
*May 19 06:30:53.620: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_IDLE(1)
*May 19 06:30:53.620: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSPRM_OPEN/SET_CODEC(54)
*May 19 06:30:53.620: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_IDLE(1)
*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSP_ENC_CONFIG(29)
*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_IDLE(1)
*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSP_SET_VOICE_PLAYOUT_DELAY(13)
*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_IDLE(1)
*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSP_IDLE_CODE_CONTROL (50)
*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_IDLE(1)

*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSP_VOICE_MODE(10)
*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GEN_PACKET_CONTROL(41)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_ECHO_CANCELLER_CONTROL(3)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_SET_GAINS(28)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_DIGIT_RELAY(22)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_VAD_ENABLE(15)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.632: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GEN_PACKET_CONTROL(41)
*May 19 06:30:53.632: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.632: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_INBAND_DETECTOR_CONTROL(45)
*May 19 06:30:53.632: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.636: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_INBAND_DETECTOR_CONTROL(45)
*May 19 06:30:53.636: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSP_VOICE_MODE(10)
*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GEN_PACKET_CONTROL(41)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_ECHO_CANCELLER_CONTROL(3)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_SET_GAINS(28)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_DIGIT_RELAY(22)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_VAD_ENABLE(15)
*May 19 06:30:53.628: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.632: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GEN_PACKET_CONTROL(41)
*May 19 06:30:53.632: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.632: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_INBAND_DETECTOR_CONTROL(45)
*May 19 06:30:53.632: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:53.636: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_INBAND_DETECTOR_CONTROL(45)
*May 19 06:30:53.636: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)

*May 19 06:30:56.512: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GET_TX_STAT(23)
*May 19 06:30:56.512: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:56.512: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GET_RX_STAT(24)
*May 19 06:30:56.512: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:56.512: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GET_VOICE_PLAYOUT_DELAY(20)
*May 19 06:30:56.512: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:56.512: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GET_VOICE_PLAYOUT_ERROR(21)
*May 19 06:30:56.512: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:59.384: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GET_TX_STAT(23)
*May 19 06:30:59.384: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:59.384: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GET_RX_STAT(24)
*May 19 06:30:59.384: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:59.384: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GET_VOICE_PLAYOUT_DELAY(20)
*May 19 06:30:59.384: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:30:59.384: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GET_VOICE_PLAYOUT_ERROR(21)
*May 19 06:30:59.384: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:31:06.524: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GEN_PACKET_CONTROL(41)
*May 19 06:31:06.524: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:31:06.532: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GET_LEVELS(26)
*May 19 06:31:06.536: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:31:06.536: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_GET_ERROR_STAT(0)
*May 19 06:31:06.536: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_VOICE(2)
*May 19 06:31:06.572: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_VOICE(2) E_HPI_DSP_IDLE_MODE(5)
*May 19 06:31:06.572: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_IDLE(1)
*May 19 06:31:06.572: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSP_CLOSE_VOICE_CHANNEL(12)
*May 19 06:31:06.572: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_CLOSED(0)
*May 19 06:31:06.576: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_CLOSED(0)
*May 19 06:31:06.576: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_CLOSED(0)

Related Commands

Command
Description

show voice hpi capture

Verifies capture status and statistics.


debug voip ipipgw

To turn on debugging for the Cisco Multiservice IP-to-IP Gateway (IPIPGW), use the debug voip ipipgw command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ipipgw

no debug voip ipipgw

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(13)T3

This command was introduced.


Examples

The following example shows debugging output from a Cisco IPIPGW:

Aug 8 15:24:30.626 EDT: cch323_build_early_fastStart_cap_response: ccb-remote_fastStart=0x63C20630
Aug 8 15:24:30.626 EDT: cch323_build_early_fastStart_cap_response:symm_mask=1,tempOtherCodec=5,templocalCodec=5,au dioFastStartArray=0x63C1299C

The following line shows fast start response beginning for the inbound leg of the IP-to-IP call:

Aug 8 15:24:30.626 EDT: cch323_build_early_fastStart_cap_response: Assuming ipipgw on inbound leg.
Aug 8 15:24:30.626 EDT: Function: cch323_build_olc_for_ccapi, Line: 1198, audioFastStartArray=0x63C1299C
Aug 8 15:24:30.626 EDT: cch323_build_olc_for_ccapi: channel_info ptr=0x63C203F0, ccb ptr=0x63C18580

The following lines indicate the inbound call leg will send the channel information to the outbound call leg (not yet created):

Aug 8 15:24:30.626 EDT: cch323_build_olc_for_ccapi: Channel Information:
Logical Channel Number (fwd/rev): 1
Channel address (fwd/rev): 0x10C0C27
RTP Channel (fwd/rev): 19362
RTCP Channel (fwd/rev): 19363
QoS Capability (fwd/rev): 0
Symmetric Audio Cap Mask: 0x1
Symmetric Audio Codec Bytes: 160
Flow Mode: 0
Silence Suppression: 0
Aug 8 15:24:30.626 EDT: cch323_build_olc_for_ccapi:NumOfElements = 1 idx = 1

The following line indicates the inbound call leg is set to work in IP-to-IP mode (0xF0):

Aug 8 15:24:30.630 EDT: cch323_set_h245_state_mc_mode_incoming: h245 state m/c mode=0xF0

The following line indicates flow mode for incoming call leg is set to FLOW_THROUGH (incoming callid = 35). At this point Session Application opens the outbound leg. Some output is omitted here.

Aug 8 15:24:30.630 EDT: cch323_media_flow_mode: IPIPGW(35):Flow Mode=1
Aug 8 15:24:30.630 EDT: cch323_set_h245_state_mc_mode_outgoing:call_spi_mode = 1

The following line indicates the outbound call leg is set to work in IP-to-IP mode (0xF0):

Aug 8 15:24:30.630 EDT: cch323_set_h245_state_mc_mode_outgoing: h245 state m/c mode=0xF0
Aug 8 15:24:30.630 EDT: cch323_get_peer_info line 1022:
Aug 8 15:24:30.630 EDT: cch323_get_peer_info line 1026:
Aug 8 15:24:30.630 EDT: cch323_set_pref_codec_list:IPIPGW(36):peer channel present: dp pref mask=FFFFFFFF
Aug 8 15:24:30.630 EDT: cch323_set_pref_codec_list:IPIPGW(36):first preferred codec(bytes)=5(160)

The following line indicates the outbound call leg is set to FLOW_THROUGH (outbound callid = 36):

Aug 8 15:24:30.630 EDT: cch323_get_peer_info: Flow Mode set to FLOW_THROUGH for callId 36
Aug 8 15:24:30.642 EDT: cch323_build_local_encoded_fastStartOLCs: state_mc_mode=0xF0 on outbound leg.
Aug 8 15:24:30.642 EDT: cch323_build_local_encoded_fastStartOLCs:srcAddress = 0x10C0C30, h245_lport = 0, flow mode = 1, minimum_qos=0
Aug 8 15:24:30.642 EDT: cch323_generic_open_logical_channel: IPIPGW: current codec = 5:160:160.

The following line indicates the IPIPGW received fast start response from the remote (called party) entity of the outbound call leg:

Aug 8 15:24:30.658 EDT: Function: cch323_receive_fastStart_cap_response Line: 2800
Aug 8 15:24:30.658 EDT: Function: cch323_build_olc_for_ccapi, Line: 1198, audioFastStartArray=0x63C1259C
Aug 8 15:24:30.658 EDT: cch323_build_olc_for_ccapi: channel_info ptr=0x63C12738, ccb ptr=0x631A4D68
Aug 8 15:24:30.658 EDT: cch323_build_olc_for_ccapi: Channel Information:
Logical Channel Number (fwd/rev): 1
Channel address (fwd/rev): 0x10C0C28
RTP Channel (fwd/rev): 19128
RTCP Channel (fwd/rev): 19129
QoS Capability (fwd/rev): 0
Symmetric Audio Cap Mask: 0x1
Symmetric Audio Codec Bytes: 160
Flow Mode: 0
Silence Suppression: 0
Aug 8 15:24:30.658 EDT: cch323_build_olc_for_ccapi:NumOfElements = 1 idx = 1
Aug 8 15:24:30.658 EDT: Function: cch323_do_open_channel_ind Line: 1080
Aug 8 15:24:30.658 EDT: Function: cch323_open_channel_ind Line: 1132

The following lines indicates the outbound call leg (36) sends the channel response back to the inbound call leg (35) via CCAPI:

Aug 8 15:24:30.658 EDT: cch323_receive_fastStart_cap_response: callID 0x24(36), audioFastStartArray = 0x0.
Aug 8 15:24:30.658 EDT: cch323_peer_channel_ind: IPIPGW:### chn info coming in chn_ind()
Aug 8 15:24:30.658 EDT: cch323_peer_channel_ind: IPIPGW(35):giving event to Fast start logic.
Aug 8 15:24:30.658 EDT: Function: cch323_do_open_channel Line: 5557
Aug 8 15:24:30.658 EDT: cch323_do_open_channel: line:5566, ccb->status=0x4000000
Aug 8 15:24:30.658 EDT: cch323_do_open_channel:srcAddress = 0x10C0C30, h245_lport = 18308, minimum_qos=0
Aug 8 15:24:30.658 EDT: cch323_build_fastStart_cap_response: Start...
Aug 8 15:24:30.658 EDT: cch323_build_fastStart_cap_response: selectCodec=5, codec_mask=1, configured_codecBytes=160
forward_codecBytes=160, reverse_codecBytes=160, audioFastStartArray=0x63C1299C
Aug 8 15:24:30.658 EDT: cch323_prepare_fastStart_cap_response line 2138
Aug 8 15:24:30.658 EDT: cch323_prepare_fastStart_cap_response: callID 0x23(35), audioFastStartArray = 0x0.
Aug 8 15:24:30.658 EDT: cch323_prepare_fastStart_cap_response, ccb->local_fastStart=0x63C183C0, srcAddr=0x10C0C30, lport=18308, rport=19362, rc=1
Aug 8 15:24:30.658 EDT: cch323_build_fastStart_cap_response: local_fastStart=0x63C183C0, negotiated_codec=5, negotiated_codec_bytes=160
Aug 8 15:24:30.658 EDT: cch323_build_fastStart_cap_response: Received peer cap info. Notify RAS state machine (possible BRQ).

Outbound leg, at this point, has prepared the fast start response to be sent to the originating (calling party). This is sent in the next outgoing call control message (such as ALERT or PROGRESS):

Aug 8 15:24:30.658 EDT: cch323_build_fastStart_cap_response: Done.
Aug 8 15:24:30.658 EDT: cch323_do_open_channel: line:5644, ccb->status=0x4004200
Aug 8 15:24:30.674 EDT: cch323_h245_connection_sm: state = 0 event=5 ccb=63C18580
Aug 8 15:24:30.674 EDT: cch323_h245_connection_sm: listen state=0
Aug 8 15:24:30.678 EDT: cch323_h245_cap_ind: IPIPGW(35): masks au=0x1 data=0xC uinp=0x32.

The following line indicates the inbound call leg (35) received capability set (CAPSET) message:

Aug 8 15:24:30.678 EDT: cch323_run_h245_cap_in_sm:IPIPGW(35): got incoming CAPSET msg.
Aug 8 15:24:30.678 EDT: cch323_do_transparent_cap_ind: IPIPGW(35):mask sent to other leg=1

The following lines show the inbound call leg (35) forwarding the TCS to the outbound leg and waiting for the response of the outbound call leg (TCSACK or TCSREJ):

Aug 8 15:24:30.678 EDT: cch323_run_h245_cap_in_sm:IPIPGW(35):suppressTCS: our TCS will be sent based on peer.
Aug 8 15:24:30.678 EDT: cch323_h245_cap_notify:IPIPGW(35):not xmiting CAPSACK: wait for peer to ack.

Aug 8 15:24:30.678 EDT: cch323_caps_ind: IPIPGW(36):setting the mask to new : current mask=0x4FFFF new mask=0x1.
Aug 8 15:24:30.678 EDT: cch323_caps_ind: IPIPGW(36): ExtendedCapsPresent
Aug 8 15:24:30.678 EDT: cch323_set_dtmf_relay_mask: IPIPGW(36): extract dtmf-caps from caps struct
Aug 8 15:24:30.678 EDT: cch323_set_dtmf_relay_mask: IPIPGW(36): After extracting dtmf-caps from caps structccb->user_caps.user_input_bit_mask[0x1C]

The following line shows the outbound leg sending the TCS to the called party. No codec filter is configured on outbound dial-peer (FFFFFFFF):


Aug 8 15:24:30.678 EDT: cch323_prepare_preferred_codec_list: IPIPGW(36):munging caps:5:1:FFFFFFFF
Aug 8 15:24:30.678 EDT: cch323_prepare_preferred_codec_list: IPIPGW(36):final mask=1
Aug 8 15:24:30.678 EDT: cch323_peer_caps_ind_common:IPIPGW(36):starting 245 via tunnel
Aug 8 15:24:30.678 EDT: cch323_h245_connection_sm: state = 0 event=1 ccb=631A4D68
Aug 8 15:24:30.678 EDT: cch323_h245_connection_sm: listen state=0
Aug 8 15:24:30.678 EDT: cch323_h245_start_cap_sm: IPIPGW(36): starting the cap/msd machine.
Aug 8 15:24:30.678 EDT: cch323_send_generic_caps: IPIPGW: audiomask raw =0x1.
Aug 8 15:24:30.678 EDT: cch323_set_pref_codec_list:IPIPGW(36):first preferred codec(bytes)=21(0)

The following line shows the outbound leg forwarding the TCS over H.225 tunnel (starting H.245 via tunnel):

Aug 8 15:24:30.678 EDT: cch323_send_generic_caps: IPIPGW:[trans]audio mask after operation=0x1.

The following lines show master-slave determination events passing from inbound to outbound and vice versa:

Aug 8 15:24:30.678 EDT: cch323_run_passthru_msd: IPIPGW(36):event = H245_EVENT_MSD
Aug 8 15:24:30.678 EDT: cch323_h245_connection_sm: state = 0 event=5 ccb=63C18580
Aug 8 15:24:30.678 EDT: cch323_h245_connection_sm: listen state=0
Aug 8 15:24:30.678 EDT: cch323_run_passthru_msd: IPIPGW(35):event = H245_EVENT_MS_IND
Aug 8 15:24:30.678 EDT: cch323_h245_connection_sm: state = 2 event=5 ccb=631A4D68
Aug 8 15:24:30.678 EDT: cch323_h245_connection_sm: listen state=0
Aug 8 15:24:30.678 EDT: cch323_h245_cap_ind: IPIPGW(36): masks au=0x1 data=0xC uinp=0x32.
Aug 8 15:24:30.678 EDT: cch323_run_h245_cap_in_sm:IPIPGW(36): got incoming CAPSET msg.
Aug 8 15:24:30.678 EDT: cch323_do_transparent_cap_ind: IPIPGW(36):mask sent to other leg=1

The following lines show the outbound leg forwarding the TCS to the other leg and waiting for its response (TCSACK or TCSREJ):

Aug 8 15:24:30.678 EDT: cch323_run_h245_cap_in_sm:IPIPGW(36):suppressTCS: our TCS will be sent based on peer.
Aug 8 15:24:30.678 EDT: cch323_h245_cap_notify:IPIPGW(36):not xmiting CAPSACK: wait for peer to ack.
Aug 8 15:24:30.678 EDT: cch323_run_passthru_msd: IPIPGW(36):event = H245_EVENT_MSD
Aug 8 15:24:30.678 EDT: cch323_caps_ind: IPIPGW(35):setting the mask to new : current mask=0x4FFFF new mask=0x1.
Aug 8 15:24:30.682 EDT: cch323_caps_ind: IPIPGW(35): ExtendedCapsPresent

Aug 8 15:24:30.682 EDT: cch323_set_dtmf_relay_mask: IPIPGW(35): extract dtmf-caps from caps struct
Aug 8 15:24:30.682 EDT: cch323_set_dtmf_relay_mask: IPIPGW(35): After extracting dtmf-caps from caps structccb->user_caps.user_input_bit_mask[0x1C]
Aug 8 15:24:30.682 EDT: cch323_prepare_preferred_codec_list: IPIPGW(35):munging caps:21:1:FFFFFFFF
Aug 8 15:24:30.682 EDT: cch323_prepare_preferred_codec_list: IPIPGW(35):final mask=1
Aug 8 15:24:30.682 EDT: cch323_peer_caps_ind_common:IPIPGW(35):starting 245 via tunnel
Aug 8 15:24:30.682 EDT: cch323_h245_connection_sm: state = 0 event=1 ccb=63C18580
Aug 8 15:24:30.682 EDT: cch323_h245_connection_sm: listen state=0
Aug 8 15:24:30.682 EDT: cch323_h245_start_cap_sm: IPIPGW(35): starting the cap/msd machine.
Aug 8 15:24:30.682 EDT: cch323_send_generic_caps: IPIPGW: audiomask raw =0x1.
Aug 8 15:24:30.682 EDT: cch323_set_pref_codec_list:IPIPGW(35):first preferred codec(bytes)=21(0)

The following line shows the inbound call leg sending the TCS to the calling party:

Aug 8 15:24:30.682 EDT: cch323_send_generic_caps: IPIPGW:[trans]audio mask after operation=0x1.
Aug 8 15:24:30.682 EDT: cch323_run_passthru_msd: IPIPGW(35):event = H245_EVENT_MSD
Aug 8 15:24:30.682 EDT: cch323_h245_connection_sm: state = 2 event=5 ccb=631A4D68
Aug 8 15:24:30.682 EDT: cch323_h245_connection_sm: listen state=0
Aug 8 15:24:30.682 EDT: cch323_run_passthru_msd: IPIPGW(36):event = H245_EVENT_MS_IND
Aug 8 15:24:30.682 EDT: cch323_h245_connection_sm: state = 2 event=5 ccb=631A4D68
Aug 8 15:24:30.682 EDT: cch323_h245_connection_sm: listen state=0
Aug 8 15:24:30.682 EDT: cch323_run_h245_cap_out_sm: IPIPGW(36): got caps ack.
Aug 8 15:24:30.682 EDT: cch323_run_h245_cap_out_sm:IPIPGW(36): sending caps ack to other leg.
Aug 8 15:24:30.682 EDT: Function: cch323_do_caps_ack Line: 1116
Aug 8 15:24:30.682 EDT: cch323_run_passthru_msd: IPIPGW(35):event = H245_EVENT_MSD
Aug 8 15:24:30.682 EDT: cch323_peer_caps_ack: IPIPGW(35):sending caps resp event to CAP state mc.
Aug 8 15:24:30.682 EDT: cch323_h245_connection_sm: state = 2 event=5 ccb=631A4D68
Aug 8 15:24:30.682 EDT: cch323_h245_connection_sm: listen state=0
Aug 8 15:24:30.682 EDT: cch323_run_passthru_msd: IPIPGW(36):event = H245_EVENT_MS_CFM
Aug 8 15:24:30.682 EDT: cch323_run_passthru_msd: IPIPGW(35):event = H245_EVENT_MS_DET_RSP

Aug 8 15:24:30.686 EDT: cch323_h245_connection_sm: state = 2 event=5 ccb=63C18580
Aug 8 15:24:30.686 EDT: cch323_h245_connection_sm: listen state=0
Aug 8 15:24:30.686 EDT: cch323_run_h245_cap_out_sm: IPIPGW(35): got caps ack.

The following line shows the inbound leg informing the outbound leg of the TCSACK:

Aug 8 15:24:30.686 EDT: cch323_run_h245_cap_out_sm:IPIPGW(35): sending caps ack to other leg.
Aug 8 15:24:30.686 EDT: Function: cch323_do_caps_ack Line: 1116
Aug 8 15:24:30.686 EDT: cch323_peer_caps_ack: IPIPGW(36):sending caps resp event to CAP state mc.
Aug 8 15:24:30.686 EDT: cch323_h245_connection_sm: state = 2 event=5 ccb=63C18580
Aug 8 15:24:30.686 EDT: cch323_h245_connection_sm: listen state=0

The following lines show that master-slave determination procedures are completed on both call legs:

Aug 8 15:24:30.686 EDT: cch323_run_passthru_msd: IPIPGW(35):event = H245_EVENT_MS_CFM
Aug 8 15:24:30.686 EDT: cch323_run_passthru_msd: IPIPGW(36):event = H245_EVENT_MS_DET_RSP


hometocprevnextglossaryfeedbacksearchhelp

Posted: Mon Jul 9 07:07:00 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.