-
Cisco IOS Debug Command Reference, Release 12.3 T
-
Debug: Introduction
-
Using Debug Commands
-
Conditionally Triggered Debugging
-
Debug Commands: debug aaa accounting through debug appn nof
-
Debug Commands: debug appn pc through debug bundle events
-
Debug Commands: debug cable env through debug ccfrf11 session
-
Debug Commands: debug cch323 through debug channel packets
-
Debug Commands: debug clns esis events through debug crypto pki messages
-
Debug Commands: debug crypto pki server through debug dlsw
-
Debug Commands: debug dmsp doc-to-fax through debug events
-
Debug Commands: debug fax dmsp through debug gprs radius
-
Debug Commands: debug h225 through debug ip drp
-
Debug Commands: debug ip dvmrp through debug ip mrouting limit
-
Debug Commands: debug ip msdp through debug ip scp
-
Debug Commands: debug ip sctp api through debug ipc rpc
-
Debug Commands: debug ipv6 cef drop through debug l2relay packets
-
Debug Commands: debug lane client through debug mmoip transfer
-
Debug Commands: debug modem through debug mpls ldp targeted-neighbors
-
Debug Commands: debug mpls ldp transport connections through debug mpls xtagatm vc
-
Debug Commands: debug mpoa client through debug oer master process
-
Debug Commands: debug packet through debug redundancy
-
Debug Commands: debug redundancy as5850 through debug rudpv1
-
Debug Commands: debug saa apm through debug source error
-
Debug Commands: debug source event through debug tacacs events
-
Debug Commands: debug tag-switching atm-cos through debug tag-switching xtagatm vc
-
Debug Commands: debug targ events through debug video vicm
-
Debug Commands: debug vlan packet through debug voip ipipgw
-
Debug Commands: debug voip ivr through debug vpm all
-
Debug Commands: debug vpm dsp through debug wlccp wds
-
Debug Commands: debug x25 through voice call debug
-
Debug: X.25 Cause and Diagnostic Codes
-
Debug: ISDN Switch Types, Codes, and Values
-
Table Of Contents
debug voip application stcapp all
debug voip application stcapp error
debug voip application stcapp events
debug voip application stcapp functions
debug voip application stcapp port
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 packetvLAN: IEEE 802.10 packet bearing vLAN ID 1000 received on interfaceFddi0 which is not configured to route/switch ID 1000.debug voice aaa asnl
To display debugging messages for gateway authentication, authorization, and accounting (AAA) Application Subscribe/Notify Layer (ASNL), use the debug voice aaa asnl command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voice aaa asnl
no debug voice aaa asnl
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging of AAA ASNL is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug voice aaa asnl command is a subset of the debug voice aaa command. It displays only events and error information related to the Accounting Server Connectivity Failure and Recovery Detection feature.
Examples
The following output is displayed when the debug voice aaa asnl command is entered:
Router# debug voice aaa asnl01:39:15:voip_aaa_accounting_pthru_send:Method List Name:ml1, aaa_av_list 0x62D69FCC, acct_rec_type 301:39:15:voip_aaa_search_mlist_node_by_name:Method List Name:ml1501:39:15:voip_aaa_accounting_pthru_send:Accounting Probe UID=1, adb = 629977A001:39:15:voip_aaa_accounting_pthru_send(1):increment num_acct_sent counterTable 302 describes the significant fields shown in the display.
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
Command Modes
Privileged EXEC
Usage Guidelines
This command is valid on the Cisco MC3810 only.
Examples
The debug voice all command output provides debug output for all the debug commands for the Voice Call Manager compiled into one display. For sample output of the individual commands, see the sample displays for the debug voice cp, debug voice eecm, debug voice protocol, debug voice signaling, and debug voice tdsm commands.
Related Commands
debug voice cp
To display debugging information for the Voice Call Processing State Machine, use the debug voice cp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voice cp [slot/port]
no debug voice cp [slot/port]
Syntax Description
slot/port
(Optional) The slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.
Command Modes
Privileged EXEC
Usage Guidelines
This command is valid on the Cisco MC3810 only.
Examples
The following is sample output from the debug voice cp command:
Router# debug voice cp 1/1Voice Call Processing State Machine debugging is on1/1: CPD( ), idle gets event seize_ind1/1: CPD( ), idle gets event dsp_ready1/1: CPD( ), idle ==> collect1/1: CPD(in), collect gets event digit1/1: CPD(in), collect gets event digit1/1: CPD(in), collect gets event digit1/1: CPD(in), collect gets event digit1/1: CPD(in), collect gets event addr_done1/1: CPD(in), collect ==> request1/1: CPD(in), request gets event call_proceeding1/1: CPD(in), request ==> in_wait_answer1/1: CPD(in), in_wait_answer gets event call_accept1/1: CPD(in), in_wait_answer gets event call_answered1/1: CPD(in), in_wait_answer ==> connected1/1: CPD(in), connected gets event peer_onhook1/1: CPD(in), connected ==> disconnect_wait1/1: CPD(in), disconnect_wait gets event idle_ind1/1: CPD(in), disconnect_wait ==> idleRelated Commands
debug voice dsp crash-dump
To display debugging information for the crash dump feature, use the debug voice dsp crash-dump command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voice dsp crash-dump [details | keepalives]
no debug voice dsp crash-dump [details | keepalives]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
DSP resource management (DSPRM) sends a debug message to the console that confirms that a crash dump file has been written to the specified destination.
CautionEnabling this debug feature adds extra time for the DSP to recover. The keepalive and detail keywords produce large volumes of output and should not be used except under the direction of a Cisco engineer.
You can also use the undebug all command to disable debugging output.
Examples
The following example shows a debug message that confirms that a crash dump file has been written to the specified destination. The stack is displayed on the console, and the DSPware version, complexity (image set), and Cisco IOS software version is also displayed.
Router# debug voice dsp crash-dump keepalives*Mar 8 03:42:19.505:Got back DSP status 0x12 0x0 for dsp 9 slot 1*Mar 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 10 slot 1*Mar 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 11 slot 1*Mar 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 12 slot 1*Mar 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 13 slot 1*Mar 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 14 slot 1*Mar 8 03:42:21.509:status cleared done, dsp 9 slot 1*Mar 8 03:42:21.513:status cleared done, dsp 10 slot 1*Mar 8 03:42:21.513:status cleared done, dsp 11 slot 1*Mar 8 03:42:21.513:status cleared done, dsp 12 slot 1*Mar 8 03:42:21.513:status cleared done, dsp 13 slot 1*Mar 8 03:42:21.513:status cleared done, dsp 14 slot 1
The following command disables all the debugging output on the screen to stop the output from the debug voice dsp crash-dump keepalives command:
Router# undebug allThe following example shows the debug voice dsp crash-dump details command entry when no DSP crash is present. There is no debugging output until there is one DSP crash. When the crash dump feature is turned on, the detailed debug messages are displayed.
Router# debug voice dsp crash-dump detailsRelated Commands
show voice dsp crash-dump
Displays voice dsp crash dump information.
voice dsp crash-dump
Enables the crash dump feature and specifies the destination file and the file limit.
debug voice eecm
To display debugging information for the Voice End-to-End Call Manager, use the debug voice eecm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voice eecm [slot/port]
no debug voice eecm [slot/port]
Syntax Description
slot/port
(Optional) Slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.
Command Modes
Privileged EXEC
Usage Guidelines
This command is valid on the Cisco MC3810 only.
Examples
The following is sample output from the debug voice eecm command:
Router# debug voice eecm1/1: EECM(in), ST_NULL EV_ALLOC_DSP1/1: EECM(in), ST_DIGIT_COLLECT EV_PARSE_DIGIT 31/1: EECM(in), ST_DIGIT_COLLECT EV_PARSE_DIGIT 71/1: EECM(in), ST_DIGIT_COLLECT EV_PARSE_DIGIT 01/1: EECM(in), ST_DIGIT_COLLECT EV_PARSE_DIGIT 21/1: EECM(in), ST_ADDRESS_DONE EV_OUT_SETUP-1/-1: EECM(out), ST_NULL EV_IN_SETUP1/1: EECM(in), ST_OUT_REQUEST EV_IN_PROCEED1/2: EECM(out), ST_SEIZE EV_ALLOC_DSP1/2: EECM(out), ST_SEIZE EV_OUT_ALERT1/1: EECM(in), ST_OUT_REQUEST EV_IN_ALERT1/1: EECM(in), ST_OUT_REQUEST EV_OUT_ALERT_ACK1/2 EECM(out), ST_IN_PENDING EV_OUT_CONNECT1/1: EECM(in), ST_WAIT_FOR_ANSWER EV_IN_CONNECT1/2: EECM(out), ST_ACTIVE EV_OUT_REL1/1: EECM(in), ST_ACTIVE EV_IN_REL1/1: EECM(in), ST_DISCONN_PENDING EV_OUT_REL_ACKRelated Commands
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
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Disable console logging and use buffered logging before using the debug voice enum command. Using the debug voice enum command generates a large volume of debugs, which can affect router performance.
Examples
The following is sample output from the debug voice enum detail command. The output shows the match number as 5108891234, ENUM table as 10. Rule 1 in table 10 matched the pattern and after applying the replacement rule, the resulting string is 5108891234. The ENUM query is sent out for the domain 4.3.2.1.9.8.8.0.1.5.e164.cisco.com. The output then shows the matching Naming Authority Pointer (NAPTR) records obtained in the response. The records are then processed and the final URLs (contact lists) are shown toward the end.
Router# debug voice enum detailenum_resolve_domain:match_num 5108891234 table_indx 10enum_resolve_domain:rule 1 result string 5108891234generate_enum_search_string :search string 4.3.2.1.9.8.8.0.1.5.e164.cisco.comenum_dns_query:name = 4.3.2.1.9.8.8.0.1.5.e164.cisco.com type = 35, ns_server = 0order 100 pref 10 service sip+E2U flag Uregexp /^.*$/sip:5108891234@1.8.50.14/ replacementorder 200 pref 10 service h323+E2U flag Uregexp /^.*$/h323:5555@1.5.1.1/ replacementnum_elem = 2NAPTR Record :order 100 pref 10 service sip+E2Uflags U regexp /^.*$/sip:5108891234@1.8.50.14/replacementNAPTR Record :order 200 pref 10 service h323+E2Uflags U regexp /^.*$/h323:5555@1.5.1.1/replacementdecode_naptr_record :re_string ^.*$decode_naptr_record :re_substitution_string sip:5108891234@1.8.50.14decode_naptr_record :re_flags_stringU_FLAG case, stopping querynew_e164_user sip:5108891234@1.8.50.14decode_naptr_record :re_string ^.*$decode_naptr_retahoe13#cord :re_substitution_string h323:5555@1.5.1.1decode_naptr_record :re_flags_stringU_FLAG case, stopping querynew_e164_user h323:5555@1.5.1.1contact_list :sip:5108891234@1.8.50.14contact_list :h323:5555@1.5.1.1enum_resolve_domain:contact_list 64558450A 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 summaryenum_resolve_domain:match_num 5108891234 table_indx 10enum_resolve_domain:rule 1 result string 5108891234Table 303 provides an alphabetical listing of the debug voice enum command fields and a description of each field.
Related Commands
debug voice protocol
To display debugging information for the Voice Line protocol State machine, use the debug voice protocol command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voice protocol [slot/port]
no debug voice protocol [slot/port]
Syntax Description
slot/port
(Optional) Slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.
Command Modes
Privileged EXEC
Command History
This command is valid on the Cisco MC3810 only.
Usage Guidelines
In the debugging display, the following abbreviations are used for the different signaling protocols:
•
•
•
•
•
Examples
The following is sample output from the debug voice protocol command:
Router# debug voice protocolVoice Line protocol State machine debugging is on1/1: LFXS( ), idle gets event offhook1/1: LFXS( ), idle ==> seize1/1: LFXS(in), seize gets event ready1/1: LFXS(in), seize ==> dial_tone1/1: LFXS(in), dial_tone gets event digit1/1: LFXS(in), dial_tone ==> collect1/1: LFXS(in), collect gets event digit1/1: LFXS(in), collect gets event digit1/1: LFXS(in), collect gets event digit1/1: LFXS(in), collect gets event addr_done1/1: LFXS(in), collect ==> call_progress1/2: LFXS( ), idle gets event seize1/2: LFXS( ), idle ==> ringing1/2: LFXS(out), ringing gets event dial_tone1/2: LFXS(out), ringing gets event offhook1/2: LFXS(out), ringing ==> connected1/1: LFXS(in), call_progress gets event answer1/1: LFXS(in), call_progress ==> connected1/2: LFXS(out), connected gets event onhook1/2: LFXS(out), connected ==> disconnect_wait1/2: LFXS(out), disconnected_wait gets event disconnect1/2: LFXS(out), disconnect_wait ==> cpc1/1: LFXS(in), connected gets event disconnect1/2: LFXS(out), connected ==> cpc1/2: LFXS(out), cpc gets event offhook1/2: LFXS(out), cpc gets event timer11/2: LFXS(out), cpc ==> cpc_recover1/2: LFXS(out), cpc gets event timer11/2: LFXS(out), cpc_recover ==> offhook_wait1/1: LFXS(in), offhook_wait gets event onhook1/1: LFXS(in), offhook_wait ==> idle1/2: LFXS(out), offhook_wait gets event onhook1/2: LFXS(out), offhook_wait ==> idleRelated Commands
debug voice signaling
To display debugging information for the voice port signaling, use the debug voice signaling command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voice signaling [slot/port]
no debug voice signaling [slot/port]
Syntax Description
slot/port
(Optional) Slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.
Command Modes
Privileged EXEC
Usage Guidelines
This command is valid on the Cisco MC3810 only.
Examples
The following is sample output from the debug voice signaling command:
Router# debug voice signaling1/1: TIU, report_local_hook=11/2: TIU, set ring cadence=11/2: TIU, ringer on1/2: TIU, ringer off1/2: TIU, ringer on1/2: TIU, report_local_hook=11/2: TIU, turning off ringer due to SW ringtrip1/2: TIU, ringer off1/2: TIU, set ring cadence=01/2: TIU, ringer off1/2: TIU, set reverse battery=11/2: TIU, set reverse battery=11/1: TIU, report_local_hook=01/2: TIU, set reverse battery=01/2: TIU, set loop disabled=11/1: TIU, set reverse battery=01/1: TIU, set loop disabled=11/2: TIU, report_local_hook=11/1: TIU, report_lead_gnd grounded=11/1: TIU, report_lead_gnd grounded=01/2: TIU, set loop disabled=01/1: TIU, set loop disabled=01/1: TIU, report_local_hook=01/2: TIU, report_local_hook=01/1: TIU, report_local_hook=11/2: TIU, report_local_hook=11/1: TIU, report_local_hook=01/2: TIU, report_local_hook=01/1: TIU, set reverse battery=01/2: TIU, set reverse battery=0Related Commands
debug voice source-group
To view voice source group information, use the debug voice source-group command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voice source-group
no debug voice source-group
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
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=100:30:49:SIPG:sipg_find_key - hashkey=1,idstring=0x63BE1C28Table 304 describes the significant fields shown in the display.
Related Commands
debug voice statistics
To enable debugging of voice statistics, use the debug voice statistics command in privileged EXEC mode. To disable the debugging, use the no form of this command.
debug voice statistics {csr | core | accounting}
no debug voice statistics {csr | core | accounting}
Syntax Description
csr
Signaling voice call statistics records collection is debugged.
core
Generic statistics collection is debugged.
accounting
Voice accounting CSR collection is debugged.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows the collection of records that is occurring in between intervals:
Router# debug voice statistics accountingvstats_timer_handle_interval_event():Between Intervals!04:52:37: vstats_acct_interval_end: interval_tag = 404:52:37: vstats_acct_interval_end: pushing out, tag=304:52:37: vstats_acct_clean_history_stats:04:52:37: vstats_acct_clean_history_stats: stats (tag=3) not to be deleted04:52:37: vstats_acct_clean_history_stats: stats (tag=2) not to be deleted04:52:37: vstats_acct_create_empty_stats:04:52:37: vstats_acct_create_new_rec_list:04:52:37: vstats_acct_create_new_rec_list: add acct rec: methodlist=h323, acct-criteria=204:52:37: vstats_acct_create_new_rec:04:52:37: vstats_acct_add_rec_entry:04:52:37: vstats_acct_add_stats_entry:04:52:37: vstat_push_driver_file_open():Cannot openftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z.errno=65540=Unknown error 65540vstat_push_drv_activate_ftp_file_tx():open file(ftp://sgcp:sgcp@jeremy-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z)=(ftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z)failed!vstats_push_api_push_formatted_text():Start CMD error!The following example shows a voice call going through the gateway:
Router# debug voice statistics csr04:55:07: EM: Notify the producer not to produce04:55:07: RADIUS(00000019): Storing nasport 0 in rad_db04:55:07: RADIUS(00000019): Config NAS IP: 0.0.0.004:55:07: RADIUS(00000019): sending04:55:07: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.20304:55:07: RADIUS(00000019): Send Accounting-Request to 1.6.10.203:1646 id 21645/49,len 49604:55:07: RADIUS: authenticator C5 B8 AA 2E C3 AF 02 93 - 45 0B AE E5 B6 B2 99 1F04:55:07: RADIUS: Acct-Session-Id [44] 10 "00000020"04:55:07: RADIUS: Vendor, Cisco [26] 5704:55:07: RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:30.994 UTCThu Feb 13 2003"04:55:07: RADIUS: Vendor, Cisco [26] 2704:55:07: RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW."04:55:07: RADIUS: Vendor, Cisco [26] 5604:55:07: RADIUS: Conf-Id [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002B935C142"04:55:07: RADIUS: Vendor, Cisco [26] 3104:55:07: RADIUS: h323-call-origin [26] 25 "h323-call-origin=answer"04:55:07: RADIUS: Vendor, Cisco [26] 3204:55:07: RADIUS: h323-call-type [27] 26 "h323-call-type=Telephony"04:55:07: RADIUS: Vendor, Cisco [26] 6504:55:07: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7800E0002 B935C142"04:55:07: RADIUS: Vendor, Cisco [26] 3004:55:07: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"04:55:07: RADIUS: Vendor, Cisco [26] 3504:55:07: RADIUS: Cisco AVpair [1] 29 "gw-rxd-cdn=ton:0,npi:0,#:11"04:55:07: RADIUS: Vendor, Cisco [26] 3204:55:07: RADIUS: Cisco AVpair [1] 26 "calling-party-category=9"04:55:07: RADIUS: Vendor, Cisco [26] 3304:55:07: RADIUS: Cisco AVpair [1] 27 "transmission-medium-req=0"04:55:07: RADIUS: User-Name [1] 4 "22"04:55:07: RADIUS: Acct-Status-Type [40] 6 Start [1]04:55:07: RADIUS: NAS-Port-Type [61] 6 Async [0]04:55:07: RADIUS: Vendor, Cisco [26] 2004:55:07: RADIUS: cisco-nas-port [2] 14 "ISDN 6/0:D:1"04:55:07: RADIUS: NAS-Port [5] 6 004:55:07: RADIUS: Calling-Station-Id [31] 4 "22"04:55:07: RADIUS: Called-Station-Id [30] 4 "11"04:55:07: RADIUS: Service-Type [6] 6 Login [1]04:55:07: RADIUS: NAS-IP-Address [4] 6 1.6.43.10104:55:07: RADIUS: Acct-Delay-Time [41] 6 004:55:07: RADIUS(0000001A): Config NAS IP: 0.0.0.004:55:07: RADIUS(0000001A): sending04:55:07: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.20304:55:07: RADIUS(0000001A): Send Accounting-Request to 1.6.10.203:1646 id 21645/50, len42704:55:07: RADIUS: authenticator E4 98 06 8C 48 63 4F AA - 56 4F 40 12 33 F0 F5 9904:55:07: RADIUS: Acct-Session-Id [44] 10 "00000021"04:55:07: RADIUS: Vendor, Cisco [26] 5704:55:07: RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:31.006 UTCThu Feb 13 2003"04:55:07: RADIUS: Vendor, Cisco [26] 2704:55:07: RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW."04:55:07: RADIUS: Vendor, Cisco [26] 5604:55:07: RADIUS: Conf-Id [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002B935C142"04:55:07: RADIUS: Vendor, Cisco [26] 3404:55:07: RADIUS: h323-call-origin [26] 28 "h323-call-origin=originate"04:55:07: RADIUS: Vendor, Cisco [26] 2704:55:07: RADIUS: h323-call-type [27] 21 "h323-call-type=VoIP"04:55:07: RADIUS: Vendor, Cisco [26] 6504:55:07: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7800E0002 B935C142"04:55:07: RADIUS: Vendor, Cisco [26] 3004:55:07: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"04:55:07: RADIUS: Vendor, Cisco [26] 3004:55:07: RADIUS: Cisco AVpair [1] 24 "session-protocol=cisco"04:55:07: RADIUS: Vendor, Cisco [26] 3504:55:07: RADIUS: Cisco AVpair [1] 29 "gw-rxd-cdn=ton:0,npi:0,#:11"04:55:07: RADIUS: User-Name [1] 4 "22"04:55:07: RADIUS: Acct-Status-Type [40] 6 Start [1]04:55:07: RADIUS: Calling-Station-Id [31] 4 "22"04:55:07: RADIUS: Called-Station-Id [30] 4 "11"04:55:07: RADIUS: Service-Type [6] 6 Login [1]04:55:07: RADIUS: NAS-IP-Address [4] 6 1.6.43.10104:55:07: RADIUS: Acct-Delay-Time [41] 6 004:55:07: EM: No consumer registered for event type NEWINFO04:55:07: EM: Notify the producer not to produce04:55:07: EM: No consumer registered for event type NEWINFO04:55:07: EM: Notify the producer not to produce04:55:08: RADIUS: no sg in radius-timers: ctx 0x65BAB1BC sg 0x000004:55:08: RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/5004:55:08: RADIUS: acct-delay-time for 403963FC (at 403965A1) now 104:55:09: RADIUS: no sg in radius-timers: ctx 0x65ADB8EC sg 0x000004:55:09: RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/4904:55:09: RADIUS: acct-delay-time for 40389BFC (at 40389DE6) now 104:55:10: RADIUS: no sg in radius-timers: ctx 0x65BAB1BC sg 0x000004:55:10: RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/5104:55:10: RADIUS: acct-delay-time for 403963FC (at 403965A1) now 204:55:10: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.8.159.10504:55:10: RADIUS: Received from id 21645/53 1.8.159.105:1645, Accounting-response, len 2004:55:10: RADIUS: authenticator 57 EF DD 90 0F 88 76 EA - A5 3D A7 44 0D 90 66 1604:55:10: vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x104:55:10: acct_rsp_status=1 callid= 26, incoming=0, leg=204:55:10: vstats_acct_rsp_handler: last acct msg not sent yet. methodlist: h32304:55:10: RADIUS: no sg in radius-timers: ctx 0x65ADB8EC sg 0x000004:55:10: RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/5204:55:10: RADIUS: acct-delay-time for 40389BFC (at 40389DE6) now 204:55:10: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.8.159.10504:55:10: RADIUS: Received from id 21645/54 1.8.159.105:1645, Accounting-response, len 2004:55:10: RADIUS: authenticator 97 88 6C BA DA 22 E7 5E - 73 EC 21 C6 36 1B 93 1804:55:10: vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x104:55:10: acct_rsp_status=callid= 25, incoming=1, leg=104:55:10: vstats_acct_rsp_handler: last acct msg not sent yet. methodlist: h32304:55:13: RADIUS(0000001A): Config NAS IP: 0.0.0.004:55:13: RADIUS(0000001A): sending04:55:13: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.20304:55:13: RADIUS(0000001A): Send Accounting-Request to 1.6.10.203:1646 id 21645/55, len88504:55:13: RADIUS: authenticator F8 4F F1 30 7E 8B 5B 46 - EF AE 17 2D 5C BA 36 E504:55:13: RADIUS: Acct-Session-Id [44] 10 "00000021"04:55:13: RADIUS: Vendor, Cisco [26] 5704:55:13: RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:31.006 UTCThu Feb 13 2003"04:55:13: RADIUS: Vendor, Cisco [26] 2704:55:13: RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW."04:55:13: RADIUS: Vendor, Cisco [26] 5604:55:13: RADIUS: Conf-Id [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002B935C142"04:55:13: RADIUS: Vendor, Cisco [26] 3404:55:13: RADIUS: h323-call-origin [26] 28 "h323-call-origin=originate"04:55:13: RADIUS: Vendor, Cisco [26] 2704:55:13: RADIUS: h323-call-type [27] 21 "h323-call-type=VoIP"04:55:13: RADIUS: Vendor, Cisco [26] 6504:55:13: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7800E0002 B935C142"04:55:13: RADIUS: Vendor, Cisco [26] 3004:55:13: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"04:55:13: RADIUS: Vendor, Cisco [26] 3004:55:13: RADIUS: Cisco AVpair [1] 24 "session-protocol=cisco"04:55:13: RADIUS: Vendor, Cisco [26] 3504:55:13: RADIUS: Cisco AVpair [1] 29 "gw-rxd-cdn=ton:0,npi:0,#:11"04:55:13: RADIUS: Vendor, Cisco [26] 5904:55:13: RADIUS: h323-connect-time [28] 53 "h323-connect-time=*16:22:31.046 UTCThu Feb 13 2003"04:55:13: RADIUS: Acct-Input-Octets [42] 6 224104:55:13: RADIUS: Acct-Output-Octets [43] 6 8104:55:13: RADIUS: Acct-Input-Packets [47] 6 11304:55:13: RADIUS: Acct-Output-Packets [48] 6 504:55:13: RADIUS: Acct-Session-Time [46] 6 504:55:13: RADIUS: Vendor, Cisco [26] 6204:55:13: RADIUS: h323-disconnect-tim[29] 56 "h323-disconnect-time=*16:22:36.070 UTCThu Feb 13 2003"04:55:13: RADIUS: Vendor, Cisco [26] 3204:55:13: RADIUS: h323-disconnect-cau[30] 26 "h323-disconnect-cause=10"04:55:13: RADIUS: Vendor, Cisco [26] 3804:55:13: RADIUS: h323-remote-address[23] 32 "h323-remote-address=14.0.0.110"04:55:13: RADIUS: Vendor, Cisco [26] 2404:55:13: RADIUS: Cisco AVpair [1] 18 "release-source=1"04:55:13: RADIUS: Vendor, Cisco [26] 2904:55:13: RADIUS: h323-voice-quality [31] 23 "h323-voice-quality=-1"04:55:13: RADIUS: Vendor, Cisco [26] 5704:55:13: RADIUS: Cisco AVpair [1] 51 "alert-timepoint=*16:22:31.030 UTCThu Feb 13 2003"04:55:13: RADIUS: Vendor, Cisco [26] 3904:55:13: RADIUS: Cisco AVpair [1] 33 "remote-media-address=14.0.0.110"04:55:13: RADIUS: Vendor, Cisco [26] 4404:55:13: RADIUS: Cisco AVpair [1] 38 "gw-final-xlated-cdn=ton:0,npi:0,#:11"04:55:13: RADIUS: Vendor, Cisco [26] 4404:55:13: RADIUS: Cisco AVpair [1] 38 "gw-final-xlated-cgn=ton:0,npi:1,#:22"04:55:13: RADIUS: User-Name [1] 4 "22"04:55:13: RADIUS: Acct-Status-Type [40] 6 Stop [2]04:55:13: RADIUS: Calling-Station-Id [31] 4 "22"04:55:13: RADIUS: Called-Station-Id [30] 4 "11"04:55:13: RADIUS: Service-Type [6] 6 Login [1]04:55:13: RADIUS: NAS-IP-Address [4] 6 1.6.43.10104:55:13: RADIUS: Acct-Delay-Time [41] 6 004:55:13: RADIUS(00000019): Using existing nas_port 004:55:13: RADIUS(00000019):Config NAS IP: 0.0.0.004:55:13: RADIUS(00000019):sending04:55:13: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.20304:55:13: RADIUS(00000019): Send Accounting-Request to 1.6.10.203:1646 id 21645/56, len76604:55:13: RADIUS: authenticator 61 60 EB 92 29 5C DE B4 - CE 40 1C AB E3 A1 C8 F704:55:13: RADIUS: Acct-Session-Id [44] 10 "00000020"04:55:13: RADIUS: Vendor, Cisco [26] 5704:55:13: RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:30.994 UTC ThuFeb 13 2003"04:55:13: RADIUS: Vendor, Cisco [26] 2704:55:13: RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW."04:55:13: RADIUS: Vendor, Cisco [26] 5604:55:13: RADIUS: Conf-Id [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002B935C142"04:55:13: RADIUS: Vendor, Cisco [26] 3104:55:13: RADIUS: h323-call-origin [26] 25 "h323-call-origin=answer"04:55:13: RADIUS: Vendor, Cisco [26] 3204:55:13: RADIUS: h323-call-type [27] 26 "h323-call-type=Telephony"04:55:13: RADIUS: Vendor, Cisco [26] 6504:55:13: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7800E0002 B935C142"04:55:13: RADIUS: Vendor, Cisco [26] 3004:55:13: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"04:55:13: RADIUS: Vendor, Cisco [26] 3504:55:13: RADIUS: Cisco AVpair [1] 29 "gw-rxd-cdn=ton:0,npi:0,#:11"04:55:13: RADIUS: Vendor, Cisco [26] 3204:55:13: RADIUS: Cisco AVpair [1] 26 "calling-party-category=9"04:55:13: RADIUS: Vendor, Cisco [26] 3304:55:13: RADIUS: Cisco AVpair [1] 27 "transmission-medium-req=0"04:55:13: RADIUS: Vendor, Cisco [26] 5904:55:13: RADIUS: h323-connect-time [28] 53 "h323-connect-time=*16:22:31.046 UTC ThuFeb 13 2003"04:55:13: RADIUS: Acct-Input-Octets [42] 6 8104:55:13: RADIUS: Acct-Output-Octets [43] 6 224104:55:13: RADIUS: Acct-Input-Packets [47] 6 504:55:13: RADIUS: Acct-Output-Packets [48] 6 11304:55:13: RADIUS: Acct-Session-Time [46] 6 504:55:13: RADIUS: Vendor, Cisco [26] 6204:55:13: RADIUS: h323-disconnect-tim[29] 56 "h323-disconnect-time=*16:22:36.064 UTCThu Feb 13 2003"04:55:13: RADIUS: Vendor, Cisco [26] 3204:55:13: RADIUS: h323-disconnect-cau[30] 26 "h323-disconnect-cause=10"04:55:13: RADIUS: Vendor, Cisco [26] 3504:55:13: RADIUS: Cisco AVpair [1] 29 "h323-ivr-out=Tariff:Unknown"04:55:13: RADIUS: Vendor, Cisco [26] 2404:55:13: RADIUS: Cisco AVpair [1] 18 "release-source=1"04:55:13: RADIUS: Vendor, Cisco [26] 2804:55:13: RADIUS: h323-voice-quality [31] 22 "h323-voice-quality=0"04:55:13: RADIUS: User-Name [1] 4 "22"04:55:13: RADIUS: Acct-Status-Type [40] 6 Stop [2]04:55:13: RADIUS: NAS-Port-Type [61] 6 Async [0]04:55:13: RADIUS: Vendor, Cisco [26] 2004:55:13: RADIUS: cisco-nas-port [2] 14 "ISDN 6/0:D:1"04:55:13: RADIUS: NAS-Port [5] 6 004:55:13: RADIUS: Calling-Station-Id [31] 4 "22"04:55:13: RADIUS: Called-Station-Id [30] 4 "11"04:55:13: RADIUS: Service-Type [6] 6 Login [1]04:55:13: RADIUS: NAS-IP-Addres [4] 6 1.6.43.10104:55:13: RADIUS: Acct-Delay-Time [41] 6 004:55:14: RADIUS: no sg in radius-timers: ctx 0x65BAB070 sg 0x000004:55:14: RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/5504:55:14: RADIUS: acct-delay-time for 40553934 (at 40553CA3) now 104:55:14: RADIUS: no sg in radius-timers: ctx 0x65BA8284 sg 0x000004:55:14: RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/5604:55:14: RADIUS: acct-delay-time for 405546C4 (at 405549BC) now 104:55:15: RADIUS: no sg in radius-timers: ctx 0x65BAB070 sg 0x000004:55:15: RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/5704:55:15: RADIUS: acct-delay-time for 40553934 (at 40553CA3) now 204:55:15: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.8.159.10504:55:15: RADIUS: no sg in radius-timers: ctx 0x65BA8284 sg 0x000004:55:15: RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/5804:55:15: RADIUS: acct-delay-time for 405546C4 (at 405549BC) now 204:55:15: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 10.8.159.10504:55:15: RADIUS: Received from id 21645/59 1.8.159.105:1645, Accounting-response, len 2004:55:15: RADIUS: authenticator B1 C4 5E FC DB FA 74 A4 - 05 E2 34 52 1A 11 26 0604:55:15: vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x404:55:15: acct_rsp_status=1 callid= 26, incoming=0, leg=204:55:15: vstats_acct_rsp_handler: increment since-reset counter04:55:15: vstats_acct_rsp_handler: increment interval counter04:55:15: RADIUS: Received from id 21645/60 10.8.159.105:1645, Accounting-response, len 2004:55:15: RADIUS: authenticator 0E 70 74 2F E5 D8 EE 98 - B9 C0 DA 66 74 ED 84 7704:55:15: vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x404:55:15: acct_rsp_status=1 callid= 25, incoming=1, leg=104:55:15: vstats_acct_rsp_handler: increment since-reset counter04:55:15: vstats_acct_rsp_handler: increment interval counterThe following example shows the collection of records that is in between intervals:
Router# debug voice statistics accountingTranslating "abc-pc"...domain server (255.255.255.255)vstats_timer_handle_interval_event():Between Intervals!04:57:37: vstats_acct_interval_end: interval_tag = 504:57:37: vstats_acct_interval_end: pushing out, tag=404:57:37: vstats_acct_clean_history_stats:04:57:37: vstats_acct_clean_history_stats: stats (tag=4) not to be deleted04:57:37: vstats_acct_clean_history_stats: stats (tag=3) not to be deleted04:57:37: vstats_acct_clean_history_stats: stats (tag=2) not to be deleted04:57:37: vstats_acct_create_empty_stats:04:57:37: vstats_acct_create_new_rec_list:04:57:37: vstats_acct_create_new_rec_list: add acct rec: methodlist=h323, acct-criteria=204:57:37: vstats_acct_create_new_rec:04:57:37: vstats_acct_add_rec_entry:04:57:37: vstats_acct_add_stats_entry:04:57:37: vstat_push_driver_file_open():Can not openftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162500Z.errno=65540=Unknown error 65540vstat_push_drv_activate_ftp_file_tx():open file(ftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162500Z)=(ftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162500Z) failed!vstats_push_api_push_formatted_text():Start CMD error!Related Commands
debug voice tdsm
To display debugging information for the voice tandem switch, use the debug voice tdsm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voice tdsm [slot/port]
no debug voice tdsm [slot/port]
Syntax Description
slot/port
(Optional) Slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.
Command Modes
Privileged EXEC
Usage Guidelines
This command is valid on the Cisco MC3810 only.
Examples
The following is sample output from the debug voice tdsm command:
Router# debug voice tdsmVoice tandem switch debugging is on-1/-1: TDSM(out), ref= -1, state NULL gets event OUT_SETUP1/1: TDSM(in), ref=6, state CALL_INITIATED gets event IN_CALLPROC1/1: TDSM(in), ref=6, state OUTG_CALLPROC gets event IN_ALERTING1/1: TDSM(in), ref=6, state CALL_DELIVERED gets event IN_CONNECT1/1: TDSM(out),ref=6, state CALL_ACTIVE send out conn. ack1/1: TDSM(out),ref=6, state CALL_ACTIVE send out release, cause LOCAL_ONHOOK1/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_ALERTING1/1: TDSM(out),ref=6, state CALL_RECEIVED gets event OUT_CONNECT1/1: TDSM(in), ref-6, state CONNECT_REQ gets event IN_CONN_ACK1/1: TDSM(out),ref-6, state CALL_ACTIVE send out release, cause LOCAL_ONHOOK1/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_SETUP1/1: TDSM(in), ref=7, state CALL_INITIATED gets event IN_CALLPROC1/1: TDSM(in), ref=7, state OUTG_CALLPROC gets event IN_ALERTING1/1: TDSM(in), ref=7, state CALL_DELIVERED gets event IN_CONNECT1/1: TDSM(out),ref=7, state CALL_ACTIVE send out conn.ack1/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_ALERTING1/1: TDSM(out),ref=7. state CALL_RECEIVED gets event OUT_CONNECT1/1: TDSM(in), ref=7, state CONNECT_REQ gets event IN_CONN_ACK1/1: TDSM(in), ref=7, state CALL_ACTIVE send out release, cause LOCAL_ONHOOK1/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_SETUP1/1: TDSM(in), ref=8, state CALL_INITIATED gets event IN_CALLPROC1/1: TDSM(in), ref=8, state OUTG_CALLPROC gets event IN_ALERTINGbug allRelated Commands
debug voice translation
To view voice translation rule information, use the debug voice translation command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voice translation
no debug voice translation
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Disable console logging and use buffered logging before using the debug voice translation command. Using the debug voice translation command generates a large volume of debugs, which can affect router performance.
Examples
Sample output from the debug voice translation command is shown below. The output shows the details of the original number following "regxrule_profile_translate".
Following "regxrule_profile_match", the output shows that rule 1 in the translation rule 1001 was a match; then the details of the SED substitution are shown.
Then the output shows the details of the translated number following "regxrule_profile_translate".
In this example, because there was no called number or redirect number translation configured on the translation profile, corresponding errors were generated with a message that no match was found.
Following "regxrule_dp_translate", the output indicates that there is no translation profile for outgoing direction, then it prints the numbers sent to the outgoing SPI.
Router#00:51:56:regxrule_get_profile_from_trunkgroup:Voice port 0x64143DA8 does not belong to any trunk group00:51:56:regxrule_get_profile_from_trunkgroup:Voice port 0x64143DA8 does not belong to any trunk group00:51:56:regxrule_stack_pop_RegXruleNumInfo:stack=0x63DECAF4; count=100:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=000:51:56:regxrule_profile_translate:number=4088880101 type=unknown plan=unknown numbertype=calling00:51:56:regxrule_profile_match:Matched with rule 1 in ruleset 100100:51:56:regxrule_profile_match:Matched with rule 1 in ruleset 100100:51:56:sed_subst:Successful substitution; pattern=4088880101 matchPattern=^.* replacePattern=5551212 replaced pattern=555121200:51:56:regxrule_subst_num_type:Match Type = none, Replace Type = none Input Type = unknown00:51:56:regxrule_subst_num_plan:Match Plan = none, Replace Plan = none Input Plan = unknown00:51:56:regxrule_profile_translate:xlt_number=5551212 xlt_type=unknown xlt_plan=unknown00:51:56:regxrule_profile_translate:number= type=UNKNOWN plan=UNKNOWN numbertype=redirect-called00:51:56:regxrule_get_RegXrule:Invalid translation ruleset tag=000:51:56:regxrule_profile_match:Error:ruleset for redirect-called number not found00:51:56:regxrule_profile_translate:No match:number= type=UNKNOWN plan=UNKNOWN00:51:56:regxrule_profile_translate:number=5108880101 type=unknown plan=unknown numbertype=called00:51:56:regxrule_get_RegXrule:Invalid translation ruleset tag=000:51:56:regxrule_profile_match:Error:ruleset for called number not found00:51:56:regxrule_profile_translate:No match:number=5108880101 type=unknown plan=unknown00:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=100:51:56:regxrule_dp_translate:No profile found in peer 5108888 for outgoing direction00:51:56:regxrule_dp_translate:calling_number=5551212 calling_octet=0x0called_number=5108880101 called_octet=0x80redirect_number= redirect_type=4294967295 redirect_plan=429496729500:51:56:regxrule_stack_pop_RegXruleNumInfo:stack=0x63DECAF4; count=200:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=1Table 305 provides an alphabetical listing of the debug voice translation command fields and a description of each field.
Related Commands
debug voice uri
To display debugging messages for uniform resource identifier (URI) voice classes, use the debug voice uri command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voice uri
no debug voice uri
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to see which URI voice class and dial peer is matched for a Session Initiation Protocol (SIP) or telephone (TEL) URI.
Examples
The following examples show output from the debug voice uri command. Comments are imbedded in the examples.
Router# debug voice uriOutput Showing Failed Match of Voice URI Class
The following output displays when an outbound dial peer match fails for the URL sip:9991234@sip.tgw.com?Subject=sip_e164_headers_plus.tcl&AccountInfo=12345&Priority=Urgent
*Jul 11 05:20:44.759:vuri_match_class:tag (767)The first dial peer in the list is 767, which contains the destination uri 767 command. 767 is a TELURI class, so it does not match the above URL.
*Jul 11 05:20:44.759:vuri_match_class:tag (766)The next dial peer, 766, contains the destination uri 766 command.
*Jul 11 05:20:44.759:vuri_match_class_sip:sip:9991234@sip.tgw.com?Subject=sip_e164_headers_plus.tc l&AccountInfo=12345&Priority=Urgent did not match pattern766 is a SIP URI class and contains only the pattern command. The regex does not match the pattern, so there is no match.
*Jul 11 05:20:44.759:vuri_match_class:tag (999)The next dial peer, 999, contains the destination uri 999 command.
*Jul 11 05:20:44.759:vuri_match_class_sip:Match with phone context*Jul 11 05:20:44.759:vuri_match_class_sip:input ()If the phone context command is not present in the URI class, it is skipped.
*Jul 11 05:20:44.759:vuri_match_class_sip:Match with host*Jul 11 05:20:44.759:vuri_match_class_sip:input (sip.tgw.com)If the host command is not present in the URI class, it is skipped.
*Jul 11 05:20:44.759:vuri_match_class_sip:Match with user-id*Jul 11 05:20:44.759:vuri_match_class_sip:input (9991234)Try to match with the user-id portion of the URL, which is 9991234.
*Jul 11 05:20:44.759:vuri_match_class_sip:Match failedThe configured pattern, however, is "driver" and it is not a match.
Output Showing Successful Match of Voice URI Class
The following debugging output is displayed when an outbound dial peer match is done for the URL sip:driver@cisco.com:
*Jul 11 06:06:30.119:vuri_match_class:tag (767)The first dial peer in the list is 767 and it contains the destination uri 767 command. 767 is a TEL URI class, so it does not match with the above URL.
*Jul 11 06:06:30.119:vuri_match_class:tag (766)The next dial peer, 766, contains the destination uri 766 command. Verify if the URL matches URI class 766.
*Jul 11 06:06:30.119:vuri_match_class_sip:sip:driver@cisco.com did not match patternThe URL does not match with the pattern command.
*Jul 11 06:06:30.119:vuri_match_class:tag (999)The next dial peer, 999, contains the destination uri 999 command.
*Jul 11 06:06:30.119:vuri_match_class_sip:Match with phone context*Jul 11 06:06:30.119:vuri_match_class_sip:input ()If the phone context command is not configured, it is skipped.
*Jul 11 06:06:30.119:vuri_match_class_sip:Match with host*Jul 11 06:06:30.119:vuri_match_class_sip:input (cisco.com)If the host command is not configured under the class, it is skipped.
*Jul 11 06:06:30.119:vuri_match_class_sip:Match with user-id*Jul 11 06:06:30.119:vuri_match_class_sip:input (driver)If the user-id command is not configured, the user-id portion from the URL is "driver."
*Jul 11 06:06:30.119:vuri_match_class_sip:driver matched; match length (6)There is a match with the configured pattern. The number of characters that matched is 6.
Related Commands
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
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 vofr1d05h: 1/1:VOFR, unconf ==> pending_start1d05h: 1/1:VOFR,create VOFR1d05h: 1/1:VOFR,search dial-peer 7100 preference 01d05h: 1/1:VOFR, pending_start ==> start1d05h: 1/1:VOFR,1d05h:voice_configure_perm_svc:1d05h:dial-peer 7100 codec = G729A payload size = 30 vad = off dtmf relay = onseq num = off1d05h:voice-port 1/1 codec = G729A payload size = 30 vad = off dtmf relay = onseq num = off1d05h: 1/1:VOFR,SIGNAL-TYPE = cept1d05h:init_frf11 tcid 0 master 0 signaltype 21d05h:Going Out Of Service on tcid 0 with sig state 00011d05h: 1/1:VOFR, start get event idle1d05h: 1/1:VOFR, start get event1d05h: 1/1:VOFR, start get event set up1d05h: 1/1:VOFR, start ==> pending_connect1d05h: 1/1:VOFR, pending_connect get event connect1d05h: 1/1:VOFR, pending_connect ==> connect1d05h: 1/1:VOFR,SIGNAL-TYPE = cept1d05h:init_frf11 tcid 0 master 1 signaltype 21d05h:start_vofr_polling on port 0 signaltype 2The following example shows sample output from the debug voice vofr command for an FRF.11 trunk:
Router# debug voice vofr1d05h: 1/1:VOFR,search dial-peer 7200 preference 21d05h: 1/1:VOFR,SIGNAL-TYPE = cept1d05h:Launch Voice Trunk:signal-type 21d05h:calculated bandwidth = 10, coding = 6, size = 301d05h:%Voice-port 1/1 is down.1d05h: 1/1:VOFR, pending_start get event idle1d05h:Codec Type = 6 Payload Size = 30 Seq# off1d05h:%Voice-port 1/1 is up.1d05h:init_frf11 tcid 0 master 1 signaltype 21d05h:status OK :cid = 1001d05h: 1/1:VOFR,1d05h:start FRF111d05h: 1/1:VOFR, pending_start ==> frf111d05h: 1/1:VOFR,SIGNAL-TYPE = ceptRelated Commands
debug voip aaa
To enable debugging messages for gateway authentication, authorization, and accounting (AAA) to be sent to the system console, use the debug voip aaa command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip aaa
no debug voip aaa
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug voip aaa command:
Router# debug voip aaaVoIP AAA debugging is enabledRouter# show debugvoip aaa:voip aaa debugging is ondebug voip ais
To enable debugging of the application information system (AIS) database, use the debug voip ais command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip ais
no debug voip ais
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug voip ais command:
Router# debug voip aisvoip AIS debugging is onRouter#*Jul 18 22:18:30.947: ais_appinst_create_record: new app inst record is created for sid=10, app_name=generic, stats:avail, elog:avail*Jul 18 22:18:30.947: ais_appinst_insert_record_to_active: app inst sid=A is inserted to active tree*Jul 18 22:18:30.963: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au*Jul 18 22:18:30.963: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245*Jul 18 22:18:30.963: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC)Router#*Jul 18 22:18:46.468: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au*Jul 18 22:18:46.468: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245*Jul 18 22:18:46.468: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC)Router#*Jul 18 22:18:51.520: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au*Jul 18 22:18:51.520: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245*Jul 18 22:18:51.520: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC)Router#*Jul 18 22:18:56.573: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au*Jul 18 22:18:56.573: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245*Jul 18 22:18:56.573: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC)Router#*Jul 18 22:19:01.625: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au*Jul 18 22:19:01.625: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245*Jul 18 22:19:01.625: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC)*Jul 18 22:19:01.949: propagate_history_stats: stats for app inst 10 is propagated to application (generic) and gateway level*Jul 18 22:19:01.949: ais_appinst_move_record_active_to_history: session record (sid=A) is moved to history repositoryRelated Commands
debug voip application
To display all application library debug messages, use the debug voip application command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip application [core | all | callsetup | digitcollect | error | redirect | session | supplementary-service]
no debug voip application [core | all | callsetup | digitcollect | error | redirect | session | supplementary-service]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you do not use any keywords, the debug voip application command displays application programming interface (API) libraries being processed.
The debug voip application all command differs from the debug voip ivr all command in that the former command enables all application framework debugs, whereas the latter command enables both Application Framework Session debugs and interactive voice response (IVR) debugs.
Examples
The following is sample output from the debug voip application callsetup command:
Router# debug voip application callsetupivr call setup debugging is onRouter#*Mar 7 22:08:40.032://7//APPL:/afsSettlementValidateCall:target=, tokenp=0x0*Mar 7 22:08:41.864://-1//PCM :LP:HN23A698CC:HN23A691A4:/InitiateCallSetup:Mode 1 RedirectMode 6 Incoming leg[-1] AlertTime -1 Destinations(1) [ 405 ]*Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/InitiateCallSetup:Destination 0 guid :231D511B.1A5F11CC.800BB191.E9DE175D*Mar 7 22:08:41.868: incoming_guid :00000000.00000000.00000000.00000000*Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNInitiate:Destination[405]*Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNMatchDialPeer:*Mar 7 22:08:41.868: src carrier id:, tgt carrier id:*Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNQueuePeers:Matched peers(1)*Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNSetupPeer: Destination 0x6221092C*Mar 7 22:08:41.872://-1//PCM :HN23A698D0:/DNSetupPeer:dialpeer tags for Rotary = 400*Mar 7 22:08:41.872://-1//PCM :HN23A698D0:/DNSetupPeer:*Mar 7 22:08:41.872:Destination SetupPeer cid(-1), destPat(405), match(2), prefix(), peer(630D95B0)*Mar 7 22:08:41.872://-1//PCM :HN23A698D0:/DNSettlementMatrixCheck:retcode=1 cid(-1) trans=0x0, provider=0 No settle-call present*Mar 7 22:08:41.940://8//PCM :/DNHandler:(DN_SETTING[2])--(CC_EV_CALL_PROCEEDING[25])--IGNORED-->>(DN_SETTING[2])*Mar 7 22:08:41.940://8//PCM :/CS_Setting_PROCEED:*Mar 7 22:08:41.940://8//PCM :/CSPopLegAndWait:*Mar 7 22:08:41.940://8//PCM :/CallSetupHandler:(CS_SETTING[0]) -----(CS_EV_PROCEEDING[3])------->>>(CS_SETTING[0])*Mar 7 22:08:41.948://-1//PCM :HN23A698CC:/CSInterceptEvent:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_SETTING)*Mar 7 22:08:41.948://8//PCM :/CSInterceptEvent:(CS_SETTING[0]) intercepting CS_EV_PROGRESS leg 8 (Mask=12)*Mar 7 22:08:41.948://-1//PCM :HN23A698CC:/CSInterceptEvent:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_SETTING)*Mar 7 22:08:41.952://-1//PCM :HN23A698CC:/CallSetupContinueEvent:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_SETTING)*Mar 7 22:08:41.956://8//PCM :/CS_CutProgress:*Mar 7 22:08:41.956://8//PCM :/CSPopLegAndWait:*Mar 7 22:08:41.956://8//PCM :/CallSetupContinueEvent:(CS_SETTING[0]) -----(CS_EV_PROGRESS[15])------->>>(CS_CONFEDALERT[5])*Mar 7 22:08:41.956://-1//PCM :HN23A698CC:/CallSetupHandleQueueEvents:*Mar 7 22:08:41.956://8//PCM :/CallSetupContinueEvent: *** Leaving function ***CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_CONFEDALERT)*Mar 7 22:08:43.864://8//PCM :/CS_ConfedAlert_CONNECTED:no of Destinations:1*Mar 7 22:08:43.864://-1//PCM :HN23A698CC:/CSDiscReturnAndEmptyLegALL:*Mar 7 22:08:43.864://8//PCM :/CSPopLegAndWait:*Mar 7 22:08:43.864://-1//PCM :HN23A698CC:/CSReturnIFDone:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_CONFED)*Mar 7 22:08:43.864:CallSetupDump:CallSetup[0x6320B998] State:CS_CONFED[3] #Handler=1 #Waits=1#Objects=2*Mar 7 22:08:43.864:All Destinations:*Mar 7 22:08:43.864:DestinationDump:Destination[0x6221092C]:DN_SETTING[2] Holding[0] Leg[8]*Mar 7 22:08:43.864:settlement_in_use:0 settlement_transaction:0x0 settlement_provider:0 settlement_type:0 settlement_callvalid:1 busyRotary:0*Mar 7 22:08:43.864:WaitList of Destinations:{HAN[DN_HAND ][CS_HAND ] ( )}*Mar 7 22:08:43.868:Handler Tree{HAN[CS_HAND ][AFS_HAND] ( HAN[DN_HAND][CS_HAND ][FALSE] [UC=1 ]LEG[8 ][CS_HAND ][LEG_OUTCONNECTED(8)][Cause(0)][UC=1 ])}*Mar 7 22:08:43.868:{HAN[DN_HAND ][CS_HAND ] ( )}*Mar 7 22:08:43.868:*Mar 7 22:08:43.868:Handler Tree Trace*Mar 7 22:08:43.868://-1//PCM :HN23A698D0:/DNCleanup:Terminate=TRUE Status DN_SUCCESS Leg[8]*Mar 7 22:08:43.868://-1//PCM :HN23A698D0:/DNSettlementCleanup:cid(-1) trans=0x0, provider=0*Mar 7 22:08:43.868://-1//PCM :HN23A698D0:/DNSetFree:*Mar 7 22:08:43.868://-1//PCM :HN23A698CC:/CSReturnIFDone:CallSetup[0x6320B998] handlercount=0 #Waits=0 #Objects=1 (CS_CONFED)*Mar 7 22:08:43.872://-1//PCM :HN23A698CC:/CSReturnIFDone: decoupled extern connection*Mar 7 22:08:43.872://-1//PCM :HN23A698CC:/CSReturnIFDone:CallSetup Returning(ls_000 Status CS_ACTIVE)*Mar 7 22:08:43.872://8//PCM :/CallSetupHandler:(CS_CONFEDALERT[5]) -----(CS_EV_CONNECTED[5])------->>>(CS_CONFED[3])*Mar 7 22:08:43.872://-1//PCM :HN23A698CC:/CallSetupCleanup:Terminate=FALSE*Mar 7 22:08:43.876://-1//PCM :HN23A698CC:/CallSetupCleanup:State CS_CONFEDThe following is sample output from the debug voip application digitcollect command:
Router# debug voip application digitcollectivr digit collect debugging is onRouter#*Mar 7 22:09:08.108://9//DCM :/DigitCollect:DialPlan=TRUE AbortKey= TermKey=# NumPatts=0Enable=FALSE InterruptPrompt=FALSE maxDigits=0 DialPlanTerm=FALSE*Mar 7 22:09:08.108://9//APPL:/AppTypeAheadGetDigit:no chars in buffer.*Mar 7 22:09:08.112://9//DCM :/act_DCRunning_RDone:callid=9 Enable succeeded.enable=0 matchDialplan=1 numPatterns=0matchDialplanTerm=0*Mar 7 22:09:11.428://9//APPL:/AppVcrControlEvent:VCR Control, not enabled.---*Mar 7 22:09:11.428://9//APPL:/AppTypeAheadEvent:Passing, not enabled.---*Mar 7 22:09:11.428://9//DCM :/act_DCRunning_Digit::pLeg 9 Digit 4 Tone Mode 0*Mar 7 22:09:11.428://9//DCM :/DCTreatDigit:*Mar 7 22:09:11.428://-1//DCM :HN23A6FF50:/DCTreatDigit:*Mar 7 22:09:11.428: src carrier id:, tgt carrier id:*Mar 7 22:09:11.428://-1//DCM :HN23A6FF50:/DCTreatDigit:Match single infotype*Mar 7 22:09:11.676://9//APPL:/AppVcrControlEvent:VCR Control, not enabled.---*Mar 7 22:09:11.676://9//APPL:/AppTypeAheadEvent:Passing, not enabled.---*Mar 7 22:09:11.676://9//DCM :/act_DCRunning_Digit::pLeg 9 Digit 0 Tone Mode 0*Mar 7 22:09:11.676://9//DCM :/DCTreatDigit:*Mar 7 22:09:11.680://-1//DCM :HN23A6FF50:/DCTreatDigit:*Mar 7 22:09:11.680: src carrier id:, tgt carrier id:*Mar 7 22:09:11.680://-1//DCM :HN23A6FF50:/DCTreatDigit:Match single infotype*Mar 7 22:09:11.908://9//APPL:/AppVcrControlEvent:VCR Control, not enabled.---*Mar 7 22:09:11.908://9//APPL:/AppTypeAheadEvent:Passing, not enabled.---*Mar 7 22:09:11.908://9//DCM :/act_DCRunning_Digit::pLeg 9 Digit 5 Tone Mode 0*Mar 7 22:09:11.908://9//DCM :/DCTreatDigit:*Mar 7 22:09:11.908://-1//DCM :HN23A6FF50:/DCTreatDigit:*Mar 7 22:09:11.908: src carrier id:, tgt carrier id:*Mar 7 22:09:11.908://-1//DCM :HN23A6FF50:/DCTreatDigit:Match single infotype*Mar 7 22:09:11.912://9//DCM :/act_DCRunning_RDone:callid=9 Reporting disabled.*Mar 7 22:09:11.912://-1//DCM :HN23A6FF50:/DigitCollectComplete:Status 4=DC_MATCHED_DIALPLAN. Digits=405*Mar 7 22:09:11.916://-1//DCM :HN23A6FF50:/DCHandlerCleanup:The following is sample output from the debug voip application session command:
Router# debug voip application sessionapplib session debugging is on*Apr 4 23:57:08.054://-1//APPL:HN04B2BC78:LG35:/AFS_CALLSETUPIND:Calling #(4155550154), Called #(52984), peer_tag(1)*Apr 4 23:57:08.054://-1//APPL:HN04B2BC78:LG35:/afsSetupCall:Called #(52984)*Apr 4 23:57:08.058://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CALLINIT)--(CC_EV_CALL_SETUP_IND)- ->>(CONTACTINGDEST)*Apr 4 23:57:08.466://-1//APPL:HN04B2BC78:LG36:/AFS_ContactingDest_ALERT:*Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:LG36:/AFS_ContactingDest_ALERT:inID(35), outID(36), outbnd peer_tag(6), prog_ind(8)*Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:LG36:/afsMsgHandler:(CONTACTINGDEST)--(CC_EV_CALL_ALERT )-->>(CONFINGALERT)*Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:CN11:/AFS_ConfingAlert_CREATEDONE: {HAN[AFS_HAND][NULL ] ( LEG[35 ][AFS_HAND][LEG_INCALERTING(4)][Cause(0)][UC=1 ]HAN[CS_HAND][AFS_HAND][FALSE] [UC=1 ]LEG[36 ][CS_HAND ][LEG_OUTINIT(6)][Cause(0)][UC=1 ]CON[11 ][AFS_HAND][CONNECTION_CONFED(2)] [UC=1 ])}*Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:CN11:/afsMsgHandler:(CONFINGALERT)--(CC_EV_CONF_CREATE_ DONE)-->>(CONFEDALERT)*Apr 4 23:57:08.478://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CONFEDALERT)--(CC_EV_VOICE_MODE_DO NE)-->>(CONFEDALERT)*Apr 4 23:57:24.162://-1//APPL:HN04B2BC78:HN04B2BC78:/AFS_ConfedAlert_SETUPDONE:*Apr 4 23:57:24.162://-1//APPL:HN04B2BC78:HN04B2BC78:/afsAppHandlerCleanup:CS_HAND*Apr 4 23:57:24.162://-1//APPL:HN04B2BC78:/afsMsgHandler:(CONFEDALERT)--(APP_EV_CALLSETUP_DONE)-- >>(CALLACTIVE)*Apr 4 23:57:24.182://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CALLACTIVE)--(CC_EV_VOICE_MODE_DON E)-->>(CALLACTIVE)*Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:LG35:/AFS_DISCONNECT:*Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CALLACTIVE)--(CC_EV_CALL_DISCONNEC TED)-->>(CALLDISCONNECT)*Apr 4 23:57:34.838://-1//APPL:/afsCallProcess: [HANDLERDONE_EVENT_END]*Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:/afsHNDCleanup:Terminate TRUE Terminated FALSE{HAN[AFS_HAND][NULL ] ( LEG[35 ][AFS_HAND][LEG_INCCONNECTED(5)][Cause(16)][UC=1 ]LEG[36 ][AFS_HAND][LEG_OUTCONNECTED(8)][Cause(0)][UC=1 ]CON[11 ][AFS_HAND][CONNECTION_CONFED(2)] [UC=1 ])}*Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:CN11:/afsMsgHandler:(CC_EV_CONF_DESTROY_DONE)*Apr 4 23:57:34.854://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CC_EV_CALL_DISCONNECT_DONE)*Apr 4 23:57:34.862://-1//APPL:HN04B2BC78:LG36:/afsMsgHandler:(CC_EV_CALL_DISCONNECT_DONE)*Apr 4 23:57:34.862://-1//APPL:/afsCallProcess: [HANDLERDONE_EVENT_END]*Apr 4 23:57:34.862://-1//APPL:HN04B2BC78:/afsHNDCleanup:Terminate TRUE Terminated TRUE{HAN[AFS_HAND][NULL ] ( )}*Apr 4 23:57:34.862://-1//APPL:HN04B32530:/afsFreeHND:Hndlr returned to the free queueThe following sample output shows an inbound call on a system with H.450.2, H.450.3, and H.450.12 capabilities enabled:
Router# debug voip application supplementary-servicesupplementary service debugging is onJan 21 01:12:21.433://-1//APPL:/SSProcessH450CommonInfoEvent: CI_INFORM featureList=0xC0000000 featureValue[0][0] featureControl=0x0Jan 21 01:12:21.433://-1//APPL:/AppStoreCommonInfoToLeg:Leg peer_tag=8100Jan 21 01:12:21.433://-1//APPL:/AppStoreCommonInfoToLeg:Received ciInform, store ss_support=0xE000 to leg.Jan 21 01:12:21.433://-1//APPL:/AppPrepareCommonInfo:Not voip dialpeer, no common info sent.Jan 21 01:12:21.437://-1//APPL:/AppPrepareCommonInfoRequestReceived:Leg peer_tag=8100Jan 21 01:12:21.437://-1//APPL:/AppPrepareCommonInfo:Global H450_2=1 H450_3=1 H450_12_ADV=1 H450_12_USAGE=1Jan 21 01:12:21.437://-1//APPL:/AppPrepareCommonInfoContent:SS_CI ss_evt=18 featureList=0xC0000000 featureValues=[0][0][0][0] featureControl=0x0Table 306 describes the significant fields shown in the display.
Related Commands
debug voip application stcapp all
To display debugging information for the components of the SCCP Telephony Control Application (STCAPP), use the debug voip application stcapp all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip application stcapp all
no debug voip application stcapp all
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug voip application stcapp all command provides debugging output for all the STCAPP debug commands compiled into one display.
Examples
The following is sample output from the debug voip application stcapp all command:
Router# debug voip application stcapp allThe following lines show the voice gateway beginning call setup:
*Jan 9 06:48:06.947: ==> Received event:STCAPP_CC_EV_CALL_SETUP_IND (evId:CC_EV_CALL_SETUP_IND) for CallId: 5*Jan 9 06:48:06.947: 1/0/0: Call State:IDLE*Jan 9 06:48:06.947: 1/0/0: stcapp_setup_ind_eh*Jan 9 06:48:06.947: 1/0/0: Acquired CCB 0x66F12558 for device id:4*Jan 9 06:48:06.947: 1/0/0: Voice Setup: callID:5, vdb_ptr:66CA57B4The voice gateway notifies the Cisco CallManager of the endpoint device (phone) in the offhook condition.
*Jan 9 06:48:06.947: 1/0/0: Sending StationOffHook to CallManager*Jan 9 06:48:06.947: 1/0/0: Sending ccCallSetupAck to Symphony for voice call id:5*Jan 9 06:48:06.947: 1/0/0: New State = OFFHOOK*Jan 9 06:48:06.955: 1/0/0: No line (line=0) found... most likely old Call Ref: event STCAPP_DC_EV_DEVICE_SET_RINGERThe following lines show that the Cisco CallManager acknowledged the offhook conditon:
*Jan 9 06:48:06.955: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_OFFHOOK (evID:DC_EV_DEVICE_CALL_STATE_OFFHOOK)*Jan 9 06:48:06.955: 1/0/0: Call State:OFFHOOK*Jan 9 06:48:06.955: 1/0/0: stcapp_cs_offhook_eh*Jan 9 06:48:06.955: 1/0/0: No state changeThe voice gateway receives the Cisco CallManager notification to send a dial tone to the phone.
*Jan 9 06:48:06.955: ==> Received event:STCAPP_DC_EV_DEVICE_START_TONE (evID:DC_EV_DEVICE_START_TONE)*Jan 9 06:48:06.955: 1/0/0: Call State:OFFHOOK*Jan 9 06:48:06.955: 1/0/0: stcapp_start_tone_ehThe voice gateway generates a dial tone and prepares to collect dialed digits.
*Jan 9 06:48:06.955: 1/0/0: Sending ccGenerateTone(8(0x8))*Jan 9 06:48:06.955: 1/0/0: Sending ccCallReportDigits*Jan 9 06:48:06.955: 1/0/0: No state changeRelated Commands
debug voip application stcapp error
To troubleshoot the SCCP Telephony Control Application (STCAPP) error log contents, use the debug voip application stcapp error command in privileged EXEC mode. To disable STCAPP error debugging, use the no form of this command.
debug voip application stcapp error
no debug voip application stcapp error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug voip application stcapp error command traces application error logs. STCAPP error logs are generated during normal call processing, when there are insufficient resources, or when there are problems in the underlying application code. This command shows error events or unexpected behavior in system software. Usually no events are generated.
Examples
The following example shows the error log contents when STCAPP debugging is enabled:
Router# debug voip application stcapp errorSTCAPP error debugging is onRouter#*Jan 9 06:54:07.583: stcapp_process_queue_events:ERROR:STCAPP_DCB_ACCESS_ERR from state machineRelated Commands
debug voip application stcapp events
To trace SCCP Telephony Control Application (STCAPP) call flow events, use the debug voip application stcapp events command in privileged EXEC mode. To disable STCAPP event call traces, use the no form of this command.
debug voip application stcapp events
no debug voip application stcapp events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to debug call flow events for all ports controlled by the STCAPP.
Examples
The following example displays call teardown and disconnect events:
Router# debug voip application stcapp eventsThe following lines show the application running on the voice gateway receiving notice to stop dial tone generation, following the onhook condition of the endpoint device (phone):
*Jan 9 06:48:55.011: ==> Received event:STCAPP_DC_EV_DEVICE_STOP_TONE (evID:DC_EV_DEVICE_STOP_TONE)*Jan 9 06:48:55.011: 1/0/1: Call State:REM_ONHOOK_PEND*Jan 9 06:48:55.011: 1/0/1: stcapp_stop_tone_eh*Jan 9 06:48:55.011: 1/0/1: Sending ccGenerateTone(NULL)*Jan 9 06:48:55.015: 1/0/1: No state changeThe application takes no additional action to process the uninteresting event.
*Jan 9 06:48:55.015: ==> Received event:STCAPP_DC_EV_DEVICE_START_TONE (evID:DC_EV_DEVICE_START_TONE)*Jan 9 06:48:55.015: 1/0/1: Call State:REM_ONHOOK_PEND*Jan 9 06:48:55.015: 1/0/1: Uninteresting eventThe application receives the call disconnect notice and proceeds to tear down the telephony call leg.
*Jan 9 06:48:58.903: ==> Received event:STCAPP_CC_EV_CALL_DISCONNECTED (evId:CC_EV_CALL_DISCONNECTED) for CallId: 6*Jan 9 06:48:58.903: 1/0/1: Call State:REM_ONHOOK_PEND*Jan 9 06:48:58.903: 1/0/1: stcapp_loc_onhook_eh*Jan 9 06:48:58.903: 1/0/1: Sending StationOnHook to CallManager*Jan 9 06:48:58.903: 1/0/1: stcapp_call_cleanup*Jan 9 06:48:58.903: 1/0/1: stcapp_set_ring_mode*Jan 9 06:48:58.903: 1/0/1: SCCP ring mode:1*Jan 9 06:48:58.903: 1/0/1: Invoking Feature:33. Mode:0 for callid:6*Jan 9 06:48:58.903: 1/0/1: stcapp_disconnect_call_leg*Jan 9 06:48:58.903: 1/0/1: Sending ccCallDisconnect for call id:6*Jan 9 06:48:58.903: 1/0/1: CCB 0x65CF3EC4 unlinked*Jan 9 06:48:58.903: 1/0/1: New State = IDLERelated Commands
debug voip application stcapp functions
To debug SCCP Telephony Control Application (STCAPP) functions, use the debug voip application stcapp functions command in privileged EXEC mode. To disable STCAPP function debugging, use the no form of this command.
debug voip application stcapp functions
no debug voip application stcapp functions
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display STCAPP entry and exit function calls for all voice ports.
Examples
The following example displays function calls for STCAPP ports 1/0/0 and 1/0/1:
Router# debug voip application stcapp functionsSTCAPP function debugging is on*Jan 9 06:55:27.583: 1/0/0: stcapp_setup_ind_eh*Jan 9 06:55:27.591: 1/0/0: stcapp_cs_offhook_eh*Jan 9 06:55:27.591: 1/0/0: stcapp_start_tone_eh*Jan 9 06:55:27.591: 1/0/0: stcapp_report_digits_done_eh*Jan 9 06:55:28.923: 1/0/0: stcapp_digit_end_eh*Jan 9 06:55:28.927: 1/0/0: stcapp_stop_tone_eh*Jan 9 06:55:29.063: 1/0/0: stcapp_digit_end_eh*Jan 9 06:55:29.203: 1/0/0: stcapp_digit_end_eh*Jan 9 06:55:29.343: 1/0/0: stcapp_digit_end_eh*Jan 9 06:55:29.355: 1/0/0: stcapp_cs_proceed_eh*Jan 9 06:55:29.359: 1/0/0: stcapp_proceed_call_info_eh*Jan 9 06:55:29.359: 1/0/0: stcapp_start_tone_eh*Jan 9 06:55:29.359: 1/0/0: stcapp_proceed_call_info_eh*Jan 9 06:55:29.359: 1/0/1: stcapp_cs_ringin_eh*Jan 9 06:55:29.359: 1/0/1: stcapp_call_info_ehRelated Commands
debug voip application stcapp port
To enable SCCP Telephony Control Application (STCAPP) debugging for a specific port, use the debug voip application stcapp port command in privileged EXEC mode. To disable specific STCAPP port debugging, use the no form of this command.
debug voip application stcapp port port-number
no debug voip application stcapp port port-number
Syntax Description
port-number
Number of the port on the interface. See the appropriate platform manual or online help for port numbers on your networking device.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display debugging information for the components of the STCAPP for a specified port.
Examples
The following example displays information on STCAPP controlled FXS port 1/0/1 during call setup:
Router# debug voip application stcapp port 1/0/1stcapp port debugging is onThe following lines show the voice gateway receiving notification from the Cisco CallManager of an incoming call:
*Jan 9 06:57:24.403: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_RINGIN (evID:DC_EV_DEVICE_CALL_STATE_RINGIN)*Jan 9 06:57:24.403: 1/0/1: Call State:IDLE*Jan 9 06:57:24.403: 1/0/1: stcapp_cs_ringin_eh*Jan 9 06:57:24.407: 1/0/1: Acquired CCB 0x66C0A428 for device id:3The next lines show the new call processing state for the port.
*Jan 9 06:57:24.407: 1/0/1: New State = RINGIN*Jan 9 06:57:24.407: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_INFO (evID:DC_EV_DEVICE_CALL_INFO)*Jan 9 06:57:24.407: 1/0/1: Call State:RINGIN*Jan 9 06:57:24.407: 1/0/1: stcapp_call_info_ehThe next lines show the application sending a call setup request for the telephony leg.
*Jan 9 06:57:24.407: 1/0/1: stcapp_set_up_voice_leg*Jan 9 06:57:24.407: 1/0/1: Sending ccIFCallSetupRequest for voice leg*Jan 9 06:57:24.407: 1/0/1: ccIFCallSetRequest returned voice call id:22. CdPN:7702CgPN:7701*Jan 9 06:57:24.407: 1/0/1: No state changeThe next lines show the application invoking the ringing state.
*Jan 9 06:57:24.407: ==> Received event:STCAPP_DC_EV_DEVICE_SET_RINGER (evID:DC_EV_DEVICE_SET_RINGER)*Jan 9 06:57:24.407: 1/0/1: Call State:RINGIN*Jan 9 06:57:24.407: 1/0/1: stcapp_set_ringer_eh*Jan 9 06:57:24.407: 1/0/1: stcapp_set_ring_mode*Jan 9 06:57:24.407: 1/0/1: SCCP ring mode:2*Jan 9 06:57:24.407: 1/0/1: Invoking Feature:12. Mode:0 for callid:22*Jan 9 06:57:24.407: 1/0/1: No state changeRelated Commands
debug voip application vxml
To troubleshoot a VoiceXML application, use the debug voip application vxml command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip application vxml [all | application | background | default | error [call [informational] | software [informational]] | event | function | grammar | gtd | inout | puts | ssml | trace | warning ]
no debug voip application vxml
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If this debug encounters a fetch failure when using an HTTP interface, an error.badfetch.http.response code message is displayed. The values for the response code are shown in Table 307.
Examples
The following is sample output from the debug voip application vxml all command when there is an HTTP badfetch error call:
Router# debug voip application vxml allAug 7 04:53:03.003: //-1/000000000000/VAPP:/vapp_evt_handler:State VAPP_ACTIVE got event CC_EV_CALL_SETUP_INDAug 7 04:53:03.003: //-1/000000000000/VAPP:/vapp_driver:pInterp[6383BA48]:Aug 7 04:53:03.003: //-1/000000000000/VAPP:/vapp_driver:evtID: 29 vapp record state: 0Aug 7 04:53:03.003: //-1/000000000000/VAPP:/vapp_evt_setup:Aug 7 04:53:03.003: //-1//VAPP:/vapp_incoming_callblock:Aug 7 04:53:03.003: vapp_incoming_callblock:Before the incoming call block data comes in, the CallEntry ID is -1, which indicates that the call leg had not been identified. In the next step, the call leg is shown as 1 and the GUID is also assigned.
Aug 7 04:53:03.003: //1/71E56a9AF8002/VAPP:/vapp_evt_setup:VXML call. GTD should be savedAug 7 04:53:03.003: //1/71E569AF8002/VAPP:/vapp_load_or_run_script:Aug 7 04:53:03.003: //1/71E569AF8002/VAPP:/vapp_load_or_run_script:The next several lines show script-specific information.
Aug 7 04:53:03.007: The VXML Script with len=1519 starts:-------------------------------------<?xml version="3.0" encoding="iso-8859-1"?><vxml version="3.0"><form id = "transfer_me"><catch event="telephone.disconnect.transfer"></catch><var name="phone_num" expr="5550100"/><vThe CallEntry ID becomes 0 in the following lines, which indicates that the output is coming from the application server rather than a call leg.
Aug 7 04:53:03.007: //0//VXML:/vxml_start_element_handler: EnterAug 7 04:53:03.007: //0//VXML:/vxml_start_element_handler: ExitAug 7 04:53:03.007: //0//VXML:/vxml_character_data: EnterAug 7 04:53:03.007: //0//VXML:/vxml_character_data:at line 888: length <=0, exit...Aug 7 04:53:03.051: //0//VXML:/vxml_end_element_handler: EnterAug 7 04:53:03.051: //0//VXML:/vxml_end_element_handler: ExitAug 7 04:53:03.051: //0//VXML:/vxml_parse:Aug 7 04:53:03.051: vxml_parse: XML_Parse success err=0Aug 7 04:53:03.051: //0//VXML:/vxml_session_delete:Aug 7 04:53:03.051: vxml_session_delete:mem_mgr_mempool_free: mempool=NULLAug 7 04:53:03.051: //-1//VXML:/vxml_create:enter url=tftp://dirt/jkuo/vxml/xfer.nosound.vxml tree_handle=63282BDCreturn_handle_add=63C84F80In the following lines, the call with the GUID 71E569AF8002 is again being tracked as the application session is initiated.
Aug 7 04:53:03.083: //1/71E569AF8002/VXML:/vxml_offramp_mailhdrs_get:Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_create_gtd_sess_vars:Created object chain for com.cisco.signal.gtdlistAug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_jse_add_gtd_obj_to_list:Sig-event name = setup_indication, gtd-len = 140, gtd-buf =IAM,PRN,isdn*,,,USI,rate,c,s,c,1USI,lay1,ulawTMR,00CPN,34,,4,52950CPC,09FCI,,,,,,,y,GCI,71e569af6b5511d4800200014232e6a8Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_jse_add_gtd_obj_to_list:gtd_obj for sig-event [setup_indication] added to session/shadowvar array [0x63826914]Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_create: ExitAug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_start:vxmlhandle=6372E9BC vapphandle=6383BA48 status=0 async_status=0Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_vxml_proc:<vxml> URI(abs):tftp://dirt/jkuo/vxml/xfer.nosound.vxmlscheme=tftphost=dirtpath=/jkuo/vxml/xfer.nosound.vxmlbase= URI(abs):tftp://dirt/jkuo/vxml/xfer.nosound.vxmlscheme=tftphost=dirtpath=/jkuo/vxml/xfer.nosound.vxml lang=none version=3.0Aug 7 04:53:03.087: //1/71E569AF8002/VXML:/vxml_form_proc:Aug 7 04:53:03.087: <form>: id=transfer_me scope=dialogIn the following line, the phone number of the caller is shown:
Aug 7 04:53:03.087: vxml_form_init current scope: dialog<var>: namep=phone_num expr=5550100Aug 7 04:53:03.091: //1/71E569AF8002/VXML:/vxml_expr_eval:expr=var phone_num=5550100<var>: namep=mydurAug 7 04:53:03.095: //1/71E569AF8002/VXML:/vxml_expr_eval:expr=var mydurvxml_counter_reset:Aug 7 04:53:03.095: //1/71E569AF8002/VXML:/vxml_formitem_select:Status=VXML_STATUS_OK,Aug 7 04:53:03.095: //1/71E569AF8002/VXML:/vxml_formitem_select:AsyncStatus=VXML_STATUS_OKAug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_transfer_proc:<transfer>:In the following lines, the attributes of the incoming phone call are shown:
Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_item_attrs_proc:name=mycall dest_expr='phone://'+ phone_num bridge=1 connecttimeout=50 maxtime=50 desttype=-1 destplan=-1 anitype=-1 aniplan=-1 anipi=-1, anisi=-1 rdn_exprp='phone://' + 4085550111 rdntype=2 rdnplan=1 rdnpi=0, rdnsi=3, redirectreason=0The next several lines show the initialization and playing of audio prompts. When troubleshooting voice applications, ensure that all your assigned prompts play when required.
Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_play_prompts: EnterAug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_prompt_proc: EnterAug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_prompt_proc:<prompt>:(default_prompt) bargein=1 count=1 typeaheadflush=0Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_audio_proc: EnterAug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_audio_proc:<audio>: URI(abs):http://px1-sun/nosound.auscheme=httphost=px1-sunpath=/nosound.au caching=fast fetchhint=invalid fetchtimeout=0Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_audio_proc: ExitAug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_vapp_media_play:bargein=1 timeout=0 typeaheadflush=0 vcr=0 rate=0Aug 7 04:53:03.099: //1/71E569AF8002/VXML:/vxml_vapp_media_play:str=http://px1-sun/nosound.au cachable=1 timeout0Aug 7 04:53:03.099: //1/71E569AF8002/VAPP:/vapp_media_play:Aug 7 04:53:03.099: //1/71E569AF8002/VAPP:/vapp_media_play:prompt=http://px1-sun/nosound.au:Aug 7 04:53:03.687: //1/71E569AF8002/VXML:/vxml_vapp_media_play: ExitAug 7 04:53:03.687: //1/71E569AF8002/VXML:/vxml_prompt_proc: ExitAug 7 04:53:03.687: //1/71E569AF8002/VXML:/vxml_play_prompts: ExitThe next several lines indicate that something is wrong with the XML form to which data is being written:
Aug 7 04:53:03.699: //1/71E569AF8002/VXML:/vxml_transfer_proc:GTD not present in <transfer>Aug 7 04:53:03.699: //1/71E569AF8002/VXML:/vxml_transfer_proc: ExitAug 7 04:53:03.699: //1/71E569AF8002/VXML:/vxml_elem_proc:at line 8521: Status not OK, exitAug 7 04:53:03.703: //1/71E569AF8002/VXML:/vxml_formitem_select:at line 4651: Status not OK, exitAug 7 04:53:03.703: //1/71E569AF8002/VXML:/vxml_form_proc:at line 4791: Status not OK, exitAug 7 04:53:03.703: //1/71E569AF8002/VXML:/vxml_elem_proc:at line 8521: Status not OK, exitAug 7 04:53:03.703: //1/71E569AF8002/VXML:/vxml_vxml_proc:at line 8703: Status not OK, exitAug 7 04:53:03.703: //1/71E569AF8002/VXML:/vxml_load_immediate_done:sidp->status=180000000Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_checksessionstate:Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_checkifdone:Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_driver: ExitAug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_evt_handler:State VAPP_ACTIVE got event CC_EV_CALL_MODIFY_DONEAug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_driver:pInterp[6383BA48]:Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_driver:evtID: 37 vapp record state: 0Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_checksessionstate:Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_checkifdone:Aug 7 04:53:03.703: //1/71E569AF8002/VAPP:/vapp_driver: ExitAug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_evt_handler:State VAPP_ACTIVE got event MSW_EV_SYNTHESIZERAug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_driver:pInterp[6383BA48]:Aug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_driver:evtID: 84 vapp record state: 0Aug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_play_done:evID=84 reason=8, protocol=2, status_code=404, dur=-1, rate=0Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_media_done:status 2 async_status 180000000 duration=-1 rate=0Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_save_lastprompt_info:Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_bind_lastprompt:Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_vapp_vcr_control_disable:Aug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_notify_play_done:Aug 7 04:53:03.735: //1/71E569AF8002/VAPP:/vapp_notify_play_done: ExitAfter checking the status of the application, the router finds a badfetch error, which indicates that a VXML form was not found.
Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_media_done:CALL_ERROR: : fail with vapp error 2, protocol_status_code=404Aug 7 04:53:03.735: //1/71E569AF8002/VXML:/vxml_media_done:CALL_ERROR: : *** error.badfetch.http.404 event is thrownAug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_event_driver:Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_event_proc:<event>: event=error.badfetch.http.404 status=0Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_default_event_handler:use default event handlerAug 7 04:53:03.739: //1/71E569AF8002/VAPP:/vapp_session_exit_event_name:Exit Event error.badfetch.http.404Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_load_immediate_done:sidp->status=10Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_start:vxmlhandle=6372E9BC vapphandle=6383BA48 status=0 async_status=10Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_vapp_terminate:vapp_status=0 ref_count 0Aug 7 04:53:03.739: //1/71E569AF8002/VAPP:/vapp_terminate:Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_destroy: EnterAug 7 04:53:03.739: //-1//VXML:/vxml_gtd_delete_callback:New ref-count = 0Related Commands
debug voip avlist
To troubleshoot the attribute value list (AVLIST) contents, use the debug voip avlist command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip avlist [all | default | detail | error [call [informational] | software [informational]] | inout]
no debug voip avlist
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug voip avlist command does not support call debug filtering.
Examples
Output is primarily used by TAC.
debug voip ccapi
To troubleshoot the call control application programming interface (CCAPI) contents, use the debug voip ccapi command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip ccapi [all | default | detail | error [call [informational] | software [informational]] | individual range | inout | function | protoheaders | service]
no debug voip ccapi
Syntax Description
all
(Optional) Displays all CCAPI debugging messages.
default
(Optional) Displays CCAPI error and inout information. This option also runs if no keywords are added.
detail
(Optional) Displays CCAPI background messages.
error
(Optional) Displays CCAPI error messages. The debug voip ccapi error command traces the error logs in the call control API. Error logs are generated during normal call processing, 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. Usually no events will be generated.
call
(Optional) Displays call processing errors.
informational
(Optional) Displays minor errors and major errors. Without the informational keyword, only major errors are displayed.
software
(Optional) Displays software errors.
individual
(Optional) Enables individual CCAPI debug outputs.
range
For the individual keyword, the range is an integer value from 1 to 145. For specific range values, see Table 308.
inout
(Optional) Displays CCAPI in/out functions. The debug voip ccapi inout command traces the execution path through the call control API, which serves as the interface between the call session application and the underlying network-specific software. You can use the output from this command to understand how calls are being handled by the router.
This command shows how a call flows through the system. Using this debug level, you can see the call setup and teardown operations performed on both the telephony and network call legs.
function
(Optional) Displays CCAPI function tracing.
protoheaders
(Optional) Displays CCAPI protocol headers passing information.
service
(Optional) Logs debug messages that are not call related.
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following examples show output for variations of the debug voip ccapi command:
•
•
•
•
For these examples, the topology shown in Figure 1 is used.
Figure 1 Network Topology for debug voip ccapi Output Examples
debug voip ccapi detail on the Originating Gateway
Router# debug voip ccapi detailvoip ccapi detail debugging is onRouter#*Apr 18 20:35:35.779: //-1/ABCE697D8005/CCAPI/cc_api_call_setup_ind_common:Interface Type=13, Protocol=0*Apr 18 20:35:35.779: //-1/ABCE697D8005/CCAPI/ccCheckClipClir:Calling Party Number Is User Provided*Apr 18 20:35:35.779: //11/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=TRUE)*Apr 18 20:35:35.779: //11/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:Total Call Count=1The following event shows that the CallEntry ID 11 is used for the incoming call leg.
*Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry:Incoming=TRUE, Call Id=11*Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_setupind_registration_lookup:Matching Parameters; Called Number=83103, Call Transfer Consult Id=*Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_setupind_registration_lookup:No Matching Node*Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/ccCheckClipClir:Calling Party Number Is User Provided*Apr 18 20:35:35.779: //12/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=FALSE)The following event shows that the incoming call leg with CallEntry ID 11 is bound to the outgoing call leg with CallEntry ID 12.
*Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_peer_bind:Bind=TRUE, Binder Call Id=11, Bindee Call Id=12The next event shows that CallEntry ID 12 is used for the outgoing call leg.
*Apr 18 20:35:35.779: //12/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry:Incoming=FALSE, Call Id=12*Apr 18 20:35:35.779: //-1/xxxxxxxxxxxx/CCAPI/cc_api_supported_data:data_mode=0x10082The next event shows an IP address for a remote device on the outgoing call leg, which indicates that this is the VoIP call leg.
*Apr 18 20:35:35.779: //12/ABCE697D8005/CCAPI/cc_incr_if_call_volume:Remote IP Address=172.16.13.81, Hwidb=FastEthernet0/0*Apr 18 20:35:35.779: //12/ABCE697D8005/CCAPI/cc_incr_if_call_volume:Total Call Count=1, Voip Call Count=1, MMoip Call Count=0*Apr 18 20:35:35.795: //11/ABCE697D8005/CCAPI/ccCallGetContext:Context=0x652C0168, Call Id=11*Apr 18 20:36:31.419: //11/ABCE697D8005/CCAPI/ccCallDisconnect:Start Calling Accounting;Call Entry(Incoming=TRUE)*Apr 18 20:36:31.419: //11/ABCE697D8005/CCAPI/ccCallDisconnect:Cause Value=16, Call Entry(Disconnect Cause=16)*Apr 18 20:36:31.419: //11/ABCE697D8005/CCAPI/ccCallDisconnect:Call Entry(Disconnect Cause=16)At this point, the CallEntry ID changes as the call accounting process begins. The accounting data is sent over the outgoing call leg. The GUID, which identifies the unique call, remains the same.
*Apr 18 20:36:31.419: //12/ABCE697D8005/CCAPI/ccCallDisconnect:Start Calling Accounting;Call Entry(Incoming=FALSE)*Apr 18 20:36:31.419: //12/ABCE697D8005/CCAPI/ccCallDisconnect:Cause Value=16, Call Entry(Disconnect Cause=0)The change of the CallEntry ID indicates that the call is using the incoming call leg, which is the POTS call leg in this case.
*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/ccCallGetVoipFlag:Data Bitmask=0x1, Call Id=11*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/ccCallGetVoipFlag:Flag=FALSE*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry:Incoming=TRUE*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry:ccFreeRawMsgInfo=0x63FF8198*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry:Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=TRUE)*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry:Total Call Count=0*Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry:Deleting profileTable[0x64F44700]The next line shows the impairment calculation. This is the only CCAPI debug command that shows impairment.
*Apr 18 20:36:31.423: //-1/ABCE697D8005/CCAPI/g113_calculate_impairment:(delay=91(ms), loss=0%), Io=0 Iq=0 Idte=0 Idd=2 Ie=10 Itot=12*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/ccCallGetVoipFlag:Data Bitmask=0x1, Call Id=12*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/ccCallGetVoipFlag:Flag=FALSE*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_decr_if_call_volume:Remote IP Address=172.16.13.81, Hwidb=FastEthernet0/0*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_decr_if_call_volume:Total Call Count=0, Voip Call Count=0, MMoip Call Count=0*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry:Incoming=FALSE*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_delete_call_entry:Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=FALSE)*Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_delete_call_entry:Deleting profileTable[0x652E3310]*Apr 18 20:36:31.427: //12/xxxxxxxxxxxx/CCAPI/cc_get_call_entry:Call Entry Is Not Founddebug voip ccapi detail on the Terminating Gateway
Router# debug voip ccapi detailvoip ccapi detail debugging is onRouter#*May 1 18:58:26.251: //-1/xxxxxxxxxxxx/CCAPI/cc_api_supported_data:data_mode=0x10082*May 1 18:58:26.255: //8/xxxxxxxxxxxx/CCAPI/cc_get_call_entry:Call Entry Is Not Found*May 1 18:58:26.255: //-1/ABCE697D8005/CCAPI/cc_api_call_setup_ind_common:Interface Type=0, Protocol=1*May 1 18:58:26.255: //-1/ABCE697D8005/CCAPI/ccCheckClipClir:Calling Party Number Is User ProvidedThe following line shows the attributes of the calling number:
*May 1 18:58:26.255: //-1/ABCE697D8005/CCAPI/cc_api_call_setup_ind_common:After Number Translation Checking:Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),Called Number=3600(TON=Unknown, NPI=Unknown)*May 1 18:58:26.255: //8/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=TRUE)*May 1 18:58:26.255: //8/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:Total Call Count=1*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry:Incoming=TRUE, Call Id=8The following line shows the IP address of the originating gateway:
*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_incr_if_call_volume:Remote IP Address=172.16.13.175, Hwidb=FastEthernet0/0*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_incr_if_call_volume:Total Call Count=1, Voip Call Count=1, MMoip Call Count=0*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_setupind_registration_lookup:Matching Parameters; Called Number=3600, Call Transfer Consult Id=*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_setupind_registration_lookup:No Matching Node*May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/ccCheckClipClir:Calling Party Number Is User Provided*May 1 18:58:26.259: //9/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=FALSE)*May 1 18:58:26.259: //8/ABCE697D8005/CCAPI/cc_peer_bind:Bind=TRUE, Binder Call Id=8, Bindee Call Id=9*May 1 18:58:26.259: //9/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry:Incoming=FALSE, Call Id=9*May 1 18:58:26.259: //9/ABCE697D8005/CCAPI/cc_set_voice_port_value:CC_IF_TELEPHONY: Echo=0, Playout=0*May 1 18:58:26.263: //9/ABCE697D8005/CCAPI/ccCallGetContext:Context=0x64B6BB5C, Call Id=9*May 1 18:59:21.871: //8/ABCE697D8005/CCAPI/ccCallDisconnect:Start Calling Accounting;Call Entry(Incoming=TRUE)*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallDisconnect:Cause Value=16, Call Entry(Disconnect Cause=16)*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallDisconnect:Call Entry(Disconnect Cause=16)*May 1 18:59:21.875: //9/ABCE697D8005/CCAPI/ccCallDisconnect:Start Calling Accounting;Call Entry(Incoming=FALSE)*May 1 18:59:21.875: //9/ABCE697D8005/CCAPI/ccCallDisconnect:Cause Value=16, Call Entry(Disconnect Cause=0)The next line shows the impairment calculation. This is the only CCAPI debug command that shows impairment.
*May 1 18:59:21.875: //-1/ABCE697D8005/CCAPI/g113_calculate_impairment:(delay=99(ms), loss=0%), Io=0 Iq=0 Idte=0 Idd=2 Ie=10 Itot=12*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallGetVoipFlag:Data Bitmask=0x1, Call Id=8*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallGetVoipFlag:Flag=FALSE*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_decr_if_call_volume:Remote IP Address=172.16.13.175, Hwidb=FastEthernet0/0*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_decr_if_call_volume:Total Call Count=0, Voip Call Count=0, MMoip Call Count=0*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry:Incoming=TRUE*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_call_entry:ccFreeRawMsgInfo=0x644EB850Router#*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_call_entry:Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=TRUE)*May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_call_entry:Total Call Count=0*May 1 18:59:21.879: //8/ABCE697D8005/CCAPI/cc_delete_call_entry:Deleting profileTable[0x64B78600]*May 1 18:59:21.879: //8/xxxxxxxxxxxx/CCAPI/cc_get_call_entry:Call Entry Is Not Found*May 1 18:59:21.879: //8/xxxxxxxxxxxx/CCAPI/cc_get_call_entry:Call Entry Is Not FoundRouter#*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/ccCallGetVoipFlag:Data Bitmask=0x1, Call Id=9*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/ccCallGetVoipFlag:Flag=FALSE*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_api_call_disconnect_done:Prefix Is Not Defined From Peer; Peer=3600, Called Number=3600*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry:Incoming=FALSE*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_delete_call_entry:Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=FALSE)*May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_delete_call_entry:Deleting profileTable[0x6453F228]debug voip ccapi inout on the Originating Gateway
Router# debug voip ccapi inoutvoip ccapi inout debugging is onRouter#*Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/cc_api_display_ie_subfields:cc_api_call_setup_ind_common:cisco-username=----- ccCallInfo IE subfields -----cisco-ani=4085550111cisco-anitype=2cisco-aniplan=1cisco-anipi=0cisco-anisi=1dest=83103cisco-desttype=0cisco-destplan=0cisco-rdn=cisco-rdntype=-1cisco-rdnplan=-1cisco-rdnpi=-1cisco-rdnsi=-1cisco-redirectreason=-1The following lines show information about the calling and called numbers. The network presentation indicator (NPI) shows the type of transmission. The Incoming Dial-Peer field shows that the incoming dial peer has been matched.
*Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/cc_api_call_setup_ind_common:Interface=0x64F26F10, Call Info(Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),Called Number=83103(TON=Unknown, NPI=Unknown),Calling Translated=FALSE, Subsriber Type Str=RegularLine, FinalDestinationFlag=TRUE,Incoming Dial-peer=1, Progress Indication=NULL(0), Calling IE Present=TRUE,Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=-1*Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/ccCheckClipClir:In: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed)*Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/ccCheckClipClir:Out: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed)In the following event, the call leg is established. The CallEntry ID field changes from -1 to 19.
*Apr 18 20:42:19.347: //19/9C5A9CA88009/CCAPI/cc_api_call_setup_ind_common:Set Up Event Sent;Call Info(Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),Called Number=83103(TON=Unknown, NPI=Unknown))*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/cc_process_call_setup_ind:Event=0x63FF4730*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetContext:Context=0x652A9858*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/cc_process_call_setup_ind:>>>>CCAPI handed cid 19 with tag 1 to app "Default"*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallProceeding:Progress Indication=NULL(0)*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetupRequest:Destination=, Calling IE Present=TRUE, Mode=0,Outgoing Dial-peer=3600, Params=0x652AA4A8, Progress Indication=NULL(0)*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCheckClipClir:In: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed)*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCheckClipClir:Out: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed)*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetupRequest:Destination Pattern=360., Called Number=3600, Digit Strip=FALSE*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetupRequest:Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),Called Number=3600(TON=Unknown, NPI=Unknown),Redirect Number=, Display Info=Account Number=, Final Destination Flag=TRUE,Guid=9C5A9CA8-5243-11D6-8009-00059A3A15A0, Outgoing Dial-peer=3600*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/cc_api_display_ie_subfields:ccCallSetupRequest:cisco-username=----- ccCallInfo IE subfields -----cisco-ani=4085550111cisco-anitype=2cisco-aniplan=1cisco-anipi=0cisco-anisi=1dest=3600cisco-desttype=0cisco-destplan=0cisco-rdn=cisco-rdntype=-1cisco-rdnplan=-1cisco-rdnpi=-1cisco-rdnsi=-1cisco-redirectreason=-1In the following lines, the outgoing dial peer is matched:
*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccIFCallSetupRequestPrivate:Interface=0x63EAF24C, Interface Type=1, Destination=, Mode=0x0,Call Params(Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),Called Number=3600(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,Subsriber Type Str=RegularLine, FinalDestinationFlag=TRUE, Outgoing Dial-peer=3600, Call Count On=FALSE,Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)*Apr 18 20:42:19.351: //20/9C5A9CA88009/CCAPI/ccIFCallSetupRequestPrivate:SPI Call Setup Request Is Success; Interface Type=1, FlowMode=1*Apr 18 20:42:19.351: //20/9C5A9CA88009/CCAPI/ccCallSetContext:Context=0x652AA458*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccSaveDialpeerTag:Outgoing Dial-peer=3600*Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccSaveDialpeerTag:Outgoing Dial-peer=3600*Apr 18 20:42:19.367: //20/9C5A9CA88009/CCAPI/cc_api_call_proceeding:Interface=0x652F6388, Progress Indication=NULL(0)The following lines show call progress. The progress and signal indications are shown.
*Apr 18 20:42:19.371: //20/9C5A9CA88009/CCAPI/cc_api_call_cut_progress:Interface=0x652F6388, Progress Indication=INBAND(8), Signal Indication=SIGNAL RINGBACK(1),Cause Value=0*Apr 18 20:42:19.371: //20/9C5A9CA88009/CCAPI/cc_api_call_cut_progress:Call Entry(Responsed=TRUE)*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccCallCutProgress:Progress Indication=INBAND(8), Signal Indication=SIGNAL RINGBACK(1), Cause Value=0Voice Call Send Alert=FALSE, Call Entry(AlertSent=FALSE)*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccCallCutProgress:Call Entry(Responsed=TRUE)The following lines show the tone generation information:
*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccGenerateToneInfo:Stop Tone On Digit=FALSE, Tone=Null,Tone Direction=Network, Params=0x0, Call Id=19*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccConferenceCreate:Conference Id=0x652F723C, Call Id1=19, Call Id2=20, Tag=0x0*Apr 18 20:42:19.371: //20/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:Conference Id=0x6, Source Interface=0x63EAF24C, Source Call Id=20,Destination Call Id=19, Disposition=0x0, Tag=0x0*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccConferenceCreate:Call Entry(Conference Id=0x6, Destination Call Id=20)*Apr 18 20:42:19.371: //20/9C5A9CA88009/CCAPI/ccConferenceCreate:Call Entry(Conference Id=0x6, Destination Call Id=19)*Apr 18 20:42:19.371: //19/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19,Destination Call Id=20, Disposition=0x0, Tag=0x0*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_generic_bridge_done:Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19,Destination Call Id=20, Disposition=0x0, Tag=0x0*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_api_caps_ind:Destination Interface=0x63EAF24C, Destination Call Id=20, Source Call Id=19,Caps(Codec=0x2887F, Fax Rate=0xBF, Vad=0x3,Modem=0x2, Codec Bytes=0, Signal Type=3)*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_api_caps_ind:Caps(Playout Mode=1, Playout Initial=60(ms), Playout Min=40(ms),Playout Max=300(ms), Fax Nom=300(ms))*Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_process_notify_bridge_done:Conference Id=0x6, Call Id1=19, Call Id2=20*Apr 18 20:42:19.375: //20/9C5A9CA88009/CCAPI/cc_api_caps_ind:Destination Interface=0x64F26F10, Destination Call Id=19, Source Call Id=20,Caps(Codec=0x4, Fax Rate=0x1, Vad=0x2,Modem=0x2, Codec Bytes=20, Signal Type=2)*Apr 18 20:42:19.375: //20/9C5A9CA88009/CCAPI/cc_api_caps_ind:Caps(Playout Mode=1, Playout Initial=60(ms), Playout Min=40(ms),Playout Max=300(ms), Fax Nom=300(ms))The following lines show codec information:
*Apr 18 20:42:19.375: //20/9C5A9CA88009/CCAPI/cc_api_caps_ack:Destination Interface=0x64F26F10, Destination Call Id=19, Source Call Id=20,Caps(Codec=g729r8(0x4), Fax Rate=FAX_RATE_NONE(0x1), Vad=ON(0x2),Modem=ON(0x2), Codec Bytes=20, Signal Type=2, Seq Num Start=6872)*Apr 18 20:42:19.375: //19/9C5A9CA88009/CCAPI/cc_api_caps_ack:Destination Interface=0x63EAF24C, Destination Call Id=20, Source Call Id=19,Caps(Codec=g729r8(0x4), Fax Rate=FAX_RATE_NONE(0x1), Vad=ON(0x2),Modem=ON(0x2), Codec Bytes=20, Signal Type=2, Seq Num Start=6872)*Apr 18 20:42:19.375: //19/9C5A9CA88009/CCAPI/cc_api_voice_mode_event:Call Id=19*Apr 18 20:42:19.375: //19/9C5A9CA88009/CCAPI/cc_api_voice_mode_event:Call Entry(Context=0x652A9858)The following lines show progress indication information. In this case, the event shows that the destination is not ISDN.
*Apr 18 20:42:26.855: //20/9C5A9CA88009/CCAPI/cc_api_call_connected:Interface=0x652F6388, Data Bitmask=0x0, Progress Indication=DESTINATION IS NON ISDN(2),Connection Handle=0*Apr 18 20:42:26.855: //20/9C5A9CA88009/CCAPI/cc_api_call_connected:Call Entry(Connected=TRUE, Responsed=TRUE, Retry Count=0)*Apr 18 20:42:26.855: //19/9C5A9CA88009/CCAPI/ccCallConnect:Progress Indication=DESTINATION IS NON ISDN(2), Data Bitmask=0x0*Apr 18 20:42:26.855: //19/9C5A9CA88009/CCAPI/ccCallConnect:Call Entry(Connected=TRUE, Responsed=TRUE)*Apr 18 20:42:26.855: //20/9C5A9CA88009/CCAPI/ccSaveDialpeerTag:Incoming Dial-peer=1*Apr 18 20:42:26.859: //19/9C5A9CA88009/CCAPI/ccSaveDialpeerTag:Outgoing Dial-peer=3600*Apr 18 20:42:26.859: //20/9C5A9CA88009/CCAPI/ccCallFeature:Feature Type=24, Call Id=20This event shows that the call is disconnected.
*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnected:Cause Value=16, Interface=0x64F26F10, Call Id=19*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnected:Call Entry(Responsed=TRUE, Cause Value=16, Retry Count=0)*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/ccConferenceDestroy:Conference Id=0x6, Tag=0x0*Apr 18 20:43:16.795: //20/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done:Conference Id=0x6, Source Interface=0x63EAF24C, Source Call Id=20,Destination Call Id=19, Disposition=0x0, Tag=0x0*Apr 18 20:43:16.795: //19/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done:Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19,Destination Call Id=20, Disposition=0x0, Tag=0x0*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_generic_bridge_done:Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19,Destination Call Id=20, Disposition=0x0, Tag=0x0*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/ccCallDisconnect:Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=16)*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/ccCallDisconnect:Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16)*Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_api_get_transfer_info:Transfer Number Is Null*Apr 18 20:43:16.795: //20/9C5A9CA88009/CCAPI/ccCallDisconnect:Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)*Apr 18 20:43:16.795: //20/9C5A9CA88009/CCAPI/ccCallDisconnect:Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16)*Apr 18 20:43:16.795: //20/9C5A9CA88009/CCAPI/cc_api_get_transfer_info:Transfer Number Is Null*Apr 18 20:43:16.803: //20/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done:Disposition=0, Interface=0x652F6388, Tag=0x0, Call Id=20,Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry Count=0)*Apr 18 20:43:16.803: //20/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done:Call Disconnect Event Sent*Apr 18 20:43:16.803: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done:Disposition=0, Interface=0x64F26F10, Tag=0x0, Call Id=19,Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry Count=0)*Apr 18 20:43:16.803: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done:Call Disconnect Event Sentdebug voip ccapi service on the Terminating Gateway
Router# debug voip ccapi servicevoip ccapi service debugging is on*May 1 19:08:41.803: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:Searching Node;Called Number=3600, Call Transfer Consult Id=This debug shows non-call related events. In this case, information about the timer is shown.
*May 1 19:08:48.027: //-1/xxxxxxxxxxxx/CCAPI/cc_handle_periodic_timer:Calling The Callback, ccTimerctx=0x63B368C0*May 1 19:08:48.027: //-1/xxxxxxxxxxxx/CCAPI/ccTimerStart:ccTimerctx=0x63B368C0*May 1 19:10:08.615: //-1/xxxxxxxxxxxx/CCAPI/cc_api_icpif:ExpectFactor=0xAdebug voip ccapi error
To trace error logs in the call control application programming interface (CCAPI), use the debug voip ccapi error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip ccapi error
no debug voip ccapi error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
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
Related Commands
debug voip ccapi inout
Traces the execution path through the CCAPI.
voice call debug
Allows configuration of the voice call debug output.
debug voip ccapi inout
To trace the execution path through the call control application programming interface (CCAPI), use the debug voip ccapi inout command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip ccapi inout
no debug voip ccapi inout
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
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
Examples
The following example shows the call setup indicated and accepted by the voice gateway:
Router# debug voip ccapi inout*Mar 1 15:35:53.588: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructTDUsrContainer:usrContainer[0x638C1BF0], magic[FACE0FFF]*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilAddDataToUsrContainer:container=0x638C1BF0, tagID=6, dataSize=16, instID=-1,modifier=1*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject:tdObject[0x638BC1AC], nxtElem[0x0], magic[0xFACE0FFF] tagID[6], dataLen[16],modif[1]*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToContainer:Adding tdObject[0x638BC1AC] instID[-1] into container[0x638C1BF0]*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilAddDataToUsrContainer:container=0x638C1BF0, tagID=5, dataSize=276, instID=-1,modifier=1*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject:tdObject[0x63401148], nxtElem[0x0], magic[0xFACE0FFF] tagID[5], dataLen[276],modif[1]*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToContainer:Adding tdObject[0x63401148] instID[-1] into container[0x638C1BF0]In the following lines, the call control API (CCAPI) receives the call setup. The called number is 34999, and the calling number is 55555. The calling number matches dial peer 10002.
*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/cc_api_display_ie_subfields:*Mar 1 15:35:53.592: cc_api_call_setup_ind:*Mar 1 15:35:53.592: cisco-username=*Mar 1 15:35:53.596: ----- ccCallInfo IE subfields -----*Mar 1 15:35:53.596: cisco-ani=55555*Mar 1 15:35:53.596: cisco-anitype=0*Mar 1 15:35:53.596: cisco-aniplan=0*Mar 1 15:35:53.596: cisco-anipi=0*Mar 1 15:35:53.596: cisco-anisi=0*Mar 1 15:35:53.596: dest=34999*Mar 1 15:35:53.596: cisco-desttype=0*Mar 1 15:35:53.596: cisco-destplan=0*Mar 1 15:35:53.596: cisco-rdn=*Mar 1 15:35:53.596: cisco-rdntype=-1*Mar 1 15:35:53.596: cisco-rdnplan=-1*Mar 1 15:35:53.596: cisco-rdnpi=-1*Mar 1 15:35:53.596: cisco-rdnsi=-1*Mar 1 15:35:53.596: cisco-redirectreason=-1*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:(vdbPtr=0x637EC1E0, callInfo={called=34999,called_oct3=0x80,calling=55555,calling_oct3=0x80,calling_oct3a=0x0, calling_xlated=false,subscriber_type_str=RegularLine,fdest=1,peer_tag=10002, prog_ind=0,callingIE_present 1, src_route_label=, tgt_route_label= clid_transparent=0},callID=0x637B4278)*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: type 13 , prot 0*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:*Mar 1 15:35:53.596: ccCheckClipClir: calling number is: "55555", calling oct3a is: 0x0*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:*Mar 1 15:35:53.596: Calling Party number is User Provided*Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:*Mar 1 15:35:53.596: Leaving ccCheckClipClircalling number is: "55555"calling oct3 is: 0x80calling oct3a is: 0x0In the next line, 44 is the CallEntry ID.
*Mar 1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: Increment call volume: 0*Mar 1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: current call volume: 1*Mar 1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: entry's incoming TRUE.*Mar 1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: is_incoming is TRUE*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructHashProfileTab: profileTable[0x6380E11C], numBuckets[11], numEntries[0]*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtProfileTableBuildManager: Invoking necessary profileTable updaters...*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContainer: Updating profileTable[0x6380E11C] with objects in container[0x638C1BF0]*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContainer: obtained key[5] for the tag[6]*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToProfileBucket: profileTable[0x6380E11C], tdObject[0x638BC1AC]*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContainer: obtained key[0] for the tag[5]*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToProfileBucket: profileTable[0x6380E11C], tdObject[0x63401148]*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtProfileTableBuildManager:*Mar 1 15:35:53.600: ccTDUtilDumpAllElemInProfileTab: profileTable[0x6380E11C],numBuckets[11], numEntries[2]*Mar 1 15:35:53.600: Bucket { 0 } ------>0x63401148[0x0,t-5,l-276,d-0x63401168,m-1,u-56153,g-FACE0FFF]*Mar 1 15:35:53.604:*Mar 1 15:35:53.604: Bucket { 5 } ------>0x638BC1AC[0x0,t-6,l-16,d-0x638BC1CC,m-1,u-56153,g-FACE0FFF]*Mar 1 15:35:53.604:*Mar 1 15:35:53.604: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructTDUsrContainer: Container[0x638C1BF0]*Mar 1 15:35:53.604: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: not the VoIP or MMoIP*Mar 1 15:35:53.608: //-1/xxxxxxxxxxxx/CCAPI/cc_process_call_setup_ind: (event=0x63073AA0)In the next line, 45F2AAE28044 is the GUID. The tag 10002 entry shows that the incoming dial peer matched the CallEntry ID.
*Mar 1 15:35:53.608: //44/45F2AAE28044/CCAPI/cc_process_call_setup_ind: >>>>CCAPI handed cid 44 with tag 10002 to app "DEFAULT"*Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(24=CC_EV_CALL_SETUP_IND), cid(44), disp(0)*Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(SSA_EV_CALL_SETUP_IND), cid(44), disp(0)*Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/ssaCallSetupInd:The next line shows CallEntry ID in hexadecimal form, 0x2C (44 in decimal). The CallID and GUID numbers have been identified. The incoming dial-peer is 10002.
*Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/CCAPI/ccCallSetContext: (callID=0x2C, context=0x634A430C)*Mar 1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: cid(44), st(SSA_CS_MAPPING),oldst(0), ev(24)ev->e.evCallSetupInd.nCallInfo.finalDestFlag= 1*Mar 1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: src route label=, tgt route label= tg_label_flag 0x0*Mar 1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: finalDest cllng(55555), clled(34999) tgt_route_label()tg_label_flag 0x0*Mar 1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: cid(44),st(SSA_CS_CALL_SETTING),oldst(0), ev(24)dpMatchPeersMoreArg result= 0For 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: ssaSetupPeer cid(44) peer list: tag(10001) called number (34999) tag(20002) called number(34999)*Mar 1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaSetupPeer: dialpeer tags in rotary= 10001 20002The 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), destPat(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, Out=1The 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, prog_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_present 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 oct3ais:0x0*Mar 1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:*Mar 1 15:35:53.616: ccCheckClipClir: calling number is: "55555", calling oct3ais: 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 ccCheckClipClircalling number is: "55555"calling oct3 is: 0x80calling oct3a is: 0x0*Mar 1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: after ccCheckClipClir - calling oct3a is:0x0The next line shows that all digits are passed.
*Mar 1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: dest pattern 34999, 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= display_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: (vdbPtr=0x62EC61A4, dest=, callParams={called=34999,called_oct3=0x80, calling=55555,calling_oct3=0x80, calling_oct3a= 0x0, calling_xlated=false, subscriber_type_str=RegularLine, fdest=1, voice_peer_tag=10001},mode=0x0)*Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:*Mar 1 15:35:53.620: ccIFCallSetupRequestPrivate: src route label tgt route label tg_label_flag 0x0*Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: vdbPtr type = 1*Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:*Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: (vdbPtr=0x62EC61A4, dest=, callParams={called=34999, called_oct3 0x80, calling=55555,calling_oct3 0x80, calling_oct3a 0x0, calling_xlated=false, fdest=1, voice_peer_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 incomingentry*Mar 1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: entry's incoming FALSE.*Mar 1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: is_incomingis FALSE*Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag: (callID=0x2C, dialpeer_tag=10001)*Mar 1 15:35:53.624: //45/xxxxxxxxxxxx/CCAPI/ccCallSetContext: (callID=0x2D, context=0x634A537C) 0x2D (decimal 45 is the second call leg ID).*Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/ccCallReportDigits: (callID=0x2C,enable=0x0)The voice gateway informs the incoming call leg that digits were forwarded.
*Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/cc_api_call_report_digits_done: (vdbPtr=0x637EC1E0, callID=0x2C, disp=0)*Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(54=CC_EV_CALL_REPORT_DIGITS_DONE), cid(44), disp(0)*Mar 1 15:35:53.624: //44/45F2AAE28044/SSRouter#APP:10002:-1/ssaTraceSct: cid(44)st(SSA_CS_CALL_SETTING)ev(SSA_EV_CALL_REPORT_DIGITS_DONE)oldst(SSA_CS_MAPPING)cfid(-1)csize(0)in(1)fDest(1)*Mar 1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaTraceSct: -cid2(45)st2(SSA_CS_CALL_SETTING)oldst2(SSA_CS_MAPPING)*Mar 1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaDebugPeers: ssaReportDigitsDone cid(44) peer list: tag(20002) called number (34999)*Mar 1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaReportDigitsDone: callid=44 Reporting disabled.*Mar 1 15:35:53.628: //-1/xxxxxxxxxxxx/CCAPI/cc_api_supported_data: data_mode=0x10082*Mar 1 15:35:53.628: //45/xxxxxxxxxxxx/CCAPI/cc_api_get_ic_leg_obtained_numbers: callID=0x2DThe 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 IPis 171.69.85.111*Mar 1 15:35:53.632: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: hwidb is Ethernet0/0*Mar 1 15:35:53.632: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: create entry in list: 1*Mar 1 15:35:53.636: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetInstanceCount: For tagID[1] of callID[45]*Mar 1 15:35:53.636: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessManager: No profileTable set for callID[45]*Mar 1 15:35:53.636: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetInstanceCount: For tagID[2] of callID[45]*Mar 1 15:35:53.636: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessManager: No profileTable set for callID[45]The next line shows that the voice gateway received a call proceeding message from the terminating gateway, and then the following line shows that the voice gateway received a call alert from the terminating gateway.
*Mar 1 15:35:53.740: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_proceeding: (vdbPtr=0x62EC61A4, callID=0x2D,prog_ind=0x0)*Mar 1 15:35:53.740: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_alert: (vdbPtr=0x62EC61A4, callID=0x2D, prog_ind=0x0, sig_ind=0x1)*Mar 1 15:35:53.744: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(21=CC_EV_CALL_PROCEEDING), cid(45), disp(0)*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS_CALL_SETTING)ev(SSA_EV_CALL_PROCEEDING)oldst(SSA_CS_MAPPING)cfid(-1)csize(0)in(0)fDest(0)*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA_CS_CALL_SETTING)oldst2(SSA_CS_CALL_SETTING)*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaCallProc:*Mar 1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C)*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaIgnore: cid(45), st(SSA_CS_CALL_SETTING),oldst(1), ev(21)*Mar 1 15:35:53.744: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(7=CC_EV_CALL_ALERT), cid(45), disp(0)*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS_CALL_SETTING)ev(SSA_EV_CALL_ALERT)oldst(SSA_CS_CALL_SETTING)cfid(-1)csize(0)in(0)fDest(0)*Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA_CS_CALL_SETTING)oldst2(SSA_CS_CALL_SETTING)*Mar 1 15:35:53.744: //44/45F2AAE28044/SSAPP:10002:-1/ssaAlert:*Mar 1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C)Router#The voice gateway forwarded a call alert to the originating gateway.
*Mar 1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccCallAlert: (callID=0x2C, prog_ind=0x0, sig_ind=0x1)Router#The phone is answered at the called number.
Router#!call answeredRouter#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=0x62EC61A4, callID=0x2D), prog_ind = 0*Mar 1 15:36:05.016: //45/45F2AAE28044/CCAPI/cc_api_call_connected: setting callEntry->connected to TRUEThe 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=0x2D, accounting=0*Mar 1 15:36:05.020: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(8=CC_EV_CALL_CONNECTED), cid(45), disp(0)*Mar 1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS_ALERT_RCVD)ev(SSA_EV_CALL_CONNECTED)oldst(SSA_CS_CALL_SETTING)cfid(-1)csize(0)in(0)fDest(0)*Mar 1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA_CS_ALERT_RCVD)oldst2(SSA_CS_CALL_SETTING)*Mar 1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaConnect:*Mar 1 15:36:05.020: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C)The next lines show a conference being set up between the two call legs 0x2C and 0x2D. Bridge complete messages are sent to both the terminating and originating gateways.
*Mar 1 15:36:05.020: //44/xxxxxxxxxxxx/CCAPI/ccConferenceCreate: (confID=0x63086424, 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=0x62EC61A4, dstCallId=0x2D, srcCallId=0x2C,caps={codec=0x2887F, fax_rate=0xBF, vad=0x3, modem=0x2codec_bytes=0, signal_type=3})*Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (Playout: mode 0,initial 60,min 40, max 300)*Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(29=CC_EV_CONF_CREATE_DONE), cid(44), disp(0)*Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: cid(44)st(SSA_CS_CONFERENCING)ev(SSA_EV_CONF_CREATE_DONE)oldst(SSA_CS_CALL_SETTING)cfid(21)csize(2)in(1)fDest(1)*Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2(SSA_CS_CONFERENCING)oldst2(SSA_CS_ALERT_RCVD)*Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaConfCreateDone:*Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/ccCallConnect: (callID=0x2C), prog_ind = 0*Mar 1 15:36:05.024: //44/45F2AAE28044/CCAPI/ccCallConnect: setting callEntry->connected to TRUE*Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaDebugPeers: ssaFlushPeerTagQueue cid(44) peer list: tag(20002) called number (34999)*Mar 1 15:36:05.028: //-1/xxxxxxxxxxxx/CCAPI/cc_process_notify_bridge_done: (event=0x63067FC0)The voice gateway sets up negotiating capability with the terminating VoIP leg.
*Mar 1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0codec_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=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0codec_bytes=20, signal_type=2, seq_num_start=2944})*Mar 1 15:36:05.028: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ack: (dstVdbPtr=0x62EC61A4, dstCallId=0x2D, srcCallId=0x2C,caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0codec_bytes=20, signal_type=2, seq_num_start=2944})*Mar 1 15:36:05.032: //44/xxxxxxxxxxxx/CCAPI/cc_api_voice_mode_event: callID=0x2C*Mar 1 15:36:05.032: //44/45F2AAE28044/CCAPI/cc_api_voice_mode_event: Call Pointer =634A430C*Mar 1 15:36:05.032: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(52=CC_EV_VOICE_MODE_DONE), cid(44), disp(0)*Mar 1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct:Router#Router# cid(44)st(SSA_CS_ACTIVE)ev(SSA_EV_VOICE_MODE_DONE)oldst(SSA_CS_CONFERENCING)cfid(21)csize(2)in(1)fDest(1)*Mar 1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2(SSA_CS_ACTIVE)oldst2(SSA_CS_ALERT_RCVD)*Mar 1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaIgnore: cid(44), st(SSA_CS_ACTIVE),oldst(5), ev(52)Router#Router#! digit punchedRouter#The phone at the terminating gateway enters digit 1.
*Mar 1 15:36:11.204: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,digit=1, digit_begin_flags=0x0, rtp_timestamp=0x0rtp_expiration=0x0, dest_mask=0x2)*Mar 1 15:36:11.504: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,digit=1,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), digit_tone_mode=0The phone at the terminating gateway enters digit 2.
*Mar 1 15:36:11.604: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,digit=2, digit_begin_flags=0x0, rtp_timestamp=0x0rtp_expiration=0x0, dest_mask=0x2)*Mar 1 15:36:11.904: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,digit=2,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), digit_tone_mode=0Router#Router#*Mar 1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/cc_handle_periodic_timer: Callingthe callback, ccTimerctx - 0x628B6330*Mar 1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/ccTimerStart: ccTimerctx - 0x628B6330Router#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=0x15, 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=0x15, srcIF=0x637EC1E0, srcCallID=0x2C, dstCallID=0x2D, disposition=0 tag=0x0)*Mar 1 15:36:22.924: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(30=CC_EV_CONF_DESTROY_DONE), cid(44), disp(0)*Mar 1 15:36:22.924: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: cid(44)st(SSA_CS_CONF_DESTROYING)ev(SSA_EV_CONF_DESTROY_DONE)oldst(SSA_CS_ACTIVE)cfid(21)csize(2)in(1)fDest(1)*Mar 1 15:36:22.924: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2(SSA_CS_CONF_DESTROYING)oldst2(SSA_CS_ACTIVE)*Mar 1 15:36:22.924: //45/45F2AAE28044/SSAPP:0:-1/ssaConfDestroyDone:*Mar 1 15:36:22.924: //44/xxxxxxxxxxxx/CCAPI/ccCallDisconnect: (callID=0x2C, cause=0x10 tag=0x0)The voice gateway stops call accounting on the incoming call, indicated by the leg_type=True message. The cause code is then set for the originating leg.
*Mar 1 15:36:22.924: //44/45F2AAE28044/CCAPI/ccCallDisconnect: calling accounting start for callID=44 leg_type=1*Mar 1 15:36:22.924: //44/45F2AAE28044/CCAPI/ccCallDisconnect: existing_cause =0x0, new_cause = 0x10*Mar 1 15:36:22.924: //44/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info: (callID=0x2C)*Mar 1 15:36:22.924: //45/xxxxxxxxxxxx/CCAPI/ccCallDisconnect: (callID=0x2D, cause=0x10 tag=0x0)The voice gateway stops call accounting for the outgoing call, indicated by the leg_type=False message. The cause code is verified for the terminating leg.
*Mar 1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: calling accounting start for callID=45 leg_type=0*Mar 1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: existing_cause =0x10, new_cause = 0x10*Mar 1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: using the existing_cause 0x10*Mar 1 15:36:22.928: //45/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info: (callID=0x2D)*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_api_icpif: expect factor = 0*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/g113_calculate_impairment: (delay=79,loss=0), Io=0 Iq=0 Idte=0 Idd=0 Ie=10 Itot=10*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: the remoteIP is 171.69.85.111*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: hwidb is Ethernet0/0*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: reduce callnum of entry: 0, voip: 0, mmoip: 0*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: remove an entry*Mar 1 15:36:22.932: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnect_done: (vdbPtr=0x62EC61A4, callID=0x2D, disp=0, tag=0x0)*Mar 1 15:36:22.932: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessManager: No profileTable set for callID[45]*Mar 1 15:36:22.936: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetDataByRef: No tdObjectfound in profileTable for tagID[6] of callID[45]*Mar 1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: not incomingentry*Mar 1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: entry's incoming FALSE.*Mar 1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: is_incomingis FALSE*Mar 1 15:36:22.940: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(12=CC_EV_CALL_DISCONNECT_DONE), cid(45), disp(0)*Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS_DISCONNECTING)ev(SSA_EV_CALL_DISCONNECT_DONE)oldst(SSA_CS_ACTIVE)cfid(-1)csize(2)in(0)fDest(0)*Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA_CS_DISCONNECTING)oldst2(SSA_CS_CONF_DESTROYING)*Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaDisconnectDone:*Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaAAA_CheckAccounting: accounting generation enabled*Mar 1 15:36:22.940: //45/xxxxxxxxxxxx/CCAPI/ccCallSetAAA_Accounting: callID=0x2D, accounting=0*Mar 1 15:36:22.944: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: not the VoIP or MMoIP*Mar 1 15:36:22.948: //44/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnect_done: (vdbPtr=0x637EC1E0, callID=0x2C, disp=0, tag=0x0)*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: ccFreeRawMsgInfo(0x6307595C)*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: Decrement call volume counter 1*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: current call volume: 0*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: entry's incoming TRUE.*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: is_incomingis TRUE*Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: Deleting profileTable[0x6380E11C]*Mar 1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructTDHashProfileTab: Destructor Profile Table (0x6380E11C)*Mar 1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructInstanceTDObject: tdObject[0x63401148] tagID[5]*Mar 1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructInstanceTDObject: tdObject[0x638BC1AC] tagID[6]*Mar 1 15:36:22.956: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(12=CC_EV_CALL_DISCONNECT_DONE), cid(44), disp(0)*Mar 1 15:36:22.956: //44/45F2AAE28044/SSAPP:10002:-1/ssaTraceSct: cid(44)st(SSA_CS_DISCONNECTING)ev(SSA_EV_CALL_DISCONNECT_DONE)oldst(SSA_CS_CONF_DESTROYING)cfid(-1)csize(1)in(1)fDest(1)Router#*Mar 1 15:36:22.956: //44/45F2AAE28044/SSAPP:10002:-1/ssaDisconnectDone:Related Commands
debug voip ccapi error
Traces error logs in the CCAPI.
voice call debug
Allows configuration of the voice call debug output.
debug voip confmsp
To display debugging information from the Conference Media Service Provider (CONFMSP) and its related applications, use the debug voip confmsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip confmsp
no debug voip confmsp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXECCommand History
Examples
The following is sample output from the debug voip confmsp command:
Router# debug voip confmspCONFMSP debugging is on...00:06:44:confmsp_setup_request:callID (6),00:06:44:confmsp_setup_request:conf structure (63DD27E4) created,00:06:44:confmsp_bridge:confID(4), callIDs(6,5) xmitFunc 61D46D4C, dstIF 6491288000:06:44:confmsp_bridge:confID(4), callIDs(6,5) event queued00:06:44:confmsp_act_bridge: state = CONFMSP_STATE_SETUP, event=EV_CONFMSP_BRIDGING00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 100:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 100:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_SETUP,event:EV_CONFMSP_BRIDGING, next_state:CONFMSP_STATE_CONNECT_CONFEREE00:06:44:confmsp_get_dsmp_req_status:condition to be returned FALSE00:06:44:confmsp_connect_response:found conf (63DD27E4) dsmp ret is 100:06:44:confmsp_act_bridge_success: state = CONFMSP_STATE_CONNECT_CONFEREE,event=EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS confmsp_caps_ind:context = 65241B3400:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECT_CONFEREE,event:EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_CONNECTED00:06:44:confmsp_bridge:confID(5), callIDs(6,7) xmitFunc 61D46D4C, dstIF 6491288000:06:44:confmsp_bridge:confID(5), callIDs(6,7) event queued00:06:44:confmsp_act_bridge: state = CONFMSP_STATE_SETUP, event=EV_CONFMSP_BRIDGING00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 100:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 100:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_SETUP,event:EV_CONFMSP_BRIDGING, next_state:CONFMSP_STATE_CONNECT_CONFEREE00:06:44:confmsp_get_dsmp_req_status:condition to be returned FALSE00:06:44:confmsp_connect_response:found conf (6358A338) dsmp ret is 100:06:44:confmsp_act_bridge_success: state = CONFMSP_STATE_CONNECT_CONFEREE,event=EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS confmsp_caps_ind:context = 63588E7000:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECT_CONFEREE,event:EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_CONNECTED00:06:44:confmsp_bridge:confID(6), callIDs(6,8) xmitFunc 61D46D4C, dstIF 6491288000:06:44:confmsp_bridge:confID(6), callIDs(6,8) event queued00:06:44:confmsp_act_bridge: state = CONFMSP_STATE_SETUP, event=EV_CONFMSP_BRIDGING00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 100:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 100:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_SETUP,event:EV_CONFMSP_BRIDGING, next_state:CONFMSP_STATE_CONNECT_CONFEREE00:06:44:confmsp_get_dsmp_req_status:condition to be returned FALSE00:06:44:confmsp_connect_response:found conf (6358CE50) dsmp ret is 100:06:44:confmsp_act_bridge_success: state = CONFMSP_STATE_CONNECT_CONFEREE,event=EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS confmsp_caps_ind:context = 63DD252400:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECT_CONFEREE,event:EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_CONNECTED00:07:28:confmsp_bdrop:confID(4), callIDs(6,5)00:07:28:confmsp_bdrop:confID(4), callIDs(6,5) event queued00:07:28:confmsp_act_bdrop: state = CONFMSP_STATE_CONNECTED, event=EV_CONFMSP_BRIDGEDROP00:07:28:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECTED,event:EV_CONFMSP_BRIDGEDROP, next_state:CONFMSP_STATE_DISCONNECT_CONFEREE00:07:28:confmsp_get_dsmp_req_status:condition to be returned FALSE00:07:28:confmsp_disconnect_response:found conf (63DD27E4)00:07:28:confmsp_connect_response:found conf (63DD27E4) dsmp ret is 1000:07:28:confmsp_act_bdrop_success: state = CONFMSP_STATE_DISCONNECT_CONFEREE,event=EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS00:07:28:CNFSM:cur_container:confmsp container,cur_state:CONFMSP_STATE_DISCONNECT_CONFEREE,event:EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_BRIDGE_DROPPED00:07:28:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED,event:CNFSM_LAMBDA_EVENT, next_state:CNFSM_NO_STATE_CHANGE00:07:29:confmsp_bdrop:confID(6), callIDs(6,8)00:07:29:confmsp_bdrop:confID(6), callIDs(6,8) event queued00:07:29:confmsp_bdrop:confID(5), callIDs(6,7)00:07:29:confmsp_bdrop:confID(5), callIDs(6,7) event queued00:07:29:confmsp_act_bdrop: state = CONFMSP_STATE_CONNECTED, event=EV_CONFMSP_BRIDGEDROP00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECTED,event:EV_CONFMSP_BRIDGEDROP, next_state:CONFMSP_STATE_DISCONNECT_CONFEREE00:07:29:confmsp_get_dsmp_req_status:condition to be returned FALSE00:07:29:confmsp_act_bdrop: state = CONFMSP_STATE_CONNECTED, event=EV_CONFMSP_BRIDGEDROP00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECTED,event:EV_CONFMSP_BRIDGEDROP, next_state:CONFMSP_STATE_DISCONNECT_CONFEREE00:07:29:confmsp_get_dsmp_req_status:condition to be returned FALSE00:07:29:confmsp_disconnect_response:found conf (6358CE50)00:07:29:confmsp_connect_response:found conf (6358CE50) dsmp ret is 1000:07:29:confmsp_act_bdrop_success: state = CONFMSP_STATE_DISCONNECT_CONFEREE,event=EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS00:07:29:CNFSM:cur_container:confmsp container,cur_state:CONFMSP_STATE_DISCONNECT_CONFEREE,event:EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_BRIDGE_DROPPED00:07:29:confmsp_act_terminate: state = CONFMSP_STATE_BRIDGE_DROPPED,event=CNFSM_LAMBDA_EVENT00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED,event:CNFSM_LAMBDA_EVENT, next_state:CNFSM_NULL_STATE00:07:29:confmsp_free_conf:freeing 6358CE5000:07:29:confmsp_disconnect_response:found conf (6358A338)00:07:29:confmsp_connect_response:found conf (6358A338) dsmp ret is 1000:07:29:confmsp_act_bdrop_success: state = CONFMSP_STATE_DISCONNECT_CONFEREE,event=EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS00:07:29:CNFSM:cur_container:confmsp container,cur_state:CONFMSP_STATE_DISCONNECT_CONFEREE,event:EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_BRIDGE_DROPPED00:07:29:confmsp_act_terminate: state = CONFMSP_STATE_BRIDGE_DROPPED,event=CNFSM_LAMBDA_EVENT00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED,event:CNFSM_LAMBDA_EVENT, next_state:CNFSM_NULL_STATE00:07:29:confmsp_free_conf:freeing 6358A33800:07:29:confmsp_disconnect:callID (6)00:07:29:confmsp_disconnect:callID (6) event queued00:07:29:confmsp_act_disconnected: state = CONFMSP_STATE_BRIDGE_DROPPED,event=EV_CONFMSP_DISCONNECT00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED,event:EV_CONFMSP_DISCONNECT, next_state:CNFSM_NULL_STATE00:07:29:confmsp_free_conf:freeing 63DD27E4debug voip dcapi
To debug the device control application programming interface (DCAPI), use the debug voip dcapi command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip dcapi [error | inout]
no debug voip dcapi [error | inout]
Syntax Description
error
(Optional) Displays error logs in the DCAPI.
inout
(Optional) Displays the execution path through the DCAPI.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug voip dcapi error command traces the error logs in the DCAPI, which is the software layer that interfaces the SCCP Telephony Control Application (STCAPP) with the Cisco CallManager using the Skinny Client Control Protocol (SCCP). Error logs are generated during normal call processing when there are insufficient resources, or when there are problems in the device control API. This debug command shows error events or unexpected behavior in system software.
The debug voip dcapi inout command shows how a call executes through the software. This command traces the execution path through the DCAPI during communications with the SCCP service provider interface (SPI) and the call control API (CCAPI) that controls the physical voice port. You can use the output from this command to understand how devices are being handled by the APIs and to see the call setup and teardown operations performed on the telephony call leg.
Examples
Following is sample output from the debug voip dcapi inout command during call setup:
Router# debug voip dcapi inout*Jan 27 16:26:23.957: dc_api_device_set_ringer_res: Set Ringer message success*Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_stop_tone_res:*Jan 27 16:26:23.957: dc_api_device_stop_tone_res: Stop Tone message success*Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_media_open_rcv_channel:*Jan 27 16:26:23.957: dc_api_media_open_rcv_channel: evt DC_EV_MEDIA_OPEN_RCV_CHNL is successsfully enqueued to app*Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_stop_tone_res:*Jan 27 16:26:23.957: dc_api_device_stop_tone_res: Stop Tone message success*Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_call_state_res:*Jan 27 16:26:23.957: dc_api_device_call_state_res: Call State message success*Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_call_info_res:Table 309 describes the significant fields shown in the display.
Related Commands
debug voip application stcapp events
Debugs STCAPP events.
debug voip application stcapp functions
Debugs STCAPP functions.
debug voip dialpeer
To display information about the voice dial peers, use the debug voip dialpeer command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug voip dialpeer [all | default | detail | error [call [informational] | software [informational]] | | function | inout]
no debug voip dialpeer
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Disable console logging and use buffered logging before using the debug voip dialpeer command. Using the debug voip dialpeer command generates a large volume of debugging messages, which can affect router performance.
Examples
The following examples show output for variations of the debug voip dialpeer command:
•
•
For these examples, the topology shown in Figure 2 is used.
Figure 2 Network Topology for debug voip dialpeer Output Examples
debug voip dialpeer detail on the Originating Gateway
Router# debug voip dialpeer detailvoip dialpeer detail debugging is onRouter#The following event identifies the called number:
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=83103*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:Is Incoming=TRUE, Number Expansion=FALSE*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:Dial String=83103, Expanded String=83103, Calling Number=Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECHThe following event identifies the incoming dial peer and shows that it has been matched:
*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:Result=Success(0); Incoming Dial-peer=1 Is Matched*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=83103*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:Is Incoming=TRUE, Number Expansion=FALSE*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:Dial String=83103, Expanded String=83103, Calling Number=Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_FAX*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx
