Avaya™ 4600 Series IP Telephone
Job Aid: Implementation Checklist
Issue 1.0
August 2002
RG Avaya
TM
4600 Series IP Telephone Implementation Checklist
Page 2
Avaya
TM
IP Telephone Implementation Checklist
Purpose: This implementation checklist is a high-level overview of the steps required to successfully implement Avaya IP Telephones. It is
supplemental to more detailed checklists found in other IP Telephone documentation.
Step
Complete
( √ )
Category Issue 4602
4606
4612
4620
4624
4630
Physical Verify LAN connection is live at the wall. Y Y Y Y Y Y
The powering plan must be identified up front. Does the customer have a mix
of Gen1 and Gen2 phones? Does the customer want to use 1151B1 "bricks",
or "IEEE power" via midspan or Cajun
®
P333T-PWR? Is the customers'
current electrical serv
ice capable of supporting the extra load? Is it within ANSI
specs as far as voltage fluctuations are concerned? Will the customer be
providing UPS protection? If so, where will the UPS be located and what is its
load capacity?
Y Y Y Y Y Y
The curren
t inventory of phones ship with the older V.08 bootloader (V.08 is not
VLAN aware), so each phone will have to be updated to the latest firmware.
[This applies only if relevant servers are not all on the default VLAN and may
require pre-installation staging.]
Y Y Y Y Y Y
Verify all appropriate parts have shipped with the phone, per the IP Telephone
Installation Guide
Y Y Y Y Y Y
MV (Multi-
Vantage™) or
ACP
(Avaya™
Call Proces-
sing) switch
translations
Minimum software release:
• 4602 – MV 1.1 or later
• 4606, 4612, 4624 – R8.4 or later (dual connect), R9.5 (single connect)
• 4620 – MV 1.1 or later
• 4630 – R10 or later
Y Y Y Y Y Y
Network speed of MultiVantage and IP Telephone ports should be set to match
the Ethernet switch port to which it is connected, e.g., auto-negotiate, etc.
Y Y Y Y Y Y
Verify extension and password are programmed. Y Y Y Y Y Y
Shuffling must be enabled on system parameters, cust options, station, and
network region forms
Y Y Y Y Y Y
Appropriate quantities of RTUs must be purchased and included in the current Y Y Y Y Y Y
RG Avaya
TM
4600 Series IP Telephone Implementation Checklist
Page 3
Step
Complete
( √ )
Category Issue 4602
4606
4612
4620
4624
4630
license file
Verify adequate resources are available on TN799C (or later) C-LAN and
TN2302AP (IP Media Processor)
Y Y Y Y Y Y
General
Network
Was Customer Infrastructure Readiness Survey (CIRS) or equivalent
performed to ensure the network is ready for VoIP? [see http://ncs.avaya.com]
Y Y Y Y Y Y
Verify wiring scheme is CAT5 equivalent or better from the DEFINITY
®
/
MultiVantage™ to the phone.
Y Y Y Y Y Y
If static addressing will be used, then static addresses must be available for
applicable TFTP, LDAP, UCC, web server, etc… server(s) and all phones
Y Y Y Y Y Y
If the customer wants Avaya to assist with the LDAP, Web and VoiceMail
administration for the Avaya™ 4630 IP Screen Phone, they will have to identify
a dedicated IT resource that will work with Avaya's Network Consulting
Services team [http://ncs.avaya.com/] for a fee. The customer must provide all
server related information such as IP Addresses, Port Usage, Proxy
Authentication, LDAP server type (iPlanet, LINUX, Microsoft Active Directory,
etc.)
Y Y Y Y Y Y
On the switch, status station to measure packet loss (statistics available for
non-shuffled calls only)
Y Y Y Y Y Y
Place test calls to another IP station on the same switch, a non-IP station on
the same switch, and voice mail. Do the same for users on another switch, if
possible, to test voice quality over the WAN. Verify the quality is OK,
subjectively.
Y Y Y Y Y Y
DHCP Server
Customer administers per the LAN Admin Guide Y Y Y Y Y Y
LAN administrator has been notified to create a DHCP scope large enough to
accommodate the expected quantity of IP Phones, as detailed in 46xx LAN
Administration Guide.
Y Y Y Y Y Y
DHCP lease expiration should be set to infinity, i.e., leases do not expire Y Y Y Y Y Y
DHCP server must be on default VLAN and "viewable" by the phone at boot-up
Y Y Y Y Y Y
All Routers will need boot-up relay enabled and other appropriate admin Y Y Y Y Y Y
RG Avaya
TM
4600 Series IP Telephone Implementation Checklist
Page 4
Step
Complete
( √ )
Category Issue 4602
4606
4612
4620
4624
4630
TFTP Server Customer administers per the LAN Admin Guide Y Y Y Y Y Y
Server must be capable of opening and transferring 30 files simultaneously Y Y Y Y Y Y
Latest software must be available for users to download from the TFTP boot
directory
Y Y Y Y Y Y
Avaya TFTP Server software has been used, else Avaya does not support the
TFTP server. Avaya's server can be downloaded from http://support.avaya.com
Y Y Y Y Y Y
Verify 46xxsettings.scr file includes Voice Mail (VMLHOME=) variable, even if
null (R1.61 and later)
— — — — — Y
If a non-windows server is used, fix the case of the files Y Y Y Y Y Y
HTTP Server Customer administers per the LAN Admin Guide — — — — — Y
The phone's default web screen is pointed at a HTML web page on Avaya's
support web site. If this will not be used, then the customer must enter the
alternate, internal IP address for the 4630's web screen into 46xxsettings.scr
— — — — — Y
LDAP Server Customer administers per the LAN Admin Guide — — — — — Y
Verify LDAP server is LDAP, version 3 or later — — — — — Y
Verify the customer's LAN administrator has translated the appropriate LDAP
parameters into the 46xxsettings.scr
— — — — — Y
Verify directory entries are displayed when tapping the Directory button and
typing a valid name
— — — — — Y
UCC Server Customer administers per the LAN Admin Guide — — — — — Y
WML Server Customer administers per the LAN Admin Guide — — — Y — —
RG Avaya
TM
4600 Series IP Telephone Implementation Checklist
Page 5
Step
Complete
( √ )
Category Issue 4602
4606
4612
4620
4624
4630
The phone's default web screen is pointed at a WML web page on Avaya's
support web site. If this will not be used, then the customer must enter the
alternate, internal IP address for the 4620's web screen into 46xxsettings.scr
— — — Y — —
Updated 5 August 2002
Notice
Every effort was made to ensure that the information in this document was complete and accurate at the time of publication. However, information
is subject to change without notice.
© 2002 Avaya Inc. All Rights Reserved. All trademarks identified by the ® or
TM
are registered trademarks or trademarks,
respectively, of Avaya Inc. All other trademarks are the property of their respective owners.
/