[asterisk-dev] NAT mapping while binding to IPv6

Simon Perreault simon.perreault at viagenie.ca
Tue Sep 6 10:38:20 CDT 2011

Kevin P. Fleming wrote, on 09/06/2011 11:22 AM:
>> Right. The STUN subsystem and other NAT handling code has not been ported to
>> IPv6 yet. As IPv6 currently has no NAT, doing that was deemed low priority. IMHO
>> it is a missing feature, not a bug per se.
> Except in this case, the endpoint that Asterisk was communicating with was using
> IPv4, and Asterisk was using a dual-stack socket. This resulted in Asterisk not
> performing its normal NAT traversal mechanics, even though they should have been
> done for this endpoint. That's the bug.

You're right. And if chan_sip supported multiple sockets, this bug would
disappear. That's one thing worth fixing IMHO. Adding NAT support to IPv6, not
so much.

DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

More information about the asterisk-dev mailing list