I checked the file manager.conf and it seems ok for the permissions you think about it?
; AMI - Asterisk Manager interface
;
; FreePBX needs this to be enabled. Note that if you enable it on a different IP, you need
; to assure that this can’t be reached from un-authorized hosts with the ACL settings (permit/deny).
; Also, remember to configure non-default port or IP-addresses in amportal.conf.
;
; The AMI connection is used both by the portal and the operator’s panel in FreePBX.
;
; FreePBX assumes an AMI connection to localhost:5038 by default.
;
[general]
enabled = yes
port = 5038
bindaddr = 127.0.0.1
displayconnects=no ;only effects 1.6+
You do not call AGI commands via AMI they are completely different. You call AMI commands via AMI. AGI and AMI have totally different ways of dealing with calls.
That’s a 10 year old post that uses AEI not standard dialplan. It also has one big glaring thing in it:
So, my patch, allow users to execute AGI commands using “Action: AGI” and get the response reading “Event: AsyncAGI”. The manager header “CommandID” can be specified to match up the responses. Let’s see an example
You are not only referencing a 10 year old post that uses a specific (and not widely used) dialplan alternative that was also PATCHED by the user.
So this is not a standard Asterisk thing and I highly doubt that patch is maintained for the current versions of Asterisk. Where you able to find any examples that are using current versions of Asterisk like 13 or 15?
You will probably need to do this in the manager_custom.conf file since the FreePBX GUI only offers a limited set of AMI permissions that can be granted.