Thank very much for your patience. You are right. In the past I already tried
to have support from the vendor but the vendor technicians don't have
understood wich is the problem. My opinion is that that the vendor techitians
don't know what rtsp is. They only know how the camera app works.
Have
> On Nov 26, 2024, at 2:07 AM, i...@denisgottardello.it wrote:
>
> Can you suggest me a workaround?
No. Once again, your IP camera appears to be buggy; you will need to contact
the manufacturer of this camera to get it fixed.
Remember: The IP camera is something that you have paid money for,
After having make some tests, by editing the function
scheduleLivenessCommand() the problem persists.
This is my experience: if I start live555ProxyServer and I connect to it
immediatrly I can watch the camera. Now I can disconnect to the server, wait
minutes and reconnect. I still see the camer
> On Nov 23, 2024, at 8:25 AM, i...@denisgottardello.it wrote:
>
> Many thanks for your reply. How much time it is required to resend the
> OPTIONS
> command? Can I edit it in order to debug the camera?
Look at the code for "ProxyRTSPClient::scheduleLivenessCommand()”
Ross Finlayson
Live Ne
Many thanks for your reply. How much time it is required to resend the OPTIONS
command? Can I edit it in order to debug the camera?
In data venerdì 22 novembre 2024 17:51:41 CET, Ross Finlayson ha scritto:
> If no ‘front end’ client is currently streaming from the proxy server, then
> the proxy s
If no ‘front end’ client is currently streaming from the proxy server, then the
proxy server (tries to) keep its RTSP connection to the ‘back end’ server
(e.g., an IP camera) alive by periodically sending it RTSP “OPTIONS” commands.
For this particular IP camera, however, it appears that this d
You didn’t say which of our software you were running (a RTSP server, a RTSP
client, a proxy server (RTSP or HLS), or some combination thereof).
But the error messages mean what they say: You have a ridiculously large frame
of data (most likely a video 'key frame') somewhere that is too large fo
> On Feb 21, 2024, at 5:30 AM, Denis Gottardello
> wrote:
>
>
> Hi, is there a way to forcelive555ProxyServer to force connection to the
> remote cameras by tcp?
I’m not sure I understand your question. RTSP (the control protocol) runs over
TCP, so all connections to RTSP servers will
use
Subject: Re: [Live-devel] Live555ProxyServer on Gateway PC with two NICs
> When I run the program, it appears to automatically start the proxy server on
> the same NIC that connects to the source RTSP server.
>
> Are there any workarounds for this?
Yes. The proxy server will
> When I run the program, it appears to automatically start the proxy server on
> the same NIC that connects to the source RTSP server.
>
> Are there any workarounds for this?
Yes. The proxy server will use the network interface that’s used for IP
multicast routing - i.e., the one that has a
> *** live555ProxyServer LOG
>
> LIVE555 Proxy Server
>
> (LIVE555 Streaming Media library version 2015.05.25)
>
>
[…]
> Sending request: PLAY rtsp://admin:1@192.168.1.121//h264/ch1/main/av_stream
> RTSP/1.0
>
> CSeq: 9
> Authorization: Digest username="admin", realm="Embed
Hi, thank you for your reply;
The commands for the server and
client:
./live555ProxyServer -V
rtsp://admin:1@192.168.1.121//h264/ch1/main/av_stream
./testRTSPClient rtsp://192.168.1.128:8554/proxyStream
As I said
before, after 70 with the client disconnected, I tryed to connect again
a
> live555ProxyServer LOG:
>
> ProxyServerMediaSubsession["H264"]::closeStreamSource()
>
> ProxyServerMediaSubsession["H264"]::createNewRTPSink()
>
> ProxyServerMediaSubsession["PCMU"]::createNewStreamSource(session id
> 929659699)
> ProxyServerMediaSubsession["PCMU"]::createNewRTPSink()
> Recei
> The problem happens when I close the clients (ffplay) and try to play
> again after some time (about 1 or 2 minutes).
>
>
I’m not sure what the problem is here, but I suspect that it may be your client
(“ffmpeg”). “ffmpeg” has a reputation as not having a particularly good RTSP
client
Thanks a bunch Ross, the latest version 2013.04.06 doesn't exhibit any such
problems with the cameras I have on test here. Everything is working
beautifully!
I will report if there are any problems.
Thanks again for adding a workaround so quickly.
On 5 April 2013 18:19, Ross Finlayson wrote:
> Could this problem be related to another issue I’ve recently had with using
> proxy server with vlc as the back end server. The RTSP session timeout is
> hardcoded to 60 secs in VLC . The VLC RTSP server does support GET_PARAMETER
> and PAUSE as shown in OPTIONS. But when live555 proxy client
Ross Finlayson
Sent: Friday, April 05, 2013 5:32 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] live555ProxyServer freezes after upgrading from
2012.12.24
I've compiled the latest version and unfortunately I'm seeing the exact same
output as above,
> I've compiled the latest version and unfortunately I'm seeing the exact same
> output as above, after about 2 and a half minutes of streaming, I see this:
>
> Sending request: GET_PARAMETER rtsp://86.162.35.136/axis-media/media.amp/
> RTSP/1.0
Oops, sorry - my mistake. My earlier 'fix' wasn'
> I've compiled the latest version and unfortunately I'm seeing the exact same
> output as above, after about 2 and a half minutes of streaming, I see this:
>
> Sending request: GET_PARAMETER rtsp://86.162.35.136/axis-media/media.amp/
> RTSP/1.0
You must not have upgraded properly. With the la
On 4 April 2013 10:16, Ross Finlayson wrote:
> I find this very difficult to believe - especially considering that nobody
> else has reported this problem.
>
I'm not sure what to say but GET_PARAMETER is causing problems with almost
all cameras I have here to test (excluding a Chinese no brand o
> Unfortunately it appears to happen on all branded cameras I have to test:
> ACTi, Sony, Axis, D-Link, Vivotek and Lilin.
I find this very difficult to believe - especially considering that nobody else
has reported this problem.
Nonetheless, because you provided definitive evidence of at least
Thanks for your fast reply.
Unfortunately it appears to happen on all branded cameras I have to test:
ACTi, Sony, Axis, D-Link, Vivotek and Lilin. I updated the firmware on this
specific Sony camera to the latest last week.
It appears to be a very typical response to kill the connection when
rece
> Hi, sorry, it's a dynamic IP and there was a power cut:
>
> rtsp://86.146.238.165/media/video1
OK, I've tested this now.
You're correct that your camera server appears to crash (closing down the TCP
connection) and reboot whenever it receives the proxy's "GET_PARAMETER"
command. I.e., the
Hi, sorry, it's a dynamic IP and there was a power cut:
rtsp://86.146.238.165/media/video1
On 4 April 2013 03:56, Ross Finlayson wrote:
> The stream will freeze after a few minutes. When the stream is opened
> directly, it does not freeze:
>
> ./testProgs/testRTSPClient rtsp://86.146.236.49/me
> The stream will freeze after a few minutes. When the stream is opened
> directly, it does not freeze:
>
> ./testProgs/testRTSPClient rtsp://86.146.236.49/media/video1
Sorry, but I can't access this stream.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
__
> here are the steps to reproduce,
> prepare a back-end stream for testing with: vlc rtsp://
> --sout=#rtp{sdp=rtsp:///Video}
> play the proxied stream with: vlc rtsp:///Video
> stop back-end stream in step 1 by pressing Stop button in VLC interface
> live555MediaServer crashes
I'm confused, for s
> I use live555ProxyServer at the LAN,when more then two client connect to
> the server playing mp4 file(1080p h264 aac),there are many mosaic and the
> sound is off and on .If one client connect to the server it is ok.why?
Most likely, packet loss. You probably don't have sufficient networ
> I have issue with proxy server at the ubuntu OS:
> Multiple clients connected to the proxy server(live555ProxyServer) and
> playing,but when one of them play over,other clients also stop and the
> following new client can't receive the rtp packet.What's the problem?
Unfortunately, I don't know
28 matches
Mail list logo
