10-06-2021 02:02 PM - edited 10-06-2021 02:03 PM
Can someone explain what is the use of * asterisk wild card in cucm ?
Let's say there is a translation pattern 9.123456789 and adding prefix ++001006.There is a route pattern **0061.! .If I run the DNA and dial 9123456789 , then I can see it's matching route pattern **0061.!
I need to understand why it's matching this route pattern.
10-06-2021 02:30 PM
10-06-2021 11:13 PM
I have gone through this doc but did not understand how it works.
The asterisk (*) character can provide an extra digit for special dialed numbers. Can you please explain with an example if possible ?
10-07-2021 01:30 AM - edited 10-07-2021 06:57 AM
Plus (+) is an example of a special dialed digit. I think that * and # would be other examples, likely there could be some more.
Apart from this * isn't actually a wild card character in CM, it is a dial-able character.
10-07-2021 05:56 AM
I think you'll need to take a deeper look into the Dialed Number Analyzer and see how the digits are manipulated and how the matches are made in CUCM. Without more going on, adding prefix ++001006 cannot result in a match to **0061.! in CUCM.
The reason is that the * character is not a wildcard in CUCM. It is an additional digit that can be dialed along with 0-9 and + and #. The route pattern **0061.! would require that the digits dialed (or translated to) actually start with **0061 and not other patterns. I tested this in my lab to make sure.
Can you post the entire output of the DNA, including the Called Party Transformations at each step? That will tell us more about what is going on in the background.
Maren
10-07-2021 07:15 AM - edited 10-07-2021 07:35 AM
Here is the DNA:-
Cisco Unified Communications Manager Dialed Number Analyzer Results
o Results Summary
• Calling Party Information
o Calling Party = +19891234567
o Partition = test-DirNum-PT
o Device CSS = test-Emer-CSS
o Line CSS = test-Enhanced-CSS
o AAR Group Name =
o AAR CSS =
• Dialed Digits = 99898399999
• Match Result = RouteThisPattern
• Matched Pattern Information
o Pattern = **0061.!
o Partition = test-LBRteSel-PT
o Time Schedule = Cu1-AllDay-TSchd
• Called Party Number = +9898399999
• Time Zone = America/New_York
• End Device = Cu1-testLocal-RL
• Call Classification = OffNet
• InterDigit Timeout = NO
• Device Override = Disabled
• Outside Dial Tone = NO
o Call Flow
• TranslationPattern :Pattern= 9.989[2-9]XXXXXX
o Partition = test-Local-PT
o Positional Match List = 9898399999
o Calling Party Number = 24396892
o PreTransform Calling Party Number = 24396892
o PreTransform Called Party Number = 9898399999
o Calling Party Transformations
• External Phone Number Mask = NO
• Calling Party Mask =
• Prefix =
• CallingLineId Presentation = Default
• CallingName Presentation = Default
• Calling Party Number = 24396892
o ConnectedParty Transformations
• ConnectedLineId Presentation = Default
• ConnectedName Presentation = Default
o Called Party Transformations
• Called Party Mask =
• Discard Digits Instruction = PreDot
• Prefix = ++010061
• Called Number = ++0100619898399999
• Route Pattern :Pattern= **0061.!
o Positional Match List = 9898399999
o DialPlan =
o Route Filter
• Filter Name =
• Filter Clause =
o Require Forced Authorization Code = No
o Authorization Level = 0
o Require Client Matter Code = No
o Call Classification =
o PreTransform Calling Party Number = +19891234567
o PreTransform Called Party Number = **00619898399999
o Calling Party Transformations
• External Phone Number Mask = YES
• Calling Party Mask =
• Prefix =
• CallingLineId Presentation = Default
• CallingName Presentation = Default
• Calling Party Number = +19891234567
o ConnectedParty Transformations
• ConnectedLineId Presentation = Default
• ConnectedName Presentation = Default
o Called Party Transformations
• Called Party Mask =
• Discard Digits Instruction = PreDot
• Prefix = +1
• Called Number = +19898987654
• Route List :Route List Name= test-RL
o RouteGroup :RouteGroup Name= RG-test
• PreTransform Calling Party Number = +19891234567
• PreTransform Called Party Number = **00619898399999
• Calling Party Transformations
o External Phone Number Mask = Default
o Calling Party Mask =
o Prefix =
o Calling Party Number = +19891234567
• Called Party Transformations
o Called Party Mask =
o Discard Digits Instructions =
o Prefix =
o Called Number = **00619898399999
• Device :Type= SIPTrunk
o Transformed Calling Party = +19891234567
o Transformed Called Party =
o End Device Name = test-Sub1-TRK
o PortNumber = 0
o Device Status = UnKnown
o AAR Group Name =
o AAR Calling Search Space =
o AAR Prefix Digits =
o Call Classification = OffNet
o Calling Party Selection = Originator
o CallingLineId Presentation = Default
o CallerID DN =
• Device :Type= SIPTrunk
o Transformed Calling Party = +19891234567
o Transformed Called Party =
o End Device Name = test-Sub2-TRK
o PortNumber = 0
o Device Status = UnKnown
o AAR Group Name =
o AAR Calling Search Space =
o AAR Prefix Digits =
o Call Classification = OffNet
o Calling Party Selection = Originator
o CallingLineId Presentation = Default
o CallerID DN =
o Alternate Matches
• Partition :Name= test-Defn-PT
o Pattern
• Pattern = \+.[^0]!
• Pattern Type = Translation
• TranslationPartition = []
• CallManager Device Type = AccessDevice
• PatternPrecedenceLevel = PlDefault
• PatternRouteClass = RouteClassDefault
• RouteNextHopByCgpn = false
• Partition :Name= test-Defn-PT
o Pattern
• Pattern = \+.[^0]!
• Pattern Type = Translation
• TranslationPartition = []
• CallManager Device Type = AccessDevice
• PatternPrecedenceLevel = PlDefault
• PatternRouteClass = RouteClassDefault
• RouteNextHopByCgpn = false
• Partition :Name= test-Defn-PT
o Pattern
• Pattern = \+.[^0]!
• Pattern Type = Translation
• TranslationPartition = []
• CallManager Device Type = AccessDevice
• PatternPrecedenceLevel = PlDefault
• PatternRouteClass = RouteClassDefault
• RouteNextHopByCgpn = false
• Partition :Name= test-Defn-PT
o Pattern
• Pattern = \+.[^0]!
• Pattern Type = Translation
• TranslationPartition = []
• CallManager Device Type = AccessDevice
• PatternPrecedenceLevel = PlDefault
• PatternRouteClass = RouteClassDefault
• RouteNextHopByCgpn = false
• Partition :Name= test-Defn-PT
o Pattern
• Pattern = \+.[^0]!
• Pattern Type = Translation
• TranslationPartition = []
• CallManager Device Type = AccessDevice
• PatternPrecedenceLevel = PlDefault
• PatternRouteClass = RouteClassDefault
• RouteNextHopByCgpn = false
• Partition :Name= test-Defn-PT
o Pattern
• Pattern = \+.[^0]!
• Pattern Type = Translation
• TranslationPartition = []
• CallManager Device Type = AccessDevice
• PatternPrecedenceLevel = PlDefault
• PatternRouteClass = RouteClassDefault
• RouteNextHopByCgpn = false
NOTE: The analysis results are purely based on configurations available in the Cisco Communications Manager database. For Gateway outbound calls, call details might differ depending on the Gateway's settings.
10-07-2021 08:00 AM
Holy smokes! There is something else going on here that is not revealed in the DNA. This happens sometimes. The reason I know this is because the output of the 9.989[2-9]XXXXXX translation pattern shows the calling party as 24396892 which makes that the originating calling party, and yet by the time the call reaches the Route Pattern the pre-transform (meaning originating) calling party has been changed to +19891234567 with nothing showing in the DNA on how that happened. (It would have to be a Translation Pattern, by the way, doing this.)
I do think the translation patterns shown at the bottom are part (or possibly all) of the problem, but I'd have to see the trace file to know what is exactly going on.
Would you be able to either post (or send in a PM) a trace file containing this call? I can dig in and see the exact mechanisms that CUCM is using to manipulate the digits and we can get this solved.
Maren
10-07-2021 08:34 AM
The number 24396892 is assigned to a phone and externa mask is set to +19891234567.
On route pattern 0061.! , the " Use Calling Party's External Phone Number Mask" checkbox is checked and that's why it is translating calling number from 24396892 to +19891234567. I will try to provide the CUCM logs file to understand why it's matching this route pattern.
10-07-2021 09:56 AM
The change in the calling party number is happening before the call hits the Route Pattern. The "Pre-Transform Calling Party" is the number as sent to the Route Pattern. The fact that this is already the EPNM means that a Translation Pattern (not shown in the DNA output) has that box checked. If the calling party were being altered by the Route Pattern, the "Pre-Transform Calling Party" would be one thing, and then the "Calling Party" under the Calling Party Transformations area would be the EPNM. I hope that all makes sense.
I look forward to seeing the trace file!
Maren
10-12-2021 01:02 AM
I won't be able to provide call manager logs because i need to ask user to make test calls for this number which is not possible and also do not have any test environment where I can test . I was randomly checking and came across this issue . I appreciate everybody's response on this and want to close this thread here.
10-09-2021 05:06 AM
If ** added in first on any TP and RP and DN it means that TP/RP/DN has been disable.
Check your line css and whatever TP you want do dial that TP partition should be added in your line css on upper priority.
Pls rate if its “Helpful”. If this answered your question pls click “Accept as solution”.
10-09-2021 06:57 AM
What do you mean by this “If ** added in first on any TP and RP and DN it means that TP/RP/DN has been disable.”? AFAIK putting ** at the beginning of anything would not mean that it’s disabled? Could you please elaborate on what you mean.
10-09-2021 07:23 AM
Ohh Sorry.
Means start with \**