Router Info

From IPitomy Wiki
Jump to: navigation, search

This page contains general information about port forwarding and disabling application layer gateways on particular routers.

Router Compatibility List

Contents

Sonicwall

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.

Mikrotik

This router has an ALG that can be disabled with the following command

  • /ip firewall service-port disable sip

The info was found at the following two links Mikrotik Wiki Mikrotik Forum

Fortigate

I found this online about solving issues with Fortigate routers and NO AUDIO with remote SIP:

In the command line of the fortigate type the following:

  • config system settings
  • set sip-helper disable
  • set sip-nat-trace disable

Reboot the device

In the command line type the following:

  • config system session-helper
  • show

(now look for SIP, mostly it will be "12")

  • delete 12

Don't use any protection profiles on the firewall of the sip rules.

Cisco Pix 506/501/515 and Cisco ASA

This is for Pix 506/501/515 but it should work with any Cisco Pix, and possibly other Cisco
routers.
  1. access-list 101 permit udp any host 64.238.XXX.XXX range 10000 20000
    (Note: Replace 64.238.XXX.XXX with your public IP assigned to be forwarded to the IPitomy PBX)
  2. access-list 101 permit tcp any host 64.238.XXX.XXX range 10000 20000
    (Note: Replace 64.238.XXX.XXX with your public IP assigned to be forwarded to the IPitomy PBX)
  3. static (inside,outside) 64.238.XXX.XX 172.16.2.129 netmask 255.255.255.255 0 0
    (Note: Replace 64.238.XXX.XXX with users public IP, replace the 172.16.2.129 with users private IP that is assigned to the IPitomy PBX)
  4. no fixup protocol sip 5060
  5. no fixup protocol sip udp 5060

Adtran

From a recent interaction with an AdTran tech, it was shown to us there is a setting for "proxy transparency" that needs to be enabled in order for all of the SIP traffic to pass unhindered. This was when the Adtran was the routing device at the remote site, but likely would need to be enabled when the Adtran is at the PBX site. Its worth trying for sure.

PepLink

Here is a document sent to a dealer from PepLink regarding configuration settings that may be required for Remote SIP to function properly:


Pdf:Peplink Config.pdf

FIOS ActionTec

We have found the following article that outlines some possible configurations that are available on the Actiontec Modem/Router combo that FIOS is installing. This gives some options on ways to configure to optimize VoIP and SIP traffic passing to remote.

http://www.dslreports.com/faq/verizonfios/3.0_Networking#16077

Comcast Modem

We have received some information from our dealers that if your site has a Comcast modem/router, you should request a SMC and not a Linksys, as the reports are that the SMC handles VoIP more consistently. Additionally, there may be issues with Comcast modem/routers ability to handle multiple concurrent NAT sessions, limiting the number of remote phones you can install at a remote site.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox