Configuring Near-End Nat Traversal For Ip Endpoints - Inter-Tel AXXESS Manual

Hide thumbs Also See for AXXESS:

Table of Contents

Appendix F – Network Topology

10. CONFIGURING NEAR-END NAT TRAVERSAL FOR IP ENDPOINTS

10.1 The Axxess system supports traversing near-end NAT using statically assigned NAT

addresses. In this configuration, a single IPRC can support internal IP endpoints, IP network-

ing over the private network, and remote IP endpoints. An administrator configures the NAT

device to always (statically) associate a specific public address with the Axxess IPRC's native

10.2 The following diagram illustrates the static NAT assignment and the IP endpoint con-

10.3 System v9.1 or later software can be programmed so that each IP endpoint could use

either the Native address or the NAT address. In other words, the system can be programmed

with corresponding IP addresses for communicating with each IP endpoint, whether the end-

point was located inside or outside the NAT/firewall. This is done in the NAT Address Type

field in System\Devices and Feature Codes\Stations\Local\<station> when the <station> is an

IP device (MGCP/SIP gateway and endpoints included). You can choose one of the following

MANUAL VERSION 11.0 – May 2008

Native: Used when the endpoint is located inside the NAT (those that do not pass

through near-end NAT).

NAT: Used when the endpoint is located outside the NAT (those that do pass through

near-end NAT).

Auto: Allows the IP endpoints to be moved inside or outside the firewall (NAT) with-

out programming intervention. This is the default value. See

mation about Automatic NAT Detection.

The "Auto" option is not applicable to SIP trunks. You must select either

"Native" or "NAT" for SIP trunks.

Configuring Near-End NAT Traversal for IP Endpoints

for more infor-

Table of Contents