TEAM 1.7 Solution Overview and Planning Guide 68009260001-A

Total Enterprise Access and Mobility (TEAM) Solution
TEAM 1.7 Solution Overview and Planning Guide
January 2009
68009260001-A
*68009260001*
2009 Motorola, Inc. All rights reserved.
Copyrights The Motorola products described in this document may include copyrighted Motorola computer programs. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola computer programs contained in the 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 the copyrights, patents or patent applications of Motorola, except for the normal nonexclusive, royalty-free license to use that arises by operation of law in the sale of 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, or may be dependent upon the characteristics of a particular mobile subscriber unit or conguration of certain parameters. Please refer to your Motorola contact for further information. Trademarks MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Ofce. All other product or service names are the property of their respective 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 by any means, without the prior written permission of Motorola, Inc.
Document History
Document History

Edition 1st Release
Description Original release of TEAM 1.7 Solution Overview and Planning Guide
Date January 2009
68009260001-A
January 2009
Document History
ii
68009260001-A
January 2009
Table of Contents
Contents

TEAM 1.7 System Solution Overview and Planning Guide

Contacting Motorolas Enterprise Mobility Support Center . Contacting Motorolas Support Central Website . . . . . . Regulatory Information . . . . . . . . . . . . . . . . . Device Country Approvals. . . . . . . . . . . . . . Health and Safety Recommendations . . . . . . . . . Radio Frequency Interference Requirements - FCC . . Radio Frequency Interference Requirements - Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xv -xvi -xvi -xvi -xvii -xvii -xvii
Chapter 1: System Overview

Introduction to the TEAM Solution . . . . . . . . . . . . . . . . . . . . . . Voice over IP (VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . WLAN Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . Benets of the TEAM Solution . . . . . . . . . . . . . . . . . . . . . Typical Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology Overview . . . . . . . . . . . . . . . . . . . . . . . . . Architecture and Components . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the Architecture . . . . . . . . . . . . . . . . . . . . . System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . Solution Equipment . . . . . . . . . . . . . . . . . . . . . . . . . Backhaul Network . . . . . . . . . . . . . . . . . . . . . . . . . Wireless LAN (WLAN) . . . . . . . . . . . . . . . . . . . . . . . TEAM smartphone . . . . . . . . . . . . . . . . . . . . . . . . . NSM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Applications . . . . . . . . . . . . . . . . . . . . . . . . Management Applications . . . . . . . . . . . . . . . . . . . . . . Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TEAM Voice Services . . . . . . . . . . . . . . . . . . . . . . . . . . Telephony Features Overview . . . . . . . . . . . . . . . . . . . . PTT Feature Overview . . . . . . . . . . . . . . . . . . . . . . . TEAM Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Mobile 6.1 Features . . . . . . . . . . . . . . . . . . . . Motorola-Specic Applications on the TEAM smartphone . . . . . . . Third-Party Applications on the TEAM smartphone . . . . . . . . . . Shared Device/Pool Feature . . . . . . . . . . . . . . . . . . . . . . . Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shared Device/Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . Use case example: . . . . . . . . . . . . . . . . . . . . . . . . . A specic example of PBX services associated with the shared devices: Micro Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1-1 1-2 1-3 1-3 1-3 1-4 1-4 1-6 1-6 1-9 1-9 1-11 1-12 1-12 1-13 1-14 1-14 1-14 1-15 1-15 1-16 1-16 1-17 1-17 1-18 1-18 1-18 1-19 1-19
68009260001-A
January 2009
iii
Contents
Example Scenarios . . . . . . . . . . . . Telephone Numbering Scheme . . . . . . . . . Introduction . . . . . . . . . . . . . . . Telephone Numbering Scheme Example . Standards-Based Design . . . . . . . . . . . . . . IEEE . . . . . . . . . . . . . . . . . . . . . 802.11 a/b/g Bands and Speeds . . . . . Wi-Fi Alliance (WFA) . . . . . . . . . . . . . Wi-Fi Multimedia (WMM) . . . . . . . . . . WMM-PS . . . . . . . . . . . . . . . . WMM-AC Admission Control (Future). . Session Initiation Protocol (SIP) . . . . . . . . ITU-T . . . . . . . . . . . . . . . . . . . . Codecs/Vocoders . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
1-19 1-20 1-20 1-21 1-21 1-21 1-22 1-22 1-23 1-23 1-23 1-24 1-24 1-24
Chapter 2: Theory of Operations

System Architecture . . . . . . . . . . . . . . . . . . Equipment . . . . . . . . . . . . . . . . . . . . . . TEAM Equipment . . . . . . . . . . . . . . . . WSM . . . . . . . . . . . . . . . . . . . . NSM Server Application . . . . . . . . . . . Enterprise Control Servers . . . . . . . . . . . . . DHCP . . . . . . . . . . . . . . . . . . . . DNS . . . . . . . . . . . . . . . . . . . . . EAP-TLS . . . . . . . . . . . . . . . . . . RADIUS (AAA) . . . . . . . . . . . . . . . Network Time Protocol (NTP) Server . . . . . Motorola Integration Server . . . . . . . . . . PBX (Telephony Servers) . . . . . . . . . . . . . Hardware and Software Specications . . . . . IP-PBX . . . . . . . . . . . . . . . . . . . IP to TDM Gateways . . . . . . . . . . . . . Cisco PBX . . . . . . . . . . . . . . . . . . . . Nortel PBX . . . . . . . . . . . . . . . . . . . . Telephony-Related Servers. . . . . . . . . . . . . Voice Mail Server. . . . . . . . . . . . . . . CDR Processing Server . . . . . . . . . . . . Directory Server . . . . . . . . . . . . . . . Other Enterprise Servers . . . . . . . . . . . . . . Network Management. . . . . . . . . . . . . Device/System Provisioning/Management . . . Email . . . . . . . . . . . . . . . . . . . . MS LCS and Others. . . . . . . . . . . . . . Backhaul Network Equipment . . . . . . . . . . . . . Routers. . . . . . . . . . . . . . . . . . . . . . Switches . . . . . . . . . . . . . . . . . . . . . WLAN Equipment (Multiple Vendors) . . . . . . . . . Industry Standard Requirements and Features . . . . Minimum AP Requirements for Data Networks . Recommended Capabilities . . . . . . . . . . Wireless Features . . . . . . . . . . . . . . . Layer 2 Features . . . . . . . . . . . . . . . Power over Ethernet (PoE) . . . . . . . . . . Policy Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2-2 2-3 2-3 2-7 2-10 2-10 2-10 2-11 2-11 2-13 2-13 2-13 2-14 2-17 2-17 2-18 2-18 2-18 2-18 2-19 2-19 2-19 2-20 2-20 2-20 2-21 2-21 2-22 2-22 2-22 2-24 2-24 2-25 2-25 2-25 2-25 2-26
iv
68009260001-A
January 2009
Contents
Motorola Enterprise WLAN . . . . . . . . . Hardware. . . . . . . . . . . . . . . . Cisco. . . . . . . . . . . . . . . . . . . . Hardware. . . . . . . . . . . . . . . . WLAN and Backhaul Network Specications . . . TEAM smartphone . . . . . . . . . . . . . . . Technical Specications . . . . . . . . . . . Features . . . . . . . . . . . . . . . . . . Photo. . . . . . . . . . . . . . . . . . . . Software . . . . . . . . . . . . . . . . . . VoIP Client Voice Client . . . . . . . Screenshots. . . . . . . . . . . . . . . Quality of Service (QoS). . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . QoS Mechanisms for the Wireless LAN . . . Packet Classication . . . . . . . . . . . . Access Point/Gateway Bandwidth Reservation 911 Dialing . . . . . . . . . . . . . . . . Section 508 Compliance . . . . . . . . . . . IPsec Requirements . . . . . . . . . . . . . . . IPsec Between NSM-WSM . . . . . . . . . IPsec Between WSM-PBX. . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
2-26 2-26 2-28 2-28 2-30 2-31 2-31 2-32 2-33 2-34 2-34 2-35 2-36 2-36 2-37 2-37 2-37 2-38 2-38 2-38 2-39 2-39
Chapter 3: Planning for Deployment

Assessing Your Environment . . . . . . . . . . . . . . . Planning for Implementation . . . . . . . . . . . . . . Installation Activities . . . . . . . . . . . . . . . . . . Initial Site Install/Pre-sale . . . . . . . . . . . . . . Compatible Hardware and Software Versions . . . . . IP Evaluation and Planning . . . . . . . . . . . . . . . Planning the WLAN Network . . . . . . . . . . . . Considerations for the WLAN . . . . . . . . . . . . Evaluating the Coverage Area . . . . . . . . . . . . Qualifying an Existing Infrastructure as Voice-Capable Quality of Service Considerations . . . . . . . . Site Surveys . . . . . . . . . . . . . . . . . . . . General Steps to Conduct a Site Survey. . . . . . Placement of Access Points . . . . . . . . . . . . . Roaming Across Access Points . . . . . . . . . Roaming Across Subnets . . . . . . . . . . . . Frequency Bands . . . . . . . . . . . . . . . . . . Considerations for Deploying 802.11a/b/g . . . . Firewalls . . . . . . . . . . . . . . . . . . . . . . Backhaul Network Considerations . . . . . . . . . . . . Local Area Network (LAN) Devices . . . . . . . . . LAN Links . . . . . . . . . . . . . . . . . . . . . Voice Network Considerations . . . . . . . . . . . . . . Voice Mail Considerations . . . . . . . . . . . . . . . . Network Topology Maps. . . . . . . . . . . . . . . . . Additional Guidelines and Requirements . . . . . . . . . Rack Requirements . . . . . . . . . . . . . . . . . Required Information . . . . . . . . . . . . . . . . Security . . . . . . . . . . . . . . . . . . . . . . . . Quality of Service Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 3-1 3-2 3-2 3-4 3-5 3-5 3-6 3-6 3-6 3-7 3-7 3-8 3-10 3-11 3-12 3-14 3-14 3-15 3-15 3-15 3-16 3-16 3-17 3-18 3-18 3-18 3-18 3-19 3-21
68009260001-A
January 2009
Contents
Overview of QoS Roles by System Component . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Appendix A: Detailed Features of the TEAM smartphone

Telephony Features . . . . . . . . . . . . . . . . . . . Make and Receive Phone Calls. . . . . . . . . . . . Direct Inward Dialing Plans . . . . . . . . . . . Direct Outward Dialing Plans . . . . . . . . . . Call Forwarding. . . . . . . . . . . . . . . . . . . Call Waiting . . . . . . . . . . . . . . . . . . . . Call Hold . . . . . . . . . . . . . . . . . . . . . . Call Transfer . . . . . . . . . . . . . . . . . . . . Caller ID . . . . . . . . . . . . . . . . . . . . . . Abbreviated Dialing . . . . . . . . . . . . . . . . . Conference Calling (Ad Hoc, Meet-Me) . . . . . . . Voice Mail Indication and Retrieval Scenarios. . . . . Messaging . . . . . . . . . . . . . . . . . . . Voicemail Notication/Message Waiting Indication Message Retrieval and Playback . . . . . . . . . DTMF (Overdial) Support . . . . . . . . . . . . . . 911. . . . . . . . . . . . . . . . . . . . . . . . . Call Restriction . . . . . . . . . . . . . . . . . . . Busy Indicator . . . . . . . . . . . . . . . . . . . PTT Features . . . . . . . . . . . . . . . . . . . . . . Private Call . . . . . . . . . . . . . . . . . . . . . Call Alert. . . . . . . . . . . . . . . . . . . . . . Group Call . . . . . . . . . . . . . . . . . . . . . PTT Caller ID . . . . . . . . . . . . . . . . . . . Missed PTT Call Indication . . . . . . . . . . . . . Talkgroup Selection . . . . . . . . . . . . . . . . . Presence/Instant Messaging . . . . . . . . . . . . . Data Features . . . . . . . . . . . . . . . . . . . . . . Text Messaging . . . . . . . . . . . . . . . . . . . Simultaneous Voice and Data . . . . . . . . . . . . Corporate E-mail . . . . . . . . . . . . . . . . . . Calendar, Phonebook, and Task . . . . . . . . . . . Directory Service . . . . . . . . . . . . . . . . . . Standard Browser Support . . . . . . . . . . . . . . Line of Business Applications . . . . . . . . . . . . Call Scenarios. . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . Subscriber States . . . . . . . . . . . . . . . . Bridged Call Appearance . . . . . . . . . . . . . . Call State Updates. . . . . . . . . . . . . . . . . . WLAN Call Hold/Remove Hold . . . . . . . . . . . WLAN Call Origination . . . . . . . . . . . . . . . WLAN Call Toggle . . . . . . . . . . . . . . . . . WLAN Conference . . . . . . . . . . . . . . . . . WLAN End of Call . . . . . . . . . . . . . . . . . WLAN Incoming Call . . . . . . . . . . . . . . . . WLAN Status Change . . . . . . . . . . . . . . . . Call Forwarding . . . . . . . . . . . . . . . . Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 A-1 A-1 A-2 A-2 A-2 A-2 A-3 A-3 A-3 A-3 A-4 A-4 A-4 A-5 A-5 A-5 A-6 A-6 A-7 A-7 A-8 A-8 A-8 A-9 A-9 A-9 A-9 A-10 A-11 A-11 A-11 A-11 A-11 A-12 A-12 A-12 A-12 A-13 A-13 A-13 A-13 A-14 A-14 A-14 A-14 A-15 A-15 A-15
vi
68009260001-A
January 2009
Contents
Appendix B: Equipment Checklists

Enterprise Equipment Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WLAN Equipment Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 B-2
Glossary
68009260001-A
January 2009
vii
Contents
This page intentionally left blank.
viii
68009260001-A
January 2009
List of Figures
List of Figures

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

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

The Total Enterprise & Mobility (TEAM) solution is a Voice over WLAN (VoWLAN) hardware and software solution that includes a TEAM smartphone combined with enterprise server software. 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; a high-level description of its system architecture, components, and features. Chapter 2, "Theory of Operations" This chapter provides a description of how the system works. Chapter 3, "Planning for Deployment" This chapter provides a description of the system deployment considerations. Appendix A, "Detailed Features of the TEAM smartphone" This appendix provides a 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 Information

The Motorola technical training team offers a variety of courses designed to assist in learning about the system. Class registration is available at www://edu.symbol.com. The online courses are: TEAM product specic technical certication (course number: EDUCEC4000) TEAM product specic sales certication (course number: EDUCEC3000)
Instructional Lead courses are : TEAM Instructional Lead product technical course (course number: EDUCEC 400)
Related Information
Refer to the following documents for associated information about the system. Document name TEAM Solution Installation and Conguration (68009262001-A) TEAM Solution System Administration Guide (68009263001-A) TEAM Solution Subscriber Provisioning Guide (68009261001-A) Purpose Describes how to install TEAM hardware and software. Lists the required and optional equipment in the system. Provides troubleshooting information. Describes the day-to-day operational tasks that need to be performed in the TEAM solution. Provides information to provision the subscribers and TEAM smartphones of the solution.
xiv
68009260001-A
January 2009
Contacting Motorolas Enterprise Mobility Support Center
Document name EWP1000/2000 Series Users Guide (6871009P12-A)
Purpose Describes the TEAM smartphone hardware (physical device) and software. Includes information on how to use the client software to perform daily job functions. Describes how to troubleshoot the TEAM smartphone hardware and reset the device. Also describes error messages and provides contacts for service/support. Covers Installation and Setup/Provisioning. Describes the Network Services Manager (NSM) software that provides a number of services for conguring, monitoring and managing the Wireless Services Manager (WSM) in a WLAN environment.
Enterprise WiFi Phone Service Manual (6802983C90-B)
NSM User Guide (part number 6871009P18-A)
Contacting Motorolas Enterprise Mobility Support Center

If you have a problem with your equipment, contact Enterprise Mobility support for your region. Contact information 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 and online 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 activation key 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 support agreements. If you purchased your Enterprise Mobility business product from a Motorola business partner, contact that business partner for support.
68009260001-A
January 2009
xv
Contacting Motorolas Support Central Website
Contacting Motorolas Support Central Website

Motorolas Support Central Web site, accessed via the Symbol-branded products link under Business Support, provides information and online assistance including developer tools, software downloads, product manuals and online repair requests.
Regulatory Information

This device (Model Number WSMHW) is approved under the Symbol Technologies brand: Symbol Technologies, Inc., is the Enterprise Mobility business of Motorola, Inc. (Motorola). All Motorola devices are designed to be compliant with rules and regulations in locations they are sold and are labeled as required. Any changes or modications to Motorola equipment, not expressly approved by Motorola, could void the users authority to operate the equipment.
Device Country Approvals

Regulatory markings, subject to certication, are applied to the device is approved for use in the following countries: United States and Canada. Please refer to the Motorola Declaration of Conformity (DoC) for details of other country markings. 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 will make the operation of this device illegal.
xvi
68009260001-A
January 2009
Health and Safety Recommendations
Health and Safety Recommendations

Ergonomic Recommendations
In order to avoid or minimize the potential risk of ergonomic injury follow the recommendations below. Consult with your local Health & Safety Manager to ensure that you are adhering to your companys safety 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 - FCC

This 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 protection against harmful interference when the equipment is operated in commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance 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 which case the user will be required to correct the interference at his own expense.
Radio Frequency Interference Requirements - Canada

This Class A digital apparatus complies with Canadian ICES-003. Cet appareil numrique 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
System Overview

Total Enterprise Access & Mobility (TEAM) is a cost-competitive wireless TEAM smartphone system that delivers voice and data communication services within an Enterprise to on-campus workers. TEAM leverages unlicensed Wi-Fi spectrum, WLAN infrastructure, and existing telephony infrastructure to 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 customer databases or Web-based applications.
The TEAM solution is a wireless communication network that facilitates mobile voice and data communication using PBX telephony. The solution includes WLAN TEAM smartphones with VoIP along with server software. The system interfaces with Enterprise communication networks using the latest 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 level of operator training and expertise.
Introduction to the TEAM Solution

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

A Voice over IP (VoIP) telephony system is built on a single, shared IP-based packet network. A packet-based network provides the foundation that can carry many types of information, including data, audio, and video. The challenge with such a network is separating and prioritizing the various
68009260001-A
January 2009
1-1
WLAN Network
types of trafc. A VoIP telephony system provides services and reliability comparable to traditional telephony systems. This converged network offers cost benets, as you can install and administer a voice and data network together and use an existing IP network for voice trafc. Integrating voice and data on one network infrastructure makes it easier to deploy business applications that bring together voice, data, and video across the Enterprise. When networks are built on industry-standard operating systems and protocols, rather than on proprietary systems, it becomes simpler and less costly for 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 benets from each network, providing seamless, contiguous voice and data communication throughout the Enterprise, using the TEAM smartphone. TEAM, in using VoIP, follows the industry in moving from analog circuit-based legacy PBXs or 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 Network
A 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 TEAM smartphones and laptops within an Enterprise. The TEAM solution utilizes WLAN in Infrastructure Mode, 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 the network. 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 connected to the wired Enterprise network through wireless switches and/or AP controllers and local switches. The APs can (alone, or in conjunction with AP controllers) perform additional functions, such as helping to encrypt wireless trafc, prioritizing wired network trafc, isolating wireless devices into multiple wireless service sets using Service Set Identier (SSID), and so on. The existing wired IP infrastructure is 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 allow the 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 handle bearer (voice) trafc for PTT calls. With unicast, only those APs that handle the appropriate subnets where the TEAM smartphones are associated are illuminated by a PTT call (such as a group call). Other solutions use multicast, in which Internet Group Management Protocol (IGMP) must be implemented to let the network know where the TEAM smartphone is located. Otherwise, all the APs in the network are illuminated for a call, implying a non-optimized use of RF resources.
1-2
68009260001-A
January 2009
Benets of the TEAM Solution
Benets of the TEAM Solution

The benets 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 charges by leveraging Enterprise networks. Provides Call Detail Recording (CDR) for billing purposes. Improves employee mobility and accessibility.
Increases worker collaboration and productivity Provides a common user experience and feature transparency. Provides unied security and management features.
Typical Customers
The typical customer for the TEAM solution is always on site and makes constant use of both voice 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 Overview
The use of common terminology is important to ensure that roles are clearly dened 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 system administrator. The operator is known by different names, depending on the interface, for example, the Network Services Manager (NSM) operator includes these roles: WSM Provisioning Client User, Account Administrator, or Site Operator. TEAM smartphone Refers to the physical TEAM smartphone. This TEAM smartphone is also known as the device, handset, Mobile Station (MS), or Subscriber Unit (SU).
68009260001-A
January 2009
1-3
Architecture and Components
Subscriber A person who uses the TEAM smartphone on the system, that is, 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, such as infrastructure, network, and TEAM smartphone.
Introduction to the Architecture

The 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 conguration.
The TEAM smartphone provides audio (telephony and PTT) and data (text messaging), along with a full Windows Mobile 6.1 mobile computing platform, providing many features (such as, e-mail and Web 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 a secure voice-enabled WLAN. Also, inside the Enterprise, the solution supports secure, always-on wireless mobile 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
Introduction to the Architecture
Figure 1-1
TEAM System Diagram
DMZ stands for Demilitarized Zone. It refers to the buffer zone that separates the Internet and the private LAN.
68009260001-A
January 2009
1-5
System Architecture
System Architecture
The 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 solution has one WSM, one NSM , and one PBX. Depending on the Enterprise, it also has one set of Enterprise Control servers (AAA, DHCP, and DNS), and one set of other Enterprise feature servers (such as, e-mail servers and application servers).
1-6
68009260001-A
January 2009
TEAM Equipment
TEAM Equipment
The Wireless Services Manager (WSM) provides the following functions: Telephony calls Provides interconnect call control between the TEAM smartphone and the PBX. PTT/Two-way radio Provides oor control and call control for PTT calls and Call Alert, independent of the PBX.
The Network Services Manager (NSM) is a Motorola server that provides the interface that allows the system operator to set various system conguration parameters and perform network management tasks. Major functions supported include: Fault Management Provides cataloging, reporting, and alarming functions for faults received from the WSM. Conguration Management Provides conguration functions for the WSM. Performance Management Provides performance measurement, data collection, and basic analysis functions. Security Management Provides secured access to network management functions through a user/role model. Interface to provisioning functions The NSM provides the interface to subscriber provisioning functions, through the WSM Provisioning Client.
Enterprise Control Servers

Customers supply and maintain their own Enterprise control servers, except for the Motorola Integration Server that is provided by Motorola. TEAM has a vendor-agnostic approach (standards based) to the Enterprise servers, which means that customers can reuse existing equipment, if the equipment meets the requirements specied in WLAN and Backhaul Specications. Table 1-1 lists the Enterprise control servers. Table 1-1 Enterprise Control Servers Server Dynamic Host Conguration Protocol (DHCP) Domain Name Service (DNS) Purpose Used to assign/manage IP addresses. Used to resolve domain names into IP addresses and vice versa.
68009260001-A
January 2009
1-7
Other Enterprise Servers
Table 1-1
Enterprise Control Servers (Continued) Server Purpose Stores user credentials that are used to authenticate TEAM smartphones and subscribers. Used to provide system timing synchronization among the different system components by receiving accurate time from a network time server. NTP is a standard protocol for sharing time of day information between networked devices. Optionally available to activate the WSM. Used by the Enterprise to obtain licenses and permission to activate the WSM. This is a Motorola-provided Internet Web service.
Authentication, Authorization, and Accounting (AAA) Network Time Protocol Server (NTP)
Motorola Integration Server
Table 1-2 lists the telephony and telephony-related servers. Table 1-2 Telephony and Telephony-Related Servers Server IP-PBXs (provided by Avaya, Nortel, and Cisco) Purpose SIP-based network element that provides telephony services to the Enterprise. Comprises a signaling server and media gateway subcomponents. Converts legacy TDM telephony signals to SIP signaling and vice versa. Provides interface to TDM PBXs. A telephony-related server that processes CDRs.
IP to TDM Gateway (provided by Dialogic) Call Detail Records (CDRs) processing server

Customers supply and maintain their own third-party Enterprise servers. These are optional components that can be added by an Enterprise on an as-needed basis. The system may have these or other additional Enterprise servers: Network Management SystemProvides an integrated view of system components and the Enterprise-wide network management system.For example, HP OpenView. Device/System Provisioning/ManagementMotorola Software Update (MSU) or Microsoft 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
Backhaul Network
Backhaul Network
The backhaul network is the wired LAN used to move trafc from a TEAM smartphone and WLAN to the servers. The backhaul network is also used to move trafc from the servers to the TEAM smartphone and WLAN. It encompasses equipment that is not part of the Wireless LAN (WLAN). Customers supply and maintain their own backhaul. TEAM has a vendor-agnostic approach to the backhaul network, which means that customers can reuse existing equipment or order equipment from multiple vendors, if the equipment meets the requirements specied in "WLAN and Backhaul Network Specications". 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 coverage and capacity drive backhaul requirements. If capacity increases in the WLAN, then the backhaul needs to expand to manage the trafc. 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 wireless TEAM smartphones as they roam across the organization. The WLAN has security protocols designed 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 Wireless controller/gateway function as Layer 2 to Layer 3 routers. AP controller/gateways/wireless switch The WLAN access point concentrator that controls AP functions and interfaces to the core wired Enterprise network.
The Enterprise can choose from multiple vendors, but cannot deploy disparate equipment from different vendors. Consistency is important to maintain QoS. Current industry standards do not enforce compatibility between vendor solutions. WLAN infrastructure needs to be engineered to support voice and data on the same medium. This includes standards-based security features required in the WLAN (enterprises require a level of security in their wireless 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 points and between subnets. Call admission control assures the availability of sufcient bandwidth before a voice call enters 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 with minimal 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 overlay over an existing 802.11b/g network; this allows segregation of the TEAM trafc (802.11a) and the legacy trafc (802.11b/g). To be optimally suited for TEAM, the third-party equipment needs to support equipment that meets the standards in Table 1-3.
68009260001-A
January 2009
1-9
Wireless LAN (WLAN)
Table 1-3 lists WLAN components and the standards that they support. Table 1-3 WLAN Components Standards WLAN Components AP300 Access Point Standards Supports 802.11a/b/g. Supported rates: 802.11a6, 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.11hstandards-based dynamic frequency selection and transmit power control 802.11isupport for IEEE standards-based security encryption Radio support: 2.4 GHz/5 GHz frequencies, frequency hopping, direct sequence, OFDM encoding techniques, and 802.11a/b/g WS5100 Wireless Switch 802.11i for security with mobility Encryption: WEB, WPA, WPA Enterprise, WPA2, and WPA2 Enterprise. 802.11Q VLAN Tagging 802.11p VLAN Priority 802.11r (future) WMM WMM Power Save WMM-AC (future) for bandwidth reservation. Layer 3 tunneling
Vendor Motorola/Symbol
1-10
68009260001-A
January 2009
TEAM smartphone
Table 1-3
WLAN Components Standards (Continued) WLAN Components ES3000 Ethernet Switch w/POE Standards 802.3af Power-over-Ethernet Layer 2 switching Cisco 4402 with 2 GB Ethernet ports supports congurations for 12, 25, and 50 access points For 1131AG802.11a/g : Non-modular LWAPP AP: Integrated Antennas Cisco 4404 with 4 GB Ethernet ports supports congurations for 100 lightweight access points For 1242AG: 802.11a/g Non-modular LWAPP AP; RP-TNC
Vendor
Cisco 4400 Wireless Controllers (4402, 4404) with 1131AG and 1242AG APs PROGRAMMED IN Light Weight AP Mode.
TEAM smartphone
The TEAM smartphone includes a subscriber unit hardware platform and an optimized voice client running on Windows Mobile 6.1 OS. It is called as a TEAM smartphone, because it offers capabilities that exceed those offered by a typical mobile phone. The TEAM smartphone supports instant communication, mobile ofce applications, and Enterprise telephony services. The TEAM smartphone helps to increase the productivity of on-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 into one 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
Web browser LOB application integration Abbreviated dialing
NSM Applications
NSM is an Motorola-provided management application to support the needs of the WSM which is used during installation and conguration. Table 1-4 lists the NSM applications provided by Motorola. Table 1-4 NSM Applications Description Provides the local administrator access to common maintenance functions for the NSM. Plots up to ve statistics in a single graph. Statistics are of two types: Historical statistics and Realtime statistics. Used to add, modify, and delete NSM operators. Also, used to manage passwords. Used to congure topology and parameters on the NSM/WSM and to collect NSM/WSM alarms and events. However, no alarms for other networks elements are collected. Uses SNMP notications to send all events/faults/alarms. When Used System administration. System administration.
Software NSM Site Administration NSM Statistics Viewer
NSM Account Management NSM Topology Manager
System administration. System administration
Management Applications
Management applications include a suite of software tools provided by Motorola and third-party vendors for Fault, Conguration, Accounting, Performance, and Security (FCAPS). Conguration and provisioning are 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 congures a set of software. This role typically involves a one-time setup process. Provisioner operator Provisions subscribers. This role typically involves setup process for the majority of subscribers and is followed by maintenance as needed. System Administrator operator Uses a set of software during day-to-day system administration.
1-12
68009260001-A
January 2009
Table 1-5 lists the software tools provided by Motorola and third-party vendors. Table 1-5 Management Applications Description Standalone platform used for securing and managing access to Web services. Motorola-provided Web-based application, which is the maintenance interface to the WSM. Used to perform monitoring and troubleshooting tasks on the WSM An effective mechanism to analyze subscriber usage. The process is: 1. Aggregate/extract CDRs from AAA/WSM. 2. Process CDRs using a third-party tool. Enterprise control servers (DHCP, DNS, and AAA) Enables administrators to create and modify security, access, connection, and user policies for controlling network access. Provides centralized call control for a resilient, distributed network of media gateways and a wide range of analog, digital, and IP-based communication devices. A Web-based application used for performing frequent move/add/change operations within an IP telephony deployment. Enables enterprises to secure and manage WLAN and remote network access, and provision security elements for TEAM smartphones and subscribers. The AAA is used to authenticate TEAM smartphones and subscribers. Installation and conguration. When Used Provisioning.
Software WSM Provisioning Client
WSM LMT interface
Installation and conguration; System Administration.
Call Detail Records from the WSM
System administration.
IP-PBX,
Installation and conguration.
IP-PBX - Voice Server Provisioning Interface,
Provisioning.
Radius (AAA) Account Management Interface,
Provisioning and system administration.
68009260001-A
January 2009
1-13
Features
Table 1-5
Management Applications (Continued) Description Congure WLAN infrastructure to enable Layer 2/3 tunneling. Provides the latest approved software for devices in warranty. Allows Enterprises to completely and remotely control all TEAM smartphones and the software that resides on the TEAM smartphones. When Used Installation and conguration. Provisioning. System Administration.
Software WLAN applications Device manager/Command Line Interface (CLI) Motorola Software Update (MSU) Microsoft SMS
Features

This section provides a description of TEAM features and services.
TEAM Voice Services

This section provides an overview of the two major types of TEAM voice services provided by VoWLAN telephony: Telephony Calls PTTPrivate 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
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 are key wireless services differentiators, providing subscriber productivity enhancements through quick voice setup and response. The PTT service supports the following features within an Enterprise: Private Call This is a Motorola feature that enables subscribers to initiate a one-to-one call within the Enterprise. The private call feature allows a subscriber to 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-many call to a pre-provisioned group within the Enterprise. The group call allows a subscriber to initiate and participate in a half-duplex conversation with more than one subscriber within the talkgroup. Subscribers can be members of multiple groups and have the option to 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 afliated to one talk group at a time. PTT services also ensure: Quick call setupCall setup time between button push and talk permit tone System and spectral efciencyThe solution does not require a dedicated connection for each PTT 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 Services

This section provides an overview of major TEAM Data services, grouped as follows: Windows Mobile 6.1 features Motorola-specic features Third-party features
Key data services include:
68009260001-A
January 2009
1-15
Windows Mobile 6.1 Features
E-mail/PIM/Messaging E-mail (through Windows Mobile interface), calendar, contacts, tasks access through mail application. Access Internet Web sites and synchronize with calendar 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 UICall 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 use voice/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, compatible with MS Outlook phonebook only)
Tasks For synchronization, you can use USB or OTA synchronization if your IT Administrator allows it. Please check with your IT Administrator. E-mail
Motorola-Specic Applications on the TEAM smartphone

In addition to the customized Windows Mobile 6.1 OS, TEAM offers applications that are specic 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 browserHTML/WAP 2.0 compliant, and Opera. Can use HTTP and HTTPS on the network and support certicates.
If MSU is not used, the customer can use MS SMS, a third-party competitor product.
1-16
68009260001-A
January 2009
Device/System Provisioning/Management Client
Device/System Provisioning/Management Client

The Device/System Provisioning/Management client allows a remote administrator to install, remove, and congure applications as well as to set TEAM smartphone registry settings and check TEAM smartphone status information such as power and battery levels. MSUA provisioning tool that provides the latest approved software for devices in warranty.
There should not be any software dependencies in the TEAM smartphone to work with MSU. MS SMSManages 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 example, you can say, Open Browser. Document editingIf an e-mail has Microsoft Word, Excel, or PowerPoint les attached, you can open and edit them using Documents To Go. Documents To Go also supports PDF and zip les. Support for third-party LOB applications (optionally available).
Shared Device/Pool Feature

TEAM supports the Shared Device/Pool feature that allows an Enterprise to congure multiple TEAM 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 group login, and an optional subscriber-specic login: A TEAM smartphone providing services associated with a single, well-dened Enterprise extension can be used by shift workers who possess the TEAM smartphone. A subscriber can secure a shareable TEAM smartphone and trigger loading of the prole to the TEAM smartphone by simply logging into the TEAM smartphone through the user login, and then remove the prole by logging out of it.
68009260001-A
January 2009
1-17
Concepts
A TEAM smartphone can be combined with additional TEAM smartphones to form a strategic group identied by a single Enterprise extension. Any call to this extension simultaneously alerts all TEAM smartphones within the strategic group. The rst TEAM smartphone to answer, receives the call while all other TEAM smartphone alerts cease shortly thereafter. The Enterprise PBX binds a single group extension to the multiple TEAM smartphones. The binding of a single group extension to multiple TEAM smartphones is only available when the system is deployed with PBXs that support Motorola TEAM smartphones as SIP line extensions.
Concepts

This section explains key concepts of the TEAM solution.
Shared Device/Pool
The Shared Device/Pool feature allows the Enterprise to congure devices for pool/department/shift usage or for personal usage. This allows a TEAM smartphone to change services depending upon the user that is logged into the TEAM smartphone. This can also provide a cost savings by 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 and password 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 users device and use it. In this case, 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 specic department of the Enterprise. The department manager would be given a personal, non-shared device provisioned 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. The department manager has a device that is not shared as the mangers set of services may be different than that of the shared devices. Examples of services that can be differentiated based upon username and password credentials are PTT private and group call, SMS, email, voice mail, PBX calling features, PBX class of service 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 specic department. The manager can also use any one of these shared devices if it is more convenient than using their personal device. In this case, the manager simply logs into the device through the User Login application using their unique username and password which then grants services to the device based upon the managers 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
A specic 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 device using the department username and password to return the device to shared device operation. A power down/power up sequence of the device also returns the device to shared device operation.
A specic example of PBX services associated with the shared devices:

A TEAM smartphone can be combined with additional TEAM smartphones to form a strategic group identied by a single enterprise extension. Any call to this extension simultaneously rings all TEAM smartphones within the strategic group. The rst TEAM smartphone to answer receives the call while all other TEAM smartphone cease ringing shortly thereafter. The enterprise PBX binds a single group extension to the multiple TEAM smartphones. The binding of a single group extension to multiple TEAM smartphones is only available when the system is deployed with PBXs that support Motorola TEAM smartphones as SIP line extensions. A manager logging into a shared device with their unique username and password causes the device to take on the services granted to the manager and remove the services granted to the department. In this case, the device does not ring if the department extension is called but does ring if the managers extension is called.
Information such as SMS, email, call history, browser history and contacts is retained for each user of the device. The system administrator should inform each user of this fact and to delete any data that a user may not want to be retained and provided to the next user of the device.
Micro Mobility
Micro mobility is a function that allows the TEAM smartphone to roam from AP to AP within a WLAN coverage area without impacting voice quality or applications. The APs may be on the same or different subnets. The TEAM smartphone roams from one subnet to another subnet within the same network with no call in progress or with a call in progress. The voice calls proceed 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 remain reachable at its current assigned IP address, regardless of the location of its serving AP. TEAM leverages specic WLAN mechanisms for fast hand-off. It is implemented exclusively between the TEAM smartphone and WLAN. Micro mobility functionality resides mainly inside 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 motion makes a voice call or, changes subnets in the WLAN. Micromobility has three groupings: Voice callsVoice calls include interconnect, private call, and group call. Private call and group call could also be grouped as PTT calls. Data sessionsData session means that the TEAM smartphone is running an application that can exchange data with servers. Idle trafcIdle condition means that no applications are running on the TEAM smartphone that will be using the IP address on the TEAM smartphone to transfer data .
68009260001-A
January 2009
1-19
Telephone Numbering Scheme
Example 1: Roaming within voice call The TEAM application lets you maintain active voice calls while roaming within the Enterprise WLAN, including while changing subnets. When a subscriber makes a telephony call, hand-offs occur to 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 maintain the same IP address for the device. If the system fails to maintain the same IP address, then the call drops when the device roams to a new AP. So, within a PTT/Interconnect call, if the device roams, it makes a restricted DHCP call - a DHCP request to retain the IP the address it currently holds. The solution relies on industry standards (802.11 and WiFi Alliance standards) and leverages WLAN infrastructure capabilities (for example, AP to AP tunneling and packet routing) to handle the continuation of a call (until the TEAM smartphone re-registers on 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, the TEAM smartphone makes an unrestricted Dynamic Host Conguration Protocol (DHCP) request, which means that the DHCP might assign the TEAM smartphone a new IP address (and ending any Layer 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 L2 address). These applications are required to use the Windows facility to receive notication of IP address changes when they occur. This is analogous to moving our laptops from our wired desk to meeting rooms where 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 reading e-mail or browsing web pages), the applications should be aware of address changes and handle them as described in the roaming in data session scenario.
Telephone Numbering Scheme

This 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 basic functions of the WSM (it brokers a single connection to/from the PBX and allows multiple TEAM smartphone connections through that one logical connection to the PBX).
Introduction
The Enterprise telephone numbering scheme establishes how the subscriber will interact with the TEAM smartphone to invoke services such as call origination, call forwarding, PPT, and text messaging. Each TEAM smartphone will be assigned with a typical 10-digit phone number. The TEAM solution supports
1-20
68009260001-A
January 2009
Telephone Numbering Scheme Example
abbreviated dialing, so that fewer digits are needed to invoke the services mentioned above. The TEAM smartphone also supports the concept of contact number. This allows a single entry in the contact list to 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 number is 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, where N can be dened 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 vendors equipment that complies with industry standards. Typically, industry standards are carefully developed and robust. They are adopted only after thorough study and discussion, and examination by industry experts. Benets of standards-based design include: New technologies utilizing open standards can usually be relied upon for more consistent, predictable integration and deployment, easier maintenance and upgrading, and clearer migration paths. Standards-based systems also help ensure compatibility and interoperability with other products based on the same standard, even when those products come from a variety of manufacturers. This leads to more exible solution alternatives. Implementing standards-based technologies prevents products/solutions from becoming obsolete quickly.
The following sections cover supported standards in more detail.
IEEE
The Institute of Electrical and Electronic Engineers (IEEE) is one of the leading organizations in the world for setting standards in technology. Notable IEEE standards includes the IEEE 802.3 Ethernet standard and the IEEE 802.11 wireless networking standard.
68009260001-A
January 2009
1-21
802.11 a/b/g Bands and Speeds
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 standard for WLAN. The TEAM smartphone operates on APs that are certied for operation on 802.11 a/b/g. Table 1-6 Standard 802.11a 802.11 a/b/g Bands and Speeds Bands 5 GHz Throughput Up to 54 Mbit/s Comments Channels are 20 MHz non-overlapping. Some adjacent channel interference is possible. Channels in 2.4 GHz band overlap. Expect interference from other products operating in the same band. Channels in 2.4 GHz band overlap. Expect interference from other products operating in the same band. 802.11 g is an extension to 802.11b and has backward compatibility with 802.11b.
802.11b
2.4 GHz
Up to 11 Mbit/s
802.11g
2.4 GHz
Up to 54 Mbit/s
For TEAM, the preferred solution is 802.11a or 802.11a with 802.11g (good for larger areas). An 802.11a/g frequency arrangement is used to allow some micromobility between bands (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 includes industry leaders who drive the adoption of globally accepted standards for high-speed WLAN. WFA is a manufacturers standard. The WFA develops rigorous tests and conducts Wi-Fi certication of wireless devices that implement the universal IEEE 802.11 specications. 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.11 standard to be ratied. It includes the majority of the IEEE 802.11i standards. WPA2 is a select subset of 802.11i. It is a list of certication tests for the device.
The TEAM solution uses the full IEEE 802.11i Wi-Fi Protected Access 2 (WPA2) specication. The WFA publishes a number of standards, including: Wi-Fi Multimedia (WMM) WMM Power Save (WMM-PS)
1-22
68009260001-A
January 2009
Wi-Fi Multimedia (WMM)
For more information, see: www.wialliance.com.
Wi-Fi Multimedia (WMM)

Wi-Fi Multimedia (WMM) is a Wi-Fi Alliance interoperability certication, based on the IEEE 802.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 to prioritize the messaging. WMM prioritizes trafc 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.11e to save power (for battery powered equipment) and ne-tune power consumption. WMM-PS is also referred 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 a voice 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 Infrastructure Power 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 simultaneous calls on a single AP. Admission control ensures that adequate bandwidth is available for a voice call and contributes to overall voice quality; this is implemented through bandwidth reservation. The bandwidth reservation record format has been described within the WMM specication. The implementation of bandwidth reservation has been previously limited to select vendor proprietary versions (such as Cisco APs). Cisco CCX has a version of admission control utilized by the TEAM solution. 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 proposed WMM-AC (Admission Control) standards. Works well with Cisco CCX which provides packet prioritization, power save, and admission control.
68009260001-A
January 2009
1-23
Session Initiation Protocol (SIP)
May be able to use RANs without the above standards, with the possible reduction of voice quality, talk/idle time, and reliability.
Session Initiation Protocol (SIP)

The Internet Engineering Task Force (IETF) introduced Session Initiation Protocol (SIP) to simplify the process of running VoIP connections across the Internet. Networks running SIP can handle VoIP calls 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 the TEAM 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 with PBXs (which typically do not have all features implemented in SIP). The WSM is the SIP proxy and registrar.
ITU-T
International Telecommunications Union-Telephony (ITU-T) has established specications for 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 is a codec that is used to compress or decompress audio data. For TEAM, a high quality vocoding scheme is used 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 Comments G.711 provides the best voice quality since it uses no compression. It also has the lowest latency (lag) because not using compression reduces processing power. It requires more bandwidth than other codecs. Maximizes call capacity on a given link. It has lower bit rate and is bandwidth efcient. The IP-PBX implements G.729 and decodes the G.729A bearer coming from the TEAM smartphone. Bandwidth efcient and provides improved audio quality.
Vocoder G.711 (64K), both G.711 a-law and -law algorithms
G.729 for infrastructure
G.729a (8K) for TEAM smartphone implementation
1-24
68009260001-A
January 2009
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 in order to improve voice quality on a telephone call. Echo cancellation algorithms improve audio quality. The digital part of a communications network does not cause any echo. Hence, only two 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. (Echo cancellation 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
1-26
68009260001-A
January 2009
Chapter
Theory 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
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 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 Equipment
This section provides a description of the hardware and software components of the TEAM components, the WSM, and the NSM. The TEAM solution supports one WSM/NSM pair communicating 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 setupcall setup time between button push and talk permit tone is typically less than one second. Solution security, with mechanisms that validate network elements, TEAM smartphones, and subscribers. System and spectral efciencysolution does not require a dedicated connection for each PTT call. PBX interoperability. Performance optimization. Reliability. Excellent PTT subscriber experience through tightly managed QoS and oor 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
SIP Registrar Stores mobile registrations and participates in the authentication and authorization of each TEAM smartphone. Subscriber Access Conguration Provides a database that stores the complete set of a subscribers provisioning data. Interface to Enterprise PBX Supports an interface to multiple manufacturers of PBX equipment 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 the network thereby enhancing performance and security. Accounting Provides Call Detail Records (CDRs) for both telephony and PTT calls. The CDRs are made available to other CDR processing server applications that can compute chargers and/or usage information.
System Responsibilities
The WSM provides PTT functionality within an Enterprise. The WSM also stores important subscriber information in the Enterprise environment: handling registration, voice services authentication within the WLAN, and message notication functions. PBX Interoperability The WSM interoperates with a variety of IP and TDM PBXs using standard interfaces. It provides interconnect call control between the TEAM smartphone and the PBX. Protocol connectors in the WSM allow a single TEAM smartphone codeline for all PBXs that are independent of PBX vendor implementation. 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 optimizes protocol for registration, synchronization, mobility-related procedures, and so on. Using Wireless MultiMedia Power Save (WMM-PS) provides advanced power-saving mechanisms for extended battery life. Network Access Control Network security prole is managed between the TEAM smartphone and the WSM. 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 individually managed by a PBX vendor or any other third party. So, extra licenses and expensive upgrades of third-party equipment 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 efciency. It has the intelligence to decide the best route for bearer trafc between endpoints while maintaining control of the session. Reliability WSM has four nines (0.9999) availability, with architecture that can be extended in the future to include redundant conguration or t into a clustered PBX architecture.
The Enterprise-supplied power to the WSM needs to be appropriately sized, and provide six nines (0.999999) availability. This is the responsibility of the system integrator and is 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
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 routingThe WSM checks the call targets unconditional Call Forwarding status for 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 datastore while paying attention to the contacts related to the targets SIP ID.
WSM
This section provides information about WSM appliance.
Conguration
The Motorola WSM appliance is available in one congurations: 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 Specications
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 is accessed with a common Web browser such as Internet Explorer or Netscape. The LMT covers operations specic 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 interfaceA text-based browser that uses a Web server. Operator accounts are the same as the LMT, and the functionality is identical.
2-6
68009260001-A
January 2009
NSM Server Application
Emergency Local Maintenance Terminal (ELMT) A text-based emergency maintenance interface to the WSM. The ELMT can be accessed locally using a serial console connection or xterm. It does not depend on a Web 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 NSM provides Java-based tools (server side) and web-based tools (client side) for conguring and monitoring the WSM 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 2003 Server 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/cleared state, and user-acknowledged state Sends e-mail notication to operators: up to 5 e-mail addresses can be congured, and the NSM sends the e-mail notications to the congured e-mail addresses Forwards SNMP to other network management systems Shows the state of a network element graphically in the Topology Manager Congures the WSM Provides full conguration, validation, and online help support Provides conguration reports on changes
Conguration Management:
68009260001-A
January 2009
2-7
NSM Server Hardware Requirements
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 activity for review. By default, NSM stores up to seven days of statistical data. This can be congured 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 as Excel or a database): NSM parses the statistic les into unl les automatically. These unl (database unload) les can be used for additional analysis of the data Provides user name/password protection for Motorola NSM access. Provides an interface to congure, enable, and disable Network Management Communication Security settings Access classes (guest, operator, and administrator) Provides conguration logs to map operators to network conguration changes Acts as the control point for management (add/delete/list/import/export) of security certicates on WSM
Security Management:
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 loaded with specic hardware and software requirements. Software requirements: Microsoft Windows 2003 Server with Service Pack 1 or Microsoft Windows XP with Service Pack 2 with rewall off. Microsoft Internet Explorer, version 6.0. Apache Web Server, version 2.0.54 (included in NSM installer).
2-8
68009260001-A
January 2009
NSM Software
NSM Software
The NSM software provides a number of services for conguring, monitoring, and managing 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. Remote access is available. However, enabling remote access using industry-standard applications 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: Conguration: Download conguration data to the WSM Validate conguration version before download Revert to previous conguration version Compare congurations Activate license and update software Process WSM events and alarms Display and lter incoming event and alarm information Clear alarms so they are no longer visible (does not update WSM state) Display current WSM site status Retrieve and process historical statistics les from WSM Display real-time and historical WSM statistics information Log incoming statistics
Fault Monitoring:
Performance Monitoring:
Figure 2-4 shows the NSM screen.
68009260001-A
January 2009
2-9
Figure 2-4
NSM Screen

The Enterprise control servers are: Dynamic Host Conguration Protocol (DHCP) Domain Name Server (DNS) Authentication, Authorization, and Accounting (AAA) Network Time Protocol (NTP) Server Motorola Integration Server
DHCP
Dynamic Host Conguration Protocol (DHCP) is a protocol that is used for assigning both dynamic and static IP addresses to devices on a network. With dynamic addressing, a TEAM smartphone can have a different IP address every time it connects to the network. Dynamic addressing simplies network administration because the software keeps track of IP addresses. DHCP allows the administrator to dene a range of addresses that are available for distribution (address pooling). DHCP servers are Enterprise-supplied servers, which support: DHCP vendor-specic options in a DHCP client request. The server must be congured to identify unique vendor-specic option text tags and associate a unique DHCP conguration with this tag. The vendor-specic option must support extended American Standard Code for Information Interchange (ASCII) for text input. Conguration of the TEAM WLAN smartphone DHCP data set that includes the Subscriber Access Conguration Server (SACS) url. Deployment of multiple DHCP servers, possibly congured in an 80/20 rule with a divided scope, or a clustered DHCP server set.
DNS
Domain Name Server (DNS) is an Internet service that translates domain names into IP addresses. Domain names are alphabetic, so they are easy to remember. DNS has its own network. If a DNS does not know how to translate a particular domain name, then it contacts another DNS to get the correct IP address.
2-10
68009260001-A
January 2009
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 specied on DNS server and should include WSM and NSM hosts.
EAP-TLS
User environments have existing security measures in place which include the requirement to authenticate a user with a username and password before access to any corporate assets or data is granted. Any additional credentials needed are either compatible with the enterprise authentication servers or, if stored in the components are accessible by trusted components within the enterprise. As such, the TEAM Smartphones support EAP-TLS RADIUS based authentication. Enterprises are assumed to have AAA servers to support User 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 is used 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 and password. Authentication is based on the idea that each individual user has unique information that sets that individual apart from other users. The AAA server uses the Remote Authentication Dial In User Service (RADIUS) protocol to authenticate TEAM smartphones and subscribers. TEAM uses two methods for authentication: X.509v3 digital certicate 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 once the user has been authenticated through the username and password. The amount of information and the number of services that the user can access depends on the users authorization level. Accounting The process of tracking a users activity while accessing network resources, including the amount of time spent in the network, the services accessed while 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 support to 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)
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-sipping-radius-accounting-00.txt (http://www.freeradius.org/rfc/draft-schulzrinne-sipping-radius-accounting-00.txt)
Minimal conguration requirements include: Security implemented on the TEAM smartphone that matches the security set up within the WLAN. For example, if the TEAM smartphone is set up with WPA2 Enterprise, so should the WLAN. 802.1 x authentications of TEAM smartphone and network elements. The TEAM smartphone is provided certicate-based authentication that must be implemented within the network deployment, that is the TEAM smartphones Root CA certicate 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 Cisco ACS Hardware Processor: Pentium III-compatible with 550 MHz or faster 256 MB RAM Juniper Steel-Belted RADIUS Processor: 2.8 GHz Pentium Memory: 512 MB RAM Disk space: 80 GB Connectivity: On-board dual 100/1000 NIC Windows XP/2000/NT runs on Windows NT 4.0 with Service Pack 6 Windows 2000 (all editions) Windows XP (all editions) Windows Server 2003 (all editions) The RADIUS Shared Secret is a password (a string value), on the WSM and AAA servers that is used to authenticate subscribers. The value must be the same on both. If you want to change the password on AAA Server and WSM Shared Secret, you can change these values on the WSM by updating the RADIUS Shared Secret. This change can be done while the WSM is in operation. For more information, refer to TEAM System Installation and Conguration Guide. Software OS: Windows 2003 Server ACS3.3
If an Enterprise tries to re-use an existing AAA certicate repository, there can be a likely need for two separate AAA servers.
2-12
68009260001-A
January 2009
Public Key Infrastructure
Public Key Infrastructure

The TEAM mobile devices will come pre-provisioned with X.509 digital certicates for device and user authentication purposes. The TEAM equipment will be provisioned with necessary certicates during license activation process. The enterprise customers IP-PBX or PBX-GW is required to install the TEAM equipment s Root CA certicate in its trusted store if TLS is the secured WSM-PBX connection type to be congured. The enterprise customers AAA is required to install the TEAM mobile devices Root CA certicate in its trusted store, and install the TEAM AAA server certicate (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 provides the accurate time to the NSM/WSM. It connects to an Internet-based NTP time server (such as pool.ntp.org) or directly to a GPS antennae that provides a GPS time synchronization signal. The server 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 establish connections 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 Certicate Download Online patch download
Certicates are distributed as part of the WSM activation process. Online through the Internet, which requires a back-end process with the Motorola Integration Server Ofine through CD-ROM
PBX (Telephony Servers)

PBXs provide a rich level of telephony features. Every Enterprise has one PBX for the Public Switched Telephone Network (PSTN) interface. A PBX provides services to Enterprise associates for the TEAM smartphones, and regular Enterprise telephones. Services include basic call, and supplementary services 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 TEAM smartphone 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 efcient manner. It can Direct voice packets through its media server for the duration of the call. Instruct TEAM smartphones to talk directly between themselves. This process is called media shufing.
68009260001-A
January 2009
2-13
Hardware and Software Specications
The PBX is supplied by the Enterprise. The means of SIP signaling to support a telephony feature set could vary with PBX vendor. The TEAM solution integrates with widely deployed existing PBX solutions from major vendors. The WSM is congured with transport type, security, and SIP translations required to work with the PBX of choice. In general, the PBX is involved for telephone calls, while the WSM handles call control for wireless calls and PTT services.
The TEAM solution currently supports one pair of WSM/NSM communicating with one 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

Table 2-2 lists the Dialogic PBX equipment hardware specications. Table 2-2 Dialogic Gateway to TDM PBXs Hardware Specications Model DMG2030DTIQ Specications Network Interfaces: 10/100 BaseT Ethernet LAN port Connector 1 shielded female RJ-45 jack for LAN Power Requirements : 90 VAC to 264 VAC Environmental Requirements: Operating temperature: 32 F to +122 F
2-14
68009260001-A
January 2009
Table 2-3 lists the Dialogic PBX equipment software specications. Table 2-3 Dialogic Gateway to TDM PBXs Software Specications Software GA version of 6.0
Model DMG2030DTIQ
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) Hardware Release S8300, S8500, S87XX Software Version 4.0, 5.0
Manufacturer/ Model Avaya Communications Manager NEC NEAX 2400 IPX Nortel Meridian Option 11C
IVS series
Version 17, Release 03.46.001
Option 11C
Version 17, Release 25, Issue 40, Version 2111
Common telephony features offered by each TEAM supported Dialogic Gateway to TDM PBX are shown in Table 2-5 . Table 2-5 Call Features Supported by TDM PBXs Avaya Communications Manager Basic Call Control Inbound Calls, Outbound Calls, Caller ID Call Transfer Blind Call Transfer Consultive Call Forward (CFNA, CFB, CFNR, and CFU) Multi-party Call Appearance E911 DTMF Tones Call Restriction Ad Hoc Conference Call Yes Nortel Meridian Option 11C Yes NEC NEAX 2400 IPX Yes
Yes Yes Yes
Yes Yes Yes
Yes Patch Required Yes
Yes Yes Yes Yes Yes
Yes Yes Yes Yes Yes
Yes Yes Yes Yes Yes
68009260001-A
January 2009
2-15
Table 2-6 shows IP PBXs supported directly by the TEAM Solution. Table 2-6 IP PBXs Supported Directly by the TEAM Solution Hardware Release S8300 / S8500 / S87XX Software Version 4.0, 5.0 SIP Trunk Supported SIP Station Supported (via OPS)
Manufacturer/ Model Avaya Communications Manager
Cisco Unied Call Manager (CUCM
MCS78XX
5.1 and later
Supported
NA
Cisco Media Express (CME)
Routers 2801, 3825
IOS 12.4(11)
Supported
NA
Nortel Communications Server 1000
CS1000E series
Succession 5.0, 5.5
Supported
NA
Common telephony features offered by IP PBXs supported directly by the TEAM solution are shown in Table 2-7 Table 2-7 Call Features Supported by TDM PBXs Avaya Nortel Communications Communications Manager Server 1000 Basic Call Control Inbound Calls, Outbound Calls, Caller ID Call Transfer Blind Call Transfer Consultive Call Forward (CFNA, CFB, CFNR, and CFU) Multi-party Call Appearance E911 DTMF Tones Call Restriction Ad Hoc Conference Call Yes Yes Cisco CUCM Yes Cisco CME Yes
Yes Yes Yes
Yes Yes Yes
TBD TBD Yes
TBD TBD Yes
Yes Yes Yes Yes Yes
Yes Yes Yes Yes Yes
Yes Yes Yes Yes TBD
Yes Yes Yes Yes TBD
2-16
68009260001-A
January 2009
IP-PBX
IP-PBX
An IP-PBX is a third-party provided SIP-based network element that provides general telephony services to the Enterprise solution. IP-PBXs packetize voice for transport through the IP network and connect the Enterprise IP telephony system to the PSTN. This PBX operates both on a circuit-switched platform to the PSTN, and on VoIP through IP ports. Current IP-PBX functionality combines a traditional telephone switch 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 additional software. 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 (the Avaya Communication Manager with Avaya Off-PBX-Station (OPS)). Avaya Media Servers A line of media servers that supports distributed IP networking and centralized call processing across multiprotocol networks. Avaya media servers have the following features and benets: 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 though the IP network and connecting the Enterprise IP Telephony system to the Public Switched Telephone Network (PSTN). Avaya media gateways support both bearer and signaling trafc that are routed between packet- and circuit-switched networks. Avaya media gateways have the following features and benets: Interoperable with standards-based data networks Stackable, modular, and congurable component solutions Redundant capabilities Distributed networking
Avaya IP-PBX Specications

The Avaya IP-PBX specications 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 TEAM solution. TDM Gateways allow the WSM to talk to a non-IP-PBX system. TEAM supports select TDM-based PBXs using a SIP Gateway product (Dialogic Gateway).
68009260001-A
January 2009
2-17
Dialogic Solutions
Dialogic Solutions
A Media Gateway is a telephony gateway appliance that connects to one or more TDM PBXs through its telephony 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 managed packet network. The Media Gateway converts signals from circuit-switched equipment into either H.323 or SIP standard protocol for transmission over a LAN to communications devices such as IP phones, wireless phones, and IP servers in almost any location. The Dialogic 2000 Media Gateway Series (DMG2000) merges traditional PSTN technology with IP 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 PBX
The TEAM Solution supports two Cisco PBXs: The router based Cisco Media Express (CME) provides basic PBX functionality The Cisco Unied Call Manager (CUCM) provide robust and exible PBX functionality
For more information regarding the Cisco CUCM 5.1 or Cisco CME PBX, refer to the Cisco customer documentation website at: http://www.cisco.com/univercd/home/home.htm
Nortel PBX
For more information regarding the Nortel CS1000 (version 4.5 and later releases), refer to the Nortel customer documentation website at: http://support.nortel.com/go/main.jsp?cscat=OVERVIEW&poid=14261
Telephony-Related Servers
This 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 Server provides voice mail indication and Message Waiting Indication (MWI).
2-18
68009260001-A
January 2009
CDR Processing Server
The PBX has the sole connection to the Voice Mail Server. It forwards any unanswered calls to the Voice Mail Server, where a caller can leave a message. The Voice Mail Server sends an MWI to the recipient phone, through the PBX and WSM, to display an icon indicating that a message has been left for the recipient. When the recipient calls into the Voice Mail Server and listens to the message, the server sends a new MWI to clear the display on the recipients TEAM smartphone.
CDR Processing Server

Call Detail Records (CDRs) are an effective mechanism to analyze subscriber usage in the TEAM solution. CDRs are generated by the IP-PBX for telephony calls traversing it and are stored on the IP-PBX. They are also generated by the WSM for telephony calls that stay within the mobile environment controlled by the WSM and for WSM controlled PTT calls. The WSM created records 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 CDR modules in the PBX. However, when the TEAM smartphones are not congured as extensions in the PBX (that is, when mobile-to-mobile calls are not routed through and not monitored by the PBX), the TEAM WSM can be enabled to generate telephony call accounting information (Call Detail 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 the AAA/RADIUS server to the Accounting Server for correlation and further processing. Once the CDR Data has 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 accounting sources (such as, the data from the PBX). It also converts the CDR data sets into the CDR data format specied by the Enterprise customer. The correlation and formatting procedures are dependent on the specic AAA/RADIUS servers and Billing Servers used by the Enterprise. Examples of typical methods 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 be interoperable 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. It centralizes the maintenance of data to a single location. It allows mapping of multiple pieces of data within the Enterprise database to a single attribute in the directory and denes a way of setting the 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, to generate a bill. Subscribers are entered into the Directory Server to support address books, and so on.

Other 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
Network Management
Motorola provides the NSM application for network management activities. If an integrated system view of other system components is required, that is, of an Enterprise management system, you could use a product like HP 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 forwarding SNMP events to the customers 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 remote administrator to install, remove, and congure applications as well as to set TEAM smartphone registry settings and check TEAM smartphone status information such as power and battery levels. It runs as a timed background process. The process starts after a congurable interval to connect with the Device Management server to post information and check for new instructions. The Device Management client uses HTTP/HTTPS to connect to the server. The Device Management client may also monitor the network connection for activity using standard WinCE API calls and throttle itself appropriately to 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 Motorolas Support Central Web site.
MS Text Messaging and New Initiative

MS SMS is a systems management software product, from Microsoft, for managing large groups of Windows-based computer systems. SMS provides functionalities such as remote control, patch management, software distribution, and hardware and software inventory.
Email
The e-mail server is supplied by the Enterprise. The server include support for Post Ofce Protocol (POP3) for the TEAM smartphone.
Microsoft Exchange
Microsoft Exchange Server is a possible vendor-specic e-mail server for use in the TEAM solution. Microsoft Exchange is an e-mail server that hosts the subscribers Enterprise e-mail account. The Enterprise Exchange Server is accessed by TEAM smartphones when using Wireless Data Applications.
2-20
68009260001-A
January 2009
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 Instant Messaging (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 trafc from a TEAM smartphone 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 the backhaul network, which means that customers can reuse existing equipment or order equipment from multiple vendors, if the equipment meets the requirements specied in "WLAN and Backhaul Network Specications". In the TEAM solution, the WLAN drives the backhaul requirements. If capacity increases in the WLAN, then the backhaul needs to expand to manage the trafc. 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 centralized TEAM deployment model, where the TEAM solution in located in a hub and spokes radiate from the hub to where various sites are located from which WLAN trafc needs to be supported, then the signaling and voice trafc need to be backhauled to/from the WSM/TEAM smartphones. Routers and switches comply with standards for QoS settings. For more information, see "Routers" and "Switches". For the voice trafc, the network mechanisms used to isolate and prioritize trafc within a given site (for example, VLANs) will probably be different from what is done with wide-area trafc, where Layer 3 routing is often done (and VLANs are not typically used). Also, the wide-area network may not use 802.1 Q/p, but instead it may use other means to do gross or simple trafc prioritization.
68009260001-A
January 2009
2-21
Routers
In certain situations, QoS may not be available over the backhaul portion of the network. In such a situation, if the user wants the WSM and the TEAM smartphones to talk cross sites, the signaling (setup) and bearer (audio) trafc may encounter signicant QoS issues for both cross-site PTT and cross-site interconnect. This needs to be recognized and dealt with before a system deployment.
Routers
Router selection and planning requires knowledgeable Network administrators and assurance that quality routers are selected. If any point of the communication path does not support QoS, then the effect is to not have QoS on that path. The effect on the voice trafc is to deprioritize the packets which then have additional jitter and delay. Deprioritization of the packets causes the audio to degrade and may manifest as drop outs and additional noise in the background.
Switches
Network switches are supplied by the Enterprise. The switches/infrastructure must be capable 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 to map 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 handles micromobility. 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 equipment from different vendors. Consistency is important to maintain QoS. Current industry standards do not enforce compatibility between vendor solutions.
2-22
68009260001-A
January 2009
WLAN Equipment (Multiple Vendors)
The WLAN infrastructure is responsible for maintaining reachability to the TEAM smartphone at its currently assigned IP address. WLAN equipment includes: APsLayer 1 to Layer 3 interface that allows the TEAM smartphone wireless access the Enterprise network. AP controller/gatewaysWLAN access point concentrator that controls AP functions and 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. This equipment meets expectations with respect to battery life, call quality, and coverage. Table 2-8 Supported WLAN Vendors Vendor Motorola/Symbol Model/ Model series WS5100 + AP300 RFS7000 + AP300 RFS6000 + AP300 Cisco CCX compliant controllers and Access points Cisco Wireless LAN Controller Series 4400 +LWAP 1030e including 1230/1240 series reashed 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 capacity is adequate, and options like QoS support within the Enterprise Network are supported by the core routers, then you will have good call quality.
Some conguration steps are out of scope of this documentation and are left to the customer/3rd party contractor to set up. Minimal conguration requirements include: Security implemented on the TEAM smartphone that matches the security set up within the WLAN. For example, if the TEAM smartphone is set up with WPA2 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 (assuming the deployment includes multiple L2 networks within the coverage area). 802.1x authentication of TEAM smartphone and network elements. The TEAM smartphone is provided with certicate-based authentication that must be implemented within the network deployment, that is, the TEAM smartphone certicates must be installed on the AAA server.
68009260001-A
January 2009
2-23
Industry Standard Requirements and Features
Industry Standard Requirements and Features

The TEAM WLAN equipment must meet industry standard and provide required features. The following sections explain these requirements and features: "Minimum AP Requirements for Data Networks" "Recommended Capabilities" "Wireless Features" "Layer 2 Features" "Power over Ethernet (PoE)" "Policy Conguration"
Minimum AP Requirements for Data Networks

In addition to the support provided for a voice-enabled WLAN infrastructure, APs must meet the minimum requirements listed in the Table 2-9 to support the data network. Table 2-9 Minimum AP Requirements for Data Networks Description Need 100 Base-T to meet TEAM throughput calculations. The wireless switch may require Gigabit Ethernet. Required for QoS, indicate how packets are marked for priority. Data network must have End-to-End QoS Support, Diffserv preferred. IP Precedence may be usable as an alternative. Systems supporting WMM ( WMM-PS ) will be able to reach maximum quoted battery life. It is expected for the WLAN to provide tunneling between L2 (Layer 2) networks during a call and without requiring a DHCP release/renew. Allows authentication to a RADIUS server to enable an 802.1x-protected Ethernet port. WMM-PS, U-APSD preferred. Gateways provide port mirroring for additional network monitoring functionality. You can lter trafc and mirror either incoming trafc to the source port or both incoming and outgoing trafc. This allows you to select the network trafc that you need to monitor. Port mirroring is useful for debugging. WMM allows the subscriber unit and the access point to categorize messaging between the endpoints and to prioritize the messaging. It limits the number of simultaneous calls on a single AP. Admission control ensures that adequate bandwidth is available for a voice call and contributes to overall voice quality; this is known as bandwidth reservation. Cisco CCX has a version of admission control utilized by the TEAM solution.
Data Network Features Ethernet, Fast Ethernet, Gigabit Ethernet Multiple Virtual Local Area Networks (VLANs) per port
RADIUS protocol for security Stations Power Saving Port Mirroring
WMM
WMM-AC (Future) for admission control/bandwidth reservation
2-24
68009260001-A
January 2009
Recommended Capabilities
Recommended Capabilities
This section provides recommendations to ensure optimal performance of the TEAM solution using a given vendors 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 Identiers (SSIDs) User Group Table Access Point Group Authentication and Encryption Modes Wireless Domain Parameters MAC Access Control List Rogue Access Point Detection RADIUS Conguration of APs
Layer 2 Features
The Layer 2 features that must be supported in the TEAM WLAN equipment are: Ethernet VLAN Conguration IEEE 802.1X MAC Aging Link Aggregation Group (LAG) Port Redundancy Multilayer Policy Port Classication
Power over Ethernet (PoE)

The PoE features that must be supported in the TEAM WLAN equipment are:
68009260001-A
January 2009
2-25
Policy Conguration
Load Detection Plug and Play Operation Powering Devices Power over Ethernet in Converged Networks
Policy Conguration
The policy congurations that must be supported in the TEAM WLAN equipment are: QoS policy conguration including Access Control Lists and Quality of Service Lists Dening Policy Lists Attaching Policy Lists to an interface Device-Wide Policy Lists Dening Rules Composite Operations DSCP Table Displaying and Testing Policy Lists
Motorola Enterprise WLAN

The 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 specications 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
Motorola/Symbol PoE Ethernet Switch
Table 2-10
Standards: WPA2, WMM. Motorola/Symbol Access Point Specications Model Part Number WSAP-5110-100-WWR WSAP-5100-100-WWR
AP-300 with integrated antenna AP-300 with external antenna
See http://www.symbol.com/ for detailed specications.
Motorola/Symbol PoE Ethernet Switch

Table 2-11 lists the Motorola/Symbol ES3000 PoE Ethernet Switch used in the TEAM solution with specications. Table 2-11 Model ES-3000 Motorola/Symbol PoE Ethernet Switch Specications Description ES-3000 24 port L2 switch with PoE injector ES-3000 with a US style power cord Part Number ES-3000-PWR-10-WW ES-3000-PWRUSCORD Capacity 24 ports
Motorola/Symbol RF Switches
Table 2-12 lists the Motorola/Symbol wireless RF switches used in the TEAM solution with specications. Table 2-12 Model MOTO WS51000 Wireless Controller Motorola/Symbol RF Switches (Validated) Description Redundant WS5100 Wireless Switch 6Port WS5100 Wireless Switch with six Access Port Licences 6Port License Upgrade AP licenses are available from 6 to 48 APs in multiples of 6 Part Numbers WS5100-RS-WWR WS-5100-06-WWR Software Release 3.X WiOS Capacity 48
WS-5100-UCWWR.
68009260001-A
January 2009
2-27
Cisco
Table 2-12 Model
Motorola/Symbol RF Switches (Validated) (Continued) Description 802.11 a/b/g connected remotely, managed through a through a Motorola wireless switch Part Numbers Software Capacity
MOTO AP-300 Access Port
Table 2-13 Model RFS7000
Motorola/Symbol RF Switches (not Validated) Description 7000 is better when encryption is turned on. Premier solution, high capacity. Support for up to four APs with PoE (for small systems/test deployments) WS2000 and 1 AP300 (802.11a/b/g) bundle WS2000 and 2 AP300 (802.11a/b/g) bundle WS2000 and 2 AP300 (802.11b/g) bundle Part Numbers TBD Software Release 3.X WiOS Capacity 256
WS-2000-SME-WWR
WS-2000-1C-ABG-WWR WS-2000-2C-ABG-WWR WS-2000-2C-BG-WW
Cisco
Cisco (http://www.cisco.com/) is one of the possible WLAN vendors for TEAM. Cisco is responsible for supplying the part numbers, equipment, software releases, and any additional 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
Cisco RF Switches
Cisco RF Switches
Table 2-14 lists the Cisco wireless RF switches used in the TEAM solution with specications. Table 2-14 Model 4400 series4402 Cisco RF Switches Description Cisco 4400 Series Wireless LAN Controllers. 2 GB Ethernet ports supports congurations for 12, 25, and 50 access points Cisco 4400 Series Wireless LAN Controllers 4 Gigabit Ethernet ports supports 100 access points Part Numbers AIR-WLC4402-12-K9 for 12 Access point AIR-WLC4402-25-K9 for 25 Access point AIR-WLC4402-50-K9 50 Access point AIR-WLC4404100-K9 Software Release 4.2 or above Capacity up to 50
4400 series4404
Release 4.2 or above
100
See http://www.cisco.com/ for detailed specications.
Cisco Access Points

Table 2-15 provides the specications for the Cisco APs used in the TEAM solution. Table 2-15 Cisco Access Point Specications Part Number 802.11a/g Non-modular LWAPP AP: Integrated Antennas AIR-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
Model 1131AG
1242AG
802.11a/g Non-modular LWAPP AP; RP-TNC AIR-LAP1242AG-x-K9 x=
68009260001-A
January 2009
2-29
WLAN and Backhaul Network Specications
Table 2-15
Cisco Access Point Specications (Continued) Part Number T=Taiwan
Model
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 specications. Verify all the part numbers as they may change.
WLAN and Backhaul Network Specications

The network infrastructure switching and routing equipment is supplied by the Enterprise. To fully maintain the end-to-end QoS required for the TEAM smartphone operation, this network infrastructure should support DiffServ at layer 3 (routing) and IEEE 802.1Q at layer 2 (switching).
2-30
68009260001-A
January 2009
TEAM smartphone
The 802.1Q/p marking occurs at the AP to Network (802.3) interface where the WMM access categories are mapped into 801.1Q priority. The TEAM smartphone utilizes AC_VO and AC_BE classes of service within WMM. The 802.1Q marking is also the mechanism used by IP Precedence on older wired backbone infrastructure networks to prioritize trafc. The TEAM smartphone, WSM and IP-PBX also preset the DiffServ Code Point value into the packet header on any originated packets to assist DiffServ Network Infrastructures to prioritize network trafc 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 Initiated Protocol (SIP) support is included, and it works with the other solution components to handle call routing. Table 2-16 lists the TEAM smartphone models that are supported: Table 2-16 TEAM smartphone Models Notes: Professional with 1400 mAh battery Professional with 1700 mAh battery Semi rugged, with 1400 mAh battery Semi rugged, with 1700 mAh battery
Model EWP1000 EWP1100 EWP2000 EWP2100
Table 2-17 lists the major technical specications of the TEAM smartphone. Table 2-17 Technical Specications Description Candy bar rugged and non-rugged WLAN Tri Band 802.11a/b/g Apps TI OMAP 2420 WLAN: TI 1253FE Bluetooth: Broadcom BCM2045 PWR MGMT: TI TWL92230
Specication Form Bands/Modes Chip sets
68009260001-A
January 2009
2-31
Features
Table 2-17 Weight Dimensions (H x W x D)
Technical Specications (Continued) Description 145 g / 4.9 oz (EWP1000 non-rugged) 160 g / 5.42 oz (EWP2000 rugged) 120 x 52 x 17.2 mm/4.7 x 2 x 0.7 inch (EWP1000 with 1400mAh battery) 120.5 x 54 x 18.6 mm/4.74 x 2.11 x 0.73 inch (EWP2000 with 1400mAh battery) 2 inch, 320 x 240 265K TMR color display Microsoft Windows 6.1 128 MB RAM/256 MB RAM, built-in Micro-SD removable memory card slot (up to 2 GB) Numeric
Specication
Display Platform/OS Memory Keyboard
Features
Table 2-18 lists the major features of the TEAM smartphone. Table 2-18 Feature Durability Battery life Features of the TEAM smartphone Description Meets indoor MIL specs (EWP2000 only) Depending on your system parameters and battery type, you can expect the following 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 Browser Audio Text Messaging PTT Std 1400 mAh/1700 mAh Excap battery HTML/WAP 2.0 compliant Toll quality voice High audio speaker phone Inside Enterprise text messaging PTT button Private Call with Call Alert Group Call to up to 255 groups
2-32
68009260001-A
January 2009
Photo
Table 2-18 Feature
Features of the TEAM smartphone (Continued) Description Click to call/Click to message PTT and text messaging UI enhancements UI capabilities call dialer, multiple line appearances, and text messaging
Enhanced User Interface
Connectivity Integrated Apps Accessories
Mini-USB, PTT headset jack, Bluetooth class 2, 802.11 a/b/g Telephony, PTT, voice recognition, document editing, support for third-party LOB application Mini-USB, single unit desktop charge, 6-slot Desktop Charger (EWP2000 only)
Photo
This 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
Figure 2-6
Menu View on the TEAM Smartphone
Software
This 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
Screenshots
Has key security enhancements, such as TLS signaling encryption to prevent user spoong. TEAM uses the encryption features of the WLAN and the associated Windows Mobile drivers to ensure that subscribers have the option to encrypt all WLAN trafc 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)
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.
Introduction
The primary purpose of QoS is to ensure clarity of voice quality and quality of experience for subscriber without hindering the efcient working of the Enterprise network dictate. Each component of the solution has a role in maintaining proper QoS functioning. TEAM species the required QoS settings for Enterprise networks and equipment, and engineers the proper QoS operation in TEAM supplied equipment and devices. QoS involves: Reserving bandwidth
2-36
68009260001-A
January 2009
QoS Mechanisms for the Wireless LAN
Packet classication
QoS includes precisely dened sound and delay requirements and well thought out network element congurations. 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 recongured to ensure that it does. As part of the various mechanisms for QoS, the WLAN equipment and IP-PBXs are considered the trust boundaries. The term trust boundaries are used to imply that they are trusted (from a security and QoS point of 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 needed QoS. Each network element that has QoS functionality honors (and sometimes changes) these markings through pre-specied behaviors. Each network element is continually monitored.
QoS Mechanisms for the Wireless LAN

QoS mechanisms between the TEAM smartphone and the AP/Gateway are derived from the 802.11e specication. Virtual LAN priorities are used between the AP/Gateway and the rest of the network.
Packet Classication
Most packet classication and marking is done at the TEAM smartphone and the IP-PBX. Each device is classied based on the application/port mapping to a Differentiated Service Code Point (DSCP), and it selects the DSCP and inserts it in the IP header for all of the packets in the ow. When the packets enter the VLAN, the device maps the DSCP over to the appropriate VLAN priorities.
Access Point/Gateway Bandwidth Reservation

Bandwidth reservation occurs as part of the Wireless LAN (WLAN) operation. Bandwidth reservation, combined with admission control, is needed for the airlink. The procedure is dened by a specication, so it is necessary for the access points to support it. There may also be some type of conguration needed in the access point to enable the feature. The AP/Gateway requires bandwidth reservation to ensure that: The requested QoS is maintained for the packet ow in question. Adequate bandwidth is available for handovers.
Bandwidth reservation for the AP/Gateway is dependent on the implementation of schedulers and policies.
68009260001-A
January 2009
2-37
911 Dialing
Solutions selected for implementation must comply with the current standards denitions for voice QoS in the WLAN environment. Interworking with LAN equipment that deploys standards-based QoS solutions are expected.
Bandwidth Reservation currently only exists within Cisco Certied Extensions (CCX) for Cisco WLAN deployments. With the adoption of WMM-AC this will also extend to other vendors, such as Motorola/Symbol.
911 Dialing
A 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 a callers location. If the call accidentally drops, the PSAP agent calls back and the return call from the PSAP is forwarded to the subscriber who dialed 911. If two different TEAM smartphones call 911 from the same location, the PBX sends the same location number for both the calls. If both calls drop and the PSAP agent calls back, the solution only rings the last TEAM smartphone to drop the 911 call, not both TEAM smartphones.
Section 508 Compliance

TEAM provides teletypewriter support in SIP and Real-time Transport Protocol (RTP) to comply with the Section 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 access to and use of information and data that is comparable to the access and use by employees who are not individuals with disabilities, unless an undue burden is imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public, seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public 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
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 both the platforms of the WSM and the NSM.
IPsec Between NSM-WSM

Information necessary for managing the WSM application is communicated through a connection between the WSM and NSM. Since voice service is a critical Enterprise capability, securing the management of voice services is important to enterprises. IPsec is a means of creating a secure connection. IPsec can be set 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 le transfer NSM-WSM network management NSM-WSM provisioning interface
IPsec Between WSM-PBX

IPsec is used to establish secured links between the WSM and a PBX that supports only the IPsec security option (no TLS). For SIP signaling security, use the IPsec ESP protocol in transport mode for securing the signaling path between the WSM and the PBX, when TLS/TCP is not supported by the partnering PBX. The transport mode is 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
2-40
68009260001-A
January 2009
Chapter
Planning 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 assessmentThe existing wired, wireless, and telephony infrastructures should be evaluated for voice readiness. This involves the analysis of the existing wired and wireless network and telephony infrastructures and any recommendations for changes or additions to support the TEAM VoIP solution. Perform network planning and design If additions or changes to the existing wired or wireless infrastructure are required, network design will be required to identify wired and/or wireless network changes such as the addition of Access Points (APs), addition or reconguration of switches or routers, or the addition of an IP PBX or TDM Gateway.
68009260001-A
January 2009
3-1
Installation Activities
New deployment IP telephony or a TDM GatewayBesides supporting mobility, IP telephony provides numerous other benets. These systems support a full complement of telephony features and call processing functions, and deliver these across the Enterprise IP network. A converged voice/data network simplies network administration and reduces the cost of endpoint moves, adds, and changes. Signicant savings are possible by routing IP voice calls over the corporate data network, instead of the costly public toll network. If an update to IP telephony is not feasible, a TDM gateway can provide the ability to deploy the TEAM solution with a TDM PBX. WLAN designDesigned from ground-up to support voice trafc, the WLAN delivers critical features such as intelligent no delay roaming, load balancing, advanced quality of service and end-to-end security. Additionally, centralized security and management capabilities have many benets for traditional data applications.
Installation Activities

The following sections explain the installation activities that range from initial site install/presale activities to verication of the compatibility of the hardware/software components (provided by the Enterprise) with the TEAM solution.
Initial Site Install/Pre-sale

Initial 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 of both. These services would typically include the following activities:
3-2
68009260001-A
January 2009
Initial Site Install/Pre-sale
Characterization of the existing LAN for voice trafc This may have to be extended to a comprehensive plan to include additional LAN ports needed to interface APs, additional bandwidth concerns, and additional IP addressing concerns. This should also work with Deployment Loading tools to avoid re-entering common information. The Deployment Loading tools are used by the end-customers 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, visit www.motorola.com/RFdesign. Tools include: Motorola LANPlanner used to design, plan, and optimize the network. Motorola SiteScanner used to simulate network activity and perform site surveys for 802.11 Wi-Fi networks. OmniPeek used for Wi-Fi and Ethernet snifng (EtherPeek and AiroPeek are now OmniPeek). Wireshark (formerly Ethereal) used for Ethernet snifng. AirMagnet, GL Communications, VXVoice, and ixChariot used for various very low level assessments of network and audio performance.
Identication 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 Conguration Protocol (DHCP) server E-mail server Voice Mail server Network Time Protocol (NTP) server IP-PBX/Analog PBX Directory server Existing WLAN infrastructure
Identication of existing customer accounting interface
68009260001-A
January 2009
3-3
Compatible Hardware and Software Versions
Compatible Hardware and Software Versions

Table 3-1 provides references to more information about hardware and software versions that are compatible with the TEAM solution. Table 3-1 Compatible Hardware and Software Versions Component Wireless Services Manager (WSM) Hardware and Software Versions Motorola - supplied appliance, Motorola-supplied appliance software. See"Technical Specications" on page 2-6.
Layer Solution Equipments
Network Services Manager (NSM)
Enterprise-supplied server, Motorola-supplied server software. See "NSM Server Hardware Requirements" on page 2-8. Enterprise-supplied servers. See "Enterprise Control Servers" on page 1-7. Enterprise-supplied servers. See "PBX (Telephony Servers)" on page 2-13. Enterprise-supplied servers. See "Telephony-Related Servers" on page 2-18. Enterprise-supplied servers. See "Other Enterprise Servers" on page 2-19. Enterprise-supplied routers. See "Routers" on page 2-22. Enterprise-supplied switches. See "Switches" on page 2-22. Enterprise-supplied WLAN equipment. See "WLAN Equipment (Multiple Vendors)" on page 2-22.
Control Servers (DHCP, DNS, AAA, NTP) PBX (Telephony Servers)
Telephony Related Servers (Voicemail, CDR, Directory) Other Enterprise Servers
Communication Backhaul
Routers Switches
Wireless LAN (WLAN)
3-4
68009260001-A
January 2009
IP Evaluation and Planning
IP Evaluation and Planning

Part of IP planning is to evaluate the customers IP scheme and provide recommendations for 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 trafc uses to tunnel from WLAN coverage areas to the backend equipment (NSM, WSM, DNS/DHCP/AAA, and so on). Determine if the Enterprise IT department will create VLANs to support the IP trafc. Check if helper addresses are required to route the IP trafc appropriately. APs are layer 2 devices No IP addresses required. Determine the need for IP network evaluation (whether the current network can handle 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 Network

This section provides information needed to plan and set up the WLAN network. Whether augmenting an existing infrastructure or implementing a new WLAN, 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 uplinks and 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 the site 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
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 WLAN

The most critical element of the TEAM solution is deciding how the WLAN is either initially built or upgraded from a data-only network to one that supports both data and voice. If planning 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 Area

While 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 planning to reduce the risk of interfering with legacy internal wireless networks. Consider conict with other wireless solutions, and keep RF low. Needs of the customers (number of subscribers, feature and services that are provided, and protocol of choice).
Qualifying an Existing Infrastructure as Voice-Capable

Perform 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 equipment that Motorola has either tested, or is in the same family as equipment tested by Motorola. 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
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 customers existing LAN equipment. The LAN network needs to support QoS (802.1Q/p). Evaluate the customers existing network management system and capacity. If it is a network management system from another vendor, then re-use for TEAM is outside the current scope.
Conduct a site survey (which determines rough coverage, not precise AP locations). See "Site Surveys" for additional considerations.

The Enterprise-provided WLAN equipment must meet Quality of Service (QoS) requirements. QoS is the prioritization of packets across a network. QoS becomes critical when voice is introduced over 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 effect is the same as not having QoS on that path. The effect on the voice trafc is to deprioritize the packets, which then have additional jitter and delay. This causes the audio to degrade and may manifest as drop outs and additional noise in the background.
Site Surveys
A Radio Frequency (RF) site survey is used to supply enough information to determine the number and placement of APs to provide adequate coverage throughout the facility. Motorola offers tools that help design and subsequently monitor WLANs. In addition, Motorola offers professional services to perform site surveys. For more information, contact your Motorola Account manager. For WLANs, it can be difcult to predict the propagation of radio waves and detect the presence of interfering signals without the use of test equipment. Even if you are using omni-directional antennas, 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 an irregular and unpredictable RF radiation pattern. As a result, it is necessary to perform an RF site survey to 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 also detects the presence of interference coming from other sources that could degrade the performance of the WLAN. The need and complexity of an RF site survey varies depending on the facility. For example: A small three-room ofce may not require a site survey. This environment requires a single AP located anywhere within the ofce to maintain adequate coverage. If this AP encounters RF interference from another nearby wireless LAN, choose a different channel to eliminate the problem.
68009260001-A
January 2009
3-7
General Steps to Conduct a Site Survey
A larger facility, such as an ofce complex, apartment building, hospital, or warehouse, generally requires an extensive RF site survey. Without a survey, subscribers can end up with inadequate network coverage and suffer from low network performance in some areas. This may force rework to relocate and add APs to the facility after installing and interconnecting 20 APs or more, which is not desirable.

When conducting an RF site survey, consider these general steps: 1. Obtain a facility diagram Before beginning the site survey, locate a set of building blueprints. If none are available, prepare a oor plan drawing that depicts the location of walls, walkways, and any other obstructions. Visually inspect the facility Be sure to walk through the facility before performing any tests to verify the accuracy of the facility diagram. This is a good time to note any potential barriers that may affect the propagation of RF signals. For example, a visual inspection will uncover obstacles to RF such as metal racks and partitions, items that blueprints generally do not show. Identify subscriber areas On the facility diagram, mark the areas of xed and mobile subscribers. In addition to illustrating where subscribers may roam, indicate where they may not roam. Determine preliminary AP locations Consider the location of subscribers and range estimations of the WLAN products you are using, to determine the locations of APs to provide adequate coverage throughout the subscriber areas. Plan for some propagation overlap among adjacent APs, but ensure that channel assignments for APs are far apart to avoid inter-AP interference. Consider mounting locations, which could be vertical posts or metal supports 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 AP mounted near an outside wall, for example, could be a good location if you use a 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.
2.
3.
4.
3-8
68009260001-A
January 2009
5.
Ensure WLAN equipment meets requirements that make it voice-capable: Include power requirements and power availability of WLAN equipment. Document A/C and oor space requirements, as well as distances to connect to LAN 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 (other vendors, older non-compliant APs, and so on).
It is unlikely that an existing WLAN will support a TEAM solution. Most WLANs 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 from Motorola (Site Scanner - www. motorola.com/RFdesign) or from a third-party company. For example, 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 walking varying distances away from the AP. You do not need to connect the AP to the distribution system because the tests merely ping the AP. However, you need AC power. Note the data rates and signal readings at different points as you move to the outer bounds of the AP coverage. In a multi-oor facility, perform tests on the oors above and below the AP.
A poor signal quality reading indicates that RF interference is affecting the wireless LAN. This would warrant the use of a spectrum analyzer to characterize the interference, especially if there are no other indications of its source. Based on the results of the test, you may need to reconsider the location of some APs and redo the affected tests. 7. 8. Ensure smooth transition from subnet to subnet Find locations to place APs to ensure seamless roaming throughout the building. Document the ndings Once you are satised that the planned location of APs will provide adequate coverage, identify the recommended mounting locations on the facility diagrams. The installers will need this information. Also, provide a log of signal readings and supported data 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
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 Recommended Over 18 dB S/N in all areas within the Enterprise building. S/N = signal/noise anything less than 18 means poor coverage and possible dropped calls. Prefer 802.11a, where channels do not overlap or if using 802.11b/g, use channels 1, 6, or 11. Comments This corresponds to an RSSI of approximately -70 dBm, given a typical noise oor of -88 dBm. The frequency and power level plan must seek to minimize co-channel interference on all WLAN cells. 802.11 is a carrier-sense system, so it does not require a certain minimum C/I in order to work. The presence of interfering cells has an unpredictable effect on system capacity and may cause other unforeseen problems.
WLAN element Coverage with in a facility
Adequate C/I (co-channel interference, two APs on a channel will interfere, unless you install them farther apart.)
The following must be considered with respect to WLAN requirements for TEAM performance: Ensure WLAN is designed to Voice specications Motorola offers products and services to assist in the planning, deployment, and maintenance of such WLANs. For example, Enterprise Planner product, RFMS, Intrusion detection systems, and so on. See www.motorola.com/RFdesign. It is recommended to put TEAM trafc on 802.11a and keep data trafc especially with slower 802.11b devices, on 802.11b/g.
Placement of Access Points

To derive a worst-case Micro- Mobility rate, an average AP coverage area must be determined. Assuming a 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-case geography could involve a subscriber walking down the hall to meeting room or cafeteria, alternately bouncing between APs that belong to separate AP Gateways. This design must be avoided to eliminate the strain on the system when the TEAM smartphones re-DHCP and SIP Register on AP Gateway changes. This hallway scenario is challenging because it involves a burst of trafc every hour as persons enter the WLAN coverage 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, building corridors, 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
Roaming Across Access Points
Using this approximation, 700 m2 covers a population of approximately 35 people. Given trafc intensity per subscriber of 0.15 Erlangs, the average call load offered to the AP is 5.25. Handling this load requires 11 servers (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 perform different 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.

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
Figure 3-2
Roaming Across Subnets

A TEAM smartphone cannot change its IP address mid-stream when moving from one AP to another on 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
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 between the 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
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 Bands
This section describes some of the common challenges of deploying systems in the 2.4 GHz and 5 GHz bands. Table 3-3 lists the frequency band challenges. Table 3-3 Standard 802.11a 802.11b Frequency Band Challenges Band 5 GHz 2.4 GHz Issue Does not have overlapping channels, but some adjacent channel interference is possible. Channels in 2.4 GHz band overlap. Increased interference sources on the 2.4 GHz band, from cordless telephones, microwave ovens, and Bluetooth devices. Bluetooth operation in the same band does consume bandwidth. Bluetooth headset operation can consume signicant bandwidth, which may interfere with other TEAM smartphones co-located on a different 802.11b/g channel. Interference due to adjacent channel(s). Need four frequencies to map a facility without overlap. Channels 1, 6, and 11 are commonly used. Channels 1,4, 7, and 11 can also be used at 10% increase in interference, which may be reduced by choices of adjacent 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/g AP, some form of protection is required to avoid having 802.11b clients 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). For example, 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 must engineer 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 extremely congested. Deployers can modify the proles of laptops with wireless access to disable the wireless when the laptop is connected to the LAN. Also, they can program APs to exclude some devices. This plan allows laptops to access a wireless network while accommodating voice over WLAN.
3-14
68009260001-A
January 2009
Firewalls
Firewalls
Data operations outside the Enterprise, such as Internet browsing, are possible because of rewall settings within the Enterprise. If rewalls exist for LAN, Internet access, or WLAN, it is recommended to have the following information: Purpose of rewall (for example, Internet access, or to separate Human Resources LAN 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 rewalls (indicate switch hostname).
Backhaul Network Considerations

This section includes considerations for the wired LAN network, including network routers and switches. It is recommended that you have the information listed in this section available so you can properly install and congure the equipment.
Local Area Network (LAN) Devices

It is recommended to access the outputs of the commands for all LAN, Internet Network devices, and WLAN through which voice travels (for example, routers, switches, and switching routers). Save the information to an individual .txt or .doc le 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: Conguration Software version Software feature set Flash and memory Modules installed Ports Port capabilities VLANs
68009260001-A
January 2009
3-15
LAN Links
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 Links
For LAN links, Motorola assumes that you have performed industry-standard planning. You need to understand and prevent QoS issues. You must implement some form of QoS, for example, in the router, check the Differentiated Services Code Point (DSCP) ag from the TEAM smartphone data to properly prioritize the trafc on the Layer 3 level.
Voice Network Considerations

The most important consideration for the voice network is proper coverage within a building. This is done 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] and Media Processor cards if applicable). Special third-party applications used (for example, Computer Telephony Integration (CTI). Wireless TEAM smartphones used. Latest PBX trafc reports, showing busy hour attempts and peak trafc usage. Determine if PBXs are linked across a WAN (through ATM, VOIP, dedicated T1s, QSIG) or not. Bandwidth of site-to-site connections for voice Check if PBX extenders (such as the Expansion Port Network) use TCP/IP or ISDN BRI links.
3-16
68009260001-A
January 2009
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 if it can be implemented for setup.
68009260001-A
January 2009
3-17
Network Topology Maps
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 maps provide the support engineers with valuable information and should reect the portion of the network that will carry the converged trafc. 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 to eliminate Ethernet port speed mismatches)
Additional Guidelines and Requirements

This section explains additional guidelines and requirements.
Rack Requirements
The TEAM equipment, including the WSM, NSM, and PBX, ts in one standard 19-inch rack.
Required Information
Appendix B provides tables that you must complete as part of system planning. This information is needed to install the system components. Refer to the TEAM Installation and Conguration 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
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 the equipment, for example, 173.32.204.254.
Security

The WLAN system employs various security protocols at different layers within the system to protect the system from unauthorized access, intrusion, and compromise. This includes security frameworks for authentication and authorization and for the encryption of signaling and bearer (voice) trafc. The security framework protects the physical components of the system from attack. Authentication and authorization determine if a TEAM smartphone and a subscriber should be granted access to the system. Encryption ensures privacy of the voice and data being transmitted. Separate security policies and measures are congured and deployed on interfaces between various 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 certicates on TEAM smartphones and servers for device authentication. Extensible Authentication Protocol Transport Layer Security (EAPTLS) 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 the SIP Proxy for both directions of the SIP signaling trafc.
Authentication delegation:
68009260001-A
January 2009
3-19
Security
Once TEAM smartphones and subscribers are authenticated by the WSM, maintaining of separate registration records on the PBX or triggering further authentication challenges by the PBX is not required. The WSM becomes Enterprise trusted.
Figure 3-5
System Architecture Security
3-20
68009260001-A
January 2009

The primary purpose of Quality of Service (QoS) is to ensure proper voice quality and quality of experience for subscribers, without hindering the efcient working of the Enterprise network. QoS is affected by packet loss, 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 the PBX. It involves reserving bandwidth, and packet classication getting preferential treatment. This is continually monitored, measured, and veried.
A pre-deployment analysis of the Enterprise network is highly recommended. The analysis requires that 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 not honored, it may be difcult or impossible to ensure adequate QoS to subscribers.
Overview of QoS Roles by System Component

Each component has a role to play in ensuring QoS. Refer to the TEAM Installation and Conguration Guide for specics on setting up QoS. Audio quality will be degraded if QoS is not set up correctly on each network element. 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 Role The VLAN ID must be set correctly for QoS during installation of the WSM. Provide a user interface for the operator to specify QoS parameters. Sets parameters by trafc type, giving higher priority to voice over call control signaling. QoS conguration information is pushed down from the NSM to the WSM.
Component WSM NSM
68009260001-A
January 2009
3-21
Overview of QoS Roles by System Component
Table 3-4 IP-PBX
Overview of QoS Roles by System Component (Continued) Role Provide a properly congured QoS capable media gateway that marks packets with the appropriate DSCP. Provide echo cancellation for all voice calls in the media gateway.
Component
During PBX conguration, the installer identies the G.711 mu codec to be used to compress data and ensure QoS, giving voice priority over data. WLAN Must participate in the bandwidth reservation scheme Determine the proper trafc class for a packet from its 802.1Q/p priority and transmits it to the TEAM smartphone accordingly. Map TID priorities from the TEAM smartphone to VLAN priorities on all frames entering the network. TEAM smartphone Provide echo cancellation in the TEAM smartphones. Provide packet error concealment algorithms for each vocoder (G.711 and 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 all packets in the ow. Determine the proper trafc identier (TID) and insert it in the 802.11 MAC header at the air interface. Determine the proper trafc class for a packet from an application and transmit it to the Enterprise infrastructure accordingly.
3-22
68009260001-A
January 2009
Appendix
Detailed 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 TEAM smartphone when it is located in the Enterprise WLAN.
Make and Receive Phone Calls

TEAMs basic call feature allows a subscriber to make or receive a call to or from another subscriber 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 DID trunks, which forward only the last three to ve 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 ofce (CO) would forward 234 (or 1234, depending up on the dialing plan conguration set for the PBX). The PBX then dials the extension. This feature is only applicable to callers outside the Enterprise. The actual translation happening between the central ofce and the PBX is completely transparent to the subscriber. The subscriber would dial the Enterprise number as any other PSTN number.
68009260001-A
January 2009
A-1
Direct Outward Dialing Plans
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 to reach the Automatic Route Selection (ARS) feature. The automatic route selection feature uses the dialed digits, 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 has the intelligence to properly route and PSTN-bound call out a PSTN trunk. This routing is usually facilitated via the congured PBX dial plan. If for some reason, the PBX does not support this, the subscriber is required to manually dial the DOD access code when accessing the PSTN.
Call Forwarding
The Call Forwarding (CF) feature allows a TEAM subscriber to redirect calls to user-dened destinations. 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 of its desired Call Forwarding Status, as follows: Unconditional Busy/No Answer
Call Forwarding empowers the WSM to inform the call originator accordingly on any subsequent call attempts impacting the TEAM smartphone so that the call can be retargeted to the destination.
Call Waiting
The Call Waiting feature of the TEAM solution provides an indication to a subscriber, who is already engaged in an established interconnect call, that one or more calls are awaiting connection. For example, it noties a subscriber of an incoming call through the use of a call waiting tone. The subscriber can then answer that call and either end or place the current call on hold.
Call Hold
The Call Hold feature of the TEAM solution allows a subscriber to change an active interconnect call into the hold state by pressing a button on the TEAM smartphone. The TEAM smartphone provides a 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. The call on hold can be retrieved at the subscribers discretion. The Call Hold feature is required for both Call Waiting and Conferencing. Music hold is determined by the conguration 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
Call Transfer
Call Transfer
Call Transfer lets a caller transfer an established interconnect call to another telephone number within or outside the Enterprise. The caller disconnects when the call is successfully transferred. The Call Transfer can be blind (unattended) or attended. Attended call transfer is not available with the TDM gateway conguration.
Caller ID
The Caller ID feature displays the name or telephone number associated with an incoming call on the called partys TEAM smartphone. A telephone-related device allows individuals to identify callers before answering the telephone. When a telephone rings, an electronic display registers the callers name and phone number. Individuals can use the Caller ID feature to screen their calls. TEAM smartphones subscribing 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 by a displayed name before the call is answered. The displayed name is associated with the Calling Party Number. The calling party name is not available with all congurations. Automatic Number Identication (ANI) is a telephone network feature that allows the transmission of the ten-digit area code and telephone number of the originating telephone to the receiving telephone.
Abbreviated Dialing
Abbreviated Dialing is a feature that requires that a caller dial only the last few digits of a phone number 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 in the PBX as SIP line extensions. The TEAM smartphone provides Abbreviated Dialing functionality in 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 or more callers, all in different locations. The maximum number of participants is dependent on the specic PBX 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 at a time) to an existing two-person call. Most PBXs use an internal audio bridge to support between 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
Meet-Me conference is a pre-planned conference where three or more subscribers are provided a conferencing bridge extension to dial in to. The PBX supporting the bridge extension merges the audio from all participants dialing into the specic extension.
Meet-Me conference calling may not be available with every PBX.
Voice Mail Indication and Retrieval Scenarios

This 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 Notication/Message Waiting Indication Message Retrieval and Playback
Messaging
Regardless of the subscriber location, each Enterprise subscriber has a single mailbox and voice mail notication. The IP-PBX partner provides access to the voice mail service in the Enterprise. The PBX is responsible for the connection of all Enterprise phones to the Enterprise voice mail system.
Voicemail Notication/Message Waiting Indication

Voice mail notication within the Enterprise is done by the PBX which activates the Message Waiting Indicator (MWI) icon on the TEAM smartphone. The TEAM smartphones receive an MWI in real-time while in WLAN coverage, or delayed through registration to the WLAN. The PBX has the sole connection to the Voice Mail Server, and denes change of state: No message, Message, or All messages Read. The PBX forwards any unanswered call to the Voice Mail Server where the caller can leave a message. After a message is left, the Voice Mail Server sends an MWI to the recipient phone through the PBX and WSM. This tells the recipients phone to display an icon indicating that a message has been left for the recipient. When a recipient calls into voice mail server and listens to the message, the Voice Mail Server sends a new MWI to clear the recipients display.
A-4
68009260001-A
January 2009
Message Retrieval and Playback
Message Retrieval and Playback

Retrieving and playing voice mail messages is based on the Telephony User Interface provided by the PBX. This is a dial-in interface that supports operations such as saving, playing, and deleting back voice messages. If an Enterprise has a unied messaging solution, the Telephony User Interface provides the same capabilities for e-mail messages. The TEAM solution supports texttospeech conversion from e-mail playback on a voice channel.
DTMF (Overdial) Support

Post Digit or Dual Tone Multi-Frequency (DTMF) dialing describes the ability of the system to capture DTMF tones from the subscriber once the call has been established. This feature is used in many automated telephony services such as menu selection, collection of credit card or pre-paid calling card numbers. DTMF collection within the Enterprise uses RFC2833, which denes specic Real-Time Transport Protocol (RTP) payloads for sending and playing back DTMF tones. To compensate for the fact that RTP is normally sent over an unreliable protocol, User Datagram Protocol (UDP), RFC 2833 species sending each digit multiple times. In WLAN, the DTMF tones are encoded packets which the infrastructure receives 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.
911
Enhanced 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 the callers location information, and for the call to indicate a call-back number in which the PSAP can dial to reconnect any 911 call that is dropped. The location information and call-back number are integrated into what is called an Emergency Line Identication Number (ELIN). An ELIN, a simple phone number owned by the Enterprise, serves the following purposes: As an identier 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 the ultimate responsibility of ensuring that the 911 call carries the proper ELIN. The granularity of the ELIN is determined by the Enterprise and facilitated in the PBX. This means the PBX controls whether the ELIN is the callers actual phone number or just a phone number representative of a geographic area known as an Enterprise Emergency Response Location (ERL). The PBX also controls whether the ELIN represents a specic oor, wing, or such in the Enterprise or just the physical address of the Enterprise. If an ELIN representative of an ERL is used, the PBX may provide the ability to map a call-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 sending of the Calling Party Number (CPN) over ISDN trunks. This ability to block the CPN is suppressed during 911 calls because the CPN may be used by the PSAP to aid in the emergency response.
68009260001-A
January 2009
A-5
Call Restriction
Call Restriction
Call Restriction allows network operators to restrict the type of phone calls that are permitted for each of the subscribers in the enterprise. That is, the WSM can prescribe that certain calls are allowed or rejected based on the originating and terminating numbers. This is implemented by: 1. 2. dening each subscriber as a member of a specic class. 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 le (format = CallRestrictionData.csv ) containing classes and associated members and uploads the le to the WSM. Each class is assigned a rule which determines which destination numbers that are restricted for that class. Once the Call Restriction le is uploaded, it must be imported into the WSM database using the wjanitor1 tool. Rules can be updated by editing the CallRestrictionData.csv le and re-importing it.
911 calls may not be restricted
If no CallRestrictionData.csv le is congured in the WSM, the WSM disables Call Restriction and permits all calls.
Busy Indicator
When the SIP Proxy sends an INVITE to a phone in the WLAN that is busy, the phone returns a 486 - Busy message as a response. The phone does not ring or present any other indication 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
PTT Features
PTT Features

The TEAM smartphone provides Push-to-Talk (PTT) voice messaging features within an Enterprise WLAN. PTT is available as an instant voice button on the TEAM smartphone. The PTT feature does not affect any other feature on the TEAM smartphone. It works by reserving a certain bandwidth for 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 between two dispatch-capable TEAM smartphones. Call Alert Send call alert notices which are data-only invitations that convey a desire for a subsequent private call. Group Call Place a call to a pre-provisioned group. The subscribers can be members of multiple groups and have the option to select which group they want to call to afliate with .
PTT is an optional purchasable feature that requires a separate purchase. Group Call is an optional licensable feature that requires an additional license to the one purchased for the PTT feature.
Private Call
The private call (one-to-one half-rate voice exchange) feature allows a TEAM subscriber to set up an instant half-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 the coverage of the Enterprise WLAN. In addition, the originator TEAM smartphone can only place calls to the TEAM smartphones that are provisioned within the same WLAN system. Likewise, a target TEAM smartphone can only receive a private call when it is currently registered and within the coverage of the WLAN system, 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 successful call attempts. The PTT call setup time is measured from the time the caller presses a PTT button to the time the talk permit tone is played on the originators TEAM smartphone. Example scenario: Bob wants to call Joe, so he enters Joes extension and presses the PTT key. All calls from a TEAM smartphone are routed through the WSM since phones only connect to 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
Call Alert
A call alert (one way attention request) allows a TEAM subscriber to invite another subscriber within the same Enterprise to participate in a private call. A call alert can only be sent from a TEAM smartphone 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 within the same WLAN system. Likewise, a target TEAM smartphone can only receive a call alert when it is currently registered and within the coverage of the WLAN system, and can only be received from a TEAM smartphone which is also within the same WLAN system.
Group Call
A group call (one-to-many half-rate shared single voice) allows one subscriber of the TEAM solution to initiate and participate in a half-duplex conversation with more than one other subscriber in the same WLAN system. Access to group call functionality requires an additional license to the one purchased for the PTT feature. Additionally, group call-specic provisioning is required to not only enable the feature on a system basis, but also for system congurations needed to use the feature. Group calls are congured through the NSM, and up to 255 talkgroups can be created. Group calls have oor control which is controlled by the WSM, one subscriber has control at a time. A subscriber receives an audible response to indicate if the call is successful or unsuccessful. The WSM sends individual messages to each TEAM smartphone. The WSM is in control of who receives audio packets, performs duplication of packets from the originator, and sends to each TEAM smartphone. If the initiator receives one or more successful answers then the call proceeds. However, the subscriber is not notied who is on the call and a few members may 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 talkgroup extension and presses the PTT key. All calls from a TEAM smartphone are routed through the WSM since phones only connect to 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 each talkgroup member (who responded successfully). The WSM is the network element that receives group call voice packets and does the duplication and routing to individual targets.
PTT Caller ID
When a subscriber sends a Call alert, Private Call, or Group call, the recipients phone emits a sound notication (or vibrates, depends on the subscriber prole) and displays the name or Private ID of the caller.
A-8
68009260001-A
January 2009
Missed PTT Call Indication
Missed PTT Call Indication

For a missed PTT call, an indication appears on the screen, and a notication tune is played.
Talkgroup Selection
The TEAM smartphone allows a subscriber to select a talkgroup for a PTT group call. A talkgroup is a predetermined group in the Enterprise. An active PTT group is the group that the subscriber is currently afliated with. A subscriber can only receive and monitor one talkgroup at a time - the active PTT Group. Example scenario Joe selects a talkgroup from his Contact list on the TEAM smartphone, or decides to call a group not 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 a time may speak on a group call. The Private ID or name of the person who is speaking appears on the display below the group number.
Presence/Instant Messaging
The 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 and view the status of other subscribers in the Enterprise.
Presence is an optional purchasable feature and is not integrated in the TEAM solution. Hence, the user can only gain access to Presence if the Enterprise purchases Microsoft Live Communication server. User can gain access to the Presence feature only if the Enterprise purchases Microsoft 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
Browsing corporate directory services (for example, various portals)
Text Messaging
The text message feature allows a TEAM subscriber to send and receive text messages within the Enterprise WLAN. A Text Messaging Client resides on the TEAM smartphone, integrated with Windows 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 set up the distribution list, select multiple people from the contact list and add to the To eld. 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 is not a valid address for text messaging). Abbreviated dialing/messaging Supports message delivery based on abbreviated extension dialing Target can be selected from contact list/address book or call log Address book integration Addresses from stored messages such as received messages Multiple target entry Send a single message to multiple targets The TEAM smartphone is pre-programmed with editable, Enterprise-specic messages Undeliverable messages stored for later delivery (upon registration of the TEAM smartphone) Can congure 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. Sender can request a delivery conrmation Queued if undeliverable Activated at Enterprise level, and provisioned for each subscriber. Subscribers can originate messages, or only receive messages. Canned Message Support Store-and-Forward Server
Delivery Conrmation
Activation and Provisioning
A-10
68009260001-A
January 2009
Simultaneous Voice and Data
Simultaneous Voice and Data

The simultaneous Voice and Data feature allows subscribers to retain data context in sessions independent of voice call activity (simultaneous voice and data). The simultaneous Voice and Data feature allows subscribers to perform web browsing and text messaging activities independent of telephony activities (simultaneous voice and data).
Corporate E-mail
The TEAM smartphone supports the corporate e-mail through the windows mobile 6.1 OS feature. E-mail access is through Windows Mobile interface. This requires integration with the Enterprise e-mail server.
Calendar, Phonebook, and Task

The TEAM smartphone supports the following Personal Information Manager (PIM) applications: Calender application client The client is only synchronized with a PC based Outlook using the Microsoft ActiveSync connection (no network involvement). Phonebook application client It performs contact and address functions. The client is only synchronized with PC based Outlook using Microsoft Activesync connection (no network involvement). The address book function is also synchronized with PC based Outlook using Microsoft active sync connection (no network involvement).
Directory Service
The TEAM subscriber supports directory services through an HTTP browser. Therefore, the directory server in the Enterprise needs to support an HTTP interface. The subscriber retrieves data from the directory server using an HTTP browser. Clicking on the data automatically dials the retrieved persons number. No direct storing capability from the directory to the phonebook is implemented.
Standard Browser Support

The TEAM smartphone supports a browser that allows a subscriber to access WML and HTML Web sites 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 certicates that the browser supports depend on the specic web servers that the subscriber is planning to access, and are not provided by Motorola. Normally, only the server side certicate is required for HTTPS, but the subscriber has to install the trusted CA certicate 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
Line of Business Applications

The 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 aggregator and are then sent to the WSM. The WSM will then send these messages to the TEAM smartphone. The text 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 customer events such as when an order is placed. In this case, the LOB application can generate a text message stating 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.
Introduction
The TEAM solution handles all the necessary call scenarios for the WLAN. The TEAM solution in the Enterprise uses a back-to-back user agent architecture. The TEAM smartphone does not independently signal to other TEAM smartphones in the Enterprise. The state of the other TEAM smartphones with which the TEAM smartphone is in logical communication is not available. Most calling scenarios are straightforward calls in this architecture. All call signaling messages between the PBX and the TEAM 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 the subscriber has not successfully registered to the WSM. This may be due to many reasons such as not complete, device not provisioned, device not in WiFi coverage, WLAN rejecting association request, User is not provisioned (WSM rejects registration attempts), and so on. Full Service his state appears when the TEAM smartphone is fully authenticated and registered and has both interconnect call and PTT capabilities. Voice Only This state appears if the subscriber has dispatch disabled (at the system or device level). Indicates that the subscriber has successfully registered to the WSM and is able to make use of telephony services. No Dispatch services are available in this state.
A-12
68009260001-A
January 2009
Bridged Call Appearance
Dispatch Only This could appear if SIP proxy is stopped for some reason, or if SIP proxy is incorrectly interrupted during registration and IC is not enabled, which is not an expected event. Indicates that the subscriber has successfully registered to the 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 appear under normal conditions.
Bridged Call Appearance

The PBX sends an update to the WSM whenever a subscriber initiates a call on a desk set, or answers a call on a call appearance bridged to a TEAM smartphone. The subscriber is allowed to join the bridge by signaling an invite to the PBX for the call appearance that the subscriber wants to bridge. The call ow is identical to a WLAN originated call.
Call State Updates

When the TEAM smartphone sends a Subscribe message to the PBX, the PBX in turn sends the current Message Waiting Indicator and Forwarding states to the TEAM smartphone through a Notify message.
WLAN Call Hold/Remove Hold

The TEAM smartphone can place an active call on hold by signaling the indication to the PBX. This is done using the standard SIP method for hold. The TEAM smartphone can take any call off hold by signaling the indication to the PBX.
WLAN Call Origination

The TEAM smartphone sends an invite message containing all the information about the call originator and the party that it is attempting to call. The TEAM smartphone receives an indicator that the call is being attempted. If it is determined that the calls receiver phone is ringing, the TEAM smartphone receives an indicator that the call is in progress and displays In Progress on the phone display. When the call attempt is answered by the receiver, the TEAM smartphone receives an OK message and displays Connected. The call ow is the same regardless of the type of party called.
68009260001-A
January 2009
A-13
WLAN Call Toggle
WLAN Call Toggle

The TEAM smartphone can toggle between an active call and a call on hold by placing the active call on hold and then removing it from hold.
WLAN Conference
When a TEAM smartphone has both a call on hold and an active call, it issues a Refer for the held party 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 participants to a conference. If sufcient streams are available on the conference device, the conference controller 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 controller does not have complete control over who joins the conference. The Meet-Me conference controller selects one of the Meet-Me conference numbers from the range specied. The conference controller then establishes the conference using that Meet-Me conference number. After the conference is established, anyone who calls that particular Meet-Me conference number is immediately connected to the conference.
WLAN End of Call

The WLAN or the TEAM smartphone may end a call by sending a Bye to the other party.
WLAN Incoming Call

The PBX sends an invite to the WSM through the TEAM smartphone indicating an attempted call. If the WLAN identies 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 incoming call, which results in the TEAM smartphone sending a nal response to the call. If a subscriber answers the incoming call, the TEAM smartphone sends an OK to the PBX. The call originator or PBX may abandon a call attempt at any time. In this case, a Cancel is sent to the TEAM smartphone. The PBX may attempt as many concurrent call attempts as the subscriber has call appearances. Bridged call appearances on the subscribers desk set phone for other subscribers are not signaled to the TEAM smartphone.
A-14
68009260001-A
January 2009
WLAN Status Change
WLAN Status Change

If the PBX determines that the status of a subscriber has changed, it signals the status change to the TEAM smartphone 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-dened destinations. 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. Forwarding can be activated for all calls, no answer (after a specied time limit), or busy.
Call Transfer
When a TEAM smartphone has a call on hold and an active call, the TEAM smartphone indicates a transfer of the two parties by issuing a Refer for the party on hold to the calling 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 to a 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 phone connects the caller to a destination line before the ringing tone begins.
68009260001-A
January 2009
A-15
A-16
68009260001-A
January 2009
Appendix
Equipment Checklists
The Appendix lists all the equipment checklists.
Enterprise Equipment Checklist

Complete Table B-1 to gather information before installing the system. This information is needed for Enterprise server installation and conguration checklist. Table B-1 Enterprise Server Installation and Conguration Checklist IP Address Entry Hostname Entry Hostname Examples wlan1nsm1 wlan1wsm1 wlan1dhcp1 wlan1dns1 wlan1aaa1 VLAN Entry
TEAM Component NSM WSM DCHP DNS Radius Server (AAA) PBX Components: PBX1-ETHERNET PBX1-SERVER PBX1-P330 PBX1-MGP PBX1-VOIP
wlan1pbx1ethernet wlan1pbx1server wlan1pbx1p330 wlan1pbx1mgp wlan1pbx-voip
68009260001-A
January 2009
B-1
WLAN Equipment Checklist
Appendix B: Equipment Checklists
Table B-1
Enterprise Server Installation and Conguration Checklist (Continued) IP Address Entry Hostname Entry Hostname Examples wlan1mail1 wlan1cmg dhcp-dns-aaa1 VLAN Entry
TEAM Component MAIL Access Point management application DHCP-DNS-AAA
1. If you are using a single machine to support DHCP, DNS, and AAA, then use this as your host name and address instead of the three separate ones above.

Complete Table B-2 before beginning WLAN equipment installation and conguration. Table B-2 WLAN Equipment Installation and Conguration Checklist Item Network Settings Wireless switch IP address Netmask (Subnet mask) Router IP address (Default Gateway) VLAN ID RADIUS Secret Wireless Parameters IP address format example: <173.32.204.x> Example: 255.255.255.0 For example, 173. 32.204.254 VLAN valid range is 1 to 4094 Enter the Secret password. Entry Notes
B-2
68009260001-A
January 2009
Table B-2
WLAN Equipment Installation and Conguration Checklist (Continued) Item Entry Notes Enter the SSID used for WLAN access. Same as RADIUS Secret password. Enter port numbers for all APs in the WLAN.
TEAM SSID Wireless Domain Secret AP port numbers
68009260001-A
January 2009
B-3
B-4
68009260001-A
January 2009
Glossary
Glossary

Glossary and Acronyms

10Base-T 10BaseT is a 10 mbit/sec half duplex Ethernet interface utilizing UTP (Unshielded Twisted Pair) wiring. AAA Authentication, Authorization and Accounting Access A performance measure of a data system. Access is measured from the time a data packet is sent from one of the units using the channel to the time the packet is received by the receiving unit. Access Method The ability and means necessary to store data, retrieve data, or communicate 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 encrypted and encrypted information can be decrypted. Different algorithms provide different levels of protection for the information. Analog 1.) As applied to an electrical or computer system, the capability of representing data in continuously varying physical phenomena (as in a voltmeter) and converting them into numbers. 2.) In telecommunications, a reference to Advanced Mobile Phone System (AMPS) or Narrowband Advanced Mobile Phone System (NAMPS) capability. Also the method of transmission of voice information used by AMPS and NAMPS phones, as dened by the Bell Spec, IS-88, IS-91, or IS-91A. 3.) A type of measurement in which the "line of measure" is continuous as compared to one which is discretely incremented. For example, a clock 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 amplier that allows audio to pass between both types of dispatch consoles and the base station. Backward Compatibility Ability of new units to operate within an "old" system infrastructure, or to directly communicate with an "old" unit. Bandwidth The difference between the limiting frequencies of a continuous frequency band, typically measured in kilohertz. May be considered, the amount in 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 call consists of a series of console and radio transmissions. A call is complete when all of 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 Challengehandshake Authentication Protocol Channel A single unidirectional or bidirectional path for transmitting and/or receiving of electrical or electromagnetic signals. This Radio Frequency (RF) resource is capable of supporting two-way trafc. Circuit-switching Circuit-switching provides a dedicated path between a sender and receiver for the duration of the communication. The advantages of the circuit-switched networks are dedicated circuits for the call and customers do not pay for idle bandwidth. Disadvantages are call setup time and potential under-utilization of the 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 Conguration Protocol DID Direct Inward Dialing DID A select number of digits that are associated with a specic radio user that allows 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 device nds 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 it only 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 Identier 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 Systems Interconnection) 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 Unied 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 Ofce 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 Conguration 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 Identier 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
AAA . . . . . . . . . . . . . . abbreviated dialing . . . . . . . . AP requirements for data networks architecture . . . . . . . . . . . assessing your environment . . . . assumptions for deployment. . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. 2-11 . A-3 . 2-24 . 1-4 . 3-1 . 3-10
Authentication, Authorization, and Accounting (AAA) server . . . . . . . . . . . . . . . . . . . . . 2-11 Avaya IP-PBX specications . . . . . . . . . . 2-17 Avaya media gateways . . . . . . . . . . . . . 2-17 Avaya media servers . . . . . . . . . . . . . . 2-17 Avaya PBX solutions . . . . . . . . . . . . . . 2-17
backhaul network. . . . . . . . backhaul network considerations backhaul network equipment . . bands and speeds, 802.11 a/b/g .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. 1-9 . 3-15 . 2-21 . 1-22
benets of the TEAM solution. . . . . . . . . . 1-3 bridged Call Appearance (CA) . . . . . . . . A-13 busy indicator . . . . . . . . . . . . . . . . . A-6
calendar, . . . . . . . . . call alert . . . . . . . . . Call Forwarding (CF) . . . call hold . . . . . . . . . call restriction . . . . . . call scenarios. . . . . . . call state updates . . . . . call transfer . . . . . . . Call Waiting (CW) . . . . caller ID . . . . . . . . . CDR processing server . . Cisco Access Points (APs)
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . A-11 1-15, A-8 . . . A-2 . . . A-2 . . . A-6 . . A-12 . . A-13 . . . A-3 . . . A-2 . . . A-3 . . . 2-19 . . . 2-29
Cisco APs . . . . . . . . . Cisco CME PBX . . . . . . Cisco CUCM PBX . . . . . Cisco PBX . . . . . . . . . Cisco RF switches . . . . . Cisco WLAN hardware . . . codecs . . . . . . . . . . . compatible hardware . . . . compatible software versions components . . . . . . . . conference calling . . . . . corporate e-mail . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . .
2-29 2-18 2-18 2-18 2-29 2-28 1-24 3-4 3-4 1-4 A-3 A-11
data features . . . . . . . . . data network, AP requirements deploying 802.11a/b/g . . . . device management client . . . device provisioning client . . . DHCP . . . . . . . . . . . . Dialogic solutions . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
A-9 2-24 3-14 1-17 1-17 2-10 2-18
Direct Inward Dialing (DID) . Direct Outward Dialing (DOD) directory server . . . . . . . directory service . . . . . . . DNS. . . . . . . . . . . . . Domain Name Server (DNS) . DTMF (overdial) support . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. A-1 . A-2 . 2-19 A-11 . 2-10 . 2-10 . A-5 IX-1
68009260001-A
January 2009
Index
Dynamic Host Conguration Protocol (DHCP) . . . . . . . . . . . . . . . . . . . . 2-10
EAP--TLS . . . . . . . . . . . . . . . . . . . 2-11 echo cancellation . . . . . . . . . . . . . . . . 1-25 enterprise control servers . . . . . . . . . . 1-7, 2-10
enterprise equipment checklist. . . . . . . . . . equipment checklists . . . . . . . . . . . . . . evaluating the coverage area . . . . . . . . . .
B-1 B-1 3-6
rewalls . . . . . . . . . . . . . . . . . . . . 3-15
frequency bands . . . . . . . . . . . . . . . . 3-14
group call . . . . . . . . . . . . . . . .
1-15, A-8
IEEE . . . . . . . . . . . . . . . . . . . . IM . . . . . . . . . . . . . . . . . . . . . initial site install/pre-sale . . . . . . . . . . . installation activities . . . . . . . . . . . . . Instant Messaging (IM) . . . . . . . . . . . . Institute of Electrical and Electronic Engineers (IEEE). . . . . . . . . . . . . . . . . . . .
. 1-21 . A-9 . 3-2 . 3-2 . A-9 . 1-21
International Telecommunications Union-Telephony (ITU-T) . . . . . . . . . . . . . . . . . . . . 1-24 IP evaluation and planning . . . . . . . . . . . 3-5 IP to TDM gateways . . . . . . . . . . . . . . 2-17 IP-PBX . . . . . . . . . . . . . . . . . . . . 2-17 IPsec requirements . . . . . . . . . . . . . . . 2-38 ITU-T . . . . . . . . . . . . . . . . . . . . . 1-24
key concepts of the TEAM solution . . . . . . . 1-18
LAN devices . . . . . . . . . . . . . . . . . . 3-15 LAN links . . . . . . . . . . . . . . . . . . . 3-16 Line of Business (LOB) applications. . . . . . A-12
LMT interface . . . . . . . . . . . . . . . . . 2-6 Local Area Network (LAN) devices . . . . . . . 3-15 Local Maintenance Terminal (LMT) interface . . 2-6
management applications . . . . . . . . . . micro mobility . . . . . . . . . . . . . . . Microsoft Exchange . . . . . . . . . . . . missed PTT call indication . . . . . . . . . Motorola enterprise. . . . . . . . . . . . . Motorola Integration Server . . . . . . . . . Motorola SW Update (MSU) . . . . . . . . Motorola-specic applications on the smartphone . . . . . . . . . . . . . . . . . . . Motorola/Symbol Access Points (APs) . . . .
. . . . . . .
. . . . . . .
1-12 1-19 2-20 A-9 2-26 2-13 2-20
. . 1-16 . . 2-26
Motorola/Symbol APs . . . . . . . . . . . . Motorola/Symbol PoE ethernet switch . . . . . Motorola/Symbol RF switches . . . . . . . . Motorola/Symbol WLAN hardware . . . . . . Motorolas Enterprise Mobility Support Center . Motorolas Support Central Website . . . . . . MS LCS . . . . . . . . . . . . . . . . . . . MS SMS. . . . . . . . . . . . . . . . . . . MS Text Messaging (MS SMS) . . . . . . . .
. . . . . . . . .
2-26 2-27 2-27 2-26 -xv -xvi 2-21 2-20 2-20
IX-2
68009260001-A
January 2009
Index
Network Time Protocol (NTP) server network topology maps . . . . . . . Nortel PBX . . . . . . . . . . . . NSM applications . . . . . . . . . NSM features . . . . . . . . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
2-13 3-18 2-18 1-12 2-7
NSM server application . . . . . . NSM server hardware requirements NSM server software requirements NSM software . . . . . . . . . . NTP server. . . . . . . . . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. 2-7 . 2-8 . 2-8 . 2-9 . 2-13
other enterprise servers . . . . . . . . . . . . . 2-19
overdial (DTMF) support . . . . . . . . . . . .
A-5
PBX (telephony servers) . . . . PBX hardware specications . . PBX software specications. . . PBX-IP . . . . . . . . . . . . phonebook . . . . . . . . . . . placement of Access Points (APs) planning for deployment . . . . planning for implementation . . planning the WLAN network . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . .
2-13 2-14 2-14 2-17 A-11 3-10 3-1 3-1 3-5
PoE ethernet switch. . . . . . . . . . . . . presence . . . . . . . . . . . . . . . . . . private call . . . . . . . . . . . . . . . . PTT caller ID . . . . . . . . . . . . . . . PTT features . . . . . . . . . . . . . . . . PTT voice messaging features . . . . . . . . public key infrastructure . . . . . . . . . . Push-to-Talk (PTT) features . . . . . . . . . Push-to-Talk (PTT) voice messaging features.
. . 2-27 . . A-9 1-15, A-7 . . A-8 . . 1-15 . . A-7 . . 2-13 . . 1-15 . . A-7
QoS . . . . . . . . . . . . . . . . Qos 911 dialing . . . . . . . . . . QoS AP bandwidth reservation . . . QoS gateway bandwidth reservation . QoS mechanisms for the WLAN . . QoS packet classication . . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
2-36 2-38 2-37 2-37 2-37 2-37
QoS roles by system component . . . . QoS section 508 compliance . . . . . qualifying an existing infrastructure as voice-capable . . . . . . . . . . . . Quality of Service (QoS) . . . . . . .
. . . . . 3-21 . . . . . 2-38 . . . . . 3-6 . . . . . 2-36
rack requirements . . . . . . . . . . . . . . . 3-18 RADIUS (AAA) . . . . . . . . . . . . . . . . 2-11 related documentation . . . . . . . . . . . . . -xiv
roaming across Access Points (APs) . . . . . . . 3-11 roaming across subnets . . . . . . . . . . . . . 3-12
security . . . . . . . . . . . . Session Initiation Protocol (SIP) . shared device . . . . . . . . . shared device/pool . . . . . . . shared pool . . . . . . . . . . simultaneous voice and data calls SIP . . . . . . . . . . . . . . site surveys . . . . . . . . . . smartphone . . . . . . . . . .
68009260001-A January 2009
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . 3-19 . . . . 1-24 1-17 to 1-18 . . . . 1-18 1-17 to 1-18 . . . A-11 . . . . 1-24 . . . . 3-7 . 1-11, 2-31
smartphone features . . . . . . . . . . . smartphone software . . . . . . . . . . . smartphone technical specications . . . . smartphone telephony features . . . . . . smartphone voice client . . . . . . . . . . smartphone VoIP client . . . . . . . . . . smartphone, Motorola-specic applications smartphone, third-party applications . . . . standard browser support . . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . .
2-32 2-34 2-31 A-1 2-34 2-34 1-16 1-17 A-11 IX-3
Index
standards-based design . . . . . . . . . . . . . 1-21 subscriber states . . . . . . . . . . . . . . . A-12 system architecture . . . . . . . . . . . . . . . 1-6
system management client . . . . . . . . . . . 1-17 system overview . . . . . . . . . . . . . . . . 1-1 system provisioning client . . . . . . . . . . . 1-17
talkgroup selection . . . . . task . . . . . . . . . . . . TEAM data services . . . . TEAM equipment . . . . . TEAM features and services TEAM services and features telephone numbering scheme telephony features . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . A-9 . A-11 . . 1-15 1-7, 2-3 . . 1-14 . . 1-14 . . 1-20 . . 1-14
telephony servers (PBX) . . . . . . . . telephony-related servers . . . . . . . . terminology . . . . . . . . . . . . . . text messaging . . . . . . . . . . . . . theory of operations . . . . . . . . . . third-party applications on the smartphone third-party enterprise servers . . . . . . typical customers . . . . . . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. 2-13 . 2-18 . 1-3 A-10 . 2-1 . 1-17 . 1-8 . 1-3
vocoders . . . . . . . . voice mail considerations voice mail indication . . voice mail server . . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. 1-24 . 3-17 . A-4 . 2-18
voice network considerations . . . . . . . . . . 3-16 Voice over IP (VoIP) . . . . . . . . . . . . . . 1-1 VoIP. . . . . . . . . . . . . . . . . . . . . . 1-1
WFA . . . . . . . . . . . . . . . . Wi-Fi Alliance (WFA) . . . . . . . . Wi-Fi Multimedia (WMM) . . . . . . Windows Mobile 6.1 Features . . . . . Wireless LAN (WLAN). . . . . . . . WLAN . . . . . . . . . . . . . . . WLAN and backhaul network . . . . . WLAN call hold . . . . . . . . . . . WLAN call origination . . . . . . . . WLAN call toggle . . . . . . . . . . WLAN conference . . . . . . . . . . WLAN end of call . . . . . . . . . . WLAN equipment . . . . . . . . . . WLAN equipment checklist . . . . . . WLAN industry standard requirements. WLAN network . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . .
. . . .
1-22 1-22 1-23 1-16 1-9 1-9 2-30 A-13 A-13 A-14 A-14 A-14 2-22 B-2 2-24 1-2
WLAN network planning . . . . . . . . WLAN status change . . . . . . . . . . WMM . . . . . . . . . . . . . . . . . WMM Power Save (WMM-PS) . . . . . WMM-AC Admission Control (Future) WMM-PS . . . . . . . . . . . . . . . WSM , key functions . . . . . . . . . . WSM appliance . . . . . . . . . . . . WSM conguration. . . . . . . . . . . WSM features . . . . . . . . . . . . . WSM LEDs . . . . . . . . . . . . . . WSM ports . . . . . . . . . . . . . . WSM software . . . . . . . . . . . . . WSM technical specications . . . . . . WSM, role in calls . . . . . . . . . . . WSM, system responsibilities . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
3-5 A-15 1-23 1-23 1-23 1-23 2-3 2-5 2-5 2-3 2-6 2-6 2-6 2-6 2-4 2-4
IX-4
68009260001-A
January 2009

TEAM 1.7 Solution Overview and Planning Guide 68009260001-A

Uploaded by

Copyright:

Available Formats

TEAM 1.7 Solution Overview and Planning Guide 68009260001-A

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TEAM 1.7 Solution Overview and Planning Guide 68009260001-A

Uploaded by

Copyright:

Available Formats

Total Enterprise Access and Mobility (TEAM) Solution

TEAM 1.7 Solution Overview and Planning Guide

2009 Motorola, Inc. All rights reserved.

Edition 1st Release

Date January 2009

TEAM 1.7 System Solution Overview and Planning Guide

Chapter 1: System Overview

Chapter 2: Theory of Operations

TEAM 1.7 System Solution Overview and Planning Guide

Chapter 3: Planning for Deployment

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

Appendix A: Detailed Features of the TEAM smartphone

Appendix B: Equipment Checklists

This page intentionally left blank.

This page intentionally left blank.

This page intentionally left blank.

About This Booklet

TEAM 1.7 System Solution Overview and Planning Guide

What Is Covered In This Booklet?

About This Booklet

Helpful Background Information

TEAM 1.7 System Solution Overview and Planning Guide

Contacting Motorolas Enterprise Mobility Support Center

Document name EWP1000/2000 Series Users Guide (6871009P12-A)

Enterprise WiFi Phone Service Manual (6802983C90-B)

NSM User Guide (part number 6871009P18-A)

Contacting Motorolas Enterprise Mobility Support Center

Contacting Motorolas Support Central Website

Contacting Motorolas Support Central Website

Device Country Approvals

TEAM 1.7 System Solution Overview and Planning Guide

Health and Safety Recommendations

Health and Safety Recommendations

Radio Frequency Interference Requirements - FCC

Radio Frequency Interference Requirements - Canada

Radio Frequency Interference Requirements - Canada

This page intentionally left blank.

Introduction to the TEAM Solution

Voice over IP (VoIP)

Chapter 1: System Overview

TEAM 1.7 System Solution Overview and Planning Guide

Benets of the TEAM Solution

Benets of the TEAM Solution

Architecture and Components

Chapter 1: System Overview

Architecture and Components

Introduction to the Architecture

TEAM 1.7 System Solution Overview and Planning Guide

Introduction to the Architecture

TEAM System Diagram

Chapter 1: System Overview

TEAM 1.7 System Solution Overview and Planning Guide

Enterprise Control Servers

Other Enterprise Servers

Chapter 1: System Overview

Motorola Integration Server

Other Enterprise Servers

TEAM 1.7 System Solution Overview and Planning Guide

Wireless LAN (WLAN)

Wireless LAN (WLAN)