From 5b41f40c31c1f5c6215e295ff2df00aade01a433 Mon Sep 17 00:00:00 2001 From: "Kevin P. Fleming" Date: Mon, 4 Apr 2005 23:47:47 +0000 Subject: update manager interface documentation (bug #3936) git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@5388 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- doc/manager.txt | 171 +++++++++++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 162 insertions(+), 9 deletions(-) (limited to 'doc') diff --git a/doc/manager.txt b/doc/manager.txt index 3693c8dbd..96ded4f52 100755 --- a/doc/manager.txt +++ b/doc/manager.txt @@ -1,15 +1,37 @@ -The Asterisk Manager TCP/IP API -=============================== +The Asterisk Manager TCP/IP API - AMI +===================================== The manager is a client/server model over TCP. With the manager interface, you'll be able to control the PBX, originate calls, check mailbox status, monitor channels and queues as well as execute Asterisk commands. +AMI is the standard management interface into your Asterisk server. +You configure AMI in manager.conf. By default, AMI is available on +TCP port 5038 if you enable it in manager.conf. + +AMI receive commands, called "actions". These generate a "response" +from Asterisk. Asterisk will also send "Events" containing various +information messages about changes within Asterisk. Some actions +generate an initial response and data in the form list of events. +This format is created to make sure that extensive reports do not +block the manager interface fully. + Management users are configured in the configuration file manager.conf and are given permissions for read and write, where write represents their ability to perform this class of "action", and read represents their ability to receive this class of "event". +The Asterisk manager interface in version 1.0.x of Asterisk is +not very well standardized. Work is under way to change this +to Asterisk 1.2. If you develop AMI applications, treat the headers +in Actions, Events and Responses as local to that particular +message. There is no cross-message standardization of headers. + +If you develop applications, please try to reuse existing manager +headers and their interpretation. If you are unsure, discuss on +the asterisk-dev mailing list. + + Command Syntax -------------- Management communication consists of tags of the form "header: value", @@ -43,10 +65,13 @@ Output from the CLI command 'show manager' command: * StopMonitor: Stop monitoring a channel * ChangeMonitor: Change monitoring filename of a channel * IAXpeers: List IAX Peers (Defaults to IAX2) - * IAX1peers: List IAX version 1 Peers + * SIPpeers: List SIP peers + * SIPshowpeer: Show data about one SIP peer * Queues: Queues * QueueStatus: Queue Status +This list depends on the version of Asterisk you are using, as +well as which modules that are loaded. Command Summary -------------- @@ -82,6 +107,8 @@ Parameters: Channel, ExtraChannel, Exten, Context, Priority Command: Timeout Parameters: Channel, Timeout +You can always get more information about a manager command +with the "show manager command " CLI command in Asterisk. Examples -------- @@ -122,10 +149,136 @@ Redirect with ExtraChannel: Where 680 is an extension that sends you to a MeetMe room. There are a number of GUI tools that use the manager interface, please search -the mailing list archives and the documentation page on the http://www.asterisk.org -web site for more information. - - - +the mailing list archives and the documentation page on the +http://www.asterisk.org web site for more information. + + +Some standard AMI headers: +-------------------------- + + Account: -- Account Code (Status) + ACL: -- Does ACL exist for object ? + Action: -- request or notification of a particular action + Address-IP: -- IPaddress + Address-Port: -- IP port number + Agent: -- Agent name + AMAflags: -- AMA flag + Append: -- CDR userfield Append flag + Application: -- Application to use + Async: -- Whether or not to use fast setup + AuthType: -- Authentication type (for login or challenge) + "md5" + CallerID: -- Caller id (name and number in Originate) + CallerID: -- CallerID number + Number or "" or "unknown" + (should change to "" in app_queue) + CallerIDName: -- CallerID name + Name or "" or "unknown" + (should change to "" in app_queue) + Callgroup: -- Call group for peer/user + CallsTaken: -- Queue status variable + Cause: -- Event change cause - "Expired" + Cause: -- Hangupcause (channel.c) + CID-CallingPres: -- Caller ID calling presentation + ChanVariable: -- Channel variable to set - name,value (comma between name and value) + Channel: -- Channel specifier + Channel: -- Dialstring in Originate + Channel: -- Channel in Registry events (SIP, IAX2) + Channel: -- Technology (SIP/IAX2 etc) in Registry events + ChannelType: -- Tech: SIP, IAX2, ZAP, MGCP etc + Channel1: -- Link channel 1 + Channel2: -- Link channel 2 + ChanObjectType: -- "peer", "user" + Codecs: -- Codec list + CodecOrder: -- Codec order, separated with comma "," + Command: -- Cli command to run + Context: -- Context + Count: -- Number of callers in queue + Data: -- Application data + Default-addr-IP: -- IP address to use before registration + Default-Username: -- Username part of URI to use before registration + Destination: -- Destination for call (Dialstring ) Dial event + DestUniqueID: -- UniqueID of destination (dial event) + Domain: -- DNS domain + Dynamic: -- Device registration supported? + EventList: -- Flag being "Start", "End", "Cancelled" or "ListObject" + Events: -- Eventmask filter ("on", "off", "system", "call", "log") + Exten: -- Extension (Redirect command) + Extension: -- Extension (Status) + Family: -- ASTdb key family + File: -- Filename (monitor) + Format: -- Format of sound file (monitor) + From: