Unimplemented AMI Actions

Unimplemented AMI Actions — Which parts of the Asterisk Manager API are currently missing

Although the GAmi Library aims to fully support the Asterisk manager API, some actions currently lack implementation (and will possibly continue to do so). As of Asterisk 1.6.0.3, those are the unimplemented actions:

  • QueueRule.  The QueueRule action lacks documentation, and is therefore unimplemented. It is a recent addition to asterisk and will hopefully be improved to behave properly - for the time being, it returns a completely empty package too often.

  • QueueStatus.  The QueueStatus action returns a list of queues including a list of queue members for each of them. There is probably no way to implement this using GLib standard types, although it should be pretty easy to implement using a dedicated data type.

  • Queues.  The Queues action does not return a proper response package but text as outputted by the queues show CLI command. With the current architecture it is quite difficult to implement, and as there are functional equivalent actions which return proper packages, it will probably remain unimplemented

  • IAXnetstats.  The IAXnetstats action is another recent API addition, which may return a completely empty packet. If the action changes to something proper, it will probably be added.

  • IAXpeers.  The IAXpeers action used to return the output of the CLI command iax2 show peers. As of asterisk 1.6.0 it was changed to return a list of event packets similar to the SIPpeers action. Unfortunately, it does not return a ListCompleted event, which makes it difficult to implement. It will be added some day, but while it remains possible that the API changes to include said event, it seems wise to wait.

  • ShowDialPlan.  The ShowDialPlan action returns the dialplan as list of events, one per extension. Unfortunately, it does not include any event to indicate completion, so it is currently difficult to add. It is not high-priority either, as its use seems esotheric.

  • UpdateConfig.  The UpdateConfig action makes it possible to change configuration files using the manager API. It does not have a fixed set of parameters, so it is unclear if it will ever be implemented. Its mainly used by asterisk-gui, so there is no hurry implementing it.

  • Command.  The Command action is used to execute any CLI command. It is certainly the most usefull action of those listed here, but unfortunately its text output may be difficult to fit with the existing API.