APP NOTE - Avaya Support

APP NOTE - Avaya Support
Avaya, Aruba and Nokia Mobility Solution
Abstract
This application note describes the Avaya, Aruba and Nokia mobility
solution. This document is not a user guide or sales brochure. It is a ‘howto/tips’ application note for the Avaya, Aruba and Nokia Wi-Fi solution
targeting engineers and administrators.
APP
NOTE
©2006 Avaya Inc. All Rights Reserved.
Page 1 of 41
avaya.com
2
TABLE OF CONTENTS
1. Terminology and Acronyms.........................................................................4
2. Dual Mode Solution Overview
5
General Solution Architecture................................................................5
3. Avaya one-X Mobile Edition Dual-Mode Application .....................................6
Avaya Communication Manager and SIP Enablement Services.................6
Nokia E-Series Devices.........................................................................7
4. Equipment and Software Validated ..............................................................8
5. WiFi System Description
9
6. WiFi System Architecture ...........................................................................9
ArubaOS Software ......................................................................................9
Aruba Mobility Controllers........................................................................10
Aruba Access Points ................................................................................11
Centralized Network Management.............................................................11
7. ARUBA Access Point Controllers ...............................................................11
8. Access Points..........................................................................................12
9. VoIP Performance Metric .........................................................................12
10. Dual-Mode Test Configuration
13
11. WiFi System Settings for VoIP Dual-Mode
14
General WiFi Settings...............................................................................14
1. SSID ..................................................................................................14
2. Data Rates (Default setting).................................................................14
3. DTIM (power save settings) .................................................................14
4. RTS threshold (Default Settings) ..........................................................14
5. Antenna Diversity ...............................................................................14
6. Band Preference.................................................................................15
7. RF Management / Channel and power settings (ARM)............................15
8. Call Admission Control........................................................................15
9. Miscellaneous....................................................................................16
Extended Battery ................................................................................16
Proxy-arp ...........................................................................................16
Local probe response .........................................................................16
12. WiFi Security Settings
17
Open..................................................................................................17
WEP ..................................................................................................17
WPA-TKIP-PSK ...................................................................................17
WPA2-AES-PSK ..................................................................................18
WPA2 PEAP 802.11i ..........................................................................18
©2006 Avaya Inc. All Rights Reserved.
Page 2 of 41
avaya.com
3
13. Security Firewall Settings and QoS
19
14. WiFi Multi-Media (WMM) Basic Support
20
QoS (802.11e) Parameters to Optimize Voice.......................................20
15. Avaya one-X Mobile Edition Settings
20
16. VoIP Settings
21
Nokia phone Administration
21
Create and configure your WLAN Access Point Profile ..........................21
17. Create and configure SIP Profile ...............................................................36
18. Setting different dual-mode network modes: ..............................................38
19. Dual-Mode Assisted Handover ..................................................................38
20. References
40
©2006 Avaya Inc. All Rights Reserved.
Page 3 of 41
avaya.com
4
1. Terminology and Acronyms
Term
Meaning
AST
Advanced SIP Telephony
Avaya CM
Avaya Communication Manager
Avaya SES
Avaya SIP enablement services
EC500
Avaya EC500 (Extension to Cellular) – An offer that lets cell
phones under control of a public wireless carrier function as if
they were extensions on an Avaya CM .
FMC
Fixed Mobile Convergence
FNE
A Feature Name Extension is a phone extension you can dial that
allows you to access an Avaya CM feature from your cell phone.
FNU
Feature Name URI
OPS
Off-PBX station
PBFMC
PuBlicFMC, RTU needed for CM 4.0 Dual-Mode (maps to user’s
cell phone)
PVFMC
PriVateFMC, RTU needed for CM 4.0 Dual-Mode (maps to user’s
cell phone)
PBX
Private Branch Exchange – A generic name for a premise based
switch supporting telephony features owned by an enterprise.
The Avaya CM is a type of PBX.
SES
Avaya SIP Enablement Services
SIP
Session Initiation Protocol
©2006 Avaya Inc. All Rights Reserved.
Page 4 of 41
avaya.com
5
2. Dual Mode Solution Overview
This application note describes the Avaya, Aruba and Nokia mobility
solution. This document is not a user guide or sales brochure. It is a ‘howto/tips’ application note for the Avaya, Aruba and Nokia WiFi solution
targeting engineers and administrators.
The Dual Mode solution has been verified by the Avaya engineers. This
application note describes the configuration steps and the software version
information that was tested for the solution in the Avaya labs.
¾ General Solution Architecture
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Avaya one-X Mobile for S60 3rd Edition Dual Mode
– Client/Phone/Device Software is responsible for all the handoff
decisions
– NO EXTRA H/W required
– Re-use existing Avaya servers (CM and SES)
– Reuse EC500 FNEs and SIP AST FNUs
– Provides Enterprise Telephony Features such as Transfer, Conference,
Call Park, Call Pickup, etc.
– Bottom-line: Get Dual-mode features without adding additional servers
Provides simple user access to Avaya Communication Manager mobile
telephony services and features
Designed to simplify user experience and access to Extension to Cellular
features
Bind graphical menu with Feature Name Extensions (FNE’s)
One Business Number
Simplified access to “Top 20” PBX features – a business softphone on a
mobile phone
Full business call control: hold, conference, transfer, assistant support,
extension dialing
It is your office phone!
One number access – incoming office phone calls extended to mobile phone
One voice mail to check
Outgoing calls use corporate network
Centralized management & reporting
Easily switch between personal and business use of mobile phone
Support for 11 Languages
©2006 Avaya Inc. All Rights Reserved.
Page 5 of 41
avaya.com
6
3. Avaya one-X Mobile Edition Dual-Mode Application
Avaya one-X mobile Dual Mode refers to a device that is capable of using
two networks: GSM and Wi-Fi/SIP (WLAN 802.11b/g) one-X mobile Dual
Mode = GSM + Wi-Fi/SIP
¾ Avaya Communication Manager and SIP Enablement Services
Following are the software requirements for the Avaya Communication
Manager and Avaya SES:
Avaya CM Requirements
• CM SW Release 3.1.2 Load 632.1 and higher (CM 4.0).
• RTUs/Licensing
– CM 3.1.2: Needs EC500 and OPS
– CM 4.0: Needs PBFMC and PVFMC (PuBlicFMC / PriVateFMC)
– SIP Trunking licenses required
• Need to administer “no-hld-cnf” button on all stations for conferencing to
work.
• Need to have respective feature buttons such as “call-park”, “call-pkup”, if
being used.
Avaya SES Requirements
•
•
SES 3.1 Release or greater.
Licensing
– Client licenses required
– Home or Home/Edge licenses required
©2006 Avaya Inc. All Rights Reserved.
Page 6 of 41
avaya.com
7
¾ Nokia E-Series Devices
•
•
Nokia Device Requirements
Only E60, E61, and E70 are supported for dual-mode.
Device must have at least the following FW:
– On the main Nokia screen, enter following sequence as a phone number:
*#0000#
– You should see the FW version here; needs to be at least 2.0618.06.05
– If the device has an older FW, Nokia allows users to flash the FW using
a Software Update Tool from Nokia’s website
– There are known issues with certain Nokia E-Series models and
upgrading the firmware to the minimum version 2.0618.06.05. This has
to do with the region code of the E-Series set. Some users are not able
to upgrade their phones (No Software Upgrade Available).
Note: more detail is available at
http://discussions.europe.nokia.com/discussions/board/message?board.i
d=swupdate&message.id=451
For support and help, contact your local Nokia support center.
©2006 Avaya Inc. All Rights Reserved.
Page 7 of 41
avaya.com
8
4. Equipment and Software Validated
The following equipments and software were used in the configuration
shown in Table 1.
Table 1: Equipment and the Software versions used
Equipment
Avaya SIP-Enablement Services (SES)
Avaya CM
Nokia E-61
Aruba Controller: Aruba 800
Aruba Access Point: Aruba-AP 61
Software
SES 3.1.1
SES03.1.1-03.1.114.0
Communication Manager 3.1.2
R13x.01.2.631.1
2.0618.06.05
2.5.4.0(build 12461)
Note: Refer to user guide and administration guide for other supported devices
and configurations. User guide and administration guide will be available for
download from Avaya Support Site.
– Go to http://www.avaya.com/
– Click on ‘Support’ link
– Click on ‘Find Documentation and Downloads by Product Name’ or click
on ‘Downloads’
– Click on ‘one-X Mobile Edition’
– Click on ‘Documents’
– Select Release 4.0
©2006 Avaya Inc. All Rights Reserved.
Page 8 of 41
avaya.com
9
5. WiFi System Description
The solution is designed to interoperate with the Avaya Communication
Manager, Avaya SES, and Nokia handsets at the edge. Avaya’s
Communication Manager integrates telephony call processing, call control,
messaging, contact center and a widely accepted application programming
interface into a highly scalable architecture designed to support both
circuit-based and IP-based telephony within a distributed Enterprise
communications network.
Note: Section 4 through 8 and 10 through13 were provided by Aruba.
6. WiFi System Architecture
Aruba’s Mobile Edge allows users and devices to connect over the air and
across any network, to securely gain access to Enterprise resources. It is a
new layer in the network that logically sits on top of existing, fixed
networks and fulfills the requirements of security, mobility and convergence
without requiring major upgrades to the existing network. The Mobile Edge
is architected to work securely over existing IP network facilities, and
extends across both private Enterprise networks as well as the public
Internet. Aruba’s Mobile Edge System consists of four components:
ArubaOS Software
Providing unified services to power the Mobile Edge, ArubaOS is a
comprehensive suite of system software for Aruba Mobility Controllers and
Access Points. ArubaOS uniquely integrates services of security, mobility,
application-awareness, management and RF-tuning together to deliver the
most secure and reliable anywhere, anytime access for Enterprise users.
©2006 Avaya Inc. All Rights Reserved.
Page 9 of 41
avaya.com
10
Aruba Mobility Controllers
Enabling secure mobile services requires a combination of network
elements and RF intelligence. Aruba offers the only mobile security system
with an integrated ICSA-certified stateful firewall and hardware-based
encryption. All Aruba Mobility Controllers combine powerful packet
processing with 10/100/1000 Mbps Ethernet switching, stateful LAN-speed
firewall, VPN termination, wireless intrusion protection, AAA, client
integrity, captive portal and advanced RF management within a single
network device. All Aruba Mobility Controllers integrate non-disruptively
into any existing L2/L3 wired network with no logical or physical reconfiguration of the underlying transport infrastructure required.
Corporate Campus
Regional Offices Remote Offices
Remot
e
AP
Home Offices Instant Internet
Offices
AP-60
AP-61
AP70
Partner
s
ARUBA 2400
LA
N
WAN
Internet
ARUBA 6000
Customers
Regional Offices
AP80
ARUBA 800
Retail Outlets
Remot
e
AP
AP-41
AP-2E
©2006 Avaya Inc. All Rights Reserved.
AP-65
Hotels
Page 10 of 41
avaya.com
11
Aruba Access Points
When Aruba dependent Access Points (APs), are connected to an IP
network, they automatically discover the Aruba Mobility Controller,
configure themselves and begin operating: the Mobility Controller is
responsible for downloading software images, configuring and coordinating
all dependent APs. APs continuously scan the RF environment, supplying
information to optimize radio coverage and provide wireless intrusion
prevention without having to deploy a separate sensor network. Aruba’s
dependent AP architecture coupled with radio planning optimization and
workspace deployment options – out of the ceiling – greatly reduces WLAN
deployment costs. IT staff can place APs supporting power over Ethernet
(PoE), in employee cubicles leveraging existing Ethernet cabling.
Aruba offers a range of APs with single- and dual-radio capability: all are
capable of operation in the 2.4 GHZ (802.11b/g) and 5 GHz (802.11a)
bands. Indoor and outdoor options are provided, including integrated
wireless bridges.
Centralized Network Management
Comprehensive network planning, configuration and monitoring are all
achieved with either a single Mobility Controller or a dedicated Mobility
Management System (MMS). In both cases, the management interface is
presented to clients as an intuitive graphical user interface (GUI). To
extend management capabilities further, either system can be used with
existing NMS systems and best of breed management tools.
7. ARUBA Access Point Controllers
The bulk of the intelligence of the Aruba Mobility System resides in the
controllers. Aruba supports a number of controller models which differ only
in their capacities (number of APs and number of users supported). All the
controllers support the same functionality. Various software licenses need
to be enabled on the controller to enable its various functionalities. The
controller will still operate as a basic WLAN switch without any of these
licenses but it is recommended to enable the security and QoS license to
secure the WiFi network and to ensure QoS. Ensure that at a minimum the
Firewall Policy Module is enabled on the controllers in use. The firewall
Module License enables session awareness, prioritized traffic processing
and packet tagging on the controller.
©2006 Avaya Inc. All Rights Reserved.
Page 11 of 41
avaya.com
12
•
•
Release 2.5.4.0 and below support on the air QoS in the downstream
direction and wired QoS. However these images do not support WMM.
Ensure that a 3.0 and above release of the software is used if WMM is
being used in the environment.
The Nokia phones have been tested for interoperability with the 2.5.4
images.
NOTE: Enabling WMM on the controllers in 3.X.X does not require additional licenses
Source: Aruba
8. Access Points
The Aruba Solution supports 802.11a and 802.11b/g mixed environments.
When using dual radio APs (AP70, AP65), 802.11a and 802.11b/g modes
can be enabled simultaneously. The Nokia handsets are 802.11b/g
handsets. The recommended setting would therefore be to enable the
802.11b and 802.11g rates. This setting ensures that the b and g clients
share the 2.4 GHz band without hidden node issues.
Note: Recommended setting is to ensure that both b and g rated are enabled on the Access
Points.
•
To interoperate with the Nokia handsets ensure that the single mode APs
are configured to operate in the 802.11b/g modes and the dual radio APs
have their b/g radios enabled and set to AP mode.
9. VoIP Performance Metric
Aruba has implemented a number of features enhancing QoS and
dramatically improving client density, with independent test results showing
maximum figures of 22 calls using 802.11b and 75 calls with 802.11g or
802.11a. These features allow a 2-radio Access Point to support up to 150
active voice calls under ideal conditions.
In actual deployments, not all clients will connect at the highest rate, and
the network manger may choose to leave some bandwidth available for data
applications. This can be achieved using the Aruba Call Admission Control
feature. The CAC limit can be set in the range 10-15 for 802.11b and 25-40
for 802.11g. This ensures that the remainder of the bandwidth is used for
the data devices. This data was obtained by using real G.711 phones and
quality measurement tools to measure the call quality when the devices are
in call. Assumption has made Since Nokia also supports SIP G.711, the
call scaling numbers should be the same for scalability.
Avaya has not yet verified above voip performance statistics.
Source: Aruba
©2006 Avaya Inc. All Rights Reserved.
Page 12 of 41
avaya.com
13
Dual-Mode Test Configuration
©2006 Avaya Inc. All Rights Reserved.
avaya.com
14
10. WiFi System Settings for VoIP Dual-Mode
The following section describes the settings as recommended by Aruba. For
details on configuring the various parameters, refer to the Aruba user
guides.
¾ General WiFi Settings
All the WiFi settings, unless otherwise specified, are made at the AP
configuration level on the Aruba system.
1. SSID
The Aruba system supports all SSID formats as per the standards.
2. Data Rates (Default setting)
Recommended Setting
Basic Rates
Transmit Rates
1, 2
1,2,5,11,6,9,12,18,24,36,48,54
3. DTIM (power save settings)
The power save mode helps the WiFi devices conserve battery life. On the
controller, set the DTIM value to recommended setting from Nokia
(Comment: In the absence of a recommended setting for the handset use the
DTIM value to 3).
Optionally, the extended battery feature of the Aruba System can be used to
extend the battery life. For this to work, set DTIM to 100 and enable the
extended battery life feature (see 9 Miscellaneous -> Extended Battery Life)
Recommended Setting
DTIM = 3 (if no recommendations from voice vendor)
DTIM = 100 when testing extended battery life feature.
4. RTS threshold (Default Settings)
Recommended Setting
Leave as default (2333)
5. Antenna Diversity
Recommended Setting
Leave as default
When changing this value please contact the Aruba team for additional
information.
©2006 Avaya Inc. All Rights Reserved.
avaya.com
15
6. Band Preference
When using with the Nokia handsets
- Set the band to 802.11b/g for the dual mode single radio APs (AP61 /
AP60 / AP41). Enable the radios.
- set the 802.11b/g radio to enable and in ap-mode for the dual mode APs
(AP65 / AP70)
Recommended Setting
Set the band to 802.11 b/g and ensure that both b and g data rates are
supported by the infrastructure.
7. RF Management / Channel and power settings (ARM)
The Aruba recommended setting for Channel and Power settings is to allow
Aruba’s Adaptive Radio Management to choose the right power and channel
values. Enable ARM at the AP level for all the APs (can be enabled at the
global level under location 0.0.0).
Recommended Settings
Enable ARM assignment and set value to single band
Enable ARM scanning
Enable VoIP aware Scan
8. Call Admission Control
Advanced Call Admissions Control is a feature unique to Aruba that prevents
any single AP from becoming overly congested with voice calls. While
most WLAN implementations solve congestion problems by relying on wellbehaved clients that understand AP load advertised in beacons, or
proprietary methods that only work with one vendor’s clients, Aruba has a
simple, accurate solution. Since Voice Flow Classification gives the
firewall knowledge of which clients have active voice calls, ArubaOS allows
direct control of the upper limit of calls per AP. Once that threshold is
reached, other idle voice devices in that cell are load-balanced to adjacent
cells, avoiding disruption of calls in progress.
The 802.11e standard includes TSpec signaling, which will be used by
future voice clients to accomplish bandwidth reservation and assured CAC.
Aruba supports the TSpec signaling protocol as an additional input to the
Advanced CAC feature, but as it may be some years before it is widely
©2006 Avaya Inc. All Rights Reserved.
avaya.com
16
implemented on clients, Advanced CAC functionality will be required for the
foreseeable future.
Recommended Settings
Enable VoIP Call Admission Control (default is disable)
Enable VoIP Active Load Balancing (default is disable)
Enable VoIP CAC Drop SIP Invite
(default is disable)
Enable VoIP CAC Disconnect Extra Call (default is disable)
Set VoIP SIP Call Capacity to 10-15 for 802.11b and 25-40 for 802.11g
Set VoIP Call Handoff Reservation 20
(in % of the Call Capacity for
roaming clients, set to default)
Set VoIP High-capacity Threshold 20 (in % of the Call Capacity for sticky
clients, set to default)
9. Miscellaneous
-
Extended Battery
This feature helps improve the battery life for the handsets. With this
feature enabled, handsets can sleep for very long durations (100 – 200
DTIM periods)
Recommended Settings
Set Battery-Boost to enable (CLI support only, AP location sub command)
-
Proxy-arp
Proxy-arp allows the controller to respond on behalf of the WiFi clients
limiting the multicast traffic in the air. This allows the clients to sleep
longer extending the battery life.
Recommended Settings
firewall voip-proxy-arp enable (CLI support only, command available under
the config mode)
-
Local probe response
Enable local probe response feature on the controller for the voice or
converged data SSID if and only if load balancing is disabled.
©2006 Avaya Inc. All Rights Reserved.
avaya.com
17
11. WiFi Security Settings
Aruba strongly recommends using unique SSIDs for secure and insecure
profiles. For example- the same SSID can be configured to support 802.1x
and 802.11i but not open and shared keys. Aruba does not recommend
using a single SSID with both open and static key encryption settings.
-
Open
Supported on the Aruba System but not recommended. Highly insecure.
-
WEP
Supported. Static WEP keys are not recommended as they are also highly
insecure. (Wireless data can be captured and decrypted)
Dynamic WEP or 802.1x is supported.
-
WPA-TKIP-PSK
WPA-PSK is higher level of encryption than WEP and is recommended if the
device cannot support 802.1x or 802.11i. This mechanism is also
recommended if the Voice device does not support good roaming times for
802.1x or 802.11i.
When configuring the SSID via the WebUI, select Mixed TKIP/AES-CCM (if
TKIP is used), and the PSK TKIP/AES-CCM option.
Configure the PSK Passphrase key.
©2006 Avaya Inc. All Rights Reserved.
avaya.com
18
-
WPA2-AES-PSK
Recommended. In case pre-shared keys have to be used or in the absence
of an authentication server, this is the most recommended static-key option.
When configuring the SSID via the WebUI, select the AES-CCM option and
then select the PSK AES-CCM option.
-
WPA2 PEAP 802.11i
Highly recommended. This method required the use of an Authentication
server. In the absence of an auth server in the network please revert back
to WPA/WA2 pre shared keys.
To configure 802.1x or 802.11i
WiFi settings
Set the encryption to AES-CCM (if AES is used) and Mixed TKIP/AES-CCM if
TKIP is used. Set the mixed AES-CCM setting to WPA/2 TKIP/AES-CCM.
Apply the changes.
Authentication
Enable 802.1x, Configure the radius server and the role derivation policies.
Refer to the Aruba guide for information on configuring802.1x and 802.11i.
When using 802.1x and 802.11i please disable Opportunistic Key Caching
on the Aruba infrastructure if the client does not support it.
Also ensure that the Enable Termination radio button in unchecked if the
EAP offload feature on the Aruba system is not used.
Avaya has not yet verified above 802.1x configuration.
Avaya uses Microsoft IAS server as its standard RADIUS solution.
st
nd
Recommended Setting: 1 choice: WPA2-AES-PSK , 2 choice: WPA-TKIPPSK
Note: When using 802.11i and 802.1x, in extreme cases the client may experience a
small space when on call as the client roams form one AP to another. This is because the
client authentication needs to occur every time the client moves across the APs and during
the re-key interval. The re-key interval on the Aruba platform is configurable and should be
set to large values for voice clients
©2006 Avaya Inc. All Rights Reserved.
avaya.com
19
12. Security Firewall Settings and QoS
On the Aruba system users are identified by Roles. The roles are derived
based on user authentication and define the access rights of the users. A
group of users with similar access rights can be assigned the same role
provided that their authentication mechanisms and security enforced on
these users are the same.
Ensure that the user role assigned to the handsets supports sip
communication to and from the network. Ensure that the ACL “any any svcsip-udp any permit queue high” and “svc-sip-tcp permit queue high” are
part of the access rights of the user-role. The E-series set support both
SIP/UDP and SIP/TCP and configurable on the set.
To enable QoS ensure that the CoS and TS bits are set on the controller for
the traffic streams.
Alternatively, the pre-voice ACL can be edited to include the ToS and CoS
bits and added to the handset user’s access rights.
Avaya has not yet verified above configuration.
©2006 Avaya Inc. All Rights Reserved.
avaya.com
20
13. WiFi Multi-Media (WMM) Basic Support
¾ QoS (802.11e) Parameters to Optimize Voice
Aruba supports the default QoS settings as per the WMM standard. To
enable WMM in a 3.0 and above image, check the WMM enable radio
button under the RF profile for the WiFi settings.
Section 4 through 8 and 10 through13 were provided by Aruba to configure the WLAN
for the Dual Mode Nokia handsets.
14. Avaya one-X Mobile Edition Settings
•
•
Following sections describe the configuration of an Avaya one-X mobile
edition and phone settings.
Detailed information and configuration steps are in the installation &
configuration guide and can be found at
http://support.avaya.com/japple/css/japple?PAGE=ProductArea&temp.produc
tID=251422&temp.bucketID=160257
Tasks
1. Complete CM and SES administration
2. Configure WLAN Access Point Profile on the device
3. DO NOT CONFIGURE SIP PROFILE USING S60/Nokia Settings
4. Check WLAN connectivity to see if you can establish connection
5. Install one-X Mobile Edition Software
6. Install one-X Mobile Edition configuration file with SIP profile settings
7. Complete the on-device configuration of the SIP profile (manually need
to map AP with SIP profile)
©2006 Avaya Inc. All Rights Reserved.
avaya.com
21
15. VoIP Settings
¾
Nokia phone Administration
Following is the set of instructions that will help you to administer the
Wireless LAN profile and SIP profile settings, which is necessary for this
dual-mode experience.
It is highly recommend to configure the WLAN Access Point settings
first prior to installing/configuring the Avaya one-X mobile Edition
client.
¾
Create and configure your WLAN Access Point Profile
1. Press Menu button on the phone
2. Navigate to Tools->Settings->Connection->Access Points
3. Select Options->New access point->Use default settings
4. Enter a unique Connection Name
5. Select Wireless LAN for Data bearer
©2006 Avaya Inc. All Rights Reserved.
avaya.com
22
6. Enter your unique ‘WLAN netw. Name’
Recommendation: Search for netw. (If SSID is not hidden)
7. Set your Network status to Public or Hidden
Select Hidden if the network you are connecting to is hidden, or public
if it is not hidden.
8. Set your WLAN netw. Mode to Infrastructure
©2006 Avaya Inc. All Rights Reserved.
avaya.com
23
9. Set your WLAN security mode based on your security infrastructure
¾ Following Section will provide necessary steps to configure WPA2
using 802.1x authentication.
Similar steps will also be used for the E60 and E70.
•
First step is to download the trusted root certificate (e.g. ATA_CA_Cert.cer).
•
Using the Nokia Phone Browser move that file over to the E61.
●
Open the file using the File Mgr. Application (Located under
Office/Documents from the Main Menu)
©2006 Avaya Inc. All Rights Reserved.
avaya.com
24
● When you open the file it will give you an option to save, select OK.
● Make sure the subject and Issuer source is from Trusted
(e.g. Avaya Trusted Authentication).
● Select “Save”
©2006 Avaya Inc. All Rights Reserved.
Authentication
avaya.com
25
● Choose appropriate certificate uses
●
Following section describes the steps how to configure access point with
WPA2/802.1x mode on the E-61.
o Push the Menu Button
o Select Tools
o Select Settings
o Select Connection
o Select Access Points
o Push the Options Button
o Select “New Access Point”
o Select “Use default settings”
o In “Connection” Name Put something meaningful (i.e. Labtest)
o In “Data Bearer” Choose Wireless LAN
o In “WLAN netw. Name” put the ssid (e.g. [email protected])
©2006 Avaya Inc. All Rights Reserved.
avaya.com
26
o In “Network status” choose Hidden
Select Hidden if the network you are connecting to is hidden, or
public if it is not hidden
o In “WLAN netw. Mode” choose Infrastructure
o In “WLAN security mode” choose WPA/WPA2
o In “Homepage” put a valid home page if you want to.
o Select “WLAN security sett.”
ƒ In “WPA mode” choose EAP
ƒ In “TKIP encryption” choose Not allowed.
©2006 Avaya Inc. All Rights Reserved.
avaya.com
27
ƒ
Choose “EAP plug-in settings”
ƒ
ƒ
Disable everything except EAP-PEAP
Highlight EAP-PEAP
ƒ
ƒ
Push Options
Select configure
©2006 Avaya Inc. All Rights Reserved.
avaya.com
28
ƒ
ƒ
Leave “User certificate” at (not defined)
In “CA certificate” scroll to and select the “appropriate
Authentication” certificate (e.g. Avaya Trusted
Authentication).
ƒ
ƒ
In “User name in use” choose User-defined
In “User name” put in the valid ID (just the ID nothing
else, i.e. smith5)
©2006 Avaya Inc. All Rights Reserved.
avaya.com
29
ƒ
ƒ
In “Realm in use” choose User-configure
In “Realm” leave this field blank
ƒ
ƒ
ƒ
In Allow “PEAPv0” leave it yes
In Allow “PEAPv1” leave it yes
In Allow “PEAPv2” leave it no
©2006 Avaya Inc. All Rights Reserved.
avaya.com
30
ƒ
ƒ
ƒ
Scroll to the left for the EAP Tab
Disable everything except “EAP-MSCHAPv2”
Highlight “EAP-MSCHAPv2”
ƒ
ƒ
Push Options
Scroll to Configure and select it
©2006 Avaya Inc. All Rights Reserved.
avaya.com
31
ƒ
ƒ
ƒ
In “User name” put in the valid ID (just the ID nothing
else, i.e. smith5)
In “Prompt password” Choose No
In “Password” put in the valid password
ƒ
ƒ
ƒ
ƒ
Select Back
Select Back
Select Back
Select Back
o Select Options
o Scroll to and select Advanced Settings
©2006 Avaya Inc. All Rights Reserved.
avaya.com
32
ƒ
ƒ
ƒ
In “Proxy serv. Address” put in a valid proxy server (i.e.
ava.proxy.avaya.com)
In “Proxy port number” (i.e. 5000)
Select Back
o Select Back
¾ Following is an example of configuring WPA/WPA2 PSK security option
● In “WLAN security mode” choose WPA/WPA2
● Now enter your WLAN security sett.
©2006 Avaya Inc. All Rights Reserved.
avaya.com
33
● Set WPA mode to “Pre-shared key”
● Set your Pre-shared key
● Leave TKIP encryption as “Allowed”
©2006 Avaya Inc. All Rights Reserved.
avaya.com
34
10. Enter HTTP proxy settings by selecting the left softkey,
Options->Advanced Settings menu
11. Here define your HTTP proxy settings (only needed for browsing web on Eseries devices, if one is required)
12. If you would like to enter a static IP address and/or HTTP proxy settings,
then select the left softkey, Options->Advanced Settings menu
13. Here you can define a static IP address (if you do not have a DHCP server)
and also define your HTTP proxy settings (only needed for browsing web
on E-series devices, if one is required).
©2006 Avaya Inc. All Rights Reserved.
avaya.com
35
14. Select ‘Back’ to save and close the profile
15. Select ‘Back’ again
16. Select ‘Back’ again
17. Navigate to ‘Wireless LAN settings’
18. Change ‘Show availability’ setting to “Yes”
19. Change ‘Scan for networks’ to either “Every minute” or “Every 5
minutes” or less. This helps when moving back in to the WLAN coverage.
©2006 Avaya Inc. All Rights Reserved.
avaya.com
36
16.
Create and configure SIP Profile
Do not create the SIP profile using Nokia Settings. Avaya one-X mobile
client is not aware of any SIP profiles created via Nokia Settings.
Please create SIP profiles using the Avaya one-X mobile client only
NOTE: If you have already included SIP Profile Settings in the
“settings.1xme” file and have installed the configuration file using this
guide, then you may skip this step.
1.
Launch the Avaya one-X Mobile Edition application
2.
Press Menu->Settings->Options->Wi-Fi (tab)->Menu->Create New
Profile
3.
Enter a unique name for the profile (For Example: My SIP Proxy)
4.
Open the Options menu and select Edit
Profile name:
A Unique profile
Service profile:
IETF
Default access
point:
your Wi-Fi access point
Public user
name:
Use
compression:
sip: SIP user @domain or IP address (currently only
numeric user name is supported; for example
[email protected])
No
Registration:
Always on (This setting is highly recommended to set as
Always on, or else your SIP profile will not be
automatically registered)
Use security:
No
©2006 Avaya Inc. All Rights Reserved.
avaya.com
37
Proxy server:
Proxy server address: IP address of your SES server
Realm:
domain (or realm of your SES server)
User name:
SIP user
Password:
Password
Allow loose routing:
Yes
Transport type:
UDP
Port:
5060
Registrar server:
Registrar serv.addr.: IP address of your SES server
Realm:
domain (or realm of your SES server)
User name:
SIP user
Password:
Password
Transport type:
UDP
Port:
5060
The following step is quite necessary as well, if you do not create a profile in “Internet tel.
Settings”, you may get associated to the Access Point, but it will not register your device with
a SIP server.
Navigate to Tools->Settings->Connection->Internet tel. settings: and create a New profile in the
Options menu with the following settings:
Name:
Default (or whatever you want to call it…)
SIP profiles:
previously defined profile
[NOTE: The SIP profile that you set here needs to be the one that was
created using Avaya one-X mobile Edition and make sure that it is also
the default profile in Avaya one-X mobile Wi-Fi settings.]
©2006 Avaya Inc. All Rights Reserved.
avaya.com
38
The following step is necessary so that you are notified of all the
incoming SIP calls effectively.
To switch between normal GSM calls or VOIP calls, navigate to
Tools->Settings->Call->Default call type.
¾ Select Activated for ‘Internet call waiting’
¾ Select On for ‘Internet call alert’
¾ Select Internet for ‘Default call type’.
17. Setting different dual-mode network modes:
You can set different modes in the Avaya one-X mobile Edition client so that
it manages handover scenarios and network appropriately.
1. Launch Avaya one-X Mobile Edition application
2. Press Menu->Settings->Options->General (tab)
3. Scroll to get to the ‘Mode’ setting
18. Dual-Mode Assisted Handover
This product allows you to switch between GSM and Wi-Fi modes. That is,
when you are in Wi-Fi/SIP coverage, you can make and receive incoming
and outgoing calls using WLAN bearer instead of using your cellular (GSM)
minutes. Moreover, if you are leaving the Wi-Fi coverage, you can handoff
the active call to the GSM (cellular) bearer. The software will present a
user with a handover notification dialog box similar to one below with an
audio beep tone:
©2006 Avaya Inc. All Rights Reserved.
avaya.com
39
So it’s up to the user to decide to handover the call from Wi-Fi to GSM or
GSM to Wi-Fi.
NOTE: You may also initiate the handover from by pressing the
Menu->Handover to GSM (or Wi-Fi) option.
©2006 Avaya Inc. All Rights Reserved.
avaya.com
40
20. References
1. SIP Enablement Services (SES), R3.1 Implementation Guide, 16-300140
Issue 3.0, February 2006
http://support.avaya.com/japple/css/japple?temp.documentID=285404&tem
p.productID=160073&temp.releaseID=283912&temp.bucketID=160257&P
AGE=Document
2. Communication Manager: Administration and System Programming
https://support.avaya.com/japple/css/japple?temp.documentID=232041&te
mp.productID=136527&temp.releaseID=282185&temp.bucketID=159898&
PAGE=Document
3.
Avaya Extension to Cellular User’s Guide
https://support.avaya.com/japple/css/japple?temp.documentID=282562&te
mp.productID=136527&temp.releaseID=282185&temp.bucketID=160257&
PAGE=Document
4. Feature Description and Implementation for Avaya Communication Manager
http://support.avaya.com/japple/css/japple?temp.documentID=282739&tem
p.productID=107622&temp.releaseID=287624&temp.bucketID=159898&P
AGE=Document
5. Aruba references and white papers
http://arubanetworks.com/solutions/mobility/
6. Nokia E-series Phone Support
http://europe.nokia.com/A4143002
©2006 Avaya Inc. All Rights Reserved.
avaya.com
41
©2006 Avaya Inc. All Rights Reserved.
Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified
by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc.
All other trademarks are the property of their respective owners. The information
provided in these Application Notes is subject to change without notice. The
configurations, technical data, and recommendations provided in these
Application Notes are believed to be accurate and dependable, but are presented
without express or implied warranty. Users are responsible for their application
of any products specified in these Application Notes.
©2006 Avaya Inc. All Rights Reserved.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement