Application Note

FS; Reviewed:
SPOC 09/07/2010
Solution & Interoperability Test Lab Application Notes
©2010 Avaya Inc. All Rights Reserved.
29 of 44
11xx12xx-SM
7. Configure Avaya 1100- and 1200-Series IP Deskphones
This section describes the basic configuration of the Avaya 1100- and 1200-Series IP
Deskphones. For additional details, see References [8, 9] available at http://www.avaya.com/.
Five models were tested: Avaya 1120E, 1140E, 1165E, 1220, and 1230. The configuration was
done using configuration files and the local telephone screen interface, as shown in these
Application Notes. The steps below show the configuration screens for the 1165E model.
Configuration files can be used for most options to support mass deployments.
The configuration steps are similar for all telephones, the main difference being the number of
accounts or line appearances that each telephone supports. Make sure the number of lines used
matches what is configured in Communication Manager.
7.1. Configure Initial Network Parameters
Network configuration of the telephone can be accomplished either manually at the telephone as
shown below, or via DHCP. Once this is accomplished, configuration files can be used to
configure the rest of the features. To manually configure the telephone, access the telephone
screen interface by selecting Prefs  Network, starting with the Prefs soft key at the bottom of
the screen. Enter the appropriate password to enter the network configuration submenus. Set
appropriate values for IP address, mask, default gateway, file server address, and file server
access type. In this case HTTP was selected as the configuration file server protocol. When the
telephone boots, it will request the file “ModelNumberSIP.cfg” from the root directory of the
HTTP server, an abbreviated copy of which is shown below. For example, for the 1165E, the
file name would be “1165eSIP.cfg”, and for the 1220 it would be “1220SIP.cfg.This file instructs
the telephone as to where to obtain its main configuration file (DEVICE_CONFIG), firmware (FW),
and local dial plan file (DIALING_PLAN), used to determine end of dialing when making calls.
Each section specifies the FILENAME to be accessed and the PROTOCOL to be used with the file
server. A value of “FORCED” as opposed to “AUTO” for the DOWNLOAD_MODE ensures explicit
control over when files will be downloaded, and was used in the sample configuration.
[DEVICE_CONFIG]
DOWNLOAD_MODE FORCED
VERSION 000100
PROTOCOL HTTP
FILENAME 1165DeviceConfig.dat
[FW]
DOWNLOAD_MODE FORCED
VERSION SIP1165e03.02.15.05
PROTOCOL HTTP
FILENAME SIP1165e03.02.15.05.bin
[DIALING_PLAN]
DOWNLOAD_MODE FORCED
VERSION 000020
PROTOCOL HTTP
FILENAME dialplan.txt