[asterisk-bugs] [Asterisk 0011259]: Jitterbuffer does not work well with injected sound

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11259 
====================================================================== 
Reported By:                plack
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   11259
Category:                   Core/Jitterbuffer
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 89125 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2007-11-15 10:28 CST
Last Modified:              2008-08-05 19:16 CDT
====================================================================== 
Summary:                    Jitterbuffer does not work well with injected sound
Description: 
Using the following in the dial plan:
exten => 208,1,Noop
exten => 208,n,Set(LIMIT_WARNING_FILE=beep)
exten => 208,n,Dial(SIP/5001||L(36000000:36000000:15000))

the injected beep file is not passing through the jitterbuffer properly. 
If you look at the additional information, the jitterbuffer is off by the
number of frames required to send the audio.

Audio quality is impacted and there is a loss of packets during the
transmission of the beep tone.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-05 19:16 svnbot         Status                   assigned => resolved
2008-08-05 19:16 svnbot         Resolution               open => fixed       
======================================================================