Avaya 1230 Administration page 106

Configure the DHCP Server
Deskphones. An IP Deskphone-aware DHCP server can automatically configure IP Deskphones by
sending all information that the IP Deskphone requires.
The IP Deskphone and the DHCP server communicate using a unique class identifier. After the IP
Deskphone first sends the DHCP DISCOVER, it includes the Nortel-SIP-Phone-A ASCII string
within the Vendor Class Identifier (Option 60). The DHCP server recognizes this special Vendor
Class Identifier (Option 60) and sends back OFFER, which also includes the same Vendor Class
Identifier. This makes it possible to notify the IP Deskphone with SIP Software that the server is IP
Deskphone-aware, and that it is safe to accept the offer from the server.
Every IP Deskphone with SIP Software fills in the Vendor Class ID option of the DHCPDISCOVER
and DHCPREQUEST messages with the null-terminated, ASCII-encoded string Nortel-SIP-Phone-
A, where A identifies the version number of the information format of the IP Deskphone.
The Class Identifier Nortel-SIP-Phone-A must be unique in the DHCP server domain.
The unique DHCP configuration is required to allow the DHCP server to respond with a unique
Option 66 parameter to the IP Deskphone with SIP Software.
Note:
The DHCP standard defines Option 66 as the bootp server address in a string. The meaning of
the bootp server address is extended in Avaya IP Deskphone with SIP Software to include the
provisioning server address. The string in the DHCP offer for Option 66 can be the numeric IP
address or name of the Provisioning server or the URI (if FTP, HTTP, or HTTPS protocol is
used) of the provisioning server in the form of
<protocol>://<provisioning server URL>.
For example:
http://mydomain.com/SIP_phone.
If provisioning server authentication is required, the user credential must be embedded in the
URI in the form of
<protocol>://<userid>;<password>@<provisioning server URL>[:port][/
path].
For example:
ftp://www.mydomain.com/ABC
or
ftp://myuserid:mypass@ftp.mydomain.com:21/ABC
Configuring the DHCP server to support the vendor class identifier is not mandatory but is one way
to segregate network configuration data for the SIP phones from that for other devices. Below is an
example of the Linux dhcpd DHCPv4 server configuration file modifications for the phone's vendor
class id when you want to have specific handling for different phone types.
dhcpd.conf
...
# Custom options for Avaya 1100 and 1200 phones
class "11xx12xxUNIStim" {
match if substring(option vendor-class-identifier, 0, 14) = "Nortel-i2004-A";
option tftp-server-name "http://< IP address>/";
}
SIP Software for Avaya 1200 Series IP Deskphones-Administration
106
Comments? infodev@avaya.com
March 2015