<div dir="ltr">Thanks Ross for your quick reply!<br><br>Regards,<br><br>Ken<br><br><div class="gmail_quote">2008/8/20 Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com">finlayson@live555.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="Ih2E3d">
<blockquote type="cite">Now the client can make an RTSP request
just fine and start playing the stream. However, the RTCP packets from
the client to the server get lost and as a result, the server stops
the streaming with liveness timeout after 45 seconds. I've captured
RTCP packets and found out that the packet's destination is set to "<a href="http://192.168.0.100" target="_blank">192.168.0.100</a>" which is the
server's real IPAddress and also is a private address.<br>
<br>
My best guess will be that the client gets the address from the RTCP
packets sent from the server</blockquote>
<div><br></div>
</div><div>No, the client gets the (RTCP destination) address from the
"source=" address that the server puts in its RTSP
"SETUP" response. </div>
<div><br></div>
<div>The bottom line is that RTSP and NAT currently do not work well,
especially if the RTSP server is behind a NAT. Don't do that
:-)</div>
<pre>--
</pre><font color="#888888">
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/" target="_blank">http://www.live555.com/</a></div>
</font></div>
<br>_______________________________________________<br>
live-devel mailing list<br>
<a href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a><br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
<br></blockquote></div><br></div>