Avaya 1600 Series IP Deskphones_16_601438_4

8/18/2019 Avaya 1600 Series IP Deskphones_16_601438_4

1/90

Avaya 1600 Series IP DeskphonesInstallation and Maintenance Guide

Release 1.2.x

16-601438Issue 4

February 2010


2/90

© 2010 Avaya Inc.All Rights Reserved.

Notice

While reasonable efforts were made to ensure that the information in thisdocument was complete and accurate at the time of printing, Avaya Inc. canassume no liability for any errors. Changes and corrections to the informationin this document may be incorporated in future releases.

For full legal page information, please see the complete document, AvayaLegal Page for Hardware Documentation, Document number 03-600759.

To locate this document on our Web site, simply go tohttp://www.avaya.com/support and search for the document number inthe search box.

Documentation disclaimer

Avaya Inc. is not responsible for any modifications, additions, or deletions tothe original published version of this documentation unless such modifications,additions, or deletions were performed by Avaya. Customer and/or End Useragree to indemnify and hold harmless Avaya, Avaya's agents, servants andemployees against all claims, lawsuits, demands and judgments arising out of,or in connection with, subsequent modifications, additions or deletions to thisdocumentation to the extent made by the Customer or End User.

Link disclaimer

Avaya Inc. is not responsible for the contents or reliability of any linked Websites referenced elsewhere within this documentation, and Avaya does notnecessarily endorse the products, services, or information described or offeredwithin them. We cannot guarantee that these links will work all of the time andwe have no control over the availability of the linked pages.

Warranty

Avaya Inc. provides a limited warranty on this product. Refer to your sales

agreement to establish the terms of the limited warranty. In addition, Avaya’sstandard warranty language, as well as information regarding support for thisproduct, while under warranty, is available through the following Web site:

http://www.avaya.com/support

Copyright

Except where expressly stated otherwise, the Product is protected by copyrightand other laws respecting proprietary rights. Unauthorized reproduction,transfer, and or use can be a criminal, as well as a civil, offense under theapplicable law.

Avaya support

Avaya provides a telephone number for you to use to report problems or to askquestions about your product. The support telephone numberis 1-800-242-2121 in the United States. For additional support telephonenumbers, see the Avaya Web site:


Software License

USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER’S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERALLICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE AThttp://support.avaya.com/LicenseInfo/ (“GENERAL LICENSE TERMS”). IFYOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUSTRETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN(10) DAYS OF DELIVERY FOR A REFUND OR CREDIT.

Avaya grants End User a license within the scope of the license typesdescribed below. The applicable number of licenses and units of capacity forwhich the license is granted will be one (1), unless a different number oflicenses or units of capacity is specified in the Documentation or othermaterials available to End User. “Designated Processor” means a singlestand-alone computing device. “Server” means a Designated Processor thathosts a software application to be accessed by multiple users. “Software”means the computer programs in object code, originally licensed by Avaya andultimately utilized by End User, whether as stand-alone Products orpre-installed on Hardware. “Hardware” means the standard hardwareProducts, originally sold by Avaya and ultimately utilized by End User.

License Type(s):Designated System(s) License (DS). End User may install and use each copyof the Software on only one Designated Processor, unless a different numberof Designated Processors is indicated in the Documentation or other materialsavailable to End User. Avaya may require the Designated Processor(s) to beidentified by type, serial number, feature key, location or other specificdesignation, or to be provided by End User to Avaya through electronic meansestablished by Avaya specifically for this purpose.

Third-party Components

Certain software programs or portions thereof included in the Product maycontain software distributed under third party agreements (“Third PartyComponents”), which may contain terms that expand or limit rights to usecertain portions of the Product (“Third Party Terms”). Information identifyingThird Party Components and the Third Party Terms that apply to them isavailable on Avaya’s Web site at:

http://support.avaya.com/ThirdPartyLicense/

Interference

Using a cell, mobile, or GSM telephone, or a two-way radio in close proximity toan Avaya IP Telephone might cause interference.

http://www.avaya.com/supporthttp://www.avaya.com/supporthttp://www.avaya.com/support/http://www.support.avaya.com/LicenseInfo/http://support.avaya.com/ThirdPartyLicense/http://www.avaya.com/supporthttp://www.avaya.com/support/http://www.support.avaya.com/LicenseInfo/http://www.avaya.com/support


3/90

Issue 4 February 2010 3

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

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

Intended Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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

Other Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

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

Chapter 2: 1600 Series IP Telephone Installation . . . . . . . . . . . . . 11

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

IP Telephone Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

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

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

Assembling the 1600 Series IP Telephone . . . . . . . . . . . . . . . . . . . . . . 15

Powering the 1600 Series IP Telephone . . . . . . . . . . . . . . . . . . . . . 15

Dynamic Addressing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Unnamed Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Printing Button Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 3: Local Administrative Options . . . . . . . . . . . . . . . . . 29

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Entering Data for Administrative Options . . . . . . . . . . . . . . . . . . . . . . 30

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

Set the 802.1X Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Change the DOT1X Mode Value . . . . . . . . . . . . . . . . . . . . . . . . . 32

Change the DOT1XSTAT Mode Value . . . . . . . . . . . . . . . . . . . . . . 33

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

Static Addressing Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Disable/Enable Automatic Gain Control . . . . . . . . . . . . . . . . . . . . . . . 38

Manually Setting the DHCP Client Hardware Address . . . . . . . . . . . . . . . 40

Clear Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Disable/Enable Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Group Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Interface Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Disable/Enable Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Logoff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Reset System Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Restart the Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Contents


4/90

Contents

4 Avaya 1600 Series IP Deskphones Installation and Maintenance Guide

Signaling Protocol Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Site-Specific Option Number Setting. . . . . . . . . . . . . . . . . . . . . . . . . 51

Self-Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 4: Maintaining 1600 Series IP Telephones . . . . . . . . . . . . 53

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Downloading Software Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Download File Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Download Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Contents of the Settings File . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Downloading Language Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Downloading Font Files for 1600 Series International Telephones . . . . . . 56

The GROUP System Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 5: Troubleshooting Guidelines . . . . . . . . . . . . . . . . . . 59

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

DTMF Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Power Interruption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

The View Administrative Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Installation Error and Status Messages . . . . . . . . . . . . . . . . . . . . . . . 63

Operational Errors and Status Messages . . . . . . . . . . . . . . . . . . . . . . 67

Appendix A: Restart Scenarios. . . . . . . . . . . . . . . . . . . . . . . 73

Scenarios for the Restart Process . . . . . . . . . . . . . . . . . . . . . . . . . . 73Restart the Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Boot File Needs to be Upgraded . . . . . . . . . . . . . . . . . . . . . . . . . 75

Latest Boot File Loaded/No Application File orApplication File Needs to be Upgraded . . . . . . . . . . . . . . . . . . . . . 78

Latest Boot File and System-SpecificApplication File Already Loaded . . . . . . . . . . . . . . . . . . . . . . . . 80

Appendix B: Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . 83

Terms Used in This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Appendix C: Related Documentation . . . . . . . . . . . . . . . . . . . 85

IETF Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

ITU Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

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


5/90

Contents


Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89


6/90

Contents



7/90


Chapter 1: Introduction

About This Guide

This guide describes how to install and maintain the Avaya 1600 Series IP Deskphone product

line and troubleshoot telephone problems.

The 1600 Series IP Deskphone product line supports only the H.323 signaling protocol and

work with Avaya Aura™ Communication Manager Release 3.0 or later call servers and Avaya

Aura Communication Manager Branch Release 1.1 or later call servers. (Avaya Aura

Communication Manager was formerly known as Avaya Distributed Office.)

Note:

Note: Unless otherwise indicated, generic references in this document to a server can

apply to DEFINITY® servers, MultiVantage servers, Avaya Aura CommunicationManager media servers, or Avaya Aura Communication Manager Branch

systems.

Note:

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

Intended Audience

This document is intended for personnel who install and administer the 1600 Series IP

Deskphones.

! CAUTION:

CAUTION: Avaya does not support 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 telephones might not

be able to operate correctly.


8/90

Introduction


Document Organization

The guide contains the following sections:

Other Documentation

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

technical and end user documentation.

The following documents are available for the 1600 Series IP Telephones:

● Avaya 1600 Series IP Deskphones Installation and Maintenance Guide, Document

Number 16-601438.

● Avaya one-X™ Deskphone Value Edition 1600 Series IP Telephone Pre-Installation

Checklist , Document Number 16-601439.

● Avaya one-X™ Deskphone Value Edition 1600 Series IP Telephone Safety Instructions,

Document Number 16-601440.

Chapter 1: Introduction Provides an overview of this guide.

Chapter 2: 1600 Series IPTelephone Installation

Describes the equipment and resources required to properlyinstall and operate the 1600 Series IP Deskphones. Providesinstructions on installing the telephones out of the box.

Chapter 3: Local Administrative Options

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

Chapter 4: Maintaining1600 Series IP Telephones

Describes maintenance actions like downloading telephonesoftware from the Avaya support Web site and customizingsystem values.

Chapter 5: TroubleshootingGuidelines

Describes error conditions and messages that might occurduring the installation of the 1600 Series IP Deskphones.

Appendix A: RestartScenarios

Explains the different scenarios possible for the sequence of therestart process.

Appendix B: Glossary ofTerms

Provides a glossary of terms used in this document or which aregenerally applicable to 1600 Series IP Deskphones.

Appendix C: RelatedDocumentation

Provides references to external documents that relate totelephony in general, and can provide additional informationabout specific aspects of the telephones.

http://www.avaya.com/supporthttp://www.avaya.com/support


9/90

Customer Support


● Avaya one-X™ Deskphone Value Edition 1600 Series IP Telephones BM32 Button

Module Installation and Safety Instructions, Document Number 16-601441.

● Avaya one-X™ Deskphone Value Edition 9600 Series IP Telephone Application

Programmer Interface (API) Guide, Document Number 16-601442.

● Avaya 1600 Series IP Deskphones Telephone Administrator Guide,


● Avaya 1603/1603SW/1603-I/1603SW-I IP Deskphone User Guide,


● Avaya 1608/1608-I IP Deskphone User Guide, Document Number 16-601446.

● Avaya 1616/1616-I IP Deskphone User Guide, Document Number 16-601448.

● Avaya one-X™ Deskphone Value Edition 1600 Series IP Telephones BM32 Button

Module User Guide, Document Number 16-601450

● Avaya one-X™ Deskphone Value Edition 1603 IP Telephone Wall Mount Instructions,


● Avaya one-X™ Deskphone Value Edition 1608/1616 IP Telephone Wall MountInstructions, Document Number 16-601933.

● Avaya 1603/1603SW/1603-I/1603SW-I IP Deskphone Quick Reference,


● Avaya 1608/1608-I IP Deskphone Quick Reference, Document Number 16-601447.

● Avaya 1616/1616-I IP Deskphone Quick Reference, Document Number 16-601449.

See Appendix C: Related Documentation for a list of non-Avaya documents, such as those

published by the Internet Engineering Task Force (IETF) and International Telecommunication

Union (ITU).

Customer Support

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

Avaya representative or Avaya reseller.

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




10/90

Introduction



11/90


Chapter 2: 1600 Series IP Telephone Installation

Introduction

The 1600 Series IP Telephone product line uses Internet Protocol (IP) technology with Ethernet

interfaces. The IP telephones supplement the existing Avaya IP Solutions platform.

The 1600 Series IP Telephones support DHCP and HTTP/HTTPS over IPv4/UDP which

enhance the administration and servicing of the telephones. These telephones use DHCP to

obtain dynamic IP addresses, HTTP or HTTPS to download customized settings for the

telephones, and HTTP only to download the new software version.

The 1603SW, 1603SW-I, 1608, 1608-I, 1616, and 1616-I IP Telephones provide the ability to

have one IP connection on the desktop for both a telephone set and a PC using an Ethernet

switch. The 1603 and 1603-I IP Telephone do not provide a secondary Ethernet connection fora PC.

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 SELV 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.


12/90

1600 Series IP Telephone Installation


IP Telephone Models

There are seven telephone set models and a button module currently defined in the 1600 Series

IP Telephone family:

The 1603SW, 1603SW-I, 1608, 1608-I, 1616, and 1616-I telephones have an internal Ethernet

switch that allows the telephone and a PC to share the same LAN connection, if appropriate.

Thus, these 1600 models do not need, or work with, the 30A switched hub interface.

This document describes the installation of these telephones and post-installation maintenance

issues. For details about using the features provided by the telephones, see the user

documentation for each telephone. For information about desk or wall mounting any of the 1600

Series IP Telephones, see the instructions boxed with the telephone. Wall or desk mount

instructions are also available on the Avaya support Web site http://www.avaya.com/support.

Software

As shipped from the factory, the 1600 Series IP Telephone may not contain the most up-to-date

software for registration and operation. When the telephone is first plugged in, a software

download from an HTTP server might be initiated. The software download gives the telephone

upgraded functionality.

For subsequent downloads of software upgrades, the Avaya Media Server provides the

capability for a remote restart of the IP telephone. As a consequence of restarting, the

telephone automatically restarts reboot procedures which result in a download if new software

Model Call Appearance/Line Appearance/Feature Buttons

Display Size

● 1603 IP Telephone 3 2 row by 16 column display

● 1603SW IP Telephone 3 2 row by 16 column display

● 1603-I IP Telephone 3 2 row by 16 column display

● 1603SW-I IP Telephone 3 2 row by 16 column display





● BM32 Button Module 32 No display



13/90

Pre-Installation Checklist


is available. Chapter 4: Maintaining 1600 Series IP Telephones covers downloading new

software releases.

Pre-Installation Checklist

Before plugging in the 1600 Series IP Telephone, verify that all the following requirements are

met. Failure to do so prevents the telephone from working properly and can have a negative

impact on the network. Print copies of this checklist for each server and IP telephone.

Verify These Network Requirements

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

2. Avaya Aura Communication Manager Release 3.0 or later software supports the1600 Series IP Telephones, aliased as 4600 Series IP Telephones. Specifically, all

of the 1603 models should be aliased as a 4610, all of the 1608 models should bealiased as a 4610, and all of the 1616 models should be aliased as a 4620.

Avaya Aura Communication Manager Release 5.2 or later software provides nativesupport for the 1600 Series IP Telephones (that is, you do not have to alias thetelephones).

Avaya Aura Communication Manager Branch provides native support for the 1600Series IP Telephones.

3. For Avaya Aura Communication Manager, the following circuit packs are installedon the switch:

● TN2602 or TN2302 IP Media Processor circuit pack. Sites with a TN2302 IPMedia Processor circuit pack are strongly encouraged to install a TN2602circuit pack to benefit from the increased capacity.

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

! Important:

Important: IP telephone firmware Release 1.0 or greater requires TN799C V3

or greater CLAN circuit pack(s). For more information, see the

Avaya Aura Communication Manager Software and Firmware

Compatibility Matrix on the Avaya support Web site

http://www.avaya.com/support.

4. For Avaya Aura Communication Manager, the Avaya Media Server is configuredcorrectly, as described in the Avaya 1600 Series IP Deskphones AdministratorGuide and Avaya Aura Communication Manager documentation. Both documentsare available athttp://www.avaya.com/support.

For Avaya Aura Communication Branch, see the Avaya Aura CommunicationManager Branch Device Manager online help.

5. The DHCP server and application are administered as described in the Avaya 1600Series IP Deskphones Administrator Guide.

http://www.avaya.com/supporthttp://www.avaya.com/supporthttp://www.avaya.com/supporthttp://www.avaya.com/support


14/90



6. The HTTP server and application are administered as described in the Avaya 1600Series IP Deskphones Administrator Guide.

7. The upgrade script and application files from the Avaya Support Web site,http://www.avaya.com/support, are loaded correctly on the HTTP/HTTPS server.

8. If applicable, the DNS server is administered as described in the Avaya 1600 SeriesIP Deskphones Administrator Guide.

Notes:

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

- See the Avaya 1600 Series IP Deskphones Administrator Guide for more informationabout:

Note:

● administering other network equipment,● administering applications like firewalls, and● information about topics like port utilization.

Requirements to Verify for Each IP Telephone

9. You have an extension number and an Avaya Aura Communication Manager or Avaya Aura Communication Manager Branch security code (password) for eachapplicable IP telephone. If your call server supports unnamed registration, and thetelephone settings file allows unnamed registration, you do not need to provide anextension or password for the telephone. However, if you do not provide anextension or password, the telephone will have very limited telephone functionality.(For information, see Unnamed Registration on page 27.)

10. A Category 5e LAN jack is available at each telephone site.

11. Electrical power is provided to each telephone by a Telephone Power Module (DC

power jack) (must be ordered separately). For Power over Ethernet inputconnection, use only with UL Listed I.T.E. equipment with Power over Ethernetoutput. If the LAN will supply IEEE-standard power to the telephone, no powermodule is required for 1608, 1608-I, 1616, and 1616-I telephones. For the 1603 and

1603-I telephones, you will need to use the Power over Ethernet adapter if the LANwill supply IEEE-standard power to the telephone. (See Connection Jacks withPower over Ethernet on a 1603/1603-I IP Telephone on page 17.)

12. 1 Category 5e modular line cord is available for the connection between the IPtelephone and the PC, if applicable.

13. Verify that the 1600 Series IP Telephone package includes the followingcomponents:

● 1 telephone set with stand.● 1 handset capable of transmitting and receiving 7KHz audio.● 1 H4DU 9-foot long (when extended) 4-conductor coiled handset cord,

plugged into the telephone and the handset.● 1 8.5"x11" sheet of labels● 1600 Series IP Telephone Safety Instructions.●

1600 Series IP Telephone Quick Reference.You will need 1 Category 5 modular line cord for the connection from the IPtelephone to the Ethernet wall jack.

Verify These Network Requirements (continued)



15/90

Assembling the 1600 Series IP Telephone


Note:

Note: For sites using headsets, the 1608 IP Telephone and the 1616 IP Telephone

support only the HIS headset cords. The 1603 IP Telephone does not support

headsets.


! CAUTION:

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

located on the back of the telephone housing and are flanked by icons to

represent their correct use.

Powering the 1600 Series IP Telephone

All 1600 Series IP Telephones can be locally powered with a Telephone Power Module (DC

power jack), available separately. The DC input rating is 5 VDC, 2A. In addition, the telephones

support IEEE 802.3af-standard LAN-based power. (To use LAN-based power with a 1603

telephone, you must use a Power over Ethernet adapter.) Before installing a 1600 Series IP

Telephone, verify with the LAN administrator whether the LAN supports IEEE 802.3af, and if so,

whether the telephone should be powered locally or by means of the LAN.

Note:

Note: The last step in assembling the 1600 Series IP Telephone 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). Do not use the 1151 power adapter with these telephones.

Note:

Note: For Brazil ian user when using the 5V pow er adapter :

For the user’s safety and to avoid electric shock, this equipment must be

connected to a grounded (three pin) electrical network power outlet according to

Standard NBR ABNT 5410.

Este equipamento deve ser conectado obrigatoriamente em tomada de rede de

energia eletrica que possua aterramento (tres pinos), conforme a Norma NBR

ABNT 5410, visando a seguranca dos usuarios contra choques eletricos.

! CAUTION:

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

outage in part of your network.


16/90



Figure 1, Figure 2, Figure 3, Figure 4, Figure 5, Figure 6, and Figure 7 provide illustrations to

connect cords to jacks on 1600 Series IP Telephones. Use the illustrations and associated

procedures as appropriate for telephone assembly.

Telephone Model: See:

1603 Figure 1 and Figure 2

1603-I Figure 1 and Figure 2

1603SW/1603SW-I Figure 3






17/90



Figure 1: Connection Jacks with Power over Ethernet on a 1603/1603-I IP Telephone


18/90


19/90



Figure 3: Connection Jacks on a 1603SW/1603SW-I IP Telephone


20/90





21/90



Figure 5: Connection Jacks with Local Power on a 1608/1608-I IP Telephone


22/90




Note:

The BM32 Button Module shown in the lower left corner can also be

attached to the telephone with the connector packaged with the module.


23/90



Figure 7: Connection Jacks with Local Power on a 1616/1616-I IP Telephone

Note:

The BM32 Button Module shown in the lower left corner can also be

attached to the telephone with the connector packaged with the module.


24/90



1. Plug one end of the first Category 5 modular line cord into the Ethernet jack of the PC and

the other end into the secondary Ethernet jack on the 1600 Series IP Telephone,

if appropriate.

2. Plug one end of the second Category 5 modular line cord into the Ethernet jack on the 1600

Series IP Telephone. Plug the other end of this cord into the Ethernet wall jack. If the

telephone is to be IEEE-powered, you are finished. Do not proceed to Step 3.

3. If the telephone is to be powered locally, plug the power cord into the 1600 Series IPTelephone and the power cord plug into the wall socket.

Dynamic Addressing Process

Note:

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

telephone and the Avaya Aura Communication Manager security code(password) for that extension, unless the telephone will use unnamed

registration. For more information, see Unnamed Registration on page 27.

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

The following description of the process of installing the IP telephones assumes that the

process is executed successfully. Only an initial out of the box installation is described. For

errors that might be encountered during the process and the messages displayed, see

Chapter 5: Troubleshooting Guidelines.

When you plug the IP telephone 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 telephone 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 telephones

are being installed at once, and similar factors.

Do not unplug the power cord during the download process.

1. The telephone 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 telephone 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 or 100 Mbps.


25/90


26/90


27/90

Unnamed Registration


11. Enter a new extension and press OK. To register the telephone without the extension orpassword (unnamed), press only OK or make no entry and wait 60 seconds.

Note:

Note: Unnamed registration is the capability to register a telephone with the call server

without entry of an extension or password. The UNNAMEDSTAT parameter must

be set to enable unnamed registration. Telephones registered unnamed havelimited functionality. For more information, see Unnamed Registration.

All IP telephones display the following prompt for a password:

12. Enter the password and press OK. To register the telephone without the extension orpassword (unnamed), press OK or make no entry and wait 60 seconds.

13. The extension is visible as you enter it but the password displays as asterisks. The system

determines whether the extension is in use.

14. Successful completion of this process produces a dial tone when the Speaker button is

pressed or the handset is lifted.

The IP telephone was installed successfully.

Unnamed Registration

Unnamed registration is a capability an IP telephone can have to register with a call server, and

receive limited service, without requiring an extension and password entry. Typical

environments where this functionality is useful include:

● “Hot-desking” environments where there is a period of time between one user logging out

and another user logging in on the same telephone.

● Using the Avaya Softphone application in “road warrior” mode, which allows a traveller to

invoke the telephony features and functionality by taking over the office telephone

extension. This takeover unregisters the office telephone.

In both examples, the user unregisters the telephone by logging off or by taking the office

telephone extension over to another telephone. Without unnamed registration, the telephone inthe first example will just wait for an extension and password entry and the telephone in the

second example will continue attempting to register at regular intervals. The downside of a

telephone being unregistered is that no one can use the telephone, for example, to report a

building emergency like a fire.

Login

Enter Password

Enter Password and press Enter or OK


28/90


29/90


Chapter 3: Local Administrative Options

Introduction

After you have successfully installed an IP telephone, you might be instructed to administer one

of the options described in this chapter.

Note:

Note: You can modify the settings file to set parameters for IP telephones that

download their upgrade script and application files from the same HTTP server.

See Chapter 4: Maintaining 1600 Series IP Telephones and “1600 Series IP

Telephone Scripts and Application Files” in Chapter 4 of the Avaya 1600 Series

IP Deskphones Administrator Guide.

! CAUTION:

CAUTION: Perform these procedures only if instructed to do so by the system or LANadministrator.

Static administration of these options causes upgrades to work differently than if

they are administered dynamically. Values assigned to options in static

administration are not changed by upgrade scripts. These values remain stored

in the telephone until either:

- a new boot file is downloaded, or

- the IP telephone is reset, as indicated in Reset System Values on page 48.

Use these option-setting procedures only with static addressing and, as always, onlyif instructed by the system or LAN administrator. Do not use these option-settingprocedures if you are using DHCP. DHCP is the Dynamic Addressing Process, as

indicated in Dynamic Addressing Process on page 24.


30/90


31/90

About Local Administrative Procedures


Note:

Note: Unless otherwise prohibited using administration, the user can view but not

change most of the parameters associated with Local Administrative Procedures.

For more information about this option, see the applicable user guide(s).

Local Programming Option Code See

Set 802.1X operational mode 8 0 2 1 X (8 0 2 1 9) Set the 802.1X OperationalMode on page 32.

Static addressing A D D R (2 3 3 7) Static Addressing Installation on

page 35. Automatic Gain Control A G C (2 4 2) Disable/Enable Automatic Gain

Control on page 38.

DHCP chaddr field value C H A D D R (2 4 2 3 3 7) Manually Setting the DHCPClient Hardware Address onpage 40.

Clear values to factory defaults C L E A R (2 5 3 2 7) Clear Procedure on page 41.

Enable/disable Debug Mode D E B U G (3 3 2 8 4) Disable/Enable Debug Mode onpage 42.

Group Identifier G R O U P (4 7 6 8 7) Group Identifier on page 43.

Interface Control I N T (4 6 8) Interface Control on page 44.

Event Logging L O G (5 6 4) Disable/Enable EventLogging on page 46.

Reset the telephone R E S E T (7 3 7 3 8) Reset System Values onpage 48.

Restart the telephone R E S E T (7 3 7 3 8) Restart the Telephone onpage 49.

Signaling protocol identifier(not applicable to Release 1.0)

S I G (7 4 4) Signaling Protocol Identifier onpage 50.

Site-Specific Option number S S O N (7 7 6 6) Site-Specific Option Number

Setting on page 51.

Test the telephone T E S T (8 3 7 8) Self-Test Procedure on page 52.

View current parameter valuesand file names

V I E W (8 4 3 9) The View AdministrativeOption on page 60.


32/90


33/90

Set the 802.1X Operational Mode


changes the value to 1 (p-t w/Logoff). ("p-t w/Logoff" stands for "pass-thru with Logoff".) If

the current value is Supplicant mode (2), pressing * changes the value to 0 (pass-thru).

If a value different from the current 802.1X value is entered, the following text displays

left-justified at the top of the display:

2. Press the * button to terminate the procedure, or the # button to save the new value. If youpress the # button, the telephone displays the following text:

The telephone saves the new value.

Change the DOT1XSTAT Mode ValueUse the following procedure to change the DOT1XSTAT mode value.

1. Press #.

The following text displays:

where the sett ing is the current value of the system value DOT1XSTAT (802.1X Supplicant

Mode), defined as:

● Disabled if setting = 0

● Unicast only if setting = 1

● Unicast/multicast if setting = 2

2. To change the mode value, press *.

Depending on the current value, the next sequential valid mode value is selected and

displayed as the setting. For example, if the current value is Disabled (0), pressing * changes the value to 1 (Unicast only). If the current value is Unicast/multicast mode (2),

pressing * changes the value to 0 (Disabled).

If a value different from the current 802.1X value is entered, the following text displays


Save new value?*=no #=yes

New value being saved

Supplicant=sett ing *=change #=OK



34/90

Local Administrative Options




Pre-Installation Checklist for Static Addressing

Before performing static addressing, verify that all the requirements listed in the Verify These

Network Requirements section of the Pre-Installation Checklist are met. You do not have to

consider item 4. on page 13, as it refers to the DHCP server. In addition, you must have the

values for the following parameters. Failure to do so can cause data entry errors that prevent

the telephone from working. Such errors can also have a negative impact on your network. Print

copies of this checklist for each subnet.


1. The IP address of the media server.

2. The transport layer port number of the address of the Management Complex(media server/gatekeeper). Although this can be a value between 0 and 65535,the default value is 1719. Do not change this value unless it conflicts with anexisting port assignment.

3. The IP address of the gateway/router.

4. The IP netmask.

5. The IP address of the HTTP server.


35/90


36/90



3. Enter the Call server IP address followed by the # button.

The telephone displays:

where nnn.nnn.nnn.nnn is the current system value of the gateway/router IP address.

4. Enter the Gateway router IP address followed by the # button.


where nnn.nnn.nnn.nnn is the current system value of the IP netmask.

5. Enter the IP netmask followed by the # button.


where nnn.nnn.nnn.nnn is the current system value of the HTTP/HTTPS server IP

address.

6. Enter the File server followed by the # button.

The telephone displays one of the following texts, depending on the current setting of the

system parameter NVL2Q (802.1Q):

7. Press * to change 802.1Q to the next sequential value. For example, if the current value is 0(auto) pressing * changes it to 1 (on) and if the current value is 2 (off), pressing * changes it

to 0 (auto).

The display is updated to show the current status of 802.1Q.

Router=nnn.nnn.nnn.nnn New=_

Mask=nnn.nnn.nnn.nnn New=_

FileSv=nnn.nnn.nnn.nnn New=_

If NVL2Q is 0: 802.1Q=auto*=change #=OK

If NVL2Q is 1: 802.1Q=on*=change #=OK

If NVL2Q is 2: 802.1Q=off*=change #=OK


37/90

Static Addressing Installation


8. Press the # button to continue the procedure without changing the displayed status of802.1Q

The telephone displays the following text:

where dddd is the current system value of the 802.1 VLAN ID.

9. Enter a valid value between 0 and 4094 for the new value of the 802.1 VLAN ID.

The telephone displays the following message:

where ddd is the number of seconds to wait for the DHCPOFFER on a non-zero VLAN.

10. Enter a valid value between 0 and 999 for the new value of the DHCPOFFER wait period.


11. Press the # button to save the new values you entered.


Once the new values are stored, the telephone is reset.

If a new boot program is downloaded from the HTTP server after you enter static

addressing information, you must reenter your static addressing information.

VLAN ID=dddd New=_

VLAN test=ddd New=_

Save new values?*=no #=yes

New valuesbeing saved


38/90


39/90

Disable/Enable Automatic Gain Control


4. To change the AGC Headset value from On to Off, press 0. To change the AGC Headsetvalue from Off to On, press 1.

One of the following displays, based on the current value of the system value AGCSPKR:

5. To change the AGC Speaker value from On to Off, press 0. To change the AGC Speakervalue from Off to On, press 1.

If a value different from the current AGCHAND value and/or the current AGCHEAD value

and/or the current AGCSPKR value is entered, the following text displays left-justified at the

top of the display:

6. Press the * button to terminate the procedure, or the # button to save the new value(s). Ifyou press the # button, the telephone displays the following text:

The telephone saves the new value(s).

If AGCSPKR = 1: Speaker AGC=on 0=off #=OK

If AGCSPKR = 0: Speaker AGC=off 1=on #=OK

Save new value?

*=no #=yes



40/90



Manually Setting the DHCP Client Hardware Address

Use this procedure to manually set or change the Client Hardware Address, if you use static

addressing rather than DHCP.

1. While the telephone is on-hook and idle, press the following sequence of keys on the

telephone’s faceplate:

Mute 2 4 2 3 3 7 # (Mute C H A D D R #)

Note:

Note: Press the Mute button momentarily. Do not press this button while pressing otherkeys/buttons.

The telephone displays the following text left-justified at the top of the display:

where ddd is the value of NVCHADDR, the system variable for the DHCP Client Hardware

Address.

2. To change the Client Hardware Address value, enter a valid client hardware address. This

value is usually the MAC address, which DHCP then converts to an integer preceded by

zeroes.

For all IP telephones, if a value different from the current value of NVCHADDR is entered,

the following text displays left-justified at the top of the display:



chaddr=ddd New=




41/90

Clear Procedure


Clear Procedure

Sometimes, you might want to remove all administered values, user-specified data, and option

settings. Essentially, you want to return a telephone to its initial “clean slate” or out of the box

condition. This is usually done when passing a telephone to a new, dedicated user when theuser’s L O G O F F option is not sufficient. For example, a new user is assigned the sameextension, but requires different permissions than the previous user.

The C L E A R option erases all administered data—static programming, file server and callserver programming, and user settings including Contact button labels and locally programmed

Feature button labels, and restores all such data to default values. The C L E A R option doesnot affect the software load itself. If you have upgraded the telephone, the telephone retains the

latest software. Once you have cleared a telephone, you can administer it normally.

! CAUTION:

CAUTION: This procedure erases all administered data, without any possibility of recovering

the data.Use the following procedure to clear the telephone of its administrative, user-assigned and

options values.


faceplate of the telephone:

Mute 2 5 3 2 7 # (Mute C L E A R #)

Note:


The following text displays left-justified at the top of the display:

2. If you do not want to clear all values, press * (no) to terminate the procedure and retain thecurrent values.

A screen displays the following prompt on the top line:

Clear all values?*=no #=yes

Are you sure?*=no #=yes


42/90



3. Press the * button to terminate the procedure without clearing the values. Press the # buttonto clear all values to their initial default values.

A confirmation tone sounds and the following text displays left-justified at the top of the

display:

The telephone is cleared to its “out of the box” state.

Disable/Enable Debug Mode

Use the following procedure to turn the debug mode for the button module serial port on or off.



Mute 3 3 2 8 4 # (Mute D E B U G #)

Note:


2. After entry of the command sequence, the following displays, based on the current value of

the system value NVDEBUG:

If a value different from the current NVDEBUG value is entered, the following text displays




Clearing values.

If NVDEBUG = 1: Debug mode=on 0=off #=OK

If NVDEBUG = 0: Debug mode=o ff 1=on #=OK




43/90

Group Identifier


Group Identifier

Use the following procedure to set or change the Group Identifier.

Note:Note: Perform this procedure only if the LAN Administrator instructs you to do so.

For more information about groups, see The GROUP System Value on page 57.

While the telephone is on-hook and idle, press the following sequence of keys on the faceplate

of the telephone:

Mute 4 7 6 8 7 (Mute G R O U P)

Note:



where ddd is the Group value.

1. Enter a valid Group value (0-999).

If a value different from the current Group value is entered, the following text displays


2. Press the * button to terminate the procedure, or the # button to save the new value.

If you press the # button, the following text displays:

The new value is saved and the user interface is restored to its previous state.

Group=ddd New=_


New valuebeing saved


44/90



Interface Control

Use the following procedure to set or change the interface control value.



Mute 4 6 8 # (Mute I N T #)

Note:


2. After entry of the command sequence, telephones with an internal Ethernet switch display

the following text, depending on the current interface control value:

where status is the value of PHY1STAT, defined as:

● Status is auto when PHY1STAT = 1

● Status is 10Mbps HDX when PHY1STAT = 2

● Status is 10Mbps FDX when PHY1STAT = 3



3. To change the PHY1 value, press *.

Depending on the current value, the next sequential valid PHY1 value is selected anddisplayed as the status. For example, if the current value is 10Mbps HDX (2), pressing * changes the value to 3 (10Mbps FDX).

PHY1=status *=change #=OK


45/90

Interface Control


4. Press the * button to terminate the procedure, or the # button to save the new value. If youpress the # button, the following text displays:

where status is the value of PHY2STAT, defined as:

● Status is disabled when PHY2STAT = 0

● Status is auto when PHY2STAT = 1





5. To change the PHY2 value, press *.

Depending on the current value, the next sequential valid PHY2 value is selected anddisplayed as the status. For example, if the current value is 10Mbps HDX (2), pressing * changes the value to 3 (10Mbps FDX).


6. Press the * button to terminate the procedure, or the # button to save the new values.If you press the # button, the following text displays.

The new values are saved and a restart occurs automatically. The user interface is restored

to its previous state.

PHY2=status *=change #=OK


New valuebeing saved


46/90



Disable/Enable Event Logging

Use the following procedure to enable or disable logging of system events.



Mute 5 6 4 # (Mute L O G #)

Note:


2. After entry of the command sequence, the telephone displays the following text, depending

on the current value of the system parameter NVLOGSTAT:

where status is the type of logging indicated by the NVLOGSTAT value, defined as:

● Status is disabled when NVLOGSTAT = 0

● Status is emergencies when NVLOGSTAT = 1

● Status is alerts when NVLOGSTAT = 2

● Status is critical when NVLOGSTAT = 3

● Status is errors when NVLOGSTAT = 4

● Status is warnings when NVLOGSTAT = 5

● Status is notices when NVLOGSTAT = 6

● Status is information when NVLOGSTAT = 7

● Status is debug when NVLOGSTAT = 8

3. To change the logging status, press *.

Depending on the current value, the next sequential valid NVLOGSTAT value is selected

and displayed as the status. For example, if the current value is alerts (2), pressing * changes the value to 3 (critical). If the current value is debug (8), pressing * changes thevalue to 0 (disabled).

If a value different from the current NVLOGSTAT value is entered, the following text displays


Log=status *=change #=OK



47/90

Logoff




Logoff

Use the following procedure to log off a telephone.

! CAUTION:

CAUTION: Once a telephone is logged off, a password and extension might be needed to

log back on.



Mute 5 6 4 6 3 3 # (Mute L O G O F F #)

Note:


2. After entry of the command sequence, the telephone unregisters from the call server. The

telephone display (and button module display, if applicable) clears, then displays the

following prompt for subsequent login:


Enter Extension

EXT= #=OK


48/90



Reset System Values

Use the following procedure to reset all system values and system initialization values except

AUTH and NVAUTH to the default values. It also resets the 802.1X identity and password to the

default values.

! CAUTION:

CAUTION: This procedure erases all static information except the extension number and

password, without any possibility of recovering the data.



Mute 7 3 7 3 8 # (Mute R E S E T #)

Note:

Note: Press the Mute button momentarily. Do not press this button while pressing other

keys/buttons.

The IP telephones display the following text left-justified at the top of the display:

! CAUTION:

CAUTION: As soon as you press the # button, all static information except the extensionnumber and password will be erased, without any possibility of recovering the

data.

2. If you do not want to reset the system values, press * (no) and proceed to Step 4.

The following prompt displays on the top line:

3. Press the * button to continue without resetting the values and proceed to Step 4. Or, pressthe # button to reset values to their defaults.

All telephones display the following text left-justified at the top of the display while the

system values are reset to defaults:

The telephone resets from the beginning of registration, which takes a few minutes.

Reset values?*=no #=yes

Are you sure?*=no #=yes

Resettingvalues.


49/90

Restart the Telephone


4. If you do not reset the telephone, the telephone displays the following prompt:

5. Press the * key to terminate the procedure without restarting the telephone. Otherwise,

press # and perform the following Restart procedure.

Restart the Telephone

Use the following procedure to restart the telephone.



Mute 7 3 7 3 8 # (Mute R E S E T #)

Note:


The IP telephones display the following text left-justified at the top of the display:

2. Press the # button to reset values to their defaults, or * to continue a restart without resettingthe values to their defaults.

The telephones display the following text left-justified at the top of the display while the

system values are reset to defaults:

Once you press the * button to restart without resetting the values, the following prompt

displays on all IP telephones:

3. Press the * key to terminate the procedure without restarting the telephone.

Press the # key to restart the telephone.

The remainder of the procedure depends on the status of the boot and application files.

See Appendix A: Restart Scenarios.

Restart phone?*=no #=yes

Reset values?*=no #=yes

Resettingvalues.



50/90



Signaling Protocol Identifier

Note:

Note: This procedure is provided for future use only, and is not currently applicable to

Release 1.0.

Use the following procedure to set or change the Signaling Protocol Identifier. A valid SIG

Protocol Identifier is either 0 (default), 1 (H.323), or 2 (SIP).

Note:

Note: Perform this procedure only if the LAN Administrator instructs you to do so.



Mute 7 4 4 (Mute S I G)

Note:


The telephone displays the following text left-justified at the top of the display:

where pro toco l is the telephone’s signaling protocol (H.323, SIP, or default) corresponding

to the numeric identifier (1, 2, or 0).

2. To change the SIG value, press *.

Depending on the current value, the next sequential valid SIG value is selected and

displayed as the protocol. I.e., if the current value is SIP (2), pressing * changes the value to0 (default). If the current value is H.323 (1), pressing * changes the value to 2 (SIP).

If a value different from the current Group value is entered, the telephone displays the

following text left-justified at the top of the display:


The new value is saved. All telephones display the following text left-justified at the top of

the display:

SIG=pro toco l *=change #=OK


New value

being saved



51/90


52/90



Self-Test Procedure

Note:

Note: 1600 Series IP Telephones store two software code images in reprogrammable

non-volatile memory. The primary image, called the “big app” must be running to

perform a self-test. The backup image, called the “little app” does not support the

self-test.

For self-testing, use the following procedure:

1. To invoke 1600 Series IP Telephone self-test procedures, press the following sequence of

keys on the faceplate of the telephone:

Mute 8 3 7 8 # (Mute T E S T #)

Note:

Note: Press the Mute button momentarily. Do not press this button while pressing other

keys/buttons. All telephones show the following text, left-justified at the top of the display, for 1 second

after self-test is invoked:

A block character with all pixels on then displays in all display character locations for

5 seconds. Display of the block character helps to find bad display pixels.

The telephone displays one of the following:

2. To terminate the self-test, press the # button on the dial pad at any time. Doing so generatesa confirmation tone, and returns the user interface to its previous state.

Self test#=end

If self-test passes: Self test passed

#=end

If self-test fails: Self test failed#=end


53/90


Chapter 4: Maintaining 1600 Series IP Telephones

Introduction

This chapter covers the maintaining the 1600 Series IP Telephones, for example, downloading

a new telephone software version from the Avaya support Web site. Note that the

recommended configuration is the latest call server software and the latest IP telephone

firmware.

Downloading Software Upgrades

The software releases containing the files needed to operate the 1600 Series IP Telephones are

bundled together in a self-extracting executable file you download to your file server from the

Avaya support Web site at: http://www.avaya.com/support. The self-extracting executable file

comes in both zipped and unzipped format.

Currently, you have one “bundle” to download. That bundle contains:

● An upgrade script file and a settings file, which allow you to upgrade to new software

releases and new functionality without having to replace IP telephones.

● Application files for all current 1600 Series IP Telephones.

● Other useful information such as a ReadMe file and a settings file template to customize

parameters and settings.

Download File Content

Two configuration files on the file server are important to understand. Other files are

needed when the Avaya IP Telephones need an upgrade. The important files are:

● An upgrade script file, which tells the IP telephone whether the telephone needs to

upgrade software. The Avaya IP Telephones attempt to read this file whenever they reset.

The upgrade script file is also used to point to the settings file.

● The settings file contains the option settings that enable, disable, or otherwise customize

the settings you might need to tailor the Avaya IP Telephones for your enterprise.



54/90


55/90

Downloading Software Upgrades


The settings file can include any of the five types of statements, one per line:

● Comments, which are statements with a “#” character in the first column.

● Tags, which are comments that have exactly one space character after the initial #,followed by a text string with no spaces.

● Goto commands, of the form GOTO tag. Goto commands cause the telephone tocontinue interpreting the settings file at the next line after a # tag statement. If no such

statement exists, the rest of the settings file is ignored.

● Conditionals, of the form IF $name SEQ st r ing GOTO tag . Conditionals cause the Goto command to be processed if the value of name is a case-insensitive equivalent to st r ing .

If no such name exists, the entire conditional is ignored.

● SET commands, of the form SET parameter_name value . Invalid values cause thespecified value to be ignored for the associated parameter_name so the default or

previously administered value is retained. All values must be text strings, even if the

value itself is numeric, a dotted decimal IP address, etc.

Note:

Note: Enclose all data in quotation marks for proper interpretation.

The Avaya-provided upgrade script file includes lines that tell the telephone to GET

46xxsett ings.scr and 46xxsett ings.txt . These lines cause the telephone to use HTTP/HTTPS

to attempt to download the file specified in the GET command. If the file is obtained, its contents

are interpreted as an additional script file. That is how your settings are changed from the

default settings. If the file cannot be obtained, the telephone continues processing the upgrade

script file. The upgrade script file is processed so that if there is no 46xxsettings.scr file, the

telephone looks for a 46xxsettings.txt file. If the settings file is successfully obtained but does

not include any setting changes the telephone stops using HTTP. This happens when you

initially download the script file template from the Avaya support Web site, before you make any

changes. When the settings file contains no setting changes, the telephone does not go back to

the upgrade script file.

You can change the settings file name, if desired, as long as you also edit the corresponding

GET command in the upgrade script file. However, we encourage you not to alter the Avaya-provided upgrade script file. If Avaya changes the upgrade script file in the future, any

changes you have made will be lost. We strongly encourage you to use the 46xxsett ings file to

customize your settings instead.

For more details on customizing your settings file, see Contents of the Settings File on page 56.


56/90

Maintaining 1600 Series IP Telephones


Contents of the Settings File

After checking the application software, the 1600 Series IP Telephone looks for a 46xxsettings

file. This optional file is under your control and is where you can identify non-default option

settings, application-specific parameters, etc. You can download a template for this file from the

Avaya support Web site. An example of what the file could look like follows.

Note:

Note: The following is intended only as a simple example. Your settings will vary from

the settings shown. This sample assumes specification of a DNS Server, turning

off enhanced local dialing, and a Web Browser.

SET DNSSRVR dnsexample.yourco.com

SET ENDIALSTAT 0

SET WMLHOME http://yourco.com/home.wml

SET WMLPROXY 11.11.11.11

See Chapter 7 in the Avaya 1600 Series IP Deskphones Administrator Guide for

details about specific values. You need only specify settings that vary from defaults,

although specifying defaults is harmless.

Downloading Language Files

Language files must be stored in the same location as the 46xxsettings file or under the HTTP

Server directory, defined using the SET HTTPDIR_ HTTP server directory p ath command.

You can download a new language file version only if the filename differs from the language filepreviously downloaded. Alternately, you can remove the old language file using an empty SETLANGxFILE command in the 46xxsettings file before downloading a language file with thesame filename.

Downloading Font Files for 1600 Series International Telephones

The font file must be stored in the same location as the 46xxsettings file or under the HTTP

Server directory, defined using the SET HTTPDIR_ HTTP server directory p ath command.

You can download a new font tile version only if the filename differs from the font file previously

downloaded. Alternately, you can remove the old font file using an empty SET FONTFILEcommand in the 46xxsettings file before downloading a font file with the same filename.


57/90

The GROUP System Value


The GROUP System Value

You might have different communities of end users, all of which have the same model

telephone, but which require different administered settings. For example, you might want to

restrict Call Center agents from being able to Logoff, which might be an essential capability for“hot-desking” associates. We provide examples of the group settings for each of these

situations later in this section.

The simplest way to separate groups of users is to associate each of them with a number. Use

the GROUP system value for this purpose. The GROUP system value cannot be set in the46xxsettings file. The GROUP system value can only be set on a telephone-by-telephone basis.

To do so, first identify which telephones are associated with which group, and designate a

number for each group. The number can be any integer from 0 to 999, with 0 as the default,

meaning your largest group would be assigned as Group 0.

Then, at each non-default telephone, instruct the installer or end-user to invoke the GROUP

Local (dialpad) Administrative procedure as specified in Chapter 3: Local Administrative

Options and specify which GROUP number to use. Once the GROUP assignments are in place,edit the configuration file to allow each telephone of the appropriate group to download its

proper settings.

Here is an illustration of a possible settings file for the example of a Call Center with hot-desking

associates at the same location:

IF $GROUP SEQ 1 goto CALLCENTER

IF $GROUP SEQ 2 goto HOTDESK

{specify settings unique to Group 0}

goto END

# CALLCENTER


goto END

# HOTDESK


# END

{specify settings common to all Groups}


58/90

Maintaining 1600 Series IP Telephones



59/90


Chapter 5: Troubleshooting Guidelines

Introduction

This chapter describes problems that might occur during both installation and normal operation

of the 1600 Series IP Telephone and possible ways of resolving these problems.

This chapter contains the following sections:

● Descriptions of error conditions and methods for resolving them.

● The use of the V I E W option to view system values.

● Error and status messages, and methods for resolving them.

Error Conditions

There are three areas where installers can troubleshoot problems before seeking assistance

from the system or LAN administrator:

1. Check both the power and Ethernet wiring for the following conditions:

● Whether all components are plugged in correctly.

● Check LAN connectivity in both directions to all servers - DHCP, HTTP, HTTPS, Avaya

Aura Communication Manager or Avaya Aura Communication Manager Branch.● If the telephone is supposed to be powered from the LAN, ensure that the LAN is

properly administered and is compliant with IEEE 803.3af.

2. If you are using static addressing:

● Use the View command to find the names of the files being used and verify that these

filenames match those on the HTTP/HTTPS server. See The View Administrative

Option on page 60 for more information. Check the Avaya Web site to verify whether the

correct files are being used.

● Use the ADDR option to verify IP addresses. See Static Addressing Installation onpage 35 for information.

3. If the 1600 Series IP Telephone is not communicating with the system (DHCP, HTTP, or Avaya Media Server), make a note of the last message displayed, as described in Table 2

and/or Table 3. Consult the system administrator.

4. If you expect the telephone to be IEEE-powered, verify with the LAN administrator that IEEE

power is indeed supported on the LAN.


60/90

Troubleshooting Guidelines


DTMF Tones

H.323 telephones do not send DTMF tones to non-H.323 telephones. The failure to hear DTMF

tones sent by a far-end 1600 Series IP Telephone does not require any action on the user’s

part. The TN2302AP board does not pass in-band DTMF tones.

Power Interruption

If power to a 1600 Series IP Telephone is interrupted while the telephone is saving the

application file, the HTTP/HTTPS application can stop responding. If this occurs, restart the

HTTP/HTTPS server.

The View Administrative Option

If you are using static addressing and encounter problems, use the following procedure to verify

the current values of system parameters and file versions.

Note:

Note: Unless otherwise prevented using administration, the user can view but not

change most of the parameters associated with Local Administrative Procedures.

For more information about this option, see the applicable user guide(s).

Note:

Note: If the View Network Information option is not available due to being disabled byadministration, use the ADDR option to view IP addresses. See Static Addressing Installation in Chapter 3: Local Administrative Options. The IP

addresses might have been entered incorrectly. Verify whether you were

provided with correct IP addresses.



Mute 8 4 3 9 # (Mute V I E W #)

Note:

Note: Press the Mute button momentarily. Do not press this key while pressing other

keys.


View settings*=next #=exit


61/90

The View Administrative Option


2. Press the * button at any time during viewing to display the next name and system valuepair or filename from Table 1. The first pair returns after the last pair displays. Values that

cannot display on one line wrap to the next line.

Press the # button at any time during viewing to terminate the procedure and restore theuser interface to its previous state. The names and values display in the following order:

Table 1: Parameter Values

Name System Value Format

Model 16ccDccc Up to 8 ASCII characters: MODELvalue.

Phone SN cccccccccccccccccc Telephone Serial Number, up to 18 ASCII characters.

PWB SN cccccccccccccccccc Printed Wiring Board (circuit board)Serial Number, up to 18 ASCIIcharacters. Applies only to 16xx IP

Telephones that have asoftware-readable PWB serial numberand comcode.

PWB comcode nnnnnnnnn 9 ASCII numeric characters. Appliesonly to 16xx IP Telephones that have asoftware-readable PWB serial numberand comcode.

MAC address hh:hh :hh :hh :hh :hh Each octet of the MAC address displaysas a pair of hexadecimal numbers.

L2 tagging ccccccccc Up to 9 ASCII characters:“on” if NVL2Q = 1“off” if NVL2Q = 2

“auto: on” if NVL2Q = 0 and 802.1Qtagging is on“auto: off” if NVL2Q = 0 and 802.1Qtagging is off

VLAN ID cccc Up to 4 ASCII characters. Value isL2QVLAN if 802.1Q tagging is on or“none” of 802.1Q tagging is off.

IP address nnn.nnn.nnn.nnn Up to 15 ASCII characters:IPADD value.

Subnet mask nnn.nnn.nnn.nnn Up to 15 ASCII characters:NETMASK value.

Router nnn.nnn.nnn.nnn Up to 15 ASCII characters:the IP address of the router in use.

1 of 2


62/90

Troubleshooting Guidelines


File server nnn.nnn.nnn.nnn.nnnnn Up to 21 ASCII characters: IP addressand port of last file server usedsuccessfully during initialization or

“0.0.0.0” if no file server was usedsuccessfully.

Call server nnn.nnn.nnn.nnn.nnnnn Up to 21 ASCII characters: IP addressand port of the call server currently inuse, otherwise “0.0.0.0.”

802.1X If DOT1X = 0If DOT1X = 1If DOT1X = 2

pass-thru mode.p-t w/Logoff (pass-thru with Logoff).Supplicant mode.

Group nnn Up to 3 ASCII numeric characters:GROUP value.

Protocol: cccccccc

f i lename.ext

cccccccc Ethernet

boo tcodename

Up to 8 ASCII characters, currently only“H.323.”

4 to 32 ASCII characters. The name ofthe primary ("big app") image filecurrently stored in the telephone(endptAPPINUSE).

2 to 7 ASCII characters, either“100Mbps”, “10Mbps”, or “No”depending on the current speed of theEthernet line interface.

1 to 32 ASCII characters. The name ofthe backup ("little app") image filecurrently stored in the telephone(endptBOOTNAME).

Button Module 1 cccccccccccccc Up to 14 ASCII characters. The versionidentifier of the software in the ButtonModule, if applicable.



Table 1: Parameter Values (continued)

Name System Value Format

2 of 2


63/90

Installation Error and Status Messages


Installation Error and Status Messages

The 1600 Series IP Telephones issue messages in English only. The IP telephones also display

messages from the switch, which can issue messages in the local language outside the United

States. The 1600 Series IP Telephones issue messages in the currently selected language, or ifthe telephone is logged off, in the language specified by the LANGSYS parameter value. If

English is not the selected language, the telephone displays messages in English only when

they are associated with local procedures, for example, MUTE V I E W.

Most of the messages in Table 2 display only for about 30 seconds, and then the telephone

resets. The most common exception is Extension in Use, which requires manual

intervention.

Table 2: Possible Error and Status Messages During Installation of 1600 Series IPTelephones

Message Cause/Resolution

802.1X Failure CAUSE: Incorrect credentials provided for authentication or notprovided at all.

RESOLUTION: Follow the display prompts and reenter the 802.1X IDand password.

AddressConflict

CAUSE: The telephone has detected an IP address conflict.

RESOLUTION: Verify administration to identify duplicate IPaddress(es).

Bad FileSvAddress

CAUSE: The HTTP/HTTPS server IP address in the IP telephone’smemory is all zeroes.

RESOLUTION: Depending on the specific requirements of yournetwork, this may not be an error. If appropriate, either administer theDHCP server with the proper address of the HTTP/HTTPS server, or

administer the telephone locally using the ADDR option. The ADDRoption is explained in Chapter 3: Local Administrative Options.

Bad Router? CAUSE: The telephone cannot find a router based on the information inthe DHCP file for GIPADD.

RESOLUTION: Use static addressing to specify a router address, orchange administration on DHCP, as indicated in the 1600 Series IPTelephone Administrator Guide.

Call Error CAUSE: The user was on a call when the connection to the gatekeeperwent down, perhaps due to a network outage or a gatekeeper problem.The telephone attempted to automatically register with the same, oranother, gatekeeper, but the responding gatekeeper had no record ofthe call.

RESOLUTION: Wait for the