[FFmpeg-devel] [PATCH] Send NAT punching packets when starting to read an RTP/UDP stream

Stefan de Konink stefan
Thu Feb 11 12:34:40 CET 2010

On Thu, 11 Feb 2010, Luca Abeni wrote:

> > I think that was what STUN was supposed to solve.
> Yes, STUN allows a host to know its "public" IP and port, but it's not
> clear to me if there is a standard way to integrate this mechanism
> with RTSP/RTP. While (I think) there are some RFCs explaining how to
> use STUN with SIP, I do not know about any proposal about using STUN
> (or similar) with RTSP or RTP (if there are similar standards or
> proposals, let me know... Because this is what we should implement :).

The problem with STUN is also that it has to be specified and hosted. The
punchholing approach could technically work if one side knows the
external IP of the other, now this is always valid for a public service.

Recently I had a similar issue and turned to [1], created some code
that does that in C, pragmatically why take new RFCs, if the simple
solution works without external help for 90% of all gateways, maybe the
last 10% doesn't want it to happen at all.


[1] http://linide.sourceforge.net/nat-traverse/

More information about the ffmpeg-devel mailing list