[OpenSIPS-Users] mid_registar max-expires does not work as expected (3.0.0)
Peter Pulham
peter at thesimworks.net
Mon Aug 19 13:05:11 EDT 2019
Turned out to be a configuration issue. I missed this error log on startup:
ERROR:mid_registrar:mod_init: max_expires < default_expires! Increasing
max_expires to 3600...
So adding:
modparam("mid_registrar", "default_expires", 20)
to my configuration file got it working as expected.
On Sat, Aug 17, 2019 at 9:00 PM Peter Pulham <peter at thesimworks.net> wrote:
> Hi,
>
> I have the following configuration for mid_registrar :
>
> loadmodule "mid_registrar.so"
> modparam("mid_registrar", "tcp_persistent_flag", "TCP_PERSIST")
> modparam("mid_registrar", "mode", 2)
> modparam("mid_registrar", "received_avp", "$avp(received_nh)")
> modparam("mid_registrar", "max_expires", 20)
> modparam("mid_registrar", "outgoing_expires", 3600)
>
> When a register is received with an expires of say 1800, a register is
> sent to the switch with an expires of 3600 as expected in the
> outgoing_expires setting. However, when the OK is sent back to the client
> the expires remains 1800 and does not change to 20.
>
> Is this a misunderstanding of the configuration or a bug?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190819/a1338ae4/attachment.html>
More information about the Users
mailing list