[Live-devel] Failed to read response: Success

[Scott Hays]

I've done some tracing, and what I've found is that my server isn't receiving 
certain commands from the client (openRTSP).  With the -O option, everything 
seems to work until openRTSP sends PLAY; the event handler in 
RTSPClientSession never gets called again, so it doesn't process that 
command, thus responding and never starting to play the stream.  Without -O, 
the same thing happens when the client sends OPTIONS; the server never seems 
to receive it.  The event loop continues normally; it just seems that select 
never detects data waiting on that socket.  

I realize that this is a pretty specific issue, so no one may have an answer, 
but I'm just wondering if anyone else has come across something like this (or 
has any intuition about this problem).  Any suggestions would be appreciated.

Scott

On Thursday 12 May 2005 18:02, Ross Finlayson wrote:
> >The rest of the server is derived directly from testMPEG4VideoStreamer.
>
> That's OK, provided that you want to stream via multicast.  However, the
> following line
>
> >c=IN IP4 127.0.0.0/255
>
> in the returned SDP description indicates that you are not using a correct
> multicast address.
>
> (If instead you want to stream via unicast, use "testOnDemandRTSPServer" as
> a model.)
>
> However, I don't know whether this multicast address issue is causing your
> problem.  But remember, You Have Complete Source Code.  You can trace
> through "RTSPServer.cpp" to figure oout why it's not handling (and
> responding to) the "SETUP" command properly.  (Compare its execution to
> that of "testMPEG4VideoStreamer", which you know works correctly.)
>
>
> 	Ross Finlayson
> 	LIVE.COM
> 	<http://www.live.com/>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live.com
> http://lists.live.com/mailman/listinfo/live-devel