Versions Compared

Old Version 5

changes.mady.by.user Former user

Saved on

compared with

New Version 6

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
  • Disable any SIP ALG functionality in the Local NAT - such features are almost always incomplete and/or buggy and cause far more trouble than benefits.
  • If the firewall is enabled, create a firewall rule that will allow TCP and UDP packets destined to the 'Public SIP Port' designated in Step 2.
  • Create a port forwarding NAT rule that will forward TCP and UDP packets destined to the 'Public SIP Port' designated in Step 2 to the IP address of the sipXecs.
  • If the firewall is enabled, create a firewall rule that will allow UDP packets destined to the range of  ports created by the 'Start RTP port' and 'End RTP port' in step 2.
  • Create a port forwarding NAT rule that will forward UDP packets destined to the port range formed by  [Start RTP port - End RTP port'[ to the IP address of the sipXecs.

High Availability Consideration:  If the sipXecs deployment is a High-Availability (HA) one, firewall rules need to be created to allow each sipXecs server's Public Port and SIP Port and RTP port range.  Also, NAT forwarding rules must be created to forward each Public Port and SIP Port and RT Port range to the IP address of their corresponding sipXecs. For example:

  1. If sipXecs Server 1 has Public Port of SIP Port of '5060' and RTP port range for [30000-31000[ then ports 5060 and [30000-31000[ must be allowed and forwarded to the IP address of Server 1.
  2. If sipXecs Server 2 has Public Port of SIP Port of '11060' and RTP port range for [31000-32000[ then ports 11060 and [31000-32000[ must be allowed and forwarded to the IP address of Server 2.
  3. If sipXecs Server 3 has Public Port of SIP Port of '12060' and RTP port range for [32000-33000[ then ports 12060 and [32000-33000[ must be allowed and forwarded to the IP address of Server 3.

...

  • Carefully review the configuration steps contained in this guide
  • Phone's outbound proxy is configured with routable IP address associated with sipXecs and that address can be pinged from a machine inside the remote network
  • Phone is configured with the proper SIP domain, SIP username and SIP password
  • If sipXecs is behind a local NAT, ensure that the pinholes and port forwarding rules have been created as per configuration step #5.
  • Verify that STUN and ICE (if supported) are disabled in the remote phone
  • Verify that SIP ALGs are disabled in both the remote and local NATs
  • Verify that the 'Use external SBC for Internet Calling' checkbox is unchecked in 'System->Internet Calling' 
  • Review the alarm history and look for reported NAT traversal-related failures.  The alarm history can be found in sipXconfig under 'Diagnostics->Alarms->History'.  Be sure to select a wide-enough date range to cover the last reboot of the box.

...