...
| Panel |
|---|
- "Enable NAT Traversal": Check this box - this will effectively enable the Remote User NAT Traversal feature
- "Server behind NAT": If the sipXecs is deployed inside a private network, check this box (this internally enables the near-end NAT traversal logic), otherwise leave blank.
|
Image Removed
Image Added
Step 2 - configuring public IP address of sipXecs
...
| Panel |
|---|
- If the WAN-facing IP address of the Local NAT is static then select "Specify IP address" and enter it under "Public IP Address". Instead, if the WAN-facing IP address is dynamic (i.e. your ISP changes it from time to time), select "Use STUN" and enter a STUN server address in the "STUN Server" field (stun01.sipphone.com is a somewhat reliable public STUN server that could be used here). If you are unsure, find out by asking your ISP and use 'Use STUN' until you get your definitive answer.
- Keep all other fields as defaults.
|
Image RemovedImage Added
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 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:
...