[prev in list] [next in list] [prev in thread] [next in thread] 

List:       helix-server-dev
Subject:    RE: [Helix-server-dev] CR: rtsp tweaks for keepalive
From:       "Irfan Makandar" <imakandar () real ! com>
Date:       2008-02-27 6:39:50
Message-ID: 0cb901c87909$e2aeeb40$0602280a () itestreal ! com
[Download RAW message or body]

If SET_PARAM request includes "ping: pong" header then server replies with
"451 Parameter Not Understood" as "ping" header is not defined and not
understood by server.
If you are using "ping: pong" for just keep alive purpose, your client
should ignore the response and from response infer that session is alive.

-Irfan

-----Original Message-----
From: helix-server-dev-bounces@helixcommunity.org
[mailto:helix-server-dev-bounces@helixcommunity.org] On Behalf Of Greg
Wright
Sent: Tuesday, February 26, 2008 11:56 PM
To: luca.allegri@nsn.com
Cc: helix-client-dev@helixcommunity.org; helix-server-dev@helixcommunity.org
Subject: Re: [Helix-server-dev] CR: rtsp tweaks for keepalive

luca.allegri@nsn.com wrote:
> Hi,
> 
> I'm working in Opeartor streaming project and I have experienced many of 
> following error in a live streaming session (.rm file):
> 
> - handset (Motorola/Ericsson) sends RTSP SET PARAMETER with Pong during 
> the streaming session
> - Server replies with "451 Parameter not understood"
> - handset closes the connection (Teardown)
> 
> I'm wondering whether the probelm is a behaviour, not-compliant to spec, 
> of handsets or helix issue.
> Can you please clarify how to avoid this kind of errors?
> Operator has Helix v.10.09.
> 
> Thanks in advance for your support.

Those should be the keep alive messages. The server should just
ignore any message it doesn't understand, which it looks like
it is doing. Once the server responds with an error the client
should stop sending those type of messages. In the case above
it sounds like the client is taking that as a serious error and
aborting the connection. I don't think it should.

Since this is a live .rm stream, I assume this is a RealServer?
RealServers should understand those messages since we have
been using them for so long. Perhaps there is a proxy in the
way that doesn't understand them?

what client is on the handset exactly?

The server folks may chime in with better information.

--greg.



> 
> Best Reagrds,
> Luca



_______________________________________________
Helix-server-dev mailing list
Helix-server-dev@helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-server-dev


_______________________________________________
Helix-server-dev mailing list
Helix-server-dev@helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-server-dev
[prev in list] [next in list] [prev in thread] [next in thread]