Avaya 4600 User Manual

Download

Page 1

4600 Series IP Telephone

LAN Administrator’s Guide

555-233-507 Issue 1.7 July 2002

Page 2

Page 3

Notice

Every effort was made to ensure that the information in this book was complete and accurate at the time of printing. However, information is subject to change.

Avaya Web Page

The world wide web home page for Avaya is: http://www.avaya.com

variety of losses to your company, including but not limited to, human/data privacy, intellectual property, material assets, financial resources, labor costs, and/or legal costs.

Federal Communications Commission Statement Part 68: Network Registration Number. This equipment is reg-

istered with the FCC in accordance with Part 68 of the FCC Rules. It is identified by FCC registration number AV1USA-43058-MFE.

Preventing Toll Fraud

Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or working on your company’s behalf). Be aware that there is a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services.

Avaya Fraud Intervention

If you suspect that you are being victimized by toll fraud and you need technical support or assistance and are in within the United States, call the Technical Service Center Toll Fraud Intervention Hotline at 1.800.643.2353. If you need technical support or assistance and are outside of the United States, contact the equipment vendor from whom you purchased your equipment service maintenance contract. If you need to report toll fraud issues regarding a public telephone, contact the in-country telephone service provider.

Providing Telecommunications Security

Telecommunications security of voice, data, and/or video communications is the prevention of any type of intrusion to, that is, either unauthorized or malicious access to or use of, your company’s telecommunications equipment by some party.

Your company’s “telecommunications equipment” includes both this Avaya product and any other voice/data/video equipment that could be accessed via this Avaya product (that is, “networked equipment”).

An “outside party” is anyone who is not a corporate employee, agent, subcontractor, or working on your company’s behalf. Whereas, a “malicious party” is anyone, including someone who may be otherwise authorized, who accesses your telecommunications equipment with either malicious or mischievous intent.

Such intrusions may be either to/through synchronous (time-multiplexed and/or circuit-based) or asynchronous (character-, message-, or packet-based) equipment or interfaces for reasons of:

• Utilization (of capabilities special to the accessed equipment)

• Theft (such as, of intellectual property, financial assets, or toll-facility access)

• Eavesdropping (privacy invasions to humans)

• Mischief (troubling, but apparently innocuous, tampering)

• Harm (such as harmful tampering, data loss or alteration, regardless of motive or intent)

Be aware that there may be a risk of unauthorized intrusions associated with your system and/or its networked equipment. Also realize that, if such an intrusion should occur, it could result in a

Part 68: Answer-Supervision Signaling. Allowing this equipment to be operated in a manner that does not provide proper answer-supervision signaling is in violation of Part 68 Rules. This equipment returns answer-supervision signals to the public switched network when:

• Answered by the called station

• Answered by the attendant

• Routed to a recorded announcement that can be administered by the CPE user

This equipment returns answer-supervision signals on all DID calls forwarded back to the public switched telephone network. Permissible exceptions are:

• A call is unanswered

• A busy tone is received

• A reorder tone is received

Industry Canada (IC) Interference Information

NOTICE: This equipment meets the applicable Industry Canada Terminal Equipment Technical Specifications. This is confirmed by the registration number. The abbreviation, IC, before the registration number signifies that registration was performed based on a Declaration of Conformity indicating that Industry Canada technical specifications were met. It does not imply that Industry Canada approved the equipment.

Le Présent Appareil Nomérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la class A préscrites dans le reglement sur le brouillage radioélectrique édicté par le Industrie Canada.

Trademarks

DEFINITY is a registered trademark of Avaya, Inc. MultiVantage is a trademark of Avaya, Inc.

Ordering Information Call: Avaya Publications Center

U.S. and Canada Voice 1 800 457 1235 Outside U.S. and Canada Voice +1 410 568 3680 U.S. and Canada Fax 1 800 457 1764 Outside U.S. and Canada Fax +1 410 891 0207 Write: GlobalWare Solutions

200 Ward Hill Avenue

Haverhill, MA 01835 USA Attention: Avaya Account Manager Email: totalware@gwsmail.com

For additional documents, refer to the section in About This Guide titled Related Documents. An online copy of this and other related Avaya product documentation can be found at: http:// www.avaya.com/support.

Page 4

Obtaining Products

To learn more about Avaya products and to order products, access the Avaya web site at http://www.avaya.com. Or call the following numbers: customers 1 800 451 2100, account executives 1 888 778 1880 (voice) or 1 888 778 1881 (fax).

European Union Declaration of Conformity

The “CE” mark affixed to the equipment means that it conforms to the referenced European Union (EU) Directives listed below: EMC Directive 89/336/EEC Low-Voltage Directive 73/23/EEC For more information on standards compliance, contact your local distributor.

Page 5

4600 Series IP Telephone LAN Administrator’s Guide

Table of Contents

1 Introduction

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

■ Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

■ Terms Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

■ Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8

2 Overview of Voice over IP (VoIP)

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Overview of Voice over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

■ Data and Voice Network Similarities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

■ Delay and Jitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2

■ Tandem Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2

■ Voice Coding Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

■ H.323 Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

■ DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

■ TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

■ NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

■ QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

Network Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

Suggestions for Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

■ Reliability and Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

■ IP Address Lists and Station Number Portability . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

■ Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

4600 Series IP Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

■ Dual Connection Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

■ Single Connection Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

■ Registration and Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

TOC v

Page 6

4600 Series IP Telephone LAN Administrator’s Guide

■ Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

■ WAN Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

■ DHCP and TFTP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

Initialization Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8

■ Step 1: Telephone to Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8

■ Step 2: DHCP Server to Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8

■ Step 3: Telephone and TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9

■ Step 4: Telephone and the DEFINITY

/MultiVantageTM Call Server . . . . . . . . . . . . 2-9

3 Requirements

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

4 Server Administration

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Administering 4600 Series IP Telephones on DEFINITY

■ DEFINITY

/MultiVantageTM Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Release 8.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4

Releases 9, 9.5, 10, and MultiVantageTM Release 11 . . . . . . . . . . . . . . 4-4

DHCP and TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4

Software Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5

Required Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

■ Choosing a DHCP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6

■ DHCP Software Alternatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6

■ DHCP Generic Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7

■ Windows NT 4.0 DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

■ Windows 2000 DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-13

TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

■ TFTP Generic Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17

■ Avaya TFTP (Suite Pro) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17

4600 Series IP Telephone Scripts and Application Files . . . . . . . . . . . . . . . . . . . . .4-18

■ Contents of the Upgrade Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-19

QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-20

■ IEEE 802.1D and 802.1Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-20

■ DIFFSERV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

■ UDP Port Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-22

■ QoS with 4620 and 4630 IP Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

■ RSVP and RTCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

Administering Options for the 4600 Series IP Telephones . . . . . . . . . . . . . . . . . . . . 4-24

vi TOC

Page 7

Table of Contents

■ DNS Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-24

■ Customizing the Site-Specific Option Number (SSON) . . . . . . . . . . . . . . . . . . . . .4-25

■ Entering Options via the Telephone Dialpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-25

■ Customizing the 4630 IP Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-26

■ 4630 Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-30

■ Call Log Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32

■ Customizing the 4620 IP Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32

5 Troubleshooting Guidelines

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

The View Administrative Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9

Appendix A: Avaya - 46xx IP Telephone MIB

Appendix B: Creating Websites for the 4630 IP Telephone

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

General Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Browser Features and Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

■ Document Skeleton . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

■ Content-Based Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3

■ Logical Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4

■ Physical Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4

■ Physical Spacing and Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-5

■ Lists and Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-5

■ Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-7

■ Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-7

■ Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-8

■ Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-8

■ Character Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-9

■ Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-9

■ Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-9

■ Cookies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-10

Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-10

■ Fixed-Width Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-10

■ Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-11

■ Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-11

■ Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-11

■ Maintaining Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-12

■ User Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-12

TOC vii

Page 8

4600 Series IP Telephone LAN Administrator’s Guide

Appendix C: Creating Websites for the 4620 IP Telephone

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1

General Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1

WML Document Skeleton . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2

Text Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-4

Text Formatting Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-4

Anchor Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-5

Image Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-5

Event Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-7

Task Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-10

Input Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-11

Variable Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-14

Character Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-15

Colors and Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-16

Summary Of WML Tags And Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-16

viii TOC

Page 9

Introduction 1

Program

About This Guide 1

This guide provides a description of Voice over IP, describes how to administer the DHCP and TFTP servers and covers how to troubleshoot operational problems with the 4600 Series IP Telephones and the servers.

The 4600 Series IP Telephone product line is a supplement to Avaya’s IP Solutions platform.

Unless otherwise indicated, references in this document to "the DEFINITY® server" also refer to the MultiVantage

media servers.

Intended Audience 1

This document is intended for personnel administering the DHCP and TFTP servers to support the 4600 Series IP Telephones and those administering the Local Area Network (LAN) itself.

CAUTION:

Many of the products mentioned in this document are not supported by Avaya. Care should be taken to ensure there is adequate technical support available for the TFTP and DHCP servers. If the TFTP or DHCP servers are not functioning correctly, the 4600 Series IP Telephones may not operate correctly.

About This Guide

1-1

Page 10

4600 Series IP Telephone LAN Administrator’s Guide

Document Organization 1

The guide contains the following sections:

Chapter 1, Introduction

Provides an overview of the 4600 Series IP Telephone Administrator’s document.

Chapter 2, Overview of Voice over IP (VoIP)

Chapter 3, Requirements

Describes VoIP and factors influencing its performance that must be considered when implementing this feature.

Describes the hardware and software requirements for Avaya’s VoIP offering.

Chapter 4, Server Administration

Chapter 5, Troubleshooting Guidelines

Appendix A, Avaya - 46xx IP Telephone MIB

Appendix B, Creating Websites for the 4630 IP Telephone

Appendix C, Creating Websites for the 4620 IP Telephone

Describes the administration of DHCP and TFTP for the 4600 Series IP Telephones.

Describes messages that may occur during the operation of the 4600 Series IP Telephones.

Provides the MIB specification for the 46xx IP Telephones (4606, 4612, 4624, and 4630).

Provides information on creating and customizing websites for viewing on the 4630 IP Telephone. Also describes the current capabilities and limitations of the 4630’s web browser.

Provides information on creating and customizing websites for viewing on the 4620 IP Telephone. Also describes the current capabilities and limitations of the 4620’s web browser.

Change History 1

Issue 1.0 This document was issued for the first time in November 200 0. Issue 1.1 This version of the document, revised and issued in Ap ril 2001,

supports through DEFINITY

Release 9.

Issue 1.5 This version of the document was revised in June, 2001 to

support DEFINITY

Release 9.5.

Issue 1.6 This version of the document was revised to support DEFINITY

Release 10 and the 4630 IP Telephone.

Issue 1.7 This is the current version of this document, revised to support

MultiVantage

Release 11 and the 4602 and 4620 IP

Telephones.

Document Organization

1-2

Page 11

Terms Used in This Guide 1

Introduction

802.1p

802.1Q

ARP Address Resolution Protocol, used to verify that the IP address

CELP Code-excited linear-predictive; voice compression requiring only

CLAN Control LAN, type of TN799 circuit pack.

DHCP Dynamic Host Configuration Protocol, an IETF protocol used to

DiffServ Differentiated Services, an IP-based QoS mechanism.

DNS Domain Name System, an IETF standard for ASCII strings to

IETF Internet Engineering Task Force, the organization that produces

LAN Local Area Network.

LDAP Lightweight Directory Access Protocol, an IETF standard for

802.1Q defines a layer 2 frame structure that supports VLAN identification and a QoS mechanism usually referred to as

802.1p, but the content of 802.1p is now incorporated in 802.1D.

provided by the DHCP server is not in use by another IP Telephone.

16 kbps of bandwidth.

automate IP Address allocation and management.

represent IP addresses.

standards for communications on the internet.

database organization and query exchange.

MAC Media Access Control, ID of an endpoint.

NAPT Network Address Port Translation.

NAT Network Address Translation.

PSTN Public Switched Telephone Network, the network used for

traditional telephony.

QoS Quality of Service, used to refer to a number of mechanisms

intended to improve audio quality over packet-based networks.

RRQ Read Request packet, a message sent from the 4600 Series IP

Telephone to the TFTP server, requesting to download the upgrade script and the application file.

RSVP Resource ReSerVation Protocol, used by hosts to request

resource reservations throughout a network.

RTCP RTP Control Protocol, monitors quality of the RTP services and

can provide real-time information to users of an RTP service.

RTP Real-time Transport Protocol, provides end-to-end services for

real-time data (such as voice over IP).

TCP/IP Transmission Control Protocol/Internet Protocol, a network-layer

protocol used on LANs and internets.

Document Organization

1-3

Page 12

4600 Series IP Telephone LAN Administrator’s Guide

TFTP Trivial File Transfer Protocol, used to provide downloading of

upgrade scripts and application files to the IP Telephones.

UDP User Datagram Protocol, a connectionless transport-layer

protocol.

VLAN Virtual LAN.

Conventions Used in This Guide 1

This guide uses the following textual, symbolic, and typographic conventions to help you interpret information.

Symbolic Conventions 1

This symbol precedes additional information about a topic. This information is not required to run your system.

CAUTION:

This symbol is used to emphasize possible harm to software, possible loss of data, or possible service interruptions.

Typographic Conventions 1

This guide uses the following typographic conventions:

command Words printed in this type are commands that you enter into your

system.

device Words printed in this type indicate parameters associated with a

command for which you must substitute the appropriate value. For example, when entering the mount command, device must be replaced with the name of the drive that contains the installation disk.

Administrative Words printed in bold type are menu or screen titles and labels, or items

on menus and screens that you select to perform a task.

italics Italic type indicates a document that contains additional information

about a topic.

<Enter> Words enclosed in angle brackets represent a single key that should be

pressed. These include <Ctrl>, <Enter>, <Esc>, <Insert>, and <Delete>.

Document Organization

1-4

Page 13

Online Documentation 1

The online documentation for the 4600 Series IP Telephones is located at the following URL:

http://www.avaya.com/support

Online Documentation

1-5

Page 14

4600 Series IP Telephone LAN Administrator’s Guide

■ 4606 IP Telephone User Guide (555-233-765) (Int’l 555-233-769)

This document provides detailed information about using the 4606 IP Telephone.

■ 4612 IP Telephone User Guide (555-233-766) (Int’l 555-233-770)

This document provides detailed information about using the 4612 IP Telephone.

■ 4620 IP Telephone User Guide (555-233-781)

This document provides detailed information about using the 4620 IP Telephone.

■ 4624 IP Telephone User Guide (555-233-768) (Int’l 555-233-771)

This document provides detailed information about using the 4624 IP Telephone.

■ 4630 IP Telephone User Guide (555-233-764)

This document provides detailed information about using the 4630 IP Telephone.

The following documents provide standards relevant to IP Telephony.

IETF Documents 1

The following documents are available for free from the IETF web site: http://www.ietf.org/ rfc.html.

Requirements for Internet Hosts - Communication Layers, October 1989, by R. Braden (STD 3: RFC 1122)

Requirements for Internet Hosts - Application and Support, October 1989, by R. Braden (STD 3: RFC 1123)

Internet Protocol (IP), September 1981, by Information Sciences Institute (STD 5: RFC 791), as amended by Internet Standard Subnetting Procedure, August 1985, by J. Mogul and J. Postel (STD 5: RFC 950)

Broadcasting Internet Datagrams, October 1984, by J. Mogul (STD 5: RFC 919)

Broadcasting Internet Datagrams in the Presence of Subnets, October 1984, by J. Mogul

(STD 5: RFC 922)

User Datagram Protocol (UDP), August 28, 1980, by J. Postel (STD 6: RFC 768)

Transmission Control Protocol (TCP), September 1981, by Information Sciences Institute

(STD 7: RFC 793)

Domain Names - Concepts and Facilities (DNS), November, 1987, by P. Mockapetris (STD 13: RFC 1034)

Domain Names - Implementation and Specification (DNS), November 1987, by P. Mockapetris (STD 13: RFC 1035)

The TFTP Protocol (Revision 2), (TFTP), July 1992, by K. Sollins, (STD 33: RFC 1350:) as updated by TFTP Option Extension, May 1998, by G. Malkin and A. Harkin (RFC 2347)

An Ethernet Address Resolution Protocol (ARP), November 1982, by David C. Plummer (STD 37: RFC 826)

Dynamic Host Configuration Protocol (DHCP), March 1997, by R. Droms (RFC 2131)

Customer Support

1-8

Page 17

Overview of Voice over IP (VoIP) 2

Introduction 2

This chapter describes the differences between data and voice networks, and the factors that influence the performance of VoIP. The installation and administration of 4600 Series IP Telephones on DEFINITY addressed.

Overview of Voice over IP 2

servers, and the installation and configuration of DHCP and TFTP are

The 4600 Series IP Telephones allow enterprises to use Voice over IP (that is, packet-switched networks) instead of telephony over the Public Switched Telephone Network (PSTN). However, the use of data networks for transmitting voice packets poses the problem that data networks were not designed for the specific qualities required by voice traffic.

Data and Voice Network Similarities 2

Data and voice networks share similar functions due to the nature of networking.

■ Signaling is used to establish a connection between two endpoints.

In a voice network, signaling is used to identify who the calling party is trying to call and where the called party is on the network. Traditional telephony uses terminals with fixed addresses and establishes a fixed connection for the communication session between two such terminals, allocating fixed bandwidth resources for the duration of the call.

IP communications constitute a connectionless network, having neither fixed addresses nor fixed connections.

■ Addressing. Each terminal on a network must be identified by a unique address.

In a voice network the unique address is a permanent attribute, based on international and national numbering plans, as well as those based on local telephone company practices and internal customer-specific codes.

In IP communications, dial plans track extension numbers assigned to terminals. No fixed connection path is needed.

Introduction

2-1

Page 18

4600 Series IP Telephone LAN Administrator’s Guide

■ Routing is related to addressing and allows connections to be established between

endpoints.

Though these functions are common to data and voice networks, the implementations differ.

Delay and Jitter 2

Data traffic is generally short and comes in bursts. Data networks like the Internet were designed to manage these bursts of traffic from many sources on a first-come, first-served basis. Data packets are sent to multiple destinations, often without any attempt to keep them in a particular order.

Voice networks are designed for continuous transmission during a call. The traffic is not bursty, and the conversation uses a specific amount of bandwidth between the two ends for the duration of the call.

Several features of data networks are unsuitable for voice telephony:

■ Data networks are designed to deliver data at the destination, but not necessarily within a

certain time. This produces delay (latency). In data networks, delay tends to be variable. For voice messages, variable delay results in jitter, an audible chopiness in conversations.

■ Variable routing also can result in loss of timing synchronization, so that packets are not

received at the destination in the proper order.

■ Data networks have a strong emphasis on error correction, resulting in repeated

transmissions.

While data network concepts include prioritization of traffic types to give some forms of traffic greater reliability (for example, for interactive transactions), data requirements tend to be not as strict as most voice requirements.

Release 1.1 of the 4600 Series IP Telephones includes a dynamic jitter buffer. This feature automatically smooths jitter to improve audio quality.

Tandem Coding 2

Tandem coding (also called transcoding) refers to the conversion of a voice signal from analog to digital and back again. When calls are routed over multiple IP facilities, they may be subject to multiple transcodings. The multiple conversions between analog and digital coding result in a deterioration in the voice quality. Tandem coding should be avoided wherever possible in any compressed voice system (for example, minimizing analog trunking on the PBX).

Overview of Voice over IP

2-2

Page 19

Overview of Voice over IP (VoIP)

Voice Coding Standards 2

There are a number of voice coding standards. The Avaya 4600 Series IP Telephones offer the options described below.

G.711, which describes the 64 kbps PCM voice coding technique. G.711-encoded voice is already in the correct format for digital voice delivery in the public phone network or through PBXs.

G.729A and G.729B, which describe adaptive code-excited linear-predictive (CELP) compression that enables voice to be coded into 8 kbps streams.

Release 1.6 of the 4600 Series IP Telephones provides support for G.711 silence suppression and custom packet loss concealment, which can improve audio quality significantly.

H.323 Standard 2

Internal signaling provides connection control and call progress (status) information. The H.323 standard is used for internal signaling for IP packet voice networks. H.323 defines more than simply voice. It defines a complete multimedia network (voice, video, data), with everything from devices to protocols. The H.245 standard links all the entities within H.323 by negotiating facilities among participants and H.323 network elements.

The H.323 standard makes G.711 PCM compression the default form of compression. All other compression formats are optional.

DHCP 2

Dynamic Host Configuration Protocol (DHCP) allows a server to assign IP addresses and other parameters to devices such as the 4600 Series IP Telephones on an as-needed basis. This eliminates the need to configure each end station with a static IP address. The DHCP application also passes information to the 4600 Series IP Telephone, identifying the IP Addresses of the PBX and the TFTP server and the path to the upgrade script and the application file on the TFTP server. For further information, refer to DHCP and TFTP Servers

on page 2-7 and DHCP on page 4-6.

TFTP 2

During the installation and, if necessary, during the reset of the 4600 Series IP Telephones, the upgrade script and potentially, the application file, are downloaded from the Trivial File Transfer Protocol (TFTP) server to each IP Telephone, simplifying the software upgrade process. For further information, refer to DHCP and TFTP Servers

on page 2-7 and TFTP on page 4-17.

Overview of Voice over IP

2-3

Page 20

4600 Series IP Telephone LAN Administrator’s Guide

NAT 2

A Network Address Translator is an application that can be administered between your network and the Internet. The NAT translates network layer IP addresses so your local intranet IP addresses can duplicate global, Internet addresses. A detailed discussion of NAT is beyond the scope of this document, but it should be noted that use of NAT can lead to problems affecting the consistency of addressing throughout your network. In Release 1.6 and earlier Releases of the 4600 Series IP Telephones, NAT is not recommended for networks handling IP-based telephony traffic. As of Release 1.7, all 4600 Series IP Telephones support NAT interworking; hence, there are no problems with NAT and Release 1.7 of the 4600 Series IP Telephones. Note, however, that support for NAT does not imply support for Network Address Port Translation (NAPT). Specifically, the 4600 Series IP Telephones do not support communication to the PBX through any NAPT device.

QoS 2

Quality of Service (QoS) is a term covering several initiatives to maximize the quality of the voice heard at both ends of a call that originates, terminates, or both, on an IP-based telephone. These initiatives include various prioritization schemes to offer voice packets a larger or prioritized share of network resources. These schemes include standards such as IEEE’s 802.1D and 802.1Q, the Internet Engineering Task Force’s (IETF’s) “Differentiated Services”, RTP Control Protocol (RTCP) and Resource ReSerVation Protocol (RSVP), and port-based priority schemes such as UDP port selection. Documentation for your LAN equipment will elaborate on the extent your network can support any or all of these initiatives. See Chapter 4, Server Administration of QoS for the 4600 Series IP Telephones.

for some implications

As of Release 1.7, both the 4620 and 4630 IP Telephones provide information to the end user about network audio quality that may be of use to the LAN Administrator. For specific information, see QoS with 4620 and 4630 IP Telephones

on page 4-22.

SNMP 2

Simple Network Management Protocol (SNMP) is a family of standards-based protocols and procedures to allow vendor-independent management of data networks. Using a simple set of protocol commands, an SNMP-compliant device will store information in standard format in one or more Management Information Bases (MIBs). In general, devices will support the standardsspecific MIB termed MIB-II. In addition, devices may define one or more "custom MIBs" that contain information about the specifics of the device.

Release 1.1 of the 4600 Series IP Telephones is fully compatible with SNMPv2c (a later version of SNMP) and with Structure of Management Information Version 2 (SMIv2), although the telephones will respond correctly to queries from entities that comply with earlier versions of SNMP, such as SNMPv1. "Fully compatible" means that the telephones will respond to queries directed either at the MIB-II or the Custom MIB. The 4600 Series IP Telephone Custom MIB is read-only (values therein cannot be changed externally via network management tools). Similarly, although the 4600 Series IP Telephone’s MIB-II has read/write permissions in accordance with the standard, to improve security any writes to MIB-II are saved but otherwise ignored.

SNMP

2-4

Page 21

Overview of Voice over IP (VoIP)

More information about SNMP and MIBs can be found in the IETF references listed in Chapter 1, Related Documents also available for download in *.txt format on the Avaya support website.

. Appendix A of this LAN Administration Guide lists the Custom MIB, which is

Network Assessment 2

The current technology allows optimum network configurations to deliver VoIP with perceived voice quality close to that of the Public Switched Telephone Network (PSTN). Not every network is able to take advantage of packet voice transmissions. Some data networks have insufficient residual capacity for even compressed voice traffic. In addition, the usual approach to developing data networks by integrating products from many vendors makes it necessary to test the components for compatibility with Voice over IP traffic.

It is assumed that your organization has performed a network assessment (with or without the assistance of Avaya) before attempting to install Voice over IP, in order to have a high degree of confidence that the existing data network has the capacity to carry voice packet traffic and is compatible with the required technology.

A network assessment would include a determination of the following:

■ A network audit to review existing equipment and evaluate its capabilities, including its ability

to meet planned voice and data needs.

■ A determination of network objectives, including the dominant traffic type, choice of

technologies, and setting voice quality objectives.

The assessment should leave you confident that the implemented network will have the capacity for the foreseen data and voice traffic, and can support H.323, DHCP, TFTP, and jitter buffers in H.323 applications.

It is important to distinguish between compliance with the minimal VoIP standards and support for QoS which is needed to run VoIP on your configuration.

Suggestions for Installation and Configuration 2

Reliability and Performance 2

There is a cost/performance trade-off associated with Voice over IP. Greater reliability and improved performance can be obtained through server redundancy and components with higher bandwidth capabilities.

The reliability and performance of the traditional PBX systems have been very high. Although much of the LAN is outside of the control of the PBX, there are several points to consider which enhance the reliability and performance of the IP Telephone network.

Network Assessment

2-5

Page 22

4600 Series IP Telephone LAN Administrator’s Guide

All 4600 Series IP Telephones support the tools "ping" and "traceroute." These are standard LAN/ WAN tools for identifying whether two points on a network can communicate with each other, and what path a sample communication takes as it traverses the network from one point to the other. All 4600 Series IP Telephones will respond appropriately to a ping or a traceroute message sent from the DEFINITY

or MultiVantageTM switch or any other source on your network, although these telephones will not, in general, initiate a ping or traceroute. With Release 1.6 of the 4600 Series IP Telephones comes support of "remote ping" and "remote traceroute." The switch can instruct such a 4600 Series IP Telephone to initiate a ping, or a traceroute, to a specified IP address. The telephone will carry out that instruction and send a message to the switch informing it of the results. See your DEFINITY

or MultiVantageTM Administration documentation for more details.

IP Address Lists and Station Number Portability 2

With Release 1.5 of the 4600 Series Telephones comes the capability to specify lists of IP addresses (either dotted decimal or DNS format) for key elements of the network, rather than merely one address for each. Specifically, you can specify up to 127 total characters in each list of the following: router/gateways, TFTP servers, and the call server. When the 4600 telephone is powered up or is rebooted, it attempts to establish communication with these various network elements in turn, starting 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 have failed.

Obviously, this capability can significantly improve the reliability of IP telephony by maximizing the likelihood the telephone can communicate with backup equipment if the primary equipment is down or inaccessible (say, perhaps due to a limited network outage).

However, this capability also has the advantage of making station number portability easier. Assume a situation where the company has multiple locations (for example, 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 power up their telephones in the new location, the local DHCP server will generally route them to the local switch, which denies service because it knows nothing about these new users. However, 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 switch.

Chapter 4 router/gateways, and TFTP servers. For specific information, see DNS Addressing

contains details on administration of DCHP servers for lists of alternate call servers,

in Chapter 4.

Security 2

In VoIP, physical wire is replaced with an IP connection. The connection is more mobile. Unauthorized relocation of the IP telephone allows unauthorized users to send and receive calls as the valid owner. For further details on toll fraud, refer to the DEFINITY documents in Chapter 1, Related Documents

or MultiVantageTM

Suggestions for Installation and Configuration

2-6

Page 23

4600 Series IP Telephones 2

Dual Connection Architecture 2

Overview of Voice over IP (VoIP)

Releases 1.0 and 1.1 of the 4600 Series IP Telephones use dual connection architecture to communicate with the DEFINITY two station extensions must be administered for each telephone.

or MultiVantageTM switch. In the dual connection architecture,

Single Connection Architecture 2

Release 1.5 and subsequent releases of the 4600 Series IP Telephones use single connection architecture to communicate with the DEFINITY connection architecture, only one station extension must be administered for each telephone.

or MultiVantageTM switch. In the single

Registration and Authentication 2

The DEFINITY Series IP Telephones using the extension and password. For further information, see Related Documents on page 1-5.

or MultiVantageTM switch supports the registering and authentication of 4600

Software 2

As shipped from the factory, the 4600 Series IP Telephones may not contain sufficient software for registration and operation. When the phone is first plugged in, a software download from a TFTP server is initiated. This gives the phone its proper functionality.

For downloads of software upgrades, the PBX provides the capability for a remote restart of the 4600 Series IP Telephone. As a consequence of restarting, the phone automatically restarts reboot procedures. If new software is available, a download will result.

WAN Considerations 2

QoS is harder on a WAN than a LAN. A LAN assumes no bandwidth concerns. A WAN assumes a finite amount of bandwidth. Therefore, QoS considerations are more significant when the IP telephony environment includes a WAN. In addition, there are administrative and hardware compatibility issues unique to WANs.

DHCP and TFTP Servers 2

The DHCP server provides the following information to the 4600 Series IP Telephone:

■ IP address of the 4600 Series IP Telephone

■ IP Address and port number of the TN799 board on the DEFINITY

server. On the call server, the standard port number is 1719.

or MultiVantageTM Call

4600 Series IP Telephones

2-7

Page 24

4600 Series IP Telephone LAN Administrator’s Guide

■ IP Address of the TFTP server

■ The subnet mask

■ IP Address of the router

You should administer the LAN so that every IP Telephone can access a DHCP server with the above information.

The IP Telephone will not function without an IP address. The failure of a DHCP server at boot time will leave all the affected voice terminals unusable. (Although it is possible for the user to manually assign an IP address to an IP Telephone, when the DHCP server finally returns, the telephone will never look for a DHCP server unless the static IP data is unassigned manually. In addition, manual entry of IP data is an error-prone process.) It is therefore strongly recommended that a DHCP server be available when the IP Telephone reboots.

A minimum of two DHCP servers is recommended for reliability.

The TFTP server provides the 4600 Series IP Telephone with a script file and, if appropriate, new or updated application software (see Step 3, Telephone and TFTP Server under Initialization Process below). In addition, you can edit the script file to customize telephone parameters for your specific environment (see Administering Options for the 4600 Series IP Telephones

in Chapter 4,

Server Administration).

Initialization Process 2

The following is a high-level description of the information exchanged when the telephone is initializing and registering. This description, which assumes all equipment is properly administered ahead of time, may be helpful in explaining how the 4600 Series IP Telephones relate to the routers and servers in your network.

Step 1: Telephone to Network 2

The telephone is appropriately installed and powered, and 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 in the network receives this message, and relays it to the appropriate DHCP server.

Step 2: DHCP Server to Telephone 2

The DHCP server provides information to the telephone, as described in DHCP and TFTP Servers on page 2-7. Among other data passed to the telephone is the IP address of the TFTP server, which is crucial for the next step.

Initialization Process

2-8

Page 25

Overview of Voice over IP (VoIP)

Step 3: Telephone and TFTP Server 2

The telephone queries the TFTP server, which transmits a script file to the telephone. This script file, at a minimum, tells the telephone which application file the telephone should be using (the application file is the software that has the telephony functionality, and can be easily updated for future enhancements).

The telephone uses the script file to determine if it has the proper application file. A newly-installed telephone will have no application file, and hence does not have the proper one. A previouslyinstalled telephone may or may not have the proper application file. In any event, if the telephone determines it does not have the application file the script file says the telephone should have, the telephone requests a download of the proper application file from the TFTP server. The TFTP server then downloads the file and conducts some checks to ensure the file was downloaded properly. If the telephone determines it already has the proper file, it proceeds to the next step without downloading the application file again.

Step 4: Telephone and the DEFINITY

/MultiVantage

Call Server 2

In this step, the telephone and the PBX exchange a series of messages which cause the display on the telephone to prompt the user. For a new installation, the user must enter the telephone’s extension and the call server password. For a restart of an existing installation, this information is already stored on the telephone, but the user must confirm the information. In either case, manual intervention is required. The telephone and the switch exchange more messaging, with the expected result that the telephone is appropriately registered on the switch.

More details about the installation process are available in the 4600 Series IP Telephone Installation Manual and in Chapter 3 of this document.

Initialization Process

2-9

Page 26

4600 Series IP Telephone LAN Administrator’s Guide

Initialization Process

2-10

Page 27

Requirements 3

Program

Introduction 3

The 4600 Series IP Telephones use Internet Protocol (IP) technology with Ethernet line interfaces. The IP telephones supplement the existing DEFINITY feature provides the user with the capability to natively administer and maintain the new 4600 Series IP Telephones.

The 4600 Series IP Telephones provide support for DHCP and TFTP over IPv4/UDP which enhance the administration and servicing of the phones. These phones use DHCP to obtain dynamic IP addresses and TFTP to download new versions of software for the phones.

The 4600 Series IP Telephones provide the ability to have one connection on the desktop for both the telephone set and the PC using the telephone’s built-in hub.

/MultiVantageTM IP Solutions platform. This

Hardware Requirements 3

Before plugging in the 4600 Series IP Telephone, verify that all of the following requirements have been met. Failure to do so will prevent the telephone from working and may have a negative impact on your network.

The following hardware is required for 4600 Series IP Telephones to work properly.

■ The DEFINITY

— DEFINITY

— MultiVantage

switch must be installed and administered correctly, with Release 8.4 or later.

Release 8.4 supports the 4612 and 4624 IP Telephones.

Release 9 and later support the 4606, 4612, and 4624 IP Telephones.

Release 10 and later support the 4630 IP Telephone.

Release 11 supports the 4602 and 4620 IP Telephones.

Introduction

3-1

Page 28

4600 Series IP Telephone LAN Administrator’s Guide

For Release 1.1 of any of the 4600 Series IP Telephones, the DEFINITY® switch must have Release 9 software installed. For Release 1.5 of any of the 4600 Series Telephones, the DEFINITY the 4600 Series IP Telephones, and for support of the 4630 IP Telephone, the DEFINITY

switch must have Release 10 software. For Release 1.7 of the 4600 Series

switch must have Release 9.5 software. For Release 1.6 of

IP Telephones, and for support of the 4602 and 4620 IP Telephones, the MultiVantage switch must have Release 11 software.

■ The following two circuit packs must be resident on the PBX server used to support the IP

telephones:

— TN2302 AP Media Processor circuit pack converts the audio levels for the IP telephone to

audio levels for DCP phones when IP phones are used in a call with non-IP telephones.

— TN799 Control-LAN (CLAN) circuit pack for the signaling capability (either the B or C

vintage) on the csi, si, and r platforms.

■ A Category 5 LAN. If the telephones are to be powered from the LAN, the LAN must comply

with the IEEE 802.3af standard for LAN powering.

■ Electrical power provided to each phone by one of the following two sources.

— A Telephone Power Module (DC power jack) (must be ordered separately).

— IEEE 802.3af, if the LAN supports this powering scheme (although the 4630 cannot be

powered this way).

■ Verify that the 4600 Series IP Telephone package includes the following components:

— 1 telephone set.

— 1 AB1C handset.

— 1 H4DU 9-foot long (when extended) 4-conductor coiled handset cord, plugged into the

telephone and the handset.

— 1 Category 5 modular line cord for the connection between the IP Telephone and the

Ethernet wall plug.

— Non-system-specific safety and installation documentation.

— Power brick

— Stylus (4630 IP Telephones only)

■ You may need a Category 5 modular line cord for the connection from the 4600 Series IP

Telephone to the PC.

Refer to the 4600 Series IP Telephone Installation Guide.

The IP telephones work the same on all DEFINITY

/MultiVantage

platforms.

Hardware Requirements

3-2

Page 29

Requirements

Software Requirements 3

The following software is required for 4600 Series IP Telephones to work properly.

■ DEFINITY

station customer options must be turned on.

■ The DHCP server and application should be installed and properly administered, as described

in DHCP

■ The TFTP server and application must be installed and properly administered, as described in

TFTP

■ For 4630 IP Telephone environments, if users are to have access to LDAP directories or

corporate Websites, the appropriate servers must be in place, and the 4630 telephones must be appropriately administered in accordance with Chapter 4, Server Administration

/MultiVantageTM Release 8.4 or later software, as appropriate. The H.323 and IP

on page 4-6.

WARNING:

A DHCP server is not mandatory, but static addressing is necessary when a DHCP server is unavailable. Due to the difficulties associated with static addressing, it is very strongly recommended that a DHCP server be installed and that static addressing be avoided.

on page 4-17.

Ensure that all required parameters are configured correctly. For DEFINITY/MultiVantage, see your administration documentation. For the DHCP and TFTP servers, see Chapter 4, Server Administration.

Figure 3-1 on the following page illustrates a sample configuration using the 4600 Series IP Telephones.

Software Requirements

3-3

Page 30

4600 Series IP Telephone LAN Administrator’s Guide

Figure 3-1. Sample Configuration Using 4600 Series IP Telephones

Software Requirements

3-4

Page 31

Server Administration 4

Introduction 4

When a 4600 Series IP Telephone is plugged in and powered, it automatically negotiates with its associated LAN to determine the Ethernet speed. From that point on, the actions taken by the phone depend in large part on the action taken in the network bef ore the phone is insta lled, and on the actions taken, if any, by the installer. This chapter discusses in detail the parameters and other data the telephone needs to operate and the alternatives for delivering that information to the telephone, where appropriate. Recommendations and specifications on which alternative(s) to choose for which parameter(s) are also provided.

The parameters under which the phone needs to operate are summarized as follows:

■ Telephone Administration on the Call Server

■ IP address management for the telephone

■ Tagging Control and VLAN administration for the telephone, if appropriate

■ Quality of Service (QOS) administration for the telephone, if appropriate

■ Site-specific Option Number (SSON) setting of DHCP servers, if appropriate

■ Interface administration for the telephone, if appropriate

■ Application-specific administration for the telephone, if appropriate (for example, Directory- or

Web-specific information required for these optional 4630 applications)

The delivery mechanisms are:

■ Maintaining the information on the Call Server (for example, the DEFINITY

switch)

■ Manually entering the information via the telephone dialpad

■ Administering the DHCP Server

■ Editing the script files on the TFTP Server

These parameters can be administered in a variety of ways, as indicated in Table 4-1, be lo w. Note that not all parameters can be administered on all delivery mechanisms.

/MultiVantageTM

Introduction

4-1

Page 32

4600 Series IP Telephone LAN Administrator’s Guide

Table 4-1. Administration Alternatives and Options for 4600 Series IP Telephones

Parameter(s) Administrative Mechanisms For More Information See:

Telephone Administration

IP Addresses DHCP (strongly recommended) DHCP and TFTP on page 4-4,

Tagging and VLAN

Call Server Administering 4600 Series IP

Telephones on DEFINITY®/ MultiVantage™ Servers on page 4-4 and Related Documents 1-5.

especially DHCP

TFTP Script files DHCP and TFTP on page 4-4 and

Administering Options for the 4600 Series IP Telephones on page 4-24.

Manual administration at the phone See "Static Addressing Installation"

in Chapter 3 of the 4600 IP

Telephone Installation Guide.

DHCP DHCP and TFTP on page 4-4, and

Administering Options for the 4600 Series IP Telephones on page 4-24.

TFTP Script files (strongly recommended)

DHCP and TFTP on page 4-4 and Administering Options for the 4600 Series IP Telephones on page 4-24.

on page 4-6.

on page

Manual administration at the phone See "Static Addressing Installation"

in Chapter 3 of the 4600 IP Telephone Installation Guide.

Quality of Service

Interface DHCP DHCP and TFTP on page 4-4, and

Introduction

DHCP DHCP and TFTP on page 4-4, and

Administering Options for the 4600 Series IP Telephones on page 4-24.

TFTP Script files (strongly recommended)

Manual administration at the phone See "QOS Option Setting" in Chapter

DHCP and TFTP on page 4-4, and Administering Options for the 4600 Series IP Telephones on page 4-24.

3 of the 4600 IP Telephone Installation Guide.

Administering Options for the 4600 Series IP Telephones on page 4-24.

4-2

Page 33

Server Administration

Parameter(s) Administrative Mechanisms For More Information See:

TFTP Script files (strongly recommended)

Manual administration at the phone See "Secondary Ethernet (Hub)

SSON DHCP Customizing the Site-Specific Option

TFTP Script files (strongly recommended)

Manual administration at the phone See "Site-Specific Option Number

Applicationspecific parameters

DHCP DHCP and TFTP on page 4-4,

DHCP and TFTP on page 4-4, and Administering Options for the 4600 Series IP Telephones on page 4-24.

Interface Enable/Disable" in Chapter 3 of the 4600 IP Telephone Installation Guide.

Number (SSON) on page 4-25; DHCP and TFTP especially DHCP

Customizing the Site-Specific Option Number (SSON) on page 4-25; DHCP and TFTP especially TFTP

Setting" in Chapter 3 of the 4600 IP Telephone Installation Guide.

especially DHCP Customizing the 4630 IP Telephone on page 4-26 and Customizing the 4620 IP Telephone on page 4-32.

on page 4-4,

on page 4-6.

on page 4-4,

on page 4-17.

on page 4-6. Also,

TFTP Script files (strongly recommended)

General information about administering DHCP servers is covered in DHCP and TFTP 4-4, especially DHCP covered in DHCP and TFTP with that material, you will be able to administer options on the telephone in accordance with Administering Options for the 4600 Series IP Telephones

on page 4-6. General information about administering TFTP servers is

on page 4-4, especially TFTP on page 4-17. Once you are familiar

DHCP and TFTP on page 4-4, especially TFTP Customizing the 4630 IP Telephone on page 4-26 and Customizing the 4620 IP Telephone on page 4-32.

on page 4-24.

on page 4-17. Also,

on page

Introduction

4-3

Page 34

4600 Series IP Telephone LAN Administrator’s Guide

Administering 4600 Series IP Telephones on DEFINITY

DEFINITY® Release 8.4 4

/MultiVantage™ Servers 4

DEFINITY Telephones are aliased as 6424 telep ho n es, adminis ter e d as IP S oft ph o nes. The adm inistrative forms for the 6424 IP Softphone are used for the two IP Telephones. See Related Documents page 1-5. Follow these guidelines:

■ Alias the I P Telephone as a 6424D+ DCP set, with the IP Softphone field set to “y.”

■ Administer a Media Complex Ext for the audio channel.

Release 8.4 supports the 4612 and 4624 IP Telephones. The 4612 and 4624 IP

DEFINITY® Releases 9, 9.5, 10, and MultiVantageTM Release 11 4

DEFINITY DEFINITY support for the 4602 and 4620 IP Telephones. Administration of a 4612 and 4624 IP telephone is identical to a 6424 IP softphone. See Related Documents

■ On the Customer Options form, verify that the IP Stations field is set to “y.” If it is not, contact

■ The IP Softphone field does not have to be set to “y.”

Releases 9 and 9.5 provide support for t he 4606, 4612, and 4624 IP Telephones.

Release 10 adds support for the 4630 IP Telephone. MultiVantageTM Release 11 adds

your Avaya sales representative.

on page 1-5. Follow these guidelines:

DHCP and TFTP 4

Dynamic Host Configuration Protocol (DHCP) provides a means by which configuration parameters can be automatically assigned to client s on a TCP/IP network. This minimizes the maintenance of a network of 4600 Series IP telephones by removing the need to assign and maintain IP addresses and other parameters for each IP telephone on the network individually.

Administering 4600 Series IP Telephones on DEFINITY®/MultiVantage™ Servers 4-4

Page 35

Server Administration

Software Checklist 4

Please make sure that you have purchased and/or own licenses to install and use the DHCP server and TFTP server software.

It is possible to install both the DHCP server and the TFTP server on the same machine.

WARNING:

The circuitry in the 4600 Series IP Telephones reserves IP addresses of the form

192.168.2.x for internal communications. The telephone(s) will not properly use addresses you specify if they are of that form.

Required Network Information 4

DHCP is the control point where an enterprise controls its IP Telephones. Before administering DHCP and TFTP, complete the information in Table 4-2 below to ensure that you have the necessary informatio n re ga rd in g your network. There may be more than one Gateway, TFTP server, subnet mask and CLAN in your configuration. You will need a copy of this table for each DHCP server.

Release 1.5 of the 4600 Series Telephones supports the ability to specify a list of IP addresses for a gateway/router, TFTP server, and DEFINITY Address Lists and Station Number Portability Each list may contain up to 127 total ASCII characters, with IP addresses separated by commas with no intervening spaces.

When specifying IP addresses for the TFTP server or call server, you can use either dotted decimal format ("xxx.xxx.xxx.xxx") or DNS names to identify the address(es). If you use DNS, note that the system value DOMAIN will be 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 specific information about DNS, see DHCP Generic Setup (page 4-24).

Table 4-2. Required Network Information Before Installation - Per DHCP Server

1. Gateway (router) IP address(es)

2. TFTP server IP address(es)

CLAN board(s), as explained in Chapter 2, IP

(page 4-7) and DNS Addressing

3. Subnet mask

4. DEFINITY CLAN IP address(es)

Software Checklist

4-5

Page 36

4600 Series IP Telephone LAN Administrator’s Guide

Table 4-2. Required Network Information Before Installation - Per DHCP Server

5. DEFINITY CLAN port

6. TFTP server file path

7. Telephone IP address range

From: To:

8. DNS Server address(es)

The TFTP server file path is the “root” directory used for all transfers by the server. This is the default directory which all files will be uploaded to or downloaded from. In configurations where the upgrade script and application files are in the default directory, item 6 should not be used.

Although this may be a value between 0 and 65535, the default value is 1719 and should not be changed unless this conflicts with an existing port assignment.

If applicable

DHCP 4

This section provides information on possible DHCP servers and generic information on administering a DHCP server.

Choosing a DHCP Configuration 4

A discussion on how to best set up your network to work with the 4600 Series IP Telephones is beyond the scope of this do cument. See Network Assessment concentrates on the simplest case of the single LAN segment. Information provided here can be extrapolated for more complex LAN configurations.

on page 2-5. This document

WARNING:

Before you start, it is important that you understand your current network configuration. An improper installation can cause network failures or reduce the reliability and performance of your network.

DHCP Software Alternatives 4

Two DHCP software alternatives are common to Windows operating systems:

■ Windows NT 4.0 DHCP Server

■ Windows 2000 DHCP Server

DHCP 4-6

Page 37

Server Administration

Any other DHCP application may work. It is the customer’s responsibility to install and configure the DHCP server correctly. This document

is limited to describing a generic administration that will work with the 4600 Series IP Telephones.

DHCP Generic Setup 4

Set up of a DHCP server involves the following phases:

1. Install the DHCP server software according to vendor instructions

2. Configure the DHCP server with the following information

■ IP add resses available for the 4600 Series IP Telephones

■ Lease duration (Infinite is recommended.)

■ The following DHCP options:

— Gatewa y (router) IP address(es) (Table 4-2, item 1). If more than one address is listed,

the total list may contain up to 127 total ASCII characters, with IP addresses

separated by commas with no intervening spaces. — Subnet mask (Table 4-2, item 3). — Option 6 (DNS server(s) address list). If more than one address is listed, the total list

may contain up to 127 total ASCII characters, with IP addresses separated by

commas with no intervening spaces. At least one addr ess in Option 6 m ust be a valid,

non-zero, dotted decimal address - otherwise, DNS will fail. — Option 15 (DNS Domain Name). This string should contain the domain name to be

used when DNS names in system parameters are resolved into IP addresses. This

domain name is appended to the DNS name before the 4600 IP Telephone attempts

to resolve the DNS address . Option 15 is necessary if you wish to use a DNS name f or

the TFTP server; ot he rw ise, you may specify a DOMAIN as part of TFTP

customization, as indicated in DNS Addressing — Option 66 (TFTP Server Name). Note: Microsoft DHCP servers support only dotted-

decimal format for TFTP addresses, not symbolic names. Option 66 need not be used

if the TFTP server is identified in the Site Specific Option string (Option 176).

However, to simplify configuration, we recommend that you use Option 66. If you use

both Option 66 and Option 176 to identify TFTP servers, the value(s) in Option 176 will

override the value(s) in Option 66. — A 4600 Series IP Telephone-specific DHCP option specifying information, such as

TFTP server and DEFINITY

CLAN IP addresses. Use the site-specific option (SSON) at #176. The value for this option should be set to either of the following strings:

on page 4-24.

MCIPADD=xxx.xxx.xxx.xxx,MCPORT=yyyy,TFTPSRVR=zzz.zzz.zzz.zzz,TFTPDIR=< path>

DHCP

4-7

Page 38

4600 Series IP Telephone LAN Administrator’s Guide

MCIPADD={list of DNS names},MCPORT=yyyy,TFTPSRVR={list of DNS names},TFTPDIR=<path>

In configurations where the upgrade script and application files are in the default directory, the TFTPDIR=<path> should not be used.

You do not have to use Option 176. For example, if the DNS server is specified in Option 6, and the Domain Name is specified in Option 15, you can use the configured names "AvayaTFTPServer" and "AvayaCallServer" for TFTPSRVR and MCIPADD, respectively.

The Call Server Name, TFTP Server Name, and SMTP Server Name must each be no more than 32 characters in length.

Where xxx.xxx.xxx.xxx is one or more IP addresses for DEFINITY

/MultiVantageTM CLAN IP boards, yyyy is the DEFINITY/MultiVantage CLAN port (1719), zzz.zzz.zzz.zzz is one or more IP addresses for TFTP servers, and <path> is the location of the location of the upgrade script and application files on the TFTP server as entered in Table 4-2, items 4, 5, 2, and 7, respectively. Each list may contain up to 127 total ASCII characters, with IP addresses separated by commas with no intervening spaces, and with quotes on either end (see the example in the NOTES below). If you use DNS, note that the system value DOMAIN will be appended to the IP addresses you specify. If DOMAIN is null, the DNS names must be fully qualified. See Administering Options for the 4600 Series IP Telephones

■ Examples of good DNS administration include the following:

on page 4-24.

- Option 6: "aaa.aaa.aaa.aaa"

- Option 15: "dnsexample.yourco.com"

- Option 66: "tftpserver.yourco.com,zzz.zzz.zzz.zzz"

- Option 176: "MCIPADD=xxxx.xxx.xxx.xxx"

■ Depending on the DHCP application you choose, you should be aware of

the fact that the application most likely will not immediately recycle expired DHCP leases. An expired lease may remain reserved for the original client for a day or more (for example, Windows NT DHCP reserves expired leases for about one da y). The intent of this reservation period is to protect a client’s lease in case the client and the DHCP server are in two different time zones, the computers’ clocks are not in synch, or the client is not on the network when the lease expires.

DHCP 4-8

■ The implication of this fact may be seen in the following example: Assume

2 IP addresses (hence 2 possible DHCP leases) and 3 IP telephones , tw o of which are using the 2 available IP addresses. When the lease expires for the first two telephones, the third will not be able to get a lease (even if the other two telephones have been removed from the network), until the reservation period expires.

Page 39

Server Administration

The 4600 Series IP Telephone sets the indicated system values to the values of the indicated fields of the DHCPACK message as indicated in Table 4-3.

Table 4-3. DHCPACK Setting of System Values

System Value Set to

IPADD The yiaddr field. NETMASK Option #1 (if received). GIPADD The first four octets of option #3 (if received). TFTPSRVR The first four octets of the siaddr field.

The remainder of this section describes some common DHCP servers.

Windows NT 4.0 DHCP Server 4

This section contains details on how to verify and configure the DHCP server included in the Windows NT 4.0 server operating system.

Use Verifying the Installation of the DHCP Server below to verify whether the DHCP server is installed. If it is not, install the DHCP server. If it is installed, go to the section Initial Configuration on page 4-9 and the following section.

Verifying the Installation of the DHCP Server 4

Use the following procedure to verify whether the DHCP server is installed.

1. Select Start->Settings->Control Panel.

2. Double-click the Network icon.

3. Verify that Microsoft DHCP Server is listed as one of the Network Services on the Services Tab.

4. If it is, go to the section Initial Configuration below. If it is not, then install the DHCP server.

Initial Configuration 4

The Windows NT 4.0 DHCP server configuration involves setting up a scope for the IP telephone. A DHCP scope is essentially a grouping of IP devices (in this case IP telephones) running the DHCP client service in a subnet. The scope is used to define parameters for each subnet. Each scope has the following properties:

■ A unique subnet mask used to determine the subnet related to a given IP address.

■ A scope name assigned by the administrator when the scope is created.

■ Lease duration values to be assigned to DHCP clients with dynamic addresses.

DHCP

4-9

Page 40

4600 Series IP Telephone LAN Administrator’s Guide

In addition, the DHCP server can assign configuration parameters to a client, and these can be specified for each individual DHCP scope.

Setting up of the Windows NT 4.0 DHCP server, requires the following steps.

1. Creating a DHCP scope for the IP Telephones.

2. Editing custom options.

3. Adding the DHCP options.

4. Activating the new scope.

Creating a DHCP Scope for the IP Telephones 4

Use the following procedure to create a DHCP scope for the IP Telephones.

1. Select Start->Programs->Admin Tools->DHCP Manager.

2. Expand Local Machine in the DHCP Servers window by double clicking on it until the + sign changes to a - sign.

3. Select Scope->Create.

4. Define the range of IP addresses used by the IP telephones listed in Line 7 of Table 4-2. The Start Address should be the first IP address to be used for the IP telephones. The End Address should be the last IP address to be used for the IP telephones. Subnet Mask should be set to the value as recorded in Table 4-2. Perform the following steps to exclude any IP addresses that you do not want to be assigned

to IP telephones within the range specified by the Start and End Addresses. a. Enter the first IP address in the range that you would like to exclude in the Start Address

field under Exclusion Range.

b. Enter the last IP address in the range that you would like to exclude in the End Address

field under Exclusion Range. c. Click the Add button. d. Repeat steps a. through c. for each IP Address range that you would like to exclude. Example Suppose the range of IP addresses available for your IP telephone network are:

■ 135.254.76.7 to 135.254.76.80

■ 135.254.76.90 to 135.254.76.200

■ 135.254.76.225 to 135.254.76.230

Your start address and end address should then be 135.254.76.7 and 135.254.76.230 respectively.

DHCP 4-10

Page 41

Server Administration

You should exclude the ranges 135.254.76.81 to 135.254.76.89 and 135.254.76.201 to

135.254.76.224.

We recommend that you provision the 4600 Series IP Telephones with sequential IP addresses.

5. Under Lease Duration, select the Limited To option and set the lease duration to the

maximum.

6. Enter a sensible name for the Name field, such as “DEFINITY IP Telephones.”

7. Click OK.

A dialog box prompts you: Activate the new scope now?

8. Click No.

You will activate the scope when all options have been set.

Editing Custom Options 4

Use the following procedure to edit custom options:

1. Select DHCP Options->Defaults in the menu.

2. Click the New button.

3. Enter “46XXOPTION” for your custom in the Add Option Type dialog.

4. Select Data Type of String and enter 176 in the Identifier field.

5. Click the OK button.

The DHCP Options menu is displayed.

6. Select the Option Name for 176 and set the value string.

7. Click the OK button.

8. Select 003 Router from the drop-down list for the Option Name field.

9. Click Edit Array.

10. Enter the Gateway IP address recorded in Line 1 of Table 4-2 for the New IP Address field .

11. Select Add and then OK.

Adding the DHCP Option 4

Use the following procedure to add the DHCP option:

1. Highlight the scope you just created.

2. Select Scope under DHCP OPTIONS.

3. Select the 176 option that you created from Unused Option List.

DHCP

4-11

Page 42

4600 Series IP Telephone LAN Administrator’s Guide

4. Click the Add button.

5. Select option 003 from the Unused Options List.

6. Click the Add button.

7. Click the OK button.

8. Chose the Global parameter under DHCP Comments.

9. Select the 176 option that you created from Unused Option List.

10. Click the Add button.

11. Click the OK button.

Activating the Leases 4

Use the following procedure to activate the leases:

1. Click Activate under the Scope Menu. The light-bulb icon for the scope is lit up.

Verifying Your Configuration 4

This section describes how to verify that the 46XXOPTIONs are correctly configured for the Windows NT 4.0 DHCP server.

Verify the Default Option, 176 46XXOPTION 4

Use the following procedure to verify the default option:

1. Select Start->Programs->Admin Tools->DHCP Manager.

2. Expand “Local Machine” in the DHCP Servers window by double clicking on it until the + sign changes to a - sign.

3. In the DHCP Servers frame, click the scope for the IP Telephone.

4. Select Defaults from the DHCP_Options menu.

5. In the Option Name pull-down list, select 176 46XXOPTION.

6. Verify that the Value String box contains the correct string from DHCP Software Alternatives on page 4-6.

If not, update the string and click the OK button twice.

Verify the Scope Option, 176 46XXOPTION 4

Use the following procedure to verify the scope option:

1. Select Scope under DHCP OPTIONS.

2. In the Active Options: scroll list, click on 176 46XXOPTION.

3. Click the Value button.

DHCP 4-12

Page 43

Server Administration

4. Verify that the Value String bo x contains the corr ect string from DHCP Generic Setup

4-7. If not, update the string and click the OK button.

on page

Verify the Global Option, 176 46XXOPTION 4

1. Select Global under DHCP OPTIONS.

2. In the Active Options: scroll list, click 176 46XXOPTION.

3. Click the Value button.

4. Verify that the Value String box contains the correct value from DHCP Generic Setup

4-7. If not, update the string and click the OK button.

on page

Windows 2000 DHCP Server 4

This section describes the configuration of the DHCP server in Windows 2000.

Verifying the Installation of the DHCP Server 4

Use the following procedure to verify whether the DHCP server is installed:

1. Select Start->Program->Administrative Tools->Computer Management.

2. Under Services and Applications in the Computer Management tree, you should find DHCP.

3. If DHCP is not installed, install the DHCP server; otherwise please skip directly to Creating

and Configuring a DHCP Scope for instructions on server configuration.

Creating and Configuring a DHCP Scope 4

Use the following procedure to create and configure a DHCP scope:

1. Select Start->Programs->Administrative Tools->DHCP.

2. In the console tree, click the DHCP server to which you wish to add the DHCP scope for the IP

telephones. Typically this will simply be the name of your DHCP server machine.

3. Select Action->New Scope from the menu.

Windows displays the New Scope Wizard to guide you through rest of the setup.

4. Click the Next button.

The Scope Name dialog box is displayed.

5. Enter a name for the scope in the Name field, such as “DEFINITY IP Telephones,” and a brief

comment in the Description field.

6. Click the Next button when finished.

The IP Address Range dialog box is displayed.

DHCP

4-13

Page 44

4600 Series IP Telephone LAN Administrator’s Guide

7. Define the range of IP addresses used by the IP telephones listed in item 7 in Table 4-2· The Start IP Address should be the first IP address available to the IP telephones. The End IP Address should be the last IP address available to the IP telephones.

8. You may define the subnet mask in one of two ways:

■ The number of bits of an IP address to use for the network/subnet IDs.

■ The subnet mask IP address.

Enter only one of these values. Click the Next button when finished. The Add Exclusions dialog box is displayed.

9. Exclude any IP addresses in the range specified in the pre vious step that you do not wish to be assigned to an IP telephone.

a. Enter the first IP address in the range that you would like to exclude in the Start Address

field under Exclusion Range.

b. Enter the last IP address in the range that you would like to exclude in the End Address

field under Exclusion Range. c. Click the Add button. d. Repeat steps a. through c. for each IP Address range that you would like to exclude.

You may add additional exclusion ranges later by right clicking on the Address Pool under the newly created scope and select the New Exclusion Range option.

Example: Suppose the ranges of IP addresses available for your IP telephone network are:

■ 135.254.76.7 to 135.254.76.80

■ 135.254.76.90 to 135.254.76.200

■ 135.254.76.225 to 135.254.76.230

Your Start IP Address and End IP Address entered on the IP Address Range dialog box should then be 135.254.76.7 and 135.254.76.230 respectively.

On the Add Exclusions dialog box, you should exclude the following ranges:

■ 135.254.76.81 to 135.254.76.89

■ 135.254.76.201 to 135.254.76.224

Click the Next button when all the exclusions have been entered. The Lease Duration dialog box is displayed.

10. Enter 30 days in the lease duration for all telephones that will receive their IP addresses from the server. This is the duration after which a device’s IP address expires and needs to be renewed by the device.

11. Click the Next button. The Configure DHCP Options dialog box is displayed.

DHCP 4-14

Page 45

Server Administration

12. Click the No, I will activate this scope later radio button.

The Router (Default Gateway) dialog box is displa yed.

13. For each router or default gateway, enter the IP address and click the Add button.

When you are done, click the Next button. The Completing the New Scope Wizard dialog box is displayed.

14. Click the Finish button.

You new scope is added under your server in the DHCP tree. It is not yet active and will not assign IP Addresses.

15. Highlight the newly created scope and select Action->Properties from the menu.

16. Under Lease duration for DHCP clients, select Unlimited and then click the OK button.

WARNING:

IP Address leases are kept active for varying periods of time. To avoid having calls terminated suddenly, make the lease duration unlimited.

Adding DHCP Options 4

Use the following procedure to add DHCP options to the scope you created in the previous procedure:

1. On the DHCP window, right-click the "Scope Options" folder under the scope you created in

the last procedure. A drop-down menu is displayed.

2. Click the Configure Options... option.

The Scope Options dialog box is displayed.

3. In the General tab page , un der t he Available Options, check the 066 ’Boot Server Host Name’

Options checkbox. The String Value dialog box is displayed.

4. Enter the TFTP Server address(es) in the string value . Use the same TFTPSR VR value format

as discussed in the TFTP Generic Setup address zzz.zzz.zzz.zzz and a second TFTP server at address tftpserver.yourco.com, in the string value enter:

"zzz.zzz.zzz.zzz,tftpserver.yourco.com"

5. Also under the Available Options, check the 176 Site-Specific Options checkbox.

6. Click the Add button and then the Edit Array button.

The IP Address Array Editor dia log box is displayed.

7. Enter the IP Address(es) for the TFTP Server(s) supporting the IP Telephones.

section. For example, if you had a TFTP server at IP

8. Click the OK button.

The Predefined Options and Values dialog box is displayed.

DHCP

4-15

Page 46

4600 Series IP Telephone LAN Administrator’s Guide

9. Click the OK button. The Predefined Options and Values dialog box is closed, leaving the DHCP dialog box

enabled.

10. Expand the newly created scope to reveal its Scope Options.

11. Click Scope Options and select Action->Configure Options from the menu.

12. In the General tab page, under the Available Options, check the 176 Site-Specific Options checkbox.

13. In the Data Entry box, enter the DHCP IP telephone option string as described in DHCP Generic Setup on page 4-7.

You can enter the text string directly on the right side o f the Data Entry box und er the ASCII label.

14. From the list in Available Options, check option 003 Router.

15. Enter the gateway (router) IP address as recorded in the IP Address field of Table 4-2.

16. Click the Add button.

17. Click the OK button.

Activating the New Scope 4

Use the following procedure to activate the new scope.

1. In the DHCP console tree, click the IP Telephone Scope created.

2. From the Action menu, select Activate. The small red down arrow o ver the scope icon disappears, indicating that the scope has been

activated.

DHCP 4-16

Page 47

Server Administration

TFTP 4

This section describes how to set up a TFTP server fo r do wnloading soft wa re update s to the 4600 Series IP Telephones.

WARNING:

The files defined by the TFTP server configuration have to be accessible from all IP Telephones. Ensure that the filenames match the nam es in the upgrade script, including case, since UNIX systems are case sensitive.

You can use any TFTP application you want. However, we strongly recommend using the TFTP application available for fre e download at www.avaya. com/suppor t. The site also contains instructions for installing and configuring the Avaya TFTP server.

TFTP Generic Setup 4

The following phases are involved in setting up a TFTP server.

■ Inst all the TFTP server software. The section below describes how to install and configure

Avaya’s TFTP application.

■ Configure the file path parameter to the directory where the files are to be stored. This is the

file path in line 6 of Table 4-2. For increased security, it is also recommended that you disable the ability to upload to the server. Note that this option may be not available to all TFTP servers.

■ In addition, y ou ma y wish to enable th e transf er size option (tsiz e) if your TFTP server supports

it. This will allow the IP telephone to display the progress of the transfer by displaying the total number of data blocks.

■ Download the upgrade script file and application file from the A vaya website (www.avaya.com/

support) to the directory as specified by the file path.

Avaya TFTP (Suite Pro) 4

Configuration 4

Use the following proced ure to configure the Avaya TFTP server:

1. Run the TFTP Suite Pro server by selecting

Start->Programs->Avaya TFTP Server >TFTPServer32. The TFTP server is started.

WARNING:

You must re-start Avaya TFTP manually every time you reboot your TFTP server machine.

TFTP

4-17

Page 48

4600 Series IP Telephone LAN Administrator’s Guide

2. Select System->Setup.

3. Enter the following values: On the Outbound tab page: 1. The Outbound path should be the TFTP file path as recorded in Table 4-2, Required Network

Information Before Installation - Per DHCP Server. The Enable Path options should be checked. Under the Options tab page: turn on the No Incoming option. Under the Client Limits tab page: Set the Maximum Simultaneous Clients to infinite by

dragging the slide bar all the way to the right.

4. Place the 46xxupgrade.scr file in the file path directory. (The filename 46xxupgrade.scr is an example, not the filename you will use. See Contents of the Upgrade Script

on page 4-19.)

4600 Series IP Telephone Scripts and Application Files

The files necessary to operate the 4600 Series IP Telephones are availab le on the following Ava y a web site:

www.avaya.com/support

Three files are needed:

■ A boot file, contain ed in the telephone when it is shipped f rom the f actory. This file contains the

software that allows the telephone to connect to the LAN and attempt to acquire necessary files and connectivity.

■ An upgrade script file, which at a minimum tells the telephone which applic ation file it should

be using. The upgrade script file can also be used to point to a file you create to specific nondefault settings for key telephone parameters.

■ An application file, which contains all the telephony functionality of the telephone.

All three files are available from the Avaya website. In general, you do not need to download the boot file, unless Avaya produces an enhancement to the file. The upgrade script and application files always must be downloaded to the TFTP server.

The Avaya-provided default script file is sufficient to allow the telephone to use default settings, or settings changed via DHCP or local progr amming on the tele phone dialpad. Ho we v er , to us e TFTP to customize values of the te lephon e par amete rs , you must create an ASCII file that resides in the same directory as the upgrade script file mentioned above. This file must be called 46xxsettings.scr or 46xxxsettings.txt (see NOTE below). This file must consist of SET commands, one per line, in this format:

SET parameter_name value

4600 Series IP Telephone Scripts and Application Files 4-18

Page 49

Server Administration

where parameter_name and value are as defined in Tables 4-4, 4-5, and 4-6. Invalid values cause the specified value to be ignored for the associated parameter_name; the default value is retained..

Most Windows systems interpret the file extension *. scr as a scree n saver. T he 4600 IP Telephones originally used *.scr to indicate a script file, but starting with Release

1.7, the file name can also have the extension *.txt.

If you choose to create a custom parameter file, you can edit the last line of the Avaya-provided default script file to be GET 46xxxsettings.txt.

All values should be text strings, even if the data itself is numeric, a dotted-decimal IP address, etc.

You are encouraged not to alter the Avaya-p rovided upgrade script file. If Avaya changes the file in the future, to accommodate new features or functionality, any changes you might have made would be lost. You are strongly encour aged to use the 46xxsettings.scr file to manage your customization.

The GET command causes the telephone to use TFTP to attempt to download the file specified in the GET command. This file is assumed to be at the same directory as the current upgrade script file. If the file sp ecified in the GET command is successfully obtained, its contents are interpreted as an additional script file - that is how your options are set. If the file cannot be obtained, interpretation of the rest of the current script file is terminated (which is why we indicate the GET should be at the end of the script file). You can change the name of the file in the GET command; just ensure the target file is identically named and is located appropriately.

Table 4-4 lists the parameters, descriptions, and acceptable values for all 4600 Series IP Telephones. Table 4-5 lists the parameters, descriptions, and acceptable values specific to applications on the 4630 IP Telephone. T ab le 4-6 lists the parameters, descriptions and acceptable values specific to applications on the 4620 IP Telephone.

Contents of the Upgrade Script 4

The following is a sample upgrade script file:

The filenames 4624_000301.BIN, 4606_000301.BIN, and 4630_00301.BIN used in this sample are examples only. The names do not match those that are used in production.

IF $BOOTNAME SEQ 46XXCOMMON.V03 GOTO GETAPP SET APPNAME REPLBOOT_V3.APP GOTO END

4600 Series IP Telephone Scripts and Application Files

4-19

Page 50

4600 Series IP Telephone LAN Administrator’s Guide

#GETAPP IF $MODEL4 SEQ 4630D01A GOTO SCREENSETS IF $MODEL4 SEQ 4624D01A GOTO BIGSETS IF $MODEL4 SEQ 4612D01A GOTO BIGSETS IF $MODEL4 SEQ 4606D01A GOTO SMALLSETS

#SCREENSETS SET APPNAME 4630_000301.BIN

GOTO END

#BIGSETS SET APPNAME 4624_000301.BIN

GOTO END

#SMALLSETS

SET APPNAME 4606_000301.BIN

#END GET 46XXSETTINGS.SCR

QoS 4

The 4600 Series IP Telephones support both IEEE 802.1D/Q and DiffServ, and may in the future support other, possibly proprietary, procedures for implementing Quality of Service. In addition, other network-based QoS initiatives such as UDP port selection do not require support by the telephones, but nonetheless can contribute to improved QoS for the entire network.

IEEE 802.1D and 802.1Q 4

IEEE’s 802.1Q standard defines a tag that can be added to v oice and data packets. Most of the information associated with this tag deals with Virtual LAN (VLAN) management, but 3 bits are reserved for identifying pac ket priority. These 3 bits allow any one of 8 priorities to be assigned to a specific packet. As defined in the standard, the 8 priorities are, from highest to lowest:

■ 7: Network management traffic

■ 6: Voice traffic with less than 10ms latency

■ 5: Voice traffic with less than 100ms latency

■ 4: “Controlled-load” traffic (mission-critical data applications)

■ 3: Traffic meriting “extra-effort” by the network for prompt delivery (for example, executives’

e-mail)

■ 2: Reserved for future use

■ 0: Traffic meriting the network’s “best-effort” for prompt delivery (the default priority)

QoS 4-20

Page 51

Server Administration

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

Priority 0 is a higher priority than Priority 1.

To support IEEE 802.1D/Q, the 4600 Series IP Telephones can be administered either from the network, via appropriate administration of the DHCP or TFTP servers , or at the telephone itself , via dialpad input. Specific implementation details f or local administra tion are in the Installation Manual, and for remote administration are in this chapter, in 4600 Series IP Telephone Scripts and Application Files on page 4-18. In summary, three IEEE 802.1D/Q QoS parameters in the telephones can be administered. These parameters are:

■ L2Q: setting the 802.1Q framing parameter ON or OFF

■ L2QAUD: setting the 802.1Q audio priority value (between 0 and 7, default is 6)

■ L2QSIG: setting the 802.1Q signaling priority value (between 0 and 7, defa ult is 6)

The 4600 Series IP Telephones can simultaneously support receipt of packets using, or not using,

802.1Q parameters.

WARNING:

If you turn VLAN framing on (L2Q=1) using the TFTP-based upgrade script (46xxupgrade.scr), and you set your VLAN ID (L2QVLAN) to something other than your default VLAN ID, the IP address you are using for the telephone will probably be wrong for the new VLAN. See Administering Option s for the 4600 Series IP Telephones for more information.

DIFFSERV 4

As defined in IETF RFCs 2474 and 2475, “services” are basically w ays of t reating diff erent subsets of a network’s traffic in different ways at the Internet Protocol (IP) layer, Lay er 3. For example, some packets might be rout ed in such a way as to expedite delivery (minimize delay), while others are routed to minimize loss, minimiz e cost, etc. Th e differentiation between these services (that is, Differentiated Services) is provided by a redefinition of an octet in the Layer 3 headers for IP versions 4 and 6, also termed IPv4 and IPv6, respectively. This octet is called a Type of Service (TOS) octet in IPv4 and a Traffic Class octet in IPv6, but in both cases the octet is interpreted differently than it was originally defined. With Differentiated Services, bits 0 through 5 of the octet identify a Differentiated Services Code Point (DSCP) that identifies a procedure to be used to handle that packet on a per-hop basis. Bits 6 and 7 of the octet are currently unused, and are ignored by DSCP-compliant routers.

With DiffServ , the def ault DSCP is all zeroes , and represents “no special ha ndling”. RFC 2474 also defines eight “Class Selector Codepoints”, which are the eight DSCP encodings that can be represented by xxx000 where “x” represents one bit. These Code Selector Codepoints are considered prioritized, with the larger numerical values having a higher relative order. DSCPcompliant routers should treat larger-valued DSCPs in such a way as to give the associated packets a “probability of timely forwarding” grea ter than a packet with a lower-valued DSCP. In addition to the eight Class Selector Codepoints, a network may define its own DSCPs by defining

QoS 4-21

Page 52

4600 Series IP Telephone LAN Administrator’s Guide

encodings that do not terminate in 000. The specific treatment intended by these custom DSCPs will not necessarily be carried out by routers outside the customer’s own network.

To support DiffSe rv, the 4600 Series IP Telephones are administered at the switch in accordance with the documentation for the switch.

UDP Port Selection 4

Some data networks include equipment that can perform UDP port selection. This is a mechanism by which packets with port numbers in a given range are given priority over packets with port numbers outside that range.

To support UDP port selection, the 4600 Series IP Telephones can be administered either from the network, via appropriate administration of the DHCP or TFTP servers , or at the telephone itself , via dialpad input. Specific implementation details for local administration are in the 4600 Series IP Telephone Installation Guide, and, for remote administration, in 4600 Series IP Telephone Scripts and Application Files on page 4-18. In summary, the system value MCPORT represents the port on the TN2302AP board. This port number can be used to administer routers, etc. that support UDP port selection, to maximize the priority given to the voice packets being exchanged between the PBX and the telephone.

The default value for MCPORT is 1719. The switch must be administered to use a port within the proper range for the specific LAN, and the IP Telephone(s) will copy that port. A related parameter is PORTAUD, which is the RTP port used by the switch. In accordance with standards RFC 1889 and 1890, the IP Telephone uses a default value for PORTAUD of 5004. MCPO RT and PORTAUD are both administrable (see Administering Options for the 4600 Series IP Telephones 4-24).

on page

QoS with 4620 and 4630 IP Telephones 4

As of Release 1.7, both the 4620 and 4630 telephones offer the end user an opportunity to monitor network audio performance while on a call. The user guides f or ea ch phone go into specific d etails on how the user gets to the appropriate screen; th is document tells you what the end user can see , and what it means. Specifically, the following parameters are displa y ed in re al-time to users o n the appropriate screens, while on a call:

Parameter Possible Values

Audio Connection Present? Yes (if a receive RTP stream has been established)

No (if a receive RTP stream has not been established)

Received Audio Coding G.711 or G.729 Silence Suppression Yes (if the telephone knows the far-end has silence

suppression Enabled)

QoS 4-22

No (if the telephone knows the far-end has silence suppression Disabled, or the telephone does not know either way)

Page 53

Server Administration

Parameter Possible Values

Packet Loss "No data" or a decimal 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 look-ahead 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

In addition, based on the current values for the above parameters, the Network Audio Quality Screen presents the user with a qualitative assessment of the o verall audio quality currently being experienced. This assessment is based on separate evaluations of the Packet Loss and the total Network Delay (the sum of Packetization Delay, One-way Network Delay, and Network Jitter Compensation Delay), and consideration of the codec in use.

The implication of this information for LAN administration depends, of course, on the values reported by the user and the specific nature of your LAN (topology, loading, QoS administration, etc.) The major use for this information is to give the user an idea of how network conditions are affecting the audio quality of the current call. It is assumed you have more detailed tools available for troubleshooting the LAN.

An integer number of milliseconds reporting the average delay introduced by the telephone’s jitter buffer.

RSVP and RTCP 4

Resource ReSerVation Protocol (RSVP) is an IETF-standard protocol used by hosts to request resource reservations throughout a network. RSVP-compliant hosts send messages through a network to receivers, which respond with messag es requesting a type of service and an amount of resources (e.g., bandwidth) to carry out that service. The host is responsible for admitting (approving) or rejecting (denying) the request. In a QoS context, RSVP is used to try to reserve bandwidth in the network for voice calls , on a call-b y-call basis. If insufficient bandwidth is av ailab le for the target voice quality, a request to use network bandwidth for a voice call will be rejected.

RTP Control Protocol (RTCP), as its name implies, is a protocol that provides control functions for Real-time Transport Protocol (RTP). RTP provides end-to-end network services for real-time data (such as Voice over IP), but does not provide a reservation function, nor does it guarantee any level of QoS. RTCP supplements RTP by monitoring the quality of the RTP services and can provide real-time information to users of an RTP service. In a QoS context, RTCP is valuable for identifying information such as pac ket loss, 1-way delay (how long a packet has to go from source

QoS 4-23

Page 54

4600 Series IP Telephone LAN Administrator’s Guide

A to destination B), jitter , etc. RTCP itself does not improve QoS, but it pro vid es information to you to help identify where problem areas might be.

You cannot change the telephone’s RSVP or RTCP parameters directly on the telephone or via TFTP or DHCP administration. The only way to change these parameters is by appropriate administration of the s witch. See y our DEFINITY detail.

/MultiVantageTM administration material for more

Administering Options for the 4600 Series IP Te l ep h on e s

As indicated in the Introduction administered for the 4600 Series IP Telephones. This section explains how to change parameters via the DHCP or TFTP servers. In all cases, you will be setting a system parameter in the telephone to a desired value. Table 4-4 lists the parameter names, their default values, the valid ranges for those values, and a description of each one. For DHCP, the parameters below are set as desired to desired values in the DHCP Option as discussed in DHCP Generic Setup this chapter. For TFTP, the parameters below are set as desired to desired values in the TFTP Script File as discussed in Contents of the Upgrade Script

TFTP Scripts are the recommended way to administer options on the 4600 Series IP Telephones. Some DHCP applications have limits on the amount of user-specified information; such limits could be exceeded by the administration required, for example, a 4630 with all applications administered.

of this chapter, there are many parameters that can be

earlier in

also earlier in this chapter .

DNS Addressing 4

As of Release 1.5, the 4600 IP Telephones support DNS addresses as well as dotted decimal addresses. The telephone attemp ts to resolv e a non- ASCII-encoded dot ted decimal IP address b y checking the contents of DHCP Option 6, as indicated in DHCP Generic Setup one address in Option 6 must be a valid non-zero dotted decimal address - otherwise, DNS will fail. The text string in the system parameter DOMAIN (Option 15, see Table 4-4) is appended to the address(es) in Option 6 befor e the telephon e attempts to resolve the DNS address. If Option 6 contains a list of DNS addresses, they are queried in the order given, if no response is received from previous addresses on the list. Alternatively to administering DNS via DHCP, you may specify the DNS server and/or Domain name in the TFTP script file (in which case, you should SET the values for DNSSRVR and DOMAIN first; then you may use those names later in the script).

, page 4-7. At least

If Options 6 and 15 are appropriately administered with DNS servers and Domain names, respectively, MCIPADD and TFTPSRVR settings need no t be specified in the Site Specific Option string.

Administering Options for the 4600 Series IP Telephones 4-24

Page 55

Customizing the Site-Specific Option Number (SSON) 4

Server Administration

As discussed in DHCP Generic Setup Series IP Telephones, can be set to a string. For each system parameter listed in Table 4-4 that you want to include, append the following to the SSON string:

a comma followed by name=value where name is a parameter name and value is its associated value. Invalid values will cause the

data to be ignored for that name. Customizing the SSON will affect all telephones associated with that DHCP server.

on page 4-7, the SSON, defined to be 176 for the 4600

Entering Options via the Telephone Dialpad 4

Chapter 3 of the 4600 Series IP Telephone Installation Guide details how to use the local administrative options.

To customize any or all of the QoS param eters locally, follow the “QoS Option Setting” procedure in Chapter 3 of the 4600 Series IP Telephone Installation Guide.

To enable or disable the secondary Ethernet hub locally, follow the “Secondary Ethernet (Hub) Interface Enab le/Disable” procedure in Chapter 3 of the 4600 Series IP Telephone Installation Guide.

To view the 4600 IP Telephone system parameters, refer to Chapter 5, The View Administrative Option, page 5-8.

Table 4-4. 4600 Series IP Telephone Customizable System Parameters

Parameter Name Default Value Description and Value Range

DNSSRVR " " (Null) Text string containing the IP address of one or more

DNS servers (at least one of which must be a valid, non-zero, dotted decimal address.

DOMAIN " " (Null) Text string containing the domain name to be used

when DNS names in system values are resolved into IP addresses.

IRSTAT 1 Text string containing status of Infrared interface (0=

off/disabled, 1= on/enabled). L2Q 0 802.1Q framing (1= on or 0= off). L2QAUD 6 Layer 2 audio priority value (0 to 7). L2QSIG 6 Layer 2 audio priority value (0 to 7).

Administering Options for the 4600 Series IP Telephones

4-25

Page 56

4600 Series IP Telephone LAN Administrator’s Guide

Table 4-4. 4600 Series IP Telephone Customizable System Parameters —Continued

Parameter Name Default Value Description and Value Range

L2QVLAN 0 802.1Q VLAN IDentifier (0 to 4095). MCPORT 1719 Call server transport-layer port number (0-65535). PHY2STAT 1 Secondary Ethernet interface status (0=off/disabled,

1=on/enabled). This parameter was called "HUBSTAT" in telephones supporting Releases 1.0 through 1.5; 4600 Series IP Telephones supporting Release 1.6 will respond to changes to "HUBSTAT" by changing "PHY2STAT".

Table 4-4 applies to all 4600 Series IP Telephones. The 4630 and 4620 IP Telephones have additional, optional administration. See Customizing the 4630 IP Telephone and Customizing the 4620 IP Telephone, below, for more information.

Customizing the 4630 IP Telephone 4

The 4630 IP Telephone has some unique and powerful capabilities that take advantage of its large display and access to LAN facilities. If your organization has an LDAP-compliant directory on your LAN, or if your organization has a corporate website su itable for displaying on the 4630’s 1/4-VGA display, you will need to provide the telephone with key information about the servers that provide those facilities. Specifically, to administer the 4630 telephone for the LDAP Directory application, you must provide t he information called for in Table 4-5, below. To administer the 4630 telephone for the Web Access application, you must provide the information called for in Table 4-5 on page 4-27. This information must be pro vided in a cust omized script file , in accordance with 4600 Series IP Telephone Scripts and Application Files on page 4-18.

CAUTION:

For the 4630 to work properly, you must have a 46xxsettings.scr file in the same directory as the 4630 application file. If you do not edit the 46xxsettings.scr file, the 4630 will use default settings only. The 46xxsettings.scr file is part of the *zip file on the software download website, and is also available as a standalone download. If you already have such a file because you downloaded it for a previous release of the 4630, installing the *zip file will overwrite the original file.

In Table 4-5, parameters shown with a Mandatory status must be accurate and non-null for the application to work (howev er, the Ava ya Help website will alw a ys be av ailab le). P arameters with an Optional status may be changed to suit your environment; if they are not changed, the defaults will be used.

Administering Options for the 4600 Series IP Telephones 4-26

Page 57

Server Administration

Table 4-5. 4630 IP Telephone Customizable System Parameters by Application

Description and Value

Parameter Name Default Value Status

Phone Application Parameters:

PHNEMERGNUM " " (Null) Optional Text string of a phone

Directory Application Parameters:

DIRSRVR " " (Null) Mandatory Text string of dotted decimal

DIRTOPDN " " (Null) Mandatory "Directory Topmost

Range

number to be dialed in case of an emergency (e.g., 911)

IP address, or DNS name, of the server containing the LDAP directory.

Distinguished Name"; text string of the root entry of the LDAP directory.

DIRFULLNAME cn Optional Text string for the customer-

specific label for the database field.

DIRTELNUM telephoneNumber Optional Text string for the customer-

specific label for the database field containing telephone numbers. The default is the standard LDAP value.

DIRSRCHTIME 0 Optional Text string for an integer

number of seconds; the maximum duration the LDAP directory should spend searching before reporting completion or failure of the search. The default is LDAP-standard for "unlimited duration."

Administering Options for the 4600 Series IP Telephones

4-27

Page 58

4600 Series IP Telephone LAN Administrator’s Guide

Description and Value

Parameter Name Default Value Status

DIRUSERID " " (Null) Optional Text string for "Directory

DIRSRVRPWD " " (Null) Optional Text string for "Directory

DIRCODING Latin 1 Optional Text string identifying the

Range

User ID," which should be modified if the LDAP server requires a User ID and password for access to the Directory.

Server Password," which should be modified if the LDAP server requires a User ID and password for access to the Directory.

character set used by the LDAP directory. Besides the default value, "ASCII" is the other valid value.

DIRLDAPPORT 389 Optional Directory LDAP Port; the

port used to exchange LDAP messages with the server.

Stock Ticker Application Parameters:

STKSTAT 1 Optional Text string identifying

whether the 4630 phones are allowed to have the Stock Ticker Application. "1" is the default in the 4630; "0" disables the Stock Ticker Application.

Voice Mail Application Parameters:

VMLCODING ASCII Optional Text string identifying the

character set used by the Voice Mail Server Application. Besides the default value, other supported values include "Latin 1" and "Unicode". Note that "Unicode" includes support only for the Latin characters of Unicode.

Administering Options for the 4600 Series IP Telephones 4-28

Page 59

Server Administration

Description and Value

Parameter Name Default Value Status

VMLHOME " " (Null) Mandatory Text string containing the

Web Access Application Parame te r s:

WEBHOME " " (Null) Mandatory Text string containing the

WEBPROXY " " (Null) Optional Text str ing containin g the IP

Range

URL of the home page for the Voice Mail Application.

URL of the home page for the Web Access application.

address, in dotted decimal or DNS format, of an HTTP proxy server. This parameter is optional if the web pages to be accessed by the user are all on your organization’s intranet.

WEBEXCEPT " " (Null) Optional Text string containing a list

of one or more HTTP proxy server exception domains, separated by commas, up to a total of 127 ASCII characters. This parameter is optional if the web pages to be accessed by the user are all on your organization’s intranet. If WEBPROXY is null, the value of this parameter is ignored.

WEBPORT 80 Optional Text string containing the

TCP port number for the HTTP proxy server. The default is the TCP default for HTTP. This parameter is optional if the web pages to be accessed by the user are all on your organization’s intranet. If WEBPROXY is null, the value of this parameter is ignored.

Administering Options for the 4600 Series IP Telephones

4-29

Page 60

4600 Series IP Telephone LAN Administrator’s Guide

Description and Value

Parameter Name Default Value Status

WEBCODING ASCII Optional Text string containing the

Backup/Restore Parameters:

Range

coding to be used for characters entered in forms on web pages. Besides the default, other supported values include "Latin 1" and "Unicode". Note that "Unicode" includes support only for the Latin characters of Unicode.

FTPSRVR " " (Null) Mandatory

(but can be userspecified

FTPDIR " " (Null) Optional

(and can be userspecified)

For assistance in developing local websites tailored to the 4630 IP Telephone’s display, see Appendix B:

Creating Websites for the 4630 IP Telephone.

Text string containing a 4octet for the FTP server to be used for storage and retrieval of 4630 user information (see 4630 Backup/Restore, page 4-

Path name for the directory on FTPSRVR used for storage and retrieval of 4630 user information.

4630 Backup/Restore 4

Backup/Restore automatically saves a phone’s speed dial button labels and options/parameter settings. When the Automatic Backup option on a 4630 IP Telephone is set to "Yes" and the FTPSRVR is specified, the FTPSTOR command attempts to save all Speed Dial contents and all system options and (non-password) parameters to the FTP server (specified by FTPSRVR in the directory path specified by FTPDIR). Data is saved in an ASCII text file called "4630data.txt". The System Administrator may optionally specify FTPSRVR and/or FPTDIR via network administration, however, these values may also be specified by the phone’s user, as covered in "Chapter 8" of the 4630 IP Telephone User’s Guide. Automatic backup occurs whenever the user executes a Save command on a Speed Dial or Options/Parameter screen.

Administering Options for the 4600 Series IP Telephones 4-30

Page 61

Server Administration

In addition to Speed Dial labels and associated phone numbers, the following options and nonpassword parameters are saved during a backup:

Setting/Parameter Name Type

Idle Timeout Option Keyboard Layout Option Click Feedback Option Edit Dialing Option Personalized Ring Option Redial Option Go to Phone on Answer Option Go to Phone on Originate Option Call Timer Option Alphabetize Entries? Option Call Log Active? Option Call Log Automatic

Archive Directory User ID Parameter Automatic Backup Option FTP Server IP Address Parameter FTP Directory Path Parameter FTP User ID Parameter Stock Ticker Active? Option STK.mm Parameter Stock Index DJIA Option Stock Index S&P 500 Option

Option

Stock Index Nasdaq Option

Administering Options for the 4600 Series IP Telephones

4-31

Page 62

4600 Series IP Telephone LAN Administrator’s Guide

Setting/Parameter Name Type

Stock Change Option Stock Volume Option

If the Automatic Backup option is set to "No," speed dial data, options and parameter settings are not saved unless the user forces a one-time backup via the appropriate option (as covered in "Chapter 8" of the 4630 IP Telephone User’s Guide). Restoring backed-up data is done via a separate user option, also covered in "Chapter 8" of the 4630 IP Telephone User’s Guide.

For specific error messages relating to Backup/Restore, see Table 5-4 on page 5-1 3.

Call Log Archive 4

Automatic archiving of the Call Log occurs when:

■ The Call Log Automatic Archive option setting is "Yes" and

■ The Call Log is more than 50% filled with unarchived entries, or a new (unarchived) log entry

occurs within two hours of the last archive (whichever occurs first).

Call Log Archive automatically saves applicable Call Log entries. When the Call Log Automatic Archive option on a 4630 IP Telephone is set to "Yes" and the FTPSRVR is specified, the FTP APPE command attempts to save all call log contents to the FTP server (specified by FTPSRVR in the directory path specified by FTPDIR). Data is saved in a file called "4630calllog.txt". The System Administrator may optionally specify FTPSRVR and/or FPTDIR via network administration, however, these values may also be specified by the phone’s user, as covered in "Chapter 8" of the 4630 IP Telephone User’s Guide. Automatic backup occurs whenever the user executes a Save command on a Speed Dial or Options/Parameter screen.

For specific error messages relating to Archiving, see Table 5-4 on page 5-13.

Customizing the 4620 IP Telephone 4

In Table 4-6, parameters shown with a Mandatory status must be accurate and non-null for the application to work. Parameters with an Optional status ma y be ch anged t o suit your environment; if they are not changed, the defaults will be used.

Administering Options for the 4600 Series IP Telephones 4-32

Page 63

Server Administration

Table 4-6. 4620 IP Telephone Customizab le System Parameters

Description and Value

Parameter Name Default Value Status

Web Access Application Parame te r s:

WMLHOME " " (Null) Mandatory Text string containing the

WMLPROXY " " (Null) Optional Text string containing the IP

WMLEXCEPT " " (Null) Optional Text string containing a list

Range

URL of the home page for the Web Access application.

address, in dotted decimal or DNS format, of an HTTP proxy server. This parameter is optional if the web pages to be accessed by the user are all on your organization’s intranet.

of one or more HTTP proxy server exception domains, separated by commas, up to a total of 127 ASCII characters. This parameter is optional if the web pages to be accessed by the user are all on your organization’s intranet. If WMLPROXY is null, the value of this parameter is ignored.

WMLPORT 80 Optional Text string containing the

TCP port number for the HTTP proxy server. The default is the TCP default for HTTP. This parameter is optional if the web pages to be accessed by the user are all on your organization’s intranet. If WMLPROXY is null, the value of this parameter is ignored.

Administering Options for the 4600 Series IP Telephones

4-33

Page 64

4600 Series IP Telephone LAN Administrator’s Guide

Description and Value

Parameter Name Default Value Status

WMLCODING ASCII Optional Text string containing the

For assistance in developing local websites tailored to the 4620 IP Telephone’s display, see Appendix C:

Creating Websites for the 4620 IP Telephone.

Range

Administering Options for the 4600 Series IP Telephones 4-34

Page 65

Troubleshooting Guidelines 5

Introduction 5

This chapter describes problems that may occur during operation of the 4600 Series IP Telephones and possible ways of resolving these problems.

Error Conditions 5

Table 5-1 below identifies some of the possible operational problems that might be encountered after successful installation of a 4600 Series IP Telephone. Problems that might be encountered during installation, and how to conduct a Self-Test of the telephone, are discussed in the Troubleshooting chapter of the 4600 Series IP Telephone Installation Guide. The 4630 IP Telephone User’s Guide and 4620 IP Telephone User’s Guide also contain guidance for users having problems with specific 4630 and 4620 applications, respectively.

Most of the problems reported by users of a 4600 Series IP Telephone are likely not to be problems with the telephone itself. More likely, the problems will be centered on the LAN, where Quality of Service, server administration, and other issues can impact end-user perception of IP Telephone performance.

Table 5-1. Some Error Conditions in Operation of 4600 Series IP Telephones

Condition Cause/Resolution

The telephone continually reboots, or reboots continuously about every 15 minutes.

The message light on the telephone turns on and off intermittently, but the telephone never registers.

CAUSE: This is a firmware fault; the MAC address in memory is corrupted.

RESOLUTION: The telephone must be returned to Avaya for repair.

CAUSE: This is a hardware fault.

RESOLUTION: The telephone must be

returned to Avaya for repair.

Introduction

5-1

Page 66

4600 Series IP Telephone LAN Administrator’s Guide

Table 5-1. Some Error Conditions in Operation of 4600 Series IP Telephones —Continued

Condition Cause/Resolution

The telephone stops working in the middle of a call,

The telephone had been working, but does not work now,

AND No lights are lit on the phone and the display is not lit.

AND Power to the telephone is fine (and the telephone may have gone through the restarting sequence).

AND no lights are lit on the phone and the display is not lit.

power to the telephone is fine, but there is no dialtone. (Display might show “System Busy”).

CAUSE: Loss of power

RESOLUTION: Check the connections

between the telephone, the power supply, and the power jack.

CAUSE: DHCP Lease expired or DHCP server not available when telephone attempts to renegotiate DHCP lease.

RESOLUTION: Short-term, restart the telephone.

Long-term, administer the DHCP application to allow longer leases (“Infinite” or “Unlimited” is recommended).

CAUSE: Loss of power.

RESOLUTION: Check the connections

between the telephone, the power supply, and the power jack.

CAUSE: Loss of communication with the PBX switch

RESOLUTION: Check LAN continuity from the PBX to the telephone (using ping or trace-route), and from the telephone to the PBX (by invoking a feature button). Verify the LAN administration has not changed for the TN799 or TN 2302AP boards, or the LAN equipment (routers, servers, etc.) between the switch and the telephone. Verify no one has locally changed the telephone settings (by using the VIEW and ADDR codes, as described in the

4600 Series IP Telephone Installation Guide). Verify the volume on the

telephone is set high enough. Finally, conduct a self-test.

Error Conditions

5-2

Page 67

Troubleshooting Guidelines

Table 5-1. Some Error Conditions in Operation of 4600 Series IP Telephones —Continued

Condition Cause/Resolution

The telephone had been working, but does not work now, (continued)

The telephone works, but the audio quality is poor, specifically:

AND the telephone was recently moved.

the network was recently changed (servers upgraded or replaced, your DEFINITY/MultiVantage switches, etc.).

the user hears echo when speaking on a handset.

CAUSE: Loss of communication with the PBX.

RESOLUTION: As above, but pay particular attention to the possibility that the telephone is being routed to a different DHCP server, or even a different PBX switch. If so, the new server or switch may need to be administered to support the telephone.

CAUSE: Loss of communication with the PBX.

RESOLUTION: As above.

CAUSE: Echo from digital-to-analog

conversion on your DEFINITY/ MultiVantage trunk.

RESOLUTION: Verify which trunk is causing the echo, and swap the trunk’s Trunk Termination parameter on the PBX.

the user hears echo on a headset, but not on a handset.

the user is on speakerphone and hears no echo, but the far end hears echo.

CAUSE: Improper headset adapter.

RESOLUTION: Replace adapter with

Avaya’s M12LU or 3412-HIC adapters. The M12LU is recommended, since it supports Automatic Gain Control.

CAUSE: Room acoustics

RESOLUTION: Ensure there are six

inches or so of blank space to the right of the telephone. If that is insufficient, use the handset.

Error Conditions

5-3

Page 68

4600 Series IP Telephone LAN Administrator’s Guide

Table 5-1. Some Error Conditions in Operation of 4600 Series IP Telephones —Continued

Condition Cause/Resolution

the user experiences sudden silences (gaps in speech), static, clipped or garbled speech, etc.

The 4612 or 4624 IP Telephone works properly except the phone does not ring.

The telephone works properly except for the speaker.

CAUSE: Jitter, delay, dropped packets, etc.

RESOLUTION: One or more Quality of Service (QoS) features should be implemented in the network (See Chapter 3 of the 4600 Series IP Telephone Installation Guide).

CAUSE: Improper (non-Category 5) wiring.

RESOLUTION: Replace non-Category 5 wiring with Category 5 wiring.

CAUSE: The Ringer Off (RngOF) softkey feature has been activated.

RESOLUTION: Use the softkey Menu option to access the RngOF feature. A downward-pointing triangle means the Ringer is off. Ensure the triangle points up. Also, check the Volume setting on the telephone. Finally, do a Self-test on the telephone.

CAUSE: The Speaker was turned off on the PBX.

The telephone works properly, except incoming DTMF tones are not received.

Error Conditions

5-4

RESOLUTION: Administer the PBX to allow that station’s speaker to operate. If that does not work, do a Self-test on the telephone.

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

RESOLUTION: None; the board is operating as designed.

Page 69

Troubleshooting Guidelines

Table 5-1. Some Error Conditions in Operation of 4600 Series IP Telephones —Continued

Condition Cause/Resolution

The telephone works properly, except sidetone DTMF is not heard.

Hands-Free Answer (HFA) is administered but the telephone did not automatically answer a call.

The TFTP application terminates and asks for registration.

CAUSE: PBX suppresses sidetone DTMF.

RESOLUTION: On PBX administration, on the Change-System-Parameters screen, enable On-Hook Dialing. If the user has Hands-Free Answer (HFA) and answers the call on the telephone’s speakerphone, then switches to the handset, pressing the dialpad buttons does not send DTMF tones. This is a known bug, and the only current resolution is to disable HFA.

CAUSE: HFA only works if the telephone is idle. If a second call comes into the telephone while the first call is in progress (including ringing before the first call is answered), the second call is ignored.

RESOLUTION: None.

CAUSE: Non-Avaya shareware or

freeware TFTP applications often cease operating to request registration.

RESOLUTION:

Short-term: Restart the application.

Long-term: Register the product or

replace it with an application that does not behave this way (for example, Avaya’s TFTP application).

Error Conditions

5-5

Page 70

4600 Series IP Telephone LAN Administrator’s Guide

Table 5-1. Some Error Conditions in Operation of 4600 Series IP Telephones —Continued

Condition Cause/Resolution

The TFTP script file is ignored or not used by the telephone

AND the TFTP server is a LINUX or UNIX system.

Power to the telephone is interrupted while the telephone is saving the application file and the TFTP application hangs.

CAUSE: The telephone expects lines of the script file to terminate with a <Carriage Return><Line Feed>. Some UNIX applications only terminate lines with <Line Feed>. Editing the script file with a UNIX-based editor can strip <Carriage Return>s from the file, causing the entire file to be treated as a comment, and thus be ignored.

RESOLUTION: Edit the script file with a Windows-based editor, or another editor that does not strip out the <Carriage Return>.

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.

CAUSE: The TFTP server hangs if power is interrupted while a telephone is saving the application file.

The DHCP server indicates the 4600 Telephone reports itself as a Token Ring device, and refuses to provide the telephone an address.

Error Conditions

RESOLUTION: Restart the TFTP server.

CAUSE: Early versions of the 4600 Series Telephones erroneously report being a Token Ring device. With most DHCP servers, this does not matter. Some LINUX servers, however, will refuse to issue addresses to Ethernet devices reporting to be Token Ring devices.

RESOLUTION: Administer the DHCP server to delete all MAC and IP addresses associated with Lucent Technologies or Avaya, or allow the associated DHCP leases to expire.

5-6

Page 71

Troubleshooting Guidelines

Table 5-1. Some Error Conditions in Operation of 4600 Series IP Telephones —Continued

Condition Cause/Resolution

The user indicates a 4620-specific or 4630-specific application is not accessible.

CAUSE: The 46xxsettings script file is not pointed to accurately, or is not properly administered to allow the application.

RESOLUTION: Assuming the user is meant to have that application, verify the 46xxsettings script file is properly specified for your system, including case (if your TFTP server is UNIX or LINUX) and extension. Then, verify all the relevant parameters (as indicated in Table 4-5 and Table 4-6, as appropriate) are accurately specified in the 46xxsettings file.

There are three areas where installers can troubleshoot problems before seeking assistance from the system or LAN administrator:

1. Check the wiring (power and Ethernet) for the following:

■ Whether all components are plugged in correctly.

■ Check LAN connectivity in both directions to all servers (DHCP, TFTP, Call Server)

■ If the telephone is supposed to be powered from the LAN, ensure the LAN is properly

administered and is compliant with IEEE 802.3af.

2. If you are using static addressing, do the following:

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

filenames match those on the TFTP server. Check on the Avaya website to verify whether the correct files are being used.

■ Use the ADDR option to verify IP addresses.

■ Use the QOS option to verify QoS parameters.

Refer to Chapter 3 of the 4600 Series IP Telephone Installation Guide.

3. If the 4600 Series IP Telephone is not communicating with the system (DHCP, TFTP, or Call Server), make a note of the last message that was displayed and consult the system administrator.

Error Conditions

5-7

Page 72

4600 Series IP Telephone LAN Administrator’s Guide

The View Administrative Option 5

If you are using static addressing and encounter problems, use the following procedure to verify the current values of system parameters and file versions.

Also use the ADDR option to view IP addresses (see “Static Addressing Installation” in Chapter 3 of 4600 Series IP Telephone Installation Guide). These may have been entered incorrectly. Verify whether you were provided with correct IP addresses.

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

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

Press the Mute key momentarily. Do not press this key while pressing other keys. The 4630 IP Telephone does not have a dedicated Hold button; for all other 4600 Series IP Telephones, pressing the Hold button instead of the Mute button will also work.

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

View settings *=next #=exit

2. Press the * button at any time during viewing to display the next name and system value pair from the list below, returning to the first pair after the last pair has been displayed.

Press the # button at any time during viewing to terminate the procedure and restore the user interface to its previous state.

The View Administrative Option

5-8

Page 73

Troubleshooting Guidelines

The names and values are displayed in the following order:

Table 5-2. Parameter Values

Name System Value Format

Model 46ccDccc up to 8 ASCII graphics characters

Market domestic

export

Phone SN cccccccccccc

cccccccc

PWB SN cccccccccccc

cccccccc

PWB comcode ccccccccc 9 ASCII numbered characters

MAC address 00:60:1D:hh:hh:hh Each octet of the MAC address is displayed as a

filename1.exe

filename2.exe

Only one value is displayed

Phone Serial Number, up to 18 ASCII graphic characters

Printed Wiring Board (circuit board) Serial Number, up to 18 ASCII graphic characters

pair of hexadecimal numbers.

up to 16 ASCII graphic characters.

Out of the box, there will be only one filename.exe. After installation, there should be two filenames. If there is only one, installation has failed. Verify the problem, and then re-install the telephone.

Error Messages 5

The 4600 Series IP Telephones issue messages in English only. The IP Telephones also display messages from the switch, which outside the United States may issue messages in the local language.

Table 5-3. Possible Error Messages During Installation or Operation of 4600 Series IP

Telephones

Error Message Cause/Resolution

During Installation

Checksum error CAUSE: Downloaded application file was not downloaded or

saved correctly.

RESOLUTION: The telephone automatically resets and attempts to re-initialize.

Error Messages

5-9

Page 74

4600 Series IP Telephone LAN Administrator’s Guide

Table 5-3. Possible Error Messages During Installation or Operation of 4600 Series IP

Telephones—Continued

Error Message Cause/Resolution

DHCP: CONFLICT * to program

File too large

Cannot save file

Gateway Error CAUSE: DEFINITY Release 8.4 does not have an H.323 station

Hardware failure CAUSE: Hardware failure prevented downloading of application

IP Address in use by another

CAUSE: At least one of the IP address offered by the DHCP server conflicts with another address.

RESOLUTION: Review DHCP server administration to identify duplicate IP address(es)

CAUSE: The telephone does not have sufficient room to store the downloaded file.

RESOLUTION: Verify the proper filename is administered in the TFTP script file, and that the proper application file is located in the appropriate location on the TFTP server.

extension for this telephone.

RESOLUTION: On the station administration screen, ensure the DCP set being aliased for this IP telephone has an H.323 station extension administered, in accordance with switch administration instructions.

file,

RESOLUTION: Replace telephone.

CAUSE: The telephone has detected an IP address conflict.

RESOLUTION: Verify administration to identify duplicate IP

address(es).

No Ethernet CAUSE: When first plugged in, the IP Telephone is unable to

communicate with the Ethernet.

RESOLUTION: Verify the connection to the Ethernet jack, verify the jack is Category 5, verify power is applied on the LAN to that jack, etc.

No file server address CAUSE: The TFTP server IP address in the IP telephone’s

memory is all zeroes.

RESOLUTION: Depending on the specific requirements of your network, this may not be an error. If appropriate, either administer the DHCP server with the proper address of the TFTP server, or administer the telephone locally using the ADDR option as detailed in the 4600 Series IP Telephone Installation Guide.

Error Messages

5-10

Page 75

Troubleshooting Guidelines

Table 5-3. Possible Error Messages During Installation or Operation of 4600 Series IP

Telephones—Continued

Error Message Cause/Resolution

System busy CAUSE: Most likely, the number of IP endpoints on the

DEFINITY/MultiVantage is already at maximum, Less likely, network resource is unavailable.

RESOLUTION: The telephone was attempting to access a network resource (DHCP server, TFTP server, or the DEFINITY/ MultiVantage) and was not successful. The resource being called upon should be checked for its availability. If it appears operational and properly linked to the network, verify addressing is accurate and a communication path exists in both directions between the telephone and the resource.

System Error CAUSE: DEFINITY/MultiVantage has an unspecified problem.

RESOLUTION: Consult your DEFINITY or MultiVantage Administration and Troubleshooting documentation.

During Registration

Extension error CAUSE: An invalid DEFINITY/MultiVantage Registration

extension has been entered.

RESOLUTION: Re-enter the extension if mis-entered initially. If appropriate, verify proper extension with respect to switch administration.

Extension in use CAUSE: The specified extension is already in use, according to

the PBX switch.

RESOLUTION: Wait a few minutes, and try again. This will work for the case when the extension is correctly administered, but service was interrupted and DEFINITY is not yet aware of that fact. Otherwise, verify proper extension with respect to switch administration.

Failed to set phone IP address

Incompatible CAUSE: This release of DEFINITY does not support the current

CAUSE: The 4600 Series Telephone was originally installed on one switch with Static Addressing, and has subsequently been installed on another switch with an active DHCP server assigning dynamic IP addresses.

RESOLUTION: Reset the telephone.

version of the IP Telephone.

RESOLUTION: Upgrade to the current version of MultiVantage software.

Error Messages

5-11

Page 76

4600 Series IP Telephone LAN Administrator’s Guide

Table 5-3. Possible Error Messages During Installation or Operation of 4600 Series IP

Telephones—Continued

Error Message Cause/Resolution

Message light blinks on and off, and the telephone did not complete registration.

Password Error CAUSE: An invalid PBX Registration password has been entered.

Resource Error CAUSE: DEFINITY rejects the registration request.

Timeout Error CAUSE: Protocol timeout error.

Undefined Error CAUSE: An error has occurred without an identifiable cause.

Wrong Set Type CAUSE: The PBX does not recognize the set type.

CAUSE: The telephone has a hardware fault.

RESOLUTION: Replace the telephone.

RESOLUTION: Re-enter the password if mis-entered initially. If

appropriate, verify proper password with respect to switch administration.

RESOLUTION: Verify your DEFINITY or MultiVantage Administration to ensure the telephone’s proper IP address, extension, and password are being used.

RESOLUTION: Retry. If failure continues, check network congestion, addresses, etc. to identify cause of timeout.

RESOLUTION: Conduct Self-test, restart the telephone, and if no other cause becomes evident, replace the telephone.

Error Messages

5-12

RESOLUTION: Ensure the PBX is properly administered to expect the appropriate telephones for the IP address and extension.

Page 77

Table 5-4. Possible Error Messages During 4630 Backup/Restore

Error Message Cause/Resolution

Troubleshooting Guidelines

Current options and Speed Dial entries have not yet been backed up.

The FTP Server Name is not known. Please check the FTP Server IP Address

The FTP Server has not yet responded, so backup has not yet succeeded.

The FTP Server has denied access. Please check FTP Setup parameters.

The FTP Server was unable to store the backup file.

CAUSE: An attempt to save the current options and speed dial entries on the FTP server has not yet been made or is in progress.

RESOLUTION: Wait for a message stating that backup was successful.

CAUSE: Invalid or missing Server name.

RESOLUTION: Verify the FTPSRVR address is the File Server to

which backup data should be saved. Verify that the FTPDIR value is the correct directory path for that File Server.

CAUSE: The FTP Server has not responded to the attempt to backup/restore.

RESOLUTION: Try again, verify the FTP server address, verify the FTP server is online, and/or verify the network connectivity.

CAUSE: The FTP Server has reported that it did not store data.

RESOLUTION: Verify the FTP server setup parameters, as

indicated on the FTP Setup Parameters screen (see "FTP Setup" Chapter 8 of the 4630 IP Telephone User’s Guide.

CAUSE: The FTP Server has reported that it could not store the data.

RESOLUTION: Verify administration and available capacity/ filespace on the FTP Server.

Error Messages

5-13

Page 78

4600 Series IP Telephone LAN Administrator’s Guide

Error Messages

5-14

Page 79

Appendix A: Avaya - 46xx IP Telephone MIB

Avaya - 46xx IP Telephone MIB 5

Avaya-46xxIPTelephone-MIB DEFINITIONS ::= BEGIN IMPORTS enterprises, OBJECT-TYPE, MODULE-IDENTITY, Integer32, IpAddress FROM SNMPv2-SMI DisplayString

FROM RFC1213-MIB ;

endpointMIB MODULE-IDENTITY

LAST-UPDATED "200206182000Z" ORGANIZATION "avaya" CONTACT-INFO "Robert Mitchell email : robmitchell@avaya.com (732) 817-6330"

DESCRIPTION "MIB Module for 46xx IP Telephones through Release 1.61" ::= { ipEndpointMIBs 1 }

avaya OBJECT IDENTIFIER ::= { enterprises 6889 } avayaProducts OBJECT IDENTIFIER ::= { avaya 1 } avayaMibs OBJECT IDENTIFIER ::= { avaya 2 } ipEndpointProducts OBJECT IDENTIFIER ::= { avayaProducts 69 }

Avaya - 46xx IP Telephone MIB

A-1

Page 80

4600 Series IP Telephone LAN Administrator’s Guide

ipEndpointMIBs OBJECT IDENTIFIER ::= { avayaMibs 69 } endptID OBJECT IDENTIFIER ::= { endpointMIB 1 } endptMARKET OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "ID designation. This variable returns a string

specifying 'domestic' or 'export'." ::= { endptID 1 } endptMODEL OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "Model identifier. This variable returns a string

of up to 8 ASCII characters." ::= { endptID 2 } endptMCIPADD OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "List of call server addresses. This variable

returns a sequence of IP address es, in dotted -d e cim al or

DNS format and separated by commas, of call server IP

addresses available for use." ::= { endptID 3 }

Avaya - 46xx IP Telephone MIB A-2

Page 81

Avaya - 46xx IP Telephone MIB

endptMCIPINUSE OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STA TUS current DESCRIPTION "Call server address. This variable returns a 4-octet string specifying the IP address of the call server currently in use. " ::= { endptID 4 } endptMCPORT OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "Transport layer port number. This variable

returns an integer specifyin g th e po rt number in use

by the current call server." ::= { endptID 5 } endptPHONESN OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "Housing serial number. This variable returns

a string of up to 18 ASCII characters, specifying the

serial number on the outside of the endpoint's housing." ::= { endptID 6 }

Avaya - 46xx IP Telephone MIB

A-3

Page 82

4600 Series IP Telephone LAN Administrator’s Guide

endptPWBCC OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "PWB comcode. This variable returns a string of up to 9 numerical characters, specifying the comcode of the printed wiring board of the endpoint." ::= { endptID 7 } endptPWBSN OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "PWB serial number. This variable returns a

string of up to 18 ASCII characters, specifying the

serial number on the endpoint's printed wiring board." ::= { endptID 8 } endptETHERADD OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STA TUS current DESCRIPTION "MAC address. This variable returns a 6-octet string specifying the endpoint's MAC address." ::= { endptID 9 }

Avaya - 46xx IP Telephone MIB A-4

Page 83

Avaya - 46xx IP Telephone MIB

endptESPEED OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "Ethernet interface speed. This variable returns

a string specifying the endpoint's Ethernet interface

speed in Mbps: '100', '10', or '0'." ::= { endptID 10 } endptIPADD OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STA TUS current DESCRIPTION "IP address. This variable returns a 4-octet

string specifying the endpoint's current IP address." ::= { endptID 11 } endptDHCPLEASETIME OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STA TUS current DESCRIPTION "Duration of IPADD lease. This variable returns an unsigned integer specifying the length of time of the IPADD lease." ::= { endptID 12 }

Avaya - 46xx IP Telephone MIB

A-5

Page 84

4600 Series IP Telephone LAN Administrator’s Guide

endptDHCPLEASERENEW OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STA TUS current DESCRIPTION "Renewal time of IPADD lease. This variable returns an unsigned integer specifying the length of time at which to renew the IPADD lease." ::= { endptID 13 } endptDHCPLEASEREBIND OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STA TUS current DESCRIPTION "Rebind time of IPADD lease. This variable returns an unsigned integer specifying the length of time at which to rebind the IPADD lease." ::= { endptID 14 } endptGIPADD OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "List of router addresses. This variable returns

a sequence of IP addresses, in dotted-decimal format and separated by commas, of routers available for use."

::= { endptID 15 }

Avaya - 46xx IP Telephone MIB A-6

Page 85

Avaya - 46xx IP Telephone MIB

endptGIPINUSE OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STA TUS current DESCRIPTION "Router address. This variable returns a 4-octet string specifying the IP address of the router currently in use." ::= { endptID 16 } endptNETMASK OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STA TUS current DESCRIPTION "Subnet mask. This variable returns a 4-octet string specifying the subnet mask currently in use." ::= { endptID 17 } endptTFTPDIR OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "TFTP server path name. This variable returns a string of 0-127 ASCII characters, specifying the path name currently prepended to file names used in TFTP read operations." ::= { endptID 18 }

Avaya - 46xx IP Telephone MIB

A-7

Page 86

4600 Series IP Telephone LAN Administrator’s Guide

endptTFTPSRVR OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "List of TFTP server addresses. This variable

returns a sequence of IP address es, in dotted -d e cim al or DNS format and separated b y commas, of TFTP servers

available for use." ::= { endptID 19 } endptTFTPINUSE OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STA TUS current DESCRIPTION "TFTP server address. This variable returns a 4-octet string specifying the IP address of the TFTP server currently in use." ::= { endptID 20 } endptBOOTNAME OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "Boot code file ID. This variable returns a string specifying the boot code file used to initiate telephone operation." ::= { endptID 21 }

Avaya - 46xx IP Telephone MIB A-8

Page 87

Avaya - 46xx IP Telephone MIB

endptAPPNAME OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "Application file ID. This variable returns a string specifying the system-specific application file that should be used for telephone operatio n." ::= { endptID 22 } endptSSON OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "Site-specific option number (SSON). This variable returns an integer between 128 and 254 inclusive, specifying the SSON in use. The default is 176." ::= { endptID 23 } endptBBURST OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS obsolete DESCRIPTION "Blackburst flag. This variable returns 0 if Blackburst is currently OFF, else 1." ::= { endptID 24 }

Avaya - 46xx IP Telephone MIB

A-9

Page 88

4600 Series IP Telephone LAN Administrator’s Guide

endptHUBSTAT OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS obsolete DESCRIPTION "Hub flag. This variable has been superseded by endptPHY2STAT." ::= { endptID 25 } endptDSCPAUD OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "DSCP for audio. This variable specifies the Differentiated Services Code Point for audio currently in use (between 0 and 63 inclusive)." ::= { endptID 26 } endptDSCPSIG OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION " DSCP for signaling. This variable specifies the Differentiated Services Code Point for signaling currently in use (between 0 and 63 inclusive)." ::= { endptID 27 }

Avaya - 46xx IP Telephone MIB A-10

Page 89

Avaya - 46xx IP Telephone MIB

endptL2Q OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "802.1Q flag. This variable returns 0 if the Layer 2 802.1Q framing parameter is currently OFF, else 1." ::= { endptID 28 } endptL2QAUD OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "Audio priority. This variable returns an integer between 0 and 7 inclusive specifying the current Layer 2

802.1Q audio priority value." ::= { endptID 29 } endptL2QSIG OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "Signaling priority. This variable returns an INTEGER between 0 and 7 inclusive specifying the current Layer 2 802.1Q signaling priority value." ::= { endptID 30 }

Avaya - 46xx IP Telephone MIB

A-11

Page 90

4600 Series IP Telephone LAN Administrator’s Guide

endptL2QVLAN OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "VLAN Identifier. This variable returns an integer between 0 and 4095 inclusive specifying the current Layer 2 802.1Q VLAN Identifier value." ::= { endptID 31 } endpt46XXUPGR OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "Upgrade script ID. This variable returns a string of up to 16 ASCII characters specifying the name of the upgrade script retrieved by TFTP after the most recent power-up or reset." ::= { endptID 32 } endptDNSSRVR OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "List of DNS server addresses. This variable

returns a sequence of IP address es, in dotted -d e cim al

format and separated by commas, of DNS servers

available for use." ::= { endptID 33 }

Avaya - 46xx IP Telephone MIB A-12

Page 91

Avaya - 46xx IP Telephone MIB

endptDNSINUSE OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STA TUS current DESCRIPTION "DNS server address. This variable returns a 4-octet string specifying the IP address of the DNS server currently in use." ::= { endptID 34 } endptDOMAIN OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "List of DNS domain labels. This variable

returns a sequence of labels, separated by periods, for use as the highest-level domain in resolving DNS names

in system values." ::= { endptID 35 } endptRTCPMON OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STA TUS current DESCRIPTION "RTCP Monitor address. This variable returns a 4-octet string specifying the IP address of the RTCP monitor currently in use." ::= { endptID 36 }

Avaya - 46xx IP Telephone MIB

A-13

Page 92

4600 Series IP Telephone LAN Administrator’s Guide

endptPHY2STAT OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "Hub flag. This variable returns 0 if the endpoint's secondary Ethernet interface is currently NOT enabled, else 1." ::= { endptID 37 } endptIRSTAT OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "IR Interface flag. This variable returns 0 if the endpoint's IR interface is currently NOT enabled, else 1." ::= { endptID 38 } endptSMTPSRVR OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "SMTP server IP addresses. This variable returns a

comma-separated list of SMTP server IP addresses available for use, in dott ed-decimal format."

::= { endptID 39 }

Avaya - 46xx IP Telephone MIB A-14

Page 93

Avaya - 46xx IP Telephone MIB

endptDSPVERSION OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "DSP Version. This variable returns a string of

up to 10 characters, that identifies the version of the

DSP firmware in the endpoint." ::= { endptID 40 } endptLOGSRVR OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "Event Log server address. This variable

returns at most one IP address, in dotted-decimal

or DNS format, of the server to be used for event logging. This

function is intended for Avaya use, in debugging if necessary." ::= { endptID 41 } endptLOGSTAT OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "Event Log flag. This variable returns 0 if the

endpoint's event logging capability is currently NOT

enabled, else 1. This function is intended for Avaya use,

in debugging if necessary." ::= { endptID 42 }

Avaya - 46xx IP Telephone MIB

A-15

Page 94

4600 Series IP Telephone LAN Administrator’s Guide

endptAGCHAND OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "Handset AGC status. This variable returns 1 if the endpoint's handset Automatic Gain Control capability is currently enabled, else 0." ::= { endptID 43 } endptAGCHEAD OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "Headset AGC status. This variable returns 1 if the endpoint's headset Automatic Gain Control capability is currently enabled, else 0." ::= { endptID 44 } endptPHONECC OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "Phone comcode. This variable returns a string of up to 9 numerical characters, specifying the comcode of the endpoint itself." ::= { endptID 45 }

endptNVM OBJECT IDENTIFIER ::= { endpointMIB 2 }

Avaya - 46xx IP Telephone MIB A-16

Page 95

Avaya - 46xx IP Telephone MIB

endptNVMCIPADD OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "IP address of call server stored in Non-Volatile

Memory (NVM). This variable returns a 4-octet string or DNS string.

Default is AvayaCallServer." ::= { endptNVM 1 } endptNVMCPORT OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM Transport layer port number. This variable returns an integer specifying the call server port number stored in NVM." ::= { endptNVM 2 } endptNVIPADD OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM IP address. This variable returns a 4-octet string specifying the endpoint's IP address stored in NVM." ::= { endptNVM 3 }

Avaya - 46xx IP Telephone MIB

A-17

Page 96

4600 Series IP Telephone LAN Administrator’s Guide

endptNVGIPADD OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM Router address. This variable returns a 4 octet string specifying the IP address of the router as stored in NVM." ::= { endptNVM 4 } endptNVNETMASK OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM Subnet mask. This variable returns a 4-octet string specifying the subnet mask as stored in NVM." ::= { endptNVM 5 } endptNVTFTPSRVR OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM TFTP server address. This variable returns a 4-octet string specifying the IP address of the file server as stored in NVM. The default is AvayaTFTPserver." ::= { endptNVM 6 }

Avaya - 46xx IP Telephone MIB A-18

Page 97

Avaya - 46xx IP Telephone MIB

endptNVSSON OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM Site-specific option number. This variable returns an integer between 128 and 254 inclusive, specifying the SSON stored in NVM. The default is 176." ::= { endptNVM 7 } endptNVBBURST OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS obsolete DESCRIPTION "NVM Blackburst flag. This variable returns 0 if the Blackburst parameter in NVM is OFF, else 1." ::= { endptNVM 8 } endptNVHUBSTAT OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS obsolete DESCRIPTION "NVM Hub flag. This variable has been superseded by endptNVPHY2STAT." ::= { endptNVM 9 }

Avaya - 46xx IP Telephone MIB

A-19

Page 98

4600 Series IP Telephone LAN Administrator’s Guide

endptNVDSCPAUD OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM DSCP for audio. This variable specifies the Differentiated Services Code Point for audio stored in NVM (integer between 0 and 63 inclusive)." ::= { endptNVM 10 } endptNVDSCPSIG OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION " NVM DSCP for signaling. This variable specifies the Differentiated Services Code Point for signaling stored in NVM (integer between 0 and 63 inclusive)." ::= { endptNVM 11 } endptNVL2Q OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM 802.1Q flag. This variable returns 0 if the Layer 2 802.1Q framing parameter in NVM is OFF, else 1." ::= { endptNVM 12 }

Avaya - 46xx IP Telephone MIB A-20

Page 99

Avaya - 46xx IP Telephone MIB

endptNVL2QAUD OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM Audio priority. This variable returns an integer between 0 and 7 inclusive specifying the Layer 2

802.1Q audio priority value stored in NVM." ::= { endptNVM 13 } endptNVL2QSIG OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM Signaling priority. This variable returns an integer between 0 and 7 inclusive specifying the Layer 2

802.1Q signaling priority value stored in NVM." ::= { endptNVM 14 } endptNVL2QVLAN OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM VLAN Identifier. This variable returns an integer between 0 and 4095 inclusive specifying the Layer 2 802.1Q VLAN Identifier value stored in NVM." ::= { endptNVM 15 }

Avaya - 46xx IP Telephone MIB

A-21

Page 100

4600 Series IP Telephone LAN Administrator’s Guide

endptNVPHY2STAT OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "NVM Hub flag. This variable returns 0 if the endpoint's secondary Ethernet interface parameter in NVM is NOT enabled, else 1." ::= { endptNVM 16 } endptNVLOGSTAT OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "Event Log flag. This variable returns 0 if the endpoint's event logging capability in NVM is currently NOT enabled, else 1." ::= { endptNVM 17 } endptNVAGCHAND OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STA TUS current DESCRIPTION "Handset AGC status. This variable returns 1 if the

endpoint's handset Automatic Gain Control capability in NVM is currently enabled, else 0."

::= { endptNVM 18}

Avaya - 46xx IP Telephone MIB A-22

Avaya 4600 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Introduction 1

Intended Audience 1

About This Guide

Change History 1

Document Organization

Terms Used in This Guide 1

Conventions Used in This Guide 1

Related Documents 1

Online Documentation

Customer Support

Overview of Voice over IP (VoIP) 2

Overview of Voice over IP 2

Data and Voice Network Similarities 2

Introduction

Delay and Jitter 2

Tandem Coding 2

Voice Coding Standards 2

H.323 Standard 2

DHCP 2

TFTP 2

SNMP

Suggestions for Installation and Configuration 2

Reliability and Performance 2

Network Assessment

IP Address Lists and Station Number Portability 2

Security 2

Dual Connection Architecture 2

Single Connection Architecture 2

Registration and Authentication 2

Software 2

WAN Considerations 2

DHCP and TFTP Servers 2

4600 Series IP Telephones

Step 1: Telephone to Network 2

Step 2: DHCP Server to Telephone 2

Initialization Process

Step 3: Telephone and TFTP Server 2

Requirements 3

Hardware Requirements 3

Introduction

Software Requirements

Server Administration 4

Introduction

DEFINITY® Release 8.4 4

DEFINITY® Releases 9, 9.5, 10, and MultiVantageTM Release 11 4

DHCP and TFTP 4

Required Network Information 4

Software Checklist

DHCP 4

Choosing a DHCP Configuration 4

DHCP Software Alternatives 4

DHCP Generic Setup 4

Windows NT 4.0 DHCP Server 4

Windows 2000 DHCP Server 4

TFTP Generic Setup 4

Avaya TFTP (Suite Pro) 4

TFTP

4600 Series IP Telephone Scripts and Application Files

Contents of the Upgrade Script 4

IEEE 802.1D and 802.1Q 4

DIFFSERV 4

UDP Port Selection 4

QoS with 4620 and 4630 IP Telephones 4

RSVP and RTCP 4

Administering Options for the 4600 Series IP Te l ep h on e s

DNS Addressing 4

Customizing the Site-Specific Option Number (SSON) 4

Entering Options via the Telephone Dialpad 4

Customizing the 4630 IP Telephone 4

4630 Backup/Restore 4

Call Log Archive 4

Customizing the 4620 IP Telephone 4

Troubleshooting Guidelines 5

Error Conditions 5

Introduction

The View Administrative Option