text
stringlengths
0
152
unknown
phones
agi_extension
500
agi_priority
1
agi_enhanced
0.0
agi_accountcode myaccount
agi_threadid
140071216785168
agi_arg_<argu
ment number>
my argument
320
|
Chapter 18: Asterisk Gateway Interface
Description
The first argument that was passed to the AGI() or EAGI()
application. For process-based AGI, this is the name of the AGI
application that has been executed. For FastAGI, this would be
the URL that was used to reach the FastAGI server.
The name of the channel that has executed the AGI() or
EAGI() application.
The language set on agi_channel.
The channel type for agi_channel.
The uniqueid of agi_channel.
The Asterisk version in use.
The full caller ID string that is set on agi_channel.
The caller ID name that is set on agi_channel.
The caller presentation associated with the caller ID set on
agi_channel. For more information, see the output of
core show function CALLERPRES at the Asterisk
CLI.
The caller ANI2 associated with agi_channel.
The caller ID TON (Type of Number) associated with
agi_channel.
The dialed number TNS (Transit Network Select) associated
with agi_channel.
The dialed number associated with agi_channel.
The redirecting number associated with agi_channel.
The context of the dialplan that agi_channel was in when
it executed the AGI() or EAGI() application.
The extension in the dialplan that agi_channel was
executing when it ran the AGI() or EAGI() application.
The priority of agi_extension in agi_context that
executed AGI() or EAGI().
An indication of whether AGI() or EAGI() was used from
the dialplan. 0.0 indicates that AGI() was used. 1.0
indicates that EAGI() was used.
The accountcode associated with agi_channel.
The threadid of the thread in Asterisk that is running the
AGI() or EAGI() application. This may be useful for
associating logs generated by the AGI application with logs
generated by Asterisk, since the Asterisk logs contain thread
IDs.
These variables provide the contents of the additional
arguments provided to the AGI() or EAGI() application.
For an example of the variables that might be sent to an AGI application, see the AGI
communication debug output in “Quick Start” on page 315. The end of the list of
variables will be indicated by a blank line. The code handles these variables by read‐
ing lines of input in a loop until a blank line is received. At that point, the application
continues and begins executing AGI commands.
Async AGI
When you use async AGI, Asterisk will send out a manager event called AsyncAGI to
initiate the async AGI session. This event will allow applications listening to manager
events to take over control of the call via the AGI manager action. Here is an example
manager event sent out by Asterisk:
Event: AsyncAGI
Privilege: agi,all
SubEvent: Start
Channel: SIP/0000FFFF0001-00000000
Env: agi_request%3A%20async%0Aagi_channel%3A%20SIP%2F0000FFFF0001-00000000%0A \
agi_language%3A%20en%0Aagi_type%3A%20SIP%0A \
agi_uniqueid%3A%201285219743.0%0A \
agi_version%3A%201.8.0-beta5%0Aagi_callerid%3A%2012565551111%0A \
agi_calleridname%3A%20Julie%20Bryant%0Aagi_callingpres%3A%200%0A \
agi_callingani2%3A%200%0Aagi_callington%3A%200%0Aagi_callingtns%3A%200%0A \