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 openRTSP. 1. Are there any required API changes for the REGISTER functionality to work in the latest version? 2. The reason for the update to the latest live555 was that we were investigating packet loss over RTP over RTSP/TCP when using the REGISTER approach to circumventing firewalls on the RTSP server side. For testing we used "openRTSP -d 5 -Q -t -R 8555". In our past experience of using live555 streaming over RTSP/TCP, there is not supposed to be any packet loss in the application layer e.g. RTCP Receiver Reports. I did go through the change log and didn't see any changes related to TCP-streaming. What is the expected behaviour of TCP streaming over the REGISTER TCP connection? RTCP RR loss should be zero? I am aware that there may be issues if the bandwidth is not sufficient to support the stream bitrate. Thanks for any help/pointers. Regards, Ralf -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. Please consider the environment before printing this email. _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
