Thanks for the note. The problem was the line "Connection: close” in the server’s response to the HTTP “GET” command. Earlier this year, we changed our RTSP client code to tear down (reset) our TCP connections whenever we see such a response. But that doesn’t make sense when we’re doing RTSP-over-HTTP tunneling, because the (separate) input and output TCP connections that we use for this tunneling need to remain intact throughout the session.
Therefore, I’ve just installed a new version (2016.11.28) of the “LIVE555 Streaming Media” code that should fix this, by ignoring “Connection: close” lines when we’re doing RTSP-over-HTTP tunneling. This should solve your problem. Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
