[asterisk-bugs] [Asterisk 0014044]: [patch] Jitterbuffer stops accepting new frames until it is empty after maxjitterbuffer is exceeded.

Sat Jan 24 03:55:18 CST 2009

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14044 
====================================================================== 
Reported By:                mnicholson
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14044
Category:                   Core/Jitterbuffer
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 162139 
Request Review:              
====================================================================== 
Date Submitted:             2008-12-09 12:16 CST
Last Modified:              2009-01-24 03:55 CST
====================================================================== 
Summary:                    [patch] Jitterbuffer stops accepting new frames
until it is empty after maxjitterbuffer is exceeded.
Description: 
Once the jitterbuffer exceeds maxjitterbuffer it stops accepting new frames
until the buffer is emptied.  This can cause large audio dropouts.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012575 IAX forcejitterbuffer + maxjitterbuffer
====================================================================== 

---------------------------------------------------------------------- 
 (0098646) vazir (reporter) - 2009-01-24 03:55
 http://bugs.digium.com/view.php?id=14044#c98646 
---------------------------------------------------------------------- 
I confirm this behavior in 1.4.21.2 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-24 03:55 vazir          Note Added: 0098646                          
======================================================================