1600 Series IP Telephone Installation and Maintenance Guide Release 1.

0
DRAFT 10/20/2006

16-601438 Issue 1 April 2007

© 2006 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full legal page information, please see the complete document, Avaya Legal Page for Hardware Documentation, Document number 03-600759. To locate this document on our Web site, simply go to http://www.avaya.com/support and search for the document number in the search box. Documentation disclaimer Avaya Inc. is not 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. Customer and/or End User agree 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 the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we 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’s standard warranty language, as well as information regarding support for this product, 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 copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Avaya support Avaya provides a telephone number for you to use to report problems or to 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 Software License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER’S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE AT http://support.avaya.com/LicenseInfo/ (“GENERAL LICENSE TERMS”). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN 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 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. “Software” 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 standard hardware Products, 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 copy of the Software on only one Designated Processor, unless a different number 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.

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 identifying Third Party Components and the Third Party Terms that apply to them is available 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 to an Avaya IP Telephone might cause interference.

Contents

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5
5 5 6 6 6 8

Chapter 2: 1600 Series IP Telephone Installation . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Telephone Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assembling the 1600 Series IP Telephone . . . . . . . . . . . . . . . . . . . . . . Powering the 1600 Series IP Telephone . . . . . . . . . . . . . . . . . . . . . Dynamic Addressing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unnamed Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9
9 9 10 10 12 12 17 20

Chapter 3: Local Administrative Options . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entering Data for Administrative Options . . . . . . . . . . . . . . . . . . . . . . About Local Administrative Procedures . . . . . . . . . . . . . . . . . . . . . . . Set the 802.1X Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-Installation Checklist for Static Addressing . . . . . . . . . . . . . . . . . . . Static Addressing Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable/Enable Automatic Gain Control . . . . . . . . . . . . . . . . . . . . . . . Manually Setting the DHCP Client Hardware Address . . . . . . . . . . . . . . . Clear Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable/Enable Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Group Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable/Enable Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logoff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View Multi-Language Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset System Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restart the Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signaling Protocol Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23
23 24 24 26 27 27 30 32 33 34 35 36 38 39 40 41 42 43

Issue 1 April 2007

3

Contents

Site-Specific Option Number Setting . . . . . . . . . . . . . . . . . . . . . . . . . Self-Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

44 45

Chapter 4: Maintaining 1600 Series IP Telephones . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading Software Upgrades. Download File Content . . . . Download Procedure . . . . . Contents of the Settings File . Downloading Language Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

47
47 47 47 48 50 50 50

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

Chapter 5: Troubleshooting Guidelines . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DTMF Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Interruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The View Administrative Option . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Error and Status Messages . . . . . . . . . . . . . . . . . . . . . . . Operational Errors and Status Messages . . . . . . . . . . . . . . . . . . . . . .

53
53 53 54 54 54 57 61

Appendix A: Restart Scenarios . . . . . . . . . . . . . . . . . . . . . . .
Scenarios for the Restart Process . . . . . . . . . Restart the Telephone . . . . . . . . . . . . . . Boot File Needs to be Upgraded . . . . . . . . Latest Boot File Loaded/No Application File or Application File Needs to be Upgraded . . . . Latest Boot File and System-Specific Application File Already Loaded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

67
67 67 68 71 72

Appendix B: Glossary of Terms . . . . . . . . . . . . . . . . . . . . . .
Terms Used in This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

75
75

Appendix C: Related Documentation . . . . . . . . . . . . . . . . . . .
IETF Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ITU Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISO/IEC, ANSI/IEEE Documents . . . . . . . . . . . . . . . . . . . . . . . . .

77
77 78 79

Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

81

4 1600 Series IP Telephone Installation and Maintenance Guide

HTTP. generic references in this document to a server can apply to DEFINITY® servers. Take care to ensure that there is adequate technical support available for the servers involved. The 1600 Series IP Telephone product line supports only the H. the IP telephones might not be able to operate correctly. including. Note: Unless otherwise indicated. If the servers are not functioning correctly.Chapter 1: Introduction About This Guide This guide describes how to install and maintain the 1600 Series IP Telephone product line and troubleshoot telephone problems. Note: Note: Intended Audience This document is intended for personnel who install and administer the 1600 Series IP Telephones. HTTPS. ! CAUTION: CAUTION: Avaya does not support many of the products mentioned in this document. and DHCP servers.0 or later call servers. MultiVantage servers or Avaya Communication Manager media servers. Note: Any reference to HTTP in this guide applies equally to HTTPS. Issue 1 April 2007 5 .323 signaling protocol and work only with Avaya Communication Manager Release 4. but not necessarily limited to.

com/support for 1600 Series IP Telephone technical and end user documentation. Provides references to external documents that relate to telephony in general. Describes the equipment and resources required to properly install and operate the 1600 Series IP Telephones.Introduction Document Organization The guide contains the following sections: Chapter 1: Introduction Chapter 2: 1600 Series IP Telephone Installation Chapter 3: Local Administrative Options Chapter 4: Maintaining 1600 Series IP Telephones Chapter 5: Troubleshooting Guidelines Appendix A: Restart Scenarios Appendix B: Glossary of Terms Appendix C: Related Documentation Provides an overview of this guide. Describes how to set local administrative options. Describes maintenance actions like downloading telephone software from the Avaya support Web site and customizing system values. Provides a glossary of terms used in this document or which are generally applicable to 1600 Series IP Telephones.avaya. Provides instructions on installing the telephones out of the box. Other Documentation See the Avaya support site at http://www. and can provide additional information about specific aspects of the telephones. if requested by the system or LAN administrator. Explains the different scenarios possible for the sequence of the restart process. 6 1600 Series IP Telephone Installation and Maintenance Guide . Change History Issue 1 This document was issued for the first time in April 2007. Describes error conditions and messages that might occur during the installation of the 1600 Series IP Telephones.

Document Number 116-601450 1600 Series IP Telephone Wall Mount Instructions. Document Number 116-601443. 1608 IP Telephone Quick Reference. Document Number 116-601453. 1603 IP Telephone Quick Reference. Document Number 116-601441. 1616 IP Telephone User Guide. 1600 Series IP Telephones BM32 Button Module User Guide. Document Number 116-601442. Document Number 116-601451. Document Number 116-601447. Document Number 116-601448. Document Number 116-601439. Document Number 116-601444. Document Number 116-601446. ● ● ● ● ● ● ● ● ● ● ● ● ● ● See Appendix C: Related Documentation for a list of non-Avaya documents. 1608 IP Telephone User Guide. 1600 Series IP Telephones BM32 Button Module Installation and Safety Instructions. 1603 IP Telephone User Guide. 1616 IP Telephone Quick Reference. Document Number 16-601438. 1600 Series IP Telephone Application Programmer Interface (API) Guide. Document Number 116-601449. Document Number 116-601440. 1600 Series Telephone Administrator Guide. Issue 1 April 2007 7 . 1600 Series IP Telephone Stand Instructions. Document Number 116-601445. such as those published by the Internet Engineering Task Force (IETF) and International Telecommunication Union (ITU).Other Documentation The following documents are available for the 1600 Series IP Telephones: ● 1600 Series IP Telephone Installation and Maintenance Guide. 1600 Series IP Telephone Safety Instructions. 1600 Series IP Telephone Pre-Installation Checklist.

Introduction

Customer Support
For 1600 Series IP Telephone 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: http://www.avaya.com/support

8 1600 Series IP Telephone Installation and Maintenance Guide

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 and HTTP or HTTPS to download new software versions or customized settings for the telephones. The 1608 and 1616 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 IP Telephone does not provide a secondary Ethernet connection for a 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.

IP Telephone Models
There are three telephone set models and a button module currently defined in the 1600 Series IP Telephone family: Model Call Appearance/ Line Appearance/ Feature Buttons 3 8 16 32 Display Size

● ● ● ●

1603 IP Telephone 1608 IP Telephone 1616 IP Telephone SBM32 Button Module

2 row by 16 column display 3 row by 24 column display 4 row by 24 column display No display

Issue 1 April 2007

9

1600 Series IP Telephone Installation

The 1608 and 1616 telephones have an internal Ethernet switch that allows the telephone and a PC to share the same LAN connection, if appropriate. Thus, 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 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. 2. Ensure that the LAN uses Ethernet Category 5e cabling running the IPv4 version of Internet Protocol. Avaya Communication Manager Release 3.0 or later software supports the 1600 Series IP Telephones, aliased as 4600 Series IP Telephones. Specifically, the 1603 should be aliased as a 4606, the 1608 should be aliased as a 4612 and the 1616 should be aliased as a 4624.

10 1600 Series IP Telephone Installation and Maintenance Guide

Pre-Installation Checklist

Verify These Network Requirements (continued) 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 must also install a TN2602 circuit pack. ● TN799B, C, or D Control-LAN (CLAN) circuit pack.

Note:

Important: IP telephone firmware Release 1.0 or greater requires TN799C V3 or greater CLAN circuit pack(s). For more information, see the Communication Manager Software and Firmware Compatibility Matrix on the Avaya support Web site http://www.avaya.com/support. 4. The Avaya Media Server is configured correctly, as described in the 1600 Series IP Telephone Administrator Guide and Avaya Communication Manager documentation. Both documents are available at http://www.avaya.com/support. 5. The DHCP server and application are administered as described in the 1600 Series IP Telephone Administrator Guide. 6. The HTTP server and application are administered as described in the 1600 Series IP Telephone 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 1600 Series IP Telephone Administrator Guide. 9. If applicable, the WML server is administered as described in the 1600 Series IP Telephone Administrator Guide. Notes: - Any or all of the server applications mentioned in items 5.-9. can be co-resident on the same hardware, subject to the specific restrictions of each individual application. - See the 1600 Series IP Telephone Administrator Guide for more information about: ● administering other network equipment, ● administering applications like firewalls, and ● information about topics like port utilization.
Important:

!

Requirements to Verify for Each IP Telephone 10. You have an extension number and an Avaya Communication Manager security code (password) for each applicable IP telephone. If your call server supports unnamed registration, and the telephone settings file allows unnamed registration, you do not need to provide an extension or password for the telephone. However, if you do not provide an extension or password, the telephone will have very limited telephone functionality. (For information, see Unnamed Registration on page 20.) A Category 5e LAN jack is available at each telephone site. Electrical power is provided to each telephone by a Telephone Power Module (DC power jack) (must be ordered separately). If the LAN will supply IEEE-standard power to the telephone, no power module is required. 1 Category 5e modular line cord is available for the connection between the IP telephone and the PC, if applicable.

11. 12. 13.

Issue 1 April 2007

11

● 1600 Series IP Telephone Stand Instructions. ● 1 H4DU 9-foot long (when extended) 4-conductor coiled handset cord. Verify that the 1600 Series IP Telephone package includes the following components: ● 1 telephone set with pre-attached stand. whether the telephone should be powered locally or by means of the LAN. ● 1 handset capable of transmitting and receiving 7KHz audio. ● 1600 Series IP Telephone Wall Mount Instructions. Powering the 1600 Series IP Telephone All 1600 Series IP Telephones can be locally powered with a Telephone Power Module (DC power jack). Note: ! CAUTION: CAUTION: Failure to connect the proper cables with the proper jacks might result in an outage in part of your network. ● 1 Category 5 modular line cord for the connection from the IP telephone to the Ethernet wall jack. the 1608 IP Telephone and the 1616 IP Telephone support only the HIS headset cords. In addition. ● 1600 Series IP Telephone Safety Instructions. 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). The 1603 IP Telephone does not support headsets. and if so.3af-standard LAN-based power.3af. Note: The last step in assembling the 1600 Series IP Telephone must be applying power. The jacks are located on the back of the telephone housing and are flanked by icons to represent their correct use. the telephones support IEEE 802. plugged into the telephone and the handset. verify with the LAN administrator whether the LAN supports IEEE 802. Before installing a 1600 Series IP Telephone. Assembling the 1600 Series IP Telephone ! CAUTION: CAUTION: Be careful to use the correct jack when plugging in the telephone. 12 1600 Series IP Telephone Installation and Maintenance Guide . Note: Note: For sites using headsets.1600 Series IP Telephone Installation 14. available separately.

Figure 3. Use the illustrations and associated procedures as appropriate for telephone assembly. and Figure 3 provide illustrations to connect cords to jacks on 1600 Series IP Telephones.Assembling the 1600 Series IP Telephone Figure 2. Telephone Model: 1603 1608 1616 See: Figure 2 Figure 3 Figure 3 Issue 1 April 2007 13 .

1600 Series IP Telephone Installation Figure 1: Connection Jacks on a 1603 Series IP Telephone 14 1600 Series IP Telephone Installation and Maintenance Guide .

Assembling the 1600 Series IP Telephone Figure 2: Connection Jacks on a 1608 Series IP Telephone Issue 1 April 2007 15 .

1600 Series IP Telephone Installation Figure 3: Connection Jacks on a 1616 Series IP Telephone Note: The SBM32 Button Module shown in the lower left corner can also be attached to the telephone with the connector packaged with the module. 16 1600 Series IP Telephone Installation and Maintenance Guide .

plug the power cord into the 1600 Series IP Telephone. see Unnamed Registration on page 20. Any reference to the HTTP server applies equally to an HTTPS server. The duration is based on LAN loading. For errors that might be encountered during the process and the messages displayed. For more information. If the telephone is to be powered locally in the United States and Canada. Only an initial out of the box installation is described. if applicable. 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. Do not unplug the power cord during the download process. if appropriate. the following process takes place. 2.Dynamic Addressing Process 1. Connect the other end of the power cable to the 1600 Series IP Telephone. The following description of the process of installing the IP telephones assumes that the process is executed successfully. and the power cord plug into the wall socket. Note: Issue 1 April 2007 17 . see Chapter 5: Troubleshooting Guidelines. Dynamic Addressing Process Note: Note: Before starting this process you must have an extension number for the IP telephone and the Avaya Communication Manager security code (password) for that extension. Note: If the application has already been downloaded. how many telephones are being installed at once. the process might take 5 . Plug one end of the H4DU 4-conductor coiled handset cord into the telephone and the other end into the handset. For software upgrades. you are finished. 4. Plug one end of the second Category 5 modular line cord into the Ethernet jack on the 1600 Series IP Telephone. Do not proceed to Step 4. unless the telephone will use unnamed registration. connect the 1151 power brick to the power cable. If the telephone is to be IEEE-powered. When you plug the IP telephone set into the Ethernet wall jack and apply power. If the telephone is to be powered locally outside the United States and Canada. the whole process takes approximately 1 to 2 minutes after the telephone is plugged in. and the plug to the wall socket. including the boot file and application file download.10 minutes. and similar factors. Plug the other end of this cord into the Ethernet wall jack. 3.

the message on the right appears if 802. 18 1600 Series IP Telephone Installation and Maintenance Guide . The message on the left appears if 802.1Q tagging is on and access to local programming procedures is disabled or restricted. Finally. When the router is located. The activation occurs as soon as possible after power-up or a reset. (See Chapter 3: Local Administrative Options for specifics.1Q tagging is on. Note: The Ethernet speed indicated is the LAN interface speed for both the telephone and any attached PC. The DHCP server provides IP addresses for the following hardware: ● ● ● The IP telephone The HTTP/HTTPS server The TN799C or D Control-LAN (CLAN) circuit pack on the media server 4. The telephone activates the Ethernet line interface. The IP telephone sends a request to the DHCP server and invokes the DHCP process. 802. Using the list of gateway IP addresses provided by the DHCP server. and dial pad input to allow the invocation of procedures. One of the following messages display: DHCP: s secs * to program DHCP: s secs VLAN ID = n DHCP: s secs Note: where s is the number of seconds that have elapsed since DHCP was invoked. that is. When both messages alternate.1600 Series IP Telephone Installation 1.1Q tagging is off and access to local programming procedures is disabled or restricted. the HTTP process starts. 3. the telephone performs a router check. access to local programming procedures is not disabled or restricted. The message No Ethernet displays until the software determines whether the interface is 10 Mbps or 100 Mbps.) The middle message appears if 802. The telephone displays the speed of the Ethernet interface in Mbps. 2. 5. the PC Ethernet jack. 10 or 100. While the IP telephone connects to the HTTP server. The telephone cycles through the gateway IP addresses with ARPs or pings until it receives a response.1Q tagging is off and access to local programming procedures is not disabled or restricted. assuming the administrator has not disabled the latter interface by a PHY2STAT setting. If the left and middle messages alternate every two seconds. the telephone displays the following message: HTTP:n ipadd where n is the number of the IP address obtained from the HTTP server and ipadd is the IP address.

All IP telephones display the following prompts for an extension: Login Enter Extension Enter Extension and press Enter or OK Issue 1 April 2007 19 . 1 secs with the percentage of the file and the number of elapsed seconds incremented as the application file is stored in flash memory. When connected. 10. The HTTP server sends and identifies an upgrade script. the telephone looks for an upgrade script file. 9.Dynamic Addressing Process 6. 7. The GET message might have to be sent several times. all IP telephones display the following message: Saving to flash 1%. all IP telephones display the following message: HTTP:n sc etag where n is the number of the IP address obtained from the HTTP server. While the upgrade script file is being downloaded. Each time the GET message is sent. While the application file is saved in flash memory. sc is the status code of the HTTP response and etag is the value of the ETag header. The telephone contacts the Avaya Media Server and attempts to log in. n is the number of HTTP requests made by the telephone and uri is the URI for the current HTTP request. 8. all IP telephones display one of the following messages: HTTP: n uri For HTTP.

Enter a new extension and press OK. The extension is visible as you enter it but the password displays as asterisks. to report a building emergency like a fire. This takeover unregisters the office telephone. 20 1600 Series IP Telephone Installation and Maintenance Guide . the user unregisters the telephone by logging off or by taking the office telephone extension over to another telephone. 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. All IP telephones display the following prompt for a password: Login Enter Password Enter Password and press Enter or OK 12. The IP telephone was installed successfully.1600 Series IP Telephone Installation 11. ● In both examples. The downside of a telephone being unregistered is that no one can use the telephone. which allows a traveller to invoke the telephony features and functionality by taking over the office telephone extension. and receive limited service. press OK or make no entry and wait 60 seconds. The system determines whether the extension is in use. The UNNAMEDSTAT parameter must be set to enable unnamed registration. Without unnamed registration. Using the Avaya Softphone application in “road warrior” mode. Successful completion of this process produces a dial tone when the Speaker button is pressed or the handset is lifted. For more information. see Unnamed Registration. Enter the password and press OK. Note: Unnamed Registration Unnamed registration is a capability an IP telephone can have to register with a call server. Telephones registered unnamed have limited functionality. To register the telephone without the extension or password (unnamed). To register the telephone without the extension or password (unnamed). for example. without requiring an extension and password entry. press only OK or make no entry and wait 60 seconds. 14. Note: Unnamed registration is the capability to register a telephone with the call server without entry of an extension or password. 13. the telephone in the 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.

like a given user’s Contacts data or Option settings are not available. and is similar from an administration perspective. access to an emergency number. Unnamed registration appears to the end user like Avaya Communication Manager TTI Mode. Because there is no extension. The user has no administered feature buttons. For more information about TTI. and hence.Unnamed Registration Unnamed registration allows the telephone to register without an extension and password. Unnamed registration is ignored after any dialpad entry. ● Unless otherwise disabled. The user is limited to the calling capability administered for PSA (Personal Station Access) on the call server. cannot transfer or conference calls. see your Avaya Communication Manager documentation. Administrators can disable unnamed registration by appropria1600 Series IP Telephone Administrator Guide. Extension-based information. specifically: ● ● ● The user has only one call appearance. Issue 1 April 2007 21 . and cannot invoke on-hook dialing. Initiating any ID or password entry disables and prevents unnamed registration from occurring. telephony functionality is limited. the telephone automatically attempts to register unnamed if no action is taken on the telephone Extension entry screen within 60 seconds. for example.

1600 Series IP Telephone Installation 22 1600 Series IP Telephone Installation and Maintenance Guide .

as always. See Chapter 4: Maintaining 1600 Series IP Telephones and “1600 Series IP Telephone Scripts and Application Files” in Chapter 4 of the 1600 Series IP Telephones Administrator Guide. only if instructed by the system or LAN administrator. as indicated in Reset System Values on page 41. or . Note: ! CAUTION: CAUTION: Perform these procedures only if instructed to do so by the system or LAN administrator. Issue 1 April 2007 23 . 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. Values assigned to options in static administration are not changed by upgrade scripts.Chapter 3: Local Administrative Options Introduction After you have successfully installed an IP telephone. DHCP is the Dynamic Addressing Process.a new boot file is downloaded. Static administration of these options causes upgrades to work differently than if they are administered dynamically. you might be instructed to administer one of the options described in this chapter. Do not use these option-setting procedures if you are using DHCP.the IP telephone is reset. Use these option-setting procedures only with static addressing and. as indicated in Dynamic Addressing Process on page 17. These values remain stored in the telephone until either: .

the user can view but not change most of the parameters associated with Local Administrative procedures. 2. up to 7 numeric dial pad buttons. 1. press the leftmost softkey. the most recently entered digit or period is erased from the display. 6. see the applicable user guides. 5. Note: Unless otherwise prohibited by administration. If you enter a numeric digit for a value or for an IP address or subnet mask field after entering only a zero. This section provides a description of each local administrative option covered in this guide. Attempts to enter invalid data are rejected.Local Administrative Options Entering Data for Administrative Options This section applies to all 1600 Series IP Telephones and describes how to enter data for administrative options. you will not be able to invoke any administrative options other than V I E W. For more information about this option. In this case. When you press the applicable button or key to backspace. A 6-second timeout is in effect between button presses after pressing the Mute button. To backspace. Invoke all local procedures by pressing the Mute button. with references to the pages on which the option appears. and the telephone emits an error beep. Note: 24 1600 Series IP Telephone Installation and Maintenance Guide . Note: If PROCSTAT has been administered to 1. If PROCPSWD is administered as indicated in Chapter 7 of the 1600 Series IP Telephones Administrator Guide. Note: About Local Administrative Procedures Local administrative procedures allow you to customize the 1600 Series IP Telephone installation for your specific operating environment. 4. the new digit replaces the zero. 3. Press the # button to go to the next step. no administrative option is invoked. the collected digits are discarded. If you do not press a valid button within 6 seconds of pressing the previous button. you must type the Local Procedure password after pressing Mute and before pressing the code for your given local programming option. and the # button. The cursor remains in the erased character’s former position.

Restart the Telephone on page 42.1X Operational Mode on page 26. Signaling Protocol Identifier on page 43. Interface Control on page 36. Clear values to factory defaults Enable/disable Debug Mode Group Identifier Interface Control Event Logging System-specific Logoff View Multi-Language Strings Reset the telephone Restart the telephone Signaling protocol identifier (not applicable to Release 1. Disable/Enable Debug Mode on page 34. For more information about this option.About Local Administrative Procedures Local Programming Option Set 802.1X operational mode Static addressing Automatic Gain Control DHCP chaddr field value Code 8 0 2 1 X (8 0 2 1 9) A D D R (2 3 3 7) A G C (2 4 2) C H A D D R (2 4 2 3 3 7) See Set the 802. Clear Procedure on page 33. Manually Setting the DHCP Client Hardware Address on page 32.0) Site-Specific Option number Test the telephone View current parameter values and file names C L E A R (2 5 3 2 7) D E B U G (3 3 2 8 4) G R O U P (4 7 6 8 7) I N T (4 6 8) L O G (5 6 4) L O G O F F (5 6 4 6 3 3) M L S (6 5 7) R E S E T (7 3 7 3 8) R E S E T (7 3 7 3 8) S I G (7 4 4) S S O N (7 7 6 6) T E S T (8 3 7 8) V I E W (8 4 3 9) Note: Note: Unless otherwise prohibited using administration. View Multi-Language Strings on page 40. Group Identifier on page 35. The View Administrative Option on page 54. the user can view but not change most of the parameters associated with Local Administrative Procedures. Logoff on page 39. Disable/Enable Event Logging on page 38. Issue 1 April 2007 25 . see the applicable user guide(s). Static Addressing Installation on page 27. Reset System Values on page 41. Self-Test Procedure on page 45. Disable/Enable Automatic Gain Control on page 30. Site-Specific Option Number Setting on page 44.

1X=setting *=change #=OK where. pressing * changes the value to 1 (Pass-thru with Logoff). the next sequential valid mode value is selected and displayed as the setting. After entry of the command sequence. except for the 9610 which displays the actual value. 2.1X value is entered. 26 1600 Series IP Telephone Installation and Maintenance Guide . or the # button to save the new value. pressing * changes the value to 0 (Pass-thru). 1.Local Administrative Options Set the 802. Do not press this button while pressing other keys/buttons. To change the mode value. If a value different from the current 802. If you press the # button. If the current value is Supplicant mode (2). Press the * button to terminate the procedure.1X Operational Mode Use the following procedure to set or change the operational mode. the setting is the current value of the system value DOTIX (802. press *. While the telephone is on-hook and idle. if the current value is Pass-thru (0). the following text displays left-justified at the top of the display: Save new value? *=no #=yes 4. the following text displays: 802. the telephone displays the following text: New value being saved The telephone saves the new value.1X Supplicant Mode). defined as: ● ● ● Note: Pass-thru mode if setting = 0 Pass-thru mode with Logoff if setting = 1 Supplicant mode without Pass-thru or Logoff if setting = 2 3. For example. press the following sequence of keys on the faceplate of the telephone: Mute 8 0 2 1 9 # (Mute 8 0 2 1 x #) Note: Press the Mute button momentarily. Depending on the current value.

Static Addressing Installation The usual way to assign IP addresses to IP telephones is the automatic method described in Dynamic Addressing Process on page 17. Print copies of this checklist for each subnet. The IP address of the gateway/router. we very strongly recommend that a DHCP server be installed and static addressing avoided. verify that all the requirements listed in the Verify These Network Requirements section of the Pre-Installation Checklist are met. Issue 1 April 2007 27 . 4. You do not have to consider item 4.Pre-Installation Checklist for Static Addressing Pre-Installation Checklist for Static Addressing Before performing static addressing. The IP netmask. Because of the increased opportunities for text entry errors associated with static addressing. 2. however. 5. Such errors can also have a negative impact on your network. ! CAUTION: CAUTION: Static addressing is necessary when a DHCP server is unavailable. Do not change this value unless it conflicts with an existing port assignment. There might be times. The IP address of the media server. The transport layer port number of the address of the Management Complex (media server/gatekeeper). 1. as it refers to the DHCP server. you must have the values for the following parameters. Although this can be a value between 0 and 65535. when manual assignment of IP addresses is desired. Failure to do so can cause data entry errors that prevent the telephone from working. 3. on page 11. The IP address of the HTTP server. the default value is 1719. In addition.

nnn is the current IP address system value of the telephone.nnn is the current system value of the gateway/router IP address.nnn.nnn.nnn. 4.nnn is the current system value of the IP netmask.nnn.nnn.nnn. press the following sequence of keys on the faceplate of the telephone: Mute 2 3 3 7 # (Mute A D D R #) Note: Press the Mute button momentarily. The telephone displays: Mask=nnn. Enter the Gatekeeper IP address followed by the # button.nnn. The telephone displays: CallSv=nnn.nnn. 3. Enter the Gateway router IP address followed by the # button.nnn.nnn. During normal DHCP processing.nnn New=_ where nnn.nnn.nnn.Local Administrative Options Use the following procedure to invoke manual address information programming.nnn.nnn is the current system value of the media server/gatekeeper IP address. Enter the telephone’s IP address followed by the # button.nnn New=_ where nnn. Note: 28 1600 Series IP Telephone Installation and Maintenance Guide .nnn New=_ where nnn. 2. Do not press this button while pressing other keys/buttons. or b. Start manual address programming by performing one of the following steps: a. While the telephone is on-hook and idle. The telephone displays: Phone=nnn.nnn New=_ where nnn.nnn. The telephone displays: Router=nnn. press the * key while “* to program“ displays during the DHCP process.nnn. 1.nnn.

The telephone displays one of the following texts.1 VLAN ID. The telephone displays the following message: VLAN test=ddd New=_ where ddd is the current system value of the DHCPOFFER wait period.nnn.1Q to the next sequential value.1Q): If NVL2Q is 0: 802.1Q=auto *=change #=OK 802. if the current value is 0 (auto) pressing * changes it to 1 (off) and if the current value is 2 (on).nnn.1Q The telephone displays the following text: VLAN ID=dddd New=_ where dddd is the current system value of the 802.nnn is the current system value of the HTTP/HTTPS server IP address. The telephone displays: FileSv=nnn.nnn.1 VLAN ID.Static Addressing Installation 5. Enter the IP netmask followed by the # button.1Q. depending on the current setting of the system parameter NVL2Q (802.1Q=on *=change #=OK If NVL2Q is 1: If NVL2Q is 2: 7.1Q=off *=change #=OK 802.nnn New=_ where nnn. 6. Issue 1 April 2007 29 . For example.nnn. 9. Press * to change 802. Enter the HTTP Server IP address followed by the # button. pressing * changes it to 0 (auto). The display is updated to show the current status of 802. Enter a valid value between 0 and 4094 for the new value of the 802. 8. Press the # button to continue the procedure without changing the displayed status of 802.

press the following sequence of keys on the faceplate of the telephone: Mute 2 4 2 # (Mute A G C #) Note: Press the Mute button momentarily. Enter a valid value between 0 and 999 for the new value of the DHCPOFFER wait period. you must reenter your static addressing information. While the telephone is on-hook and idle. the backup file stores the AGC value(s) set by the user and ignores any setting established using this local procedure. headset. If a new boot program is downloaded from the HTTP server after you enter static addressing information. the telephone is reset.Local Administrative Options 10. 2. Disable/Enable Automatic Gain Control Use the following procedure to turn automatic gain control for the handset. The telephone displays: Save new values? *=no #=yes 11. If overridden. After entry of the command sequence. and/or the Speaker on or off. Press the # button to save the new values you entered. Note: The user can potentially override the AGC local procedure settings. one of the following displays. as described in the telephone user guide. based on the current value of the system value AGCHAND: If AGCHAND = 1: Handset AGC=on 0=off #=OK Handset AGC=off 1=on #=OK Note: Note: If AGCHAND = 0: 30 1600 Series IP Telephone Installation and Maintenance Guide . Do not press this button while pressing other keys/buttons. The telephone displays: New values being saved Once the new values are stored. 1.

press 0. the following text displays left-justified at the top of the display: Save new value? *=no #=yes 6.Disable/Enable Automatic Gain Control 3. or the # button to save the new value(s). press 1. 4. the telephone displays the following text: New value being saved The telephone saves the new value(s). Issue 1 April 2007 31 . One of the following displays. If a value different from the current AGCHAND value and/or the current AGCHEAD value and/or the current AGCSPKR value is entered. If the telephone has a Headset interface one of the following displays. Press the * button to terminate the procedure. To change the AGC Handset value from On to Off. press 0. To change the AGC Speaker value from Off to On. proceed to Step 5. based on the current value of the system value AGCHEAD: If AGCHEAD = 1: Headset AGC=on 0=off #=OK Headset AGC=off 1=on #=OK If AGCHEAD = 0: If the telephone does not have a headset interface. If you press the # button. To change the AGC Headset value from Off to On. press 0. To change the AGC Speaker value from On to Off. press 1. press 1. based on the current value of the system value AGCSPKR: If AGCSPKR = 1: Speaker AGC=on 0=off #=OK Speaker AGC=off 1=on #=OK If AGCSPKR = 0: 5. To change the AGC Headset value from On to Off. To change the AGC Handset value from Off to On.

This value is usually the MAC address. if a value different from the current value of NVCHADDR is entered. 1. To change the Client Hardware Address value. 2. Do not press this button while pressing other keys/buttons. The telephone displays the following text left-justified at the top of the display: chaddr=ddd New= where ddd is the value of NVCHADDR. enter a valid client hardware address. Press the * button to terminate the procedure.Local Administrative Options Manually Setting the DHCP Client Hardware Address Use this procedure to manually set or change the Client Hardware Address. 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: Press the Mute button momentarily. For all IP telephones. if you use static addressing rather than DHCP. the system variable for the DHCP Client Hardware Address. or the # button to save the new value. which DHCP then converts to an integer preceded by zeroes. Note: 32 1600 Series IP Telephone Installation and Maintenance Guide . While the telephone is on-hook and idle. the telephone displays the following text: New value being saved The telephone saves the new value. If you press the # button. the following text displays left-justified at the top of the display: Save new value? *=no #=yes 3.

the telephone retains the latest software. If you do not want to clear all values. you can administer it normally. user-assigned and options values. Once you have cleared a telephone. If you have upgraded the telephone. but requires different permissions than the previous user. and option settings. ! CAUTION: CAUTION: This procedure erases all administered data. 1. file server and call server programming. While the telephone is on-hook and idle. and restores all such data to default values. dedicated user when the user’s L O G O F F option is not sufficient. press * (no) to terminate the procedure and retain the current values. The C L E A R option does not affect the software load itself. without any possibility of recovering the data. For example. Do not press this button while pressing other keys/buttons. and user settings including Contact button labels and locally programmed Feature button labels. user-specified data. Essentially. A screen displays the following prompt on the top line: Are you sure? *=no #=yes Note: Issue 1 April 2007 33 . The following text displays left-justified at the top of the display: Clear all values? *=no #=yes 2. press the following sequence of keys on the faceplate of the telephone: Mute 2 5 3 2 7 # (Mute C L E A R #) Note: Press the Mute button momentarily. you might want to remove all administered values.Clear Procedure Clear Procedure Sometimes. The C L E A R option erases all administered data—static programming. a new user is assigned the same extension. Use the following procedure to clear the telephone of its administrative. 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.

the telephone displays the following text: New value being saved The telephone saves the new value. the following displays. Press the * button to terminate the procedure.Local Administrative Options 3. Press the * button to terminate the procedure without clearing the values. or the # button to save the new value. A confirmation tone sounds and the following text displays left-justified at the top of the display: Clearing values. 1. If you press the # button. the following text displays left-justified at the top of the display: Save new value? *=no #=yes 3. Do not press this button while pressing other keys/buttons. While the telephone is on-hook and idle. After entry of the command sequence. Press the # button to clear all values to their initial default values. Disable/Enable Debug Mode Use the following procedure to turn the debug mode for the button module serial port on or off. press the following sequence of keys on the faceplate of the telephone: Mute 3 3 2 8 4 # (Mute D E B U G #) Note: Press the Mute button momentarily. The telephone is cleared to its “out of the box” state. 2. 34 1600 Series IP Telephone Installation and Maintenance Guide . based on the current value of the system value NVDEBUG: If NVDEBUG = 1: Debug mode=on 0=off #=OK Debug mode=off 1=on #=OK Note: If NVDEBUG = 0: If a value different from the current NVDEBUG value is entered.

Group Identifier Group Identifier Use the following procedure to set or change the Group Identifier. If a value different from the current Group value is entered. see The GROUP System Value on page 50. Enter a valid Group value (0-999). or the # button to save the new value. Press the * button to terminate the procedure. The following text displays left-justified at the top of the display: Group=ddd New=_ where ddd is the Group value. 1. If you press the # button. the following text displays: New value being saved The new value is saved and the user interface is restored to its previous state. 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: Press the Mute button momentarily. the following text displays left-justified at the top of the display: Save new value? *=no #=yes 2. Note: Perform this procedure only if the LAN Administrator instructs you to do so. Note: Issue 1 April 2007 35 . Do not press this button while pressing other keys/buttons. For more information about groups. Note: While the telephone is on-hook and idle.

Local Administrative Options Interface Control Use the following procedure to set or change the interface control value. For example. the next sequential valid PHY1 value is selected and displayed as the status. defined as: ● ● ● ● ● Note: Status is auto when PHY1STAT = 1 Status is 10Mbps HDX when PHY1STAT = 2 Status is 10Mbps FDX when PHY1STAT = 3 Status is 100Mbps HDX when PHY1STAT = 4 Status is 100Mbps FDX when PHY1STAT = 5 3. pressing * changes the value to 3 (10Mbps FDX). telephones with an internal Ethernet switch display the following text. After entry of the command sequence. press the following sequence of keys on the faceplate of the telephone: Mute 4 6 8 # (Mute I N T #) Note: Press the Mute button momentarily. 36 1600 Series IP Telephone Installation and Maintenance Guide . press *. If the current value is 1000Mbps FDX (6). While the telephone is on-hook and idle. if the current value is 10Mbps HDX (2). To change the PHY1 value. Do not press this button while pressing other keys/buttons. pressing * changes the value to 1 (auto). 1. 2. Depending on the current value. depending on the current interface control value: PHY1=status *=change #=OK where status is the value of PHY1STAT.

If you press the # button. the following text displays: PHY2=status *=change #=OK where status is the value of PHY2STAT. Press the * button to terminate the procedure. Depending on the current value. The user interface is restored to its previous state. if the current value is 10Mbps HDX (2). defined as: ● ● ● ● ● ● Status is disabled when PHY2STAT = 0 Status is auto when PHY2STAT = 1 Status is 10Mbps HDX when PHY2STAT = 2 Status is 10Mbps FDX when PHY2STAT = 3 Status is 100Mbps HDX when PHY2STAT = 4 Status is 100Mbps FDX when PHY2STAT = 5 5. the following text displays. Press the * button to terminate the procedure. Issue 1 April 2007 37 . the next sequential valid PHY2 value is selected and displayed as the status. New value being saved The new values are saved and a restart occurs automatically. If you press the # button. To change the PHY2 value. For example. press *. The following text displays left-justified at the top of the display: Save new value? *=no #=yes 6. or the # button to save the new value. pressing * changes the value to 3 (10Mbps FDX). pressing * changes the value to 0 (disabled). or the # button to save the new values. If the current value is 1000Mbps FDX (6).Interface Control 4.

1. Depending on the current value.Local Administrative Options Disable/Enable Event Logging Use the following procedure to enable or disable logging of system events. pressing * changes the value to 0 (disabled). press *. If a value different from the current NVLOGSTAT value is entered. For example. if the current value is alerts (2). defined as: ● ● ● ● ● ● ● ● ● Note: 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. After entry of the command sequence. the next sequential valid NVLOGSTAT value is selected and displayed as the status. 2. press the following sequence of keys on the faceplate of the telephone: Mute 5 6 4 # (Mute L O G #) Note: Press the Mute button momentarily. the following text displays left-justified at the top of the display: Save new value? *=no #=yes 38 1600 Series IP Telephone Installation and Maintenance Guide . depending on the current value of the system parameter NVLOGSTAT: Log=status *=change #=OK where status is the type of logging indicated by the NVLOGSTAT value. While the telephone is on-hook and idle. the telephone displays the following text. To change the logging status. Do not press this button while pressing other keys/buttons. If the current value is debug (8). pressing * changes the value to 3 (critical).

While the telephone is on-hook and idle. the telephone unregisters from the call server. 2. Do not press this button while pressing other keys/buttons. a password and extension might be needed to log back on. ! CAUTION: CAUTION: Once a telephone is logged off. Press the * button to terminate the procedure. The telephone display (and button module display. After entry of the command sequence. If you press the # button. then displays the following prompt for subsequent login: Login Enter Extension Enter Extension and press Enter or OK Note: Issue 1 April 2007 39 . 1. Logoff Use the following procedure to log off a telephone. press the following sequence of keys on the faceplate of the telephone: Mute 5 6 4 6 3 3 # (Mute L O G O F F #) Note: Press the Mute button momentarily. the telephone displays the following text: New value being saved The telephone saves the new value. if applicable) clears. or the # button to save the new value.Logoff 4.

press #. 1. After entry of the command sequence. press *. To exit the language string display. A language string is any set of words or phrases on the IP Telephone user interface. To view the next language string. While the telephone is on-hook and idle. repeat Steps 3 and 4. press the Left navigation button. You can continue to press the Right navigation button to view the entire string. The text string of the language file currently selected displays as follows. To shift the language string one character to the right. 4. You can continue to press the Left navigation button to view the entire string. Note: Note: 40 1600 Series IP Telephone Installation and Maintenance Guide . press the Right navigation button. 2. 5. Do not press this button while pressing other keys/buttons. Choose one of the following actions: To shift the language string one character to the left.Local Administrative Options View Multi-Language Strings Use this procedure to scan the language strings available on the telephone. press the following sequence of keys on the faceplate of the telephone: Mute 6 5 7 # (Mute M L S #) Note: Press the Mute button momentarily. the telephone displays the following text: View text strings *=next #=Exit 3. To view the text string of the current language file. English displays instead: tag language string Note: The “tag” in the language string display is the label associated with a specific language in the downloaded language file. If no language file is being used or if a translation is not provided in the current language.

If you do not want to reset the system values. Issue 1 April 2007 41 . All telephones display the following text left-justified at the top of the display while the system values are reset to defaults: Resetting values. The telephone resets from the beginning of registration.Reset System Values Reset System Values Use the following procedure to reset all system initialization values to the application software default values. 2. press the following sequence of keys on the faceplate of the telephone: Mute 7 3 7 3 8 # (Mute R E S E T #) Note: Press the Mute button momentarily. Press the * button to continue without resetting the values and proceed to Step 4. The IP telephones display the following text left-justified at the top of the display: Reset values? *=no #=yes Note: ! CAUTION: CAUTION: As soon as you press the # button. press the # button to reset values to their defaults. Or. press * (no) and proceed to Step 4. ! CAUTION: CAUTION: This procedure erases all static information. 1. without any possibility of recovering the data. all static information will be erased. The following prompt displays on the top line: Are you sure? *=no #=yes 3. without any possibility of recovering the data. While the telephone is on-hook and idle. Do not press this button while pressing other keys/buttons. which takes a few minutes.

Note: 42 1600 Series IP Telephone Installation and Maintenance Guide . Press the * key to terminate the procedure without restarting the telephone. While the telephone is on-hook and idle. Press the # key to restart the telephone. See Appendix A: Restart Scenarios.Local Administrative Options 4. press # and perform the following Restart procedure. Once the system values are reset. Press the # button to reset values to their defaults. press the following sequence of keys on the faceplate of the telephone: Mute 7 3 7 3 8 # (Mute R E S E T #) Note: Press the Mute button momentarily. the following prompt displays on all IP telephones: Restart phone? *=no #=yes 3. The IP telephones display the following text left-justified at the top of the display: Reset values? *=no #=yes 2. The telephones display the following text left-justified at the top of the display while the system values are reset to defaults: Resetting values. The remainder of the procedure depends on the status of the boot and application files. Do not press this button while pressing other keys/buttons. or * to continue a restart without resetting the values to their defaults. Otherwise. 1. Restart the Telephone Use the following procedure to restart the telephone. Press the * key to terminate the procedure without restarting the telephone. the telephone displays the following prompt: Restart phone? *=no #=yes 5. If you do not reset the telephone.

If you press the # button. 1. If a value different from the current Group value is entered. If the current value is H. the telephone displays the following text: New value being saved The new value is saved. pressing * changes the value to 0 (default). Note: Perform this procedure only if the LAN Administrator instructs you to do so. A valid SIG Protocol Identifier is either 0 (default). the telephone displays the following text left-justified at the top of the display: Save new value? *=no #=yes 3. 1 (H. if the current value is SIP (2). press *. the next sequential valid SIG value is selected and displayed as the protocol. or the # button to save the new value. pressing * changes the value to 2 (SIP). The telephone displays the following text left-justified at the top of the display: SIG=protocol *=change #=OK where protocol is the telephone’s signaling protocol (H. press the following sequence of keys on the faceplate of the telephone: Mute 7 4 4 (Mute S I G) Note: Press the Mute button momentarily.323). Press the * button to terminate the procedure. All telephones display the following text left-justified at the top of the display: Restart phone? *=no #=yes Note: Note: Issue 1 April 2007 43 .323. and is not currently applicable to Release 1. Use the following procedure to set or change the Signaling Protocol Identifier.e.323 (1). While the telephone is on-hook and idle. Depending on the current value. I. SIP.. To change the SIG value. 2. or 2 (SIP). or default) corresponding to the numeric identifier (1.0. 2. Do not press this button while pressing other keys/buttons. or 0).Signaling Protocol Identifier Signaling Protocol Identifier Note: Note: This procedure is provided for future use only.

the following text displays left-justified at the top of the display: Save new value? *=no #=yes 3. if a value different from the current SSON value is entered. press the following sequence of keys on the faceplate of the telephone: Mute 7 7 6 6 # (Mute S S O N #) Note: Press the Mute button momentarily. the telephone displays the following text: New value being saved The telephone saves the new value. 1.Local Administrative Options 4. Do not press this button while pressing other keys/buttons. Perform this procedure only if you are using DHCP and the LAN administrator instructs you to do this. For all IP telephones. Site-Specific Option Number Setting ! CAUTION: CAUTION: Do not perform this procedure if you are using static addressing. 2. Press the * (asterisk) key to terminate the procedure without restarting the telephone. Use the following procedure to set the Site-Specific Option Number (SSON). Note: 44 1600 Series IP Telephone Installation and Maintenance Guide . or the # button to save the new value. See Appendix A: Restart Scenarios. Press the * button to terminate the procedure. Press the # (pound) key to restart the telephone. The remainder of this procedure depends on the status of the boot and application files. Enter a valid value between 128 and 255 for the SSON. If you press the # button. and restores the user interface to its previous state. While the telephone is on-hook and idle. The telephone displays the following text left-justified at the top of the display: SSON=ddd New=_ where ddd is the value of SSON.

For self-testing. The primary image. Do not press this button while pressing other keys/buttons. To invoke 1600 Series IP Telephone self-test procedures. Display of the block character helps to find bad display pixels. The backup image. use the following procedure: 1. Doing so generates a confirmation tone. and returns the user interface to its previous state. for 1 second after self-test is invoked: Self test #=end A block character with all pixels on then displays in all display character locations for 5 seconds. All telephones show the following text. press the # button on the dial pad at any time.Self-Test Procedure Self-Test Procedure Note: Note: 1600 Series IP Telephones store two software code images in reprogrammable non-volatile memory. press the following sequence of keys on the faceplate of the telephone: Mute 8 3 7 8 # (Mute T E S T #) Note: Press the Mute button momentarily. Issue 1 April 2007 45 . To terminate the self-test. The telephone displays one of the following: If self-test passes: Self test passed #=end Self test failed #=end Note: If self-test fails: 2. called the “big app” must be running to perform a self-test. left-justified at the top of the display. called the “little app” does not support the self-test.

Local Administrative Options 46 1600 Series IP Telephone Installation and Maintenance Guide .

Other useful information such as a ReadMe file and a settings file template to customize parameters and settings. The settings file contains the option settings that enable. The self-extracting executable file comes in both zipped and unzipped format. That bundle contains: ● An upgrade script file and a settings file. which tells the IP telephone whether the telephone needs to upgrade software. you have one “bundle” to download. Application files for all current 1600 Series IP Telephones. downloading a new telephone software version from the Avaya support Web site. The important files are: ● An upgrade script file.com/support. which allow you to upgrade to new software releases and new functionality without having to replace IP telephones. ● Issue 1 April 2007 47 . Note that the recommended configuration is the latest call server software and the latest IP telephone firmware. or otherwise customize the settings you might need to tailor the Avaya IP Telephones for your enterprise. 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. Other files are needed when the Avaya IP Telephones need an upgrade. ● ● Download File Content Two configuration files on the file server are important to understand. Currently.Chapter 4: Maintaining 1600 Series IP Telephones Introduction This chapter covers the maintaining the 1600 Series IP Telephones.avaya. The Avaya IP Telephones attempt to read this file whenever they reset. disable. The upgrade script file is also used to point to the settings file. for example.

You should not need to modify them. Restart the HTTP/HTTPS server.txt file as desired. We highly recommend that the settings file have the extension *. Reset your Avaya IP Telephones. The 4600 IP Telephones originally used *.com/support.txt file to a backup location.avaya. Back up all the current file server directories as applicable. 9600 Series IP Telephones.Maintaining 1600 Series IP Telephones Note: Note: You can use one settings file for all your Avaya IP Telephones including the 1600 Series IP Telephone. Download Procedure The Avaya-provided upgrade script files and the binaries included in the zip files upgrade the Avaya IP Telephones.” from http://www.scr to indicate a script file. However. This file allows the telephone to use default settings for customer-definable options. Copy your 46xxsettings. Remove all the files in the download directory. This ensures that you do not have an inappropriate binary or configuration file on the server. Note: Most Windows systems interpret the file extension *.txt.scr or 46xxsettings. we recommend that you: ● ● ● ● Stop the file server. Download the self-extracting executable file. these settings can also be changed with DHCP or in some cases. or the corresponding zip file. Modify the 46xxsettings. and 4600 Series IP Telephones. from the telephone’s dialpad itself. When downloading a new release onto a file server with an existing release already on it. Check the Readme files for release-specific information. Extract all the files. The only system values that can be used in the Conditional statement are: BOOTNAME.scr as a screen saver. Of course. Copy your 46xxsettings. and SIG.txt. sometimes called merely the “script file. In addition to the upgrade script and settings files. ● ● ● ● ● ● ● You can download a default upgrade script file.txt file back into the download directory. and must be called 46xxsettings. you need the latest binary code used in the Avaya IP Telephones. This file must reside in the same directory as the upgrade script file. GROUP. The Avaya IP Telephones can operate without this file. Note: 48 1600 Series IP Telephone Installation and Maintenance Guide . It is essential that all the binary files be together on the file server. you might want to open the default file and administer the options to add useful functionality to your Avaya IP Telephones.

txt file. If no such name exists. These lines cause the telephone to use HTTP/HTTPS to attempt to download the file specified in the GET command. If no such statement exists. of the form IF $name SEQ string GOTO tag. If Avaya changes the upgrade script file in the future. If the file is obtained. If the settings file is successfully obtained but does not include any setting changes the telephone stops using HTTP. the telephone looks for a 46xxsettings. All values must be text strings. That is how your settings are changed from the default settings. SET commands. For more details on customizing your settings file. which are statements with a “#” character in the first column.txt.scr file. even if the value itself is numeric. When the settings file contains no setting changes.Downloading Software Upgrades The settings file can include any of the five types of statements. Conditionals. the telephone does not go back to the upgrade script file. However. followed by a text string with no spaces. of the form GOTO tag. of the form SET parameter_name value. Tags. the telephone continues processing the upgrade script file. You can change the settings file name. The upgrade script file is processed so that if there is no 46xxsettings. the entire conditional is ignored. Issue 1 April 2007 49 . etc. Invalid values cause the specified value to be ignored for the associated parameter_name so the default or previously administered value is retained. if desired. Conditionals cause the Goto command to be processed if the value of name is a case-insensitive equivalent to string.scr and 46xxsettings. Goto commands. see Contents of the Settings File on page 50. ● ● ● Note: Note: The Avaya-provided upgrade script file includes lines that tell the telephone to GET 46xxsettings. any changes you have made will be lost. We strongly encourage you to use the 46xxsettings file to customize your settings instead. the rest of the settings file is ignored. one per line: ● ● Comments. before you make any changes. as long as you also edit the corresponding GET command in the upgrade script file. This happens when you initially download the script file template from the Avaya support Web site. a dotted decimal IP address. If the file cannot be obtained. we encourage you not to alter the Avaya-provided upgrade script file. Goto commands cause the telephone to continue interpreting the settings file at the next line after a # tag statement. Enclose all data in quotation marks for proper interpretation. which are comments that have exactly one space character after the initial #. its contents are interpreted as an additional script file.

The GROUP system value cannot be set in the 46xxsettings file.11 See Chapter 7 in the 1600 Series IP Telephone Administrator Guide for details about specific values. Your settings will vary from the settings shown. Use the GROUP system value for this purpose. you can remove the old language file using an empty SET LANGxFILE command in the 46xxsettings file before downloading a language file with the same filename. although specifying defaults is harmless. The GROUP System Value You might have different communities of end users. which might be an essential capability for “hot-desking” associates.yourco.com/home. Note: Downloading Language Files Language files must be stored in the same location as the 46xxsettings file or under the HTTP Server directory. 50 1600 Series IP Telephone Installation and Maintenance Guide . An example of what the file could look like follows. The simplest way to separate groups of users is to associate each of them with a number.wml SET WMLPROXY 11. We provide examples of the group settings for each of these situations later in this section. The GROUP system value can only be set on a telephone-by-telephone basis. You need only specify settings that vary from defaults. Alternately. defined using the SET HTTPDIR_HTTP server directory path command. etc. For example. SET DNSSRVR dnsexample. the 1600 Series IP Telephone looks for a 46xxsettings file. You can download a template for this file from the Avaya support Web site.Maintaining 1600 Series IP Telephones Contents of the Settings File After checking the application software. This sample assumes specification of a DNS Server. but which require different administered settings. turning off enhanced local dialing. Note: The following is intended only as a simple example. you might want to restrict Call Center agents from being able to Logoff. You can download a new language file version only if the filename differs from the language file previously downloaded. This optional file is under your control and is where you can identify non-default option settings. and a Web Browser. all of which have the same model telephone. application-specific parameters.com SET ENDIALSTAT 0 SET WMLHOME http://yourco.11.11.

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. and designate a number for each group. with 0 as the default. meaning your largest group would be assigned as Group 0.The GROUP System Value To do so. Then. 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 {specify settings unique to Group 1} goto END # HOTDESK {specify settings unique to Group 2} # END {specify settings common to all Groups} Issue 1 April 2007 51 . edit the configuration file to allow each telephone of the appropriate group to download its proper settings. The number can be any integer from 0 to 999. at each non-default telephone. first identify which telephones are associated with which group. Once the GROUP assignments are in place.

Maintaining 1600 Series IP Telephones 52 1600 Series IP Telephone Installation and Maintenance Guide .

Check LAN connectivity in both directions to all servers . The use of the V I E W option to view system values. ensure that the LAN is properly administered and is compliant with IEEE 803. HTTP. Consult the system administrator. HTTP. See Static Addressing Installation on page 27 for information. See The View Administrative Option on page 54 for more information. If the telephone is supposed to be powered from the LAN. 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. verify with the LAN administrator that IEEE power is indeed supported on the LAN. Use the ADDR option to verify IP addresses. Check the Avaya Web site to verify whether the correct files are being used. If you expect the telephone to be IEEE-powered.DHCP. make a note of the last message displayed. ● 3. If the 1600 Series IP Telephone is not communicating with the system (DHCP. This chapter contains the following sections: ● ● ● Descriptions of error conditions 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. 4.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. and methods for resolving them. ● 2. or Avaya Media Server).3af. Error and status messages. Check both the power and Ethernet wiring for the following conditions: ● ● Whether all components are plugged in correctly. DEFINITY®/MultiVantage™. Issue 1 April 2007 53 . HTTPS. as described in Table 2 and/or Table 3.

Do not press this key while pressing other keys. The View Administrative Option If you are using static addressing and encounter problems. The following text displays left-justified at the top of the display: View settings *=next #=exit Note: Note: Note: 54 1600 Series IP Telephone Installation and Maintenance Guide . restart the HTTP/HTTPS server. use the following procedure to verify the current values of system parameters and file versions. press the following sequence of keys on the faceplate of the telephone: Mute 8 4 3 9 # (Mute V I E W #) Note: Press the Mute button momentarily. Power Interruption If power to a 1600 Series IP Telephone is interrupted while the telephone is saving the application file. Verify whether you were provided with correct IP addresses. For more information about this option. See Static Addressing Installation in Chapter 3: Local Administrative Options.323 telephones do not send DTMF tones to non-H. the user can view but not change most of the parameters associated with Local Administrative Procedures. While the telephone is on-hook and idle. see the applicable user guide(s). If this occurs. Note: If the View Network Information option is not available due to being disabled by administration. The TN2302AP board does not pass in-band DTMF tones. Note: Unless otherwise prevented using administration.Troubleshooting Guidelines DTMF Tones H.323 telephones. 1. 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 IP addresses might have been entered incorrectly. the HTTP/HTTPS application can stop responding. use the ADDR option to view IP addresses.

9 ASCII numeric characters. Press the * button at any time during viewing to display the next name and system value pair or filename from Table 1. Values that cannot display on one line wrap to the next line.1Q tagging is off Up to 4 ASCII characters. Telephone Serial Number. 1 of 2 PWB comcode nnnnnnnnn PWB version ccccccccc MAC address L2 tagging hh:hh:hh:hh:hh:hh ccccccccc VLAN ID cccc IP address Subnet mask nnn.nnn Issue 1 April 2007 55 . up to 18 ASCII characters. Up to 15 ASCII characters: NETMASK value.1Q tagging is on or “none” of 802. Press the # button at any time during viewing to terminate the procedure and restore the user interface to its previous state. Up to 9 ASCII characters: “on” if NVL2Q = 1 “off” if NVL2Q = 2 “auto: on” if NVL2Q = 0 and 802.nnn.nnn nnn.nnn. 9 ASCII numeric characters.1Q tagging is off.1Q tagging is on “auto: off” if NVL2Q = 0 and 802.nnn. Up to 15 ASCII characters: IPADD value. Applies only to 16xx IP Telephones that have a software-readable PWB serial number and comcode. Value is L2QVLAN if 802.The View Administrative Option 2. The first pair returns after the last pair displays. Each octet of the MAC address displays as a pair of hexadecimal numbers. The names and values display in the following order: Table 1: Parameter Values Name Model Phone SN PWB SN System Value 16ccDccc cccccccccccccccccc cccccccccccccccccc Format Up to 8 ASCII characters: MODEL value. Applies only to 16xx IP Telephones that have a software-readable PWB serial number and comcode. Printed Wiring Board (circuit board) Serial Number.nnn. Applies to 16xx IP Telephones without a software-readable PWB serial number and comcode. up to 18 ASCII characters.

nnnnn 802. Version identifier of the GigE Adapter software. either"1000Mbps".0” if no file server was used successfully.nnn. 2 to 8 ASCII characters.nnnnn Format Up to 15 ASCII characters: the IP address of the router in use.nnn. 14 ASCII characters.nnn.0.323.” Pass-thru mode. Up to 21 ASCII characters: IP address and port of the call server currently in use. Up to 8 ASCII characters. Up to 3 ASCII numeric characters: GROUP value. or “No.1X If DOT1X = 0 If DOT1X = 1 If DOT1X = 2 nnn cccccccc filename.” 4 to 32 ASCII characters (primary application). otherwise “0. “100Mbps”.nnn. 14 ASCII characters. if applicable. Version identifier of the software in the first Button Module. “10Mbps”.nnn.0.0.nnn nnn. Pass-thru with Logoff.Troubleshooting Guidelines Table 1: Parameter Values (continued) Name Router File server System Value nnn.ext cccccccc Ethernet bootcodename Group Protocol: GigE Adapter cccccccccccccc Button Module 1 cccccccccccccc 56 1600 Series IP Telephone Installation and Maintenance Guide . currently only “H.0. Up to 21 ASCII characters: IP address and port of last file server used successfully during initialization or “0.nnn. Supplicant mode. if applicable. 2 of 2 Call server nnn.nnn.0.nnn.” 1 to 32 ASCII characters (backup image name).

MUTE V I E W. in the language specified by the LANGSYS parameter value. RESOLUTION: Follow the display prompts and reenter the 802. but the responding gatekeeper had no record of the call. RESOLUTION: Use static addressing to specify a router address. CAUSE: The telephone has detected an IP address conflict.1X Failure Cause/Resolution CAUSE: Incorrect credentials provided for authentication or not provided at all. If English is not the selected language. or another. or change administration on DHCP. which can issue messages in the local language outside the United States. Table 2: Possible Error and Status Messages During Installation of 1600 Series IP Telephones Message 802. or if the telephone is logged off. restart the telephone. RESOLUTION: Verify administration to identify duplicate IP address(es). RESOLUTION: Wait for the call to end. The telephone attempted to automatically register with the same. this may not be an error. or administer the telephone locally using the ADDR option. The most common exception is Extension in Use. for example. 1 of 4 Address Conflict Bad FileSv Address Bad Router? Call Error Contacting call server. as indicated in the 1600 Series IP Telephone Administrator Guide. Issue 1 April 2007 57 . Most of the messages in Table 2 display only for about 30 seconds. the telephone displays messages in English only when they are associated with local procedures. CAUSE: The HTTP/HTTPS server IP address in the IP telephone’s memory is all zeroes.. either administer the DHCP server with the proper address of the HTTP/HTTPS server. gatekeeper. perhaps due to a network outage or a gatekeeper problem. If appropriate. which requires manual intervention.1X ID and password. CAUSE: The telephone cannot find a router based on the information in the DHCP file for GIPADD. and then the telephone resets. RESOLUTION: Depending on the specific requirements of your network.Installation Error and Status Messages Installation Error and Status Messages The 1600 Series IP Telephones issue messages in English only.. CAUSE: The telephone has rebooted successfully and is moving on to attempt to register with the call server. The ADDR option is explained in Chapter 3: Local Administrative Options. The IP telephones also display messages from the switch. The 1600 Series IP Telephones issue messages in the currently selected language. and if the telephone does not automatically register. RESOLUTION: Allow the telephone to continue. CAUSE: The user was on a call when the connection to the gatekeeper went down.

Contact Avaya. verify with the LAN Administrator that a DHCP server is appropriately administered on the network. Then press * to reset the telephone and enter a different extension and password.bbb. RESOLUTION: Confirm the extension is correct and is correctly administered on the switch. “100Mbps” or “10Mbps” message. CAUSE: Downloaded application file was not downloaded or saved correctly. taking particular care to enter the extension accurately. The 1600 Series IP Telephone prompts you again for the extension and password. RESOLUTION: If this message appears for more than a few seconds. RESOLUTION: You can force the current telephone to register. CAUSE: The telephone is proceeding through boot-up. RESOLUTION: Review DHCP server administration to identify duplicate IP address(es). CAUSE: The 16xx telephone is attempting to find a DHCP server and the user is not allowed to view IP addresses. CAUSE: Incompatible emergency option. quickly press the * (asterisk) button. Press # to unregister the original user and to register the current telephone. and thereby disconnect the other user. To break into the Discovering process. RESOLUTION: This should never happen.. CAUSE: The call server detects an extension conflict with an existing set or Softphone. and when you see the "1000Mbps". 58 1600 Series IP Telephone Installation and Maintenance Guide . CAUSE: The telephone is attempting to find a DHCP server. and when you see the “100Mbs” or “10Mbs” message. repair required Emergency Option Extension Error Extension in Use Finding router. CAUSE: The call server does not recognize the extension entered. Then try registration again.ddd Discovering. you are asked to confirm that you want to unregister the original user. RESOLUTION: If this message appears for more than a few seconds.Troubleshooting Guidelines Table 2: Possible Error and Status Messages During Installation of 1600 Series IP Telephones (continued) Message DHCP: CONFLICT * to program Cause/Resolution CAUSE: At least one of the IP address offered by the DHCP server conflicts with another address. EEPROM error.. press the # button. 2 of 4 Discover aaa. If there is not supposed to be a DHCP server. you must “break into” the Discovering process and use static addressing.. verify with the LAN Administrator that a DHCP server is appropriately administered on the network. by pressing #. quickly press the * (asterisk) button. and the user is allowed to view IP addresses. RESOLUTION: The telephone automatically resets and attempts to re-initialize. press the # button. you must “break into” the Discovering process and use static addressing. If you enter the same extension and password.ccc. See Static Addressing Installation on page 27. See Static Addressing Installation on page 27. If there is not supposed to be a DHCP server. To break into the Discovering process. RESOLUTION: Allow the telephone to continue..

CAUSE: DEFINITY Release 8. RESOLUTION: Check power and cabling. RESOLUTION: Review gatekeeper/call server administrations.323 station extension for this telephone. CAUSE: This release of the call server does not support the current version of the IP telephone. Since the 1600 Series IP Telephones are not supported on DEFINITY Release 8. CAUSE: The call server does not support IP telephony. you must upgrade to a release that does support these telephones. RESOLUTION: Contact Avaya to upgrade your license. CAUSE: When first plugged in. No Ethernet Issue 1 April 2007 59 . and that the proper application file is located in the appropriate location on the HTTP/HTTPS server. RESOLUTION: Verify the connection to the Ethernet jack. RESOLUTION: Unregister telephones not in use. RESOLUTION: On the station administration screen.. Contact Avaya. the IP telephone is unable to communicate with the Ethernet. RESOLUTION: This should never happen.. including IP network parameters. or contact Avaya to upgrade your license. ensure the DCP set being aliased for this IP telephone has an H. CAUSE: The telephone does not have sufficient room to store the downloaded file. Trying to reestablish. which the 1600 Series IP Telephones do not support. CAUSE: The gatekeeper reports an invalid IP address. CAUSE: The call server has reached its limit of IP stations. 3 of 4 Gateway Error Incompatible Invalid file IP Address Error License Error Limit Error NAPT Error Network connectivity has been lost. verify the jack is Category 5.Installation Error and Status Messages Table 2: Possible Error and Status Messages During Installation of 1600 Series IP Telephones (continued) Message Gatekeeper Error Cause/Resolution CAUSE: The gatekeeper rejects the registration attempt for an unspecified reason. verify power is applied on the LAN to that jack. in accordance with switch administration instructions. RESOLUTION: Contact the System Administrator to remove or re-administer the device. CAUSE: The telephone has detected a loss of signal on the Ethernet interface lasting longer than about one second. RESOLUTION: Upgrade to the current version of Avaya Communication Manager (4. etc.323 station extension administered.4.4 does not have an H. RESOLUTION: Verify the proper filename is administered in the script file. CAUSE: A device between the telephone and the call server is invoking Network Address Port Translation.0 or greater) software.

then try registration again. Subnet conflict System busy System Error Undefined Error Updating: DO NOT UNPLUG THE TELEPHONE Wrong Set Type 60 1600 Series IP Telephone Installation and Maintenance Guide . reboot the telephone. or administer network equipment to administer the telephone appropriately.. CAUSE: The call server has an unspecified problem. RESOLUTION: Administer an IP address on the telephone using Static Addressing Installation. CAUSE: The telephone is in the initial stage of rebooting. RESOLUTION: The telephone was attempting to access a network resource (DHCP server. network resource is unavailable.. 4 of 4 Password Error Request Error Restarting. the number of IP endpoints on the call server is already at maximum. contact the System Administrator. CAUSE: Most likely. RESOLUTION: Confirm the password is correct. CAUSE: The call server does not recognize the password entered. CAUSE: The telephone is not on the same VLAN subnet as the router. If the condition persists. CAUSE: The gatekeeper believes the telephone’s registration request is improperly formatted. RESOLUTION: The telephone will automatically attempt to register with the next gatekeeper on its list. taking particular care to enter the password accurately. verify that addressing is accurate and that a communication path exists in both directions between the telephone and the resource. or the call server) and was not successful. RESOLUTION: Allow the telephone to continue.Troubleshooting Guidelines Table 2: Possible Error and Status Messages During Installation of 1600 Series IP Telephones (continued) Message Packet Error Cause/Resolution CAUSE: Protocol timeout error. If the resource appears operational and properly linked to the network. CAUSE: The call server does not recognize the set type. RESOLUTION: Consult your Avaya Media Server administration and troubleshooting documentation. Less likely. RESOLUTION: Ensure the call server is properly administered to expect the appropriate telephone for the IP address and extension. RESOLUTION: Allow the telephone to continue. Check the resource being called upon for its availability. CAUSE: The call server has rejected registration for an unspecified reason. CAUSE: The telephone is updating its software image. RESOLUTION: Reenter the correct extension and password. If the problem persists. HTTP server. RESOLUTION: Consult your Avaya Media Server administration and troubleshooting documentation.

CAUSE: This might be a firmware fault because the MAC address in memory is corrupted. as appropriate. For example. The telephone stops working in the middle of a call. RESOLUTION: As above. CAUSE: This is a hardware fault. the power supply. server administration. Cause/Resolution CAUSE: The telephone cannot find the call server. Table 3: Operational Error Conditions for 1600 Series IP Telephones Condition The telephone continually reboots. Issue 1 April 2007 61 . RESOLUTION: The telephone must be returned to Avaya for repair. and the power jack. Most of the problems reported by 1600 Series IP Telephone users are not likely to be problems with the telephone itself. 1 of 6 The message light on the telephone turns on and off intermittently. where Quality of Service. verify that either static addressing was not used or that any changes to static addresses were entered correctly. CAUSE: Loss of power. or reboots continuously about every 15 minutes. Problems are more likely LAN-based.Operational Errors and Status Messages Operational Errors and Status Messages Table 3 identifies some of the possible operational problems that might be encountered after successful 1600 Series IP Telephone installation. or DHCP server not available when telephone attempts to renegotiate DHCP lease. RESOLUTION: Return the telephone to Avaya for repair. AND no lights are lit on the telephone and the display is not lit. CAUSE: Loss of path to Avaya Media Server. AND power to the telephone is fine (and the telephone might have gone through the restarting sequence). and other issues can impact end-user perception of IP telephone performance. but the telephone never registers. DHCP Lease expired. RESOLUTION: Ensure that MCIPADD is administered either manually or through DHCP or HTTP. The user guide for a specific telephone model also contains troubleshooting for users having problems with specific IP telephone applications. RESOLUTION: Check the connections between the telephone.

or the LAN equipment (routers. AND no lights are lit on the telephone and the display is not lit. Verify the telephone volume is set high enough. etc. and the power jack. RESOLUTION: Check LAN continuity from the call server to the telephone using ARP or trace-route and from the telephone to the call server by invoking a Feature button. RESOLUTION: As above. CAUSE: Loss of communication with the call server.Troubleshooting Guidelines Table 3: Operational Error Conditions for 1600 Series IP Telephones (continued) Condition The telephone was working. but there is no dial tone. Verify no one changed the telephone settings locally using the VIEW and ADDR codes.) between the switch and the telephone. CAUSE: Loss of communication with the call server. conduct a self-test. RESOLUTION: Check the connections between the telephone. as described earlier in this guide. 2 of 6 62 1600 Series IP Telephone Installation and Maintenance Guide . The display might show “System Busy. add or change NAT. If so. RESOLUTION: As above. the new server or switch might need to be administered to support the telephone. TN 2302AP boards. AND power to the telephone is fine. Verify that LAN administration has not changed for the Gatekeeper. Finally.” Cause/Resolution CAUSE: Loss of power. re-administer the Avaya Media Server. the power supply. or even a different call server switch. CAUSE: Loss of communication with the call server. but does not work now. AND the telephone was recently moved. servers. but pay particular attention to the possibility that the telephone is being routed to a different DHCP server. etc. AND the network was recently changed to upgrade or replace servers.

clipped or garbled speech. CAUSE: Room acoustics. CAUSE: The user has changed the Automatic Gain Control (AGC) or environmental acoustics are not consistent with the current audio settings. 3 of 6 Issue 1 April 2007 63 . We recommend the M12LU. RESOLUTION: Try different on/off settings for the AGCHAND. The telephone works properly except for the Speaker. RESOLUTION: You can have the user provide diagnostic data by invoking the Network Information feature under the A (Avaya) button on the telephone. etc. specifically: the user hears echo when speaking on a handset. CAUSE: Improper non-Category 5 wiring. do a self-test on the telephone. AGCHEAD. but the far-end hears echo. RESOLUTION: Replace non-Category 5 wiring with Category 5 wiring. or when a call goes from no one talking abruptly to a loud voice. the user is on Speaker and hears no echo. but not on a handset. CAUSE: The Speaker was turned off at the call server. and AGCSPKR parameters. and swap the trunk’s Trunk Termination parameter on the call server. If that is insufficient. RESOLUTION: Ensure that there are six inches or so of blank space to the right of the telephone. use the handset. CAUSE: Improper headset adapter.Operational Errors and Status Messages Table 3: Operational Error Conditions for 1600 Series IP Telephones (continued) Condition The telephone works. or static. dropped packets. the user hears fluctuations in the volume level which are worse when the Speaker is on. RESOLUTION: Administer the call server to allow that station’s Speaker to operate. CAUSE: Jitter. the user experiences sudden silences such as gaps in speech. RESOLUTION: Replace adapter with Avaya’s M12LU or 3412-HIC adapters. Cause/Resolution the user hears echo on a headset. RESOLUTION: Verify which trunk is causing the echo. since it supports Automatic Gain Control. as explained in the Self-Test Procedure on page 45. or at the beginning of a call. If that does not work. but the audio quality is poor. delay. etc. One or more Quality of Service (QoS) features should be implemented in the network as covered in Chapter 3: Local Administrative Options. CAUSE: Echo from digital-to-analog conversion on your Avaya Media Server trunk.

Some UNIX applications only terminate lines with <Line Feed>. answers a call using the Speaker and switches to the handset. The HTTP/HTTPS script file and settings file are ignored (not being used by the telephone). and thus be ignored. except incoming DTMF tones are not received.txt file from the Avaya support Web site at http://www. A second call is ignored if it comes in while a call is in progress.txt file was edited incorrectly. 64 1600 Series IP Telephone Installation and Maintenance Guide . or enter a valid address for TLSSRVR. and the only current resolution is to disable HFA. CAUSE: call server suppresses sidetone DTMF. 4 of 6 The telephone works properly. CAUSE: HFA only works if the telephone is idle. CAUSE: The telephone expects lines of the script file to terminate with a <Carriage Return> <Line Feed>. Customize or change only the 46xxsettings file. AND telephone administration recently changed. Hands-Free Answer (HFA) is administered but the telephone did not automatically answer a call. and do not edit or rename it. on the Change-System-Parameters screen. RESOLUTION: On call server administration. etc. RESOLUTION: Change AUTH to 0 (zero). RESOLUTION: Edit the script file with a Windows®-based editor. enable On-Hook Dialing. Doing so causes the entire file to be treated as a comment. The HTTP/HTTPS script file is ignored or not used by the telephone. RESOLUTION: None. RESOLUTION: Download a clean copy of the 16xxupgrade. If the user has Hands-Free Answer (HFA).com/support.avaya. AND the HTTP/ HTTPS server is a LINUX or UNIX system. This is a known bug. CAUSE: The 16xxupgrade. except sidetone DTMF is not heard. including ringing before the first call is answered. CAUSE: The system value AUTH is set to 1 (HTTPS required) but no valid address is specified in TLSSRVR. RESOLUTION: None. the board is operating as designed. pressing dialpad buttons does not send DTMF tones. renamed. or another editor that does not strip out the <Carriage Return>.Troubleshooting Guidelines Table 3: Operational Error Conditions for 1600 Series IP Telephones (continued) Condition The telephone works properly. Editing the script file with a UNIX-based editor can strip <Carriage Return>s from the file. CAUSE: UNIX and LINUX systems use case-sensitive addressing and file labels. RESOLUTION: Verify the file names and path in the script file are accurately specified. as discussed in Chapter 4: Maintaining 1600 Series IP Telephones. Cause/Resolution CAUSE: The TN2302AP board does not pass in-band DTMF tones.

Issue 1 April 2007 65 . AND the setting being ignored is one or more of the AGC settings. which were placed in the backup/restore file of the user. CAUSE: The HTTP/HTTPS server stops responding if power is interrupted while a telephone is saving the application file. CAUSE: The second telephone is unable to access the backup file. The user indicates an application or option is not available. Then. Again. or the backup file can be edited to delete the custom AGC settings. Some settings in the settings file are being ignored while other settings are being used properly. 5 of 6 Telephone power is interrupted while the telephone is saving the application file and the HTTP/HTTPS application stops responding. including case if your file server is UNIX or LINUX. CAUSE: The 46xxsettings script file is not pointed to accurately. as applicable. RESOLUTION: Assuming the user is meant to have that application. RESOLUTION: The user can reset the AGC value(s) back to the desired setting(s). and extension. Then verify that the second telephone is administered to retrieve data from the same location as the first telephone. or is not properly administered to allow the application. Cause/Resolution CAUSE: Improper settings file administration. RESOLUTION: Verify that the first telephone created a backup file by checking that the appropriate administration was done in accordance with Chapter 7 of the 1600 Series IP Telephones Administrator Guide. verify all the relevant parameters indicated in Table 7 of the 1600 Series IP Telephones Administrator Guide. RESOLUTION: Restart the HTTP/HTTPS server. verify the 46xxsettings script file is properly specified for your system.Operational Errors and Status Messages Table 3: Operational Error Conditions for 1600 Series IP Telephones (continued) Condition Some settings in the settings file are being ignored while other settings are being used properly. Finally. are accurately specified in the 46xxsettings file. RESOLUTION: Verify that customized settings are correctly spelled and formatted. check that the appropriate administration was done in accordance with Chapter 7 of the 1600 Series IP Telephones Administrator Guide. CAUSE: The user changed the AGC setting(s). User data disappeared when the user logged off one telephone and logged into another telephone. verify that the HTTP server on which the backup file is located is operational and accessible from the second telephone.

Troubleshooting Guidelines Table 3: Operational Error Conditions for 1600 Series IP Telephones (continued) Condition The user reports SBM32 buttons are not labeled when they should be. CAUSE: The user has been pressing the SBM32 button to indicate which button to relabel. Cause/Resolution CAUSE: Improper administration on the call server. scroll to highlight the desired button label. The user reports personalized labels cannot be placed on the SBM32 buttons. CAUSE: Improper administration on the call server. RESOLUTION: Verify correct administration. 6 of 6 66 1600 Series IP Telephone Installation and Maintenance Guide . AND the user has tried using the Personalize Labels option on the telephone. and press either OK or the corresponding 1616 line button. RESOLUTION: The user should use the list displayed on the telephone. RESOLUTION: Verify correct administration. AND the user has tried using the Program AD button feature.

Do not press this key while pressing other keys. Your particular file names are likely to be different. Note: Restart the Telephone Use the following procedure to restart the telephone. press the following sequence of keys on the faceplate of the telephone: Mute 7 3 7 3 8 # (Mute R E S E T #) Note: Press the Mute button momentarily. 1. Note: The file names used in this appendix are examples only. Once the system values are reset. This appendix explains the different scenarios possible. While the telephone is on-hook and idle. The following text displays left-justified at the top of the display while the system values are reset to defaults: Resetting values.Appendix A: Restart Scenarios Scenarios for the Restart Process The sequence of the restart process depends on the status of the boot and application files. the following prompt displays: Restart phone? #=yes *=no Note: Issue 1 April 2007 67 . Press the # button to continue the procedure. The following text displays left-justified at the top of the display: Reset values? #=yes *=no 2.

Restart Scenarios 3. Press the # key to restart the telephone. The telephone displays: Restarting. The remainder of the procedure depends on the status of the boot and application files: If this condition applies: Boot File Needs to be Upgraded Latest Boot File Loaded/No Application File or Application File Needs to be Upgraded Latest Boot File and System-Specific Application File Already Loaded See: Boot File Needs to be Upgraded on page 68. While the hardware is being initialized. Latest Boot File Loaded/No Application File or Application File Needs to be Upgraded on page 71. these messages appear: 1. 68 1600 Series IP Telephone Installation and Maintenance Guide .. 2. Latest Boot File and System-Specific Application File Already Loaded on page 72. the telephone displays: Loading: 5 secs replboot_v3. the telephone displays: Initializing 3. Boot File Needs to be Upgraded The telephone automatically downloads an upgraded boot file if applicable. While either the application file if there is one or the boot code is uncompressed into RAM.app 4084KB This message counts the seconds as the application file (replboot_v3. Press the * key to terminate the procedure without restarting the telephone. In this case.app in this example) is being written into RAM..

. The message No Ethernet displays until the software determines whether the interface is 10 Mbps or 100 Mbps. In this scenario. it is discovered that sufficient information has not been downloaded. Note: The Ethernet speed indicated is the LAN interface speed for both the telephone and any attached PC. until DHCP successfully completes. or 100.. that is. 8. 6.. The telephone displays the speed of the Ethernet interface in Mbps. the telephone displays the following message: HTTP:n ipadd Note: where n is the number of the IP address obtained from the HTTP server and ipadd is the IP address. DO NOT UNPLUG THE PHONE! This message continues while the new boot code is being written into RAM. The following message displays while the DHCP process is invoked: DHCP: 0 secs * to program The number of elapsed seconds is incremented once per second. Updating boot code. 7. until the HTTP server responds. Issue 1 April 2007 69 . 0. 10. While the IP telephone establishes a TCP connection to the HTTP server. When control is passed to the software that was just loaded. assuming the administrator has not disabled the latter interface through the PHY2STAT setting. The software determines whether sufficient IP address information was downloaded. the following messages display: Starting.Scenarios for the Restart Process 4.. The following message displays while the HTTP process is invoked: HTTP: n uri The number increments once per second. 5.

x secs where n is the percentage of the file stored.. The following message displays while the application file is downloaded into RAM: app_filename n KB received where n is the number of KBs downloaded. 13. the telephone displays: Updating. This usually takes longer than the file download. x secs where n is the percentage of boot code rewritten and x is the number of elapsed seconds during rewriting.. The script file is processed. The software determines that the telephone’s boot code file name (BOOTNAME) is not the latest version. 10. When the new boot code is successfully written into the flash memory. n%. While the upgrade script file is being downloaded. The following message displays while the application file is stored in flash memory: Saving to flash n%. The application then resets the telephone so the latest system-specific application file can be downloaded. APPNAME is set to the name of an application file to replace the boot code.. and x is the number of elapsed seconds. 70 1600 Series IP Telephone Installation and Maintenance Guide . 15. the application corrupts its own checksum stored in flash. Continue with the next procedure. The following message displays while the telephone is reset so the application file can be executed: Restarting. sc is the status code of the HTTP response and etag is the value of the ETag header. all IP telephones display the following message: HTTP:n sc etag where n is the number of the IP address obtained from the HTTP server. 12. 14. 11. While the boot code is rewritten.Restart Scenarios 9..

1. The telephone detects and displays the speed of the Ethernet interface in Mbps. the telephone displays the following message: HTTP:n ipadd Note: where n is the number of the IP address obtained from the HTTP server and ipadd is the IP address. Issue 1 April 2007 71 . 5... The telephone displays: Restarting. 0. The following message displays while the DHCP process is invoked: DHCP: 0 secs * to program The number of elapsed seconds is incremented once per second. 10. 2. While the IP telephone establishes a TCP connection to the HTTP server. The message No Ethernet displays until the software determines whether the interface is 10 Mbps or 100 Mbps. In this scenario. The software determines whether sufficient IP address information was downloaded. The following message displays while the HTTP process is invoked: HTTP: n uri The number increments once per second. until the HTTP server responds. Note: The Ethernet speed indicated is the LAN interface speed for both the telephone and any attached PC. it is discovered that sufficient information has not been downloaded. 4. or 100. until DHCP successfully completes. 3.Scenarios for the Restart Process Latest Boot File Loaded/No Application File or Application File Needs to be Upgraded This procedure occurs with normal application file upgrades. that is.

The following message displays while the application file is stored in flash memory: Saving to flash n%. 9.. all IP telephones display the following message: HTTP:n sc etag where n is the number of the IP address obtained from the HTTP server. and x is the number of elapsed seconds. Note: The Ethernet speed indicated is the LAN interface speed for both the telephone and any attached PC. The following message displays while the application file is downloaded into RAM: app_filename n KB received where n is the number of KBs downloaded. Continue with the next procedure.Restart Scenarios 6. The telephone is reset so the new system-specific application file can be executed. 7.. 10. The telephone detects and displays the speed of the Ethernet interface in Mbps. 1. This usually takes longer than the file’s download. sc is the status code of the HTTP response and etag is the value of the ETag header. 8. 2. 10. The message No Ethernet displays until the software determines whether the interface is 10 Mbps or 100 Mbps. that is. The software determines that the name of the boot code file in the telephone (BOOTNAME) is not the latest version. The script file is processed. 0. or 100. APPNAME is set to the name of an application file to replace the boot code. x secs where n is the percentage of the file that was stored. Latest Boot File and System-Specific Application File Already Loaded This happens with normal resets. Note: 72 1600 Series IP Telephone Installation and Maintenance Guide . The telephone displays: Restarting. While the upgrade script file is being downloaded from the HTTP server.

While the IP telephone establishes a TCP connection to the HTTP server. 4. The following message displays while the DHCP process is invoked: DHCP: 0 secs * to program The number of elapsed seconds is incremented once per second. The software determines whether sufficient IP address information was downloaded. 7. 5. sc is the status code of the HTTP response and etag is the value of the ETag header. all IP telephones display the following message: HTTP:n sc etag where n is the number of the IP address obtained from the HTTP server. and the name of the application file in the telephone is the same as APPNAME. When registration finishes. 8.Scenarios for the Restart Process 3. In this scenario. a dial tone is available on the telephone. 6. While the upgrade script file is being downloaded from the HTTP server. until DHCP successfully completes. Issue 1 April 2007 73 . The script file is processed. The following message displays while the HTTP process is invoked: HTTP: n uri The number increments once per second. 9. it is discovered that sufficient information has not been downloaded. the telephone displays the following message: HTTP:n ipadd where n is the number of the IP address obtained from the HTTP server and ipadd is the IP address. System-specific registration with the Avaya media server is invoked. until the HTTP server responds. The software determines that the name of the boot code file in the telephone (BOOTNAME) is the latest version.

Restart Scenarios 74 1600 Series IP Telephone Installation and Maintenance Guide .

A TCP/IP-based protocol for VoIP signaling.1Q defines a layer 2 frame structure that supports VLAN identification and a QoS mechanism usually referred to as 802. Virtual LAN. an IETF standard for ASCII strings to represent IP addresses. to verify that the IP address provided by the DHCP server is not in use by another IP telephone. Control LAN. Registration with Avaya Communication Manager by an IP telephone with no extension. In DHCP.1D 802. used. type of Gatekeeper circuit pack. Applicable 1600 Series IP Telephones support IEEE 802. Transport Layer Security.1D. The Domain Name System (DNS) is a distributed Internet directory service. ID of an endpoint. H. Media Access Control. Local Area Network. Avaya 1600 Series IP Telephones can use DNS to resolve names into IP addresses. TFTP.1X 802. the organization that produces standards for communications on the internet. DNS names can be used wherever IP addresses were available as long as a valid DNS server is identified first. Registration with Avaya Communication Manager by an IP telephone with no extension. Voice over IP. and managerial functions in the media server. DNS is used mostly to translate between domain names and IP addresses. used to request and transmit pages on the World Wide Web. A secure version of HTTP.1Q 802. Allows limited outgoing calling. Domain Name System. and HTTP files. Hypertext Transfer Protocol. used to refer to several mechanisms intended to improve audio quality over packet-based networks. a class of technology for sending audio data and signaling over LANs. Authentication method for a protocol requiring a network device to authenticate with a back-end Authentication Server before gaining network access. an IP-based QoS mechanism. Allows limited outgoing calling. Quality of Service. administrative.1X for pass-through and for Supplicant operation with the EAP-MD5 authentication method. Dynamic Host Configuration Protocol. Address Resolution Protocol. TLS is compatible with SSL 3. for example. ARP CLAN DHCP DiffServ DNS Gatekeeper H.323 HTTP HTTPS IETF LAN MAC QoS Unnamed Registration TLS Unnamed Registration VLAN VoIP Issue 1 April 2007 75 . Sometimes called CLAN in Avaya documents.Appendix B: Glossary of Terms Terms Used in This Guide 802. an IETF protocol used to automate IP address allocation and management. Differentiated Services. an enhancement of Secure Sockets Layer (SSL). Internet Engineering Task Force.323 application that performs essential control.0 and allows for privacy and data integrity between two communicating applications.

Glossary of Terms 76 1600 Series IP Telephone Installation and Maintenance Guide .

Droms (RFC 2132) RTP: A Transport Protocol for Real-Time Applications (RTP/RTCP). November.org/rfc. Alexander and R. by David C. by J. November 1982. 1980. edited by K. Postel (STD 5: RFC 950) Broadcasting Internet Datagrams. Mockapetris (STD 13: RFC 1035) An Ethernet Address Resolution Protocol (ARP). by P. (DIFFSRV). September 1981. by J. by J. Jacobson (RFC 1889) Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers. January 1996. Plummer (STD 37: RFC 826) Dynamic Host Configuration Protocol (DHCP). Postel (STD 6: RFC 768) Transmission Control Protocol (TCP). V. 1987. Nichols. December 1998. by J. by H. Blake. October 1984. as amended by Internet Standard Subnetting Procedure. March 1997. by S. November 1987. March 1997. Casner. March 1991. October 1989. Mogul (STD 5: RFC 919) Broadcasting Internet Datagrams in the Presence of Subnets. Schulzrinne. Mogul and J. Mockapetris (STD 13: RFC 1034) Domain Names . Baker and D. by P. Rose (RFC 1213) ● ● ● ● ● ● ● ● ● ● ● ● ● ● Issue 1 April 2007 77 . Droms (RFC 2131) DHCP Options and BOOTP Vendor Extensions. October 1984. Braden (STD 3: RFC 1122) Requirements for Internet Hosts . ● Requirements for Internet Hosts . Braden (STD 3: RFC 1123) Internet Protocol (IP). by Information Sciences Institute (STD 5: RFC 791). R. by R.Implementation and Specification (DNS). August 28.Appendix C: Related Documentation IETF Documents The following documents provide standards relevant to IP Telephony and are available for free from the IETF Web site: http://www. August 1985.html. McCloghrie and M. Black (RFC 2474) Management Information Base for Network Management of TCP/IP Internets: MIB-II.ietf.Concepts and Facilities (DNS). Mogul (STD 5: RFC 922) User Datagram Protocol (UDP). by R. by R. Frederick. by Information Sciences Institute (STD 7: RFC 793) Domain Names . September 1981. by K. S. October 1989. F.Communication Layers. S.Application and Support.

Berson.245.0. Pulse Code Modulation (PCM) of Voice Frequencies.729. Coding of speech at 8 kbit/s using Conjugate-Structure Algebraic-Code-Excited Linear-Prediction (CS-ACELP). Dierks and C. by T. Allen (RFC 2246) ● ● ● ITU Documents The following documents are available for a fee from the ITU Web site: http://www.729 optimized for terminals conforming to Recommendation V. by R.int. L. Schoenwaelder (RFC 2578) Resource ReSerVation Protocol VI. April 1999.722.729: A silence compression scheme for G. January 1999.70. S. February 1998 Recommendation H. and S.323. S. McCloghrie (RFC 2011) Structure of Management Information Version 2 (SMIv2). February 1998 ● ● ● ● ● ● ● 78 1600 Series IP Telephone Installation and Maintenance Guide . ● Recommendation G. November 1988 Recommendation G. Packet-based multimedia communications systems.Related Documentation ● SNMPv2 Management Information Base for the Internet Protocol using SMIv2.225. edited by K. November 1996 Annex B to Recommendation G. November 1996 Recommendation H. Jamin (RFC 2205) The TLS Protocol Version 1.itu. Zhang. McCloghrie. 7 kHz Audio-Coding within 64 kbit/s. Braden. Control protocol for multimedia communication. and J. Herzog.0. February 1998 Recommendation H. Perkins. Call signalling protocols and media stream packetization for packet-based multimedia communications systems.711. D. November 1996.729: Reduced complexity 8 kbit/s CS-ACELP speech codec. September 1997. edited by K. November 1988 Recommendation G. March 1996 Annex A to Recommendation G.

Telecommunications and information exchange between systems .1Q-1998.Specific requirements. 1998 Edition. IEEE Standards for Local and Metropolitan Area Networks: Virtual Bridged Local Area Networks IEEE Std 802.Local and metropolitan area networks.Part 2: Logical Link Control ISO/IEC 15802-3: 1998 ANSI/IEEE Std 802.iec.Local and metropolitan area networksSpecific requirements. 1998 Edition.Part 3: Media Access Control (MAC) Bridges IEEE Std 802.ch. Information technologyTelecommunications and information exchange between systems. ● International Standard ISO/IEC 8802-2:1998 ANSI/IEEE Std 802.Local and metropolitan area networks.Telecommunications and information exchange between systems.1D.ISO/IEC.Amendment: Data Terminal Equipment (DTE) Power via Media Dependent Interface (MDI) ● ● ● Issue 1 April 2007 79 .2.Common specifications. Information technology . ANSI/IEEE Documents The following documents are available for a fee from the ISO/IEC standards Web site: http://www.3af-2003.Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications. IEEE Standard for Information technology.

Related Documentation 80 1600 Series IP Telephone Installation and Maintenance Guide .

. . 27 . . . . . . . . . . Numerical 1600 Series IP Telephone Assembling the . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 I IEC/ISO Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 36 . . . . . . . . . . . . . . . .9 79 78 . . . IP Telephone Models . . . . 6 47 Maintaining 1600 Series IP Telephones . . . . . . . Dynamic Addressing Process . . . . . . . AGC . . . . 9 . . . . .11 42 . . . . . . . . . . . . . ADDR Option . . . . . . . Administrative Options Entering Data for . . . . . . . . . . . . . . . . . . . . . . . . ISO/IEC.Index Index Download Procedure . . 30 38 24 57 53 38 A About This Guide . . . . . . . . . . . Setting the . . . . 47 . . . . Downloading . . . . . . . . . . Connection Jacks for 1603 Series IP Telephones Connection Jacks for 1608 Series IP Telephones Connection Jacks for 1616 Series IP Telephones Contents of the Settings File . . . . . IEEE/ANSI Documents . . . . . . . . . . . . . . . . . 9 12 E Enable Automatic Gain Control (AGC) . . . . . . . 48 50 47 54 17 . . . . Enable Event Logging . . Local . 24 23 30 79 12 30 G Glossary of Terms . . . . . . . . Local Administrative Options . . . . . . . . . . . . . . . . . . . .9 . . . . . 75 Group Identifier . . . . Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . Assembling the 1600 Series IP Telephone . . . . . . . . . . . . . . . . . Clear Procedure . . . . . Installation . . . . . . ANSI/IEEE Documents . . . . . . . . . . . . . . . . Downloading Language Files . . . . . . for this document Interface Control . . . . . . . . . 35 GROUP System Value . . . . Error Conditions . . . . . . . . . Download File Content . . . . . IETF Documents . . . . . . . . . . . . . . 61 Issue 1 April 2007 81 . upgrading the . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 L Language Files. . . . . . . . . . About LOG Procedure . Downloading Software Upgrades DTMF Tones . . . . 79 79 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 . . . . . . . . . . . . . . . . ANSI/IEEE Documents . . . . . . . . . . . . . . Powering the . . . . . Event Logging . . Client Hardware Address . . . . . . . . . Disable/Enable . . . . . . . .1X Operational Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error and Status Messages. . . . . . . . . . . . . . . . . . . . . . . . 68 C Change History . . 50 23 24 38 39 D Debug Procedure . . . Intended Audience. . . . . Requirements . . . . . . . . . . . 12 . . DHCP Client Hardware Address . . . . M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ITU Documents. . . 1600 Series IP Telephones Maintenance . . . . . . . . . . . . . . . . . . . . . . . 6 33 32 14 15 16 50 . . . 26 . . . . . . . . . . . . . . . . . . . . . . Restart . . . . . . . . . . . . . . . . . . . . . Document Organization . . . . . . . . 34 32 30 38 . . . . Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802. . . . . . . B Boot File. . . . . . . Entering Data for Administrative Options . . Models . . . . . Local Administrative Procedures. Disable Automatic Gain Control (AGC) Disable Event Logging . . . . . . . . . . . . Logoff Procedure . . . 47 O Operational Errors and Status Messages . . . . Automatic Gain Control. . . . . . . . . . . .

. . . . . . . . . . Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Upgrade Application File . . 67 Restart Scenarios . . . 71 Boot File Needs to be Upgraded . . . . . . . . . . . . . . . . . . . . Pre-Installation Checklist . . Parameter Values . . . . . . . . . . . . 67 V VIEW Administrative Option . . . . . . . . . . . . . . Contents . . . . . . . . . . . . SIG Procedure . . . . . . . . . . . . . . . . . . . . . . . 77 Requirements. . . . . . Signaling Protocol Identifier . . . . . . . . . . . . . . . . . Power Interruption . . . . . . . . . . . . . Site-Specific Option Number Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-Installation Checklist for Static Addressing . . . . . . . . . . . . . . . . . . . . . . 72 Boot File Loaded/No Application File or Application File Needs to be Upgraded.Index Other Documentation . . . . . . . . . . Power Interruption . . . . . . . . for each IP Telephone . . . . . . . . . . 8 . . . . . . . . . . . . . . . . Self-Test . . . Reset . . . . 68 R Related Documentation . . . . . . . . . . . . . . . . troubleshooting System Values. . . . . 45 . . . . . . . . . . . 71 Boot File . . Scenarios for the . . . . . . . . . . . . . . Software Upgrades. . . . . . . . . . . . . . . . . . . . . . Powering the 1600 Series IP Telephone . . . . . . . . . . . . . System Parameter Values. . . . . . . . . . Pre-Installation Checklist . . . . . . . . . . . . . . . . . . Settings File. . . . . . U . . . . . . 41 Restart Process. . . . . . . . . . . . Terms. . . . . . . . . . . . . . . 54 P Parameter Values . . . . . . . . . . TEST Procedure . . Glossary of . . . . . . . . . . SSON Procedure . . . . . . . . . . . . Guidelines for . . . . . 67 45 50 43 43 44 10 47 44 27 27 55 41 T Technical Support . Downloading . . . . . . . . . 6 VIEW Administrative Option . . . . . . . . . . . 54 S Scenarios for the Restart Process . . . . . . . . . . . . . . . Static Addressing Installation . . . . 75 . . . . . . . . . . . . . . . . . . . . . 55 54 12 10 27 Unnamed Registration . . Installation Error and Status Messages . . . 68 Reset System Values . Troubleshooting DTMF Tones . . . . . . . . . . . .11 Reset Boot File and System-Specific Application File Already Loaded . . . . . . . . . . . Operational Errors and Status Messages . . . . . 67 Restart the Telephone . Software . . . . . . . . . . . . . . . . . . . . . . 54 53 53 57 61 55 54 82 1600 Series IP Telephone Installation and Maintenance Guide . . . . . . . . . . . .