On 09/10/2014 11:28 PM, Gilles Chanteperdrix wrote:
> RTSP/1.0 400 Bad Request
> Date: Wed, Sep 10 2014 21:21:50 GMT
> Allow: OPTIONS, DESCRIBE, SETUP, TEARDOWN, PLAY, PAUSE, GET_PARAMETER,
> SET_PARAMETER
Also, the Bad Request answer does not have a CSeq, which causes an RTSP
client to complain.
On 07/09/2014 06:00 AM, Ross Finlayson wrote:
> Actually, thinking about this a bit more - I'm going to include your
> 'hack' in the next release of the "LIVE555 Streaming Media" software,
> because it's generally useful - for any type of file - if the
> underlying file has changed since the last t
> I have a streaming source that already provides me with a h264 RTP stream and
> would like to use live555 just as a RTSP server.
> I require neither RTP packetization nor RTCP generation.
> The ideal use case would be to be able to run custom scripts on events that
> represent RTSP commands, an
I have a streaming source that already provides me with a h264 RTP stream and
would like to use live555 just as a RTSP server.
I require neither RTP packetization nor RTCP generation.
The ideal use case would be to be able to run custom scripts on events that
represent RTSP commands, and be able
