[asterisk-bugs] [Asterisk 0018742]: [patch] MIXMON_ARGS not processed when call being monitored via chanspy

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18742 
====================================================================== 
Reported By:                jkister
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18742
Category:                   Applications/app_mixmonitor
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.8.2.3 
JIRA:                       SWP-3043 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-02-03 11:02 CST
Last Modified:              2011-03-10 13:44 CST
====================================================================== 
Summary:                    [patch] MIXMON_ARGS not processed when call being
monitored via chanspy
Description: 
x146 is talking to an outside line
x143 uses extenspy to listen on x146

x146 hangs up the call to outside line (while x143 is still monitoring)

${MIXMON_ARGS} is not honored.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0018750 The MixMonitor application fails to exe...
====================================================================== 

---------------------------------------------------------------------- 
 (0132823) jrose (manager) - 2011-03-10 13:44
 https://issues.asterisk.org/view.php?id=18742#c132823 
---------------------------------------------------------------------- 
Alrighty, I'm having a look at this.

I've tested it with a couple of different options on both Dial and
MixMonitor.  It seems that this bug only really happens though when Dial is
used on a SIP channel (granted, the only other type of channel I've tested
it with is DAHDI, so that isn't the best sample size).  In any event, in
order for execution to occur normally in the meantime, you can use the
following:

When you use Dial, do something like this:
Dial(<channel>,<timeout>,g)

The g option guarantees that once the channel is hung up on the receiver's
side that it will continue to execute dial plan commands from where it left
off in the extension.

Then, when you use MixMonitor(whateverfile.extension,<whateveroptions>,
<whatever command>) make sure you use StopMixMonitor before you reach the
end of the extension.

The end result is that the mix monitor will destruct properly and then the
command will run.

So yeah, the behavior as it is right now isn't ideal, but you can use that
to at least be able to spy normally without having to stop the spy channel
each time to use your commands.  It's good practice to always use
StopMixMonitor() with MixMonitor anyway.  We still want to have a better
look at it though since the behavior isn't consistent between different
channel types and that's less than desirable. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-10 13:44 jrose          Note Added: 0132823                          
======================================================================