Difference between revisions of "Router Info Sonicwall"
Jump to navigation
Jump to search
WARNING!
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. |
Revision as of 20:46, 29 November 2018
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:
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.