[asterisk-bugs] [Asterisk 0012983]: [patch] Retransmitted RFC 2833 RTP events do not increment the RTP sequence number

noreply at bugs.digium.com noreply at bugs.digium.com
Wed Jul 16 04:36:17 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12983 
====================================================================== 
Reported By:                vt
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12983
Category:                   Core/RTP
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 127721 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-03-2008 10:01 CDT
Last Modified:              07-16-2008 04:36 CDT
====================================================================== 
Summary:                    [patch] Retransmitted RFC 2833 RTP events do not
increment the RTP sequence number
Description: 
All 3 retransmitted ending packets share the same sequence number, which
does not comply with RFC 4733 Sect. 2.5.1.6. RTP Sequence Number:

   The RTP sequence number MUST be incremented by one in each successive
   RTP packet sent.  Incrementing applies to retransmitted as well as
   initial instances of event reports, to permit the receiver to detect
   lost packets for RTP Control Protocol (RTCP) receiver reports.
====================================================================== 

---------------------------------------------------------------------- 
 vt - 07-16-08 04:36  
---------------------------------------------------------------------- 
Yes, I understand that. This "issue" was actually reported to me as causing
interop problems but after investigation and testing, I realized it was not
the case. Anyhow, I had the patch and thought I should as well send it
upstream for you to check. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-16-08 04:36  vt             Note Added: 0090331                          
======================================================================




More information about the asterisk-bugs mailing list