rtspclientsink: Fix client ports for the RTCP backchannel
authorMathieu Duponchelle <mathieu@centricular.com>
Thu, 29 Mar 2018 00:51:02 +0000 (02:51 +0200)
committerMathieu Duponchelle <mathieu@centricular.com>
Fri, 30 Mar 2018 15:55:32 +0000 (17:55 +0200)
commit7f9b8c2107f3b64eda753ae27e44958ee2020930
treedea491cd933385f31694302245c55f7a5d0d1fa6
parent3a129300f0e6e7d0336c2d2c315a2b36e052eaf1
rtspclientsink: Fix client ports for the RTCP backchannel

This was broken since the work for delayed transport creation
was merged: the creation of the transports string depends on
calling stream_get_server_port, which only starts returning
something meaningful after a call to stream_allocate_udp_sockets
has been made, this function expects a transport that we parse
from the transport string ...

Significant refactoring is in order, but does not look entirely
trivial, for now we put a band aid on and create a second transport
string after the stream has been completed, to pass it in
the request headers instead of the previous, incomplete one.

https://bugzilla.gnome.org/show_bug.cgi?id=794789
gst/rtsp-sink/gstrtspclientsink.c
tests/check/gst/rtspclientsink.c