Back to Blog
Tech

SIP Gateway behind NAT

Published on:

October 4, 2013

Network Address Translation (NAT) was a workaround for the limited IPv4 addresses, and SIP was designed to be NAT-unfriendly to encourage IPv6 adoption. As IPv6 remains far from mainstream, however, NAT is still a challenge. The Vodia PBX addresses this with a "mini-session border controller" that detects non-routable IPs and ignores SIP routing information. This solution works well with endpoints, but it faces issues with gateways behind NAT. The upcoming version, 5.1.3, introduces a trunk flag to prevent the PBX from updating the SIP route, allowing for better communication. This also simplifies gateway registration, offering a more stable NAT workaround until IPv6 becomes common.

Christian Stredicke

Network Address Translation (NAT) was a hack becasue most of us just get one IPv4 IP address from our provider. SIP was purposely defined NAT-unfriendly to promote the use of IPv6 networks. While we have been waiting for IPv6 to become mainstream for more than a decade now, we have to deal with this reality.

For the SIP phones the Vodia PBX has a logic we call a “mini-session border controller”. It detects when a device runs on a network address that's not routable and then ignores the SIP routing information in it. While this makes our life easier with endpoints, we recently found out life isn't so simple with gateways if they are behind NAT. Here is the setup:

A PSTN gateway runs on a private IP address. On the firewall, the SIP port was forwarded to the private IP address of the gateway so the PBX can send SIP INVITE to the gateway. On the gateway, the outbound proxy is set to the PBX, which runs on a public IP (e.g., on a hosted PBX like the one on our http://hostedi.am).

The problem is this: when the PBX sends an INVITE to the gateway, the gateway responds with its private IP address in the routing headers. In SIP, the UAC (the PBX) is supposed to update the routing information, and there the communication breaks. The PBX can't send the ACK request to the gateway, and the call setup eventually times out.The solution we will introduce in version 5.1.3 is another trunk flag. It will have the name “Don't accept SIP routing changes in dialog” and it does what it's name says: when the PBX receives a response, it sticks to the original destination and doesn't update the route. Because the PBX advertises an address for the media that's routable for the gateway, it will start receiving media from the gateway, and that’s where it sends the media back. Fortunately, most gateways did not follow the IETF proposal to use different ports for sending and receiving, so this also works when the gateway is behind NAT.

This new setting has the potential to render the dial plan feature to send calls to a registered extension obsolete. Instead of registering the gateway to the PBX, the firewall just needs to forward the requests to UDP port 5060 to the gateway. Of course, other ports than 5060 can be easily used. If the public IP address of the local network keeps changing, services like dyndns can help directing the PBX to the right location.

Another workaround for NAT. I can’t wait until IPv6 becomes widely available.

Latest Articles

View All
Announcement

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
Tech

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
Editorial

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