Table of Contents
Advertisement
Avaya 1692 IP Conference Phone
by the phone. The phone will copy files from and write files to the file server directory.
If network access configuration prevents copying or writing files there may be issues
including an inability of the 1692 to complete the boot process and register
successfully.
3.
DHCP (with a file server): When a DHCP server is used to obtain the phone's
configuration settings, a DHCP server must be correctly provisioned to recognize and
respond to the1692 phone. The instructions below explain which settings are
required.
Static configuration with no file server
When a 1692 is configured without a file server or DHCP server, settings specific to the facility
must reside in the phone. Required local values include device IP address, subnet mask, and
router. These are manually entered through its configuration menu as described below. In this
type of configuration, the phone uses default settings for anything not statically configured and
does not check for software updates or take settings from any other location than its own static
settings and cache. If the phone has previously registered successfully the cache may contain
settings from the previous registration.
This configuration will not accept software upgrades. In order to perform a software upgrade, a
file server must be designated and configured. It may be decommissioned after the upgrade is
complete. Thereafter, the static settings in the phone and in the cache contain the information the
phone needs to continue to operate without a file server.
With no file server, the 1692 phone cannot upgrade or downgrade software versions.
Static configuration with file server
If using a file server and not a DHCP server, the phone must be manually configured with network
settings. Starting with R1.1, the default file server type is HTTP. If a different file server type is
used, it must be specified in the manual configuration sequence as described below.
A configured file server is required in order to load code; deliver device-specific configurations
and remote management; syslogs for troubleshooting; and logging device boot activity via file
server logs.
As part of its usual initialization process, the phone seamlessly checks the file server and
proceeds to install code, if the version on the file server is different than the code currently loaded
on the phone.
NOTE: Prior to R1.1, the default file server type is FTP.
DHCP server requirements
When using DHCP, the phone will automatically receive all of its settings from the DHCP server.
See below for the required DHCP parameters. If the IP address of the 1692 conference phone is
not set, the DHCP configuration parameters will be used. If the IP address of the 1692 is set, then
the static options will be used and not DHCP.
Please refer to Appendix A of this document for detailed 1692 DHCP Scope information.
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 1692 Series IP
Telephones and the following DHCP options:
The DHCP options that are requested by the 1692 are listed below.
Issue 1, September 2010
Installation, Configuration and Software Upgrade Guide
12
Advertisement
Table of Contents
