Hello Bogdan-Andrei, I have a conversation with VoIP provider, he decrease "expires" time by 1 sec on each registration from 120 sec (our expiry value) to 29 sec (according 30 sec - minimal provider's value). So registration become to process too often. It is not make any problems for now. The provider motivates its behavior by the following:
> " > > In fact, this is the time left to the end of the registration, which is > indicated in the "expires" parameter sent in our 200 OK. "The time left to > the end of the registration" was my interpretation, but I think it's a > reasonable one. When your side requests "expires=120", our side honors this > request, but due to the actual record in the location registrar occurring > milliseconds later, the required "expires" time becomes 119. > > Imagine that a bigger delay happens between receiving INVITE and the actual > recording to the location registrar, let's say about 2 seconds. In this case, > if 200 OK was generated with "expires=120" and sent 2 seconds later after > receiving the first INVITE, your side would think that the registration ends > 2 seconds later than actually it was requested. > > " this is not a violation of RFC3261 Section 10.3 step 8: > ``` > > " > The registrar returns a 200 (OK) response. The response MUST contain Contact > header field values enumerating all current bindings. Each Contact value > MUST feature an "expires" parameter indicating its expiration interval chosen > by the registrar. > ``` > > " But in my opinion, the interpretation of the provider is not entirely correct. Despite this, I would like to know your opinion on this issue. Regards, <table style="border: 0; font-family: 'Helvetica', sans-serif; font-size: 13px; line-height: 20px;"><tbody><tr><td style="width: 95px; padding-right: 15px;"></td> <td style="width: 250px; padding-left: 15px; border-left: 3px solid #F6921E;"><span style="font-size: 16px;font-family:'Poppins',sans-serif">**Artem Fomenko**</span> <span style="font-size: 12px;font-weight: 500;font-family:'Poppins',sans-serif">**Development Team**</span> +421 2 33 456 826 (EU & Worldwide) +1-888-257-8754 (USA & Canada) [www.liveagent.com](https://www.liveagent.com/) </td> </tr></tbody></table> <table style="border: 0; font-family: 'Helvetica', sans-serif; font-size: 12px; line-height: 20px;"><tbody><tr style="width: 350px;"><td colspan="10">**How nice was my reply?** </td> </tr><tr style="width: 350px;"><td style="display: inline-block; margin: 0;">[](https://survey.nicereply.com/qualityunitqu/wuo5vwrn/fwuacc91?s=1)</td> <td style="display: inline-block; margin: 0;">[](https://survey.nicereply.com/qualityunitqu/wuo5vwrn/fwuacc91?s=2)</td> <td style="display: inline-block; margin: 0;">[](https://survey.nicereply.com/qualityunitqu/wuo5vwrn/fwuacc91?s=3)</td> <td style="display: inline-block; margin: 0;">[](https://survey.nicereply.com/qualityunitqu/wuo5vwrn/fwuacc91?s=4)</td> <td style="display: inline-block; margin: 0;">[](https://survey.nicereply.com/qualityunitqu/wuo5vwrn/fwuacc91?s=5)</td> <td style="display: inline-block; margin: 0;">[](https://survey.nicereply.com/qualityunitqu/wuo5vwrn/fwuacc91?s=6)</td> <td style="display: inline-block; margin: 0;">[](https://survey.nicereply.com/qualityunitqu/wuo5vwrn/fwuacc91?s=7)</td> <td style="display: inline-block; margin: 0;">[](https://survey.nicereply.com/qualityunitqu/wuo5vwrn/fwuacc91?s=8)</td> <td style="display: inline-block; margin: 0;">[](https://survey.nicereply.com/qualityunitqu/wuo5vwrn/fwuacc91?s=9)</td> <td style="display: inline-block; margin: 0;">[](https://survey.nicereply.com/qualityunitqu/wuo5vwrn/fwuacc91?s=10)</td> </tr><tr colspan="10" style="width: 350px;"><td style="margin: 15px 0 5px 0; font-size: 11px;">**Rate the answer or view the ticket history [here](https://support.qualityunit.com/ticket_HGFe1uycDX9XkGp8)**</td> </tr></tbody></table> -----Original message----- From: Bogdan-Andrei Iancu <[email protected]> Sent: 2022-10-10 16:50:42 > <font face="monospace">Hi Artem, > > This is the intended behavior of the module, re-register with the last > "expires" provided by the server - if the server had a good reason to lower > the registration time on first register, it will most probably do it for the > re-register's also. So does not make too much of a sense to keep using the > initial DB value - or do you have some good reason not to update ? > > Regards, > </font> ``` > <pre class="moz-signature">Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > <a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com"; > rel="noreferrer" target="_blank">https://www.opensips-solutions.com</a> > OpenSIPS Summit 27-30 Sept 2022, Athens > <a class="moz-txt-link-freetext" > href="https://www.opensips.org/events/Summit-2022Athens/"; rel="noreferrer" > target="_blank">https://www.opensips.org/events/Summit-2022Athens/</a> > ``` > > <div class="moz-cite-prefix">On 9/23/22 7:15 PM, Artem Fomenko via Users > wrote: > </div>
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
