GNOME Bugzilla – Bug 770954
Client cannot decide destination/port in SETUP
Last modified: 2018-11-03 15:40:23 UTC
Currently the mcast address is allocated from the address pool on DESCRIBE, and only one mcast group is supported. So if a client asks for a specific destination/port in SETUP, default_configure_client_transport() will call gst_rtsp_stream_reserve_address() and will return an error.
That would require adding a new updsink, which potentially causes pipelines getting stuck. The queues after the tee might be full (because the pipeline is blocked, waiting for the actual client sink to be added) and then the newly added client sink never prerolls because it will never get data. At this point it might be nicer to write a custom RTSP server sink element (and maybe even a source element) for UDP, that handles multiple sockets internally from one thread (and does not require queues, threads per udpsrc, ...). We almost completely manage the sockets already anyway.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-rtsp-server/issues/27.