[cisco-voip] CUCM pattern matching logic

[Mac GroupStudy]

I don't understand when you say that 2! equals 1000 possible matches and 20!
equals 100 possible matches. The "!" means variable length which should be
more than 1000 and 100 matches respectively and without actually counting
the possible number of matches.


On Mon, Apr 25, 2011 at 9:57 PM, Ryan Ratliff <rratliff at cisco.com> wrote:

> Likely a bug or typo and your 2XXX with urgent priority wasn't being
> matched at all.  Urgent Priority on a pattern will always route regardless
> of alternate matches (T302 will never kick in).
>
> -Ryan
>
> On Apr 25, 2011, at 12:38 AM, Cisco Voip wrote:
>
> Hi all.
>
>
> I am trying to understand call routing logic of cucm.
>
>
> I created 2 route patterns in cucm 7
>
>
> 2!
> 2XXX (with urgent priority)
>
>
> Now when i dialed 2001, i had to wait 15 seconds. The call wasnt routed as
> i expected. I opened up Troubleshooting cisco ip telephony book, and
> according to that, i must calculate the possible results each route pattern
> defines.
>
>
> 1) 2! for 2001 = 1000 combinations
> 2) 2XXX for 2001 = 1000 combinations.
>
>
> Since they were equal, i can understand why urgent priority didnt work (pls
> correct me here if what i understood is wrong !!)\
>
>
> Now i deleted the above and created 2 new patterns
>
>
> 1) 20!
> 2) 20XX (urgent priority)
>
>
> Now when i dialed 2001, my call went immediately. Why is this so ?? if i
> calculate the combinations
>
>
> 1) 20! for 2001 = 100 combinations
> 2) 20XX for 2001 = 100 combinations
>
>
> So why second route pattern was selected immediately ???
> _______________________________________________
> cisco-voip mailing list
>
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110427/d32e9248/attachment.html>