[SR-Users] Question about registrar behavior

[Володимир Іванець]

Hello!

I've just tested this on Kamailio v. 5.3.0-dev6 with *modparam("usrloc",
"db_mode", 0)* setting. save() return code was 1 too. I'm also interested
if this behavior is by design.

Thanks.

ср, 26 черв. 2019 о 11:34 Lars Olsson <lars.olsson at optimobile.se> пише:

> Hi,
>
> I have found a behavior in the registrar module that I do have a question
> about. Is the current behavior correct and wanted?
>
> Using the save() method in the script I see the following:
>
>
>    - Processing a register request for a user gives return code 1 ( or 2 )
>    - Processing a unregister request (expires=0) for registered user
>    gives return code 3
>    - Processing a unregister request (expires=0) for a user which is NOT
>    registered gives return code 1. Why?
>
> What is the reason behind this?
> No database entry is added which is expected.
>
> Test performed on 5.1.4, using DB mode 3.
>
> For handling a late unregister request ( where registration has already
> expired) return code does not reflect the the action.
> I assume that manually checking $expires(max) is the option to go then if
> I want to detect the unregister request or?
>
> Cheers,
> Lars
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190626/b6ac1422/attachment.html>