CUCM Dialled Number Analyser for Digit by Digit Analysis?

Question

Hi,
I'm wondering if anyone can help.
I work in a diagnostic team that often has to solve issues with problems on dial plans and customers not being able to call particular numbers. We often use Dialled Number Analyser to help us with this, but this only helps when the number is dialled en bloc. Often, a customer will say they try to dial a number and it will stop at a specific point, indicating there's an overlapping pattern somewhere. This can be very difficult to find. We use route plan report to help us but often the offending pattern will have wild cards in it and therefore merely searching for the number or the first few digits of the number will not help.
Is there another Cisco tool that will show the matches that Call Manager is making as each digit is dialled? Dialled number analyser does NOT help with this. It can be very time consuming trying to locate a route pattern otherwise (because there may be several partitions to look through and various patterns with wildcards in them).
Many thanks,
Neil

Answer 1

You should be able to pull the CCM SDI traces and see the digit analysis which will show you the pattern matched. You will need to know the calling DN and time of the call to find this.
Here's an example that I pulled from a CUCM 8.5(1) system. Older versions may be more/less information and the formatting may change slightly. The DialingPartition and DialingPattern lines are the actual route pattern matched in the database. Note that I replaced the real calling DID with 16085550100 here for privacy reasons.
16:28:14.410 |Digit analysis: analysis results|5,100,50,1.934924^10.245.58.160^SEP00270DBD4BA916:28:14.410 ||PretransformCallingPartyNumber=[phone]|CallingPartyNumber=[phone]|DialingPartition=Sec1_Route_PT|DialingPattern=\+1XXXXXXXXXX|FullyQualifiedCalledPartyNumber=[phone]|DialingPatternRegularExpression=(+1[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9])|DialingWhere=|PatternType=Enterprise|PotentialMatches=NoPotentialMatchesExist|DialingSdlProcessId=(0,0,0)|PretransformDigitString=[phone]|PretransformTagsList=SUBSCRIBER|PretransformPositionalMatchList=[phone]|CollectedDigits=[phone]|UnconsumedDigits=|TagsList=SUBSCRIBER|PositionalMatchList=[phone]|VoiceMailbox=|VoiceMailCallingSearchSpace=|VoiceMailPilotNumber=|RouteBlockFlag=RouteThisPattern|RouteBlockCause=0|AlertingName=|UnicodeDisplayName=|DisplayNameLocale=1|OverlapSendingFlagEnabled=0|WithTags=|WithValues=|CallingPartyNumberPi=NotSelected|ConnectedPartyNumberPi=NotSelected|CallingPartyNamePi=NotSelected|ConnectedPartyNamePi=NotSelected|CallManagerDeviceType=NoDeviceType|PatternPrecedenceLevel=Routine|CallableEndPointName=[67bee3e6-a58e-13dc-88c8-731e76915835]|PatternNodeId=[ffe93d92-a48a-5b00-c450-2b0a9097b6e2]|AARNeighborhood=[]|AARDestinationMask=[]|AARKeepCallHistory=true|AARVoiceMailEnabled=false|NetworkLocation=OffNet|Calling Party Number Type=Cisco Unified CallManager|Calling Party Numbering Plan=Cisco Unified CallManager|Called Party Number Type=Cisco Unified CallManager|Called Party Numbering Plan=Cisco Unified CallManager|ProvideOutsideDialtone=true|AllowDeviceOverride=false|AlternateMatches= Information Not Available|TranslationPatternDetails= Information Not Available|ResourcePriorityNamespace=|PatternRouteClass=RouteClassDefault|5,100,50,1.934924^10.245.58.160^SEP00270DBD4BA9