[asterisk-bugs] [Asterisk 0015860]: wrong parsing of received RTCP packets
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Nov 15 15:26:44 CST 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15860
======================================================================
Reported By: klaus3000
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15860
Category: Core/RTP
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-09-09 06:12 CDT
Last Modified: 2009-11-15 15:26 CST
======================================================================
Summary: wrong parsing of received RTCP packets
Description:
The code for parsing the RTCP packets is buggy. When an RTCP RR/SR frame is
handled, it expects some fields present although they are optional.
E.g. take a look at the RTCP packets in the attached pcap dump. The first
RTCP packet contains a RR without any RTP statistics data. Nevertheless
Asterisk sets the statistics, reading wrong data from the RTCP packet (the
following SDS).
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0015819 [patch] buggy output in "sip show ...
======================================================================
----------------------------------------------------------------------
(0113833) oej (manager) - 2009-11-15 15:26
https://issues.asterisk.org/view.php?id=15860#c113833
----------------------------------------------------------------------
I just went through this code in 1.4 and it's very buggy. It just parses
the first report in a compound packet, ignoring the SDES and misbehaves in
many ways. I guess that the new code is not much better, even though there
has been some improvements in how we aggregate data.
Issue History
Date Modified Username Field Change
======================================================================
2009-11-15 15:26 oej Note Added: 0113833
======================================================================
More information about the asterisk-bugs
mailing list