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

Transforming Maritime Connectivity with MS Teams: A Communication Solution for Cruise Ships

Reliable communication is essential for cruise ship safety, operational efficiency, and an exceptional guest experience, yet it faces unique challenges including remote connectivity, signal interference from metal structures, and stringent network security requirements. The Vodia PBX, now certified for MS Teams, offers seamless satellite integration, emergency calling, and direct communication between crew and passengers. This combination ensures continuous 24/7 connectivity, supports emergency protocols, and enhances onboard collaboration.

June 5, 2025

Embrace Unparalleled Digital Diversity and Secure Data Ownership with the Vodia PBX

Vodia gives you full control over your communications with operating system independence, multi-cloud VoIP capability, and complete data ownership. Whether you deploy on-premise, in your own data center, or across major cloud platforms like AWS or Azure, Vodia’s flexibility ensures resilience, scalability, and freedom from vendor lock-in. With support for multiple OS environments and features like zero-touch provisioning and redundant SIP trunks, it’s a future-proof solution built for secure, adaptable business communications.

June 3, 2025

The Vodia PBX Now Integrates with ActiveCampaign

Vodia’s latest integration with ActiveCampaign brings together a powerful cloud PBX system and a leading customer experience automation platform. This integration enables businesses to automatically track and manage customer interactions by creating and updating contacts based on call activity, recording detailed call information, and linking calls to the appropriate users within ActiveCampaign. By combining Vodia’s advanced telephony features with ActiveCampaign’s AI-driven marketing and sales automation tools, companies can deliver more personalized experiences, improve team productivity, and drive growth through smarter, data-backed communication.

May 29, 2025