RE: CR: rtsp tweaks forkeepalive

Hi,
  We have seen 451 response for SET_PARAM on other servers.
But the
failure DOES NOT stop the client in any way. Helix Client
was still
progressing in playback and further SET_PARAM were also
sent. The
SET_PARAM we noticed was SetDeliveryBandwidth messages and I
think the
handling of all SET_PARAM messages are same.
Our observation is on 210CayS branch. We are yet to make
changes to
switchoff SetDeliveryBandwidth on 451 error. 

Thanks,
Rajesh.
 
 

>-----Original Message-----
>From: helix-client-dev-bounceshelixcommunity.org 
>[mailto:helix-client-dev-bounceshelixcommunity.org] On
Behalf 
>Of ext Irfan Makandar
>Sent: Wednesday, February 27, 2008 12:28 AM
>To: 'Greg Wright'; Allegri Luca (NSN - IT/Milan)
>Cc: helix-client-devhelixcommunity.org; 
>helix-server-devhelixcommunity.org
>Subject: [Helix-client-dev] RE: [Helix-server-dev] CR:
rtsp 
>tweaks forkeepalive
>
>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-bounceshelixcommunity.org
>[mailto:helix-server-dev-bounceshelixcommunity.org] On
Behalf 
>Of Greg Wright
>Sent: Tuesday, February 26, 2008 11:56 PM
>To: luca.allegrinsn.com
>Cc: helix-client-devhelixcommunity.org; 
>helix-server-devhelixcommunity.org
>Subject: Re: [Helix-server-dev] CR: rtsp tweaks for
keepalive
>
>luca.allegrinsn.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-devhelixcommunity.org
>http://lists.helixcommunity.org/mailman/listinf
o/helix-server-dev
>
>
>_______________________________________________
>Helix-client-dev mailing list
>Helix-client-devhelixcommunity.org
>http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev
>

_______________________________________________
Helix-server-dev mailing list
Helix-server-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-server-dev