[gstreamer-bugs] [Bug 520626] New: Implement collision and loop detection in rtpmanager

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=520626

  GStreamer | gst-plugins-bad | Ver: HEAD CVS
           Summary: Implement collision and loop detection in rtpmanager
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: tester at tester.ca
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Here is a basic implementation of the collision and loop detection stuff
present in RFC 3550 section 8.2. I does not collect all the stats and increment
all the counters where it should (I'm not certain how the whole stats thing is
supposed to work in rtpmanager).  I'm also not certain that the resetting is
done correctly after changing the SSRC of the sender. Also, I think the
RTPSource from the old sender should be kept according to the RFC.

I'm also attaching at patch against the netaddress code in g-p-base that adds a
gst_netaddress_compare (since there is padding in the structure, memcmp can't
be used). The g-p-bad code contains a static version of that function (since
its probably too late to get it into base) and I'm also attaching a patch that
can be applied to rtpmanager once it gets into base after the dep freeze.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=520626.