<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix"><tt>Hi Patrick,<br>
        <br>
        First, you can control the timeout in a per-request fashion, by
        setting from script some TM variables:<br>
            - in 1.11 -
        <a class="moz-txt-link-freetext" href="http://www.opensips.org/html/docs/modules/1.11.x/tm.html#id295747">http://www.opensips.org/html/docs/modules/1.11.x/tm.html#id295747</a><br>
            - in 1.10 -
        <a class="moz-txt-link-freetext" href="http://www.opensips.org/html/docs/modules/1.10.x/tm.html#id294137">http://www.opensips.org/html/docs/modules/1.10.x/tm.html#id294137</a><br>
        <br>
        And no, 4320 is not supported, I will look into it.<br>
        <br>
        Regards,<br>
      </tt>
      <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
      On 16.09.2014 20:45, Patrick Wakano wrote:<br>
    </div>
    <blockquote
cite="mid:CAPu3kNWNpgXqu7wLZ8NMSGEDe53hzHZPRTbw2mQkzMZ5zbsADg@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hello list,
        <div><br>
        </div>
        <div>I have a scenario with mobile user - Opensips - Asterisk
          and I was having some trouble with Options requests sent from
          Asterisk to mobile user.</div>
        <div>Due to a high value of the qualify timeout on Asterisk a
          and low value of the fr_timeout from tm module, Options
          requests sent to unreachable users were being answered with a
          408 by Opensips and so Asterisk was considering the user
          reachable when in fact they weren't.</div>
        <div>After some debug I discovered that the low fr_timeout was
          inducing a fast 408 reply back to Asterisk, and since its
          qualify mechanism accepts *any* reply as valid, then the user
          remained reachable until the registration expired.</div>
        <div>Problem was solved but during my research I found the
          RFC4320 (<a moz-do-not-send="true"
            href="http://www.ietf.org/rfc/rfc4320.txt">http://www.ietf.org/rfc/rfc4320.txt</a>)
          that deals with this situation. According to it, I think that
          Opensips should not send this 408 for non-invites. Not sure if
          Opensips should implement anything related but I thought it
          was worth the advice!</div>
        <div><br>
        </div>
        <div>Regards,</div>
        <div>Patrick</div>
        <div><br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>