hope it's more clear now.
On Mon, Feb 22, 2021 at 6:25 PM Ross Finlayson
wrote:
>
>
> > On Feb 22, 2021, at 7:14 AM, Idan Freiberg wrote:
> >
> > That basically means the server acts as a gateway behinds multiple
> backend video sources (RTSP sources). So I nee
Finlayson <
finlay...@live555.com>:
>
>
> > On Feb 22, 2021, at 6:43 AM, Idan Freiberg wrote:
> >
> >
> > I’m writing a reverse RTSP proxy so multiple client will try to access
> different cameras through it.
>
> I’m not sure exactly what you mean by a ‘rev
I’m writing a reverse RTSP proxy so multiple client will try to access
different cameras through it.
בתאריך יום ב׳, 22 בפבר׳ 2021 ב-9:23 מאת Ross Finlayson <
finlay...@live555.com>:
>
>
> > On Feb 21, 2021, at 10:00 PM, Idan Freiberg wrote:
> >
> > Thanks Ross
>
Thanks Ross
I specifically looking for the host address /IP form the requests.
בתאריך יום ב׳, 22 בפבר׳ 2021 ב-0:18 מאת Ross Finlayson <
finlay...@live555.com>:
>
>
> > On Feb 21, 2021, at 1:58 PM, Idan Freiberg wrote:
> >
> > Hello,
> >
> > Is it
Hello,
Is it possible to fetch or extract RTSP requests headers such as
DESCRIBE/OPTIONS/... like getting the *full* URL passed to the server, eg.
DESCRIBE rtsp:///params (including the host part) ?
What’s the best way to achieve this?
Thanks
--
*Idan Freiberg *Software Engineer
Tel. + 972
=640x480&audio=true
And then to get the resolution and audio parameters on demand.
While the /camera/1 URI suffix will be registered earlier at setup time.
Is that possible? How should I implement it?
Thanks in advance,
Idan
--
*Idan Freiberg*
*Software Engineer*
+972-52-2925213 *