Ross Finlayson wrote:
After doing a bit more digging in the code and on the web I've
discovered that the problem of not receiving RTSP commands after the
play command when using RTP-over-TCP streaming is a known problem
(although it is usually associated with the keep-a-live feature
(cough h
After doing a bit more digging in the code and on the web I've
discovered that the problem of not receiving RTSP commands after the
play command when using RTP-over-TCP streaming is a known problem
(although it is usually associated with the keep-a-live feature
(cough hack
The standard way fo
I found this very good discussion on persistent tcp vs non-persistent
tcp RTSP clients.
http://www.ietf.org/mail-archive/web/mmusic/current/msg00655.html
From reading some of this thread and the live555 RTPSClient code it
appears that the RTSPClient is a persistent tcp client is this true?
H
After doing a bit more digging in the code and on the web I've
discovered that the problem of not receiving RTSP commands after the
play command when using RTP-over-TCP streaming is a known problem
(although it is usually associated with the keep-a-live feature (cough
hack) and not with usages
Ok I've got a little more information.
With respect to problem #2 I've discovered that the server is not
receiving or responding to any RTSP commands once the play command has
been issued when streaming over tcp. In particular I've tested the
TEARDOWN and SET_PARAMETER commands both of which th
