We have set up a Patton VoIP-gateway behind a SonicWall TZ170W (which has a public IP on the WAN-port).
We have forwarded UDP-ports: 5060, 16300->16700, 4864-5118 and 4865-5119 to the VoIP-gateway's IP-address. By the ISP's recommendation, everything under VoIP-settings is disabled. The firewall is setup to allow all traffic from LAN to everything.
When we pick up a phone here on the inside and dial out, everything works properly. However, when somebody calls in, we can hear them, but they cannot hear us.
An expert who has achieved level 3 by getting 1000 points
An expert that got 20 achievements.
An expert that got 10 achievements.
An expert that got 5 achievements.
Re: Patton SIP / VoIP problem behind TZ170W
How about a simpleton's laziest answer is------------ switching/enabling/allow/accept just what you yourself go against-------- exactly the opposite(like drinking alcohol or not wearing an Helmet whenever u go out on ur bike is injuriousdangerous or like stutary warning Z ! Do not try to open the cover yourself(&a yellow triangle with a cross) but we still do it, I mean, OK at the most i'll get a shock, cool so what, I won't be fried, right!!?
And do against these "danger/hazardous" your ISP recommendation Quote---By the ISP's recommendation, everything under VoIP-settings is
disabled. The firewall is setup to allow all traffic from LAN to
everything.----------unquote. So I can't differentiate/understand everything. BUT FIREWALL IS ALLOWED; is that not true for EVERYTHING so how about the interface, its function includes this as everythig but not everywhere its blocked so unless allowed to go out but door has topend to allow some in OR out. Crude but logical.....sodeep
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
The high-level answer is to get the login parameters and internal IP for the Sonicwall, get the Internet parameters for your new ISP, and then log into the Sonicwall device, go to Networking-> Interfaces, and configure the WAN adapter with those settings.
So I can understand better... You are trying to move DHCP off of your Small Business Server and on to a router that is connected to your firewalls WAN? I don't understand why you are trying to block the connection between your router and your server. Once you turn off DHCP on your server and remove the static IP on it, it should get a new address from your router.
This is not directly possible to do with a TZ170 as the device will only allow configuration for 1 static or dynamic IP at a time for the WAN port. However this being the case, I suggest setting the SonicWALL up as a perimeter firewall and place devices that require the other public IPs form the additional IP range behind the TZ170. Basically the SonicWALL becomes the gateway for the other IPs needed as long as the range of the IP block is contiguous. This would involve using the 4 ports of the LAN on the back of the TZ170 to connect directly to the other devices or if it is more then 4 devices, using a switch connected to the LAN side of the SonicWALL to provide connectivity to the multiple devices behind it. Most TZ170 are licensed for 10 connections on the LAN side and if you require more then 10, additional licenses will need to be purchased. I would be careful pushing too much traffic through a TZ170 as it is designed for Small Business use and will quickly become overloaded with too much traffic causing high latency/traffic bottlenecks and in extreme cases connections being dropped. This is especially true for multiple VPNs.
Please find below is to configure what ever you want.
Setup Wizard - This wizard will help you quickly configure the SonicWALL to secure your Internet connection. Once completed, you can use the SonicWALL Web Management Interface for additional configuration.
Registration & License Wizard - This wizard will help you register you and your firewall with mysonicwall.com and obtain licenses for additional Security Services features.
PortShield Interface Wizard - Segment and configure the integrated managed LAN switch of the SonicWALL.
Public Server Wizard - Quickly configure your SonicWALL to provide public access to an internal server.
VPN Wizard - Create a new site-to-site VPN Policy or configure the WAN GroupVPN to accept connections from the SonicWALL Global VPN Client
Saibrains is correct unless your firmware is of earlier version. you might have to upgrade your firmware. Also you can not use a port #
No ports required for Ping as it uses icmp packets
It needs to allow icmp 'echo-request' (type 8) packets out and icmp 'echo-reply' (type 0) packets in
to allow ping request. On earlier versions of the sonicwall firmware it only absorbed Ping request as to stop hackers from ping attacking pass the firewall.
check the manufactures website for your model and see if they have newwer firmware.
The GUI should have a place where you can set it up
open control panel and then add printers and other hardware, then up in left hand menu go to system then hardware, device managed and check if your driver is updated. if it says it's working properly then uninstall it and it'll pop back up reinstall then it should work fine.
If you're within a network and try connecting to computers on it with the WAN public IP, it simply won't work - you must use the network IP.
On an external Internet connection, it should connect fine to the public IP. If you have access to an external machine (remote desktop), or if you know of an FTP proxy, you can try it that way.
I also believe http://www.webftp.co.uk/ a web based FTP client would act as somewhat of a proxy, you could try that with the public IP and see how you go.