Hello Bogdan,<br><br>I try it. <br>I use 0920 account to login. <br>Could this command "opensipsctl ul show --brief" can handle how many user login at the same time ?<br>It seems to show all login users. <br><br>
######################################<br>[root@opensips1 ~]# opensipsctl ul show --brief<br>Domain:: location table=512 records=1<br> AOR:: 0920<br>[root@opensips1 ~]#<br>######################################<br>
<br>¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°<br><br>Hello Anca Vamanu,<br><br>I saw the link.<br>If I set db_mode to 1, as the document description, <span style="background-color: rgb(255, 255, 51);"> "This is very slow</span>" means the opsnSIPS will become very slow ?<br>
Does "very slow" mean ? Does It affect openSIPS performance
?<br><br>======================================<br><h3 class="title">1.3.20. <code class="varname">db_mode</code> (integer)</h3><div class="itemizedlist"><ul type="disc"><li><p>
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>
1 - Write-Through scheme. All changes to usrloc are immediately
reflected in database too.<span style="background-color: rgb(255, 255, 51);"> This is very slow</span>, 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>
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>
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>¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°¡°<br><br>Dear All,<br><br><br>May I ask another question ?<br>I want to create user account using MySQL store procedure. <br>I want to insert a record to Subscriber table to create a user account, is this <span id="result_box" class="short_text" lang="en"><span style="" title="">legal ?</span></span> Will this action cause openSIPS crash(segment fault or memory fault) ?<br>
Is there any different between "insert subscriber table" and "opensipsctl add 2000 yourpassword" ?<br><br><br><br><br>Thanks!<br>Best regards,<br>YITA.<br>