<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <tt>Hi Giovanni,<br>
      <br>
      The CANCEL is hop-by-hop, which means each SIP hop will generate a
      completely new CANCEL (to be sent further) - there is not
      proxying, so the changes you do over the incoming CANCEL will not
      propagate into the outgoing CANCEL.<br>
      <br>
      I cannot recall it, but is there a standard case of pushing ISUP
      into CANCEL ?<br>
      <br>
      Best regards,<br>
    </tt>
    <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  <a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
OpenSIPS Summit 2019
  <a class="moz-txt-link-freetext" href="https://www.opensips.org/events/Summit-2019Amsterdam/">https://www.opensips.org/events/Summit-2019Amsterdam/</a>
</pre>
    <div class="moz-cite-prefix">On 12/07/2018 02:00 PM, Giovanni
      Maruzzelli wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CALXCt0qyWsjGNnxhisn7vUxZM-_ACL4gtkdPaOc44fs5t2WTnA@mail.gmail.com">
      <div dir="ltr">
        <div>Hi all,</div>
        <div><br>
        </div>
        <div>using 2.4<br>
        </div>
        <div><br>
        </div>
        <div>I am trying to add_isup_part("Release"); to a CANCEL</div>
        <div><br>
        </div>
        <div>It does not give errors (I use same isup_param(s) as per
          BYE), but the CANCEL that is being sent out does not have the
          isup part. <br>
        </div>
        <div>Eg, it does not even have a body, and Content-Length is 0.
          <br>
        </div>
        <div><br>
        </div>
        <div>I suspect t_relay, when it recreate the CANCEL from the
          original INVITE, does not care about what add_isup_part added
          to the CANCEL (it makes sense, t_relay creates the CANCEL
          anew, from original INVITE). <br>
        </div>
        <div><br>
        </div>
        <div>Any known workaround?</div>
        <div><br>
        </div>
        <div>Using forward instead of t_relay sends a CANCEL with the
          isup part, but remote reject it with 481 (call/transaction
          does not exists), probably because is not routed exactly like
          the initial INVITE, a branch parameter in a via header is
          different...</div>
        <div><br>
        </div>
        <div>-giovanni<br>
        </div>
        <br clear="all">
        <br>
        -- <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 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>