SonicWall second WAN interface, no audio

Status
Not open for further replies.

Ianing

Customer
Joined
Nov 14, 2019
Messages
6
Reaction score
0
Some 5-20 minutes after I enable the second WAN interface on my SonicWall firewall, audio no longer works in calls. I can still place calls but neither side can hear each other. Everything is fine until shortly after I enable the second WAN interface. Failover is not yet configured.

I created a route for 3CX services to the primary interface but it didn't help. Any suggestions where to start?
 
If you follow the 3CX firewall instructions for SonicWall at https://www.3cx.com/docs/sonicwall-firewall-configuration/ you will need to specify the WAN interface to use. This will keep all voice and 3CX traffic using the desired interface while you have load balancing enabled.

This does make failover manual, unless you really dig in and setup secondary routes AND update the 3CX DNS. Due to that issue we try to cloud host any site that has dual WAN connections and use an SBC at the site because the SBC does not care - it will just use whatever internet connection the SonicWall tells it to use.

In your rules replace the "WAN" interface option with the corresponding X1 option. (Assuming your primary WAN is in the default X1 port.) This will force the SIP traffic over the correct WAN.

Inbound NAT Policy:
Original Destination: X1 IP (default is WAN Interface IP)
Outbound Interface: X1 (default is Any)

Outbound NAT Policy:
Translated Source: X1 IP (default is WAN Interface IP)
Inbound Interface: X1 (Default is Any)

Been a while since doing one. Hopefully I caught them all.

Hope this helps.
 
Thanks [B]accentlogic[/B]. I chose not use a SBC because failback to POTS was a priority. Now it's possible I was mistaken and didn't see a solution but we've been generally happy. X3 is my primary WAN and X1 is secondary.

Unfortunately, with the inbound NAT Policy, I can't set outbound interface to x3. The Sonicwall error is "Original Source: Cannot set Outbound Interface for Destination Remap ". Which I haven't been able to find any more information on.

My settings are as follows.
3CX Inbound NAT policy
Any
Original
Wan Interface IP
3CX PBX Address Object
3CX Services
Original
X3
Any
Enabled

3CX Outbound NAT Policy
3CX PBX Address Object
X3 IP
Any
Original
Any
Original
Any
X3
Enabled
Disable Port Source Remap
 
Thanks [B]accentlogic[/B]. I chose not use a SBC because failback to POTS was a priority. Now it's possible I was mistaken and didn't see a solution but we've been generally happy. X3 is my primary WAN and X1 is secondary.

Unfortunately, with the inbound NAT Policy, I can't set outbound interface to x3. The Sonicwall error is "Original Source: Cannot set Outbound Interface for Destination Remap ". Which I haven't been able to find any more information on.

Good point - if you have local dial tone you should have the PBX local.

You don't need to disable source port remap on inbound, only outbound.

Try these settings:

3CX Inbound NAT policy
Any
Original
X3 IP (was Wan Interface IP)
3CX PBX Address Object (LAN IP)
3CX Services
Original
X3
Any
Enabled

3CX Outbound NAT Policy
3CX PBX Address Object (LAN IP)
X3 IP
Any
Original
Any
Original
Any
X3
Enabled
Disable Port Source Remap
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,962
Messages
589,993
Members
164,867
Latest member
swegner