<div dir="ltr">Do you correctly set db_mode for usrloc?<div><br></div><div><div class="" style="color:rgb(0,0,0);font-family:Helvetica,Arial;font-size:medium"><h3 class="">1.3.20. <code class="">db_mode</code> (integer)</h3>
</div><p style="font-family:Helvetica,Arial;font-size:12px;text-align:justify;color:rgb(0,0,0)">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:</p>
<div class="" style="color:rgb(0,0,0);font-family:Helvetica,Arial;font-size:medium"><ul type="disc"><li><p style="font-size:12px;text-align:justify">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.</p>
</li><li><p style="font-size:12px;text-align:justify">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.</p>
</li><li><p style="font-size:12px;text-align:justify">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.</p>
</li><li><p style="font-size:12px;text-align:justify">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.</p>
</li></ul></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/6/27 Nandini madhu <span dir="ltr"><<a href="mailto:sermj2012@gmail.com" target="_blank">sermj2012@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Dear all.<br><br></div> i have installed opensips server and open-sips control panel on my pc successfully.<br>
</div> In user management ,i can see the clients listed,but when the clients<br>
</div>are registered,when we click on line users,its showing no data found.<br></div>In CDRviewer also its showing no data.<br><br></div>please help me,<br></div>Thanks in advance</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>