[OpenSIPS-Users] opensips control panel

[Nandini madhu]

thanks for your prompt response,

the db_mode set for usrloc is 2.

modparam("usrloc", "db_mode", 2)

but i could not find the online users


On Thu, Jun 27, 2013 at 3:39 PM, pavel at eremina.net <eremina.net at gmail.com>wrote:

> Do you correctly set db_mode for usrloc?
>
> 1.3.20. db_mode (integer)
>
> The usrloc module can utilize database for persistent contact storage. If
> you use database, your contacts will survive machine restarts or SW
> crashes. The disadvantage is that accessing database can be very time
> consuming. Therefore, usrloc module implements four database accessing
> modes:
>
>    -
>
>    0 - This disables database completely. Only memory will be used.
>    Contacts will not survive restart. Use this value if you need a really fast
>    usrloc and contact persistence is not necessary or is provided by other
>    means.
>    -
>
>    1 - Write-Through scheme. All changes to usrloc are immediately
>    reflected in database too. This is very slow, but very reliable. Use this
>    scheme if speed is not your priority but need to make sure that no
>    registered contacts will be lost during crash or reboot.
>    -
>
>    2 - Write-Back scheme. This is a combination of previous two schemes.
>    All changes are made to memory and database synchronization is done in the
>    timer. The timer deletes all expired contacts and flushes all modified or
>    new contacts to database. Use this scheme if you encounter high-load peaks
>    and want them to process as fast as possible. The mode will not help at all
>    if the load is high all the time. Also, latency of this mode is much lower
>    than latency of mode 1, but slightly higher than latency of mode 0.
>    -
>
>    3 - DB-Only scheme. No memory cache is kept, all operations being
>    directly performed with the database. The timer deletes all expired
>    contacts from database - cleans after clients that didn't un-register or
>    re-register. The mode is useful if you configure more servers sharing the
>    same DB without any replication at SIP level. The mode may be slower due
>    the high number of DB operation. For example NAT pinging is a killer since
>    during each ping cycle all nated contact are loaded from the DB; The lack
>    of memory caching also disable the statistics exports.
>
>
>
> 2013/6/27 Nandini madhu <sermj2012 at gmail.com>
>
>> Dear all.
>>
>>   i have installed opensips server and open-sips control panel on my pc
>> successfully.
>>   In user management ,i can see the clients listed,but when the clients
>> are registered,when we click on line users,its showing no data found.
>> In CDRviewer also its showing no data.
>>
>> please help me,
>> Thanks in advance
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130627/376a1491/attachment.htm>