Manuals / Cisco Systems / Communications / Cordless Telephone

Cisco Systems 30 VIP manual Cisco Systems, Inc

Models: 30 VIP

1 96

Download 96 pages 30.93 Kb

Page 76

Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)

16:05:33.484 CCMStationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOn tcpHandle=0x4fbbc30

In the following traces, the user is dialing the called number (2000) of the Cisco IP Phone, and the process of digit analysis is trying to match the number.

16:05:33.484 CCMDigit analysis: match(fqcn="", cn="1001", pss="", dd="")

16:05:33.484 CCMDigit analysis: potentialMatches=PotentialMatchesExist

16:05:35.921 CCMDigit analysis: match(fqcn="", cn="1001", pss="", dd="2")

16:05:35.921 CCMDigit analysis:potentialMatches=ExclusivelyOffnetPotentialMatchesExist 16:05:36.437 CCMDigit analysis: match(fqcn="", cn="1001", pss="", dd="20") 16:05:36.437 CCMDigit analysis:potentialMatches=ExclusivelyOffnetPotentialMatchesExist 16:05:36.656 CCMDigit analysis: match(fqcn="", cn="1001", pss="", dd="200") 16:05:36.656 CCMDigit analysis:potentialMatches=ExclusivelyOffnetPotentialMatchesExist 16:05:36.812 CCMDigit analysis: match(fqcn="", cn="1001", pss="", dd="2000")

The digit analysis has now been completed and the results are shown in the following traces. It is important to note that the “PotentialMatches=NoPotentialMatchesExist” reference below indicates that the Cisco CallManager is unable to match this directory number. Finally a reorder tone is sent to the calling party (1001), which is followed by an on-hook message.

16:05:36.812 CCMDigit analysis: analysis results 16:05:36.812 CCMPretransformCallingPartyNumber=1001 CallingPartyNumber=1001

DialingPattern=2XXX

DialingRoutePatternRegularExpression=(2XXX)

PotentialMatches=NoPotentialMatchesExist

CollectedDigits=2000

16:05:36.828 CCMStationD - stationOutputCallInfo CallingPartyName=1001, CallingParty=1001, CalledPartyName=, CalledParty=2000, tcpHandle=0x4fbbc30

16:05:36.828 CCMStationD - stationOutputStartTone: 37=ReorderTone tcpHandle=0x4fbbc30 16:05:37.953 CCMStationInit - InboundStim - OnHookMessageID tcpHandle=0x4fbbc30

© 2000 Cisco Systems, Inc.

76

Image 76

Cisco Systems 30 VIP manual Cisco Systems, Inc

Contents

SDI Trace Output Configuring Traces Reorder Tone Through Gateways Gateway Registration Problems Page Purpose Documentation Checklist Acronym/Term Cnf Law mu-law Channel Calling Search Space CCAPiCisco IOS Cluster Codec ChannelJitter Law mu-law Flow Full duplex 711 729 225 245 323 Half Duplex HookflashPartition Route Filter Route Group Route List Route Pattern 931Silence Suppression Voice Activation Detection Translation Pattern Voice Activation Detection Silence Suppression VoIPCisco CallManager Administration Details Microsoft Performance View ReportMicrosoft Event Viewer SDI Trace Configuring Traces SDL Trace Page SDLTraceTypeFlag Value Definition SDLTraceDataFlag ValueSniffer Trace Call Detail Records CDR and Call Management Records CMRSelect Service Service Parameters CDRs Problem Categories Voice QualityPage Packet Number Time absolute ms Time delta ms Button Help John Check Your Loads Phone Resets Dropped Calls Page Page Cisco CallManager Feature Issues Locations Conf Bridge Region1 Region2 MTP Resource Problems MTP Dial Plans Dialing DOES-NOT-EXIST Page Name DialPlanWizardG ClausePattern Partition Pattern Device Name Device Description UsageSlow Server Response Reorder Tone Through GatewaysGateway Registration Problems CFG Booting Dhcp for dynamic configuration Module.portTracyclose mod port tracystart mod port TaskID Cmd show dhcp Gmsg ***TFTP Error File Not Found Gatekeeper Problems Gmsg CCM#0 CPEvent = Loadid -- CPState = LoadResponseRegistration Rejects RRJ Sample Topology Cisco IP Phone Initialization ProcessPage Skinny Station Registration Process Station Reset Message Description Station RegisterStation IP Port AcknowledgePage Cisco CallManager Initialization Process Self-Starting Processes Cisco CallManager Registration Process Cisco CallManager KeepAlive Process Cisco CallManager Intra-Cluster Call Flow Traces Cisco Systems, Inc CCMStationD stationOutputStopTone tcpHandle=0x4fbbc30 Cisco Systems, Inc Call Flow Traces Page Cisco Systems, Inc Following debug messages show that the call is in progress Debug Messages and Show Commands on the Cisco IOS Gateway Gatekeeper Endpoint RegistrationCisco Systems, Inc Page Cisco IOS Gateway with T1/PRI Interface Cisco IOS Gateway with T1/CAS Interface Cisco Systems, Inc Inter-Cluster H.323 Communication Call Flow Traces Failed Call Flow Cisco Systems, Inc Writing Records Reading RecordsTable Schema Removing RecordsKnown Issues Fields in a Call Detail RecordDeciphering the Time Stamp Global Call Identifier Origination leg call identifierDate/time of call origination Originator’s node IDIsdn location value Calling party cause Of call terminationIP address for the originator’s media connection Port for the originator’s media connectionDestination span or port IP address to which the call was delivered unsigned integerIP port to which the call was delivered Called party’s partitionIP address for the destination outgoing media connection Codec type used by the destination on sending sideDate/time of connect Date/time of disconnect unsigned integerGlobal Call Identifier for this call Cisco CallManager node identifierCall Identifier Directory number used on this callInterarrival jitter during this connection Lost RTP packets during this connectionLatency experienced during this connection Normal Calls Cisco IP Phone-to-Cisco IP Phone Call Management Records Logged By Call Type Codec Types Compression / Payload types Codec Cause Codes DescriptionNumber changed Alarms Calling Cisco Technical Assistance Center TAC Index Debug messages and show commands Page Topology