[Live-devel] NAT and RTCP

Ken Seo ken.seo at gmail.com
Wed Aug 20 13:18:19 PDT 2008


Thanks Ross for your quick reply!

Regards,

Ken

2008/8/20 Ross Finlayson <finlayson at live555.com>

>  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 "192.168.0.100" which is the server's real IPAddress
> and also is a private address.
>
> My best guess will be that the client gets the address from the RTCP
> packets sent from the server
>
>
> No, the client gets the (RTCP destination) address from the "source="
> address that the server puts in its RTSP "SETUP" response.
>
> 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 :-)
>
> --
>
>
> Ross Finlayson
> Live Networks, Inc.
> http://www.live555.com/
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20080820/9dac5159/attachment.html>


More information about the live-devel mailing list