Re: [Live-devel] can't stream - unsupported RTSP server error

2007-09-18 Thread Ross Finlayson
The instructioins say media file must be stored in the current working directory. What is the current working directory? The directory from which you launch the "live555MediaServer" application. My Live server is saved in /root. Note that the application need not be (and, to be on the safe

Re: [Live-devel] can't stream - unsupported RTSP server error

2007-09-18 Thread yyang
Ross, > The real error is the "404 Stream Not Found" error from the RTSP server. The "LIVE555 Media Server" returns this error because it does not support >".avi" files. >See for a description of the types of files that can be streamed by the "LIVE555 Med

Re: [Live-devel] can't stream - unsupported RTSP server error

2007-09-18 Thread yyang
Ross, The instructioins say media file must be stored in the current working directory. What is the current working directory? My Live server is saved in /root. Frank Ross Finlayson <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 09/18/2007 04:41 PM Please respond to LIVE555 Streaming Medi

Re: [Live-devel] can't stream - unsupported RTSP server error

2007-09-18 Thread Ross Finlayson
But when I ran mplayer stream. I got the "unsupported RTSP server" error as below. Any idea what's wrong? The real error is the "404 Stream Not Found" error from the RTSP server. The "LIVE555 Media Server" returns this error because it does not support ".avi" files. See

[Live-devel] can't stream - unsupported RTSP server error

2007-09-18 Thread yyang
Hi, I have two FC6 boxes. One is named server the other called workstation. They are back to back connected via a Gigabit ethernet link. There is no switch, router or any firewall in between. The network connectivity between them works fine ( I can ping, I can mount a directory using nfs, etc

Re: [Live-devel] RTSP Server 'Keep Alive' support

2007-09-18 Thread Ross Finlayson
>Further to my previous questions on this. I'm wondering how to activate >this feature It is activated by default! You already have it. Our server does not set the "timeout=" field in its responses (because it uses incoming RTCP "RR" packets, as well as incoming RTSP commands, to indicate cl

Re: [Live-devel] RTSP Server 'Keep Alive' support

2007-09-18 Thread Glen Gray
Sorry, meant to say Session field not Transport field in the below paragraph Glen Gray wrote: > SETUP is to populate the Transport: field with the timeout period in > seconds ("...; timeout=60;"). I can't see this in the RTSPServer.cpp > code (lines 797 - 838 is where I looked) or in the response

Re: [Live-devel] RTSP Server 'Keep Alive' support

2007-09-18 Thread Glen Gray
Hey guys, Further to my previous questions on this. I'm wondering how to activate this feature and I'm still not sure on the standards as it's not my area of expertise. From what I can see in RFC2326, the servers response to SETUP is to populate the Transport: field with the timeout period in

Re: [Live-devel] Pipelined request Seg Fault

2007-09-18 Thread Ross Finlayson
Thanks for sending the debug trace. However, I'm puzzled by this, because (for now, at least) I can't see how it is possible (in the current version of the code) for the server to receive two "DESCRIBE" commands in succession, without sending a response to the first command inbetween. (I assu