Joesph,
The stream can be either encoded mp4 or H.264 so since either of those can
be played in most modern browsers no need to re-encode the video.
The thought is that when the video is needed by the particular internal web
page the server will launch the vpn client to connect to the site then
offer it up as a stream for the viewers. Most of the time it will be only a
couple people for a short duration but it could be as many as 50 for hours
at a time.
Based on that I will look into ffserver since restarting it each time isn't
a big deal.
Thanks
On Tue, Sep 8, 2015 at 4:00 PM, Joseph Sinclair <
plug-discussion@stcaz.net>
wrote:
> Assumptions:
> 1) you need audio and video (as RTSP is just a control protocol, either
> or both could be the case)
> 2) You do not need a proprietary input codec (RTSP does not set codec,
> that's a stream detail)
> 3) Any reasonably common container/codec combination will work for your
> clients
> 4) Input source is RTSP with a reasonably "open" container/codec choice
> 5) Output is streamed via RTSP, possibly with transcoding, and
> completely under your control
> 6) Output streams do not need to change sources on the fly
> 7) Each source may be a different output stream
> 8) You have access to a reasonably capable dedicated server (with a
> decent GPU if transcoding is needed) to run the rebroadcast stream service
> 9) You do not have policy restrictions that mandate virtual servers,
> proprietary software, Windows O/S or anything similar
> 10) Security and privacy are important considerations
> 11) All of your clients are purely internal to your organization and
> connected to your internal network (possibly via VPN).
>
> Given those assumptions:
> 1) VLC can do this (although not terribly well), simply open a "network
> stream" source for the input, and choose "stream" from the expansion
> dropdown next to play in the open source dialog and follow the wizard.
> 2) ffserver (https://www.ffmpeg.org/ffserver-all.html) is closer to
> what you're asking for, although it's horribly complex to setup, and each
> stream usually ends up being a separate instance (although this isn't
> required, it's easier due to lack of any way to reconfigure without
> restarting).
> 3) Feng (https://github.com/lscube/feng) may work for what you want,
> but it hasn't been updated in years.
> 4) Nimble Server (https://wmspanel.com/nimble) is *proprietary*
> "freeware" that's almost exactly what you want, but it's closed-source
> nature leaves some questions around security and privacy that you may need
> to consider carefully.
>
>
> On 09/08/2015 02:41 PM, Shawn Badger wrote:
> > I am looking for a way to stream an RTSP stream to a bunch of people
> > internally, so kind of a locally hosted live CDN. I have looked into
> > trying it with VLC but it seems to only stream files.
> > Here are a couple of the base requiremnets that I need to meet:
> >
> > 1. locally hosted
> > 2. CLI to add/remove stream or just control
> > 3. a single connection to the original stream
> >
> >
> > Does anyone know of a way to do this?
> >
> >
> >
> > ---------------------------------------------------
> > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> > To subscribe, unsubscribe, or to change your mail settings:
> > http://lists.phxlinux.org/mailman/listinfo/plug-discuss
> >
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
(text/plain)