Tag Info

New answers tagged

0

I suspect your SIP port is now in the RTP range, so Asterisk doesn't realize this is a SIP connection. Either move the SIP port or move the RTP port range so they don't overlap. To capture the CLI output, from the bash prompt: asterisk -r core set verbose 10 Then make a call from your LAN which works, Then make a call from outside your LAN which fails ...


0

I think you are heading down the wrong path here. Asterisk is moving away from simple security event logging (to a flat file) and instead moving towards security events through the AMI. Considering blocking based on AMI events, and NOT on the security log. There are a number of free alternatives to fail2ban (look at ...



Top 50 recent answers are included