[asterisk-users] How run AsyncAGI commands in background

[Jose Arias]

Hi Moy,

I'm using an asterisk 1.4.18 from scratch patched with the last AsyncAGI 
patch, which fixes a bug about stopping AsyncAGI applications, as may be 
you can recall from the thread [asterisk-users] async agi question in 
http://lists.digium.com/pipermail/asterisk-users/2009-April/230488.html.

This patched asterisk works fine and it stops the async agi applications 
launched from the AsyncAGI loop before the Redirect as it's expected. 
It's for that I don't think stopping the mixmonitor application launched 
from the AsyncAGI loop would be a bug if I redirect the call. I would be 
only getting the same behavior than I got with the stream file 
application as you explained it should be at 
http://www.moythreads.com/wordpress/2007/12/24/asterisk-asynchronous-agi/#comment-365 


I'm only asking if there's any way to prevent stopping applications 
launched on a channel from the AsyncAGI loop if this channel is 
redirected afterward, with something like a 
continue_running_in_background flag in the previous AGI invocation from 
AMI. Of course, it bring us the problem we'll need some kind of 
identifier and some stop action to be able to stop those applications 
running in background launched from the AsyncAGI loop

Anyway, as you asked me some days ago, I have published at 
http://docs.google.com/View?id=ahfnfrcrh3rr_4dkcx9dgw a simple 
configuration and a simple scenario in order you can try to reproduce 
what I'm saying.

I don't need anyone to do anything for me. I'm willing to do the work, I 
like programming and trying new things as well, but I'll need some 
guidelines to go straight ahead.

Thanks all
Jose

Moises Silva escribió:
> On Sun, Jun 7, 2009 at 4:37 PM, Jose Arias<cyr2242 at gmail.com> wrote:
>   
>> Hi Moy,
>>
>> I'll do it so, but for your answer, it seems you are thinking about it as it
>> could be a bug. I don't think so. I mean: the redirect action on a channel
>> in AsyncAGI stops the current agi execution. It's the normal behavior. It's
>> the way to stop a playfile on a channel if it was previously launched from
>> AsyncAGI: making a redirect out of the AsyncAGI loop.
>>
>> Therefore, when I realized the previously launched EXE MixMonitor AsyncAGI
>> execution was stopping after doing a redirect to meetme, I didn't think it
>> was a bug. I though what I was needing it was a way to tell AsyncAGI, "hey,
>> don't stop this agi execution on the channel, even it will be redirected out
>> of AGI" on an individual basis for each AsyncAGI EXEC command launched.
>>
>> Thanks
>> Jose
>>
>>     
> The way I see it if you make EXEC MixMonitor inside AsyncAGI loop and
> then redirect to MeetMe and you don't get the audio recorded, then
> it's not a normal behavior, MixMonitor is an application that should
> passively monitor the channel audio independently of where the channel
> is (regardless of whether the command was executed in Async AGI or
> dial plan or whatever). However you are also using an old asterisk
> version and is not likely you can report a bug unless you upgrade to
> the latest Asterisk and reproduce without a patched Asterisk (for
> example executing EXEC MixMonitor inside a regular AGI script and then
> redirect to MeetMe).
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090619/edee8f61/attachment.htm