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

Keep Talking: AI and the Future of Business Communication

From the moment humans learned to speak, communication has shaped how we live, work, and connect. Today, voice remains one of the most natural and information-rich forms of human interaction, even as business communication expands across chat, video, messaging, and digital platforms. As AI becomes more deeply integrated into phone systems and contact centers, voice may play an increasingly important role in how intelligent systems understand context, respond to people, and support real-time communication.

September 9, 2026

How MSPs Can Build Recurring Revenue by White-Labeling the Vodia PBX

White-labeling the Vodia PBX enables MSPs and VARs to offer business communications under their own brand without developing and maintaining the underlying PBX technology. Providers control branding, packaging, pricing, service delivery, and customer relationships, while Vodia supplies the multi-tenant platform. With V70’s expanded branding and management tools, MSPs can get to market faster and create new recurring-revenue opportunities.

September 3, 2026

CarPlay Now Available with the New Vodia iOS App

Apple CarPlay support is now available with the Vodia iOS app, bringing essential PBX communication features to the vehicle display through Apple’s native in-car interface. Users can access recent calls, browse the extension directory, view colleague presence, listen to voicemail, use Siri for calls and PBX messages, and receive communication alerts, while built-in readiness checks and automatic recovery help maintain reliable access when network conditions change. The experience supports compatible wired and wireless CarPlay systems.

September 1, 2026