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) which was 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 that SIP almost did not make it into the real world.

While there are plenty of IPv6 addresses, it does not mean that 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 be 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 that devices in the private network should be accessible from the outside only for connections that they have actually initiated. For SIP clients, that is perfectly okay. Actually I even believe that running a SIP IPv6 client behind a NAT for IPv6 with snom ONE would be working perfectly fine. I could not try it out; but looking at the mechanisms it should be working fine: SIP packets that are using TCP or TLS are connection oriented anyway. SIP UDP packets are usually tagged with received parameters, so that the responses find their way back without any issues. RTP packets are also automatically sent back where they come from; I don’t see a reason why that should not work with IPv6.

The only problem with NAT and IPv6 that I see are servers that run in the LAN. We know that problem well from IPv4. However the good news is that it will be relatively simple to get this working perfectly. All that is needed is that the firewall makes an exception for that device in the LAN, so that 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 will not lose any feature that they had with IPv4. Instead, they will have finally the opportunity to expose exactly those servers and services they want to (which includes SIP) while keeping the clients protected from the public Internet.

Derniers articles

Voir tous

The Vodia PBX On-Premise Whisper AI Deployment​

Whisper, OpenAI’s Automatic Speech Recognition system, delivers multilingual, noise-tolerant, and technical-language-ready transcription through a streamlined encoder-decoder architecture. With Vodia PBX’s integration, organizations can choose between using OpenAI’s service or hosting Whisper AI locally for complete data sovereignty and control. This on-premise option ensures that sensitive call data stays within your infrastructure while still benefiting from powerful transcription capabilities. To explore deployment options, see our Whisper AI on-premise setup documentation, review a self-hosted integration example, or follow our cloud-based call transcription guide.

March 27, 2025

Vodia Will Attend Seatrade Cruise Global 2025

Vodia is excited to attend Seatrade Cruise Global 2025, marking the event’s 40th anniversary, taking place in Miami from April 7-10. In partnership with Lufthansa Industry Solutions, Vodia will showcase the Vodia Maritime Communication Server (Vodia MCS)—a next-generation solution designed to seamlessly integrate voice, video, and messaging within cruise ship communications. Engineered for both new vessels and retrofits, the Vodia MCS enhances onboard connectivity, passenger experience, and operational efficiency, while supporting essential maritime safety and security systems. Join us at booth #3608 to discover how Vodia MCS is reshaping onboard communication in the cruise industry.

March 24, 2025

The Vodia PBX Gives Hotels a Peerless Suite of Hospitality Features

Vodia PBX delivers a comprehensive hospitality communication system that enhances guest experience and streamlines hotel operations. With support for multiple device types, seamless PMS integration, in-house call center functionality, and Microsoft Teams connectivity, hotels can optimize efficiency while maintaining high-quality service. Guests can easily access hotel services, communicate with staff, and integrate their personal devices for a seamless and convenient stay. Advanced automation, multilingual support, AI-driven call management, and building automation features further enhance functionality, making Vodia PBX a powerful, scalable solution for modern hospitality environments.

March 20, 2025