Juha, Ovidiu:
Does the LCR implementation in 1.2 search the lcr_routes table in order listed? If so, then we can live without regexps for prefixes. Otherwise we have ambiguity in our dialplan. For instance, we have entries like:
3_____ (in regexp this would be 3[0-9]{4}) 311
If we change this in the lcr_route table to:
311 ... 3 ...
Then we'd be OK, but if the query randomly comes back in the other order which is a function of the SQL select and underlying table structure unless there's an order by some field which is not explicitly shown as being a sequence number we are screwed.
/a
Ovidiu Sas wrote:
Hi Juha,
I will see if I can slip it in for 1.3. Just ping me if you hear nothing from me in the next ... let's say ... two months.
-ovi
On 6/7/07, Juha Heinanen jh@tutpro.com wrote:
Ovidiu Sas writes:
Adding regex support for prefix shouldn't be very hard. Unfortunately, right now I'm busy with some other stuff, but maybe latter on I can work on it.
ovidiu,
it would be nice if you had time to do it. the code is getting quite long and complex already so maintainability might start getting an issue though.
-- juha
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users