4600 Series IP Telephone LAN Administrator’s Guide
4600 Series IP Telephones
2-8
Registration and Authentication 2
The Avaya media server switch supports registering and authenticating 4600 S eries IP
Telephones using the extension and password. For further information, see Related Documents,
on page 1-5.
Software 2
As shipped from the factory, the 4600 Series IP Telephones may not contain sufficient software for
registration and operation. When the phone is first plugged in, a software download from a TFTP
server is initiated. This gives the phone its proper functionality.
For downloads of software upgrades, the PBX provides the capability for a remote res tart of the
4600 Series IP Telephone. As a consequence of restarting, the phone automatically restarts
reboot procedures. If new software is available, a download will result.
WAN Considerations 2
QoS is harder on a WAN than a LAN. A LAN assumes no bandwidth concerns. A WAN assumes a
finite amount of bandwidth. Therefore, QoS considerations are more significant w hen the IP
telephony environment includes a WAN. In addition, there are administrative and hardware
compatibility issues unique to WANs. WAN administration is beyond the scope of this document.
DHCP and TFTP Servers 2
The DHCP server provides the following information to the 4600 Series IP Telephone:
IP Address of the 4600 Series IP Telephone
IP Address of the TN799 board on the Avaya Call Server.
IP Address of the TFTP server
The subnet mask
IP Address of the router
DNS Server IP Address
You should administer the LAN so that every IP Telephone can access a DHCP server with the
above information.
The IP Telephone will not function without an IP address. The failure of a DHCP server at boot
time will leave all the affected voice terminals unusable. It is possible for the user to manually
assign an IP address to an IP Telephone, but when the DHCP server finally returns, the telephone
will never look for a DHCP server unless the static IP data is unassigned manually. In addition,
manual entry of IP data is an error-prone process. It is therefore strongly recommended that a
DHCP server be available when the IP Telephone reboots.
A minimum of two DHCP servers are recommended for reliability.