please explain the settings

[tonyguadagno]

sorry to be dense, but what are
context
protocol
channel

referring to?
thanks

[susobaco]

After much testing and research, I got the perfect configuration. For one thing, we have to look at our asterisk configuration. To do this, we run it on the server:
vi /etc/asterisk/manager.conf
We add this line:
#include manager_custom.conf
Now we edit the file:
vi /etc/asterisk/manager_custom.conf
And we created a user with the following:

[our_user]
secret = our_password
deny=0.0.0.0/0.0.0.0
permit=192.168.1.0/255.255.255.0
permit=127.0.0.1/255.255.255.255
read = system,call,log,verbose,command,agent,user
write = system,call,log,verbose,command,agent,user

In the permet section must be our LAN.
Now the configuration of the addon:
SERVER: 192.168,1.XXX (The IP address of the Asterisk server)
PORT: 8088 (The addon only supports the AJAM protocol)
Username: our_user (The user we created before)
Password: our_password (The password we created earlier)
Context: from-internal (Here I don't know where it corresponds to the server configuration, I suppose it will be the extension from which we call)
Protocol: SIP (Same as above)
Channel: XXX (The number of the extension from which we make the call)

The addon generates two http commands to the web server, one for authentication and one for calling:
http://SERVER:8088/asterisk/manager?action=login&username=our_user&secret=our_password
http://SERVER:8088/asterisk/mxml?action=originate&channel=SIP/XXX&exten=called_number"&context=from-internal&CallerId=SIP/XXX&priority=1&codecs=alaw&timeout=5000

You can test from your web browser with those two addresses to see if you authenticate and make the call. If I have also seen that the timeout is for my taste quite short, instead of 5000, I would put 10000.
I hope it helps.