Router Info Sonicwall - Revision history

Mike Lunn at 19:27, 12 January 2022

2022-01-12T19:27:11Z

Mike Lunn: complete sonicwall info revamp

2021-11-18T18:47:34Z

complete sonicwall info revamp

Mike Lunn at 16:36, 13 August 2020

2020-08-13T16:36:06Z

Mike Lunn at 16:35, 13 August 2020

2020-08-13T16:35:45Z

Mike Lunn at 14:17, 10 May 2019

2019-05-10T14:17:29Z

Mike Lunn at 14:16, 10 May 2019

2019-05-10T14:16:40Z

Mike Lunn at 14:15, 10 May 2019

2019-05-10T14:15:51Z

Mike Lunn at 20:46, 29 November 2018

2018-11-29T20:46:15Z

Mike Lunn at 20:45, 29 November 2018

2018-11-29T20:45:42Z

Mike Lunn at 19:41, 6 December 2016

2016-12-06T19:41:54Z

@@ Line 35: / Line 35: @@
 After that go to the Advanced tab and check the box for "Disable Source Port Remap" and click OK.<br/>
-[[File:Sonicwallspr.PNG]]<br/>
+[[File:Sonicwallspr.PNG|link=Special:FilePath/Sonicwallspr.PNG]]<br/>
 Once completed the PBX will always use the proper source ports on the WAN side.
@@ Line 66: / Line 66: @@
 </table>
-Navigate to the Advance tab and reduce the UDP timeout to 30 seconds, once saved phones should remain REACHABLE.
+Navigate to the Advance tab and increase the UDP timeout to 300 seconds, once saved phones should remain REACHABLE.

@@ Line 1: / Line 1: @@
-We have a document on setting up a Sonicwall here:
+===Disable SIP Header Transformations and Enable Consistent NAT===
-[http://www.ipitomy.com/webrelease/Sonicwall/Sonicwall%20Quick%20Guide.pdf http://www.ipitomy.com/webrelease/Sonicwall/Sonicwall%20Quick%20Guide.pdf]<br/>
+SonicWALL SIP ALG is called SIP Header Transformations, this should be Disabled and Consistent NAT should be Enabled:<br/>
-We have seen that having IPS turned on with the check box for Prevent Low Priority Attacks checked can cause issues with some calls not going through.  If you are having intermittent call failures try disabling this setting.<br/>
+===Create Outbound NAT Policy and Disable Source Port Remap===
-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.  To configure this, create a NAT rule as follows:<br/><br/>
+In some cases the SonicWALL will remap the 5060 and 10000-20000 UDP source ports causing one way audio and calls dropping after 30 seconds.
-After that go to the Advanced tab and check the box for "Disable Source Port Remap" and click OK.  The system will now talk to us from source port 5060.<br/>
+To resolve this, create an inside to outside rule like the following:
-=== '''WARNING!'''<br/> ===
+Most often seen in cloud deployments you will see phones going REACHABLE/UNREACHABLE with complaints of calls going directly to voicemail and BLFs not lighting properly.
-VoIP phones behind a firewall running SonicOS 6.2.7.1 cannot make outbounds calls, although inbound calls and phone registration are working fine. Occurs when the internal SIP device uses a port that is different from the source port (the port associated with the Via or Contact fields), and when the remote device sends packets to this port, the firewall is not forwarding them to the internal device.
+To fix this add a LAN to WAN Access Policy as follows:

@@ Line 3: / Line 3: @@
 [http://www.ipitomy.com/webrelease/Sonicwall/Sonicwall%20Quick%20Guide.pdf http://www.ipitomy.com/webrelease/Sonicwall/Sonicwall%20Quick%20Guide.pdf]<br/>
-We have seen that having IPS turned on with the check box for Prevent Low Priority Attacks checked can cause issues with some calls not going through.  If you are having intermittent call failures disables this setting.<br/>
+We have seen that having IPS turned on with the check box for Prevent Low Priority Attacks checked can cause issues with some calls not going through.  If you are having intermittent call failures try disabling this setting.<br/>
 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.  To configure this, create a NAT rule as follows:<br/><br/>

@@ Line 1: / Line 1: @@
 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 http://www.ipitomy.com/webrelease/Sonicwall/Sonicwall%20Quick%20Guide.pdf]<br/>
 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.  To configure this, create a NAT rule as follows:<br/><br/>

← Older revision		Revision as of 14:17, 10 May 2019
Line 2:		Line 2:

	[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 http://www.ipitomy.com/webrelease/Sonicwall/Sonicwall%20Quick%20Guide.pdf]
−
−	~~<br/>Additional info on Sonicwall has been received from a customer recently:~~

	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. To configure this, create a NAT rule as follows:<br/><br/>		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. To configure this, create a NAT rule as follows:<br/><br/>

← Older revision		Revision as of 14:16, 10 May 2019
Line 15:		Line 15:
	Outbound Interface: WAN interface (X1 for example)<br/><br/>		Outbound Interface: WAN interface (X1 for example)<br/><br/>

−	After that go to the Advanced tab and check the box for "Disable Source Port Remap". The system will now talk to us from source port 5060.<br/>	+	After that go to the Advanced tab and check the box for "Disable Source Port Remap" and click OK. The system will now talk to us from source port 5060.<br/>

← Older revision		Revision as of 14:15, 10 May 2019
Line 5:		Line 5:
	<br/>Additional info on Sonicwall has been received from a customer recently:		<br/>Additional info on Sonicwall has been received from a customer recently:

−	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.	+	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. To configure this, create a NAT rule as follows:<br/><br/>
		+	Original Source: PBX Private IP<br/>
		+	Translated Source: IP of the WAN interface (X1 IP for example)<br/>
		+	Original Destination: Address Group for our SIP servers (52.5.220.123 or 54.200.236.200)<br/>
		+	Translated Destination: Original<br/>
		+	Original Service: Service Group including 5060 UDP and 10000-20000 UDP<br/>
		+	Translated Service: Original<br/>
		+	Inbound Interface: Any<br/>
		+	Outbound Interface: WAN interface (X1 for example)<br/><br/>
		+
		+	After that go to the Advanced tab and check the box for "Disable Source Port Remap". The system will now talk to us from source port 5060.<br/>

← Older revision		Revision as of 20:46, 29 November 2018
Line 7:		Line 7:
	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.		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.

−	WARNING VoIP phones behind a firewall running SonicOS 6.2.7.1 cannot make outbounds calls, although inbound calls and phone registration are working fine. Occurs when the internal SIP device uses a port that is different from the source port (the port associated with the Via or Contact fields), and when the remote device sends packets to this port, the firewall is not forwarding them to the internal device.	+
		+
		+	=== '''WARNING!'''<br/> ===
		+
		+	VoIP phones behind a firewall running SonicOS 6.2.7.1 cannot make outbounds calls, although inbound calls and phone registration are working fine. Occurs when the internal SIP device uses a port that is different from the source port (the port associated with the Via or Contact fields), and when the remote device sends packets to this port, the firewall is not forwarding them to the internal device.

← Older revision		Revision as of 20:45, 29 November 2018
Line 1:		Line 1:
−	~~[[Category: Router Configuration]]~~
	We have a document on setting up a Sonicwall here:		We have a document on setting up a Sonicwall here:

Line 7:		Line 6:

	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.		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.
		+
		+	WARNING VoIP phones behind a firewall running SonicOS 6.2.7.1 cannot make outbounds calls, although inbound calls and phone registration are working fine. Occurs when the internal SIP device uses a port that is different from the source port (the port associated with the Via or Contact fields), and when the remote device sends packets to this port, the firewall is not forwarding them to the internal device.

← Older revision		Revision as of 19:41, 6 December 2016
Line 6:		Line 6:
	<br/>Additional info on Sonicwall has been received from a customer recently:		<br/>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.	+	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.