OK understood. Thanks for the information. Actually I thought it would be using TCP in any case, good to know UDP is the default. So it like using ffmpeg "-rtsp_transport tcp" parameter on the client side then.
-----Original Message----- From: live-devel <live-devel-boun...@us.live555.com> On Behalf Of Ross Finlayson Sent: Monday, January 9, 2023 8:54 PM To: LIVE555 Streaming Media - development & use <live-de...@us.live555.com> Subject: Re: [Live-devel] question RTSP server > On Jan 9, 2023, at 11:41 AM, g.jaegy <g.ja...@imagine3d.fr> wrote: > > Perfect, that what I've done and it's working like a charm 👍 I've indeed > extracted an underlying class with one instance shared across all my custom > source inputs, so that input sources can be destroyed/created at anytime. > Works great. > > I'll now try to have the stream to be accessible on the internet, I think I > have seen some example or documentation mentioning http/port 80 somewhere, I > will check that tomorrow. That’s for RTSP/RTP-over-HTTP, which our server supports, but which you probably don’t need, unless you have a firewall - between your server and client - that blocks all ports except port 80. Otherwise, if your client can reach the server via the normal RTSP ports (554 or 8554), then you just use RTSP as usual. By default, this will give you RTP-over-UDP. But if your have a firewall that blocks UDP packets, your client can, instead, request RTP-over-TCP (using the RTSP TCP connection). You can test this using VLC (which automatically tries RTP-over-TCP within a few seconds if RTP-over-UDP doesn't work). Or you can use our “openRTSP” command-line RTSP client, using the “-t” option. Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
