[Live-devel] RTSPClient WRT connection to rtsp server (camera)

[Tyson, Russell A. III]

Thanks for your quick response Ross!

 

Note that you don't have to do that.  It's possible for a single proxy
server to serve multiple 'back end' streams.  (E.g., our "LIVE555 Proxy
Server" application can do this.)

 

Our approach with this one-to-one setup was to ensure that we didn't
lose all of our camera streams if one proxy server crashed.  This system
is designed to run on its own for long periods of time (days, weeks,
etc.) with minimal user interaction other than connecting clients (VLC)
to view available streams.

 

Note that our proxy server code already monitors and keeps alive the
connection to each of its 'back end' server.  This is not something that
you need to handle separately.

 

Yes, and we are relying on that code to reconnect to the camera.  What I
was looking for was a connection status event, if you will, so that my
manager service can notify, or respond to queries from other services
about the proxy/camera connection state.  

i.e. A GUI displays a list of available cameras to an end user.  I would
like to only list cameras that are currently connected to their
respective proxy.  If, for some reason, a proxy loses its connection to
a camera, I would like to be able to exclude this particular camera from
the list, or at least notify the "client" that it is not currently
connected.  This type of event could also be used to alert other
services of a problem with the system if a camera/proxy connection
suddenly goes down and is not restored by the proxy server in some
period of time.

 

Cheers!

 

Russell Tyson | SAIC
Senior Software Engineer | Software Solutions Team
phone: 256-971-6640 | mobile: 256-651-9981
russell.a.tyson.iii at saic.com | saic.com <http://www.saic.com/> 

 

From: live-devel-bounces at ns.live555.com
[mailto:live-devel-bounces at ns.live555.com] On Behalf Of Ross Finlayson
Sent: Monday, April 29, 2013 2:29 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] RTSPClient WRT connection to rtsp server
(camera)

 

	I am working on a windows service (a "Manager") that starts,
monitors, and stops multiple Proxy servers.  These proxy servers are
based on your Live555 Proxy Server code. Each proxy is serving a single
stream from a single back end camera.

 

Note that you don't have to do that.  It's possible for a single proxy
server to serve multiple 'back end' streams.  (E.g., our "LIVE555 Proxy
Server" application can do this.)

 





During the lifetime of the proxy, I expect that the back end connection
could terminate for some reason, or not connect at all in the first
place.  I have been looking for a hook to report this state back to the
manager, but have not been successful.  Does the RTSPClient provide any
type of event, or other signal that could be used by other
processes/services for the purpose of monitoring the state of the back
end connection?

 

Note that our proxy server code already monitors and keeps alive the
connection to each of its 'back end' server.  This is not something that
you need to handle separately.

 





In our system, we also have an archiving service.  This service connects
to the stream provided by the proxy and archives the data to a file.
One archiver exists for each proxy.  The Archiver uses the OpenRTSP
client to achieve this.  I have noticed that if the OpenRTSP client
terminates unexpectedly, the CPU usage of the proxy skyrockets from
about .07 average up to around 22.5 average.  We run about 25 of the
proxies, so you can imagine the hit if 4 of these clients die.  In the
case where the archiving service as a whole dies, all of the clients can
terminate, which leaves us with 25 proxies running at around a 22% CPU
usage with makes the system unusable.

 

I had considered monitoring the CPU load on all of the proxies through
the manager, and terminating/restarting any that run high on CPU usage.
But I was wondering if you could shed some light on what is going on in
the proxy to produce this effect.

 

Sorry - no idea.  That's something that you're going to have to track
down yourself.

 

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/ 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20130429/e91bcc60/attachment-0001.html>