[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 09:40 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0095769) mdu113 (reporter) - 2008-12-04 09:40
 http://bugs.digium.com/view.php?id=13801#c95769 
---------------------------------------------------------------------- 
Are you sure it's related to talker optimization? Have you checked what it
sends with optimization disabled?
All my devices are (and always have been) configured for default 20ms per
packet and so my opinion is based on the experience with that
configuration.
Also, honestly I just don't believe in technology. It's based on the same
principle as silence suppression/VAD and I've played quite some time with
VAD implementation from different vendors several years ago and my
conclusion is that if voice quality is of your concern you better disable
it. I belive it just can't be made working fine for everybody. During that
time I've been receiving constant complaints about comfort noise level is
ok for one, but not good for another person complaining of dead silence,
complaints of audible click when silence suppression kicks in and out, then
there's always some inertia and more often than not when a person starts
speaking first few milliseconds of the speech are cut out by silence
suppression and so on.
When I tried to enable talker optimization feature all those complaints
have immediately arose again, so I'd prefer to disable it and never look
back. Bandwidth/computers are not that expensive today to risk customer
satisfaction for the sake of that little savings. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-04 09:40 mdu113         Note Added: 0095769                          
======================================================================