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 Brings the Future of Hospitality Communication to NoVacancy Sydney 2025

Vodia participated in NoVacancy Sydney 2025, Australia’s largest conference and exhibition for the accommodation industry, showcasing its cloud PBX solutions designed specifically for hotels, resorts, and other hospitality venues. With advanced VoIP and AI-driven features, Vodia enables properties to provide guests with seamless, personalized experiences while streamlining operations, reducing costs, and boosting staff efficiency. The company highlighted its recent integration with the Shiji Property Management System (PMS) and Microsoft Teams certification, making it a versatile communication platform for both boutique hotels and multinational chains.

September 26, 2025

The Vodia Call Recordings and Transcription Dashboard

The Vodia Call Recordings and Transcription Dashboard is a modern, powerful tool for businesses to manage and analyze call activity efficiently. Its sleek interface provides a widescreen view of key call metrics including average call length, calls per day, and ongoing calls in real time. With filtering, analytics, transcription, and export options, users can easily access, playback, and share recordings. Designed for industries requiring call recording for legal compliance such as healthcare, government, and utilities, it ensures secure storage, encrypted sharing, and more. Combining robust functionality with a user-friendly design, it helps businesses improve customer service, monitor staff performance, resolve disputes, and gain insights.

September 25, 2025

Small Hotel Phone Systems: 7+1 Reasons Boutique Hotels Need Small Hotel Systems

In today’s fast-paced travel world, boutique hotels must provide seamless, instant communication to meet guest expectations. Vodia PBX offers a complete phone system designed for small hotels, streamlining front desk operations, automating housekeeping and room services, integrating with PMS systems, and supporting advanced features like AI-driven IVR and Teams integration. With proven uptime, robust security, and personalized support, Vodia enables hotels to deliver professional, efficient, and reliable guest experiences, all without outdated hardware or complex setups, while providing the key features that make a boutique property competitive.

September 23, 2025