[Bug 794789] rtspclientsink: Fix client ports for the RTCP backchannel

[GStreamer (GNOME Bugzilla)]

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

--- Comment #11 from Mathieu Duponchelle <mduponchelle1 at gmail.com> ---
(In reply to Patricia Muscalu from comment #10)
> There is no need to call this function at all I think. It's just about
> allocating client ports for receiving RTP and RTCP, so it shouldn't be any
> dependencies to the server ports.
> 

You realize that RTCP goes both ways don't you? In the RECORD case,
rtspclientsink will send RTP and RTCP (eg Sender Reports) to the server, but it
also needs to inform the server, through "client_ports" in the transports
string, about the port it will listen on for RTCP, to receive the Receiver
Reports and potential retransmission requests. It obtains these ports through
the confusingly named gst_rtsp_stream_get_server_port () API.

> > > What if the "server ports" are already allocated on the client
> > > side?
> > 
> > I don't understand that question.
> 
> The RTP/RTCP sockets are bound to the RTP/RTCP ports (<=> server ports). The
> client issues a SETUP request with the client_port pair of ports, so I guess
> that there are the corresponding sockets associated with these ports on the
> client side. Am I wrong?

See my answer above :)

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