Avaya one-X 9601 Installation And Maintenance Manual

Avaya one-X™ Deskphone SIP
Installation and Maintenance Guide
Release 6.1 for 9601IP Deskphone

16-603843

December 2010

Issue 1

© 2010 Avaya Inc.
All Rights Reserved.

Notice

While reasonable efforts have been made t o en sure t hat the inf orma tion in t his
document is complete and accurate at the time of printing, Av aya assumes no
liability for any errors. Avaya reserves the right to make changes and
corrections to the information in this document without the obligation to notify
any person or organization of such changes.

Note

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 by Avaya in varying mediums
which may include product information, operating instru ctions and performance
specifications that Avaya generally makes available to users of its products.
Documentation does not include marketing materials

Avaya shall not be responsible for any modifications, additions, or deletions to
the original published version of this documentation unless such modifications,
additions, or deletions were performed by 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.

For the most current versions of documentation, go to the Avaya support Web
site http://www.avaya.com/support

Link disclaimer

Avaya is not responsible for the contents or reliability of any linked Web sites
referenced within this site or documentation(s) provided by Avaya. Av aya is not
responsible for 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 of the time and we have no control over the availability of the linked
pages.

Warranty

Avaya provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warran ty. 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 Web site: http://www.avaya.com/support.
Please note that if you acquired the product from an authorized Avaya reseller
outside of the United States and Canada, the warranty is provided to you by
said Avaya reseller and not by Avaya.

License

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE,
HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE APPLICABLE TO
ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA
SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR
AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A
COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA
RESELLER. 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 AUTHORIZED RESELLER, AND 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 INST ALLING, 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 End User a license within the scope of the license types
described below. 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 End User. “Designated Processor” means a single
stand-alone computing device. “Server” means a Designated Processor that
hosts a software application to be accessed by multiple users. “Soft w are”
means the computer programs in object code, originally licensed by Avaya and
ultimately utilized by End User, whether as stand-alone products or
pre-installed on Hardware. “Hardware” means the sta ndard hardware origin ally
sold by Avaya and ultimately utilized by End User.

License Types:

Designated System(s) License (DS). End User may install and use each copy
of the Software on only one Designated Processor, unless a different number

and search for "one-X Deskphone SIP".

of Designated Processors is indicated in the Documentation or other materials
available to End User. Avaya may require the Designated Processor(s) to be
identified by type, serial number, feature key, 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). With respect to Software that contains elements
provided by third party suppliers, End User may install and use the Software in
accordance with the terms and conditions of the applicable license
agreements, such as "shrinkwrap" or "clickwrap" license accompanying or
applicable to the Software ("Shrinkwrap License"). The text of the Shrinkwrap
License will be available from Avaya upon End User’s request (see "Third-party
Components" below for more information).

Copyright

Except where expressly stated otherwise, no use should be made of materials
on this site, the Documentation, Software, or Hardware provided by Avaya. All
content on this site, the documentation 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.

Third-party components

Certain software programs or portions thereof included in the Product may
contain software distributed under third party agreements (“Third Party
Components”), which may contain terms that expand or limit rights to use
certain portions of the Product (“Third Party Terms”). Information regarding
distributed Linux OS source code (for those products that have distributed the
Linux OS source code), and identifying the co pyrigh t h olders of the Th ird P arty
Components and the Third Party Terms that apply to them is available on
Avaya’s Web site at: http://www.avaya.com/support/Copyright.

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.

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 [phone] for the United States
and Canada. For additional support telephone numbers, see the Avaya
Support Web site: http://support.avaya.com
Suspected security vulnerabilities with Avaya products should be
reported to Avaya by sending mail to: [e-mail]

Trademarks

The trademarks, logos and service marks ("Marks") displayed in this site, the
Documentation and Product(s) provided by Avaya are the registe red or
unregistered Marks of Avaya, its affiliates, or other third p arties. 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 and Product(s) should be co nstrued 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, and

"Linux" is a registered trademark of Linus Torvalds.

.

Downloading Documentation

For the most current versions of documentation, see the Avaya Support Web
site: http://www.avaya.com/support

Contact Avaya Support

Avaya provides a telephone number for you to use to report pro blems or t o ask
questions about your product. The support telephone number is
1-800-242-2121 in the United States. For additional support telephone
numbers, see the Avaya Web site:http://www.avaya.com/support

Federal Communications Commission (FCC) Interference Statement

This equipment has been tested and found to comply with t he limit s for a Class
B digital device, pursuant to Part 15 of the FCC rules. These limits are
assigned to provide reasonable protection against harmful interference 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 doe s cause harmful interference to radio or
television reception, which can be determined by turning the equipment of f and
on, the user is encouraged to try to correct the interference by one 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 diff erent f rom that
to which the receiver is connected.

• Consult the dealer or an experienced radio/TV technician for help.

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
interference that may cause undesired operation.

FCC Caution: Any changes or modifications not expressly approved by
the party responsible for compliance could void the user's authority to
operate this equipment.

FCC/Industry Canada Radiation Exposure Statement

This device complies with the FCC's and Industry Canada's RF radiation
exposure limits set forth for the general population (uncontrolled environment)
and must not be co-located or operated in conjunction with any other antenna
or transmitter.

Warning

The handset receiver contains magnetic devices that can attract small metallic
objects. Care should be taken to avoid personal injury.

.

.

Contents

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Intended Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

What’s New in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Online Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

IETF Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

ITU Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

ISO/IEC, ANSI/IEEE Documents . . . . . . . . . . . . . . . . . . . . . . . . . 9

Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2: 9600 Series IP Deskphone Installation . . . . . . . . . . . . 11

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

IP Deskphone Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

SES or Session Manager/Avaya Communication Manager (CM)/Secondary Gateway

Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Pre-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Assembling the Deskphone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Powering the IP Deskphone. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Power-Up and Reset Operation (Dynamic Addressing Process). . . . . . . . . . 18

Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Power-Up and Reset Process. . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 3: Local Administrative Options . . . . . . . . . . . . . . . . . 27

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Accessing Local (Craft) Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 28

Entering Data for Administrative Options . . . . . . . . . . . . . . . . . . . . . . 29

About Local Administrative Procedures . . . . . . . . . . . . . . . . . . . . . . . 30

Setting the 802.1X Operational Mode. . . . . . . . . . . . . . . . . . . . . . . . . 31

Pre-Installation Checklist for Static Addressing. . . . . . . . . . . . . . . . . . . 32

Static Addressing Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Disable/Enable Automatic Gain Control . . . . . . . . . . . . . . . . . . . . . . . 35

Calibrating the Touch Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Clear Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Disable/Enable Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Group Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Issue 1 December 2010 5

Contents

Interface Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Disable/Enable Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Reset System Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Restart the Deskphone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Configuring SIP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Configuring Time Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Site-Specific Option Number Setting. . . . . . . . . . . . . . . . . . . . . . . . . 47

The View Administrative Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 4: Maintaining 9600 Series IP Deskphones . . . . . . . . . . . 51

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Downloading Software Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Download Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Contents of the Settings File . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Downloading Text Language Files . . . . . . . . . . . . . . . . . . . . . . . . 54

Changing the Signaling Protocol . . . . . . . . . . . . . . . . . . . . . . . . . 55

The GROUP Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 5: Troubleshooting Guidelines . . . . . . . . . . . . . . . . . . 57

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

DTMF Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Power Interruption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Installation Error and Status Messages . . . . . . . . . . . . . . . . . . . . . . . 58

Operational Errors and Status Messages . . . . . . . . . . . . . . . . . . . . . . 60

Network Ping Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

SRTP Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Other Troubleshooting (including Failover) . . . . . . . . . . . . . . . . . . . . . 66

Appendix A: Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . 69

Terms Used in This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

6 SIP Deskphones Release 6.1 Installation and Maintenance Guide

Chapter 1: Introduction

About This Guide

This guide describes how to install and maintain Avaya one-X™ 9601 IP Deskphones in a

Session Initiation Protocol (SIP) environment and troubleshoot telephone problems.

The IP Deskphone this guide describes supports the SIP signaling protocol only and must be

aliased as certain 9600 Series IP Telephone sets, as described in the Avaya one-X™

Deskphone SIP Administrator Guide.

Note:

Note: The 9601 IP Deskphone does not support the H.323 protocol.

The 9601 IP Deskphone supports Session Initiation Protocol (SIP). Both of the following must

be installed to use 9601 Series IP Deskphones with the SIP protocol:

● Avaya Aura

software Release 5.2.1 and greater, or

● Avaya Aura

Release 6.0 and greater.

®

Communication Manager (CM) and SIP Enablement Services (SES)

®

Communication Manager (CM) and Avaya Aura® Session Manager (SM)

Note:

Note: Any reference to HTTP in this guide applies equally to HTTPS.

This document does not cover administration for Avaya Aura

®

Manager Branch. Full documentation for Avaya Aura™ Commun ication Manager
Branch is available on the Avaya support Web site.

This document does not cover installation or administration for Avaya Aura

®

Session Manager . Find full docume ntation for Avaya Aura
the Avaya support Web site, www.avaya.com/support

Session Manager on

, specifically Installing and

Upgrading Avaya Aura™ Session Manager (Document Number 03-603473) and
Administering Avaya Aura™ Session Manager (Document Number 03-603324).

This document covers installation and troubleshooting only for the 9601 IP
Deskphones. To install or troubleshoot other 9600 Series SIP Deskphones, see
the Avaya one-X™ Deskphone SIP Installation and Maintenance Guide Re lease

2.6 (Document Number 16-601943) or the Avaya one-X™ Deskphone SIP
Installation and Maintenance Guide Release 6.0 for 9608, 9611G, 9621G, and
9641G IP Deskphones.

Communication

®

Issue 1 December 2010 7

Introduction

Intended Audience

This document is intended for personnel who install and administer 9600 Se ries IP Deskphones

for a SIP environment.

!

CAUTION:

CAUTION: Avaya does not provide product support for many of the products mentioned in

this document. Take care to ensure that there is adequate technical support
available for the servers involved, including, but not necessarily limited to, HTTP,
HTTPS, and DHCP servers. If the servers are not functioning correctly, the IP
Deskphones might not be able to operate correctly.

Document Organization

The guide contains the following sections:

Chapter 1: Introduction Provides an overview of this guide.
Chapter 2: 9600 Series IP

Deskphone Installation

Chapter 3:
Administrative Options

Chapter 4: Maintaining
9600 Series IP
Deskphones

Chapter 5:
Guidelines

Appendix A: Glossary of
Terms

Local

Troubleshooting

Describes the equipment and resources required to properly
install and operate the 9600 Series IP Deskphones. Provides
instructions on installing the deskphones out of the box.

Describes how to set local administrative options, if requested by
the system or LAN administrator.

Describes maintenance actions like downloading deskphone
software from the Avaya support Web site and customizing
system values.

Describes error conditions and messages that might occur
during the installation of the 9600 Series IP Deskphones.

Provides a glossary of terms used in this document or which are
generally applicable to 9600 Series IP Deskphones.

Change History

Issue 1 This is the second release of this document, issued in December 2010 to support one

new deskphone model: the 9601.

8 SIP Deskphones Release 6.1 Installation and Maintenance Guide

What’s New in this Release

Release 6.1 supports the 9601 IP Deskphone on SIP only.

Online Documentation

See the Avaya support site at http://www.avaya.com/support for 9600 Series IP Deskphone

technical and end user documentation.

Web sites that list related, non-Avaya documents, such as those published by the Internet

Engineering Task Force (IETF) and the International Telecommunication Union (ITU) are

provided in the sections that follow.

What’s New in this Release

IETF Documents

IETF documents provide standards relevant to IP Telephony and are available for free from the

IETF Web site: http://www.ietf.org/rfc.html

ITU Documents

Access the ITU Web site for more information about ITU guidelines and documents, available

for a fee from the ITU Web site: http://www.itu.int.

ISO/IEC, ANSI/IEEE Documents

Access the ISO/IEC standards Web site for more information about IP Telephony standards,

guidelines, and published documents: http://www.iec.ch

Customer Support

.

.

For 9600 Series IP Deskphone support, call the Avaya support number provided to you by your

Avaya representative or Avaya reseller.

Issue 1 December 2010 9

Introduction

Information about Avaya products can be obtained at the following URL:

http://www.avaya.com/support

10 SIP Deskphones Releas e 6. 1 In st al lat io n an d Ma in t en a nc e Gui de

Chapter 2: 9600 Series IP Deskphone Installation

Introduction

9600 Series IP Deskphones use Internet Protocol (IP) technology with Ethernet interfaces. The

9601 Deskphones introduced in Release 6.1 supplement the existing Avaya IP Solutions

platform.

The 9600 Series IP Deskphones support DHCP and HTTP/HTTPS over IPv4/UDP which

enhances the administration and servicing of the deskphones. These deskphones use DHCP to

obtain dynamic IP Addresses and HTTP or HTTPS to download new software versions and

customized settings.

All 9600 Series IP Deskphones provide the ability to have one IP connection on the d esktop for

both a deskphone set and a PC using an Ethernet switch.

In compliance with Australian law, the following information is provided:

This equipment shall be installed and maintained by trained service personnel. All the input/
output ports are classified as Safety Extra Low Voltage (SELV, in the meaning of IEC

60950). To maintain safety compliance when connecting the equipment electrically to other
equipment, the interconnecting circuits shall be selected to provide continued conformance
of clause 2.3 for SEL V circuits (generally, double/reinforced insulation to 240VAC rms to any
primary/mains circuitry and 120VAC rms to any telecommunications network circuitry). To
ensure that these conditions are adhered to, interconnect the equipment only with the
already approved/certified equipment.

IP Deskphone Models

There are fifteen models currently defined in the 9600 Series IP Deskphone family that run the

SIP protocol. Only the model shown in bold text are covered in this guide; the remaining models

are described in the Avaya one-X™ Deskphone SIP Administrator Guide (Document Number

16-601944) and the Avaya one-X™ Deskphone SIP Installation and Maintenance Guide

Release 6.0 for 9608, 9611G, 9621G, and 9641G IP Deskphones (Document Number

16-603604):

● 9601 ● 9620 ● 9630 ● 9641G

● 9608 ● 9620C ● 9630G ● 9650

● 9610 ● 9620L ● 9640

● 961 1G ● 9621G ● 9640G

Issue 1 December 2010 11

9600 Series IP Deskphone Installation

The deskphones have an internal Ethernet switch that allows t he deskphone an d a PC to share

the same LAN connection, if appropriate. Thus, 9600 models do not need, or work with, the 30 A

switched hub interface.

This document describes the installation of the 9601 and post-installation maintenance issues.

For details about using deskphone features, see the user documentation for the deskphone.

Software

The 9601 IP Deskphones ship from the factory set to the SIP protocol. To run the deskphones in

a SIP environment, you must convert the deskphone(s) to SIP settings. Further, a

factory-shipped 9600 Series IP Deskphone may not contain the most up-to-date software for

registration and SIP operation. When the deskphone is first plugged in, a software download

from an HTTP server might be initiated. The software download gives the deskp hone upgraded

SIP functionality.

For subsequent downloads of software upgrades, SIP Enablement Services (SES) or Avaya

®

Aura

consequence of restarting, the deskphone automatically starts reboot procedures which result

in a download if new SIP software is available. Chapter 4:

Deskphones covers downloading new software releases.

Session Manager provides the capability for a remote restart of the deskphone. As a

Maintaining 9600 Series IP

SES or Session Manager/Avaya Communication Manager
(CM)/Secondary Gateway Configurations

SIP Software Release 6.0 is compatible with Release 6.0 of both Avaya Aura® Communication

Manager and SIP Enablement Services, with Release 6.0 of Communication Manager and

Avaya Aura

gateways:

● Avaya Secure Router 2330 and 4134

● Audiocodes MP-series analog and BRI gateways

● Cisco 2811 ISR

● Juniper SRX 210 and 240

● I55

● Teldat Vyda gateway

®

Session Manager. This release supports the following certified secondary

12 SIP Deskphones Releas e 6. 1 In st al lat io n an d Ma in t en a nc e Gui de

Pre-Installation Checklist

Before plugging in a 9601 Deskphone, verify that all the following requirement s are met. Failure

to do so prevents the deskphones from working properly and can h ave a negative imp act on the

network. Print copies of this checklist for each server and deskphone.

Verify These Network Requirements

1. Ensure that the LAN uses Ethernet Category 5e cabling running the IPv4 version of

Internet Protocol.

2. Ensure that the following is installed and/or set up and operative:

● Avaya Aura

(SES) software Release 5.2.1 or greater, or

● Avaya Aura Communication Manager (CM) and Avaya Aura

Manager, Release 6.0 or greater.

● NTP Time Server.

Note: 9600 Series IP Deskphones with SIP software running on SES 5.2.1 servers
have only those features compatible with that server.

®

Communication Manager (CM) and SIP Enablement Services

Pre-Installation Checklist

®

Session

See SES

or Session Manager/Avaya Communication Manager (CM)/Secondary
Gateway Configurations for information on allowable configurations before

proceeding.

!

Important:

Important: The above must be configured properly to support SIP. The CM

Outboard Proxy SIP (OPS) Station Form must be completed to
enable SIP prior to plugging in the deskphones. For information, see

SIP Support in Avaya Communication Manager Running on Avaya
S8XXX Servers (Document Number 555-245-206).

Note:

Note: CM/SES 5.2.1 and greater and SM 6.0 are the only environments that

support survivability with a supported, certified third-party proxy/
gateway.

3. The following circuit packs are installed on the switch:

● TN2602 IP Media Processor circuit pack. Sites with a TN2302 IP Media

Processor circuit pack are strongly encouraged to install a TN2602 circuit p ack
to benefit from increased capacity.

● TN799C, or D Control-LAN (C-LAN) circuit pack.

!

Important:

Important: Software Release 6.0 and greater requires TN799C V3 or greater

C-LAN circuit pack(s). For more information, see the Communication
Manager Software and Firmware Compatibility Matrix on the Avaya
support Web site h

ttp://www.avaya.com/support.

Issue 1 December 2010 13

9600 Series IP Deskphone Installation

Verify These Network Requirements (continued)

4. The Communication Manager (CM) call server is configured correctly, as described in

the Avaya one-X™ Deskphone SIP Administrator Guide and Avaya Communication
Manager documentation. Both documents are available at h

support.

5. The DHCP server and application are administered as described in the Avaya
one-X™ Deskphone SIP Administrator Guide.

6. The HTTP/HTTPS server and application are administered as described in the Avaya
one-X™ Deskphone SIP Administrator Guide.

7. The SIP upgrade script and application files from the Avaya Support Web site,

http://www.avaya.com/support

8. If applicable, the Voice Mail server is administered as described in the Avaya
one-X™ Deskphone SIP Administrator Guide.

Notes:

- Any or all of the server applications mentioned in items 5-8 can be co-resident on the
same hardware, subject to the specific restrictions of each individual application.

- See the Avaya one-X™ Deskphone SIP Administra tor Guide for more information about:

● administering other network equipment,

Note:

● administering applications like firewalls, and

● information about topics like port utilization.

ttp://www.avaya.com/

, are loaded correctly on the HTTP/HTTPS server.

Requirements to Verify for Each IP Telephone

9. Y ou have an extension numbe r and an A vaya Communication Manager security code

(password) for each applicable IP deskphone.

10. You have an OPTIM extension number and an Avaya Communication Manager
security code (password) for each deskphone, and have configured SIP Enablement
Services for each deskphone.

11. A Category 5e LAN jack is available at each deskphone site and a Category 5
modular line cable is available for connecting the deskphone to th e Ethernet wall jack.

12. Electrical power is provided to each deskphone by a Telephone Power Module (DC
power jack - SPPOE-1A IP Phone Single Port POE Injector, which must be ordered
separately). For PoE Input connection, use only with UL listed I.T.E. equipment with
PoE output. If the LAN will supply IEEE-standard power to the deskphone, no power
module is required.

13. A Category 5e modular line cord is available for the connection between the IP
deskphone and the PC, if applicable.

14. Verify that the 9600 Series IP Deskphone package includes the following
components:

● 1 deskphone set with dual position flip- or clip-stand.

● 1 handset capable of transmitting and receiving 7KHz audio.

● 1 H4DU 9-foot long (when extended) 4-conductor coiled handset cord, plu gged

into the deskphone and the handset.

● An "Important Notice and Warning" page which provides the URL for the Avaya

support site to download all other documentation.

14 SIP Deskphones Releas e 6. 1 In st al lat io n an d Ma in t en a nc e Gui de

Note:

Note: For sites using headsets, the 9600 Series IP Deskphones support only the HIS

headset cords.

Assembling the Deskphone

!

CAUTION:

CAUTION: Be careful to use the correct jack when plugging in the deskphone. The jacks are

located on the back of the deskphone housing and are flanked by icons to
represent their correct use.

Powering the IP Deskphone

The 9601 deskphones can be locally powered only with the new Telephone Power Module (DC
power jack), the IP Phone Single Port PoE Injector (SPPOE-xx), which is available separately.
In addition, the deskphones support IEEE 802.3af-standard LAN-based power . Before installing
a 9601 Deskphone, verify with the LAN administrator whether the LAN supports IEEE 802.3af,
and if so, whether the deskphone should be powered locally or by means of the LAN.

Assembling the Deskphone

Table 1: Impact of Additional Devices on Telephone Power over Ethernet Power Class

Phone

Model

Default

PoE

(Class

"L" on

IEEE

One
BM12
(IEEE

switch

setting)

Two

BM12’s

(IEEE

switch

setting)

Three

BM12’s

(IEEE

switch

setting)

One

SBM24

(IEEE

switch

setting)

Two

SBM24’s

(IEEE

switch

setting)

Three

SBM24’s

(IEEE

switch

setting)

switch)

9601 Class 1 Not Applicable; the 9601 does not support Button Modules.

!

Important:

Important: The last step in assembling the 9600 Series IP Deskphone must be applying

power. Apply power either by plugging the power cord into the power source
(local powering) or plugging the modular line cord into the Ethernet wall jack
(IEEE powering).

!

CAUTION:

CAUTION: Failure to connect the proper cables with the proper jacks might result in an

outage in part of your network.

Issue 1 December 2010 15

9600 Series IP Deskphone Installation

Figure 1 provides illustrations to connect cords to jacks on the deskphones covered in this
guide. Use the illustrations and associated procedures as appropriate for telephone assembly.

Telephone Model: See:

9601 Figure 1

16 SIP Deskphones Releas e 6. 1 In st al lat io n an d Ma in t en a nc e Gui de

Figure 1: Connection Jacks on a 9601 Deskphone

Assembling the Deskphone

1. Plug one end of the H4DU 4-conductor coiled handset cord into the deskphone and the
other end into the handset.

Issue 1 December 2010 17

9600 Series IP Deskphone Installation

2. Plug one end of the first Category 5e modular line cord into the Ethernet jack of the PC and
the other end into the secondary Ethernet jack on the 9600 Series IP Telephone,
if appropriate.

3. If the deskphone is to be IEEE-powered, plug one end of the second Category 5e
modular line cord into the Ethernet jack on the deskphone. Plug the other end of this cord
into the Ethernet wall jack. You are now finished. Do not proceed to Step 4.

4. If the deskphone is to be powered locally, connect the Category 5 modular line cord
provided with the IP Phone Single Port PoE Injector (SPPOE-xx, where xx represents the
model number) into the Ethernet jack on the phone. Plug the femite end of this cord into the
deskphone. Plug the other end of this cord into the SPPOE-xx power injector jack labeled
DATA & POWER OUT. Plug another Category 5 cord into the SPPOE-xx power injector
jack labeled DATA IN. Plug the other end of this cord into the Ethernet wall jack. Finally,
connect the SPPOE-xx to an AC power source.

Power-Up and Reset Operation (Dynamic Addressing
Process)

Note:

Note: Before starting this process you must have an OPTIM extension number for the

SIP deskphone, the Avaya Aura Communication Manager security code
(password), and a login and password on the SES/SM server.

Any reference to the HTTP server applies equally to an HTTPS server.

The initial display messages, some of which are part of DHCP give a "power on" indication and
dynamic feedback as the telephone initializes. The intent of these messages is to reassure the
user that the phone is active and has not "locked up," and to provide useful information about
the status of network, server or downloading operations before the availability of dial tone.

Initialization

The following process describes the software architecture as well as providing a high-level
overview of how the telephone is expected to operate during startup and software upgrades.
This is by no means a comprehensive description of all of the internal tasks performed during
startup.

Files are stored in five areas of reprogrammable non-volatile (flash) memory in the deskp hones:

● a boot program area,

● two Kernel/Root File Systems,

18 SIP Deskphones Releas e 6. 1 In st al lat io n an d Ma in t en a nc e Gui de

Power-Up and Reset Operation (Dynamic Addressing Process)

● one Application File System, and

● one Temporary Storage area.

Two Kernel/Root File Systems are supported in case one becomes corrupted, but only one is
activated when the telephone powers up or resets. Temporary Storage is used to store a new
Signed Application/Library Software Package that has been downloaded by the current
application until it can be installed by a process in the active Kernel/Root File System after the
next reset.

When a telephone starts up, the boot programs check the Kernel/Root File System that has
previously been marked as the one to be activated to ensure that it has not become corrupted,
and if it has not, it transfers control to a process in that file system. If that file system is
corrupted, the boot program checks the other Kernel/Root File System. If that file system is not
corrupted, it is marked as the one to be activated, the value of RFSINUSE is set to the name of
the Signed Kernel/Root Software Package that was used to install that file system, and control
is transferred to a process in it. If both Kernel/Root File Systems are corrupted, the telephone
will not operate and must be returned for repair.

A process in the active Kernel/Root File System first checks whether a Signed Application/
Library Software Package is stored in Temporary Storage, and if it finds one, it installs the
Application Software Package and/or the Library Software Package if either has a different file
name than the currently installed version, replacing the existing corresponding files in the
Application File System. The copy of the Signed Application/Library Soft ware Package stored in
Temporary Storage is then deleted. If a Signed Application/Library Software Package is not
found in Temporary Storage, the process checks the integrity of the application file s, and if they
are corrupted, the process installs files from the Backup Package, replacing the corrupted
application files in the Application File System. Any time an Application Software Package or a
Library Software Package is installed, the value of the persistent parameter APPINUSE is set to
the file name of the Signed Application/Library Software Package from which it was installed. If
the application files are not corrupted, or after the Backup Package has been inst alled, control is
transferred to the application installed in the Application File System. Note that the processes in
the Kernel/Root File System do not connect to the network or download files.

The application then connects to the network, obtains any necessary IP address information,
and download files, starting with the upgrade and settings configuration files, and including
Signed Software Packages and other separately downloaded files such as Language Files and
Certificate Files. When a Signed Software Package (which can contain either Kernel and Root
Software Packages or Application and Library Software Packages) is downloaded, it is initially
stored in volatile memory (RAM). Other downloaded files (such as Language Files and
Certificate Files) are installed directly in the Application File System.

When either type of Signed Software Package is downloaded, the Signing Authority Certificate
is extracted from the package and is validated using a copy of the Avaya Product Root
Certificate Authority Certificate that is contained in the existing application software files. If the
Signing Authority Certificate is invalid, the package is deleted. If the Signing Authority Certificate
is valid, the Hardware Version File in the package is validated using the corresponding
Signature File in the package and the Signing Authority Ce rtificate. If the signature is invalid, the
package is deleted. If the signature is valid, the Hardware Version File is used to validate
whether the package is valid for the model and hardware version of the telephone. If it is invalid,

Issue 1 December 2010 19

9600 Series IP Deskphone Installation

the package is deleted. If it is valid, the signature of the Software Packages is validated using
the corresponding Signature Files in the package and the Signing Authority Certificat e. If eit her
signature is invalid, the package is deleted.

If the signatures are valid and the Signed Software Package is a Signed Application/Library
Software Package, the package is stored in Temporary Storage. If the Backup Flag is set in the
Hardware Version File, a copy of the Signed Application / Library Software Package is also
stored as the Backup Package, replacing the previous Backup Package.

If the signatures are valid and the Signed Software Package is a Signed Kernel/Root Software
Package, the Kernel Software Package and/or the Root File System Software Package is
installed if either has a different file name than the currently installed version, replacing the
existing corresponding files in the Kernel/Root File System that was not active during st artup (a
Root File System Software Package may also install new boot programs in the boot program
area), that Kernel/Root File System is marked as the one to be activated after the next
power-up or reset, and the value of the persistent parameter RFSINUSE is set to the file name
of the Signed Kernel/Root Software Package that was installed.

Finally , if a new Signed Kernel/Roo t Sof tware Package was inst alled, the te lephone will reset to
activate the new Kernel/Root File System, which will install a new Signed Application/Library
Software Package as described above if one has been stored in Temporary Storage. If a new
signed Kernel/Root Software Package was not installed, the telephone application attempts to
register with a call server.

Power-Up and Reset Process

When you plug the deskphone set into the Ethernet wall jack and apply power, if applicable, the
following process takes place.

Note:

Note: If the application has already been downloaded, the whole process takes

approximately 1 to 2 minutes after the deskphone is plugged in. For software
upgrades, including the boot file and application file download, the process might
take 5 - 10 minutes. The duration is based on LAN loading, how many
deskphones are being installed at once, and similar factors.

Do not unplug the power cord during the download process.

During hardware initialization, the system initialization values NVCONTRAST and
NVBRIGHTNESS are checked for non-null values, and set accordingly. The Avaya one-X™
name and logo display on sets with bit-mapped displays.

1. The system initialization value for the language file in use (NVLANGFILE) is checked for a
non-null value, in which case the text strings in that language file are used for text display.
Otherwise, English text strings are displayed.

2. The boot programs check the Kernel/Root File System that has previously been marked as
the one to be activated to ensure that it has not become corrupted, and if it has not,

20 SIP Deskphones Releas e 6. 1 In st al lat io n an d Ma in t en a nc e Gui de

Power-Up and Reset Operation (Dynamic Addressing Process)

transfers control to a process in that file system. If that file system is corrupted, the boot
program checks the other Kernel/Root File System. If that file system is not corrupted, it is
marked as the one to be activated, the value of RFSINUSE is set to the name of the Signed
Kernel/Root Software Package that was used to install that file system, and control is
transferred to it. If both Kernel/Root File Systems are corrupted, processing halts. The
software checks whether a Signed Application/Library Software Package has been
previously downloaded, and if one is found, the Application Software Package and/or the
Library Software Package is installed if either has a different file name than the currently
installed version, replacing the existing corresponding files in the Application File System.
The downloaded Signed Application/Library Software Package is then deleted. If a new
Signed Application/Library Software Package is not found, the integrity of the application
files is checked. If they are corrupted, files from the Backup Package are inst alled, replacing
the corrupted files in the Application File System. Any time an Application Software
Package or a Library Software Package is installed, the value of the persistent parameter
APPNAME_IN_USE is set to the file name of the Application Software Package that was
installed. If the application files are not corrupted, or after the Backup Package has been
installed, control is transferred to the application installed in the Application File System.
While loading the application files into volatile memory and as control is transferred to them,
the value of the APPNAME_IN_USE parameter is displayed on the bottom text line.

3. The internal clock/calendar is set to 0:00:00 Saturday, January 1, 2000 and started.

4. The deskphone activates the Ethernet line interface, the PC Ethernet jack, and dial pad
input to allow the invocation of procedures. The activation occurs as soon as possible after
power-up or a reset.

The deskphone displays the speed of the Ethernet interface in Mbps, that is,
10 or 100. The message No Ethernet displays until the software determines whether the
interface is 10 Mbps or100 Mbps.

Note:

Note: The Ethernet speed indicated is the LAN interface speed for both the deskphone

and any attached PC, assuming the administrator has not disabled the latter
interface by a PHY2STAT setting.

!

Important:

Important: Pressing the Program softkey at any time during startup invokes the Craft

Access entry procedure to allow manual settings, but only if the PROCSTAT
(local dialpad procedure status) system value is “0” providing full access to local
procedures or if PROCSTAT is “1” in certain instances requiring input. For
information, see Chapter 3:

Local Administrative Options. If Craft procedures are

invoked, the startup process terminates. The Program softkey also displays in
conjunction with a message describing a processing conflict, for example, when
an ARP response indicates a conflict in obtaining the IP Address.

Issue 1 December 2010 21

9600 Series IP Deskphone Installation

5. The deskphone sends a request to the DHCP server and invokes the DHCP process.
The following message displays:

DHCP: s secs

where s is the number of seconds that have elapsed since DHCP was invoked.

6. VLAN verification and tagging occur. The following message displays:

VLAN ID = n

where n is the VLAN ID being used.

7. Determination of the DHCP protocol (IPv4 is done, and the applicable parameters enabled.
The DHCP server provides IP Addresses for the following hardware:
The 9600 Series IP Deskphone
The HTTP/HTTPS server
The TN799C or D Control-LAN (C-LAN) circuit pack on the media server
The SIP Proxy server

8. Using the list of gateway IP Addresses provided by the DHCP server, the deskphone
performs a router check and verifies that the router is on the same subnet as the IP
Address. The deskphone cycles through the gateway IP Addresses with ARPs or pings until
it receives a response. When the router is located, received LLDP TLVs are processed.
Then the HTTP process starts.

Note:

Note: Any change in VLAN-related configuration parameters resulting from LLDP

triggers a deskphone reset.

9. The HTTP process starts with an HTTP GET command, which displays on the deskphone’ s
Status Line.

Note:

Note: Pressing the Program softkey at any time during startup invokes the Craf t Access

entry procedure to allow manual settings, but only if the PROCSTAT (local
dialpad procedure status) system value is “0” providing full access to local
procedures or if PROCSTAT is “1” in certain instances requiring input. For
information, see Chapter 3:

Local Administrative Options. If Craft procedures are

invoked, the startup process terminates. The Program softkey also displays in
conjunction with a message describing a processing conflict, for example, when
an ARP response indicates a conflict in obtaining the IP Address.

10. When connected, the deskphone looks for an upgrade script file.
1 1. The HTTP server sends and identifies an upgrade script, gets the settings file, the language

file, and any firmware updates.

22 SIP Deskphones Releas e 6. 1 In st al lat io n an d Ma in t en a nc e Gui de

Power-Up and Reset Operation (Dynamic Addressing Process)

Note:

Note: The GET message might have to be sent several times. Each time the GET

message is sent, the URI for the current HTTP request displeases SIG parameter
value determines the signaling protocol (H.323, SIP, both) and is used to
determine the proper upgrade file that is downloaded. If the SIG parameter was
manually set using the local administrative (Craft) SIG procedure, that value has
precedence over a SIG setting in a configuration file. A change in the SIG value
may require a reset so that a new or different upgrade file can be downloaded to
the phone.

12. When the deskphone determines that the application file received is valid, the following

message displays:

File Obtained;please wait...
s secs

where s is the number of elapsed seconds while non-volatile memory is erased.

13. While the application file is saved in flash memory, a progress bar shows the status:

14. The deskphone checks for LLDP messages and re-checks VLAN status and tagging. If

LLDP causes a change in the values of L2Q or L2QVLAN, a reset occurs to obt ain a new IP
Address.

15. If applicable, the deskphone attempts to download a valid device certificate using simple

certificate enrollment protocol (SCEP).

Simple Certificate Enrollment Protocol (SCEP)

1. When SCEP is initiated the deskphone attempts to contact an SCEP server via HTTP, using
the value of the configuration parameter MYCER TURL as the URI. The HTTP connection is
established to the transport address specified by the value of the configuration parameter
HTTPPROXY if HTTPPROXY is not null and if the configuration parameter
HTTPEXCEPTIONDOMAINS is null, or if HTTPEXCEPTIONDOMAINS is not null and the
rightmost part of the domain portion of MYCERTURL does not match one of the values of
HTTPEXCEPTIONDOMAINS. The values of the configuration parameters
MYCERTKEYLEN, MYCERTCN, MYCERTDN are used in the certificate request.

2. While the deskphone is attempting to contact the SCEP server and to obtain a certificate,
the Title Line displays:

SCEP: In progress...
s secs

where s is the number of seconds since SCEP was initiated/

Issue 1 December 2010 23