[cisco-voip] Route pattern Issue on Closest Match

[Kin Wai]

Hi Ryan, 

Thanks again! Just ignore my previous mail. 

 

In my mind, I always thought that 9.010! have unlimited
possibilities(wildcards) while [3689] have limited possibilities . It
confused me for quite a while till you explained it. 

 

Regards,

Kin Wai

 

From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Friday, October 30, 2009 11:29 PM
To: Ryan Ratliff
Cc: Kin Wai; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Route pattern Issue on Closest Match

 

To re-phrase my previous email the more specific match is always taken,
regardless of order in the pss.  Only when they are both equal length
matches will partition order come into play.

 

-Ryan

 

On Oct 30, 2009, at 10:53 AM, Ryan Ratliff wrote:

 

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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091030/44bfa0b3/attachment.html>