Hi, I'm working on an embedded Live streaming platform.
I've cross-compiled live555 with a SoC toolchain, using -DLOCALE_NOT_USED and adjusting compiler name (these are the only changes I made). Now I tried to run testH264VideoStreamer with a test.264 file and using openRTSP tool to receive the stream. ./openRTSP rtsp://192.168.31.102:8554/testStream results in: Opening connection to 192.168.31.102, port 8554... ...remote connection opened Sending request: OPTIONS rtsp://192.168.31.102:8554/testStream RTSP/1.0 CSeq: 2 User-Agent: ./openRTSP (LIVE555 Streaming Media v2015.06.11) followed by some received bytes and requests and finally Received 192 new bytes of response data. Received a complete PLAY response: RTSP/1.0 200 OK CSeq: 5 Date: Mon, Jun 29 2015 17:11:31 GMT Range: npt=0.000- Session: 6C315064 RTP-Info: url=rtsp://192.168.31.102:8554/testStream/track1;seq=46799;rtptime=3977882759 Started playing session but the created openRTSP output file is empty. Using testOnDemandRTSPServer, openRTSP does receive packets, so I guess it's not a problem of firewall settings? What are possible reasons for this behaviour? What are the essential differences between testOnDemandRTSPServer and testH264VideoStreamer regarding the sending and receiving part? What might be system or platform depending factors? (all the streaming samples worked for my typical pc platforms where I already coded a working live image streaming based on testH264VideoStreamer sample server settings) Thanks in advance Michael
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
