used freepbx 13 for 6 years with no problems, upgrade to 17, sip vicious is driving me crazy, had to downgrade back to 13,
What was the issue to mad you crazy// and why you did not connect with (community) us before you downgrade…
phones ringing all the time, blocked ips, configured freepbx firewall and fail2ban, still gets through, read other posts about what to do, none worked
no problems with 13, i just gave up on 17
Not sure if you still need help or not with this, but if yes, you should probably start in your firewall depending if it’s behind a nat, in your main firewall.
I think you had hurry up to downgrade to Freepbx13 but that version is EOL you will have more issues in a feature time. Maybe you need to make more attention to Firewall and F2B settings at FreePBX17.
Agreed with @slobera
I believe that the SIPVicious scripts
are only coded to check UDP transport (and almost almost always just UDP:5060 
) one very easy solution is to not listen on UDP, TCP is a very easy to move to, TLS is not much harder and far more secure with “server check” enabled .
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.