Avaya 4600 Series Service manual

4600 Series IP Telephone
Release 2.1
LAN Administrator’s Guide
555-233-507
Issue 2.1
July 2004

Copyright 2004, Avaya Inc.
All Rights Reserved
Notice
Every effort was made to ensure that the information in this document
was complete and accurate at the time of printing. However,
information is subject to change.
Warranty
Avaya Inc. provides a limited warranty on this product. Refer to your
sales agreement to establish the terms of the limited warranty. In
addition, Avaya’s standard warranty language as well as information
regarding support for this product, while under warranty, is available
through the following Web site: http://www.avaya.com/support.
Trademarks
All trademarks identified by the ® or ™ are registered trademarks or
trademarks, respectively, of Avaya, Inc. All other trademarks are the
property of their respective owners.
Preventing Toll Fraud
“Toll fraud” is the unauthorized use of your telecommunications
system by an unauthorized party (for example, a person who is not a
corporate employee, agent, subcontractor, or is not working on your
company's behalf). Be aware that there may be a risk of toll fraud
associated with your system and that, if toll fraud occurs, it can result
in substantial additional charges for your telecommunications
services.
Avaya Fraud Intervention
If you suspect that you are being victimized by toll fraud and you need
technical assistance or support, in the United States and Canada, call
the Technical Service Center's Toll Fraud Intervention Hotline at
1-800-643-2353.
Disclaimer
Avaya is not responsible for any modifications, additions or deletions
to the original published version of this documentation unless such
modifications, additions or deletions were performed by Avaya.
Customer and/or End User agree to indemnify and hold harmless
Avaya, Avaya's agents, servants and employees against all claims,
lawsuits, demands and judgments arising out of, or in connection with,
subsequent modifications, additions or deletions to this documentation
to the extent made by the Customer or End User.
How to Get Help
For additional support telephone numbers, go to the Avaya support
Web site: http://www.avaya.com/support. If you are:
• Within the United States, click the Escalation Management link.
Then click the appropriate link for the type of support you need.
• Outside the United States, click the Escalation Management link.
Then click the International Services link that includes telephone
numbers for the international Centers of Excellence.
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 is not 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
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).
Responsibility for Your Company’s Telecommunications Security
The final responsibility for securing both this system and its
networked equipment rests with you - Avaya’s customer system
administrator, your telecommunications peers, and your managers.
Base the fulfillment of your responsibility on acquired knowledge and
resources from a variety of sources including but not limited to:
• Installation documents
• System administration documents
• Security documents
• Hardware-/software-based security tools
• Shared information between you and your peers
• Telecommunications security experts
To prevent intrusions to your telecommunications equipment, you and
your peers should carefully program and configure:
• Your Avaya-provided telecommunications systems and their
interfaces
• Your Avaya-provided software applications, as well as their
underlying hardware/software platforms and interfaces
• Any other equipment networked to your Avaya products
TCP/IP Facilities
Customers may experience differences in product performance,
reliability and security depending upon network configurations/design
and topologies, even when the product performs as warranted.
Standards Compliance
Avaya Inc. is not responsible for any radio or television interference
caused by unauthorized modifications of this equipment or the
substitution or attachment of connecting cables and equipment other
than those specified by Avaya Inc. The correction of interference
caused by such unauthorized modifications, substitution or attachment
will be the responsibility of the user. Pursuant to Part 15 of the Federal
Communications Commission (FCC) Rules, the user is cautioned that
changes or modifications not expressly approved by Avaya Inc. could
void the user’s authority to operate this equipment.
To order copies of this and other documents:
Call: Avaya Publications Center
Voice 1.800.457.1235 or 1.207.866.6701
FAX 1.800.457.1764 or 1.207.626.7269
Write: Globalware Solutions
200 Ward Hill Avenue
Haverhill, MA 01835 USA
Attention: Avaya Account Management
E-mail: totalware@gwsmail.com
For the most current versions of documentation, go to the Avaya
support Web site: http://www.avaya.com/support.

Contents
4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide 3
July 2004
Contents
1 Introduction 9
• About This Guide 9
Intended Audience 9
• Document Organization 10
Change History 11
What’s New in Release 2.1 11
Terms Used in This Guide 12
Conventions Used in This Guide 13
• Online Documentation 13
• Related Documents 14
IETF Documents 16
ITU Documents 17
ISO/IEC, ANSI/IEEE Documents 17
• Customer Support 18
2 Overview of Voice over IP (VoIP) 19
• Introduction 19
• Overview of Voice over IP 19
Data and Voice Network Similarities 19
Delay and Jitter 20
Tandem Coding 20
Voice Coding Standards 20
H.323 Standard 21
DHCP 21
TFTP 21
DNS 21
NAT 21
QoS 22
•SNMP 22
• Network Assessment 23
• TCP/UDP Port Utilization 23

Contents
4 4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide
July 2004
• Suggestions for Installation and Configuration 27
Reliability and Performance 27
IP Address Lists and Station Number Portability 28
Security 28
• 4600 Series IP Telephones 29
Dual Connection Architecture 29
Single Connection Architecture 29
Registration and Authentication 29
Software 29
WAN Considerations 29
DHCP and TFTP Servers 30
• Initialization Process 30
Step 1: Telephone to Network 30
Step 2: DHCP Server to Telephone 31
Step 3: Telephone and TFTP Server 31
Step 4: Telephone and the Avaya Media Server 31
3 Requirements 33
• Introduction 33
• Hardware Requirements 33
Additional Hardware Requirements 34
• Software Requirements 35
4 Server Administration 37
• Introduction 37
• Administering 4600 Series IP Telephones on Avaya Media Servers 39
DEFINITY Releases 9, 9.5, 10, and Avaya
Communication Manager Software Release 1.1+ 39
DEFINITY Release 8.4 39
• DHCP and TFTP 40
• Software Checklist 40
• Required Network Information 40
• DHCP 41
Choosing a DHCP Configuration 41
DHCP Software Alternatives 42
DHCP Generic Setup 42
Windows NT 4.0 DHCP Server 45
Windows 2000 DHCP Server 49

Contents
4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide 5
July 2004
• TFTP 52
TFTP Generic Setup 52
Avaya TFTP (Suite Pro) 53
TFTP Server on S8300 Media Server 53
• 4600 Series IP Telephone Scripts and Application Files 55
Choosing the Right Application File and Upgrade Script File 57
Contents of the Upgrade Script 59
Contents of the TFTP Settings File 60
• The GROUP System Value 61
•QoS 62
IEEE 802.1D and 802.1Q 62
DIFFSERV 63
UDP Port Selection 63
Network Audio Quality Display on 4600 Series IP Telephones 64
RSVP and RTCP 65
• VLAN Considerations 65
• Administering Options for the 4600 Series IP Telephones 66
DNS Addressing 69
Customizing the Site-Specific Option Number
(SSON) 69
Entering Options via the Telephone Dialpad 69
• Enhanced Local Dialing 70
• Customizing the 4630/4630SW IP Telephone 71
4630/4630SW Backup/Restore 73
Call Log Archive 75
• Customizing the 4610SW/4620/4620SW IP Telephones 75
The Application Status Flag (APPSTAT) 77
• 4610SW/4620/4620SW Backup/Restore 78
5 Troubleshooting Guidelines 81
• Introduction 81
• Error Conditions 81
• The Clear Administrative Option 86
• The Reset Administrative Option 87
Reset System Values 87

Contents
6 4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide
July 2004
• Restart the Telephone 88
• The View Administration Option 89
• Error Messages 91
• Troubleshooting the 4601 IP Telephone 95
A Avaya - 46xx IP Telephone MIB 99
• Downloading the Avaya - 46xx IP Telephone MIB 99
B Creating Web sites for the
4630/4630SW IP Telephone 101
• Introduction 101
• General Background 101
• Browser Features and Behavior 102
Document Skeleton 102
Content-Based Style 102
Logical Style 103
Physical Style 103
Physical Spacing and Layout 104
Lists and Tables 104
Images 105
Links 106
Frames 106
Forms 107
Character Entities 107
Colors 108
Fonts 108
Cookies 108
• Design Guidelines 108
Fixed-Width Objects 109
Images 109
Frames 110
Fonts 110
Maintaining Context 111
User Interaction 111
Click-to-Dial Functionality 111

Contents
4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide 7
July 2004
C Creating Web sites for the 4610SW
and 4620 IP Telephones 113
• Introduction 113
• General Background 113
• WML Document Skeleton 114
• Text Elements 116
• Text Formatting Tags 117
• Anchor Elements 117
• Image Elements 118
• Event Elements 119
• Task Elements 122
• Input Elements 123
• Variable Elements 125
• Character Entities 126
• Colors and Fonts 126
• Wireless Telephony Applications (WTA) 126
Syntax Implementation 127
• Summary Of WML Tags And Attributes 133
D Administering the 4610SW and 4620
Thin Client Directories 137
• Introduction 137
• Application Platform Requirements 139
• Installing the Thin Client Directory on the Server 139
Pre-Installation Requirements (Apache/PHP) 139
Avaya-Provided Download Files 139
Installing the Thin Client Directory 140
• Web Application User Interface 142
Generic User Interface Screen Characteristics 143
Web Application Search Screen 143
Web Application Successful Search Screen 144
Web Application Detail Screen 145
Web Application Directory Trouble Screen 146

Contents
8 4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide
July 2004
• Directory Database Administration Interface 148
Configuring the General Directory Application Administration Screen 150
Configuring the Directory Application Search Administration Screen 152
Configuring the Directory Application Details Administration Screen 153
Configuring the Directory Application Softkey Administration Screen 155
E 4610SW/4620/4620SW Push Feature 157
• Introduction 157
• Push Content 157
• Push Priorities 158
• For More Information on Push 158
Index 159

Introduction
About This Guide
4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide 9
July 2004
1Introduction
About This Guide
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.
NOTE:
Unless otherwise indicated, any reference to “the DEFINITY®server” in this document
also refers to the Avaya Communication Manager media servers.
The 4602/4602SW (non-SIP) IP Telephones are covered in this guide.
The 4602/4602SW SIP Telephones are not covered in this guide. See the “4602 SIP
Telephone Administrator's Guide” (Document Number 16-300037) for information on
administering 4602/4602SW SIP Telephones.
Intended Audience
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,
DHCP, LDAP, and Web servers. If the servers are not functioning correctly, the 4600
Series IP Telephones may not operate correctly.

Introduction
Document Organization
10 4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide
July 2004
Document Organization
The guide contains the following sections:
Chapter 1, “Introduction” Provides an overview of the 4600 Series IP
Telephone LAN Administrator’s document.
Chapter 2, “Overview of Voice over IP (VoIP)” Describes VoIP and factors influencing its
performance that must be considered when
implementing this feature.
Chapter 3, “Requirements” Describes the hardware and software
requirements for Avaya’s VoIP offering.
Chapter 4, “Server Administration” Describes DHCP and TFTP administration for
the 4600 Series IP Telephones.
Chapter 5, “Troubleshooting Guidelines” Describes messages that may occur during the
operation of the 4600 Series IP Telephones.
Appendix A, “Avaya - 46xx IP Telephone MIB” Provides a link to the MIB specification for the
46xx IP Telephones (4601/4602/4602SW, 4606,
4610SW, 4612, 4620/4620SW, 4624, and
4630/4630SW).
Appendix B, “Creating Web sites for the
4630/4630SW IP Telephone” Provides information on creating and
customizing Web sites for viewing on the
4630/4630SW IP Telephone. Also describes the
current capabilities and limitations of the
4630/4630SW’s web browser.
Appendix C, “Creating Web sites for the
4610SW and 4620 IP Telephones” Provides information on creating and
customizing Web sites for viewing on the
4610SW and 4620/4620SW IP Telephones. Also
describes the current capabilities and limitations
of the web browser.
Appendix D, “Administering the 4610SW and
4620 Thin Client Directories” Provides information on administering an LDAP
directory for the 4610SW and 4620/4620SW IP
Telephones.
Appendix E, “4610SW/4620/4620SW Push
Feature” Provides information about the Push feature
available as of Release 2.1 for 4610SW, 4620,
and 4620SW IP Telephones.

Introduction
Document Organization
4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide 11
July 2004
Change History
What’s New in Release 2.1
New material in this release includes:
•Support for Avaya Communication Manager Release 2.1.
•Support for the TFTP Server on the Avaya S8300 Media Server.
•Support for the 4601 IP Telephone.
•Support for DHCP Options 1, 3, 52, 58, and 59.
•Support for DHCP Option 51, including the ability to administer a system parameter to allow the
telephone to override a DHCP lease expiration.
•Additional information about setting VLANTEST to “0” in the 46xxsettings file.
•New general system parameters: ACGSPKR, APPSTAT, DHCPSTD, ENHDIALSTAT, and
STATIC.
•New 4610SW/4620/4620SW-specific system parameters: SUBSCRIBELIST and TPSLIST to
support the new “push” feature, and FTPDIR and FTPUSERSTAT to enhance the FTP
Backup/Restore feature.
•Appendix E, which describes the new “push” feature.
•Support for the Clear Administrative Option.
•New Error messages and actions in Chapter 5.
This release also reflects removal of the following obsolete system parameters: HTTPSRVR, HTTPDIR,
and HTTPPORT.
Issue 1.0 This document was issued for the first time in November 2000.
Issue 1.1 This version of the document, revised and issued in April 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 version of the document was revised in July, 2002 to support Avaya Communication
Manager Release 1.1 and the 4602 and 4620 IP Telephones.
Issue 1.8 This version of this document was revised in June, 2003 to support Avaya Communication
Manager Releases 1.2 and 1.3, as well as the 4602SW and 4630SW IP Telephones.
Issue 2.0 This version of this document was revised in December, 2003 to add support for Avaya
Communication Manager Release 2.0, the 4610SW and 4620SW IP Telephones, and the 4690 IP
Conference Telephone.
Issue 2.1 This is the current version of this document, revised and issued in July, 2004.

Introduction
Document Organization
12 4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide
July 2004
Terms Used in This Guide
802.1p
802.1Q 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.
ARP Address Resolution Protocol, used for example, to verify that the IP address provided by the DHCP
server is not in use by another IP Telephone.
CELP Code-excited linear-predictive; voice compression requiring only 16 kbps of bandwidth.
CLAN Control LAN, type of Gatekeeper circuit pack.
DHCP Dynamic Host Configuration Protocol, an IETF protocol used to automate IP Address allocation and
management.
DiffServ Differentiated Services, an IP-based QoS mechanism.
DNS Domain Name System, an IETF standard for ASCII strings to represent IP addresses.
Gate-
keeper H.323 application that performs essential control, administrative, and managerial functions in the
media server. Sometimes called CLAN in Avaya documents.
HTTP Hypertext Transfer Protocol, used to request and transmit pages on the World Wide Web.
IETF Internet Engineering Task Force, the organization that produces standards for communications on the
internet.
LAN Local Area Network.
LDAP Lightweight Directory Access Protocol, an IETF standard for database organization and query
exchange.
MAC Media Access Control, ID of an endpoint.
NAPT Network Address Port Translation.
NAT Network Address Translation.
PHP Hypertext Preprocessor, software used to assist in the format and display of web pages.
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.
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).
SIP Session Initiation Protocol; an alternative to H.323 for VoIP signaling.
TCP/IP Transmission Control Protocol/Internet Protocol, a network-layer protocol used on LANs and
internets.
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.
VoIP Voice over IP, a class of technology for sending audio data and signaling over LANs.
WML Wireless Markup Language, used by the 4620 web browser to communicate with WML servers.

Introduction
Online Documentation
4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide 13
July 2004
Conventions Used in This Guide
This guide uses the following textual, symbolic, and typographic conventions to help you interpret
information.
Symbolic Conventions
NOTE:
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
This guide uses the following typographic conventions:
Online Documentation
The online documentation for the 4600 Series IP Telephones is located at the following URL:
http://www.avaya.com/support
command Words printed in this type are commands that you enter into your system.
message Words printed in this type are system messages.
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 or enter to perform a task, i.e., fields, buttons, icons
and for general emphasis.
italics Italic type indicates a document that contains additional information about a topic.

Introduction
Related Documents
14 4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide
July 2004
Related Documents
•DEFINITY®Documentation Release 8.4
This CD contains documentation that describes, among other things, how to administer a
DEFINITY switch with Release 8.4 software. This document is provided with the
DEFINITY Release 8.4 product.
•DEFINITY®Documentation Release 9
This CD contains documentation that describes, among other things, how to administer a
DEFINITY switch with Release 9 software. This document is provided with the
DEFINITY Release 9 product.
•DEFINITY®Documentation Release 10
This CD contains documentation that describes, among other things, how to administer a
DEFINITY switch with Release 10 software. This document is provided with the
DEFINITY Release 10 product.
•Avaya Communication Manager Software Documentation Release 1.1
This documentdescribes how to administer a switch with Avaya Communication Manager
software. This document is provided with the Avaya Communication Manager Release 1.1
product.
•Avaya Communication Manager Software Documentation Release 1.2
This documentdescribes how to administer a switch with Avaya Communication Manager
software. This document is provided with the Avaya Communication Manager Release 1.2
product.
•Avaya Communication Manager Documentation Release 1.3
This documentdescribes how to administer a switch with Avaya Communication Manager
software. This document is provided with the Avaya Communication Manager Release 1.3
product.
•Avaya Communication Manager Documentation Release 2.0
This documentdescribes how to administer a switch with Avaya Communication Manager
software. This document is provided with the Avaya Communication Manager Release 2.0
product.
•Avaya Communication Manager Documentation Release 2.1
This documentdescribes how to administer a switch with Avaya Communication Manager
software. This document is provided with the Avaya Communication Manager Release 2.1
product.
•Administration for Network Connectivity for Avaya Communication Manager Software
This document describes how to implement Voice over IP (VoIP) applications for TCP/IP
for DCS signaling, H.323 trunks, and private networks through Avaya Communication
Manager software administration.
•Administrator’s Guide for Avaya Communication Manager Software
This document provides an overall reference for planning, operating, and administering
your Avaya Communication Manager solution.

Introduction
Related Documents
4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide 15
July 2004
•Installation and Upgrades for Avaya G700 Media Gateway and Avaya S8300 Media Server
This document describes procedures for installing, upgrading, and performing initial
configuration tasks for the Avaya G700 Media Gateway and the Avaya S8300 Media
Server.
The following documents are available on the Web site listed under Online Documentation:
•4600 Series IP Telephones Safety Instructions
This document contains important user safety instructions for the 4600 Series IP
Telephones.
•30A Switched Hub Set Up Quick Reference, Issue 2, July 2002 (Comcode 700234750)
This document contains important safety and installation information for the 30A
Switched Hub.
•4600 Series IP Telephone Installation Guide
This document describes how to install 4600 Series IP Telephones. It also provides
troubleshooting guidelines for the 4600 Series IP Telephones.
•4601/4602/4602SW IP Telephone Stand Instructions
This document provides information on how to desk- or wall-mount a 4601 or
4602/4602SW IP Telephone.
•4601 IP Telephone User’s Guide
This document provides detailed information about using the 4601 IP Telephone.
•4602/4602SW IP Telephone User’s Guide
This document provides detailed information about using the 4602/4602SW IP
Telephones.
•4606 IP Telephone User’s Guide
This document provides detailed information about using the 4606 IP Telephone.
•4610SW IP Telephone User’s Guide
This document provides detailed information about using the 4610SW IP Telephone.
•4612 IP Telephone User’s Guide
This document provides detailed information about using the 4612 IP Telephone.
•4620/4620SW IP Telephone User’s Guide
This document provides detailed information about using the 4620/4620SW IP Telephone.
•4624 IP Telephone User’s Guide
This document provides detailed information about using the 4624 IP Telephone.
•4630/4630SW IP Telephone User’s Guide
This document provides detailed information about using the 4630/4630SW IP
Telephones.
•Avaya 4690 IP Conference Telephone User’s Guide
This document provides detailed information about using the 4690 IP Conference
Telephones.

Introduction
Related Documents
16 4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide
July 2004
IETF Documents
The following documents provide standards relevant to IP Telephony and 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)
DHCP Options and BOOTP Vendor Extensions, March 1997, by S. Alexander and R. Droms
(RFC 2132)
RTP: A Transport Protocol for Real-Time Applications (RTP/RTCP), January 1996, by H.
Schulzrinne, S. Casner, R. Frederick, V. Jacobson (RFC 1889)
Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers,
(DIFFSRV), December 1998, by K. Nichols, S. Blake, F. Baker and D. Black (RFC 2474)
Introduction to version 2 of the Internet-standard Network Management Framework (SNMPv2),
April 1993, by J. Case, K. McCloghrie, M. Rose, and S. Waldbusser (RFC 1441)
Management Information Base for Network Management of TCP/IP Internets: MIB-II, March
1991, edited by K. McCloghrie and M. Rose (RFC 1213)
SNMPv2 Management Information Base for the Internet Protocol using SMIv2, November 1996,
edited by K. McCloghrie (RFC 2011)
Structure of Management Information Version 2 (SMIv2), April 1999, edited by K. McCloghrie,
D. Perkins, and J. Schoenwaelder (RFC 2578)
Resource ReSerVation Protocol VI, September 1997, by R. Braden, L. Zhang, S. Berson, S.
Herzog, and S. Jamin (RFC 2205)
Lightweight Directory Access Protocol, March 1995, by M. Wahl, T. Howes, and S. Kille
(RFC 1777)

Introduction
Related Documents
4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide 17
July 2004
Lightweight Directory Access Protocol (v3), December 1997, by M. Wahl, T. Howes, and S. Kille
(RFC 2251)
Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions, December 1997, by M.
Wahl, Coulbeck, T. Howes, and S. Kitte (RFC 2252)
Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished
Names, December 1997, by M. Wahl, S. Kille, and T. Howes (RFC 2253)
ITU Documents
The following documents are available for a fee from the ITU web site: http://www.itu.int.
Recommendation G.711, Pulse Code Modulation (PCM) of Voice Frequencies, November 1988
Recommendation G.729, Coding of speech at 8 kbit/s using Conjugate-Structure Algebraic-Code-
Excited Linear-Prediction (CS-ACELP), March 1996
Annex A to Recommendation G.729: Reduced complexity 8 kbit/s CS-ACELP speech codec,
November 1996
Annex B to Recommendation G.729: A silence compression scheme for G.729 optimized for
terminals conforming to Recommendation V.70, November 1996
Recommendation H.225.0, Call signalling protocols and media stream packetization for packet-
based multimedia communications systems, February 1998
Recommendation H.245, Control protocol for multimedia communication, February 1998
Recommendation H.323, Packet-based multimedia communications systems, February 1998
ISO/IEC, ANSI/IEEE Documents
The following documents are available for a fee from the ISO/IEC standards web site:
http://www.iec.ch.
International Standard ISO/IEC 8802-2:1998 ANSI/IEEE Std 802.2, 1998 Edition, Information
technology - Telecommunications and information exchange between systems - Local and
metropolitan area networks- Specific requirements- Part 2: Logical Link Control
ISO/IEC 15802-3: 1998 ANSI/IEEE Std 802.1D, 1998 Edition, Information technology-
Telecommunications and information exchange between systems- Local and metropolitan area
networks- Common specifications- Part 3: Media Access Control (MAC) Bridges
IEEE Std 802.1Q-1998, IEEE Standards for Local and Metropolitan Area Networks: Virtual
Bridged Local Area Networks
IEEE Std 802.3af-2003, IEEE Standard for Information technology- Telecommunications and
information exchange between systems- Local and metropolitan area networks- Specific
requirements- Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access
Method and Physical Layer Specifications- Amendment: Data Terminal Equipment (DTE) Power
via Media Dependent Interface (MDI)

Introduction
Customer Support
18 4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide
July 2004
Customer Support
For support for your 4600 Series IP Telephones, call the Avaya support number provided to you by your
Avaya representative or Avaya reseller.
Information about Avaya products can be obtained at the following URL:
http://www.avaya.com/support

Overview of Voice over IP (VoIP)
Introduction
4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide 19
July 2004
2Overview of Voice over IP (VoIP)
Introduction
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 Avaya media
servers, and the installation and configuration of DHCP and TFTP are addressed.
Overview of Voice over IP
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
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 helps 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, and/or 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.
•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.

Overview of Voice over IP (VoIP)
Overview of Voice over IP
20 4600 Series IP Telephone Release 2.1 LAN Administrator’s Guide
July 2004
Delay and Jitter
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 form of greater traffic
reliability (for example, for interactive transactions), data requirements tend to not be as strict as most
voice requirements.
Starting with Release 1.1, the 4600 Series IP Telephones include a dynamic jitter buffer. This feature
automatically smooths jitter to improve audio quality.
Tandem Coding
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, by minimizing analog trunking on the PBX).
Voice Coding Standards
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.
Other manuals for 4600 Series
20
Table of contents
Other Avaya Telephone manuals

Avaya
Avaya Definity 6408 User manual

Avaya
Avaya PARTNER Phone Parts list manual

Avaya
Avaya 3905 User manual

Avaya
Avaya 9601 Assembly Instructions

Avaya
Avaya 9330 AV User manual

Avaya
Avaya 9508 Series User manual

Avaya
Avaya Partner 18 Quick guide

Avaya
Avaya 6424D+M User manual

Avaya
Avaya IP Office 9508 User manual

Avaya
Avaya IP OFFICE 2420 User manual