[Live-devel] Retrieving progress / status

[Andy Hawkins]

Hi,

The backend RTSP URL is provided by the user, so if they get this wrong I want to provide them with feedback as to what might be going wrong. Things like connection timed out (they've provided the wrong host name or maybe there's a firewall in the way), connection refused (they've probably provided the wrong port), DESCRIBE returning 404 (they've provided the wrong path part in the URL).

I don't want these just appearing on stdout / stderr, and if I were to capture them using the streaming operator overloads in a class derived from UsageEnvironment, then there'd be no way to tie these to a particular proxy connection (I expect to be proxying a number of 'source' RTSP servers to different URLs locally).

I had a look at subclassing ProxyServerMediaSubsession, but there don't appear to be any useful virtual functions in that class that I could override.

I did also consider modifying the existing classes, but obviously that's the least attractive option.

Thanks

Andy









Andy Hawkins


Senior Software
  Engineer
































Office:






+44 1635 35111








Email:






andy.hawkins at uniguest.com








Address:






64 Greenham Road, Newbury, Berkshire, RG14 7HX UK

















UNIGUEST.COM















From: live-devel <live-devel-bounces at us.live555.com> on behalf of Ross Finlayson <finlayson at live555.com>
Sent: 20 October 2023 11:10
To: LIVE555 Streaming Media - development & use <live-devel at us.live555.com>
Subject: Re: [Live-devel] Retrieving progress / status



> On Oct 20, 2023, at 11:39 AM, Andy Hawkins <Andy.Hawkins at uniguest.com> wrote:
>
> Hi,
>
> We're using live555 to proxy RTSP streams, by adding a ProxyServerMediaSession to an RTSP server.
>
> Is there any way to retrieve progress / status of the connection to the 'source' RTSP server? I'm interested in whether socket connections fail, whether there's an error returned by the 'DESCRIBE' call, that sort of thing.

First, note that the “ProxyServerMediaSession” implementation automatically reconnects to the ‘back-end’ RTSP server whenever its connection fails (and/or it detects that the stream is no longer alive).  So there is nothing that you should need to do yourself to recover from this.

If you want to see more information about what the “ProxyServerMediaSession” is doing to recover, then you could pass a value of 2 as the “verbosityLevel” parameter (equivalent to running “live555ProxyServer” with the “-V” option), to get enhanced error output (to ’stderr’).  If you want to do more than this, you could subclass (or, at worst, modify) “ProxyServerMediaSubsession”, but then you’re on your own.


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


_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel