<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>note that we currently have
<a class="moz-txt-link-freetext" href="https://opensips.org/html/docs/modules/3.6.x/dialog.html#func_dlg_send_sequential">https://opensips.org/html/docs/modules/3.6.x/dialog.html#func_dlg_send_sequential</a>
      , it can be used to generate a PRACK ( you'll have to manually add
      the Rseq header), but it's not working properly if the upstream
      has multiple TO-TAGS that are ringing ( it will always generate to
      the newest learnt to-tag, and there's also some quirks with CSEQ
      mapping ), so perhaps the 'manual' approach would be getting
      dlg_send_sequential to work properly for generating early requests
      ( with PRACK being a rather specific use-case due to it's
      cseq/rseq stuff )</p>
    <div class="moz-cite-prefix">On 11/25/25 13:14, Giovanni Maruzzelli
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CALXCt0odxGKZqZ3BEFgztDjAXY3_0JG+PKwA-Kc0y7KXUtBXyg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">
        <div dir="auto"><br>
        </div>
        <div class="gmail_quote gmail_quote_container" dir="auto">
          <div dir="ltr" class="gmail_attr">On Tue, Nov 25, 2025, 11:57
            Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org"
              moz-do-not-send="true" class="moz-txt-link-freetext">bogdan@opensips.org</a>>
            wrote:</div>
          <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div><font face="monospace"> <br>
                The result here should be a dlg dedicated function to
                generate a PRACK from the onreply_route, like
                "dlg_answer_with_prack()" kind of function? or should we
                look into a more automatic approach, like flagging the
                dialog at creation to automatically generate the PRACK
                upon replies flagged with so?<br>
              </font></div>
          </blockquote>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">personally I'm a control freak and would like
          better an explicit function, maybe even with parameters to
          modify things if needed :))</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">-giovanni</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto"><br>
        </div>
        <div class="gmail_quote gmail_quote_container" dir="auto">
          <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div><font face="monospace"> <br>
                Regards,<br>
              </font>
              <pre cols="72">Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  <a href="https://www.opensips-solutions.com" target="_blank"
              rel="noreferrer" moz-do-not-send="true"
              class="moz-txt-link-freetext">https://www.opensips-solutions.com</a>
  <a href="https://www.siphub.com" target="_blank" rel="noreferrer"
              moz-do-not-send="true" class="moz-txt-link-freetext">https://www.siphub.com</a></pre>
              <div>On 25.11.2025 11:46, Giovanni Maruzzelli wrote:<br>
              </div>
              <blockquote type="cite">
                <div dir="ltr">
                  <div>
                    <div>hello OpenSIPSers,</div>
                    <div><br>
                    </div>
                    <div>in previous mails has been noticed that various
                      ITSPs are starting to require PRACK support.</div>
                    <div><br>
                    </div>
                    <div>We know that PRACK belongs to endpoints,
                      specifically phones and B2BUAs.</div>
                    <div><br>
                    </div>
                    <div>But...</div>
                    <div><br>
                    </div>
                    <div>There can be a use case where OpenSIPS will
                      work as SBC (not necessarily using the b2b module)</div>
                    <div><br>
                    </div>
                    <div>So, we can have a case where we would like to
                      support that the dialogue module insert the 100rel
                      in the Supported: INVITE's header, and manage to
                      send a PRACK method to acknowledge provisional
                      responses</div>
                    <div><br>
                    </div>
                    <div>If and when 100rel/PRACK are "generated" by
                      OpenSIPS, they will be filtered out (not
                      propagated) to/from the endpoints, even if the
                      endpoint would like to support it</div>
                    <div><br>
                    </div>
                    <div>Reference RFC: <a
                        href="https://www.ietf.org/rfc/rfc3262.txt"
                        target="_blank" rel="noreferrer"
                        moz-do-not-send="true"
                        class="moz-txt-link-freetext">https://www.ietf.org/rfc/rfc3262.txt</a></div>
                    <div><br>
                    </div>
                    <div>I believe this will be enough to make ITSPs
                      happy.</div>
                    <div><br>
                    </div>
                    <div>Further developments can be moved to future.</div>
                    <div><br>
                    </div>
                    <div>Would be very very nice to have this feature
                      backported to OpenSIPS 3.6, being it the last of
                      the 3.X series, and an LTS</div>
                    <div><br>
                    </div>
                    <div>Please let's gather here your thoughts ,
                      requests, corrections and observations on this
                      issue.</div>
                    <div><br>
                    </div>
                    <div>Have a nice Monday you all!</div>
                    <font color="#888888">
                      <div><br>
                      </div>
                      <div>-giovanni</div>
                    </font></div>
                  <div><br>
                  </div>
                  <span class="gmail_signature_prefix">-- </span><br>
                  <div dir="ltr" class="gmail_signature"
                    data-smartmail="gmail_signature">Sincerely,<br>
                    <br>
                    Giovanni Maruzzelli<br>
                    OpenTelecom.IT<br>
                    cell: +39 347 266 56 18<br>
                    <br>
                  </div>
                </div>
                <br>
                <fieldset></fieldset>
                <pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank"
                rel="noreferrer" moz-do-not-send="true"
                class="moz-txt-link-freetext">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
                target="_blank" rel="noreferrer" moz-do-not-send="true"
                class="moz-txt-link-freetext">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
              </blockquote>
              <br>
            </div>
          </blockquote>
        </div>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre wrap="" class="moz-quote-pre">_______________________________________________
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>
  </body>
</html>