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
Tech

Why Vodia is the Ideal PBX for Microsoft Environments

Many organizations rely on Microsoft as the foundation of their daily operations, but their communication systems often exist in parallel rather than in harmony. Vodia closes that gap by bringing telephony into the same environment where teams already work, turning separate systems into one connected structure. This approach removes friction between platforms, simplifies management, and gives IT teams better control and visibility over daily communication. It also creates a more seamless experience for employees, reduces operational overhead, and builds a stronger, more flexible foundation that supports growth, collaboration, and long-term scalability.

October 17, 2025
Announcement

Vodia to Attend CVxExpo 2025 in Glendale, Arizona

Vodia will be attending CVxExpo 2025 in Glendale, Arizona, from November 3–5. Sales Engineer Eric Altman will be on site to meet with current and prospective partners, demonstrating how Vodia’s PBX solutions can strengthen technology roadmaps for 2026. This year, Vodia highlights new integrations with ActiveCampaign, Freshdesk, HighLevel, Microsoft 365, Microsoft Presence, monday.com, and Odoo Cloud, along with enhanced call center capabilities such as agent activity dashboards, call recordings, and transcription features. Partners and attendees can schedule meetings with Eric to learn more about scalable, feature-rich, and cost-effective telecommunications solutions built for enterprises and SMBs.

October 14, 2025
Tech

Enterprise Call Analytics: Real-Time Insights Built Right Into Your PBX

Vodia Enterprise Call Analytics gives businesses comprehensive, real-time insights into every aspect of their call operations. Built natively into the PBX, it delivers live, color-coded dashboards, detailed call records, smart filtering, and exportable data. Enterprises can track key metrics such as answer rates, call volume, peak hours, talk times, and top performers, while also monitoring call quality through integrated MOS scoring. By turning call data into actionable intelligence, Vodia helps organizations optimize team productivity, improve customer experience, manage costs effectively, streamline workflows efficiently, and make smarter, data-driven decisions that contribute directly to revenue, operational performance, and long-term ROI.

October 10, 2025