Sonicwall – Important Update, NAT HotFix

Sonicwall StackFollowing our previous post regarding Sonicwall’s NAT limitation, 3CX is pleased to announce that a SonicOS update was released which enables clients and partners to use these devices in front of the 3CX Phone System as NAT device. With this change, VoIP Providers and direct remote extensions (STUN) can be connected to the 3CX Phone System and are covered by the 3CX Support team as a supported setup.

Take a look at our updated our Sonicwall configuration guide with detailed instructions to help you configure your Sonicwall device.

DELL Sonicwall reference ID: KB HF152075

Liked this article?

Get notified of new articles
or share
You might also be interested in:
  1. Nuit

    Does this fix suggest the Sonicwall works fine without the fix when a public static IP address, other than the Sonicwall’s Primary WAN IP address (X1), is NAT’d to the 3CX Server?

    If yes, that explains why quite a few of us have successfully been using Sonicwall and 3CX together for a number of years.

    October 14, 2014 at 6:15 pm
    • Yes, if you have an IP address to spare for the 3CX Phone System and use this dedicated for a 1-to-1 NAT then you don’t need to apply the fix.
      The most common case is the 1-to-Many NAT, even without a static IP address in the WAN interface. These cases are now covered by the fix.

      October 15, 2014 at 9:35 am
  2. Jon Rapoport

    The following manual from Sonicwall is very good for one-on-one nat. The user manual that is specific to the Sonicwall TZ routers is very poor and a little contradictory at describing how to set this up.

    http: //

    Testing now. Very happy to have my favorite router brand properly support 3CX!

    October 17, 2014 at 2:05 am