Phones; Configuration Guidelines For Nat - Altigen AltiWare OE/ACC Version 5.0A Administration Manual

Network Configuration Guidelines for the Alti-IP 600
Series of IP Phones
The following guidelines (specific to the Alti-IP 600 series of IP phones)
should be taken into consideration as a precursor to configuring your
network for use with NAT (see Network Configuration Guidelines below).
• DHCP is recommended to reduce the risks for duplicating IP
addresses. AltiServ provides seamless support for AltiGen IP Phones
using dynamic IP addresses. Select Dynamic IP address for IP
Extensions in AltiAdmin.
• A switch is recommended at the corporate network, rather than a hub,
for IP phone connection. This can reduce packet loss ratio.
• If there are not enough IP addresses in the corporate network, refer to
"Private and Public Network Configuration (AltiWare with Both
Private and Public IP Addresses)" on page 6-21. If DHCP is used in
this configuration, the administrator will need to perform the following
for the Alti-IP 600:
1. Configure the DHCP server to assign a private network IP address
for each phone based on the phone's MAC address (printed on the
label on the bottom of the IP Phone.
2. Private IP address needs to be added to AltiServ and TFTP server
as well.
3. Launch an AltiGatekeeper with private IP address and point to
AltiWare's private IP address.

Configuration Guidelines for NAT

Note: This section only applies to Alti-IP 600 phones or IP Talk
integrated with AltiView. For third party IP Phones, refer to
AltiGen's NAT Application Note.
The following section discusses the use of NAT (Network Address
Translation) with AltiWare's IP functionality. Configurations and
limitations for using NAT are addressed, and network diagrams explain the
topology of these configurations. The first 3 examples involve AltiWare
configurations for remote IP phones with a public IP address, with a private
AltiWare OE System Installation & Administration Manual
Board Configuration
6-11