[OpenSIPS-Devel] how to get user that login in opsnSIPS ?

[Yita Wu]

Hello Bogdan,

I try it.
I use 0920 account to login.
Could this command "opensipsctl ul show --brief" can handle how many user
login at the same time ?
It seems to show all login users.

######################################
[root at opensips1 ~]# opensipsctl ul show --brief
Domain:: location table=512 records=1
        AOR:: 0920
[root at opensips1 ~]#
######################################

※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※

Hello Anca Vamanu,

I saw the link.
If I set db_mode to 1, as the document description, "This is very slow"
means the opsnSIPS will become very slow ?
Does "very slow" mean ? Does It affect openSIPS performance ?

======================================
1.3.20. db_mode (integer)

   -

   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.

※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※※

Dear All,


May I ask another question ?
I want to create user account using MySQL store procedure.
I want to insert a record to Subscriber table to create a user account, is
this legal ? Will this action cause openSIPS crash(segment fault or memory
fault) ?
Is there any different between "insert subscriber table" and "opensipsctl
add 2000 yourpassword" ?




Thanks!
Best regards,
YITA.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/devel/attachments/20101008/fed547bd/attachment.htm