[Bug 720435] rtpbasepayload: Prefer downstream SSRC after collision if possible

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Tue Dec 17 06:32:21 PST 2013


https://bugzilla.gnome.org/show_bug.cgi?id=720435
  GStreamer | gst-plugins-good | unspecified

--- Comment #5 from Wim Taymans <wim.taymans at gmail.com> 2013-12-17 14:32:14 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > So, selection of the SSRC is then done by setting the SSRC properties on the
> > relevant elements.
> 
> The how do you handle the case where a receiver become a sender later, how do
> you prevent a second useless SSRC from being added ? And the original
> sender-only one never times out.

When a session needs to generate RTCP and it was only a receiver, it generates
an internal source and SSRC. If you later want to make a sender with this same
SSRC you will have to configure it that way (currently it's set on the sinkpad
caps so new senders can pick it up for backwards compatibility). This doesn't
work for multiple senders.

The original receiver-only SSRC should time out when the session has a
(different) sender SSRC, I guess that's not implemented yet.

> 
> This is also an API break from 1.0, at least Farstream relies on the
> "internal-ssrc" property of the internal-source to set the SSRC..

I'm sure we can fix that.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list