<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Live-devel] openrtsp</title></head><body>
<blockquote type="cite" cite>I have built and tested the openrtsp
command line utility. It works fine for most of the most commonly used
payload formats. I also tried to use the -t and -T options to use a
RTP over RTSP (or HTTP) tunnel and again it works very nice. My
question is as follows - I have a special camera with in-built RTSP
server and I can receive video with no problems. According to the
camera manufacturer they also support the TCP tunnel but when I use
the -t option some error ocurrs (see below). Does anybody recognize
whats wrong here? Thanks in advance. I am afraid it can be a firmware
problem of the camera.</blockquote>
<div><br></div>
<div>[...]</div>
<div><br>
<br>
</div>
<blockquote type="cite" cite>Sending request: PLAY
rtsp://10.0.0.122/ioImage/1 RTSP/1.0<br>
CSeq: 4<br>
Session: 3830<br>
Range: npt=0.000-<br>
User-Agent: openrtsp (LIVE555 Streaming Media v2009.09.28)<br>
</blockquote>
<blockquote type="cite" cite><br>
Discarding interleaved RTP or RTCP packet (48133 bytes, channel id
0)<br>
Received PLAY response:
Hѧţ2?Kˤ??ʧ%>/Ű&?sC>\<span
></span>=W`O?Ŵ>??=5Ů?<br>
dѩԞh;WRܶѩxh<span
></span
>?"?5OSKt|9?RܣѶѰ?-qŰ<span
></span>ѧŰ#'Failed to start
playing session: no response code in line:
"Hѧţ2?Kˤ??ʧ%<br>
>/Ű&?sC>\=W`O?Ŵ<span
></span
>>??=5Ů?dѩԞh;WRܶѩxh<span
></span
>?"?5OSKt|9?RܣѶѰ</blockquote>
<blockquote type="cite"
cite>?-qŰѧŰ#'</blockquote>
<div><br></div>
<div>Yes, there seems to be a problem with your server's
implementation of RTP-over-TCP. In this mode, your server is
apparently not sending back a response to the client's "PLAY"
command. Instead, it appears to start sending back RTP/RTCP data
over the RTSP (TCP) connection, but without first sending back a
response to the "PLAY" command.</div>
<div><br></div>
<div>You will need to contact your server manufacturer to get this
fixed (perhaps a firmware upgrade is available?).</div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
http://www.live555.com/</div>
</body>
</html>