<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <tt>Hmm, maybe I've not explained this scenario properly.<br>
      <br>
      The proxy that is sitting on the customer premises is calling via
      our proxy. I dont have access to the customer's proxy at all. <br>
      <br>
      When their invite (via their proxy) hits our proxy the issue I
      explained originally is encountered. I believe they are only
      running a pure sip proxy, be it kamailio/opensips etc, and their
      ua's point to it for registration etc. When making a call it
      appears to just relay the invite but inserts a record route for
      their proxy. This causes issues with our b2b when it generates the
      bye message.<br>
      <br>
      I doubt stun/turn/rtpengine will help me in this scenario, unless
      I'm misunderstanding you.<br>
      <br>
      Will kamailio not honour the recieved/rport parameters in the
      route-header?<br>
      <br>
    </tt><br>
    <div class="moz-cite-prefix">On 03/05/18 15:44, Amar Tinawi wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAGjMUphE+i6NkiFRQ+hEvAp2q+uBW_t-xpKEq4v-QnDc-GemvA@mail.gmail.com">
      <div dir="auto">Then you may be use stun/turn solution or
        rtpengine
        <div dir="auto"><br>
        </div>
        <div dir="auto">Regards</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr">On Thu, May 3, 2018, 5:30 PM Asgaroth <<a
            href="mailto:00asgaroth00@gmail.com" target="_blank"
            rel="noreferrer" moz-do-not-send="true">00asgaroth00@gmail.com</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div text="#000000" bgcolor="#FFFFFF"> <tt>This would not
              work if I dont have access to the proxy that is
              advertising a private address in the record-route header,
              thanks for the tip though.<br>
              <br>
              <br>
            </tt><br>
            <div
              class="m_-4293252755143832784m_2739383449457061252moz-cite-prefix">On
              03/05/18 15:26, Amar Tinawi wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="auto">You may introduce advertise command  in
                the configuration files when defining the interfaces
                <div dir="auto"><br>
                  <div dir="auto"><br>
                  </div>
                  <div dir="auto">Like this way :</div>
                  <div dir="auto">listen=private ip  advertise public ip</div>
                </div>
              </div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr">On Thu, May 3, 2018, 4:52 PM Asgaroth
                  <<a href="mailto:00asgaroth00@gmail.com"
                    rel="noreferrer noreferrer" target="_blank"
                    moz-do-not-send="true">00asgaroth00@gmail.com</a>>
                  wrote:<br>
                </div>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
                  All,<br>
                  <br>
                  I've come accros a scenario where a proxy is sitting
                  on a private <br>
                  address range and inserts a record-route specifying
                  the the private address.<br>
                  <br>
                  This causes issues whereby the BYE to an INVITE
                  attempts to relay to the <br>
                  private address defined in record-route.<br>
                  <br>
                  I was wondering, if we were inject a received and
                  rport parameter into <br>
                  the record-route header of the original invite, whould
                  kamailio relay <br>
                  the response (BYE) to the receive/rport destination
                  instead of the uri <br>
                  defined in the record-route header.<br>
                  <br>
                  As an example, initial invite comes in with a
                  record-route as follows:<br>
                  <br>
                  Record-Route: <a
                    class="m_-4293252755143832784m_2739383449457061252moz-txt-link-rfc2396E"
                    rel="noreferrer noreferrer" moz-do-not-send="true"><sip:172.17.0.2:5062;lr;ftag=b4551d29></a><br>
                  <br>
                  If we injected received and rport as follows:<br>
                  <br>
                  Record-Route: <br>
                  <a
                    class="m_-4293252755143832784m_2739383449457061252moz-txt-link-rfc2396E"
                    rel="noreferrer noreferrer" moz-do-not-send="true"><sip:172.17.0.2:5062;lr;ftag=b4551d29;rport=33429;received=212.172.2.212></a><br>
                  <br>
                  and relayed the message to the B2B.<br>
                  <br>
                  Then, I assume, when the B2B creates its BYE message,
                  the Route header <br>
                  should look like this:<br>
                  <br>
                  Route: <br>
                  <a
                    class="m_-4293252755143832784m_2739383449457061252moz-txt-link-rfc2396E"
                    rel="noreferrer noreferrer" moz-do-not-send="true"><sip:172.17.0.2:5062;lr;ftag=b4551d29;rport=33429;received=212.172.2.212></a><br>
                  <br>
                  Once this hits the kamailio instance to relay to the
                  last route header <br>
                  as mentioned above, would it set $du to received:rport
                  like it does with <br>
                  Via headers?<br>
                  <br>
                  Thanks<br>
                  <br>
                  _______________________________________________<br>
                  Kamailio (SER) - Users Mailing List<br>
                  <a href="mailto:sr-users@lists.kamailio.org"
                    rel="noreferrer noreferrer noreferrer"
                    target="_blank" moz-do-not-send="true">sr-users@lists.kamailio.org</a><br>
                  <a
                    href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"
                    rel="noreferrer noreferrer noreferrer noreferrer"
                    target="_blank" moz-do-not-send="true">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
                </blockquote>
              </div>
              <br>
              <fieldset
                class="m_-4293252755143832784m_2739383449457061252mimeAttachmentHeader"></fieldset>
              <br>
              <pre>_______________________________________________
Kamailio (SER) - Users Mailing List
<a class="m_-4293252755143832784m_2739383449457061252moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org" rel="noreferrer noreferrer" target="_blank" moz-do-not-send="true">sr-users@lists.kamailio.org</a>
<a class="m_-4293252755143832784m_2739383449457061252moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer noreferrer" target="_blank" moz-do-not-send="true">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
            </blockquote>
            <br>
          </div>
          _______________________________________________<br>
          Kamailio (SER) - Users Mailing List<br>
          <a href="mailto:sr-users@lists.kamailio.org" rel="noreferrer
            noreferrer" target="_blank" moz-do-not-send="true">sr-users@lists.kamailio.org</a><br>
          <a
            href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"
            rel="noreferrer noreferrer noreferrer" target="_blank"
            moz-do-not-send="true">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Kamailio (SER) - Users Mailing List
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a>
<a class="moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>