<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix"><tt>H</tt><tt>i </tt><tt>J</tt><tt>orge,</tt><tt><br>
      </tt><tt><br>
      </tt><tt>Any SIP client must answer to an incoming request (even
        if it understands it or not) - it must send back some reply. The
        dialog module terminates the call if it gets a timeout (408) of
        487 (transaction/dialog not found) from the client. Other
        negative replies are not considered. </tt><tt><br>
      </tt><tt><br>
      </tt><tt>Usually, the risk is to have clients blindly answering
        with 200 OK to any OPTIONS (even if the dialog does not exist).</tt><tt><br>
      </tt><tt><br>
      </tt><tt>Regards,</tt><br>
      <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 17.07.2014 10:15, Jorge Luis Ortea wrote:<br>
    </div>
    <blockquote cite="mid:DUB128-W84494B263868375E96E4F4DCF40@phx.gbl"
      type="cite">
      <style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
      <div dir="ltr">Yes, the "B" flag was already configured (6 hours).<br>
        <br>
        But, might have a problem with Pp flag if a UAC don't reply to
        SIP OPTIONS messages?<br>
        <br>
        Thanks.<br>
        Regards.<br>
        <br>
        <br>
        <div>
          <hr id="stopSpelling">Date: Wed, 16 Jul 2014 15:35:07 +0300<br>
          From: <a class="moz-txt-link-abbreviated" href="mailto:bogdan@opensips.org">bogdan@opensips.org</a><br>
          To: <a class="moz-txt-link-abbreviated" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:darham@hotmail.com">darham@hotmail.com</a><br>
          Subject: Re: [OpenSIPS-Users] False dialogs due to network
          failures<br>
          <br>
          <div class="ecxmoz-cite-prefix"><tt>Or, be sure and set a
              reasonable dialog lifetime (like maybe 2 hours) together
              with the "B" flag (to send BYEs one dialog timeout).<br>
              <br>
              Regards,&nbsp; </tt><br>
            <pre class="ecxmoz-signature">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="ecxmoz-txt-link-freetext" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
            On 16.07.2014 13:14, Schneur Rosenberg wrote:<br>
          </div>
          <blockquote
cite="mid:CANvjR0X6cWZbYQatk4=xO8pz8mn17Dq7N7_9uiehL8+kSp7Z=g@mail.gmail.com">
            <p dir="ltr">create_dialog with Pp flag.</p>
            <div class="ecxgmail_quote">On Jul 16, 2014 10:45 AM, "Jorge
              Luis Ortea" &lt;<a moz-do-not-send="true"
                href="mailto:darham@hotmail.com">darham@hotmail.com</a>&gt;

              wrote:<br>
              <blockquote class="ecxgmail_quote" style="border-left:1px
                #ccc solid;padding-left:1ex;">
                <div>
                  <div dir="ltr"><br>
                    <div>
                      <div dir="ltr">Hi all,<br>
                        <br>
                        I'm using OpenSIPS 1.8. with several Asterisk.
                        When Proxy SIP manages a call keeps a dialog
                        with (called,caller,Asterisk) through
                        store_dlg_value function from dialog module.
                        Later through get_dialog_info function it match
                        calls and resolves transfers issue. <br>
                        <br>
                        I have the following problem, when a network
                        failure occurs those dialogs keep on and this
                        generate errors. <br>
                        How can I avoid this and remove those dialogs?<br>
                        <br>
                        Note: I don't know if it can be useful but
                        'Failure Route' is performed shortly after the
                        failure.<br>
                        <br>
                        Thanks.<br>
                        Regards.<br>
                      </div>
                    </div>
                  </div>
                </div>
                <br>
                _______________________________________________<br>
                Users mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
                <a moz-do-not-send="true"
                  href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
                  target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
                <br>
              </blockquote>
            </div>
            <br>
            <fieldset class="ecxmimeAttachmentHeader"></fieldset>
            <br>
            <pre>_______________________________________________
Users mailing list
<a moz-do-not-send="true" class="ecxmoz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a moz-do-not-send="true" class="ecxmoz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
          </blockquote>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>