Worldwide [change] |Account |Register |About Cisco
Guest

Hierarchical Navigation

Gateway Protocols

Troubleshooting Tandem Switch VoFR Configurations

Downloads

Document ID: 46271


Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Configure
      Network Diagram
Verify
      Debug and Verification for Cisco 3640
      Debug on 3600
Understanding Debug Output
Troubleshoot
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

In VoFR, a feature called Tandem switching is available. Tandem switching allows calls to be routed to a hub location prior to reaching their final destination, where you can also modify the dial plan and destination-pattern. This feature bypasses traditional tandem PBX switching and avoids the use of valuable PBX trunk lines and multiple voice encoding. Tandem switching helps you to plan a large network, because the hub can be the central router through which all calls pass, and a full mesh topology is not necessary. It also simplifies the troubleshooting stages of a call, because the call can be easily broken down into more call-legs with Tandem switching. Tandem switching also helps with you to manage calls.

This document helps you to debug and troubleshoot the problems that are faced when you use Tandem switching.

Prerequisites

Requirements

This document requires a basic knowledge of the dial-peer voice vofr command and of the different steps involved in a call setup. Refer to Configuring Voice over Frame Relay.

Components Used

This document uses a Cisco 3640 router as Tandem switch with Cisco IOS® Software Release 12.3(7)T and can use any Cisco router which supports FXS ports at the edges. For the example in this document, Cisco 2600 and Cisco MC3810 Series Routers are used as spoke routers.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to Cisco Technical Tips Conventions.

Configure

This document provides information about the debug output that you can expected from a Tandem switch that is configured according to the instructions in Configuring Tandem Switching in a VoFR Environment.

Note: To find additional information on the commands used in this document, use the Command Lookup Tool ( registered customers only) .

Network Diagram

This document uses this network setup:

vofr_3600_verify.gif

After you configure the devices in this sample network, you must verify that the configurations are correct and that the network is operating properly. Use the sample debug outputs in this document to ensure that your network is operating properly.

Verify

This section provides information that you can use to confirm that your configuration is working properly.

Note: Before you issue debug commands, refer to Important Information on Debug Commands.

Debug and Verification for Cisco 3640

To verify that the Cisco 3640 is operating properly in the sample network, enable these debug commands from the enable prompt:

The Cisco 3640 acts as a Tandem switch in the sample network. The Cisco 3640 has to direct calls from sources to appropriate destinations. In this case, the 3640 will accept a call from the Cisco 2600, examine the packets, determine the destination, and then route the call. A minimum of two dial-peer voice vofr commands must be configured on a Tandem switch router.

Note: A call may be routed through multiple hops (over multiple Tandem switching routers) before it reaches the final destination.

Debug on 3600 

3640# show debugging

Voice Telephony session debugging is on (filter is OFF)
Voice Telephony dsp debugging is on (filter is OFF)
Voice Telephony error debugging is on (filter is OFF)
Voice Telephony tone generation debugging is on (filter is OFF)
voip ccAPI function enter/exit debugging is on (filter is OFF)

Voice Port Module session debugging is on
Voice Port Module DSP message debugging is on
Voice Port Module DSPware ovelay debugging is on
Voice Port Module error debugging is on
Voice Port Module signaling debugging is on
Voice Port Module voaal2 debugging (type3 ) is on

Voice Port Module trunk conditioning is on
Voice Port Module tgrm debugging is on

When you are satisfied that the correct debug commands are enabled, place a call from one end of the network to the other end, to generate traffic across the network. In this document, the call is made from extension 6666 to extension 5555. The traffic that is generated after you place a call in the sample network is shown in next sections. Issue the show logging command to view the debug output, unless your router is configured to write all output to your monitor in real time.

Understanding Debug Output

The next sample output shows confirmations that the network is operating properly and, more specifically, that the Cisco 3640 is operating properly.

As you can see, each grouped set of debug output lines has an explanation of what is happening in the call process. This will help you to identify and troubleshoot problems, should problems occur.

3640# show logging

Syslog logging: enabled (11 messages dropped, 1 messages rate-limited,
0 flushes, 0 overruns, xml disabled, filtering disabled)
Console logging: level debugging, 2155 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 1819 messages logged, xml disabled,
filtering disabled
Logging Exception size (4096 bytes)
Count and timestamp logging messages: disabled

No active filter modules.

Trap logging: level informational, 40 message lines logged

Log Buffer (4096 bytes):

*Mar 5 00:13:05.822: //-1/xxxxxxxxxxxx/CCAPI/cc_api_display_ie_subfields:
*Mar 5 00:13:05.826: cc_api_call_setup_ind_common:
*Mar 5 00:13:05.826: cisco-username=
*Mar 5 00:13:05.826: ----- ccCallInfo IE subfields -----
*Mar 5 00:13:05.826: cisco-ani=6666
*Mar 5 00:13:05.826: cisco-anitype=0
*Mar 5 00:13:05.826: cisco-aniplan=0
*Mar 5 00:13:05.826: cisco-anipi=0
*Mar 5 00:13:05.826: cisco-anisi=0
*Mar 5 00:13:05.826: dest=5555
*Mar 5 00:13:05.826: cisco-desttype=0
*Mar 5 00:13:05.826: cisco-destplan=1
*Mar 5 00:13:05.826: cisco-rdn=
*Mar 5 00:13:05.826: cisco-rdntype=0
*Mar 5 00:13:05.826: cisco-rdnplan=0
*Mar 5 00:13:05.826: cisco-rdnpi=0
*Mar 5 00:13:05.826: cisco-rdnsi=0
*Mar 5 00:13:05.826: cisco-redirectreason=0

*Mar 5 00:13:05.826: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind_common:
(vdb Ptr=0x645BA0BC, callInfo={called=5555,called_oct3=0x81,calling=6666,
calling_oct3=0x0,calling_oct3a=0x0,calling_xlated=false,
subscriber_type_str=Unknown,fdest=1,peer_tag=2, prog_ind=0,
callingIE_present 0, src_route_label=, tgt_route_label=,
clid_transparent=0},callID=0x63CF3854)
*Mar 5 00:13:05.826: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind_common:
*Mar 5 00:13:05.826: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind_common:
type 0 , prot 13
*Mar 5 00:13:05.826: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 5 00:13:05.826: ccCheckClipClir: calling number is: "6666",
calling oct3ais: 0x0
*Mar 5 00:13:05.830: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 5 00:13:05.830: Calling Party number is User Provided
*Mar 5 00:13:05.830: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 5 00:13:05.830: Leaving ccCheckClipClir
calling number is: "6666"
calling oct3 is: 0x0
calling oct3a is: 0x0

!--- This debug output indicates that Call Control
!--- receives a call:

*Mar 5 00:13:05.830: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind_common:
(vdbPtr=0x645BA0BC, callInfo={called=5555, calling=6666, fdest=1 peer_tag=2},
callID=0x63CF3854)
*Mar 5 00:13:05.830: //12/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
Increment call volume: 0
*Mar 5 00:13:05.830: //12/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
current call volume: 1
*Mar 5 00:13:05.830: //12/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
entry's incoming TRUE.
*Mar 5 00:13:05.830: //12/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
is_incoming is TRUE
*Mar 5 00:13:05.830: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume:
not the VoIP or MMoIP

*Mar 5 00:13:05.834: //-1/xxxxxxxxxxxx/CCAPI/cc_process_call_setup_ind:
(event=0x646B0A60)
*Mar 5 00:13:05.834: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_registration_lookup:
matching parameters - called# [5555], consultid []
*Mar 5 00:13:05.834: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
Searching for node with called# [5555], consultid []
*Mar 5 00:13:05.834: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_registration_lookup:
No matching node

*Mar 5 00:13:05.834: //12/xxxxxxxxxxxx/CCAPI/ccCallSetContext:
(callID=0xC, context=0x63CBAF94)
*Mar 5 00:13:05.834: //12/A9AD583D800B/CCAPI/cc_process_call_setup_ind:
>>>>CCAPI handed cid 12 with tag 2 to app "Default"
*Mar 5 00:13:05.834: //12/A9AD583D800B/CCAPI/
ccTDPvtProfileTableObjectAccessManager:
Access Failed; profileTable not set [callID-0xC]
*Mar 5 00:13:05.834: //12/xxxxxxxxxxxx/CCAPI/ccTDUtilGetDataByRef:
No tdObject found in profileTable for tagID[6] of callID[12]

!--- This debug output indicates that Call Control
!--- proceeds to place calls:

*Mar 5 00:13:05.834: //12/xxxxxxxxxxxx/CCAPI/ccCallProceeding:
(callID=0xC, prog_ind=0x0)
*Mar 5 00:13:05.838: //12/A9AD583D800B/CCAPI/
ccTDPvtProfileTableObjectAccessManager:
Access Failed; profileTable not set [callID-0xC]
*Mar 5 00:13:05.838: //12/xxxxxxxxxxxx/CCAPI/ccTDUtilGetDataByRef:
No tdObject found in profileTable for tagID[6] of callID[12]
*Mar 5 00:13:05.838: //12/xxxxxxxxxxxx/CCAPI/ccCallSetupRequest:
(Inbound call= 0xC, outbound peer =1, dest=, params=0x63CBBC04 mode=0,
*callID=0x63CBBC00, prog_ind = 0callingIE_present 0)
*Mar 5 00:13:05.838: //12/A9AD583D800B/CCAPI/ccCallSetupRequest:
*Mar 5 00:13:05.838: ccCallSetupRequest numbering_type 0x81
*Mar 5 00:13:05.838: //12/A9AD583D800B/CCAPI/ccCallSetupRequest:
dest pattern 5555, called 5555, digit_strip 0
*Mar 5 00:13:05.838: //12/A9AD583D800B/CCAPI/ccCallSetupRequest:
*Mar 5 00:13:05.838: callingNumber=6666, calledNumber=5555,
redirectNumber= display_info= calling_oct3a=0
*Mar 5 00:13:05.842: accountNumber=, finalDestFlag=1,
guid=A9AD583D-2C11-11D6-800B-8E895DFA65F6
*Mar 5 00:13:05.842: peer_tag=1
*Mar 5 00:13:05.842: //-1/xxxxxxxxxxxx/CCAPI/cc_api_display_ie_subfields:
*Mar 5 00:13:05.842: ccCallSetupRequest:
*Mar 5 00:13:05.842: cisco-username=
*Mar 5 00:13:05.842: ----- ccCallInfo IE subfields -----
*Mar 5 00:13:05.842: cisco-ani=6666
*Mar 5 00:13:05.842: cisco-anitype=0
*Mar 5 00:13:05.842: cisco-aniplan=0
*Mar 5 00:13:05.842: cisco-anipi=0
*Mar 5 00:13:05.842: cisco-anisi=0
*Mar 5 00:13:05.842: dest=5555
*Mar 5 00:13:05.842: cisco-desttype=0
*Mar 5 00:13:05.842: cisco-destplan=1
*Mar 5 00:13:05.842: cisco-rdn=
*Mar 5 00:13:05.842: cisco-rdntype=0
*Mar 5 00:13:05.842: cisco-rdnplan=0
*Mar 5 00:13:05.842: cisco-rdnpi=0
*Mar 5 00:13:05.842: cisco-rdnsi=0
*Mar 5 00:13:05.842: cisco-redirectreason=0

*Mar 5 00:13:05.842: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
(vdbPtr=0x645BA0BC, dest=, callParams={called=5555,called_oct3=0x81,
calling=6666,calling_oct3=0x0, calling_oct3a= 0x0, calling_xlated=false,
subscriber_type_str=Unknown, fdest=1, voice_peer_tag=1},mode=0x0,
appl_call_id=)
*Mar 5 00:13:05.842: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
*Mar 5 00:13:05.842: ccIFCallSetupRequestPrivate:
src route label tgt route label tg_label_flag 0x0

*Mar 5 00:13:05.842: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
vdbPtr type = 13
*Mar 5 00:13:05.846: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
*Mar 5 00:13:05.846: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
(vdbPtr=0x645BA0BC, dest=, callParams={called=5555, called_oct3 0x81,
calling=6666,calling_oct3 0x0, calling_oct3a 0x0, calling_xlated=false,
fdest=1, voice_peer_tag=1}, mode=0x0, xltrc=-5)
*Mar 5 00:13:05.846: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
*Mar 5 00:13:05.846: //13/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
not incoming entry
*Mar 5 00:13:05.846: //13/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
entry's incoming FALSE.
*Mar 5 00:13:05.846: //13/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry:
is_incoming is FALSE
*Mar 5 00:13:05.846: //-1/xxxxxxxxxxxx/CCAPI/cc_set_voice_port_value:
*Mar 5 00:13:05.846: callParams->spi_info is NULL
*Mar 5 00:13:05.846: //13/xxxxxxxxxxxx/CCAPI/ccCallSetContext:
(callID=0xD, context=0x63CBBBB4)
*Mar 5 00:13:05.846: //12/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag:
(callID=0xC, dialpeer_tag=1)
*Mar 5 00:13:05.846: //12/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag:
(callID=0xC, dialpeer_tag=1)
*Mar 5 00:13:05.850: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume:
not the VoIP or MMoIP
*Mar 5 00:13:05.950: //13/xxxxxxxxxxxx/CCAPI/cc_api_call_proceeding:
(vdbPtr=0x645BA0BC, callID=0xD, prog_ind=0x0)

*Mar 5 00:13:05.950: //13/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag:
(callID=0xD, dialpeer_tag=2)
*Mar 5 00:13:05.950: //12/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag:
(callID=0xC, dialpeer_tag=1)
*Mar 5 00:13:05.954: //13/xxxxxxxxxxxx/CCAPI/cc_api_call_cut_progress:
(vdbPtr=0x645BA0BC, callID=0xD, prog_ind=0x8, sig_ind=0x2, cause=0x0)
*Mar 5 00:13:05.954: //12/xxxxxxxxxxxx/CCAPI/ccCallCutProgress:
(callID=0xC, prog_ind=0x8, sig_ind=0x2, cause=0x0)
*Mar 5 00:13:05.954: //13/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag:
(callID=0xD, dialpeer_tag=2)
*Mar 5 00:13:05.954: //12/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag:
(callID=0xC, dialpeer_tag=1)
*Mar 5 00:13:05.954: //12/xxxxxxxxxxxx/CCAPI/ccGenerateToneInfo:
(callID=0xC tone=0)

!--- This debug output indicates that Call Control
!--- connects the two calls:

*Mar 5 00:13:05.954: //12/xxxxxxxxxxxx/CCAPI/ccConferenceCreate:
(confID=0x63CE #6154, callID1=0xC, callID2=0xD, tag=0x0) #
*Mar 5 00:13:05.958: //12/xxxxxxxxxxxx/CCAPI/ccConferenceCreate:
(pConf=0x6437E778)
*Mar 5 00:13:05.958: //12/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
(confID=0x6, srcIF=0x645BA0BC, srcCallID=0xC, dstCallID=0xD, disposition=0,
tag=0x0)
*Mar 5 00:13:05.958: //13/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
(confID=0x6, srcIF=0x645BA0BC, srcCallID=0xD, dstCallID=0xC, disposition=0,
tag=0x0)
*Mar 5 00:13:05.958: //-1/xxxxxxxxxxxx/CCAPI/cc_process_notify_bridge_done:
(event=0x646B02A8)
*Mar 5 00:13:09.626: //13/xxxxxxxxxxxx/CCAPI/cc_api_call_connected:
(vdbPtr=0x645BA0BC, callID=0xD), prog_ind = 0, cData->bitmask=0x0
*Mar 5 00:13:09.630: //13/A9AD583D800B/CCAPI/cc_api_call_connected:
setting callEntry->connected to TRUE

*Mar 5 00:13:09.630: //12/xxxxxxxxxxxx/CCAPI/ccCallConnect:
(callID=0xC), prog_ind=0, cData->bitmask=0x0
*Mar 5 00:13:09.630: //12/A9AD583D800B/CCAPI/ccCallConnect:
setting callEntry->connected to TRUE

*Mar 5 00:13:09.630: //13/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag:
(callID=0xD, dialpeer_tag=0)
*Mar 5 00:13:09.630: //12/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag:
(callID=0xC, dialpeer_tag=0)
*Mar 5 00:13:09.630: //13/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag:
(callID=0xD, dialpeer_tag=2)
*Mar 5 00:13:09.630: //12/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag:
(callID=0xC, dialpeer_tag=1)
*Mar 5 00:13:09.630: //12/xxxxxxxxxxxx/CCAPI/ccCallFeature:
(callID=0xC, feature.type=24)
*Mar 5 00:13:09.634: //13/xxxxxxxxxxxx/CCAPI/ccCallFeature:
(callID=0xD, feature.type=24)

!--- This debug output indicates that Call Control
!--- receives the disconnect message:

*Mar 5 00:13:16.614: //13/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnected:
(vdbPtr= #0x645BA0BC, callID=0xD, cause=0x10, rawmsg=0x0) #
*Mar 5 00:13:16.614: //-1/xxxxxxxxxxxx/CCAPI/ccConferenceDestroy:
(confID=0x6,tag=0x0)
*Mar 5 00:13:16.614: //12/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done:
(confID=0x6, srcIF=0x645BA0BC, srcCallID=0xC, dstCallID=0xD, disposition=0
tag=0x0)
*Mar 5 00:13:16.614: //13/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done:
(confID=0x6, srcIF=0x645BA0BC, srcCallID=0xD, dstCallID=0xC, disposition=0
tag=0x0)
*Mar 5 00:13:16.618: //12/xxxxxxxxxxxx/CCAPI/ccTDUtilGetDataByValue:
CallID[12], tagID[31], instID[-1]
*Mar 5 00:13:16.618: //12/A9AD583D800B/CCAPI/
ccTDPvtProfileTableObjectAccessManager:
Access Failed; profileTable not set [callID-0xC]
*Mar 5 00:13:16.618: //12/xxxxxxxxxxxx/CCAPI/ccTDUtilGetDataByValue:
No tdObject found in profileTable for tagID[31] of callID[12]
*Mar 5 00:13:16.618: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilSetDataInstance:
Setting data for callID[12], tagID[31], instID[-1], dataSize[4]
*Mar 5 00:13:16.618: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructDataObject:
TD Data Object Constructed 0x6437F260<<r-1,t-31,l-4,d-0x6437F280,m-8,
u-22035,g-FACE0FFF>>

*Mar 5 00:13:16.618: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject:
TD Queuable Instance Constructed 0x63CE672C[0x0,t-31,o-0x6437F260
<<r-1,t-31,l-4,d-0x6437F280,m-8,u-22035,g-FACE0FFF>>]
*Mar 5 00:13:16.618: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructHashProfileTab:
TD ProfileTable Constructed [profileTable-0x63CF7B54]
*Mar 5 00:13:16.618: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtProfileTableBuildManager:
profileTable[0x63CF7B54], numBuckets[11], numEntries[1]
*Mar 5 00:13:16.618: Bucket { 0 } ---->0x63CE672C[0x0,t-31,o-0x6437F260
<<r-1,t-31,l-4,d-0x6437F280,m-8,u-22035,g-FACE0FFF>>]
*Mar 5 00:13:16.622:
*Mar 5 00:13:16.622: //12/xxxxxxxxxxxx/CCAPI/ccCallDisconnect:
(callID=0xC, cause=0x10 tag=0x0)
*Mar 5 00:13:16.622: //12/A9AD583D800B/CCAPI/ccCallDisconnect:
calling accounting start for callID=12 leg_type=1
*Mar 5 00:13:16.622: //12/A9AD583D800B/CCAPI/ccCallDisconnect:
existing_cause = 0x0, new_cause = 0x10
*Mar 5 00:13:16.622: //12/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info:
(callID=0xC)
*Mar 5 00:13:16.622: //12/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info:
no transferNumber (callID=0xC)
*Mar 5 00:13:16.622: //13/xxxxxxxxxxxx/CCAPI/ccTDUtilGetDataByValue:
CallID[13], tagID[31], instID[-1]
*Mar 5 00:13:16.622: //13/A9AD583D800B/CCAPI/
ccTDPvtProfileTableObjectAccessManager:
Access Failed; profileTable not set [callID-0xD]
*Mar 5 00:13:16.622: //13/xxxxxxxxxxxx/CCAPI/ccTDUtilGetDataByValue:
No tdObject found in profileTable for tagID[31] of callID[13]
*Mar 5 00:13:16.622: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilSetDataInstance:
Setting data for callID[13], tagID[31], instID[-1], dataSize[4]
*Mar 5 00:13:16.622: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructDataObject:
TD Data Object Constructed 0x63CF7BF0<<r-1,t-31,l-4,d-0x63CF7C10,m-8,
u-22035,g-FACE0FFF>>

*Mar 5 00:13:16.622: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject:
TD Queuable Instance Constructed 0x63CF7C44[0x0,t-31,o-0x63CF7BF0
<<r-1,t-31,l-4,d-0x63CF7C10,m-8,u-22035,g-FACE0FFF>>]
*Mar 5 00:13:16.626: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructHashProfileTab:
TD ProfileTable Constructed [profileTable-0x63CF7C88]
*Mar 5 00:13:16.626: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtProfileTableBuildManager:
profileTable[0x63CF7C88], numBuckets[11], numEntries[1]
*Mar 5 00:13:16.626: Bucket { 0 } ---->0x63CF7C44[0x0,t-31,o-0x63CF7BF0
<<r-1,t-31,l-4,d-0x63CF7C10,m-8,u-22035,g-FACE0FFF>>]
*Mar 5 00:13:16.626:
*Mar 5 00:13:16.626: //13/xxxxxxxxxxxx/CCAPI/ccCallDisconnect:
(callID=0xD, cause=0x10 tag=0x0)
*Mar 5 00:13:16.626: //13/A9AD583D800B/CCAPI/ccCallDisconnect:
calling accounting start for callID=13 leg_type=0
*Mar 5 00:13:16.626: //13/A9AD583D800B/CCAPI/ccCallDisconnect:
existing_cause = 0x10, new_cause = 0x10
*Mar 5 00:13:16.626: //13/A9AD583D800B/CCAPI/ccCallDisconnect:
using the existing_cause 0x10
*Mar 5 00:13:16.626: //13/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info:
(callID=0xD)
*Mar 5 00:13:16.626: //13/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info:
no transferNumber (callID=0xD)
*Mar 5 00:13:16.630: //13/xxxxxxxxxxxx/CCAPI/ccCallGetVoipFlag:
ccCallGetVoipFlag: callID=0xD, mask=1
*Mar 5 00:13:16.630: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume:
not the VoIP or MMoIP
*Mar 5 00:13:16.630: //13/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnect_done:
(vdbPtr=0x645BA0BC, callID=0xD, disp=0, tag=0x0)

!--- Output suppressed.

Troubleshoot

These commands can be issued on any of the routers, to troubleshoot the VoFR network:

The output from the Cisco 3640 that is configured as a Tandem switch shows two VoFR dial-peers:

3640# show dial-peer voice summary

dial-peer hunt 0
AD PRE PASS
TAG TYPE MIN OPER PREFIX DEST-PATTERN FER  THRU      SESS-TARGET PORT
1   vofr up  up   5555   0            syst Serial3/0 100
2   vofr up  up   6666   0            syst Serial3/0 101

The show frame-relay vofr command shows this output:

3640# show frame-relay vofr

interface vofr-type dlci cid cid-type
Serial3/0.1 VoFR cisco 101 4 data
Serial3/0.1 VoFR cisco 101 5 voice call-control
Serial3/0.2 VoFR cisco 100 4 data
Serial3/0.2 VoFR cisco 100 5 voice call-control

NetPro Discussion Forums - Featured Conversations

Networking Professionals Connection is a forum for networking professionals to share questions, suggestions, and information about networking solutions, products, and technologies. The featured links are some of the most recent conversations available in this technology.
NetPro Discussion Forums - Featured Conversations for Voice
Service Providers: Voice over IP
Voice & Video: Voice over IP
Voice & Video: IP Telephony
Voice & Video: IP Phone Services for End Users
Voice & Video: Unified Communications
Voice & Video: IP Phone Services for Developers
Voice & Video: General

Related Information

Updated: Feb 02, 2006Document ID: 46271