<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Igor,<div class=""><br class=""></div><div class="">If the phone lost registration, it should also be deleted from mid_registrar. With nathelper, e.g. So next REGISTER should be forwarded, not consumed. But it would be really good solution to have feature like this <a href="https://github.com/OpenSIPS/opensips/issues/1769" class="">https://github.com/OpenSIPS/opensips/issues/1769</a></div><div class="">In the case of UDP, may be it make sense to use simple mirroring mode with nathelper pings.</div><div class=""><br class=""></div><div class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div class="">-----</div><div class="">Alexey Vasilyev</div><div class=""><a href="mailto:alexei.vasilyev@gmail.com" class="">alexei.vasilyev@gmail.com</a></div><div class=""><br class=""></div></span><br class="Apple-interchange-newline">

</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">27 Sep 2019, в 22:58, Igor Olhovskiy [via OpenSIPS (Open SIP Server)] <<a href="mailto:ml+s1449251n7616299h3@n2.nabble.com" class="">ml+s1449251n7616299h3@n2.nabble.com</a>> написал(а):</div><br class="Apple-interchange-newline"><div class="">

        <div dir="ltr" class=""><div class=""><div class="">Enpoint B also have 3600 expiry time. So, 1000 + 2600 = 3600.<br class=""></div><div class="">But you got the point.<br class=""></div><div class=""><br class="">Actually I faced more interesting issue a bit later, maybe actually it was the reason.<br class=""></div>Only 1 phone involved.<br class=""></div><div class="">Time 0       ->  Enpoint A -> mid_registrar -> upstream_registrar (expires 3600)</div><div class="">Time 1000  ->  Enpoint A -> mid_registrar (just consume registration)<br class=""></div><div class="">Time 3600 -> NOTHING. upstream_registrar expires.<br class=""></div><div class="">1000 sec GAP<br class=""></div><div class="">Time 4600 ->  Enpoint A -> mid_registrar -> upstream_registrar.<br class=""><br class=""></div><div class="">Yes, looks like non logic behaviour, but some of my Yealink endpoints sometimes just refreshes registration (maybe TCP network loss or so) in a middle of expires period and than - just wait for full expire time to re-register</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">пт, 27 сент. 2019 г. в 18:53, Liviu Chircu <<a href="x-msg://17/user/SendEmail.jtp?type=node&node=7616299&i=0" target="_top" rel="nofollow" link="external" class="">[hidden email]</a>>:<br class=""></div><blockquote style="border-left:2px solid #CCCCCC;padding:0 1em" class="gmail_quote">Hi, Igor!<br class="">
<br class="">
Correct me if I'm wrong, but doesn't endpoint B think it's registered<br class="">
for another 1000 seconds at step 4) in your example?<br class="">
<br class="">
Anyway, logically speaking, on step 2), the mid-registrar should forward<br class="">
the call to main reg, since there is no guarantee that any of the endpoints<br class="">
will send a binding refresh register within the next 2600 seconds.  For all<br class="">
it's worth, A could lose its connection and B could wait between<br class="">
2601 to 3599 before re-registering, which would temporarily cause <br class="">
registration<br class="">
state to be incorrectly lost on the backend layer.<br class="">
<br class="">
Let me set up a test for this scenario and I will come back to you with <br class="">
my findings.<br class="">
<br class="">
Regards,<br class="">
<br class="">
Liviu Chircu<br class="">
OpenSIPS Developer<br class="">
<a href="http://www.opensips-solutions.com/" rel="nofollow" target="_blank" link="external" class="">http://www.opensips-solutions.com</a><br class="">
<br class="">
On 27.09.2019 18:18, Igor Olhovskiy wrote:<br class="">
> but Enpoint B still thinks it's registered at least 2599 seconds.<br class="">
<br class="">
_______________________________________________<br class="">
Users mailing list<br class="">
<a href="x-msg://17/user/SendEmail.jtp?type=node&node=7616299&i=1" target="_top" rel="nofollow" link="external" class="">[hidden email]</a><br class="">
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="nofollow" target="_blank" link="external" class="">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br class="">
</blockquote></div><br clear="all" class=""><br class="">-- <br class=""><div dir="ltr" class="gmail_signature"><div dir="ltr" class="">Best regards,<div class="">Igor</div></div></div>
<br class="">_______________________________________________
<br class="">Users mailing list
<br class=""><a href="x-msg://17/user/SendEmail.jtp?type=node&node=7616299&i=2" target="_top" rel="nofollow" link="external" class="">[hidden email]</a>
<br class=""><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_top" rel="nofollow" link="external" class="">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br class="">

        
        
        
        <br class="">
        <br class="">
        <hr noshade="noshade" size="1" class="">
        <div style="color:#444; font: 12px tahoma,geneva,helvetica,arial,sans-serif;" class="">
                <div style="font-weight:bold" class="">If you reply to this email, your message will be added to the discussion below:</div>
                <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/mid-registrar-question-tp7616290p7616299.html" class="">http://opensips-open-sip-server.1449251.n2.nabble.com/mid-registrar-question-tp7616290p7616299.html</a>
        </div>
        <div style="color:#666; font: 11px tahoma,geneva,helvetica,arial,sans-serif;margin-top:.4em;line-height:1.5em" class="">
                To start a new topic under OpenSIPS - Users, email <a href="mailto:ml+s1449251n1449235h19@n2.nabble.com" class="">ml+s1449251n1449235h19@n2.nabble.com</a> <br class="">
                To unsubscribe from OpenSIPS - Users, <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1449235&code=YWxleGVpLnZhc2lseWV2QGdtYWlsLmNvbXwxNDQ5MjM1fC0xOTc3MDM4NDMy" class="">click here</a>.<br class="">
                <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml" rel="nofollow" style="font:9px serif" class="">NAML</a>
        </div></div></blockquote></div><br class=""></div></body></html>