[cisco-voip] Route pattern Issue on Closest Match

[Kin Wai]

Thanks everyone, learned something new today. Will go read more on dial
pattern again.

-----Original Message-----
From: matthn at gmail.com [mailto:matthn at gmail.com] On Behalf Of Nick Matthews
Sent: Saturday, October 31, 2009 9:15 AM
To: Fuermann, Jason
Cc: Kin Wai; Ryan Ratliff; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Route pattern Issue on Closest Match

I think the troubleshooting voip book explains that the longest match
algorithm with the ! operator does the longest match calculation after
it fills the pattern to be the exact length.

ex:

dialing 912345
with these route patterns:
9.!
9[0-5]XXXX
compares
9.XXXXX
9[0-5]XXXX


-nick

On Fri, Oct 30, 2009 at 3:13 PM, Fuermann, Jason <JBF005 at shsu.edu> wrote:
> I think 9.01X! is catching because you are matching 3 digits and [689]
isn’t
> because you are only matching 1. Are you using enbloc dialing, or dialing
> from tone?
>
>
>
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Kin Wai
> Sent: Friday, October 30, 2009 10:39 AM
> To: 'Ryan Ratliff'
> Cc: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Route pattern Issue on Closest Match
>
>
>
> Hi Ryan,
>
> Thanks for the explanation.
>
>
>
> Originally, 9.010! is actually in a partition known as P_International
while
>  [689]XXXXXXX is in a partition call P_local
>
>
>
> The CSS I’m using is as follows
>
> 1)      P_Internal
>
> 2)      P_Local
>
> 3)      P_International
>
>
>
> However, it seems like 9.010! route pattern always takes the priority.
>
> I always think that it will search partition by partition too, now It’s
> bothering me.
>
>
>
> (I have attached a screenshot together, not sure whether it’s permitted or
> not in the newsgroup.)
>
>
>
> Regards,
>
> Kin Wai
>
>
>
>
>
> From: Ryan Ratliff [mailto:rratliff at cisco.com]
> Sent: Friday, October 30, 2009 10:54 PM
> To: Kin Wai
> Cc: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Route pattern Issue on Closest Match
>
>
>
> It should be the most specific match only if the two patterns are in the
> same partition.  If they are in different partitions I believe it takes
the
> higher partition in the CSS even if it is less specific.
>
>
>
> In your case however the 9.010! is more specific because it has fewer
> wildcards, ie it is matching 4 specific digits vs only 1 in [3689]XXXXXXX.
>
>
>
> -Ryan
>
>
>
> On Oct 30, 2009, at 10:43 AM, Kin Wai wrote:
>
>
>
> I have 2 route patterns in the same partition,
>
> 9.010!
>
> or
>
> [3689]XXXXXXX
>
>
>
>
>
> Which one is closest match above?
>
> If I key in 90101314
>
>
>
> I keep getting the result of 9.010! , just wondering do I hit into some
bug
> or I had the wrong concept.
>
>
>
> Cheers,
> Kin Wai
>
>
>
>
>
> _______________________________________________
> 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
>
>