> Does this encrypt only the RTSP part of the conversation? Is the video still
> in the clear?
Only the RTSP connection is encrypted. RTP/UDP packets are unaffected. There
is currently no support for SRTP. And, once again, this change is only for
our client implementation of RTSP.
>
I can diff the code once it downloads but I thought it might be good to ask
at a high level.
Does this encrypt only the RTSP part of the conversation? Is the video
still in the clear?
I know there are 3 ways to stream in live555, TCP interleave, tunneled and
UDP.
Did we get SRTP and SRTCP in this
I don’t recommend checking for timeouts at such a low level in the codfe,
because this will complicate the normal (common-case) running of the code, and
because timeouts (and/or other failures) of RTSP/RTP connections can occur at
many different levels (e.g., closure of the RTSP TCP session by
“A day that will live in infamy” :-)
I have just released a new version (2019.12.07) of the “LIVE555 Streaming
Media” code that adds support to "RTSPClient" for connecting to the server via
TLS (encrypted TCP). “RTSPClient” will now connect via TLS if the URL begins
with "rtsps://", or if the
hi,i am using live555 (testRTSPClient) inside my program to get frame from
camera. sometime network connection may lost i want to resume capturing frame
from camera.
is 6 millisecond good for timeout?
beacause my network has some failure rapidly on some time and if they occur in
one 6
