8 Jun
2007
8 Jun
'07
8:43 p.m.
A solution to consider is to do first match rather than longest match
and make it explicitly incumbent upon the person entering data into LCR
tables to put things in the right order (by adding a sort column). This
is analogous to Cisco access list entires for example. Basically you
need to extend the openserctl UI by just adding another column....
/a
Ovidiu Sas wrote:
Hi Juha,
I know that you were referring to Alan's setup. I was just pointing
out that regex has this issue in general.
Let's consider the following example: a call to a 1800 number.
The destination is 18001231234 and in the lcr table we have the
following two prefixes:
1. ^18[01234567]
2. ^18[0-2]01
The second prefix is a better match for the 1800 number, but it has a
shorter length.
-ovi
On 6/8/07, Juha Heinanen <jh(a)tutpro.com> wrote:
> Ovidiu Sas writes:
>
> > This would be an issue for prefix regex matching.
>
> i was referring to alan's current setup.
>
> > How we determine the best match, since checking the prefix length
> > doesn't make sense anymore?
>
> it would still need to be on the longest match of any regexp and may get
> tricky.
>
> -- juha
>