<div dir="ltr">Hi,<br><br>I'm just curious, if anyone addressed the case I'm having now.<br><br>I have an RTSP server (Live555) running in my testing lab and recently put a router in front of it. Then I configured port-forwarding options in the router so that RTSP clients can access the RTSP server through the router's public IP address. <br>
<br>e.g. <br>router: <a href="http://74.210.123.123">74.210.123.123</a><br>RTSP server: <a href="http://192.168.0.100">192.168.0.100</a> (Live555)<br><br> client: <a href="http://74.210.123.122">74.210.123.122</a> (OpenRTSP, VLC, QuickTime)<br>
<br>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, then use it as destination.<br><br>Any idea, comment is greatly appreciated,<br><br>Regards,<br><br>Ken Seo<br><br><br>
</div>