Avaya 3631 User manual

All rights reserved forAvaya Inc. and Avaya Deutschland GmbH
Avaya 3631IP Wireless Handset
Configuration Guide for Co-existence with
the Avaya 3641/3645 IP Wireless Handset
Offering
Edition 1.0
January20, 2011
Document number:21-603883

- 2 -
All rights reserved forAvaya Inc. and Avaya Deutschland GmbH
History
Date Version Changes
Nov.12,20100.1First internal draft
Nov.24,20100.2Updates byR&D
Dec. 07,20100.3Updates byR&D
Dec. 15,20100.4Updates after comments fromAGS
Jan. 20, 20111.0Official versionwith document number
Table of Contents
1INTRODUCTION ..................................................................................................3
2HANDSET HARDWARE COMPARISON.............................................................3
3HANDSET CONFIGURATION .............................................................................5
3.1 3631 CONFIGURATION.......................................................................................5
3.2 3641, 3645 CONFIGURATION .............................................................................5
3.3 SOFTWARE UPGRADE........................................................................................5
4WLANACCESS POINT DEPLOYMENT CONSIDERATIONS & GUIDELINES..5
4.1 CONFIGURATION WITHIN THE SAME SSID ............................................................6
4.2 CONFIGURATION WITHIN MULTIPLE SSIDS...........................................................6
4.3 QOSUNDER 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
5COMMUNICATION MANAGER ADMINISTRATION CONSIDERATIONS AND
GUIDELINES..............................................................................................................7
5.1 SUPPORTED ACM RELEASES AND STATION TYPE .................................................7
6KNOWN LIMITATIONS........................................................................................7
7VERIFICATION TESTS AND TROUBLESHOOTING..........................................8

- 3 -
All rights reserved forAvaya Inc. and Avaya Deutschland GmbH
1Introduction
The AvayaIP wireless handset 3631 was generallyavailable from2007 to 2010. It will be “end of
sales” fromJanuary1st 2011, see https://support.avaya.com/css/P8/documents/100113780.
The AvayaIP wireless handsets 3641 or 3645 can be used as successor.
Avaya recommendsa complete deployment of either only3631 phones oronly364x phones, to
overcome the belowdescribed limitations and to avoid the belowdescribed configuration
risks. Configuration risksmayarise from the need to change the existing 3631 configuration or
from the need to understand and support two different configuration environments in parallel.
Ifa complete replacement of3631 phones is not possible,a mixed deploymentis possible. The
purpose ofthis configuration guideis todescribe 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 orlater. The 3631was onlyapproved for the CM.
3) Customer mayor maynot 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 (VIEWcertification) than the3631. The
364x phone supports a different (and smaller) set ofsecuritymethods than the 3631.
5) Differences in user interface and feature operationwill exist and are not addressed inthis guide.
2Handset hardware comparison
Feature
3631
3641
3645
DisplayColor, 128 x 128 pixel B/W, 128 x 96 pixelB/W, 128 x 96 pixel
Soft keys244
Specific hardkeysMute
Speaker
Cancel
A (Avaya menu)
FCN
LINE FCN LINE
Push to Talk
BacklightingDisplayandkeypadDisplayandkeypadDisplayandkeypad
Weight107 g 110,6 g (standard batt.) 119,1 g (standard batt.)
Separate Loudspeaker - YesYes
Personal data storageSIM card- -
Durability-IP53, MIL STD 810FIP53, MIL STD 810F
Radio modes 802.11 b/g802.11 a
802.11 b/g 802.11 a 802.11 b/g
Headsetjack Samsung SG4Standard 2,5 mm Standard 2,5 mm
BatterytechnologyLi-IonNiMhNiMh
Batterycapacities4 h talk, 40 h standby4 h talk, 80 h standby
6 h talk, 120 h standby
8 h talk, 160 h standby
4 h talk, 80 h standby
6 h talk, 120 h standby
8 h talk, 160 h standby
Charger optionsTravel charger
Single stand
Dual stand
Single stand
Dual stand
Quad batterycharger
Single stand
Dual stand
Quad batterycharger
ServiceabilityinterfaceUSB / serial cable
directlyto phone USB via the dual stand (configuration cradle) USB via the dual stand (configuration cradle)
Accessories leather holsterGreat varietyGreat variety

- 4 -
All rights reserved forAvaya Inc. and Avaya Deutschland GmbH
Key
-
Lock Button
Left Soft Button
SendButton
Navigation Button
End/Power Button
A-menu Button
Dial Pad
Microphone
Speaker
Volume Button
Cancel Button
Right Soft Button
Quiet mode Button
Mute Button
Speakerphone Button
OK Button
Headset Jack

- 5 -
All rights reserved forAvaya Inc. and Avaya Deutschland GmbH
3Handset configuration
3.1 3631 Configuration
The Avaya3631 phone canbe configured via
1. the User Interface (Admin mode in Advanced Settings),
2. USB connection to aPC (local upload of46xxsettings.txt file)
3. remote upload of46xxsettings.txt file via HTTP server.
The 3631 admin mode is accessible without unregistering or restarting the phone.
3.2 3641, 3645 Configuration
The Avaya3641 and 3645can be configured via
1. the User Interface (Admin Mode)
2. HATtool (HAT: Handset AdministrationTool). Make sure HATtool is installed on the PC and
364x phones is reachable via USB charger.
Access to the 364x Administration Menu requires a restart ofthe phone, the phone is not registeredin
this state.
3.3 Software Upgrade
3631phones: Software upgrade can onlybe done remotelyvia HTTP.
364x phones (withH.323 software load) do not support HTTP server, theyonlysupport TFTP server
for remote upgrade ofsoftware. The handling ofthe TFTP server for software upgrade is described in
the 364x Administration Guide.
In addition the software onthe 364x phones can be upgraded locallyvia HAT.
4WLANAccess Point Deployment Considerations
& Guidelines
Avaya3631 phones and Avaya3641/3645phones can be used in the sameWLAN infrastructure.
See Polycom´s VIEWCertification Guidelines for WLAN access point models, which are approved for
the Avaya3641 and3645 phones (SpectraLink8020/8030 Wireless Telephones). Polycomand Avaya
onlysupport 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 and3641/3645 phones with QoS (QualityofService) = WMM,
because otherwise anAVPP must be purchased and installed for the 3641/3645phones, but the QoS
strategies ofthe 3631 phones (none or WMM) and 3641/3645 phones (SVP) would notbe
synchronized withtherisk,that access points would become overloaded.
WMM and 802.1X requires software “R3” (version 117.052 and higher) on the 3641/3645 phones.
Newphones manufactured in 2010or later will have loadedthis version in the factory. Iffor any
reason an older phone withan older softwareshall be used, the software can be upgraded via the
HATtool.
More documents to read:PolycomAdmin Guide
https://support.avaya.com/css/P8/documents/100068905

- 6 -
All rights reserved forAvaya Inc. and Avaya Deutschland GmbH
4.1 Configuration within thesame SSID
Configure 364x phones withsameWLAN SystemSet Identifiers SSID as usedby3631phones. This
can be done, ifcommon settings for QoS andWLAN securitycan be used.
Advantages: The whole WLAN Voice networkwill be on same SSID.
Restrictions: Refer KnownLimitations Section below for more details
4.2 Configuration within multiple SSIDs
Configure 364x phones withdifferent WLAN SystemSet Identifiers SSID as used by3631 phones.
This can be used, ife.g.the installedbase of3631uses asecuritymethod, which 3641/3645 don´t
support.
Advantages: Required WLAN settings for 364x phones can be done without disturbing thecurrent
setup.
Restrictions: Refer KnownLimitations Section below for more details.
4.3 QoS under 802.11e Wireless Multimedia(WMM)
requirements (inclusiveof VIEW requirements)
3631phones canbeoperated with QoS= noneor WMM basic.
3641/3645 phones require QoS =SVP or WMM. WMMmeans WMM basic, PS (power safe) and AC
(admission control).
ConsideringWLAN infrastructure is configuredfor WMM (802.11e), 3631and 364x phones will work
with the same configuration.
Note: For detailed configurationofQoS with SVP andWMM for 364x phones, refer the belowlinkfor
configuration guides with different vendor.
http://www.polycom.com/global/documents/support/user/products/voice/VIEW_Certified_Products_Gui
de.pdf
4.3.1Upgrade a 3631installed basefromQoS = none toWMM basic
See chapter 5 regarding QoS in the document “3631 Wireless Telephone Administrator Guide”. The
configuration must be made inthephones, the access points and the ACM.
https://support.avaya.com/css/P8/documents/100013880
4.4 Securityoptions and configuration (inclusiveof
802.1x/WPA/WPA2, etc)
The following table shows common (green) securitysettings:
WLAN
security
3631
3641
/3645
none Yes Yes
WEP 40 bit and 128 bit Yes Yes
WPA-PSK Yes Yes
WPA-Enterprise YesNo
WPA2-PSK Yes Yes
WPA2-Enterprise withEAP PEAPv0-MSCHAPv2 PEAPv0-MSCHAPv2

- 7 -
All rights reserved forAvaya Inc. and Avaya Deutschland GmbH
methods mentionedEAP-TLS
PEAPv1/EAP-GTC
LEAP
TTLS-CHAP
TTLS-MD5
TTLS-MSCHAP
TTLS-MSCHAPV2
EAP-FAST
CCXv4NoYes
Cisco FSRNoYes
Regarding WPA2-Enterprise:
•3631phoneneeds thecertificate in format PEM.Phoneprompts theuser for EAP credentials
(userid, password), ifthecredentials are missing or have expired.
•3641/3645 phoneneeds certificate in format DER. EAP credentials can onlybe entered bythe
administrator. Therefore it is recommended, that thecredentials in theRADIUS server don´t
expire.
•3631 phone supports over-the-air downloadofthe certificate. Certificates can be loaded on
the 364x phones onlyvia the HATtool.
5Communication Manager Administration
Considerations and Guidelines
5.1 SupportedACM releases and station type
3631and 364x phones support CM3.1and above.
CM provisioningdifferences/model emulation:
3631phones emulate ACMstation type 4620.
While registering 364x phones withCM 5.2.1 andabove station type must be 4612CL andfor CM
version below 5.2.1 stationtype must be 4612.
6Known limitations
Reallya summaryofthe issues identified above and anyother miscellaneous ones.
1. 802.1X: 364x onlysupportsWPA2-Enterprise (while 3631 also supports WPA-Enterprise).
2. 802.1X: The onlyEAP method, which both3631 and 364x support, is PEAP-MSCHAPv2. But
the certificate format needs to be different: PEM on the 3631 and DER on the 364x.
3631Supports: PEAP-MSCHAPv2, EAP-TLS, EAP-TTLS, EAP-GTC, LEAP.
364xSupports: PEAP-MSCHAPv2 and EAP-FAST
3. 802.1X: EAP credentials (userid, password) can beenteredintothe 3641/3645 onlyby
administrator, therefore should not expire.
4. WPA2-PSK: 364x onlysupports AES encryption (while 3631also supports WPA2-PSK with
TKIP).
5. WMM: 364x requires that the AP´s WMM policyis setto Required or Allowed(while 3631can
also workwithWMM disabled).
6. SW upgrade: 3631 requires a HTTP server for SWupgrade.364x uses a TFTP server for SW
upgrade (alternativelySWupgrade canbe done locallythroughtheHATtool).
7. Multiple WLANProfiles: 364xPhonedoesn’t support multiple WLAN Profiles as it is
supported in 3631 Phone.3631Phone supports up to3 WLAN Profiles

- 8 -
All rights reserved forAvaya Inc. and Avaya Deutschland GmbH
7Verification Tests and Troubleshooting
Careful verificationstestsaremandatoryita mixture of 3631phones and 364x phones shall
be installed. First modifythe configuration ofthe existing 3631phones and WLAN
infrastructure, if necessary.Verification tests shallensure that the existinginstallation of
3631phones goes into service again undisturbed.
Then configure afewnew364x phones, connect them to the network and verifythat they
go into service. Finallyverifythe co-existenceof both phone types (callsbetween 3631
phones and 364x phones,QoS if 3631and 364x phones are associated to the same WLAN
Access Point, …).
1. 364x Phones gets ‘NoReg Domain’ error message
Resolution: 364x Phones needs to beset to the RegulatoryDomain without whichis does not
start the bootprocess. 3631 has no such limitation.
2. There are fewother settingsthat are mandatoryfor the 364x Phones to start the boot process.
Theyare as below:
•SSID (andthesecurityparameters associated with this SSID)
•QoS Settings - StandardWMM or AVPP (AVPP is the Default Valuefor 364x Phone)
•364x Phone uses DHCP SSON 176 (3631 phone uses SSON 242).
For more details please refer the Admin Guide ofthe 364x Phones.
3. IfanewCM feature is added,thenthe364x Phones needs tobe rebootedto get those
feature. 3631 Phone doesn’t need a reboot.
4. Enhanced Dialing Parameters are neededto be able to makeasuccessful callbackfromthe
Call Log. 3631phone getsthesevalues fromthe 46xxsettings file. Needs to be enabledand
set using Admin Menu or through HATin the 364x Phones.