Cisco IOS Debug Command Reference, Release 12.2 T
debug vlan packet through debug voip settlement enter

Table Of Contents

debug vlan packet

debug voice all

debug voice cp

debug voice eecm

debug voice enum

debug voice protocol

debug voice signaling

debug voice source-group

debug voice tdsm

debug voice translation

debug voice vofr

debug voip aaa

debug voip ccapi

debug voip ccapi error

debug voip ccapi inout

debug voip ccapi inout

debug voip enum

debug voip ivr

debug voip ivr all

debug voip ivr applib

debug voip ivr callsetup

debug voip ivr digitcollect

debug voip ivr dynamic

debug voip ivr error

debug voip ivr script

debug voip ivr settlement

debug voip ivr states

debug voip ivr tclcommands

debug voip rawmsg

debug voip rtcp

debug voip r1tp

debug voip settlement all

debug voip settlement enter


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 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/port argument is entered, then only debugging information for that voice port is displayed. If the slot/port is not entered, debugging information for all voice ports is displayed.


Command Modes

Privileged EXEC

Usage Guidelines

This command is valid on the Cisco MC3810 device 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 voip ccapi

Debugs the call control API.

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

debug voice tdsm

Displays debugging information for the voice tandem switch.


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/port argument is entered, then only debugging information for that voice port is displayed.


Command Modes

Privileged EXEC

Usage Guidelines

This command is valid on the Cisco MC3810 device 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 signalling.

debug voice tdsm

Displays debugging information for the voice tandem switch.


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/port is entered, then only debugging information for that voice port is displayed.


Command Modes

Privileged EXEC

Usage Guidelines

This command is valid on the Cisco MC3810 device 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 voip ccapi

Debugs the call control API.

debug voice protocol

Displays debugging information for the Voice Line protocol State machine.

debug voice signaling

Displays debugging information for the voice port signalling.

debug voice tdsm

Displays debugging information for the voice tandem switch.


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

This command is disabled by default.

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

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

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 towards 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 276 provides an alphabetical listing of the debug voice enum command fields and a description of each field.

Table 276 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 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/port number of the voice port. If the slot/port is entered, then only debugging information for that voice port is displayed.


Command Modes

Privileged EXEC

Usage Guidelines

In the debugging display, the following abbreviations are used for the different signalling 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.


Command History

This command is valid on the Cisco MC3810 device only.

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 voip ccapi

Debugs the call control API.

debug voice eecm

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

debug voice signaling

Displays debugging information for the voice port signalling.

debug voice tdsm

Displays debugging information for the voice tandem switch.


debug voice signaling

To display debugging information for the voice port signalling, 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/port argument is entered, then only debugging information for that voice port is displayed.


Usage Guidelines

This command is valid on the Cisco MC3810 device 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 voip ccapi

Debugs the call control API.

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

This command is disabled by default.

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 277 describes the significant field shown in the display.

Table 277 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 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/port argument is entered, then only debugging information for that voice port is displayed.


Usage Guidelines

This command is valid on the Cisco MC3810 device 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 voip ccapi

Debugs the call control API.

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


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

This command is disabled by default.

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

A sample output of 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 278 provides an alphabetical listing of the debug voice translation command fields and a description of each field.

Table 278 debug voice translation Field Descriptions 

Field
Description

called_number

Called number (DNIS).

called_octet

Octect3 of called IE.

calling_number

Calling number (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 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 keywords or arguments.

Defaults

This command is disabled by default.

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 of 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 ccapi

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

debug voip ccapi [error | inout]

no debug voip ccapi [error | inout]

Syntax Description

error

(Optional) Displays error logs in the CCAPI . If there are no errors, no output is displayed.

inout

(Optional) Displays the execution path through the CCAPI.


Defaults

No default behavior or values.

Command Modes

Privileged EXEC

Command History

Release
Modification

11.3(6)NA2

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660 series; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

The error keyword displays the errors in the call control application programming interface (API). Error logs are generated during normal call processing, if there are insufficient resources or problems in the underlying network-specific code, the higher call session application, or the call control API itself. This keyword shows error events or unexpected behavior in system software. In most cases, no errors are generated and nothing is displayed.

The inout keyword displays the execution path through the call control API, which serves as the interface between the call session application and the underlying network-specific software. The output from this command shows how calls are being handled by the router. This keyword shows how a call flows through the system including call setup and teardown operations performed on both the telephony and network call legs.

Examples

The following is sample output of the debug voip ccapi command without any keywords:

Router# debug voip ccapi

voip ccAPI function enter/exit debugging is on

Oct 9 17:39:20.267:cc_api_call_setup_ind (vdbPtr=0x60ED5134,  callInfo={called=3001, 
calling=4004, fdest=0 peer_tag=1}, callID=0x6104B374)
Oct 9 17:39:20.275:cc_process_call_setup_ind (event=0x60D45CF0) handed call to app "sess"
Oct 9 17:39:20.279:ccAppInitialize (name=App for callId 3, appHandle=0x6103DD44)
Oct 9 17:39:20.279:ccCallSetContext (callID=0x3, context=0x6103DD3C)
Oct 9 17:39:20.279:ccCallSetupAck (callID=0x3)
Oct 9 17:39:20.279:ccGenerateTone (callID=0x3 tone=8)
Oct 9 17:39:20.279:ccCallApp (callID=0x3)
Oct 9 17:39:20.279:ccCallSetContext (callID=0x3, context=0x60DC4594) 
00:11:31:%RADIUS-6-SERVERALIVE:Radius server 10.0.0.0 is responding again (previously 
dead.

The following is sample output that shows the call setup that it is accepted by the router:

Router# debug voip ccapi inout
!
cc_api_call_setup_ind (vdbPtr=0x60BFB530, callInfo={called=, calling=, fdest=0}, 
callID=0x60BFAEB8)
!
cc_process_call_setup_ind (event=0x60B68478) sess_appl: ev(14), cid(1), disp(0) 
ccCallSetContext (callID=0x1, context=0x60A7B094) ccCallSetPeer (callID=0x1, 
peer=0x60C0A868, voice_peer_tag=2, encapType=1, dest-pat=+14085231001, answer=) 
!
ccCallSetupAck (callID=0x1)
!
!The following output shows the caller entering DTMF digits until a dial-peer is matched.
!
cc_api_call_digit (vdbPtr=0x60BFB530, callID=0x1, digit=4, mode=0) sess_appl: ev(8), 
cid(1), disp(0) ssa: cid(1)st(0)oldst(0)cfid(-1)csize(0)in(1)fDest(0) cc_api_call_digit 
(vdbPtr=0x60BFB530, callID=0x1, digit=1, mode=0) sess_appl: ev(8), cid(1), disp(0) ssa: 
cid(1)st(0)oldst(0)cfid(-1)csize(0)in(1)fDest(0)
!

Related Commands

Command
Description

debug vtsp event

Displays the state of the gateway and the call event.

voice call debug

Debugs a voice call.


debug voip ccapi error

To trace error logs in the call control application programming interface (API), 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

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


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 API, 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.

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

Examples

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


Router# debug voip ccapi inout

cc_api_call_setup_ind (vdbPtr=0x60BFB530, callInfo={called=, calling=, fdest=0}, 
callID=0x60BFAEB8)
cc_process_call_setup_ind (event=0x60B68478)
sess_appl: ev(14), cid(1), disp(0)
ccCallSetContext (callID=0x1, context=0x60A7B094)
ccCallSetPeer (callID=0x1, peer=0x60C0A868, voice_peer_tag=2, encapType=1, 
dest-pat=+14085231001, answer=)
ccCallSetupAck (callID=0x1)

The following example shows the caller entering DTMF digits until a dial-peer is matched:


cc_api_call_digit (vdbPtr=0x60BFB530, callID=0x1, digit=4, mode=0)
sess_appl: ev(8), cid(1), disp(0)
ssa: cid(1)st(0)oldst(0)cfid(-1)csize(0)in(1)fDest(0)
cc_api_call_digit (vdbPtr=0x60BFB530, callID=0x1, digit=1, mode=0)
sess_appl: ev(8), cid(1), disp(0)
ssa: cid(1)st(0)oldst(0)cfid(-1)csize(0)in(1)fDest(0)
cc_api_call_digit (vdbPtr=0x60BFB530, callID=0x1, digit=0, mode=0)
sess_appl: ev(8), cid(1), disp(0)
ssa: cid(1)st(0)oldst(0)cfid(-1)csize(0)in(1)fDest(0)
cc_api_call_digit (vdbPtr=0x60BFB530, callID=0x1, digit=0, mode=0)
sess_appl: ev(8), cid(1), disp(0)
ssa: cid(1)st(0)oldst(0)cfid(-1)csize(0)in(1)fDest(0)
cc_api_call_digit (vdbPtr=0x60BFB530, callID=0x1, digit=1, mode=0)
sess_appl: ev(8), cid(1), disp(0)
ssa: cid(1)st(0)oldst(0)cfid(-1)csize(0)in(1)fDest(0)
ccCallProceeding (callID=0x1, prog_ind=0x0)
ssaSetupPeer cid(1), destPat(+14085241001), matched(8), prefix(), peer(60C0E710)

The following example shows the call setup over the IP network to the remote router:


ccCallSetupRequest (peer=0x60C0E710, dest=, params=0x60A7B0A8 mode=0, *callID=0x60B6C110)
ccIFCallSetupRequest: (vdbPtr=0x60B6C5D4, dest=, callParams={called=+14085241001, 
calling=+14085231001, fdest=0, voice_peer_tag=104}, mode=0x0)
ccCallSetContext (callID=0x2, context=0x60A7B2A8)

The following example shows the called party is alerted, a CODEC is negotiated, and voice path is cut through:


cc_api_call_alert(vdbPtr=0x60B6C5D4, callID=0x2, prog_ind=0x8, sig_ind=0x1)
sess_appl: ev(6), cid(2), disp(0)
ssa: cid(2)st(1)oldst(0)cfid(-1)csize(0)in(0)fDest(0)-cid2(1)st2(1)oldst2(0)
ccCallAlert (callID=0x1, prog_ind=0x8, sig_ind=0x1)
ccConferenceCreate (confID=0x60B6C150, callID1=0x1, callID2=0x2, tag=0x0)
cc_api_bridge_done (confID=0x1, srcIF=0x60B6C5D4, srcCallID=0x2, dstCallID=0x1, 
disposition=0, tag=0x0)
cc_api_bridge_done (confID=0x1, srcIF=0x60BFB530, srcCallID=0x1, dstCallID=0x2, 
disposition=0, tag=0x0)
cc_api_caps_ind (dstVdbPtr=0x60B6C5D4, dstCallId=0x2,srcCallId=0x1, caps={codec=0x7, 
fax_rate=0x7F, vad=0x3})
cc_api_caps_ind (dstVdbPtr=0x60BFB530, dstCallId=0x1,srcCallId=0x2, caps={codec=0x4, 
fax_rate=0x2, vad=0x2})
cc_api_caps_ack (dstVdbPtr=0x60BFB530, dstCallId=0x1,srcCallId=0x2, caps={codec=0x4, 
fax_rate=0x2, vad=0x2})
cc_api_caps_ack (dstVdbPtr=0x60B6C5D4, dstCallId=0x2,srcCallId=0x1, caps={codec=0x4, 
fax_rate=0x2, vad=0x2})
sess_appl: ev(17), cid(1), disp(0)
ssa: cid(1)st(3)oldst(0)cfid(1)csize(0)in(1)fDest(0)-cid2(2)st2(3)oldst2(1)

The following example shows that the call is connected and voice is active:


cc_api_call_connected(vdbPtr=0x60B6C5D4, callID=0x2)
sess_appl: ev(7), cid(2), disp(0)
ssa: cid(2)st(4)oldst(1)cfid(1)csize(0)in(0)fDest(0)-cid2(1)st2(4)oldst2(3)
ccCallConnect (callID=0x1)

The following example shows how the system processes voice statistics and monitors voice quality during the call:


ccapi_request_rt_packet_stats (requestorIF=0x60B6C5D4, requestorCID=0x2,
   requestedCID=0x1, tag=0x60A7C598)
cc_api_request_rt_packet_stats_done (requestedIF=0x60BFB530, requestedCID=0x1,
   tag=0x60A7A4C4)
ccapi_request_rt_packet_stats (requestorIF=0x60B6C5D4, requestorCID=0x2,
   requestedCID=0x1, tag=0x60A7C598)
cc_api_request_rt_packet_stats_done (requestedIF=0x60BFB530, requestedCID=0x1,
   tag=0x60C1FE54)
ccapi_request_rt_packet_stats (requestorIF=0x60B6C5D4, requestorCID=0x2,
   requestedCID=0x1, tag=0x60A7C598)
cc_api_request_rt_packet_stats_done (requestedIF=0x60BFB530, requestedCID=0x1,
   tag=0x60A7A5F4)
ccapi_request_rt_packet_stats (requestorIF=0x60B6C5D4, requestorCID=0x2,
   requestedCID=0x1, tag=0x60A7C598)
cc_api_request_rt_packet_stats_done (requestedIF=0x60BFB530, requestedCID=0x1,
   tag=0x60A7A6D8)
ccapi_request_rt_packet_stats (requestorIF=0x60B6C5D4, requestorCID=0x2,
   requestedCID=0x1, tag=0x60A7C598)
cc_api_request_rt_packet_stats_done (requestedIF=0x60BFB530, requestedCID=0x1,
   tag=0x60A7ACBC)

The following example shows that disconnection is indicated from the calling party, call legs are torn down and disconnected:


cc_api_call_disconnected(vdbPtr=0x60BFB530, callID=0x1, cause=0x10)
sess_appl: ev(9), cid(1), disp(0)
ssa: cid(1)st(5)oldst(3)cfid(1)csize(0)in(1)fDest(0)-cid2(2)st2(5)oldst2(4)
ccConferenceDestroy (confID=0x1, tag=0x0)
cc_api_bridge_done (confID=0x1, srcIF=0x60B6C5D4, srcCallID=0x2, dstCallID=0x1, 
disposition=0 tag=0x0)
cc_api_bridge_done (confID=0x1, srcIF=0x60BFB530, srcCallID=0x1, dstCallID=0x2, 
disposition=0 tag=0x0)
sess_appl: ev(18), cid(1), disp(0)
ssa: cid(1)st(6)oldst(5)cfid(-1)csize(0)in(1)fDest(0)-cid2(2)st2(6)oldst2(4)
ccCallDisconnect (callID=0x1, cause=0x10 tag=0x0)
ccCallDisconnect (callID=0x2, cause=0x10 tag=0x0)
cc_api_call_disconnect_done(vdbPtr=0x60B6C5D4, callID=0x2, disp=0, tag=0x0)
sess_appl: ev(10), cid(2), disp(0)
ssa: cid(2)st(7)oldst(4)cfid(-1)csize(0)in(0)fDest(0)-cid2(1)st2(7)oldst2(6)
cc_api_call_disconnect_done(vdbPtr=0x60BFB530, callID=0x1, disp=0, tag=0x0)
sess_appl: ev(10), cid(1), disp(0)
ssa: cid(1)st(7)oldst(6)cfid(-1)csize(1)in(1)fDest(0)

debug voip ccapi inout

To trace the execution path through the call control application programming interface (API), 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

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


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: usrCo
ntainer[0x638C1BF0], magic[FACE0FFF]
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilAddDataToUsrContainer: con
tainer=0x638C1BF0, tagID=6, dataSize=16, instID=-1,modifier=1
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject: tdO
bject[0x638BC1AC], nxtElem[0x0], magic[0xFACE0FFF] tagID[6], dataLen[16], modif[
1]
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToContainer: Addin
g tdObject[0x638BC1AC] instID[-1] into container[0x638C1BF0]
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilAddDataToUsrContainer: con
tainer=0x638C1BF0, tagID=5, dataSize=276, instID=-1,modifier=1
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject: tdO
bject[0x63401148], nxtElem[0x0], magic[0xFACE0FFF] tagID[5], dataLen[276], modif
[1]
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToContainer: Addin
g 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=0x6
37EC1E0, 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_labe
l= 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 , p
rot 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 ca
ll 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 inco
ming 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: profi
leTable[0x6380E11C], numBuckets[11], numEntries[0]
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtProfileTableBuildManager: I
nvoking necessary profileTable updaters...
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContain
er: Updating profileTable[0x6380E11C] with objects in container[0x638C1BF0]
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContain
er: obtained key[5] for the tag[6]
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToProfileBucket: p
rofileTable[0x6380E11C], tdObject[0x638BC1AC]
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContain
er: obtained key[0] for the tag[5]
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToProfileBucket: p
rofileTable[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: Contai
ner[0x638C1BF0]
*Mar  1 15:35:53.604: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: not the Vo
IP 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: >>>>CCA
PI 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_SE
TUP_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 rout
e label=, tgt route label= tg_label_flag 0x0
*Mar  1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: finalDes
t 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 ta
gs 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,c
alling_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 la
bel tg_label_flag 0x0
*Mar  1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:  vdbP
tr type = 1
*Mar  1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
*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,  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 inco
ming 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, d
ialpeer_tag=10001)
*Mar  1 15:35:53.624: //45/xxxxxxxxxxxx/CCAPI/ccCallSetContext: (callID=0x2D, co
ntext=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: (v
dbPtr=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: ssaReportD
igitsDone 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=0
x10082
*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 E
thernet0/0 
*Mar  1 15:35:53.632: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: create ent
ry 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/ccTDPvtProfileTableObjectAccessMan
ager: No profileTable set for callID[45]
*Mar  1 15:35:53.636: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetInstanceCount: For tagI
D[2] of callID[45]
*Mar  1 15:35:53.636: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessMan
ager: 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=0x
62EC61A4, callID=0x2D,
      prog_ind=0x0) 
*Mar  1 15:35:53.740: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_alert: (vdbPtr=0x62EC6
1A4, 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_A
LERT), 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_in
d=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 cal
lEntry->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_C
ONNECTED), 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(SS
A_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: ssaFlushPe
erTagQueue cid(44) peer list: tag(20002) called number (34999)
*Mar  1 15:36:05.028: //-1/xxxxxxxxxxxx/CCAPI/cc_process_notify_bridge_done: (ev
ent=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=0x
2C
*Mar  1 15:36:05.032: //44/45F2AAE28044/CCAPI/cc_api_voice_mode_event: Call Poin
ter =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: (dstVdbPt
r=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), dig
it_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), dig
it_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 - 0x628B6
330
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(SS
A_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, ca
use=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 accounti
ng 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, ca
use=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 accounti
ng 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 existi
ng_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 E
thernet0/0
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: reduce cal
lnum 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: (vdbP
tr=0x62EC61A4, callID=0x2D, disp=0, tag=0x0)
*Mar  1 15:36:22.932: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessMan
ager: 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 inco
ming 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: accou
nting generation enabled
*Mar  1 15:36:22.940: //45/xxxxxxxxxxxx/CCAPI/ccCallSetAAA_Accounting: callID=0x
2D, accounting=0
*Mar  1 15:36:22.944: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: not the Vo
IP or MMoIP
*Mar  1 15:36:22.948: //44/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnect_done: (vdbP
tr=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 ca
ll 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 inco
ming 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 pro
fileTable[0x6380E11C]
*Mar  1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructTDHashProfileTab: Dest
ructor Profile Table (0x6380E11C)
*Mar  1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructInstanceTDObject: tdOb
ject[0x63401148] tagID[5]
*Mar  1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructInstanceTDObject: tdOb
ject[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(SS
A_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 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

This command is disabled by default.

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

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

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 towards 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 279 provides an alphabetical listing of the debug voip enum command fields and a description of each field.

Table 279 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 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 ivr

To display debug messages for Voice over IP (VoIP) interactive voice response (IVR) interactions, use the debug voip ivr command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr type

no debug voip ivr type

Syntax Description

type

Type of debug messages. The keywords are as follows:

all—(Optional) Displays debug messages for all types.

applib—(Optional) Displays application programming interface (API) libraries being processed.

callsetup—(Optional) Displays call setup being processed.

digitcollect—(Optional) Displays digits collected during the call.

dynamic—(Optional) Displays dynamic prompt play debug.

error—(Optional) Displays errors.

script—(Optional) Displays script debug.

settlement—(Optional) Displays settlement activities.

states—(Optional) Displays states.

tclcommands—(Optional) Displays the Tool Command Language (TCL) commands used in the script.


Defaults

This command is disabled by default.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660 series; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following access servers: Cisco AS5300, and Cisco AS5800; and on the Cisco MC3810 multiservice access concentrators.


Examples

The following is sample output that is displayed when the debug voip ivr command is entered with the applib keyword:

Router# debug voip ivr applib 

ivr:
 ivr app library debugging is on
!
Jan 10 17:42:04.180:AppManagerCCAPI_Interface:
Jan 10 17:42:04.180:AppNewLeg
Jan 10 17:42:04.180:AppPushLegORConnection:Pushing LEG[34   ][NULL
] Onto {HAN[TCL_HAND][NULL  ]   ( )}
Jan 10 17:42:04.180:Event CC_EV_CALL_SETUP_IND[29]:LEG[34
][TCL_HAND]
Jan 10 17:42:04.184:AppPushHandler:Pushing {HAN[DC_HAND ][NULL  ]
( )} Onto {HAN[TCL_HAND][NULL  ]   ( LEG[34   ][TCL_HAND] )}
Jan 10 17:42:04.184:AppPushLegORConnection:Pushing LEG[34
][TCL_HAND] Onto {HAN[DC_HAND ][TCL_HAND]   ( )}
Jan 10 17:42:04.184:$ mediaPlay():CallID 34
Jan 10 17:42:04.184:Event CC_EV_CALL_REPORT_DIGITS_DONE[45]:LEG[34
][DC_HAND ]
Jan 10 17:42:17.261:AppMediaCallback:CallID 34 received
           response 'MSW_RESPONSE_TYPE_PLAY'
           with reason 'MSW_REASON_GENERIC_SUCCESS'
Jan 10 17:42:17.261:Event APP_EV_MEDIA_CALLBACK[47]:LEG[34
][DC_HAND ]
Jan 10 17:42:18.209:%ISDN-6-DISCONNECT:Interface Serial0:0
disconnected from unknown , call lasted 13 seconds

The following is sample output when the debug voip ivr command is entered with the callsetup keyword:

Router# debug voip ivr callsetup
!
Jan 10 17:45:57.528:%SYS-5-CONFIG_I:Configured from console by lab on console
Jan 10 17:46:37.682:InitiateCallSetup:Incoming[66] AlertTime -1
Destinations(1) [ 3450070 ]
Jan 10 17:46:37.682:DNInitiate:Destination[3450070]
Jan 10 17:46:37.682:DNSetupPeer:
Jan 10 17:46:37.682:Destination SetupPeer cid(66), destPat(3450070),
match(2), prefix(), peer(61CB5CAC)
Jan 10 17:46:37.762:DNHandler:
(DN_SETTING[1])--(CC_EV_CALL_ALERT[11])--IGNORED-->>(DN_SETTING[1])
Jan 10 17:46:37.762:CS_Setting_ALERT:
Jan 10 17:46:37.762:CSPopLegAndWait:
Jan 10 17:46:37.762:CallSetupHandler:
 (CS_SETTING[0]) -----(CS_EV_ALERT[0])------->>>(CS_CONFINGALERT[4])
Jan 10 17:46:37.762:CS_ConfingAlert_CREATEDONE:
Jan 10 17:46:37.762:CallSetupHandler:
 (CS_CONFINGALERT[4])
-----(CS_EV_CREATEDONE[4])------->>>(CS_CONFEDALERT[5])
Jan 10 17:46:37.762:CallSetupHandler:
 (CS_CONFEDALERT[5])--(DN_SETTING[APP_EV_NULL])--IGNORED-->>>(CS_CONFEDALERT[5])
!
Jan 10 17:46:47.682:CallSetupHandler:
 (CS_CONFEDALERT[5])--(DN_SETTING[APP_EV_NULL])--IGNORED-->>>(CS_CONFEDALERT[5])
Jan 10 17:46:48.642:CS_ConfedAlert_CONNECTED:
Jan 10 17:46:48.642:CSDiscReturnAndEmptyLegALL:
Jan 10 17:46:48.642:DNCleanup:
Jan 10 17:46:48.642:DNSettlementCleanup:cid(66) trans=0, provider=0
Jan 10 17:46:48.642:CSReturnIFDone:CallSetup Returning(Status
CS_ACTIVE)
Jan 10 17:46:48.642:CallSetupHandler:
 (CS_CONFEDALERT[5]) -----(CS_EV_CONNECTED[1])------->>>(CS_CONFED[3])
Jan 10 17:46:48.646:CallSetupCleanup:
!

The following is sample output when the debug voip ivr command is entered with the digitcollect keyword:

Router# debug voip ivr digitcollect

ivr:
 ivr digit collect debugging is on
!
Jan 10 17:47:55.558:DigitCollect:DialPlan=FALSE AbortKey=* TermKey=#
NumPatts=1
       Enable=FALSE InterruptPrompt=TRUE maxDigits=11
Jan 10 17:47:55.558:act_DCRunning_RDone:callid=68 Enable succeeded.
!
Jan 10 17:48:04.006:DCHandlerFunc:PassingThrough
Jan 10 17:48:04.066:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:04.066:act_DCRunning_RDone:callid=68 Reporting disabled.
Jan 10 17:48:04.066:DigitCollectComplete:Status 5=DC_MATCHED_PATTERN.
Digits=1
Jan 10 17:48:04.070:DigitCollect:DialPlan=FALSE AbortKey=* TermKey=#
NumPatts=0
       Enable=FALSE InterruptPrompt=TRUE maxDigits=11
Jan 10 17:48:04.070:DCHandlerCleanup:
Jan 10 17:48:04.074:act_DCRunning_RDone:callid=68 Enable succeeded.
!
Jan 10 17:48:08.038:DCHandlerFunc:PassingThrough
Jan 10 17:48:09.246:DCHandlerFunc:PassingThrough
Jan 10 17:48:09.286:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:09.478:DCHandlerFunc:PassingThrough
Jan 10 17:48:09.506:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:10.739:DCHandlerFunc:PassingThrough
Jan 10 17:48:10.779:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:11.027:DCHandlerFunc:PassingThrough
Jan 10 17:48:11.067:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:11.687:DCHandlerFunc:PassingThrough
Jan 10 17:48:11.747:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:12.219:DCHandlerFunc:PassingThrough
Jan 10 17:48:12.279:act_DCRunning_Digit::pLeg 68 Digit 2
Jan 10 17:48:14.227:DCHandlerFunc:PassingThrough
Jan 10 17:48:14.287:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:14.779:DCHandlerFunc:PassingThrough
Jan 10 17:48:14.859:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:15.307:DCHandlerFunc:PassingThrough
Jan 10 17:48:15.359:act_DCRunning_Digit::pLeg 68 Digit 1
Jan 10 17:48:15.719:DCHandlerFunc:PassingThrough
Jan 10 17:48:15.759:act_DCRunning_Digit::pLeg 68 Digit 2
Jan 10 17:48:16.219:DCHandlerFunc:PassingThrough
Jan 10 17:48:16.299:act_DCRunning_Digit::pLeg 68 Digit T
Jan 10 17:48:16.299:act_DCRunning_RDone:callid=68 Reporting disabled.
Jan 10 17:48:16.299:DigitCollectComplete:Status 5=DC_MATCHED_PATTERN.
Digits=1111121112
Jan 10 17:48:16.303:DCHandlerCleanup:
Jan 10 17:48:16.335:DigitCollect:DialPlan=TRUE AbortKey=* TermKey=#
NumPatts=0
       Enable=FALSE InterruptPrompt=TRUE maxDigits=0
Jan 10 17:48:16.339:act_DCRunning_RDone:callid=68 Enable succeeded.

The following is sample output when the debug voip ivr command is entered with the script keyword:

Router# debug voip ivr script

ivr:
 ivr script debugging is on
!
Jan 10 17:49:10.250:FSM Transtion:([1
]CALL_INIT,[29]ev_setup_indication)---([10]act_Setup)--->([4
]LANGSELECTION)
Jan 10 17:49:10.250:TotalLanguages= 2
!
Jan 10 17:49:16.662:FSM Transtion:([4
]LANGSELECTION,[55]ev_digitcollect_done)---([1 ]act_LangSelect)--->([5
]CARDSELECTION)
!
Jan 10 17:49:20.630:([5 ]CARDSELECT,[47]ev_media_d) ------> NOTHANDLED
Jan 10 17:49:26.770:FSM Transtion:([5
]CARDSELECTION,[55]ev_digitcollect_done)---([2
]act_GotCardNumber)--->([6 ]AUTHORIZE)
Jan 10 17:49:26.806:FSM Transtion:([6
]AUTHORIZE,[49]ev_authorize_done)---([8 ]act_FirstAuthorized)--->([7
]GETDEST)
Jan 10 17:49:26.806: aaa authorize Status=ao_000
!
Jan 10 17:49:33.395:([7 ]GETDEST  ,[47]ev_media_d) ------> NOTHANDLED
Jan 10 17:49:36.411:FSM Transtion:([7
]GETDEST,[55]ev_digitcollect_done)---([3 ]act_GotDest)--->([8
]SECONDAUTHORIZE)
Jan 10 17:49:36.451:FSM Transtion:([8
]SECONDAUTHORIZE,[49]ev_authorize_done)---([5
]act_SecondAuthorized)--->([10]PLACECALL)
Jan 10 17:49:36.451: aaa authorize Status=ao_000
Jan 10 17:49:42.179:FSM Transtion:
([10]PLACECALL,[47]ev_media_done)---([9
]act_CallSetup)--->([10]PLACECALL)

The following is sample output when the debug voip ivr command is entered with the tclcommands keyword:

Router# debug voip ivr tclcommands

ivr tcl commands debugging is on
Jan 10 17:50:29.106:tcl_infotagCmd:infotag get leg_ani
Jan 10 17:50:29.106:tcl_getInfoCmd:get leg_ani
Jan 10 17:50:29.106:vtr_ci_incani:argc 2 argindex 2
Jan 10 17:50:29.106:tcl_infotagCmd:infotag set med_language 1
Jan 10 17:50:29.106:tcl_setInfoCmd:set med_language 1
Jan 10 17:50:29.106:vtw_ms_language:
Jan 10 17:50:29.106:tcl_legCmd:leg setupack leg_incoming
Jan 10 17:50:29.106:tcl_setupAckCmd:setupack leg_incoming
Jan 10 17:50:29.106:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:29.106:tcl_legCmd:leg proceeding leg_incoming
Jan 10 17:50:29.106:tcl_callProceedingCmd:proceeding leg_incoming
Jan 10 17:50:29.106:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:29.110:tcl_legCmd:leg connect leg_incoming
Jan 10 17:50:29.110:tcl_callConnectCmd:connect leg_incoming
Jan 10 17:50:29.110:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:29.110:tcl_legCmd:leg collectdigits leg_incoming param1
patterns
Jan 10 17:50:29.110:tcl_collectDigitsCmd:collectdigits leg_incoming
param1 patterns
Jan 10 17:50:29.110:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:29.110:tcl_mediaCmd:media play leg_incoming _welcome.au
%s1000 %c1 _lang_sel1.au %s1000 %c2 _lang_sel2.au
Jan 10 17:50:29.110:tcl_mediaPlayCmd:play leg_incoming _welcome.au
%s1000 %c1 _lang_sel1.au %s1000 %c2 _lang_sel2.au
Jan 10 17:50:29.110:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
!
Jan 10 17:50:35.506:tcl_infotagCmd:infotag get evt_status
Jan 10 17:50:35.506:tcl_getInfoCmd:get evt_status
Jan 10 17:50:35.506:vtr_ev_status:
Jan 10 17:50:35.510:tcl_infotagCmd:infotag get evt_dcdigits
Jan 10 17:50:35.510:tcl_getInfoCmd:get evt_dcdigits
Jan 10 17:50:35.510:vtr_ev_dcdigits:
Jan 10 17:50:35.510:DCDIGITS [1]
Jan 10 17:50:35.510:tcl_infotagCmd:infotag set med_language 1
Jan 10 17:50:35.510:tcl_setInfoCmd:set med_language 1
Jan 10 17:50:35.510:vtw_ms_language:
Jan 10 17:50:35.510:tcl_legCmd:leg collectdigits leg_incoming param1
Jan 10 17:50:35.510:tcl_collectDigitsCmd:collectdigits leg_incoming
param1
Jan 10 17:50:35.510:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:35.510:tcl_mediaCmd:media play leg_incoming
_enter_card_num.au
Jan 10 17:50:35.510:tcl_mediaPlayCmd:play leg_incoming
_enter_card_num.au
Jan 10 17:50:35.514:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
!
Jan 10 17:50:43.878:tcl_infotagCmd:infotag get evt_status
Jan 10 17:50:43.878:tcl_getInfoCmd:get evt_status
Jan 10 17:50:43.878:vtr_ev_status:
Jan 10 17:50:43.882:tcl_infotagCmd:infotag get evt_dcdigits
Jan 10 17:50:43.882:tcl_getInfoCmd:get evt_dcdigits
Jan 10 17:50:43.882:vtr_ev_dcdigits:
Jan 10 17:50:43.882:DCDIGITS [1111121112]
Jan 10 17:50:43.882:tcl_aaaCmd:aaa authorize 111112 1112 50073
leg_incoming
Jan 10 17:50:43.882:tcl_AuthorizeCmd:authorize 111112 1112 50073
leg_incoming
Jan 10 17:50:43.882:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:43.882:Authorize
Jan 10 17:50:43.882:  account=111112
Jan 10 17:50:43.882:  password=1112
Jan 10 17:50:43.882:  ani   =50073
Jan 10 17:50:43.882:  dnis  =
Jan 10 17:50:43.910:tcl_infotagCmd:infotag get evt_status
Jan 10 17:50:43.910:tcl_getInfoCmd:get evt_status
Jan 10 17:50:43.910:vtr_ev_status:
Jan 10 17:50:43.914:tcl_infotagCmd:infotag get aaa_avpair_exists
creditAmount
Jan 10 17:50:43.914:tcl_getInfoCmd:get aaa_avpair_exists creditAmount
Jan 10 17:50:43.914:vtr_ra_avpair_exists:
Jan 10 17:50:43.914:tcl_infotagCmd:infotag get aaa_avpair creditAmount
Jan 10 17:50:43.914:tcl_getInfoCmd:get aaa_avpair creditAmount
Jan 10 17:50:43.914:vtr_ra_avpair:
Jan 10 17:50:43.914:tcl_legCmd:leg collectdigits leg_incoming param2
Jan 10 17:50:43.914:tcl_collectDigitsCmd:collectdigits leg_incoming
param2
Jan 10 17:50:43.914:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1
Jan 10 17:50:43.914:tcl_mediaCmd:media play leg_incoming _you_have.au
%a1000 %s1000 _enter_dest.au
Jan 10 17:50:43.914:tcl_mediaPlayCmd:play leg_incoming _you_have.au
%a1000 %s1000 _enter_dest.au
Jan 10 17:50:43.918:vtd_lg_incoming:Legs [71 ]VARTAG Translation Leg
Count=1

debug voip ivr all

To display both states and error debugging messages for interactive voice response (IVR) interactions, use the debug voip ivr all command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr all

no debug voip ivr all

Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

We recommend that you log output from the debug voip ivr all 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 debugging output for the debug voip ivr all command. The show debug command shows all of the enabled IVR debugging traces.

Router# debug voip ivr all 

All ivr debugging is on

Router#
Router#show debug

ivr:
  ivr errors debugging is on
  ivr state transitions debugging is on
  ivr settlement activities debugging is on
  ivr dynamic promptplaying debugging is on
  ivr script debugging is on
  ivr app library debugging is on
  ivr tcl commands debugging is on
  ivr digit collect debugging is on
  ivr call setup debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 03:15:57.831: //170/90241C6380DD/APPL:/AppManagerCCAPI_Interface:
*Mar 11 03:15:57.831: //-1//TCL2:/TclGetInterp: Script test
*Mar 11 03:15:57.831: //-1//APPL:/AppNewLeg:
*Mar 11 03:15:57.831: //-1//APPL:/AppSaveRawMsg:
*Mar 11 03:15:57.831: //170//APPL:LP:HN34330144:/AppPushLegORConnection: Pushing LEG[170    
][NULL    ][LEG_INCINIT(1)][
Cause(0)][UC=1 ] Onto {HAN[TCL_HAND][NULL    ]  ( )}
*Mar 11 03:15:57.835: //170//APPL:/AppProcessEvent: Event CC_EV_CALL_SETUP_IND[28]:
*Mar 11 03:15:57.835: //170//APPL:/AppProcessEvent: LEG[170    
][TCL_HAND][LEG_INCINIT(1)][Cause(0)][UC=1 ]
*Mar 11 03:15:57.835: //170//TCL2:/TclInterpHandler: CC_EV_CALL_SETUP_IND
*Mar 11 03:15:57.835: //170//TCL2:/TclInterpDriver:
*Mar 11 03:15:57.835: //170//TCL2:/TclEventPreprocessing:
*Mar 11 03:15:57.835: //-1//TCL2:/TclIncomingCallBlock:
*Mar 11 03:15:57.835: //170//TCL2:/SettlementValidateCall: target=, tokenp=0x0
*Mar 11 03:15:57.835: //170//TCL2:/MakeTransition: FSM Transtion: ([1 
]CALL_INIT,[28]ev_setup_indication)---([10]act_Set
up)--->([7 ]AUTHENTICATE)
*Mar 11 03:15:57.835: //170//TCL2:/tcl_legCmd: leg setupack leg_incoming
*Mar 11 03:15:57.835: //170//TCL2:/tcl_setupAckCmd: setupack leg_incoming
*Mar 11 03:15:57.835: //170//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 03:15:57.835: //170//TCL2:/vtd_lg_incoming: Legs [170 ]
*Mar 11 03:15:57.835: //170//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 03:15:57.839: //170//TCL2:/tcl_legCmd: leg proceeding leg_incoming
*Mar 11 03:15:57.839: //170//TCL2:/tcl_callProceedingCmd: proceeding leg_incoming
*Mar 11 03:15:57.839: //170//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 03:15:57.839: //170//TCL2:/vtd_lg_incoming: Legs [170 ]
*Mar 11 03:15:57.839: //170//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 03:15:57.839: //170//TCL2:/tcl_legCmd: leg connect leg_incoming
*Mar 11 03:15:57.839: //170//TCL2:/tcl_callConnectCmd: connect leg_incoming
*Mar 11 03:15:57.839: //170//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 03:15:57.839: //170//TCL2:/vtd_lg_incoming: Legs [170 ]
*Mar 11 03:15:57.839: //170//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 03:15:57.839: //170//TCL2:/tcl_infotagCmd: infotag get leg_ani
*Mar 11 03:15:57.839: //170//TCL2:/tcl_getInfoCmd: get leg_ani
*Mar 11 03:15:57.843: //170//TCL2:/vtr_lg_incani: argc 2 argindex 2
*Mar 11 03:15:57.843: //170//TCL2:/tcl_aaaCmd: aaa authenticate 300
*Mar 11 03:15:57.843: //170//TCL2:/tcl_AuthenticateCmd: authenticate 300
*Mar 11 03:15:57.843: //170//TCL2:/tcl_AuthenticateCmd: account=300, password=, 
methodList=, av-send=
*Mar 11 03:15:57.851: //-1//APPL:HN34330144:/AppProcessEvent: Event 
APP_EV_AUTHENTICATE_DONE[81]:
*Mar 11 03:15:57.851: //-1//APPL:HN34330144:/AppProcessEvent: HAN[TCL_HAN][NULL    
][FALSE] [UC=1 ]
*Mar 11 03:15:57.851: //-1//TCL2:HN34330144:/TclInterpHandler: APP_EV_AUTHENTICATE_DONE
*Mar 11 03:15:57.851: //-1//TCL2:HN34330144:/TclInterpDriver:
*Mar 11 03:15:57.851: //-1//TCL2:HN34330144:/TclEventPreprocessing:
*Mar 11 03:15:57.851: //-1//TCL2:HN34330144:/TclEventPreprocessing:
*Mar 11 03:15:57.851: TclEventPreprocessing: app_event->e.evAuthenticateDone.status = 0
*Mar 11 03:15:57.851: //-1//TCL2:HN34330144:/TclEventPreprocessing:
*Mar 11 03:15:57.851: TclEventPreprocessing: lastFailureCause = 0

Table 280 describes the significant fields shown in the display.

Table 280 debug voip ivr all Field Descriptions

Field
Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//170/

Identifies the CallEntry ID.

APPL:HN34330144:

Identifies the application.

TCL2:

Identifies the TCL IVR 2 module.


Related Commands

Command
Description

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.


debug voip ivr applib

To display debugging messages for interactive voice response (IVR) application programming interface (API) libraries being processed, use the debug voip ivr applib command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr applib

no debug voip ivr applib

Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

We recommend that you log output from the debug voip ivr applib 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 debugging output for the debug voip ivr applib command:

Router# debug voip ivr applib 

ivr app library debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 00:36:20.356: //91/43855ACF809E/APPL:/AppManagerCCAPI_Interface:
*Mar 11 00:36:20.356: //-1//APPL:/AppNewLeg:
*Mar 11 00:36:20.356: //-1//APPL:/AppSaveRawMsg:
*Mar 11 00:36:20.356: //91//APPL:LP:HN33A0DD40:/AppPushLegORConnection: Pushing LEG[91     
][NULL    
][LEG_INCINIT(1)][Cause(0)][UC=1 ] Onto {HAN[TCL_HAND][NULL    ]   ( )}
*Mar 11 00:36:20.356: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_SETUP_IND[28]:
*Mar 11 00:36:20.356: //91//APPL:/AppProcessEvent: LEG[91     
][TCL_HAND][LEG_INCINIT(1)][Cause(0)][UC=1 ]
*Mar 11 00:36:20.368: //-1//APPL:HN33A0DD40:/AppProcessEvent: Event 
APP_EV_AUTHENTICATE_DONE[81]:
*Mar 11 00:36:20.368: //-1//APPL:HN33A0DD40:/AppProcessEvent: HAN[TCL_HAN][NULL    
][FALSE] [UC=1 ]
*Mar 11 00:36:20.368: //-1//APPL:LP:HN33A0DD4C:HN33A0DD40:/AppPushHandler: Pushing 
{HAN[DC_HANDL][NULL    ]     ( )} Onto 
{HAN[TCL_HAND][NULL    ]      ( LEG[91     ][TCL_HAND][LEG_INCCONNECTED(5)][Cause(0)][UC=1 
])}
*Mar 11 00:36:20.372: //91//APPL:LP:HN33A0DD4C:/AppPushLegORConnection: Pushing LEG[91    
][TCL_HAND][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ] Onto {HAN[DC_HANDL][TCL_HAND]      ( )}
*Mar 11 00:36:20.372: //91//APPL:LP:DP4:/AppMediaPlay:
*Mar 11 00:36:20.376: //91//APPL:/AppProcessEvent: Event 
CC_EV_CALL_REPORT_DIGITS_DONE[58]:
*Mar 11 00:36:20.376: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:22.804: //91//APPL:/AppProcessEvent: Event MSW_EV_SYNTHESIZER[78]:
*Mar 11 00:36:22.804: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:24.044: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DIGIT_BEGIN[14]:
*Mar 11 00:36:24.044: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:24.124: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DIGIT_END[13]:
*Mar 11 00:36:24.124: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:24.312: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DIGIT_BEGIN[14]:
*Mar 11 00:36:24.312: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:24.412: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DIGIT_END[13]:
*Mar 11 00:36:24.412: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:24.940: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DIGIT_BEGIN[14]:
*Mar 11 00:36:24.944: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:25.012: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DIGIT_END[13]:
*Mar 11 00:36:25.012: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:25.140: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DIGIT_BEGIN[14]:
*Mar 11 00:36:25.144: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:25.220: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DIGIT_END[13]:
*Mar 11 00:36:25.224: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:25.392: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DIGIT_BEGIN[14]:
*Mar 11 00:36:25.392: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:25.480: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DIGIT_END[13]:
*Mar 11 00:36:25.480: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:25.484: //91//APPL:/AppProcessEvent: Event 
CC_EV_CALL_REPORT_DIGITS_DONE[58]:
*Mar 11 00:36:25.484: //91//APPL:/AppProcessEvent: LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
*Mar 11 00:36:25.484: //91//APPL:/AppPopLegORConnection: Poping LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ] From {HAN[DC_HANDL][TCL_HAND]      ( 
LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ])} To {HAN[TCL_HAND][NULL    ]    ( 
LEG[91     
][DC_HANDL][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]HAN[DC_HAND][TCL_HAND][TRUE] [UC=1 ])}
*Mar 11 00:36:25.484: //91//APPL:LP:HN33A0DD40:/AppPopLegORConnection: Pushing onto 
grandparent
*Mar 11 00:36:25.488: //-1//APPL:LP:HN33A0F148:HN33A0DD40:/AppPushHandler: Pushing 
{HAN[CS_HAND ][NULL    ]     ( )} Onto 
{HAN[TCL_HAND][NULL    ]      ( LEG[91     
][TCL_HAND][LEG_INCCONNECTED(5)][Cause(0)][UC=1]HAN[DC_HAND][TCL_HAND][TRUE] [UC=1 ])}
*Mar 11 00:36:25.488: //91//APPL:LP:HN33A0F148:/AppPushLegORConnection: Pushing LEG[91     
][TCL_HAND][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ] Onto {HAN[CS_HAND ][TCL_HAND]      ( )}
*Mar 11 00:36:25.488: //-1//APPL:LP:HN33A0F14C:HN33A0F148:/AppPushHandler: Pushing 
{HAN[DN_HAND ][NULL    ]     ( )} Onto 
{HAN[CS_HAND ][TCL_HAND]      ( LEG[91     ][CS_HAND ][LEG_INCCONNECTED(5)][Cause(0)][UC=1 
])}
*Mar 11 00:36:25.488: //-1//APPL:/AppSaveRawMsg:
*Mar 11 00:36:25.488: //-1//APPL:/AppNewLeg:
*Mar 11 00:36:25.492: //94/43855ACF809E/APPL:/AppLegSetupRequest: ccCallSetupRequest done
*Mar 11 00:36:25.492: //94//APPL:LP:HN33A0F14C:/AppPushLegORConnection: Pushing LEG[94     
][NULL    
][LEG_OUTINIT(6)][Cause(0)][UC=1 ] Onto {HAN[DN_HAND ][CS_HAND ]   ( )}
*Mar 11 00:36:25.492: //-1//APPL:HN33A0DD4C:/AppPopHandler: Poping 
{HAN[DC_HANDL][TCL_HAND]     ( )}
*Mar 11 00:36:25.728: //94//APPL:/AppProcessEvent: Event CC_EV_CALL_PROCEEDING[25]:
*Mar 11 00:36:25.728: //94//APPL:/AppProcessEvent: LEG[94     ][DN_HAND 
][LEG_OUTINIT(6)][Cause(0)][UC=1 ]
*Mar 11 00:36:25.728: //94//APPL:/AppPopLegORConnection: Poping LEG[94     ][DN_HAND 
][LEG_OUTINIT(6)][Cause(0)][UC=1 ]
From {HAN[DN_HAND ][CS_HAND ]   ( LEG[94     ][DN_HAND ][LEG_OUTINIT(6)][Cause(0)][UC=1 
])} To 
{HAN[CS_HAND][TCL_HAND]( LEG[91     ][CS_HAND ][LEG_INCCONNECTED(5)][Cause(0)][UC=1 
]HAN[DN_HAND][CS_HAND 
][FALSE] [UC=1 ])}
*Mar 11 00:36:25.728: //94//APPL:LP:HN33A0F148:/AppPopLegORConnection: Pushing onto 
grandparent
*Mar 11 00:36:25.732: //94//APPL:/AppProcessEvent: Event CC_EV_CALL_ALERT[11]:
*Mar 11 00:36:25.732: //94//APPL:/AppProcessEvent: LEG[94     ][CS_HAND 
][LEG_OUTINIT(6)][Cause(0)][UC=1 ]
Router#
Router#!call answered
Router#
*Mar 11 00:36:42.272: //94//APPL:/AppProcessEvent: Event CC_EV_CALL_CONNECTED[12]:
*Mar 11 00:36:42.272: //94//APPL:/AppProcessEvent: LEG[94     ][CS_HAND 
][LEG_OUTINIT(6)][Cause(0)][UC=1 ]
*Mar 11 00:36:42.272: //-1//APPL:/AppSaveRawMsg:
*Mar 11 00:36:42.272: //-1//APPL:LG91:LG94:/AppConnectionCreate:
*Mar 11 00:36:42.272: //-1//APPL:CN13:/AppConnectionCreate: Conference created
*Mar 11 00:36:42.272: //-1//APPL:LP:CN13:LG91:LG94:/AppMakeConnection: 
conn[63A605E8],leg1[63A75744]leg2[63A7620C]
*Mar 11 00:36:42.276: //-1//APPL:LP:CN13:HN33A0F148:/AppPushLegORConnection: Pushing 
CON[13     ][NULL    
][CONNECTION_CONFING(1)] [UC=1 ] Onto {HAN[CS_HAND ][TCL_HAND]        ( LEG[91     
][CS_HAND 
][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]HAN[DN_HAND][CS_HAND ][FALSE] [UC=1 ]LEG[94     
][CS_HAND 
][LEG_OUTINIT(6)][Cause(0)][UC=1 ])}
*Mar 11 00:36:42.276: //-1//APPL:CN13:/AppProcessEvent: Event CC_EV_CONF_CREATE_DONE[33]:
*Mar 11 00:36:42.276: //-1//APPL:CN13:/AppProcessEvent: CON[13     ][CS_HAND 
][CONNECTION_CONFED(2)] [UC=1 ]
*Mar 11 00:36:42.276: //-1//APPL:HN33A0F14C:/AppPopHandler: Poping {HAN[DN_HAND ][CS_HAND 
]     ( )}
*Mar 11 00:36:42.276: //91//APPL:/AppPopLegORConnection: Poping LEG[91     ][CS_HAND 
][LEG_INCCONNECTED(5)][Cause(0)][UC=1 
] From {HAN[CS_HAND ][TCL_HAND]      ( LEG[91     ][CS_HAND 
][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]CON[13     
][CS_HAND ][CONNECTION_CONFED(2)] [UC=1 ]LEG[94     ][CS_HAND 
][LEG_OUTINIT(6)][Cause(0)][UC=1 ])} To 
{HAN[TCL_HAND][NULL    ]( LEG[91     ][CS_HAND ][LEG_INCCONNECTED(5)][Cause(0)][UC=1 
]HAN[CS_HAND][TCL_HAND][TRUE] [UC=1 ])}
*Mar 11 00:36:42.280: //91//APPL:LP:HN33A0DD40:/AppPopLegORConnection: Pushing onto 
grandparent
*Mar 11 00:36:42.280: //94//APPL:/AppPopLegORConnection: Poping LEG[94     ][CS_HAND 
][LEG_OUTINIT(6)][Cause(0)][UC=1 ]
From {HAN[CS_HAND ][TCL_HAND]   ( LEG[94     ][CS_HAND ][LEG_OUTINIT(6)][Cause(0)][UC=1 
]CON[13     
][CS_HAND][CONNECTION_CONFED(2)] [UC=1 ])} To {HAN[TCL_HAND][NULL    ]     ( 
LEG[91][TCL_HAND][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]HAN[CS_HAND][TCL_HAND][TRUE] [UC=1 
])}
*Mar 11 00:36:42.280: //94//APPL:LP:HN33A0DD40:/AppPopLegORConnection: Pushing onto 
grandparent
*Mar 11 00:36:42.280: //-1//APPL:CN13:/AppPopLegORConnection: Poping CON[13     ][CS_HAND 
][CONNECTION_CONFED(2)] [UC=1] 
From {HAN[CS_HAND ][TCL_HAND] ( CON[13     ][CS_HAND ][CONNECTION_CONFED(2)] [UC=1 ])} To 
{HAN[TCL_HAND][NULL ]
( LEG[91     ][TCL_HAND][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]HAN[CS_HAND][TCL_HAND][TRUE] 
[UC=1 
]LEG[94][TCL_HAND] [LEG_OUTINIT(6)][Cause(0)][UC=1 ])}
*Mar 11 00:36:42.280: //-1//APPL:LP:CN13:HN33A0DD40:/AppPopLegORConnection: Pushing onto 
grandparent
*Mar 11 00:36:42.284: //-1//APPL:HN33A0F148:/AppPopHandler: Poping {HAN[CS_HAND 
][TCL_HAND]     ( )}
*Mar 11 00:36:42.288: //91//APPL:/AppProcessEvent: Event CC_EV_VOICE_MODE_DONE[56]:
*Mar 11 00:36:42.288: //91//APPL:/AppProcessEvent: LEG[91     
][TCL_HAND][LEG_INCCONNECTED(5)][Cause(0)][UC=1 ]
Router#
Router#!digits dialed
Router#
Router#!call disconnected
Router#
*Mar 11 00:37:20.748: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DISCONNECTED[15]:
*Mar 11 00:37:20.752: //91//APPL:/AppProcessEvent: LEG[91     
][TCL_HAND][LEG_INCCONNECTED(5)][Cause(16)][UC=1 ]
*Mar 11 00:37:20.752: //-1//APPL:/AppSaveRawMsg:
*Mar 11 00:37:20.752: //-1//APPL:CN13:/AppConnectionDestroy:
*Mar 11 00:37:20.752: //-1//APPL:CN13:/AppBreakConnection:
*Mar 11 00:37:20.752: CON[13     ][TCL_HAND][CONNECTION_UNCONFING(3)] 
{LEG[91][TCL_HAND][LEG_INCCONNECTED(5)][Cause(16)][UC=1 ],LEG[94     
][TCL_HAND][LEG_OUTINIT(6)][Cause(0)][UC=1 ]}
*Mar 11 00:37:20.752: //-1//APPL:CN13:/AppProcessEvent: Event CC_EV_CONF_DESTROY_DONE[34]:
*Mar 11 00:37:20.752: //-1//APPL:CN13:/AppProcessEvent: CON[13     
][TCL_HAND][CONNECTION_UNCONFED(0)] [UC=1 ]
*Mar 11 00:37:20.756: //-1//APPL:CN13:/AppFreeConnection:
*Mar 11 00:37:20.756: CON[13     ][TCL_HAND][CONNECTION_UNCONFED(0)] [UC=1 
]{HAN[TCL_HAND][NULL    ]    ( LEG[91     
][TCL_HAND][LEG_INCCONNECTED(5)][Cause(16)][UC=1 ]CON[13     
][TCL_HAND][CONNECTION_UNCONFED(0)] [UC=1 ]LEG[94     
][TCL_HAND][LEG_OUTINIT(6)][Cause(16)][UC=1 ])}
*Mar 11 00:37:20.776: //91//APPL:/AppProcessEvent: Event CC_EV_CALL_DISCONNECT_DONE[16]:
*Mar 11 00:37:20.776: //91//APPL:/AppProcessEvent: LEG[91     
][TCL_HAND][LEG_DISCONNECTING(9)][Cause(16)][UC=1 ]
*Mar 11 00:37:20.776: //91//APPL:/AppFreeLeg:
*Mar 11 00:37:22.764: //94//APPL:/AppProcessEvent: Event CC_EV_CALL_DISCONNECT_DONE[16]:
*Mar 11 00:37:22.764: //94//APPL:/AppProcessEvent: LEG[94     
][TCL_HAND][LEG_DISCONNECTING(9)][Cause(16)][UC=1 ]
*Mar 11 00:37:22.764: //94//APPL:/AppFreeLeg:
*Mar 11 00:37:22.764: //-1//APPL:/AppManagerFreeProcess: pProcess(0x63A60C8C)=1

Table 281 describes the significant fields shown in the display.

Table 281 debug voip ivr applib Field Descriptions

Field
Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//91/ and //94/

Identifies the CallEntry ID.

APPL:

Identifies the application.


Related Commands

Command
Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.


debug voip ivr callsetup

To display debugging messages for interactive voice response (IVR) call setup being processed, use the debug voip ivr callsetup command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr callsetup

no debug voip ivr callsetup

Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

We recommend that you log output from the debug voip ivr callsetup 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 debugging output for the debug voip ivr callsetup command:

Router# debug voip ivr callsetup

Router#
Router#!call initiated
Router#
*Mar 11 00:33:11.336: //-1//PCM :LP:HN339DFAE4:HN339DE238:/InitiateCallSetup: Incoming[87] 
AlertTime -1 Destinations(1) [ 34998  ]
*Mar 11 00:33:11.336: //-1//PCM :HN339DFAE4:/InitiateCallSetup: Destination 0 guid : 
CF1773A4.1CCE11CC.809BA499.0FED1E30
*Mar 11 00:33:11.336:  incoming_guid : 00000000.00000000.00000000.00000000
*Mar 11 00:33:11.336: //-1//PCM :LP:HN339DFAE4:HN339DFAE4:/DNInitiate: Destination[34998]
*Mar 11 00:33:11.336: //-1//PCM :HN339DFAE4:/DNMatchDialPeer:
*Mar 11 00:33:11.336:  src carrier id:, tgt carrier id:
*Mar 11 00:33:11.336: Matched peers(1)
*Mar 11 00:33:11.336: //-1//PCM :HN339DFAE4:/DNSetupPeer:
*Mar 11 00:33:11.336: //-1//PCM :HN339DFAE4:/DNSetupPeer: dialpeer tags for Rotary =  100
*Mar 11 00:33:11.336: //-1//PCM :HN339DFAE4:/DNSetupPeer:
*Mar 11 00:33:11.336: Destination SetupPeer cid(87), destPat(34998), match(5), prefix(), 
peer(63947E8C)
*Mar 11 00:33:11.340: //-1//PCM :HN339DFAE4:/DNSettlementMatrixCheck: retcode=1 cid(87) 
trans=0x0, provider=0 No settle-call present
*Mar 11 00:33:11.592: //90//PCM :/DNHandler: 
(DN_SETTING[2])--(CC_EV_CALL_PROCEEDING[25])--IGNORED-->>(DN_SETTING[2])
*Mar 11 00:33:11.596: //90//PCM :/CS_Setting_PROCEED:
*Mar 11 00:33:11.596: //90//PCM :/CSPopLegAndWait:
*Mar 11 00:33:11.596: //90//PCM :/CallSetupHandler: (CS_SETTING[0]) 
-----(CS_EV_PROCEEDING[3])------->>>(CS_SETTING[0])
*Mar 11 00:33:11.600: //90//PCM :/CS_Setting_ALERT:
*Mar 11 00:33:11.600: //90//PCM :/CSPopLegAndWait:
*Mar 11 00:33:11.600: //90//PCM :/CallSetupHandler: (CS_SETTING[0]) 
-----(CS_EV_ALERT[4])------->>>(CS_ALERTING[1])
Router#
Router#!call answered
Router#
Router#
*Mar 11 00:33:24.988: //90//PCM :/CS_Alerting_CONNECTED:
*Mar 11 00:33:24.988: //-1//PCM :HN339DFAE4:/CSDiscReturnAndEmptyLegALL:
*Mar 11 00:33:24.988: //90//PCM :/CSPopLegAndWait:
*Mar 11 00:33:24.988: //90//PCM :/CallSetupHandler: (CS_ALERTING[1]) 
-----(CS_EV_CONNECTED[5])------->>>(CS_CONFING[2])
*Mar 11 00:33:24.992: //-1//PCM :HN339DFAE4:/CS_Confing_CREATEDONE:
*Mar 11 00:33:24.992: //-1//PCM :HN339DFAE4:/DNCleanup: Terminate=TRUE Status DN_SUCCESS
*Mar 11 00:33:24.992: //-1//PCM :HN339DFAE4:/DNSettlementCleanup: cid(87) trans=0x0, 
provider=0
*Mar 11 00:33:24.992: //-1//PCM :HN339DFAE4:/CSReturnIFDone: CallSetup Returning(Status 
CS_ACTIVE)
*Mar 11 00:33:24.992: //-1//PCM :HN339DFAE4:/CallSetupHandler: (CS_CONFING[2]) 
-----(CS_EV_CREATEDONE[8])------->>>(CS_C
ONFED[3])
*Mar 11 00:33:24.992: //-1//PCM :HN339DFAE4:/CallSetupCleanup: Terminate=FALSE
*Mar 11 00:33:24.996: //-1//PCM :HN339DFAE4:/CallSetupCleanup: State CS_CONFED
Router#
Router#!digits dialed
Router#
Router#!call terminated
Router#

Table 282 describes the significant fields shown in the display.

Table 282 debug voip ivr callsetup Field Descriptions

Field
Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//90/

Identifies the CallEntry ID.

PCM:

Identifies the IVR module name. This is the place call module.


Related Commands

Command
Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.


debug voip ivr digitcollect

To display debugging messages for interactive voice response (IVR) digits collected during a call, use the debug voip ivr digitcollect command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr digitcollect

no debug voip ivr digitcollect

Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

We recommend that you log output from the debug voip ivr digitcollect 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 debugging output for the debug voip ivr digitcollect command:

Router# debug voip ivr digitcollect

Router#
Router#!call initiated
Router#
*Mar 11 00:30:05.384: //83//DCM :/DigitCollect: DialPlan=TRUE AbortKey=* TermKey=# 
NumPatts=0
              Enable=FALSE InterruptPrompt=TRUE maxDigits=0 DialPlanTerm=FALSE
*Mar 11 00:30:05.384: //83//APPL:/AppTypeAheadGetDigit: no chars in buffer.
*Mar 11 00:30:05.440: //83//DCM :/act_DCRunning_RDone: callid=83 Enable succeeded.enable=0 
matchDialplan=1 
numPatterns=0matchDialplanTerm=0
*Mar 11 00:30:07.912: //83//DCM :/DCHandlerFunc: PassingThrough
*Mar 11 00:30:09.652: //83//APPL:/AppVcrControlEvent: VCR Control, not enabled.---
*Mar 11 00:30:09.652: //83//APPL:/AppTypeAheadEvent: Passing, not enabled.---
*Mar 11 00:30:09.652: //83//DCM :/act_DCRunning_Digit: : pLeg 83 Digit 3 Tone Mode 0
*Mar 11 00:30:09.652: //83//DCM :/DCTreatDigit:
*Mar 11 00:30:09.652: //-1//DCM :HN339B2484:/DCTreatDigit:
*Mar 11 00:30:09.656:  src carrier id:, tgt carrier id:
*Mar 11 00:30:09.656: //-1//DCM :HN339B2484:/DCTreatDigit: Match single infotype
*Mar 11 00:30:09.964: //83//APPL:/AppVcrControlEvent: VCR Control, not enabled.---
*Mar 11 00:30:09.964: //83//APPL:/AppTypeAheadEvent: Passing, not enabled.---
*Mar 11 00:30:09.964: //83//DCM :/act_DCRunning_Digit: : pLeg 83 Digit 4 Tone Mode 0
*Mar 11 00:30:09.964: //83//DCM :/DCTreatDigit:
*Mar 11 00:30:09.964: //-1//DCM :HN339B2484:/DCTreatDigit:
*Mar 11 00:30:09.964:  src carrier id:, tgt carrier id:
*Mar 11 00:30:09.964: //-1//DCM :HN339B2484:/DCTreatDigit: Match single infotype
*Mar 11 00:30:10.264: //83//APPL:/AppVcrControlEvent: VCR Control, not enabled.---
*Mar 11 00:30:10.264: //83//APPL:/AppTypeAheadEvent: Passing, not enabled.---
*Mar 11 00:30:10.264: //83//DCM :/act_DCRunning_Digit: : pLeg 83 Digit 9 Tone Mode 0
*Mar 11 00:30:10.264: //83//DCM :/DCTreatDigit:
*Mar 11 00:30:10.264: //-1//DCM :HN339B2484:/DCTreatDigit:
*Mar 11 00:30:10.264:  src carrier id:, tgt carrier id:
*Mar 11 00:30:10.264: //-1//DCM :HN339B2484:/DCTreatDigit: Match single infotype
*Mar 11 00:30:10.492: //83//APPL:/AppVcrControlEvent: VCR Control, not enabled.---
*Mar 11 00:30:10.492: //83//APPL:/AppTypeAheadEvent: Passing, not enabled.---
*Mar 11 00:30:10.492: //83//DCM :/act_DCRunning_Digit: : pLeg 83 Digit 9 Tone Mode 0
*Mar 11 00:30:10.492: //83//DCM :/DCTreatDigit:
*Mar 11 00:30:10.492: //-1//DCM :HN339B2484:/DCTreatDigit:
*Mar 11 00:30:10.492:  src carrier id:, tgt carrier id:
*Mar 11 00:30:10.492: //-1//DCM :HN339B2484:/DCTreatDigit: Match single infotype
*Mar 11 00:30:10.752: //83//APPL:/AppVcrControlEvent: VCR Control, not enabled.---
*Mar 11 00:30:10.752: //83//APPL:/AppTypeAheadEvent: Passing, not enabled.---
*Mar 11 00:30:10.752: //83//DCM :/act_DCRunning_Digit: : pLeg 83 Digit 8 Tone Mode 0
*Mar 11 00:30:10.752: //83//DCM :/DCTreatDigit:
*Mar 11 00:30:10.752: //-1//DCM :HN339B2484:/DCTreatDigit:
*Mar 11 00:30:10.752:  src carrier id:, tgt carrier id:
*Mar 11 00:30:10.752: //-1//DCM :HN339B2484:/DCTreatDigit: Match single infotype
*Mar 11 00:30:10.756: //83//DCM :/act_DCRunning_RDone: callid=83 Reporting disabled.
*Mar 11 00:30:10.756: //-1//DCM :HN339B2484:/DigitCollectComplete: Status 
4=DC_MATCHED_DIALPLAN. Digits=34998
*Mar 11 00:30:10.756: //-1//DCM :HN339B2484:/DCHandlerCleanup:
Router#
Router#!call answered
Router#
Router#!digits dialed
Router#
Router#!call terminated
Router#

Table 283 describes the significant fields shown in the display.

Table 283 debug voip ivr digitcollect Field Descriptions

Field
Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//83/

Identifies the CallEntry ID.

DCM:

Identifies the IVR module name. This is the digit collect module.

APPL:

Identifies the application.


Related Commands

Command
Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.


debug voip ivr dynamic

To display debugging messages for interactive voice response (IVR) dynamic prompt play, use the debug voip ivr dynamic command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr dynamic

no debug voip ivr dynamic

Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

We recommend that you log output from the debug voip ivr dynamic 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 debugging output for the debug voip ivr dynamic command:

Router# debug voip ivr dynamic

ivr dynamic promptplaying debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 02:39:28.007: //-1//DPM :DP12:/pc_mc_createDynamicS: calloc mcDynamicS_t
*Mar 11 02:39:28.007: //-1//DPM :DP12:/pc_mc_addToDynamicS: Doing : 
flash:enter_destination.au
*Mar 11 02:39:28.007: //-1//DPM :DP12:/pc_mc_addToDynamicS: Token : 
flash:enter_destination.au
*Mar 11 02:39:28.007: //-1//MCM :MC2:/mc_getFromUrlName: enter_destination.au on ram
*Mar 11 02:39:28.007: //-1//MCM :MC2:/mc_waitq_delete: nothing to delete
*Mar 11 02:39:28.007: //-1//DPM :LP:DP12:MC2:/dp_mcDQfromURL:
*Mar 11 02:39:28.007: $ $du_get_vpPromptName() OK###
*Mar 11 02:39:28.007: //-1//MCM :MR11:/mc_createDynamicReader:
*Mar 11 02:39:28.011: //118//MSM :/ms_associate: packet_size = 160 timestamp increment = 
160 packet_duration = 20 Coder= 5 vad = 0 
SampleRate = 8000
*Mar 11 02:39:28.011: //118//MSM :/ms_associate: >>ccAssociateStream()
*Mar 11 02:39:28.015: //-1//MCM :MR11:/mc_setup_reader_encaps:
*Mar 11 02:39:28.019: //-1//MCM :MR11:/mc_make_packets_DQ: mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:28.019: //-1//MCM :MR11:/mc_make_packets_DQ: mc_fill_pakList(): 
status_fillpak 1, /                      mcr->thisMcBytesPlay 
9600, mc:638E1FC8 name:enter_destination.au
*Mar 11 02:39:28.019: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:28.019: //118//MSM :/ms_start_play: 1w3d mgdTstart(rf)
*Mar 11 02:39:28.023: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.043: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.063: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.083: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.103: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.123: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.143: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.163: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.183: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.203: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.219: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 11200, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:28.219: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:28.219: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:28.223: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.243: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.263: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.283: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.303: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.323: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.343: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.363: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.383: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.403: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.419: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 12800, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:28.419: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:28.419: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:28.423: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.443: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.463: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.483: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.503: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.523: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.543: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.563: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.583: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.603: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.619: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 14400, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:28.619: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:28.619: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:28.623: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.643: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.663: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.683: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.703: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.723: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.743: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.763: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.783: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.803: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.819: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 16000, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:28.819: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:28.819: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:28.823: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.843: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.863: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.883: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.903: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.923: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.943: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.963: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:28.983: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.003: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.019: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 17600, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:29.019: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:29.019: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:29.023: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.043: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.063: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.083: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.103: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.123: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.143: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.163: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.183: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.203: //118//MSM :/ms_fill_buffer: F(160)
*Mar 11 02:39:29.227: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.231: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 1, 
mcr->thisMcBytesPlay 19360, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:29.231: //-1//MCM :MR11:/mc_make_packets_DQ: count: 60
*Mar 11 02:39:29.231: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:29.247: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.267: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.287: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.307: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.327: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.347: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.367: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.387: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.407: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.427: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.431: //-1//MCM :MR11:/mc_make_packets_DQ: status_fillpak 0, 
mcr->thisMcBytesPlay 19360, mc:638E1FC8 
name:enter_destination.au
*Mar 11 02:39:29.431: //-1//MCM :MR11:/mc_make_packets_DQ: count: 50
*Mar 11 02:39:29.431: //-1//MCM :MR11:/mc_make_packets_DQ: count: 50
*Mar 11 02:39:29.431: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:29.447: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.467: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.487: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.507: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.527: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.547: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.567: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.587: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.607: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.627: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.631: //-1//MCM :MR11:/mc_make_packets_DQ: No more on reader
*Mar 11 02:39:29.631: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:29.647: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.667: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.687: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.707: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.727: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.747: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.767: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.787: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.807: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.827: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.831: //-1//MCM :MR11:/mc_make_packets_DQ: No more on reader
*Mar 11 02:39:29.831: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:29.847: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.867: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.887: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.907: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.927: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.947: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.967: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:29.987: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.007: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.027: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.031: //-1//MCM :MR11:/mc_make_packets_DQ: No more on reader
*Mar 11 02:39:30.031: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:30.047: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.067: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.087: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.107: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.127: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.147: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.167: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.187: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.207: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.227: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.231: //-1//MCM :MR11:/mc_make_packets_DQ: No more on reader
*Mar 11 02:39:30.231: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:30.247: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.267: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.287: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.307: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.327: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.347: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.367: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.387: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.407: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.427: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.431: //-1//MCM :MR11:/mc_make_packets_DQ: No more on reader
*Mar 11 02:39:30.431: //118//MSM :/ms_need_packets_more: mgdTstart(rf) at 1w3d
*Mar 11 02:39:30.447: //118//MSM :/ms_fill_buffer: F(192)
*Mar 11 02:39:30.447: //118//MSM :/ms_process: $w$ intEvent MS_E_STOP_PLAY
*Mar 11 02:39:30.447: //118//MSM :/ms_stop_play: mgdTstop(rf) at 1w3d
*Mar 11 02:39:30.447: //-1//DPM :DP12:/dp_delete_mcDynamicS: >dequeue(mcDynamicQ)
*Mar 11 02:39:30.447: //-1//MCM :MC2:/mc_delete: mc=0x638E1FC8
*Mar 11 02:39:30.447: //-1//MCM :MC2:/mc_delete: refCount=1
*Mar 11 02:39:30.447: //-1//MCM :MC2:/mc_waitq_add: already in the waitq
*Mar 11 02:39:30.447: //-1//MCM :MC2:/mc_delete: prompt_wait=0 prompt_active=0
*Mar 11 02:39:30.447: //-1//DPM :DP12:/dp_delete_mcDynamicS: >free(p_mcDynamicS)
*Mar 11 02:39:30.447: //-1//MCM :MR11:/mc_delete_read: dequeue(pakList)
*Mar 11 02:39:30.447: //118//MSM :/ms_process: >>ms_delete_event(MS_E_int)
Router#
Router#!call answered
Router#
Router#!digits dialed
Router#
Router#!call terminated
Router#

Table 284 describes the significant fields shown in the display.

Table 284 debug voip ivr dynamic Field Descriptions

Field
Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//118/

Identifies the CallEntry ID.

PDM:

Identifies the IVR module name. This is the dynamic prompt module.

MCM:

Identifies the IVR module name. This is the media content module.


Related Commands

Command
Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.


debug voip ivr error

To display debugging messages for interactive voice response (IVR) errors, use the debug voip ivr error command in privileged EXEC mode. Messages only appear if an error has occurred. To disable debugging output, use the no form of this command.

debug voip ivr error

no debug voip ivr error

Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

Error output should only occur if something is not working or an error condition is indicated.


Note We recommend that you log output from the debug voip ivr 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 ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.


debug voip ivr script

To display debugging messages for interactive voice response (IVR) scripts, use the debug voip ivr script command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr script

no debug voip ivr script

Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

We recommend that you log output from the debug voip ivr script 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 output is an example of what is displayed when the debug voip ivr script command is entered:

Router# debug voip ivr script

ivr script debugging is on
Router#
Router#!call initiated
Router#
Router#!call answered
Router#
*Mar 11 02:50:59.431: //-1//TCL2:HN341BC8B0:/tcl_PutsCmd:
 Unlimited Time
*Mar 11 02:50:59.431:
Router#
*Mar 11 02:51:28.343: //-1//TCL2:HN341C6A88:/tcl_PutsCmd:
 Unlimited Time
*Mar 11 02:51:28.343:
Router#
Router#!digits entered
Router#
Router#!call terminated
Router#

Table 285 describes the significant fields shown in the display.

Table 285 debug voip ivr script Field Descriptions

Field
Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

TCL2:

Identifies the TCL IVR 2 module.


Related Commands

Command
Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.


debug voip ivr settlement

To display debugging messages for interactive voice response (IVR) settlement activities, use the debug voip ivr settlement command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr settlement

no debug voip ivr settlement

Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

11.3(6)NA2

This command was introduced.

12.0(4)XH

Settlement was added.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

Settlement output logs activities related to settlement when a call is processed.


Note We recommend that you log output from the debug voip ivr settlement 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 output is an example of what is displayed when the debug voip ivr settlement command is entered:

Router # debug voip ivr settlement

ivr settlement activities debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 03:02:20.819: //142//TCL2:/SettlementValidateCall: target=, tokenp=0x0
Router#
Router#!call answered
Router#
*Mar 11 03:02:40.979: //-1//TCL2:HN342689D0:/vtr_lg_cssettlement_time: 
credit_time=uninitialized
Router#
Router#!digits dialed
Router#
Router#!call terminated

Table 286 describes the significant fields shown in the display.

Table 286 debug voip ivr settlement Field Descriptions

Field
Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//142/

Identifies the CallEntry ID.

TCL2:

Identifies theTCL IVR 2 module.


Related Commands

Command
Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.


debug voip ivr states

To display debugging messages that supply information about the current status of the interactive voice response (IVR) script and the different events that occur in that state, use the debug voip ivr states command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr states

no debug voip ivr states

Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

State output supplies information about the current status of the IVR script and the different events that occur in that state.


Note We recommend that you log output from the debug voip ivr states 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 debugging output for the debug voip ivr states command:

Router# debug voip ivr states 

ivr state transitions debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 02:54:11.539: //-1//TCL2:/TclGetInterp: Script test
*Mar 11 02:54:11.539: //134//TCL2:/TclInterpHandler: CC_EV_CALL_SETUP_IND
*Mar 11 02:54:11.539: //134//TCL2:/TclInterpDriver:
*Mar 11 02:54:11.539: //134//TCL2:/TclEventPreprocessing:
*Mar 11 02:54:11.539: //-1//TCL2:/TclIncomingCallBlock:
*Mar 11 02:54:11.539: //134//TCL2:/MakeTransition: FSM Transtion: ([1 
]CALL_INIT,[28]ev_setup_indication)---([10]act_Set
up)--->([7 ]AUTHENTICATE)
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/TclInterpHandler: APP_EV_AUTHENTICATE_DONE
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/TclInterpDriver:
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/TclEventPreprocessing:
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/TclEventPreprocessing:
*Mar 11 02:54:11.551: TclEventPreprocessing: app_event->e.evAuthenticateDone.status = 0
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/TclEventPreprocessing:
*Mar 11 02:54:11.551: TclEventPreprocessing: lastFailureCause = 0
*Mar 11 02:54:11.551: //-1//TCL2:HN341F1290:/MakeTransition: FSM Transtion: ([7 
]AUTHENTICATE,[81]ev_authenticate_done)-
--([7 ]act_Authenticated)--->([9 ]GETDEST)
*Mar 11 02:54:11.555: //-1//DPM :DP19:/pc_mc_addToDynamicS: (1) flash:enter_destination.au
*Mar 11 02:54:11.555: //-1//MCM :/mc_createFromFileUrl: Getting a media content: 
name=enter_destination.au
    url=flash:enter_destination.au
    load fast, load in background, fetchtimeout=-1
*Mar 11 02:54:11.555: //-1//MSW :GS15:/msw_create: cbf=0x6134CCAC
*Mar 11 02:54:11.555: //-1//MSM :MS29:/ms_create: Iniz ply_timer
*Mar 11 02:54:11.555: //-1//MSW :GS15:/msw_synth_open: mediaStream 0x63AE2790 created
*Mar 11 02:54:11.555: //-1//MSW :GS15:/msw_synth_open: rtspStream 0x633AF070 created,
            status=RTSP_STATUS_SUCCESS, session_id=0x1D (29)
*Mar 11 02:54:11.559: //-1//MSM :MS30:/ms_create: Iniz ply_timer
*Mar 11 02:54:11.559: //-1//MSW :GS15:/msw_recrd_open:
*Mar 11 02:54:11.559: :msw_recrd_open mediaStream 0x638D31CC created
*Mar 11 02:54:11.559: //-1//MSW :GS15:/msw_recrd_open: rtspStream 0x633AF078 created,
            status=RTSP_STATUS_SUCCESS, session_id=0x1E (30)
*Mar 11 02:54:11.559: //-1//MSW :/msw_set_backup_server: server[0] = '',
                     genericStream=0x634505E8
*Mar 11 02:54:11.559: //-1//MSW :/msw_set_backup_server: server[1] = '',
                     genericStream=0x634505E8
*Mar 11 02:54:11.559: //-1//MSW :/msw_associate_call:
*Mar 11 02:54:11.559: msw_associate_call: callID=0x86(134),
                     genericStream=0x634505E8
*Mar 11 02:54:11.559: //134//MSW :/msw_get_stream_state:
*Mar 11 02:54:11.559: msw_get_stream_state: genericStream 0x634505E8 is in state 
MSW_S_IDLE
*Mar 11 02:54:11.559: //134//MSW :/msw_synth_start: current_stream_id=1, content 0x0, 
dynamicS 0x63A5DB80, current_state
=MSW_S_IDLE
*Mar 11 02:54:11.559: //134//MSW :/msu_synth_partial_play: Media Stream URL
*Mar 11 02:54:11.563: //134//MSM :LP:MS29:/ms_associateDone:
*Mar 11 02:54:11.563: //134//MSM :/ms_asDone_buginf: callID=0x86, pVdb=0x63A4D214, 
disposition=0, playFunc=0x6129C58C,
    codec=0x5=g711ulaw, vad=255, mediaType=6, streamAssocID=0
*Mar 11 02:54:11.567: //134//MSM :/ms_associateDone: First Buf Play at 1w3d of 
enter_destination.au
*Mar 11 02:54:11.567: //134//MSM :/ms_associateDone: 1w3d, Tstart(ply: iSndDly 0)
*Mar 11 02:54:11.571: //134//MSM :/ms_handle_stream_timer: >>ms_start_play()
*Mar 11 02:54:11.571: //134//MSM :/ms_start_play: 1w3d mgdTstop(ply)
*Mar 11 02:54:13.999: //134//MSM :/ms_stop_play: mgdTstop at 1w3d (cause MS_STOP_COMPLETE)
*Mar 11 02:54:13.999: //134//MSM :/ms_stop_play: Play Stopped at 1w3d
*Mar 11 02:54:13.999: //134//MSM :/ms_stop_play: calling CBF for stream_id 1
*Mar 11 02:54:13.999: //134//MSW :/msu_synth_ms_play_complete: context=0x634505EC, 
use_dynamic=1, dynamicElement=0x0,
            cause=MS_STOP_COMPLETE, stream_id=1, duration=2436, rate=0
*Mar 11 02:54:13.999: //134//MSW :/msu_call_app: app_cbf=0x6134CCAC
        Event = MSW_EV_SYNTHESIZER(1), Context 0x63A741B4, Type    
MSW_SYNTH_TYPE_SYNTHESIZE(2), Reason  
MSW_SYNTH_REASO
N_GENERIC_SUCCESS(13)
*Mar 11 02:54:13.999: //134//TCL2:/TclInterpHandler: MSW_EV_SYNTHESIZER
*Mar 11 02:54:13.999: //134//TCL2:/TclInterpDriver:
*Mar 11 02:54:14.003: //134//TCL2:/TclEventPreprocessing:
*Mar 11 02:54:14.003: //134//TCL2:/MakeTransition: FSM Transtion: ([9 
]GETDEST,[80]ev_media_done)---([-1]IGNORE)--->([9
]GETDEST)
*Mar 11 02:54:18.891: //-1//TCL2:HN341F1290:/TclInterpHandler: APP_EV_DIGITCOLLECT_DONE
*Mar 11 02:54:18.891: //-1//TCL2:HN341F1290:/TclInterpDriver:
*Mar 11 02:54:18.891: //-1//TCL2:HN341F1290:/TclEventPreprocessing:
*Mar 11 02:54:18.895: //-1//TCL2:HN341F1290:/MakeTransition: FSM Transtion: ([9 
]GETDEST,[88]ev_collectdigits_done)---([
8 ]act_PromptCollect_dest)--->([8 ]PLACECALL)
Router#
Router#!call answered
Router#
*Mar 11 02:54:35.327: //-1//TCL2:HN341F1290:/TclInterpHandler: APP_EV_CALLSETUP_DONE
*Mar 11 02:54:35.327: //-1//TCL2:HN341F1290:/TclInterpDriver:
*Mar 11 02:54:35.327: //-1//TCL2:HN341F1290:/TclEventPreprocessing:
*Mar 11 02:54:35.327: //-1//TCL2:HN341F1290:/MakeTransition: FSM Transtion: ([8 
]PLACECALL,[85]ev_setup_done)---([5 ]act
_CallSetupDone)--->([3 ]CALLACTIVE)
*Mar 11 02:54:35.335: //134//TCL2:/TclInterpHandler: CC_EV_VOICE_MODE_DONE
*Mar 11 02:54:35.335: //134//TCL2:/TclInterpDriver:
*Mar 11 02:54:35.335: //134//TCL2:/TclEventPreprocessing:
*Mar 11 02:54:35.335: //134//TCL2:/MakeTransition: FSM Transtion: ([3 
]CALLACTIVE,[56])---([-1]IGNORE)--->([3 ]CALLACTIV
E)
Router#
Router#!digits dialed
Router#
Router#!call terminated
Router#
*Mar 11 02:57:01.627: //134//TCL2:/TclInterpHandler: CC_EV_CALL_DISCONNECTED
*Mar 11 02:57:01.627: //134//TCL2:/TclInterpDriver:
*Mar 11 02:57:01.627: //134//TCL2:/TclEventPreprocessing:
*Mar 11 02:57:01.631: //134//TCL2:/MakeTransition: FSM Transtion: ([3 
]CALLACTIVE,[15]ev_disconnected)---([1 ]act_Cleanu
p)--->([4 ]CALLDISCONNECT)
*Mar 11 02:57:01.631: //-1//TCL2:HN341F1290:/TclCallProcess: Interp Done
*Mar 11 02:57:01.631: //134//TCL2:/TclInterpCleanup: Terminate TRUE Terminated 
FALSE{HAN[TCL_HAND][NULL    ]    ( LEG[13
4    ][TCL_HAND][LEG_INCCONNECTED(5)][Cause(16)][UC=1 ]CON[19     
][TCL_HAND][CONNECTION_CONFED(2)] [UC=1 
]LEG[137    ][
TCL_HAND][LEG_OUTINIT(6)][Cause(0)][UC=1 ])}
*Mar 11 02:57:01.631: //-1//TCL2:HN341F1290:/TclInterpHandler: CC_EV_CONF_DESTROY_DONE
*Mar 11 02:57:01.631: //134//TCL2:/TclInterpCleaner:
*Mar 11 02:57:01.659: //134//TCL2:/TclInterpHandler: CC_EV_CALL_DISCONNECT_DONE
*Mar 11 02:57:01.659: //134//TCL2:/TclInterpCleaner:
*Mar 11 02:57:01.659: //134//MSW :/msw_destroy:
*Mar 11 02:57:01.659: //-1//MSW :/msw_stop: genericStream=0x634505E8,
               reason=MSW_REASON_DISCONNECTED
*Mar 11 02:57:01.659: //-1//MSW :/msw_synth_stop: genericStream=0x634505E8,
               mediaStream=0x63AE2790, rtspStream=0x633AF070
               reason=MSW_SYNTH_REASON_DISCONNECTED, current_state=MSW_S_IDLE
*Mar 11 02:57:01.663: //134//MSW :/msw_synth_stop: Stream not currently active
*Mar 11 02:57:01.663: //-1//MSW :/msw_recrd_stop: genericStream=0x634505E8,
               mediaStream=0x638D31CC, rtspStream=0x633AF078
               reason=MSW_RECRD_REASON_DISCONNECTED current_state=MSW_S_IDLE
*Mar 11 02:57:01.663: //-1//MSW :/msw_recrd_stop: Stream not currently active
*Mar 11 02:57:01.663: //-1//MSW :/msw_recog_stop:
*Mar 11 02:57:01.663: msw_recog_stop: genericStream=0x634505E8,
               mrcpStream=0x63450B9C
               reason=MSW_RECOG_REASON_DISCONNECTED, current_state=MSW_S_IDLE
*Mar 11 02:57:01.663: //-1//MSW :/msw_synth_stop: genericStream=0x634505E8,
               mediaStream=0x63AE2790, rtspStream=0x633AF070
               reason=MSW_SYNTH_REASON_DISCONNECTED, current_state=MSW_S_IDLE
*Mar 11 02:57:01.663: //134//MSW :/msw_synth_stop: Stream not currently active
*Mar 11 02:57:01.663: //-1//MSW :/msw_recrd_stop: genericStream=0x634505E8,
               mediaStream=0x638D31CC, rtspStream=0x633AF078
               reason=MSW_RECRD_REASON_DISCONNECTED current_state=MSW_S_IDLE
*Mar 11 02:57:01.663: //-1//MSW :/msw_recrd_stop: Stream not currently active
*Mar 11 02:57:01.663: //-1//MSW :/msw_recog_stop:
*Mar 11 02:57:01.667: msw_recog_stop: genericStream=0x634505E8,
               mrcpStream=0x63450B9C
               reason=MSW_RECOG_REASON_DISCONNECTED, current_state=MSW_S_IDLE
*Mar 11 02:57:03.639: //137//TCL2:/TclInterpHandler: CC_EV_CALL_DISCONNECT_DONE
*Mar 11 02:57:03.639: //-1//TCL2:HN341F1290:/TclInterpCleaner:
*Mar 11 02:57:03.639: //-1//TCL2:HN341F1290:/TclCallProcess: Interp Done
*Mar 11 02:57:03.639: //-1//TCL2:HN341F1290:/TclInterpCleanup: Terminate TRUE Terminated 
TRUE{HAN[TCL_HAND][NULL    ]
( )}
*Mar 11 02:57:03.639: //-1//TCL2:HN341F1290:/TclFreeInterp:  {HAN[TCL_HAND][NULL ]   ( )}

Table 287 describes the significant fields shown in the display.

Table 287 debug voip ivr states Field Descriptions

Field
Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//134/

Identifies the CallEntry ID.

PDM:

Identifies the IVR module name. This is the dynamic prompt module.

MCM:

Identifies the IVR module name. This is the media content module.

MSW:

Identifies the IVR module name. This is the media service wrapper.

TCL2

Idenifies the TCL IVR 2 module.


Related Commands

Command
Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.


debug voip ivr tclcommands

To display debugging messages for the Toolkit Command Language (TCL) commands used in interactive voice response (IVR) scripts, use the debug voip ivr tclcommands command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip ivr tclcommands

no debug voip ivr tclcommands

Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.1(3)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

We recommend that you log output from the debug voip ivr tclcommands 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 debugging output for the debug voip ivr tclcommands command:

Router# debug voip ivr tclcommands

ivr tcl commands debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 02:58:37.467: //138//TCL2:/tcl_legCmd: leg setupack leg_incoming
*Mar 11 02:58:37.467: //138//TCL2:/tcl_setupAckCmd: setupack leg_incoming
*Mar 11 02:58:37.467: //138//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 02:58:37.467: //138//TCL2:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:37.467: //138//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 02:58:37.467: //138//TCL2:/tcl_legCmd: leg proceeding leg_incoming
*Mar 11 02:58:37.467: //138//TCL2:/tcl_callProceedingCmd: proceeding leg_incoming
*Mar 11 02:58:37.467: //138//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 02:58:37.467: //138//TCL2:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:37.467: //138//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 02:58:37.467: //138//TCL2:/tcl_legCmd: leg connect leg_incoming
*Mar 11 02:58:37.471: //138//TCL2:/tcl_callConnectCmd: connect leg_incoming
*Mar 11 02:58:37.471: //138//TCL2:/vtd_lg_incoming: argc 2
*Mar 11 02:58:37.471: //138//TCL2:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:37.471: //138//TCL2:/tcl_parseCallID_vartag: VARTAG Translation Leg Count=1
*Mar 11 02:58:37.471: //138//TCL2:/tcl_infotagCmd: infotag get leg_ani
*Mar 11 02:58:37.471: //138//TCL2:/tcl_getInfoCmd: get leg_ani
*Mar 11 02:58:37.471: //138//TCL2:/vtr_lg_incani: argc 2 argindex 2
*Mar 11 02:58:37.471: //138//TCL2:/tcl_aaaCmd: aaa authenticate 300
*Mar 11 02:58:37.471: //138//TCL2:/tcl_AuthenticateCmd: authenticate 300
*Mar 11 02:58:37.471: //138//TCL2:/tcl_AuthenticateCmd: account=300, password=, 
methodList=, av-send=
*Mar 11 02:58:37.479: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get evt_status
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get evt_status
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/vtr_ev_status: argc 2 argindex 2
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get leg_isdid
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get leg_isdid
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/vtr_lg_incdid: argc 2 argindex 2
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get leg_dnis
*Mar 11 02:58:37.483: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get leg_dnis
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/vtr_lg_incdnis: argc 2 argindex 2
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/tcl_legCmd: leg collectdigits leg_incoming 
param1
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/tcl_collectDigitsCmd: collectdigits 
leg_incoming param1
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/vtd_lg_incoming: argc 3
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/tcl_parseCallID_vartag: VARTAG Translation 
Leg Count=1
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/tcl_mediaCmd: media play leg_incoming 
flash:enter_destination.au
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/tcl_mediaPlayCmd: play leg_incoming 
flash:enter_destination.au
*Mar 11 02:58:37.487: //-1//TCL2:HN34232154:/vtd_lg_incoming: argc 3
*Mar 11 02:58:37.491: //-1//TCL2:HN34232154:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:37.491: //-1//TCL2:HN34232154:/tcl_parseCallID_vartag: VARTAG Translation 
Leg Count=1
Router#
Router#
Router#
*Mar 11 02:58:45.003: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get evt_status
*Mar 11 02:58:45.003: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get evt_status
*Mar 11 02:58:45.003: //-1//TCL2:HN34232154:/vtr_ev_status: argc 2 argindex 2
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get evt_dcdigits
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get evt_dcdigits
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/vtr_ev_dcdigits: argc 2
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/vtr_ev_dcdigits: DCDIGITS [34998]
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/tcl_legCmd: leg setup 34998 callInfo 
leg_incoming
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/tcl_callSetupCmd: setup 34998 callInfo 
leg_incoming
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/vtd_lg_incoming: argc 4
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/vtd_lg_incoming: Legs [138 ]
*Mar 11 02:58:45.007: //-1//TCL2:HN34232154:/tcl_parseCallID_vartag: VARTAG Translation 
Leg Count=1
Router#
Router#!call answered
Router#
*Mar 11 02:58:58.107: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get evt_status
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get evt_status
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/vtr_ev_status: argc 2 argindex 2
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/tcl_infotagCmd: infotag get 
leg_settlement_time leg_outgoing
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/tcl_getInfoCmd: get leg_settlement_time 
leg_outgoing
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/vtr_lg_cssettlement_time: argc 3 argindex 2
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/vtd_lg_outgoing: argc 3
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/vtd_lg_outgoing: Legs [141 ]
*Mar 11 02:58:58.111: //-1//TCL2:HN34232154:/tcl_parseCallID_vartag: VARTAG Translation 
Leg Count=1
Router#
Router#!digits dialed
Router#
Router#!call terminated
Router#
*Mar 11 02:59:28.079: //138//TCL2:/tcl_callCmd: call close
*Mar 11 02:59:28.079: //138//TCL2:/tcl_closeCallCmd: close {HAN[TCL_HAND][NULL    ]     ( 
LEG[138    ][TCL_HAND][LEG_INC
CONNECTED(5)][Cause(16)][UC=1 ]CON[20     ][TCL_HAND][CONNECTION_CONFED(2)] [UC=1 ]LEG[141    
][TCL_HAND][LEG_OUTINIT(6)
][Cause(0)][UC=1 ])}

Table 288 describes the significant fields shown in the display.

Table 288 debug voip ivr tclcommands Field Descriptions

Field
Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//138/

Identifies the CallEntry ID.

TCL2

Idenifies the TCL IVR 2 module.


Related Commands

Command
Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

voice call debug

Allows configuration of the voice call debug output.


debug voip rawmsg

To display the raw message owner, length, and pointer, use the debug voip rawmsg command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip rawmsg [detail]

no debug voip rawmsg [detail]

Syntax Description

detail

(Optional) Prints the contents of the raw message in hexadecimal.


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release
Modification

12.0(6)T

This command was introduced.

12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


Usage Guidelines

We recommend that you log output from the debug voip rawmsg 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 output when you use the debug voip rawmsg command:

Router# debug voip rawmsg

voip rawmsg debugging is on
Router#
*Mar  1 01:16:25.155: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al
loc from 1, Length 18 Body 638E0C5

These debug messages show that a raw message is allocated for this call. The pointer to the memory location for this raw message is 63075164.

*Mar  1 01:16:25.155: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL
OCATED: ptr is 63075164, owner is 1, length is 18, msg is 638E0C54, type is 0, p
rotocol id is 0

The call control API (CCAPI) gets a setup indicator. It has no information about the callid (-1) and GUID (xxxxxxxxxxxx).

*Mar  1 01:16:25.159: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:

*Mar  1 01:16:25.159: Raw Message MaMa is TSP owner is CCAPI, length is 77, ptr
is 63075164, type is 0, protocol id is 2

The SSAPP at this stage knows about the CallEntry ID (30) but not about GUID (xxxxxxxxx) or the dial-peer (-1).

*Mar  1 01:16:25.163: //30/xxxxxxxxxxxx/SSAPP:-1:-1/ssaCallSetupInd:
*Mar  1 01:16:25.163: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2

The SSAPP learns about the GUID (34C457CD802F) and also learns the incoming dial peer (10002).

*Mar  1 01:16:25.163: //30/34C457CD802F/SSAPP:10002:-1/ssaSetupPeer:
*Mar  1 01:16:25.163: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2

The CCAPI gets the call proceeding for CallEntry ID 30. CCAPI still does not have a GUID (xxxxxxxxxxx).

*Mar  1 01:16:25.163: //30/xxxxxxxxxxxx/CCAPI/ccCallProceeding:

A new raw message buffer is created and the previous one is released.

*Mar  1 01:16:25.163: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al
loc from 10, Length 77 Body 0
*Mar  1 01:16:25.167: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL
OCATED: ptr is 630751EC, owner is 10, length is 77, msg is 638E0F0C, type is 0,
protocol id is 0
*Mar  1 01:16:25.167: //30/34C457CD802F/SSAPP:10002:-1/ssaSetupPeer:
*Mar  1 01:16:25.167: ssaSetupPeer: Saved rawmsgpp 630751EC len 77
IAM,
GCI,34c457cd14f911cc802f95f5fabb6b0f?)??p?34999

*Mar  1 01:16:25.167: //30/xxxxxxxxxxxx/CCAPI/ccCallSetupRequest:
*Mar  1 01:16:25.167: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2
*Mar  1 01:16:25.167: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
*Mar  1 01:16:25.167: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2

The SSAPP gets a message indicating the digits were passed along the VoIP call leg to the terminating gateway. The CallEntry ID is 30, GUID is 34C457CD802F and the incoming dial peer is 10002.

*Mar  1 01:16:25.167: //30/34C457CD802F/SSAPP:10002:-1/ssaReportDigitsDone:

The old raw message 63075164 was freed. The new one is 630751EC.

*Mar  1 01:16:25.179: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo:
Router#Raw Message FREED: ptr is 63075164, owner is 3, length is 4D, msg is 638E
0DB0, type is 0, protocol id is 2

CCAPI got a call proceeding on the second call leg (31); it has no information about the GUID (xxxxxxxxx).

*Mar  1 01:16:25.223: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_proceeding:

CCAPI got a call alert on the second call leg (31); still no information about the GUID (xxxxxxxxx).

*Mar  1 01:16:25.227: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_alert:

The alert is sent to the first call leg (30), GUID 34C457CD802F.

*Mar  1 01:16:25.227: //30/34C457CD802F/SSAPP:10002:-1/ssaAlert:
*Mar  1 01:16:25.227: //30/xxxxxxxxxxxx/CCAPI/ccCallAlert:

The call is answered at this point and the CCAPI gets a call connect for the second call leg (CallEntry ID is 31; GUID is xxxxxxxxx).

*Mar  1 01:16:40.975: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_connected:

The call connect is sent to the first call leg (30), GUID 34C457CD802F.

*Mar  1 01:16:40.975: //30/34C457CD802F/SSAPP:10002:-1/ssaConnect:
*Mar  1 01:16:40.975: //30/xxxxxxxxxxxx/CCAPI/ccCallConnect:

The current raw message (ptr 630751EC) is released; a new one will be proclaimed when needed.

*Mar  1 01:16:40.975: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo: Raw Message FREE
D: ptr is 630751EC, owner is 10, length is 4D, msg is 638E0F0C, type is 0, proto
col id is 2

A new raw message (ptr 63075274) is proclaimed.

*Mar  1 01:17:04.007: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al
loc from 1, Length 4 Body 638E1068
*Mar  1 01:17:04.007: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL
OCATED: ptr is 63075274, owner is 1, length is 4, msg is 638E1068, type is 0, pr
otocol id is 0

The call terminates now. CCAPI detects a call disconnect from the first call leg (30) with no GUID (xxxxxxxxx).

*Mar  1 01:17:04.007: //30/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnected:
*Mar  1 01:17:04.007: Raw Message MaMa is TSP owner is CCAPI, length is 4, ptr i
s 63075274, type is 0, protocol id is 2

The disconnect is sent to the first call leg (30), GUID (34C457CD802F).

*Mar  1 01:17:04.011: //30/34C457CD802F/SSAPP:10002:14/ssaDisconnected:
*Mar  1 01:17:04.011: Raw Message MaMa is TSP owner is SSAPP, length is 4, ptr i
s 63075274, type is 0, protocol id is 2

The CCAPI disconnects both call legs (incoming 30 and outgoing 31).

*Mar  1 01:17:04.011: //30/xxxxxxxxxxxx/CCAPI/ccCallDisconnect:
*Mar  1 01:17:04.011: //31/xxxxxxxxxxxx/CCAPI/ccCallDisconnect:
*Mar  1 01:17:04.011: Raw Message MaMa is TSP owner is SSAPP, length is 4, ptr i
s 63075274, type is 0, protocol id is 2

The raw message is released.

*Mar  1 01:17:04.015: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo: Raw Message FREE
D: ptr is 63075274, owner is 3, length is 4, msg is 638E1068, type is 0, protoco
l id is 2

The following example shows output when you use the debug voip rawmsg detail command. This example shows that the CCAPI layer received an indication for call setup. The detailed raw message dumps the hex of the message. This output is used to track down data pointing to different variables within the software modules.

Router# debug voip rawmsg detail

*Mar  6 17:03:24.169://-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo:VoIP Raw Msg Al
loc from 5, Length 0 Body 0
*Mar  6 17:03:24.173://-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:
*Mar  6 17:03:24.173:Raw Message MaMa is CCAPI owner is CCAPI, length is 59, pt
r is 63045C14, type is 0, protocol id is 18
*Mar  6 17:03:24.173:Raw Message is :1C 39 9E 01 00 03 67 74 64 00 00 00 2E 49
 41 4D 2C 0D 0A 47 43 49 2C 35 33 39 61 30 35 39 64 31 39 36 62 31 31 63 63 38 3
9 30 63 39 30 37 65 31 65 31 37 35 61 34 37 0D 0A 0D 0A

Related Commands

Command
Description

debug cdapi

Displays information about the call distributor application programming interface.

debug tsp

Displays information about the telephony service provider.

voice call debug

Allows configuration of the voice call debug output.


debug voip rtcp

To enable debugging for Real-Time Transport Control Protocol (RTCP) packets, use the debug voip rtcp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip rtcp {error | packet | session}

no debug voip rtcp

Syntax Description

error

Prints out a trace for error cases.

packet

Provides debug output for RTCP packets.

session

Provides all session debug information.


Defaults

Debugging for RTCP packets is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(2)T

This command was introduced.

12.2(8)T

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

12.2(11)T

This command was implemented on the Cisco AS5300, Cisco AS5400, and Cisco AS5850.

12.2(15)T

This command was implemented on the Cisco 1751 and Cisco 1760.


Usage Guidelines

When used without a keyword, this command turns on debugging for all events. This command severely impacts performance; use with caution.

Examples

The following example shows sample output for the debug voip rtcp command.

Router# debug voip rtcp

1w0d: voip_rtcp_create_session: callID=37, dstCallID=36 laddr=172.19.169.85, lp0
1w0d: voip_rtcp_get_cname: cname=0.0.0@172.19.169.85
1w0d: voip_rtcp_send_event: event=EV_NEW
1w0d: voip_rtcp_new: rtcp_interval=1893
Router#
1w0d: voip_rtcp_send_event: event=EV_STATS
1w0d: voip_rtcp_stats_req: rtcp_interval=3448
1w0d: voip_rtcp_stats_req:delay=45 lost_packets=0 rtt=0 
Router#
1w0d: recv:
1w0d: SR: ssrc=0x1272A94D sr_ntp_h=0xAF44E045 sr_ntp_l=0xA6CE39C sr_timestamp=02
1w0d: SDES: ssrc=0x1272A94D name=1 len=19 data=0.0.0@172.19.169.77
1w0d: rtcp_round_trip_delay: ssrc=0x1D86A955
Router#
1w0d: voip_rtcp_send_event: event=EV_STATS
1w0d: voip_rtcp_stats_req: rtcp_interval=6394
1w0d: voip_rtcp_stats_req:delay=40 lost_packets=0 rtt=0 
1w0d: recv:
1w0d: SR: ssrc=0x1272A94D sr_ntp_h=0xAF44E047 sr_ntp_l=0xFFB007F6 sr_timestamp=6
1w0d: SDES: ssrc=0x1272A94D name=1 len=19 data=0.0.0@172.19.169.77
1w0d: rtcp_round_trip_delay: ssrc=0x1D86A955
Router#
1w0d: voip_rtcp_remove_ccb
1w0d: voip_rtcp_send_event: event=EV_DESTROY
1w0d: voip_rtcp_destroy_idle
1w0d: voip_rtcp_close_session
1w0d: Cleaning up sess=62F95F58, sp=19544, dp=17130

debug voip r1tp

To enable debugging for Real-Time Transport Protocol (RTP) named event packets, use the debug voip rtp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug voip rtp {error | session [nse | multicast | conference | dtmf-relay | named-event] | packet remote-ip ipaddress remote-port portnum packetnum | packet callid idnum packetnum}

no debug voip rtp

Syntax Description

error

Prints out a trace for error cases.

session

Provides all session debug information. If used with a keyword, supplies more specific debug information according to the keywords used.

nse

(Optional) Provides debug information for named signaling events (NSEs).

multicast

(Optional) Provides debug information for multicast packets.

conference

(Optional) Provides debug information for conference packets.

dtmf-relay

(Optional) Provides debug information for dual-tone multifrequency (DTMF) packets.

named-event

(Optional) Provides debug information for named telephony event (NTE) packets.

packet remote-ip ipaddress remote-port portnum packetnum

Provides debug information for a remote IP address and port number. Using the packetnum argument specifies the number of packets to trace so that the display is not flooded.

packet callid idnum packetnum

Provides debug information for a specific call ID number (obtained by using the show voip rtp connections command). Using the packetnum argument specifies the number of packets to trace so that the display is not flooded.


Defaults

Debugging for RTP named event packets is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(2)XB

This command was introduced.

12.2(8)T

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

12.2(11)T

This command was implemented on the Cisco AS5300, Cisco AS5400, and Cisco AS5850.

12.2(15)T

This command was implemented on the Cisco 1751 and Cisco 1760.


Usage Guidelines

This command severely impacts performance and should be used only for single-call debug capture. We do not recommend using this command when using fax relay, because it can adversely affect fax relay.

Examples

The following example shows debugging output for the debug voip rtp session named-event command. The example is for a gateway that sends digits 1, 2, 3, then receives digits 9,8,7. The payload type, event ID, and additional packet payload are shown in each log.

The first three packets indicate the start of the tone (initial packet and two redundant). The last three packets indicate the end of the tone (initial packet and two redundant). The packets in between are refresh packets that are sent every 50 milliseconds (without redundancy).

Router# debug voip rtp session named-event

00:09:29:          Pt:99     Evt:1       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:03 01 90  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:03 03 20  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:03 04 B0  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:83 04 C8  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:83 04 C8  <<<Rcv>
00:09:29:          Pt:99     Evt:1       Pkt:83 04 C8  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 01 90  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 03 20  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:03 04 B0  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:83 05 18  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:83 05 18  <<<Rcv>
00:09:29:          Pt:99     Evt:2       Pkt:83 05 18  <<<Rcv>
00:09:29:          Pt:99     Evt:3       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:3       Pkt:03 00 00  <<<Rcv>
00:09:29:          Pt:99     Evt:3       Pkt:03 00 00  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:03 01 90  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:03 03 20  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:03 04 B0  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:03 06 40  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:83 06 80  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:83 06 80  <<<Rcv>
00:09:30:          Pt:99     Evt:3       Pkt:83 06 80  <<<Rcv>
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 01 90
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 03 20
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 04 B0
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:02 06 40
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:82 06 58
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:82 06 58
00:09:31:  <Snd>>> Pt:99     Evt:9       Pkt:82 06 58
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 01 90
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 03 20
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 04 B0
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:02 06 40
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:82 06 90
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:82 06 90
00:09:31:  <Snd>>> Pt:99     Evt:8       Pkt:82 06 90
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 00 00
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 01 90
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 03 20
00:09:31:  <Snd>>> Pt:99     Evt:7       Pkt:02 04 B0
00:09:32:  <Snd>>> Pt:99     Evt:7       Pkt:02 06 40
00:09:32:  <Snd>>> Pt:99     Evt:7       Pkt:82 06 58
00:09:32:  <Snd>>> Pt:99     Evt:7       Pkt:82 06 58
00:09:32:  <Snd>>> Pt:99     Evt:7       Pkt:82 06 58

debug voip settlement all

To enable debugging in all settlement areas, enter the debug voip settlement all EXEC command. To disable debugging output, use the no form of this command.

debug voip settlement all

no debug voip settlement all

Syntax Description

enter

Displays all entrances.

error

Displays information only if an error occurs.

exit

Displays all exits.

misc

Displays the details on the code flow of each transaction.

network

Displays network connectivity data.

security

Displays security and encryption errors.

transaction

Displays transaction information.


Defaults

Not enabled

Command Modes

EXEC

Command History

Release
Modification

12.0(4)XH1

This command was introduced.


Usage Guidelines

The debug voip settlement all EXEC command enables the following debug settlement commands:

debug voip settlement enter

debug voip settlement error

debug voip settlement exit

debug voip settlement security

debug voip settlement misc

debug voip settlement security

debug voip settlement transaction

debug voip settlement enter

To show all the settlement function entrances, enter the debug voip settlement enter command. To disable debugging output, use the no form of this command.

debug voip settlement enter

no debug voip settlement enter

Defaults

Not enabled

Command History

Release
Modification

12.0(4)XH1

This command was introduced.


Examples

00:43:40:OSP:ENTER:OSPPMimeMessageCreate()
00:43:40:OSP:ENTER:OSPPMimeMessageInit()
00:43:40:OSP:ENTER:OSPPMimeMessageSetContentAndLength()
00:43:40:OSP:ENTER:OSPPMimeMessageBuild()
00:43:40:OSP:ENTER:OSPPMimeDataFree()
00:43:40:OSP:ENTER:OSPPMimePartFree()
00:43:40:OSP:ENTER:OSPPMimePartFree()
00:43:40:OSP:ENTER:OSPPMsgInfoAssignRequestMsg()
00:43:40:OSP:ENTER:osppHttpSelectConnection
00:43:40:OSP:ENTER:OSPPSockCheckServicePoint() ospvConnected = <1>
00:43:40:OSP:ENTER:OSPPSockWaitTillReady()
00:43:40:OSP:ENTER:osppHttpBuildMsg()
00:43:40:OSP:ENTER:OSPPSSLSessionWrite()
00:43:40:OSP:ENTER:OSPPSockWrite()
00:43:40:OSP:ENTER:OSPPSockWaitTillReady()