[Devel] LCR change?

[Andreas Granig]

Hi,

Just a guess: change from_uri from '%' to '^.*$', because in caching 
mode, it uses regex instead of db-wildcards (and since there's no 
non-caching mode anymore, it might be worth a try).

Andreas

Helge Waastad wrote:
> Hi,
> yes I've seen that you'll have to reload after adding new entries to
> database (openserctl lcr reload).
> However,
> looking up next_gw for 47xxxxxx from any number in the following table
> fails (and it really worked before....)
> 
> LCR Routes:
> 
> | id | prefix | from_uri | grp_id | priority |
> |  1 | 47     | %        |      1 |        1 | 
> 
> LCR Gateways:
> 
> | gw_name | ip | port | uri_scheme | transport | grp_id | strip | prefix
> | cisco   | (yyyyyyy) (x.x.x.x)  | 5060 | 1 | 1 | 1 | 2 |  |
> 
> br hw
> 
> 
> On tir, 2007-01-30 at 12:07 +0100, Andreas Granig wrote:
>> Helge Waastad wrote:
>>> Hi,
>>> has there been any major changes to the lcr module these last couple of
>>> days?
>>>
>>> The last cvs update breaks my prefix lookups (next_gw() returns no hit).
>>> (worked last week :-) )
>> DB-only mode has been abandoned, as far as I have seen...
>>
>> Cheers,
>> Andreas