[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1908
  • Last Modified:

Route all voip traffic to secondary gateway on sonicwall

I need to route all voip traffic to our secondary gateway(x2). In the event there is an issue with the X2, I would like it to use the primary gateway (x1). I am using a sonicwall tz200 with basic failover setup. Any ideas?
  • 2
1 Solution
please do followings;

1) Create on AO for your VOIP Phones Network...logon to SNA> Network > Address Objects

Name: VOIP Phones
Zone Assignment: LAN
Type: Range
Starting IP Address:, VOIP Phones First ip
Ending IP Address: VOIP Phones Last IP


now in order to route traffic to Secondary Gateway,,, do as followings;

Login to the SonicWALL Network Appliance and go to Network >Routing > add
Source:      VOIP Phones
Destination:       Any
Service:       Any
Gateway:       Secondary Default Gateway
Interface:       X2
Metric:       20
Comment:       VOIP Phones Static Route

Select the Disable route when the interface is disconnected checkbox to have the route automatically disabled when the interface is disconnected. i Recomend to CHECK this BOX....

for more routes please look at my article on EE http://www.experts-exchange.com/Hardware/Networking_Hardware/Firewalls/A_6509-Network-Traffic-Routing-in-Sonicwall.html
dave1184Author Commented:
I have a rule like that setup currently. My concern is if that X2 goes down will traffic be able to go out X1? We conducted a test where we failed X2 and the phones could not get to X1.
i understand your concrens,,,
you need to do routing and enable probe so if ISP is down (modem and interface both are up) SNA probe will deduct the service is down and disable specic route.... please read below

Static Route Configuration
In SonicOS Enhanced, a static route is configured through a basic route policy. To configure a static route, complete the following steps:

Step 1  Scroll to the bottom of the Network > Routing page and click on the Add button. The Add Route Policy window is displayed.  

Step 2  From the Source menu, select the source address object for the static route, or select Create new address object to dynamically create a new address object.  

Step 3  From the Destination menu, select the destination address object.  

Step 4  From the Service menu, select a service object. For a generic static route that allows all traffic types, simply select Any.  

Step 5  From the Gateway menu, select the gateway address object to be used for the route.  

Step 6  From the Interface menu, select the interface to be used for the route.  

Step 7  Enter the Metric for the route. The default metric for static routes is one. For more information on metrics, see the “Policy Based Routing” section  

Step 8  (Optional) Select the Disable route when the interface is disconnected checkbox to have the route automatically disabled when the interface is disconnected.  

Step 9  (Optional) The Allow VPN path to take precedence option allows you to create a backup route for a VPN tunnel. By default, static routes have a metric of one and take precedence over VPN traffic. The Allow VPN path to take precedence option gives precedence over the route to VPN traffic to the same destination address object. This results in the following behavior:  

  •  When a VPN tunnel is active: static routes matching the destination address object of the VPN tunnel are automatically disabled if the Allow VPN path to take precedence option is enabled. All traffic is routed over the VPN tunnel to the destination address object.  

  •  When a VPN tunnel goes down: static routes matching the destination address object of the VPN tunnel are automatically enabled. All traffic to the destination address object is routed over the static routes.  

Step 10  The Probe, Disable route when probe succeeds, and Probe default state is UP options are used to configure Probe-Enabled Policy Based Routing. See the following “Probe-Enabled Policy Based Routing Configuration” section for information on their configuration.  

Step 11  Click OK to add the route.  

Probe-Enabled Policy Based Routing Configuration
When configuring a static route, you can optionally configure a Network Monitor policy for the route. When a Network Monitor policy is used, the static route is dynamically disabled or enabled, based on the state of the probe for the policy.

Step 1  Configure the static route as described in “Static Route Configuration” on page 252.  

Step 2  In the Probe pulldown menu select the appropriate Network Monitor object or select Create New Network Monitor object... to dynamically create a new object. For more information, see “Network > Network Monitor” on page 339.  

Step 3  Typical configurations will not check the Disable route when probe succeeds checkbox, because typically administrators will want to disable a route when a probe to the route’s destination fails. This option is provided to give administrators added flexibility for defining routes and probes.  

Step 4  Select the Probe default state is UP to have the route consider the probe to be successful (i.e. in the “UP” state) when the attached Network Monitor policy is in the “UNKNOWN” state. This is useful to control the probe-based behavior when a unit of a High Availability pair transitions from “IDLE” to “ACTIVE,” because this transition sets all Network Monitor policy states to “UNKNOWN.”  

Step 5  Click OK to apply the configuration.

refer to below kb;


Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now