All rights reserved under the International and
pan-American copyright Conventions.
No part of this manual, or the software
described herein, may be reproduced or
transmitted in any form or by any means, or
translated into another language or format, in
whole or in part, without the express written
permission of Polycom, Inc.
Do not remove (or allow any third party to
remove) any product identification, copyright or
other notices.
Every effort has been made to ensure that the
information in this document is accurate.
Polycom, Inc. is not responsible for printing or
clerical errors. Information in this document is
subject to change without notice and does not
represent a commitment on the part of Polycom,
Inc.
Notice
Polycom, Inc. has prepared this document for
use by Polycom personnel and customers. The
drawings and specifications contained herein
are the property of Polycom and shall be neither
reproduced in whole or in part without the prior
written approval of Polycom, nor be implied to
grant any license to make, use, or sell equipment
manufactured in accordance herewith.
Polycom reserves the right to make changes in
specifications and other information contained
in this document without prior notice, and the
reader should in all cases consult Polycom to
determine whether any such changes have been
made.
NO REPRESENTATION OR OTHER
AFFIRMATION OF FACT CONTAINED IN
THIS DOCUMENT INCLUDING BUT NOT
LIMITED TO STATEMENTS REGARDING
CAPACITY, RESPONSE-TIME
PERFORMANCE, SUITABILITY FOR USE, OR
PERFORMANCE OF PRODUCTS DESCRIBED
HEREIN SHALL BE DEEMED TO BE A
WARRANTY BY POLYCOM FOR ANY
PURPOSE, OR GIVE RISE TO ANY LIABILITY
OF POLYCOM WHATSOEVER.
Contact Information
Please contact your Polycom Authorized
Reseller for assistance.
Polycom, Inc.
4750 Willow Road,
Pleasanton, CA 94588
http://www.polycom.com
2 PN: 1725-36038-001-M.doc
About this Guide
This document explains how to configure and maintain the
SpectraLink 8020/8030 Wireless Telephones using Session Initiation
Protocol (SIP).
Polycom Model Numbers
This document covers the following registered model numbers:
802X, 803X
Related Documents
SpectraLink 8020/8030 Wireless Telephone and Accessories User Guide for
SIP (1725-36165-001)
SpectraLink 8000 SVP Server: Administration Guide for SIP
(1725-36033-001)
SpectraLink 8020/8030 Wireless Telephone: SIP User Agent: Features and
Standards (1725-36037-001)
Index ................................................................................... 147
PN: 1725-36038-001-M.doc 9
1
SpectraLink 8020/8030
Wireless Telephone Overview
The SpectraLink 8020/8030 Wireless Telephones is a Wi-Fi handset
for workplace telephone systems. The handsets operate over a VIEW
Certified 802.11a/b/g/n wireless LAN (WLAN) providing users a
wireless extension of the SIP call server. By seamlessly integrating
into a SIP environment, wireless telephone users are provided with
high-quality mobile voice communications throughout the workplace,
giving users the freedom to roam throughout the workplace while
providing all the features and functionality of a wired SIP desk
phone.
In the SIP environment, the handsets support up to three SIP call
servers. Each handset may have five line appearances and two calls
per line. Each handset may have up to 10 sets of credentials to
identify itself by current user.
The latest wireless telephone and Handset Administration Tool
software versions are required to support the features described in
this document. See Chapter 3 Software License and Protocol Management.
WLAN Quality of Service
WLAN Quality of Service (QoS) is provided by using one of three
available mechanisms: SpectraLink Voice Priority (SVP), Wi-Fi Standard
QoS, or Cisco Compatible Extensions (CCX) version 4. These QoS
modes can not be mixed within the same WLAN; therefore, all Wireless
Telephones on the network must have the same QoS setting.
SVP
SpectraLink Voice Priority (SVP) is a proprietary method of WLAN
QoS, developed by Polycom, to ensure enterprise-grade voice quality,
battery life and call capacity for SpectraLink Wireless Telephones.
PN: 1725-36038-001-M.doc 11
SpectraLink 8020/8030 Wireless Telephone: Administration Guide for SIP
SVP requires the use of the SVP Server, which is an Ethernet LAN
device that works with in conjunction with Wi-Fi APs to ensure QoS
over the WLAN. Voice packets to and from the Wireless Telephones
are tunneled through the SVP Server to ensure voice prioritization as
they are routed between the handset and SIP call server. See the
SpectraLink SVP Server: Administration Guide within IP Environments
document for detailed information about this device.
Wi-Fi Standard QoS
SpectraLink Wireless Telephones support WMM, WMM Power Save
and WMM Admission Control - all QoS standards from the Wi-Fi
Alliance based on IEEE 802.11e. The combination of these three
standards provides enterprise-class QoS in terms of voice quality,
battery life and call capacity. The WLAN must also support and
enable each of these QoS mechanisms in order to ensure they are
utilized. This option does not require the SVP Server.
CCXv4
The CCX program requires WLAN client devices operating on Cisco
APs to use a defined set of industry standards and Cisco-specific
features. The SpectraLink 8020/8030 Wireless Telephone has been
certified by Cisco as CCXv4 compliant. When the CCXv4 operating
mode is selected on the handset, it automatically initiates the required
set of Cisco-specific and industry standard QoS mechanisms. This
option does not require the SVP Server.
WLAN Security
The following security methods are supported by the handset.
WPA2 Enterprise
The handset supports WPA2 Enterprise, as defined by the Wi-Fi
Alliance. WPA2, which is based on the 802.11i standard, provides
government-grade security by implementing the Advanced
Encryption Standard (AES) encryption algorithm. The Enterprise
version of WPA2 uses 802.1X authentication, which is a port-based
network access control mechanism using dynamic encryption keys to
protect data privacy. Two 802.1X authentication methods are
supported on the Wireless Telephone, EAP-FAST and
12 PN: 1725-36038-001-M.doc
SpectraLink Wireless Telephone Overview
PEAPv0/MSCHAPv2. Both of these methods require a RADIUS
authentication server to be available on the network and accessible to
the phone. See the System Components section for tested models.
Additional details are provided in Chapter 3
Normal 802.1X authentication requires the client to renegotiate its key
with the authentication server on every AP handoff, which is a timeconsuming process that negatively affects time-sensitive applications
such as voice. Fast AP handoff methods allow for the part of the key
derived from the server to be cached in the wireless network, thereby
shortening the time to renegotiate a secure handoff. The Wireless
Telephone supports two fast AP handoff techniques, Cisco Client Key
Management (CCKM) (only available on Cisco APs) or Opportunistic
Key Caching (OKC). One of these methods must be configured for
support on the WLAN to ensure proper performance of the handset.
WPA and WPA2 Personal
The handset supports WPA and WPA2 Personal, as defined by the
Wi-Fi Alliance. WPA2, which is based on the 802.11i standard,
provides government-grade security by implementing the Advanced
Encryption Standard (AES) encryption algorithm. WPA, which is
based on a draft version of the 802.11i standard before it was ratified,
uses Temporal Key Integrity Protocol (TKIP) encryption. The Personal
version uses an authentication technique called WPA2 is based on the
802.11i standard. Pre-Shared Key (PSK) allows the use of manually
entered keys or passwords to initiate WPA security.
Cisco Fast Secure Roaming
Cisco’s Fast Secure Roaming (FSR) mechanism uses a combination of
standards-based and proprietary security components including
Cisco Client Key Management (CCKM), LEAP authentication,
Michael message integrity check (MIC) and Temporal Key Integrity
Protocol (TKIP). FSR provides strong security measures for
authentication, privacy and data integrity along with fast AP handoff
on Cisco APs.
WEP
The handset supports Wired Equivalent Privacy (WEP) with both 40bit and 128-bit encryption.
PN: 1725-36038-001-M.doc 13
SpectraLink 8020/8030 Wireless Telephone: Administration Guide for SIP
Minimum System Requirements
•
A wireless LAN must be properly configured and operational
through the use of 802.11a/b/g/n wireless APs. Consult the
VIEW Configuration Guide for the appropriate make/model of
WLAN.
•
A TFTP must be available on the network in order to load the
appropriate software into the handsets. The current handset
software must be installed in the proper TFTP download
directory.
•
If SVP is used for QoS, the SVP Server must be installed and
properly configured.
•
Software versions required, if SVP and/or OAI are used:
Component Version
SpectraLink 8000 SVP Server 17x.034 or higher
OAI Server MOG 600 54.032 or higher
OAI Server MOG 700 82.019 or higher
•
If Wi-Fi Standard QoS is used, then each AP must be configured
for such features as WMM-Power Save; WMM-Admission
Control; proper EDCA parameters; DSCP mapping for voice and
control traffic; call admission control and Proxy ARP. Consult the
appropriate VIEW Configuration Guide for these settings.
•
If WPA2-Enterprise is used, then all portions of the Public Key
Infrastructure (PKI) need to be installed and configured properly
in order acquire the network.
•
An approved SIP call server must be installed and operational on
the LAN. A complete list of approved product can be found on
the Polycom website at
The following diagram shows the Polycom components residing on a
network with APs and wireless LAN Ethernet Switch.
SpectraLink Wireless Telephone Overview
PN: 1725-36038-001-M.doc 15
SpectraLink 8020/8030 Wireless Telephone: Administration Guide for SIP
System Components
SpectraLink 8020/8030 Wireless Telephone
The SpectraLink 8020 Wireless Telephone is a lightweight, durable
handset specifically designed for mobile workplace use. The SpectraLink
8030 Wireless Telephone has the same features and function, but in a
more durable design with and includes push-to-talk capability.
Like a wired desk phone, the handset can receive calls directly, receive
transferred calls, transfer calls to other extensions, and make outside and
long distance calls. The Wireless Telephones can only be used onpremises within the WLAN coverage area with the local SIP call server.
SpectraLink 8000 SVP Server (required when using
SVP)
As described earlier, the SVP Server is a Polycom wired LAN device
that is required when using SpectraLink Voice Priority for QoS.
Access points
Enterprise-grade Wi-Fi access points provide the connection between
the wired LAN and the wireless LAN. VIEW Certified 802.11a/b/g/n
APs must be positioned in all areas where Wireless Telephones will
be used to ensure seamless radio coverage. The number, type and
placement of access points will affect the coverage area and capacity
of the wireless system. Careful planning of the WLAN is necessary to
ensure good voice quality. See the Best Practices Guide for Deploying SpectraLink 8020/8030 Wireless Telephones for additional guidance.
APs must be properly configured to support the corresponding QoS
and security methods selected for the handset.
Ethernet switch
One or more Ethernet switches interconnect multiple network
devices, including the SpectraLink 8000 SVP Server (if used for QoS),
the proxy server(s), wired IP phones, TFTP Server, RADIUS
authentication server (if using WPA2 Enterprise) and WLAN access
points. Enterprise Ethernet switches provide the highest performance
16 PN: 1725-36038-001-M.doc
SpectraLink Wireless Telephone Overview
networks, which can handle combined voice and data traffic, and are
required when using the SpectraLink 8020/8030 Wireless Telephones.
Although a single Ethernet switch network is recommended, the
handsets and the SpectraLink 8000 SVP Server can operate in larger,
more complex networks, including networks with multiple Ethernet
switches, routers, VLANs and/or multiple subnets, as long as the SVP
Server and access points and handsets are on the same subnet.
However, in such networks, it is possible for the quality of service
(QoS) features of the SVP Server to be compromised, and
consequently voice quality may suffer. Any network that consists of
more than a single Ethernet switch should be thoroughly tested to
ensure any quality issues are addressed. See the Best Practices Guide for Deploying SpectraLink 8020/8030 Wireless Telephones for additional
guidance.
SpectraLink 8020/8030 Wireless Telephones cannot roam with
uninterrupted service between subnets unless specific LAN
components are present. Certain AP/Ethernet switch combinations
establish a Layer-2 tunnel across subnets that enable the handsets to
roam. Without this capability, any call in progress will be dropped
when the user moves out of range and the handset must be power
cycled in order to resume functionality in the new subnet area.
Ensure that all your APs are attached to the same subnet for proper
operation. The handset can change subnets if DHCP is enabled and
the handset is powered off then back on when within range of APs on
the new subnet. Note that the wireless telephones cannot “roam”
across subnets, since they cannot change IP addresses while
operational.
SIP server
The SIP server is a component from a third-party vendor that
provides access to telephony services. The handsets can recognize up
to three distinct SIP servers in a single system.
The handsets can operate with SIP proxy servers such as SER (SIP
Extensible Router) or with SIP Back-to-Back User Agents (B2BUA) –
the most common form of SIP server for PBX-based systems. In this
case the IP address location services provided by the SIP server are
not available, so direct IP address dialing must be used.
The SIP proxy server connects to another device such as a PBX or
gateway and from there, other wired phones and the PSTN.
PN: 1725-36038-001-M.doc 17
SpectraLink 8020/8030 Wireless Telephone: Administration Guide for SIP
TFTP (Trivial File Transfer Protocol) server
A TFTP server is required in the system to distribute software to the
handsets. It may be on a different subnet than the APs and/or
handsets.
SIP TFTP server
The SIP TFTP server is required in the system to deliver SIP
configuration parameters to the SIP handset whenever a SIP handset
is powered-up. The location of the SIP TFTP server is separately
specified in SIP handset administration parameters (See Chapter 2
SpectraLink 8020/8030 Wireless Telephone Configuration, section The
Admin Menu.) Normally, the SIP TFTP server is the same as the
network TFTP server, see above.
NTP (Network Time Protocol) Server
If WPA2 Enterprise security is used, the handset will confirm the
PEAP certificate has a valid date and time with the NTP Server on the
network, if one is available. If an NTP Server is not available, the
certificate will be assumed valid and operate accordingly.
Authentication Server (if using WPA2 Enterprise)
A RADIUS authentication server must be used to provide
username/password-based authentication using RSA certificates for
PEAPv0/MSCHAPv2 or PAC files for EAP-FAST.
The following authentication servers have been validated for use with
R3.0:
Microsoft Internet Security and Acceleration (ISA) Server 2003
•
Cisco Secure Access Control Server (ACS), v4.1
•
FreeRADIUS v2.0.1 and 1.1.7
Other RADIUS servers may work properly with SpectraLink
handsets, but have not been tested. Inquiries on untested servers will
receive limited, “Best Effort”, support.
The SpectraLink 8020/8030 Wireless Telephones are compatible with
the G.711µ-law, G.711a-law and G.729 codecs. There is no setting
required on the handset.
DHCP
Dynamic Host Configuration Protocol (DHCP) is a standardized
protocol that enables clients to be dynamically assigned with various
configuration parameters, such as an IP address, subnet mask, default
gateway, and other critical network configuration information. DHCP
servers centrally manage such configuration data, and are configured
by network administrators with settings that are appropriate for a
given network environment. The handset will use the following
DHCP options if DHCP use is enabled:
2
Option Meaning
1 Subnet mask
3 Default gateway
6 DNS server
7 Syslog server logging
15 Domain name
66 TFTP server
151 SpectraLink 8000 SVP Server
152 SpectraLink 8000 OAI Gateway
siaddr Boot server or next server
DNS
Domain Name System (DNS), an industry-standard protocol, locates
computers on an IP-based network. IP networks rely on numberbased addresses to move information on the network. However, it is
easier to remember user-friendly names than number-based
addresses, so it is necessary to translate user-friendly names into
PN: 1725-36038-001-M.doc 23
SpectraLink 8020/8030 Wireless Telephone: Administration Guide for SIP
addresses that the network can recognize. The handset will use DNS
to automatically translate names into IP addresses for the TFTP server
and SpectraLink 8000 SVP Server.
In DHCP mode, the SIP handset will use DNS to look up an address
for the logical name “siptftp” to locate the SIP TFTP file server. If this
logical name is undefined, then the address specified by option 66 or
the boot server/next server (siaddr) field is used for the SIP TFTP
server.
Sample DHCP Server Configuration File
A sample DHCP server configuration file is illustrated below. Please
note that this is only a sample and will not work on your system as
written here. In addition, this file is specific to the ISC DHCP server.
Your configuration files must be locally programmed according to
your site requirements.
dhcpd.cfg
# /etc/dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# Type "man dhcp-options" at prompt to get help for these options.
#
# Global parameters start at beginning of file.
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
# This means the DHCP server will send DHCPNAK messages to misconfigured
# clients.
authoritative;
# Use local address if you want the DHCP server to listen for DHCP requests
# on a specified address, rather than requests send to all addresses.
local-address 192.168.0.1;
# define the DNS server(s) option 6
option domain-name-servers 192.168.0.1;
# define the SYSLOG server option 7
option log-servers 192.168.0.1;
# define the domain name option 15
option domain-name "polycom.com";
# define the SVP server option code 151 as an IP address.
option svp-server code 151 = ip-address;
# define the OAI server option code 152 as an IP address.
24 PN: 1725-36038-001-M.doc
SIP Integration Factors
option oai-server code 152 = ip-address;
# This should be the length in seconds that will be
# assigned to a lease if the client requesting the lease does not ask
# for a specific expiration time. 86400 seconds is 1 day.
default-lease-time 86400;
# This should be the maximum length in seconds that will be assigned
# to a lease.
max-lease-time 86400;
# minimum lease time of 10 minutes
min-lease-time 600;
# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses in the range 192.168.0.100 to 192.168.0.149,
# and all other clients get addresses in the range 192.168.0.150 to
# 192.168.0.199.
class "SpectraLinkPhones" {
match if substring (option vendor-class-identifier, 0, 11) = "SpectraLink";
}
# DHCP lease pool for Polycom SpectraLink phones
pool {
allow members of "SpectraLinkPhones";
range 192.168.0.100 192.168.0.149;
# define the siaddr / next server field as the alternative TFTP server address
next-server 192.168.0.1;
# define the NTP server option 42
option ntp-servers 192.168.0.1;
# define the primary TFTP server address option 66
option tftp-server-name "192.168.0.1";
# define the SVP server address option 151 if using SVP QoS
option svp-server 192.168.0.5; # option 151
# define the OAI server address option 152
option oai-server 192.168.0.6; # option 152
}
# DHCP lease pool for other devices
pool {
deny members of "SpectraLinkPhones";
range 192.168.0.150 192.168.0.199;
next-server 192.168.0.1;
option tftp-server-name "192.168.0.1";
PN: 1725-36038-001-M.doc 25
System Configuration
Each handset may be configured for site-specific requirements by
opening the
information. Any settings entered in the
to system settings. Only the handset being configured is affected by
the
Admin
The wireless telephone user may select several usability options from
the Standby menu, described below in the User-defined Preferences
section. This information is also provided in the end-user manual.
The SpectraLink Handset Administration Tool is a software utility
that enables rapid configuration of handsets by utilizing the USB port
on the Dual Charger. See the Handset Administration Tool (HAT)
document for specific instructions. Please see your service
representative or contact Polycom customer service for more
information about this time-saving tool.
Admin
menu settings.
menu and selecting options or entering specific
Admin
3
menu must conform
When WPA2 Enterprise security is used, PAC files for EAP-FAST can
be provisioned wirelessly or by using the HAT. For PEAP, the HAT
must be used to enroll certificates. See section WPA2 Enterprise PEAP Certification Enrollment and EAP-FAST Manual PAC Provisioning at the
end of this chapter for details.
Other settings that must be configured include, but are not limited to,
WLAN QoS, DSCP tagging, DHCP and regulatory domain
information. If these are not selected by the administrator the handset
will use the default settings.
PN: 1725-36038-001-M.doc 27
SpectraLink 8020/8030 Wireless Telephone: Administration Guide for SIP
Configuration Flow Chart
(Each step is explained in the following pages)
28 PN: 1725-36038-001-M.doc
Configure Call Server
See the documentation which accompanies your call server. Review
the proxy information in this document for configuration
requirements. You will also need to configure an extension and
related information for each handset to be deployed.
Configure Access Points
See the documentation which accompanies your access point. It is
absolutely required that WMM be enabled on the access point.
Polycom VIEW certified access points are listed in the Polycom VIEW Certified Products Guide. Configuration Guides for each certified
product can be found on the Polycom website. See the RelatedDocuments section at the beginning of this document for link
information.
System Configuration
Configure SIP Handset Files
In order for the handset to function in the SIP environment, it
downloads two files from the root directory of the SIP TFTP server
during startup. The first file contains generic system information and
is downloaded by every handset during the power-up sequence. A
second file, unique for each handset, is then downloaded. It contains
specific information for each handset such as username, password,
and line appearances. Both of these files must be written specifically
for the facility where the handsets will operate.
Sample files populated with default parameters are provided with the
software downloaded from the website. We recommend using these
sample files as a starting point and adjusting them according to your
system requirements.
SIP TFTP Server Configuration Files
The two file types, generic and specific, are identical in format. Any or
all of the configuration information can be contained in either file.
Any information in the specific file that conflicts with the information
in the generic file will take precedence over that in the generic file.
PN: 1725-36038-001-M.doc 29
SpectraLink 8020/8030 Wireless Telephone: Administration Guide for SIP
Authentication information will be accepted from both files. For ease
of administration, it is recommended both file types be utilized.
Guidelines
•
The files are in plain text, US-ASCII. The general form of the
configuration file data is “parameter = value.”
•
The generic filename must be SIP_allusers.cfg.
•
Each specific filename must have the form of SIP_username.cfg
where [username] is as assigned to each individual user by the
system administrator. See Chapter 5 Configure Each SpectraLink
8020/8030 Wireless Telephone, section The Admin Menu, subsection
SIP Registration.
•
Username parameters are: alphanumeric, no spaces, no
punctuation, case is ignored, 1-16 characters.
•
Generic file information should contain proxy server information
and other SIP system data.
•
Specific file information should contain data specific to each user
such as authentication credentials and line appearance data.
•
Some parameter lines accept more than one value, separated by a
colon or semicolon character as defined below.
•
Any line that begins with a pound sign (#) is ignored.
•
In general, space characters are ignored. Space characters may be
included in string values by replacing the space with “%20” or by
enclosing the string in quotes (″).
•
If necessary, other special characters may be included by using a
hexadecimal representation: (%hh) where hh is the representation
of the character.
•
Lines may appear in any order although maintenance may be
simplified by preserving the order in the supplied example file.
Program each of the files according to the following instructions.
30 PN: 1725-36038-001-M.doc
Loading...
+ 117 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.