team 1.7 solution overview and planning guide 68009260001-a

Total Enterprise Access and Mobility (TEAM) Solution

© 2009 Motorola, Inc. All rights reserved.

January 2009

TEAM 1.7 Solution Overview and Planning Guide

68009260001-A

*68009260001*

Copyrights

The Motorola products described in this document may include copyrighted Motorola computer programs. Laws in the United States and other countriespreserve for Motorola certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola computer programs contained inthe Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola.

Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under thecopyrights, patents or patent applications of Motorola, except for the normal nonexclusive, royalty-free license to use that arises by operation of law in the saleof a product.

Disclaimer

Please note that certain features, facilities and capabilities described in this document may not be applicable to or licensed for use on a particular system, ormay be dependent upon the characteristics of a particular mobile subscriber unit or configuration of certain parameters. Please refer to your Motorola contactfor further information.

Trademarks

MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of theirrespective owners.

Copyrights

© 2009 Motorola, Inc. All rights reserved.

No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into any language or computer language, in any form or byany means, without the prior written permission of Motorola, Inc.

DocumentHistory

Document History■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Edition Description Date

1st Release Original release of TEAM 1.7 Solution Overview andPlanning Guide

January2009

68009260001-A January 2009 i

Document History

ii 68009260001-A January 2009

Tableof

Contents

Contents■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

TEAM 1.7 System Solution Overview and Planning GuideContacting Motorola’s Enterprise Mobility Support Center . . . . . . . . . . . . . . . . . . . . . . -xvContacting Motorola’s Support Central Website . . . . . . . . . . . . . . . . . . . . . . . . . . . -xviRegulatory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xvi

Device Country Approvals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xviHealth and Safety Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xviiRadio Frequency Interference Requirements - FCC . . . . . . . . . . . . . . . . . . . . . . . -xviiRadio Frequency Interference Requirements - Canada . . . . . . . . . . . . . . . . . . . . . . -xvii

Chapter 1: System OverviewIntroduction to the TEAM Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Voice over IP (VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1WLAN Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Benefits of the TEAM Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Typical Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Terminology Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Architecture and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Introduction to the Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Solution Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Backhaul Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Wireless LAN (WLAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9TEAM smartphone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

NSM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

TEAM Voice Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Telephony Features Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14PTT Feature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

TEAM Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Windows Mobile 6.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Motorola-Specific Applications on the TEAM smartphone . . . . . . . . . . . . . . . . . . 1-16Third-Party Applications on the TEAM smartphone . . . . . . . . . . . . . . . . . . . . . 1-17

Shared Device/Pool Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

Shared Device/Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18Use case example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18A specific example of PBX services associated with the shared devices: . . . . . . . . . . . 1-19

Micro Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

68009260001-A January 2009 iii

Contents

Example Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19Telephone Numbering Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20Telephone Numbering Scheme — Example . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

Standards-Based Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21IEEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

802.11 a/b/g — Bands and Speeds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22Wi-Fi Alliance (WFA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22Wi-Fi Multimedia (WMM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23

WMM-PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23WMM-AC – Admission Control (Future). . . . . . . . . . . . . . . . . . . . . . . . . . 1-23

Session Initiation Protocol (SIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24ITU-T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24

Codecs/Vocoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24

Chapter 2: Theory of OperationsSystem Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

TEAM Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3WSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3NSM Server Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Enterprise Control Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10EAP-TLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11RADIUS (AAA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Network Time Protocol (NTP) Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Motorola Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

PBX (Telephony Servers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Hardware and Software Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14IP-PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17IP to TDM Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Cisco PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Nortel PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Telephony-Related Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Voice Mail Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18CDR Processing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Other Enterprise Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Network Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20Device/System Provisioning/Management . . . . . . . . . . . . . . . . . . . . . . . . . 2-20Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20MS LCS and Others. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Backhaul Network Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

WLAN Equipment (Multiple Vendors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Industry Standard Requirements and Features . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

Minimum AP Requirements for Data Networks . . . . . . . . . . . . . . . . . . . . . . . 2-24Recommended Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25Wireless Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25Layer 2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25Power over Ethernet (PoE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25Policy Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26

iv 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Contents

Motorola Enterprise WLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26

Cisco. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28

WLAN and Backhaul Network Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30TEAM smartphone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32Photo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

VoIP Client — Voice Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34Screenshots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

Quality of Service (QoS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36QoS Mechanisms for the Wireless LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37Packet Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37Access Point/Gateway Bandwidth Reservation . . . . . . . . . . . . . . . . . . . . . . . . . 2-37911 Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38Section 508 Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

IPsec Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38IPsec Between NSM-WSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39IPsec Between WSM-PBX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

Chapter 3: Planning for DeploymentAssessing Your Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Planning for Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Installation Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Initial Site Install/Pre-sale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Compatible Hardware and Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

IP Evaluation and Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Planning the WLAN Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Considerations for the WLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Evaluating the Coverage Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Qualifying an Existing Infrastructure as Voice-Capable . . . . . . . . . . . . . . . . . . . . . 3-6

Quality of Service Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Site Surveys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

General Steps to Conduct a Site Survey. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Placement of Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Roaming Across Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Roaming Across Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Considerations for Deploying 802.11a/b/g . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Backhaul Network Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Local Area Network (LAN) Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15LAN Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Voice Network Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Voice Mail Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17Network Topology Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18Additional Guidelines and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Rack Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18Required Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19Quality of Service Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

68009260001-A January 2009 v

Contents

Overview of QoS Roles by System Component . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

Appendix A: Detailed Features of the TEAM smartphoneTelephony Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Make and Receive Phone Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Direct Inward Dialing Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Direct Outward Dialing Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Call Forwarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Call Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Caller ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Abbreviated Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Conference Calling (Ad Hoc, Meet-Me) . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Voice Mail Indication and Retrieval Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4Voicemail Notification/Message Waiting Indication . . . . . . . . . . . . . . . . . . . . . A-4Message Retrieval and Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

DTMF (Overdial) Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5911. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Call Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6Busy Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

PTT Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7Private Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7Call Alert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8Group Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8PTT Caller ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8Missed PTT Call Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9Talkgroup Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9Presence/Instant Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Data Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9Text Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10Simultaneous Voice and Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11Corporate E-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11Calendar, Phonebook, and Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11Directory Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11Standard Browser Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11Line of Business Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

Call Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

Subscriber States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12Bridged Call Appearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13Call State Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13WLAN Call Hold/Remove Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13WLAN Call Origination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13WLAN Call Toggle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14WLAN Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14WLAN End of Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14WLAN Incoming Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14WLAN Status Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15

Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15

vi 68009260001-A January 2009

Contents

Appendix B: Equipment ChecklistsEnterprise Equipment Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

WLAN Equipment Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Glossary

68009260001-A January 2009 vii

Contents

This page intentionally left blank.

viii 68009260001-A January 2009

Listof

Figures

List of Figures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Figure 1-1: TEAM System Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Figure 1-2: Layered Diagram of the System Architecture. . . . . . . . . . . . . . . . . . . . . . . 1-6Figure 2-1: TEAM – Detailed System Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Figure 2-2: WSM Appliance — Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Figure 2-3: WSM Appliance — Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Figure 2-4: NSM Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Figure 2-5: Front View of the TEAM Smartphone . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Figure 2-6: Menu View on the TEAM Smartphone . . . . . . . . . . . . . . . . . . . . . . . . . 2-34Figure 2-7: View of Callers Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Figure 2-8: View of Active Call Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Figure 2-9: View of Contacts Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36Figure 2-10: View of Call on Hold Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36Figure 3-1: Wireless Design Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Figure 3-2: Roaming Across Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12Figure 3-3: WLAN Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13Figure 3-4: Toll-Quality Voice Delivered through Quality of Service Implementation . . . . . . . . . 3-17Figure 3-5: System Architecture Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20

68009260001-A January 2009 ix

List of Figures


x 68009260001-A January 2009

Listof

Tables

List of Tables■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Table 1-1: Enterprise Control Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Table 1-2: Telephony and Telephony-Related Servers . . . . . . . . . . . . . . . . . . . . . . . . 1-8Table 1-3: WLAN Components Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Table 1-4: NSM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Table 1-5: Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Table 1-6: 802.11 a/b/g — Bands and Speeds . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22Table 1-7: List of Interconnect Vocoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24Table 2-1: AAA Server supported by TEAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Table 2-2: Dialogic Gateway to TDM PBXs Hardware Specifications . . . . . . . . . . . . . . . . . 2-14Table 2-3: Dialogic Gateway to TDM PBXs Software Specifications . . . . . . . . . . . . . . . . . 2-15Table 2-4: TDM PBXs Supported by TEAM Solution Through Dialogic GateWay (DMG2000). . . . . 2-15Table 2-5: Call Features Supported by TDM PBXs . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Table 2-6: IP PBXs Supported Directly by the TEAM Solution . . . . . . . . . . . . . . . . . . . . 2-16Table 2-7: Call Features Supported by TDM PBXs . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Table 2-8: Supported WLAN Vendors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23Table 2-9: Minimum AP Requirements for Data Networks . . . . . . . . . . . . . . . . . . . . . . 2-24Table 2-10: Motorola/Symbol — Access Point Specifications . . . . . . . . . . . . . . . . . . . . 2-27Table 2-11: Motorola/Symbol — PoE Ethernet Switch Specifications . . . . . . . . . . . . . . . . . 2-27Table 2-12: Motorola/Symbol — RF Switches (Validated) . . . . . . . . . . . . . . . . . . . . . . 2-27Table 2-13: Motorola/Symbol RF Switches (not Validated) . . . . . . . . . . . . . . . . . . . . . . 2-28Table 2-14: Cisco — RF Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Table 2-15: Cisco — Access Point Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Table 2-16: TEAM smartphone Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31Table 2-17: Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31Table 2-18: Features of the TEAM smartphone . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32Table 3-1: Compatible Hardware and Software Versions . . . . . . . . . . . . . . . . . . . . . . . 3-4Table 3-2: Minimum Requirements for System Performance . . . . . . . . . . . . . . . . . . . . . 3-10Table 3-3: Frequency Band Challenges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Table 3-4: Overview of QoS Roles by System Component . . . . . . . . . . . . . . . . . . . . . . 3-21Table B-1: Enterprise Server Installation and Configuration Checklist . . . . . . . . . . . . . . . . . B-1Table B-2: WLAN Equipment Installation and Configuration Checklist . . . . . . . . . . . . . . . . B-2

68009260001-A January 2009 xi

List of Tables


xii 68009260001-A January 2009

AboutThis

Booklet

TEAM 1.7 System Solution Overview andPlanning Guide

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

The Total Enterprise & Mobility (TEAM) solution is a Voice over WLAN (VoWLAN) hardwareand software solution that includes a TEAM smartphone combined with enterprise serversoftware. The complete solution provides a product that enables telephony, Push-to-Talk (PTT)capability, data services, and securely managed mobility.

This book is intended for use by Network Engineers and System Designers.

What Is Covered In This Booklet?This book provides an overview of the TEAM solution and planning for deployment.The book contains the following chapters:

• Chapter 1, "System Overview" — This chapter provides an overview of the TEAM solution; ahigh-level description of its system architecture, components, and features.

• Chapter 2, "Theory of Operations" — This chapter provides a descrip-tion of how the system works.

• Chapter 3, "Planning for Deployment" — This chapter provides a descriptionof the system deployment considerations.

• Appendix A, "Detailed Features of the TEAM smartphone" — This appendix providesa detailed description of the features of the TEAM smartphone.

• Appendix B, "Equipment Checklists" — This appendix provides equipment checklists.

68009260001-A January 2009 xiii

About This Booklet

Helpful Background InformationThe Motorola technical training team offers a variety of courses designed to assist in learning about thesystem. Class registration is available at www://edu.symbol.com. The online courses are:

• TEAM product specific technical certification (course number: EDUCEC4000)

• TEAM product specific sales certification (course number: EDUCEC3000)

Instructional Lead courses are :

• TEAM Instructional Lead product technical course (course number: EDUCEC 400)

Related InformationRefer to the following documents for associated information about the system.

Document name PurposeTEAM Solution Installation andConfiguration(68009262001-A)

Describes how to install TEAM hardwareand software. Lists the required and optionalequipment in the system. Provides troubleshootinginformation.

TEAM Solution System AdministrationGuide(68009263001-A)

Describes the day-to-day operational tasks thatneed to be performed in the TEAM solution.

TEAM Solution SubscriberProvisioning Guide(68009261001-A)

Provides information to provision the subscribersand TEAM smartphones of the solution.

xiv 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Contacting Motorola’s Enterprise Mobility Support Center

Document name PurposeEWP1000/2000 Series User’s Guide(6871009P12-A)

Describes the TEAM smartphone hardware(physical device) and software. Includesinformation on how to use the client software toperform daily job functions.

Enterprise WiFi Phone Service Manual(6802983C90-B)

Describes how to troubleshoot the TEAMsmartphone hardware and reset the device. Alsodescribes error messages and provides contactsfor service/support. Covers Installation andSetup/Provisioning.

NSM User Guide(part number 6871009P18-A)

Describes the Network Services Manager (NSM)software that provides a number of servicesfor configuring, monitoring and managing theWireless Services Manager (WSM) in a WLANenvironment.

Contacting Motorola’s Enterprise Mobility Support Center■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

If you have a problem with your equipment, contact Enterprise Mobility support for your region. Contactinformation is available by visiting http://www.motorola.com/customersupport and after selecting your region,click on the Symbol-branded products link under Business Support. This site provides information andonline assistance including developer tools, software downloads, product manuals and online repair requests.

When contacting Enterprise Mobility support, please provide the following information:

• Serial number of the unit. For WSM and NSM software, this is the activationkey that was provided with your software media.

• Model number or product name.

• Software type and version number.

Motorola responds to calls by email, telephone or fax within the time limits set forth in supportagreements. If you purchased your Enterprise Mobility business product from a Motorolabusiness partner, contact that business partner for support.

68009260001-A January 2009 xv

Contacting Motorola’s Support Central Website

Contacting Motorola’s Support Central Website■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Motorola’s Support Central Web site, accessed via the Symbol-branded products link underBusiness Support, provides information and online assistance including developer tools, softwaredownloads, product manuals and online repair requests.

Regulatory Information■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This device (Model Number WSMHW) is approved under the Symbol Technologies brand: SymbolTechnologies, Inc., is the Enterprise Mobility business of Motorola, Inc. (“Motorola”).

All Motorola devices are designed to be compliant with rules and regulations in locationsthey are sold and are labeled as required.

Any changes or modifications to Motorola equipment, not expressly approved by Motorola,could void the user’s authority to operate the equipment.

Device Country ApprovalsRegulatory markings, subject to certification, are applied to the device is approved for usein the following countries: United States and Canada.

Please refer to the Motorola Declaration of Conformity (DoC) for details of other countrymarkings. This is available at http://www2.symbol.com/doc/.

Operation of the device without regulatory approval is illegal.

Select only the country in which you are using the device. Any other selection willmake the operation of this device illegal.

xvi 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Health and Safety Recommendations

Health and Safety Recommendations

Ergonomic Recommendations

In order to avoid or minimize the potential risk of ergonomic injuryfollow the recommendations below. Consult with your local Health &Safety Manager to ensure that you are adhering to your company’ssafety programs to prevent employee injury.

• Reduce or eliminate repetitive motion

• Maintain a natural position

• Reduce or eliminate excessive force

• Keep objects that are used frequently within easy reach

• Perform tasks at correct heights

• Reduce or eliminate vibration

• Reduce or eliminate direct pressure

• Provide adjustable workstations

• Provide adequate clearance

• Provide a suitable working environment

• Improve work procedures.

Radio Frequency Interference Requirements - FCCThis equipment has been tested and found to comply with the limits for a Class A digital device,pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protectionagainst harmful interference when the equipment is operated in commercial environment. Thisequipment generates, uses, and can radiate radio frequency energy and, if not installed and used inaccordance with the instruction manual, may cause harmful interference to radio communications.Operation of this equipment in a residential area is likely to cause harmful interference in whichcase the user will be required to correct the interference at his own expense.

Radio Frequency Interference Requirements - CanadaThis Class A digital apparatus complies with Canadian ICES-003.

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada. 6.

68009260001-A January 2009 xvii

Radio Frequency Interference Requirements - Canada


xviii 68009260001-A January 2009

Chapter

1System Overview

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Total Enterprise Access & Mobility (TEAM) is a cost-competitive wireless TEAM smartphone systemthat delivers voice and data communication services within an Enterprise to on-campus workers. TEAMleverages unlicensed Wi-Fi spectrum, WLAN infrastructure, and existing telephony infrastructureto provide the following voice and data wireless communications services:

• Basic Telephony including several advanced features such as, Call Forwarding and Voicemail.

• Push-To-Talk (PTT) features, such as private and group calls.

• Data features, such as e-mail, Personal Information Manager (PIM), and Messaging.

• Application Flexibility – Windows Mobile 6.1, for access to customerdatabases or Web-based applications.

The TEAM solution is a wireless communication network that facilitates mobile voice and datacommunication using PBX telephony. The solution includes WLAN TEAM smartphones with VoIPalong with server software. The system interfaces with Enterprise communication networks using thelatest telephony and Internet Engineering Task Force (IETF) standards. WLAN Access Points (APs)are installed throughout the Enterprise to provide Radio Frequency (RF) coverage.

The system is installed and optimized by IT professionals with a minimum levelof operator training and expertise.

Introduction to the TEAM Solution■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The TEAM voice mobility solution provides (telephony and PTT) and data (e-mail, Internet, and textmessaging) services. This section provides an overview of some key technologies in the solution,including VoIP and WLAN networks, and explains the benefits of the solution.

Voice over IP (VoIP)A Voice over IP (VoIP) telephony system is built on a single, shared IP-based packet network. Apacket-based network provides the foundation that can carry many types of information, includingdata, audio, and video. The challenge with such a network is separating and prioritizing the various

68009260001-A January 2009 1-1

WLAN Network Chapter 1: System Overview

types of traffic. A VoIP telephony system provides services and reliability comparable to traditionaltelephony systems. This converged network offers cost benefits, as you can install and administer avoice and data network together and use an existing IP network for voice traffic.

Integrating voice and data on one network infrastructure makes it easier to deploy business applications thatbring together voice, data, and video across the Enterprise. When networks are built on industry-standardoperating systems and protocols, rather than on proprietary systems, it becomes simpler and less costlyfor network planners to integrate products from multiple vendors and reuse existing equipment.

The convergence of wireless voice and data networks enables the implementation of voice-enabled WLANs.The TEAM solution combines features and benefits from each network, providing seamless, contiguousvoice and data communication throughout the Enterprise, using the TEAM smartphone.

TEAM, in using VoIP, follows the industry in moving from analog circuit-based legacy PBXsor TDM digital solutions, to IP protocol packet-based solutions, using Quality of Service(QoS) settings to ensure a high-quality subscriber experience.

The TEAM solution can work with TDM digital PBXs through the addition of a TDM gateway to the solution.

WLAN NetworkA WLAN is a wireless network that uses spread-spectrum or Orthogonal Frequency Division Multiplexing(OFDM) modulation technology based on radio waves to enable communication between TEAMsmartphones and laptops within an Enterprise. The TEAM solution utilizes WLAN in InfrastructureMode, in which the TEAM smartphones communicate with Access Points to a wired infrastructure.It gives subscribers the ability to roam within a broad coverage area and still stay connected to thenetwork. The WLAN network has the following infrastructure elements:

• Access points/ports (APs)

• Switching units (AP controllers/also known as Wireless Switching Units)

The APs interface between the wireless medium and a wired infrastructure which in turn is connectedto the wired Enterprise network through wireless switches and/or AP controllers and local switches. TheAPs can (alone, or in conjunction with AP controllers) perform additional functions, such as helpingto encrypt wireless traffic, prioritizing wired network traffic, isolating wireless devices into multiplewireless service sets using Service Set Identifier (SSID), and so on. The existing wired IP infrastructureis used as the transmission medium, which minimizes the cost of operation.

WLAN networks have the following characteristics in the TEAM solution:

• Use common protocols to support TEAM smartphones, 802.11 a/b/g.

• Provide authentication to validate TEAM smartphones and authorization to allowthe TEAM smartphones to use the network.

• Support the roaming of TEAM smartphones throughout the Enterprise.

A key differentiator of the TEAM solution is that the APs use the unicast routing scheme to handlebearer (voice) traffic for PTT calls. With unicast, only those APs that handle the appropriate subnetswhere the TEAM smartphones are associated are illuminated by a PTT call (such as a group call). Othersolutions use multicast, in which Internet Group Management Protocol (IGMP) must be implementedto let the network know where the TEAM smartphone is located. Otherwise, all the APs in thenetwork are illuminated for a call, implying a non-optimized use of RF resources.

1-2 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Benefits of the TEAM Solution

Benefits of the TEAM SolutionThe benefits of the TEAM solution are as follows:

• Reduces communication costs

◦ Leverages existing Enterprise resources, such as the PBX and WLAN.

◦ Initiates calls through the PBX, thereby saving on local call chargesby leveraging Enterprise networks.

◦ Provides Call Detail Recording (CDR) for billing purposes.

• Increases worker collaboration and productivity

◦ Improves employee mobility and accessibility.

• Provides a common user experience and feature transparency.

• Provides unified security and management features.

Typical CustomersThe typical customer for the TEAM solution is always on site and makes constant use of bothvoice and data. These customers have the following requirements:

• Long talk time

• Excellent voice quality

• Secure call setup mechanism

• PSTN access for some subscribers

• Telephony capabilities

• Push-To-Talk (2-way radio)

• Basic messaging

• Line of Business (LOB) applications

Terminology OverviewThe use of common terminology is important to ensure that roles are clearly defined in this manual.The following list provides the correct terminology and some common variations.

• Operator— A person who controls or maintains the system, for example, a systemadministrator. The operator is known by different names, depending on the interface, forexample, the Network Services Manager (NSM) operator includes these roles: WSMProvisioning Client User, Account Administrator, or Site Operator.

• TEAM smartphone— Refers to the physical TEAM smartphone. This TEAM smartphone isalso known as the device, handset, Mobile Station (MS), or Subscriber Unit (SU).

68009260001-A January 2009 1-3

Architecture and Components Chapter 1: System Overview

• Subscriber— A person who uses the TEAM smartphone on the system, thatis, the Enterprise associate. The subscriber is also known as the system user,end-user, user, TEAM smartphone user, or employee.

• Provisioning— Refers to the management of subscribers within the TEAM solution.An operator provisions each subscriber within the enterprise.

• System— Refers to the TEAM solution.

Architecture and Components■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section provides a high-level description of the TEAM solution components, suchas infrastructure, network, and TEAM smartphone.

Introduction to the ArchitectureThe TEAM solution brings world-class hardware and software applications to the solution:

• Interoperability with IP telephony solutions and applications.

• Interoperability with Wi-Fi WLAN technology.

• Standards-based configuration.

The TEAM smartphone provides audio (telephony and PTT) and data (text messaging), along with a fullWindowsMobile 6.1 mobile computing platform, providing many features (such as, e-mail andWeb browsing).

Inside an Enterprise, the TEAM smartphone uses the Institute of Electrical and Electronic Engineers(IEEE) 802.11 a/b/g Wi-Fi standard to connect to a Session Initiation Protocol (SIP)-based PBX through asecure voice-enabled WLAN. Also, inside the Enterprise, the solution supports secure, always-on wirelessmobile access to the IP telephony features and capabilities provided by the PBX, such as real-time,multi-person conferencing, and voice-enabled access to corporate directories and databases.

Figure 1-1 shows an overview of the TEAM solution architecture.

1-4 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Introduction to the Architecture

Figure 1-1 TEAM System Diagram

DMZ stands for Demilitarized Zone. It refers to the buffer zone that sepa-rates the Internet and the private LAN.

68009260001-A January 2009 1-5

System Architecture Chapter 1: System Overview

System ArchitectureThe TEAM solution consists of four component categories:

• Solution Servers

• Communication Backhaul/Backhaul Network

• Wireless LAN (WLAN))

• TEAM smartphone

Figure 1-2 provides a layered view of the system architecture.

Figure 1-2 Layered Diagram of the System Architecture

Solution Equipment

This section covers TEAM servers and existing Enterprise equipment. The TEAM solutionhas one WSM, one NSM , and one PBX. Depending on the Enterprise, it also has one set ofEnterprise Control servers (AAA, DHCP, and DNS), and one set of other Enterprise featureservers (such as, e-mail servers and application servers).

1-6 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide TEAM Equipment

TEAM Equipment

The Wireless Services Manager (WSM) provides the following functions:

• Telephony calls— Provides interconnect call control between the TEAMsmartphone and the PBX.

• PTT/Two-way radio— Provides floor control and call control for PTT callsand Call Alert, independent of the PBX.

The Network Services Manager (NSM) is a Motorola server that provides the interface thatallows the system operator to set various system configuration parameters and perform networkmanagement tasks. Major functions supported include:

• Fault Management— Provides cataloging, reporting, and alarming functionsfor faults received from the WSM.

• Configuration Management— Provides configuration functions for the WSM.

• Performance Management— Provides performance measurement, datacollection, and basic analysis functions.

• Security Management— Provides secured access to network managementfunctions through a user/role model.

• Interface to provisioning functions— The NSM provides the interface to subscriberprovisioning functions, through the WSM Provisioning Client.

Enterprise Control Servers

Customers supply and maintain their own Enterprise control servers, except for the Motorola IntegrationServer that is provided by Motorola. TEAM has a vendor-agnostic approach (standards based) tothe Enterprise servers, which means that customers can reuse existing equipment, if the equipmentmeets the requirements specified in “WLAN and Backhaul Specifications.”

Table 1-1 lists the Enterprise control servers.

Table 1-1 Enterprise Control Servers

Server Purpose

Dynamic Host ConfigurationProtocol (DHCP)

Used to assign/manage IP addresses.

Domain Name Service (DNS) Used to resolve domain names intoIP addresses and vice versa.

68009260001-A January 2009 1-7

Other Enterprise Servers Chapter 1: System Overview

Table 1-1 Enterprise Control Servers (Continued)

Server Purpose

Authentication, Authorization,and Accounting (AAA)

Stores user credentials that are usedto authenticate TEAM smartphonesand subscribers.

Network Time Protocol Server(NTP)

Used to provide system timingsynchronization among the differentsystem components by receivingaccurate time from a network timeserver. NTP is a standard protocolfor sharing time of day informationbetween networked devices.

Motorola Integration Server Optionally available to activatethe WSM. Used by the Enterpriseto obtain licenses and permissionto activate the WSM. This is aMotorola-provided Internet Webservice.

Table 1-2 lists the telephony and telephony-related servers.

Table 1-2 Telephony and Telephony-Related Servers

Server Purpose

IP-PBXs (provided byAvaya, Nortel, and Cisco)

SIP-based network element that providestelephony services to the Enterprise.Comprises a signaling server and mediagateway subcomponents.

IP to TDM Gateway(provided by Dialogic)

Converts legacy TDM telephony signalsto SIP signaling and vice versa. Providesinterface to TDM PBXs.

Call Detail Records (CDRs)processing server

A telephony-related server that processesCDRs.

Other Enterprise Servers

Customers supply and maintain their own third-party Enterprise servers. These are optionalcomponents that can be added by an Enterprise on an as-needed basis. The system mayhave these or other additional Enterprise servers:

• Network Management System—Provides an integrated view of system components and theEnterprise-wide network management system.For example, HP OpenView.

• Device/System Provisioning/Management—Motorola Software Update (MSU) orMicrosoft Systems Management Server (MS SMS).

• E-mail— MS Exchange, and so on.

• IM— Microsoft Live Communications Server (MS LCS) or similar applications.

1-8 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Backhaul Network

Backhaul Network

The backhaul network is the wired LAN used to move traffic from a TEAM smartphone and WLAN tothe servers. The backhaul network is also used to move traffic from the servers to the TEAM smartphoneand WLAN. It encompasses equipment that is not part of the Wireless LAN (WLAN). Customers supplyand maintain their own backhaul. TEAM has a vendor-agnostic approach to the backhaul network, whichmeans that customers can reuse existing equipment or order equipment from multiple vendors, if theequipment meets the requirements specified in "WLAN and Backhaul Network Specifications".

Ensuring consistent Quality of Service (QoS) is a requirement when evaluating a backhaul network.TEAM requires end-to-end QoS from servers to TEAM smartphones.

The backhaul can have a huge impact if it is not planned and designed well. WLAN coverageand capacity drive backhaul requirements. If capacity increases in the WLAN, then the backhaulneeds to expand to manage the traffic. Backhaul has two views:

• Local backhaul (for example, AP to switch)

• Wide-area backhaul (for example, cross regional or wide-area sites)

Wireless LAN (WLAN)

The Wireless LAN (WLAN) is a radio network that uses common protocols to support wirelessTEAM smartphones as they roam across the organization. The WLAN has security protocolsdesigned to ensure authenticated transmissions between TEAM smartphones.

The WLAN consists of two components:

• APs (Access Points/Access Ports) — A Layer 1 to Layer 2 devices. The Wirelesscontroller/gateway function as Layer 2 to Layer 3 routers.

• AP controller/gateways/wireless switch — The WLAN access point concentrator thatcontrols AP functions and interfaces to the core wired Enterprise network.

The Enterprise can choose from multiple vendors, but cannot deploy disparate equipmentfrom different vendors. Consistency is important to maintain QoS. Current industry standardsdo not enforce compatibility between vendor solutions.

WLAN infrastructure needs to be engineered to support voice and data on the same medium. This includesstandards-based security features required in the WLAN (enterprises require a level of security in theirwireless networks that is at least equal to the security available to other segments of their network).

WLAN provides seamless mobility throughout the Enterprise with transparent handoffs between access pointsand between subnets. Call admission control assures the availability of sufficient bandwidth before a voice callenters the Wi-Fi network. QoS needs to be designed throughout the system without any breaks in connectivity,to ensure that voice calls have the highest priority on the Wi-Fi network. Voice is allowed priority access withminimal jitter and delay. Data is allowed use of the network only when it is not needed for voice calls.

When setting up a TEAM solution, it is preferable to install an 802.11a overlayover an existing 802.11b/g network; this allows segregation of the TEAM traffic(802.11a) and the legacy traffic (802.11b/g).To be optimally suited for TEAM, the third-party equipment needs to supportequipment that meets the standards in Table 1-3.

68009260001-A January 2009 1-9

Wireless LAN (WLAN) Chapter 1: System Overview

Table 1-3 lists WLAN components and the standards that they support.

Table 1-3 WLAN Components Standards

Vendor WLAN Components StandardsMotorola/Symbol

AP300 Access Point • Supports 802.11a/b/g.

• Supported rates:802.11a—6, 9, 12, 18, 24, 36, 48,54 Mbps;802.11b— 1, 2, 5.5, 11 Mbps;802.11g— 1, 2, 5.5, 11, 6, 9, 12,18, 24, 36, 48, 54 Mbps.

• 2.4 GHz and 5 GHz bands.

• WMM

• 802.1x supplicant

• 802.11h—standards-baseddynamic frequency selectionand transmit power control

• 802.11i—support for IEEEstandards-based security encryption

• Radio support: 2.4 GHz/5 GHzfrequencies, frequency hopping,direct sequence, OFDM encodingtechniques, and 802.11a/b/g

WS5100 WirelessSwitch

• 802.11i for security with mobility

• Encryption: WEB, WPA,WPA Enterprise, WPA2, andWPA2 Enterprise.

• 802.11Q VLAN Tagging

• 802.11p VLAN Priority

• 802.11r (future)

• WMM

• WMM Power Save

• WMM-AC (future) for bandwidthreservation.

• Layer 3 tunneling

1-10 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide TEAM smartphone

Table 1-3 WLAN Components Standards (Continued)

Vendor WLAN Components StandardsES3000 Ethernet Switchw/POE

• 802.3af Power-over-Ethernet

• Layer 2 switching

Cisco

4400 WirelessControllers (4402,4404)with 1131AG and1242AG AP’sPROGRAMMED INLight Weight AP Mode.

• Cisco 4402 with 2 GB Ethernetports supports configurations for12, 25, and 50 access points

• For 1131AG802.11a/g :Non-modular LWAPP AP:Integrated Antennas

• Cisco 4404 with 4 GB Ethernetports supports configurations for100 lightweight access points

• For 1242AG: 802.11a/gNon-modular LWAPP AP;RP-TNC

TEAM smartphone

The TEAM smartphone includes a subscriber unit hardware platform and an optimized voice client running onWindows Mobile 6.1 OS. It is called as a TEAM smartphone, because it offers capabilities that exceed thoseoffered by a typical mobile phone. The TEAM smartphone supports instant communication, mobile officeapplications, and Enterprise telephony services. The TEAM smartphone helps to increase the productivity ofon-campus workers by mobilizing access to Enterprise applications and voice and data communications.

Model choices include:

• EWP1000/1100: Professional Business Smartphone

• EWP2000/2100: Semi-Rugged Business Smartphone

The EWP1000/1100 and EWP2000/2100 bridge critical voice and data communication intoone TEAM smartphone. They integrate with the Motorola Wireless Services Manager (WSM)to provide on-campus communication and collaboration.

Key capabilities include:

• PBX extension

• One voicemail box and Message Waiting Indicator (MWI)

• Push-To-Talk (2-way radio), private call (one-to-one), and group call (one-to-many) services

• E-mail/calendar/PIM

• Information access

68009260001-A January 2009 1-11

NSM Applications Chapter 1: System Overview

• Web browser

• LOB application integration

• Abbreviated dialing

NSM ApplicationsNSM is an Motorola-provided management application to support the needs of the WSMwhich is used during installation and configuration.

Table 1-4 lists the NSM applications provided by Motorola.

Table 1-4 NSM Applications

Software Description When UsedNSM Site Administration Provides the local administrator access to common

maintenance functions for the NSM.System administration.

NSM Statistics Viewer Plots up to five statistics in a single graph. Statisticsare of two types: Historical statistics and Realtimestatistics.

System administration.

NSM AccountManagement

Used to add, modify, and delete NSM operators.Also, used to manage passwords.


NSM Topology Manager Used to configure topology and parameters on theNSM/WSM and to collect NSM/WSM alarms andevents. However, no alarms for other networkselements are collected. Uses SNMP notifications tosend all events/faults/alarms.

System administration

Management ApplicationsManagement applications include a suite of software tools provided by Motorola and third-party vendorsfor Fault, Configuration, Accounting, Performance, and Security (FCAPS). Configuration and provisioningare performed separately for each product element. The suite also includes secured interfaces.

Management applications can be described in terms of user roles:

• Installer— Installs and configures a set of software. This role typicallyinvolves a one-time setup process.

• Provisioner operator— Provisions subscribers. This role typically involves setup processfor the majority of subscribers and is followed by maintenance as needed.

• System Administrator operator— Uses a set of software duringday-to-day system administration.

1-12 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Management Applications

Management Applications

Table 1-5 lists the software tools provided by Motorola and third-party vendors.

Table 1-5 Management Applications

Software Description When UsedWSM Provisioning Client Standalone platform used for

securing and managing access toWeb services.

Provisioning.

WSM LMT interface Motorola-provided Web-basedapplication, which is themaintenance interface to theWSM. Used to perform monitoringand troubleshooting tasks on theWSM

Installation andconfiguration; SystemAdministration.

Call Detail Records fromthe WSM

An effective mechanism to analyzesubscriber usage. The process is:

1. Aggregate/extract CDRs fromAAA/WSM.

2. Process CDRs using athird-party tool.


Enterprise control servers(DHCP, DNS, and AAA)

Enables administrators to create andmodify security, access, connection,and user policies for controllingnetwork access.

Installation andconfiguration.

IP-PBX, Provides centralized call control fora resilient, distributed network ofmedia gateways and a wide rangeof analog, digital, and IP-basedcommunication devices.


IP-PBX - Voice ServerProvisioning Interface,

A Web-based applicationused for performing frequentmove/add/change operations withinan IP telephony deployment.

Provisioning.

Radius (AAA) AccountManagement Interface,

Enables enterprises to secure andmanage WLAN and remote networkaccess, and provision securityelements for TEAM smartphonesand subscribers. The AAA is usedto authenticate TEAM smartphonesand subscribers.

Provisioning and systemadministration.

68009260001-A January 2009 1-13

Features Chapter 1: System Overview

Table 1-5 Management Applications (Continued)

Software Description When UsedWLAN applications -Device manager/CommandLine Interface (CLI)

Configure WLAN infrastructure toenable Layer 2/3 tunneling.


Motorola Software Update(MSU)

Provides the latest approvedsoftware for devices in warranty.

Provisioning.

Microsoft SMS Allows Enterprises to completelyand remotely control all TEAMsmartphones and the software thatresides on the TEAM smartphones.

System Administration.

Features■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section provides a description of TEAM features and services.

TEAM Voice ServicesThis section provides an overview of the two major types of TEAM voice servicesprovided by VoWLAN telephony:

• Telephony Calls

• PTT—Private Call and Group Call

Telephony Features Overview

The following is a list of features provided by VoIP telephony:

• Make and Receive phone calls

• Call Forwarding

• Call Waiting

• Call Hold/Call Transfer

• Caller ID (number, name, and blocking)

• Abbreviated Dialing, also called Extension Dialing

• Ad Hoc and Meet-Me conference calls (availability depends on PBX brand)

1-14 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide PTT Feature Overview

• Voice Mail Indicator

• DMTF (Over Dial) Support

• E911 Support

• Busy Indicator

For a complete list and detailed descriptions of the telephony features and services, refer to Appendix A.

PTT Feature Overview

Push-to-Talk (PTT) features offer a unique service complement to traditional telephony. PTT features arekey wireless services differentiators, providing subscriber productivity enhancements through quick voicesetup and response. The PTT service supports the following features within an Enterprise:

• Private Call— This is a Motorola feature that enables subscribers to initiate aone-to-one call within the Enterprise. The private call feature allows a subscriberto set up an instant half-duplex call with another subscriber.

• Group Call— This is a Motorola feature that enables subscribers to initiate a one-to-manycall to a pre-provisioned group within the Enterprise. The group call allows a subscriberto initiate and participate in a half-duplex conversation with more than one subscriberwithin the talkgroup. Subscribers can be members of multiple groups and have the optionto select which group they want to call. TEAM supports up to 255 talkgroups.

• Call Alert— This is a Motorola feature that sends a call alert notice to a subscriber,conveying a desire for a subsequent private call.

Users can belong to multiple talk groups, but can only be affiliated to one talk group at a time.

PTT services also ensure:

• Quick call setup—Call setup time between button push and talk permit tone

• System and spectral efficiency—The solution does not require a dedicated connection for eachPTT call. The TEAM smartphones can talk to each other without involving the PBX.

For detailed descriptions of PTT features and services, refer to Appendix A.

TEAM Data ServicesThis section provides an overview of major TEAM Data services, grouped as follows:

• Windows Mobile 6.1 features

• Motorola-specific features

• Third-party features

Key data services include:

68009260001-A January 2009 1-15

Windows Mobile 6.1 Features Chapter 1: System Overview

• E-mail/PIM/Messaging – E-mail (through Windows Mobile interface), calendar, contacts,tasks access through mail application. Access Internet Web sites and synchronize withcalendar and corporate directory/contacts information through Microsoft AirSync.

• Application Flexibility – Windows Mobile 6.1

◦ Supports Windows Mobile LOB applications.

◦ Web browser, web-based forms.

◦ Two-way text messaging

◦ Enhanced UI—Call dialer, multiple line appearance, and text messaging

For a complete list and detailed descriptions of TEAM Data Services, refer to Appendix A.

Windows Mobile 6.1 Features

Microsoft Windows Mobile 6.1 is a compact Operating System (OS), that provides basic applications,with some extensions for the voice communication client. TEAM subscribers primarily usevoice/PTT. They also have access to data features, such as:

• Personal Information Manager (PIM) applications, which include Over-The-Air(OTA) synchronization for the following applications:

◦ Calendar

◦ Phonebook (corporate directory/contacts and address book, compatiblewith MS Outlook phonebook only)

◦ TasksFor synchronization, you can use USB or OTA synchronization if your IT Administratorallows it. Please check with your IT Administrator.

• E-mail

Motorola-Specific Applications on the TEAM smartphone

In addition to the customized Windows Mobile 6.1 OS, TEAM offers applications that arespecific to Motorola. The following are the applications:

• Device/System Provisioning/Management clients (optional), which could be:

◦ Motorola Software Update (MSU), or

◦ Microsoft Text messaging

◦ Internet browser—HTML/WAP 2.0 compliant, and Opera. Can use HTTPand HTTPS on the network and support certificates.

If MSU is not used, the customer can useMS SMS, a third-party competitor product.

1-16 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Device/System Provisioning/Management Client

Device/System Provisioning/Management Client

The Device/System Provisioning/Management client allows a remote administrator to install,remove, and configure applications as well as to set TEAM smartphone registry settings and checkTEAM smartphone status information such as power and battery levels.

• MSU—A provisioning tool that provides the latest approved software for devices in warranty.

There should not be any software dependencies in the TEAMsmartphone to work with MSU.

• MS SMS—Manages large groups of Windows-based computer systems.

Third-Party Applications on the TEAM smartphone

This section includes information on third-party applications pre-loaded into the TEAM smartphone.

• Voice recognition for hands-free dialing and application control, for exam-ple, you can say, Open Browser.

• Document editing—If an e-mail has Microsoft® Word, Excel, or PowerPoint filesattached, you can open and edit them using Documents To Go®. DocumentsTo Go® also supports PDF and zip files.

• Support for third-party LOB applications (optionally available).

Shared Device/Pool FeatureTEAM supports the Shared Device/Pool feature that allows an Enterprise to configure multipleTEAM smartphones for use across many subscribers.

It allows a TEAM smartphone to have two personalities simultaneously:

• a personality of a work group

• an individuals’ personality within the workgroup.

This feature allows two simultaneous active logins on the TEAM smartphone, a grouplogin, and an optional subscriber-specific login:

• A TEAM smartphone providing services associated with a single, well-defined Enterpriseextension can be used by shift workers who possess the TEAM smartphone.

• A subscriber can secure a shareable TEAM smartphone and trigger loading of the profileto the TEAM smartphone by simply logging into the TEAM smartphone through theuser login, and then remove the profile by logging out of it.

68009260001-A January 2009 1-17

Concepts Chapter 1: System Overview

• A TEAM smartphone can be combined with additional TEAM smartphones to form a strategicgroup identified by a single Enterprise extension. Any call to this extension simultaneouslyalerts all TEAM smartphones within the strategic group. The first TEAM smartphone toanswer, receives the call while all other TEAM smartphone alerts cease shortly thereafter. TheEnterprise PBX binds a single group extension to the multiple TEAM smartphones. The bindingof a single group extension to multiple TEAM smartphones is only available when the systemis deployed with PBXs that support Motorola TEAM smartphones as SIP line extensions.

Concepts■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section explains key concepts of the TEAM solution.

Shared Device/PoolThe Shared Device/Pool feature allows the Enterprise to configure devices for pool/department/shiftusage or for personal usage. This allows a TEAM smartphone to change services dependingupon the user that is logged into the TEAM smartphone. This can also provide a cost savingsby eliminating the need to purchase a device for every user.

A persistent login and a temporary login are allowed. The persistent login utilizes the username andpassword credentials from the initial provisioning of the device as the persistent identity of the device.The temporary login allows any authorized user to login to another user’s device and use it. In thiscase, the temporary user is granted services based upon their level of authorization.

Use case example:

An Enterprise may provision a set of devices to be shared among a pool of people associated with a specificdepartment of the Enterprise. The department manager would be given a personal, non-shared deviceprovisioned with their unique services. Both shared and personal devices may be granted a set of WSM, PBX,internet/intranet and line of business application services based upon the username and login credentials. Thedepartment manager has a device that is not shared as the manger’s set of services may be different than thatof the shared devices. Examples of services that can be differentiated based upon username and passwordcredentials are PTT private and group call, SMS, email, voice mail, PBX calling features, PBX class ofservice and class of restriction features, internet, intranet and access to line of business applications.

The shared devices can be used across all workers and all shifts of the specific department. The manager canalso use any one of these shared devices if it is more convenient than using their “personal” device. In thiscase, the manager simply logs into the device through the User Login application using their unique usernameand password which then grants services to the device based upon the manager’s level of authorization.Once the manager completes the intended activities, the manager can logoff and the device will return to

1-18 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide A specific example of PBX services associated with the shared devices:

operation as a shared device of the department. Alternatively, any department worker can log into the deviceusing the department username and password to return the device to shared device operation. A powerdown/power up sequence of the device also returns the device to shared device operation.

A specific example of PBX services associated with the shared devices:

A TEAM smartphone can be combined with additional TEAM smartphones to form a strategic group identifiedby a single enterprise extension. Any call to this extension simultaneously rings all TEAM smartphones withinthe strategic group. The first TEAM smartphone to answer receives the call while all other TEAM smartphonecease ringing shortly thereafter. The enterprise PBX binds a single group extension to the multiple TEAMsmartphones. The binding of a single group extension to multiple TEAM smartphones is only available whenthe system is deployed with PBXs that support Motorola TEAM smartphones as SIP line extensions. Amanager logging into a shared device with their unique username and password causes the device to take onthe services granted to the manager and remove the services granted to the department. In this case, the devicedoes not ring if the department extension is called but does ring if the manager’s extension is called.

Information such as SMS, email, call history, browser history and contacts is retained for eachuser of the device. The system administrator should inform each user of this fact and to delete anydata that a user may not want to be retained and provided to the next user of the device.

Micro MobilityMicro mobility is a function that allows the TEAM smartphone to roam from AP to AP withina WLAN coverage area without impacting voice quality or applications. The APs may be onthe same or different subnets. The TEAM smartphone roams from one subnet to another subnetwithin the same network with no call in progress or with a call in progress. The voice callsproceed normally during AP transitions even between subnets.

During a voice call as the TEAM smartphone moves from AP to AP in the WLAN, it must remainreachable at its current assigned IP address, regardless of the location of its serving AP.

TEAM leverages specific WLAN mechanisms for fast hand-off. It is implemented exclusivelybetween the TEAM smartphone and WLAN. Micro mobility functionality resides mainlyinside the WLAN and is provided by the WLAN Vendor.

Example Scenarios

This section includes example scenarios of what happens when a subscriber who is in motionmakes a voice call or, changes subnets in the WLAN.

Micromobility has three groupings:

• Voice calls—Voice calls include interconnect, private call, and group call. Privatecall and group call could also be grouped as PTT calls.

• Data sessions—Data session means that the TEAM smartphone is running anapplication that can exchange data with servers.

• Idle traffic—Idle condition means that no applications are running on the TEAM smartphonethat will be using the IP address on the TEAM smartphone to transfer data .

68009260001-A January 2009 1-19

Telephone Numbering Scheme Chapter 1: System Overview

Example 1: Roaming within voice call

The TEAM application lets you maintain active voice calls while roaming within the EnterpriseWLAN, including while changing subnets. When a subscriber makes a telephony call, hand-offs occurto ensure that the call does not drop if the subscriber is in motion, as follows:

• Intra-subnet handoff from an AP to an AP on same subnet.

• Inter-subnet handoff (APs on different subnets.

◦ During active voice calls (PTT or interconnect), the system should maintainthe same IP address for the device. If the system fails to maintain the same IPaddress, then the call drops when the device roams to a new AP. So, within aPTT/Interconnect call, if the device roams, it makes a restricted DHCP call - aDHCP request to retain the IP the address it currently holds.

◦ The solution relies on industry standards (802.11 and WiFi Alliance standards) andleverages WLAN infrastructure capabilities (for example, AP to AP tunneling and packetrouting) to handle the continuation of a call (until the TEAM smartphone re-registerson the new subnet and acquires a new IP address on that segment).

Within 30 seconds of ending the PTT/interconnect call, if a roam occurred during the call, theTEAM smartphone makes an unrestricted Dynamic Host Configuration Protocol (DHCP) request,which means that the DHCP might assign the TEAM smartphone a new IP address (and ending anyLayer 2 [L2] tunneling that might be set up for the TEAM smartphone).

Example 2: Roaming in data session

All non PTT/interconnect applications are expected to be immune to temporary link loss conditions (such as,going out of coverage, or being connected to a new AP without having an IP address that is valid for that L2address). These applications are required to use the Windows facility to receive notification of IP addresschanges when they occur. This is analogous to moving our laptops from our wired desk to meeting roomswhere we jump on the wireless network, and Outlook reconnects through the new address seamlessly.

Example 3: Roaming when neither voice call nor data session is active (Idle condition)

The idle condition includes the scenario when non PTT/interconnect applications are not running.If the applications are running but the device is not in use (for example, if the user is not readinge-mail or browsing web pages), the applications should be aware of address changes and handlethem as described in the roaming in data session scenario.

Telephone Numbering SchemeThis section provides a brief description of the telephone numbering scheme for the TEAM smartphone.In general, the TEAM smartphones act as extensions on the Enterprise PBX. This is one of the basicfunctions of the WSM (it brokers a single connection to/from the PBX and allows multiple TEAMsmartphone connections through that one logical connection to the PBX).

Introduction

The Enterprise telephone numbering scheme establishes how the subscriber will interact with the TEAMsmartphone to invoke services such as call origination, call forwarding, PPT, and text messaging. EachTEAM smartphone will be assigned with a typical 10-digit phone number. The TEAM solution supports

1-20 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Telephone Numbering Scheme — Example

abbreviated dialing, so that fewer digits are needed to invoke the services mentioned above. The TEAMsmartphone also supports the concept of contact number. This allows a single entry in the contact listto make a potential recipient reachable through telephony, PTT, or text messaging.

Telephone Numbering Scheme — Example

A TEAM smartphone is associated with one unique Enterprise phone number. The Enterprise phone numberis used to dial the TEAM smartphone. If the PBX solution allows, extension numbers can be set up as well:

• Enterprise Phone number, for example, 8475557701.

• PTT number is the last 5 digits of the Enterprise Phone Number. For example,Dispatch ID for Enterprise Number 8475557701 is 57701.

• Extension number is the last N digits of the Enterprise Phone Number will be used, whereN can be defined at the time of system provisioning, for example, 7701.

• Subscriber <User ID>, for example usr7701.

Standards-Based Design■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

A standards-based solution, like TEAM, works with any vendor’s equipment that complieswith industry standards. Typically, industry standards are carefully developed and robust.They are adopted only after thorough study and discussion, and examination by industryexperts. Benefits of standards-based design include:

• New technologies utilizing open standards can usually be relied upon for moreconsistent, predictable integration and deployment, easier maintenance andupgrading, and clearer migration paths.

• Standards-based systems also help ensure compatibility and interoperability with otherproducts based on the same standard, even when those products come from a varietyof manufacturers. This leads to more flexible solution alternatives.

• Implementing standards-based technologies prevents products/solutionsfrom becoming obsolete quickly.

The following sections cover supported standards in more detail.

IEEEThe Institute of Electrical and Electronic Engineers (IEEE) is one of the leading organizations inthe world for setting standards in technology. Notable IEEE standards includes the IEEE 802.3Ethernet standard and the IEEE 802.11 wireless networking standard.

68009260001-A January 2009 1-21

802.11 a/b/g — Bands and Speeds Chapter 1: System Overview

802.11 a/b/g — Bands and Speeds

The 802.11 standard, developed over the past 10 years, is emerging as the mostly widely accepted standardfor WLAN. The TEAM smartphone operates on APs that are certified for operation on 802.11 a/b/g.

Table 1-6 802.11 a/b/g — Bands and Speeds

Standard Bands Throughput Comments802.11a 5 GHz Up to 54

Mbit/sChannels are 20 MHznon-overlapping. Someadjacent channel interferenceis possible.

802.11b 2.4 GHz Up to 11Mbit/s

Channels in 2.4 GHz bandoverlap. Expect interferencefrom other products operatingin the same band.

802.11g 2.4 GHz Up to 54Mbit/s

Channels in 2.4 GHz bandoverlap. Expect interferencefrom other products operatingin the same band. 802.11 g isan extension to 802.11b andhas backward compatibilitywith 802.11b.

For TEAM, the preferred solution is 802.11a or 802.11a with 802.11g (good for largerareas). An 802.11a/g frequency arrangement is used to allow some micromobility betweenbands (2.4 GHz and 5 GHz). This solution maximizes capacity.

Wi-Fi Alliance (WFA)The Wi-Fi Alliance (WFA) is a trade group that owns the trademark to Wi-Fi. The WFA includesindustry leaders who drive the adoption of globally accepted standards for high-speed WLAN. WFAis a manufacturers’ standard. The WFA develops rigorous tests and conducts Wi-Fi certification ofwireless devices that implement the universal IEEE 802.11 specifications.

The WFA developed Wi-Fi Protected Access (WPA and WPA2) to secure wireless networks.

• WPA was developed as an early standard to replace WEP, while waiting for the 802.11standard to be ratified. It includes the majority of the IEEE 802.11i standards.

• WPA2 is a select subset of 802.11i. It is a list of certification tests for the device.

The TEAM solution uses the full IEEE 802.11i Wi-Fi Protected Access 2 (WPA2) specification.

The WFA publishes a number of standards, including:

• Wi-Fi Multimedia (WMM)

• WMM Power Save (WMM-PS)

1-22 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Wi-Fi Multimedia (WMM)

For more information, see: www.wifialliance.com.

Wi-Fi Multimedia (WMM)Wi-Fi Multimedia (WMM) is a Wi-Fi Alliance interoperability certification, based on the IEEE802.11e draft standard. 802.11e adds QoS extensions to the 802.11 standard.

WMM allows the subscriber unit and the access point to categorize messaging between the endpoints and toprioritize the messaging. WMM prioritizes traffic according to four Access Categories (AC):

• AC_VO (Voice)

• AC_VI (Video)

• AC_BE (Best Effort)

• AC_BK (Background)

However, it does not provide guaranteed throughput. TEAM uses WMM (802.11e)to segregate voice from data packets.

WMM-PS

WMM Power Save (WMM-PS) adds power saving capabilities. Power Save uses mechanisms from 802.11eto save power (for battery powered equipment) and fine-tune power consumption. WMM-PS is alsoreferred to (under an older name) as Unscheduled Automatic Power Save Delivery (U-APSD).

For TEAM, Power Save allows a unit to receive data packets, while battery conserving the battery life.During this time, the AP broadcasts and tracks TEAM smartphones associated with it.

Power save during a voice call— The TEAM smartphone can poll the AP, allowing deep sleeping during avoice call. The AP buffers downlink voice packets until a poll is received from the TEAM smartphone.

Power save when not in a call— The AP buffers TEAM smartphone packets, using 802.11 InfrastructurePower Save. The TEAM smartphone monitors AP beacon frames at reduced rates.

WMM-AC – Admission Control (Future)

WMM-AC adds admission control to the WMM access classes. It limits the number of simultaneouscalls on a single AP. Admission control ensures that adequate bandwidth is available for a voice call andcontributes to overall voice quality; this is implemented through bandwidth reservation.

The bandwidth reservation record format has been described within the WMM specification. Theimplementation of bandwidth reservation has been previously limited to select vendor proprietaryversions (such as Cisco APs). Cisco CCX has a version of admission control utilized by the TEAMsolution. The WiFi Alliance is in the process of inter-vendor testing for WMM-AC.

The TEAM solution:

• Works best when the RAN supports WMM, WMM-PS and the proposedWMM-AC (Admission Control) standards.

• Works well with Cisco CCX which provides packet prioritization, powersave, and admission control.

68009260001-A January 2009 1-23

Session Initiation Protocol (SIP) Chapter 1: System Overview

• May be able to use RANs without the above standards, with the possible reductionof voice quality, talk/idle time, and reliability.

Session Initiation Protocol (SIP)The Internet Engineering Task Force (IETF) introduced Session Initiation Protocol (SIP) to simplifythe process of running VoIP connections across the Internet. Networks running SIP can handle VoIPcalls regardless of which vendor has created the TEAM smartphones or soft phones.

SIP allows consistent inter-connectivity between products, such as between the WSM, the PBX and theTEAM smartphone, when it is used as the baseline call signaling protocol. SIP is an application-layer control(signaling) protocol for creating, modifying, and terminating sessions with one or more participants.

For TEAM, the TEAM smartphone uses standard SIP, while the WSM translates it, and communicates withPBXs (which typically do not have all features implemented in SIP). The WSM is the SIP proxy and registrar.

ITU-TInternational Telecommunications Union-Telephony (ITU-T) has established specificationsfor audio compression, including standard codecs.

Codecs/Vocoders

Codecs encode and decode the data of any given format (for example, audio, video, and so on). A Vocoder isa codec that is used to compress or decompress audio data. For TEAM, a high quality vocoding scheme isused within the Enterprise for transmission of toll-quality voice for both telephony and PTT.

Table 1-7 lists the interconnect vocoders supported in TEAM:

Table 1-7 List of Interconnect Vocoders

Vocoder CommentsG.711 (64K), bothG.711 a-law and µ-lawalgorithms

G.711 provides the best voice quality since ituses no compression. It also has the lowestlatency (lag) because not using compressionreduces processing power. It requires morebandwidth than other codecs.

G.729 for infrastructure Maximizes call capacity on a given link. Ithas lower bit rate and is bandwidth efficient.The IP-PBX implements G.729 and decodesthe G.729A bearer coming from the TEAMsmartphone.

G.729a (8K) forTEAM smartphoneimplementation

Bandwidth efficient and provides improvedaudio quality.

1-24 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Echo Cancellation

The PTT/Dispatch Vocoder that is supported in TEAM is Vector Sum Excited Linear Prediction(VSELP), a low bit rate vocoder used for dispatch private calls and group calls.

Echo Cancellation

Echo cancellation describes the process of removing echo from a voice communication inorder to improve voice quality on a telephone call. Echo cancellation algorithms improve audioquality. The digital part of a communications network does not cause any echo. Hence, onlytwo types of echo cancellation mechanisms are needed for TEAM:

• Provide cancellation of acoustic echo in TEAM smartphones.

• Provide echo cancellation for echoes caused in the PSTN and beyond. (Echocancellation is provided for all voice calls in the PBX.)

Echo cancellation is required in instances of 2-wire to 4-wire conversion in the network. This can be:

• Analog to digital

• Analog to analog

68009260001-A January 2009 1-25

Echo Cancellation Chapter 1: System Overview


1-26 68009260001-A January 2009

Chapter

2Theory of Operations

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

This chapter provides a description of the TEAM solution architecture, components,services, and requirements.

System Architecture■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the TEAM solution architecture. The architecture includes the following:

• WSM application

• Solution Servers

• Communication Backhaul

• Wireless LAN (WLAN)

• Mobile TEAM smartphones

Figure 2-1 shows a detailed diagram of the TEAM solution.

68009260001-A January 2009 2-1

Equipment Chapter 2: Theory of Operations

Figure 2-1 TEAM – Detailed System Diagram

Equipment■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section provides a brief description of the equipment used in the TEAM solution.

The TEAM is equipped with:

2-2 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide TEAM Equipment

• Wireless Services Manager (WSM)

• Network Services Manager (NSM)

The Enterprise servers are:

• Control Servers

• PBX (Telephony Servers)

• Telephony Related Servers

• Other Enterprise Servers

TEAM EquipmentThis section provides a description of the hardware and software components of the TEAMcomponents, the WSM, and the NSM. The TEAM solution supports one WSM/NSM paircommunicating with one IP-PBX or one IP-to-TDM GW at a time.

WSM

The Wireless Services Manager (WSM) offers the following general features:

• Push-to-talk communication within an Enterprise.

• Quick PTT call setup—call setup time between button push and talk permittone is typically less than one second.

• Solution security, with mechanisms that validate network elements, TEAMsmartphones, and subscribers.

• System and spectral efficiency—solution does not require a dedicatedconnection for each PTT call.

• PBX interoperability.

• Performance optimization.

• Reliability.

• Excellent PTT subscriber experience through tightly managed QoS and floor control.

• Centralized subscriber provisioning.

• Easily scalable to serve a large number of subscribers.

The WSM also provides telephony calling between two TEAM smartphones if no PBX is available.

Key Functions

The WSM provides the following functions:

• PTT Application—Enables PTT private calls and group calls between TEAM smartphones.

• SIP Proxy— Main interface to all IP-PBXs or TDM PBX gateways.

68009260001-A January 2009 2-3

System Responsibilities Chapter 2: Theory of Operations

• SIP Registrar— Stores mobile registrations and participates in the authenticationand authorization of each TEAM smartphone.

• Subscriber Access Configuration— Provides a database that stores thecomplete set of a subscriber’s provisioning data.

• Interface to Enterprise PBX— Supports an interface to multiple manufacturers of PBXequipment to enable wireless TEAM smartphones to access PBX calling features.

• Security Management— Validates each network element that interacts with the WSM.

• Smartphone Link Management— Controls the TEAM smartphone link to thenetwork thereby enhancing performance and security.

• Accounting— Provides Call Detail Records (CDRs) for both telephony and PTTcalls. The CDRs are made available to other CDR processing server applicationsthat can compute chargers and/or usage information.

System Responsibilities

The WSM provides PTT functionality within an Enterprise. The WSM also stores importantsubscriber information in the Enterprise environment: handling registration, voice servicesauthentication within the WLAN, and message notification functions.

PBX Interoperability—TheWSM interoperates with a variety of IP and TDMPBXs using standard interfaces.It provides interconnect call control between the TEAM smartphone and the PBX. Protocol connectors inthe WSM allow a single TEAM smartphone codeline for all PBXs that are independent of PBX vendorimplementation. The TEAM smartphone uses standard SIP, WSM translates it, and communicates with PBXs .

Performance Optimization— A proprietary link between the TEAM smartphone and WSM that optimizesprotocol for registration, synchronization, mobility-related procedures, and so on. Using Wireless MultiMediaPower Save (WMM-PS) provides advanced power-saving mechanisms for extended battery life.

Network Access Control— Network security profile is managed between the TEAM smartphone and theWSM. This is a security enhancement that is offered in addition to existing security techniques (WPA2,802.1X, and so on). It protects the network through a single entry point into network.

Scalability—A link management from a TEAM smartphone to the system that does not need to be individuallymanaged by a PBX vendor or any other third party. So, extra licenses and expensive upgrades of third-partyequipment are not required to support the extra capacity. The reuse of a single Transport Layer Security (TLS)connection between a TEAM smartphone and the WSM improves network efficiency. It has the intelligenceto decide the best route for bearer traffic between endpoints while maintaining control of the session.

Reliability— WSM has four nines (0.9999) availability, with architecture that can be extended in thefuture to include redundant configuration or fit into a clustered PBX architecture.

The Enterprise-supplied power to the WSM needs to be appropriately sized, and providesix nines (0.999999) availability. This is the responsibility of the system integrator andis outside the scope of the solution supplied by Motorola.

WSM Role in Calls

The WSM facilitates telephone connections between:

2-4 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide WSM

• The EWP1000/1100 or /WP2000/2100 smartphones provisioned on the WSM.

• Other TEAM smartphones or softphones capable of being connected through a PBX.

The WSM provides its own services for subscribers of TEAM smartphones connected exclusively to it:

• PTT

• Call routing—The WSM checks the call target’s unconditional Call Forwarding statusfor each call (INVITE) that it receives from PBX, or, in the case WSM Call Control(WSMCC) is enabled, from a TEAM smartphone. It basically checks its SIP datastorewhile paying attention to the contacts related to the target’s SIP ID.

WSM

This section provides information about WSM appliance.

Configuration

The Motorola WSM appliance is available in one configurations:

• 1U Chassis w/260W PS; no Rails

• Intel Pentium E2160 Dual-Core 1.80GHz

• 2GB DDR2 667MHz Memory

• 80GB 7.2kRPM SATA2 Hard Drive

• Supports up to 4500 subscribers

• Requires external USB DVD-ROM for installs and upgrades (not supplied)

Photo

Figure 2-2 and Figure 2-3 show the WSM appliance.

Figure 2-2 WSM Appliance — Front View

Figure 2-3 WSM Appliance — Rear View

68009260001-A January 2009 2-5

Technical Specifications Chapter 2: Theory of Operations

Technical Specifications

The Motorola WSM Appliance is equipped with:

• ICC 1U SRV E2160/2GB/80GB/Video/2xLAN/Riser

• 1U Chassis w/260W PS; no rails

• MB X7SLM

• E2160 Dual-Core 1.8GHz

• 2GB DDR2 667MHz UMB

• WD 89GB 7.2k RPM SATA2

• Power Splitter SATA

• SATA data cable

• 1U P CI-E x8 riser card

• Retention kit 775 socket

• 1U aluminum heatsink

• External USB DVD-ROM drive is required but not provided

LEDs/Ports

The LEDs/Ports for WSM Appliance are:

• Two USB ports

• One active ethernet port (left side port)

• One serial port

WSM Software

This section provides information about the WSM software.

LMT Interface

Local Maintenance Terminal (LMT) is the maintenance interface to the WSM. The interface isaccessed with a common Web browser such as Internet Explorer or Netscape.

The LMT covers operations specific to WSM maintenance. Example tasks include:

• Running database reports

• Tracing subscriber activity

• Starting and stopping the application

Also, two alternate access methods are available:

• Text interface—A text-based browser that uses a Web server. Operator accountsare the same as the LMT, and the functionality is identical.

2-6 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide NSM Server Application

• Emergency Local Maintenance Terminal (ELMT) — A text-based emergency maintenanceinterface to the WSM. The ELMT can be accessed locally using a serial console connection orxterm. It does not depend on aWeb server. It contains a minimal set of critical WSM operations.

NSM Server Application

The NSM is a Motorola-provided management application that supports the WSM. The Motorola NSMprovides Java-based tools (server side) and web-based tools (client side) for configuring and monitoring theWSM and other servers in the TEAM network. The NSM server is deployed as a standalone element manager;however, the Enterprise has the option to incorporate it as part of an integrated network management solution.

The NSM runs on an Enterprise-supplied server running Microsoft Windows 2003Server or Microsoft Windows XP.

Features

The NSM has the following features:

• Fault Management:

◦ Displays stored events in the Event Viewer GUI

◦ Uses SNMP for reporting from WSM to NSM

◦ Monitors non-Motorola equipment using Ping/SNMP polling

◦ Stores up to 32 days of normal events and one year of availability data

◦ Displays multiple severity levels (Critical, Major, Minor, and Warning)

◦ Provides fault information for the WSM and possible root causes and remedies

◦ Filters events based on severity, type, IP address, active/clearedstate, and user-acknowledged state

◦ Sends e-mail notification to operators: up to 5 e-mail addresses can be configured,and the NSM sends the e-mail notifications to the configured e-mail addresses

◦ Forwards SNMP to other network management systems

◦ Shows the state of a network element graphically in the Topology Manager

• Configuration Management:

◦ Configures the WSM

◦ Provides full configuration, validation, and online help support

◦ Provides configuration reports on changes

68009260001-A January 2009 2-7

NSM Server Hardware Requirements Chapter 2: Theory of Operations

• Performance Management:

◦ Collects and displays statistical data in the Statistics Viewer Display

◦ Provides historical statistics

◦ Offers up to 32 days of statistical data for a substantial baseline of activityfor review. By default, NSM stores up to seven days of statistical data.This can be configured to store up to 32 days

◦ Collects information from the WSM every 30 minutes

◦ Supports extraction of data for additional analysis or viewing in another tool (such asExcel or a database): NSM parses the statistic files into unl files automatically. Theseunl (database unload) files can be used for additional analysis of the data

• Security Management:

◦ Provides user name/password protection for Motorola NSM access.Provides an interface to configure, enable, and disable Network Man-agement Communication Security settings

- Access classes (guest, operator, and administrator)

◦ Provides configuration logs to map operators to network configuration changes

◦ Acts as the control point for management (add/delete/list/import/ex-port) of security certificates on WSM

NSM Server Hardware Requirements

The NSM is installed on an Enterprise-supplied server that meets the following hardware requirements:

• 2.8 GHz Pentium 4 CPU

• 60 GB hard drive

• 1 GB RAM

• 10/100/1000 BaseT network interface card

• DVD-ROM drive

• SVGA Video Card

NSM Server Software Requirements

The NSM is a software-only product. It can be installed on a computer that is loadedwith specific hardware and software requirements.

Software requirements:

• Microsoft Windows 2003 Server with Service Pack 1 or Microsoft WindowsXP with Service Pack 2 with firewall off.

• Microsoft Internet Explorer, version 6.0.

• Apache Web Server, version 2.0.54 (included in NSM installer).

2-8 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide NSM Software

NSM Software

The NSM software provides a number of services for configuring, monitoring, andmanaging the WSM in a WLAN environment.

The NSM allows you to perform the following tasks:

Environment:

• Single-launch page to access all NSM partner management applications

• Accessible from any Client workstation in the TEAM network. Remoteaccess is available. However, enabling remote access using industry-standardapplications is the responsibility of the Enterprise.

Provisioning:

• Provision subscribers and talkgroups into the WSM

• Add subscribers and their assigned talkgroups individually or in bulk

The NSM allows you to perform the following tasks:

• Configuration:

◦ Download configuration data to the WSM

◦ Validate configuration version before download

◦ Revert to previous configuration version

◦ Compare configurations

◦ Activate license and update software

• Fault Monitoring:

◦ Process WSM events and alarms

◦ Display and filter incoming event and alarm information

◦ Clear alarms so they are no longer visible (does not update WSM state)

◦ Display current WSM site status

• Performance Monitoring:

◦ Retrieve and process historical statistics files from WSM

◦ Display real-time and historical WSM statistics information

◦ Log incoming statistics

Figure 2-4 shows the NSM screen.

68009260001-A January 2009 2-9

Enterprise Control Servers Chapter 2: Theory of Operations

Figure 2-4 NSM Screen

Enterprise Control ServersThe Enterprise control servers are:

• Dynamic Host Configuration Protocol (DHCP)

• Domain Name Server (DNS)

• Authentication, Authorization, and Accounting (AAA)

• Network Time Protocol (NTP) Server

• Motorola Integration Server

DHCP

Dynamic Host Configuration Protocol (DHCP) is a protocol that is used for assigning both dynamic andstatic IP addresses to devices on a network. With dynamic addressing, a TEAM smartphone can havea different IP address every time it connects to the network. Dynamic addressing simplifies networkadministration because the software keeps track of IP addresses. DHCP allows the administrator todefine a range of addresses that are available for distribution (address pooling).

DHCP servers are Enterprise-supplied servers, which support:

• DHCP vendor-specific options in a DHCP client request. The server must be configuredto identify unique vendor-specific option text tags and associate a unique DHCPconfiguration with this tag. The vendor-specific option must support extended AmericanStandard Code for Information Interchange (ASCII) for text input.

• Configuration of the TEAM WLAN smartphone DHCP data set that includes theSubscriber Access Configuration Server (SACS) url.

• Deployment of multiple DHCP servers, possibly configured in an 80/20 rule witha divided scope, or a clustered DHCP server set.

DNS

Domain Name Server (DNS) is an Internet service that translates domain names into IP addresses. Domainnames are alphabetic, so they are easy to remember. DNS has its own network. If a DNS does not knowhow to translate a particular domain name, then it contacts another DNS to get the correct IP address.

2-10 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide EAP-TLS

DNS is an Enterprise-supplied server. TEAM uses DNS for:

• IP lookup

• IP address translations

Both Forward and Reverse lookup zones must be specified on DNS serverand should include WSM and NSM hosts.

EAP-TLS

User environments have existing security measures in place which include the requirement to authenticate auser with a username and password before access to any corporate assets or data is granted. Any additionalcredentials needed are either compatible with the enterprise authentication servers or, if stored in thecomponents are accessible by trusted components within the enterprise. As such, the TEAM Smartphonessupport EAP-TLS RADIUS based authentication. Enterprises are assumed to have AAA servers to supportUser Name and Password authentication as well as WLAN Device authorization with the TEAM solution.

RADIUS (AAA)

The Authentication, Authorization, and Accounting (AAA) server is a system in IP-based networking that isused to control access to computer resources and to keep track of the user activity over a network.

• Authentication— The process of identifying an individual, based on a username andpassword. Authentication is based on the idea that each individual user has uniqueinformation that sets that individual apart from other users. The AAA server uses theRemote Authentication Dial In User Service (RADIUS) protocol to authenticate TEAMsmartphones and subscribers. TEAM uses two methods for authentication:

◦ X.509v3 digital certificate and MAC address for the TEAM smartphone

◦ Username and passwords for the TEAM smartphone user

TEAM solution can optionally support SIP Digest Authentication.

• Authorization— The process of granting or denying a user access to network resources oncethe user has been authenticated through the username and password. The amount of informationand the number of services that the user can access depends on the user’s authorization level.

• Accounting— The process of tracking a user’s activity while accessing networkresources, including the amount of time spent in the network, the services accessedwhile in the network, and the amount of data transferred during the session.Currently, this feature is not used in the TEAM solution.

The standards/Internet Request For Comments (RFC) and drafts that AAA has to supportto be interoperable with TEAM solution are:

• RFC 2865 RADIUS, http://www.ietf.org/rfc/rfc2865.txt

• RFC 2866 RADIUS Accounting, http://www.ietf.org/rfc/rfc2866.txt

68009260001-A January 2009 2-11

RADIUS (AAA) Chapter 2: Theory of Operations

• RFC 2869 RADIUS Extensions, http://www.ietf.org/rfc/rfc2869.txt

• RADIUS Types, http://www.iana.org/assignments/radius-types

• RFC 2869 RADIUS, draft-sterman-aaa-sip-00.txt

• IETF working draft: RADIUS accounting for SIP servers, draft-schulzrinne-sip-ping-radius-accounting-00.txt (http://www.freeradius.org/rfc/draft-schulzrinne-sip-ping-radius-accounting-00.txt)

Minimal configuration requirements include:

• Security implemented on the TEAM smartphone that matches the security setup within the WLAN. For example, if the TEAM smartphone is set up withWPA2 Enterprise, so should the WLAN.

• 802.1 x authentications of TEAM smartphone and network elements.

• The TEAM smartphone is provided certificate-based authentication that must beimplemented within the network deployment, that is the TEAM smartphones’Root CA certificate are installed on the AAA server

AAA is an Enterprise-supplied server. The TEAM solution supports the following AAA server:

Table 2-1 AAA Server supported by TEAM

Brand Hardware Software

Cisco ACS • Processor: PentiumIII-compatible with 550MHz or faster

• 256 MB RAM

• OS: Windows 2003 Server

• ACS3.3

Juniper Steel-BeltedRADIUS

• Processor: 2.8 GHz Pentium

• Memory: 512 MB RAM

• Disk space: 80 GB

• Connectivity: On-board dual100/1000 NIC

• Windows XP/2000/NT runs onWindows NT 4.0 with ServicePack 6

• Windows 2000 (all editions)

• Windows XP (all editions)

• Windows Server 2003 (alleditions)

The RADIUS Shared Secret is a password (a string value), on the WSM and AAA servers that isused to authenticate subscribers. The value must be the same on both. If you want to change thepassword on AAA Server and WSM Shared Secret, you can change these values on the WSM byupdating the RADIUS Shared Secret. This change can be done while the WSM is in operation. Formore information, refer to TEAM System Installation and Configuration Guide.

If an Enterprise tries to re-use an existing AAA certificate repository, there canbe a likely need for two separate AAA servers.

2-12 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Public Key Infrastructure

Public Key Infrastructure

The TEAM mobile devices will come pre-provisioned with X.509 digital certificates for device and userauthentication purposes. The TEAM equipment will be provisioned with necessary certificates during licenseactivation process. The enterprise customer’s IP-PBX or PBX-GW is required to install the TEAM equipments’ Root CA certificate in its trusted store if TLS is the securedWSM-PBX connection type to be configured. Theenterprise customer’s AAA is required to install the TEAM mobile devices’ Root CA certificate in its trustedstore, and install the TEAM AAA server certificate (retrieved from the TEAM NSM/WSM upon activation).

Network Time Protocol (NTP) Server

The Network Time Protocol (NTP) server is provided by the Enterprise. The NTP server providesthe accurate time to the NSM/WSM. It connects to an Internet-based NTP time server (such aspool.ntp.org) or directly to a GPS antennae that provides a GPS time synchronization signal. Theserver then sends network time data out to local clients in the NTP format.

NTP is required to provide system timing synchronization among the different system components.If the system is not synchronized, it could cause several problems, such as the inability to establishconnections between components (security threats) or audio quality issues.

Motorola Integration Server

The Motorola Integration Server is an Internet Web service used by the WSM for the following:

• Online activation of the WSM

• X.509 Certificate Download

• Online patch download

Certificates are distributed as part of the WSM activation process.

• Online through the Internet, which requires a back-end process with theMotorola Integration Server

• Offline through CD-ROM

PBX (Telephony Servers)PBXs provide a rich level of telephony features. Every Enterprise has one PBX for the Public SwitchedTelephone Network (PSTN) interface. A PBX provides services to Enterprise associates for the TEAMsmartphones, and regular Enterprise telephones. Services include basic call, and supplementaryservices such as transfer, conferencing, call forwarding, and access to voice mail.

For a telephony call, the PBX connects a TEAM smartphone to a TEAM smartphone, or a TEAMsmartphone to a deskset phone, or a TEAM smartphone to the PSTN.

Depending on the vendor, the PBX can steer a voice call to utilize resources in the most efficient manner. It can

• Direct voice packets through its media server for the duration of the call.

• Instruct TEAM smartphones to talk directly between themselves. Thisprocess is called media shuffling.

68009260001-A January 2009 2-13

Hardware and Software Specifications Chapter 2: Theory of Operations

The PBX is supplied by the Enterprise. The means of SIP signaling to support a telephony featureset could vary with PBX vendor. The TEAM solution integrates with widely deployed existingPBX solutions from major vendors. The WSM is configured with transport type, security, and SIPtranslations required to work with the PBX of choice. In general, the PBX is involved for telephonecalls, while the WSM handles call control for wireless calls and PTT services.

The TEAM solution currently supports one pair of WSM/NSM communicating withone IP-PBX or one IP-to-TDM Gateway at a time.

WSM can integrate with the IP PBXs via SIP Trunk. The supported IP PBX vendors are:

• IP-PBXs

◦ Avaya

◦ Cisco

◦ Nortel

WSM can integrate to TDM PBXs via the Dialogic Gateway. The supported TDM PBX vendors are:

• Avaya

• Nortel

• NEC

Hardware and Software Specifications

Table 2-2 lists the Dialogic PBX equipment hardware specifications.

Table 2-2 Dialogic Gateway to TDM PBXs Hardware Specifications

Model SpecificationsDMG2030DTIQ • Network Interfaces:

10/100 BaseT EthernetLAN port Connector 1shielded female RJ-45 jackfor LAN

• Power Requirements : 90VAC to 264 VAC

• EnvironmentalRequirements: Operatingtemperature: 32 ° F to +122° F

2-14 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Hardware and Software Specifications

Table 2-3 lists the Dialogic PBX equipment software specifications.

Table 2-3 Dialogic Gateway to TDM PBXs Software Specifications

Model Software

DMG2030DTIQ GA version of 6.0

Table 2-4 shows TDM PBXs supported by the TEAM Solution through Dialogic GateWay (DMG2000)

Table 2-4 TDM PBXs Supported by TEAM Solution Through Dialogic GateWay (DMG2000)

Manufacturer/Model Hardware Release Software Version

AvayaCommunications Manager

S8300, S8500, S87XX 4.0, 5.0

NECNEAX 2400 IPX

IVS series Version 17, Release 03.46.001

NortelMeridian Option 11C

Option 11C Version 17, Release 25, Issue40, Version 2111

Common telephony features offered by each TEAM supported Dialogic Gateway toTDM PBX are shown in Table 2-5 .

Table 2-5 Call Features Supported by TDM PBXs

AvayaCommunications

Manager

NortelMeridianOption 11C

NECNEAX 2400

IPXBasic Call ControlInbound Calls, OutboundCalls, Caller ID

Yes Yes Yes

Call TransferBlind

Yes Yes Yes

Call TransferConsultive

Yes Yes Patch Required

Call Forward(CFNA, CFB, CFNR, andCFU)

Yes Yes Yes

Multi-party CallAppearance

Yes Yes Yes

E911 Yes Yes Yes

DTMF Tones Yes Yes Yes

Call Restriction Yes Yes Yes

Ad Hoc Conference Call Yes Yes Yes

68009260001-A January 2009 2-15

Hardware and Software Specifications Chapter 2: Theory of Operations

Table 2-6 shows IP PBXs supported directly by the TEAM Solution.

Table 2-6 IP PBXs Supported Directly by the TEAM Solution

Manufacturer/Model

HardwareRelease

SoftwareVersion

SIPTrunk

SIPStation

AvayaCommunications Manager

S8300 / S8500/ S87XX

4.0, 5.0 Supported Supported(via OPS)

CiscoUnified Call Manager (CUCM

MCS78XX 5.1 and later Supported NA

CiscoMedia Express (CME)

Routers 2801,3825

IOS 12.4(11) Supported NA

NortelCommunications Server 1000

CS1000Eseries

Succession5.0, 5.5

Supported NA

Common telephony features offered by IP PBXs supported directly by theTEAM solution are shown in Table 2-7

Table 2-7 Call Features Supported by TDM PBXs

AvayaCommunications

Manager

NortelCommunicationsServer 1000

CiscoCUCM

CiscoCME

Basic Call ControlInbound Calls,Outbound Calls,Caller ID

Yes Yes Yes Yes

Call TransferBlind

Yes Yes TBD TBD

Call TransferConsultive

Yes Yes TBD TBD

Call Forward(CFNA, CFB,CFNR, and CFU)

Yes Yes Yes Yes

Multi-party CallAppearance

Yes Yes Yes Yes

E911 Yes Yes Yes Yes

DTMF Tones Yes Yes Yes Yes

Call Restriction Yes Yes Yes Yes

Ad Hoc ConferenceCall

Yes Yes TBD TBD

2-16 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide IP-PBX

IP-PBX

An IP-PBX is a third-party provided SIP-based network element that provides general telephony servicesto the Enterprise solution. IP-PBXs packetize voice for transport through the IP network and connect theEnterprise IP telephony system to the PSTN. This PBX operates both on a circuit-switched platform tothe PSTN, and on VoIP through IP ports. Current IP-PBX functionality combines a traditional telephoneswitch with a new set of capabilities for VoIP calls as well as standard analog and digital calls.

The IP-PBX partner supplies the IP-PBX components, operating system, software releases, and additionalsoftware. Generally, an IP-PBX comprises a signaling server and media gateway subcomponents.

Avaya PBX Solutions

The Avaya PBX includes both hardware, (Media Servers, and Media Gateways) and software (theAvaya Communication Manager with Avaya Off-PBX-Station (OPS)).

• Avaya Media Servers— A line of media servers that supports distributed IPnetworking and centralized call processing across multiprotocol networks. Avayamedia servers have the following features and benefits:

◦ Redundant, survivable call processing, and media processing.

◦ Standards-based computing supports Linux, Microsoft Windows,and an Avaya Media Server

◦ Distributed survivable IP networking supports campus, multisite,and branch environments.

• Avaya Media Gateways— Handle the tasks of packetizing voice for transport thoughthe IP network and connecting the Enterprise IP Telephony system to the PublicSwitched Telephone Network (PSTN). Avaya media gateways support both bearerand signaling traffic that are routed between packet- and circuit-switched networks.Avaya media gateways have the following features and benefits:

◦ Interoperable with standards-based data networks

◦ Stackable, modular, and configurable component solutions

◦ Redundant capabilities

◦ Distributed networking

Avaya IP-PBX Specifications

The Avaya IP-PBX specifications are as follows:

• Hw:—S8300 / S8500 / S87XX

• Sw: Communications Manager 4.X and later

IP to TDM Gateways

Customers with legacy PBX systems operating on circuit-based TDM can adapt to the TEAMsolution. TDM Gateways allow the WSM to talk to a non-IP-PBX system. TEAM supports selectTDM-based PBXs using a SIP Gateway product (Dialogic Gateway).

68009260001-A January 2009 2-17

Dialogic Solutions Chapter 2: Theory of Operations

Dialogic Solutions

A Media Gateway is a telephony gateway appliance that connects to one or more TDM PBXs through itstelephony interfaces and connects to the LAN through a 10 BaseT or 100 BaseT Ethernet connector.

The Media Gateway provides an inexpensive bridge between a legacy PBX or PSTN and a managedpacket network. The Media Gateway converts signals from circuit-switched equipment into eitherH.323 or SIP standard protocol for transmission over a LAN to communications devices such asIP phones, wireless phones, and IP servers in almost any location.

The Dialogic® 2000 Media Gateway Series (DMG2000) merges traditional PSTN technology withIP networks. The Dialogic gateway models that work with TEAM include:

• DMG2030DTIQ: The single span (1 T1)

• DMG2060DTIQ: The dual span (2 T1s)

• DMG2120DTIQ: The quad span (4 T1s)

See http://www.dialogic.com/support/helpweb/mg/default.htm for more details.

Cisco PBXThe TEAM Solution supports two Cisco PBXs:

• The router based Cisco Media Express (CME) provides basic PBX functionality

• The Cisco Unified Call Manager (CUCM) provide robust and flexible PBX functionality

For more information regarding the Cisco CUCM 5.1 or Cisco CME PBX, refer to the Cisco customerdocumentation website at: http://www.cisco.com/univercd/home/home.htm

Nortel PBXFor more information regarding the Nortel CS1000 (version 4.5 and later releases), refer to the Nortelcustomer documentation website at: http://support.nortel.com/go/main.jsp?cscat=OVERVIEW&poid=14261

Telephony-Related ServersThis section contains information about servers that perform tasks related to telephony.

Voice Mail Server

Voice Mail Server is supplied by the PBX vendor or the Enterprise. The Voice Mail Serverprovides voice mail indication and Message Waiting Indication (MWI).

2-18 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide CDR Processing Server

The PBX has the sole connection to the Voice Mail Server. It forwards any unanswered calls to theVoice Mail Server, where a caller can leave a message. The Voice Mail Server sends an MWI to therecipient phone, through the PBX and WSM, to display an icon indicating that a message has been leftfor the recipient. When the recipient calls into the Voice Mail Server and listens to the message, theserver sends a new MWI to clear the display on the recipient’s TEAM smartphone.

CDR Processing Server

Call Detail Records (CDRs) are an effective mechanism to analyze subscriber usage in the TEAMsolution. CDRs are generated by the IP-PBX for telephony calls traversing it and are stored onthe IP-PBX. They are also generated by the WSM for telephony calls that stay within the mobileenvironment controlled by the WSM and for WSM controlled PTT calls. The WSM createdrecords are stored on the AAA using its accounting functions.

In the TEAM solution, the main CDR function for telephony is normally carried out by the CDRmodules in the PBX. However, when the TEAM smartphones are not configured as extensions inthe PBX (that is, when mobile-to-mobile calls are not routed through and not monitored by thePBX), the TEAM WSM can be enabled to generate telephony call accounting information (CallDetail Records) through an interface to a compliant AAA/RADIUS server.

Like other typical call accounting practices by PBX vendors, the CDRs are then transferred from theAAA/RADIUS server to the Accounting Server for correlation and further processing. Once the CDR Datahas been transferred, the Accounting Server can generate the reports needed for further accounting purposes.

Enterprise Billing Server correlates the stored data on the AAA/RADIUS server and other call accountingsources (such as, the data from the PBX). It also converts the CDR data sets into the CDR data formatspecified by the Enterprise customer. The correlation and formatting procedures are dependent onthe specific AAA/RADIUS servers and Billing Servers used by the Enterprise. Examples of typicalmethods include custom correlation/conversion scripts and UI-based procedures.

For a list of standards/Internet RFCs and drafts that the AAA server needs to support to beinteroperable with TEAM solution, see "RADIUS (AAA)" on page 2-11.

Directory Server

The Directory Server is a network server that provides a directory service or a naming service. Itcentralizes the maintenance of data to a single location. It allows mapping of multiple pieces ofdata within the Enterprise database to a single attribute in the directory and defines a way of settingthe directory account properties such as user password or login access.

In the TEAM solution, a Directory Server interface is needed to capture and keep history; for example, togenerate a bill. Subscribers are entered into the Directory Server to support address books, and so on.

Other Enterprise ServersOther Enterprise Servers are optional servers, such as, third-party Network Management,Device/System Provisioning/Management, e-mail, and IM.

68009260001-A January 2009 2-19

Network Management Chapter 2: Theory of Operations

Network Management

Motorola provides the NSM application for network management activities. If an integrated system view ofother system components is required, that is, of an Enterprise management system, you could use a product likeHP OpenView that manages different system elements using Simple Network Management Protocol (SNMP).The NSM supports an Enterprise management system by supporting remote GUI access and forwardingSNMP events to the customer’s management tools. If your system requires an Enterprise management system,work with your WLAN and PBX vendors to integrate those also into the overall management system.

Device/System Provisioning/Management

The Device/System Provisioning/Management client on the TEAM smartphone allows a remoteadministrator to install, remove, and configure applications as well as to set TEAM smartphone registrysettings and check TEAM smartphone status information such as power and battery levels. It runs as atimed background process. The process starts after a configurable interval to connect with the DeviceManagement server to post information and check for new instructions. The Device Managementclient uses HTTP/HTTPS to connect to the server. The Device Management client may also monitorthe network connection for activity using standard WinCE API calls and throttle itself appropriatelyto ensure that it does not interfere with user-initiated network activities.

The section includes the following topics:

• MSU

• MS SMS

Motorola SW Update (MSU)

A provisioning tool from Motorola that provides the latest approved software for devices in warranty.To access the MSU, refer to Motorola’s Support Central Web site.

MS Text Messaging and New Initiative

MS SMS is a systems management software product, from Microsoft, for managing large groupsof Windows-based computer systems. SMS provides functionalities such as remote control, patchmanagement, software distribution, and hardware and software inventory.

Email

The e-mail server is supplied by the Enterprise. The server include support for PostOffice Protocol (POP3) for the TEAM smartphone.

Microsoft Exchange

Microsoft Exchange Server is a possible vendor-specific e-mail server for use in the TEAM solution.Microsoft Exchange is an e-mail server that hosts the subscriber’s Enterprise e-mail account. The EnterpriseExchange Server is accessed by TEAM smartphones when using Wireless Data Applications.

2-20 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide MS LCS and Others

MS LCS and Others

MS LCS is a third-party web conferencing and chat server that can be integrated with existing PBXs. An InstantMessaging (IM) Presence server runs on an exchange server. The IM client also shows presence information.

Backhaul Network Equipment■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The backhaul network is the wired LAN. The backhaul network is used to move traffic from a TEAMsmartphone and WLAN to servers. It encompasses equipment that is not part of the Wireless LAN (WLAN).The customer supplies and maintains their own backhaul. TEAM has a vendor-agnostic approach to thebackhaul network, which means that customers can reuse existing equipment or order equipment from multiplevendors, if the equipment meets the requirements specified in "WLAN and Backhaul Network Specifications".

In the TEAM solution, the WLAN drives the backhaul requirements. If capacity increases inthe WLAN, then the backhaul needs to expand to manage the traffic.

The backhaul network equipment includes:

• Routers

• Switches

• Other networking gear

The backhaul network is of two types:

• Local backhaul (layer 2), from the AP to the switch, which uses VLAN and switching.

• Wide-area backhaul (layer 3) for cross-regional or wide-area sites.

Quality of Service (QoS) is a requirement when setting up the backhaul. If an Enterprise uses a centralizedTEAM deployment model, where the TEAM solution in located in a hub and spokes radiate from the hubto where various sites are located from which WLAN traffic needs to be supported, then the signalingand voice traffic need to be backhauled to/from the WSM/TEAM smartphones.

Routers and switches comply with standards for QoS settings. For more informa-tion, see "Routers" and "Switches".

For the voice traffic, the network mechanisms used to isolate and prioritize traffic within a given site (forexample, VLANs) will probably be different from what is done with wide-area traffic, where Layer 3routing is often done (and VLANs are not typically used). Also, the wide-area network may not use802.1 Q/p, but instead it may use other means to do gross or simple traffic prioritization.

68009260001-A January 2009 2-21

Routers Chapter 2: Theory of Operations

In certain situations, QoS may not be available over the backhaul portion of the network. In such asituation, if the user wants the WSM and the TEAM smartphones to talk cross sites, the signaling(setup) and bearer (audio) traffic may encounter significant QoS issues for both cross-site PTT andcross-site interconnect. This needs to be recognized and dealt with before a system deployment.

RoutersRouter selection and planning requires knowledgeable Network administrators and assurance thatquality routers are selected. If any point of the communication path does not support QoS, then theeffect is to not have QoS on that path. The effect on the voice traffic is to deprioritize the packetswhich then have additional jitter and delay. Deprioritization of the packets causes the audio to degradeand may manifest as drop outs and additional noise in the background.

SwitchesNetwork switches are supplied by the Enterprise. The switches/infrastructure must becapable of interfacing with the following:

• 10/100 Ethernet for IP-PBX, network management, and accounting.

• 1000 GB Cu/Fiber for Access Point (AP) controllers.

The switches/infrastructure must be capable of supporting:

• QoS DiffServ at layer 3 and IEEE 802.1Q at layer 2.

• Devices that span QoS mechanisms (multi-layer switches) may also need tomap DiffServ Code Points (DSCP) to 802.1Q/p.

WLAN Equipment (Multiple Vendors)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The WLAN network consists of a set of wireless Access Points, AP controllers (depends on the vendor),and wireless-enabled switches. These elements essentially form the part of the network that handlesmicromobility. This section explains key supported third-party solutions, and their role in the TEAM solution.

The Enterprise can choose from multiple vendors, but cannot deploy disparate equipmentfrom different vendors. Consistency is important to maintain QoS. Current industry standardsdo not enforce compatibility between vendor solutions.

2-22 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide WLAN Equipment (Multiple Vendors)

The WLAN infrastructure is responsible for maintaining reachability to the TEAM smartphoneat its currently assigned IP address. WLAN equipment includes:

• APs—Layer 1 to Layer 3 interface that allows the TEAM smartphone wire-less access the Enterprise network.

• AP controller/gateways—WLAN access point concentrator that controls AP functionsand interfaces to the core, wired Enterprise network.

• Additional wireless switches.

Table 2-8 includes the network elements tested by Motorola to verify proper system operation. Thisequipment meets expectations with respect to battery life, call quality, and coverage.

Table 2-8 Supported WLAN Vendors

Vendor Model/ Model seriesWS5100 + AP300

RFS7000 + AP300

Motorola/Symbol

RFS6000 + AP300

CCX compliant controllers and Access pointsCisco

Cisco Wireless LAN Controller Series 4400+LWAP 1030e including 1230/1240 seriesreflashed as LWAP

TEAM solution utilizes WMM Power Save (WMM-PS) to maximize battery life of the subscriber units.

Coverage prediction and measurement can be part of sold services from Motorola (for more information,contact your Motorola account manager), third-party contracted services, or a combination of both.

Call quality depends on call capacity, call coverage, and options chosen within the infrastructure.The call quality can be a part of sold services. However, if the coverage is good, the capacityis adequate, and options like QoS support within the Enterprise Network are supported bythe core routers, then you will have good call quality.

Some configuration steps are out of scope of this documentation and are left tothe customer/3rd party contractor to set up.

Minimal configuration requirements include:

• Security implemented on the TEAM smartphone that matches the security setup within the WLAN. For example, if the TEAM smartphone is set up withWPA2 Enterprise, so should the WLAN.

• The infrastructure must include WMM (including PS), WMM-AC, and QoS.

• L3 tunneling is automatically provided from the WLAN between L2 networks (assumingthe deployment includes multiple L2 networks within the coverage area).

• 802.1x authentication of TEAM smartphone and network elements.

• The TEAM smartphone is provided with certificate-based authentication that mustbe implemented within the network deployment, that is, the TEAM smartphonecertificates must be installed on the AAA server.

68009260001-A January 2009 2-23

Industry Standard Requirements and Features Chapter 2: Theory of Operations

Industry Standard Requirements and FeaturesThe TEAM WLAN equipment must meet industry standard and provide required features. Thefollowing sections explain these requirements and features:

• "Minimum AP Requirements for Data Networks"

• "Recommended Capabilities"

• "Wireless Features"

• "Layer 2 Features"

• "Power over Ethernet (PoE)"

• "Policy Configuration"

Minimum AP Requirements for Data Networks

In addition to the support provided for a voice-enabled WLAN infrastructure, APs must meet theminimum requirements listed in the Table 2-9 to support the data network.

Table 2-9 Minimum AP Requirements for Data Networks

Data Network Features DescriptionEthernet, Fast Ethernet, GigabitEthernet

Need 100 Base-T to meet TEAM throughput calculations.The wireless switch may require Gigabit Ethernet.

Multiple Virtual Local AreaNetworks (VLANs) per port

Required for QoS, indicate how packets are markedfor priority. Data network must have End-to-End QoSSupport, Diffserv preferred. IP Precedence may be usableas an alternative. Systems supporting WMM ( WMM-PS) will be able to reach maximum quoted battery life. It isexpected for the WLAN to provide tunneling between L2(Layer 2) networks during a call and without requiring aDHCP release/renew.

RADIUS protocol for security Allows authentication to a RADIUS server to enable an802.1x-protected Ethernet port.

Stations Power Saving WMM-PS, U-APSD preferred.

Port Mirroring Gateways provide port mirroring for additional networkmonitoring functionality. You can filter traffic and mirroreither incoming traffic to the source port or both incomingand outgoing traffic. This allows you to select thenetwork traffic that you need to monitor. Port mirroringis useful for debugging.

WMM WMM allows the subscriber unit and the access pointto categorize messaging between the endpoints and toprioritize the messaging.

WMM-AC (Future) foradmission control/bandwidthreservation

It limits the number of simultaneous calls on a single AP.Admission control ensures that adequate bandwidth isavailable for a voice call and contributes to overall voicequality; this is known as bandwidth reservation. CiscoCCX has a version of admission control utilized by theTEAM solution.

2-24 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Recommended Capabilities

Recommended Capabilities

This section provides recommendations to ensure optimal performance of the TEAMsolution using a given vendor’s WLAN equipment.

The standards that equipment vendors must meet are:

• 802.11a, or 802.11b/g compliance

• 802.1x security compliance

• 802.1Q/p QoS/VLAN tagging compliance

• Inter-subnet AP handoff assist/tunneling

Wireless Features

The wireless features that must be supported in the TEAM WLAN equipment are:

• Multiple Service Set Identifiers (SSIDs)

• User Group Table

• Access Point Group

• Authentication and Encryption Modes

• Wireless Domain Parameters

• MAC Access Control List

• Rogue Access Point Detection

• RADIUS

• Configuration of APs

Layer 2 Features

The Layer 2 features that must be supported in the TEAM WLAN equipment are:

• Ethernet

• VLAN Configuration

• IEEE 802.1X

• MAC Aging

• Link Aggregation Group (LAG)

• Port Redundancy

• Multilayer Policy

• Port Classification

Power over Ethernet (PoE)

The PoE features that must be supported in the TEAM WLAN equipment are:

68009260001-A January 2009 2-25

Policy Configuration Chapter 2: Theory of Operations

• Load Detection

• Plug and Play Operation

• Powering Devices

• Power over Ethernet in Converged Networks

Policy Configuration

The policy configurations that must be supported in the TEAM WLAN equipment are:

• QoS policy configuration including Access Control Lists and Quality of Service Lists

• Defining Policy Lists

• Attaching Policy Lists to an interface

• Device-Wide Policy Lists

• Defining Rules

• Composite Operations

• DSCP Table

• Displaying and Testing Policy Lists

Motorola Enterprise WLANThe Motorola Enterprise division (formerly known as Symbol, see http://www.symbol.com/)is one of the possible WLAN vendors for TEAM.

Hardware

This section provides hardware details of the Motorola/Symbol WLAN hardware used in the TEAM solution.

Motorola/Symbol Access Points

Table 2-10 provides the specifications of the Motorola/Symbol WLAN APs used in the TEAM solution.

The AP-300 meet the following requirements:

• Speeds of up to 54 Mbps in both the 2.4 GHz and 5.2 GHz bands (dual band).

• 802.11a, 802.11b/g or both; the preferred solution includes both radios.

2-26 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Motorola/Symbol PoE Ethernet Switch

• Standards: WPA2, WMM.

Table 2-10 Motorola/Symbol — Access Point Specifications

Model Part Number

AP-300 with integrated antenna WSAP-5110-100-WWR

AP-300 with external antenna WSAP-5100-100-WWR

See http://www.symbol.com/ for detailed specifications.

Motorola/Symbol PoE Ethernet Switch

Table 2-11 lists the Motorola/Symbol ES3000 PoE Ethernet Switch used in theTEAM solution with specifications.

Table 2-11 Motorola/Symbol — PoE Ethernet Switch Specifications

Model Description Part Number CapacityES-3000 24 port L2 switch withPoE injector

ES-3000-PWR-10-WW 24 portsES-3000

ES-3000 with a US style powercord

ES-3000-PWR-USCORD


Motorola/Symbol RF Switches

Table 2-12 lists the Motorola/Symbol wireless RF switches used in the TEAM solution with specifications.

Table 2-12 Motorola/Symbol — RF Switches (Validated)

Model Description Part Numbers Software CapacityRedundant WS5100 WirelessSwitch

WS5100-RS-WWR Release3.X WiOS

48

6–Port WS5100 WirelessSwitch with six Access PortLicences

WS-5100-06-WWR

MOTO WS51000WirelessController

6–Port License Upgrade —AP licenses are available from6 to 48 APs in multiples of 6

WS-5100-UC-WWR.

68009260001-A January 2009 2-27

Cisco Chapter 2: Theory of Operations

Table 2-12 Motorola/Symbol — RF Switches (Validated) (Continued)

Model Description Part Numbers Software Capacity802.11 a/b/g connectedremotely, managed through athrough a Motorola wirelessswitch

—MOTO AP-300Access Port

Table 2-13 Motorola/Symbol RF Switches (not Validated)

Model Description Part Numbers Software Capacity

RFS7000 7000 is better when encryption isturned on. Premier solution, highcapacity.

TBD Release3.X WiOS

256

Support for up to four APswith PoE (for small systems/testdeployments)

WS-2000-SME-WWR —

WS2000 and 1 AP300 (802.11a/b/g)bundle

WS-2000-1C-ABG-WWR

WS2000 and 2 AP300 (802.11a/b/g)bundle

WS-2000-2C-ABG-WWR

WS2000 and 2 AP300 (802.11b/g)bundle

WS-2000-2C-BG-WW


CiscoCisco (http://www.cisco.com/) is one of the possible WLAN vendors for TEAM. Ciscois responsible for supplying the part numbers, equipment, software releases, and anyadditional software/options for the WLAN system.

Hardware

This section provides details of the Cisco WLAN hardware used in the TEAM solution.

2-28 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Cisco RF Switches

Cisco RF Switches

Table 2-14 lists the Cisco wireless RF switches used in the TEAM solution with specifications.

Table 2-14 Cisco — RF Switches

Model Description Part Numbers Software Capacity4400

series–4402Cisco 4400 Series Wireless LANControllers.2 GB Ethernet ports supportsconfigurations for 12, 25, and 50access points

AIR-WLC4402-12-K9for 12 Access pointAIR-WLC4402-25-K9for 25 Access pointAIR-WLC4402-50-K950 Access point

Release4.2 orabove

up to 50

4400series–4404

Cisco 4400 Series Wireless LANControllers4 Gigabit Ethernet ports supports 100access points

AIR-WLC4404-100-K9

Release4.2 orabove

100

See http://www.cisco.com/ for detailed specifications.

Cisco Access Points

Table 2-15 provides the specifications for the Cisco APs used in the TEAM solution.

Table 2-15 Cisco — Access Point Specifications

Model Part Number

1131AG 802.11a/g Non-modular LWAPP AP: Integrated AntennasAIR-LAP1131AG-x-K9 LWAPP x=

• A=FCC

• C=China

• E=ETSI

• I=Israel

• J=TELEC (Japan)

• K=Korea

• N=North America (Excluding FCC)

• S=Singapore

• P=Japan2

• T=Taiwan

1242AG 802.11a/g Non-modular LWAPP AP; RP-TNCAIR-LAP1242AG-x-K9 x=

68009260001-A January 2009 2-29

WLAN and Backhaul Network Specifications Chapter 2: Theory of Operations

Table 2-15 Cisco — Access Point Specifications (Continued)

Model Part Number

• T=Taiwan

• A=FCC

• C=China

• E=ETSI

• I=Israel

• J=TELEC (Japan)

• K=Korea

• N=North America (Excluding FCC)

• P=Japan2

• S=Singapore

Antennas for 5 Ghz with 1242AG include:

• AIR-ANT5135D-R

• AIR-ANT5135DG-R****

• AIR-ANT5135DW-R

Antennas for 2.4 Ghz with 1242AG include:

• AIR-ANT4941

• AIR-ANT2422DG-R**

• AIR-ANT2422DW-R

See http://www.cisco.com/ for detailed specifications. Verify all the partnumbers as they may change.

WLAN and Backhaul Network Specifications■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The network infrastructure switching and routing equipment is supplied by the Enterprise. To fullymaintain the end-to-end QoS required for the TEAM smartphone operation, this network infrastructureshould support DiffServ at layer 3 (routing) and IEEE 802.1Q at layer 2 (switching).

2-30 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide TEAM smartphone

The 802.1Q/p marking occurs at the AP to Network (802.3) interface where the WMM access categoriesare mapped into 801.1Q priority. The TEAM smartphone utilizes AC_VO and AC_BE classes ofservice within WMM. The 802.1Q marking is also the mechanism used by IP Precedence on olderwired backbone infrastructure networks to prioritize traffic. The TEAM smartphone, WSM and IP-PBXalso preset the DiffServ Code Point value into the packet header on any originated packets to assistDiffServ Network Infrastructures to prioritize network traffic on newer networks.

TEAM smartphone■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The TEAM smartphone is a small wireless telephone that supports the voice over WLAN mobility solution.

Key features such as call transfer, and call hold are available at the touch of a button. Session InitiatedProtocol (SIP) support is included, and it works with the other solution components to handle callrouting. Table 2-16 lists the TEAM smartphone models that are supported:

Table 2-16 TEAM smartphone Models

Model Notes:EWP1000 Professional with 1400 mAh battery

EWP1100 Professional with 1700 mAh battery

EWP2000 Semi rugged, with 1400 mAhbattery

EWP2100 Semi rugged, with 1700 mAhbattery

Technical SpecificationsTable 2-17 lists the major technical specifications of the TEAM smartphone.

Table 2-17 Technical Specifications

Specification DescriptionForm Candy bar – rugged and non-rugged

Bands/Modes WLAN Tri – Band 802.11a/b/g

Chip sets • Apps – TI OMAP 2420

• WLAN: TI 1253FE

• Bluetooth: Broadcom BCM2045

• PWR MGMT: TI TWL92230

68009260001-A January 2009 2-31

Features Chapter 2: Theory of Operations

Table 2-17 Technical Specifications (Continued)

Specification DescriptionWeight • 145 g / 4.9 oz (EWP1000 – non-rugged)

• 160 g / 5.42 oz (EWP2000 – rugged)

Dimensions(H x W x D)

120 x 52 x 17.2 mm/4.7 x 2 x 0.7 inch (EWP1000 with1400mAh battery)120.5 x 54 x 18.6 mm/4.74 x 2.11 x 0.73 inch (EWP2000with 1400mAh battery)

Display 2 inch, 320 x 240 265K TMR color display

Platform/OS Microsoft Windows 6.1

Memory 128 MB RAM/256 MB RAM, built-inMicro-SD removable memory card slot (up to 2 GB)

Keyboard Numeric

FeaturesTable 2-18 lists the major features of the TEAM smartphone.

Table 2-18 Features of the TEAM smartphone

Feature DescriptionDurability Meets indoor MIL specs (EWP2000 only)

Battery life Depending on your system parameters and battery type, you can expect thefollowing talk times, for voice and data calls.

• 1480mAh battery

◦ Talk Time: 6.5 hours (voice and data)

◦ Standby time: 140 hours

• 1750mAh battery

◦ Talk Time: 8 hours (voice and data)

◦ Standby time: 180 hours

Battery type Std 1400 mAh/1700 mAh Excap battery

Browser HTML/WAP 2.0 compliant

Audio Toll quality voiceHigh audio speaker phone

TextMessaging

Inside Enterprise text messaging

PTT • PTT button – Private Call with Call Alert

• Group Call to up to 255 groups

2-32 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Photo

Table 2-18 Features of the TEAM smartphone (Continued)

Feature DescriptionEnhanced UserInterface

• Click to call/Click to message

• PTT and text messaging UI enhancements

• UI capabilities – call dialer, multiple line appearances, and textmessaging

Connectivity Mini-USB, PTT headset jack, Bluetooth class 2, 802.11 a/b/g

IntegratedApps

Telephony, PTT, voice recognition, document editing, support forthird-party LOB application

Accessories Mini-USB, single unit desktop charge, 6-slot Desktop Charger (EWP2000only)

PhotoThis section provides two photos of the TEAM smartphone.

Figure 2-5 shows the front view of the EWP1000 series smartphone.

Figure 2-5 Front View of the TEAM Smartphone

Figure 2-6 shows the menu view on the EWP1000 series smartphone.

68009260001-A January 2009 2-33

Software Chapter 2: Theory of Operations

Figure 2-6 Menu View on the TEAM Smartphone

SoftwareThis section covers the software details of the TEAM smartphone.

VoIP Client — Voice Client

The TEAM smartphone contains an embedded Voice Client, which provides the following:

• Motorola customized UI based on Windows Mobile 6.1

• Toll quality voice communications (VoIP)

• Text messaging

• Seamless voice mobility to maintain a call while roaming between access points and subnets

• Optimized roaming and mobility through a motion prediction algorithm

• Secure connectivity to the WLAN

Key platform features include:

• Microsoft Windows Mobile 6.1

• WLAN VoIP – Best in class audio with dynamic QoS

• Micro Mobility Adaptation Framework

• 802.11 a/b/g + bluetooth support and co-existence

• Security – WPA, WPA2

• QOS – Wi-Fi Multimedia (WMM)

• Power Management – WMM power save, Motion Prediction Algorithm

The Voice Client provides the following key functionalities:

• Decides when and how to perform AP to AP handoffs

2-34 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Screenshots

• Has key security enhancements, such as TLS signaling encryption to prevent userspoofing. TEAM uses the encryption features of the WLAN and the associatedWindows Mobile drivers to ensure that subscribers have the option to encrypt allWLAN traffic using higher security methods such as WPA.

Screenshots

This section provides a few screenshots of various menu options of the TEAM smartphone.

Figure 2-7 shows a view of the Callers screen.

Figure 2-7 View of Callers Screen

Figure 2-8 shows a view of the Active Call screen.

Figure 2-8 View of Active Call Screen

Figure 2-9 shows a view of the Contacts screen.

68009260001-A January 2009 2-35

Quality of Service (QoS) Chapter 2: Theory of Operations

Figure 2-9 View of Contacts Screen

Figure 2-10 shows a view of the Call on Hold screen.

Figure 2-10 View of Call on Hold Screen

Quality of Service (QoS)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section provides an overview of Quality of Service (QoS) and its application across the TEAM solution.

IntroductionThe primary purpose of QoS is to ensure clarity of voice quality and quality of experience for subscriberwithout hindering the efficient working of the Enterprise network dictate.

Each component of the solution has a role in maintaining proper QoS functioning. TEAMspecifies the required QoS settings for Enterprise networks and equipment, and engineers theproper QoS operation in TEAM supplied equipment and devices.

QoS involves:

• Reserving bandwidth

2-36 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide QoS Mechanisms for the Wireless LAN

• Packet classification

QoS includes precisely defined sound and delay requirements and well thought out network elementconfigurations. Continual QoS monitoring ensures that parameters are adjusted as network conditions dictate.The Enterprise can purchase tools to continually monitor QoS (Motorola does not provide this capability).When QoS does not meet expectations, the network can be reconfigured to ensure that it does.

As part of the various mechanisms for QoS, the WLAN equipment and IP-PBXs are considered the trustboundaries. The term trust boundaries are used to imply that they are trusted (from a security and QoS pointof view) with assigning the priorities for the Media Access Control (MAC) frames and IP packets.

Particular qualities of service are determined at the endpoints (for example, IP-PBX) of the network.Through mapping schemes, the endpoints classify, prioritize, and mark packets based on the neededQoS. Each network element that has QoS functionality honors (and sometimes changes) these markingsthrough pre-specified behaviors. Each network element is continually monitored.

QoS Mechanisms for the Wireless LANQoS mechanisms between the TEAM smartphone and the AP/Gateway are derived from the 802.11especification. Virtual LAN priorities are used between the AP/Gateway and the rest of the network.

Packet ClassificationMost packet classification and marking is done at the TEAM smartphone and the IP-PBX. Each deviceis classified based on the application/port mapping to a Differentiated Service Code Point (DSCP), andit selects the DSCP and inserts it in the IP header for all of the packets in the flow.

When the packets enter the VLAN, the device maps the DSCP over to the appropriate VLAN priorities.

Access Point/Gateway Bandwidth ReservationBandwidth reservation occurs as part of the Wireless LAN (WLAN) operation. Bandwidth reservation,combined with admission control, is needed for the airlink. The procedure is defined by a specification, so it isnecessary for the access points to support it. There may also be some type of configuration needed in theaccess point to enable the feature. The AP/Gateway requires bandwidth reservation to ensure that:

• The requested QoS is maintained for the packet flow in question.

• Adequate bandwidth is available for handovers.

Bandwidth reservation for the AP/Gateway is dependent on the implemen-tation of schedulers and policies.

68009260001-A January 2009 2-37

911 Dialing Chapter 2: Theory of Operations

Solutions selected for implementation must comply with the current standards definitionsfor voice QoS in the WLAN environment. Interworking with LAN equipment thatdeploys standards-based QoS solutions are expected.

Bandwidth Reservation currently only exists within Cisco Certified Extensions(CCX) for Cisco WLAN deployments. With the adoption of WMM-AC this willalso extend to other vendors, such as Motorola/Symbol.

911 DialingA WLAN subscriber can use the 911 call feature to make an emergency 911 call from the Enterprise WLAN.The PBX sends a single number to the Public Safety Answering Point (PSAP). This number corresponds to acaller’s location. If the call accidentally drops, the PSAP agent calls back and the return call from the PSAP isforwarded to the subscriber who dialed 911. If two different TEAM smartphones call 911 from the samelocation, the PBX sends the same location number for both the calls. If both calls drop and the PSAP agent callsback, the solution only rings the last TEAM smartphone to drop the 911 call, not both TEAM smartphones.

Section 508 ComplianceTEAM provides teletypewriter support in SIP and Real-time Transport Protocol (RTP) to comply with theSection 508 of the Rehabilitation Act of 1973. Section 508 requires that when Federal agencies develop,procure, maintain, or use electronic and information technology, employees with disabilities have accessto and use of information and data that is comparable to the access and use by employees who are notindividuals with disabilities, unless an undue burden is imposed on the agency. Section 508 also requiresthat individuals with disabilities, who are members of the public, seeking information or services from aFederal agency, have access to and use of information and data that is comparable to that provided to thepublic who are not individuals with disabilities, unless an undue burden is imposed on the agency.

IPsec Requirements■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

IPsec is a network layer security protocol with the following major components:

• Authentication Header (AH) and Encapsulating Security Payload (ESP)for data protection facilities

• Internet Key Exchange (IKE) for key management

There are two modes of operation:

2-38 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide IPsec Between NSM-WSM

• Transport (protecting payload)

• Tunnel (protecting entire IP datagram)

In a TEAM solution, IPsec is used to establish secured links between the WSM -NSM, and between the WSM-PBX.

IPsec and the related protocols are commonly available as network services to boththe platforms of the WSM and the NSM.

IPsec Between NSM-WSMInformation necessary for managing the WSM application is communicated through a connection betweenthe WSM and NSM. Since voice service is a critical Enterprise capability, securing the management ofvoice services is important to enterprises. IPsec is a means of creating a secure connection. IPsec can beset up on the Site Admin tool using a key to provide full encryption between NSM and WSM.

The following NSM-WSM interfaces are protected at the IP layer using IPsec:

• NSM-WSM activation interface

• NSM-WSM file transfer

• NSM-WSM network management

• NSM-WSM provisioning interface

IPsec Between WSM-PBXIPsec is used to establish secured links between the WSM and a PBX that supportsonly the IPsec security option (no TLS).

For SIP signaling security, use the IPsec ESP protocol in transport mode for securing the signaling pathbetween the WSM and the PBX, when TLS/TCP is not supported by the partnering PBX. The transport modeis easier to set up and more appropriate for securing the targeted end-to-end connection between the two nodes.

68009260001-A January 2009 2-39

IPsec Between WSM-PBX Chapter 2: Theory of Operations


2-40 68009260001-A January 2009

Chapter

3Planning for Deployment

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

The chapter explains the important points to consider while planning for deployment of the TEAM solution.

Assessing Your Environment■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The TEAM solution can be deployed in any of the following types of environments:

• New building with no existing WLAN or PBX infrastructure.

• Existing building with no WLAN or PBX infrastructure.

• Existing building with WLAN and/or PBX infrastructure.

Planning for Implementation■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Consider the following points when planning to implement the TEAM solution:

• Existing infrastructure —

◦ Perform VoIP assessment—The existing wired, wireless, and telephony infrastructuresshould be evaluated for voice readiness. This involves the analysis of the existingwired and wireless network and telephony infrastructures and any recommendationsfor changes or additions to support the TEAM VoIP solution.

◦ Perform network planning and design — If additions or changes to the existing wiredor wireless infrastructure are required, network design will be required to identify wiredand/or wireless network changes such as the addition of Access Points (APs), addition orreconfiguration of switches or routers, or the addition of an IP PBX or TDM Gateway.

68009260001-A January 2009 3-1

Installation Activities Chapter 3: Planning for Deployment

• New deployment —

◦ IP telephony or a TDM Gateway—Besides supporting mobility, IP telephony providesnumerous other benefits. These systems support a full complement of telephonyfeatures and call processing functions, and deliver these across the Enterprise IPnetwork. A converged voice/data network simplifies network administration andreduces the cost of endpoint moves, adds, and changes. Significant savings arepossible by routing IP voice calls over the corporate data network, instead of the costlypublic toll network. If an update to IP telephony is not feasible, a TDM gateway canprovide the ability to deploy the TEAM solution with a TDM PBX.

◦ WLAN design—Designed from ground-up to support voice traffic, the WLANdelivers critical features such as intelligent no delay roaming, load balancing, advancedquality of service and end-to-end security. Additionally, centralized security andmanagement capabilities have many benefits for traditional data applications.

Installation Activities■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following sections explain the installation activities that range from initial site install/pre-sale activities to verification of the compatibility of the hardware/software components(provided by the Enterprise) with the TEAM solution.

Initial Site Install/Pre-saleInitial Site Install/Pre-sale items can be sold services from Motorola (for more information,contact your Motorola account manager), third-party contracted services, or a combination ofboth. These services would typically include the following activities:

3-2 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Initial Site Install/Pre-sale

• Characterization of the existing LAN for voice traffic – This may have to be extended to acomprehensive plan to include additional LAN ports needed to interface APs, additionalbandwidth concerns, and additional IP addressing concerns. This should also work withDeployment Loading tools to avoid re-entering common information. The DeploymentLoading tools are used by the end-customer’s planning team and/or System Integration (SI)vendor.

Motorola RF Design software is used for measuring the existing environment(sniff) and planning (layout) the network(s); for more information, visitwww.motorola.com/RFdesign. Tools include:

◦ Motorola LANPlanner – used to design, plan, and optimize the network.

◦ Motorola SiteScanner – used to simulate network activity and performsite surveys for 802.11 Wi-Fi networks.

◦ OmniPeek – used for Wi-Fi and Ethernet sniffing (EtherPeek andAiroPeek are now OmniPeek).

◦ Wireshark® (formerly Ethereal®) – used for Ethernet sniffing.

◦ AirMagnet®, GL Communications, VXVoice, and ixChariot® – used for variousvery low level assessments of network and audio performance.

• Identification of existing customer LAN servers (vendor, platform, and software release)for compatibility and capacity for a WLAN solution. This includes:

◦ Authentication, Authorization, and Accounting (AAA) server

◦ Domain Name Services (DNS) server

◦ Dynamic Host Configuration Protocol (DHCP) server

◦ E-mail server

◦ Voice Mail server

◦ Network Time Protocol (NTP) server

◦ IP-PBX/Analog PBX

◦ Directory server

◦ Existing WLAN infrastructure

• Identification of existing customer accounting interface

68009260001-A January 2009 3-3

Compatible Hardware and Software Versions Chapter 3: Planning for Deployment

Compatible Hardware and Software VersionsTable 3-1 provides references to more information about hardware and software versionsthat are compatible with the TEAM solution.

Table 3-1 Compatible Hardware and Software Versions

Layer Component Hardware and SoftwareVersions

Wireless Services Manager (WSM) Motorola - supplied appliance,Motorola-supplied appliancesoftware. See"TechnicalSpecifications" on page 2-6.

Network Services Manager (NSM) Enterprise-supplied server,Motorola-supplied server software.See "NSM Server HardwareRequirements" on page 2-8.

Control Servers (DHCP, DNS, AAA,NTP)

Enterprise-supplied servers. See"Enterprise Control Servers" onpage 1-7.

PBX (Telephony Servers) Enterprise-supplied servers. See"PBX (Telephony Servers)" on page2-13.

Telephony Related Servers(Voicemail, CDR, Directory)

Enterprise-supplied servers. See"Telephony-Related Servers" onpage 2-18.

SolutionEquipments

Other Enterprise Servers Enterprise-supplied servers. See"Other Enterprise Servers" on page2-19.

Routers Enterprise-supplied routers. See"Routers" on page 2-22.

CommunicationBackhaul

Switches Enterprise-supplied switches. See"Switches" on page 2-22.

Wireless LAN(WLAN)

Enterprise-supplied WLANequipment. See "WLANEquipment(Multiple Vendors)" on page 2-22.

3-4 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide IP Evaluation and Planning

IP Evaluation and Planning■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Part of IP planning is to evaluate the customer’s IP scheme and provide recommendationsfor creating an IP plan for the solution.

While creating an IP plan, consider the following:

• Determine the number of IP addresses required to support the WLAN.

• Determine the need for multiple subnets.

• Decide the route the traffic uses to tunnel from WLAN coverage areas to the backendequipment (NSM, WSM, DNS/DHCP/AAA, and so on).

• Determine if the Enterprise IT department will create VLANs to support the IP traffic.

• Check if helper addresses are required to route the IP traffic appropriately.

• APs are layer 2 devices – No IP addresses required.

• Determine the need for IP network evaluation (whether the current network canhandle the additional capacity of adding VoIP).

• Check if the network supports 802.1 Q/p QoS. If not, check which QoS is supported.

Planning the WLAN NetworkThis section provides information needed to plan and set up theWLAN network. Whether augmenting an exist-ing infrastructure or implementing a newWLAN,Motorola recommends the following wireless design process:

Figure 3-1 Wireless Design Process

The following tasks need to be performed before installing the WLAN hardware:

• Ensure that adequate ports exist on the Ethernet switch for wireless switch uplinksand that Ethernet drops exist for the Wireless switch.

• Ensure the availability of space in data closets or other locations to place the wireless switches.

• Set up the mounting hardware for the AP mounting locations based on thesite survey. See “Site Surveys".

• Ensure Ethernet drops exist for each AP mounting locations.

In order to successfully set up your WLAN for TEAM, perform the following tasks:

68009260001-A January 2009 3-5

Considerations for the WLAN Chapter 3: Planning for Deployment

• Set default route for each AP.

• Select the wireless controller wireless domain name to use (if applicable).

• Document user/community names and passwords after you change the defaults.

Considerations for the WLANThe most critical element of the TEAM solution is deciding how the WLAN is either initiallybuilt or upgraded from a data-only network to one that supports both data and voice. Ifplanning is incomplete, the following problems may occur:

• Calls may be dropped.

• TEAM smartphones cannot get a connection to make a call.

• Call voice quality will be poor.

• Handoff within the network will be poor.

• Call security of the WLAN may not exist.

• Battery life of the TEAM smartphone will be poor.

Evaluating the Coverage AreaWhile performing an evaluation of the planned coverage area, check the following:

• Site survey to understand the current 802.11a/b/g coverage. See "Site Surveys".

• Existence of legacy wireless infrastructure. An Enterprise needs careful planningto reduce the risk of interfering with legacy internal wireless networks. Considerconflict with other wireless solutions, and keep RF low.

• Needs of the customers (number of subscribers, feature and services thatare provided, and protocol of choice).

Qualifying an Existing Infrastructure as Voice-CapablePerform the following checks to determine that the network infrastructure is voice-capable:

• Evaluate the WLAN.

◦ Ensure that the WLAN supports QoS (WMM/WMM-PS), and uses equipmentthat Motorola has either tested, or is in the same family as equipment tested byMotorola. For more details, see “Telephony-Related Servers.”

◦ Inventory the number and model of existing wireless clients, 802.11b,802.11g, and possibly 802.11a.

3-6 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Quality of Service Considerations

• Evaluating LAN

◦ Evaluate the existing PBX (circuit, packet, existing IP-PBX, capacity, interfaces,and so on) for upgrade, replacement, or co-location.

◦ Evaluate the customer’s existing LAN equipment. The LAN networkneeds to support QoS (802.1Q/p).

◦ Evaluate the customer’s existing network management system and capacity.If it is a network management system from another vendor, then re-usefor TEAM is outside the current scope.

• Conduct a site survey (which determines rough coverage, not precise AP locations).See "Site Surveys" for additional considerations.

Quality of Service Considerations

The Enterprise-provided WLAN equipment must meet Quality of Service (QoS) requirements. QoSis the prioritization of packets across a network. QoS becomes critical when voice is introducedover IP (VoIP). We need QoS in the infrastructure for the following reasons:

• If any point of the communication path does not support QoS, then the effectis the same as not having QoS on that path.

• The effect on the voice traffic is to deprioritize the packets, which then haveadditional jitter and delay. This causes the audio to degrade and may manifestas drop outs and additional noise in the background.

Site SurveysA Radio Frequency (RF) site survey is used to supply enough information to determine the number andplacement of APs to provide adequate coverage throughout the facility. Motorola offers tools that helpdesign and subsequently monitor WLANs. In addition, Motorola offers professional services to performsite surveys. For more information, contact your Motorola Account manager.

For WLANs, it can be difficult to predict the propagation of radio waves and detect the presenceof interfering signals without the use of test equipment. Even if you are using omni-directionalantennas, radio waves do not travel the same distance in all directions.

Walls, doors, elevator shafts, people, and other obstacles offer varying degrees of attenuation, which causes anirregular and unpredictable RF radiation pattern. As a result, it is necessary to perform an RF site surveyto understand the behavior of radio waves within a facility before installing wireless network APs.

In most implementations, adequate coverage means support of a minimum data rate. An RF site survey alsodetects the presence of interference coming from other sources that could degrade the performance of theWLAN. The need and complexity of an RF site survey varies depending on the facility. For example:

• A small three-room office may not require a site survey. This environment requiresa single AP located anywhere within the office to maintain adequate coverage. Ifthis AP encounters RF interference from another nearby wireless LAN, choosea different channel to eliminate the problem.

68009260001-A January 2009 3-7

General Steps to Conduct a Site Survey Chapter 3: Planning for Deployment

• A larger facility, such as an office complex, apartment building, hospital, or warehouse,generally requires an extensive RF site survey. Without a survey, subscribers can end upwith inadequate network coverage and suffer from low network performance in someareas. This may force rework to relocate and add APs to the facility after installingand interconnecting 20 APs or more, which is not desirable.

General Steps to Conduct a Site Survey

When conducting an RF site survey, consider these general steps:

1. Obtain a facility diagram— Before beginning the site survey, locate a set ofbuilding blueprints. If none are available, prepare a floor plan drawing that depictsthe location of walls, walkways, and any other obstructions.

2. Visually inspect the facility— Be sure to walk through the facility before performing any teststo verify the accuracy of the facility diagram. This is a good time to note any potential barriersthat may affect the propagation of RF signals. For example, a visual inspection will uncoverobstacles to RF such as metal racks and partitions, items that blueprints generally do not show.

3. Identify subscriber areas— On the facility diagram, mark the areas of fixedand mobile subscribers. In addition to illustrating where subscribers mayroam, indicate where they may not roam.

4. Determine preliminary AP locations— Consider the location of subscribers and rangeestimations of the WLAN products you are using, to determine the locations of APsto provide adequate coverage throughout the subscriber areas.Plan for some propagation overlap among adjacent APs, but ensure that channelassignments for APs are far apart to avoid inter-AP interference.

◦ Consider mounting locations, which could be vertical posts or metalsupports above ceiling tiles.

◦ Recognize suitable locations for installing the AP, antenna, data cable, and power line.

◦ Consider different antenna types when deciding where to position APs. An APmounted near an outside wall, for example, could be a good location if you usea patch antenna with relatively high gain oriented within the facility.

◦ Consider the worse case scenario in terms of subscribers and ensuring coverage.

◦ Use a tool, such as the Motorola LANPlanner to build an RF design.

3-8 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide General Steps to Conduct a Site Survey

5. Ensure WLAN equipment meets requirements that make it voice-capable:

◦ Include power requirements and power availability of WLAN equipment.

◦ Document A/C and floor space requirements, as well as distances to connect toLAN infrastructure (100 meter limits for 100BaseT and so on).

◦ Determine the number and type of existing wireless clients – 802.11 b/g/a.Describe existing wireless clients and estimate the total capacity.

◦ Identify any existing 802.11a/b/g APs to be upgraded for WLAN use (othervendors, older non-compliant APs, and so on).

It is unlikely that an existing WLAN will support a TEAM solution. MostWLANs will require new access points, switches, and network QoS.

6. Verify AP locations—This is when the real testing begins. Use a site survey tool available fromMotorola (Site Scanner - www. motorola.com/RFdesign) or from a third-party company. Forexample, Berkeley Varitronics Systems offers a line of handheld devices, such as Grasshopper,Scorpion, AirMagnet and Yellowjacket that provide advanced site survey functions.Install an AP at each preliminary location, and monitor site survey software readings by walkingvarying distances away from the AP. You do not need to connect the AP to the distributionsystem because the tests merely ping the AP. However, you need AC power. Note the data ratesand signal readings at different points as you move to the outer bounds of the AP coverage.

In a multi-floor facility, perform tests on the floors above and below the AP.

A poor signal quality reading indicates that RF interference is affecting thewireless LAN. This would warrant the use of a spectrum analyzer to characterizethe interference, especially if there are no other indications of its source.

Based on the results of the test, you may need to reconsider the locationof some APs and redo the affected tests.

7. Ensure smooth transition from subnet to subnet— Find locations to place APsto ensure seamless roaming throughout the building.

8. Document the findings— Once you are satisfied that the planned location of APs will provideadequate coverage, identify the recommended mounting locations on the facility diagrams.The installers will need this information. Also, provide a log of signal readings and supporteddata rates near the outer propagation boundary of each AP as a basis for future redesign efforts.

68009260001-A January 2009 3-9

Assumptions for Deployment Chapter 3: Planning for Deployment

Assumptions for Deployment

The WLAN must meet the minimum requirements listed in Table 3-2 to guarantee system performance.

Table 3-2 Minimum Requirements for System Performance

WLAN element Recommended CommentsCoverage with in afacility

Over 18 dB S/N in all areaswithin the Enterprise building.S/N = signal/noise anything lessthan 18 means poor coverage andpossible dropped calls.

This corresponds to an RSSIof approximately -70 dBm,given a typical noise floor of-88 dBm.

Adequate C/I(co-channelinterference, two APs ona channel will interfere,unless you install themfarther apart.)

Prefer 802.11a, where channelsdo not overlap or if using802.11b/g, use channels 1, 6, or11.

The frequency and power levelplan must seek to minimizeco-channel interference onall WLAN cells. 802.11 isa carrier-sense system, soit does not require a certainminimum C/I in order to work.The presence of interferingcells has an unpredictableeffect on system capacity andmay cause other unforeseenproblems.

The following must be considered with respect to WLAN requirements for TEAM performance:

• Ensure WLAN is designed to Voice specifications

• Motorola offers products and services to assist in the planning, deployment, andmaintenance of such WLANs. For example, Enterprise Planner product, RFMS, Intrusiondetection systems, and so on. See www.motorola.com/RFdesign.

• It is recommended to put TEAM traffic on 802.11a and keep data traffic especiallywith slower 802.11b devices, on 802.11b/g.

Placement of Access PointsTo derive a worst-case Micro- Mobility rate, an average AP coverage area must be determined. Assuminga worst-case building environment (for example, clutter, obstructions, and hostile building materials),average AP coverage could be limited to a 10-20 m radius, or an area of about 700 m2.

Depending on how AP channel reuse and AP Gateway redundancy plans are designed, a worst-casegeography could involve a subscriber walking down the hall to meeting room or cafeteria, alternatelybouncing between APs that belong to separate AP Gateways. This design must be avoided to eliminate thestrain on the system when the TEAM smartphones re-DHCP and SIP Register on AP Gateway changes. Thishallway scenario is challenging because it involves a burst of traffic every hour as persons enter the WLANcoverage area, walk to meeting rooms, go to the cafeteria for lunch, or leave work for the day.

The average cubicle size is about 7 m2. After adding space for cubicle halls, buildingcorridors, and meeting facilities, an average of about 10 people every 200 m2 can be supported.Therefore, APs can cover a rather large population.

3-10 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Roaming Across Access Points

Using this approximation, 700 m2 covers a population of approximately 35 people. Given traffic intensity persubscriber of 0.15 Erlangs, the average call load offered to the AP is 5.25. Handling this load requires 11servers (Erlang-B 1% blocking). The AP capacity for 18 simultaneous calls is therefore adequate in this case.

Placement of AP is best performed with a WLAN coverage estimation tool.

• Use of software, such as LANPlanner, allows installation and deployment teams to performdifferent scenarios prior to running cables and mounting hardware.

• Effects of existing wireless infrastructure can also be demonstrated prior to actual installation.

• Coverage and interference impact the best possible systems.

Roaming Across Access Points

When subscribers move from AP to AP in a subnet, the TEAM smartphone roams easily.This is called an intra-subnet handoff (Layer 2 mobility).

68009260001-A January 2009 3-11

Roaming Across Subnets Chapter 3: Planning for Deployment

Figure 3-2 Roaming Across Access Points

Roaming Across Subnets

A TEAM smartphone cannot change its IP address mid-stream when moving from one AP to anotheron different subnets. AP to AP tunneling allows this action without dropping the call. This functionality,called Inter-subnet handoff (Layer 3 mobility), is provided by the WLAN network.

3-12 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Why Use Multiple Subnets?

Figure 3-3 WLAN Deployment

Why Use Multiple Subnets?

A high number of subnets leads to more Layer 3 routing. A trade-off occurs betweenthe number of subnets and the coverage domain.

On a given subnet, all the subscribers hear all Layer 2 (L2) transmissions. This is due to the following:

• Broadcast packets sent to all destinations on L2 networks.

• Increased likelihood of collisions.

Do not use many subnets because:

• More routing between subnets may be needed while the TEAM smartphone is on a call.

68009260001-A January 2009 3-13

Frequency Bands Chapter 3: Planning for Deployment

• TEAM smartphone keeps the same IP address within a call, even when crossing L2 subnets.

• Routing packets consume the capacity of the wireless routers.

Frequency BandsThis section describes some of the common challenges of deploying systems in the 2.4 GHzand 5 GHz bands. Table 3-3 lists the frequency band challenges.

Table 3-3 Frequency Band Challenges

Standard Band Issue802.11a 5 GHz Does not have overlapping channels, but some adjacent channel

interference is possible.

802.11b 2.4 GHz • Channels in 2.4 GHz band overlap.

• Increased interference sources on the 2.4 GHz band, fromcordless telephones, microwave ovens, and Bluetooth devices.Bluetooth operation in the same band does consume bandwidth.Bluetooth headset operation can consume significant bandwidth,which may interfere with other TEAM smartphones co-locatedon a different 802.11b/g channel.

• Interference due to adjacent channel(s). Need four frequenciesto map a facility without overlap. Channels 1, 6, and 11 arecommonly used. Channels 1,4, 7, and 11 can also be used at 10%increase in interference, which may be reduced by choices ofadjacent channels.

802.11g 2.4 GHz • 802.11g must deal with the same interference sources as 802.11b.

• When 802.11g and 802.11b clients share a common 802.11b/gAP, some form of protection is required to avoid having 802.11bclients transmit on top of an 802.11g client transmission.

Considerations for Deploying 802.11a/b/g

The Enterprise needs to plan coverage around a mix of 802.11a/b/g access points. For a new install,the recommendation is to use primarily 802.11a or 802.11a with 802.11g (no 802.11b clients). Forexample, you can use four channels of 802.11a and four channels of 802.11g.

• 802.11a is the preferred solution for TEAM. 802.11a reduces the coverage footprint, one mustengineer for good coverage and capacity for where people walk in the Enterprise.

• 802.11g is preferred for coverage in long hallways.

For example, an Enterprise primarily uses a 2.4 MHz band (802.11b and 802.11g), which is extremelycongested. Deployers can modify the profiles of laptops with wireless access to disable the wireless whenthe laptop is connected to the LAN. Also, they can program APs to exclude some devices. This planallows laptops to access a wireless network while accommodating voice over WLAN.

3-14 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Firewalls

FirewallsData operations outside the Enterprise, such as Internet browsing, are possible becauseof firewall settings within the Enterprise.

If firewalls exist for LAN, Internet access, or WLAN, it is recommended to have the following information:

• Purpose of firewall (for example, Internet access, or to separate Human ResourcesLAN from Marketing LAN).

• List of the make, model, and software version.

• Check if ports 1719, 1720, and so on, are open or blocked.

• Check if Network Address Translation (NAT) is used.

• Location of the firewalls (indicate switch hostname).

Backhaul Network Considerations■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section includes considerations for the wired LAN network, including network routersand switches. It is recommended that you have the information listed in this section availableso you can properly install and configure the equipment.

Local Area Network (LAN) DevicesIt is recommended to access the outputs of the commands for all LAN, Internet Network devices, and WLANthrough which voice travels (for example, routers, switches, and switching routers). Save the information to anindividual .txt or .doc file named using your device hostname. This information can be used for TEAM solution.

The commands are vendor-dependent, depending on the equipment or application. Generally,it is best to use commands that access the following information:

• Configuration

• Software version

• Software feature set

• Flash and memory

• Modules installed

• Ports

• Port capabilities

• VLANs

68009260001-A January 2009 3-15

LAN Links Chapter 3: Planning for Deployment

• Interfaces

• Trunks

• Spanning-tree and spanning-tree backbonefast/uplinkfast/portfast

• Neighbors (through Cisco Discovery Protocol (CDP))

• QoS (DSCP/DiffServ, IP Precedence, 802.1Q/p)

LAN LinksFor LAN links, Motorola assumes that you have performed industry-standard planning. You needto understand and prevent QoS issues. You must implement some form of QoS, for example, inthe router, check the Differentiated Services Code Point (DSCP) flag from the TEAM smartphonedata to properly prioritize the traffic on the Layer 3 level.

Voice Network Considerations■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The most important consideration for the voice network is proper coverage within a building. This isdone in conjunction with setting up the WLAN. Ensure that there are no dead spots for WLAN. Also,decide how to administer a subscriber’ TEAM smartphone. This includes features such as:

• Administration

• Bridged call appearances

• Features that are active for the subscriber

It is recommended to collect the following information about each telephone system (PBX) in the network:

• Equipment (manufacturer, model, software version).

• Physical ports available (for CLAN [Control Local Area Network] andMedia Processor cards if applicable).

• Special third-party applications used (for example, Computer Telephony Integration (CTI).

• Wireless TEAM smartphones used.

• Latest PBX traffic reports, showing busy hour attempts and peak traffic usage.

• Determine if PBXs are linked across aWAN (through ATM, VOIP, dedicated T1’s, QSIG) or not.

◦ Bandwidth of site-to-site connections for voice

◦ Check if PBX extenders (such as the Expansion Port Network) useTCP/IP or ISDN BRI links.

3-16 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Voice Mail Considerations

Figure 3-4 Toll-Quality Voice Delivered through Quality of Service Implementation

Voice Mail Considerations■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The considerations for voice mail on the TEAM solution network should include:

• Setting up multiple mailboxes or a single mailbox based on need.

• Checking if the system has a Message Waiting Indicator (MWI) and ifit can be implemented for setup.

68009260001-A January 2009 3-17

Network Topology Maps Chapter 3: Planning for Deployment

Network Topology Maps■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Network topology maps provide details of the hardware in the network and how each device is connected.This is an important tool to help support and maintain networks for IP-enabled solutions. Topology mapsprovide the support engineers with valuable information and should reflect the portion of the network that willcarry the converged traffic. Topology maps should include all endpoints and should cover the following:

• Server locations

• Data Switch and Router locations

• PBX components

• WLAN components, APs, AP controllers, wireless switches

• Manufacturer and Model of all switches

• IP Address Plan

• Ethernet switch port settings of all ports-facing equipment (in an attempt toeliminate Ethernet port speed mismatches)

Additional Guidelines and Requirements■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section explains additional guidelines and requirements.

Rack RequirementsThe TEAM equipment, including the WSM, NSM, and PBX, fits in one standard 19-inch rack.

Required InformationAppendix B provides tables that you must complete as part of system planning. This information isneeded to install the system components. Refer to the TEAM Installation and Configuration Guide(p/n) for detailed procedures. Determine these settings for your system:

• Core Name, which is the name of your system, for example, wlan

• System Number, for example, 1

3-18 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Security

• Domain name, for example, wlan4@<your company>.com

• IP addresses, using this format as an example: Example: <173.32.204.x>

• VLAN — valid range is 1 to 4094

The suggested default for the Subnet mask is 255.255.255.0.The Router IP (default gateway) can be set to the same IP address for theequipment, for example, 173.32.204.254.

Security■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The WLAN system employs various security protocols at different layers within the system to protectthe system from unauthorized access, intrusion, and compromise. This includes security frameworks forauthentication and authorization and for the encryption of signaling and bearer (voice) traffic.

• The security framework protects the physical components of the system from attack.

• Authentication and authorization determine if a TEAM smartphone and asubscriber should be granted access to the system.

• Encryption ensures privacy of the voice and data being transmitted.

• Separate security policies and measures are configured and deployed on interfaces betweenvarious elements within the Enterprise network (such as the WSM - AAA server and WSM -PBX connections) as well as between the Enterprise network and remote subscribers.

• Network Management interfaces are secured with authentication and encryption mechanisms.

The following framework provides a comprehensive standards based security solution:

• WPA/WPA2 (802.11i) on-the-air interface from the TEAM smartphone to the WLAN.

• X.509 certificates on TEAM smartphones and servers for device authentication.

• Extensible Authentication Protocol – Transport Layer Security (EAP-TLS) on the system interface.

Optimized approaches on security interfaces include:

• WLAN authentication with abbreviated 802.1x exchange during AP change.

• Reuse of a single TLS/TCP connection between the TEAM smartphone and theSIP Proxy for both directions of the SIP signaling traffic.

Authentication delegation:

68009260001-A January 2009 3-19

Security Chapter 3: Planning for Deployment

• Once TEAM smartphones and subscribers are authenticated by the WSM,maintaining of separate registration records on the PBX or triggering furtherauthentication challenges by the PBX is not required.

• The WSM becomes Enterprise trusted.

Figure 3-5 System Architecture Security

3-20 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Quality of Service Considerations

Quality of Service Considerations■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The primary purpose of Quality of Service (QoS) is to ensure proper voice quality and quality of experiencefor subscribers, without hindering the efficient working of the Enterprise network. QoS is affected by packetloss, causing skips, clipping of voice, jitter, latency (delay), and so on. Buffers are used to combat these issues.

QoS covers almost every part of the system, from the TEAM smartphone through to thePBX. It involves reserving bandwidth, and packet classification getting preferential treatment.This is continually monitored, measured, and verified.

A pre-deployment analysis of the Enterprise network is highly recommended. The analysis requiresthat hardware and software be used to anticipate any problems or bottlenecks in the network.If the network cannot be converged to supply high-quality, reliable voice communications,recommendations for equipment upgrades will be made. If these recommendations are nothonored, it may be difficult or impossible to ensure adequate QoS to subscribers.

Overview of QoS Roles by System ComponentEach component has a role to play in ensuring QoS. Refer to the TEAM Installation and Configuration Guidefor specifics on setting up QoS. Audio quality will be degraded if QoS is not set up correctly on each networkelement. The following table describes the role played by each component in ensuring optimum QoS.

Table 3-4 lists the overview of QoS roles by system component.

Table 3-4 Overview of QoS Roles by System Component

Component RoleWSM The VLAN ID must be set correctly for QoS during installation of the

WSM.

NSM • Provide a user interface for the operator to specify QoS parameters.Sets parameters by traffic type, giving higher priority to voice overcall control signaling.

• QoS configuration information is pushed down from the NSM to theWSM.

68009260001-A January 2009 3-21

Overview of QoS Roles by System Component Chapter 3: Planning for Deployment

Table 3-4 Overview of QoS Roles by System Component (Continued)

Component RoleIP-PBX • Provide a properly configured QoS capable media gateway that marks

packets with the appropriate DSCP.

• Provide echo cancellation for all voice calls in the media gateway.

During PBX configuration, the installer identifies the G.711mu codec to be used to compress data and ensure QoS, givingvoice priority over data.

WLAN • Must participate in the bandwidth reservation scheme

• Determine the proper traffic class for a packet from its 802.1Q/ppriority and transmits it to the TEAM smartphone accordingly.

• Map TID priorities from the TEAM smartphone to VLAN prioritieson all frames entering the network.

TEAMsmartphone

• Provide echo cancellation in the TEAM smartphones.

• Provide packet error concealment algorithms for each vocoder (G.711and G.729A).

• Reserve OAP bandwidth for voice transmissions.

• Classify the proper differentiated service (DiffServ) code point(DSCP) based on the application and insert it in the IP header for allpackets in the flow.

• Determine the proper traffic identifier (TID) and insert it in the 802.11MAC header at the air interface.

• Determine the proper traffic class for a packet from an application andtransmit it to the Enterprise infrastructure accordingly.

3-22 68009260001-A January 2009

Appendix

ADetailed Features of the TEAM smartphone

This Appendix provides detailed features of the TEAM smartphone.

Telephony Features■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the basic and supplemental telephone services available in the TEAMsmartphone when it is located in the Enterprise WLAN.

Make and Receive Phone CallsTEAM’s basic call feature allows a subscriber to make or receive a call to or from anothersubscriber when it is located within the Enterprise WLAN.

The following scenarios are supported:

• TEAM smartphone to TEAM smartphone

• TEAM smartphone to IP Deskset and vice versa

• TEAM smartphone to PSTN target and vice versa

The basic call feature includes Direct Inward Dialing (DID) and Direct Outward Dialing (DOD) calling.

Direct Inward Dialing Plans

Direct Inward Dialing (DID) enables callers to dial directly to an extension on a Private Branch Exchange(PBX) without the assistance of an operator or automated call attendant. This service makes use of DIDtrunks, which forward only the last three to five digits of a phone number to the PBX.

For example, if an Enterprise has phone extensions from 723-1000 to 723-1999, and a caller dials 723-1234,the local central office (CO) would forward 234 (or 1234, depending up on the dialing plan configurationset for the PBX). The PBX then dials the extension. This feature is only applicable to callers outside theEnterprise. The actual translation happening between the central office and the PBX is completely transparentto the subscriber. The subscriber would dial the Enterprise number as any other PSTN number.

68009260001-A January 2009 A-1

Direct Outward Dialing Plans Appendix A: Detailed Features of the TEAM smartphone

Direct Outward Dialing Plans

Direct Outward Dialing (DOD) lets an Enterprise subscriber dial a PSTN number while in the Enterprise.Callers dial a DOD access code (for example, 9) to reach a PSTN trunk. The PBX uses the access code toreach the Automatic Route Selection (ARS) feature. The automatic route selection feature uses the dialeddigits, caller location, and other information (when required) to select a PSTN trunk.

The ideal scenario does not require the subscriber to dial the DOD access code, rather, the PBX hasthe intelligence to properly route and PSTN-bound call out a PSTN trunk. This routing is usuallyfacilitated via the configured PBX dial plan. If for some reason, the PBX does not support this, thesubscriber is required to manually dial the DOD access code when accessing the PSTN.

Call ForwardingThe Call Forwarding (CF) feature allows a TEAM subscriber to redirect calls to user-defineddestinations. The capability exists to activate/deactivate Call Forwarding in each TEAM smartphone.This feature is controlled by the WSM in a proprietary manner.

A subscriber uses the TEAM smartphone UI to command the WSM to keep track ofits desired Call Forwarding Status, as follows:

• Unconditional

• Busy/No Answer

Call Forwarding empowers the WSM to inform the call originator accordingly on any subsequent callattempts impacting the TEAM smartphone so that the call can be retargeted to the destination.

Call WaitingThe Call Waiting feature of the TEAM solution provides an indication to a subscriber, who is alreadyengaged in an established interconnect call, that one or more calls are awaiting connection. For example,it notifies a subscriber of an incoming call through the use of a call waiting tone. The subscribercan then answer that call and either end or place the current call on hold.

Call HoldThe Call Hold feature of the TEAM solution allows a subscriber to change an active interconnect callinto the hold state by pressing a button on the TEAM smartphone. The TEAM smartphone providesa visual indication of the name/number of the party and the hold status.

When a call is placed on hold, no media data is exchanged between the participating parties. Thecall on hold can be retrieved at the subscriber’s discretion. The Call Hold feature is required for bothCall Waiting and Conferencing. Music hold is determined by the configuration of the Enterprise PBX.If the Enterprise is set up to music hold, music is played for calls placed on hold.

A-2 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Call Transfer

Call TransferCall Transfer lets a caller transfer an established interconnect call to another telephone number within oroutside the Enterprise. The caller disconnects when the call is successfully transferred. The Call Transfer canbe blind (unattended) or attended. Attended call transfer is not available with the TDM gateway configuration.

Caller IDThe Caller ID feature displays the name or telephone number associated with an incoming call on thecalled party’s TEAM smartphone. A telephone-related device allows individuals to identify callers beforeanswering the telephone. When a telephone rings, an electronic display registers the caller’s name andphone number. Individuals can use the Caller ID feature to screen their calls. TEAM smartphonessubscribing to Caller ID are able to view the CPN or ANI of the calling party.

• Caller Party Name (CPN) enables the terminating customer to identify the calling party bya displayed name before the call is answered. The displayed name is associated with theCalling Party Number. The calling party name is not available with all configurations.

• Automatic Number Identification (ANI) is a telephone network feature thatallows the transmission of the ten-digit area code and telephone number of theoriginating telephone to the receiving telephone.

Abbreviated DialingAbbreviated Dialing is a feature that requires that a caller dial only the last few digits of a phonenumber to call another Enterprise associate. For example, a caller dials 5-1234 to reach 505-555-1234.Abbreviated dialing is provided by the Enterprise PBX when the caller and target are provisioned inthe PBX as SIP line extensions. The TEAM smartphone provides Abbreviated Dialing functionalityin the scenarios when the PBX is not involved in call routing.

Conference Calling (Ad Hoc, Meet-Me)Conference calling is a feature that allows a subscriber to participate in a conference call with two ormore callers, all in different locations. The maximum number of participants is dependent on the specificPBX or conference server vendor (for example, six being the limit for Avaya PBX).

Ad Hoc conference is generally used to spontaneously add on one or more callers (one ata time) to an existing two-person call. Most PBXs use an internal audio bridge to supportbetween three and six participants in an Ad Hoc conference.

Ad Hoc conference calling is only available if your system has an Avaya PBX.

68009260001-A January 2009 A-3

Voice Mail Indication and Retrieval Scenarios Appendix A: Detailed Features of the TEAM smartphone

Meet-Me conference is a pre-planned conference where three or more subscribers are provideda conferencing bridge extension to dial in to. The PBX supporting the bridge extension mergesthe audio from all participants dialing into the specific extension.

Meet-Me conference calling may not be available with every PBX.

Voice Mail Indication and Retrieval ScenariosThis topic describes the TEAM solution voice mail indication and retrieval in the Enterprise.The various functions of voice mail indication and retrieval are:

• Messaging

• Voicemail Notification/Message Waiting Indication

• Message Retrieval and Playback

Messaging

Regardless of the subscriber location, each Enterprise subscriber has a single mailbox and voice mailnotification. The IP-PBX partner provides access to the voice mail service in the Enterprise. The PBXis responsible for the connection of all Enterprise phones to the Enterprise voice mail system.

Voicemail Notification/Message Waiting Indication

Voice mail notification within the Enterprise is done by the PBX which activates the Message WaitingIndicator (MWI) icon on the TEAM smartphone. The TEAM smartphones receive an MWI in real-timewhile in WLAN coverage, or delayed through registration to the WLAN.

• The PBX has the sole connection to the Voice Mail Server, and defines change ofstate: No message, Message, or All messages Read.

• The PBX forwards any unanswered call to the Voice Mail Server wherethe caller can leave a message.

• After a message is left, the Voice Mail Server sends an MWI to the recipient phonethrough the PBX and WSM. This tells the recipient’s phone to display an iconindicating that a message has been left for the recipient.

• When a recipient calls into voice mail server and listens to the message, the VoiceMail Server sends a new MWI to clear the recipient’s display.

A-4 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Message Retrieval and Playback

Message Retrieval and Playback

Retrieving and playing voice mail messages is based on the Telephony User Interface providedby the PBX. This is a dial-in interface that supports operations such as saving, playing, anddeleting back voice messages. If an Enterprise has a unified messaging solution, the TelephonyUser Interface provides the same capabilities for e-mail messages. The TEAM solution supportstext–to–speech conversion from e-mail playback on a voice channel.

DTMF (Overdial) SupportPost Digit or Dual Tone Multi-Frequency (DTMF) dialing describes the ability of the system to captureDTMF tones from the subscriber once the call has been established. This feature is used in many automatedtelephony services such as menu selection, collection of credit card or pre-paid calling card numbers.

DTMF collection within the Enterprise uses RFC2833, which defines specific Real-Time TransportProtocol (RTP) payloads for sending and playing back DTMF tones. To compensate for the fact that RTPis normally sent over an unreliable protocol, User Datagram Protocol (UDP), RFC 2833 specifies sendingeach digit multiple times. In WLAN, the DTMF tones are encoded packets which the infrastructurereceives and then re-creates as the actual DTMF tones on the bearer channel.

Overdialing is a process where the subscriber dials tones in addition to the ones required to establish the call.For overdialing, a subscriber includes the digits into the SIP INVITE, which the Back to Back User Agent(B2BUA) then forwards (that the call is routed) using protocol such as SIP, PSTN, and so on.

911Enhanced 911 (911) extends basic 911 service by requiring the 911 call to be routed to the PSAP(Public Safety Answering Point) physically closest to the caller, for the 911 call to convey thecaller’s location information, and for the call to indicate a call-back number in which the PSAP candial to reconnect any 911 call that is dropped. The location information and call-back number areintegrated into what is called an Emergency Line Identification Number (ELIN). An ELIN, a simplephone number owned by the Enterprise, serves the following purposes:

• As an identifier which maps to the physical location of an Enterprise.

• Can be dialed by the PSAP to reach the original 911 caller (or an attendant nearby)

The Enterprise PBX is responsible for routing the 911 call to the proper PSAP. The PBX also has theultimate responsibility of ensuring that the 911 call carries the proper ELIN. The granularity of the ELINis determined by the Enterprise and facilitated in the PBX. This means the PBX controls whether theELIN is the caller’s actual phone number or just a phone number representative of a geographic areaknown as an Enterprise Emergency Response Location (ERL). The PBX also controls whether theELIN represents a specific floor, wing, or such in the Enterprise or just the physical address of theEnterprise. If an ELIN representative of an ERL is used, the PBX may provide the ability to map acall-back from the PSAP to the actual caller who initiated the emergency response.

911 Call Availability: Ordinarily it is possible for an subscriber or the PBX administrator to block sendingof the Calling Party Number (CPN) over ISDN trunks. This ability to block the CPN is suppressed during911 calls because the CPN may be used by the PSAP to aid in the emergency response.

68009260001-A January 2009 A-5

Call Restriction Appendix A: Detailed Features of the TEAM smartphone

Call RestrictionCall Restriction allows network operators to restrict the type of phone calls that are permitted for eachof the subscribers in the enterprise. That is, the WSM can prescribe that certain calls are allowed orrejected based on the originating and terminating numbers. This is implemented by:

1. defining each subscriber as a member of a specific class.

2. associating restriction rules with each class.

Based on the rule assigned to the class of the originating number and the number being dialed,each call is either permitted or rejected by the WSM.

The system administrator creates a file (format = CallRestrictionData.csv ) containing classesand associated members and uploads the file to the WSM. Each class is assigned a rule whichdetermines which destination numbers that are restricted for that class.

Once the Call Restriction file is uploaded, it must be imported into the WSM database using the wjanitor1tool. Rules can be updated by editing the CallRestrictionData.csv file and re-importing it.

911 calls may not be restricted

If no CallRestrictionData.csv file is configured in the WSM, the WSM disablesCall Restriction and permits all calls.

Busy IndicatorWhen the SIP Proxy sends an INVITE to a phone in the WLAN that is busy, the phonereturns a 486 - Busy message as a response. The phone does not ring or present any otherindication to the subscriber that a call was received.

A called phone located in the WLAN is busy and cannot answer the call if:

• It is already in a call and does not support call waiting.

• The target subscriber manually rejects the call.

• The target is busy in a PTT call.

A-6 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide PTT Features

PTT Features■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The TEAM smartphone provides Push-to-Talk (PTT) voice messaging features within an EnterpriseWLAN. PTT is available as an instant voice button on the TEAM smartphone. The PTT feature doesnot affect any other feature on the TEAM smartphone. It works by reserving a certain bandwidthfor the communication/alert every time the PTT button is pressed.

PTT service supports the following features within a single campus of a single Enterprise:

• Private Call— Place private calls which are half duplex voice calls betweentwo dispatch-capable TEAM smartphones.

• Call Alert— Send call alert notices which are data-only invitations thatconvey a desire for a subsequent private call.

• Group Call— Place a call to a pre-provisioned group. The subscribers can be members ofmultiple groups and have the option to select which group they want to call to affiliate with .

PTT is an optional purchasable feature that requires a separate purchase. Group Call is an optionallicensable feature that requires an additional license to the one purchased for the PTT feature.

Private CallThe private call (one-to-one half-rate voice exchange) feature allows a TEAM subscriber to set up an instanthalf-duplex call with another TEAM subscriber. With private call, you can use your phone as a long-range,walkie-talkie. A private call reserves bandwidth for bearer (voice) before the call can proceed.

A private call can only be placed from a TEAM smartphone which is currently registered and within thecoverage of the Enterprise WLAN. In addition, the originator TEAM smartphone can only place calls tothe TEAM smartphones that are provisioned within the same WLAN system. Likewise, a target TEAMsmartphone can only receive a private call when it is currently registered and within the coverage of the WLANsystem, and can only be received from a TEAM smartphone which is also within the same WLAN system.

Half-duplex dispatch private call and group calls must be set up in less than 1 sec for 95% of all successfulcall attempts. The PTT call setup time is measured from the time the caller presses a PTT button tothe time the talk permit tone is played on the originator’s TEAM smartphone.

Example scenario:

• Bob wants to call Joe, so he enters Joe’s extension and presses the PTT key.

• All calls from a TEAM smartphone are routed through the WSM since phones only connectto the WSM, and the WSM has the PTT call processing engine and database.

• The WSM pages Joe at his IP address.

• If Joe responds successfully, Bob and Joe can now exchange voice packets – in other words,they can talk. But in PTT, only one person talks at a time in a half– duplex fashion.

68009260001-A January 2009 A-7

Call Alert Appendix A: Detailed Features of the TEAM smartphone

Call AlertA call alert (one way attention request) allows a TEAM subscriber to invite another subscriber withinthe same Enterprise to participate in a private call. A call alert can only be sent from a TEAMsmartphone which is currently registered and within the coverage of the Enterprise WLAN. In addition,the originator TEAM smartphone can only target TEAM smartphones which are provisioned withinthe same WLAN system. Likewise, a target TEAM smartphone can only receive a call alert whenit is currently registered and within the coverage of the WLAN system, and can only be receivedfrom a TEAM smartphone which is also within the same WLAN system.

Group CallA group call (one-to-many half-rate shared single voice) allows one subscriber of the TEAM solution toinitiate and participate in a half-duplex conversation with more than one other subscriber in the sameWLAN system. Access to group call functionality requires an additional license to the one purchasedfor the PTT feature. Additionally, group call-specific provisioning is required to not only enable thefeature on a system basis, but also for system configurations needed to use the feature.

Group calls are configured through the NSM, and up to 255 talkgroups can be created. Group calls have floorcontrol which is controlled by the WSM, one subscriber has control at a time. A subscriber receives an audibleresponse to indicate if the call is successful or unsuccessful. The WSM sends individual messages to eachTEAM smartphone. The WSM is in control of who receives audio packets, performs duplication of packetsfrom the originator, and sends to each TEAM smartphone. If the initiator receives one or more successfulanswers then the call proceeds. However, the subscriber is not notified who is on the call and a few membersmay not be on the call. Members can join or leave a group call conversation that is already in progress.

Example scenario:

• Bob wants to contact the members of a talkgroup, so he enters the talkgroupextension and presses the PTT key.

• All calls from a TEAM smartphone are routed through the WSM since phones only connectto the WSM and the WSM has the PTT call processing engine and database.

• The WSM sends the Group call to the members of talkgroup (paging).

• Bob can now initiate voice transmission – sending voice packets to the IP address of eachtalkgroup member (who responded successfully). The WSM is the network element thatreceives group call voice packets and does the duplication and routing to individual targets.

PTT Caller IDWhen a subscriber sends a Call alert, Private Call, or Group call, the recipient’s phone emits a soundnotification (or vibrates, depends on the subscriber profile) and displays the name or Private ID of the caller.

A-8 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Missed PTT Call Indication

Missed PTT Call IndicationFor a missed PTT call, an indication appears on the screen, and a notification tune is played.

Talkgroup SelectionThe TEAM smartphone allows a subscriber to select a talkgroup for a PTT group call. A talkgroup is apredetermined group in the Enterprise. An active PTT group is the group that the subscriber is currentlyaffiliated with. A subscriber can only receive and monitor one talkgroup at a time - the active PTT Group.

Example scenario

• Joe selects a talkgroup from hisContact list on the TEAM smartphone, or decides to call a groupnot on his Contact list, so he dials # and a number between 1 and 255 and presses the PTT key.

• The members of the talkgroup answer the PTT group call. Only one person at atime may speak on a group call. The Private ID or name of the person who isspeaking appears on the display below the group number.

Presence/Instant MessagingThe Instant Messaging (IM) application provides presence information if end user is busy.Once a subscriber logs into the IM application, they can designate their own status andview the status of other subscribers in the Enterprise.

Presence is an optional purchasable feature and is not integrated in the TEAMsolution. Hence, the user can only gain access to Presence if the Enterprisepurchases Microsoft Live Communication server.

User can gain access to the Presence feature only if the Enterprise purchases Mi-crosoft Live Communication server.

Data Features■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The TEAM smartphone provides its subscribers typical Data Applications such as:

• Access (while in the WLAN) to the Enterprise Exchange Server for e-mail services

• Enterprise directory services

68009260001-A January 2009 A-9

Text Messaging Appendix A: Detailed Features of the TEAM smartphone

• Browsing corporate directory services (for example, various portals)

Text MessagingThe text message feature allows a TEAM subscriber to send and receive text messages within theEnterprise WLAN. A Text Messaging Client resides on the TEAM smartphone, integrated withWindows Mobile 6.1, which is a mechanism to send text messages.

It is easy to set up a distribution list in the TEAM smartphone using Microsoft Windows Mobile. To setup the distribution list, select multiple people from the contact list and add to the To field.

TEAM supports SIP-based text messages with a maximum of 160 characters.

TEAM provides support for two-way messaging as follows:

• LOB application interface

◦ LOB applications can send messages to TEAM smartphones.

• Enterprise dial plan (10-digit dialing) as the target address. (e-mail ID isnot a valid address for text messaging).

• Abbreviated dialing/messaging

◦ Supports message delivery based on abbreviated extension dialing

• Address book integration

◦ Target can be selected from contact list/address book or call log

• Addresses from stored messages such as received messages

• Multiple target entry

◦ Send a single message to multiple targets

• Canned Message Support

◦ The TEAM smartphone is pre-programmed with editable, Enterprise-specific messages

• Store-and-Forward Server

◦ Undeliverable messages stored for later delivery (upon registrationof the TEAM smartphone)

◦ Can configure the maximum number of messages stored, and how long they are stored.Audits are performed nightly, and messages are deleted if the parameters are exceeded.

• Delivery Confirmation

◦ Sender can request a delivery confirmation

◦ Queued if undeliverable

• Activation and Provisioning

◦ Activated at Enterprise level, and provisioned for each subscriber. Subscriberscan originate messages, or only receive messages.

A-10 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Simultaneous Voice and Data

Simultaneous Voice and DataThe simultaneous Voice and Data feature allows subscribers to retain data context in sessionsindependent of voice call activity (simultaneous voice and data).

The simultaneous Voice and Data feature allows subscribers to perform web browsing and text messagingactivities independent of telephony activities (simultaneous voice and data).

Corporate E-mailThe TEAM smartphone supports the corporate e-mail through the windows mobile 6.1 OS feature. E-mailaccess is through Windows Mobile interface. This requires integration with the Enterprise e-mail server.

Calendar, Phonebook, and TaskThe TEAM smartphone supports the following Personal Information Manager (PIM) applications:

• Calender application client— The client is only synchronized with a PC based Outlookusing the Microsoft ActiveSync connection (no network involvement).

• Phonebook application client— It performs contact and address functions. The client isonly synchronized with PC based Outlook using Microsoft Activesync connection (nonetwork involvement). The address book function is also synchronized with PC basedOutlook using Microsoft active sync connection (no network involvement).

Directory ServiceThe TEAM subscriber supports directory services through an HTTP browser. Therefore, the directoryserver in the Enterprise needs to support an HTTP interface. The subscriber retrieves data from thedirectory server using an HTTP browser. Clicking on the data automatically dials the retrieved person’snumber. No direct storing capability from the directory to the phonebook is implemented.

Standard Browser SupportThe TEAM smartphone supports a browser that allows a subscriber to access WML and HTML Websites from the WLAN. The browser uses HTTP and HTTPS on the network.

The Windows Mobile 6.1 OS provides support for Web browsers and web-based forms.

The certificates that the browser supports depend on the specific web servers that the subscriber is planning toaccess, and are not provided by Motorola. Normally, only the server side certificate is required for HTTPS,but the subscriber has to install the trusted CA certificate for the server in order to authenticate the server.This process is expected to be done by the end user or Enterprise IT support, not Motorola.

68009260001-A January 2009 A-11

Line of Business Applications Appendix A: Detailed Features of the TEAM smartphone

Line of Business ApplicationsThe TEAM solution supports receipt of text messages to the TEAM smartphone from Line of Business (LOB)applications. These messages are sent from the LOB application or LOB message application aggregatorand are then sent to the WSM. The WSM will then send these messages to the TEAM smartphone. Thetext messages can be up to 160 characters in length and should follow RFC3261 protocol. As an example:there may be a Customer Relationship Management (CRM) application that tracks important customerevents such as when an order is placed. In this case, the LOB application can generate a text messagestating that the order has been placed and send it to the salesperson responsible for the order.

The Windows Mobile 6.1 OS provides support to LOB applications.

Call Scenarios■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section provides details of Call Scenarios supported in the TEAM smartphone.

IntroductionThe TEAM solution handles all the necessary call scenarios for the WLAN. The TEAM solution in theEnterprise uses a back-to-back user agent architecture. The TEAM smartphone does not independentlysignal to other TEAM smartphones in the Enterprise. The state of the other TEAM smartphones withwhich the TEAM smartphone is in logical communication is not available. Most calling scenariosare straightforward calls in this architecture. All call signaling messages between the PBX and theTEAM smartphone are WLAN transmitted through the WSM as a SIP proxy.

Subscriber States

The TEAM smartphone has the following subscriber states which appear on the home screen:

• No Service— This state appears when the subscriber is not registered. Indicates that thesubscriber has not successfully registered to the WSM. This may be due to many reasonssuch as not complete, device not provisioned, device not in WiFi coverage, WLAN rejectingassociation request, User is not provisioned (WSM rejects registration attempts), and so on.

• Full Service— his state appears when the TEAM smartphone is fully authenticatedand registered and has both interconnect call and PTT capabilities.

• Voice Only— This state appears if the subscriber has dispatch disabled (at the system or devicelevel). Indicates that the subscriber has successfully registered to the WSM and is able tomake use of telephony services. No Dispatch services are available in this state.

A-12 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Bridged Call Appearance

• Dispatch Only— This could appear if SIP proxy is stopped for some reason, or ifSIP proxy is incorrectly interrupted during registration and IC is not enabled, whichis not an expected event. Indicates that the subscriber has successfully registered tothe WSM for Dispatch and is able to make use of the Dispatch services (PC, GC,CA) . No Telephony services are available in this state.

In the TEAM solution, the Dispatch Only state should not ap-pear under normal conditions.

Bridged Call AppearanceThe PBX sends an update to the WSM whenever a subscriber initiates a call on a desk set, oranswers a call on a call appearance bridged to a TEAM smartphone. The subscriber is allowedto join the bridge by signaling an invite to the PBX for the call appearance that the subscriberwants to bridge. The call flow is identical to a WLAN originated call.

Call State UpdatesWhen the TEAM smartphone sends a Subscribe message to the PBX, the PBX in turn sends the currentMessage Waiting Indicator and Forwarding states to the TEAM smartphone through a Notify message.

WLAN Call Hold/Remove HoldThe TEAM smartphone can place an active call on hold by signaling the indication to thePBX. This is done using the standard SIP method for hold. The TEAM smartphone can takeany call off hold by signaling the indication to the PBX.

WLAN Call OriginationThe TEAM smartphone sends an invite message containing all the information about the call originatorand the party that it is attempting to call. The TEAM smartphone receives an indicator that the call isbeing attempted. If it is determined that the call’s receiver phone is ringing, the TEAM smartphonereceives an indicator that the call is in progress and displays In Progress on the phone display. Whenthe call attempt is answered by the receiver, the TEAM smartphone receives an OK message anddisplays Connected. The call flow is the same regardless of the type of party called.

68009260001-A January 2009 A-13

WLAN Call Toggle Appendix A: Detailed Features of the TEAM smartphone

WLAN Call ToggleThe TEAM smartphone can toggle between an active call and a call on hold by placingthe active call on hold and then removing it from hold.

WLAN ConferenceWhen a TEAM smartphone has both a call on hold and an active call, it issues a Refer for the heldparty to the currently active party. The conference can have up to six participants.

The WLAN conference is only available on Avaya.

Ad Hoc conference: In an Ad Hoc conference, only a conference controller can add participantsto a conference. If sufficient streams are available on the conference device, the conferencecontroller can add up to six participants to the conference.

Meet-Me conference: Unlike in an Ad Hoc conference, in a Meet-Me conference, the conference controllerdoes not have complete control over who joins the conference. The Meet-Me conference controller selectsone of the Meet-Me conference numbers from the range specified. The conference controller then establishesthe conference using that Meet-Me conference number. After the conference is established, anyone whocalls that particular Meet-Me conference number is immediately connected to the conference.

WLAN End of CallThe WLAN or the TEAM smartphone may end a call by sending a Bye to the other party.

WLAN Incoming CallThe PBX sends an invite to the WSM through the TEAM smartphone indicating an attempted call.If the WLAN identifies the caller, then the call information includes:

• Called party information

• Calling party information

The TEAM smartphone is allowed to refuse a call attempt if the subscriber does not answer the incomingcall, which results in the TEAM smartphone sending a final response to the call. If a subscriber answers theincoming call, the TEAM smartphone sends an OK to the PBX. The call originator or PBX may abandona call attempt at any time. In this case, a Cancel is sent to the TEAM smartphone. The PBX may attemptas many concurrent call attempts as the subscriber has call appearances. Bridged call appearances on thesubscriber’s desk set phone for other subscribers are not signaled to the TEAM smartphone.

A-14 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide WLAN Status Change

WLAN Status ChangeIf the PBX determines that the status of a subscriber has changed, it signals the status change to the TEAMsmartphone by sending a Notify message with the new state of Message Waiting Indicator and Forwarding.The TEAM smartphone accordingly updates its display. Status changes include the following:

• Send All Calls

• Call Hold/Retrieval

• Message Waiting Indication

• Multiple Call Appearances

• Facility Busy Indicator

• Call Forwarding

Call Forwarding

Call Forwarding allows a TEAM subscriber to redirect calls to subscriber-defined desti-nations. The forwarded-to destinations can be:

• Internal extension (another TEAM subscriber)

• External number

• Attendant

Voice mail and coverage can also be used if the forwarded number is not answered or is busy. Forwardingcan be activated for all calls, no answer (after a specified time limit), or busy.

Call TransferWhen a TEAM smartphone has a call on hold and an active call, the TEAM smartphoneindicates a transfer of the two parties by issuing a “Refer” for the party on hold to thecalling party to which the caller is being transferred.

Attended transfer is the ability to transfer a call, and speak to the called party before putting the call through.A consultative transfer is one in which the transferring or forwarding party either connects the caller toa ringing phone or speaks with the third-party before connecting the caller to the third party.

Blind (Unattended) transfer is the ability to transfer a call without talking to the called party.A blind call transfer or blind call forward is one in which the transferring or forwarding phoneconnects the caller to a destination line before the ringing tone begins.

68009260001-A January 2009 A-15


A-16 68009260001-A January 2009

Appendix

BEquipment Checklists

The Appendix lists all the equipment checklists.

Enterprise Equipment Checklist■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Complete Table B-1 to gather information before installing the system. This information isneeded for Enterprise server installation and configuration checklist.

Table B-1 Enterprise Server Installation and Configuration Checklist

TEAMComponent IP Address Entry Hostname Entry Hostname

ExamplesVLANEntry

NSM wlan1–nsm1

WSM wlan1wsm1

DCHP wlan1–dhcp1

DNS wlan1–dns1

Radius Server(AAA)

wlan1–aaa1

wlan1–pbx1–ether-net

wlan1–pbx1–server

wlan1–pbx1–p330

wlan1–pbx1–mgp

PBX Components:PBX1-ETHERNETPBX1-SERVERPBX1-P330PBX1-MGPPBX1-VOIP

wlan1–pbx-voip

68009260001-A January 2009 B-1

WLAN Equipment Checklist Appendix B: Equipment Checklists

Table B-1 Enterprise Server Installation and Configuration Checklist (Continued)

TEAMComponent IP Address Entry Hostname Entry Hostname

ExamplesVLANEntry

MAIL wlan1–mail1

Access Pointmanagementapplication

wlan1–cmg

DHCP-DNS-AAA dhcp-dns-aaa1

1. If you are using a single machine to support DHCP, DNS, and AAA, then use this as your host name and address insteadof the three separate ones above.

WLAN Equipment ChecklistComplete Table B-2 before beginning WLAN equipment installation and configuration.

Table B-2 WLAN Equipment Installation and Configuration Checklist

Item Entry Notes

Network Settings

Wireless switch IP address IP address format example:<173.32.204.x>

Netmask (Subnet mask) Example: 255.255.255.0

Router IP address (DefaultGateway)

For example, 173.32.204.254

VLAN ID VLAN — valid range is 1to 4094

RADIUS Secret Enter the Secret password.

Wireless Parameters

B-2 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide WLAN Equipment Checklist

Table B-2 WLAN Equipment Installation and Configuration Checklist (Continued)

Item Entry Notes

TEAM SSID Enter the SSID used forWLAN access.

Wireless Domain Secret Same as RADIUS Secretpassword.

AP port numbers Enter port numbers for allAPs in the WLAN.

68009260001-A January 2009 B-3


B-4 68009260001-A January 2009

Glossary

Glossary■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Glossary and Acronyms10Base-T — 10BaseT is a 10 mbit/sec half duplex Ethernet interface utilizingUTP (Unshielded Twisted Pair) wiring.

AAA — Authentication, Authorization and Accounting

Access — A performance measure of a data system. Access is measured fromthe time a data packet is sent from one of the units using the channel to thetime the packet is received by the receiving unit.

Access Method — The ability and means necessary to store data, retrieve data, orcommunicate with a system. FDMA, TDMA, and CDMA are examples.

AC — Access Categories

ACS — Access Control Server (Cisco Secure Access Control Server)

Algorithm — A process by which unencrypted information can be encryptedand encrypted information can be decrypted. Different algorithms providedifferent levels of protection for the information.

Analog — 1.) As applied to an electrical or computer system, the capability of representingdata in continuously varying physical phenomena (as in a voltmeter) and converting them intonumbers. 2.) In telecommunications, a reference to Advanced Mobile Phone System (AMPS)or Narrowband Advanced Mobile Phone System (NAMPS) capability. Also the methodof transmission of voice information used by AMPS and NAMPS phones, as defined bythe Bell Spec, IS-88, IS-91, or IS-91A. 3.) A type of measurement in which the "line ofmeasure" is continuous as compared to one which is discretely incremented. For example, aclock with hands is an analog device, as compared to a digital clock which is not.

AP — Access Point or Access Port

API — Application Programming Interface

ARS — Automatic Route Selection

ASCII — American Standard Code for Information Interchange

ATM — Asynchronous Transfer Mode

Audio Bridge — A bi-directional analog amplifier that allows audio to pass betweenboth types of dispatch consoles and the base station.

Backward Compatibility — Ability of new units to operate within an "old" systeminfrastructure, or to directly communicate with an "old" unit.

Bandwidth — The difference between the limiting frequencies of a continuousfrequency band, typically measured in kilohertz. May be considered, the amountin kilohertz required for a single communications channel.

Call — An event beginning when a user requests voice resources (primarily RF channels),and ending when those resources are released and available for a new request. A callconsists of a series of console and radio transmissions. A call is complete when allof the transmissions have ended and the hang time has expired

68009260001-A January 2009 GL-1

Glossary

Call Continuation — The capability of passing active calls across site or zone boundaries.Also called Call Handoff, Call Coordination, or Call Reconnect.

CAD — Computer Aided Dispatch

CD ROM — Compact Disc Read Only Memory.

CDR — Call Detail Recording

CHAP — Challenge–handshake Authentication Protocol

Channel — A single unidirectional or bidirectional path for transmitting and/orreceiving of electrical or electromagnetic signals. This Radio Frequency (RF)resource is capable of supporting two-way traffic.

Circuit-switching — Circuit-switching provides a dedicated path between asender and receiver for the duration of the communication. The advantages of thecircuit-switched networks are dedicated circuits for the call and customers do not payfor idle bandwidth. Disadvantages are call setup time and potential under-utilization ofthe communication channel. Circuit-switching is useful for short duration transmissions,for feeders to main sites or for backup/disaster recovery situations

CLI — Command Line Interface

CRM — Customer Relationship Management

CSV — Comma Separated Values

dB — Decibels. Unit relating to power levels (for example, of a speech signal).

DAP — Dispatch Application Processor

DDD — Direct Distance Dialing

DHCP — Dynamic Host Configuration Protocol

DID — Direct Inward Dialing

DID — A select number of digits that are associated with a specific radio user thatallows a landline caller to reach the user directly. The private branch exchange(PBX) forwards the dialed digits to the Zone Controller.

Delay — The delay experienced when a call arriving at an automatic switching devicefinds no idle channel or facility available to process the call immediately.

DNS — Domain Name Service

DOD — Direct Outward Dialing

EAP-TLS — Extensible Authentication Protocol – Transport Layer Security

ELMT — Emergency Local Maintenance Terminal

ESP —

Floor Control — Floor Control enhances the user experience during a Group Call, as itonly allows one person to talk at a time. This prevents users from talking over each other,which is possible in a Group Call since it is a half duplex conversation.

GUI — Graphical User Interface

HAMS Logs — Highly Available Monitoring Services Logs

ID — Identifier

IEEE — Institute of Electrical and Electronic Engineers

IGMP — Internet Group Management Protocol

GL-2 68009260001-A January 2009

Glossary

IKE — Internet Key Exchange

IP — Internet Protocol

IM — Instant Messaging

ITU-T — International Telecommunications Union-Telephony

LAG — Link Aggregation Group

LAN — Local Area Network

LMT — Local Maintenance Terminal

LOB — Line of Business

LOM — Lights Out Management

MAC — Media Access Control. Sublayer of the OSI (Open SystemsInterconnection) Data Link Layer

MAC Address — Media Access Control Address

MS — Mobile Subscriber

MS SMS — Microsoft Systems Management Server

MSU — Motorola SW Update

MS UCS — Microsoft Unified Communications Server

MTA — Maintenance Terminal Administrator

MWI — Message Waiting Indicator

NOA — Network Operator Administrator

NSM — Network Services Manager

NTP — Network Time Protocol

OAP — Over-the-Air Provisioning

OHMT Log — OS and Hardware Manager Task Log

OTA — Over-The-Air

PAP — Password Authentication Protocol

PBX — Private Branch Exchange

PCM — Provisioning Client Maintenance

PIM — Personal Information Manager

PoE — Power over Ethernet

POP3 — Post Office Protocol

PSAP — Public Safety Answering Point

PSTN — Public Switched Telephone Network

PTT — Push-To-talk

QoS — Quality of Service

RADIUS — Remote Authentication Dial In User Service

WLAN — Wireless LAN

SACS — Subscriber Access Configuration Server

68009260001-A January 2009 GL-3

Glossary

SAT — System Administration Terminal

SI — System Integration

SIP — Session Initiation Protocol

SMSC — Short Message Service Center

SNMP — Simple Network Management Protocol

SSID — Service Set Identifier

SU — Subscriber Unit

TKIP — Temporal Key Integrity Protocol

TLS — Transport Layer Security

U-APSD — Unscheduled Automatic Power Save Delivery

URL — Uniform Resource Locator

USB — Universal Serial Bus

VLR — Visitor Location Register

VoIP — Voice over Internet Protocol

VoWLAN — Voice over Wireless Local Area Network

WFA — Wi-Fi Alliance

WMM — Wi-Fi Multimedia

WMM-PS — WMM Power Save

WMM-AC — WMM Admission Control

WPA — WiFi Protected Access

WLAN — Wireless Local Area Network

WSM — Wireless Services Manager

WSMCC — WSM Call Control

GL-4 68009260001-A January 2009

Index

Index■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

802.11 a/b/g — bands and speeds . . . . . . . . 1-22 911 . . . . . . . . . . . . . . . . . . . . . . A-5

A■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

AAA . . . . . . . . . . . . . . . . . . . . . 2-11abbreviated dialing . . . . . . . . . . . . . . . A-3AP requirements for data networks . . . . . . . 2-24architecture . . . . . . . . . . . . . . . . . . 1-4assessing your environment . . . . . . . . . . . 3-1assumptions for deployment. . . . . . . . . . . 3-10

Authentication, Authorization, and Accounting (AAA)server . . . . . . . . . . . . . . . . . . . . . 2-11Avaya IP-PBX specifications . . . . . . . . . . 2-17Avaya media gateways . . . . . . . . . . . . . 2-17Avaya media servers . . . . . . . . . . . . . . 2-17Avaya PBX solutions . . . . . . . . . . . . . . 2-17

B■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

backhaul network. . . . . . . . . . . . . . . . 1-9backhaul network considerations . . . . . . . . 3-15backhaul network equipment . . . . . . . . . . 2-21bands and speeds, 802.11 a/b/g . . . . . . . . . 1-22

benefits of the TEAM solution. . . . . . . . . . 1-3bridged Call Appearance (CA) . . . . . . . . A-13busy indicator . . . . . . . . . . . . . . . . . A-6

C■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

calendar, . . . . . . . . . . . . . . . . . . . A-11call alert . . . . . . . . . . . . . . . . . 1-15, A-8Call Forwarding (CF) . . . . . . . . . . . . . . A-2call hold . . . . . . . . . . . . . . . . . . . . A-2call restriction . . . . . . . . . . . . . . . . . A-6call scenarios. . . . . . . . . . . . . . . . . A-12call state updates . . . . . . . . . . . . . . . A-13call transfer . . . . . . . . . . . . . . . . . . A-3Call Waiting (CW) . . . . . . . . . . . . . . . A-2caller ID . . . . . . . . . . . . . . . . . . . . A-3CDR processing server . . . . . . . . . . . . . 2-19Cisco Access Points (APs) . . . . . . . . . . . 2-29

Cisco APs . . . . . . . . . . . . . . . . . . . 2-29Cisco CME PBX . . . . . . . . . . . . . . . . 2-18Cisco CUCM PBX . . . . . . . . . . . . . . . 2-18Cisco PBX . . . . . . . . . . . . . . . . . . . 2-18Cisco RF switches . . . . . . . . . . . . . . . 2-29Cisco WLAN hardware . . . . . . . . . . . . . 2-28codecs . . . . . . . . . . . . . . . . . . . . . 1-24compatible hardware . . . . . . . . . . . . . . 3-4compatible software versions . . . . . . . . . . 3-4components . . . . . . . . . . . . . . . . . . 1-4conference calling . . . . . . . . . . . . . . . A-3corporate e-mail . . . . . . . . . . . . . . . A-11

D■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

data features . . . . . . . . . . . . . . . . . . A-9data network, AP requirements . . . . . . . . . 2-24deploying 802.11a/b/g . . . . . . . . . . . . . 3-14device management client . . . . . . . . . . . . 1-17device provisioning client . . . . . . . . . . . . 1-17DHCP . . . . . . . . . . . . . . . . . . . . . 2-10Dialogic solutions . . . . . . . . . . . . . . . 2-18

Direct Inward Dialing (DID) . . . . . . . . . . A-1Direct Outward Dialing (DOD) . . . . . . . . . A-2directory server . . . . . . . . . . . . . . . . 2-19directory service . . . . . . . . . . . . . . . A-11DNS. . . . . . . . . . . . . . . . . . . . . . 2-10Domain Name Server (DNS) . . . . . . . . . . 2-10DTMF (overdial) support . . . . . . . . . . . . A-5

68009260001-A January 2009 IX-1

Index

Dynamic Host Configuration Protocol(DHCP) . . . . . . . . . . . . . . . . . . . . 2-10

E■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

EAP--TLS . . . . . . . . . . . . . . . . . . . 2-11echo cancellation . . . . . . . . . . . . . . . . 1-25enterprise control servers . . . . . . . . . . 1-7, 2-10

enterprise equipment checklist. . . . . . . . . . B-1equipment checklists . . . . . . . . . . . . . . B-1evaluating the coverage area . . . . . . . . . . 3-6

F■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

firewalls . . . . . . . . . . . . . . . . . . . . 3-15 frequency bands . . . . . . . . . . . . . . . . 3-14

G■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

group call . . . . . . . . . . . . . . . . 1-15, A-8

I■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

IEEE . . . . . . . . . . . . . . . . . . . . . 1-21IM . . . . . . . . . . . . . . . . . . . . . . A-9initial site install/pre-sale . . . . . . . . . . . . 3-2installation activities . . . . . . . . . . . . . . 3-2Instant Messaging (IM) . . . . . . . . . . . . . A-9Institute of Electrical and Electronic Engineers(IEEE). . . . . . . . . . . . . . . . . . . . . 1-21

International Telecommunications Union-Telephony(ITU-T) . . . . . . . . . . . . . . . . . . . . 1-24IP evaluation and planning . . . . . . . . . . . 3-5IP to TDM gateways . . . . . . . . . . . . . . 2-17IP-PBX . . . . . . . . . . . . . . . . . . . . 2-17IPsec requirements . . . . . . . . . . . . . . . 2-38ITU-T . . . . . . . . . . . . . . . . . . . . . 1-24

K■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

key concepts of the TEAM solution . . . . . . . 1-18

L■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

LAN devices . . . . . . . . . . . . . . . . . . 3-15LAN links . . . . . . . . . . . . . . . . . . . 3-16Line of Business (LOB) applications. . . . . . A-12

LMT interface . . . . . . . . . . . . . . . . . 2-6Local Area Network (LAN) devices . . . . . . . 3-15Local Maintenance Terminal (LMT) interface . . 2-6

M■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

management applications . . . . . . . . . . . . 1-12micro mobility . . . . . . . . . . . . . . . . . 1-19Microsoft Exchange . . . . . . . . . . . . . . 2-20missed PTT call indication . . . . . . . . . . . A-9Motorola enterprise. . . . . . . . . . . . . . . 2-26Motorola Integration Server . . . . . . . . . . . 2-13Motorola SW Update (MSU) . . . . . . . . . . 2-20Motorola-specific applications on the smart-phone . . . . . . . . . . . . . . . . . . . . . 1-16Motorola/Symbol Access Points (APs) . . . . . . 2-26

Motorola/Symbol APs . . . . . . . . . . . . . 2-26Motorola/Symbol PoE ethernet switch . . . . . . 2-27Motorola/Symbol RF switches . . . . . . . . . 2-27Motorola/Symbol WLAN hardware . . . . . . . 2-26Motorola’s Enterprise Mobility Support Center . . -xvMotorola’s Support Central Website . . . . . . . -xviMS LCS . . . . . . . . . . . . . . . . . . . . 2-21MS SMS. . . . . . . . . . . . . . . . . . . . 2-20MS Text Messaging (MS SMS) . . . . . . . . . 2-20

IX-2 68009260001-A January 2009

TEAM 1.7 System Solution Overview and Planning Guide Index

N■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Network Time Protocol (NTP) server . . . . . . 2-13network topology maps . . . . . . . . . . . . . 3-18Nortel PBX . . . . . . . . . . . . . . . . . . 2-18NSM applications . . . . . . . . . . . . . . . 1-12NSM features . . . . . . . . . . . . . . . . . 2-7

NSM server application . . . . . . . . . . . . . 2-7NSM server hardware requirements . . . . . . . 2-8NSM server software requirements . . . . . . . 2-8NSM software . . . . . . . . . . . . . . . . . 2-9NTP server. . . . . . . . . . . . . . . . . . . 2-13

O■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

other enterprise servers . . . . . . . . . . . . . 2-19 overdial (DTMF) support . . . . . . . . . . . . A-5

P■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

PBX (telephony servers) . . . . . . . . . . . . 2-13PBX hardware specifications . . . . . . . . . . 2-14PBX software specifications. . . . . . . . . . . 2-14PBX-IP . . . . . . . . . . . . . . . . . . . . 2-17phonebook . . . . . . . . . . . . . . . . . . A-11placement of Access Points (APs) . . . . . . . . 3-10planning for deployment . . . . . . . . . . . . 3-1planning for implementation . . . . . . . . . . 3-1planning the WLAN network . . . . . . . . . . 3-5

PoE ethernet switch. . . . . . . . . . . . . . . 2-27presence . . . . . . . . . . . . . . . . . . . . A-9private call . . . . . . . . . . . . . . . . 1-15, A-7PTT caller ID . . . . . . . . . . . . . . . . . A-8PTT features . . . . . . . . . . . . . . . . . . 1-15PTT voice messaging features . . . . . . . . . . A-7public key infrastructure . . . . . . . . . . . . 2-13Push-to-Talk (PTT) features . . . . . . . . . . . 1-15Push-to-Talk (PTT) voice messaging features. . . A-7

Q■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

QoS . . . . . . . . . . . . . . . . . . . . . . 2-36Qos 911 dialing . . . . . . . . . . . . . . . . 2-38QoS AP bandwidth reservation . . . . . . . . . 2-37QoS gateway bandwidth reservation . . . . . . . 2-37QoS mechanisms for the WLAN . . . . . . . . 2-37QoS packet classification . . . . . . . . . . . . 2-37

QoS roles by system component . . . . . . . . . 3-21QoS section 508 compliance . . . . . . . . . . 2-38qualifying an existing infrastructure asvoice-capable . . . . . . . . . . . . . . . . . 3-6Quality of Service (QoS) . . . . . . . . . . . . 2-36

R■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

rack requirements . . . . . . . . . . . . . . . 3-18RADIUS (AAA) . . . . . . . . . . . . . . . . 2-11related documentation . . . . . . . . . . . . . -xiv

roaming across Access Points (APs) . . . . . . . 3-11roaming across subnets . . . . . . . . . . . . . 3-12

S■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

security . . . . . . . . . . . . . . . . . . . . 3-19Session Initiation Protocol (SIP) . . . . . . . . . 1-24shared device . . . . . . . . . . . . . 1-17 to 1-18shared device/pool . . . . . . . . . . . . . . . 1-18shared pool . . . . . . . . . . . . . . 1-17 to 1-18simultaneous voice and data calls . . . . . . . A-11SIP . . . . . . . . . . . . . . . . . . . . . . 1-24site surveys . . . . . . . . . . . . . . . . . . 3-7smartphone . . . . . . . . . . . . . . . 1-11, 2-31

smartphone features . . . . . . . . . . . . . . 2-32smartphone software . . . . . . . . . . . . . . 2-34smartphone technical specifications . . . . . . . 2-31smartphone telephony features . . . . . . . . . A-1smartphone voice client . . . . . . . . . . . . . 2-34smartphone VoIP client . . . . . . . . . . . . . 2-34smartphone, Motorola-specific applications . . . 1-16smartphone, third-party applications . . . . . . . 1-17standard browser support . . . . . . . . . . . A-11

68009260001-A January 2009 IX-3

Index

standards-based design . . . . . . . . . . . . . 1-21subscriber states . . . . . . . . . . . . . . . A-12system architecture . . . . . . . . . . . . . . . 1-6

system management client . . . . . . . . . . . 1-17system overview . . . . . . . . . . . . . . . . 1-1system provisioning client . . . . . . . . . . . 1-17

T■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

talkgroup selection . . . . . . . . . . . . . . . A-9task . . . . . . . . . . . . . . . . . . . . . A-11TEAM data services . . . . . . . . . . . . . . 1-15TEAM equipment . . . . . . . . . . . . . 1-7, 2-3TEAM features and services . . . . . . . . . . 1-14TEAM services and features . . . . . . . . . . 1-14telephone numbering scheme . . . . . . . . . . 1-20telephony features . . . . . . . . . . . . . . . 1-14

telephony servers (PBX) . . . . . . . . . . . . 2-13telephony-related servers . . . . . . . . . . . . 2-18terminology . . . . . . . . . . . . . . . . . . 1-3text messaging . . . . . . . . . . . . . . . . A-10theory of operations . . . . . . . . . . . . . . 2-1third-party applications on the smartphone . . . . 1-17third-party enterprise servers . . . . . . . . . . 1-8typical customers . . . . . . . . . . . . . . . . 1-3

V■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

vocoders . . . . . . . . . . . . . . . . . . . . 1-24voice mail considerations . . . . . . . . . . . . 3-17voice mail indication . . . . . . . . . . . . . . A-4voice mail server . . . . . . . . . . . . . . . . 2-18

voice network considerations . . . . . . . . . . 3-16Voice over IP (VoIP) . . . . . . . . . . . . . . 1-1VoIP. . . . . . . . . . . . . . . . . . . . . . 1-1

W■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

WFA . . . . . . . . . . . . . . . . . . . . . 1-22Wi-Fi Alliance (WFA) . . . . . . . . . . . . . 1-22Wi-Fi Multimedia (WMM) . . . . . . . . . . . 1-23Windows Mobile 6.1 Features . . . . . . . . . . 1-16Wireless LAN (WLAN). . . . . . . . . . . . . 1-9WLAN . . . . . . . . . . . . . . . . . . . . 1-9WLAN and backhaul network . . . . . . . . . . 2-30WLAN call hold . . . . . . . . . . . . . . . A-13WLAN call origination . . . . . . . . . . . . A-13WLAN call toggle . . . . . . . . . . . . . . A-14WLAN conference . . . . . . . . . . . . . . A-14WLAN end of call . . . . . . . . . . . . . . A-14WLAN equipment . . . . . . . . . . . . . . . 2-22WLAN equipment checklist . . . . . . . . . . . B-2WLAN industry standard requirements. . . . . . 2-24WLAN network . . . . . . . . . . . . . . . . 1-2

WLAN network planning . . . . . . . . . . . . 3-5WLAN status change . . . . . . . . . . . . . A-15WMM . . . . . . . . . . . . . . . . . . . . . 1-23WMM Power Save (WMM-PS) . . . . . . . . . 1-23WMM-AC – Admission Control (Future) . . . . 1-23WMM-PS . . . . . . . . . . . . . . . . . . . 1-23WSM , key functions . . . . . . . . . . . . . . 2-3WSM appliance . . . . . . . . . . . . . . . . 2-5WSM configuration. . . . . . . . . . . . . . . 2-5WSM features . . . . . . . . . . . . . . . . . 2-3WSM LEDs . . . . . . . . . . . . . . . . . . 2-6WSM ports . . . . . . . . . . . . . . . . . . 2-6WSM software . . . . . . . . . . . . . . . . . 2-6WSM technical specifications . . . . . . . . . . 2-6WSM, role in calls . . . . . . . . . . . . . . . 2-4WSM, system responsibilities . . . . . . . . . . 2-4

IX-4 68009260001-A January 2009