Tech

IPv6 and NAT

Published on:

October 30, 2013

IPv6 was designed to eliminate the need for network address translation (NAT) that became necessary with IPv4 due to the limited number of IP addresses. While IPv6 provides an abundance of addresses, NAT is still being considered by some firewall manufacturers as a necessary feature. For SIP clients, NAT behind IPv6 should work fine, as connection-oriented SIP packets like TCP or TLS handle responses naturally. The main issue with NAT and IPv6 arises when servers inside a network need to be accessed. The solution is simple: configure firewalls to forward packets to the PBX server, maintaining the security of internal devices while enabling remote connectivity.

One of the core goals of IPv6 was to get rid of the unfortunate network address translation (NAT) introduced with IPv4 and the foreseeable lack of IPv4 addresses for every connected device. Especially for SIP, NAT was a disaster that caused so much trouble SIP almost didn't make it into the real world.

While there are plenty of IPv6 addresses, it doesn't mean NAT will be completely a matter of the past. I was a little shocked when I saw discussions about NAT for IPV6. What I thought would be completely useless seems to have been picked up by firewall manufacturers as a must-have feature for their next generation firewall products. But on a second thought, at the end of the day what should be achieved here is devices in the private network should be accessible from the outside only for connections they have actually initiated. For SIP clients, this is perfectly okay. Actually, I even believe running a SIP IPv6 client behind a NAT for IPv6 with snom ONE would work perfectly fine. I couldn't try it out but, looking at the mechanisms, it should be working fine: SIP packets using TCP or TLS are connection-oriented anyway; SIP UDP packets are usually tagged with received parameters, so the responses find their way back without any issues. RTP packets are also automatically sent back where they come from, and I don’t see a reason why this shouldn't work with IPv6.

The only problem I see with NAT and IPv6 are servers that run in the LAN - we know this problem well from IPv4. The good news, however, is it will be relatively simple to get this working perfectly: all that's needed is that the firewall makes an exception for the device in the LAN so packets are forwarded to the PBX server. This will even work well with remote workers.

A well-designed firewall will be great for IPv6 and SIP. Companies won't lose any feature they had with IPv4; instead, they will finally have the opportunity to expose exactly those servers and services they want to (which includes SIP) while keeping clients protected from the public Internet.

Latest Articles

View All

Vodia Attends CVxExpo 2025

Vodia attended CVxExpo 2025, one of the nation’s leading IT and telecom trade shows, to connect with industry leaders and explore the latest innovations in cloud communications and AI. Eric highlighted how this year’s event focused heavily on AI adoption and shared Vodia’s commitment to integrating intelligent call routing, real-time transcription, and 24/7 availability into the Vodia PBX. These enhancements aim to simplify business communications, boost collaboration, and elevate customer experiences for enterprises and service providers.

November 7, 2025

MS Teams Integration and the Benefits of Microsoft Certification for Communications

Microsoft Teams has become a cornerstone of modern business communication, empowering over 250 million users worldwide with tools for collaboration, automation, and productivity. Yet while Teams excels at internal communication, it lacks native support for traditional phone systems and analog devices. That’s where certified integrations like the Vodia PBX come in. As a Microsoft-certified solution, Vodia bridges Teams with SIP phones, VoIP devices, and analog endpoints, enabling businesses to make and receive external calls directly within Teams.

November 4, 2025

Vodia PBX Now Integrates with Smokeball to Streamline Law Firm Communications

Law firms can now handle client communications more efficiently with the new integration between Vodia and Smokeball, the AI-powered legal practice management software. The integration connects the phone system directly with Smokeball, giving staff instant caller identification, access to related matters, and real-time client insights. By unifying calls and case management in one platform, it helps firms save time, reduce errors, and deliver faster, more informed client service.

October 31, 2025