[OpenSIPS-Users] mid_registrar question

[Alexey Vasilyev]

Hi Igor,

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 https://github.com/OpenSIPS/opensips/issues/1769 <https://github.com/OpenSIPS/opensips/issues/1769>
In the case of UDP, may be it make sense to use simple mirroring mode with nathelper pings.

-----
Alexey Vasilyev
alexei.vasilyev at gmail.com <mailto:alexei.vasilyev at gmail.com>



> 27 Sep 2019, в 22:58, Igor Olhovskiy [via OpenSIPS (Open SIP Server)] <ml+s1449251n7616299h3 at n2.nabble.com <mailto:ml+s1449251n7616299h3 at n2.nabble.com>> написал(а):
> 
> Enpoint B also have 3600 expiry time. So, 1000 + 2600 = 3600.
> But you got the point.
> 
> Actually I faced more interesting issue a bit later, maybe actually it was the reason.
> Only 1 phone involved.
> Time 0       ->  Enpoint A -> mid_registrar -> upstream_registrar (expires 3600)
> Time 1000 ->  Enpoint A -> mid_registrar (just consume registration)
> Time 3600 -> NOTHING. upstream_registrar expires.
> 1000 sec GAP
> Time 4600 -> Enpoint A -> mid_registrar -> upstream_registrar.
> 
> 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
> 
> пт, 27 сент. 2019 г. в 18:53, Liviu Chircu <[hidden email] <x-msg://17/user/SendEmail.jtp?type=node&node=7616299&i=0>>:
> Hi, Igor!
> 
> Correct me if I'm wrong, but doesn't endpoint B think it's registered
> for another 1000 seconds at step 4) in your example?
> 
> Anyway, logically speaking, on step 2), the mid-registrar should forward
> the call to main reg, since there is no guarantee that any of the endpoints
> will send a binding refresh register within the next 2600 seconds.  For all
> it's worth, A could lose its connection and B could wait between
> 2601 to 3599 before re-registering, which would temporarily cause 
> registration
> state to be incorrectly lost on the backend layer.
> 
> Let me set up a test for this scenario and I will come back to you with 
> my findings.
> 
> Regards,
> 
> Liviu Chircu
> OpenSIPS Developer
> http://www.opensips-solutions.com <http://www.opensips-solutions.com/>
> 
> On 27.09.2019 18:18, Igor Olhovskiy wrote:
> > but Enpoint B still thinks it's registered at least 2599 seconds.
> 
> _______________________________________________
> Users mailing list
> [hidden email] <x-msg://17/user/SendEmail.jtp?type=node&node=7616299&i=1>
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
> 
> 
> -- 
> Best regards,
> Igor
> 
> _______________________________________________ 
> Users mailing list 
> [hidden email] <x-msg://17/user/SendEmail.jtp?type=node&node=7616299&i=2> 
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
> 
> 
> If you reply to this email, your message will be added to the discussion below:
> http://opensips-open-sip-server.1449251.n2.nabble.com/mid-registrar-question-tp7616290p7616299.html <http://opensips-open-sip-server.1449251.n2.nabble.com/mid-registrar-question-tp7616290p7616299.html>
> To start a new topic under OpenSIPS - Users, email ml+s1449251n1449235h19 at n2.nabble.com <mailto:ml+s1449251n1449235h19 at n2.nabble.com> 
> To unsubscribe from OpenSIPS - Users, click here <http://opensips-open-sip-server.1449251.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1449235&code=YWxleGVpLnZhc2lseWV2QGdtYWlsLmNvbXwxNDQ5MjM1fC0xOTc3MDM4NDMy>.
> NAML <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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190927/cc9a58a9/attachment.html>