Re: [OpenSIPS-Users] Db_mode=3(sql only) in USRLOC module in opensips_3.1

Hi Donat/Opensips Team, We have tested with "working_mode_preset" as *sql only* because db_mode is deprecated. And as far as opensips logs is concerned , I am attaching opensips logs as a text file with *log_level=4, *please check if you could find anything unusual. Will wait for your feedback.

Re: [OpenSIPS-Users] Db_mode=3(sql only) in USRLOC module in opensips_3.1

Good day Sasmita and Saurabh, that's a good question to ask and answer actually. As I was mentioning at the very beginning, did you try to look into the logs with the deep log_level? https://www.opensips.org/Documentation/Script-CoreParameters-3-1#toc37 This is highly appreciated when doing a debu

Re: [OpenSIPS-Users] Db_mode=3(sql only) in USRLOC module in opensips_3.1

Hi Donat, According to Saurabh , he is saying in " *db_mode=3 and sql-only mode* " that direct DB operation happens . When a user get registered that contact immediately get populated to the DB and when the user send un-registration the entry from the DB should be deleted at that time . *The delet

Re: [OpenSIPS-Users] Db_mode=3(sql only) in USRLOC module in opensips_3.1

Good day Saurabh, could you refer to the RFC and the particular row in that, that talks about a backend database and time in which the row should be deleted from that? I just wonder if I missed this somewhere. I haven't ever seen a specification for databases backend in RFCs related to the SIP prot

Re: [OpenSIPS-Users] Db_mode=3(sql only) in USRLOC module in opensips_3.1

Hi Donat/Opensips Team, Apologies for late response, but ideally the entry should be deleted after un-registration is sent otherwise it will violate the RFC rule. Also, this SQL Only Mode is perfectly working with opensips 2.2 and 3.0 versions with the same configuration. Could you guys try to rep

Re: [OpenSIPS-Users] Db_mode=3(sql only) in USRLOC module in opensips_3.1

I just want to follow up with the thing that, using the sql-only mode, expired location records might not be deleted right away. I just remembered all of the sudden, that the timer interval controls data clearing/updating when using sql-only mode. Then you might also want to play with your timer i

Re: [OpenSIPS-Users] Db_mode=3(sql only) in USRLOC module in opensips_3.1

Good morning Saurabh, that sounds a bit odd, as the sql only mode supposes that usrloc.so updates the backend sql right away. Do you have any warnings occurring in the OpenSIPS log? There might be a case for an inability of OpenSIPS to reach the sql server at the moment of de-registration. See if

[OpenSIPS-Users] Db_mode=3(sql only) in USRLOC module in opensips_3.1

Hi All, I am testing a usrloc module with db_mode=3(sql only) and a strange thing is happening, when we send an unregistration request the user entry is not deleting from the database . However the entry is deleted after expiry timer. loadmodule "usrloc.so" modparam("usrloc", "nat_bflag", "NAT")