Filter
Top Products
VoIP Settings
826
SonicOS 5.8.1 Administrator Guide
Generic Deployment Scenario
All three of the follow deployment scenarios begin with the following basic configuration
procedure:
Step 1 Enable bandwidth management on the WAN interface on Network > Interfaces.
Step 2 Configure SIP or H.323 transformations and inactivity settings on VoIP > Settings.
Step 3 Configure the DHCP Server on the Network > DHCP Server page with static private IP address
assignments to VoIP clients.
Step 4 Enable SonicWALL Intrusion Prevention Service to provided application-layer protection for
VoIP communications on the Security Services > Intrusion Prevention page.
Step 5 Connect VoIP Clients to network.
Deployment Scenario 1: Point-to-Point VoIP Service
The point-to-point VoiP service deployment is common for remote locations or small office
environments that use a VoIP end point device connected to the network behind the firewall to
receive calls directly from the WAN. The VoIP end point device on the Internet connects to VoIP
client device on LAN behind the firewall using the SonicWALL security appliance’s Public IP
address. The following figure shows a point-to-point VoIP service topology
This deployment does not require a VoIP server. The Public IP address of the SonicWALL
security appliance is used as the main VoIP number for hosts on the network. This requires a
static Public IP address or the use of a Dynamic DNS service to make the public address
available to callers from the WAN. Incoming call requests are routed through the SonicWALL
security appliance using NAT, DHCP Server, and network access rules.
To make multiple devices behind the SonicWALL security appliance accessible from the public
side, configure One-to-One NAT. If Many-to-One NAT is configured, only one SIP and one NAT
device will be accessible from the public side. See “” for more information on NAT.
(Corporate Office)
(Remote Office)
Public: VoIP Clients
E7500
W0
wlan wan
X2X3X4X5X6
activity
security
on/act
TZ 210
wireless-N