less for the case at hand.
- Original Message -
From: "Ross Finlayson"
To: "LIVE555 Streaming Media, development & use"
Sent: Wednesday, August 14, 2024 6:51:11 AM
Subject: Re: [Live-devel] Live555 Proxy add/remove frequently
Unfortunately I have not been able to reproduce thi
Unfortunately I have not been able to reproduce this issue.
Could you try running your proxy server under valgrind:
cd live; make clean; ./genMakefiles linux-gdb; make
valgrind your-proxy-server-application
and email us the output if you see the crash.
Ross Finlayson
Live Network
> On Aug 13, 2024, at 2:15 AM, Gous Mulla via live-devel
> wrote:
>
> Even though there's a lock in place, we're making sure to invoke live555
> functions from a single application thread.
OK, and that needs to be the same thread that runs the proxy server itself - in
other words, the whole
evelopment & use
Subject: Re: [Live-devel] Live555 Proxy add/remove frequently
External email: Use caution opening links or attachments
Whoa! Why are you using 'mutex'es? I hope this doesn't mean that you are
calling LIVE555 code from more than one thread? You absolutely can
Whoa! Why are you using ‘mutex’es? I hope this doesn’t mean that you are
calling LIVE555 code from more than one thread? You absolutely cannot do this;
a LIVE555-based application must be single-threaded, using an event loop
(rather than threads) to provide concurrency. See
http://live555.c
ion(sms);
}
}
}
delete iter;
}
Thanks & Regards,
Gous Mulla
Senior Software Engineer, Nvidia
http://www.nvidia.com/
-Original Message-
From: live-devel On Behalf Of Ross Finlayson
Sent: Tuesday, August 13, 2024 10:45 AM
To: LIVE555 Streaming Media - developm
> On Aug 12, 2024, at 9:55 PM, Gous Mulla via live-devel
> wrote:
>
> We’ve confirmed that the same crash occurs in the latest live version,
> 2024.08.01.
OK, it looks like there is a bug in the LIVE555 code that is causing this,
because it should be OK for a (proxy) server to delete - usi
12, 2024 8:11 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Live555 Proxy add/remove frequently
External email: Use caution opening links or attachments
On Aug 12, 2024, at 3:24 AM, Gous Mulla via live-devel
mailto:live-de...@us.live555.com>> wrot
> On Aug 12, 2024, at 3:24 AM, Gous Mulla via live-devel
> wrote:
>
> We are using the Live555 Proxy Server, live version 2023.07.24.
Sorry, but only the latest version of the code is supported; see
http://live555.com/liveMedia/faq.html#old-versions
Ross Finlayson
Live Networks, Inc.
http:
--- Begin Message ---
Hi,
We are using the Live555 Proxy Server, live version 2023.07.24.
In our use case, we frequently add RTSP proxy URLs using
ProxyServerMediaSession::createNew and remove them with
deleteServerMediaSession(sms).
However, we encounter occasional crashes during the proxy rem
> On Aug 11, 2023, at 9:23 PM, Gous Mulla via live-devel
> wrote:
>
>
> Hi,
> We are using Proxy Server from Live555 version - 2021.12.07
Sorry, but we support only the latest version of the code; see
http://live555.com/liveMedia/faq.html#latest-version
http://live555.com/l
--- Begin Message ---
Hi,
We are using Proxy Server from Live555 version - 2021.12.07
As per our understanding, Proxy server sends its own time (System time) as a
part of Sender Report.
Is there any provision for Proxy Sever to forward Sender Report received from
backend Rtsp-Server (Camera Tim
> We are using LIve555 proxy server to generate proxy RTSP stream. Its getting
> generated in format
> rtsp://ipaddress/proxystream-1
>
> Is there any way I can format the RTSP proxy stream so that it will be
> generated in following format:
> rtsp://[testRTSP]/proxystream-[anyID]
> here [testRT
--- Begin Message ---
Good Day,
We are using LIve555 proxy server to generate proxy RTSP stream. Its
getting generated in format
*rtsp://ipaddress/proxystream-1*
Is there any way I can format the RTSP proxy stream so that it will be
generated in following format:
*rtsp://[testRTSP]/proxystream-[a
>>> 1) The proxyserver reconnects to the source, but no data frames are
>>> forwarded to the clients.
>>
>> If no data are forwarded to the (‘front-end’) clients, then that must mean
>> that the ‘back-end’ server was not sending any data to the proxy server. If
>> the ‘back-end’ server appears r
> The proxy server only creates a whole new RTSP session under certain
> conditions, for example while waiting for an "OPTIONS" liveness reply.
> If the RTSP TCP session is interrupted when there is no pending
> request, the proxy server instead silently reconnects before sending
> the next request
>>
>> To reproduce the issue:
>> - Restart 'back end' server
>> - RTSP proxy will reconnect, and reuse the previous SESSION identifier
>> for PLAY / PAUSE, assuming the session is still valid
>> - 'Back end' server incorrectly accepts this, although the SESSION has
>> not been setup
>
> I don’t und
> It turns out that the sequence of SESSION identifiers is the same each
> time the 'back end' server's RTSP deamon is restarted, presumably
> because dome device unique constant such as serial number or MAC is
> used as random seed for the session identifiers.
>
> To reproduce the issue:
> - Rest
>> 1) The proxyserver reconnects to the source, but no data frames are
>> forwarded to the clients.
>
> If no data are forwarded to the (‘front-end’) clients, then that must mean
> that the ‘back-end’ server was not sending any data to the proxy server. If
> the ‘back-end’ server appears respons
> Actually, all of the client’s ‘request queues’ should be reset by
> “RTSPClient::reset()”.
>
> I’ve now installed a new version (2016.09.08) of the “LIVE555 Streaming
> Media” code that fixes this.
Thanks a lot, Ross!
I did some extended testing by modifying one of the 'back-end' devices
to r
> Should the fRequestsAwaitingResponse queue be cleared by
> RTSPClient::reset to prevent this?
>
> Or, should the fRequestsAwaitingConnection queue be cleared in
> RTSPClient::reset?
Actually, all of the client’s ‘request queues’ should be reset by
“RTSPClient::reset()”.
I’ve now installed a n
Regarding issue 2)
>> the state for the stream has timed out, and the proxy server then attempts
>> to re-open a RTSP connection to the ‘back-end’ server. However, this appears
>> to be hanging - again, apparently due to your ‘back-end’ server being broken.
>The issue is triggered when there is n
Thanks Ross,
Regarding issue 1)
You might be right, I'll try to reproduce while recording network traffic.
Regarding issue 2)
> the state for the stream has timed out, and the proxy server then attempts to
> re-open a RTSP connection to the ‘back-end’ server. However, this appears to
> be hangi
> Most of the time, the proxy server reconnects to the source after a
> loss of connection to a source, but every now and then I observe one
> of the following issues:
In each case, the problem (from what I can tell) seems to be the fault of the
‘back-end’ server - i.e., it seems to be broken.
Hi,
Most of the time, the proxy server reconnects to the source after a
loss of connection to a source, but every now and then I observe one
of the following issues:
1) The proxyserver reconnects to the source, but no data frames are
forwarded to the clients.
An example log of scenario 1) is paste
>> By the way, I think there might be a bug in the handling of the
>> periodic liveness commands:
> No, the periodic ‘liveness’ commands are intended to test that the TCP
> connection is still alive, and also to compensate for a large number of
> servers that require these periodic commands in te
Thanks. From this I was able to figure out the bug in our proxy server code,
and have now installed a new version of the “LIVE555 Streaming Media” code that
should fix it.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel ma
> By the way, I think there might be a bug in the handling of the
> periodic liveness commands:
> If an OPTIONS response is never received,
> ProxyRTSPClient::continueAfterLivenessCommand is never called, and the
> next liveness command will never be scheduled.
No, the periodic ‘liveness’ commands
> OK, I still can’t quite figure out what’s going wrong here, but I think I’m
> getting closer. I’ve just installed a new version (2016.03.16) of the code
> that adds some extra checking, and some more ‘internal error’ debugging
> fprintf()s. > Please run this new version, and let me know if yo
> What would be a good way to modify the proxy server such that:
> 1. The connection to a proxied server is torn down and setup again if
> the server is not sending any data
> 2. The connection to a proxied server is torn down and setup again if
> there is a mismatch between "Session" expected by t
> OK, I still can’t quite figure out what’s going wrong here, but I think I’m
> getting closer. I’ve just installed a new version (2016.03.16) of the code
> that adds some extra checking,
> and some more ‘internal error’ debugging fprintf()s. Please run this new
> version, and let me know if y
OK, I still can’t quite figure out what’s going wrong here, but I think I’m
getting closer. I’ve just installed a new version (2016.03.16) of the code
that adds some extra checking, and some more ‘internal error’ debugging
fprintf()s. Please run this new version, and let me know if you see any
>> I still don’t know how/why this can occur, but I’ve just released a new
>> version (2016.01.24) of the code that adds some ‘INTERNAL ERROR’ messages if
>> the queue gets into an inconsistent state. Should you see any of these
>> messages, please let us know.
>>
> I noticed one of the prints
2016-01-24 22:22 GMT+01:00 Ross Finlayson :
>> On Jan 12, 2016, at 1:48 PM, Erik Montnemery wrote:
>>
>> I'm using the live555ProxyServer to be able to reliably record and view
>> streams from four cheap cameras concurrently.
>> Recording is done in 15 minute chunks with 15 seconds of overlap, me
> On Jan 12, 2016, at 1:48 PM, Erik Montnemery wrote:
>
> I'm using the live555ProxyServer to be able to reliably record and view
> streams from four cheap cameras concurrently.
> Recording is done in 15 minute chunks with 15 seconds of overlap, meaning
> there will normally be between 4-8 acti
The important thing to realize about the proxy server is that it sends the
*exact* same packet contents (for both RTP and RTCP), regardless of how many
‘front-end’ clients there are for a stream. In other words, the only
difference between having one front-end client and having two front-end cl
Hi,
I'm using the live555ProxyServer to be able to record and view streams from
four cheap cameras concurrently.
Version of live555ProxyServer is 2015.12.22
There seems to be something strange going on when an additional client
connects a stream which is already being played by another client.
Re
I will no longer accept - nor respond to - any posting to this mailing list
that mentions “RTP timestamps”.
As I have explained numerous times, users of the “LIVE555 Streaming Media”
software should never need to concern themselves with “RTP timestamps”, because
the software automatically conve
As mentioned earlier, I'm using the live555ProxyServer to be able to record
and view streams from four cheap cameras concurrently.
There seems to be something strange going on when an additonal client
connects to an already active proxied stream.
The stream is h264+aac.
After some testing it seem
Thanks for the report. At first glance, I can’t figure out why this is
happening, but I’ll keep it in mind. (If anyone can provide more details about
what/how this is happening, please let us know.)
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_
I'm using the live555ProxyServer to be able to reliably record and view
streams from four cheap cameras concurrently.
Recording is done in 15 minute chunks with 15 seconds of overlap, meaning
there will normally be between 4-8 active clients for the 4 proxied streams.
The live 555 version is 2015.1
> Is there any possibility to log or add in debug access log in Proxy Server? I
> looked for it in code but I didn't find it.
>
> I consider to log (for some stats): date/timestamp, client IP, client UA,
> response code (maybe something else). What do you think about it?
If you add
#define DEBU
Dear all,
Is there any possibility to log or add in debug access log in Proxy
Server? I looked for it in code but I didn't find it.
I consider to log (for some stats): date/timestamp, client IP, client
UA, response code (maybe something else). What do you think about it?
Best,
--
Dariusz J
> I have a 15fps recoreded video file,
> but live555 is streaming it with 30fps (VLC stats). VLS show fast
> forward video.
http://www.live555.com/liveMedia/faq.html#my-file-doesnt-work
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
l
Hello,
I am new in live555 development. I am using live555 proxy server for
streaming live and recorded video. I am able to stream recorded video,
but facing an issue with that. I have a 15fps recoreded video file,
but live555 is streaming it with 30fps (VLC stats). VLS show fast
forward video.
I
> Please, i have the following:
> a RTSP Back end server (Vod) that contin about 50Video's
> 2. Live555 Proxy server in front of it
> but i'm obligated to put akll the 50 movie's into the url list, is there a
> way to put Live555 Proxy Server to proxy a single ip for any rtsp query?
No, not with
Hello,
Please, i have the following:
a RTSP Back end server (Vod) that contin about 50Video's
2. Live555 Proxy server in front of it
but i'm obligated to put akll the 50 movie's into the url list, is there a way
to put Live555 Proxy Server to proxy a single ip for any rtsp query?
Thank
> if the back-end stream has failed, proxy server only send "SETUP" and "PLAY"
> to it, which usually does NOT work. e.g., if a camera rebooted and proper
> security is enforced, it will return 403 or 401 on "SETUP" without "DESCRIBE".
Yes, you're correct - restarting the connection by sending
if the back-end stream has failed, proxy server only send "SETUP" and "PLAY" to
it, which usually does NOT work. e.g., if a camera rebooted and proper
security is enforced, it will return 403 or 401 on "SETUP" without "DESCRIBE".
___
live-devel maili
> I have issue with multiple connections to RTSP proxy:
> only one client works fine, if i connect second, the 1st freezes...
> Compiled from latest sources
>
> Same as in this thread:
> http://www.mail-archive.com/live-devel@lists.live555.com/msg08635.html
>
> Tried to debug, check logs - everyt
Hello
I have issue with multiple connections to RTSP proxy:
only one client works fine, if i connect second, the 1st freezes...
Compiled from latest sources
Same as in this thread:
http://www.mail-archive.com/live-devel@lists.live555.com/msg08635.html
Tried to debug, check logs - everything look
> H264VideoStreamDiscreteFramer error: MPEG 'start code' seen in the input
We had a similar report back in July. See
http://lists.live555.com/pipermail/live-devel/2012-July/015474.html
In short: The camera is sending invalid H.264/RTP packets, violating the
standard. It needs to be fix
Below is the log, FYI. Appreciate to get your response :-)
E:\DELTA\Item\VidaGrid\M2\RTSP\open-source\live555-delta\bin\Debug>proxyServer.e
xe -V rtsp://172.17.92.36:8557/h264
LIVE555 Proxy Server
(LIVE555 Streaming Media library version 2012.07.26)
Opening connection to 172.17.92.36, po
Dear Madam/Sir
I am a master student from Dublin City University, Ireland. I want to develop
a multi-source proxy use these libraries. Should I change the code in packet
level or session level? Can you help me with some hints or sample source
code?
Thanks.
Qing Hai
_
54 matches
Mail list logo
