<span style="color: rgb(0, 0, 0);" class="gI"><span class="gD">I agree with @William Suffill</span></span><span style="color: rgb(0, 0, 0);"> mentioned. very good advise. Because putting third party router in front of your FS switch will put your back to NAT issues.</span> <br style="color: rgb(0, 0, 0);">
<br style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0);">So, putting iptables as suggested can protect + keep the voice quality stable.</span><br style="color: rgb(0, 0, 0);"><br style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0);">Thanks & Regards</span><br>
<br><br><div class="gmail_quote">On Tue, Oct 5, 2010 at 8:55 PM, Mario <span dir="ltr"><<a href="mailto:mario_fs@mgtech.com">mario_fs@mgtech.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
After working 4 hours I found that FS was hosed due to someone from<br>
208.109.87.234 sending tons of traffic to FS. I blocked the IP address.<br>
Not only did it overload the connection but stopped FS from working,<br>
meaning no phones. This had not happened with the SPA9000. I listed on<br>
on a FS conference call discussing this issue. Is there someplace that<br>
has a list of things to do to prevent/reduce this? I did have ports,<br>
etc. blocked in the firewall. Thanks. Mario<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br>