[Live-devel] problem choosing HTTP port for live555ProxyServer -- for output not input

2018-06-07 Thread Steve Morton
I'm following up my earlier question about using the -T option with live555ProxyServer to change its http port. I see the problem. I mistakenly thought the -T option affected the output like -p does. But I misread the spec because I now see that it only affects the input stream. Wish List: It

[Live-devel] problem choosing HTTP port for live555ProxyServer

2018-06-07 Thread Steve Morton
I'm following up my earlier question about using the -T option with live555ProxyServer to change its http port. I get endless error messages when I use the -T option, of the form: (We use port 80 for optional RTSP-over-HTTP tunneling.) ...Connection to server failed: Connection refused I don't

[Live-devel] follow-up posting #1 for live555proxyServer

2018-06-01 Thread Steve Morton
Ross, thank you for your quick reply. I'm trying to create a H.264 video stream that looks like it comes from an IP camera using rtsp-and-rtp-tunneled-over-http. I'm not trying to view it in a browser. Since you explained that the stream does not really use http, then it is not feasible to use a

[Live-devel] posting for live555proxyServer

2018-05-31 Thread Steve Morton
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 availab