For what it's worth, if you have a FS instance exposed to the world you're almost certainly better off with something in front of it.

Even if you lock down your server in such a way that no unauthorized calls can be made, the traffic is still going to make it to your freeswitch instance. Generating enough bogus traffic could materially impact the quality of active calls by wasting CPU cycles, disk I/O from logs, and memory from the connections.

Whether the "something" you put in front of it is a firewall with appropriate restrictions, a SIP proxy of some kind, or something else, is up to you (depending on the amount of introspection to the request you need). But I wouldn't recommend leaving it open.

Best,
Colin

On Wed, Aug 3, 2016 at 11:44 AM jungle Boogie <jungleboogie0@gmail.com> wrote:
On 3 August 2016 at 01:12, Mirko Brankovic <mirkobrankovic@gmail.com> wrote:
> Hi,
> I guess you can set this to true on your profile:
> https://wiki.freeswitch.org/wiki/Sofia.conf.xml#log-auth-failures
>
> and than fail2ban can pick it up from the log.
>

yes, that work's if the registration attempts are actually being
picked up by freeswitch. I only see a register request and no reply
from my side whatsoever.

The IP address has been added to my iptables but the entries are still
occurring.  As seen in the original email, I have iptables to block
based on the useragent but I still see the scans.



> Mirko




--
-------
inum: 883510009027723
sip: jungleboogie@sip2sip.info

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org