[Bug 793441] rtsp-stream: client transport is not updated for multicast clients

[GStreamer (GNOME Bugzilla)]

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

--- Comment #9 from Patricia Muscalu <patricia at axis.com> ---
(In reply to Patricia Muscalu from comment #8)
> (In reply to Sebastian Dröge (slomo) from comment #7)
> > (In reply to Patricia Muscalu from comment #6)
> > > But we should already respond with the correct ttl value on the SETUP
> > > request.
> > 
> > But we don't?
> We respond, but the value might not be the one, the current client is
> requesting.
> Example:
> * SETUP 1: ttl=1 => the value will be set on the rtp socket
>   RTSP OK ttl=1
> * SETUP 2: ttl=3 
>   RTSP OK ttl=3  => but this value is never set on the socket!
> 
> > Do you have a suggestion how to solve this? Instead of taking the maximum or
> > minimum ttl-mc, we could also take only the one of the first for example.
> I think, that your first suggestion of taking the maximum value is the one
> we should implement. I'll send you a patch.

The drawback of this approach is that, that the first client will suddenly
receive IP packets with ttl=3 (if we follow the example above). So, you are
probably right, that the first client should decide.

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