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). You 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”).
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.
Page 3
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.
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
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
HTTP://WWW.MPEGLA.COM.
https://
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 (https://
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:
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.
Regulatory Statements
Australia Statements
Handset Magnets Statement:
Industry Canada (IC) Statements
RSS Standards Statement
https://support.avaya.com (or such successor site as
Danger:
The handset receiver contains magnetic devices that can
attract small metallic objects. Care should be taken to avoid
personal injury.
https://support.avaya.com, or such successor site
https://support.avaya.com or such
https://support.avaya.com for
HTTP://
https://
Page 4
This device complies with Industry Canada licence-exempt RSS
standard(s). Operation is subject to the following two conditions:
1. This device may not cause interference, and
2. This device must accept any interference, including
interference that may cause undesired operation of the
device.
Le présent appareil est conforme aux CNR d'Industrie Canada
applicables aux appareils radio exempts de licence. L'exploitation est
autorisée aux deux conditions suivantes:
1. L'appareil ne doit pas produire de brouillage, et
2. L'utilisateur de l'appareil doit accepter tout brouillage
radioélectrique subi, même si le brouillage est susceptible
d'en compromettre le fonctionnement.
Radio Transmitter Statement
Under Industry Canada regulations, this radio transmitter may only
operate using an antenna of a type and maximum (or lesser) gain
approved for the transmitter by Industry Canada. To reduce potential
radio interference to other users, the antenna type and its gain
should be so chosen that the equivalent isotropically radiated power
(EIRP) is not more than that necessary for successful
communication.
Conformément à la réglementation d'Industrie Canada, le présent
émetteur radio peut fonctionner avec une antenne d'un type et d'un
gain maximal (ou inférieur) approuvé pour l'émetteur par Industrie
Canada. Dans le but de réduire les risques de brouillage
radioélectrique à l'intention des autres utilisateurs, il faut choisir le
type d'antenne et son gain de sorte que la puissance isotrope
rayonnée équivalente ne dépasse pas l'intensité nécessaire à
l'établissement d'une communication satisfaisante.
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.
Radiation Exposure Statement
This equipment complies with FCC & IC RSS102 radiation exposure
limits set forth for an uncontrolled environment. This equipment
should be installed and operated with minimum distance 20cm
between the radiator & your body. This transmitter must not be colocated or operating in conjunction with any other antenna or
transmitter.
Cet équipement est conforme aux limites d'exposition aux
rayonnements ISEDétablies pour un environnement non contrôlé.
Cet équipement doit être installé et utilisé avec un minimum de 20
cm de distance entre la source de rayonnement et votre corps.
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.
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.
Power over Ethernet (PoE) Statement
This equipment must be connected to PoE networks without routing
to the outside plant.
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.
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.
Page 5
• 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.
ENERGY STAR® compliance statement
As an ENERGY STAR partner, Avaya Inc. has determined that this
product meets the ENERGY STAR guidelines for energy efficiency.
Information on the ENERGY STAR program can be found at
www.energystar.gov. ENERGY STAR and the ENERGY STAR mark
are registered trademarks owned by the U.S. Environmental
Protection Agency.
EU Countries
This device when installed complies with the essential requirements
and other relevant provisions of EMC Directive 2014/30/EU and LVD
Directive 2014/35/EU. A copy of the Declaration may be obtained
http://support.avaya.com or Avaya Inc., 4655 Great America
from
Parkway, Santa Clara, CA 95054–1233 USA.
WiFi transmitter
• Frequencies for 2412-2472 MHz, transmit power: 17.8 dBm
• Frequencies for 5180-5240 MHz, transmit power: 19.14 dBm
General Safety Warning
• Use only the Avaya approved Limited Power Source power
supplies specified for this product.
• Ensure that you:
- Do not operate the device near water.
- Do not use the device during a lightning storm.
- Do not report a gas leak while in the vicinity of the leak.
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.
Device Usage Consent
By using the Avaya device you agree that Avaya, from time to
time,may collect network and device data from your device and may
use suchdata in order to validate your eligibility to use the device.
Avaya J100 Series IP Phones provide a range of applications and features for unified
communications. The phones leverage the enterprise IP network and eliminate the need of a
separate voice network. The phones offer superior audio quality with the amplified handsets and
customization with low power requirements in a Session Initiation Protocol (SIP) environment.
Avaya J100 Series IP Phones work with Avaya Aura®, IP Office, and third-party call control
environments to provide a flexible architecture where you can:
• Make conference calls more efficiently and enhance customer interactions with high-quality
audio.
• Gain access to information quickly through easy-to-read and high-resolution displays.
• 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 sleep mode,
which lowers energy consumption significantly.
• Enhance audio quality by using amplified handset mode.
J100 Series IP Phone models
Phone model
J129 IP PhoneA SIP-based phone with a monochrome display that supports
J139 IP PhoneA SIP-based phone with a color display that supports four call
J169 IP PhoneA SIP-based phone with a grayscale display that supports eight
Description
single line call appearance.
appearances with two lines of call display.
call appearances with four lines of call display.
The phone can also support up to three button modules each
supporting 24 application lines.
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones12
The power requirements of the phone vary depending on the connected peripherals. The following
table provides the correlation between the connected peripherals and power requirements.
Phone modelPoE Class
J129• IEEE 802.3af PoE Class 1 without any peripheral.
• IEEE 802.3af PoE Class 2 with a Wi-Fi module.
J139• IEEE 802.3af PoE, Class 1 device.
J169• IEEE 802.3af PoE Class1 without button module.
• IEEE 802.3af PoE Class 2 for up to two button
modules.
• 5V DC adapter for three button modules.
J179• IEEE 802.3af PoE Class1 without Wi-Fi module or
button module.
• IEEE 802.3af PoE Class 2 for up to two button
modules.
• 5V DC adapter for three button modules.
Note:
Use 5V DC adapter if you simultaneously
connect a Wi-Fi module along with one or
more button modules.
Supported codecs
Avaya J100 Series IP Phones supports the following codecs and call control protocol:
Codecs
Call control
protocol
Codecs• G.711a
J129J139J169J179
SIPSIPSIPSIP
• G.711µ
• G.729
• G.711a
• G.711µ
• G.729
• G.711a
• G.711µ
• G.729
• G.711a
• G.711µ
• G.729
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones15
When using Avaya J100 Series IP Phones, always adhere to the following safety precautions to
reduce the risk of fire, electric shock, and injury to persons.
• Read and understand all instructions.
• Follow all warnings and instructions marked on the phone.
• Do not immerse Avaya J100 Series IP Phones in water and do not use the phone when you
are wet. If you accidentally drop the phone into water, do not retrieve it until you have first
unplugged the line cord from the modular wall jack. Then call service personnel to ask about
a replacement. Never spill liquid of any kind on the phone. If liquid is spilled, however, refer
servicing to proper service personnel.
• Do not use Avaya J100 Series IP Phones during electrical storms in your immediate area to
prevent the risk of electric shock from lightning. Keep urgent calls brief. In spite of protective
measures to limit electrical surges, absolute protection from lightning is impossible.
• Report suspected natural gas leak immediately, but use a telephone away from the area in
question. The phone’s electrical contacts could generate a tiny spark, which could ignite
heavy concentrations of gas.
• Never push objects of any kind into Avaya J100 Series IP Phones through housing slots. The
objects may touch hazardous voltage points or short out parts resulting in electric shock.
Button modules overview
On Avaya J100 Series IP Phones, the number of call appearances and feature / application
buttons can be extended with the JBM24 Button Module (JBM24) and the Avaya J100 Expansion
Module (JEM24).
Note:
The button modules are supported only by Avaya J169/J179 IP Phones.
JBM24 Button Module provides 24 additional lines for incoming calls, outgoing calls, autodialing,
and calling features. The Avaya J100 Expansion Module provides 72 additional lines.
You can connect up to three button modules to Avaya J100 Series IP Phones. Each button
module can be placed in both stand and wall mount positions together with the phone.
December 2018Installing and Administering Avaya J100 Series IP Phones16
Hot plugging is not supported in Avaya J100 Expansion Module. Connect all the expansion
modules to the phone before connecting the phone to a power source.
The following table shows the number of button modules attached to the phone and the
corresponding number of lines available on JBM24 Button Module / Avaya J100 Expansion
Module:
Button modulesCall lines / Features /
Applications
124 / 72 (24 on each page)No / Yes
224No
324No
Switching between pages
Note:
If an Avaya J100 Expansion Module is attached to the Avaya J169 IP Phone, the display
screen changes to gray scale.
Avaya J100 Expansion Module upgrade
You can upgrade the Avaya J100 Expansion Module firmware to a new version using Avaya J100
Series IP Phones software distribution package. For more information about downloading and
extracting a software distribution package, see
page 101.
During the boot-up, the phone will download the new firmware for the Avaya J100 Expansion
Module. The Updating software notification will be displayed.
After the phone downloads the expansion module firmware, the upgrade process will continue in
the background. The Upgrading status is displayed in Main Menu > Administration > View >
Button modules.
Downloading and saving the software on
The upgrade procedure for an Avaya J100 Expansion Module takes up to 4 hours for each
attached module. During this time, the expansion module is operable, you can make and receive
calls with it and have access to other functionality.
When the upgrade is complete, the Avaya J100 Expansion Module displays the following
notification: “This device will be out of service for 3 minutes to apply theupdate”. Press the corresponding line button for Apply now or Apply tonight option to select
the suitable upgrade time.
Note:
When the Upgrade notification is displayed, the expansion module screen saver is disabled
and the backlight is not turned off.
December 2018Installing and Administering Avaya J100 Series IP Phones17
Use this task to upgrade Avaya J100 Expansion Module firmware to a new version.
Before you begin
Download Avaya J100 Series IP Phones software distribution package from the https://
support.avaya.com/ website. See Downloading and saving the software on page 101 for more
details.
Procedure
1. Extract the zipped file with the expansion module firmware and save it at an appropriate
location on the file server.
2. Set the expansion module firmware file name in J100Supgrade.txt.
3. Reboot the phone. The expansion module will reboot automatically.
Debugging the expansion module
Avaya J100 Expansion Module log files contain all messages that are sent to and received from
the phone. You can view the log files to monitor the user’s actions on the expansion module like
configuring labelled keys, making and receiving calls, enabling and disabling features, etc.
Note:
The maximum size of Avaya J100 Expansion Module log file is 5 Mb. When this size is
exceeded, a bak prefix is added to its file name, for example, BMLog_bak.txt. The
initial .txt file is cleared and writing starts from the beginning.
The log files can be generated using bm_cli debug tool which can be accessed through the phone
command line.
Note:
An SSH connection must be established via an SSH client to access the phone command
line. For more details, contact Avaya support at https://support.avaya.com/.
Important:
To generate log files, set log categories and levels, connect Avaya J100 Expansion Module to
the phone. If the expansion module is not connected, you will get the following error message:
“Phone doesn't have JEM24 with specified id”.
The following table shows the list of commands available through the bm_cli debug tool:
Command
help
Description
To print bm_cli help.
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones18
Add /bm to the file path as set in the example
to ensure no empty files are created.
list_files
To view the list of log files of the selected expansion
module in the specified directory, for example:
list_files 1 “/AvayaDir/var/log”
remove_authfile
To deactivate authfile.txt for the selected
expansion module, for example:
remove_authfile 1
set_log_category
To set a log category for the selected expansion
module, for example:
set_log_category 1 AUDIO
Button modules overview
Note:
The full list of available log categories and their
description is provided in your
46xxsettings.txt file. View allowed values
for the LOG_CATEGORY parameter.
set_log_level
To set a log level for the selected expansion
module, for example:
set_log_level 1 0
Note:
The full list of available log levels and their
description is provided in your
46xxsettings.txt file. View allowed values
for the LOCAL_LOG_LEVEL parameter.
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones19
The Wi-Fi module enables the phone to connect to a network through a wireless network. If the
phone loses connection to one Wi-Fi network, it continues to operate with another redundantly
configured wireless network or Ethernet network. A Wi-Fi status icon displays when Wi-Fi is in
use. If the phone is connected to Ethernet switch and the Ethernet link goes down, a pop-up
message displays to change network connectivity to Wi-Fi.
You can configure Wi-Fi network by:
• Setting Wi-Fi parameters by using the 46xxsettings.txt file
• Configuring Wi-Fi from the phone UI
• Configuring Wi-Fi parameters from the web UI
Note:
VLAN and LLDP functionalities are not supported over a wireless network.
J100 wireless module
Avaya J129 IP Phone and Avaya J179 IP Phone support wireless module. The wireless module is
an optional component and you can order this module separately.
Note:
Avaya J139 IP Phone and Avaya J169 IP Phone do not support J100 wireless module.
Installing the wireless module
Before you begin
Obtain the following items:
• Phillips #1 screw driver to install the screw of the J100 Wireless Module.
• A flat screw driver that fits in the opening of the module panel.
December 2018Installing and Administering Avaya J100 Series IP Phones21
WLAN_PASSWORDN/ASpecifies the pre-configured Wi-Fi
network password. This
parameter is applicable if the
WIFISTAT is enabled and
WLAN_SECURITY is wpa2psk,
or WLAN_SECURITY is wpa2e,
WLAN_WPA2E_EAP_METHOD
is PEAP and
WLAN_WPA2E_EAP_PHASE2 is
MSCHAPV2.
The password must be from 8 to
63 characters. Note that the
space and ASCII 0x20 are not
supported.
WEP_KEY_1 to WEP_KEY_4N/ASpecifies the name of the WEP
key.
The name of the 40 bit key and
128 bit key are of 10 hex digits
and 26 hex digits respectively.
WLAN_WPA2E_EAP_METHOD
PEAP
Specifies the pre-configured
802.1x EAP method. This
parameter is applicable if
WIFISTAT parameter is enabled
and WLAN_SECURITY is set as
wpa2e.
Value operation:
PEAP
•
TLS
•
WLAN_WPA2E_IDENTITYN/ASpecifies the 802.1x name of pre-
configured Wi-Fi network. This
parameter is applicable if
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones26
WIFISTAT parameter is enabled
and WLAN_SECURITY is set as
wpa2e.
The name must be from one to 32
characters.
Note that the space character and
ASCII 0x20 are not supported.
WLAN_WPA2E_ANONYMOUS_I
DENTITY
N/ASpecifies the 802.1x anonymous
name of pre-configured Wi-Fi
network. This parameter is
applicable if WIFISTAT parameter
is enabled,
WLAN_WPA2E_EAP_METHOD
is set to PEAP and
WLAN_SECURITY is set as
wpa2e.
The name must be from one to 32
characters.
Hardware setup
WLAN_L2QUAD
WLAN_DSCPAUD
WLAN_L2QSIG
SET WLAN_DSCPSIG
6
46
3
34
Note that the space character and
ASCII 0x20 are not supported.
Specifies the layer 2 priority value
for audio frames generated by the
telephone.
Valid value is from 0 to 7.
Specifies the layer 3
Differentiated Services (DiffServ)
Code Point for audio frames
generated by the telephone.
Valid value is from 0 to 63.
Specifies the layer 3
Differentiated Services (DiffServ)
Code Point for audio frames
generated by the telephone.
Valid value is from 0 to 63.
Specifies the layer 3
Differentiated Services (DiffServ)
Code Point for signaling frames
generated by the telephone.
Valid value is from 0 to 63.
December 2018Installing and Administering Avaya J100 Series IP Phones27
The wall mounting procedure for all Avaya J100 Series IP Phones is similar. Wall mounting
brackets look different for Avaya J169/J179 IP Phone and Avaya J129 IP Phone.
You can order the kit separately, using the part numbers that correspond to the phone model. For
example, the part number of the wall mount bracket is 700512707. The procedure describes the
wall mounting procedure with illustrations as reference.
The following procedure describes Avaya J100 Series IP Phones wall mounting with typical
illustrations provided as reference.
Before you begin
Obtain the following items:
• Wall mounting kit that contains a wall mount bracket, and an Ethernet cable.
• Four #8 screws. The screws are not provided with the wall mounting kit.
Procedure
1. Do one of the following:
• Place the bracket on the wall, drill holes, and then affix the #8 screws.
• If there is a pre-installed wall plate, place the wall mount bracket over the wall plate. In
this case, you do not need the screws.
December 2018Installing and Administering Avaya J100 Series IP Phones28
2. Attach an Ethernet cable to the network port of the phone and to the wall jack.
3. Attach the phone to the wall mount bracket by inserting the two upper tabs of the wall
mount bracket into the slots on the back of the phone. The lower pair of tabs rest against
the back of the phone and ensure that the phone does not move when the keys are
pressed.
Related links
Wall mounting Avaya J100 Expansion Module on page 29
Wall mounting Avaya J100 Expansion Module
About this task
Wall mounting procedure for an Avaya J100 Expansion Module is similar to the one for Avaya
J100 Series IP Phones.
December 2018Installing and Administering Avaya J100 Series IP Phones29
You can order the wall mounting bracket for Avaya J100 Expansion Module separately, along with
the kit. The part number of the wall mount bracket is 700514338.
Before you begin
Obtain the following items:
• Wall mounting kit that contains a wall mount bracket.
• Two #8 screws. The kit does not include the screws.
Procedure
1. Remove the phone from the wall mount bracket.
2. Place the expansion module bracket on one level to the right of the phone bracket, drill
holes, and then affix the #8 screws.
December 2018Installing and Administering Avaya J100 Series IP Phones30
3. Attach the Avaya J100 Expansion Module to the wall mount bracket by inserting the upper
tab of the wall mount bracket into the slot on the back of the expansion module.
4. Attach the phone to the wall mount bracket. See Wall mounting Avaya J100 Series IP
Phones on page 28 for more details.
Related links
Wall mounting Avaya J100 Series IP Phones on page 28
Software installation
Phone installation process
You can install Avaya J100 Series IP Phones in the following ways:
• With the Device Enrollment Server (DES) discovery process: The installation process begins
after the phone is connected to a network. This is an automated process.
• Without the DES discovery process: The installation process includes a series of preconfiguration tasks.
Phone installation with DES
DES server
Device Enrollment Service (DES) is an Avaya cloud service used to automate the deployment of
phones, especially during initial deployment. DES exposes interfaces to allow different entities to
interact with the service.
December 2018Installing and Administering Avaya J100 Series IP Phones31
Installing the phone by using DES eliminates the need for manual configuration of a provisioning
server. Device Enrollment Service is available at des.avaya.com.
The DES phone interface
The phone which supports DES comes from the factory with a unique device certificate that is
known to the DES server. The phone’s firmware includes a list of trusted root certificates of wellknown public certificate authorities. The phone is programmed with the identity of the DES service,
des.avaya.com.
Installing the phone using the DES server
During initial boot-up, the phone prompts the user to select if he wants to contact the DES server.
The Do you want to activate Auto Provisioning now notification is displayed on the
phone.
The user has 60 seconds to select Yes or No options or the timeout will be activated.
The following options are available:
• Yes: This option indicates that the phone should use only DES for server discovery instead of
a local network.
If the phone can contact DES and is able to obtain the configuration server URL, it will
contact the configuration server to get the settings. If the phone fails to contact the
configuration server, it will prompt the user to enter the configuration server information
manually.
If the phone can contact DES, but there is no configuration server assigned to the phone on
DES, it will prompt the user to enter the enrollment code.
When the user enters the enrollment code, the phone will contact DES again to obtain data
on its configuration server and will contact the configuration server for downloading the
settings.
The user can cancel the operation of entering the enrollment code. In this case, he will be
prompted to enter the configuration server manually.
• No: This option indicates that the phone should not use DES and should discover the
configuration server using the existing mechanism based on DHCP option 242. If the phone
fails to discover the configuration server using DHCP option 242, it will prompt the user to
enter a configuration server manually.
• Timeout: After the interval of 60 seconds, if no option is selected, the phone will use the
existing mechanism based on DHCP option 242. If the phone fails to discover the
configuration server in this case, it will contact DES to get the configuration server URL.
The following diagram shows the flow of DES discovery procedure:
December 2018Installing and Administering Avaya J100 Series IP Phones32
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.
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
addresses
DHCP—
LLDP———
Settings file—
Avaya Aura® System Manager and IP
Office
Administration menu on the phone——
Web UI
————
Tagging
and VLAN
Can administer
Network
Time
Server
Quality of
Service
Applicationspecific
parameters
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
December 2018Installing and Administering Avaya J100 Series IP Phones35
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
Phone installation
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. Administering the phone from the web UI.
3. Avaya Aura® System Manager and IP Office.
4. 46xxsettings.txt file
5. DHCP.
6. 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, DSCPVID, 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.
Diagram: Phone deployment process
December 2018Installing and Administering Avaya J100 Series IP Phones36
For information about IP Office preinstallation data gathering, see Avaya IP Office Platform
10.0 SIP Telephone Installation Notes.
Installing the phone
Before you begin
You must do the following:
• Configure the file server.
• Download and extract the firmware zip file to your file server.
• Configure the 46xxsettings.txt file.
Procedure
1. Set up the phone hardware.
2. Plug the Ethernet cable to the phone.
The phone powers up and starts to initialize.
3. The initialization procedure consists of the following processes:
Software installation
a. The phone checks for LLDP messages.
b. The phone sends a DHCP DISCOVER message to discover the DHCP server in the
network and invokes the DHCP process.
If the phone does not receive a provisioning server address from the configuration
setup, the phone displays the Configure Provision Server screen.
c. In the Configure Provision Server screen, press the Config softkey and enter the
address of the provisioning server. The provisioning server address can be in the form
of IP address or a Fully Qualified Domain Name (FQDN). To enter the dot symbol (.)
in the field, press the alphanumeric softkey to toggle to the alphanumeric mode.
d. The phone verifies the VLAN ID, and starts tagging the data and voice packets
accordingly.
e. The phone sends and identifies an upgrade script file, gets the Settings file, the
language files, and any firmware updates.
• If configured to use simple certificate enrollment protocol (SCEP), the phone
downloads a valid device certificate.
• The phone displays only the Admin softkey for 15 seconds, and then the Admin
and the Login softkeys.
Note:
For subsequent restarts, if the user login is automatic and the supplied
credentials are valid, the Login softkey is not displayed.
December 2018Installing and Administering Avaya J100 Series IP Phones39
Administrators can enable access to the web interface of the phone through one of the following
methods:
• By using the phone Administration menu.
• By setting the required parameter in the 46xxsettings.txt file.
Related links
Enabling access to the web interface through the Phone Administration menu on page 41
Enabling web interface access through the settings file on page 42
Viewing IP address of the phone on page 42
Enabling access to the web interface through the Phone
Administration menu
Procedure
1. On the phone, press Main Menu.
2. Scroll to Administration, and press Select.
3. In the Access code field, enter the administration password.
The default access code is 27238.
4. Press Enter.
5. Scroll to Web Server, and press Select.
You can enable or disable access to the web interface only in third-party call control set up.
6. Scroll to Web on HTTP, and Toggle to Yes.
7. Press one of the following:
• Save
• OK
December 2018Installing and Administering Avaya J100 Series IP Phones41
Use this procedure to log in or log out of the web interface. Note that the system prompts you to
change your default password only after the first log in.
Procedure
1. In your browser, enter the IP address of the phone and press Enter.
2. On the login page, type the following:
• Username: The user name is always admin.
• Password: The default password is 27238.
3. Click Login.
The system displays the Change Default Password dialog box.
4. In the Change Default Password dialog box, type the following:
• Current password
• New password
• Confirm password
5. Click Update.
The system displays the login page.
6. Log in by entering the username and the new password.
7. To log out of the web UI, click Logout.
Configuring network settings
About this task
Avaya J100 Series IP Phones display the details of the configuration fields in the Description
section.
Procedure
1. Log in to the web interface as an administrator.
2. In the navigation pane, click Network.
3. Configure the following areas:
• Network
• DNS
• ICMP
December 2018Installing and Administering Avaya J100 Series IP Phones43
• Yes (default): To use the assigned IP address after the DHCP lease
expires.
• No: To stop using the assigned IP address after the DHCP lease
expires.
IPv4 AddressSpecifies the IP address of the phone. You can enter the IP address in
this field.
The valid value is an IP address in the dotted decimal name format.
The maximum number of characters is 15.
Subnet MaskSpecifies the network mask address. To assign the network mask
address manually to your phone, type the address in this field.
The valid value is an IP address in the dotted decimal name format.
The maximum number of characters is 15.
IPv4 GatewaySpecifies the IP address of the gateway.
The valid value is an IP address in the dotted decimal name format.
The maximum number of characters is 15.
IPv6 Configuration
DHCPv6 Client StatusSpecifies whether DHCPv6 Client is enabled or disabled.
The options are:
• DHCPv6 client enabled (default)
• DHCPv6 client disabled
Use DHCPv6Specifies whether to use DHCPv6 as a source in IPv6 network.
The options are:
• Yes (default): To assign the IPv4 address automatically to your
phone.
• No: To assign the IPv4 address manually to your phone.
Continue to use DHCPv6
information after lease expiry
Specifies whether the DHCPv6 will comply with the IETF RFC 3155
standard and immediately stop using an IPv6 address if the address
valid lifetime expires.
The options are:
• Yes (default)
• No
IPv6 AddressSpecifies the IPv6 address of the phone.
Value format: eight groups of four hexadecimal digits. The default value
is null.
IPv6 Link Local AddressSpecifies the link local address.
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones48
Specifies the time duration in minutes for XSI event channel. The phone
will ask XSP server to maintain the established Comet HTTP connection
for the specified period of time. After 50% of this time phone will reestablish
Comet HTTP connection.
The valid value is an integer from 60 to 1440. The default value is 60
minutes.
XSI Event Channel
HeartBeat
Specifies the time interval in seconds to send heartbeat messages over
Comet HTTP connection to XSP server of BroadWorks.
The valid value is an integer from 1 to 999. The default value is 15
seconds.
XSI User IdSpecifies the BroadSoft user ID which the phone must use for XSI
authentication.
BroadSoft user Id is the SIP user Id excluding at (@) and domain.
The valid value is a string of 0 to 255 ASCII characters.
XSI Web PasswordSpecifies the BroadSoft's web portal password which the phone must use
for XSI web authentication.
If the value is null, SIP authentication method is used.
Busy Lamp Field( BLF)
Allow User to Change BLF
List
Specifies the control to provide the user permissions to add and remove
BLF monitored users from the phone.
The values are:
• User is allowed to add or delete BLF monitored users
• User is allowed to add BLF monitored users
• User is allowed to delete BLF monitored users
• User is allowed to add and delete BLF monitored users (default)
SIP Global Settings
SIP DomainSpecifies the SIP domain used for SIP registration.
The valid value is a string of 0 to 255 ASCII characters.
Enable PPM as source of
Proxy Server
Specifies whether PPM is used as a source of SIP proxy server
information.
Note:
This is an Avaya Aura® setting which is ignored in the 3PCC
environment.
The options are:
• Yes (default)
• No
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones59
Proxy PolicySpecifies whether SIP proxy servers are read-only or can be edited.
The options are:
• Manual (Use Phone Admin Menu or WEB to configure): To configure
SIP proxy server manually by using the phone or the web interface.
• Automatic (Can be set from DHCP, LLDP, Settings File, PPM)(default): To use the SIP proxy server settings received from the
46xxsettings.txt file or PPM.
SIP Proxy ServerSpecifies the SIP proxy server domain.
The valid value is a string of 0 to 255 ASCII characters, for example:
Specifies the SIP proxy server settings as received from the
46xxsettings.txt file or PPM.
Register to Proxy ServerSpecifies whether the phone registers simultaneously to a proxy server.
The options are:
• Simultaneous (default)
• Alternate
Number of proxy server to
register simultaneously
Specifies the number of SIP proxy controllers that the phone can register
simultaneously.
The options are:
• 1
• 2
• 3 (default)
Registration IntervalSpecifies the time interval in seconds between two registrations to the SIP
proxy.
The valid value is an integer from 30 to 86,400. The default value is 900
seconds.
Un-registration Wait Timer
(seconds)
Specifies the time in seconds during which the phone waits before
terminating all SIP dialog and SIP registrations.
The valid value is an integer from 4 to 3,600. The default value is 32
seconds.
Registration Wait Timer
(seconds)
Specifies the time in seconds during which the phone waits for a response
message from registration. If no response message is received within this
time, the phone tries to register again.
The valid value is an integer from 4 to 3,600. The default value is 32
seconds.
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones60
Send DTMFSpecifies whether the phone sends DTMF tones in-band as regular audio,
or out-of-band using RFC 2833 procedures.
The options are:
• In-band
• Out-of-band (default)
OPUS PayloadDynamically specifies the RTP payload type to be used for OPUS codec.
The parameter is used when the media request is sent to the far-end in an
INVITE or 200 OK when INVITE with no Session Description Protocol
(SDP) is received.
The valid value is an integer from 96 to 127. The default value is 116.
G.726 PayloadSpecifies the RTP payload type to be used for the G.726 codec.
The valid value is an integer from 96 to 127. The default value is 110.
DTMF PayloadSpecifies the RTP payload type to be used for RFC 2833 signaling.
The valid value is an integer from 96 to 127. The default value is 120.
RTP
Play Tone till RTPSpecifies whether the locally generated ringback tone stops when SDP is
received for an early media session, or whether it continues until RTP is
actually received from the far-end party.
The options are:
• Yes (default)
• No
Symmetric RTPSpecifies whether the phone must receive RTP if the UDP source port
number is not same as the UDP destination port number.
The options are:
• Disable
• Enable (default)
RTCP_XRSpecifies whether VoIP Metrics Report Block as defined in RTP Control
Protocol Extended Reports (RTCP XR) (RFC 3611) is sent as part of the
RTCP packets to a remote peer or an RTCP monitoring server.
The options are:
• Yes
• No (default)
SRTP
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones62
SIP Timer T4Specifies the maximum duration in milliseconds for which a message
remains in the network.
The valid value is an integer from 2,500 to 60,000.
The default value is 5,000 milliseconds.
INVITE Response TimeoutSpecifies the maximum number of seconds that the phone waits for
another response after receiving a SIP 100 Trying response.
The valid value is an integer from 30 to 180.
The default value is 60 seconds.
Failed Session Removal
Timer
Specifies the time in seconds to automatically remove a failed call session.
The valid value is an integer from 5 to 999.
The default value is 60 seconds.
Outbound Subscription
Duration Request
Specifies the Outbound subscription request duration in seconds.
The valid value is an integer from 60 to 31,53,600.
The default value is 86,400 seconds.
Controller Search IntervalSpecifies the time in seconds that the phone waits to complete the
maintenance check for monitored controllers.
The valid value is an integer from 4 to 3,600.
The default value is 16 seconds.
Active subscription wait
time for "avaya-cmfeature-status"
Specifies the time in seconds that the phone waits to validate an active
subscription when it subscribes to the avaya-cm-feature-status package.
The valid value is an integer from 16 to 3,600.
The default value is 60 seconds.
Remote Data Source initial
retry time
Specifies the number of seconds that the phone waits for the first time
before trying to contact the PPM server again after a failed attempt. Each
subsequent retry is delayed by double the previous delay time.
The valid value is an integer from 2 to 60.
The default value is 2 seconds.
Remote Data Source
maximum retry time
Specifies the maximum delay interval in seconds after which the phone
stops to contact the PPM server.
The valid value is an integer from 2 to 3,600.
The default value is 600 seconds.
Remote Data Source initial
retry attempts
Specifies the number of attempts the PPM adaptor must try to download
from PPM before it stops connecting to the PPM server.
The valid value is an integer from 1 to 30.
The default value is 15 attempts.
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones64
Extend RingtoneSpecifies the audio files to customize the ring tone.
Value format: the list of file names in .xml format separated by
commas.
The default value is empty.
Group NumberSpecifies group numbers if available.
The valid value is an integer from 0 to 999. The default value is
0.
Minimum delay to backup volume
level to PPM
Specifies the minimal time in seconds between backups of the
volume levels to the PPM service when the phone is registered
to Avaya Aura® Session Manager.
The valid value is an integer from 0 to 900. The default value is
2.
Audio
Call Progress Tone CountrySpecifies the country of operation.
The valid value is a sting of 0 to 255 characters. The default
value is USA.
AGC HandsetSpecifies the Automatic Gain Control setting for the handset.
The options are:
• Disable
• Enable (default)
AGC HeadsetSpecifies the Automatic Gain Control setting for the headset
interface.
The options are:
• Disable
• Enable (default)
AGC SpeakerSpecifies the Automatic Gain Control setting for the speaker.
The options are:
• Disable
• Enable (default)
Handset Sidetone LevelSpecifies the level of side tone in the handset.
The options are:
• Normal level (default)
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones73
1. Log in to the web interface as an administrator.
2. In the navigation pane, click Date & Time.
3. In the SNTP area, configure the following:
• SNTP Server: Type the SNTP server IP address.
• SNTP SYNC Interval: Type the SNTP synchronization time interval in minutes to resynchronize the phone’s local time . The valid value is from 60 to 2880 minutes. The
default synchronization time is 1440 minutes.
• GMT Offset: Type the time between the local standard time and Greenwich Mean Time
(GMT) in hours and minutes. The valid value is from 0:00 to ±12:59.
4. In the Daylight Saving section, configure the following:
• Daylight Saving Mode: Select one of the following options:
- No daylight saving time
- Manual daylight savings activated (time set to DSTOFFSET)
Configuring date and time
- Automatic daylight savings adjustments (as specified by DSTSTART and
DSTSTOP) (default)
• DST Offset: Specifies the time in hours between the standard time and daylight savings
time. Select one of the following options:
- 0
- 1 hour (default)
- 2 hours
• DST Start: Specifies when to apply the offset for daylight savings time. The value format
must be either odddmmmht or Dmmmht, where:
- o represents a one-character ordinal adjective. For example, 1 for first, 2 for second,
3 for third, 4 for fourth, or L for last.
- D represents 1 or 2 ASCII digits or characters representing the date of the month.
- ddd represents three characters containing the English abbreviation for the day of the
week. For example, Sun for Sunday, Mon for Monday, etc.
- mmm represents a three-character English abbreviation for the month. For example,
Jan for January, Feb for February, etc.
- h represents a one-numeric digit representing the time to make the adjustment at
hAM (0h00 in military format).
The valid values of h are from 0 to 9.
- t represents one character for the time zone to which the changes are applied. For
example, “L” for local time or “U” for Universal Time.
December 2018Installing and Administering Avaya J100 Series IP Phones79
• Reset to Default: To revert to the default values.
Related links
Management settings field descriptions on page 81
Management settings field descriptions
NameDescription
Device Enrollment Service
DES DiscoverySpecifies the DES Discovery mode.
The options are:
• Enable (default)
• Disable
• Disable and Restored with Reset to Default
Embedded Public CertificatesSpecifies whether to trust the embedded public
certificates.
The options are:
• Trusted only if Trustcerts is empty (default)
• Always Trusted
HTTP Provisioning Server
HTTP Server AddressSpecifies the IP address of the of the provisioning
file server.
The valid value is the IP address in the dotted
decimal name format, DNS name format or colonhex.
The default value is “0.0.0.0”.
HTTP Server Directory PathSpecifies the path all configurations and data files
the device might request when starting up. This
path is relative to the root of the HTTP file server, to
the directory in which the device configuration and
date files are stored.
The valid value is a sting of up to 127 ASCII
characters without spaces. The default value is
empty.
HTTP PortSpecifies the HTTP port address.
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones81
The valid value is an integer from 0 to 65535. The
default port number is 80.
HTTPS Provisioning Server
HTTPS Server AddressSpecifies the IP address of the HTTPS provisioning
file server.
The valid value is the IP address in the dotted
decimal name format, DNS name format or colonhex.
The default value is “0.0.0.0”.
HTTPS Server Directory PathSpecifies the path all configurations and data files
the device might request when starting up. 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.
The valid value is a sting of up to 127 ASCII
characters without spaces. The default value is
empty.
HTTPS PortSpecifies the HTTPS port address.
The valid value is an integer from 0 to 65535. The
default is 443.
Configuration
Configuration Server Access ModeSpecifies the server access mode of the
provisioning server.
The options are:
• HTTP
• HTTPS (default)
Note:
Use HTTPS if the SIP transport mode is TLS,
otherwise, use HTTP.
Download configuration file using HTTPS onlySpecifies whether only HTTPS is used to download
the settings file.
The options are:
• Yes
• No (default)
Import Configuration FileEnables the user to import the settings file. To
import the settings file, click Browse to browse your
local PC or any PC connected to the network.
Select the file and click Import.
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones82
Changing the password of the web interface and the phone admin
NameDescription
Note:
Restart the phone for new parameters from the
settings file to take effect.
Export Configuration FileEnable user to export a configuration file. To export
the configuration file, click Export .
Firmware
Software VersionDisplays the version of the SIP software.
The default value is empty.
Backup Software VersionDisplays the backup software version.
The default value is empty.
Firmware UpgradeEnables the user to import the firmware upgrade file
from a local PC or any PC connected to the
network.
To upload the firmware upgrade file, click Browse
to browse your PC, select the file and click
Upgrade.
The phone reboots after you select Yes in the
prompt.
Backup/Restore User Data
User store Address for Backup/RestoreSpecifies the IP address or the DNS name used for
HTTP(S) data backup and retrieval.
The valid value starts with http:// or https://
and contains either an IP address or a DNS name
without any intervening spaces. The maximal value
length is 255 characters.
Related links
Configuring management settings on page 80
Changing the password of the web interface and the
phone admin
About this task
Use this procedure to change the administrator password for the phone Administration menu and
the web interface.
Your administration password must be between 8 to 31 alphanumeric characters including upper,
lower, and special characters. Your password must contain at least 2 digits. You can use special
characters such as: tilde (~), exclamation mark (!), at (@), pound (#), dollar ($), percent (%), carat
December 2018Installing and Administering Avaya J100 Series IP Phones83
Available Trusted CertificateDisplays the file names of available certificates for authentication.
Upload Trusted CertificateSpecifies the trusted certificate used by the phone. You can also
browse and upload the certificates from the local PC by clicking
Browse > Import.
Trusted Certificates file to uploadSpecifies the name of the certificate file to be uploaded.
The valid value is a string os up to 255 ASCII characters. File
names must be separated by commas without any intervening
spaces.
The default value is empty.
Match Identity to trust certificateSpecifies the status of the TLS server identification.
The options are:
• Yes (default)
• No
Server Certificate re-check hoursSpecifies the time interval in hours for rechecking the expiration
and revocation status of the certificates used to establish any
existing TLS connections.
The valid value is an integer from 0 to 32767. The default value is
24 hours.
Warning on number of days
before Certificate expiration
FQDN IP MappingSpecifies a FQDN contained in the certificate when an IP address
Online Certificate Status Protocol (OCSP)
Enable OCSPSpecifies the status of OSCP.
Specifies the number of days before the expiration of a certificate
that a warning must first appear on the phone screen.
The valid value is an integer from 0 to 99. The default value is 60
days.
is used to establish the connection. The parameter is a commaseparated list of names or value pairs where the name is an FQDN
and the value is an IP address.
The valid value is a string of up to 255 characters without any
intervening spaces. The default value is empty.
The options are:
• Disable (default)
• Enable
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones89
OCSP Cache ExpirySpecifies the time interval in minutes for the OCSP cache expiry.
The valid value is an integer from 60 to 10080. The default value is
2880 minutes.
SCEP
SCEP ServerSpecifies the URL address of the SCEP server.
The valid value is a string of up to 255 ASCII characters without
any intervening spaces. The default value is empty.
Common NameSpecifies the common name for the subject in an SCEP certificate
request.
The valid value is a string of up to 255 ASCII characters without
any intervening spaces. The default value is “$SERIALNO”.
SubjectSpecifies the part of SUBJECT in an SCEP certificate request that
is common for requests from different device. For example,
Organizational Unit, Organization, Location, State, and Country.
The valid value is a string of up to 255 ASCII characters without
any intervening spaces. The default value is empty.
CA IdentifierSpecifies the Certificate Authority Identifier.
Certificate Authority servers may require a specific CA Identifier
string to accept GetCA requests. If the device works with such a
Certificate Authority, the CA identifier string can be set through this
parameter.
The valid value is a string of up to 255 ASCII characters without
any intervening spaces. The default value is “CAIdentifier”.
Initiate renewal on % of Validity
Interval
Specifies the percentage of the identity certificate’s Validity interval
after which renewal procedures will be initiated.
If the renewal time interval has elapsed, the phone starts to contact
the SCEP server periodically to renew the certificate.
The valid value is an integer from 1 to 90. The default value is 90
percent.
Phone behavior on Pending
request
Specifies the functioning of the device when performing certificate
enrolment.
The options are:
• Poll SCEP server periodically in background
• Wait until a certificate is received or rejected (default)
SCEP PasswordSpecifies a challenge password to use with SCEP.
Table continues…
December 2018Installing and Administering Avaya J100 Series IP Phones91
To install Avaya J100 Series IP Phones in your telephony environment, you must configure the
following servers:
• DHCP server: To dynamically assign IP addresses to the devices and provide the device
configuration parameters. The DHCP server also provides the device with the addresses of
the SIP controller and file server.
• HTTP or HTTPS file server: To download and save the software distribution package and the
settings file.
In a Device Enrollment Services environment, the DHCP server is used to assign IP addresses to
the devices. The device receives the file server address from Device Enrollment Services.
Related links
File Server configuration on page 97
DHCP server configuration on page 104
File Server configuration
A file server is an HTTP or an HTTPS server that is required to download and save the software
distribution package and the Settings file.
On restarting, the phone checks for software updates and Settings files on the specified file
servers.
You can provide the file server addresses to phones through one of the following methods:
• DHCP
• LLDP
• Administration menu on the phone
• Settings file
December 2018Installing and Administering Avaya J100 Series IP Phones97
Provides the software
Software distribution
package and Settings
file (configurable
parameters for
provisioning)
1
2
46xxsettings.txt
Sets the system
parameters for
configuration
Configures user, communication, and session profile
Manages power
and provides
configurable
parameters
for provisioning
Network server /
Switch (LLDP)
F I L E
S E RV E R
3
Avaya IP
Office Manager
Primary
Avaya IP
Office Manager
Secondary
Avaya Aura
®
System Manager
Avaya IP Office Manager
Server configuration
Related links
Setting up a file server
Figure 2: Diagram: Phone setup in IP Office environment
Server configuration on page 97
Setting up a file server on page 99
Software distribution package on page 100
Downloading and saving the software on page 101
Contents of the settings file on page 101
Modifying the Settings file on page 103
About this task
Use this procedure to configure an HTTP or HTTPS file server. You can use the file server to
download and store distribution packages and settings files for the phones.
Procedure
1. Install the HTTP or HTTPS server software according to the software vendor’s instructions.
For HTTPS connections, you must initially install a trust certificate through an HTTP server
and then transfer to an HTTPS server. Ensure that the TRUSTCERTS parameter includes
the root CA certificate of the HTTPS file server identity certificate.
December 2018Installing and Administering Avaya J100 Series IP Phones99
2. Download the software distribution package and the 46xxsettings.txt settings file.
3. Extract the distribution package, and save the extracted files and the 46xxsettings.txt
settings file on the file server.
Related links
File Server configuration on page 97
Software distribution package
Note:
For any new software release, ensure that you download the latest software distribution
package and read any Product Support Notices (PSNs) associated with the new release. Both
are available on the
Review the release notes and any Read Me files associated with a distribution package.
Ensure that the Settings file is not cached in your browser. To do this, clear the browser
cache before downloading the Settings file from the Avaya support Web site, so that you
don’t get an old version.
Software distribution package containing the files needed to operate the Avaya J100 Series IP
Phones are packaged together in a ZIP format. You can download the package from the Avaya
support website.
Avaya support website
Note:
From IP Office R 10.0 SP3 or later, the software distribution package for the Avaya J100
Series IP Phones is part of the IP Office admin CD.
SIP software distribution package contains:
• One or more software files
• One upgrade file (J100Supgrade.txt)
• Language files. For example, Mlf_J129_BrazilianPortuguese.xml,
Mlf_J129_Chinese.xml.
• Files av_prca_pem_2033.txt and av_sipca_pem_2027.txt that contain a copy of the Avaya
Product Root Certificate Authority certificate in PEM format that may be downloaded to
phones based on the value of the TRUSTCERTS parameter.
• File named release.xml that is used by the Avaya Software Update Manager application.
Avaya Software Update Manager upgrades and maintains firmware for Avaya managed
devices.
Note:
Settings files are not included in the software distribution packages because they would
overwrite your existing files and settings.
Two configuration files that are important to understand are as follows:
• The upgrade file, J100Supgrade.txt that tells the phone whether the phone needs to
upgrade software. The phones attempt to read this file whenever they reset. The upgrade
file is also used to point to the Settings file.
December 2018Installing and Administering Avaya J100 Series IP Phones100