Hi Loretta,
I have tried to repro this behavior, but could not get
through
Here are my steps:-
I just simply played a live session from server and at the
client end
started playing the clip. After some time I terminated the
live session
and the server sent a RTCP BYE message to the client.
Once the client receive this message, it plays the clip for
few secs and
then stops.
When I analyzed the logs, I observed
1. Client do get one or two packets in Transport Buffer's
Add/Insert()
function that Server might have sent before the RTCP_BYE
message(expected)
2. Client plays the packets that are stored in the queue for
the
renderer (expected)
3.There is no call of OnBuffering() as client does not
expect any more
packet from the server
4. Then StreamDone is called and consequently TEARDOWN
message is sent
to the server and finally
5. Player is stopped, and hence the presentation is closed.
Please find the RTSP server-client conversation as well as
the packet logs.
Please provide me the contents with which you reprod the
"*case 2*"* ,
*so that I can work on this issue.
Thanks & Regards
Gaurav Bajaj
Loretta Lamieri wrote:
>
> Hi thanks for the answer,
>
> But I need more information about the handling of RTCP
BYE packet.
>
> We have identified two different cases:
>
> 1. *Stream of a media content with a finite duration
(trace file
> Stream1.cap)*
>
> * *In this case the TEARDOWN method is correctly sent
by the client
> after the reception of the RTCP BYE packet on both
audio and video stream
>
> 2. *Streaming of 1 minute of a mobile pay-TV
channel* *(trace file
> Stream2.cap)*
>
> * *In this case the RTCP packet is received after 1
minute of
> streaming, but the client doesn’t send the TEARDOWN
method even if
> there is no RTP traffic. So the RTSP session remains
erroneously (from
> our point of view) active.
>
> We need to know the reasons why in the second case the
TEARDOWN method
> is not sent by the client after the reception of the
RTCP BYE packet.
>
> Thanks again
>
> Loretta Lamieri
>
>
------------------------------------------------------------
------------
>
> *From Jeff Ayars
[mailto:jeffa real.com]
> *Sent Friday,
January 05, 2007 7:42 AM
> *To Loretta
Lamieri; helix-client-devhelixcommunity.org
> *Subject Re:
[Helix-client-dev] RTCP Goodbye
>
> At 10:21 PM 1/4/2007, Loretta Lamieri wrote:
>
> Hi again,
> Im using your Helix DNA Client (Branch
"hxclient_1_4_2_neptunex", to
> test a streaming platform on a mobile phone
environment.
> I m trying to stream a media content that have a
finite duration
> (i.e. 1 minute) and at the end of the RTP stream I
receive a RTCP BYE
> packet from the streaming server instead of RTSP
TEARDOWN.
>
> So, It seems that this packet is used to close the RTSP
session.
>
>
> No. It's used to signal the end of the RTP stream.
>
> Is it compliant to the RTSP rfc?
>
>
> Yes. The client sends the TEARDOWN when it doesn't need
the session
> anymore. If it is in a state where it might re-play the
stream, it is
> a valid optimization to not send the TEARDOWN.
>
> If yes, how the client has to behave when it receives
this kind of packet?
>
>
> It allows the client to know it has all of the packets
for the
> session. It can stop sending RTCP messages. It can know
that the
> network resources are free to setup another stream. It
can do nothing.
>
> Does it must send a RTSP TEARDOWN to the streaming
server?
>
>
> No, only if the client knows it doesn't need the
session with the
> server anymore does it need to send the TEARDOWN
>
> JEff
>
>
> Thanks
> Loretta Lamieri
> _______________________________________________
> Helix-client-dev mailing list
> Helix-client-devhelixcommunity.org
> http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev
>
>
------------------------------------------------------------
------------
>
> _______________________________________________
> Helix-client-dev mailing list
> Helix-client-devhelixcommunity.org
> http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev
>
|