I’m not sure what exactly you’re asking here. When receiving a
RTP/RTCP-over-TCP stream (i.e., on the RTSP TCP connection), we certainly do
handle socket read errors, if they occur. But the actual socket itself (for
the RTSP TCP connection) is not closed until the “RTSPClient” decides that it
I have realized that streaming in interleaved mode and having the state
AWAITING_PACKET_DATA, we use fReadHandlerProc as incomingReportHandler1()
for RTPInterface for rtcp
networkReadHandler1() for RTPInterface for rtp.
But I don't see the remote close event(readSocket returning -1) being
handled h
Hi,
We are currently facing a socket descriptor leak for the source through
which we stream using live555 as proxy. I was looking for a location where
sockets are closed for the source. I looked into the networkReadHandler
callback to check if we close sockets if readSocket returns -1(for
bytesRea
