Avaya 3631 IP Wireless Handset Configuration

Avaya 3631 IP Wireless Handset
Configuration Guide for Co-existence with
the Avaya 3641/3645 IP Wireless Handset
Offering
Edition 1.0
January 20, 2011
Document number: 21-603883
All rights reserved for Avaya Inc. and Avaya Deutschland GmbH
-2-
History
Date
Nov. 12, 2010
Nov. 24, 2010
Dec. 07, 2010
Dec. 15, 2010
Jan. 20, 2011
Version
0.1
0.2
0.3
0.4
1.0
Changes
First internal draft
Updates by R&D
Updates by R&D
Updates after comments from AGS
Official version with document number
Table of Contents
1
INTRODUCTION .................................................................................................. 3
2
HANDSET HARDWARE COMPARISON ............................................................. 3
3
HANDSET CONFIGURATION ............................................................................. 5
3.1
3.2
3.3
4
3631 CONFIGURATION ....................................................................................... 5
3641, 3645 CONFIGURATION ............................................................................. 5
SOFTWARE UPGRADE ........................................................................................ 5
WLAN ACCESS POINT DEPLOYMENT CONSIDERATIONS & GUIDELINES .. 5
4.1 CONFIGURATION WITHIN THE SAME SSID ............................................................ 6
4.2 CONFIGURATION WITHIN MULTIPLE SSIDS ........................................................... 6
4.3 QOS UNDER 802.11E WIRELESS MULTIMEDIA (WMM) REQUIREMENTS (INCLUSIVE
OF VIEW REQUIREMENTS) .......................................................................................... 6
4.3.1 Upgrade a 3631 installed base from QoS = none to WMM basic.............. 6
4.4 SECURITY OPTIONS AND CONFIGURATION (INCLUSIVE OF 802.1X/WPA/WPA2, ETC)
6
5 COMMUNICATION MANAGER ADMINISTRATION CONSIDERATIONS AND
GUIDELINES .............................................................................................................. 7
5.1
SUPPORTED ACM RELEASES AND STATION TYPE ................................................. 7
6
KNOWN LIMITATIONS ........................................................................................ 7
7
VERIFICATION TESTS AND TROUBLESHOOTING .......................................... 8
All rights reserved for Avaya Inc. and Avaya Deutschland GmbH
-3-
1 Introduction
The Avaya IP wireless handset 3631 was generally available from 2007 to 2010. It will be “end of
st
sales” from January 1 2011, see https://support.avaya.com/css/P8/documents/100113780.
The Avaya IP wireless handsets 3641 or 3645 can be used as successor.
Avaya recommends a complete deployment of either only 3631 phones or only 364x phones, to
overcome the below described limitations and to avoid the below described configuration
risks. Configuration risks may arise from the need to change the existing 3631 configuration or
from the need to understand and support two different configuration environments in parallel.
If a complete replacement of 3631 phones is not possible, a mixed deployment is possible. The
purpose of this configuration guide is to describe the following aspects:
1) Customer has 3631 units deployed and wants to add one or more 364x handsets.
2) Customer uses a CM 3.0 or later. The 3631 was only approved for the CM.
3) Customer may or may not have WMM enabled WLAN infrastructure for his 3631 deployment.
4) Configuration changes may need to occur with the 3631 deployment: The 364x telephones have
more restrictive requirements for the WLAN access points (VIEW certification) than the 3631. The
364x phone supports a different (and smaller) set of security methods than the 3631.
5) Differences in user interface and feature operation will exist and are not addressed in this guide.
2 Handset hardware comparison
Feature
3631
3641
3645
Display
Soft keys
Specific hardkeys
B/W, 128 x 96 pixel
4
FCN
LINE
B/W, 128 x 96 pixel
4
FCN
LINE
Push to Talk
Backlighting
Weight
Separate Loudspeaker
Personal data storage
Durability
Radio modes
Color, 128 x 128 pixel
2
Mute
Speaker
Cancel
A (Avaya menu)
Display and keypad
107 g
SIM card
802.11 b/g
Headset jack
Battery technology
Battery capacities
Samsung SG4
Li-Ion
4 h talk, 40 h standby
Charger options
Travel charger
Single stand
Dual stand
USB / serial cable
directly to phone
leather holster
Display and keypad
110,6 g (standard batt.)
Yes
IP53, MIL STD 810F
802.11 a
802.11 b/g
Standard 2,5 mm
NiMh
4 h talk, 80 h standby
6 h talk, 120 h standby
8 h talk, 160 h standby
Single stand
Dual stand
Quad battery charger
USB via the dual stand
(configuration cradle)
Great variety
Display and keypad
119,1 g (standard batt.)
Yes
IP53, MIL STD 810F
802.11 a
802.11 b/g
Standard 2,5 mm
NiMh
4 h talk, 80 h standby
6 h talk, 120 h standby
8 h talk, 160 h standby
Single stand
Dual stand
Quad battery charger
USB via the dual stand
(configuration cradle)
Great variety
Serviceability interface
Accessories
All rights reserved for Avaya Inc. and Avaya Deutschland GmbH
-4-
Speaker
Volume Button
Headset Jack
Mute Button
OK Button
Left Soft Button
Send Button
Speakerphone Button
Navigation Button
Right Soft Button
End/Power Button
Cancel Button
A-menu Button
Dial Pad
Key-Lock Button
Quiet mode Button
Microphone
All rights reserved for Avaya Inc. and Avaya Deutschland GmbH
-5-
3 Handset configuration
3.1 3631 Configuration
The Avaya 3631 phone can be configured via
1. the User Interface (Admin mode in Advanced Settings),
2. USB connection to a PC (local upload of 46xxsettings.txt file)
3. remote upload of 46xxsettings.txt file via HTTP server.
The 3631 admin mode is accessible without unregistering or restarting the phone.
3.2 3641, 3645 Configuration
The Avaya 3641 and 3645 can be configured via
1. the User Interface (Admin Mode)
2. HAT tool (HAT: Handset Administration Tool). Make sure HAT tool is installed on the PC and
364x phones is reachable via USB charger.
Access to the 364x Administration Menu requires a restart of the phone, the phone is not registered in
this state.
3.3 Software Upgrade
3631 phones: Software upgrade can only be done remotely via HTTP.
364x phones (with H.323 software load) do not support HTTP server, they only support TFTP server
for remote upgrade of software. The handling of the TFTP server for software upgrade is described in
the 364x Administration Guide.
In addition the software on the 364x phones can be upgraded locally via HAT.
4 WLAN Access Point Deployment Considerations
& Guidelines
Avaya 3631 phones and Avaya 3641/3645 phones can be used in the same WLAN infrastructure.
See Polycom´s VIEW Certification Guidelines for WLAN access point models, which are approved for
the Avaya 3641 and 3645 phones (SpectraLink 8020/8030 Wireless Telephones). Polycom and Avaya
only support the certified access points.
http://www.polycom.com/global/documents/support/user/products/voice/VIEW_Certified_Products_Gui
de.pdf.
It is recommended to use the 3631 and 3641/3645 phones with QoS (Quality of Service) = WMM,
because otherwise an AVPP must be purchased and installed for the 3641/3645 phones, but the QoS
strategies of the 3631 phones (none or WMM) and 3641/3645 phones (SVP) would not be
synchronized with the risk, that access points would become overloaded.
WMM and 802.1X requires software “R3” (version 117.052 and higher) on the 3641/3645 phones.
New phones manufactured in 2010 or later will have loaded this version in the factory. If for any
reason an older phone with an older software shall be used, the software can be upgraded via the
HAT tool.
More documents to read: Polycom Admin Guide
https://support.avaya.com/css/P8/documents/100068905
All rights reserved for Avaya Inc. and Avaya Deutschland GmbH
-6-
4.1 Configuration within the same SSID
Configure 364x phones with same WLAN System Set Identifiers SSID as used by 3631 phones. This
can be done, if common settings for QoS and WLAN security can be used.
Advantages: The whole WLAN Voice network will be on same SSID.
Restrictions: Refer Known Limitations Section below for more details
4.2 Configuration within multiple SSIDs
Configure 364x phones with different WLAN System Set Identifiers SSID as used by 3631 phones.
This can be used, if e.g. the installed base of 3631 uses a security method, which 3641/3645 don´t
support.
Advantages: Required WLAN settings for 364x phones can be done without disturbing the current
setup.
Restrictions: Refer Known Limitations Section below for more details.
4.3 QoS under 802.11e Wireless Multimedia
requirements (inclusive of VIEW requirements)
(WMM)
3631 phones can be operated with QoS = none or WMM basic.
3641/3645 phones require QoS = SVP or WMM. WMM means WMM basic, PS (power safe) and AC
(admission control).
Considering WLAN infrastructure is configured for WMM (802.11e), 3631 and 364x phones will work
with the same configuration.
Note: For detailed configuration of QoS with SVP and WMM for 364x phones, refer the below link for
configuration guides with different vendor.
http://www.polycom.com/global/documents/support/user/products/voice/VIEW_Certified_Products_Gui
de.pdf
4.3.1 Upgrade a 3631 installed base from QoS = none to WMM basic
See chapter 5 regarding QoS in the document “3631 Wireless Telephone Administrator Guide”. The
configuration must be made in the phones, the access points and the ACM.
https://support.avaya.com/css/P8/documents/100013880
4.4 Security options and
802.1x/WPA/WPA2, etc)
configuration
(inclusive
The following table shows common (green) security settings:
WLAN security
3631
3641/3645
none
WEP 40 bit and 128 bit
WPA-PSK
WPA-Enterprise
WPA2-PSK
WPA2-Enterprise with EAP
Yes
Yes
Yes
Yes
Yes
PEAPv0-MSCHAPv2
Yes
Yes
Yes
No
Yes
PEAPv0-MSCHAPv2
All rights reserved for Avaya Inc. and Avaya Deutschland GmbH
of
-7-
methods mentioned
CCXv4
Cisco FSR
EAP-TLS
PEAPv1/EAP-GTC
LEAP
TTLS-CHAP
TTLS-MD5
TTLS-MSCHAP
TTLS-MSCHAPV2
No
No
EAP-FAST
Yes
Yes
Regarding WPA2-Enterprise:
• 3631 phone needs the certificate in format PEM. Phone prompts the user for EAP credentials
(userid, password), if the credentials are missing or have expired.
• 3641/3645 phone needs certificate in format DER. EAP credentials can only be entered by the
administrator. Therefore it is recommended, that the credentials in the RADIUS server don´t
expire.
• 3631 phone supports over-the-air download of the certificate. Certificates can be loaded on
the 364x phones only via the HAT tool.
5 Communication
Manager
Considerations and Guidelines
Administration
5.1 Supported ACM releases and station type
3631 and 364x phones support CM 3.1 and above.
CM provisioning differences/model emulation:
3631 phones emulate ACM station type 4620.
While registering 364x phones with CM 5.2.1 and above station type must be 4612CL and for CM
version below 5.2.1 station type must be 4612.
6 Known limitations
Really a summary of the issues identified above and any other miscellaneous ones.
1. 802.1X: 364x only supports WPA2-Enterprise (while 3631 also supports WPA-Enterprise).
2. 802.1X: The only EAP method, which both 3631 and 364x support, is PEAP-MSCHAPv2. But
the certificate format needs to be different: PEM on the 3631 and DER on the 364x.
3631 Supports: PEAP-MSCHAPv2, EAP-TLS, EAP-TTLS, EAP-GTC, LEAP.
364x Supports: PEAP-MSCHAPv2 and EAP-FAST
3. 802.1X: EAP credentials (userid, password) can be entered into the 3641/3645 only by
administrator, therefore should not expire.
4. WPA2-PSK: 364x only supports AES encryption (while 3631 also supports WPA2-PSK with
TKIP).
5. WMM: 364x requires that the AP´s WMM policy is set to Required or Allowed (while 3631 can
also work with WMM disabled).
6. SW upgrade: 3631 requires a HTTP server for SW upgrade. 364x uses a TFTP server for SW
upgrade (alternatively SW upgrade can be done locally through the HAT tool).
7. Multiple WLAN Profiles: 364x Phone doesn’t support multiple WLAN Profiles as it is
supported in 3631 Phone. 3631 Phone supports up to 3 WLAN Profiles
All rights reserved for Avaya Inc. and Avaya Deutschland GmbH
-8-
7 Verification Tests and Troubleshooting
Careful verifications tests are mandatory it a mixture of 3631 phones and 364x phones shall
be installed. First modify the configuration of the existing 3631 phones and WLAN
infrastructure, if necessary. Verification tests shall ensure that the existing installation of
3631 phones goes into service again undisturbed.
Then configure a few new 364x phones, connect them to the network and verify that they
go into service. Finally verify the co-existence of both phone types (calls between 3631
phones and 364x phones, QoS if 3631 and 364x phones are associated to the same WLAN
Access Point, …).
1. 364x Phones gets ‘No Reg Domain’ error message
Resolution: 364x Phones needs to be set to the Regulatory Domain without which is does not
start the boot process. 3631 has no such limitation.
2. There are few other settings that are mandatory for the 364x Phones to start the boot process.
They are as below:
•
SSID (and the security parameters associated with this SSID)
•
QoS Settings - Standard WMM or AVPP (AVPP is the Default Value for 364x Phone)
•
364x Phone uses DHCP SSON 176 (3631 phone uses SSON 242).
For more details please refer the Admin Guide of the 364x Phones.
3. If a new CM feature is added, then the 364x Phones needs to be rebooted to get those
feature. 3631 Phone doesn’t need a reboot.
4. Enhanced Dialing Parameters are needed to be able to make a successful callback from the
Call Log. 3631 phone gets these values from the 46xxsettings file. Needs to be enabled and
set using Admin Menu or through HAT in the 364x Phones.
All rights reserved for Avaya Inc. and Avaya Deutschland GmbH