On 12.01.2023 17:26, Daren FERREIRA wrote:
If I well understood, if a client is registered with a 500 seconds
expiry, the server side is set to outgoing_expires, and, if the
register is not renewed by the client, opensips should de-register.
In my case, the de-registers that should be triggered are never triggered.
I found no parameters relative to this in mid_registrar module, but,
looking at the source code, it seems it depends on usrloc module.
On usrloc module, it seems that contact_refresh_timer is in charge of
treating events, like expires, so I tried to enable it, without success.
Even after client expiry + timer_interval, the client is not
de-registered on server side.
Is there anything I may have missed?
Hi Daren,
I notice you are using "mode == 2", which means De-REGISTERs will only
be generated when the AoR gets deleted. For example, if you have 2 SIP
UAs registering to the same AoR and you are trying to kill one of them
in an attempt to see a De-REGISTER being auto-generated downstream, that
will never happen! This is because the remaining Contact is enough to
maintain "liveness" of the AoR to the downstream registrar.
Let me know if this is the case - if not, we can continue digging.
Ideally, a SIP trace (.pcap or .txt) for the entire flow would be
helpful (you can email it to me personally, if privacy is an issue).
Best regards,
--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
