[asterisk-dev] Meetme AMI actions

[Nick Lewis]

> I'd suggest that the response contain the same fields as
> the CLI commands 'meetme list <conf>' or 'meetme list 
> <conf> concise' 

There seems to be much commonality in the requirements of AMI and CLI
requests. Responses in both cases are either tabular or detailed i.e.

param-name param-name param-name ...
para-value para-value para-value ...
para-value para-value para-value ...
para-value para-value para-value ...
...

or

param-name para-value
param-name para-value
param-name para-value
param-name para-value
param-name para-value
...

For new data structures could we have a standard way of 
defining the parameters to be output that applies to both 
AMI and CLI and then postprocess the result to provide 
the applicable formatting? 

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre.
_____________________________________________________________________
Disclaimer of Liability
ATL Telecom Ltd shall not be held liable for any improper or incorrect use of the  information described and/or contained herein and assumes no responsibility for anyones use  of the information. In no event shall ATL Telecom Ltd be liable for any direct, indirect,  incidental, special, exemplary, or consequential damages (including, but not limited to,  procurement or substitute goods or services; loss of use, data, or profits; or business  interruption) however caused and on any theory of liability, whether in contract, strict  liability, or tort (including negligence or otherwise) arising in any way out of the use of  this system, even if advised of the possibility of such damage.

Registered Office: ATL Telecom Ltd, Fountain Lane, St. Mellons Cardiff, CF3 0FB
Registered in Wales Number 4335781

All goods and services supplied by ATL Telecom Ltd are supplied subject to ATL Telecom Ltd standard terms and conditions, available upon request.