[Live-devel] RTSP over TCP advice

[Ralf Globisch]

Hi Ross,
Please could you venture your expert opinion on the following:

We are streaming from a live555 RTSP server to an android version of
VLC built with live555 using RTSP over TCP.

When streaming over wifi, there are no problems.
When streaming over 3G/Edge, the VLC client never starts playing and
we have observed the following:

The RTSP reply to the PLAY is in the same TCP frame as some
interleaved media as can be seen in the attached wireshark capture (rtsp_3g).
It looks like the interleaved media precedes the RTSP response (unless
wireshark reorders it).

This is not the case when streaming over wifi (see attached rtsp_wifi).
Here each response is in it's own TCP frame.

Is this permissible according to the standard?

If this is the issue, how would we best go about solving this issue:
 - Do we solve the issue on the server side i.e. prevent the RTSP
server from sending any media until the RTSP response has been sent.
 - Or do we look at the client (i.e. parsing such a TCP packet)?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rtsp_3g
Type: application/octet-stream
Size: 8226 bytes
Desc: not available
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20111004/90bdf546/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rtsp_wifi
Type: application/octet-stream
Size: 3445 bytes
Desc: not available
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20111004/90bdf546/attachment-0003.obj>