<!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] NAT and RTCP</title></head><body>
<blockquote type="cite" 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">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>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>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
http://www.live555.com/</div>
</body>
</html>