Dhcp Generic Setup - Avaya 4600 Series Administrator's Manual

DHCP Generic Setup

This document is limited to describing a generic administration that works with the 4600 Series
IP Telephones. Three DHCP software alternatives are common to Windows operating systems:
Windows NT
●
Windows 2003
●
Windows 2000
●
Any other DHCP application might work. It is the responsibility of the customer to install and
configure the DHCP server correctly.
DHCP server setup involves:
1. Installing the DHCP server software according to vendor instructions.
2. Configuring the DHCP server with:
IP Addresses available for the 4600 Series IP Telephones.
●
The following DHCP options:
●
- Option 1 - Subnet mask.
As described in
- Option 3 - Gateway (router) IP Address(es).
As described in
contain up to 255 total ASCII characters. You must separate IP Addresses with
commas with no intervening spaces.
- Option 6 - DNS server(s) address list.
If using more than one address, the total list can contain up to 127 total ASCII
characters. You must separate IP Addresses with commas with no intervening spaces.
At least one address in Option 6 must be a valid, non zero, dotted decimal address.
Otherwise, DNS will fail.
- Option 15 - DNS Domain Name.
This string contains the domain name to be used when DNS names in system
parameters are resolved into IP Addresses. This domain name is appended to the
DNS name before the 4600 IP Telephone attempts to resolve the DNS address.
Option 15 is necessary if you want to use a DNS name for the TFTP server.
Otherwise, you can specify a DOMAIN as part of customizing TFTP as indicated in
DNS Addressing
- Option 51 - DHCP lease time.
Optional. Avaya recommends a lease time of six weeks or greater. Expired leases
cause Avaya IP Telephones to reboot.Avaya recommends providing enough leases so
an IP Address for an IP telephone does not change if it is briefly taken offline.
®
4.0 DHCP Server
®
DHCP Server
®
DHCP Server
Table 3, item 3.
Table 3, item 1. If using more than one address, the total list can
on page 107.
Issue 5 November 2006
DHCP
59