We had a "different" discussion, but related. As a note FS is not used for nat traversal, proxy or registrar services so doing anything in FS would not be useful. The discussion centered around the sipx services (proxy, registrar, and perhaps providing information to a firewall for automated scripting...). ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431
Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: [email protected] <[email protected]> To: Discussion list for users of sipXecs software <[email protected]> Sent: Sat Oct 09 18:42:26 2010 Subject: [sipx-users] frequent restarts needed On Sat, 9 Oct 2010, Tony Graziano wrote: > http://blog.myitdepartment.net/?p=124 I think the problem rather points up a need for thinking through, and adding a range of in-product rate limiting of various type -- per source IP, wrappreing per netblocks, per real-time failure stats, and so forth, in free-switch The Linux kernel will fall back to a more restrictive 'new session' approach when it sees a TCP 'half-open' attack, and so forth -- same basic idea here -- Russ herrold _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
