Hi Ross, That is what I suspect as well, however I was trying to recover from such an error as it would be nice to be more robust and not fail because of a firmware issue with the camera. I am in the process of having the manufacture look into the issue, however this can be a slow process. I was hoping to be more robust on my side with the live555 and handle such errors. I started to make changes to recover from the 400 error but have a few things to fix as my rtspclient fails after the force restart in the ProxyRTSPClient. If I can solve this I can make our side more robust to failures on camera sources.
Thanks, Craig On 11/03/2013 04:24 AM, Ross Finlayson wrote: Sending request: SETUP rtsp://172.16.10.109/live.sdp/trackID=1 RTSP/1.0 CSeq: 4 User-Agent: ProxyRTSPClient (LIVE555 Streaming Media v2013.10.25) Transport: RTP/AVP;unicast;client_port=60278-60279 Received 37 new bytes of response data. Received a complete SETUP response: RTSP/1.0 400 Bad Request CSeq: 4 OK, so there appears to be a bug in the back-end server. You will need to contact the manufacturer of this server, and ask them to fix this bug. 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
