Just was i thought, the first request after time expires are applying the multiplier<br><br><div class="gmail_quote">On Thu, Jun 18, 2009 at 2:41 PM, Mark Michelson <span dir="ltr"><<a href="mailto:mmichelson@digium.com">mmichelson@digium.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Eduardo Nunes Pereira wrote:<br>
> But, do the "qualify" equal "yes" have a influence over that rule ?<br>
> forgive my knowledge about asterisk internals, but "qualify" option is<br>
> used to send OPTIONS packages ? [ qualify=no ]<br>
><br>
> And the first retry of REGISTER after expire time continues with delay<br>
> 1000ms<br>
><br>
<br>
</div>qualify sends OPTIONS requests to the peer. The time taken to respond to the<br>
OPTIONS is used as timer T1. If you do not have qualify enabled, then Asterisk<br>
uses a default of 500 ms for T1.<br>
<br>
Asterisk appears to be scheduling its first retransmission of requests after 2 *<br>
T1 instead of just using T1. This same logic is used for all request types that<br>
may be retransmitted.<br>
<div><div></div><div class="h5"><br>
Mark Michelson<br>
<br>
_______________________________________________<br>
--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Eduardo Nunes Pereira<br>Consultor de Informática e Internet<br>cel.: (48) 9989-2997<br>email: <a href="mailto:eduardonunesp@gmail.com">eduardonunesp@gmail.com</a><br>