Using a cell, mobile, or GSM phone, or a two-way radio in close
proximity to an Avaya IP telephone might cause interference.
Documentation disclaimer
“Documentation” means information published in varying mediums
which may include product information, operating instructions and
performance specifications that are generally made available to users
of products. Documentation does not include marketing materials.
Avaya shall not be responsible for any modifications, additions, or
deletions to the original published version of Documentation unless
such modifications, additions, or deletions were performed by or on
the express behalf of Avaya. End User agrees to indemnify and hold
harmless Avaya, Avaya's agents, servants and employees against all
claims, lawsuits, demands and judgments arising out of, or in
connection with, subsequent modifications, additions or deletions to
this documentation, to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked
websites referenced within this site or Documentation provided by
Avaya. Avaya is not responsible for the accuracy of any information,
statement or content provided on these sites and does not
necessarily endorse the products, services, or information described
or offered within them. Avaya does not guarantee that these links will
work all the time and has no control over the availability of the linked
pages.
Warranty
Avaya provides a limited warranty on Avaya hardware and software.
Refer to your sales agreement to establish the terms of the limited
warranty. In addition, Avaya’s standard warranty language, as well as
information regarding support for this product while under warranty is
available to Avaya customers and other parties through the Avaya
Support website:
https://support.avaya.com/helpcenter/
getGenericDetails?detailId=C20091120112456651010 under the link
“Warranty & Product Lifecycle” or such successor site as designated
by Avaya. Please note that if You acquired the product(s) from an
authorized Avaya Channel Partner outside of the United States and
Canada, the warranty is provided to You by said Avaya Channel
Partner and not by Avaya.
“Hosted Service” means an Avaya hosted service subscription that
You acquire from either Avaya or an authorized Avaya Channel
Partner (as applicable) and which is described further in Hosted SAS
or other service description documentation regarding the applicable
hosted service. If You purchase a Hosted Service subscription, the
foregoing limited warranty may not apply but You may be entitled to
support services in connection with the Hosted Service as described
further in your service description documents for the applicable
Hosted Service. Contact Avaya or Avaya Channel Partner (as
applicable) for more information.
Hosted Service
THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA
HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA
WEBSITE,
HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER
THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH
SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF
YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
SERVICE.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,
UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya
Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY
AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED
FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.
UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA
AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
AND ANYONE ELSE USING OR SELLING THE SOFTWARE
WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
YOU ARE INSTALLING, DOWNLOADING OR USING THE
SOFTWARE (HEREINAFTER REFERRED TO
INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
THESE TERMS AND CONDITIONS AND CREATE A BINDING
CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).
Avaya grants You a license within the scope of the license types
described below, with the exception of Heritage Nortel Software, for
which the scope of the license is detailed below. Where the order
documentation does not expressly identify a license type, the
applicable license will be a Designated System License as set forth
below in the Designated System(s) License (DS) section as
applicable. The applicable number of licenses and units of capacity
for which the license is granted will be one (1), unless a different
number of licenses or units of capacity is specified in the
documentation or other materials available to You. “Software” means
computer programs in object code, provided by Avaya or an Avaya
Channel Partner, whether as stand-alone products, pre-installed on
hardware products, and any upgrades, updates, patches, bug fixes,
or modified versions thereto. “Designated Processor” means a single
stand-alone computing device. “Server” means a set of Designated
Processors that hosts (physically or virtually) a software application
to be accessed by multiple users. “Instance” means a single copy of
the Software executing at a particular time: (i) on one physical
machine; or (ii) on one deployed software virtual machine (“VM”) or
similar deployment.
License types
Designated System(s) License (DS). End User may install and use
each copy or an Instance of the Software only: 1) on a number of
Designated Processors up to the number indicated in the order; or 2)
up to the number of Instances of the Software as indicated in the
order, Documentation, or as authorized by Avaya in writing. Avaya
may require the Designated Processor(s) to be identified in the order
by type, serial number, feature key, Instance, location or other
specific designation, or to be provided by End User to Avaya through
electronic means established by Avaya specifically for this purpose.
Shrinkwrap License (SR). End User may install and use the Software
in accordance with the terms and conditions of the applicable license
agreements, such as “shrinkwrap” or “clickthrough” license
accompanying or applicable to the Software (“Shrinkwrap License”)
as indicated in the order, Documentation, or as authorized by Avaya
in writing.
Heritage Nortel Software
“Heritage Nortel Software” means the software that was acquired by
Avaya as part of its purchase of the Nortel Enterprise Solutions
Business in December 2009. The Heritage Nortel Software is the
software contained within the list of Heritage Nortel Products located
https://support.avaya.com/LicenseInfo under the link “Heritage
at
Nortel Products” or such successor site as designated by Avaya. For
Heritage Nortel Software, Avaya grants Customer a license to use
Heritage Nortel Software provided hereunder solely to the extent of
the authorized activation or authorized usage level, solely for the
purpose specified in the Documentation, and solely as embedded in,
for execution on, or for communication with Avaya equipment.
Charges for Heritage Nortel Software may be based on extent of
activation or use authorized as specified in an order or invoice.
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, Hosted Service,
or hardware provided by Avaya. All content on this site, the
documentation, Hosted Service, and the product provided by Avaya
including the selection, arrangement and design of the content is
owned either by Avaya or its licensors and is protected by copyright
and other intellectual property laws including the sui generis rights
relating to the protection of databases. You may not modify, copy,
reproduce, republish, upload, post, transmit or distribute in any way
any content, in whole or in part, including any code and software
unless expressly authorized by Avaya. Unauthorized reproduction,
transmission, dissemination, storage, and or use without the express
written consent of Avaya can be a criminal, as well as a civil offense
under the applicable law.
Virtualization
The following applies if the product is deployed on a virtual machine.
Each product has its own ordering code and license types. Unless
otherwise stated, each Instance of a product must be separately
licensed and ordered. For example, if the end user customer or
Avaya Channel Partner would like to install two Instances of the
same type of products, then two products of that type must be
ordered.
Third Party Components
“Third Party Components” mean certain software programs or
portions thereof included in the Software or Hosted Service may
contain software (including open source software) distributed under
third party agreements (“Third Party Components”), which contain
terms regarding the rights to use certain portions of the Software
(“Third Party Terms”). As required, information regarding distributed
Linux OS source code (for those products that have distributed Linux
OS source code) and identifying the copyright holders of the Third
Party Components and the Third Party Terms that apply is available
in the products, Documentation or on Avaya’s website at:
support.avaya.com/Copyright or such successor site as designated
by Avaya. The open source software license terms provided as Third
Party Terms are consistent with the license rights granted in these
Software License Terms, and may contain additional rights benefiting
You, such as modification and distribution of the open source
software. The Third Party Terms shall take precedence over these
Software License Terms, solely with respect to the applicable Third
Party Components to the extent that these Software License Terms
impose greater restrictions on You than the applicable Third Party
Terms.
T9 Text Input and other products are covered by one or more of the
following patents: U.S. Pat. Nos. 5,187,480,5,818,437, 5,945,928,
5,953,541, 6,011,554, 6,286,064, 6,307,548, 6,307,549, and
6,636,162,6,646,573, 6,970,599; Australia Pat. Nos. 727539,
746674, 747901; Austria Pat. Nos. AT225534, AT221222; Brazil P.I.
No. 9609807-4; Canada Pat. Nos. 1,331,057, 2,227,904,2,278,549,
2,302,595; Japan Pat. Nos. 3532780, 3492981; United Kingdom Pat.
No. 2238414B; Hong Kong Standard Pat. No. HK1010924; Republic
of Singapore Pat. Nos. 51383, 66959, 71979; European Pat. Nos. 1
010 057 (98903671.0), 1 018 069 (98950708.2); Republic of Korea
Pat. Nos. KR201211B1, KR226206B1, 402252; People's Republic of
China Pat. No. ZL96196739.0; Mexico Pat. Nos. 208141, 216023,
218409; Russian Federation Pat. Nos. 2206118, 2214620, 2221268;
additional patent applications are pending
The following applies only if the H.264 (AVC) codec is distributed with
the product. THIS PRODUCT IS LICENSED UNDER THE AVC
PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE
REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH
THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC
VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA,
L.L.C. SEE
Service Provider
THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S
HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS
HTTP://WWW.MPEGLA.COM.
https://
SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE
PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM
THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER’S
HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN
WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE
OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING
BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS,
THE AVAYA CHANNEL PARTNER IS REQUIRED TO
INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE
AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE,
DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER.
WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED
THE H.264 CODEC OR H.265 CODEC, THE AVAYA CHANNEL
PARTNER ACKNOWLEDGES AND AGREES THE AVAYA
CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL
RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC) CODEC
IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE
FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES
IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I)
ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD
(“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS
ENCODED BY A CONSUMER ENGAGED IN A PERSONAL
ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER
LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED
OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL
INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS
MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE
WWW.MPEGLA.COM.
Compliance with Laws
You acknowledge and agree that it is Your responsibility for
complying with any applicable laws and regulations, including, but not
limited to laws and regulations related to call recording, data privacy,
intellectual property, trade secret, fraud, and music performance
rights, in the country or territory where the Avaya product is used.
Preventing Toll Fraud
“Toll Fraud” is the unauthorized use of your telecommunications
system by an unauthorized party (for example, a person who is not a
corporate employee, agent, subcontractor, or is not working on your
company's behalf). Be aware that there can be a risk of Toll Fraud
associated with your system and that, if Toll Fraud occurs, it can
result in substantial additional charges for your telecommunications
services.
Avaya Toll Fraud intervention
If You suspect that You are being victimized by Toll Fraud and You
need technical assistance or support, call Technical Service Center
Toll Fraud Intervention Hotline at +1-800-643-2353 for the United
States and Canada. For additional support telephone numbers, see
the Avaya Support website:
successor site as designated by Avaya.
Security Vulnerabilities
Information about Avaya’s security support policies can be found in
the Security Policies and Support section of
support.avaya.com/security.
Suspected Avaya product security vulnerabilities are handled per the
Avaya Product Security Support Flow (
support.avaya.com/css/P8/documents/100161515).
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support website:
as designated by Avaya.
Contact Avaya Support
See the Avaya Support website: https://support.avaya.com for
product or Hosted Service notices and articles, or to report a problem
with your Avaya product or Hosted Service. For a list of support
telephone numbers and contact addresses, go to the Avaya Support
website:
designated by Avaya), scroll to the bottom of the page, and select
Contact Avaya Support.
https://support.avaya.com (or such successor site as
https://support.avaya.com, or such successor site
https://support.avaya.com or such
https://
HTTP://
https://
Regulatory Statements
Australia Statements
Handset Magnets Statement:
Danger:
The handset receiver contains magnetic devices that can
attract small metallic objects. Care should be taken to avoid
personal injury.
Industry Canada (IC) Statements
This Class B digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe B est conformeà la norme
NMB-003 du Canada.
This product meets the applicable Innovation, Science and Economic
Development Canada technical specifications.
Japan Statements
Class B Statement
This is a Class B product based on the standard of the VCCI Council.
If this is used near a radio or television receiver in a domestic
environment, it may cause radio interference. Install and use the
equipment according to the instruction manual.
Denan Power Cord Statement
Danger:
Please be careful of the following while installing the
equipment:
• Please only use the connecting cables, power cord, and
AC adapters shipped with the equipment or specified by
Avaya to be used with the equipment. If you use any
other equipment, it may cause failures, malfunctioning,
or fire.
• Power cords shipped with this equipment must not be
used with any other equipment. In case the above
guidelines are not followed, it may lead to death or
severe injury.
The operation of this equipment is subject to the following two
conditions:
1. It is possible that this equipment or device may not cause
harmful interference, and
2. This equipment or device must accept any interference,
including interference that may cause undesired operation.
La operación de este equipo está sujeta a las siguientes dos
condiciones:
1. Es posible que este equipo o dispositivo no cause
interferencia perjudicial y
2. Este equipo o dispositivo debe aceptar cualquier
interferencia, incluyendo la que pueda causar su operación
no deseada.
Brazil Statement
Este equipamento não tem direito à proteção contra interferência
prejudicial e não pode causar interferência em sistemas devidamente
autorizados
Power over Ethernet (PoE) Statement
This equipment must be connected to PoE networks without routing
to the outside plant.
Taiwan Low Power Radio Waves Radiated Devices Statement
802.11b/802.11g/BT:
Article 12 — Without permission granted by the NCC, any company,
enterprise, or user is not allowed to change frequency, enhance
transmitting power or alter original characteristic as well as
performance to an approved low power radio-frequency devices.
Article 14 — The low power radio-frequency devices shall not
influence aircraft security and interfere legal communications; If
found, the user shall cease operating immediately until no
interference is achieved. The said legal communications means radio
communications is operated in compliance with the
Telecommunications Act. The low power radio-frequency devices
must be susceptible with the interference from legal communications
or ISM radio wave radiated devices.
U.S. Federal Communications Commission (FCC) Statements
Compliance Statement
The changes or modifications not expressly approved by the party
responsible for compliance could void the user’s authority to operate
the equipment.
To comply with the FCC RF exposure compliance requirements, this
device and its antenna must not be co-located or operating to
conjunction with any other antenna or transmitter.
This device complies with part 15 of the FCC Rules. Operation is
subject to the following two conditions:
1. This device may not cause harmful interference, and
2. This device must accept any interference received,
including interferences that may cause undesired
operation.
When using IEEE 802.11a wireless LAN, this product is restricted to
indoor use, due to its operation in the 5.15 to 5.25GHz frequency
range. The FCC requires this product to be used indoors for the
frequency range of 5.15 to 5.25GHz to reduce the potential for
harmful interference to co channel mobile satellite systems. Highpower radar is allocated as the primary user of the 5.25 to 5.35GHz
and 5.65 to 5.85GHz bands. These radar stations can cause
interference with and/or damage to this device.
Class B Part 15 Statement
For product available in the USA/Canada market, only channel 1~11
can be operated. Selection of other channels is not possible.
This equipment has been tested and found to comply with the limits
for a Class B digital device, pursuant to Part 15 of the FCC Rules.
These limits are designated to provide reasonable protection against
harmful interferences in a residential installation. This equipment
generates, uses and can radiate radio frequency energy and, if not
installed and used in accordance with the instructions, may cause
harmful interference to radio communications. However, there is no
guarantee that interference will not occur in a particular installation. If
this equipment does cause harmful interferences to radio or
television reception, which can be determined by turning the
equipment off and on, the user is encouraged to try to correct the
interference by one or more of the following measures:
• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from
that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for
help.
Radiation Exposure Statement
This equipment complies with FCC radiation exposure limits set forth
for an uncontrolled environment . This equipment should be installed
and operated with minimum distance of 8 in or 20 cm between the
radiator and your body. This transmitter must not be co-located or
operating in conjunction with any other antenna or transmitter.
EU Countries
This device when installed complies with the essential requirements
and other relevant provisions of the EMC Directive 2014/30/EU,
Safety LV Directive 2014/35/EU, and Radio Equipment Directive
2014/53/EU. A copy of the Declaration may be obtained from https://
support.avaya.com or Avaya Inc., 2605 Meridian Parkway Suite 200.
Durham, NC 27713 USA.
This device when installed complies with the essential requirements
and other relevant provisions of the EMC Directive 2014/30/EU,
Safety LV Directive 2014/35/EU, and Radio Equipment Directive
2014/53/EU. A copy of the Declaration may be obtained from https://
support.avaya.com or Avaya Inc., 2605 Meridian Parkway Suite 200.
Durham, NC 27713 USA.
General Safety Warning
• Use only the Avaya approved Limited Power Source power
supplies specified for this product.
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation, Hosted Service(s), and product(s) provided
by Avaya are the registered or unregistered Marks of Avaya, its
affiliates, its licensors, its suppliers, or other third parties. Users are
not permitted to use such Marks without prior written consent from
Avaya or such third party which may own the Mark. Nothing
contained in this site, the Documentation, Hosted Service(s) and
product(s) should be construed as granting, by implication, estoppel,
or otherwise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners.
Linux® is the registered trademark of Linus Torvalds in the U.S. and
other countries.
Appendix A: List of configuration parameters................................................................... 163
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP10
Comments on this document? infodev@avaya.com
Chapter 1:Introduction
Purpose
This document contains information about how to install and deploy 9600 Series IP Deskphones.
It provides administration information for only the following 9600 Series IP Deskphones models:
• 9601
• 9608
• 9608G
• 9611G
• 9621G
• 9641G
• 9641GS
This document is intended for people who install and maintain the 9600 Series IP Deskphones.
For example, administrators and service engineers.
Change history
DateSummary of changes
October 2020Updated Phone administration chapter
June 2020Added LDAP Directory topic
January 2020Updated the Data Privacy Controls Addendum chapter
October 2019Updated Phone administration chapter
Updated List of configuration parameters
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP11
Comments on this document? infodev@avaya.com
Chapter 2:9600 Series IP Deskphones
overview
9600 Series IP Deskphones overview
Avaya 9600 Series IP Deskphones is a set of desk handset devices that you can use for unified
communication. The series leverages the enterprise IP network and eliminates the need for a
separate voice network. It works with the Avaya Aura® environment to provide a flexible
architecture that works with your investments and accommodates growth as your business needs
change.
The deskphones offer high audio quality and low power requirements and the flexibility to
customize. With the high-performance models of this series that can operate in both the H.323
and the Session Initiated Protocol (SIP) environments, you can use the phones to:
• Make conference calls more efficient and enhance customer interactions.
• Gain access to information quickly through easy-to-read and high-resolution displays.
• Speed up completion of common telephony tasks by using prompts on touch screens.
• Improve productivity with context-sensitive graphical interfaces that enhance call control and
call management.
• Create a survivable, scalable infrastructure that delivers reliable performance and flexible
growth as business needs change.
• Increase performance by deploying Gigabit Ethernet within your infrastructure.
• Reduce energy costs by using efficient Power-over-Ethernet (POE), including the sleep
mode, that lowers energy consumption dramatically.
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP12
Comments on this document? infodev@avaya.com
9600 Series IP Deskphones models
9600 Series IP Deskphones models
Deskphone modelDescription
9601The 9601 deskphone is SIP-only phone that provides a four-row
monochrome display and two lines with dual red and green
LEDs. The phone has a built in 10/100 Ethernet switch with a
port for your personal computer or a laptop.
9608/9608GYou can use up to eight lines for the deskphone. The deskphone
supports a traditional user interface and a graphical
monochrome display. The 9608 has a built in 10/100 Ethernet
switch, and the 9608G has an integrated Gigabit.
9611GThe 9611G has a traditional user interface and a graphical color
display. You can use up to eight lines with the 9611G deskphone.
The 9611G deskphone has an integrated Gigabit and a USB
interface. The deskphone has a graphical color display with a
white backlight.
9621GThe 9621G IP deskphone provides gigabit capability and touch
screen functionality. Customers with a need for gigabit
connectivity to the desktop prefer the 9621G deskphone.
with a color touch screen, wideband speaker, USB interface,
Bluetooth® enabled headset support, and gigabit connectivity to
the desktop. Customers who require gigabit capability for the
desktop and the option to add more advanced capabilities prefer
the 9641G/9641GS deskphone.
New in this release
Security enhancements
• Supports OpenSSL FIPS 140-2 certified cryptographic algorithms.
• Supports IPv6.
• Supports OpenSSL FIPS 140-2 certified cryptographic algorithms
• Supports Department of Defense solution deployment with Joint Inter-operability Test
Command (JITC) compliance.
• Supports display of SSH fingerprint in the Administration menu.
• Displays version of OpenSSH and OpenSSL in the Administration menu.
• Supports SHA2 hash algorithm and strong encryption (256 bit symmetric and RSA 2048 and
4096 bit asymmetric keys) in TLS mode.
• Supports SRTP/SRTCP and TLS v1.2.
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP13
Comments on this document? infodev@avaya.com
9600 Series IP Deskphones overview
• Supports Enhanced Avaya Services Login (EASG) feature where an administrator can
escalate to root privileges using an authentication file.
IPv6 and related features
• Supports ICMPv6, PPMv6, and DHCPv6.
• SIP registration over IPv4 and IPv6.
• Supports call features and MDA devices with ANAT and non-ANAT phones.
• Supports early media, delayed media, and media reshuffling with ANAT.
AS-SIP features
• Supports Multiple Level Precedence and Preemption, DSCP, and Blind Transfer as part of
the AS-SIP feature.
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP14
Comments on this document? infodev@avaya.com
Chapter 3:Initial setup and connectivity
Hardware and software prerequisites
Check the prerequisites to ensure that you have the required software and hardware before you
install the 9600 Series IP Deskphones.
Hardware prerequisites
Ensure that the LAN:
• Uses Ethernet Cat. 5e or Cat. 6 cabling
• Has either of the following specifications:
- IEEE 802.3af PoE
- IEEE 802.3af PoE injector
Software prerequisites
Ensure that your network already has the following components installed and configured:
• Avaya Aura® Session Manager 6.3.8 or later
• Avaya Aura® Communication Manager 6.3.6 or later
• Avaya Aura® System Manager 6.3.8 or later
• If applicable, Avaya Aura® Presence Services 6.2.4 or later
• If applicable, Avaya Aura® Session Border Controller 7.0 or later
• If applicable, IP Office IPO 11.0.0 or later
• A DHCP server for providing dynamic IP addresses to the .
• A file server, an HTTP, HTTPS, or the Avaya Aura® Utility Services for downloading the
software distribution package and the settings file
IPv6 deployment requires Avaya Aura® Session Manager v7.1 or later, Avaya Aura
Communication Manager v7.1 or later, Avaya Aura® System Manager v7.1 or later, and Avaya
Aura® Session Border Controller v7.1 or later. For more information about installing and
configuring the components, see their respective documentation.
®
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP15
Comments on this document? infodev@avaya.com
Initial setup and connectivity
Installation checklist
Use the following checklist to see the tasks that you must perform to setup and connect the9600
Series IP Deskphones.
No.TaskReference
1.Check the prerequisites.See Prerequisites topic for more
information.
2.Collect the configuration data for the
Deskphone, File Server, Network Server/
Switch (LLDP), Avaya Aura® System
Manager, and DHCP Server.
3.Configure the File Server, DHCP, and
Network Server/Switch (LLDP).
4.Create user, session, and
communication profile on Avaya Aura
System Manager
5.Download and install Avaya Aura
System Manager certificates on the
phone.
6.Unpack and assemble the deskphone
components.
7.Connect the 9600 Series IP Deskphones
to the power source and network.
®
See Configuration through DHCP, File
Server configuration, and Configuration
through LLDP topics for more
information.
See Configuration through DHCP, File
Server configuration, and Configuration
through LLDP topics for more
information.
SeeAdministering Avaya Aura® System
®
Manager guide for more information.
SeeAdministering Avaya Aura® System
Manager guide for more information.
See Plugging in the deskphone for more
information.
Administration methods
You can use the following methods to administer the devices. The following table lists the
configuration parameters that you can administer through each of the corresponding methods.
Method
IP
address
es
DHCP—
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Tagging
and
VLAN
Comments on this document? infodev@avaya.com
Provisionin
g Server
Deskphones SIP16
Can administer
GroupNetwork
Time
Server
Quality
of
Service
Table continues…
Applicat
ionspecific
paramet
ers
Administration methods
MethodCan administer
LLDP————
Settings file———
Avaya Aura® System
Manager and IP Office
Administration menu on the
phone
Web UI
—————
—
Precedence of administration methods
Most of the parameters are configured through multiple methods. If you configure a parameter
through more than one method, the device applies the settings of the method that has a higher
precedence. The following list shows the precedence of the methods in the highest to lowest
order:
1. Administration menu on the phone. When the parameter USE_DHCP is set to 1, the phone
gets the DHCP values from the DHCP rather than Administration menu of the phone.
2. Avaya Aura® System Manager and IP Office.
3. 46xxsettings.txt file
4. DHCP.
5. LLDP. There is an exception of LLDP getting a higher precedence than the Settings file
and DHCP when the layer 2 parameters, such as L2QVLAN, L2Q, L2QAUD, L2QVID,
L2QSIG, DSCPAUD, DSCPSIG, and PHY2VLAN are set through LLDP.
Note:
When parameters of the 46xxsettings.txt file are removed, or are not used, they reset to
their default value.
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP17
Comments on this document? infodev@avaya.com
Collect configuration data for the following components
DHCP Server
DHCP
Deskphone
Network Server /
Switch (LLDP)
File Server
File Server
2
3
4
5
1
Configure the servers
NTP Server
NTP
NTP Server
NTP
Configure the following servers
DHCP Server
DHCP
Network Server /
Switch (LLDP)
File Server
File Server
User, Session &
Communication Profile
Connect IP Phone
to the network
User, Session &
Communication Profile
Unpack and assemble
Configure security
certificates
Initial setup and connectivity
Diagram: Phone deployment process
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Comments on this document? infodev@avaya.com
Deskphones SIP18
Diagram: IP phone setup
IP PHONE
IP PHONE
D H CP
Provides IP address
& sets configurable
parameters for
provisioning
46xxsettings.txt
Sets the system
parameters for
configuration
Configures user, communication,
and session profile
A provisioning server is an HTTP or an HTTPS server that the Avaya J100 Series IP Phones
connect to obtain J100 firmware files and configuration settings files.
When the Avaya J100 Series IP Phones boot up, or is performing a check for updates, the phone
checks for firmware updates and configuration files on the configured provisioning server.
The following methods are available to configure the Avaya J100 Series IP Phones provisioning
server address:
• DHCP
• LLDP
• Device Enrollment Services (DES)
• Administration menu on the phone
• Web interface of the phone
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP19
Comments on this document? infodev@avaya.com
Initial setup and connectivity
• Prompt on the phone for entering the provisioning details on the first time boot-up
The block diagram of the provisioning server configuration is as follows:
Configuration through LLDP
Link Layer Discovery Protocol (LLDP) is an open standards, layer 2 protocol that IP phones use to
advertise their identity and capabilities and to receive administration from Ethernet switches. LAN
equipment can use LLDP to manage power and administer VLANs, DSCP, and 802.1p priority
fields.
The transmission and reception of LLDP is specified in IEEE 802.1AB-2005. The 9600 Series IP
Deskphones Avaya J100 Series IP Phones use Type-Length-Value (TLV) elements specified in
IEEE 802.1AB-2005, TIA TR-41 Committee - Media Endpoint Discovery (LLDP-MED, ANSI/
TIA-1057), and Proprietary elements. LLDP Data Units (LLDPDUs) are sent to the LLDP Multicast
MAC address.
The 9600 Series IP Deskphones Avaya J100 Series IP Phones running SIP software support
IEEE 802.1AB if the value of the configuration parameter LLDP_ENABLED is “1” (On) or “2”
(Auto). If the value of LLDP_ENABLED is “0” (off), the transmission and reception of Link Layer
Discovery Protocol (LLDP) is not supported. When the value of LLDP_ENABLED is “2”, the
transmission of LLDP frames does not begin until an LLDP frame is received. The first LLDP
frame is transmitted within 2 seconds after the first LLDP frame is received. After transmission
begins, an LLDPDU is transmitted every 30 seconds. A delay of up to 30 seconds in phone
initialization might occur if the file server address is delivered by LLDP and not by DHCP.
These phones do not transmit 802.1AB multicast LLDP packets from an Ethernet line interface to
the secondary line interface and vice versa.
By using LLDP, you can configure the following:
• Call server IP address
• File server
• PHY2VLAN
• L2QVLAN and L2Q
• DSCP
• 802.1p priority
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP20
Comments on this document? infodev@avaya.com
Configuration through LLDP
LLDPDU transmitted by the phones
CategoryTLV Name (Type)TLV Info String (Value)
Basic MandatoryChassis IDIPADD of phone, IANA Address Family Numbers enumeration
value for IPv4, or subtype 5:Network address.
Basic MandatoryPort IDMAC address of the device.
Basic MandatoryTime-To-Live120 seconds.
Basic OptionalSystem NameThe Host Name sent to the DHCP server in DHCP option 12.
Basic OptionalSystem
Capabilities
Basic OptionalManagement
Address
IEEE 802.3
Organization
Specific
TIA LLDP MEDLLDP-MED
TIA LLDP MEDNetwork PolicyTagging Yes/No, VLAN ID for voice, L2 Priority, DSCP Value.
TIA LLDP MEDInventory –
TIA LLDP MEDInventory –
TIA LLDP MEDInventory –
TIA LLDP MEDInventory – Serial
TIA LLDP MEDInventory –
TIA LLDP MEDInventory – Model
Avaya ProprietaryCall Server IP
Avaya ProprietaryIP Phone
Avaya ProprietaryFile ServerFile Server IP Address. Subtype = 6.
MAC / PHY
Configuration /
Status
Capabilities
Hardware Revision
Firmware Revision
Software Revision
Number
Manufacturer
Name
Name
address
addresses
Bit 2 (Bridge) will be set in the System Capabilities if the phone
has an internal Ethernet switch. If Bit 2 is set in Enabled
Capabilities then the secondary port is enabled.
Mgmt IPv4 IP address of device.
Interface number subtype = 3 (system port). Interface number
= 1.
OID = SNMP MIB-II sysObjectID of the device.
Reports auto negotiation status and speed of the uplink port on
the device.
Media Endpoint Discovery capabilities = 00-33 (Inventory,
Power-via-MDI, Network Policy, MED Caps).
MODEL - Full Model Name.
Firmware version.
Software version or filename.
Device serial number.
Avaya.
MODEL with the final Dxxx characters removed.
Call Server IP Address. Subtype = 3.
Phone IP address, Phone Address Mask, Gateway IP
Address. Subtype = 4.
Table continues…
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP21
Comments on this document? infodev@avaya.com
Initial setup and connectivity
CategoryTLV Name (Type)TLV Info String (Value)
Avaya Proprietary802.1Q Framing802.1Q Framing = 1 if tagging or 2 if not.
Basic MandatoryEnd-of-LLDPDUNot applicable.
TLV impact on system parameter values
System parameter
name
PHY2VLANIEEE 802.1 Port
L2QVLAN and L2QIEEE 802.1 VLAN
L2Q, L2QVLAN,
L2QAUD,
DSCPAUD
TLV nameImpact
VLAN ID
Name
TIA LLDP MED
Network Policy
(Voice) TLV
The value of the PHY2VLAN parameter on the phone is
configured from the value of the Port VLAN identifier in the
TLV.
The value is changed to the TLV VLAN Identifier. L2Q is set to
1 (ON).
A check is made as to whether a reset is necessary to obtain a
new IP address due to a change in the values of the
parameters L2Q or L2QVLAN.
VLAN Name TLV is ignored if:
• The value of USE_DHCP is 0 and the value of IPADD is not
0.0.0.0.
• The current value of L2QVLAN was set by a TIA LLDP MED
Network Policy TLV.
• The VLAN name in the TLV does not contain the substring
“voice” in lower-case, upper-case or mixed-case ASCII
characters anywhere in the VLAN name.
L2Q - set to 2 (off) if T (the Tagged Flag) is set to 0 and to 1
(on) if T is set to 1.
L2QVLAN - Set to the VLAN ID in the TLV.
L2QAUD - Set to the Layer 2 Priority value in the TLV.
DSCPAUD - Set to the DSCP value in the TLV.
A check is made as to whether a reset is necessary to obtain a
new IP address due to a change in the values of the
parameters L2Q or L2QVLAN.
This TLV is ignored if:
• The value of USE_DHCP is 0 and the value of IPADD is not
0.0.0.0.
• The Application Type is not 1 (Voice) or 2 (Voice Signaling).
• The Unknown Policy Flag (U) is set to 1.
Table continues…
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP22
Comments on this document? infodev@avaya.com
Configuration through LLDP
System parameter
TLV nameImpact
name
L2Q, L2QVLANTIA LLDP MED
Network Policy
(Voice Signaling)
SIP_CONTROLL
ER_LIST
TLSSRVR and
HTTPSRVR
Proprietary Call
Server TLV
Proprietary File
Server TLV
L2QProprietary 802.1 Q
Framing
L2Q - set to 2 (off) if T (the Tagged Flag) is set to 0 and to 1
(on) if T is set to 1.
L2QVLAN - Set to the VLAN ID in the TLV.
L2QAUD - Set to the Layer 2 Priority value in the TLV.
DSCPAUD - Set to the DSCP value in the TLV.
A check is made as to whether a reset is necessary to obtain a
new IP address due to a change in the values of the
parameters L2Q or L2QVLAN.
This TLV is ignored if:
• The value of USE_DHCP is 0 and the value of IPADD is not
0.0.0.0.
• The Application Type is not 1 (Voice) or 2 (Voice Signaling).
• The Unknown Policy Flag (U) is set to 1.
SIP_CONTROLLER_LIST will be set to the IP addresses in
this TLV value.
Note:
This parameter cannot be used in an environment where
both SIP phones and H.323 phones exist.
TLSSRVR and HTTPSRVR will be set to the IP addresses in
this TLV value.
If the value of TLV = 1, L2Q is set to 1 (On).
If the value of TLV = 2, L2Q is set to 2 (Off).
If the value of TLV = 3, L2Q is set to 0 (Auto).
A check is made as to whether a reset is necessary to obtain a
new IP address due to a change in the values of the
parameters L2Q or L2QVLAN.
This TLV is ignored if:
• The value of USE_DHCP is 0 and the value of IPADD is not
0.0.0.0.
• The current L2QVLAN value was set by an IEEE 802.1
VLAN name.
• The current L2QVLAN value was set by a TIA LLDP MED
Network Policy (Voice) TLV.
POE_CONS_
SUPPORT
Proprietary - PoE
Conservation Level
If the value of POE_CONS_SUPPORT is 1,
POE_CONS_MODE is set to the level requested in the TLV.
Request TLV
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP23
Comments on this document? infodev@avaya.com
Initial setup and connectivity
Configuration through DHCP
The Avaya J100 Series IP Phones obtain network and configuration information using DHCP
protocol. You can configure the DHCP server to provide the following information to the device:
• Avaya Aura® Session Manager address.
• IP address
• Subnet mask
• IP address of the router
• IP address of the HTTP or HTTPS file server
• IP address of the SNTP server
• IP address of DNS
You can configure the DHCP server to:
• Dynamically assign IP addresses to the Avaya J100 Series IP Phones.
• Provision device and site-specific configuration parameters through various DHCP options.
DHCP Site Specific Option
The phones support DHCP configuration option called Site Specific Option(SSON). Using this
parameter, custom parameters can be configured on the phone through a DHCP server. In the
DHCP DISCOVER, the phone requests for the DHCP Site-specific option (SSON), typically
configured in DHCP Option 242. To configure and respond to this request, configure the DHCP
server with proper data supplied in the offer for the value of this option. An example of such
configuration is as follows:
Following parameters can be configured with this feature:
Parameter
ADMIN_PASS
WORD
Description
Specifies the security string used to access local procedures.
The default is 27238. This is meant to replace PROCPSWD as it provides a more
secure password syntax.
Table continues…
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP24
Comments on this document? infodev@avaya.com
Configuration through DHCP
ParameterDescription
HTTPDIRSpecifies the path to the configurations and data files in HTTP and HTTPS GET
operations during device bootup. This path is relative to the root of the HTTPS file
server, to the directory in which the device configuration and date files are stored. If
$MACADDR and/or $MODEL4 and/or $SERIALNO macro is present in the configured
path then such macro is replaced with its actual value.The path may contain no more
than 127 characters and may contain no spaces. HTTPDIR is the path for all HTTP
operations.
The command is HTTPDIR=<path>. In configurations where the upgrade and binary
files are in the default directory on the HTTP server, do not use the SETHTTPDIR=<path>.
HTTPPORTSets the TCP port used for HTTP file downloads from non-Avaya servers. The default is
80.
HTTPSRVRIP addresses or DNS names of HTTP file servers used for downloading settings,
language, and firmware files during startup.
The firmware files are digitally signed, so TLS is not required for security.
ICMPDUControls the extent to which ICMP Destination Unreachable messages are sent in
response to messages sent to closed ports so as not to reveal information to potential
hackers. The default is 1, that is sends Destination Unreachable messages for closed
ports used by traceroute.
ICMPREDControls whether ICMP Redirect messages are processed. The default is 0, that is,
redirect messages are not processed.
L2Q802.1Q tagging mode. The default is 0 for automatic.
L2QVLANVLAN ID of the voice VLAN. The default is 0.
PHY1STATSpecifies the speed and duplex settings for the Ethernet line interface. The default value
is 1 for auto-negotiate.
PHY2STATSpecifies the speed and duplex settings for the secondary (PC) Ethernet interface. The
default value is 1.
PROCPSWDSecurity string used to access local procedures.
The default is 27238. ADMIN_PASSWORD replaces this parameter if
ADMIN_PASSWORD is set in the 46xxsettings.txt file.
PROCSTATControls whether local (Admin menu) procedures can be used to configure the phone.
REUSETIMETime in seconds for IP address reuse timeout, in seconds. The default is 60 seconds.
SIGThe signaling protocol download flag that indicates the protocol applied as follows:
• 0 for Default
• 1 for H.323
• 2 for SIP
SIP_CONTROL
LER_LIST
SIP proxy or registrar server IP or DNS addresses that can be 0 to 255 characters, IP
address in the dotted decimal name format, separated by commas and without any
intervening spaces. The default is null, that is, no controllers.
Table continues…
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP25
Comments on this document? infodev@avaya.com
Initial setup and connectivity
ParameterDescription
TLSDIRSpecifies the path to the configurations and data files in HTTPS GET operations during
device bootup. This path is relative to the root of the HTTPS file server, to the directory
in which the device configuration and date files are stored. If $MACADDR and/or
$MODEL4 and/or $SERIALNO macro is present in the configured path then such macro
is replaced with its actual value. The string length can be from 0 to 127, without spaces.
TLSPORTDestination TCP port used for requests to https server in the range of 0 to 65535. The
default is 443, the standard HTTPS port.
TLSSRVRIP addresses or DNS names of Avaya file servers used to download configuration files.
Firmware files can also be downloaded using HTTPS.
Note:
Transport Layer Security is used to authenticate the server.
VLANTESTNumber of seconds to wait for a DHCPOFFER on a non-zero VLAN. The default is 60
seconds.
In an IP Office environment 46xxsettings.txt and 96x1Supgrade.txt files are
autogenerated. There is a provision where you can set up a different file server with your own
custom Settings file.
DHCP options
You can configure the following options in the DHCP server:
Option
Option 1Specifies the subnet mask of the network.
Option 3Specifies the gateway IP address list. The list can contain up to 127 total ASCII
Option 6Specifies the DNS server address list. The list can contain up to 127 total ASCII
Description
characters. Separate more than one IP address with commas with no intervening
spaces.
characters. Separate more than one IP address with commas with no intervening
spaces.
The phone supports DNS and the dotted decimal addresses. The phone attempts to
resolve a non-ASCII-encoded dotted decimal IP address by checking the contents of
DHCP Option 6. At least one address in Option 6 must be a valid, nonzero, dotted
decimal address, otherwise the DNS address fails.
Table continues…
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP26
Comments on this document? infodev@avaya.com
Configuration through DHCP
OptionDescription
Option 12Avaya J100 Series IP Phones identify themselves to the DHCP server by sending
the host name in Sub-Option 12 in DHCP DISCOVER and DHCP REQUEST options.
The host name has the following format:
AVohhhhhh, where:
• AV stands for Avaya.
• o is one of the following values based on Object Unique Identifier (OUI) derived
from the first three octets of the phone MAC address:
- A if OUI is 00-04-0D
- B if OUI is 00-1B-4F
- E if OUI is 00-09-6E
- L if OUI is 00-60-1D
- T if the OUI is 00-07-3B
- X if the OUI is anything else
• hhhhhh are the ASCII characters for the hexadecimal representation of the last
three octets of the phone MAC address.
Option 15Specifies the domain name. The domain name is required to resolve DNS names
into IP addresses.
Configure this option if you use a DNS name for the HTTP server. Otherwise, you
can specify a domain as part of customizing the HTTP server.
This domain name is appended to the DNS addresses specified in Option 6 before
the phone attempts to resolve the DNS address. The phone queries the DNS
address in the order they are specified in Option 6. If there is no response from an
address, the phone queries the next DNS address.
As an alternative to administering DNS by DHCP, you can specify the DNS server
and domain name in the HTTP script file. If you use the script file, you must
configure the DNSSRVR and DOMAIN parameters so that you can use the values of
these parameters in the script.
Administer Option 6 and Option 15 appropriately with DNS servers and domain
names respectively.
Option 42Specifies the SNTP IP address list. List servers in the order of preference. The
minimum length is 4 and the length must be a multiple of 4.
Option 43Specifies the encapsulated vendor-specific options that clients and servers use to
exchange the vendor-specific information. Option 43 is processed only if the first
code in the Option is 1 with a value of 6889. The value 6889 is an Avaya enterprise
number. All values are interpreted as strings of ASCII characters that are accepted
with or without a null termination character. Any invalid value is ignored and the
corresponding parameter value is not set. Cannot be used simultaneously with
DHCP SSON (Option 242).
Table continues…
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP27
Comments on this document? infodev@avaya.com
Initial setup and connectivity
OptionDescription
Option 51Specifies the DHCP lease time. If this option is not received, the DHCPOFFER is not
accepted. Assign a lease time of six weeks or greater. If this option has a value of
FFFFFFFF hex, the IP address lease is assumed to be infinite, so that the renewal
and rebinding procedures are not necessary even if Options 58 and 59 are received.
Expired leases causes the device to reboot.
Option 52Specifies the overload option. If this option is received in a message, the device
interprets the sname and file parameters.
Option 53Specifies the DHCP message type. The value can be one of the following:
• 1 for DHCPDISCOVER
• 3 for DHCPREQUEST
For DHCPREQUEST sent to renew the device IP address lease:
• If a DHCPACK is received in response, a log event record is generated with a Log
Category of DHCP.
• If a DHCPNAK is received in response, the device immediately ceases IP address
usage, generates a log event record, sets IPADD to 0.0.0.0, and enters the DHCP
INIT state.
Option 55Specifies the parameter request list. Acceptable values are:
• 1 for subnet mask
• 3 for router IP addresses
• 6 for domain name server IP addresses
• 7 for log server
• 15 for domain name
• 26 for interface MTU
• 42 for NTP servers
Option 57Specifies the maximum DHCP message size.
Set the value to 1500.
Set the value to 1000.
Option 58Specifies the DHCP lease renew time. If not received or if this value is greater than
that for Option 51, the default value of T1, renewal timer is used.
Option 59Specifies the DHCP lease rebind time. If not received or if this value is greater than
that for Option 51, the default value of T2, rebinding timer is used.
Option 242Specifies the site-specific option (SSON). It is optional but cannot be used
simultaneously with Option 43.
If you do not configure this option, ensure that one of the following parameters is
configured appropriately elsewhere:
• HTTPSRVR
• TLSSRVR
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP28
Comments on this document? infodev@avaya.com
Configuration through DHCP
DHCP vendor-specific option
You can set DHCP vendor-specific parameters by using DHCP option 43. The supported codes for
Option 43 and the corresponding parameters are as follows:
CodeParameter
1Does not set any parameter. The value must be 6889.
2HTTPSRVR
3HTTPDIR
4HTTPPORT
5TLSSRVR
6TLSDIR
7TLSPORT
8TLSSRVRID
9L2Q
10L2QVLAN
11PHY1STAT
12PHY2STAT
13PROCSTAT
14SIG
15SIP_CONTROLLER_LIST
Extending use of DHCP lease
9600 Series IP Deskphones support configuration of network parameters using DHCP as per RFC
2131. However, when a DHCP server becomes unreachable and the DHCP lease currently held
by the phone expires, the phone continues to use the same lease until the DHCP server becomes
reachable. This functionality is controlled by setting the following parameter:
Parameter nameDefault valueDescription
DHCPSTD0Specifies if the expired DHCP lease is used.
Value operation:
• 0: Continue use of the expired DHCP lease if
the lease could not be renewed.
• 1: Stop using the DHCP lease immediately
when it expires, as per the standard.
The parameter is configured through the
46xxsettings.txt file.
When this feature is enabled (DHCPSTD=1), the phone continues to use the lease data, including
IP address, router and other options if the lease could not be renewed. In this state, the phone will
attempt to reach a DHCP server every 60 seconds. When a DHCP server becomes available and
a lease is renewed or new lease obtained, the phone performs a duplicate address detection on
February 2021Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP29
Comments on this document? infodev@avaya.com
Initial setup and connectivity
the offered IP address. If no conflicts are detected, this IP address is assigned to the local network
interface for use.
Parameter configuration through DHCP
The phones support the DHCP configuration option called Site Specific Option (SSON). Using this
option, custom parameters can be configured on the phone through a DHCP server. In DHCP
DISCOVER, the phone requests for the SSON, typically configured in DHCP Option 242. To
respond to this request, configure the DHCP server with proper data supplied in the offer for this
option value. The following is an example of such configuration: