>Thanks. I’ll likely add this to a future release of the software.
Great!!! many thanks Ross.
By the way could you also remove the fuzzy file "live\liveMedia\stDjgzxL" from
your future release?
Denis.
___
live-devel mailing list
live-devel@lists.live
> Ross, you can find attached the following patch I have used. It is enabled by
> a #define macro configuration and it only concerns the TCP socket of the RTSP
> connection.. What do you think about it?
Thanks. I’ll likely add this to a future release of the software.
Ross Finlayson
Live Netw
Hi,
First of all, thank you for all your quick replies.
The problem we are seeing appears on our RTSP server software installed in an
environment which has a terrible quality of service (regularly the network shut
down,) and tens of front end clients connected on it. When a network
shutdown
On May 30, 2018, at 8:28 PM, Ross Finlayson wrote:
>
>> On May 30, 2018, at 7:16 PM, Warren Young wrote:
>>
>> On May 30, 2018, at 7:34 AM, GENESTIER Denis
>> wrote:
>>>
>>> Then if you disconnect the Ethernet wire of the computer B, the server will
>>> close the session, the RTP and RTCP s
> On May 30, 2018, at 7:16 PM, Warren Young wrote:
>
> On May 30, 2018, at 7:34 AM, GENESTIER Denis
> wrote:
>>
>> Then if you disconnect the Ethernet wire of the computer B, the server will
>> close the session, the RTP and RTCP sockets (in UDP mode), but not the RTSP
>> connection (in TC
On May 30, 2018, at 7:34 AM, GENESTIER Denis
wrote:
>
> Then if you disconnect the Ethernet wire of the computer B, the server will
> close the session, the RTP and RTCP sockets (in UDP mode), but not the RTSP
> connection (in TCP)
I’d say the real mystery here is how the UDP streams are bein
First, I assume that you’re referring to the per-client TCP socket that’s set
up to handle each client’s RTSP commands/responses. (In contrast, the server’s
(single) main RTSP socket - on port 554 or 8554 - remains open as long as the
server stays up.)
The per-client TCP socket gets closed (by
