Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)
08:38:56.015 Cisco CallManagerStationInit - InboundStim - KeypadButtonMessageID kpButton: 0 tcpHandle=0x6b88028
08:38:56.015 Cisco CallManagerDigit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="50")
08:38:56.015 Cisco CallManagerDigit analysis: potentialMatches=PotentialMatchesExist
08:38:56.187 Cisco CallManagerStationInit - InboundStim - KeypadButtonMessageID kpButton: 0 tcpHandle=0x6b88028
08:38:56.187 Cisco CallManagerDigit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="500")
08:38:56.187 Cisco CallManagerDigit analysis: potentialMatches=PotentialMatchesExist
08:38:56.515 Cisco CallManagerStationInit - InboundStim - KeypadButtonMessageID kpButton: 3 tcpHandle=0x6b88028
08:38:56.515 Cisco CallManagerDigit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="5003") 08:38:56.515 Cisco CallManagerDigit analysis: analysis results 08:38:56.515 Cisco CallManagerPretransformCallingPartyNumber=5000
The key thing to note above is that "PotentialMatchesExist" is the result of Digit Analysis of the numbers that were dialed until the exact match is found and the call is routed accordingly.
Below is a trace when the number attempted to be dialed "1001" is not in the Calling Search Space of the device. Again, the key thing to note is the digit analysis routine had potential matches until only the first digit was dialed. The route pattern associated with the digit "1" is in a partition that is not in the device's calling search space, "RTP_NC_Hardwood;RTP_NC_Woodland;Local_RTP". Therefore the phone was sent Reorder Tone.
08:38:58.734 Cisco CallManagerStationInit - InboundStim - OffHookMessageID tcpHandle=0x6b88028 08:38:58.734 Cisco CallManagerStationD - stationOutputDisplayText tcpHandle=0x6b88028, Display= 5000
08:38:58.734 Cisco CallManagerStationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOn tcpHandle=0x6b88028
08:38:58.734 Cisco CallManagerStationD - stationOutputCallState tcpHandle=0x6b88028 08:38:58.734 Cisco CallManagerStationD - stationOutputDisplayPromptStatus tcpHandle=0x6b88028 08:38:58.734 Cisco CallManagerStationD - stationOutputSelectSoftKeys tcpHandle=0x6b88028 08:38:58.734 Cisco CallManagerStationD - stationOutputActivateCallPlane tcpHandle=0x6b88028 08:38:58.734 Cisco CallManagerDigit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="")
08:38:58.734 Cisco CallManagerDigit analysis: potentialMatches=PotentialMatchesExist
08:38:58.734 Cisco CallManagerStationD - stationOutputStartTone: 33=InsideDialTone tcpHandle=0x6b88028
08:38:59.703 Cisco CallManagerStationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x6b88028
08:38:59.703 Cisco CallManagerStationD - stationOutputStopTone tcpHandle=0x6b88028 08:38:59.703 Cisco CallManagerStationD - stationOutputSelectSoftKeys tcpHandle=0x6b88028 08:38:59.703 Cisco CallManagerDigit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="1")
08:38:59.703 Cisco CallManagerDigit analysis: potentialMatches=NoPotentialMatchesExist
08:38:59.703 Cisco CallManagerStationD - stationOutputStartTone: 37=ReorderTone tcpHandle=0x6b88028
Route partitions work by associating a partition name with every directory number in the system. The directory number can be called only if the calling device contains the partition within a list
© 2000 Cisco Systems, Inc. | 39 |
