Reply To: SecAst not detecting attacks on FreePBX system

You have discovered a problem in FreePBX! When creating the SecAst AMI user account and selecting ‘all’ for permissions in the FreePBX GUI, FreePBX does not actually add the ‘all’ permission. Instead FreePBX adds individual permissions and omits the ‘security’ permission.

Until this is fixed in FreePBX please do NOT create your AMI user account through the FreePBX GUI. Instead modify the manager_custom.conf file to manually insert the credentials. For example, your manager_custom.conf might look like this:


[teliumuser]
secret = teliumpassword!
deny=0.0.0.0/0.0.0.0
permit=172.31.0.0/255.255.0.0
permit=127.0.0.1/255.255.255.0
read = all
write = all
 


Where the username (in [] brackets) and the password (secret) match the values you set in the secast.conf file. If you need further assistance with this workaround please contact support.