AGI is analogous to CGI in Apache. AGI provides an interface between the Asterisk dialplan and an external program that wants to manipulate a channel in the dialplan. In general, the interface is synchronous - actions taken on a channel from an AGI block and do not return until the action is completed.
AMI provides a mechanism to control where channels execute in the dialplan. Unlike AGI, AMI is an asynchronous, event driven interface. For the most part, AMI does not provide mechanisms to control channel execution - rather, it provides information about the state of the channels and controls about where the channels are executing.
voipmuch wrote:Hi ambiorixg12,
Thanks for the reply.
We are not looking for any channel related function... I have found those details.
We are looking to get/set an user/extension call forward details.
We are looking to get/set an user/extension speed dial details.
We are looking to get/set an user/extension voicemail password.
Basically all user/extension based functions.
No, Asterisk's REST API does not provide calls that allow manipulating call forward, speed dial, or voicemail password.
voipmuch wrote:Thank you for the replies.
OK... so to confirm, there is no way to set a call forward for a user except for the user to physically pickup the phone connected to Asterisk and dial the associated * feature?
Portals like Elastic and FreePBX seem to be able to do this somehow.
voipmuch wrote:Thanks.... that would mean that the existing * codes to call forward already do that (or there would be no way for the phone * codes and the webportal to be in sync with each other. I will check the current .conf files and see where the * feature codes store and lookup this information, and go from there.
Users browsing this forum: No registered users and 3 guests