[asterisk-bugs] [Asterisk 0012679]: [patch] Transcoding breaks jitterbuffering

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12679 
====================================================================== 
Reported By:                damjan
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12679
Category:                   Channels/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.18 
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-05-19 03:46 CDT
Last Modified:              2008-09-27 12:57 CDT
====================================================================== 
Summary:                    [patch] Transcoding breaks jitterbuffering
Description: 
Asterisk doesn't copy or regenerate ts, len or seqno when transcoding from
the original frame to the transcoded frame. The jitterbuffer then sees a
frame with bad timing info and fails to dejitter the frame.

====================================================================== 

---------------------------------------------------------------------- 
 (0092904) msalles (reporter) - 2008-09-27 12:57
 http://bugs.digium.com/view.php?id=12679#c92904 
---------------------------------------------------------------------- 
Yes, it really happens in my setup, transcoding between ZAP and SIP, with
jbenable=yes on zapata.conf. I´ve tested with:

asterisk-1.4.18.1
asterisk-1.4.20-1
asterisk-1.4.21.2

They all have the same problem. The jitterbuffer can´t work properly
because transcoding has ripped the timing info. I´ve got the following in
the logs: 

[Sep 26 20:30:09] WARNING[3200] abstract_jb.c: Zap/106-1 recieved frame
with invalid timing info: has_timing_info=0, len=0, ts=0, src=g729tolin_f
rameout

PS: I´ve tested the patch and it worked! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-27 12:57 msalles        Note Added: 0092904                          
======================================================================