> Ross, please find attached patch to fix the issue where code in
> RTSPServerRegister.cpp does not continue with OPTIONS, etc after REGISTER.
Thanks for the report. I’ve just installed a new version (2016.11.03) of the
“LIVE555 Streaming Media” code that includes this fix.
Ross Finlayson
Liv
> Still seeing packet loss in the latest release after fixing the bug though.
Never mind, after enabling debugging I see that the TCP send is failing with
WSAEWOULDBLOCK on Windows so we've just increased TCP send buffer sizes.
I do wonder if it would make sense to retry sending the packet on t
Ross, please find attached patch to fix the issue where code in
RTSPServerRegister.cpp does not continue with OPTIONS, etc after REGISTER.
Cheers,
Ralf
--
This message is subject to the CSIR's copyright terms and conditions, e-mail
legal notice, and implemented Open Document Format (ODF) stan
Hi Ross,
> 1. Are there any required API changes for the REGISTER functionality to work
> in the latest version?
Never mind, I found the bug and will submit a patch shortly.
> 2. The reason for the update to the latest live555 was that we were
> investigating packet loss over RTP over RTSP/T
Hi Ross,
We just upgraded our live555 version from 2016.06.26 to 2016.10.21.
After updating, the REGISTER command is still sent to the RTSP client, but the
client no longer
initiates the rest of the RTSP interchange to the server (i.e. OPTIONS,
DESCRIBE, etc).
We have verified this using openRTS
