Back to Blog
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.

Christian Stredicke

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
Announcement

The World of Vodia: One Extension, Every Way You Work

Your Vodia extension is no longer tied to a single device or location. Native iOS and Android apps, the browser-based User Portal, PWA support, Vodia Hub and click-to-dial extensions provide different ways to connect with the same Vodia PBX. Make and receive business calls from your smartphone, manage communication from your browser, control calls from the Windows desktop or dial numbers directly from the applications and webpages you already use. Wherever work takes place, Vodia provides an experience designed for the device and workflow at hand.

August 20, 2026
Announcement

From Check-In to Check-Out: Two Years of the Vodia-Cloudbeds Integration

The Vodia-Cloudbeds integration connects hotel communications with essential property-management workflows. From check-in to check-out, it automatically enables and personalizes room extensions, applies guest calling permissions, posts eligible call charges to Cloudbeds and resets extension data after each stay. Two years on, the integration continues Vodia’s long-standing work in hospitality, helping hotel teams reduce manual administration, protect guest information and keep telephone services synchronized with their daily operations.

August 18, 2026
Announcement

The Vodia-Jitsi Meet Integration: Some Thoughts on Content Privacy

The Vodia integration with Jitsi Meet brings secure, self-hosted video conferencing directly into the Vodia PBX web portal. Users can launch meetings with a single click, while organizations maintain control over their infrastructure, meeting content and access. With JWT-based authentication, automatic room creation tied to extensions and controlled guest access, the integration offers a private, scalable alternative to conventional hosted video conferencing platforms while bringing voice and video together in one communications environment.

August 13, 2026