Avaya 4600 Administrator's Guide
4600 Series IP Telephone LAN Administrator Guide
555-233-507
Issue 8
© 2008 Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts were made to ensure that the infor mation in this
document was complete and accurate at the time of printing, Avaya Inc. can
assume no liability for any errors. Changes and corrections to the information
in this document may be incorporated in future releases.
For full legal page information, please see the complete document,
Avaya Legal Page for Hardware Documentation, Document number
03-600759.
To locate this document on our Web site, simply go to
http://www.avaya.com/support
the search box.
Documentation disclaimer
Avaya Inc. is not responsible for any modifications, addition s, or deletions to
the original published version of this documentation unless such modifications,
additions, or deletions were performed by Avaya. Customer and/or End User
agree to indemnify and hold harmless Avaya, Avaya's agents, servants and
employees against all claims, lawsuits, demands and judgments arising out of,
or in connection with, subsequent modifications, additions or deletions to this
documentation to the extent made by the Customer or End User.
Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any linked Web
sites referenced elsewhere within this documentation, and Avaya does not
necessarily endorse the products, services, or informa tion described or o ff ered
within them. We cannot guarantee that these links will work all of the time and
we have no control over the availability of the linked pages.
Warranty
Avaya Inc. provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warran ty. In addition, Avaya’s
standard warranty language, as well as information regarding support for this
product, while under warranty, is available through the following Web site:
http://www.avaya.com/support
Copyright
Except where expressly stated otherwise, the Product is protected by copyrigh t
and other laws respecting proprietary rights. Unauthorized reproduction,
transfer, and or use can be a criminal, as well as a civil, offense un der the
applicable law.
Avaya support
Avaya provides a telephone number for you to use to report pro blems or t o ask
questions about your product. The support telephone number
is 1-800-242-2121 in the United States. For additional support telephone
numbers, see the Avaya Web site:
http://www.avaya.com/support
Software License
USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER’S
ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL
LICENSE TERMS AVAIL ABLE ON T HE AVAYA WEBSITE AT
http://support.avaya.com/LicenseInfo/
YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST
RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN
(10) DAYS OF DELIVERY FOR A REFUND OR CREDIT.
Avaya grants End User a license within the scope of the license types
described below. The applicable number of licenses and units of capacity for
which the license is granted will be one (1), unless a different number of
licenses or units of capacity is specified in the Documentation or other
materials available to End User. “Designated Processor” means a single
stand-alone computing device. “Server” means a Designated Processor that
hosts a software application to be accessed by multiple users. “Soft w are”
means the computer programs in object code, originally licensed by Avaya and
ultimately utilized by End User, whether as stand-alone Products or
pre-installed on Hardware. “Hardware” means the standard hardware
Products, originally sold by Avaya and ultimately utili zed by End User.
License Type(s):
Designated System(s) License (DS). End User may install and use each copy
of the Software on only one Designated Processor, unless a different number
of Designated Processors is indicated in the Documentation or other mat erials
available to End User. Avaya may require the Designated Processor(s) to be
identified by type, serial number, feature key, location or other specific
designation, or to be provided by End User to Avaya through elect roni c mean s
established by Avaya specifically for this purpose.
and search for the document number in
(“GENERAL LICENSE TERMS”). IF
Third-party Components
Certain software programs or portions thereof included in the Product may
contain software distributed under third party agreements (“Third Party
Components”), which may contain terms that expand or limit rights to use
certain portions of the Product (“Third Party Terms”). Information identifying
Third Party Components and the Third Party Terms that apply to them is
available on Avaya’s Web site at:
http://support.avaya.com/ThirdPartyLicense/
Interference
Using a cell, mobile, or GSM telephone, or a two-way radio in close proximity to
an Avaya IP Telephone might cause interference.
Security
See http://support.avaya.com/security
vulnerabilities in Avaya products. See http://support.avaya.com
latest software patches and upgrades. For information about secure
configuration of equipment and mitigation of toll fraud threats, see the Avaya
Toll Fraud and Security Handbook at http://support.avaya.com
to locate and/or report known
to locate the
.
Contents
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Intended Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
What’s New in This Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Terms Used in This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . 17
Symbolic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Typographic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Online Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
IETF Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
ITU Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
ISO/IEC, ANSI/IEEE Documents . . . . . . . . . . . . . . . . . . . . . . . . . 25
Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 2: Overview of Voice over IP (VoIP) and Network Protocols . . 27
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Overview of Voice over IP (VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Data and Voice Network Similarities . . . . . . . . . . . . . . . . . . . . . . . 27
Delay and Jitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Tandem Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Voice Coding Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Telephony Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Network Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4600 Series IP Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
DHCP and File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
H.323 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Registration and Authentication . . . . . . . . . . . . . . . . . . . . . . . 35
Time-to-Service (TTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Issue 8 July 2008 3
Contents
SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Registration and Authentication . . . . . . . . . . . . . . . . . . . . . . . 36
WAN Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Initialization Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Step 1: Telephone to Network . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Step 2: DHCP Server to Telephone. . . . . . . . . . . . . . . . . . . . . . . . 37
Step 3: Telephone and File Server . . . . . . . . . . . . . . . . . . . . . . . . 37
Step 4: Telephone and the Call Server . . . . . . . . . . . . . . . . . . . . . . 38
TCP/UDP Port Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Suggestions for Installation and Configuration . . . . . . . . . . . . . . . . . . . 44
Reliability and Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
IP Address Lists and Station Number Portability . . . . . . . . . . . . . . . . 45
Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Chapter 3: Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Additional Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . 51
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Chapter 4: Server Administration . . . . . . . . . . . . . . . . . . . . . 53
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Parameter Data Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Administering H.323 and SIP IP Telephones on the Same Network . . . . . . . . 56
Administering 4600 Series IP Telephones on Avaya Media Servers (H.323 Only). 57
DEFINITY Releases 9, 9.5, 10, and Avaya
Communication Manager Software Release 1.1+ . . . . . . . . . . . . . . . 57
DEFINITY Release 8.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
DHCP and File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Software Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Required Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Choosing a DHCP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 60
DHCP Software Alternatives . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
DHCP Generic Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Windows NT 4.0 DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Verifying the Installation of the DHCP Server . . . . . . . . . . . . . . . . 65
Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Creating a DHCP Scope for the IP Telephones . . . . . . . . . . . . . . . 66
4 4600 Series IP Telephone LAN Administrator Guide
Editing Custom Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Adding the DHCP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Activating the Leases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Verifying Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 68
Windows 2000 DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Verifying the Installation of the DHCP Server . . . . . . . . . . . . . . . . 69
Adding DHCP Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Activating the New Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . 73
TFTP (H.323 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
TFTP Generic Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
TFTP Server on S8300 Media Server . . . . . . . . . . . . . . . . . . . . . . . 74
Avaya File Server Application . . . . . . . . . . . . . . . . . . . . . . . . . . 74
HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
HTTP Generic Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
HTTP Configuration for Backup/Restore. . . . . . . . . . . . . . . . . . . . . . . 76
For IIS Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
For Apache Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Contents
4600 Series IP Telephone Scripts and Application Files . . . . . . . . . . . . . . 78
Choosing the Right Application File and Upgrade Script File . . . . . . . . . 80
Contents of the Upgrade Script. . . . . . . . . . . . . . . . . . . . . . . . . . 82
Contents of the Settings File . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
The GROUP System Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
IEEE 802.1D and 802.1Q. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
DIFFSERV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
UDP Port Selection (H.323 Only) . . . . . . . . . . . . . . . . . . . . . . . . . 87
Network Audio Quality Display on 4600 Series IP Telephones. . . . . . . . . 87
RSVP and RTCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Internal Audio Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
VLAN Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
VLAN Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
VLAN Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
VLAN Separation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Unnamed Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
IEEE 802.1X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
I802.1X Pass-Through and Proxy Logoff. . . . . . . . . . . . . . . . . . . . . 95
802.1X Supplicant Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Link Layer Discovery Protocol (LLDP) . . . . . . . . . . . . . . . . . . . . . . . . 97
Administering Options for the 4600 Series IP Telephones . . . . . . . . . . . . . 101
Issue 8 July 2008 5
Contents
DNS Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Customizing the Site-Specific Option Number (SSON) . . . . . . . . . . . . . 114
Entering Options Using the Telephone Dialpad . . . . . . . . . . . . . . . . . 114
Enhanced Local Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Setting the Date and Time on SIP IP Telephones . . . . . . . . . . . . . . . . . . 116
Setting the Dial Plan on SIP IP Telephones . . . . . . . . . . . . . . . . . . . . . 117
Customizing the 4630/4630SW IP Telephone . . . . . . . . . . . . . . . . . . . . 117
4630/4630SW Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Call Log Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Customizing 4610SW, 4620/4620SW, 4621SW, 4622SW,
and 4625SW IP Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
The Application Status Flag (APPSTAT) . . . . . . . . . . . . . . . . . . . . . 126
Backup/Restore for 4610SW, 4620/4620SW, 4621SW,
4622SW and 4625SW IP Telephones . . . . . . . . . . . . . . . . . . . . . . . . 127
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
User Permissions for FTP Backup/Restore Files . . . . . . . . . . . . . . . . 128
File Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Backup Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Chapter 5: Troubleshooting Guidelines . . . . . . . . . . . . . . . . . . 133
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
The Clear Administrative Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
The Reset Administrative Option. . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Reset System Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Restart the Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
The View Administration Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Troubleshooting the 4601 IP Telephone . . . . . . . . . . . . . . . . . . . . . . . 156
Appendix A: Avaya - 46xx IP Telephone MIB . . . . . . . . . . . . . . . 159
Downloading the Avaya - 46xx IP Telephone MIB . . . . . . . . . . . . . . . . . . 159
Appendix B: Creating Web Sites for the
4630/4630SW IP Telephone . . . . . . . . . . . . . . . . . . . . . . . . . 161
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
General Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Browser Features and Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Document Skeleton . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
6 4600 Series IP Telephone LAN Administrator Guide
Content-Based Style. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Logical Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Physical Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Physical Spacing and Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Lists and Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Character Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Colors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Cookies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Fixed-Width Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Maintaining Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
User Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Click-to-Dial Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Contents
Appendix C: Creating Web Sites for Other 4600
Series IP Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Appendix D: Administering Thin Client Directories. . . . . . . . . . . . 179
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Appendix E: The Push Feature . . . . . . . . . . . . . . . . . . . . . . . 181
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Push Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Push Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
For More Information on Push . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Appendix F: Sample Upgrade Script File . . . . . . . . . . . . . . . . . 183
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Issue 8 July 2008 7
Contents
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
8 4600 Series IP Telephone LAN Administrator Guide
Chapter 1: Introduction
About This Guide
This guide provides a description of Vo ice over IP and describes how to administer the DHCP,
TFTP, and HTTP servers. It also covers how to troubleshoot operational problems with the 4600
Series IP Telephones and the servers.
The 4600 Series IP Telephone product line supports two signaling protocols - the Session
Initiation Protocol (SIP) and the H.323 protocol. The chart below shows the 4600 Series IP
Telephone models and the protocol(s) they support.
IP Telephone Model H323 Protocol Supported? SIP Protocol Supported?
4601 Yes No
4601+ Yes No
4602 Yes Yes
4602SW Yes Yes
4602SW+ Yes Yes
4606 Yes No
4610SW Yes Yes
4612 Yes No
4620 Yes No
4620SW Yes Yes
4621SW Yes Yes
4622SW Yes No
4624 Yes No
4625SW Yes No
4630 Yes No
4630SW Yes No
4690 Yes No
Issue 8 July 2008 9
Introduction
Sets that support both protocols, for example, the 4610SW, do not support each protocol
simultaneously. Instead, a given telephone must be loaded with software that supports one
protocol or the other.
Telephones with H.323 software work only with Avaya Communication Manager call servers.
Telephones with SIP software are supported only in Avaya server environments.
Note:
Note: Unless otherwise indicated, any reference to “the DEFINITY
document also refers to the Avaya Communication Manager media servers.
Administration of the 4602/4602SW SIP Telephones with Release 1.x software is
not covered in this guide. See the 4602 SIP Telephone Administrator's Guide
(Document Number 16-300037) for information on administering these 4602/
4602SW SIP Telephones.
Intended Audience
This document is intended for personnel who administer:
®
server” in this
● DHCP, TFTP, HTTP, SIP Registration and/or other servers to support the 4600 Series SIP
IP and IP Telephones, and
● Local Area Networks.
!
CAUTION:
CAUTION: Avaya does not support many of the products mentioned in this document. Take
care to ensure that there is adequate technical support available for these types
of servers:
- TFTP servers,
- HTTP servers,
- DHCP servers,
- SIP Registration servers,
- FTP servers,
- LDAP servers, and
- Web servers.
Note: If the servers are not functioning correctly, the 4600 Series IP Telephones may
not operate correctly.
10 4600 Series IP Telephone LAN Administrator Guide
Document Organization
The guide contains the following sections:
Chapter 1: Introduction Provides an overview of the 4600 Series IP
Document Organization
Telephone LAN Administrator document.
Chapter 2: Overview of Voice over IP (VoIP)
and Network Protocols
Chapter 3: Requirements Describes the hardware and software
Chapter 4: Server Administration
Chapter 5: Troubleshooting Guidelines Describes messages that might occur
Appendix A: Avaya - 46xx IP Telephone MIB
Appendix B: Creating Web Sites for the
4630/4630SW IP Telephone
Describes VoIP and factors influencing its
performance that must be considered
when implementing this feature.
requirements for Avaya’s VoIP offering.
Describes DHCP, TFTP, and HTTP
administration for the 4600 Series IP and
SIP IP Telephones.
during the operation of the 4600 Series IP
Telephones.
Provides a link to the MIB specification for
the 46xx IP Telephones:
4601, 4601+, 4602/4602SW/4602SW+,
4606, 4610SW, 4612, 4620/4620SW,
4621SW, 4622SW, 4624, 4625SW, and
4630/4630SW.
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 Other
4600 Series IP Telephones
Appendix D: Administering Thin Client
Directories
Appendix E: The Push Feature
Appendix F: Sample Upgrade Script File Provides a detailed example of a 46xx
Provides information on creating and
customizing Web sites for viewing on the
4610SW, 4620/4620SW, 4621SW,
4622SW, and 4625SW IP Telephones.
Provides information on administering an
LDAP directory for the 4610SW, 4620/
4620SW, 4621SW, 4622SW, and 4625SW
IP Telephones.
Provides information about the Push
feature available as of Release 2.1.
upgrade script file.
Issue 8 July 2008 11
Introduction
Change History
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
Issue 1.5 This version of the document was revised in June, 2001 to support DEFINI TY® Release
9.5.
Issue 1.6 This version of the document was revised to support DEFINITY
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. This version also supported 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. This version also supported the 4610SW and
4620SW IP Telephones, and the 4690 IP Conference Telephone.
Issue 2.1 This version of this document was revised in July, 2004 to add support for Avaya
Communication Manager Release 2.1. This version also added support for the TFTP
server on the Avaya S8300 Media Server, and support for the 4601 IP Telephone.
Issue 2.2 This version of this document was revised and issued in April, 2005. This version
supports through Avaya Communication Manager Release 2.2. This version also
introduces the 4621SW, 4622SW, and 4625SW IP Telephones.
Issue 2.2.1 This version of this document was revised and issued in August, 2005. This version
introduced the SIP IP Telephones. This version also distinguishes between functionality
that is H.323-specific and functionality that is SIP-specific.
Issue 2.3 This version of this document was revised and issued in November, 2005 to provide
support through Avaya Communication Manager Release 3.0.
Issue 3 This version of this document was revised and issued in April, 2006 to support Software
Release 2.4. This version provides VLAN separation parameters, an unnamed
registration parameter, and audio customization parameters.
Issue 4 This version of this document was revised and issued in August, 2006. This version
supports Avaya Communication Manager 3.1 and Software Release 2.6. New features
for 802.1X authentication, Link Layer Discovery Protocol (LLDP), and power
conservation are introduced.
Issue 5 This version of this document was revised and issued in November, 2006 to support
Software Release 2.7. This version introduced additional Unicode languages, support
for dialpad-activated Web links, the capability to turn off the display backlight, several
new system parameters, and two ne w local p rocedures. This issue also introduced new
telephone models and 4602SW+, which replace the 4601 and 4602/4602SW,
respectively.
Issue 6 This version of this document was revised and issued in February 2007 to support
Software Release 2.8. This version introduced backup/restore capabilities to HTTP
servers, additional security measures for TCP, new system parameters for adding IP
Source Addresses, configuring HTTP ports, and using HTTP filepaths, and reduced
time-to-service through Communication Manager 4.0 upgrades.
Issue 7 This version was revised and issued in September, 2007 to support Software Release
2.8.3. This version introduced new audio parameters and changes to audio parameter
settings, guidance on a troubleshooting issue related to Message Waiting Indicators,
and Communication Manager 3.1.3 and above support for downloading of four key
administrative parameters to individual phones.
®
Release 9.
®
Release 10 and the
12 4600 Series IP Telephone LAN Administrator Guide
Document Organization
Issue 8 This is the current version of this document, revised and issued in July 2008 to support
Software Release 2.9. This version introduces the capability to disable the 802.1X
supplicant operation, offers enhanced LLDP MED Network Policy TLV processing, and
allows immediate access to the manual addressing local administrative procedure
during startup. For information, see What’s New in This Release
.
What’s New in This Release
New material in this issue to support Release 2.9 software includes:
● The ability to download and use third-party trusted certificates to authenticate file servers
that download configuration files and for encryption of backup/restore file parameters.
● New system parameter BRAUTH can be used to control whether registration credentials
are sent to a backup/restore server so that the telephone requesting the file can be
authenticated. For information, see Backup/Restore for 4610SW , 4620/4620SW, 4621SW,
4622SW and 4625SW IP Telephones.
● New system parameter TRUSTCERTS is used to specify the file names of trusted
Certificate Authority certificates the telephone should download to authenticate server
certificates.
● The manual addressing local administrative procedure (ADDR) can now be accessed
during telephone initialization, as described in Chapter 3 of the 4600 Series IP Telephone
Installation Guide. When saving statically programmed values, the telephone now resets if
the system parameter PROCSTAT is set to "1" (access to administrative procedures
allowed).
● 802.1X supplicant operation can now be disabled using the new system parameter
DOT1XSTAT
. As covered in Chapter 3 of the 4600 Series IP Telephone Installation Guide,
the "Set the 802.1X Operational Mode" local administrative procedure has been modified
to reflect changes in pass-thru and supplicant operation.
● LLDP MED Network Policy TLV processing has been modified, as described in Link Layer
Discovery Protocol (LLDP).
● Certain parameters and sections in this guide relating to HTTP Backup and Restore have
been revised to correct documentation errors in describing Release 2.8 processing. The
affected parameters and sections are: HTTP Configuration for Backup/Restore
, Backup/
Restore for 4610SW, 4620/4620SW, 4621SW, 4622SW and 4625SW IP Telephones,
BRURI
, HTTP, and HTTPS.
For detailed information regarding installation-related updates and revisions, see the 4600
Series IP Telephone Installation Guide (Document Number 555-233-128).
Terms Used in This Guide
Issue 8 July 2008 13
Introduction
802.1D
802.1Q
802.1Q defines a layer 2 frame structure that supports VLAN identification and a QoS
mechanism usually referred to as 802.1D.
802.1X Authentication method for a protocol requiring a network device to authenticate with a
back-end Authentication Server before gaining network access. Applicable 4600
Series IP telephones support IEEE 802.1X as a Supplicant with the EAP-MD5
authentication method.
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.
CNA Converged Network Analyzer, an Avaya product to test and analyze network
performance.
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.
EAP Extensible Application Protocol.
Gatekeeper H.323 application that performs essential control, administrative, and managerial
functions in the media server. Sometimes called CLAN in Avaya documents.
H.323 A TCP/IP-based protocol for VoIP signaling.
HTTP Hypertext Transfer Protocol, used to request and transmit pages on the World Wide
Web.
HTTPS A secure version of HTTP.
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.
LLDP Link Layer Discovery Protocol. All IP telephones with an Ethernet interface support
the transmission and reception of LLDP frames on the Ethernet line interface in
accordance with IEEE standard 802.1AB.
MAC Media Access Control, ID of an endpoint.
Media
Channel
Encryption of the audio information exchanged between the IP telephone and the call
server or far end telephone.
Encryption
NAPT Network Address Port Translation.
NAT Network Address Translation.
1 of 3
14 4600 Series IP Telephone LAN Administrator Guide
Document Organization
OPS Off-PBX Station.
PAE Port Access Entity. The protocol entity associated with a port. The PAE supports the
protocol functionality associated with the authenticator, supplicant, or both.
PHP Hypertext Preprocessor, software used to assist in the format and display of Web
pages.
PoE Power over Ethernet.
PSTN Public Switched Telephone Network, the network used for traditional telephony.
QoS Quality of Service, used to refer to several mechanisms intended to improve audio
quality over packet-based networks.
Registration
Server
A SIP server that accepts REGISTER requests. The Registration Server places the
information received in the requests into the location service for the domain the
server handles.
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.
SDP Session Description Protocol. A well-defined format for conveying sufficient
information to discover and participate in a multimedia session.
Signaling
Channel
Encryption
Encryption of the signaling protocol exchanged between the IP telephone and the call
server. Signaling channel encryption provides additional security to the security
provided by media channel encryption.
SIP Session Initiation Protocol. An IETF standard protocol for IP communication. SIP
enables IP telephony gateways, client endpoints, PBXs, and other communication
systems or devices to communicate with each other. SIP mainly addresses the call
setup and tear down mechanisms of sessions and is independent of the transmission
of media streams between the caller and the called party. SIP is an alternative to
H.323 for VoIP signaling.
SMTP Simple Mail Transfer Protocol. An IETF standard pr otocol (RFC 2821) for e-mail. Part
of the TCP/IP protocol suite. SMTP sets the message format and message transfer
agent that stores and forwards the email.
SNMP Simple Network Management Protocol. The Internet standard protocol, defined in
STD 15, RFC 1157, developed to manage nodes on an IP network.
SNTP Simple Network Time Protocol. An adaptation of the Network Time Protocol used to
synchronize computer clocks in the internet.
Supplicant An entity at one end of a point-to-point LAN segment that is being authenticated by
an authenticator at the other end.
TCP/IP Transmission Control Protocol/Internet Protocol, a network-layer protocol used on
LANs and internets.
2 of 3
Issue 8 July 2008 15
Introduction
TFTP Trivial File Transfer Protocol, used to provide downloading of upgrade scripts and
application files to the IP telephones.
Time-toService
(TTS)
A new feature with Communication Manager 4.0, IP Endpoint Time-to-Service (TTS)
decouples gatekeeper H.323 registration from TCP socket establishment for call
signaling, thus reducing the time for the endpoint to come into service.
TLS Transport Layer Security, an enhancement of Secure Sockets Layer (SSL). TLS is
compatible with SSL 3.0 and allows for privacy and data integrity between two
communicating applications.
TLV Type-Length-Value elements transmitted and received as part of Link Layer
Discovery Protocol (LLDP).
UDP User Datagram Protocol, a connectionless transport-layer protocol.
Unnamed
Registration
Registration with Avaya Communication Manager by an IP telephone with no
extension. Unnamed registration is typically used to limit incoming calls.
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 any 4600 Series IP Telephones that can
communicate with WML servers.
3 of 3
16 4600 Series IP Telephone LAN Administrator Guide
Conventions Used in This Guide
This guide uses the following textual, symbolic, and typographic conventions to help you
interpret information.
Symbolic Conventions
Note:
Note: This symbol precedes additional information about a topic. This information is not
required to run your system.
!
CAUTION:
CAUTION: This symbol emphasizes possible harm to software, possible loss of data, or
possible service interruptions.
Typographic Conventions
Online Documentation
This guide uses the following typographic conventions:
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. W ords
printed in bold type can also be items on menus and screens that you
select or enter to perform a task, i.e., fields, buttons, or icons. Bold
type also provides general emphasis for words or concepts.
italics Italic type indicates a document that contains additional information
about a topic.
Online Documentation
The online documentation for the 4600 Series IP Telephones is located at the following URL:
http://www.avaya.com/support
Issue 8 July 2008 17
Introduction
Related Documents
● DEFINITY
®
ECS (Enterprise Communication Server) Documentation Release 8.4
This CD contains documentation that describes, among other things, how to administer a
DEFINITY ECS switch with Release 8.4 software. This document is provided with the
DEFINITY Release 8.4 product.
● DEFINITY
®
ECS (Enterprise Communication Server) Documentation Release 9
This CD contains documentation that describes, among other things, how to administer a
DEFINITY ECS switch with Release 9 software. This document is provided with the
DEFINITY Release 9 product.
● DEFINITY
®
ECS (Enterprise Communication Server) Documentation Release 10
This CD contains documentation that describes, among other things, how to administer a
DEFINITY ECS switch with Release 10 software. This document is provided with the
DEFINITY Release 10 product.
● Audio Quality Tuning for IP Telephones, Issue 2
This document describes how to administer audio parameters for the 4600 telephones.
● Avaya Communication Manager Software Documentation Release 1.1
This document describes 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 document describes 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 document describes 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 document describes 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 document describes how to administer a switch with Avaya Communication
Manager software. This document is provided with the Avaya Communication Manager
Release 2.1 product.
18 4600 Series IP Telephone LAN Administrator Guide
Related Documents
● Avaya Communication Manager Documentation Release 2.2
This document describes how to administer a switch with Avaya Communication
Manager software. This document is provided with the Avaya Communication Manager
Release 2.2 product.
● Avaya Communication Manager Documentation Release 3.0
This document describes how to administer a switch with Avaya Communication
Manager software. This document is provided with the Avaya Communication Manager
Release 3.0 product.
● Avaya Communication Manager Documentation Release 3.12
This document describes how to administer a switch with Avaya Communication
Manager software. This document is provided with the Avaya Communication Manager
Release 3.12 product.
The following documents are availab le on the W eb si te listed under Online Documentation
● Administration for Network Connectivity for Avaya Communication Manager Software
(555-233-504)
This document describes how to administer Avaya Communication Manager software to
implement Voice over IP (VoIP) applications for TCP/IP for DCS signaling, H.323 trunks,
and private networks.
● Administrator Guide for Avaya Communication Manager (03-300509)
This document provides an overall reference for planning, operating, and administering
your Avaya Communication Manager solution.
● Installation and Upgrades for Avaya G700 Media Gateway and Avaya S8300 Media
Server (555-234-100)
This document describes procedures for installing, upgrading, and performing initial
configuration tasks for the Avaya G700 Media Gateway and the Avaya S8300 Media
Server.
● Downloading Avaya 46xx IP Telephone Software Using Avaya Media Servers
This White Paper provides information on using HTTP/HTTPS or TFTP file transfer
protocols to transfer Avaya 46xx IP telephone software from Avaya Media Servers to
Avaya 46xx IP telephones.
● SIP Support in Release 3.0 of Avaya Communication Manager running on the Avaya
S8300, S8500, and 8710 Media Server (555-245-206)
:
This document describes requirements and introduces procedures for administering SIP
(Session Initiation Protocol) with Avaya Communication Manager Release 3.0.
● Converged Communications Server Release 3.1.1 Installation and Administration
(555-245-705)
This document describes procedures for installing and administering the Converged
Communication Server, used by Session Initiation Protocol (SIP) IP Telephones.
Issue 8 July 2008 19
Introduction
● Avaya Extension to Cellular and Off-PBX Station (OPS) Installation and Administration
● Avaya IP Telephone File Server Application Reference Guide (16-601433)
● Avaya Application Solutions - IP Telephony Deployment Guide (555-245-600)
● 4600 Series IP Telephones Safety Instructions (555-233-779)
Guide (210-100-500)
This document describes the installation, administration, maintenance, and
troubleshooting tasks necessary to install and set up Avaya Extension to Cellular and
Off-PBX Stations.
This document describes how to install and implement the File Server Application for IP
Telephones.
This document describes the Avaya Application Solutions product line, IP telephony
product deployment, and network requirements for
integrating IP telephony products with
an IP network. Includes information on traffic engineering, voice quality and quality of
service, reliability and recovery, and network management.
This document contains important user safety instructions for the 4600 Series IP
Telephones.
● 30A Switched Hub Set Up Quick Reference, Issue 2, July 2002 (555-236-700)
This document contains important safety and installation information for the 30A
Switched Hub.
● 4600 Series IP Telephone Installation Guide (555-233-128)
This document describes how to install 4600 Series IP Telephones. It also provides
troubleshooting guidelines for the 4600 Series IP Telephones.
● 4600 Series IP Telephones Application Programmer Interface (API) Guide (16-300256)
This document provides information on developing Web applications for 4610SW, 4620/
4620SW, 4621SW, 4622SW, and 4625SW IP Telephones. This document also covers
Push feature administration.
● 4601 IP Telephone User Guide (16-300043)
This document provides detailed information about using the 4601 and 4601+ IP
Telephone.
● 4602/4602SW IP Telephone User Guide (555-233-780)
This document provides detailed information about using the 4602/4602SW/4602SW+ IP
Telephone.
● 4602/4602SW SIP IP Telephone User Guide (16-300470)
This document provides detailed information about using the 4602/4602SW SIP IP
Telephone.
● 4606 IP Telephone User Guide (555-233-775)
This document provides detailed information about using the 4606 IP Telephone.
20 4600 Series IP Telephone LAN Administrator Guide
Related Documents
● 4610SW IP Telephone User Guide (555-233-784)
This document provides detailed information about using the 4610SW IP Telephone.
● 4610SW SIP IP Telephone User Guide (16-300472))
This document provides detailed information about using the 4610SW SIP IP Telephone.
● 4612 IP Telephone User Guide (555-233-777)
This document provides detailed information about using the 4612 IP Telephone.
● 4620/4620SW/4621SW IP Telephone User Guide (555-233-781)
This document provides detailed information about using the 4620/4620SW and
4621SW IP Telephones.
● 4620SW/4621SW SIP IP Telephone User Guide (16-300474)
This document provides detailed information about using the 4620SW and 4621SW SIP
IP Telephones.
● 4622SW IP Telephone User Guide (16-300297)
This document provides detailed information about using the 4622SW IP Telephone.
● 4624 IP Telephone User Guide (555-233-776)
This document provides detailed information about using the 4624 IP Telephone.
● 4625SW IP Telephone User Guide (16-300298)
This document provides detailed information about using the 4625SW IP Telephone.
● 4630/4630SW IP Telephone User Guide (555-233-764)
This document provides detailed information about using the 4630/4630SW IP
Telephone.
● Avaya 4690 IP Conference Telephone User Guide (555-233-787)
This document provides detailed information about using the 4690 IP Conference
Telephone.
● 4601/4602/4602SW IP Telephone Stand Instructions (555-233-147)
This document provides information on how to desk- or wall-mount a
4601 or 4602/4602SW IP Telephone and a 4602/4602SW SIP IP Telephone.
● 4610SW IP Telephone Stand Instructions (555-233-165)
This document provides information on how to desk- or wall-mount a
4610SW IP or SIP IP Telephone.
● 4620/4620SW/4621SW/4622SW/4625SW IP Telephone Stand Instructions (16-300299)
This document provides information on how to mount a 4620/4620SW/4621SW/
4622SW/4625SW IP or 4620SW/4621SW SIP IP Telephone on a wall.
Issue 8 July 2008 21
Introduction
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)
22 4600 Series IP Telephone LAN Administrator Guide
Related Documents
● 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)
● 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)
● The TLS Protocol Version 1.0, January 1999, by T. Dierks and C. Allen (RFC 2246)
● SDP: Session Description Protocol, April 1998, by M. Handley and V. Jacobsen (RFC
2327)
● RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals, May 2000, by H.
Schulzrinne and S. Petrack (RFC 2833)
● SIP: Session Initiation Protocol, June 2002, by J. Rosenberg et. al. (RFC 3261)
● Session Initiation Protocol (SIP): Locating SIP Servers, June 2002, by J. Rosenberg and
H. Schulzrinne (RFC 3263)
● Session Initiation Protocol (SIP) - Specific Event Notification, June 2002, by A.B. Roach
(RFC 3265)
● The Session Initiation Protocol (SIP) Refer Method, April 2003, by R. Sparks (RFC 3515)
● A Message Summary and Message Waiting Indication Event Package for the Session
Initiation Protocol (SIP), August 2004, by R. Mahy (RFC 3842)
Issue 8 July 2008 23
Introduction
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
● Recommendations G.726: 40, 32, 24, 16 kbit/s Adaptive Differential Pulse Code
Modulation (ADPCM), December 1990
● G .726 Appendix II, Digit al test sequences for the verification of the G.726 40, 32, 24 and 16
kbit/s ADPCM, March 1991
● G.726 Appendix III, comparison of ADPCM algorithms, May 1994
● G.726 Annex A, Extensions of Recommendation G.726 for use with uniform-quantized
input and output, November 1994
● G.726 Annex B, Packet format capability identifier and capability parameters for H.245
signaling, July 2003
● 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
24 4600 Series IP Telephone LAN Administrator Guide
ISO/IEC, ANSI/IEEE Documents
The following documents are available free from the ISO/IEC standards Web site:
http://www.standards.ieee.org/getieee802/portfolio.html
● 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 Metropolit an 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 networksSpecific 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)
Customer Support
.
● IEEE Std. 802.1X-2004, IEEE Standard for Local and Metropolitan Area Networks -
Port-Based Network Access Control
● IEEE Std. 802.1AB-2005, IEEE Standard for Local and Metropolitan Area Networks:
Station and Media Access Control Connectivity Discovery
● For more information about 802.1AB, see:
http://www.standards.ieee.org/getieee802/download/802.1AB-2005.pdf
● For more information about 802.1X, see:
http://www.standards.ieee.org/getieee802/download/802.1X-2004.pdf
Customer Support
Call the Avaya support number provided to you by your Avaya representative or Avaya reseller
for 4600 Series IP Telephone support.
Information about Avaya products can be obtained at the following URL:
http://www.avaya.com/support
.
.
Issue 8 July 2008 25
Introduction
26 4600 Series IP Telephone LAN Administrator Guide
Chapter 2: Overview of Voice over IP (VoIP) and
Network Protocols
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 (VoIP)
The 4600 Series IP Telephones allow enterprises to use Voice over IP (VoIP). VoIP uses
packet-switched networks over the Public Switched Telephone Network (PSTN) instead of
telephony. However, using data networks to transmit voice packets poses a problem. 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 because of the nature of networking.
● Signaling: establishes 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. Traditional telephony 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.
Issue 8 July 2008 27
Overview of Voice over IP (VoIP) and Network Protocols
● Addressing: a unique address that must identify each terminal on a network.
In a voice network, the unique address is a permanent attribute, based on any
combination of:
- international numbering plans,
- national numbering plans,
- local telephone company practices,
- internal customer-specific codes.
In IP communications, dial plans track extension numbers assigned to terminals. No
fixed connection path is needed.
● Routing: related to addressing and allows connections to be established between
endpoints.
Although these functions are common to data and voice networks, the implementations differ.
Delay and Jitter
Data traffic is usually short and comes in burst s. Dat a networks like the Internet are 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 during the call.
Several features of data networks are unsuitable for voice telephony:
● Data network design delivers data at the destination, but not necessarily within a certain
time, producing delay (latency). In data networks, delay tends to be variable. For voice
messages, variable delay results in jitter, an audible choppiness in conversations.
● Variable routing also can result in loss of timing synchronization, so packets are not
received at the destination in the proper order.
● Data networks have a strong emphasis on error correction, resulting in repeated
transmissions.
Data network concepts include prioritization of traffic types to provide some form of greater
traffic reliability, for example, for interactive transactions. However, data requirements tend to
not be as strict as most voice requirements.
The 4600 Series IP Telephones include a dynamic jitter buffer. This feature automatically
smooths jitter to improve audio quality.
28 4600 Series IP Telephone LAN Administrator Guide
Tandem Coding
Tandem coding, also called transcoding, refers to converting a voice signal from analog to
digital and back again. When calls are routed over multiple IP facilities, they can be subject to
multiple transcodings. The multiple conversions between analog and digital coding result in a
deterioration in the voice quality. Avoid tandem coding wherever possible in any compressed
voice system, for example, by minimizing analog trunking on the PBX.
Voice Coding Standards
There are several voice coding standards. Avaya 4600 Series IP Telephones offer these
options:
● 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 telephone network or
through PBXs.
● G.726 ADPCM at 32Kbps.
● G.729A and G.729B, both of which describe adaptive code-excited, linear-predictive
(CELP) compression that allows voice to be coded into 8 kbps streams.
Overview of Voice over IP (VoIP)
Telephony Protocols
There are two major protocols used for Voice over IP (VoIP) signaling - Session Initiation
Protocol (SIP) and H.323. The two protocols provide connection control and call progress
signaling, but in very different ways. These protocols can be used simult aneously over the same
network, but in general, no endpoint supports both protocols at the sa me time. Neith er protocol
is necessarily superior, but each offers some unique advantages. SIP telephones, for example,
do not require centralized call servers, and can route telephone calls when a URL identifies the
destination. H.323 telephones leverage the call server’s presence into the potential availability
of hundreds of telephone-related features that a standalone SIP telephone cannot provide.
DHCP
Dynamic Host Configuration Protocol (DHCP) allows a server to assign IP Addresses and other
parameters to devices like the 4600 Series IP Telephones on an as-needed basis. DHCP
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. The DHCP application
identifies the PBX and the file server’s IP Addresses. The application also identifies the paths to
the upgrade script and the application file on the file server.
For further information, see DHCP and File Servers
on page 58 and DHCP on page 60.
Issue 8 July 2008 29
Overview of Voice over IP (VoIP) and Network Protocols
TFTP
The Avaya 4600 IP Telephones can get useful application information from the TFTP server.
The telephones also can upgrade themselves using files stored on the TFTP server. After
downloading software, the Avaya 4600 Series IP Telephones can operate without a file server.
However, some functionality can be lost if the file server is not available for a telephone reset.
For further information, see:
● DHCP and File Servers on page 58,
● TFTP (H.323 Only) on page 73, and
● Table 1: File Servers and Compatible Telephone Software.
HTTP
HTTP is potentially a more secure alternative to TFTP, particularly when Transport Layer
Security (TLS) is used to create HTTPS (Secure HTTP). You can store the same application
software, script file, and settings file on an HTTP server as you can on the TFTP server. With
proper administration, the telephone seeks out and uses that material appropriately. However,
not all 4600 Series IP Telephones support HTTP, as indicated in Table 1
Table 1: File Servers and Compatible Telephone Software
.
DNS
IP Telephone Software
File Server IP Telephone Models
HTTP, HTTPS, or TFTP 4601+, 4602SW+, 4625SW
4601, 4602, 4602SW, 4610SW, 4620,
Release Number
R2.7
R2.2+
4620SW, 4621SW, 4622SW
HTTP, HTTPS or TFTP 4690 R 2.3
TFTP 4606, 4612, 4624, 4625SW, 4630,
All releases
4630SW
For Release 2.8 and future releases only, use HTTPDIR
and HTTPPORT to configure backup/
restore and file retrieval operations. These must be set via DHCP for retrieving script files.
As with TFTP, some functionality might be lost by a reset if the HTTP server is not available.
For more information, see DHCP and File Servers
on page 58 and HTTP on page 75.
The Domain Name System (DNS) is a distributed Internet directory service. DNS is used mostly
to translate between domain names and IP Addresses. Release 1.5 and later Avaya IP
Telephones can use DNS to resolve names into IP Addresses. In DHCP, TFTP, and HTTP files,
DNS names can be used wherever IP Addresses were available as long as a valid DNS server
is identified first. See DNS Addressing
on page 114.
30 4600 Series IP Telephone LAN Administrator Guide
Loading...