<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Liviu,<div><br></div><div>Thank you for your reply.</div><div><br></div><div>I don’t expect an unregister from one device to trigger a de-register for the two, that would be illogic.</div><div>It would make sense only if the device is the last registered one. </div><div><br></div><div>In our case, captures would be useless. That would only show no de-REGISTER is sent by OpenSIPS.</div><div><br></div><div>Please, let me try to best describe the case and my understanding.</div><div><br></div><div>We are in mode==2.</div><div>You have several devices registering (2).</div><div>The devices register with an expire < 3600 (in our case, around 600).</div><div>Opensips registers with a default_expires (3600 by default) (that’s expected, that’s a way to throttle and reduce backend load).</div><div><br></div><div>The devices are disconnected from internet, so their registry is not renewed, and expires (from client side view).</div><div>OpenSIPS doesn’t send any de-register even if all endpoints registry have expired.</div><div><br></div><div>My understanding was opensips should do the cleaning, as mentioned on the documentation.</div><div><br></div><div><i>A common occurence is for some SIP User Agents to lose their network connection (especially when dealing with mobile devices), hence they do not properly de-register from the mid-registrar. In this case, in order to avoid stale registrations on the main registrar (which contains SIP contacts with greatly extended lifetimes!), the mid-registrar will appropriately generate De-REGISTER requests and remove these contacts from the main registrar's location service as soon as it considers them to have expired. </i></div><div><br></div><div>Have I misunderstood?</div><div>If not, what can explain the un-register to never been sent by OpenSIPS?</div><div><br></div><div><br></div><div>Thank you</div><div><br></div><div>Best regards</div><div><br></div><div><div><br><blockquote type="cite"><div>Le 17 janv. 2023 à 15:13, Liviu Chircu <liviu@opensips.org> a écrit :</div><br class="Apple-interchange-newline"><div><div>On 12.01.2023 17:26, Daren FERREIRA wrote:<br><blockquote type="cite">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.<br><br>In my case, the de-registers that should be triggered are never triggered.<br><br>I found no parameters relative to this in mid_registrar module, but, looking at the source code, it seems it depends on usrloc module.<br>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.<br>Even after client expiry + timer_interval, the client is not de-registered on server side.<br><br>Is there anything I may have missed?<br></blockquote><br>Hi Daren,<br><br>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.<br><br>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).<br><br>Best regards,<br><br>-- <br>Liviu Chircu<br>www.twitter.com/liviuchircu | www.opensips-solutions.com<br><br></div></div></blockquote></div><br></div></body></html>