The public context is unauthentecared that is why its called public. Only public facing extensions should be defined there.
1) Output network_ip of received INVITE with appropriate comment like "Block for one day ip x.x.x.x"2) Add fail2ban rule to search strings like "Block for one day ip x.x.x.x" and block ipOn Sat, Aug 15, 2015 at 12:18 PM, Nikolay Zaytsev <nzaytsevc@gmail.com> wrote:Hi,all)I have the freeswitch on public ip with set up fail2ban.However, there is an external invites which proceed to dialplan's context public.How can I defend my freeswitch from such attaks?The log of such attack is in the attachment.Bets Regards,Nikolay Zaytsev
_________________________________________________________________________
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