<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Understood, I though it was quite strange to see these unsolicited
    ACKs from the Polycoms followed by a RST.<br>
    <br>
    Thanks,<br>
    Spencer<br>
    <br>
    <br>
    On 05/13/2013 02:07 PM, Steven Schoch wrote:
    <blockquote
cite="mid:CAOkuKdcOqW1exccJZKSYmZKMaSihbLcETdYcrxYUH8vGwJnZgg@mail.gmail.com"
      type="cite">
      <div dir="ltr">On Sun, May 12, 2013 at 2:54 PM, Spencer Thomason <span
          dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:spencer@5ninesolutions.com" target="_blank">spencer@5ninesolutions.com</a>&gt;</span>
        wrote:<br>
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">The
              phones periodically send a TCP ACK ping to<br>
              Freeswitch which goes unanswered and then phone then tears
              down the TCP<br>
              connection. &nbsp;I'm not at all a TCP expert but should
              Freeswitch be<br>
              responding to this unsolicited ACK?</blockquote>
            <div><br>
            </div>
            <div style="">I've been working with TCP for 25 years, and
              this is the first I have heard of ACK ping. A quick Google
              search told me that this technique involves sending a
              normal TCP ACK packet (which all TCP packets except the
              initial one have, by the way) to a random TCP port. The
              host will then respond with a RST packet. (Which means
              reset the connection because the ACK was not sent to an
              established connection.)</div>
            <div style=""><br>
            </div>
            <div style="">However, a firewall may filter and discard
              these random ACK packets. Since they're not part of
              "normal" TCP, no one cares.</div>
            <div style=""><br>
            </div>
            <div style="">In answer to your question, this is in the TCP
              layer much deeper than Freeswitch. There is nothing
              Freeswitch can do at this level.</div>
            <div style=""><br>
            </div>
            <div style="">--&nbsp;</div>
            <div style="">Steve</div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
<a class="moz-txt-link-abbreviated" href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitchsolutions.com">http://www.freeswitchsolutions.com</a>

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
<a class="moz-txt-link-freetext" href="http://www.cudatel.com">http://www.cudatel.com</a>

Official FreeSWITCH Sites
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://wiki.freeswitch.org">http://wiki.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://www.cluecon.com">http://www.cluecon.com</a>

FreeSWITCH-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a>
</pre>
    </blockquote>
  </body>
</html>