[Bug 790412] unit test failure: rtspclientsink test_record fails with GST_MESSAGE_TYPE (msg) != GST_MESSAGE_EOS

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=790412

--- Comment #20 from Patricia Muscalu <patricia at axis.com> ---
> Generally what would have to happen for rtspclientsink is:
> 
> 1) In READY->PAUSED the rtsp-streams are created, added to the rtpbin and
> blocked. This allows us to get all the information needed for sending
> ANNOUNCE to the server (i.e. the SDP)

Yes, it's correct.

> 
> 2) In PAUSED->PLAYING the sink is doing SETUP(s) and RECORD. Between the
> last SETUP and RECORD, all transports are known and can be configured on the
> rtsp-streams. Which can then be "completed" (-> add udpsink, appsink, etc.
> as needed for the RTP streams but also for the RTCP streams. How would we
> know before this where to send the RTCP?), and once RECORD has happened we
> can unblock the rtsp-streams so that data gets send to the RTP sinks, and
> thus to the RTSP server.

Yes, before SETUP we need to allocate UDP ports for RTP and RTCP and complete
the streams with the receiver and the sender parts.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.