Enhanced Debug Capabilities for Cisco Voice Gateways [Cisco IOS Software Releases 12.2 T]

Table Of Contents

Enhanced Debug Capabilities for Cisco Voice Gateways

Contents

Information About Enhanced Debug Capabilities for Cisco Voice Gateways

Debug Header Format

IVR Module Dependent List

CallEntry ID and GUID Call Legs

How to Manage the Voice Call Debug Output

Sample Output Examples for the Enhanced Debug Commands

Full GUID Header Example

Short Header Example

Setup and Teardown Example

Additional References

Related Documents

MIBs

Technical Assistance

Command Reference

debug rtsp all

debug rtsp api

debug rtsp client

debug rtsp error

debug rtsp pmh

debug rtsp session

debug rtsp socket

debug voip ccapi error

debug voip ccapi inout

debug voip ivr all

debug voip ivr applib

debug voip ivr callsetup

debug voip ivr digitcollect

debug voip ivr dynamic

debug voip ivr error

debug voip ivr script

debug voip ivr settlement

debug voip ivr states

debug voip ivr tclcommands

debug voip rawmsg

debug vtsp all

debug vtsp dsp

debug vtsp error

debug vtsp event

debug vtsp port

debug vtsp rtp

debug vtsp send-nse

debug vtsp session

debug vtsp stats

debug vtsp tone

debug vtsp vofr subframe

voice call debug

Enhanced Debug Capabilities for Cisco Voice Gateways

This feature module describes enhanced debugging capabilities for Cisco voice gateways.

Feature Specifications for the Enhanced Debug Capabilities for Cisco Voice Gateways

Feature History

Release

Modification

12.2(11)T

This feature added a call identification header for Cisco voice gateways to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.

12.2(15)T

The header-only option was removed and the short-header option was added.

Supported Platforms

Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660, Cisco AS5300, Cisco AS5350, Cisco AS5400, Cisco AS5800, Cisco AS5850, and Cisco MC3810 multiservice access concentrators.

Finding Support Information for Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Contents

•Information About Enhanced Debug Capabilities for Cisco Voice Gateways

•How to Manage the Voice Call Debug Output

•Sample Output Examples for the Enhanced Debug Commands

•Additional References

•Command Reference

Information About Enhanced Debug Capabilities for Cisco Voice Gateways

The enhanced debugging capability for Cisco voice gateways provides improvements to the debugging output in order to identify and track a specific call in a multiple-call environment. Before the implementation of this feature, it was difficult to correlate call information between gateways or to identify specific debug messages associated with a single call, when multiple voice calls were simultaneously active. The output was unstructured and presented in a free form.

This feature adds a standardized header to the debug outputs of multiple voice modules, such as voice telephony service provider (VTSP), call control application program interface (CCAPI), session application (SSAPP), and interactive voice response (IVR).

Use the following concepts to better understand the enhanced debug capabilities on Cisco voice gateways:

•Debug Header Format, page 2

•CallEntry ID and GUID Call Legs, page 4

Debug Header Format

The user can control the contents of the standardized header. The display options for the header are as follows:

•Short 6-byte GUID

•Full 16-byte GUID

•Short header which contains only the CallEntry ID

The format of the GUID headers are as follows:
//CallEntryID/GUID/Module-Dependent-List/Function-name:.

The format of the short header is as follows:
//CallEntryID/Function-name:.

The parameters in the header are as follows:

•CallEntryID—Numerically identifies a specific call leg such as an incoming ISDN call or an outgoing H.323 call. The CallentryID ranges between 1 and 32767. When the CallEntryID is not available to the function producing the debug message, the header displays the CallEntryID field as "-1."

•GUID—The global unique identifier (GUID) is a "meeting point" of multiple call legs, sometimes called a conference point. Each call is assigned a GUID, which is generally used for billing purposes. The GUID is a 16-byte quantity that uniquely identifies a call throughout the entire network and over all time. Gateway information and timestamp are embedded in the GUID. See the "CallEntry ID and GUID Call Legs" section on page 4 for an example of the GUID and CallEntry ID call legs.

By default, the debug header displays a more compact 6-byte form of the GUID that is generally unique enough for debugging purposes. If there is a need to correlate GUID information to third-party devices or to conduct debugging sessions lasting more than a month, the user can display the full 16-byte header with the voice call debug command using the full-guid keyword.

When the GUID information is unavailable to the module producing the debug message, the header displays the GUID field as blank or filled with "x" (/xxxxxxx/). For non-IVR debugs, if the GUID field is unavailable, the header displays as //CallentryID/xxxxxxxx/. For IVR debugs, the header displays as //CallentryID//. IVR rarely has GUID information, but reserves the space in order to have field-by-field consistency.

•Module-dependent-list—These parameters are dependent on which module is used. The dependent parameters for the various modules are shown in Table 1.

Table 1 Module Dependent List Parameters

Module

Dependent Parameters

CCAPI

None

VTSP

Port name, channel number, DSP slot, and DSP channel number

SSAPP

Dial-peer number and the number of the connection through the dial peer (there can be multiple sessions associated with a single dial peer)

IVR

See the "IVR Module Dependent List" section

•Function-name—Identifies call progress though the internal modules of the Cisco IOS code. This is free-form debugging used by developers.

IVR Module Dependent List

The module dependent list for IVR information has the following form:
<Module Name> : [LP:] [<OBJ><OBJ-ID>: [<OBJ><OBJ-ID>:[...]]]

Module names are shown in Table 1. The LP parameter is the link point, which is the point where two or more objects can be associated together. The OBJ parameter is the object name, shown in Table 2. The OBJ-ID is a numeric identifier for the object and the ranges are also shown in Table 2.

Table 2 IVR Module Names

Module Name

Module

AAPL

Application infrastruction

DCM

Digit collect

DPM

Dynamic prompt

MCM

Media content

MSM

Media stream

MSW

Media service wrapper

PCM

Place call (call setup)

RTSP

RTSP client

TCL2

TCL IVR 2

Table 3 Object Names and Identifier Values

Object Name

Description

Identifier Range

CN

Connection

-2147483647 to -2147483647
with 0 and -1 being invalid (either) or unavailable (latter)

DP

Dynamic prompt

1 to -4294967295
or 0 (invalid or unavailable)

GS

Generic stream

1 to -4294967295
or 0 (invalid or unavailable)

HN

Handler

0 to -4294967295

LG

Call leg

1 to -2147483647
or -1 (invalid or unavailable)

MC

Media content

1 to -4294967295
or 0 (invalid or unavailable)

MR

Media content reader

1 to -4294967295
or 0 (invalid or unavailable)

MS

Media stream

1 to -4294967295
or 0 (invalid or unavailable)

RS

RTSP session

1 to -4294967295
or 0 (invalid or unavailable)

CallEntry ID and GUID Call Legs

The parts of the call that are identified by CallEntry IDs and GUIDs are shown in Figure 1. The example shown in the figure is a conference call in which two of the participants are on the same IP network and the third participant is called over the POTS network. Most of the IP-based voice signaling protocols (like H.225) carry the GUID information between gateways. Traditional voice connections such as POTS and ISDN have no means to carry a GUID. A voice gateway creates a new GUID when one is not available from the call originator. In the illustrated example, call legs 1, 2, and 5 use GUID A, while leg 4 uses GUID B. Leg 3 is across the POTS network, so no GUID is associated with it. Note that there is a CallEntry ID for each incoming or outgoing call on each gateway.

Figure 1 GUIDs and CallEntry IDs in a Conference Call

How to Manage the Voice Call Debug Output

The debug output for calls on Cisco voice gateways is managed by using the voice call debug command in global configuration mode. When this command is enabled, the standardized header appears when voice debugs are used.

SUMMARY STEPS

1. enable

2. configure {terminal | memory | network}

3. voice call debug {full-guid | short-header }

4. exit

5. debug {rstp | voip ccapi | voip ivr | voip rawmsg | vtsp}

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

voice call debug {full-guid | short-header}
Example:

Router(config)# voice call debug full-guid

Specifies the full GUID or short header for debugging a voice call in a multiple-call environment.

•full-guid—Displays the GUID in a 16-byte header. When the no version of this command is input with the full-guid keyword, the short 6-byte version displays. This is the default.

•short-header—Displays the CallEntry ID in the header without displaying the GUID or module-specific parameters.

Step 4

exit
Example:

Router(config)# exit

Exits to privileged EXEC mode.

Step 5

debug rtsp {all | api | client | error | pmh | session | socket}
debug voip ccapi {error | inout}
debug voip ivr {all | applib | callsetup | digitcollect | dynamic | error | script | settlement | states | tclcommands}
debug voip rawmsg
debug vtsp {all | dsp | error | event | port | rtp | send-nse | session | stats | vofr subframe | tone}
Example:

Router# debug voip ccapi inout

Enter the appropriate debug command for your troubleshooting needs. The debug commands that support the standardized header and detailed examples of the individual debug commands are in the "Command Reference" section.

The debug commands that support the standardized header include the following:

•debug rtsp all

•debug rtsp api

•debug rtsp client

•debug rtsp error

•debug rtsp pmh

•debug rtsp socket

•debug voip ccapi error

•debug voip ccapi inout

•debug voip ivr all

•debug voip ivr applib

•debug voip ivr callsetup

•debug voip ivr digitcollect

•debug voip ivr dynamic

•debug voip ivr error

•debug voip ivr script

•debug voip ivr settlement

•debug voip ivr states

•debug voip ivr tclcommands

•debug voip rawmsg

•debug vtsp all

•debug vtsp dsp

•debug vtsp error

•debug vtsp event

•debug vtsp port

•debug vtsp rtp

•debug vtsp send-nse

•debug vtsp session

•debug vtsp stats

•debug vtsp vofr subframe

•debug vtsp tone

For detailed examples of these debug commands, see the "Command Reference" section.

Sample Output Examples for the Enhanced Debug Commands

This section provides sample output examples for the enhanced debug commands, including:

•Full GUID Header Example

•Short Header Example

•Setup and Teardown Example

Full GUID Header Example

The following is sample output for the voice call debug command when the full-guid keyword is specified:
Router(config)# voice call debug full-guid
!
00:05:12: //1/0E2C8A90-BC00-11D5-8002-DACCFDCEF87D/VTSP:(0:D):0:0:4385/vtsp_insert_cdb: 
00:05:12: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: 
In the first line, the following parameters are described:

•1 denotes the CallEntry ID.

•0E2C8A90-BC00-11D5-8002-DACCFDCEF87D is the GUID.

•VTSP:(0:D):0:0:4385 is the module and its dependent parameters. In this case, the module is VTSP, the port number is 0:D, the channel number is 0, the DSP slot is 0, and the DSP channel number is 4385.

•vtsp_insert_cdb: is the function name.

In the second line, the following parameters are described:

•-1 indicates that the CallEntry ID for the CCAPI module is unavailable.

•xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx indicates that the GUID is unavailable.

•CCAPI is the module.

•cc_incr_if_call_volume: is the function name.

Short Header Example

The following is sample output for the voice call debug command when the header-only keyword is specified:
Router(config)# voice call debug short-header
!
00:10:12: //-1/cc_incr_if_call_volume:
00:10:12: //9/vtsp_open_voice_and_set_params:
In the first line, the CallEntry ID is not available, and in the following line the CallEntry ID is 9. The remainder of the line displays the function name.

Setup and Teardown Example

In the following example, the debug voip ccapi inout command used with the voice call debug full-guid 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. This output shows how calls are being handled by the voice gateway. Using this debug level, you can see the call setup and teardown operations performed on both the telephony and network call legs.
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]
Note In the following lines, the call control API (CCAPI) receives the call setup. The called number is 34999, and the calling number is 55555. The calling number matches dial peer 10002.
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/cc_api_display_ie_subfields:
*Mar  1 15:35:53.592: cc_api_call_setup_ind:
*Mar  1 15:35:53.592:  cisco-username=
*Mar  1 15:35:53.596: ----- ccCallInfo IE subfields -----
*Mar  1 15:35:53.596:  cisco-ani=55555
*Mar  1 15:35:53.596:  cisco-anitype=0
*Mar  1 15:35:53.596:  cisco-aniplan=0
*Mar  1 15:35:53.596:  cisco-anipi=0 
*Mar  1 15:35:53.596:  cisco-anisi=0
*Mar  1 15:35:53.596:  dest=34999
*Mar  1 15:35:53.596:  cisco-desttype=0
*Mar  1 15:35:53.596:  cisco-destplan=0 
*Mar  1 15:35:53.596:  cisco-rdn=
*Mar  1 15:35:53.596:  cisco-rdntype=-1
*Mar  1 15:35:53.596:  cisco-rdnplan=-1 
*Mar  1 15:35:53.596:  cisco-rdnpi=-1
*Mar  1 15:35:53.596:  cisco-rdnsi=-1
*Mar  1 15:35:53.596:  cisco-redirectreason=-1
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: (vdbPtr=0x637EC1E0, 
callInfo={called=34999,called_oct3=0x80,calling=55555,calling_oct3=0x80,calling_oct3a=0x0,
calling_xlated=false,subscriber_type_str=RegularLine,fdest=1,peer_tag=10002, 
prog_ind=0,callingIE_present 1, src_route_label=, tgt_route_label= 
clid_transparent=0},callID=0x637B4278)
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: type 13 , prot 0
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar  1 15:35:53.596: ccCheckClipClir: calling number is: "55555", calling oct3a is: 0x0
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar  1 15:35:53.596: Calling Party number is User Provided
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar  1 15:35:53.596: Leaving ccCheckClipClir
  calling number is: "55555"
  calling oct3 is:  0x80
  calling oct3a is: 0x0
Note In the next line, 44 is the CallEntry ID.
*Mar  1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: Increment call volume: 
0 
*Mar  1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: current call volume: 1
*Mar  1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: entry's incoming TRUE.
*Mar  1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: is_incomingis 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)
Note 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:
Note The next line shows CallEntry ID in hexadecimal form, 0x2C (44 in decimal). The CallEntry ID and GUID numbers have been identified. The incoming dial-peer is 10002.
*Mar  1 15:35:53.608: //44/xxxxxxxxxxxx/CCAPI/ccCallSetContext: (callID=0x2C, 
context=0x634A430C) 
*Mar  1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: cid(44), 
st(SSA_CS_MAPPING),oldst(0), ev(24)ev->e.evCallSetupInd.nCallInfo.finalDestFlag = 1 
*Mar  1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: src route label=, 
tgt route label= tg_label_flag 0x0
*Mar  1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: finalDest 
cllng(55555), clled(34999) tgt_route_label()tg_label_flag 0x0
*Mar  1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: cid(44), 
st(SSA_CS_CALL_SETTING),oldst(0), ev(24)dpMatchPeersMoreArg result= 0
Note For CallEntry ID 44, two dial-peer tags (10001 and 20002) were matched with called number 34999.
*Mar  1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaDebugPeers: 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  20002
Note The next line shows that 5 digits were matched for this dial-peer and no prefix was added. The encapType (2) entry indicates a VoIP call.
*Mar  1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaSetupPeer: cid(44), 
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=1
Note The next line shows the voice gateway sending out a call-proceeding message to the incoming call leg with a progress indicator of 0x0.
*Mar  1 15:35:53.612: //44/xxxxxxxxxxxx/CCAPI/ccCallProceeding: (callID=0x2C, 
prog_ind=0x0) 
Note 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 oct3a is: 0x0
*Mar  1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar  1 15:35:53.616: Calling Party number is User Provided
*Mar  1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar  1 15:35:53.616: Leaving ccCheckClipClir
  calling number is: "55555"
  calling oct3 is:  0x80
  calling oct3a is: 0x0
*Mar  1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: after ccCheckClipClir - 
calling oct3a is:0x0
Note The 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:
Note In the next line, outgoing CallEntry ID 45 is bound to the same GUID 45F2AAE28044.
*Mar  1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: not incoming entry 
*Mar  1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: entry's incoming 
FALSE.
*Mar  1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: is_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)
Note The next line shows that the voice gateway informs the incoming call leg that digits were forwarded.
*Mar  1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/cc_api_call_report_digits_done: 
(vdbPtr=0x637EC1E0, callID=0x2C, disp=0)
*Mar  1 15:35:53.624: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: 
ev(54=CC_EV_CALL_REPORT_DIGITS_DONE), cid(44), disp(0)
*Mar  1 15:35:53.624: //44/45F2AAE28044/SS
Router#APP:10002:-1/ssaTraceSct: 
cid(44)st(SSA_CS_CALL_SETTING)ev(SSA_EV_CALL_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=0x2D
Note The next two lines show the IP address of the terminating gateway and that the terminating gateway is reached through Ethernet port 0/0.
*Mar  1 15:35:53.628: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: remote IP is 
171.69.85.111 
*Mar  1 15:35:53.632: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: hwidb is Ethernet0/0 
*Mar  1 15:35:53.632: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: create entry in 
list: 1
*Mar  1 15:35:53.636: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetInstanceCount: For 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]
Note 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#
Note 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#
Note The phone is answered at the called number.
Router#!call answered 
Router#
Note 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 TRUE
Note The next line shows that the call accounting starts. The leg_type=False message means this is for an outgoing call. The line that follows shows that AAA accounting is not configured.
*Mar  1 15:36:05.016: //45/45F2AAE28044/CCAPI/cc_api_call_connected: calling accounting 
start for callID=45 leg_type=0 
*Mar  1 15:36:05.020: //45/xxxxxxxxxxxx/CCAPI/ccCallSetAAA_Accounting: callID=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)
Note 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)
Note 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=0x2
           codec_bytes=0, signal_type=3})
*Mar  1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (Playout: mode 0, initial 
60,min 40, max 300) 
*Mar  1 15:36:05.024: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: 
ev(29=CC_EV_CONF_CREATE_DONE), cid(44), disp(0)
*Mar  1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: 
cid(44)st(SSA_CS_CONFERENCING)ev(SSA_EV_CONF_CREATE_DONE)
oldst(SSA_CS_CALL_SETTING)cfid(21)csize(2)in(1)fDest(1)
*Mar  1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: 
-cid2(45)st2(SSA_CS_CONFERENCING)oldst2(SSA_CS_ALERT_RCVD)
*Mar  1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaConfCreateDone:
*Mar  1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/ccCallConnect: (callID=0x2C), prog_ind = 0
*Mar  1 15:36:05.024: //44/45F2AAE28044/CCAPI/ccCallConnect: setting callEntry->connected 
to TRUE
*Mar  1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaDebugPeers: ssaFlushPeerTagQueue 
cid(44) peer list: tag(20002) called number (34999)
*Mar  1 15:36:05.028: //-1/xxxxxxxxxxxx/CCAPI/cc_process_notify_bridge_done: 
(event=0x63067FC0)
Note 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=0x0
           codec_bytes=20, signal_type=2})
*Mar  1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (Playout: mode 0, initial 
60,min 40, max 300) 
Note 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=0x0
           codec_bytes=20, signal_type=2, seq_num_start=2944})
*Mar  1 15:36:05.028: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ack: (dstVdbPtr=0x62EC
61A4, dstCallId=0x2D, srcCallId=0x2C,
     caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0
           codec_bytes=20, signal_type=2, seq_num_start=2944})
*Mar  1 15:36:05.032: //44/xxxxxxxxxxxx/CCAPI/cc_api_voice_mode_event: callID=0x2C
*Mar  1 15:36:05.032: //44/45F2AAE28044/CCAPI/cc_api_voice_mode_event: Call Pointer 
=634A430C
*Mar  1 15:36:05.032: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: 
ev(52=CC_EV_VOICE_MODE_DONE), cid(44), disp(0)
*Mar  1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct:
Router#
Router#cid(44)st(SSA_CS_ACTIVE)ev(SSA_EV_VOICE_MODE_DONE)oldst(SSA_CS_CONFERENCING)cfid(21
)csize(2)in(1)fDest(1)
*Mar  1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: 
-cid2(45)st2(SSA_CS_ACTIVE)oldst2(SSA_CS_ALERT_RCVD)
*Mar  1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaIgnore: cid(44), 
st(SSA_CS_ACTIVE),oldst(5), ev(52)
Router#
Router#! digit punched
Router#
Note The phone at the terminating gateway enters digit 1.
*Mar  1 15:36:11.204: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin: (dstVdbPt
r=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,
    digit=1, digit_begin_flags=0x0, rtp_timestamp=0x0
    rtp_expiration=0x0, dest_mask=0x2)
*Mar  1 15:36:11.504: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: 
(dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,
    digit=1,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), 
digit_tone_mode=0
Note The 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=0x0
    rtp_expiration=0x0, dest_mask=0x2)
*Mar  1 15:36:11.904: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: (dstVdbPtr=
0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,
    digit=2,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), 
digit_tone_mode=0
Router#
*Mar  1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/cc_handle_periodic_timer: Calling the 
callback, ccTimerctx - 0x628B6330
*Mar  1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/ccTimerStart: ccTimerctx - 0x628B6330
Router#
Router#!call hung up  The user at the terminating gateway hangs up the call.
Router#
Note 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)
Note 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)
Note 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)
Note The voice gateway stops call accounting for the outgoing call, indicated by the leg_type=False message. The cause code is verified for the terminating leg.
*Mar  1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: calling accounting start 
for callID=45 leg_type=0
*Mar  1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: existing_cause = 0x10, 
new_cause = 0x10 
*Mar  1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: using the existing_cause 
0x10
*Mar  1 15:36:22.928: //45/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info: (callID=0x2D)
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_api_icpif: expect factor = 0
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/g113_calculate_impairment: (delay=79,
      loss=0), Io=0 Iq=0 Idte=0 Idd=0 Ie=10 Itot=10
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: the remote IP is 
171.69.85.111
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: hwidb is Ethernet0/0
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: reduce callnum of 
entry: 0, voip: 0, mmoip: 0
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: remove anentry
*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 incoming entry
*Mar  1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: entry's incoming 
FALSE.
*Mar  1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: is_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)fDe
st(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:
Additional References

For additional information related to enhanced debugging for Cisco voice gateways, refer to the following references:

Related Documents

Related Topic

Document Title

Debug commands: complete command syntax, defaults, usage guidelines, and examples

Cisco IOS Debug Command Reference, Release 12.2 T

Cisco IOS voice configuration

Cisco IOS Voice, Video, and Fax Configuration Guide, Release 12.2

Cisco IOS voice command reference

Cisco IOS Voice, Video, and Fax Command Reference, Release 12.2 T

Platform-specific information

Use the appropriate documenation for your platform:

•Cisco 2600 Series product documentation

•Cisco 3600 Series product documentation

•Cisco AS5300 product documentation

•Cisco AS5350 product documentation

•Cisco AS5400 product documentation

•Cisco AS5800 product documentation

•Cisco AS5850 product documentation

•Cisco MC3810 product documentation

MIBs

MIBs¹

MIBs Link

No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.

To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

¹Not all supported MIBs are listed.

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://tools.cisco.com/ITDIT/MIBS/servlet/index

If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:

http://www.cisco.com/register

Technical Assistance

Description

Link

Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, tools, and lots more. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/public/support/tac/home.shtml

Command Reference

This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2T command reference publications.

Modified Commands

•debug rtsp all

•debug rtsp api

•debug rtsp client

•debug rtsp error

•debug rtsp pmh

•debug rtsp session

•debug rtsp socket

•debug voip ccapi error

•debug voip ccapi inout

•debug voip ivr all

•debug voip ivr applib

•debug voip ivr callsetup

•debug voip ivr digitcollect

•debug voip ivr dynamic

•debug voip ivr error

•debug voip ivr script

•debug voip ivr settlement

•debug voip ivr states

•debug voip ivr tclcommands

•debug voip rawmsg

•debug vtsp all

•debug vtsp dsp

•debug vtsp error

•debug vtsp event

•debug vtsp port

•debug vtsp rtp

•debug vtsp send-nse

•debug vtsp session

•debug vtsp stats

•debug vtsp tone

•debug vtsp vofr subframe

•voice call debug

debug rtsp all

To display all related information about the Real Time Streaming Protocol (RTSP) data, use the debug rtsp all command in privileged EXEC mode. To disable the output, use the no form of this command.

debug rtsp all
no debug rtsp all
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug rtsp all command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following output is an example of what is displayed when the debug rtsp all command is used. The show debug command shows which RTSP modules are traced:
Router# debug rtsp all
All RTSP client debugging is on
Router#show debug
RTSP:
  RTSP client Protocol Error debugging is on
  RTSP client Protocol Message Handler debugging is on
  RTSP client API debugging is on
  RTSP client socket debugging is on
  RTSP client session debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_get_new_scb:
*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_initialize_scb:
*Mar 11 03:14:23.471: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5FE6C
*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_api_create_session: evh=0x6155F0D4 
context=0x6345042C
*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_get_new_scb:
*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_initialize_scb:
*Mar 11 03:14:23.471: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5D874
*Mar 11 03:14:23.471: //-1//RTSP:/rtsp_api_create_session: evh=0x6155F204 
context=0x6345046C
*Mar 11 03:14:23.471: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A59FB8
*Mar 11 03:14:23.471: //-1//RTSP:RS45:/rtsp_api_handle_req_set_params: msg=0x63A59FB8
*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A59FB8
*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A5A304
*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_handle_req_set_params: msg=0x63A5A304
*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A5A304
*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A5A650
*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_handle_req_set_params: msg=0x63A5A650
*Mar 11 03:14:23.475: //166//RTSP:LP:RS45:/rtsp_api_handle_req_set_params:
*Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A5A650
*Mar 11 03:14:23.475: //-1//RTSP:RS46:/rtsp_api_request: msg=0x63A5A99C
*Mar 11 03:14:23.475: //-1//RTSP:RS46:/rtsp_api_handle_req_set_params: msg=0x63A5A99C
*Mar 11 03:14:23.475: //166//RTSP:LP:RS46:/rtsp_api_handle_req_set_params:
*Mar 11 03:14:23.475: //-1//RTSP:RS46:/rtsp_api_free_msg_buffer: msg=0x63A5A99C
Router#
Router#!call answered
Router#
Router#!digits dialed
Router#
Router#!call terminated
Router#
*Mar 11 03:14:51.603: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A5ACE8
*Mar 11 03:14:51.603: //-1//RTSP:RS46:/rtsp_api_request: msg=0x63A5B034
*Mar 11 03:14:51.607: //-1//RTSP:RS45:/rtsp_control_process_msg:
*Mar 11 03:14:51.607: //166//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 
0
*Mar 11 03:14:51.607: //166//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY
*Mar 11 03:14:51.607: //166//RTSP:/rtsp_session_cleanup:
*Mar 11 03:14:51.607: //-1//RTSP:/rtsplib_free_svr_session:
*Mar 11 03:14:51.607: //-1//RTSP:/rtsplib_stop_timer: timer(0x638D5DDC) stops
*Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: scb=0x63A5FE6C, 
callID=0xA6
*Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: No streams in session 
control block
*Mar 11 03:14:51.611: //166//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5FE6C
*Mar 11 03:14:51.611: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A5ACE8
*Mar 11 03:14:51.611: //-1//RTSP:RS46:/rtsp_control_process_msg:
*Mar 11 03:14:51.611: //166//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 
0
*Mar 11 03:14:51.611: //166//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY
*Mar 11 03:14:51.611: //166//RTSP:/rtsp_session_cleanup:
*Mar 11 03:14:51.611: //-1//RTSP:/rtsplib_free_svr_session:
*Mar 11 03:14:51.611: //-1//RTSP:/rtsplib_stop_timer: timer(0x63A60110) stops
*Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: scb=0x63A5D874, 
callID=0xA6
*Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: No streams in session 
control block
*Mar 11 03:14:51.611: //166//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5D874
*Mar 11 03:14:51.611: //-1//RTSP:RS46:/rtsp_api_free_msg_buffer: msg=0x63A5B034
Related Commands

Command

Description

debug rtsp api

Displays debug output for the RTSP client API.

debug rtsp client

Displays debug output for the RTSP client data.

debug rtsp error

Displays error message for RTSP data.

debug rtsp pmh

Displays debug messages for the PMH.

debug rtsp socket

Displays debug output for the RTSP client socket data.

voice call debug

Allows configuration of the voice call debug output.

debug rtsp api

To display information about the Real Time Streaming Protocol (RTSP) API messages passed down to the RTSP client, use the debug rtsp api command in privileged EXEC mode. To disable the output, use the no form of this command.

debug rtsp api
no debug rtsp api
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug rtsp api command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following output is an example of what is displayed when the debug rtsp api command is used:
Router# debug rtsp api
RTSP client API debugging is on
Router# !call initiated
*Mar 11 03:04:41.699: //-1//RTSP:/rtsp_api_create_session: evh=0x6155F0D4 
context=0x6345088C
*Mar 11 03:04:41.699: //-1//RTSP:/rtsp_api_create_session: evh=0x6155F204 
context=0x634508CC
*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_request: msg=0x63A59FB8
*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_handle_req_set_params: msg=0x63A59FB8
*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A59FB8
*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_request: msg=0x63A5A304
*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_handle_req_set_params: msg=0x63A5A304
*Mar 11 03:04:41.699: //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A5A304
*Mar 11 03:04:41.703: //-1//RTSP:RS35:/rtsp_api_request: msg=0x63A5A650
*Mar 11 03:04:41.703: //-1//RTSP:RS35:/rtsp_api_handle_req_set_params: msg=0x63A5A650
*Mar 11 03:04:41.703: //146//RTSP:LP:RS35:/rtsp_api_handle_req_set_params:
*Mar 11 03:04:41.703: //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A5A650
*Mar 11 03:04:41.703: //-1//RTSP:RS36:/rtsp_api_request: msg=0x63A5A99C
*Mar 11 03:04:41.703: //-1//RTSP:RS36:/rtsp_api_handle_req_set_params: msg=0x63A5A99C
*Mar 11 03:04:41.703: //146//RTSP:LP:RS36:/rtsp_api_handle_req_set_params:
*Mar 11 03:04:41.703: //-1//RTSP:RS36:/rtsp_api_free_msg_buffer: msg=0x63A5A99C
Router!call answered
Router#!digits dialed
Router#!call terminated
*Mar 11 03:05:15.367: //-1//RTSP:RS35:/rtsp_api_request: msg=0x63A5ACE8
*Mar 11 03:05:15.367: //-1//RTSP:RS36:/rtsp_api_request: msg=0x63A5B034
*Mar 11 03:05:15.367: //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A5ACE8
*Mar 11 03:05:15.367: //-1//RTSP:RS36:/rtsp_api_free_msg_buffer: msg=0x63A5B034
Related Commands

Command

Description

debug rtsp client

Displays debug output for the RTSP client data.

debug rtsp error

Displays error message for RTSP data.

debug rtsp pmh

Displays debug messages for the PMH.

debug rtsp socket

Displays debug output for the RTSP client socket data.

voice call debug

Allows configuration of the voice call debug output.

debug rtsp client

To display client information and stream information for the stream that is currently active for the Real Time Streaming Protocol (RTSP) client, use the debug rtsp client command in privileged EXEC mode. To disable the output, use the no form of this command.

debug rtsp client
no debug rtsp client
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug rtsp client command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Related Commands

Command

Description

debug rtsp api

Displays debug output for the RTSP client API.

debug rtsp error

Displays error message for RTSP data.

debug rtsp pmh

Displays debug messages for the PMH.

debug rtsp socket

Displays debug output for the RTSP client socket data.

voice call debug

Allows configuration of the voice call debug output.

debug rtsp error

To display error information about the Real-Time Streaming Protocol (RTSP) client, use the debug rtsp error command in privileged EXEC mode. To disable the output, use the no form of this command.

debug rtsp error
no debug rtsp error
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Related Commands

Command

Description

debug rtsp api

Displays debug output for the RTSP client API.

debug rtsp client

Displays debug output for the RTSP client data.

debug rtsp pmh

Displays debug messages for the PMH.

debug rtsp socket

Displays debug output for the RTSP client socket data.

voice call debug

Allows configuration of the voice call debug output.

debug rtsp pmh

To display debug information about the Protocol Message Handler (PMH), use the debug rtsp pmh command in privileged EXEC mode. To disable the output, use the no form of this command.

debug rtsp pmh
no debug rtsp pmh
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug rtsp pmh command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Related Commands

Command

Description

debug rtsp api

Displays debug output for the RTSP client API.

debug rtsp client

Displays debug output for the RTSP client data.

debug rtsp error

Displays error message for RTSP data.

debug rtsp socket

Displays debug output for the RTSP client socket data.

voice call debug

Allows configuration of the voice call debug output.

debug rtsp session

To display cumulative information about the session, packet statistics, and general call information such as call ID, session ID, individual RTSP stream URLs, packet statistics, and play duration about the current Real-Time Streaming Protocol (RTSP) session, use the debug rtsp session command in privileged EXEC mode. To disable the output, use the no form of this command.

debug rtsp session
no debug rtsp session
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug rtsp session command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following example shows the display of the debug messages of the RTSP session:
Router# debug rtsp session
RTSP client session debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 03:09:58.123: //-1//RTSP:/rtsp_get_new_scb:
*Mar 11 03:09:58.123: //-1//RTSP:/rtsp_initialize_scb:
*Mar 11 03:09:58.123: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5FE6C
*Mar 11 03:09:58.123: //-1//RTSP:/rtsp_get_new_scb:
*Mar 11 03:09:58.123: //-1//RTSP:/rtsp_initialize_scb:
*Mar 11 03:09:58.123: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5D874
Router#
Router#!call answered
Router#
Router#!digits dialed
Router#
Router#!call terminated
Router#
*Mar 11 03:10:38.139: //-1//RTSP:RS41:/rtsp_control_process_msg:
*Mar 11 03:10:38.139: //158//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 
0
*Mar 11 03:10:38.139: //158//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY
*Mar 11 03:10:38.139: //158//RTSP:/rtsp_session_cleanup:
*Mar 11 03:10:38.139: //-1//RTSP:/rtsplib_free_svr_session:
*Mar 11 03:10:38.139: //-1//RTSP:/rtsplib_stop_timer: timer(0x638D5DDC) stops
*Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: scb=0x63A5FE6C, 
callID=0x9E
*Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: No streams in session 
control block
*Mar 11 03:10:38.143: //158//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5FE6C
*Mar 11 03:10:38.143: //-1//RTSP:RS42:/rtsp_control_process_msg:
*Mar 11 03:10:38.143: //158//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 
0
*Mar 11 03:10:38.143: //158//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY
*Mar 11 03:10:38.143: //158//RTSP:/rtsp_session_cleanup:
*Mar 11 03:10:38.143: //-1//RTSP:/rtsplib_free_svr_session:
*Mar 11 03:10:38.143: //-1//RTSP:/rtsplib_stop_timer: timer(0x63A60110) stops
*Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: scb=0x63A5D874, 
callID=0x9E
*Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: No streams in session 
control block
*Mar 11 03:10:38.143: //158//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5D874
Related Commands

Command

Description

debug rtsp api

Displays debug output for the RTSP client API.

debug rtsp error

Displays error message for RTSP data.

debug rtsp pmh

Displays debug messages for the PMH.

debug rtsp socket

Displays debug output for the RTSP client socket data.

voice call debug

Allows configuration of the voice call debug output.

debug rtsp socket

To display debug messages about the packets received or sent on the TCP or User Datagram Protocol (UDP) sockets, use the debug rtsp socket command in privileged EXEC mode. To disable the output, use the no form of this command.

debug rtsp socket
no debug rtsp socket
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Each RTSP session has a TCP port for control and a UDP (RTP) port for delivery of data. The control connection (TCP socket) is used to exchange a set of messages (request from the RTSP client and the response from the server) for displaying a prompt. The debug rtsp socket command enables the user to debug the message exchanges being done on the TCP control connection.

Note Cisco recommends that you log output from the debug rtsp socket command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Related Commands

Command

Description

debug rtsp api

Displays debug output for the RTSP client API.

debug rtsp client

Displays debug output for the RTSP client data.

debug rtsp error

Displays error message for RTSP data.

debug rtsp pmh

Displays debug messages for the PMH.

voice call debug

Allows configuration of the voice call debug output.

debug voip ccapi error

To trace error logs in the call control API, use the debug voip ccapi error command in privileged EXEC mode. To disable the output, use the no form of this command.

debug voip ccapi error
no debug voip ccapi error
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T

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

Usage Guidelines

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

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

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

Related Commands

Command

Description

debug voip ccapi inout

Traces the execution path through the CCAPI.

voice call debug

Allows configuration of the voice call debug output.

debug voip ccapi inout

To trace the execution path through the call control API, use the debug voip ccapi inout command in privileged EXEC mode.To disable the output, use the no form of this command.

debug voip ccapi inout
no debug voip ccapi inout
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T

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

Usage Guidelines

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

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

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

Examples

The following example shows the call setup indicated and accepted by the voice gateway:
Router# debug voip ccapi inout
*Mar  1 15:35:53.588: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructTDUsrContainer: usrCo
ntainer[0x638C1BF0], magic[FACE0FFF]
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilAddDataToUsrContainer: con
tainer=0x638C1BF0, tagID=6, dataSize=16, instID=-1,modifier=1
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject: tdO
bject[0x638BC1AC], nxtElem[0x0], magic[0xFACE0FFF] tagID[6], dataLen[16], modif[
1]
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToContainer: Addin
g tdObject[0x638BC1AC] instID[-1] into container[0x638C1BF0]
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilAddDataToUsrContainer: con
tainer=0x638C1BF0, tagID=5, dataSize=276, instID=-1,modifier=1
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject: tdO
bject[0x63401148], nxtElem[0x0], magic[0xFACE0FFF] tagID[5], dataLen[276], modif
[1]
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToContainer: Addin
g tdObject[0x63401148] instID[-1] into container[0x638C1BF0]
Note In the following lines, the call control API (CCAPI) receives the call setup. The called number is 34999, and the calling number is 55555. The calling number matches dial peer 10002.
*Mar  1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/cc_api_display_ie_subfields:
*Mar  1 15:35:53.592: cc_api_call_setup_ind:
*Mar  1 15:35:53.592:  cisco-username=
*Mar  1 15:35:53.596: ----- ccCallInfo IE subfields -----
*Mar  1 15:35:53.596:  cisco-ani=55555
*Mar  1 15:35:53.596:  cisco-anitype=0
*Mar  1 15:35:53.596:  cisco-aniplan=0
*Mar  1 15:35:53.596:  cisco-anipi=0 
*Mar  1 15:35:53.596:  cisco-anisi=0
*Mar  1 15:35:53.596:  dest=34999
*Mar  1 15:35:53.596:  cisco-desttype=0
*Mar  1 15:35:53.596:  cisco-destplan=0 
*Mar  1 15:35:53.596:  cisco-rdn=
*Mar  1 15:35:53.596:  cisco-rdntype=-1
*Mar  1 15:35:53.596:  cisco-rdnplan=-1 
*Mar  1 15:35:53.596:  cisco-rdnpi=-1
*Mar  1 15:35:53.596:  cisco-rdnsi=-1
*Mar  1 15:35:53.596:  cisco-redirectreason=-1
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: (vdbPtr=0x6
37EC1E0, callInfo={called=34999,called_oct3=0x80,calling=55555,calling_oct3=0x80
,calling_oct3a=0x0,calling_xlated=false,subscriber_type_str=RegularLine,fdest=1,
peer_tag=10002, prog_ind=0,callingIE_present 1, src_route_label=, tgt_route_labe
l= clid_transparent=0},callID=0x637B4278)
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: type 13 , p
rot 0
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar  1 15:35:53.596: ccCheckClipClir: calling number is: "55555", calling oct3a
 is: 0x0
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar  1 15:35:53.596: Calling Party number is User Provided
*Mar  1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar  1 15:35:53.596: Leaving ccCheckClipClir
  calling number is: "55555"
  calling oct3 is:  0x80
  calling oct3a is: 0x0
Note In the next line, 44 is the CallEntry ID.
*Mar  1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: Increment ca
ll volume: 0 
*Mar  1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: current call
 volume: 1
*Mar  1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: entry's inco
ming TRUE.
*Mar  1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: is_incoming
is TRUE
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructHashProfileTab: profi
leTable[0x6380E11C], numBuckets[11], numEntries[0]
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtProfileTableBuildManager: I
nvoking necessary profileTable updaters...
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContain
er: Updating profileTable[0x6380E11C] with objects in container[0x638C1BF0]
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContain
er: obtained key[5] for the tag[6]
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToProfileBucket: p
rofileTable[0x6380E11C], tdObject[0x638BC1AC]
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContain
er: obtained key[0] for the tag[5]
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToProfileBucket: p
rofileTable[0x6380E11C], tdObject[0x63401148]
*Mar  1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtProfileTableBuildManager:
*Mar  1 15:35:53.600: ccTDUtilDumpAllElemInProfileTab: profileTable[0x6380E11C],
 numBuckets[11], numEntries[2]
*Mar  1 15:35:53.600: Bucket { 0 } ------>0x63401148[0x0,t-5,l-276,d-0x63401168,
m-1,u-56153,g-FACE0FFF]
*Mar  1 15:35:53.604:
*Mar  1 15:35:53.604: Bucket { 5 } ------>0x638BC1AC[0x0,t-6,l-16,d-0x638BC1CC,m
-1,u-56153,g-FACE0FFF]
*Mar  1 15:35:53.604:
*Mar  1 15:35:53.604: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructTDUsrContainer: Contai
ner[0x638C1BF0]
*Mar  1 15:35:53.604: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: not the Vo
IP or MMoIP
*Mar  1 15:35:53.608: //-1/xxxxxxxxxxxx/CCAPI/cc_process_call_setup_ind: (event=
0x63073AA0)
Note In the next line, 45F2AAE28044 is the GUID. The tag 10002 entry shows that the incoming dial-peer matched the CallEntry ID.
*Mar  1 15:35:53.608: //44/45F2AAE28044/CCAPI/cc_process_call_setup_ind: >>>>CCA
PI handed cid 44 with tag 10002 to app "DEFAULT" 
*Mar  1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(24=CC_EV_CALL_
SETUP_IND), cid(44), disp(0)
*Mar  1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(SSA_EV_CALL_SE
TUP_IND), cid(44), disp(0)
*Mar  1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/ssaCallSetupInd:
Note The next line shows CallEntry ID in hexadecimal form, 0x2C (44 in decimal). The CallID and GUID numbers have been identified. The incoming dial-peer is 10002.
*Mar  1 15:35:53.608: //44/xxxxxxxxxxxx/CCAPI/ccCallSetContext: (callID=0x2C, 
context=0x634A430C) 
*Mar  1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: cid(44),
 st(SSA_CS_MAPPING),oldst(0), ev(24)ev->e.evCallSetupInd.nCallInfo.finalDestFlag
 = 1 
*Mar  1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: src rout
e label=, tgt route label= tg_label_flag 0x0
*Mar  1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: finalDes
t cllng(55555), clled(34999) tgt_route_label()tg_label_flag 0x0
*Mar  1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: cid(44),
 st(SSA_CS_CALL_SETTING),oldst(0), ev(24)dpMatchPeersMoreArg result= 0
Note For CallEntry ID 44, two dial-peer tags (10001 and 20002) were matched with called number 34999.
*Mar  1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaDebugPeers: ssaSetupPe
er cid(44) peer list: tag(10001) called number (34999) tag(20002) called number
(34999) 
*Mar  1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaSetupPeer: dialpeer ta
gs in rotary= 10001  20002
Note The next line shows that 5 digits were matched for this dial-peer and no prefix was added. The encapType (2) entry indicates a VoIP call.
*Mar  1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaSetupPeer: cid(44), de
stPat(34999), matched(5), prefix(), peer(637B0984), peer->encapType (2)
*Mar  1 15:35:53.612: //-1/xxxxxxxxxxxx/CCAPI/cc_can_gateway: Call legs: In=6, O
ut=1
Note The next line shows the voice gateway sending out a call-proceeding message to the incoming call leg with progress indicator of 0x0.
*Mar  1 15:35:53.612: //44/xxxxxxxxxxxx/CCAPI/ccCallProceeding: (callID=0x2C, pr
og_ind=0x0) 
Note The next line shows the voice gateway sending out the call-setup request to the outgoing call leg. The dial-peer is 10001 with the incoming CallEntry ID being 0x2C.
*Mar  1 15:35:53.612: //44/xxxxxxxxxxxx/CCAPI/ccCallSetupRequest: (Inbound call
= 0x2C, outbound peer =10001, dest=,
        params=0x63085D80 mode=0, *callID=0x63086314, prog_ind = 0callingIE_pres
ent 1) 
*Mar  1 15:35:53.612: //44/45F2AAE28044/CCAPI/ccCallSetupRequest:
*Mar  1 15:35:53.612: ccCallSetupRequest numbering_type 0x80 
*Mar  1 15:35:53.612: //44/45F2AAE28044/CCAPI/ccCallSetupRequest:
*Mar  1 15:35:53.616: ccCallSetupRequest: calling number is:55555
*Mar  1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: calling oct3a
is:0x0
*Mar  1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar  1 15:35:53.616: ccCheckClipClir: calling number is: "55555", calling oct3a
 is: 0x0
*Mar  1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar  1 15:35:53.616: Calling Party number is User Provided
*Mar  1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar  1 15:35:53.616: Leaving ccCheckClipClir
  calling number is: "55555"
  calling oct3 is:  0x80
  calling oct3a is: 0x0
*Mar  1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: after ccCheckC
lipClir - calling oct3a is:0x0
Note The next line shows that all digits are passed.
*Mar  1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: dest pattern 3
4999, called 34999, digit_strip 0 
*Mar  1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest:
*Mar  1 15:35:53.616: callingNumber=55555, calledNumber=34999, redirectNumber= d
isplay_info= calling_oct3a=0
*Mar  1 15:35:53.616: accountNumber=, finalDestFlag=1,
guid=45f2.aae2.1571.11cc.8044.95f5.fabb.6b0f
*Mar  1 15:35:53.616: peer_tag=10001
*Mar  1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/cc_api_display_ie_subfields:
*Mar  1 15:35:53.616: ccCallSetupRequest:
*Mar  1 15:35:53.616:  cisco-username=
*Mar  1 15:35:53.616: ----- ccCallInfo IE subfields -----
*Mar  1 15:35:53.616:  cisco-ani=55555
*Mar  1 15:35:53.616:  cisco-anitype=0
*Mar  1 15:35:53.616:  cisco-aniplan=0
*Mar  1 15:35:53.616:  cisco-anipi=0
*Mar  1 15:35:53.616:  cisco-anisi=0
*Mar  1 15:35:53.620:  dest=34999
*Mar  1 15:35:53.620:  cisco-desttype=0
*Mar  1 15:35:53.620:  cisco-destplan=0
*Mar  1 15:35:53.620:  cisco-rdn=
*Mar  1 15:35:53.620:  cisco-rdntype=-1
*Mar  1 15:35:53.620:  cisco-rdnplan=-1
*Mar  1 15:35:53.620:  cisco-rdnpi=-1
*Mar  1 15:35:53.620:  cisco-rdnsi=-1
*Mar  1 15:35:53.620:  cisco-redirectreason=-1
*Mar  1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: (vdbP
tr=0x62EC61A4, dest=, callParams={called=34999,called_oct3=0x80, calling=55555,c
alling_oct3=0x80, calling_oct3a= 0x0, calling_xlated=false,  subscriber_type_str
=RegularLine, fdest=1, voice_peer_tag=10001},mode=0x0)
*Mar  1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
*Mar  1 15:35:53.620: ccIFCallSetupRequestPrivate: src route label  tgt route la
bel tg_label_flag 0x0
*Mar  1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:  vdbP
tr type = 1
*Mar  1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
*Mar  1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: (vdbP
tr=0x62EC61A4, dest=, callParams={called=34999, called_oct3 0x80,  calling=55555
,calling_oct3 0x80, calling_oct3a 0x0, calling_xlated=false,  fdest=1, voice_pee
r_tag=10001}, mode=0x0, xltrc=-5)
*Mar  1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
Note In the next line, outgoing CallEntry ID 45 is bound to the same GUID 45F2AAE28044.
*Mar  1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: not incoming
 entry 
*Mar  1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: entry's inco
ming FALSE.
*Mar  1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: is_incoming
is FALSE
*Mar  1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag: (callID=0x2C, d
ialpeer_tag=10001)
*Mar  1 15:35:53.624: //45/xxxxxxxxxxxx/CCAPI/ccCallSetContext: (callID=0x2D, co
ntext=0x634A537C) 0x2D (decimal 45 is the second call leg ID).
*Mar  1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/ccCallReportDigits: (callID=0x2C,
enable=0x0)
Note The voice gateway informs the incoming call leg that digits were forwarded.
*Mar  1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/cc_api_call_report_digits_done: (v
dbPtr=0x637EC1E0, callID=0x2C, disp=0)
*Mar  1 15:35:53.624: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(54=CC_EV_CALL_
REPORT_DIGITS_DONE), cid(44), disp(0)
*Mar  1 15:35:53.624: //44/45F2AAE28044/SS
Router#APP:10002:-1/ssaTraceSct: cid(44)st(SSA_CS_CALL_SETTING)ev(SSA_EV_CALL_RE
PORT_DIGITS_DONE)
oldst(SSA_CS_MAPPING)cfid(-1)csize(0)in(1)fDest(1)
*Mar  1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaTraceSct: -cid2(45)st2
(SSA_CS_CALL_SETTING)oldst2(SSA_CS_MAPPING)
*Mar  1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaDebugPeers: ssaReportD
igitsDone cid(44) peer list: tag(20002) called number (34999)
*Mar  1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaReportDigitsDone: call
id=44 Reporting disabled.
*Mar  1 15:35:53.628: //-1/xxxxxxxxxxxx/CCAPI/cc_api_supported_data: data_mode=0
x10082
*Mar  1 15:35:53.628: //45/xxxxxxxxxxxx/CCAPI/cc_api_get_ic_leg_obtained_numbers
: callID=0x2D
Note The next two lines shows the IP address of the terminating gateway and that the terminating gateway is reached through Ethernet port 0/0.
*Mar  1 15:35:53.628: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: remote IP
is 171.69.85.111 
*Mar  1 15:35:53.632: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: hwidb is E
thernet0/0 
*Mar  1 15:35:53.632: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: create ent
ry in list: 1
*Mar  1 15:35:53.636: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetInstanceCount: For tagI
D[1] of callID[45]
*Mar  1 15:35:53.636: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessMan
ager: No profileTable set for callID[45]
*Mar  1 15:35:53.636: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetInstanceCount: For tagI
D[2] of callID[45]
*Mar  1 15:35:53.636: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessMan
ager: No profileTable set for callID[45]
Note The next line shows that the voice gateway received a call proceeding message from the terminating gateway, and then the following line shows that the voice gateway received a call alert from the terminating gateway.
*Mar  1 15:35:53.740: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_proceeding: (vdbPtr=0x
62EC61A4, callID=0x2D,
      prog_ind=0x0) 
*Mar  1 15:35:53.740: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_alert: (vdbPtr=0x62EC6
1A4, callID=0x2D, prog_ind=0x0, sig_ind=0x1) 
*Mar  1 15:35:53.744: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(21=CC_EV_CALL_
PROCEEDING), cid(45), disp(0)
*Mar  1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS
_CALL_SETTING)ev(SSA_EV_CALL_PROCEEDING)
oldst(SSA_CS_MAPPING)cfid(-1)csize(0)in(0)fDest(0)
*Mar  1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA
_CS_CALL_SETTING)oldst2(SSA_CS_CALL_SETTING)
*Mar  1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaCallProc:
*Mar  1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C)
*Mar  1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaIgnore: cid(45), st(SSA_CS
_CALL_SETTING),oldst(1), ev(21)
*Mar  1 15:35:53.744: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(7=CC_EV_CALL_A
LERT), cid(45), disp(0)
*Mar  1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS
_CALL_SETTING)ev(SSA_EV_CALL_ALERT)
oldst(SSA_CS_CALL_SETTING)cfid(-1)csize(0)in(0)fDest(0)
*Mar  1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA
_CS_CALL_SETTING)oldst2(SSA_CS_CALL_SETTING)
*Mar  1 15:35:53.744: //44/45F2AAE28044/SSAPP:10002:-1/ssaAlert:
*Mar  1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C)
Router#
Note The voice gateway forwarded a call alert to the originating gateway.
*Mar  1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccCallAlert: (callID=0x2C, prog_in
d=0x0, sig_ind=0x1) 
Router#
Note The phone is answered at the called number.
Router#!call answered 
Router#
Note The voice gateway receives a connect message from the terminating gateway.
*Mar  1 15:36:05.016: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_connected: (vdbPtr=0x6
2EC61A4, callID=0x2D), prog_ind = 0 
*Mar  1 15:36:05.016: //45/45F2AAE28044/CCAPI/cc_api_call_connected: setting cal
lEntry->connected to TRUE
Note The next line shows that the call accounting starts. The leg_type=False message means this is for an outgoing call. The line that follows shows that AAA accounting is not configured.
*Mar  1 15:36:05.016: //45/45F2AAE28044/CCAPI/cc_api_call_connected: calling accounting 
start for callID=45 leg_type=0 
*Mar  1 15:36:05.020: //45/xxxxxxxxxxxx/CCAPI/ccCallSetAAA_Accounting: callID=0x
2D, accounting=0 
*Mar  1 15:36:05.020: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(8=CC_EV_CALL_C
ONNECTED), cid(45), disp(0)
*Mar  1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS
_ALERT_RCVD)ev(SSA_EV_CALL_CONNECTED)
oldst(SSA_CS_CALL_SETTING)cfid(-1)csize(0)in(0)fDest(0)
*Mar  1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA
_CS_ALERT_RCVD)oldst2(SSA_CS_CALL_SETTING)
*Mar  1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaConnect:
*Mar  1 15:36:05.020: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C)
Note The next lines show a conference being set up between the two call legs 0x2C and 0x2D. Bridge complete messages are sent to both the terminating and originating gateways.
*Mar  1 15:36:05.020: //44/xxxxxxxxxxxx/CCAPI/ccConferenceCreate: (confID=0x6308
6424, callID1=0x2C, callID2=0x2D, tag=0x0) 
*Mar  1 15:36:05.020: //45/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done: (confID=0x15,
srcIF=0x62EC61A4, srcCallID=0x2D, dstCallID=0x2C, disposition=0, tag=0x0)
*Mar  1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done: (confID=0x15,
srcIF=0x637EC1E0, srcCallID=0x2C, dstCallID=0x2D, disposition=0, tag=0x0)
Note Here, the voice gateway sets up negotiating capability with the originating telephony leg.
*Mar  1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (dstVdbPtr=0x62EC
61A4, dstCallId=0x2D, srcCallId=0x2C,
     caps={codec=0x2887F, fax_rate=0xBF, vad=0x3, modem=0x2
           codec_bytes=0, signal_type=3})
*Mar  1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (Playout: mode 0,
 initial 60,min 40, max 300) 
*Mar  1 15:36:05.024: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(29=CC_EV_CONF_
CREATE_DONE), cid(44), disp(0)
*Mar  1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: cid(44)st(SS
A_CS_CONFERENCING)ev(SSA_EV_CONF_CREATE_DONE)
oldst(SSA_CS_CALL_SETTING)cfid(21)csize(2)in(1)fDest(1)
*Mar  1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2
(SSA_CS_CONFERENCING)oldst2(SSA_CS_ALERT_RCVD)
*Mar  1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaConfCreateDone:
*Mar  1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/ccCallConnect: (callID=0x2C), prog
_ind = 0
*Mar  1 15:36:05.024: //44/45F2AAE28044/CCAPI/ccCallConnect: setting callEntry->
connected to TRUE
*Mar  1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaDebugPeers: ssaFlushPe
erTagQueue cid(44) peer list: tag(20002) called number (34999)
*Mar  1 15:36:05.028: //-1/xxxxxxxxxxxx/CCAPI/cc_process_notify_bridge_done: (ev
ent=0x63067FC0)
Note The voice gateway sets up negotiating capability with the terminating VoIP leg.
*Mar  1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (dstVdbPtr=0x637E
C1E0, dstCallId=0x2C, srcCallId=0x2D,
     caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0
           codec_bytes=20, signal_type=2})
*Mar  1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (Playout: mode 0,
 initial 60,min 40, max 300) 
Note The capabilities are acknowledged for both call legs.
*Mar  1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ack: (dstVdbPtr=0x637E
C1E0, dstCallId=0x2C, srcCallId=0x2D,
     caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0
           codec_bytes=20, signal_type=2, seq_num_start=2944})
*Mar  1 15:36:05.028: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ack: (dstVdbPtr=0x62EC
61A4, dstCallId=0x2D, srcCallId=0x2C,
     caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0
           codec_bytes=20, signal_type=2, seq_num_start=2944})
*Mar  1 15:36:05.032: //44/xxxxxxxxxxxx/CCAPI/cc_api_voice_mode_event: callID=0x
2C
*Mar  1 15:36:05.032: //44/45F2AAE28044/CCAPI/cc_api_voice_mode_event: Call Poin
ter =634A430C
*Mar  1 15:36:05.032: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(52=CC_EV_VOICE
_MODE_DONE), cid(44), disp(0)
*Mar  1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct:
Router#
Router#cid(44)st(SSA_CS_ACTIVE)ev(SSA_EV_VOICE_MODE_DONE)
oldst(SSA_CS_CONFERENCING)cfid(21)csize(2)in(1)fDest(1)
*Mar  1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2
(SSA_CS_ACTIVE)oldst2(SSA_CS_ALERT_RCVD)
*Mar  1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaIgnore: cid(44), st(SS
A_CS_ACTIVE),oldst(5), ev(52)
Router#
Router#! digit punched
Router#
Note The phone at the terminating gateway enters digit 1.
*Mar  1 15:36:11.204: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin: (dstVdbPt
r=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,
    digit=1, digit_begin_flags=0x0, rtp_timestamp=0x0
    rtp_expiration=0x0, dest_mask=0x2)
*Mar  1 15:36:11.504: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: (dstVdbPtr=
0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,
    digit=1,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), dig
it_tone_mode=0
Note The phone at the terminating gateway enters digit 2.
*Mar  1 15:36:11.604: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin: (dstVdbPt
r=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,
    digit=2, digit_begin_flags=0x0, rtp_timestamp=0x0
    rtp_expiration=0x0, dest_mask=0x2)
*Mar  1 15:36:11.904: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: (dstVdbPtr=
0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,
    digit=2,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), dig
it_tone_mode=0
Router#
Router#
*Mar  1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/cc_handle_periodic_timer: Calling
the callback, ccTimerctx - 0x628B6330
*Mar  1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/ccTimerStart: ccTimerctx - 0x628B6
330
Router#
Router#!call hung up  The user at the terminating gateway hangs up the call.
Router#
Note 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)
Note The voice gateway begins tearing down the conference and dropping the bridge.
*Mar  1 15:36:22.920: //-1/xxxxxxxxxxxx/CCAPI/ccConferenceDestroy: (confID=0x15,
 tag=0x0) 
*Mar  1 15:36:22.920: //45/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done: (confID=0
x15, srcIF=0x62EC61A4, srcCallID=0x2D, dstCallID=0x2C, disposition=0 tag=0x0)
*Mar  1 15:36:22.920: //44/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done: (confID=0
x15, srcIF=0x637EC1E0, srcCallID=0x2C, dstCallID=0x2D, disposition=0 tag=0x0)
*Mar  1 15:36:22.924: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(30=CC_EV_CONF_
DESTROY_DONE), cid(44), disp(0)
*Mar  1 15:36:22.924: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: cid(44)st(SS
A_CS_CONF_DESTROYING)ev(SSA_EV_CONF_DESTROY_DONE)
oldst(SSA_CS_ACTIVE)cfid(21)csize(2)in(1)fDest(1)
*Mar  1 15:36:22.924: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2
(SSA_CS_CONF_DESTROYING)oldst2(SSA_CS_ACTIVE)
*Mar  1 15:36:22.924: //45/45F2AAE28044/SSAPP:0:-1/ssaConfDestroyDone:
*Mar  1 15:36:22.924: //44/xxxxxxxxxxxx/CCAPI/ccCallDisconnect: (callID=0x2C, ca
use=0x10 tag=0x0)
Note The voice gateway stops call accounting on the incoming call, indicated by the leg_type=True message. The cause code is then set for the originating leg.
*Mar  1 15:36:22.924: //44/45F2AAE28044/CCAPI/ccCallDisconnect: calling accounti
ng start for callID=44 leg_type=1 
*Mar  1 15:36:22.924: //44/45F2AAE28044/CCAPI/ccCallDisconnect: existing_cause =
 0x0, new_cause = 0x10 
*Mar  1 15:36:22.924: //44/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info: (callID=
0x2C)
*Mar  1 15:36:22.924: //45/xxxxxxxxxxxx/CCAPI/ccCallDisconnect: (callID=0x2D, ca
use=0x10 tag=0x0)
Note The voice gateway stops call accounting for the outgoing call, indicated by the leg_type=False message. The cause code is verified for the terminating leg.
*Mar  1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: calling accounti
ng start for callID=45 leg_type=0
*Mar  1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: existing_cause =
 0x10, new_cause = 0x10 
*Mar  1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: using the existi
ng_cause 0x10
*Mar  1 15:36:22.928: //45/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info: (callID=
0x2D)
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_api_icpif: expect factor = 0
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/g113_calculate_impairment: (delay=
79,
      loss=0), Io=0 Iq=0 Idte=0 Idd=0 Ie=10 Itot=10
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: the remote
 IP is 171.69.85.111
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: hwidb is E
thernet0/0
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: reduce cal
lnum of entry: 0, voip: 0, mmoip: 0
*Mar  1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: remove an
entry
*Mar  1 15:36:22.932: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnect_done: (vdbP
tr=0x62EC61A4, callID=0x2D, disp=0, tag=0x0)
*Mar  1 15:36:22.932: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessMan
ager: No profileTable set for callID[45]
*Mar  1 15:36:22.936: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetDataByRef: No tdObject
found in profileTable for tagID[6] of callID[45]
*Mar  1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: not incoming
 entry
*Mar  1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: entry's inco
ming FALSE.
*Mar  1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: is_incoming
is FALSE
*Mar  1 15:36:22.940: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(12=CC_EV_CALL_
DISCONNECT_DONE), cid(45), disp(0)
*Mar  1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS
_DISCONNECTING)ev(SSA_EV_CALL_DISCONNECT_DONE)
oldst(SSA_CS_ACTIVE)cfid(-1)csize(2)in(0)fDest(0)
*Mar  1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA
_CS_DISCONNECTING)oldst2(SSA_CS_CONF_DESTROYING)
*Mar  1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaDisconnectDone:
*Mar  1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaAAA_CheckAccounting: accou
nting generation enabled
*Mar  1 15:36:22.940: //45/xxxxxxxxxxxx/CCAPI/ccCallSetAAA_Accounting: callID=0x
2D, accounting=0
*Mar  1 15:36:22.944: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: not the Vo
IP or MMoIP
*Mar  1 15:36:22.948: //44/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnect_done: (vdbP
tr=0x637EC1E0, callID=0x2C, disp=0, tag=0x0)
*Mar  1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: ccFreeRawMsg
Info(0x6307595C)
*Mar  1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: Decrement ca
ll volume counter 1
*Mar  1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: current call
 volume: 0
*Mar  1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: entry's inco
ming TRUE.
*Mar  1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: is_incoming
is TRUE
*Mar  1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: Deleting pro
fileTable[0x6380E11C]
*Mar  1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructTDHashProfileTab: Dest
ructor Profile Table (0x6380E11C)
*Mar  1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructInstanceTDObject: tdOb
ject[0x63401148] tagID[5]
*Mar  1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructInstanceTDObject: tdOb
ject[0x638BC1AC] tagID[6]
*Mar  1 15:36:22.956: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(12=CC_EV_CALL_
DISCONNECT_DONE), cid(44), disp(0)
*Mar  1 15:36:22.956: //44/45F2AAE28044/SSAPP:10002:-1/ssaTraceSct: cid(44)st(SS
A_CS_DISCONNECTING)ev(SSA_EV_CALL_DISCONNECT_DONE)
oldst(SSA_CS_CONF_DESTROYING)cfid(-1)csize(1)in(1)fDest(1)
Router#
*Mar  1 15:36:22.956: //44/45F2AAE28044/SSAPP:10002:-1/ssaDisconnectDone:
Related Commands

Command

Description

debug voip ccapi error

Traces error logs in the CCAPI.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr all

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

debug voip ivr all
no debug voip ivr all
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug voip ivr all command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

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

Command

Description

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr applib

To display debug messages for IVR API libraries being processed, use the debug voip ivr applib command in privileged EXEC mode. To disable the debug output, use the no form of this command.

debug voip ivr applib
no debug voip ivr applib
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug voip ivr applib command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

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

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr callsetup

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

debug voip ivr callsetup
no debug voip ivr callsetup
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug voip ivr callsetup command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

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

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr digitcollect

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

debug voip ivr digitcollect
no debug voip ivr digitcollect
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug voip ivr digitcollect command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

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

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr dynamic

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

debug voip ivr dynamic
no debug voip ivr dynamic
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug voip ivr dynamic command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

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

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr error

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

debug voip ivr error
no debug voip ivr error
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

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

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

Related Commands

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr script

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

debug voip ivr script
no debug voip ivr script
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug voip ivr script command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following output is an example of what is displayed when the debug voip ivr script command is entered:
Router# debug voip ivr script
ivr script debugging is on
Router#
Router#!call initiated
Router#
Router#!call answered
Router#
*Mar 11 02:50:59.431: //-1//TCL2:HN341BC8B0:/tcl_PutsCmd:
 Unlimited Time
*Mar 11 02:50:59.431:
Router#
*Mar 11 02:51:28.343: //-1//TCL2:HN341C6A88:/tcl_PutsCmd:
 Unlimited Time
*Mar 11 02:51:28.343:
Router#
Router#!digits entered
Router#
Router#!call terminated
Router#
Related Commands

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr settlement

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

debug voip ivr settlement
no debug voip ivr settlement
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2

This command was introduced.

12.0(4)XH

Settlement was added.

12.2(11)T

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

Usage Guidelines

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

Note Cisco recommends that you log output from the debug voip ivr settlement command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following output is an example of what is displayed when the debug voip ivr settlement command is entered:
Router # debug voip ivr settlement
ivr settlement activities debugging is on
Router#
Router#!call initiated
Router#
*Mar 11 03:02:20.819: //142//TCL2:/SettlementValidateCall: target=, tokenp=0x0
Router#
Router#!call answered
Router#
*Mar 11 03:02:40.979: //-1//TCL2:HN342689D0:/vtr_lg_cssettlement_time: 
credit_time=uninitialized
Router#
Router#!digits dialed
Router#
Router#!call terminated
Related Commands

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr states

Displays IVR states.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.
debug voip ivr states

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

debug voip ivr states
no debug voip ivr states
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

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

Note Cisco recommends that you log output from the debug voip ivr states command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

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

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr tclcommands

Displays the TCL commands used in the script.

voice call debug

Allows configuration of the voice call debug output.

debug voip ivr tclcommands

To display debug messages for the TCL commands used in IVR scripts, use the debug voip ivr tclcommands command in privileged EXEC mode. To disable the debug output, use the no form of this command.

debug voip ivr tclcommands
no debug voip ivr tclcommands
Syntax Description

This command has no arguments or keywords.

Defaults

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug voip ivr tclcommands command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

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

Command

Description

debug voip ivr all

Displays all IVR messages.

debug voip ivr applib

Displays IVR API libraries being processed.

debug voip ivr callsetup

Displays IVR call setup being processed.

debug voip ivr digitcollect

Displays IVR digits collected during the call.

debug voip ivr dynamic

Displays IVR dynamic prompt play debug.

debug voip ivr error

Displays IVR errors.

debug voip ivr script

Displays IVR script debug.

debug voip ivr settlement

Displays IVR settlement activities.

debug voip ivr states

Displays IVR states.

voice call debug

Allows configuration of the voice call debug output.
debug voip rawmsg

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

debug voip rawmsg [detail]
no debug voip rawmsg [detail]
Syntax Description

detail

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

Defaults

Disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(6)T

This command was introduced.

12.2(11)T

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

Usage Guidelines

Cisco recommends that you log output from the debug voip rawmsg command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following example shows output when you use the debug voip rawmsg command:
Router#debug voip rawmsg
voip rawmsg debugging is on
Router#
*Mar  1 01:16:25.155: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al
loc from 1, Length 18 Body 638E0C5
Note These debug messages show that a raw message is allocated for this call. 63075164 is the pointer to the memory location for this raw message.
*Mar  1 01:16:25.155: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL
OCATED: ptr is 63075164, owner is 1, length is 18, msg is 638E0C54, type is 0, p
rotocol id is 0
Note The call control API (CCAPI) gets a setup indicator. It has no information about the callid (-1) and GUID (xxxxxxxxxxxx).
*Mar  1 01:16:25.159: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:
*Mar  1 01:16:25.159: Raw Message MaMa is TSP owner is CCAPI, length is 77, ptr
is 63075164, type is 0, protocol id is 2
Note The SSAPP at this stage knows about the CallEntry ID (30) but not about GUID (xxxxxxxxx) or the dial-peer (-1)
*Mar  1 01:16:25.163: //30/xxxxxxxxxxxx/SSAPP:-1:-1/ssaCallSetupInd:
*Mar  1 01:16:25.163: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2
Note The SSAPP learns about the GUID (34C457CD802F) and also learns the incoming dial peer (10002)
*Mar  1 01:16:25.163: //30/34C457CD802F/SSAPP:10002:-1/ssaSetupPeer:
*Mar  1 01:16:25.163: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2
Note The CCAPI gets the call proceeding for CallEntry ID 30. CCAPI still does not have a GUID (xxxxxxxxxxx).
*Mar  1 01:16:25.163: //30/xxxxxxxxxxxx/CCAPI/ccCallProceeding:
Note A new raw message buffer is created and the previous one is released.
*Mar  1 01:16:25.163: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al
loc from 10, Length 77 Body 0
*Mar  1 01:16:25.167: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL
OCATED: ptr is 630751EC, owner is 10, length is 77, msg is 638E0F0C, type is 0,
protocol id is 0
*Mar  1 01:16:25.167: //30/34C457CD802F/SSAPP:10002:-1/ssaSetupPeer:
*Mar  1 01:16:25.167: ssaSetupPeer: Saved rawmsgpp 630751EC len 77
IAM,
GCI,34c457cd14f911cc802f95f5fabb6b0f?)??p?34999
*Mar  1 01:16:25.167: //30/xxxxxxxxxxxx/CCAPI/ccCallSetupRequest:
*Mar  1 01:16:25.167: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2
*Mar  1 01:16:25.167: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
*Mar  1 01:16:25.167: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr
is 63075164, type is 0, protocol id is 2
Note The SSAPP gets a message indicating the digits were passed along the VoIP call leg to the terminating gateway. The CallEntry ID is 30, GUID is 34C457CD802F and the incoming dial peer is 10002.
*Mar  1 01:16:25.167: //30/34C457CD802F/SSAPP:10002:-1/ssaReportDigitsDone:
Note The old raw message 63075164 was freed. The new one is 630751EC.
*Mar  1 01:16:25.179: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo:
Router#Raw Message FREED: ptr is 63075164, owner is 3, length is 4D, msg is 638E
0DB0, type is 0, protocol id is 2
Note CCAPI got a call proceeding on the second call leg (31); it has no information about the GUID (xxxxxxxxx).
*Mar  1 01:16:25.223: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_proceeding:
Note CCAPI got a call alert on the second call leg (31); still no information about the GUID (xxxxxxxxx)
*Mar  1 01:16:25.227: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_alert:
Note The alert is sent to the first call leg (30), GUID 34C457CD802F.
*Mar  1 01:16:25.227: //30/34C457CD802F/SSAPP:10002:-1/ssaAlert:
*Mar  1 01:16:25.227: //30/xxxxxxxxxxxx/CCAPI/ccCallAlert:
Note The call is answered at this point and the CCAPI gets a call connect for the second call leg (CallEntry ID is 31; GUID is xxxxxxxxx)
*Mar  1 01:16:40.975: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_connected:
Note The call connect is sent to the first call leg (30), GUID 34C457CD802F
*Mar  1 01:16:40.975: //30/34C457CD802F/SSAPP:10002:-1/ssaConnect:
*Mar  1 01:16:40.975: //30/xxxxxxxxxxxx/CCAPI/ccCallConnect:
Note The current raw-message (ptr 630751EC) is released; a new one will be proclaimed when needed.
*Mar  1 01:16:40.975: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo: Raw Message FREE
D: ptr is 630751EC, owner is 10, length is 4D, msg is 638E0F0C, type is 0, proto
col id is 2
Note A new raw message (ptr 63075274) is proclaimed
*Mar  1 01:17:04.007: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al
loc from 1, Length 4 Body 638E1068
*Mar  1 01:17:04.007: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL
OCATED: ptr is 63075274, owner is 1, length is 4, msg is 638E1068, type is 0, pr
otocol id is 0
Note The call terminates now. CCAPI detects a call disconnect from the first call leg (30) with no GUID (xxxxxxxxx).
*Mar  1 01:17:04.007: //30/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnected:
*Mar  1 01:17:04.007: Raw Message MaMa is TSP owner is CCAPI, length is 4, ptr i
s 63075274, type is 0, protocol id is 2
Note The disconnect is sent to the first call leg (30), GUID (34C457CD802F)
*Mar  1 01:17:04.011: //30/34C457CD802F/SSAPP:10002:14/ssaDisconnected:
*Mar  1 01:17:04.011: Raw Message MaMa is TSP owner is SSAPP, length is 4, ptr i
s 63075274, type is 0, protocol id is 2
Note The CCAPI disconnects both call legs (incoming 30 and outgoing 31)
*Mar  1 01:17:04.011: //30/xxxxxxxxxxxx/CCAPI/ccCallDisconnect:
*Mar  1 01:17:04.011: //31/xxxxxxxxxxxx/CCAPI/ccCallDisconnect:
*Mar  1 01:17:04.011: Raw Message MaMa is TSP owner is SSAPP, length is 4, ptr i
s 63075274, type is 0, protocol id is 2
Note The raw message is released.
*Mar  1 01:17:04.015: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo: Raw Message FREE
D: ptr is 63075274, owner is 3, length is 4, msg is 638E1068, type is 0, protoco
l id is 2
Note The following example shows output when you use the debug voip rawmsg detail command. This example shows that the CCAPI layer received an indication for call setup. The detailed raw message dumps the hex of the message. This output is used to track down data pointing to different variables within the software modules:
Router# debug voip rawmsg detail
*Mar  6 17:03:24.169://-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo:VoIP Raw Msg Al
loc from 5, Length 0 Body 0
*Mar  6 17:03:24.173://-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:
*Mar  6 17:03:24.173:Raw Message MaMa is CCAPI owner is CCAPI, length is 59, pt
r is 63045C14, type is 0, protocol id is 18
*Mar  6 17:03:24.173:Raw Message is :1C 39 9E 01 00 03 67 74 64 00 00 00 2E 49
 41 4D 2C 0D 0A 47 43 49 2C 35 33 39 61 30 35 39 64 31 39 36 62 31 31 63 63 38 3
9 30 63 39 30 37 65 31 65 31 37 35 61 34 37 0D 0A 0D 0A
Related Commands

Command

Description

debug cdapi

Displays information about the call distributor application programming interface

debug tsp

Displays information about the telephony service provider.

voice call debug

Allows configuration of the voice call debug output.

debug vtsp all

To show debugging information for all debug vtsp commands, use the debug vtsp all command in privileged EXEC mode. Use the no form of this command to disable debugging output.

debug vtsp all
no debug vtsp all
Syntax Description

This command has no arguments or keywords.

Defaults

Debugging for VTSP is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)T

This command was introduced on the Cisco AS5300.

12.0(7)XK

This command was first supported on the Cisco 2600, Cisco 3600 and Cisco MC3810 series.

12.1(2)T

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

12.2(11)T

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

Usage Guidelines

The debug vtsp all command enables the following debug vtsp commands: debug vtsp session, debug vtsp error, and debug vtsp dsp. For more information or sample output, see the individual commands.

Execution of the no debug vtsp all command will turn off all VTSP-level debugging. You should turn off all debugging and then enter the debug commands you are interested in one by one. This process helps avoid confusion about which ports you are actually debugging.

Caution Using this command can severely impact network performance and prevent any faxes from succeeding.

Examples

The following example shows the debug vtsp all command on a Cisco 3640 modular access router:
Router# debug vtsp all
Voice telephony call control all debugging is on
Note At this point, the VTSP is not aware of anything. The format of this message is
//callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number:

•CallEntry ID is -1.

•GUID is xxxxxxxxxx.

•The voice port is blank.

•Channel ID is -1.

•DSP ID is -1.

•DSP channel ID is -1.
*Mar  1 08:23:10.869: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: .
Note The original and the translated calling number are the same (55555) and the original and the translated called number are the same (888545). These numbers are often the same because if a translation rule is applied, it will be on the dial peers or the ports, both of which comes later than these VTSP messages in the Cisco IOS code execution.
*Mar  1 08:23:10.869: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: 
calling_number(original)= calling_number(xlated)=55555 called_number(original)= 
called_number(xlated)=888545 redirectNumber(original)= redirectNumber(xlated)=
Note The VTSP got a call setup indicator from the TSP layer with called number 888545 and calling number 55555. There is no awareness of the CallEntry ID (-1) or the GUID (xxxxxxxxxxxx).
*Mar  1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_call_setup_ind: 
(sdb=0x634C90EC, tdm_info=0x0, tsp_info=0x63083950, calling_number=55555 calling_oct3 = 
0x80, called_number=888545 called_oct3 = 0x80, oct3a=0x0): peer_tag=10002
*Mar  1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_fill_setup_ind
: ev.clg.clir is 0
 ev.clg.clid_transparent is 0
 ev.clg.null_orig_clg is 0
 ev.clg.calling_translated is false
*Mar  1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_call_setup_ind: .
*Mar  1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_allocate_cdb: ,cdb 
0x635FC480
*Mar  1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_call_setup_ind:
*Mar  1 08:23:10.873:  source route label
Note At this point, the VTSP is not aware of anything. The format of this message is
//callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number:

•CallEntry ID is -1.

•GUID is D2F6429A8A8A.

•The voice port is 1/0:23 where 23 indicates D channel.

•The T1 channel is still unknown at this point (-1).

•The DSP is 0.

•The DSP channel is 4.
*Mar  1 08:23:10.873: //-1/D2F6429A8A8A/VTSP:(1/0:23):-1:0:4/vtsp_do_call_setup_
ind: Call ID=101002, guid=635FCB08
Note The VTSP learns about the B-channel (changed from -1 to 22), and the CallEntry ID is still unknown (-1).
*Mar  1 08:23:10.873: //-1/D2F6429A8A8A/VTSP:(1/0:23):22:0:4/vtsp_do_call_setup_ind: 
type=0, under_spec=1615186336, name=, id0=23, id1=0, id2=0, calling=55555,called=888545 
subscriber=RegularLinevtsp_do_call_setup_ind: redirect DN =  reason = -1
*Mar  1 08:23:10.877: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_normal_call_setup_ind: .
Note The VTSP learns the CallEntry ID. The format of this message is
//callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number:

•CallEntry ID is 899 (changed from -1 to 899)

•GUID is D2F6429A8A8A

•The voice port is 1/0:23 where 23 indicates D channel

•The T1 channel is 22

•The DSP is 12

•The DSP channel is 4
*Mar  1 08:23:10.877: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_insert_cdb:,cdb 
0x635FC480, CallID=899
*Mar  1 08:23:10.877: 
//899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_open_voice_and_set_params: .
Note In the following outputs VTSP sets some of the voice parameters for this call:

•Modem capability

•Playout delay

•Dial-peer tag 10003

•Digit timeouts
*Mar  1 08:23:10.877: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_proto_from_cdb: 
cap_modem_proto 0
*Mar  1 08:23:10.881: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_playout_cdb:playout 
default
*Mar  1 08:23:10.881: 
//899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_dsp_echo_canceller_control: echo_cancel: 1
*Mar  1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_save_dialpeer_tag: tag 
= 10003
*Mar  1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_report_digit_control: 
vtsp_report_digit_control: enable=0:
*Mar  1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_report_digit_control: 
digit reporting disabled
*Mar  1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_digit_timeouts: : 
vtsp_get_digit_timeouts
Note VTSP sends out a call-proceeding message to the POTS leg:
*Mar  1 08:23:10.885: 
//899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event:vtsp:[1/0:23:899, 
S_SETUP_INDICATED, E_CC_PROCEEDING]
*Mar  1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_proceeding: .
*Mar  1 08:23:10.941: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_dialpeer_tag: tag 
= 10003
*Mar  1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_dialpeer_tag: tag 
= 10003
Note VTSP sends out an alerting to the POTS leg; the phone is ringing at this time.
*Mar  1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_PROCEEDING, E_CC_ALERT]
*Mar  1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_alert: .
*Mar  1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3019095
*Mar  1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_dialpeer_tag: tag 
= 10003
Note The phone gets answered here, a bridge is now setup between the two call legs.
*Mar  1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_ALERTING, E_CC_BRIDGE]
*Mar  1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_bridge: .
Note The call is now connected.
*Mar  1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_ALERTING, E_CC_CONNECT]
*Mar  1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_alert_connect: .
*Mar  1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_ring_noan_timer_stop: 
3019877
Note The VTSP received a capabilities indication event from the CCAPI . The VTSP needs to be aware of this because it handles the DSPs.
*Mar  1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_CONNECT, E_CC_CAPS_IND]
*Mar  1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: .
*Mar  1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: RTP
 
PT:NTE[101],NTEtx[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDTMF[121],FaxRelay[122],CASsig[
123],ClearChan[125],PCMu[0],PCMa[8]Codec[4],TxDynamicPayload[0], RxDynamicPayload[0]
*Mar  1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: dtmf relay: 
mode=32, codec=1
*Mar  1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: passthrough: 
cap_modem_proto 0, cap_modem_codec 0, cap_modem_redundancy 0, payload100, modem_relay 0, 
gw-xid=0
*Mar  1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: Encap 1, Vad 
2, Codec 0x4, CodecBytes 20,
             FaxRate 2, FaxBytes 20, FaxNsf 0xAD0051
             SignalType 2
             DtmfRelay 32, Modem 0, SeqNumStart 0x1343
*Mar  1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind:
*Mar  1 08:23:18.777:  FORKING Parameters are forking mask: 0, simple_forking_codec_mask: 
0, complex_forking_codec_mask 0
*Mar  1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: [ 
mode:0,init:60, min:40, max:200]
Note The VTSP received events regarding capabilities acknowledged from the CCAPI.
*Mar  1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_CONNECT, E_CC_CAPS_ACK]
*Mar  1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ack: .
*Mar  1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ack: passthrough: 
cap_modem_proto 0, cap_modem_codec 0, cap_modem_redundancy 0, payload100, modem_relay 0, 
gw-xid=0
*Mar  1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ack: Named 
Telephone Event payload: rcv 101, tx 101
*Mar  1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_switch_codec:
*Mar  1 08:23:18.777:  DTMF Relay in act_switch_codec is 32
*Mar  1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_dsp_encap_config:
*Mar  1 08:23:18.777:  set_dsp_encap_config: logical ssrc 40
*Mar  1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_proto_from_cdb: 
cap_modem_proto 0
*Mar  1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_switch_codec: codec = 
16
*Mar  1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3019878
*Mar  1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, SP_PENDING_CODEC_SWITCH, E_DSPRM_PEND_SUCCESS]
*Mar  1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_pend_codec_success: .
*Mar  1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3019878
*Mar  1 08:23:18.781: 
//899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_open_voice_and_set_params: .
*Mar  1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_dsp_encap_config:
*Mar  1 08:23:18.781:  set_dsp_encap_config: logical ssrc 40
*Mar  1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_proto_from_cdb: 
cap_modem_proto 0
*Mar  1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_playout_cdb:playout 
default
*Mar  1 08:23:18.781: 
//899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_dsp_echo_canceller_control: echo_cancel: 1
*Mar  1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_add_fork:
*Mar  1 08:23:18.785: vtsp_add_fork
*Mar  1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info:
*Mar  1 08:23:18.785: vtsp_update_fork_info: add_fork=0
*Mar  1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_xmit_info_node:
*Mar  1 08:23:18.785: vtsp_get_xmit_info_node
*Mar  1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info:
*Mar  1 08:23:18.785:  vtsp_update_fork_info xmit func is 60FC43F0, context is 
635BC51Cpeer_call_id: 900, stream_count: 1, update_flag 0
Router#
*Mar  1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info:
*Mar  1 08:23:18.785:  The stream bit-mask is 1
*Mar  1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info:
*Mar  1 08:23:18.785:  The stream type is 0
*Mar  1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info:
*Mar  1 08:23:18.785:  The logical ssrc is 64 for stream 0
*Mar  1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_stream_count:
*Mar  1 08:23:18.785:  g711_voice_count=0 g711_avt_count = 0
 g711_voice_avt_count = 0 complex_voice_count = 1
 complex_avt_count = 0 complex_voice_avt_count = 0
Note A digit begin event was detected while in the connect state. Digit 1 is dialed outbound on the POTS legs.
*Mar  1 08:23:26.745: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_call_digit_begin: 
vtsp_call_digit_begin: digit=1, digit_begin_flags=0x0, rtp_timestamp=0, rtp_expiration=0
*Mar  1 08:23:26.745: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_CONNECT, E_CC_DIGIT_BEGIN]
*Mar  1 08:23:26.745: 
//899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_digit_begin:act_digit_begin
*Mar  1 08:23:27.045: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_call_digit_end: 
vtsp_call_digit_end: digit=1, duration=300
Note A digit end event was detected while in the connect state. The total duration of the digit was 300 ms.
*Mar  1 08:23:27.045: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_CONNECT, E_CC_DIGIT_END,]
*Mar  1 08:23:27.045: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_digit_end: 
act_digit_end
Note The call is hung up at this point, VTSP receives a bridge drop event from the CCAPI.
*Mar  1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_CONNECT, E_CC_BRIDGE_DROP]
*Mar  1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_remove_stream_node:
*Mar  1 08:23:39.393: vtsp_remove_stream_node
*Mar  1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_xmit_info_node:
*Mar  1 08:23:39.393: vtsp_get_xmit_info_node
*Mar  1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_remove_stream_node:
*Mar  1 08:23:39.393:  Stream count is 1 in function vtsp_remove_stream_node
*Mar  1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_bdrop: .
*Mar  1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_is_record_active:
*Mar  1 08:23:39.393: vtsp_is_record_active: false
Note VTSP gets a disconnect event from the CCAPI.
*Mar  1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_CONNECT, E_CC_DISCONNECT]
*Mar  1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_disconnect: .
Note Following the disconnect event from the CCAPI, the timers are stopped.
*Mar  1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_ring_noan_timer_stop: 
3021940
*Mar  1 08:23:39.397: 
//899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_pcm_tone_detect_timer_stop: 3021940
*Mar  1 08:23:39.397: 
//899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_pcm_switchover_timer_stop: 3021940
*Mar  1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_cm_detect_timer_stop: 
3021940
*Mar  1 08:23:39.397: 
//899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_relay_mode_timer_stop: 3021940
*Mar  1 08:23:39.397: 
//899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_relay_stats_timer_stop: 3021940
*Mar  1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021940
*Mar  1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_disconnect: cdb 
0x635FC480, cause 0x10
*Mar  1 08:23:39.401: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3021940
Note Statistics are collected for the DSP.
*Mar  1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_WAIT_STATS, E_DSP_GET_ERROR]
*Mar  1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_get_error: .
*Mar  1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_print_error_stats: 
rx_dropped=0 tx_dropped=0
*Mar  1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_print_error_stats: 
rx_control=55 tx_control=18 tx_control_dropped=0  dsp_mode_channel_1=0 
dsp_mode_channel_2=0c[0]=0c[1]=2c[2]=6c[3]=87c[4]=83c[5]=84c[6]=106c[7]=78c[8]=0c[9]=32639
c[10]=32639c[11]=32639c[12]=32639c[13]=32639c[14]=32639c[15]=32639
*Mar  1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021941
*Mar  1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3021941
*Mar  1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_WAIT_STATS, E_DSP_GET_LEVELS]
*Mar  1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_get_levels: .
*Mar  1 08:23:39.413: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_stats_complete: .
*Mar  1 08:23:39.413: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021941
*Mar  1 08:23:39.413: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_ring_noan_timer_stop: 
3021941
*Mar  1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3021942
Note The VTSP received a disconnect confirmation from the TSP layer.
*Mar  1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_WAIT_RELEASE, E_TSP_DISCONNECT_CONF]
*Mar  1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_wrelease_release: .
*Mar  1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_play_busy_timer_stop:
*Mar  1 08:23:39.417: vtsp_play_busy_timer_stop: 3021942
*Mar  1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021942
*Mar  1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history: .
*Mar  1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history:
*Mar  1 08:23:39.417: vtsp_do_call_history :  src carrier id
*Mar  1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history:
*Mar  1 08:23:39.421: vtsp_do_call_history : tgt carrier id
*Mar  1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history: 
CoderRate 16
Note DSP resource manager updates the state.
*Mar  1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: 
vtsp:[1/0:23:899, S_CLOSE_DSPRM, E_DSPRM_CLOSE_COMPLETE]
*Mar  1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_terminate: .
*Mar  1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_free_cdb: ,cdb 
0x635FC4803
Related Commands

Command

Description

debug vtsp port

Limits VTSP debug output to a specific voice port.

show debug

Displays which debug commands are enabled.

Hierarchical Navigation

Cisco IOS Software Releases 12.2 T

Enhanced Debug Capabilities for Cisco Voice Gateways

Downloads

Table Of Contents

Enhanced Debug Capabilities for Cisco Voice Gateways

Contents

Information About Enhanced Debug Capabilities for Cisco Voice Gateways

Debug Header Format

IVR Module Dependent List

CallEntry ID and GUID Call Legs

How to Manage the Voice Call Debug Output

SUMMARY STEPS

DETAILED STEPS

Sample Output Examples for the Enhanced Debug Commands

Full GUID Header Example

Short Header Example

Setup and Teardown Example

Additional References

Related Documents

MIBs

Technical Assistance

Command Reference

debug rtsp all

Syntax Description

Defaults

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

debug rtsp api

Syntax Description

Defaults

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

debug rtsp client

Syntax Description

Defaults

Command Modes

Command History

Usage Guidelines

Related Commands

debug rtsp error

Syntax Description

Defaults

Command Modes

Command History

Related Commands

debug rtsp pmh

Syntax Description

Defaults

Command Modes

Command History

Usage Guidelines

Related Commands

debug rtsp session

Syntax Description

Defaults

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

debug rtsp socket

Syntax Description

Defaults

Command Modes

Command History

Usage Guidelines

Related Commands

debug voip ccapi error

Syntax Description

Command Modes

Command History

Usage Guidelines

Related Commands