For the final time: This model of communication is not one that we support, or
endorse using LIVE555.
If you have a proxy server that cannot access a ‘back-end’ camera server (due
to the presence of a firewall), then you can instruct the camera to ‘register’
itself with the proxy server, so tha
: LIVE555 Streaming Media - development & use
Date: Tuesday 13 October 2015 02:23
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] PUSH stream LIVE555
> Thanks for replying.
> I feel a little lost here, might need your a second explanation.
> We don´t wan
> Thanks for replying.
> I feel a little lost here, might need your a second explanation.
> We don´t want to add a second equipment
No, you wouldn’t ‘add’ equipment (or software). Instead, you would *replace*
your existing server (which takes media by ‘pushing’ (a complex and
non-standard mecha
Streaming Media - development & use
Date: Monday 12 October 2015 20:46
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] PUSH stream LIVE555
> I have a camera module that uses LIVE555, and I would like to be able to PUSH
> the rtsp to a external server
No, we
> I have a camera module that uses LIVE555, and I would like to be able to PUSH
> the rtsp to a external server
No, we don’t support that model of communication (‘pushing’ media to a server),
because it’s excessively complex, and non-standard. Instead, we support a
(much simpler) model whereby
I have a camera module that uses LIVE555, and I would like to be able to
PUSH the rtsp to a external server no need any transcoding.
This camera module let me open: rtsp://u:p@ip:port/stream in VLC or record
to a local mount drive.
What I would like to add a simple script that send (PUSH) this RT
