[asterisk-bugs] [Asterisk 0010060]: MixMonitor does not work in MeetMe using Zap Channels

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10060 
====================================================================== 
Reported By:                mparker
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10060
Category:                   Applications/app_mixmonitor
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:             1.2.17  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             06-25-2007 18:17 CDT
Last Modified:              08-03-2007 18:22 CDT
====================================================================== 
Summary:                    MixMonitor does not work in MeetMe using Zap
Channels
Description: 
If you start a mixmonitor on a zap channel and put that channel into a
MeetMe conference, you will only hear outgoing audio from the channel and
no incoming.  This does work for SIP channels however.  I need it working
for Zap channels also.  
====================================================================== 

---------------------------------------------------------------------- 
 qwell - 08-03-07 18:22  
---------------------------------------------------------------------- 
During an internal Digium training session on MeetMe this morning, the
topic that this issue describes came up.

It was explained that the audio going to Zap channels from a MeetMe
conference does not actually go through Asterisk - this is done on purpose.
 It is "optimized" to stay inside of Zaptel, rather than coming back to
Asterisk, and then through Zaptel a second time.  The workaround we
discussed, as eldadran suggested, was to use a Local channel (with the 'n'
option).

I'm not really sure what we want to do here.  I guess if something like
MixMonitor is attached to the channel, it shouldn't try to optimize
Asterisk out of the audio path. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-03-07 18:22  qwell          Note Added: 0068425                          
======================================================================