<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <tt>Hi,<br>
      <br>
      There was a similar email couple of days ago - the idea is to do
      fix_nated_contact() for all the traffic (replies and requests)
      coming from the WS(S) end point (as such endpoints are not able to
      provide a routable contact)<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="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 06/12/2019 12:08 PM, Callum Guy
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAFjCFzmdZvQZn8i_TdFgnfLwZTFAWZ4AhzZFLZb29ZLGkiNHKw@mail.gmail.com">
      <div dir="ltr">Hi All,<br>
        <div><br>
        </div>
        <div>I am in the process of configuring a WebRTC/SIP proxy and
          wanted to know if there was any way to prevent OpenSIPs from
          attempting to resolve the .invalid domains present in the Via
          headers:</div>
        <div><font face="courier new, monospace"><br>
          </font></div>
        <div><font face="courier new, monospace">INVITE <a
              href="mailto:sip%3Aabc@us.net" moz-do-not-send="true">sip:abc@us.net</a>
            SIP/2.0<br>
            Via: SIP/2.0/WSS b7evbq9f9q22.invalid;branch=z9hG4bK5495466</font><br>
        </div>
        <div><br>
        </div>
        <div>Although all is working I'm seeing the following log
          message.</div>
        <div><br>
        </div>
        <div><font face="courier new, monospace">CRITICAL:core:mk_proxy:
            could not resolve hostname: "</font><span
            style="font-family:"courier new",monospace">b7evbq9f9q22</span><font
            face="courier new, monospace">.invalid"</font><br>
        </div>
        <div><br>
        </div>
        <div>Certainly it seems that this is compliant with the RFC
          defined behaviour (<a
            href="https://tools.ietf.org/html/rfc7118#appendix-B.1"
            moz-do-not-send="true">https://tools.ietf.org/html/rfc7118#appendix-B.1</a>)
          however I am hoping there is a simple way to block lookups to
          this domain to save resources etc.</div>
        <div><br>
        </div>
        <div>On a side note I am typically reviewing SIP on our network
          using sngrep, when relaying these messages over UDP sngrep is
          failing to read the packets (presumably due to the extremely
          large SDP failing reassembly). While I'm writing I wondered if
          anyone has seen this before and could offer advice - the
          target endpoint (FreeSWITCH) has no issues reading it. One
          workaround could be to use TCP (tested and works) however I
          was curious if there was another solution?</div>
        <div><br>
        </div>
        <div>Thanks,</div>
        <div><br>
        </div>
        <div>Callum</div>
        <div><br>
        </div>
      </div>
      <br>
      <p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify"><font
          face="Verdana" size="3"><span
style="font-size:8px;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline"></span></font></p>
      <div><img
src="https://www.x-on.co.uk/email/footer/banner-surgeryconnect-jun-sep-19.jpg"
          moz-do-not-send="true"></div>
      <div><br>
      </div>
      <div>
        <div>
          <div><font size="4"><b><sup><font face="Verdana">0333 332
                    0000  |  <a href="http://www.x-on.co.uk"
                      target="_blank" moz-do-not-send="true">www.x-on.co.uk</a> 
                    |  <sub> </sub></font></sup></b></font><font
              size="4"><b><sub><sup><font face="Verdana"><a
                        href="https://www.linkedin.com/company/x-on"
                        target="_blank" moz-do-not-send="true"><img
                          src="http://www.x-on.co.uk//images/icon/linkedin.png"
                          moz-do-not-send="true" height="24" width="24"></a>
                       <a href="https://www.facebook.com/XonTel"
                        target="_blank" moz-do-not-send="true"><img
                          src="http://www.x-on.co.uk//images/icon/facebook.png"
                          moz-do-not-send="true" height="24" width="24"></a>
                       <a href="https://twitter.com/xonuk"
                        target="_blank" moz-do-not-send="true"><img
                          src="http://www.x-on.co.uk//images/icon/twitter.png"
                          moz-do-not-send="true" height="24" width="24"></a></font></sup></sub> </b></font><br>
            <p><span
                style="font-size:6.0pt;font-family:Verdana;color:black">X-on
                is a trading name of Storacall Technology Ltd a limited
                company registered in
                England and Wales.<br>
                Registered Office : Avaland House, 110 London Road,
                Apsley, Hemel Hempstead,
                Herts, HP3 9SD. Company Registration No. 2578478.<br>
                The information in this e-mail is confidential and for
                use by the addressee(s)
                only. If you are not the intended recipient, please
                notify X-on immediately on <span>+44(0)333 332 0000</span>
                and delete the<br>
                message from your computer. If you are not a named
                addressee you must not use,
                disclose, disseminate, distribute, copy, print or reply
                to this email. </span><span
                style="font-size:6.0pt;font-family:Verdana;color:black">Views
                or opinions expressed by an individual<br>
                within this email may not necessarily
                reflect the views of X-on or its associated companies.
                Although X-on routinely
                screens for viruses, addressees should scan this email
                and any attachments<br>
                for
                viruses. X-on makes no representation or warranty as to
                the absence of viruses
                in this email or any attachments.</span></p>
            <p><span
                style="font-size:6.0pt;font-family:Verdana;color:black"></span><font
                size="2"><span
                  style="font-size:6.0pt;font-family:Verdana;color:black"></span></font></p>
          </div>
        </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>