[Users] Updating usrloc database

[Bogdan-Andrei Iancu]

Please note that db_mode=3 (DB_ONLY) has great impact on performance 
since all user location operations (add, update, remove, expire) will 
trigger DB queries...not to mention the NAT ping...
If you really do not need this mode, try to avoid it and use "openserctl 
ul" to add new entries into the cache.

regards,
bogdan


Daniel-Constantin Mierla wrote:

>
>
> On 06/16/06 15:28, Mike Williams wrote:
>
>> On Thursday 15 June 2006 03:23, Britton Payne wrote:
>>
>> I believe the usrloc module in the development version supports 
>> cacheless mode. This sounds like it would solve your problems.
>>   
>
> Just for sake of completion, you have to set db_mode=3 in usrloc 
> module. And indeed, you have to use development version - currently it 
> is in freeze (testing) state, to be release stable version 1.1.0 in 
> terms of days/weeks.
>
> Cheers,
> Daniel
>
>
>> ---Mike
>>
>>
>>  
>>
>>> Hello, all.  In our current configuration OpenSER is using a MySQL db
>>> for location information.  Registrations made to openser get pushed 
>>> into
>>> the db ok, but changes to the database directly (like additions) do not
>>> appear to make it to openser.  Is there a way to make changes to the
>>> database become visible to openser like a fifo command or should I be
>>> using db_mode=1?  We would like to be able to do this without 
>>> restarting
>>> openser and dropping calls in progress.
>>>
>>> Thank you,
>>> Britton
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at openser.org
>>> http://openser.org/cgi-bin/mailman/listinfo/users
>>>     
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/users
>>
>>   
>
>
> _______________________________________________
> Users mailing list
> Users at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>