Difference between revisions of "Router Info Sonicwall"

From IPitomy Wiki
Jump to navigation Jump to search
(Created page with "We have a document on setting up a Sonicwall here: http://www.ipitomy.com/webrelease/Sonicwall/Sonicwall%20Quick%20Guide.pdf Additional info on Sonicwall has been received...")
 
Line 1: Line 1:
We have a document on setting up a Sonicwall here:  
+
[[Category: Router Configuration]]
 +
We have a document on setting up a Sonicwall here:
  
http://www.ipitomy.com/webrelease/Sonicwall/Sonicwall%20Quick%20Guide.pdf
+
[http://www.ipitomy.com/webrelease/Sonicwall/Sonicwall%20Quick%20Guide.pdf http://www.ipitomy.com/webrelease/Sonicwall/Sonicwall%20Quick%20Guide.pdf]
  
 
+
<br/>Additional info on Sonicwall has been received from a customer recently:
Additional info on Sonicwall has been received from a customer recently:
 
  
 
It's seems the process of consistent NAT does not do what it's supposed to across the board therefore I've recommend that it is turned off across our knowledge base. We have verified that enabling an inside--outside rule resolves the problems with dropped calls as it forces the Sonicwall to stick to port 5060.
 
It's seems the process of consistent NAT does not do what it's supposed to across the board therefore I've recommend that it is turned off across our knowledge base. We have verified that enabling an inside--outside rule resolves the problems with dropped calls as it forces the Sonicwall to stick to port 5060.

Revision as of 21:09, 24 April 2013

We have a document on setting up a Sonicwall here:

http://www.ipitomy.com/webrelease/Sonicwall/Sonicwall%20Quick%20Guide.pdf


Additional info on Sonicwall has been received from a customer recently:

It's seems the process of consistent NAT does not do what it's supposed to across the board therefore I've recommend that it is turned off across our knowledge base. We have verified that enabling an inside--outside rule resolves the problems with dropped calls as it forces the Sonicwall to stick to port 5060.