# UCM Longest Match Routing question

Hello all,

I'm reading through the CIPT1 Cisco Book and have come across a statement that contradicts what Mark Snow stated in his CIPT1 Dian Plan video, I was hoping someone could clear up the concept so I have the most correct thought process of how this works.

Ok so if you have the CIPT1 8.0 book, the example is on page 241.

It states the dial string as 1311<timeout>

1[23]XX - Possible 100-digit matches

(Should this be 200 possible digit strings?)

13[0-4]X  - Possible 10-digit matches

(Should this be 50 possible digit strings?)

13! - Possible infinite matches

(However since only 4 digits were dialed, should this be 100 possible strings?)

With Marks' example in the video I was under the impression the correct digit string values are in the parenthesis above, however the books example states otherwise.

Any clarity or additional examples help, thank you!

## Comments

• Hi Bobfromfpl,

I would say the explanation from the video is most likely to give you the correct results. It appears the book takes into account only the unknowns.

Starting from the bottom, the pattern with the exclamation (13!) is definitely interpreted as infinite number of matches (of course till the system defined maximum digit length) but for the purpose of this example, it will match exactly 100 inputs.

Now for the other two patterns, let us assume that the same number 1311 is dialed but the available patterns are the following:

131X and 13[0-4]X.

If you go by the book, then we would conclude that these two patterns have 10 possible matches. However, this is not the case the 131X pattern clearly has less matches (or is more specific) than 13[0-4]X.

The easiest way to tell is of course to check the traces.

HTH

•

Hi,

Here is an explanation from Cisco website for the patterns from the book.

"If the user dials 1311, Cisco CallManager waits for the inter-digit timer to expire. Because of the 13! pattern, there is the potential that the user is not done entering numbers yet. Once the timer expires, there are three matches: 1[23]XX13[0-4]X, and 13!. Because 1[23]XX matches about 200 patterns, 13[0-4]X matches about 50 patterns, and 13! matches an infinite number of patterns, 13[0-4]X is selected."

Just to make it seem real, I went ahead and ran the Dialed Number Analyzer on the patterns from the book as you mentioned. I created 3 translation patterns (13!, 1[23]XX and 13[0-4]X), then I simulated with a dialed number of 1311 calling from ext. 1000.

See results below. Note that the order of matching is consistent with both the Book and the INE VoD results. But like I said the book counts from the first non-explicitly matched digit, thus causing the discrepancy in explanations.

Cisco Unified Communications Manager Dialed Number Analyzer Results

Results Summary

Calling Party Information

Calling Party = 1000

Partition =

Device CSS =

Line CSS = CSS_INTL-CALLS

AAR Group Name =

AAR CSS =

Dialed Digits = 1311

Match Result = BlockThisPattern

Matched Pattern Information

Pattern = 13[0-4]X

Partition = PT_Internal-DNs

Time Schedule =

Called Party Number = 1311

Time Zone = Greenwich Standard Time

Call Classification =

InterDigit Timeout = NO

Device Override = Disabled

Outside Dial Tone = NO

Call Flow

TranslationPattern :Pattern=

Positional Match List = 1311

Calling Party Number = 1000

PreTransform Calling Party Number =

PreTransform Called Party Number =

Calling Party Transformations

External Phone Number Mask = NO

Calling Party Mask =

Prefix =

CallingLineId Presentation =

CallingName Presentation =

Calling Party Number = 1000

ConnectedParty Transformations

ConnectedLineId Presentation =

ConnectedName Presentation =

Called Party Transformations

Called Party Mask =

Discard Digits Instruction =

Prefix =

Called Number =

Alternate Matches

Partition :Name= PT_Internal-DNs

Pattern

Pattern = 13!

Pattern Type = Translation

TranslationPartition = [a9b042be-f911-f21e-d76c-0b31c62f0a3c]

CallManager Device Type = AccessDevice

PatternPrecedenceLevel = ExecutiveOverride

Pattern

Pattern = 1[23]XX

Pattern Type = Translation

TranslationPartition = [a9b042be-f911-f21e-d76c-0b31c62f0a3c]

CallManager Device Type = AccessDevice

PatternPrecedenceLevel = ExecutiveOverride

HTH

• Thanks for the DNA output, that does help clarify the decision making between the book and the videos.  That is one of the main reasons I enjoy Mark's videos.. it seems like he literally touches up on alot of material and then attempts to show it in practice.  Just something one can't get from only a book!

Sign In or Register to comment.