[asterisk-bugs] [Asterisk 0011282]: [patch] Execute AGI from the CLI and the manager interface

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11282 
====================================================================== 
Reported By:                moy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11282
Category:                   Applications/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 89394 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             11-17-2007 23:09 CST
Last Modified:              12-11-2007 14:01 CST
====================================================================== 
Summary:                    [patch] Execute AGI from the CLI and the manager
interface
Description: 
This new application allow to take control of the applications executed
using the Asterisk console or via AMI.

[default]
exten => _X.,1,Answer()
exten => _X.,2,DynamicApp()
exten => _X.,3,Hangup()

Once the channel enter DynamicApp, it will wait there for applications to
execute. Applications may arrive either from the console or AMI, like
this:

*CLI> dynapp SIP/testing-09124338 Playback hello-world

That will execute Playback application with hello-world arguments.

The same using AMI:

Action: AddDynApp
Channel: SIP/testing-09124338
App: Playback
Data: hello-world

I need some help of you guys to check locking/unlocking of channels, I
think I am doing right, but I am still unsure about some cases. It seems to
work though.

Comments and corrections are always welcomed.
====================================================================== 

---------------------------------------------------------------------- 
 moy - 12-11-07 14:01  
---------------------------------------------------------------------- 
Thanks for your comments Tilghman.

1. Thanks for pointing that out.

2. Done.

3. Done.

4. Done.

5. Just after launch_script, a verification is done in order to call
run_agi(). For the Async AGI, we don't want to run_agi(), since
launch_script does all the work. That's why AGI_RESULT_SUCCESS_ASYNC is
needed. If you don't like it or find a good reason to try to avoid that
return code, we can work around it in some other way.

The patch is updated for revision 92324. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-11-07 14:01  moy            Note Added: 0075234                          
======================================================================