Sorry, to keep posting. I think the problem is due to the 400 Bad response from the Setup. This would be a problem on the camera we use and not honoring the OPTION command keepalive. I'l check into this an report back.
Thanks, Craig On 11/17/2013 12:38 PM, Craig Matsuura wrote: I apologize for the last post being so big and the duplicate posting, I moved the log output to pastebin. Ok, I have managed to create the problem where a working camera providing an RTSP stream to the rtsp proxy does not work via the proxy. I downloaded the latest code and compiled it on my laptop and setup the proxy to use the cameras providing my RTSP streams. I tested the proxy stream using gstreamers playbin2 (this has always worked for me) and vlc. Both failed to display my camera. I have other streams setup on the proxy server with the same model of cameras that work great with both playbin2 and vlc. I tried the openRTSP test, but wasn't sure what the expected output should be. (I paste it below). Here is the log out using -V http://pastebin.com/XtM2zHjd OUTPUT FROM oepnRTSP craig@craig-ThinkPad-W530:~/hg/live555-new/testProgs$ ./openRTSP -V rtsp://172.16.10.101:8554/proxyStream-4 Opened URL "rtsp://172.16.10.101:8554/proxyStream-4"<rtsp://172.16.10.101:8554/proxyStream-4>, returning a SDP description: v=0 o=- 1384715305499911 1 IN IP4 172.16.10.101 s=LIVE555 Streaming Media v2013.11.15 i=LIVE555 Streaming Media v2013.11.15 t=0 0 a=tool:LIVE555 Streaming Media v2013.11.15 a=type:broadcast a=control:* a=range:npt=0- a=x-qt-text-nam:LIVE555 Streaming Media v2013.11.15 a=x-qt-text-inf:LIVE555 Streaming Media v2013.11.15 m=video 0 RTP/AVP 96 c=IN IP4 0.0.0.0 b=AS:50 a=rtpmap:96 H264/90000 a=fmtp:96 packetization-mode=1;profile-level-id=64401F;sprop-parameter-sets=J2RAH6wsagFAFumoKDAqAAAH0gAB1MAo,KO4EYsA= a=control:track1 Created receiver for "video/H264" subsession (client ports 40540-40541) Setup "video/H264" subsession (client ports 40540-40541) Created output file: "video-H264-1" Started playing session Receiving streamed data (signal with "kill -HUP 13953" or "kill -USR1 13953" to terminate)... Thanks, Craig On 11/13/2013 04:06 PM, Ross Finlayson wrote: I'm wondering if there is a specific message I can look for in the logs when at level 2 that will indicate if a proxies stream has failed? I'm using the proxyServer example and at times the stream stops streaming. I can see the OPTION commands going out to the camera with a response, but connecting a client to the proxied stream does not work. Not sure if it is due to loosing a connection, but what I find strange is the OPTION command appears to respond. Is there something in the response of the OPTION that indicates a problem? I'm not sure. Why don't you post the diagnostic output (from the proxy server) around the time that "connecting a client to the proxied stream does not work"? (And also, please clarify what "does not work" means). Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
