[gstreamer-bugs] [Bug 545710] New: [rtspsrc] : create rtp/rtcp socket pair + same port for different tracks problem

[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=545710

  GStreamer | gst-plugins-good | Ver: HEAD CVS
           Summary: [rtspsrc] : create rtp/rtcp socket pair + same port for
                    different tracks problem
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: gstelzz at yahoo.fr
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Here is a patch to enhance rtp/rtcp socket pair.

Before : the RTP port was always the result of an anonymous bind.
if RTP port + 1 was busy, rtspsrc creation fails.

After : the first RTP port is an anonymous bind.
if not even, try RTP + 1 and whil it fails try RTP + 2
when ok, set RTCP to RTP+1. if it fails, go again with RTP+1

But, There might be a problem. (in fact there is in my application).
udpsrc sets the flag SO_REUSEADDR, so RTP/RTCP ports for tw different RTSP
tracks may be the same.
It seems a bit confusing for rtpbin following.
Here is a .dot and .log file to illustrate.
rtsp stream contains audio AMR (pt=97) and video H263 (pt=96)
Both streams goes to same rtpssrcdemux, then different jitterbuffer and
rtpdemux.
This could be ok if caps (except pt) whene not the same on both streams

Is this method for allocating RTP pair a mistake ?
Should we set a "no_reuse" property on udpsrc to be use in rtspsrc ?


-- 
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=545710.