and the remote works firewall.
don
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Matt White
Sent: Monday, February 20, 2012 4:00 PM
To: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] Sipxecs 4.4 / NAT traversal / Server behind NAT
-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Matt White
Sent: Monday, February 20, 2012 4:00 PM
To: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] Sipxecs 4.4 / NAT traversal / Server behind NAT / 5
min drop
With a true public ip you
: [sipx-users] Sipxecs 4.4 / NAT traversal / Server behind
NAT / 5 min drop
With a true public ip you will want the following settings
Server behind NAT: off
PUBLIC IP: enter the public ip
Intranet Subnet: what you have is fine (assuming you dont have any
natted remote workers on that subnet
Hi Matt,
The NIC in the Sipx box has a true public IP address. The unit is safe guarded
by a true bridging firewall that is transparent to the sipx machine. Only the
required traffic is passed true. No NAT or any port forwarding involved.
The Public ip address under Internet calling tab is
With a true public ip you will want the following settings
Server behind NAT: off
PUBLIC IP: enter the public ip
Intranet Subnet: what you have is fine (assuming you dont have any
natted remote workers on that subnet)
NAT TRAVERSAL: on
Use external SBC for Internet Calling: not checked
For
If the phones are not in the same sub net and they have to pass through Nat
in order to get to the server only the sipx server IP (/32) should be added.
On Feb 20, 2012 3:42 PM, glomos-info i...@glomos.com wrote:
Hi Matt,
** **
The NIC in the Sipx box has a true public IP address. The
