My objectives for using the live555ProxyServer are to create
rtsp-and-rtp-tunneled-over-http H.264 video streams that can traverse
firewalls using a single, statically chosen public port, and so that I
can use a Cloud-based, Apache web server as a http proxy server to make
that http stream available to multiple viewing clients on the Internet
simultaneously.
I'm having several problems. This post is a bit wordy but I'm trying to
be clear what is doing what to whom.
As a first step to get this to work, my H.264 video source, rtsp server
(CVLC), and live555ProxyServer are all on one linux machine, my viewing
client (VLC) is on a PC, and all are on the same LAN. As root, I'm using
this command (with a capital V) to run live555ProxyServer
(v2017.10.28):
/home/live/proxyServer/live555ProxyServer -V
rtsp://127.0.0.1:9554/
I choose 9554 for my source to avoid conflicts by live555ProxyServer for
its default rtsp ports, 554 and 8554. I have a web server on port 8000,
which is one of the two (or possibly three, including 8080 ?) default
http ports used by live555ProxyServer, but port 80 is available. I can
see in netstat -a -n that port 80 is used when live555ProxyServer is
active. BTW: I could not use just
rtsp://:9554/ as a source, I
had to add 127.0.0.1, and I had to use a trailing /.
Problems are:
1)
live555ProxyServer keeps adding a new track, for no obvious reason, about
once a minute when I view proxyStream in the VLC viewing client, causing
VLC to stop playing the stream, from which it does not automatically
resume playing. (I'm not using tunneling with the VLC viewing client for
this test.) In contrast, the VLC viewing client can display the stream
for long periods when it accesses the stream that is input to
live555ProxyServer. The message I get whenever viewing proxyStream drops
out, is:
ProxyServerMediaSession[rtsp://127.0.0.1:9554/]
added new "ProxyServerMediaSubsession" for RTP/video/H264
track
Why does live555ProxyServer keep adding a new subsession, and how
do I stop it so VLC does not keep dropping out ?
2) I
cannot view the stream when I change the rtsp server port used by
live555ProxyServer. I use this command:
/home/live/proxyServer/live555ProxyServer -V -p 10000
rtsp://127.0.0.1:9554/
netstat -a -n reports that port 10000 is in use when live555ProxyServer
is active.
3)
live555ProxyServer reports connection to server failed, connection
refused, when I try to change the http server port used by
live555ProxyServer, so I am not able to change the http port. I use this
command:
/home/live/proxyServer/live555ProxyServer -V -T 8100
rtsp://127.0.0.1:9554/
How can I change the http port ?
4) When I
configure the VLC viewing client to tunnel using http (tools >
preferences > show settings all > input / codecs > demuxers >
rtp/rtsp > check (only) tunnel rtsp over http, and keep the default
http tunneling port of 80), I can view the stream on my LAN using
rtsp://<live555ProxyServer ip
address on my LAN>/proxyStream. However, I cannot view it using a
http:// URL. What http URL should
I use ? And, if I pass the tunneling port of 80 through my router, for
both tcp and udp, to the Internet, I cannot view the stream from the
Internet, so http tunneling does not seem to be working after all. How do
I fix this ?
5) If http
tunneling were working and I pass it through my router using a single
static port number, presumably using only tcp, what http URL would I tell
a distant apache web server to proxy ? The proxy only works for http
URL's not rtsp. I know that apache can proxy http traffic because I use
it all the time. It is essential that I be to do such proxying due to
IP-routing limitations of my source.
6) Is
there a way for live555ProxyServer to take a stream from a pipe instead
of a rtsp server to avoid the delay in the first rtsp server in the
current pipeline ?
Thank you in advance for your help.
-- NewtownGuy
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
