<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix"><tt>Hi George,<br>
        <br>
        If your OpenSIPS fails to reach the UAC is because of two
        reasons:<br>
            - NAT pinhole is closed - but if pinging is done, it shouldn't
        be<br>
            - opensips is trying to contact UAC via wrong IP:port - can
        you confirm that when calling the UAC, OpenSIPS sends the INVITE
        to same IP and port as where the pingings are coming from ?<br>
        <br>
        TCP works as this part is "automatically" resolved because of
        the connection (where the other pipe is known).<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="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
      On 15.10.2014 03:24, george wu wrote:<br>
    </div>
    <blockquote
      cite="mid:4dd40a9b.e54.14911311a6a.Coremail.aihuawu2012@163.com"
      type="cite">
      <div
        style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><br>
        <div>Hi, Bogdan-Andrei:<br>
          <br>
          For udp, it fails when <tt>reaching the UAC even though the
            UAC keeps pinging the server all the time.<br>
            <br>
            For tcp, although it works. I find something interesting.<br>
            Only when the client pings the server, the invite message is
            sent to the UAC.<br>
            In my understanding, the server should be able to send
            message to the UAC since the <br>
            tcp connection is open. Actually the sip server is unable to
            send message to the UAC.<br>
            <br>
            About the firewall type, I use opensipsctl ul show/rm to
            check.<br>
            I find every time when it register, i get the same ip/port</tt><tt><tt>
              most of time</tt>. <br>
            But occasionally it might get different ip/port.<br>
            I believe it is nat within a cone.<br>
            <br>
            I am using ice, the ice only work after the first invite
            message is delivered to the peer.<br>
            My ice with mediaproxy works perfectly.<br>
            <br>
          </tt></div>
        <br>
        George Wu<br>
        <br>
        At 2014-10-15 00:22:46, "Bogdan-Andrei Iancu"
        <a class="moz-txt-link-rfc2396E" href="mailto:bogdan@opensips.org">&lt;bogdan@opensips.org&gt;</a> wrote:<br>
        <blockquote id="isReplyContent" style="PADDING-LEFT: 1ex;
          MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
          <div class="moz-cite-prefix"><tt>Hi George,<br>
              <br>
              NAT traversal is not only about pinging, but also about
              mangling/correcting the SIP traffic (from private IPs
              perspective) and ensuring the RTP flow.<br>
              <br>
              So you need to be sure that all 3 points are addressed.<br>
              <br>
              TCP versus UDP - there is only a difference at IP
              transport level...like datagram versus connection, and
              their implications at NAT level (being able to reach the
              device behind the nat). Otherwise it;s the same.<br>
              <br>
              For UDP, can you see what fails ? the registration?
              reaching the UAC ? <br>
              <br>
              Regards,<br>
            </tt>
            <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
            On 14.10.2014 18:37, george wu wrote:<br>
          </div>
          <blockquote
            cite="mid:9f50cdb.2658d.1490f4e26ee.Coremail.aihuawu2012@163.com"
            type="cite">
            <div
              style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial">
              <div>My experience is for two uac (linphone) behind a
                firewall,<br>
                tcp/tls will always work.<br>
                udp will never work.<br>
                <br>
                for both tcp/udp, my uac will send keep alive every 10
                seconds.<br>
                I don't understand what makes those difference.<br>
                Can any one  share your experience?<br>
                <br>
                George Wu<br>
                <br>
                <br>
              </div>
            </div>
            <br>
            <br>
            <span title="neteasefooter"><span id="netease_mail_footer"></span></span><br>
            <fieldset class="mimeAttachmentHeader"></fieldset>
            <br>
            <pre wrap="">_______________________________________________
Users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a moz-do-not-send="true" 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>
        </blockquote>
      </div>
      <br>
      <br>
      <span title="neteasefooter"><span id="netease_mail_footer"></span></span>
    </blockquote>
    <br>
  </body>
</html>