Olivier,
Thanks for reporting this.
In a recent release, we accidentally included code that turns out to be
non-portable (across all Unix-like systems).
I will shortly be releasing a new version of the code that fixes this.
In the meantime, you can fix the problem by replacing the four lines
--- Begin Message ---
Hello
I tried to build live555 on :
- my ubuntu 20.4 box
- my ubuntu 20.4 VPS
First, I got an error because some ssl headers where missing but this
was easily fixed,
either by installing openssl or by "genMakeFile linux-no-openssl"
But then, I got another one that I coul
SungHwan,
We don’t support the “Require:” header in “openRTSP” (or in our RTSP client
implementation in general), as it is rarely, if ever, used. I know of no RTSP
server that recognizes/handles this header.
What specific feature do you want to ask for (in a “Require:” header in a
“SETUP” req
> On Nov 26, 2020, at 11:30 PM, Лисовой Андрей Витальевич
> wrote:
>
> Hi!
>
> I found bug (using live.2018.02.18, but in 2020.06.25 RTPInterface.cpp is the
> same).
First, you should always try to use the latest version of the code (currently,
2020.11.26)
> It occures when proxyServer u
Hi All,
I would like to know how to request a openRTSP command with "Require" parameter
as OPTIONS.
Could you give me some advice?
I found the below article from RFC2326, but I have no idea how to apply this
kind of option to openRTSP command.
---
Hi!
I found bug (using live.2018.02.18, but in 2020.06.25 RTPInterface.cpp is the
same).
It occures when proxyServer used with -t flag (RTP-over-TCP with backend
server).
In some cases, like client disconnects or reconnects, backend socket
deregistering RTP channels, and only RTCP channels have
