Versions Compared

Old Version 6

changes.mady.by.user Former user

Saved on

compared with

New Version 7

changes.mady.by.user Former user

Saved on

Key

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

...

High Availability Consideration:  If the sipXecs deployment is a High-Availability (HA) one, Remote NAT Traversal can still work but the HA brings about a few complexities with respect to step 2.  Basically, Step 2 has to be repeated for each server found under "System->Servers" and each server must be configured with unique a 'Public SIP Port" value and non-overlapping RTP port ranges as defined by the 'Start RTP port' and 'End RTP port' fields found under the 'Advanced Settings".  So for example, if the HA deployment has 3 servers, the following settings could be used:

  1. sipXecs Server 1 has Public Port of SIP Port of '5060' and RTP port range for [30000-31000[
  2. sipXecs Server 2 has Public Port of SIP Port of '11060' and RTP port range for [31000-32000[
  3. sipXecs Server 3 has Public Port of SIP Port of '12060' and RTP port range for [32000-33000[

...

Panel
  • Begin by deleting all the default entries in "Intranet subnets" as they are almost always wrong.
  • In "Intranet subnets", add as many entries as required to describe the local private network that sipXecs is a part of.  For example, if your sipXecs  is part of the private network 10.10.10.0/24 then you need to have a single "Intranet subnets" entry of "10.10.10.0/24".
  • In "Intranet Domains", the default provided is almost always all you need - leave it as is.
  • [xecsuserV4r2:Important] Make sure that 'Use external SBC for Internet Calling' check box is disabled. This setting may only be only useful when using a session border controller other than sipXbridge.

...