[Live-devel] R: "GET_PARAMETER" as a client 'liveness' indicator

Trotti Matteo matteo.trotti at elsagdatamat.com
Mon May 3 01:02:15 PDT 2010


You have to schedule a dummy task which get called at a given time interval inside the EventLoop.

 

Create a task where you will just issue a GET_PARAMETER command

rtspClient->getMediaSessionParameter

and after that, simply re-schedule the task itself with a given time interval

env->taskScheduler().scheduleDelayedTask.

Now just call the task for the first time before starting the EventLoop.

Bye,

 

Matteo Trotti

Videosurveillance Lab

Elsag Datamat Spa

Genova, Italy

 

Da: live-devel-bounces at ns.live555.com [mailto:live-devel-bounces at ns.live555.com] Per conto di Stéphane Le Jeune
Inviato: lunedì 26 aprile 2010 15.20
A: live-devel at ns.live555.com
Oggetto: [Live-devel] "GET_PARAMETER" as a client 'liveness' indicator

 

Hello,

I read that openRTSP can send GET_PARAMETER as keepAlive (or client liveness indicator) but nothing in the source code show that (in RTSPClient.cpp). During our session, the timeout is sent by the video server in the RTSP SETUP response and catched by openRTSP, but nothing append then when the time expired. 

Why no behavior has been developped ? 

Is there any player that can be able to send GET_PARAMETER in place of RTCP "RR" packet ?

Fan

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


More information about the live-devel mailing list