[Live-devel] live-devel Digest, Vol 121, Issue 12
Ognjen Milosavljević
ognjenm at rcub.bg.ac.rs
Fri Nov 15 04:03:08 PST 2013
Hi,
Thank for replay.
Comments are in line.
> -----Original Message-----
> From: live-devel-bounces at ns.live555.com [mailto:live-devel-
> bounces at ns.live555.com] On Behalf Of live-devel-request at ns.live555.com
> Sent: 14. novembar 2013 22:29
> To: live-devel at ns.live555.com
> Subject: live-devel Digest, Vol 121, Issue 12
>
> Send live-devel mailing list submissions to
> live-devel at lists.live555.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.live555.com/mailman/listinfo/live-devel
> or, via email, send a message with subject or body 'help' to
> live-devel-request at lists.live555.com
>
> You can reach the person managing the list at
> live-devel-owner at lists.live555.com
>
> When replying, please edit your Subject line so it is more specific than
"Re:
> Contents of live-devel digest..."
>
>
> Today's Topics:
>
> 1. Re: VLC and The LIVE555 Proxy Server (Ross Finlayson)
> 2. Unable to proxy an rtsp stream on alternate port (Dan Desjardins)
> 3. Re: Unable to proxy an rtsp stream on alternate port
> (Ross Finlayson)
> 4. Re: Unable to proxy an rtsp stream on alternate port
> (Dan Desjardins)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 14 Nov 2013 09:04:27 -0800
> From: Ross Finlayson <finlayson at live555.com>
> To: LIVE555 Streaming Media - development & use
> <live-devel at ns.live555.com>
> Subject: Re: [Live-devel] VLC and The LIVE555 Proxy Server
> Message-ID: <322C57CD-B03D-4E33-88AA-04605439A790 at live555.com>
> Content-Type: text/plain; charset="iso-8859-2"
>
> > When I try to restream, rtsp stream from VLC, I get these messages on
> LIVE555 Proxy Server:
> >
> > ProxyRTSPClient["rtsp://XXX"]: RTSP "DESCRIBE" command failed; trying
> > again in 1 seconds Opening connection to YYY, port ZZZ...
> > ...Connection to server failed: Connection timed out
> [...]
> > Also I confirmed streaming from VLC with VLC on the other pc and it was
> working fine, I could see the stream.
> >
> > VLCs and LIVE555 Proxy Server are in the same VLAN so there is no
> problem with firewall or filtering (I disabled firewall on all server and
pc).
>
> Sorry, but I can't explain this. VLC (when used as a RTSP client) uses
our
> RTSP client implementation - as does the "LIVE555 Proxy Server" - so I
don't
> understand why the proxy server would be failing to connect to the 'back-
> end' server, but VLC succeeds.
>
> What happens when you try connecting to the stream using our
> "testRTSPClient" or "openRTSP" demo applications?
[OM] Here are the outputs:
./testRTSPClient rtsp://X:Y/stream
Opening connection to X, port Y...
...Connection to server failed: Connection timed out
[URL:"rtsp://X:Y/stream"]: Failed to get a SDP description: Connection to
server failed: Connection timed out
[URL:"rtsp://X:Y/stream"]: Closing the stream.
./openRTSP rtsp://X:Y/stream
Opening connection to X, port Y...
...Connection to server failed: Connection timed out
Opening connection to X, port Y...
...Connection to server failed: Connection timed out
Failed to get a SDP description for the URL "rtsp://X:Y/stream": Connection
to server failed: Connection timed out
X is beck-end server IP address, Y port. I am using VLC 2.0.8 as backend
server.
Regards,
Ognjen
>
>
> Ross Finlayson
> Live Networks, Inc.
> http://www.live555.com/
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.live555.com/pipermail/live-
> devel/attachments/20131114/77ebd8a8/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 14 Nov 2013 13:16:07 -0600
> From: Dan Desjardins <dan.desjardins at weather.com>
> To: live-devel at ns.live555.com
> Subject: [Live-devel] Unable to proxy an rtsp stream on alternate port
> Message-ID:
> <CAELg6uiyYEeky7BitX13yYRZ3YyrYMD7QfLJHxt+DwWkC0XEyg at mail
> .gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I have successfully compiles the LIVE555ProxyServer and it works great
with
> one exception. If I attempt to proxy a stream that originates on a port
> other than 554 it does not appear to work.
> My command line is:
>
> live555proxyserver -u username password rtsp://<ip
> address>:9494/axis-media/media.amp?streamprofile=Balanced
>
> The proxyserver indicates that I can "Play this stream using the URL:
> rtsp://<ip address>/proxyStream
>
> But vlc never successfully connects. I can connect to the rtsp stream
> directly with vlc (though it takes about 12 seconds to connect) but the
> connection through the proxy appears to time out. Here are the error
> messages I get:
>
> ProxyServerMediaSession["rtsp://*<ip address>*:9494/axis-
> media/media.amp/"]
> added
> new "ProxyServerMediaSubsession" for RTP/video/H264 track
> ProxyServerMediaSubsession["H264"]::createNewStreamSource(session id
> 0)
> Initiated: ProxyServerMediaSubsession["H264"]
> ProxyServerMediaSubsession["H264"]::createNewRTPSink()
> ProxyServerMediaSubsession["H264"]::closeStreamSource()
> ProxyServerMediaSubsession["H264"]::createNewStreamSource(session id
> 3001992683)
>
> ProxyServerMediaSubsession["H264"]::createNewRTPSink()
> ProxyServerMediaSubsession["H264"]::closeStreamSource()
> ProxyServerMediaSubsession["H264"]::createNewStreamSource(session id
> 1100823848)
>
> ProxyServerMediaSubsession["H264"]::createNewRTPSink()
> ProxyServerMediaSubsession["H264"]::closeStreamSource()
>
> If it is just a timeout issue can I extend the timeout? Where would I do
> that?
>
> * Dan **Desjardins *| *senior technology manager*
> * w:* 608 236 4399 *e:* dan.desjardins at weather.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.live555.com/pipermail/live-
> devel/attachments/20131114/50292382/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 14 Nov 2013 12:27:54 -0800
> From: Ross Finlayson <finlayson at live555.com>
> To: LIVE555 Streaming Media - development & use
> <live-devel at ns.live555.com>
> Subject: Re: [Live-devel] Unable to proxy an rtsp stream on alternate
> port
> Message-ID: <0CD7ECC3-09F3-4AC8-A20E-A1CB00BB346C at live555.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> > I have successfully compiles the LIVE555ProxyServer and it works great
> with one exception. If I attempt to proxy a stream that originates on a
port
> other than 554 it does not appear to work.
>
> That's strange; I wonder if it could be a firewall problem? I.e., maybe
you
> have a firewall - sitting between the proxy server and the back-end server
-
> that is blocking UDP packets? But that wouldn't explain the problem if
the
> *only* difference between a working back-end server and a non-working
> back-end server is its port number. But I suspect that - in reality - the
RTSP
> port number is *not* the only difference between these two streams :-)
>
> Does the "DESCRIBE" command - sent from the proxy server to the back-end
> server - still work successfully when the back-end server uses a port
other
> than 554?
>
>
> > I can connect to the rtsp stream directly with vlc (though it takes
> > about 12 seconds to connect)
>
> This suggests that you do, indeed, have a problem with receiving UDP
> (because VLC works by first requesting regular RTP-over-UDP streaming, and
> then - if it fails to receive packets within several seconds - requesting
RTP-
> over-TCP streaming instead; that would explain the long delay).
>
> To test this:
>
> NOTE TO EVERYONE: If you want to test a RTSP stream, you should do so
> first using our client applications: "testRTSPClient" and/or "openRTSP".
> Only after you have gotten those to work should you then try using VLC.
> (VLC is not our software.)
>
> Try running "openRTSP -n rtsp://<ip address>:9494/axis-media/media.amp",
> and see whether it reports that "Data packets have begun arriving". If it
> doesn't, then try again, but this time adding the "-t" option to
"openRTSP"
> (to request RTP-over-TCP streaming).
>
> If the "-t" option to "openRTSP" works, then the "LIVE555 Proxy Server"
> should also work (with this back-end stream) if you give it the "-t"
option
> also.
>
>
> Ross Finlayson
> Live Networks, Inc.
> http://www.live555.com/
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.live555.com/pipermail/live-
> devel/attachments/20131114/999f34d7/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 14 Nov 2013 15:28:46 -0600
> From: Dan Desjardins <dan.desjardins at weather.com>
> To: "LIVE555 Streaming Media - development & use"
> <live-devel at ns.live555.com>
> Subject: Re: [Live-devel] Unable to proxy an rtsp stream on alternate
> port
> Message-ID:
> <CAELg6uh8+UY7KC=UMM3bfSWzBxJ1Y8wYz1ska-
> _WQKH+GKmutg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Perfect - yes the openrtsp.exe was able to open the stream from the camera
> on the alternate port without any problem at all. I went ahead and added
> the -t to the proxy stream and tried again in VLC and it immediately
opened.
> I was worried because my receiver/decoder (providing HDSDI output with
> genlock) is actually VLC based. This works a treat!
> Thanks for your help!
>
> Des
>
>
> * Dan **Desjardins *| *senior technology manager*
> * w:* 608 236 4399 *e:* dan.desjardins at weather.com
>
>
>
> On Thu, Nov 14, 2013 at 2:27 PM, Ross Finlayson
> <finlayson at live555.com>wrote:
>
> > I have successfully compiles the LIVE555ProxyServer and it works great
> > with one exception. If I attempt to proxy a stream that originates on
a
> > port other than 554 it does not appear to work.
> >
> >
> > That's strange; I wonder if it could be a firewall problem? I.e.,
> > maybe you have a firewall - sitting between the proxy server and the
> > back-end server - that is blocking UDP packets? But that wouldn't
> > explain the problem if the *only* difference between a working
> > back-end server and a non-working back-end server is its port number.
> > But I suspect that - in reality - the RTSP port number is *not* the
> > only difference between these two streams :-)
> >
> > Does the "DESCRIBE" command - sent from the proxy server to the
> > back-end server - still work successfully when the back-end server
> > uses a port other than 554?
> >
> >
> > I can connect to the rtsp stream directly with vlc (though it takes
> > about
> > 12 seconds to connect)
> >
> >
> > This suggests that you do, indeed, have a problem with receiving UDP
> > (because VLC works by first requesting regular RTP-over-UDP streaming,
> > and then - if it fails to receive packets within several seconds -
> > requesting RTP-over-TCP streaming instead; that would explain the long
> delay).
> >
> > To test this:
> >
> > NOTE TO EVERYONE: If you want to test a RTSP stream, you should do so
> > first using our client applications: "testRTSPClient" and/or "openRTSP".
> > Only after you have gotten those to work should you then try using VLC.
> > (VLC is not our software.)
> >
> > Try running "openRTSP -n rtsp://<ip
> > address>:9494/axis-media/media.amp",
> > and see whether it reports that "Data packets have begun arriving".
> > If it doesn't, then try again, but this time adding the "-t" option to
> "openRTSP"
> > (to request RTP-over-TCP streaming).
> >
> > If the "-t" option to "openRTSP" works, then the "LIVE555 Proxy Server"
> > should also work (with this back-end stream) if you give it the "-t"
> > option also.
> >
> >
> > Ross Finlayson
> > Live Networks, Inc.
> > http://www.live555.com/
> >
> >
> > _______________________________________________
> > live-devel mailing list
> > live-devel at lists.live555.com
> > http://lists.live555.com/mailman/listinfo/live-devel
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.live555.com/pipermail/live-
> devel/attachments/20131114/afc2fa28/attachment.html>
>
> ------------------------------
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
>
>
> End of live-devel Digest, Vol 121, Issue 12
> *******************************************
More information about the live-devel
mailing list