OK, thanks. I’ve just installed a new version (2024.09.29) of the code that
fixes this.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/liv
Yes.
Something like this:
1) ~ProxyServerMediaSession
2) ~ServerMediaSession //(at this point fProxyRTSPClient is already deleted)
3) deleteAllSubsessions()
4) Medium::close(fSubsessionsHead)
...
5) delete medium
6) ~ProxyServerMediaSubsession
7) envir() << *this << "::~ProxyServerMediaSubsession(
Andrey,
Thank you for the bug report.
I agree that there is probably a bug here, but I don’t like your proposed
solution.
If a “ProxyServerMediaSession” has been deleted, then nobody should be calling
“url()” on it.
I.e., the problem is not that code is trying to access an already-deleted
“P
Hello. I tried live555ProxyServer.cpp example and found that if:
1) we start program with -V option
2) there are active proxy streams (not clients, but just get descriptions
from rtsp streams);
3) we EXIT from event loop and delete server with *Medium::close()*
then it will crash due to access to
> On Sep 7, 2022, at 6:16 PM, Специалист IT wrote:
>
> [back-end RTSP/RTP stream] --> [LIVE555 Proxy Server]... BUT [back-end
> RTSP/RTP SERVER] --> [LIVE555 Proxy Server]...
OK, I’ve made that change to the web page, if that makes things clearer for you.
> Did I understand you correctly th
Thank you for the opportunity to ask a question and for your very quick
response
First, we do not support the model whereby a data source 'pushes' media
into a RTSP server (something that's excessively complex, and
non-standard). That's why the "ANNOUNCE" command did not work.
Unexpectedly,
First, we do not support the model whereby a data source ‘pushes’ media into a
RTSP server (something that’s excessively complex, and non-standard). That’s
why the “ANNOUNCE” command did not work.
Instead of using a ‘ffmpeg’ video encoder to ’stream’ encoded video into a RTSP
server, you simpl
Hello!
I have done heavy transcoding from usb mjpeg camera to h264 in my code
and now streaming to a third-party rtsp server (for example to
rtsp-simple-server) using ffmpeg libraries
On the command line, it looks something like
./ffmpeg -f v4l2 -input_format mjpeg -i /dev/video0 -c:v libx264
By default, the server uses the network interface that’s used for IP multicast
routing - i.e., the one that has a route for 224.0.0.0/4. (The reason for this
is that it uses IP multicast to detect its own IP address.)
So, the easiest way to choose a particular network interface is to reconfigur
Hi,
I am trying to use the RTSP Proxy Server to host a RTSP stream. However, with
both the Wi-Fi and the Ethernet connected, the IP address for the proxy server
can sometimes be the Wi-Fi IP while sometimes it is the Ethernet IP. May I know
whether there are any ways to ensure that the restream
Thanks for sending the log. It shows that the problem is with your ‘back-end’
server (i.e., IP camera). The LIVE555 Proxy Server is working properly.
> Attached. As before, the sequence of actions:
>
> - start proxyserver
> - run player: fails
>
> Playing: rtsp://proxyaddr/proxyStream
> [ffm
On Tue, Sep 17 2019, Ross Finlayson wrote:
> And send us the complete log output (especially during the time that the
> proxy server returns "454 Session Not Found”).
Attached. As before, the sequence of actions:
- start proxyserver
- run player: fails
Playing: rtsp://proxyaddr/proxyStream
[ffmp
> On Sep 17, 2019, at 10:34 AM, Yuri D'Elia wrote:
>
> On Mon, Sep 16 2019, Ross Finlayson wrote:
>> Try adding the -V (upper-case V) option, to get verbose diagnostic output,
>> and send us this diagnostic output, when the problem occurs.
>
> Ran as following:
>
> /usr/bin/live555ProxyServe
On Mon, Sep 16 2019, Ross Finlayson wrote:
> Try adding the -V (upper-case V) option, to get verbose diagnostic output,
> and send us this diagnostic output, when the problem occurs.
Ran as following:
/usr/bin/live555ProxyServer -p 554 -R -V -u user pass 'rtsp://camera/videoMain'
"camera" is 19
> On Sep 16, 2019, at 6:21 AM, Yuri D'Elia wrote:
>
> I've been using live555ProxyServer for a while, starting a couple of
> years ago and currently using 2019.08.28 from debian unstable.
>
> I'm relaying an authenticated rtsp stream from a webcam.
> I'm using proxyserver as follows:
>
> live
I've been using live555ProxyServer for a while, starting a couple of
years ago and currently using 2019.08.28 from debian unstable.
I'm relaying an authenticated rtsp stream from a webcam.
I'm using proxyserver as follows:
live555ProxyServer -p 554 -R -U user pass
'rtsp://user:pass@cameraip/vide
> On Sep 5, 2019, at 5:23 PM, HAN Hao wrote:
>
>
> In this case, the maximum number of proxy server instances created can only
> be 2(ports 554 and 8554)?
No. You can create servers that use whatever port number(s) you wish. Just
note that only two port numbers - 554 and 8554 - are reser
> At the same time, may I also ask whether it is possible to set the RTSP Proxy
> Server to use the same port? When multiple instances of RTSP Proxy Server is
> hosted, the first proxy server does not show the port number(i.e
> xxx.xxx.xxx.xxx/proxyStream). From the second proxy server onwards,
> Note also that port 554 is the ‘default’ port number for RTSP. “rtsp://“
> URLs that use port 554 don’t have to use it (although they can if you wish).
> (This is analogous to port 80 for HTTP.)
My explanation here was a little unclear. This is better:
Port 554 is the ‘default’ port numb
> On Sep 5, 2019, at 12:55 AM, HAN Hao wrote:
>
>
>> Thank you! For that situation, I am able to see the accepted connection. May
>> I know whether there are any ways to know if the accepted IP Address has
>> terminated or lost that connection?
>
>> Yes, the “ClientConnection” object (or,
> Thank you! For that situation, I am able to see the accepted connection. May
> I know whether there are any ways to know if the accepted IP Address has
> terminated or lost that connection?
>Yes, the “ClientConnection” object (or, in this case, the subclass object
>“RTSPServer::RTSPClientCo
> On Sep 4, 2019, at 12:32 AM, HAN Hao wrote:
>
>
> Thank you! For that situation, I am able to see the accepted connection. May
> I know whether there are any ways to know if the accepted IP Address has
> terminated or lost that connection?
Yes, the “ClientConnection” object (or, in this
> Thank you for your assistance! I managed to change the URL of the
> proxystream. However, for the compilation of the genericmediaserver.cpp, may
> I know what are the steps I take to see the IP addresses of the devices
> connected?
>As I already noted, you can do this simply by compiling
>
Hello!
> On Sep 1, 2019, at 8:25 PM, HAN Hao wrote:
>
> Thank you for your assistance! I managed to change the URL of the
> proxystream. However, for the compilation of the genericmediaserver.cpp, may
> I know what are the steps I take to see the IP addresses of the devices
> connected?
>As
(First, please trim your message when responding to an email. This is basic
email ’netiquette’, that everyone should know.)
> On Sep 1, 2019, at 8:25 PM, HAN Hao wrote:
>
> Thank you for your assistance! I managed to change the URL of the
> proxystream. However, for the compilation of the ge
. Thank you!
Regards,
Han Hao
-Original Message-
From: live-devel [mailto:live-devel-boun...@us.live555.com] On Behalf Of Ross
Finlayson
Sent: Friday, 30 August, 2019 4:37 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] RTSP Proxy Server Front End
> On Aug 30, 2019, at 10:07 AM, HAN Hao wrote:
>
> Hi Sir/Madam,
>
> I am trying to use the proxy server as a mean to manage downlink and uplink
> from my RTSP source. However, using the default setting of the RTSP Proxy
> Server, the front end URL can only be set as IP/proxyStream%i.
>
>
Hi Sir/Madam,
I am trying to use the proxy server as a mean to manage downlink and uplink
from my RTSP source. However, using the default setting of the RTSP Proxy
Server, the front end URL can only be set as IP/proxyStream%i.
May I know how do I change this setting such that the front end URL
> I can indeed see this running the proxy server with -V. It is not the case
> of a TCP connection being misinterpreted as valid. It is the case of when the
> proxy server retries an OPTIONS command, it sees the TCP connection has gone
> away, reconnects and receives a valid response, it doesn'
On 22/09/14 15:42, Ross Finlayson wrote:
It is possible to restart an origin server quickly enough that a live
555 proxy server does not notice.
As a test this can be done by modifying one of the live 555 test
programs (I was using testH264VideoStreamer) to enable
SO_REUSEADDR/SO_REUSEPORT, t
> It is possible to restart an origin server quickly enough that a live 555
> proxy server does not notice.
>
> As a test this can be done by modifying one of the live 555 test programs (I
> was using testH264VideoStreamer) to enable SO_REUSEADDR/SO_REUSEPORT, then
> the process could be quickl
Hello,
It is possible to restart an origin server quickly enough that a live
555 proxy server does not notice.
As a test this can be done by modifying one of the live 555 test
programs (I was using testH264VideoStreamer) to enable
SO_REUSEADDR/SO_REUSEPORT, then the process could be quickly
I'm still working on duplicating what I saw and will capture logs and post once
I do. So far I have not seen a drop of the streaming data.
Thanks,
Craig
On 11/13/2013 04:06 PM, Ross Finlayson wrote:
I'm wondering if there is a specific message I can look for in the logs
when at level 2 that wil
> I'm wondering if there is a specific message I can look for in the logs
> when at level 2 that will indicate if a proxies stream has failed? I'm
> using the proxyServer example and at times the stream stops streaming.
> I can see the OPTION commands going out to the camera with a response,
I'm wondering if there is a specific message I can look for in the logs
when at level 2 that will indicate if a proxies stream has failed? I'm
using the proxyServer example and at times the stream stops streaming.
I can see the OPTION commands going out to the camera with a response,
but conn
.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of agrit...@cnord.ru
Sent: Thursday, February 28, 2013 1:58 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] rtsp proxy: memory leak
2013/2/28 Ross Finlayson :
> Unfortunately I can not use valgrind for debuggi
2013/2/28 Ross Finlayson :
> Unfortunately I can not use valgrind for debugging the leak because it
> is not available on the platforms the problem is reproducible on.
>
>
> And what platforms are these? Let me guess - Windows? Sigh...
No, they are are qemu-arm (which emulates armv5) and TI AM33
> Unfortunately I can not use valgrind for debugging the leak because it
> is not available on the platforms the problem is reproducible on.
And what platforms are these? Let me guess - Windows? Sigh...
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
You are right, it is available. I tried to use it but it fails with
disInstr(arm): unhandled instruction: 0xEEBA7BC1
cond=14(0xE) 27:20=235(0xEB) 4:4=0 3:0=1(0x1)
immediately after the log message
"ProxyServerMediaSubsession["H264"]::createNewStreamSource".
--
Anton
2013/2/28 F
Hi Anton,
On 02/28/2013 08:39 AM, agrit...@cnord.ru wrote:
Hello,
I believe I found a huge memory leak in the rtsp proxy server. The
problem is that I can only reliably reproduce it on qemu-arm or
physical armv7 device. It doesn't happen when I run rtsp proxy on my
x86-64 machine. Moreover, it
Hello,
I believe I found a huge memory leak in the rtsp proxy server. The
problem is that I can only reliably reproduce it on qemu-arm or
physical armv7 device. It doesn't happen when I run rtsp proxy on my
x86-64 machine. Moreover, it only reveals when there are four or more
clients connected to
There is an existing RTSP server for which there is no programatic control
and cannot be changed.
I need to implement a custom feature at the application level which
requires server control.
So was thinking on these terms.
Regards,
Sambhav
On Tue, Jun 19, 2012 at 8:25 PM, Ross Finlayson wrote:
> Is the following RTSP proxy server mode of operation possible ?
> ProxyServer only acts as proxy only for RTSP commands, but the RTP/RTCP data
> flows to the client directly from the main RTSP Server
No, and for most back-end servers, that would not even be possible. For
security reasons (to
Hi,
Is the following RTSP proxy server mode of operation possible ?
ProxyServer only acts as proxy only for RTSP commands, but the RTP/RTCP data
flows to the client directly from the main RTSP Server
Regards,
Sambhav
___
live-devel mailing list
live-
Hi Ross,
I want to modify live555 code to work it as an RTSP proxy,
please guide me what all would I require to do do we already have proxy
support I think we dont.
Many Thanks,
Nishesh
___
live-devel mailing list
live-devel@lists.live555.com
http://list
Hi Ross,
I am thinking of implementing a back to back server and client from
the library acting as a proxy. I would like to ask for some
points/ideas how is it possible or if has anyone implement rtsp *only*
proxy, meaning the accompanying rtp would not be flowing through the
proxy but instead di
46 matches
Mail list logo
