Not with a SonicWall, per se, but with other routing firewalls where the VoIP provider insists that it's the firewall causing problems and wants us to put in a different firewall for the VoIP network. I've done this multiple times with no issues. Otherwise, it won't care what the other IP addresses are being used for or on (that's like saying that you can't use 192.168.1.6 for your mail server since your DC is at 192.168.1.5 and they're both on the same /24 subnet internally). 198 address would be if you've got that IP address explicitly setup on there as an alternate IP. The only reason the SonicWall would be looking at the. Otherwise, we're (the Spiceworks community) around to help, as well. SonicWALL support can help you get that setup and working correctly, assuming you've got a valid support contract with them, if you're not sure on exactly what to do. I'm guessing that you haven't allocated all your available ports to the internal network? If not, assign one port to the VoIP network and route the public IP through to there. If possible, try moving it all under your SonicWALL device. I've had issues in the past with some of their equipment and, once replaced, didn't have those issues anymore (network drops, lockups, weird issues with configurations not taking effect correctly, etc). Then again, I may just be showing my bias against TP Link (which others on here have renamed to Toilet Paper Link). The TPlink is then connected to a cisco SF300-24P POE switch that has only the voip phones on it. It goes directly to the cable modem/router supplied by optimum. It does not connect to the NSA220 at all. The other router is a relatively inexpensive TPlink TL-R470T +. How should I have this set up correctly so that 4 IP's (really only need two) are on the NSA220, and the other one is free to use for the phone system. We have intermittent connectivity issues and I'm wondering if its because the NSA220 is also looking at traffic on that IP. Here is the problem: I have a separate router for our VOIP phone system, and have it set to the last *.198 IP address as its address. I could never figure out how to explicitly program multiple IPs, I could only get it to work using the network mask. Firewall routing for the two services works just fine on their unique ID. In my understanding this means that the router is looking for traffic on all 5 IP's. I have the NSA 220 Wan IP address set as *.*.*.194 and 255.255.255.248 as the network mask. This is all working great on a SonicWall NSA220. I have an exchange server running, and also terminal services/remote desktop applications. They start with *.*.*.193 as the default gateway, and 194-198 as the usable IP addresses.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |