Summary:ASTERISK-03374: [patch] let app_queue inherit MONITOR_EXEC and MONITOR_EXEC_ARGS from calling channel, if they exist.
Reporter:twisted (twisted)Labels:
Date Opened:2005-01-28 13:32:38.000-0600Date Closed:2008-01-15 15:23:56.000-0600
Versions:Frequency of
Environment:Attachments:( 0) queue_monitor-HEAD.txt
Description:Currently app_queue only accepts vars MONITOR_EXEC and MONITOR_EXEC_ARGS from the agent side (peer) instead of the calling channel (qe->chan).  This patch allows us to set these vars on the calling side and have monitor deal with it appropriately.  If the vars don't exist on the calling side, it will go ahead and use the old method, and process on the agent side.


Disclaimer on file
Comments:By: Mark Spencer (markster) 2005-01-28 23:10:15.000-0600

I'm fine with this, can we get anthm to take a peek just to be sure?

By: Anthony Minessale (anthm) 2005-01-31 11:20:56.000-0600

Seems perfectly ok to me but just as an FYI, you could always disable agent recording and just call Monitor on the caller with the b flag to delay recording till the bridge starts right before sticking them in the Queue.  The bonus of that is if the caller leaves by pressing a 1 digit exten and ends up elsewhere in a bridged call it will still get recorded but I'm just pointing that out the patch seems reasonable to me.

By: Mark Spencer (markster) 2005-01-31 21:48:30.000-0600

Added to CVS, with small formatting mods.

By: Russell Bryant (russell) 2005-02-06 21:03:58.000-0600

not in 1.0

By: Digium Subversion (svnbot) 2008-01-15 15:23:56.000-0600

Repository: asterisk
Revision: 4941

U   trunk/apps/app_queue.c

r4941 | markster | 2008-01-15 15:23:56 -0600 (Tue, 15 Jan 2008) | 2 lines

Make monitoring accept args from both sides (bug ASTERISK-3374, with mods)