[asterisk-bugs] [Asterisk 0013801]: [patch] No way to tune talker optimization in meetme, causes users to get cut off while they're still talking

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13801 
====================================================================== 
Reported By:                justdave
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   13801
Category:                   Applications/app_meetme
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.4.22 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-29 13:47 CDT
Last Modified:              2008-11-24 15:44 CST
====================================================================== 
Summary:                    [patch] No way to tune talker optimization in
meetme, causes users to get cut off while they're still talking
Description: 
I enabled 'o' talker optimization on my conference rooms because the
documentation in 1.4 says the feature will be permanently enabled in
Asterisk 1.6 with no way to disable it, so I figured we should probably get
used to it. However, if it works like this we'll have to never upgrade to
1.6.  We get constant complaints about people getting cut off while still
talking in the conferences, and I can't find any way to tune what it
considers "talking". If the feature is going to be permanently enabled, we
at least need some way to tune how sensitive it is.
====================================================================== 

---------------------------------------------------------------------- 
 (0095426) DEA (reporter) - 2008-11-24 15:44
 http://bugs.digium.com/view.php?id=13801#c95426 
---------------------------------------------------------------------- 
I am begining to think the issue is somewhere else in the code.

I have tried threshold set to 0,128 and 256.  There was some
improvement, but nothing major.

I started to suspect that maybe the extra RealTime scheduling
overhead was an issue, but a static conference with RealTime
disabled still sounds bad.  A conference of two or three callers
seems to work fine, but after the fourth caller, quality degrades
for that caller and beyond.  The first two/three callers do not
seem to be impacted.

I am running out of ideas to check, so maybe I will be rolling
back to 1.4 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-24 15:44 DEA            Note Added: 0095426                          
======================================================================