Avaya 16-601443, 1600 User Manual

Avaya 1600 Series IP Deskphones

Administrator Guide Release 1.3.x

16-601443

Issue 4

April 2010

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

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.

Warr ant y

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

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 LI CE N SE TE RMS AVAI LAB LE ON THE AVAYA W EB S IT E AT

http://support.avaya.com/LicenseInfo/

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.

and search for the document number in

(“GENERAL LICENSE TERMS”). IF

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.

Security

See http://support.avaya.com/security vulnerabilities in Avaya products. See http://support.avaya.com latest software patches and upgrades. For information about secure configuration of equipment and mitigation of toll fraud threats, see the Avaya Toll Fraud and Security Handbook at http://support.avaya.com

to locate and/or report known

to locate the

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

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

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

Other Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2: Administration Overview and Requirements . . . . . . . . . 11

1600 Series IP Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Parameter Data Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

The Administrative Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Administrative Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Telephone Initialization Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Step 1: Telephone to Network . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Step 2: DHCP Server to Telephone . . . . . . . . . . . . . . . . . . . . . . . . 18

Step 3: Telephone and File Server . . . . . . . . . . . . . . . . . . . . . . . . 18

Step 4: Telephone and the Call Server . . . . . . . . . . . . . . . . . . . . . . 18

Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 3: Network Requirements . . . . . . . . . . . . . . . . . . . . . 21

Network Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

HTTP/HTTPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Required Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Other Network Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Reliability and Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

IEEE 802.1P and 802.1Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Network Audio Quality Display on 1600 Series IP Telephones . . . . . . . . . 26

IP Address Lists and Station Number Portability . . . . . . . . . . . . . . . . 26

TCP/UDP Port Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Registration and Authentication . . . . . . . . . . . . . . . . . . . . . . . 30

Issue 5 April 2010 3

Contents

Chapter 4: Avaya Aura Communication Manager Administration . . . . 31

Call Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Switch Compatibility and Aliasing IP Telephones. . . . . . . . . . . . . . . . 31

Media Server (Switch) Administration . . . . . . . . . . . . . . . . . . . . . . . . 33

IP Interface and Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

UDP Port Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

RSVP and RTCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

IEEE 802.1P and 802.1Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

DIFFSERV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Voice Mail Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

1600 Series IP Telephones with Avaya Aura Communication Manager 5.2

Native Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

1600 Series IP Telephones Aliased as 4600 Series IP Telephones. . . . . . . 36

Telephone Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

System-Wide Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Feature-Related System Parameters . . . . . . . . . . . . . . . . . . . . . . . 37

Administering Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Aliasing 1600 Series IP Telephones . . . . . . . . . . . . . . . . . . . . . . . 39

Administering Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Feature Buttons and Call Appearances . . . . . . . . . . . . . . . . . . . . . . . 40

For the 1603/1603SW/1603-I/1603SW-I and 1608/1608-I IP Telephones . . . . 40

For the 1616/1616-I IP Telephones . . . . . . . . . . . . . . . . . . . . . . . . 40

Conference Details Screen for Ad-Hoc Conferences . . . . . . . . . . . . . . 41

Shuffling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Printing Button Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 5: Server Administration . . . . . . . . . . . . . . . . . . . . . 43

Software Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

DHCP and File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

DHCP Server Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

DHCP Generic Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Windows NT 4.0 DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Verifying the Installation of the DHCP Server . . . . . . . . . . . . . . . . 48

Creating a DHCP Scope for the IP Telephones . . . . . . . . . . . . . . . 49

Editing Custom Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Adding the DHCP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Activating the Leases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4 Avaya 1600 Series IP Deskphones Administrator Guide

Verifying Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 51

Windows 2000 DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Verifying the Installation of the DHCP Server . . . . . . . . . . . . . . . . 52

Adding DHCP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Activating the New Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

HTTP Generic Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

HTTP Configuration for Backup/Restore. . . . . . . . . . . . . . . . . . . . . . . 56

For IIS Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Web Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 6: Telephone Software and Application Files . . . . . . . . . . 61

General Download Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

1600 Series IP Telephone Scripts and Application Files . . . . . . . . . . . . . . 62

Choosing the Right Application File and Upgrade Script File . . . . . . . . . 62

Upgrade Script File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Settings File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Contents of the Settings File . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Contents

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

Chapter 7: Administering Telephone Options . . . . . . . . . . . . . . . 67

Administering Options for the 1600 Series IP Telephones . . . . . . . . . . . . . 67

VLAN Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

VLAN Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

VLAN Default Value and Priority Tagging . . . . . . . . . . . . . . . . . . . . 74

VLAN Separation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

DNS Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

IEEE 802.1X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

802.1X Pass-Through and Proxy Logoff . . . . . . . . . . . . . . . . . . . . . 78

802.1X Supplicant Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Link Layer Discovery Protocol (LLDP) . . . . . . . . . . . . . . . . . . . . . . . . 79

Local Administrative Options Using the Telephone Dialpad . . . . . . . . . . . . 84

Clear Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Disable/Enable Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Group Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Reset System Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Restart the Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Issue 5 April 2010 5

Contents

Interface Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

The View Administrative Option . . . . . . . . . . . . . . . . . . . . . . . . . 91

Static Addressing Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Disable/Enable Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Logoff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Self-Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Language Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

1600 Series Global Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . 100

1600 Series International Telephones . . . . . . . . . . . . . . . . . . . . . . 102

Enhanced Local Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Chapter 8: Administering Applications and Options . . . . . . . . . . . 111

Customizing 1600 Series IP Telephone Applications and Options. . . . . . . . . 111

The Application Status Flag (APPSTAT) . . . . . . . . . . . . . . . . . . . . . 114

Appendix A: Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . 117

Appendix B: Related Documentation . . . . . . . . . . . . . . . . . . . 119

IETF Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

ITU Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

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

Appendix C: Sample Administration Forms . . . . . . . . . . . . . . . . 123

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

6 Avaya 1600 Series IP Deskphones Administrator Guide

Chapter 1: Introduction

About This Guide

This guide is for personnel who administer Avaya Aura™ Communication Manager, Avaya Aura Communication Manager Branch (formerly known as Avaya Distributed Office), DHCP, HTTP/ HTTPS servers for Avaya 1600 Series IP Deskphones, a Local Area Network (LAN), or a Web server.

The 1600 Series IP Telephones use Internet Protocol (IP) technology with Ethernet line interfaces and support the H.323 protocol only. The 1600 Series IP Telephones provide support for DHCP, HTTP, and HTTPS over IPv4/UDP, which enhance the administration and servicing of the telephones. These telephones use DHCP to obtain dynamic IP Addresses, and HTTPS or HTTP to download new versions of software or customized settings for the telephones.

CAUTION:

CAUTION: Avaya does not support many of the products mentioned in this document. Take

care to ensure that there is adequate technical support available for servers used with any 1600 Series IP Telephone system. If the servers are not functioning correctly, the 1600 Series IP Telephones might not operate correctly.

Issue 5 April 2010 7

Introduction

Document Organization

The guide contains the following sections:

Chapter 1:

Chapter 2: Administration Overview and Requirements

Chapter 3: Requirements

Chapter 4: Avaya Aura Communication Manager Administration

Chapter 5: Administration

Chapter 6: Telephone Software and Application Files

Chapter 7: Telephone Options

Chapter 8: Administering Applications and Options

Appendix A: Glossary of Te rms

Appendix B: Related Documentation

Appendix C: Administration Forms

Introduction Provides an overview of this document.

Network

Server

Administering

Sample

Provides an overview of the administrative process and describes general hardware, software, and operational requirements.

Describes administrative requirements for your Local Area Network.

Describes how to administer Avaya Aura Communication Manager to operate with 1600 Series IP Telephones.

Describes DHCP, HTTP, and HTTPS administration for the 1600 Series IP Telephones.

Describes telephone software, covers application software downloads, and provides information about the configuration file.

Describes how to use file parameters and options to administer 1600 Series IP Telephones. Covers backup and restoration of telephone data. Also describes how to use local procedures to customize a single telephone from the dialpad.

Provides a table of customizable application-specific parameters, to provide administrative control of telephone functions and options.

Provides a glossary of terms used in this document or which can be applicable to 1600 Series IP Telephones.

Provides references to external documents that relate to telephony in general, which can provide additional information about specific aspects of the telephones.

Provides examples of Avaya Aura Communication Manager forms related to system-wide and individual telephone administration.

8 Avaya 1600 Series IP Deskphones Administrator Guide

1600 Series IP Telephones

The 1600 Series IP Telephones currently support the H.323 signaling protocol.

The H.323 standard provides for real time audio, video, and data communications transmission over a packet network. An H.323 telephone protocol stack comprises several protocols:

● H.225 for registration, admission, status (RAS), and call signaling,

● H.245 for control signaling,

● Real Time Transfer Protocol (RTP), and

● Real Time Control Protocol (RTCP)

The parameters under which the 1600 Series IP Telephones need to operate are summarized as follows:

● Telephone and System Administration on the Avaya Media Server, as covered in

Chapter 4:

Avaya Aura Communication Manager Administration.

● IP address management for the telephone, as covered in DHCP and File Servers on

page 43 for dynamic addressing. For static addressing, see the Avaya 1600 Series IP Deskphones Installation and Maintenance Guide.

● Tagging Control and VLAN administration for the telephone, if appropriate, as covered in

Chapter 7:

● Quality of Service (QoS) administration for the telephone, if appropriate. QoS is covered in

QoS

● Interface administration for the telephone, as appropriate. Administer the telephone to

LAN interface using the PHY1 parameter described in Chapter 3:

Administering Telephone Options.

on page 25 and QoS on page 34.

Network Requirements.

Administer the telephone to PC interface using the PHY2 parameter described in “Local Procedures” in the Avaya 1600 Series IP Deskphones Installation and Maintenance

Guide.

● Application-specific telephone administration, if appropriate, as described in Chapter

8: Administering Applications and Options. An example of application-specific data is

specifying the extent to which users can add/edit/delete data for Contacts entries.

● Protocol administration, for example, Simple Network Management Protocol (SNMP) and

Link Layer Discovery Protocol (LLDP).

Issue 5 April 2010 11

Administration Overview and Requirements

Table 1 indicates that you can administer system parameters in a variety of ways and use a

variety of delivery mechanisms like:

● Maintaining the information on the call server.

● Manually entering the information by means of the telephone dialpad.

● Administering the DHCP server.

● Editing the configuration file on the applicable HTTP or HTTPS file server.

● User modification of certain parameters, when given administrative permission to do so.

Note:

Note: Not all parameters can be administered on all delivery mechanisms.

Table 1: Administration Alternatives and Options for 1600 Series IP Telephones

Administrative

Parameter(s)

Mechanisms

For More Information See:

Telephone

Avaya call server Chapter 4:

Administration

IP Addresses DHCP

(strongly recommended)

Configuration file Chapter 6: Telephone Software and Application

Manual administration at the telephone

LLDP Link Layer Discovery Protocol (LLDP) on page 79.

Tagging and

LLDP

VLAN

DHCP DHCP Server Administration

Configuration file (strongly recommended)

Avaya Aura Communication Manager Administration, Chapter 5: Server Administration,

and Appendix B: Related Documentation.

DHCP and File Servers on page 43, and especially DHCP Server Administration

on page 44.

Files and Chapter 7: Administering Telephone Options.

“Static Addressing Installation” in the Avaya 1600

Series IP Deskphones Installation and Maintenance Guide.

Link Layer Discovery Protocol (LLDP) on page 79.

on page 44, and

Chapter 7:

DHCP and File Servers

Administering Telephone Options.

on page 43 and Chapter

7: Administering Telephone Options.

12 Avaya 1600 Series IP Deskphones Administrator Guide

1 of 3

Table 1: Administration Alternatives and Options for 1600 Series IP Telephones (continued)

Administrative

Parameter(s)

Mechanisms

For More Information See:

1600 Series IP Telephones

Manual administration at the telephone

“Static Addressing Installation” in the Avaya 1600

Series IP Deskphones Installation and Maintenance Guide.

Avaya call server Use the change ip-network-map command to

configure the VLAN ID.

2 of 3

Issue 5 April 2010 13

Administration Overview and Requirements

Table 1: Administration Alternatives and Options for 1600 Series IP Telephones (continued)

Administrative

Parameter(s)

Mechanisms

For More Information See:

Quality of Service

Avaya call server (strongly

UDP Port Selection on page 34 and Appendix B: Related Documentation

recommended)

DHCP DHCP and File Servers on page 43, and Chapter

7: Administering Telephone Options.

Configuration file DHCP and File Servers on page 43, and Chapter

7: Administering Telephone Options.

Interface DHCP DHCP and File Servers

6: Telephone Software and Application Files.

Configuration file (strongly

DHCP and File Servers 6: Telephone Software and Application Files.

recommended)

Manual administration at the telephone

“Ethernet (Hub) Interface Enable/Disable” in the

Avaya 1600 Series IP Deskphones Installation and Maintenance Guide.

Link Layer Discovery Protocol (LLDP) on page 79.

DHCP Server Administration on page 44.

Also, Chapter 8:

Administering Applications and

Application specific parameters

LLDP

DHCP DHCP and File Servers on page 43, and especially

Options.

on page 43, and Chapter

Configuration file (strongly recommended)

DHCP and File Servers on page 43, and especially HTTP Generic Setup on page 55. Also, Chapter 8:

General information about administering DHCP servers is covered in DHCP and File

Servers on page 43, and more specifically, DHCP Server Administration on page 44. General

information about administering HTTP servers is covered in DHCP and File Servers specifically, HTTP Generic Setup telephone options as described in Chapter 7:

14 Avaya 1600 Series IP Deskphones Administrator Guide

. Once you are familiar with that material, you can administer

Administering Telephone Options.

Administering Applications and Options.

3 of 3

, and more

Parameter Data Precedence

If a given parameter is administered in multiple places, the last server to provide the parameter has precedence. The precedence, from lowest to highest, is:

1. LLDP,

2. Manual administration, with the two exceptions described for the system parameter

STATIC

3. DHCP,

4. HTTP/HTTPS script file,

5. the Avaya Media Server, and finally,

6. Backup files, if administered and if permitted.

Settings the IP telephone receives from backup files or the media server overwrite any previous settings, including manual settings. The only exception to this sequence is in the case of VLAN IDs. In the case of VLAN IDs, LLDP settings of VLAN IDs are the absolute authority. Then the usual sequence applies through HTTP/HTTPS.

on page 72,

Parameter Data Precedence

Note:

Note: For the L2QVLAN and L2Q system values, LLDP settings of VLAN IDs are the

absolute authority only if the LLDP task receives the VLAN IDs before DHCP and HTTP, and the DHCP client of the telephone is activated at all. If the LLDP task receives the VLAN IDs after DHCP negotiation, several criteria must be successful before the telephone accepts VLAN IDs from LLDP. For more information, see Link Layer Discovery Protocol (LLDP)

The Administrative Process

The following list depicts administration for a typical 1600 Series IP Telephone network. Your own configuration might differ depending on the servers and system you have in place.

1. LAN and applicable servers administered to accept the telephones.

2. Telephone software downloaded from the Avaya support site.

3. 46xxsettings file updated with site-specific information, as applicable.

4. 1600 Series Telephones installed. For more information, see the Avaya 1600 Series IP Deskphones Installation and Maintenance Guide.

5. Individual 1600 Series IP Telephones updated using local procedures, as applicable. For more information, see “Local Administrative Procedures” in the Avaya 1600 Series IP Deskphones Installation and Maintenance Guide.

Issue 5 April 2010 15

Administration Overview and Requirements

Administrative Checklist

Use the following checklist as a guide to system and LAN administrator responsibilities. This high-level list helps ensure that all telephone system prerequisites and requirements are met prior to telephone installation.

Note:

Note: One person might function as both the system administrator and the LAN

administrator in some environments.

Table 2: Administrative Checklist

Task Description For More Information See:

Network Requirements Assessment

Administer the call server

DHCP server installation

Administer DHCP application

HTTP/HTTPS server installation

Application file(s), script file, and settings file installation on HTTP/ HTTPS server

Determine that network hardware is in place and can handle telephone system requirements.

Verify that the call server is licensed and is administered for Voice over IP (VoIP).

Verify the individual telephones are administered as desired.

Install a DHCP application on at least one new or existing PC on the LAN.

Add IP telephone administration to DHCP application.

Install an HTTP/HTTPS application on at least one new or existing PC on the LAN.

Download the files from the Avaya support site.

Chapter 3:

Network

Requirements.

Chapter 4: Avaya Aura Communication Manager Administration.

Chapter 4:

Avaya Aura Communication Manager Administration.

Vendor-provided instructions.

DHCP Server Administration in Chapter 5:

Server Administration.

Vendor-provided instructions.

http://www.avaya.com/support

Chapter 6: Telephone Software and Application Files.

Modify settings file as desired

Edit the settings file as desired, using your own tools or the [Avaya] Web configuration tool.

16 Avaya 1600 Series IP Deskphones Administrator Guide

Chapter 6:

Telephone Software and Application Files and Web Configuration Tool on page 58.

1 of 2

Telephone Initialization Process

Table 2: Administrative Checklist (continued)

Task Description For More Information See:

Administer telephones locally as applicable

As a Group: The GROUP System Value

page 65 and the Avaya 1600

Series IP Deskphones Installation and Maintenance Guide.

Individually: The applicable Local

Procedures in the Avaya 1600

Series IP Deskphones Installation and Maintenance Guide.

Installation of telephones in the network

Allow user to modify Options, if applicable

Avaya 1600 Series IP Deskphones Installation and Maintenance Guide.

OPSTAT

on page 70 and the respective User Guide for the specific telephone model.

Note:

Note: The 1608/1608-I and 1616/1616-I telephones support the Top Line Text and

Audio Push types (but not the WML Push type).

2 of 2

Telephone Initialization Process

These steps offer a high-level description of the information exchanged when the telephone initializes and registers. This description assumes that all equipment is properly administered ahead of time. This description can help you understand how the 1600 Series IP Telephones relate to the routers and servers in your network.

Step 1: Telephone to Network

The telephone is appropriately installed and powered. After a short initialization process, the telephone identifies the LAN speed and sends a message out into the network, identifying itself and requesting further information. A router on the network receives and relays this message to the appropriate DHCP server if the phone IP address is 0.0.0.0.

Issue 5 April 2010 17

Administration Overview and Requirements

Step 2: DHCP Server to Telephone

The DHCP file server provides information to the telephone, as described in DHCP and File

Servers on page 43. Among other data passed to the telephone is the IP address of the HTTP

or HTTPS server.

Step 3: Telephone and File Server

The 1600 Series IP Telephones can download script files and settings files from either an HTTP or HTTPS server. These telephones can also download the application files from the HTTP server. The telephone queries the file server, which transmits a script file to the telephone. This script file, at a minimum, tells the telephone which application file the telephone must use. The application file is the software that has the telephony functionality.

The telephone uses the script file to determine if it has the proper application file. If the telephone determines the proper application file is missing, the telephone requests an application file download from the HTTP server. The telephone then downloads the file and conducts some checks to ensure that the file was downloaded properly. If the telephone determines it already has the proper file, the telephone proceeds as described in the next paragraph without downloading the application file again.

The telephone checks and loads the application file, then uses the script file to look for a settings file, if appropriate. The optional settings file can contain settings you have administered for any or all of the 1600 Series IP Telephones in your network. For more information about this download process and settings file, see Chapter 6:

Step 4: Telephone and the Call Server

The call server referred to in this step is the Avaya Media Server.

In this step, the telephone might prompt the user for an extension and password. The telephone uses that information to exchange a series of messages with the call server. For a new installation and for full service, the user can enter the telephone extension and password. For a restart of an existing installation, this information is already stored on the telephone, but the user might have to confirm the information. The telephone and the call server exchange more messaging. The expected result is that the telephone is appropriately registered and call server data such as feature button assignments are downloaded.

Telephone Software and Application Files.

18 Avaya 1600 Series IP Deskphones Administrator Guide

Error Conditions

The 1600 Series IP Telephones support a feature called Unnamed Registration. Unnamed Registration allows a telephone to register with the Avaya Media Server without an extension, assuming the Avaya Media Server also supports this feature. To invoke Unnamed Registration, take no action. Allow the Extension... prompt to display for 60 seconds without making an entry. The telephone automatically attempts to register by means of Unnamed Registration. A telephone registered with Unnamed Registration has the following characteristics:

● only one call appearance,

● no administrable features,

● can make only outgoing calls, subject to call server Class of Restriction/Class of Service

limitations, and

● can be converted to normal “named” registration by the user entering a valid extension and

password (that is, logging in).

Note:

Note: Unnamed Registration requires administration on the Avaya Aura

Communication Manager system.

You can also administer the telephone to avoid unnamed registration and remain unregistered if no extension and password are provided. For more information, see UNNAMEDSTAT

Table 8

For more information about the installation process, see the Avaya 1600 Series IP Deskphones Installation and Maintenance Guide.

Error Conditions

Assuming proper administration, most of the problems reported by telephone users are likely to be LAN-based. Quality of Service, server administration, and other issues can impact user perception of IP telephone performance.

The Avaya 1600 Series IP Deskphones Installation and Maintenance Guide covers possible operational problems that might be encountered after successful 1600 Series IP Telephone installation. The following User Guides also contain guidance for users having problems with specific IP telephone applications:

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

Document Number 16-601444.

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

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

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

Module User Guide, Document Number 16-601450.

Issue 5 April 2010 19

Administration Overview and Requirements

20 Avaya 1600 Series IP Deskphones Administrator Guide

Chapter 3: Network Requirements

Network Assessment

Perform a network assessment to ensure that the network will have the capacity for the expected data and voice traffic, and that it can support for all applications:

● H.323,

● DHCP,

● HTTP/HTTPS, and

● Jitter buffers

Also, QoS support is required to run VoIP on your configuration. For more information, see

Appendix B: Related Documentation

and UDP Port Selection on page 34.

Hardware Requirements

To operate properly, you need:

● Category 5e cables designed to the IEEE 802.3af-2003 standard, for LAN powering,

● For Avaya Aura Communication Manager: TN2602 IP Media Processor circuit pack. Sites

with a TN2302 IP Media Processor circuit pack are strongly encouraged to install a TN2602 circuit pack.

● For Avaya Aura Communication Manager: TN799C or D Control-LAN (CLAN) circuit pack.

Important:

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

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

http://www.avaya.com/support

To ensure that the appropriate circuit pack(s) are administered on your media server, see

Chapter 4:

hardware requirements in general, see the Avaya 1600 Series IP Deskphones Installation and Maintenance Guide.

Avaya Aura Communication Manager Administration. For more information about

Issue 5 April 2010 21

Network Requirements

Server Requirements

Two server types can be configured for the 1600 Series IP Telephones:

● DHCP

● HTTP or HTTPS

Note:

Note: HTTPS does not provide all of the functionality of HTTP. For example, backup/

restore is unavailable via HTTPS, and firmware cannot be downloaded via HTTPS.

While the servers listed provide different functions that relate to the 1600 Series IP Telephones, they are not necessarily different boxes. For example, DHCP provides file management whereas HTTP provides application management, yet both functions can co-exist on one hardware unit. Any standards-based server is recommended.

For parameters related to Avaya Media Server information, see Chapter 4:

Communication Manager Administration, and the administration documentation for your call

server. For parameters related to DHCP and file servers, see Chapter 5:

CAUTION:

CAUTION: The telephones obtain important information from the script files on the file server

and depend on the application file for software upgrades. If the DHCP file server is unavailable when the telephones reset, the telephones register with the media server and operate. Some features might not be available. To restore them you need to reset the telephone(s) when the file server is available.

DHCP Server

Avaya recommends that a DHCP server and application be installed and that static addressing be avoided. Install the DHCP server and application as described in DHCP and File Servers page 43.

HTTP/HTTPS Server

Avaya Aura

Server Administration.

Administer the HTTP or HTTPS file server and application as described in HTTP Generic

Setup on page 55.

22 Avaya 1600 Series IP Deskphones Administrator Guide

Required Network Information

Before you administer DHCP and HTTP, and TLS, as applicable, complete the information in

Table 3

Gatekeeper in your configuration, complete Table 3

The 1600 Series IP Telephones support specifying a list of IP addresses for a gateway/router, HTTP/HTTPS server, and Avaya Media Server Gatekeeper(s). Each list can contain up to 255 total ASCII characters, with IP addresses separated by commas with no intervening spaces. Depending on the specific DHCP application, only 127 characters might be supported.

When specifying IP addresses for the file server or media server, use either dotted decimal format (“xxx.xxx.xxx.xxx”) or DNS names. If you use DNS, the system value DOMAIN is appended to the IP addresses you specify. If DOMAIN is null, the DNS names must be fully qualified, in accordance with IETF RFCs 1034 and 1035. For more information about DNS, see

DHCP Generic Setup

Table 3: Required Network Information Before Installation - Per DHCP Server

. If you have more than one Gateway, HTTP/TLS server, subnetwork mask, and

on page 44 and DNS Addressing on page 76.

1. Gateway (router) IP address(es)

2. HTTP server IP address(es)

Required Network Information

for each DHCP server.

3. Subnetwork mask

4. Avaya Media Server Gatekeeper IP address(es)

5. Avaya Media Server Gatekeeper port Although this can be a value between 0 and

65535, the default value is 1719. Do not change the default value unless that value conflicts with an existing port assignment.

6. HTTP server file path

7. Telephone IP address range

From: To:

8. DNS server address(es) If applicable.

9. HTTPS server address(es) If applicable.

The file server file path is the “root” directory used for all transfers by the server. All files are uploaded to or downloaded from this default directory. In configurations where the upgrade script and application files are in the default directory, do not use item 6 in Table 3

As the LAN or System Administrator, you are also responsible for:

● Administering the DHCP server as described in Chapter 5: Server Administration.

● Editing the configuration file on the applicable HTTP or HTTPS file server, as covered in

00 Series IP Telephone Scripts and Application Files.

Issue 5 April 2010 23

Network Requirements

Other Network Considerations

SNMP

The 1600 Series IP Telephones are fully compatible with SNMPv2c and with Structure of Management Information Version 2 (SMIv2). The telephones respond correctly to queries from entities that comply with earlier versions of SNMP, such as SNMPv1. “Fully compatible” means that the telephones respond to queries directed either at the MIB-II or the read-only Custom MIB. Read-only means that the values therein cannot be changed externally by means of network management tools.

You can use the system value SNMPADD to restrict the IP addresses from which the telephone accepts SNMP queries. You can also customize your community string with the system value SNMPSTRING. For more information, see Chapter 5:

Series IP Telephone Customizable System Parameters.

Note:

Note: As of Release 1.0, SNMP is disabled by default. Administrators must initiate

SNMP by setting the SNMPADD and SNMPSTRING system values appropriately.

Server Administration and Ta bl e 8 : 1600

For more information about SNMP and MIBs, see the IETF references listed in

Appendix B: Related Documentation

. The Avaya Custom MIB for the 1600 Series IP Telephones is available for download in *.txt format on the Avaya support Web site at

http://www.avaya.com/support

24 Avaya 1600 Series IP Deskphones Administrator Guide

Reliability and Performance

Other Network Considerations

QoS

All 1600 Series IP Telephones respond to a ping or traceroute message sent from the DEFINITY

, MultiVantage™, Avaya Aura Communication Manager, or Avaya Aura Communication Manager Branch system (formerly known as Avaya Distributed Office) or any other network source. The telephones do not originate a ping or traceroute. The 1600 Series IP Telephones offer and support “remote ping” and “remote traceroute.” The switch can instruct the telephone to originate a ping or a traceroute to a specified IP address. The telephone carries out that instruction and sends a message to the switch indicating the results. For more information, see your switch administration documentation.

If applicable, the telephones test whether the network Ethernet switch port supports IEEE

802.1P/Q tagged frames by ARPing the router with a tagged frame. For more information, see

VLAN Considerations

on page 73. If your LAN environment includes Virtual LANs (VLANs),

your router must respond to ARPs for VLAN tagging to work properly.

For more information about the extent to which your network can support any or all of the QoS initiatives, see your LAN equipment documentation. See QoS

on page 34 about QoS

implications for the 1600 Series IP Telephones.

All 1600 Series IP Telephones provide some detail about network audio quality. For more information see, Network Audio Quality Display on

1600 Series IP Telephones on page 26.

IEEE 802.1P and 802.1Q

For more information about IEEE 802.1P and IEEE 802.1Q and the 1600 Series IP Telephones, see IEEE 802.1 the 802.1Q tag are reserved for identifying packet priority to allow any one of eight priorities to be assigned to a specific packet.

● 7: Network management traffic

● 6: Voice traffic with less than 10ms latency

● 5: Voice traffic with less than 100ms latency

● 4: “Controlled-load” traffic for critical data applications

● 3: Traffic meriting “extra-effort” by the network for prompt delivery, for example, executive

e-mail

● 2: Reserved for future use

● 0: The default priority for traffic meriting the “best-effort” for prompt delivery of the network.

● 1: Background traffic such as bulk data transfers and backups

P and 802.1Q on page 34 and VLAN Considerations on page 73. Three bits of

Issue 5 April 2010 25

Network Requirements

Note:

Note: Priority 0 is a higher priority than Priority 1.

Network Audio Quality Display on 1600 Series IP Telephones

All 1600 Series IP Telephones give the user an opportunity to monitor network audio performance while on a call. For more information, see the telephone user guide.

While on a call, the telephones display network audio quality parameters in real-time, as shown in Ta bl e 4

Table 4: Parameters in Real-Time

Parameter Possible Values

Received Audio Coding G. 711 , G.711u, G.711a, G.72 6, G.729A, or G.729B.

Packet Loss "No data" or a percentage. Late and out-of-sequence packets

are counted as lost if they are discarded. Packets are not counted as lost until a subsequent packet is received and the loss confirmed by the RTP sequence number.

Packetization Delay "No data" or an integer number of milliseconds. The number

reflects the amount of delay in received audio packets, and includes any potential delay associated with the codec.

One-way Network Delay "No data" or an integer number of milliseconds. The number is

one-half the value RTCP computes for the round-trip delay.

Network Jitter Compensation Delay

"No data" or an integer number of milliseconds reporting the average delay introduced by the jitter buffer of the telephone.

The implication for LAN administration depends on the values the user reports and the specific nature of your LAN, like topology, loading, and QoS administration. This information gives the user an idea of how network conditions affect the audio quality of the current call. Avaya assumes you have more detailed tools available for LAN troubleshooting.

IP Address Lists and Station Number Portability

The 1600 Series IP Telephones provide the capability to specify IP address lists. On startup or a reboot, the telephone attempts to establish communication with these various network elements in turn. The telephone starts with the first address on the respective list. If the communication is denied or times out, the telephone proceeds to the next address on the appropriate list and tries that one. The telephone does not report failure unless all the addresses on a given list fail, thereby improving the reliability of IP telephony.

26 Avaya 1600 Series IP Deskphones Administrator Guide

Other Network Considerations

This capability also has the advantage of making station number portability easier. Assume a situation where the company has multiple locations in London and New York, all sharing a corporate IP network. Users want to take their telephones from their offices in London and bring them to New York. When users start up their telephones in the new location, the local DHCP server usually routes them to the local call server. With proper administration of the local DHCP server, the telephone knows to try a second call server IP address, this one in London. The user can then be automatically registered with the London call server.

Chapter 5:

Server Administration contains details on administration of DHCP servers for lists of

alternate media servers, router/gateways, and HTTP/HTTPS servers. For more information, see DNS Addressing

on page 76.

TCP/UDP Port Utilization

The 1600 Series IP Telephones use a variety of protocols, particularly TCP and UDP, to communicate with other equipment in the network. Part of this communication identifies which TCP or UDP ports each piece of equipment uses to support each protocol and each task within the protocol. For additional TCP/UDP port utilization information as it applies to Avaya Aura Communication Manager, see UDP Port Selection

Depending on your network, you might need to know what ports or ranges are used in the operation of 1600 Series IP Telephones. Knowing these ports or ranges helps you administer your networking infrastructure.

In Figure 1

● The box on the left always represents the 1600 Series IP Telephone.

● Depending on the diagram, the boxes on the right refer to various pieces of network

● Open-headed arrows (for example, ) represent the direction(s) of socket

and Figure 2:

equipment with which the telephone can communicate.

initialization.

on page 34.

● Closed-headed arrows (for example, ) represent the

direction(s) of data transfer.

● The text the arrows point to identifies the port or ports that the 1600 Series IP Telephones

support for the specific situation. Brackets identify ranges when more than one port applies. The text indicates any additional qualifications or clarifications. In many cases, the ports used are the ones called for by IETF or other standards bodies.

Issue 5 April 2010 27

Network Requirements

Figure 1: Signaling, Audio and Management Diagram

Signaling, Audio and Management

1600 Series IP Telephone

Port: 49300

Port: [1500–6500]

randomly selected

Port: [4000–10000]

randomly selected;

range may be changed via

Gatekeeper administration;

always an even number

Port: audio port + 1

(only active during a call

if RTCP is enabled)

Port: audio port + 2

(only active during a call

if RTCP monitoring

is enabled)

H.323 RAS (UDP/IP)

H.323 Signaling (TCP/IP)

H.323 Gatekeeper

Port: 1719

Port: 1720

Media Gateway or another IP endpoint

RTP Audio (UDP/IP)

Port selected from the audio port range administered for the network region

RTCP (UDP/IP)

Port: audio port + 1

Voice Monitoring Manager

RTCP (UDP/IP)

Port depends on Voice Monitoring Manager admin

SNMP (UDP/IP)

Port:161

28 Avaya 1600 Series IP Deskphones Administrator Guide

SNMP MIB Viewer

Port depends on MIB viewer admin

Figure 2: Initialization and Address Resolution Diagram

Initialization and Address Resolution

Other Network Considerations

1600 Series IP Telephone

Port: 68

Port: [1024 - 5000]

Operating System

–selected (a new port is

used for each file

requested)

Port: [1024 - 5000]

Operating System –

selected (a new port

is used for each file

requested)

HTTPS Read Request (TCP/IP)

HTTPS Data, ACKs & Errors (TCP/IP)

HTTP Read Request (TCP/IP)

HTTPS Data, ACKs & Errors (TCP/IP)

DHCP (TCP/IP)

DHCP Server

Port: 67

HTTPS Server

Port:411

Port: Operating System – selected (a new port is used for each file

HTTP Server

Port: 80

Port: Operating System – selected (a new port is used for each file)

Port: [1024 - 5000]

Operating System

–selected

DNS(UDP/IP)

DNS Server

Port: 53

Issue 5 April 2010 29

Network Requirements

Security

For information about toll fraud, see the DEFINITY®, Avaya Aura Communication Manager, or Avaya Aura Communication Manager Branch documents on the Avaya support Web site. The 1600 Series IP Telephones cannot guarantee resistance to all Denial of Service attacks. However, there are checks and protections to resist such attacks while maintaining appropriate service to legitimate users.

You also have a variety of optional capabilities to restrict or remove how crucial network information is displayed or used. These capabilities are covered in more detail in

Chapter 5:

● Support signaling channel encryption while registering, and when registered, with

Note: Signaling and audio are not encrypted when unnamed registration is effective.

● Restricting the response of the 1600 Series IP Telephones to SNMP queries to only IP

Server Administration.

appropriately administered Avaya Media Servers.

Note:

addresses on a list you specify.

● Specifying an SNMP community string for all SNMP messages the telephone sends.

● Restricting dialpad access to Local Administration Procedures, such as specifying IP

addresses, with a password.

● Removing dialpad access to most Local Administration Procedures.

● Restricting the end user’s ability to use a telephone Options application to view network

data.

As of Release 1.1, three existing security-related parameters can be administered on the call server and downloaded with encrypted signaling, in addition to unencrypted HTTP or encrypted HTTPS. Those parameters are SNMP community string, SNMP Source IP Addresses, and Craft Access Code (PROCPSWD).

Registration and Authentication

The Avaya Media Server supports using the extension and password to register and authenticate 1600 Series IP Telephones. For more information, see the current version of your call server administration manual.

30 Avaya 1600 Series IP Deskphones Administrator Guide

+ 112 hidden pages