[asterisk-bugs] [Asterisk 0011429]: Sent RTP video packets have a timestamp based on a 8000 Hz clock instead of 90000 Hz when mark bit is on

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11429 
====================================================================== 
Reported By:                sperreault
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11429
Category:                   Core/RTP
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 90351 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             11-30-2007 14:53 CST
Last Modified:              01-15-2008 18:51 CST
====================================================================== 
Summary:                    Sent RTP video packets have a timestamp based on a
8000 Hz clock instead of 90000 Hz when mark bit is on
Description: 
When you ast_write() a video packet, you are supposed to put the mark bit
into the LSB of the subclass member:

f->subclass = AST_FORMAT_H263 | 1;

This makes this conditional in ast_rtp_raw_write() true while it should be
false:

if (f->subclass & AST_FORMAT_AUDIO_MASK) {

The solution is simple: invert the video and audio code paths. First check
for video, and then if video is not present check for audio.
====================================================================== 

---------------------------------------------------------------------- 
 qwell - 01-15-08 18:51  
---------------------------------------------------------------------- 
Testing what I suggested would be a good way to help get it fixed. :)

See bugnote:74623 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-15-08 18:51  qwell          Note Added: 0080716                          
======================================================================