[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:                     confirmed
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-12-04 15:31 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0095800) DEA (reporter) - 2008-12-04 15:31
 http://bugs.digium.com/view.php?id=13801#c95800 
---------------------------------------------------------------------- 
OK, so I have been chasing a similar, but unrelated bug.  I still have
some
test findings that might help this issue.  The biggest one I noted is
segfaults and a possible Kernel panic when I tried setting the detection
threshold to 0.

The comment added to the code recently about the threshold not needing to
be a power of 2 was a nice addition, but more helpful would be to
identify
the units that threshold represents (ms, audio energy, something else)
and
perhaps some suggestions on tuning (icrease or decrease if silence is 
incorrectly detected) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-04 15:31 DEA            Note Added: 0095800                          
======================================================================