Shoretel 13.1 Install Guide

ShoreTel 13.
1 Planning and Installation Guide

Part Number: 800-1685-01
Document and Software Copyrights

Copyright 1998-2013 by ShoreTel Inc., Sunnyvale, California, USA. All rights reserved. Printed in the United States of America. Contents of this publication may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without prior written authorization of ShoreTel, Inc. ShoreTel, Inc. reserves the right to make changes without notice to the specifications and materials contained herein and shall not be responsible for any damage (including consequential) caused by reliance on the materials presented, including, but not limited to typographical, arithmetic or listing errors.
Trademarks
ShoreTel, ShoreTel (and logo), Brilliantly Simple, Brilliantly Simple Communication, ShoreGear, ShorePhone, and ShoreWare are registered trademarks of ShoreTel, Inc. in the United States and/or other countries. The ShoreTel logo is a trademark of ShoreTel, Inc. in the United States and/or other countries. All other copyrights and trademarks herein are the property of their respective owners.
Patents
The ShoreTel System is covered by patents as listed at http://www.shoretel.com/about/patents.html.
Version Information
ShoreTel 13.1 Planning and Installation Guide Part Number: 800-1685-01 Version: PIG_13.1_20130117 Date: January 17, 2013
Company Information
ShoreTel, Inc. 960 Stewart Drive Sunnyvale, California 94085 USA +1.408.331.3300 +1.408.331.3333 (fax) www.shoretel.com
TABLE OF CONTENTS
PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 CHAPTER 1: GETTING STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.1 Assembling the Team. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
AND
CHAPTER 2: PLANNING
2.1 2.2 2.3
SYSTEM DESIGN . . . . . . . . . . . . . . . . . . . . . . 23
Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Network Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Determine System Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.3.6
2.4 2.5 2.6 2.7
Determine Number of ShoreTel Voice Switches . . . . . . . . . . . . . . . . . . . . . . . . 28 WAN Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 System Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.7.1 2.7.2 2.7.3 2.7.4 2.7.5
Sites and Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Headquarters and Distributed ShoreTel Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Citrix and Windows Terminal Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Teleworker Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Telephone Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Trunk Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Busy Hour Call Completion (BHCC) Call Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Busy Hour Call Attempts (BHCA) Call Volume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Call Load Capacity for Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Extension Monitoring Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 ShoreTel Voice Switch Feature Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
CHAPTER 3: NETWORK REQUIREMENTS AND PREPARATION . . . . . . . . . . . . 41

3.1 3.2
3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.2.7 3.2.8 3.2.9 3.2.10 3.2.11 3.2.12 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Understanding the Requirements for Toll-Quality Voice . . . . . . . . . . . . 42
3.3
WAN Technology Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Network Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Bandwidth Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Jitter for Voice Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Packet Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Bandwidth Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Distributed Call Control Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 Admission Control in the Wide Area Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 Spanning Tree Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 Traffic Shaping to Reduce Bottlenecks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 Echo Cancellation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 Resultant Voice Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Minimum Bandwidth Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Leased T1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 SDSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 IDSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 ADSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 3
ShoreTel 13.1
Planning and Installation Guide 3.3.7 3.3.8 3.3.9
Table of Contents
3.4 3.5 3.6 3.7 3.8
IP Address Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Configuring DHCP for ShoreTel IP Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Configuring Automatic VLAN Assignment through DHCP. . . . . . . . . . . 72 Time Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Virtual Private Network (VPN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.8.1 3.8.2 3.8.3 3.8.4
Cable Modems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 ISDN BRI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Dial-Up Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.9 3.10 3.11 3.12 3.13
3.10.1 3.10.2
Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Media Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Session Initiation Protocol (SIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Example Network Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Integrated Security Appliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Details: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Supported Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.12.1 3.12.2 3.13.1 3.13.2 3.13.3
Computing Admission Control Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Single-Site Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Multisite Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 WAN Bandwidth per Call (Full Duplex) Without cRTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 WAN Bandwidth per Call (Full Duplex) with cRTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Setting Admission Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
CHAPTER 4: ROUTING CALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

4.1 4.2 4.3 Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Direct All Calls to an Auto-Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.3.1 4.3.2 4.3.3
4.4
Direct All Calls to a Live Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

4.4.1 4.4.2 4.4.3 4.4.4 4.5.1 4.5.2 4.5.3
Trunk Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 After-Hours Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Example of Auto-Attendant Call Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.5
Direct All Calls to Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Trunk Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 After-Hours Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Example Using Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Example of Operator Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.6
Blended Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

4.6.1 4.6.2 4.6.3
Trunk Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 After-Hours Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Example of Direct Inward Dial Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Trunk Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 After-Hours Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Example of Blended Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
4.7
Analyze Outbound Call Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Table of Contents
Planning and Installation Guide
CHAPTER 5: TRUNK PLANNING AND ORDERING . . . . . . . . . . . . . . . . . . . . 97

5.1 5.2 Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Reviewing and Selecting Trunk Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.2.7 5.2.8 5.2.9 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.3.7 5.3.8 Analog Loop-Start Trunks (North America) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Analog Loop-Start Trunks (EMEA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Digital Loop-Start Trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 Analog Wink-Start Trunks (Analog DID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 Digital Wink-Start Trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 BRI Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 T1 PRI Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 E1 PRI Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 SIP Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 Caller ID Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Caller ID Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 Automatic Number Identification (ANI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 Direct Inward Dial (DID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 Dialed Number Identification Service (DNIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 Outbound Caller ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Tandem Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Tie Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
5.3
Understanding Trunk Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.4 5.5
Performing Traffic Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 Ordering Telephone Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

5.5.1 5.5.2 5.5.3 5.5.4 5.5.5
Analog Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 T1 Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 T1 PRI Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Ordering Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 E1 PRI Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
CHAPTER 6: DIALING PLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

6.1 6.2 6.3 6.4 6.5 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Define Digit Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Define Digit Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 On-Net Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Quick Reference of Star Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6.5.1 6.5.2 6.5.3 6.4.1 6.2.1 6.2.2 Configuring Internal Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Configuring External Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Common Star Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Extension Assignment Star Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Trunk Star Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
CHAPTER 7: NETWORK CALL ROUTING . . . . . . . . . . . . . . . . . . . . . . . . . 129

7.1 7.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 Define Network Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129
7.2.1 7.2.2 7.2.3 7.2.4 Call Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Account Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Trunk Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Specifying Parameters for the Routing Decision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
ShoreTel 13.1
Table of Contents
CHAPTER 8: PLANNING APPLICATIONS AND SERVICES . . . . . . . . . . . . . . . 135

8.1 Account Code Collection Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
8.1.1 8.1.2 8.1.3 8.1.4 8.1.5 8.1.6 8.1.7 8.1.8 8.1.9 8.1.10 8.1.11 8.2.1 Account Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Call Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Distributed Voice Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Escalation Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Auto-deletion of Voice Mail Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Mailbox Full Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 AMIS Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 SMDI Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Find Me Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Call Sender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Time Stamps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.10
Planning Fax Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Private Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148 Automated Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 Call Handling Delegation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 ShoreTel Communicator for Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 ShoreTel Communicator for Mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 ShoreTel Communicator for Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Bridged Call Appearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8.9.1 8.10.1 8.10.2 8.10.3
Using a Fax Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Switch Support for Bridged Call Appearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8.11 8.12 8.13
Pickup Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

8.12.1 8.12.2
Hunt Group Busy State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Configurable Hunting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Hunt Group Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
8.14
8.13.1 8.13.2 8.13.3 8.13.4 8.13.5 8.13.6
Enterprise Telephony Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Agent Multiplicity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Call Monitor and Barge In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
ShoreTel Enterprise Contact Center Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Music on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Overhead Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Multi-site Paging Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Night Bell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 Intercom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 Call Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
CHAPTER 9: TELEPHONE PLANNING AND ORDERING . . . . . . . . . . . . . . . . 165

9.1 9.2 Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Application Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
9.2.1 9.2.2 9.2.3 9.2.4 9.2.5 9.2.6 9.2.7 Operators, Receptionists, and Call Center Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Receptionists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 General Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Conference Rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Lobby Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Multi-line Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Teleworkers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Table of Contents
9.3
9.4 9.5
9.3.1 9.3.2 9.3.3 9.3.4 9.3.5 9.3.6 9.3.7 9.3.8 9.3.9 9.3.10 9.4.1
ShoreTel IP Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Analog Phone Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
ShoreTel IP Phone 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 ShoreTel IP Phone 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 ShoreTel IP Phone 212k. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168 ShoreTel IP Phone 230/230g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168 ShoreTel IP Phone 265 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 ShoreTel IP Phone 560 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 ShoreTel IP Phone 560g. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170 ShoreTel IP Phone 565g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 ShoreTel IP Phone 655 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 ShoreTel IP Phone BB24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Caller ID Standard Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
9.5.1 9.5.2
Fax Machines and Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Fax Machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
CHAPTER 10: SERVER REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . 179

10.1 10.2 General Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Requirements for ShoreTel Enterprise Systems . . . . . . . . . . . . . . . . . . . . . . . 179
10.2.1 10.2.2 10.2.3 10.3.1 10.3.2 10.3.3 Capacity and Hardware Requirements for Headquarters Servers . . . . . . . . . . . . . . . . . . . .180 Capacity and Hardware Requirements for Distributed Voice Servers . . . . . . . . . . . . . . . 181 Operating System Requirements for All Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
10.3
ShoreTel SBE System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
10.4
Requirements for VMware Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

10.4.1 10.4.2 10.4.3 10.4.4
Summary of SBE Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Capacity for Small Business Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184 SBE Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 ShoreTel Capacity in VMware Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Hardware Requirements for VMware Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186 Operating System Requirements for VMware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186 VMware Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186
10.5 10.6
10.7
10.6.1 10.6.2 10.6.3
Double-Take Availability Software for Failover . . . . . . . . . . . . . . . . . . . . . . 187 Hard Disk Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
10.8 10.9
10.7.1 10.7.2 10.7.3 10.7.4 10.7.5
Preparing Your Server for the ShoreTel Installation . . . . . . . . . . . . . . . . . . 189
Voicemail Utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188 Call Detail Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188 Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
ShoreTel Mobility Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Third-Party Applications Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Server IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Workgroup Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 DHCP on the ShoreTel Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Windows Server 2008 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189 Additional Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
ShoreTel 13.1
Table of Contents
CHAPTER 11: SHORETEL SERVER INSTALLATION . . . . . . . . . . . . . . . . . . . 199

11.1 11.2 11.3 11.4 11.5 11.6
11.1.1
Checking Server for Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
11.2.1 11.2.2 11.3.1 11.3.2
Installing the Headquarters Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . 200
Running the Compatibility Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Installing the Distributed Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Upgrading the Headquarters Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 Installing the Headquarters Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Upgrading the Distributed Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Installing the Distributed Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
11.5.1 11.5.2
Verifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Installing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212 Upgrading the Server Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Obtaining Conference License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212 Installing the License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
11.6.1 11.6.2 11.6.3
11.7
11.6.4 11.6.5 11.7.1
Ensuring Proper Server Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
Preparing to Upgrade from Windows 2003 to Windows 2008 R2 (64-bit). . . . . . . . . . 213 Upgrading the Uboot Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214 Upgrading Servers from Windows 2003 (32-bit) to Windows 2008 (32-bit or 64-bit R2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Upgrading Servers from Windows 2008 (32-bit) to Windows 2008 R2 (64-bit). . . .218 Upgrading the System to New Hardware (Same OS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Setting the Server to Maximize for Network Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
CHAPTER 12: SITE REQUIREMENTS AND PREPARATION . . . . . . . . . . . . . . 223

12.1 12.2
12.1.1
Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Voice Switch Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Switch Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Physical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Input Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Power and Heat Dissipation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Reliability and Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Memory and Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
12.3
12.2.1 12.2.2 12.2.3 12.2.4 12.2.5 12.2.6 12.2.7 12.3.1 12.3.2
Racks and Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
General Cabling Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Rack Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
CHAPTER 13: INSTALLING SHORETEL VOICE SWITCHES . . . . . . . . . . . . . . 233

13.1 13.2 13.3 13.4 13.5 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Mounting the ShoreTel Voice Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Installing ShoreTel Voice Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
13.3.1
13.5.1 13.5.2 13.5.3 13.5.4 13.5.5
ShoreTel Director Switch Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
RJ-21X Cable Retainer Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235
Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235 Packaging Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235 Regulatory Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237 General Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237
Table of Contents
CHAPTER 14: IP PHONE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . 239

14.1 14.2
14.2.1 14.2.2 14.2.3 14.2.4 14.3.1 14.3.2 14.3.3 14.3.4 14.4.1
Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Preparing Your ShoreTel System for IP Phones . . . . . . . . . . . . . . . . . . . . . . . 239
14.3
Installing a ShoreTel IP Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Configuring Voice Switches for IP Phone Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Configuring Teleworker IP Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Assigning the Configuration Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Setting IP Address Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241 Boot Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 802.1x Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 DHCP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Manually Configuring the ShoreTel IP Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Resetting a ShoreTel IP Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
14.4 14.5
Displaying ShoreTel IP Phone Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Associating a User Group with Unassigned IP Phones . . . . . . . . . . . . . . . 246
CHAPTER 15: DESKTOP REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . 247

15.1 15.2 15.3 Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
15.3.1 15.3.2 15.3.3 15.3.4 Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 .NET Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 ShoreTel Communicator for Web Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Microsoft Outlook Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
CHAPTER 16: DESKTOP INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . 253

16.1 16.2 16.3 Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Notifying Users via Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
16.4
16.3.1 16.3.2 16.3.3 16.3.4 16.3.5 16.3.6 16.3.7 16.3.8
16.5 16.6
Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 User Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

16.6.1 16.6.2 16.6.3
16.4.1 16.4.2 16.4.3
Installing Outlook Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Silent Client Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255 Prerequisites for ShoreTel Communicator Installation in a Large Deployment . . . . .256 Standard Integrated Software Distribution Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257 Installing ShoreTel Communicator on a Windows PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257 Installing ShoreTel Communicator on a Mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Configure the TAPI Dialing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Starting the ShoreTel Communicator Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Installing Voice Mail Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Activating the Integration of Voice Mail with Microsoft Outlook. . . . . . . . . . . . . . . . . . . 269 Memorized Phone Number Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Purchasing User Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Language Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 License Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
ShoreTel 13.1
Table of Contents
CHAPTER 17: SHORETEL INTEGRATION WITH EXTERNAL APPLICATIONS . . . 275

17.1 17.2
17.1.1
Importing Public Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
17.2.1 17.2.2
Installing the ShoreTel Telephony Interface (STI) . . . . . . . . . . . . . . . . . . . 277
Creating a CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277
CHAPTER 18: LEGACY INTEGRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

18.1 18.2 18.3 18.4 18.5 18.6 18.7 18.8 18.9 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Coordinated Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Trunk Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Coordinated Dialing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 PSTN Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Multi-Site Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Single Site Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Consolidated Long Distance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Voice Mail Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
18.10 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 18.11 Connection Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
18.9.1 18.9.2 18.9.3 18.9.4
AMIS Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 SMDI Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Configuring Legacy Voice Mail Integration Using SMDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Configuring ShoreTel Voice Mail Integration Using SMDI. . . . . . . . . . . . . . . . . . . . . . . . . . . 293
18.12 Administration and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
18.11.1 Special Considerations - Nortel PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 18.11.2 Special Considerations - Avaya/Lucent PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301 18.12.1 Tie Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301 18.12.2 Services Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301
18.13 Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
CHAPTER 19: CUT-OVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

19.1
19.1.1 19.1.2 19.1.3
Cut-Over Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
19.2
19.3
19.2.1 19.2.2 19.2.3 19.2.4
Cut-Over Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Basic Cut-Over Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trunking Cut-Over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cut-Over of Remaining Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cut-Over Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cut-Over Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 New Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Cut-Over Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 306 306 307 307
Cut-Over Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
10
Table of Contents
APPENDIX A: INTERNATIONAL PLANNING

A.1 A.2 A.3 A.4
AND INSTALLATION
311
Software and Feature Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Language Packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Analog Telephones, Tones, Cadences, and Impedances. . . . . . . . . . . . . . .314 Dialing Plan Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314
A.4.1 A.4.2 A.4.3 A.4.4 A.4.5
A.5
Carrier Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Single-Extension Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314 Trunk Access Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314 Operator Digit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314 Emergency Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314 DID Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
APPENDIX B: REGULATORY AND SAFETY INFORMATION

B.1 B.2
B.2.1 B.2.2 B.2.3 B.2.4 B.2.5 B.3.1 B.3.2
317
Agency Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 EMC Compliance Statements (SG-8/12/24 and T1) . . . . . . . . . . . . . . . . . . . . 318
B.3
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
United States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 European Union. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Restricted Access Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 WEEE Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Important Safety Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Electrical Safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
APPENDIX C: INSTALLING COMMUNICATOR ON CITRIX XENAPP AND WINDOWS TERMINAL SERVERS

C.1 C.2 C.3 C.4
C.1.1 C.1.2
321
XenApp Support Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
C.2.1
WTS Support Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Citrix XenApp Environment Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Citrix XenApp Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
C.3.1 C.3.2
Installing ShoreTel Communicator on Citrix XenApp or WTS. . . . . 323
WTS Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Preliminary Steps for Upgrading ShoreTel Communicator on 64-bit Platforms. . . 323 Installing ShoreTel Communicator for Windows on a Terminal Server. . . . . . . . . . . . 323
Using Third-Party Applications with ShoreTel Communicator on a Citrix Terminal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
C.4.1
Installing ShoreTel Telephony Interface (STI) on a Citrix Terminal Server . . . . . . . . 324
APPENDIX D: SESSION INITIATION PROTOCOL

D.1 D.2
D.2.1 D.2.2 D.2.3 D.2.4 D.2.5
327
328 328 328 328 329
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 General SIP Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DTMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Foreign Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Feature Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ShoreTel 13.1
11
Table of Contents
APPENDIX E: REVERSE PROXY SERVERS FOR SHORETEL COMMUNICATOR ON IPHONE 331

E.1 E.2 E.3 Reverse Proxy Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Example Reverse Proxy Configuration for Apache 2.2 On a Linux Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Example Reverse Proxy Configuration for Apache 2.2 On a Microsoft Windows Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
E.3.1 E.3.2 E.3.3
Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337 About the Security Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337 Example Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339
APPENDIX F: SHORETEL VOICE SWITCHES

F.1
F.1.1 F.1.2 F.1.3 F.1.4
345
Switch Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
F.2
F.3
Specifications SG Voice Model Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

F.3.1 F.3.2 F.3.3
F.2.1 F.2.2 F.2.3 F.2.4 F.2.5 F.2.6 F.2.7 F.2.8 F.2.9 F.2.10
Specifications SG 1-U Half-Width Switches . . . . . . . . . . . . . . . . . . . . . . . . . 348
ShoreTel 1-U Half Width Voice Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 ShoreTel Voicemail Model Voice Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 ShoreTel 1-U Full Width Voice Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 ShoreTel IPBX Voice Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 ShoreTel 90 Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 ShoreTel 90BRI Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 ShoreTel 50 Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355 ShoreTel 30 Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .358 ShoreTel 30BRI Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 ShoreTel 220T1 Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365 ShoreTel 220T1A Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 ShoreTel-220E1 Voice Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372 ShoreTel T1k Voice Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .375 ShoreTel E1k Voice Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378
F.4
Specification SG 1U Full Width Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

F.4.1 F.4.2 F.4.3 F.4.4
ShoreTel 90V Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 ShoreTel 90BRIV Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385 ShoreTel 50V Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 ShoreTel 120 Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 ShoreTel 24A Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .396 ShoreTel 60 Voice Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .399 ShoreTel-T1 and ShoreTel E1 Voice Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
12
Preface
This preface provides information about the objectives, organization, and conventions of the ShoreTel Planning and Installation Guide.
Objectives
This document provides planning and installation information for the ShoreTel system and components.
Audience
This guide is written for the person who plans, installs, administers, and maintains the ShoreTel system. This individual should be knowledgeable about data networking and telephony to use this guide effectively.
Organization
This document is generally organized into major tasks, presented in the order in which they should be completed.
Documentation Overview
The ShoreTel system is documented as described in the following sections.
System Documentation
The ShoreTel Planning and Installation Guide (this guide) is in the documentation folder on the ShoreTel DVD. In addition, and ShoreTel Director has a link to this guide. This guide provides information on how to plan the implementation of the ShoreTel system, as well as how to install the necessary hardware, data communications, and telecommunications elements. The ShoreTel Planning and Installation Guide can be used in conjunction with the ShoreCare project management tool.
Software Documentation
The ShoreTel System Administration Guide provides detailed reference information (both task-based and screen-by-screen) on how to administer and maintain the ShoreTel system using ShoreTel Director. If you are installing one or more ShoreTel Server Appliances, refer to the ShoreTel Conferencing & Instant Messaging Planning and Installation Guide for complete installation and configuration information. Both guides can be found in the documentation folder on the DVD.
ShoreTel 13.1
13
The following release notes can be found in the documentation folder on the associated DVD and may also be accessed from ShoreTel Director: ShoreTel Release Notes provide information about new releases, new features, installation, and upgrading for the ShoreTel server.
Hardware Documentation
The following hardware installation documents are packaged with their associated ShoreTel voice switch, Service Appliance, or ShoreTel IP phone: ShoreGear Voice Switch Quick Install Guide ShoreTel Conferencing & Instant Messaging Planning and Installation Guide ShoreTel IP Phone Quick Install Guide
User Documentation
End-user documentation is installed during the ShoreTel Communicator installation. It is available through the Help > Contents and Index command within the ShoreTel Communicator application. Analog Phone Quick Reference, which is available in the telephone user interface IP Phone Quick Reference, which is available in the telephone user interface
Release Notes
The ShoreTel Release Notes provide information about new releases and new features as well as installation and upgrade information. They can be found in the documentation folder on the associated DVD and can also be accessed from ShoreTel Director.
Online Knowledge Base

To access additional information about the current release or to resolve issues with the ShoreTel system, you can use the ShoreTel online knowledge base. This password-protected, online database is accessible to authorized contacts through the ShoreTel web site at www.ShoreTel.com.
Document Conventions
Conventions used in this guide include the following: Data-entry field names, hypertext links, control buttons, keywords, and other items within the system management interface are in boldface text. Information that you enter in data-entry fields is in a data_entry font.
14
Chapter 1
Getting Started
This document describes how to plan and install a ShoreTel system. Each chapter in this document begins with recommendations that help with the transition to a ShoreTel system. For an installation outside the U.S., see International Planning and Installation on page 311.
1.1
Assembling the Team

To deploy a ShoreTel system, the members of the team might include some or all of the type of support sources:
System Designer: The system designer determines the number of telephones,

number and type of trunks, and the call flow that the customer needs in the network. communicates important decisions to the entire team. The project manager usually is an IT manager.
Project Manager: The project manager oversees the entire project and
IT Manager: The IT department needs to give its full support and cooperation. Electrician: An electrician might be necessary for installing new power
outlets and cooling and ventilation systems. The building that has the ShoreTel system must be able to provide enough power to the system. for local and long-distance telephone service is necessary. The phone company or Internet service provider and the customer must have a clear understanding of the technical requirements and characteristics that exist on both sides of the network boundary. implementation. This possibility likely depends on the complexity of the network and support package that the customer purchased.
Service Providers: An effective relationship with a telephone service provider
ShoreTel: A certified ShoreTel partner might be necessary for the
ShoreTel 13.1
15
Chapter 1: Getting Started
Phase 1: Voice Communications System Analysis and Ordering

Task Download and modify the Microsoft Project installation schedule included in Resources Complete Call Flow Analysis Inventory and determine trunk requirements Order new trunk lines Trunk installation date Inventory your existing telephone equipment Order new phones and/or headsets Review your need for a ShoreTel Server Appliance Order a ShoreTel Server Appliance Review the need for a ShoreTel Enterprise Contact Center Solution Order a ShoreTel Enterprise Contact Center Solution Order ShoreTel voice switches ShoreTel shipping date Date Completed
16
Phase 2: Environmental and Infrastructure Analysis and Upgrade

Task Participate in the Phase 2 conference call Read ShoreTel's power requirements Order power upgrades (as necessary) Scheduled power upgrade completion date Read ShoreTel's racking requirements Racking installation date (if racking is ordered) Read ShoreTel's ventilation requirements Ventilation system upgrade completion date (if ordered) Read ShoreTel's recommendations for uninterruptable power source (UPS) UPS installation date (if ordered) Read ShoreTel's cabling requirements Cabling installation date (if ordered) Determine the overhead paging needs Source your Music on Hold needs Read ShoreTel's LAN requirements Attach LAN topology map LAN installation date (if ordered) Read ShoreTel's WAN requirements Attach WAN topology map WAN upgrade installation date (if ordered) Read ShoreTel's server requirements Order your server for the ShoreTel System Server installation date Read ShoreTel's desktop requirements Desktop software upgrade installation date (if required or ordered) ShoreTel scheduled installation date Date Completed
ShoreTel 13.1
17
Phase 3: Resource Scheduling and Tracking

Task Participate in the Phase 3 conference call Verify Telco order is on schedule Verify phone order is on schedule Verify power order is on schedule Verify racking order is on schedule Verify ventilation order is on schedule Verify uninterruptable power source (UPS) order is on schedule Verify cabling order is on schedule Verify LAN upgrade order is on schedule Verify WAN upgrade order is on schedule Verify desktop upgrade order is on schedule Verify ShoreTel order is on schedule Read ShoreTels descriptions of the different ShoreTel Communicator applications Schedule your System Administration training with ShoreTel Order new business cards and business stationary if your phone numbers are changing Verify that you have obtain all licenses and license keys for your planned installation. Date Completed
18
Phase 4: System Load and Configuration

Task Participate in the Phase 4 conference call Verify receipt of ShoreTel equipment Reserve IP addresses for your network Configure server with the appropriate server operating system Load the ShoreTel software Enter the database configuration for ShoreTel Confirm your ShoreTel System installation and cut-over dates Confirm installation and cut-over coverage Verify racking is complete Verify power is in compliance Verify UPS is installed Verify cabling is complete Verify ventilation upgrade is complete Verify new phones and headsets have been delivered Verify your System Administrators have been trained Schedule training for your Operators and Workgroup(s) Date Completed
ShoreTel 13.1
19
Phase 5: Installation Readiness Review

Task Participate in the Phase 5 conference call Upgrade desktops, if necessary, and ensure readiness for Client software installation Notify users of the ShoreTel system implementation Verify telephone trunk lines are installed and tested Verify server appliance is installed Configure on-hour and off-hour schedules for Auto-Attendant menus and Workgroups Configure your Workgroups Configure your Auto-Attendant menus Script and record all Auto-Attendant and department voice mail greetings Date Completed
20
Phase 6: Cut-Over
Task Participate in the Phase 6 conference call Complete your Cutover Review Checklist Send web-based training modules to end users Send TUI guides to end users Verify that operators are trained Verify that workgroups are trained Verify that all phones have been placed and extensions tested Verify that existing trunk lines have been swapped and tested Verify that end users have been sent the ShoreTel client notification Cut-over to the ShoreTel system Complete your Post Cut-over Survey Review ShoreTel Web Center to understand the available ShoreTel support resources Date Completed
ShoreTel 13.1
21
22
Chapter 2
Planning and System Design

This chapter describes the initial design of the ShoreTel system. The topics are:
Recommendations on page 23 Network Assessment on page 23 Determine System Topology on page 24 Determine Number of ShoreTel Voice Switches on page 28 WAN Connections on page 30 Failover on page 30
2.1
Recommendations
The following recommendations will assist you in designing your new voice communications system.
Make sure you understand all the unique routing and hunting requirements of
your current system.
Be sure to account for all devices, including conference rooms, lobby phones,
fax machines, and modems.
Make sure you consider the changes to the call flow and overall system design
that may drive the need for additional trunks.
2.2
Network Assessment
As you plan your phone system, ShoreTel recommends that you have a network assessment performed. A network assessment does the following:
Ensure necessary protocols and standards are supported Confirm that the infrastructure is optimally configured for IP telephony traffic Verify that the installed WAN technologies are compatible with IP telephony. Measure delay, packet loss and jitter to ensure that they meed acceptable
thresholds for toll-quality voice calls
x for Wi-Fi.
ShoreTel 13.1
23
Chapter 2: Planning and System Design
To complete your system design, the final step is to identify your network connectivity. You should identify the following for the network connections to each site:
Bandwidth Latency Jitter Packet Loss
2.3
Determine System Topology

The ShoreTel system has a unique distributed call control software architecture that enables you to deploy ShoreTel voice switches and IP phones anywhere across your IP network. Even though multiple sites are supported, the ShoreTel system is a single system with an extensive set of integrated applications and a single management image. The ShoreTel system offers unmatched simplicity through this single image system, and delivers high availability, with no single point of failure, through its distributed architecture. The first step in planning a voice network is to determine the overall network topology. Topology information includes the following:
Sites and Users. Number of sites and number of users at each site. Headquarters and Distributed ShoreTel Servers. Number of servers
required, plus the name or IP address of all ShoreTel servers (main and distributed). telephones supported.
Teleworker Sites. Number of teleworker installations and the type of Telephone Requirements. Number of telephones at each site (by type). Trunk Requirements. Number of trunks required for optimal performance. ShoreTel Voice Switches. What models are needed and how many of each
model. service-level information. See "Network Requirements and Preparation" on page 41, for detailed information on planning your network for the ShoreTel system.
WAN Connections. The number of WAN connections (per site) and complete
2.3.1
Sites and Users

Your network topology diagram should provide an accurate inventory of the different physical sites and the number of users at each site.
24
2.3.2
Headquarters and Distributed ShoreTel Servers

The Headquarters ShoreTel server hosts the voice applications platform and the management web site, as well as the integrated voice applications. Typically, the Headquarters ShoreTel server is located at the largest location, containing the majority of users. Make special note of the main ShoreTel server on your topology diagram.
ShoreTel 13.1
25
On your topology diagram, provide the following information about ShoreTel servers:
Total number of servers (i.e. sum of servers at all sites). Number of servers at each site. The name and IP address of every server.
The ShoreTel system also supports Distributed Voice Servers (DVS) to allow distributing voicemail and other applications. Distributed servers help accomplish the following:
Reduce bandwidth, because local users calls to voice mail are answered by the
local voice mail application and do not go across the WAN. control services to additional users of the applications.
Increase system scale by extending the unified messaging and desktop call
applications if a site loses connectivity with the Headquarters server. Even though there are multiple servers, the ShoreTel system provides a single image system across your entire network. The system is currently certified to support up to 21 servers, one at the headquarters site and up to 20 distributed servers. You should add a server at any site that exceeds 100 users. You must deploy a server for every 1,000 users. The distributed voice applications platform can also provide an open applications platform for extending telephone services through TAPI-compliant third-party applications. A dedicated distributed server is required to host the third-party applications. This server is deployed like other distributed servers, except that it must not have voice mail users assigned to it. The distributed voice application servers Remote TAPI Service Provider relies on the call control information from the main server. To add reliability to your remote server, consider using redundant network paths to the main server.
Increase reliability by providing local support for some services and
2.3.3
Citrix and Windows Terminal Server

Citrix and Windows Terminal Server (WTS) technologies enable processing for multiple users to be aggregated on a single Windows computer. The single Windows computer is a process- and disk-sharing server for multiple users who have lightweight or thin graphics stations on their desktop. Citrix communicates between the server and clients using the ICA protocol, whereas Windows Terminal Server uses the RDP protocol. For more information on configuring ShoreTel Communicator clients on Citrix and WTS, see "Installing Communicator on Citrix XenApp and Windows Terminal Servers" on page 321.
2.3.4
Teleworker Sites
ShoreTel IP Phones can operate away from the ShoreTel site. For example, employees (telecommuters) can have an IP phone at their home so that they can work from home. The ShoreTel topology diagram must include the number and location of offsite IP phones. For information on configuring ShoreTel IP phones for teleworkers, see "IP Phone Installation" on page 239.
26
2.3.5
Telephone Requirements
This section describes how to determine the telephone requirements, as follows. Step 1 Count the telephone users in the current environment. Include conference room telephones, lobby telephones, and telephones that multiple users share. Step 2 Count the number of ShoreTel BB24 button boxes that operators and receptionists need. The maximum number of BB24s on a multi-line phone is four. Step 3 Count the number of ports that fax machines and modems will use. Step 4 If you are deploying IP phones, determine the number of telephones that will be IP phones and the number that will be analog phones. Some users might need specialized features. For example, an operator needs a phone with programmable buttons. Therefore, consider the type of functions that each user needs to select the appropriate phone for each user. Step 5 Consider the needs for additional telephone ports for third-party systems, including server appliances and overhead paging systems. See Telephone Planning and Ordering on page 165, for more information about selecting telephones. Step 6 Determine the number of user licenses you need. Each user on the system requires a user access license. The types of user licenses are listed below:
Extension and mailbox: Purchase of this license entitles the user to be

assigned to both a physical extension and a ShoreTel voice mailbox.
Extension-only: This license lets the user have a physical extension
through an explicit assignment or through the Extension Assignment feature. NOTE An Extension-only license is a requirement for each conference room telephone, lobby telephone, fax machine, and modem. A user access license is not necessary for trunks and anonymous telephones.
Mailbox-only: This license lets the user have only a ShoreTel voice
mailbox.
Audio conference: Purchase this license for each audio port that you want
to use in conferences managed by the ShoreTel Service Appliance. A license allows one audio endpoint to participate in a conference.
Web conference: Purchase this license for each Web port that you want to
use in conferences managed by the ShoreTel Service Appliance. A license allows one data-compatible endpoint to participate in a conference
2.3.6
Trunk Requirements
Trunks provide connectivity between users on the ShoreTel system and the public switched telephone network (PSTN). In this next task in the system design process, you determine the number of trunks required.
ShoreTel 13.1
27
The number of trunks required on your system varies, depending on the number of users and your specific application needs. It is important to size your trunking correctly because not having enough trunks can lead to blocked calls when all trunks are busy, and too many trunks can lead to wasted money on monthly access charges. See Telephone Planning and Ordering on page 165, for more information about trunk features, ordering, and installation. You have several options for determining the number of trunks your site requires:
Review the number of trunks on your current system. In general, this is one of
the best methods to gauge the number of trunks you need.
You can also request a traffic analysis from your service provider, interconnect,
or telecom manager to understand your current trunk utilization. This method will help you understand your current usage and allow you to maintain the current service level. your trunk requirements.
Visit a web site, such as www.erlang.com, to use a traffic calculator for determining Consider the following:
Larger locations can typically use lower-density trunking (15%). Smaller locations need higher-density trunking (50%). Some applications, such as call centers, can demand higher-density trunking (50%). Table 2-1 Trunk Density Low Average High Trunk Density Trunks/ Users% 15% 30% 50%
When planning trunks, consider the call volume for your workgroups or ACD groups. Since there is generally a queuing solution in place for ACD calls, the number of trunks required should be based on the full utilization of the expected number of agents and sufficient trunks for the expected number of waiting callers.
2.4
Determine Number of ShoreTel Voice Switches

The ShoreTel telephony solution is a mixture of hardware and software components that you install across your enterprise to create a single telephone system. A critical component to the solution is the ShoreTel voice switch. Voice switches are the interface that connect the telephones to the ShoreTel system. These switches provide signaling and call-setup functions for the phones and trunking to interface with service providers and other telephony networks. The ShoreTel voice-switch portfolio offers a broad range of telephony switches to meet the needs of our different customers. "ShoreTel Voice Switches" on page 345 provides more information about all of the ShoreTel voice switches.
28
See "International Planning and Installation" on page 311 for information about the ShoreTel Voice Switches and features that we support outside the U.S.
ShoreTel 13.1
29
2.5
WAN Connections
To complete your system design, the final step is to identify your network connectivity. You should identify the following for the network connections to each site:
Bandwidth Latency Jitter Packet Loss
2.6
Failover
To provide high availability, ShoreTel supports failover at two very important points in the system. ShoreTel supports failover for the headquarters (HQ) server and for voice switches. For the headquarters server, ShoreTel supports a back-up server that monitors and can duplicate the primary server. If the primary server fails, the back-up server immediately starts operating as the headquarters server with minimal interruption. After the primary server returns to operation, the system administration must perform a manual fail-back to restore the servers to their previous operation. For voice switch backup, ShoreTel supports two approaches. The system administrator can configure extra port capacity or install a dedicated spare voice switch. A spare voice switch be on a network that is remote to the failed voice switch.
2.7
System Capacity
The ShoreTel Release 12 system can scale incrementally up to 20,000 ports (users and trunks) representing 500 ShoreTel voice switches over the entire system. The system is completely nonblocking and can support 10,000 simultaneous calls at a rate of 100,000 calls per hour depending upon server configurations. Table 2-2 provides a summary of the ShoreTel system capacity. Table 2-2 Component System Sites Switches 500 100/site 500/ system 100/ server 300/ server 5,000 Exact number varies by configuration. Exact number varies by configuration. ShoreTel System Capacity Capacity Notes
Route Points Analog Ports
This is per server Exact number varies by configuration.
30
Table 2-2 Component IP Phones
ShoreTel System Capacity (Continued) Capacity Notes 20,000 (max) 10,000 100,000 Exact number varies by configuration. See Server capacity table. 10,000 calling 10,000. Depending upon server configurations
Simultaneous Calls Busy Hour Call Completion Users Users Port Based Users IP Phone Users Virtual Users User Groups Call Permissions Trunks Trunks Trunk Groups Servers Number of servers
20,000 5,000 20,000 1,000/ server 250 100
Telephony Permissions 100 Voice Mail Permissions 100 10,000 500
Number of Trunks/TG 500 21 1 main, 20 distributed (for voice mail, autoattendant, messaging, directory, configuration services, and desktop call control). Each server is certified to support up to 1,000 users.
Number of Voicemail Box Switches (VMBs)
500/ system 100/ server
Number of 3rd Party SIP Servers Media streams (G.711 per server) Media streams (G.729 per server) Media streams (total) Voice Mail Mailboxes (total)
ShoreTel 13.1
20 254 40 9,384 21 servers x 254 media streams per server + 500VMB x 9 streams per VMB. These can be distributed across the servers.
31
Simultaneous voice mail sessions, for example.
20,000
Table 2-2 Component
ShoreTel System Capacity (Continued) Capacity Notes 3,000 Unlimited Restricted by the size of disk available (1 hour of voice mail per 30 MB of disk storage). 1,000 Every server has every menu.
Mailboxes (per server) Storage Auto-Attendant Menus (total) Hunt Groups
Hunt groups per switch 8 Total hunt group members per switch Workgroups Workgroups (total) Members per workgroup WG Agents (total per system) WG Agents Calls in Queue per Queue 256/ system 300 300/ system 16 254/ server Top down, round robin, and longest idle hunt pattern. If more are required it is recommended you investigate the ShoreTel Enterprise Contact Center Solution Simultaneous ring. Overflow is directed to the workgroup backup extension. 16
BHCC/system without Very See Server HW specs for size & traffic reports during business Large considerations hrs HW=100k /Large HW = 50K / Med HW =2 5K /Small HW = 5K BHCC/system with Very See Server HW specs for size & traffic reports during business Large considerations hrs HW=10k /Large HW = 5K / Med HW = 1K / Small HW = not recomme nded Max # of PCM's in WG server
32
300
Table 2-2 Component Paging Groups
ShoreTel System Capacity (Continued) Capacity Notes 300/ system
Paging Groups (total)
Paging Group Members 300/ system Max # of simultaneous 100/ pages server Account Code Account Code (per system) Call Detail Record Storage 1.5 GB (MySQL has a capacity of 64TB) 500,000 workgroup calls, OR 1.5 million extension-to-extension calls, OR 1.0 million combined call records Implementing a database of this size typically requires 4.0 GB of disk space, including disk space for the main database (1.5 GB), the archive database (1.5 GB), and temporary space required to generate reports (1.0 GB). 100,000/ system)
ShoreTel Communicator ShoreTel 10,000 Communicators (total) ShoreTel Communicators (per server) Personal Professional Workgroup Agent Workgroup Agent/ server 1,000
10,000 10,000 300 300 per server, 300 per system 128 per server, 128 per system 200 250 monitored extensions/each operator maximum.
Workgroup Supervisor 128
Workgroup Supervisor/server
Operator
ShoreTel 13.1
33
Table 2-2 Component
ShoreTel System Capacity (Continued) Capacity Notes 1,000 Per system.
ShoreTel Communicator for Mobile Music on Hold (MOH) Music on Hold (MOH) Programmable Buttons IP phone buttons configured for extension monitoring (per switch) Phones that can monitor an extension Voice Switch Capacity Media streams/switch (No encryption) Media streams/switch (encryption) Media streams/switch (SRTP) Media streams/switch (SRTP + authentication) G711 Limits for VMB G729 Limits for VMB
15
One switch can provide MOH for up to 15 switches per site.
1024
32
60 60 40 30
9 5
BAA Simultaneous # of 60 calls - Voice Switches Simultaneous # of calls 60 SIP Ringing - Voice Switches -G711 Simultaneous # of calls 0 SIP Ringing - Voice Switches -G729 The following tables contain information on how to select a server for your ShoreTel implementation. Server requirements are specified in four tiers:

34
Servers for small systems that support up to 500 users. Servers for medium sized systems that support up to 2,500 users. Servers for large systems that support up to 10,000 users. Servers for very large systems that support up to 20,000 users.
Table 2-3 describes the key capacity limits for each of the new server tiers.
ShoreTel 13.1
35
Table 2-3
System and Service Capacities Maximum number Maximum of users System BHCC1 assigned per Server 500 1,000 1,000 1,000 5,000 25,000 50,000 100,000 Maximum BHCC per server2 Reports run outside business hours 1,000 5,000 10,000 10,000 Maximum BHCC per server2 Reports run during
business hours
Size
Maximum number of users per System 500
Small
Not Recommended3 1,000 5,000 10,000
Medium 2,500 Large Very Large 10,000 20,000
NOTE: Busy Hour Call Completion (BHCC) includes all traffic that can occur in that server - regular voice calls, workgroup calls, voicemail etc. 1 BHCC (Busy Hour Call Completion) per system is the total number of calls in the system during the busy hour including internal and external calls and including calls terminated to desk phones, softphones, trunks, or server applications such as voicemail. during the business hour including workgroup calls in menus and queues, autoattendant calls and calls to the voicemail service.
3 The ShoreTel report generation tools that run on the server are configured by 2 BHCC per server is based on the number of calls actually handled by the server
default to run at a lower priority than other, more critical services. A light demand of report generation should have little or no affect on a server with adequate minimum performance specifications. If you are a heavy report user or experience any degradation of voicemail or other server prompts on an underpowered server, you must move up to the next tier level of servers. To select a server for your new system deployment, first consult the sizing table and determine the tier of the server needed using the system and per server specifications. Then match that size (small, medium, large or very large) to the server requirements shown in Table 2-4. Table 2-4 Size Small Server Specifications RAM Network 100 Base-T
Processor
Intel Core 2 Duo E8400, Single Dual 4 GB Core 3.00 GHz or Intel Core i3540 Processor (4M Cache, 3.06 GHz) Intel Xeon 5520 Single Quad Core 2.27 GHz Intel Xeon 5520 Dual Quad Core 2.27 GHz Intel Xeon 5680 Dual Six Core 3.33 GHz 8 GB
Medium
100 Base-T or Gigabit Ethernet Gigabit Ethernet Gigabit Ethernet
Large Very Large

36
8 GB 12GB
NOTE: The new hardware specifications are to be used to size servers running ShoreTel's Headquarters server software as well as ShoreTel's Distributed Voice Services software. For example, consider a 2 location system with 2,000 users and 20,000 BHCC. A Headquarters server is located at the main site and a Distributed Voice Services server is located at the remote site. Each of the servers handle 2,000 BHCC. In this case, both servers should be provisioned with hardware that meets the medium tier of hardware requirements because the system capacity and both server capacities fall within this tier. When deploying servers for medium or large systems, please note that you must select an operating system with support for expanded memory by using the Enterprise Editions of either Microsoft Windows 2003 server or Microsoft Windows 2008 Server.
2.7.1
Busy Hour Call Completion (BHCC) Call Volume

Busy Hour Call Completion (BHCC) per system is the total number of calls in the system during the busy hour including internal and external calls and calls terminated to desk phones, softphones, trunks, or server applications such as voicemail. This includes all traffic that can occur in the server - regular voice calls, workgroup calls, voicemail etc. See Table 2-3 on page 36 for information about BHCC capacity for the different sizes of ShoreTel systems.
2.7.2
Busy Hour Call Attempts (BHCA) Call Volume

Busy Hour Call Attempts (BHCA) is the number of calls attempted at the busiest hour of the day (peak hour). The higher the BHCA, the higher the stress on the network processors. If a bottleneck in the network exists with a capacity lower than the estimated BHCA, then congestion will occur resulting in many failed calls and customer dissatisfaction. ShoreTel systems support 5,000 BHCA.
2.7.3
Call Load Capacity for Switches

A ShoreTel system supports a maximum of 100 Voicemail Model Switches. There are no restrictions concerning the allocation of switches among the sites defined by the system. For ShoreTel Voicemail Model Switches, call load capacity is:
5400 BHCC when supporting 90 MGCP IP Phones or 90 SIP Trunks. 3600 BHCC when supporting 90 SIP IP Phones or 90 SIP Trunks.
2.7.4
Extension Monitoring Limitations

That there is a limit to the number of extensions that can be monitored, whether from a ShoreTel IP Phone -BB24 device or from a ShoreTel IP Phone multiline phone. This limitation is dependent on two factors:
Update rate (every call causes one or more monitoring phones to be updated. Whether the monitoring phones are spread across one or more switches.
ShoreTel Voice Switches support an update rate of 1 per second. This limit is independent of whether the monitored extensions are on the same switch or a different switch.
ShoreTel 13.1
37
2.7.5
ShoreTel Voice Switch Feature Capacity

The ShoreTel voice switch is designed to handle the maximum load for the services it provides. Some features place a higher real-time load on the ShoreTel voice switch processor than others, and the use of these features must be carefully planned to take into account the impact on the processing power of a switch to handle call control signaling messages. Table 2-5 offers some general guidelines for the number of extensions and group members for several commonly used features. Keep in mind that in addition to observing these limitations, you must stay below the real-time requirements of the switch itself. Table 2-5 Feature Capacity Hunt Group Extension Members / extensions 8 16 Bridged Call Appearance 24 Pickup Group 16 IP Phones 120 N/A
32 phones on a 24 switch monitoring the same extension 24 N/A N/A 80
Stack size/extensions Total members on all extensions
24 16
24 N/A
2.7.5.1
IP phones
Ringing a single user's IP phone generates only one set of call control messages. However, as the call rate increases, the load on the processor also increases. Note that the call rate is the driving factor of load and not the length of a call. For instance, sixty calls placed over one hour, with each call lasting one minute, is a much higher load on the processor than a single call lasting one hour.
2.7.5.2
Hunt Groups
Hunt groups place a significantly heavier burden on the ShoreTel voice switch. For example, if you have a hunt group with 16 members, a single call into the hunt group will generate 16 simultaneous calls (assuming the feature is configured to simultaneously ring each hunt group member). To extend this example, assume that the call stack size for this hunt group is set to 16, and 16 calls arrived at the same time, this would be equivalent to 256 calls (16 x 16) simultaneous calls. The number of hunt group members (as well as the call stack depth) is a multiplying factor for the signaling load that would be generated thus, you should closely engineer hunt groups to ensure that the voice switch is not overburdened in order to ensure optimal performance. You can have 8 hunt groups on a switch. Each hunt group can have up to 16 members and each hunt group can have a call stack of 24. The maximum number of members across all groups on the switch also has to remain below 16. For instance, you could have one hunt group of 16 members or 2 hunt groups with 8 members each.
38
2.7.5.3
Bridged Call Appearances

With Bridged Call Appearances (BCA), additional processor load is related to the call control signaling transmission to the buttons that have been programmed on the ShoreTel IP phones. If a single BCA with a call stack of one is configured on a phone, this represents one load. However, if that same BCA were to appear on 24 different phones, that would represent 24 times more call signaling load than if the BCA were to appear on one phone. The switch is capable of handling 24 BCAs, with a call stack depth of 24 and up to 32 phones monitoring a single BCA. If there are no hunt groups on the switch, it is possible for the switch to support up to 160 buttons programmed to monitor BCAs.
2.7.5.4
Pickup Groups
Pickup Groups place an additional load on the processor related to tracking the extensions in the group (although the actual real-time load is rather light and is not factored into the real time equation). The switch is capable of supporting 16 pickup groups with a maximum of 24 members in the group. The total number of members in all groups on the switch must not exceed 80.
2.7.5.5
Real Time Capacity

In addition to the overall feature capacity limit, you should calculate the real-time load on the switch using the formula below:
Thus, with the following configurations:

HG 1 4x4 16
A hunt group with four members and a call stack of four. A second hunt group with eight members and a call stack of three. Ten phones, each monitoring four BCA. + + + HG 2 8x3 24 + + + BCAs (10 x 4)/2 20 = = = 60 Total 60
You would have room to spare:
ShoreTel 13.1
39
40
Chapter 3
Network Requirements and Preparation

Use the information in this chapter to determine specific network requirements for the ShoreTel system. After determining the network requirements, you will be ready to configure your network appropriately. The topics discussed include:
Overview on page 41 Understanding the Requirements for Toll-Quality Voice on page 42 WAN Technology Choices on page 66 IP Address Assignment on page 67 Configuring DHCP for ShoreTel IP Phones on page 68 Configuring Automatic VLAN Assignment through DHCP on page 72 Time Services on page 73 Virtual Private Network (VPN) on page 73 Firewalls on page 76 Media Encryption on page 78 Session Initiation Protocol (SIP) on page 79 Example Network Topologies on page 79 Computing Admission Control Bandwidth on page 81
3.1
Overview
The ShoreTel system is an IP-based voice solution deployed across your IP network. This allows the components of the system to be located anywhere on your IP network, resulting in a single system for all your voice applications at all locations. This single system approach significantly reduces the complexity associated with legacy systems that consist of multiple PBXs, multiple voice mail systems, multiple auto-attendants, and multiple automatic call distribution systems, each with their unique management interfaces. Since the ShoreTel system becomes another application on your IP network, it is important to understand how the system integrates with your data network. As you migrate your network to include voice as another application across your wide area network, it becomes necessary for your IP LAN and WAN to provide a network that meets the requirements for toll-quality voice. The ability of your network to deliver
ShoreTel 13.1
41
Chapter 3: Network Requirements and Preparation
this performance will vary based on the number of simultaneous calls between locations, the voice quality required, and the other application traffic on the network. Some of the key considerations are:
Bandwidth Latency Jitter Quality of service
3.2
Understanding the Requirements for Toll-Quality Voice

The ShoreTel system is designed to deliver the highest possible voice quality. To ensure high quality voice transmissions, you must be sure that the entire network on which you deploy the ShoreTel telephony system is able to provide toll-quality voice communications throughout. Both LAN and WAN links must be adequately constructed to ensure the fluid transmission of time- and order-sensitive voice packets. This section provides you with the background to understand the factors involved in engineering an IP network that is ready for voice communications. In general, to ensure voice quality on the LAN, the ShoreTel system must be used in a switched Ethernet network. To ensure voice quality on the WAN, the ShoreTel system requires that you do the following:
Get a service level agreement (SLA) from your WAN service provider that
guarantees prioritization of voice traffic.
Prioritize your voice traffic ahead of your data traffic on network routers. Set the ShoreTel admission control feature to ensure that the voice traffic does
not flood the WAN links. With these items taken into consideration, you can simply and easily achieve tollquality voice using the ShoreTel system. The ShoreTel system is designed to work in multi-vendor network environments and, therefore, leverages Quality of Services (QoS) standards to ensure voice prioritization including:
Layer 2 IP Precedence (802.1p and 802.1q) (this only applies on the LAN) Layer 3 Differentiated Services Code Point (DiffServ/ToS) Layer 4 UDP 5004
3.2.1
Network Requirements
When your voice traffic travels across your IP network, you must ensure that your network does all of the following:
Delivers enough bandwidth Meets the latency and jitter requirements Meets the packet loss requirements for toll-quality voice
42
You also need to prioritize your voice traffic over your data traffic and configure the ShoreTel systems Admission Control feature.
3.2.2
Bandwidth Requirements
The amount of bandwidth for voice calls depends on these details:
Number of simultaneous calls Voice encoding scheme in use Amount of signaling overhead 3.2.2.1 Voice Encoding
Within a site, linear broadband encoding is recommended since bandwidth in the LAN is inexpensive and readily available. Between sites, G.729a is recommended because it uses the least amount of bandwidth. The linear codec provides slightly higher voice quality than G.711, but should not be used if there are any bandwidth concerns. If you select linear broadband or linear encoding, end points that do not support either codec will negotiate for the highest quality codec for both end points and G.711 is the only high-quality codec shared by all end points. Table 3-1 provides bandwidth information for different codecs. Table 3-1 Supported Codecs Supported ShoreTel Endpoints IP 110/115/212/ 230/230g/265/ 560/560g/655 All All All All All
Effective Codec Sample Rate Sample Size L16/1600 (Linear 16 KHz 16 bits Broadband) L16/8000 (Linear) PCMU (G.711 law) PCMA (G.711 Alaw) G.722 (ADPCM) G.729a AAC_LC BV-32 BV-16 DV-14 T.38 8 KHz 8 KHz 8 KHz 8 KHz 8 KHz 32 KHz 16KHz 8KHz 8KHz 16 bits 8 bits 8 bits 4 bits 1 bit
Data Rate 256 Kbps
128 Kbps 64 Kbps 64 Kbps 32 Kbps 8 Kbps 32 Kbps 16 Kbps
3.2.2.2
ShoreTel TCP and UDP Port Usage

Table 3-2 and Table 3-3 provide information about the ports ShoreTel devices and applications use to communicate with other ShoreTel devices and applications.
ShoreTel 13.1
43
Table 3-2 Originating Device Switch Traffic Type Call Control
Port Usage Part 1 Destination Device Switch IP Phone Communicator Softphone MGCP UDP 2427 Location Service MGCP UDP 5440 UDP 2427 Call Control UDP 5441 Bandwidth Manager UDP 5443 Admission Control UDP 5445
Media Stream
RTP UDP 5004 (dynamic: 102465535)
RTP UDP 5004 (dynamic: 1024-65535)
44
Table 3-2 Originating Device Service Appliance Traffic Type Call Control
Port Usage Part 1 (Continued) Destination Device Switch Location Service UDP 5440 Call Control UDP 5441 Bandwidth Manager UDP 5443 Admission Control UDP 5445 HTTP Web share TCP 80 HTTPS Web share TCP 443 Instant Messaging XMPP TCP5222 Presenter TCP 443 TCP 80 HTTPConfiguration Control TCP 80 RTP UDP 5004 Configurable dynamic default: 1000010550) RTP UDP 5004 Configurable dynamic default: 1000010550) RTP for SIP UDP 102465535 IP Phone Communicator Softphone
Conference Bridge Integration
Media Stream
Service Appliance
Media Stream V Switch only Call Control Media Stream MGCP UDP 2727 RTP UDP 5004 if dynamic 10000-10550 RTP UDP 5004 [if dynamic 10000-10550 BB to Phone UDP 5554
NTP UDP 123
IP Phone
UDP 5004 RTP if dynamic: 1000010550
ShoreTel 13.1
45
Table 3-2 Originating Device Traffic Type
Port Usage Part 1 (Continued) Destination Device Switch IP Phone Communicator Softphone CMCP server TCP 5464 CMCP client TCP 5465
Communicato Video r
Media Stream
Dynamic configurable default 100010550 MGCP UDP 2727 RTP UDP 5004 if dynamic 100010550 RPC - NCC TCP 1024-65535 MGCP - Media proxy UDP 2427 Location Service UDP 5440 Call Control UDP 5441 Bandwidth Manager UDP 5443 Admission Control UDP 5445 RTP UDP 5004 if dynamic 10000-10550 Remote TAPI TCP 1024-65535 RTP UDP 5004 if dynamic 1000010550
SoftPhone
Call Control Media Stream
DVM Server
Call Control
DVM Server
Media Stream
RTP UDP 5004 [if dynamic 102465535] Port Mapper RPC TCP 111 UDP 111
RTP UDP 5004 [if dynamic 1024-65535] RTP UDP 5004 [if dynamic 1024-65535]
RPC Connection Negotiation
Configuratio Firmware n Control download TCP 1024-65535
46
Table 3-2 Originating Device HQ/Director Server Traffic Type Call Control
Port Usage Part 1 (Continued) Destination Device Switch RPC - NCC TCP 1024-65535 MGCP - Media proxy UDP 2427 Location Service UDP 5440 Call Control UDP 5441 Bandwidth Manager UDP 5443 Admission Control UDP 5445 IP Phone Communicator Softphone TCP 1024-65535 Remote TAPI
Media Stream
RTP UDP 5004 [if dynamic 1024-65535] Port Mapper RPC TCP 111 UDP 111
RTP UDP 5004 [if dynamic 1024-65535]
RPC Connection Negotiation
Configuratio Firmware n Control download TCP 1024-65535 HQ/Director Server Maintenance Diagnostic ipbxctl TCP 5555 TCP 5555 Diagnostic phonectl
RTP UDP 5004 [if dynamic 1024-65535]
ShoreTel 13.1
47
Table 3-2 Originating Device Other Traffic Type Call Control Media Stream
Port Usage Part 1 (Continued) Destination Device Switch SIP UDP 5060 RTP - for SIP UDP 1024-65535 RTP UDP 5004 [if dynamic 1024-65535] DHCP Client UDP 68 Telnet TCP 23 IP Phone Communicator Softphone
Configuratio DHCP Client n Control UDP 68 Maintenance Telnet TCP 23 SNMP UDP 161 Table 3-3 Originating Device Switch Traffic Type Call Control Port Usage Part 2
Destination Device Service Appliance Location Service UDP 5440 DVM Server HQ/Director Server Other
SIP RPC - NCC RPC - NCC TCP 1024-65535 TCP 1024-65535 UDP 5060 MGCP - Media proxy UDP 2727
MGCP - Media Call Control proxy UDP 2727 UDP 5441 DRS UDP 5442 Bandwidth Manager UDP 5443 Admission Control UDP 5445 Call Control: Softswitch
Location Service Location Service UDP 5440 UDP 5440
48
Table 3-3 Originating Device Switch Traffic Type
Port Usage Part 2 (Continued) Destination Device Service Appliance DVM Server Call Control UDP 5441 DRS UDP 5442 Bandwidth Manager UDP 5443 Admission Control UDP 5445 DRS keepalive UDP 5446 HQ/Director Server Call Control UDP 5441 DRS UDP 5442 Bandwidth Manager UDP 5443 Admission Control UDP 5445 DRS keepalive UDP 5446 NCC Event port TCP 5457 SUNRPC Broadcast UDP 5458 Other
Call Control: Softswitch
Call Control: TMS RPC
NCC Event port TCP 5457 SUNRPC Broadcast UDP 5458
MSRPC MSRPC TCP/UDP 5500- TCP/UDP 55005600 5600
ShoreTel 13.1
49
Table 3-3 Originating Device Switch Traffic Type Media Stream
Port Usage Part 2 (Continued) Destination Device Service Appliance RTP UDP 5004 Configurable dynamic default: 1000010550) DVM Server RTP Static UDP 5004 RTP Configurable dynamic default: 1000010550) Port Mapper RPC TCP 111 UDP 111 FTP CTL - Boot files TCP 21 FTP DATA Boot files TCP 20 HQ/Director Server RTP Static UDP 5004 RTP Configurable dynamic default: 1000010550) Port Mapper RPC TCP 111 UDP 111 FTP CTL Switch Boot TCP 21 FTP DATA Switch Boot TCP 20 MYSQL TCP 4306 MYSQL Config TCP 4308 CDS TCP 5432 SNMP TRAP UDP 162 DHCP Server UDP 67 Other RTP - for SIP UDP 102465535
RPC Connection Negotiation Configuratio n Control
Database V Switch only Transport V Switch only Maintenance
MYSQL TCP 4306 MYSQL Config TCP 4308 CDS TCP 5432
50
Table 3-3 Originating Device Service Appliance Traffic Type Call Control
Port Usage Part 2 (Continued) Destination Device Service Appliance Location Service UDP 5440 DVM Server Softswitch HQ/Director Server Softswitch Other
Call Control Call Control UDP 5441 UDP 5441 Bandwidth DRS Manager UDP 5442 UDP 5443 Bandwidth Admission Manager Control UDP 5443 UDP 5445 Admission Control UDP 5445
Location Service Location Service UDP 5440 UDP 5440 Call Control UDP 5441 DRS UDP 5442 Bandwidth Manager UDP 5443 Admission Control UDP 5445 DRS Keepalive UDP 5446 NCC Event port TCP 5457 SUNRPC Broadcast UDP 5458
DRS Keepalive UDP 5446 Call Control: TMS RPC NCC Event port TCP 5457 SUNRPC Broadcast UDP 5458
MSRPC MSRPC TCP/UDP 5500- TCP/UDP 55005600 5600 Configuratio n Control FTP CTL - Boot files TCP 21 FTP CTL - Boot files TCP 21
FTP DATA -Boot FTP DATA -Boot files files TCP 20 TCP 20 Database MYSQL TCP 4306 MYSQL Config TCP 4308 MYSQL TCP 4306 MYSQL Config TCP 4308 MYSQL CDR TCP 4309 Transport CDS TCP 5432 CDS TCP 5432
ShoreTel 13.1
51
Table 3-3 Originating Device Service Appliance Traffic Type Media Stream
Port Usage Part 2 (Continued) Destination Device Service Appliance RTP UDP 5004 Configurable dynamic default: 1000010550) (Web Share) Ping Sync UDP/TCP 5450 DVM Server RTP Static UDP 5004 RTP Configurable dynamic default: 1000010550) HQ/Director Server RTP Static UDP 5004 RTP Configurable dynamic default: 1000010550) Other RTP for SIP Endpoints UDP 102465535
Collaboratio n Management (CMCA)
Ping Sync/ UDP 5450 (CMCA) to other Service Appliance TCP 5450 Any HTTP TCP 80 Any HTTP TCP 80
Instant Messaging
UDP 5451 UDP 5463 TCP/UDP 5466
Web-proxy, Web-proxy, session manager session manager TCP 5449, 5469 TCP 5449, 5469 TCP/UDP 5466 message forwarding
IM XMPP
STTS -NCC STTS - Media
TCP 5467 TCP 5468 NTP UDP 123 DHCP Server UDP 67 SMTP Trap UDP162 SMTP TCP 125 DNS TCP/UDP 53
52
Table 3-3 Originating Device IP Phone Traffic Type Call Control Media Stream
Port Usage Part 2 (Continued) Destination Device Service Appliance DVM Server RTP UDP 5004 if dynamic 10000-10550 FTP TCP 21 HQ/Director Server RTP UDP 5004 if dynamic 10000-10550 FTP TCP 21 FTP CTL Config TCP 21 FTP DATA Config TCP 20 ICMP - PING UDP 5004 RTP [if dynamic 1024-65535] DHCP Server UDP 67 SNTP UDP 123 Other
Configuratio n Control
FTP CTL Config TCP 21 FTP DATA Config TCP 20 ICMP PING
Communicato Call Control r
MS RPC Remote TAPI TCP/UDP 55005600
MS RPC Remote TAPI TCP/UDP 55005600
Remote TAPI Remote TAPI Event Event TCP 1024-65535 TCP 1024-65535 Configuratio n Control CAS TCP 5440 CAS TCP 5447 Web-proxy, Mgmt API TCP 5449, 5469 Web client, Online help TCP 80 HTTP CAS TCP 5440 CAS TCP 5447 Web-proxy, Mgmt API TCP 5449, 5469 RPC Connection Negotiation Port Mapper RPC TCP 135 MS Port Mapper RPC TCP 135 MS
ShoreTel 13.1
53
Table 3-3 Originating Device Traffic Type
Port Usage Part 2 (Continued) Destination Device Service Appliance DVM Server Web-proxy, WCM options page/Mgmt API TCP 5449, 5469 Session Mgmt AD/non-AD login auth & Web content TCP 80 CAS TCP5447 HQ/Director Server Web-proxy, WCM options page/Mgmt API TCP 5449, 5469 Session Mgmt AD/non-AD login auth & Web content TCP 80 CAS TCP5447 MCM Server TCP 80 Other
Communicato Web r
Mobile Instant Messaging Conference Bridge Integration XMPP TCP 5222 HTTP Configuratio n Control TCP 80 Presenter TCP 443 TCP 80 SoftPhone Media Stream RTP UDP 5004 if dynamic 10000-10550
MCM Server TCP 80
RTP UDP 5004 if dynamic 10000-10550
RTP UDP 5004 if dynamic 10000-10550 HTTP TCP 80
Configuratio n Control
54
Table 3-3 Originating Device DVM Server Traffic Type Call Control
Port Usage Part 2 (Continued) Destination Device Service Appliance DVM Server HQ/Director Server Other
MS RPC - DTAS/ MS RPC - DTAS/ TMS TMS TCP 1024-65535 TCP 1024-65535 MS RPC - DB access Location Service TCP 1024-65535 Call data UDP 5440 TCP 5441 Call Control Call data TCP 5441 UDP 5441 Bandwidth Manager UDP 5443 Admission Control UDP 5445 DRS keepalive UDP 5446
Location Service UDP 5440 Call Control UDP 5441 Bandwidth Manager UDP 5443 Admission Control UDP 5445 DRS keepalive UDP 5446
Media Stream RPC Connection Negotiation Port Mapper MS RPC TCP 135 Port Mapper RPC TCP 111 UDP 111 MS RPC TCP 135 Maintenance RPC Quicklook TCP 102465535 SMTP - Voice Mail transport TCP 25 SMTP - Voice Mail transport TCP 25 SMTP TCP 25
Distributed Voice Mail Voice Mail Notification
ShoreTel 13.1
55
Table 3-3 Originating Device HQ/Director Server Traffic Type Call Control
Port Usage Part 2 (Continued) Destination Device Service Appliance DVM Server MS RPC - DTAS/ TMS TCP 1024-65535 MS RPC - DB Notify TCP 1024-65535 Call data TCP 5441 Location Service UDP 5440 Call Control UDP 5441 Bandwidth Manager UDP 5443 Admission Control UDP 5445 DRS keepalive UDP 5446 HQ/Director Server Other
Media Stream RPC Connection Negotiation Port Mapper RPC TCP 111 UDP 111 MS RPC TCP 135 Maintenance Distributed Voice Mail Voice Mail Notification RPC - Quicklook TCP 1024-65535 SMTP - Voice Mail transport TCP 25 SMTP TCP 25
56
Table 3-3 Originating Device HQ/Director Server Traffic Type CDR
Port Usage Part 2 (Continued) Destination Device Service Appliance DVM Server HQ/Director Server Other CDR archive on remote server TCP 3306 HTTP - Director TCP 80 HTTP Quicklook TCP 80
Other
Configuratio n Control Maintenance
3.2.2.3
Bandwidth in the LAN

For LAN calls using the voice switches, 10 msecs of voice samples are encapsulated in a Real Time Protocol (RTP) packet before being transmitted onto the LAN. For IP phones and SoftPhones, 20 msecs of voice samples are encapsulated in an RTP packet before being transmitted onto the network. The protocol overhead consists of 12 bytes for the RTP header, 8 bytes for the UDP header, 20 bytes for the IP header, and 26 bytes for the Ethernet framing. When ADPCM voice encoding is used, an additional 4 bytes are added to the voice data for decoding purposes. This yields an effective LAN bandwidth as shown in Table 3-4. Table 3-4 LAN BandwidthBytes Linear Broadba nd Voice data (10 msec) RTP header UDP header IP header Ethernet header and framingc 320 12 8 20 26 Linear 160 12 8 20 26 G.711 80 12 8 20 26 ADPCM (G.722) 40+4a 12 8 20 26 G.729a 20 (20 msec)b 12 8 20 26 G.729a 30 (30 msec) 12 8 20 26
ShoreTel 13.1
57
Table 3-4
LAN BandwidthBytes (Continued) Linear Broadba nd Linear 226 G.711 146 ADPCM (G.722) 110 32 Kbps G.729a 86 (20 msec) 8 Kbps G.729a 96 (30 msec) 8 Kbps
Total bytes per packetd Bandwidth for voice onlye Bandwidth with overhead
386 256 Kbps
128 Kbps 64 Kbps
309 Kbps
181 Kbps
117 Kbps
88 Kbps
34 Kbps
34 Kbps
a. When ADPCM using voice encoding, four bytes are added to the voice data for decoding purposes. b. G.729a is supported in 10-msec, 20-msec, and 30-msec packets. c. Ethernet framing = 14 bytes of Ethernet header, a 4-byte checksum, and 8 bytes of additional framing. d. Voice data bytes per packet = (# bits/sample) x (8 samples/msec) x (10 msecs/ packet) / (8 bits/byte). e. Bandwidth = (# bytes/10 msecs) x (8 bits/byte).
For calls between analog telephones, voice bandwidth is used only on the connection between the voice switches. For calls involving IP telephones, the bandwidth is required between the IP phones at the users desktop. This means that for IP telephones, network planning must include provisioning capacity to each IP phone.
3.2.2.4
Bandwidth in the WAN

Increasing the number of voice samples per packet decreases the bandwidth required (since the percentage of signaling overhead is reduced); however, it also increases the latency of the voice call, which can result in poorer voice quality. Consequently, the ShoreTel system uses 10-msec voice packets on the LAN, where bandwidth is readily available, and 20-msec voice packets on the WAN, where bandwidth conservation is more important. WAN calls are calls made between ShoreTel system sites. For WAN calls, routers with RTP Header Compression (cRTP) reduce the 40 bytes in the IP + UDP + RTP header to 4 bytes. If you want to use cRTP, make sure the routers implementation of cRTP does not increase the latency or jitter of the voice traffic, since this can have a negative impact on voice quality. If the router does increase latency or jitter with cRTP, add this to your overall expected latency and make sure you still have sufficient performance for acceptable voice quality. Table 3-5 shows the resulting effective WAN bandwidth. It does not include the overhead associated with the underlying WAN network protocol, such as HDLC, frame relay, ATM, and VPN; however, the ShoreTel admission control software computes bandwidth requirements according to the data in this table and assumes a PPP header-size for computations.
58
Table 3-5
WAN BandwidthBytes Linear Broadba nd Linear 320 12 8 20 5 365 G.711 160 12 8 20 5 205 ADPCM 80+4a 12 8 20 5 129 G.729a 20 12 8 20 5 65 8 Kbps G.729a 30 12 8 20 5 75 8 Kbps
Voice data (20 msec)
640
RTP header 12 UDP header 8 IP header PPP header 20 5
Total bytes 685 per packetb Bandwidth for voice onlyc Bandwidth including overhead Bandwidth after cRTP 256 Kbps
128 Kbps 64 Kbps 32 Kbps
284 Kbps
26 Kbps
26 Kbps
260 Kbps
12 Kbps
12 Kbps
a. When ADPCM voice encoding is used, an additional 4 bytes are added to the voice data for decoding purposes. b. Voice data bytes per packet = (# bits/sample) x (8 samples/msec) x (20 msecs/ packet) / (8 bits/byte) c. Bandwidth = (# bytes/20 msecs) x (8 bits/byte)
3.2.3
Latency
Latency is the amount of time it takes for one persons voice to be sampled, digitized (or encoded), packetized, sent over the IP network, de-packetized, and replayed to another person. This one-way delay, from mouth-to-ear, must not exceed 100 msecs for toll-quality voice, or 150 msecs for acceptable-quality voice. If the latency is too high, it interferes with the natural flow of the conversation, causing the two parties to confuse the latency for pauses in speech. The resulting conversation is reminiscent of international calls over satellite facilities. The latency introduced by the ShoreTel system can be understood as follows: When a person talks, the voice is sampled by the ShoreTel voice switch, generating a latency of 5 msecs. If the call does not traverse ShoreTel voice switches and is handled completely internally by the switch, the latency is generated by the basic internal pipeline of the switch. In this case, the switch samples the voice, processes it, combines it with other voice streams (switchboard), and then converts it back to audio for output to the phone in 5-msec packets, for a total latency of about 17 msecs. When the call transfers between voice switches, the voice is packetized in larger packets10-msec for LAN and 20-msec for WAN to reduce network overhead. The larger packets take more time to accumulate and convert to RTP before being
ShoreTel 13.1
59
sent out. On the receive side, the incoming packets are decoded and placed in the queue for the switchboard. For a 10-msec packet, this additional send/receive time is approximately 15 msecs, and for a 20-msec packet it is about 25 msecs. For IP phones, the latency is 20 ms in the LAN and 30ms in the WAN. When the codec is G.729a, the encoding process takes an additional 10 msecs and the decoding process can take an additional 10 msecs. See Table 3-6 for specific information about latency on the ShoreTel system. Table 3-6 Configuration Switch LAN WAN Latency Frame Size -5 0 5 15 15 Jitter Decodin Buffera g Varies Varies Varies Varies 0 5 5 15 Total (+/ 5 msec)b 17 32 + Jitter Buffer 42 + Jitter Buffer 62 + Jitter Buffer
Overhea Encodin d g 17 17 17 0 5 5 15
G.729a 17 (LAN and WAN)
a. The jitter buffer varies, depending on network conditions. See below for more information. b. If a call comes in on a trunk through either T1/E1 or analog loop-start, the total latency is increased by the delay in the PSTN. You must add this latency to the total latency. Latency for the PSTN varies; however, it is probably a minimum of 10 msecs (for local), and it could be as high as hundreds of msecs (for long international calls).
3.2.4
Jitter for Voice Switches

Jitter is the variation of latency across the network and the variation in packet processing inside the switches. To compensate for jitter, the ShoreTel voice switches continuously measure the jitter in the system and dynamically change the size of the receive jitter buffers to optimize voice quality. If the jitter buffer is too small, there can be packet loss from buffer underflows. This occurs when the jitter buffer runs out of valid voice samples. If the jitter buffer is too large, there will be unnecessary latency. Both conditions have a negative impact on voice quality. The jitter buffer starts at the minimum size of 0 msecs as packets from the network are placed into the switchboard queue for immediate processing. When jitter is detected on the network, the jitter buffer dynamically increases in increments of 5 msecs to compensate for increased jitter and decreases in size in reaction to less jitter. The maximum value of the jitter buffer is set by ShoreTel Director and ranges from 20 to 400 msecs, with a default of 300 msecs. As the jitter increases on the network and the jitter buffer needs to be increased to guarantee timely audio play, the latency of the audio also increases. The system attempts both to maintain a minimum jitter buffer size that provides good-quality voice without dropping packets and to provide minimum latency. For IP phones that are configured into the ShoreTel system, the jitter buffer is not configurable. The minimum jitter buffer is 10 msecs, and the maximum is 80 msecs.
60
Maximum values greater than 100 should rarely be necessary. If needed, this could indicate a problem in your network that should be addressed in another way.
3.2.5
Packet Loss
Lost packets can occur on the IP network for any number of reasons. Packet loss above 1% begins to adversely affect voice quality. To help reduce this problem, the ShoreTel voice switches have a feature called lost packet concealment. When there is no voice sample to be played, the last sample available is replayed to the receiving party at a reduced level. This is repeated until a nominal level is reached, effectively reducing the clicking and popping associated with low levels of packet loss. Fax and modem calls demand essentially zero packet loss to avoid missing lines on fax calls and to avoid dropped modem calls. In addition, fax and modem calls, when detected, may change to a higher-rate codec.
3.2.5.1
Summary of the Network Requirements

Table 3-7 summarizes the network requirements for bandwidth, latency, jitter, and packet loss. Table 3-7 Parameter Bandwidth (WAN) Network Requirements Requirement With ADPCM and no RTP Header Compression: 52 Kbps per call With G.729a and no RTP Header Compression: 26 Kbps per call With G.711 and no RTP Header Compression: 82 Kbps per call If your network uses VPN, bandwidth use is affected. Latency and jitter for toll quality < 100 msecs total 100 msecs less 42 msecs allocated for the ShoreTel system yields a 58 msec budget for the network. When G.729a encoding is used, 100 msecs less 62 msecs allocation for the ShoreTel system yields a 38 msec budget for the network. Latency and jitter for acceptable quality < 150 msecs total 150 msecs less 42 msecs allocated for the ShoreTel system yields a 108 msec budget for the network. When G.729a encoding is used, 150 msecs less 62 msecs allocated for the ShoreTel system yields an 88 msec budget for the network. Packet loss < 1% for voice calls, and no packet loss for fax and modem calls
ShoreTel 13.1
61
3.2.5.2
Impact of Long Network Outages

The ShoreTel system is a completely distributed system in which each ShoreTel voice switch provides all call control functionality for inbound and outbound calls, as well as features such as transfer, conference, pickup, and trunk selection. When there is a long network outage, the switches will detect the problem and run isolated from the switches that can no longer be reached. In the ShoreTel system, switches communicate every 30 seconds and disconnect when there is no response after 60 seconds.
3.2.6
Bandwidth Management
In addition to the network requirements discussed above, bandwidth management techniques need to be deployed to ensure that real-time voice data is not affected by bursts or high amounts of data traffic.
3.2.6.1
Local Area Network

To manage bandwidth in the local area network (intra-site) and meet the requirements for toll-quality voice, use Ethernet switching. Ethernet switching is cost effective and simple to provision. Your LAN configuration requirements will vary depending on your infrastructure and whether your network includes IP phones. IP phones sample the users voice and convert the voice signal to IP packets using the Real Time Protocol (RTP). These packets must be tagged for higher prioritization in the network. ShoreTel IP phones have embedded Ethernet switches and will automatically prioritize voice traffic ahead of any data traffic coming from daisychained personal computers (for example, large files transfers and e-mail). On the local area network, there are several methods to prioritize voice packets, including:
IP Precedence = 5 (configurable, recommendation is 5) DiffServ/ToS = EF (configurable, recommendation is EF) UDP (Destination port) = 5004 (when not using SIP)
The Ethernet switch configuration should prioritize traffic using one of these methods. This allows the voice traffic arriving at the switch to travel ahead of the data traffic. ShoreTel customers typically choose to prioritize Differentiated Service Code Point (DSCP) since this configuration is easy to set up on smart Ethernet switches. When IP phones are used, the desktop connection to the users computer and phone must also be part of your switched Ethernet network. The users phone is connected to the port on the Ethernet switch, and the users computer or other data device is connected to the integrated two-port Ethernet switch inside the IP phone. In this configuration, the switch port connected to the phone must be configured to prioritize the voice packets from the phone above the data packets. PCs connected through IP phones will lose their connection to the network if the IP phone loses power. Voice quality can be guaranteed by putting each of the ShoreTel voice switches and the ShoreTel server on its own Ethernet switch port. A network with this topology meets the bandwidth, jitter, and latency requirements for toll-quality voice without the additional need for special prioritization of voice packets.
62
3.2.6.2
Virtual LANs
An alternative method to prioritize voice over data is to create a separate virtual LAN strictly for your voice traffic. The ShoreTel IP phone as well as the ShoreTel voice switches can be configured on a specific VLAN. Set the voice VLAN for higher prioritization in the network. The Ethernet switch infrastructure needs to be configured to prioritize the voice VLAN. This allows the voice traffic arriving at the switch to travel ahead of the data traffic.
3.2.6.3
Wide Area Network

To manage bandwidth in the wide area network, prioritize your voice traffic ahead of your data traffic. The voice packets on the ShoreTel system always travel on UDP port 5004, so you simply prioritize this UDP port within your routers with priority queueing. You can prioritize based on the voice switch IP address, the MAC address, or the physical port on the Ethernet switch. As an additional step, you can also prioritize the distributed call control signaling that always travels on UDP port 5440 through UDP port 5445. If the voice traffic for the call needs to flow across a WAN link, the routers needs to be configured to prioritize voice ahead of data using one of the two tagging methods, DiffServ/ToS or UDP 5004. ShoreTel customers typically choose to prioritize UDP 5004 to avoid costly network upgrades since older routers and more Ethernet switches support this function. Additionally, configuring UDP 5004 for prioritization is easy to set up.
3.2.6.4
Client Bandwidth
ShoreTel Communicators communicate with the ShoreTel server for call information and control, configuration changes, and advanced services such as extension monitoring. Table 3-8 provides an estimate of the client bandwidth used for each of the ShoreTel Communicator applications. Table 3-8 Personal Professional Operator Extension Monitor Workgroup Agent Queue Monitor Workgroup Supervisor Queue Monitor Agent Monitor Typical ShoreTel Communicator Bandwidth Use Bandwidth Use .2 Kbps .2 Kbps .2 Kbps + 1.5 Kbps 1.5 Kbps per monitored extension .25 Kbps 6.5 Kbps per queued call .25 Kbps 6.5 Kbps per queued call 1.5 Kbps per agent
ShoreTel Communicator
ShoreTel 13.1
63
3.2.7
Distributed Call Control Signaling

Voice switches maintain communication with each other. A single voice switch maintaining basic connectivity with 59 other voice switches consumes less than 1.5 Kbps of bandwidth.
3.2.8
Admission Control in the Wide Area Network

To ensure that your voice traffic does not overwhelm the wide area network and degrade voice quality, the ShoreTel system has an Admission Control feature. From ShoreTel Director, you can limit the amount of WAN bandwidth used for telephone calls on a per-site basis. For a telephone call to be established between sites, admission control must be met at both sites. If the admission control limit is reached at a site, additional calls cannot be placed to or from the site, thus ensuring the voice quality of calls already in progress. If the user is making an outbound call, the call is automatically routed out of a trunk at the site. When making an extension-toextension call, the user is informed that there is insufficient network bandwidth to complete the call. The user can try again later or dial the external number of the other user. If PSTN failover is enabled for a user extension, the users extension-to-extension calls are automatically routed to the public switched telephone network (PSTN) when there is insufficient bandwidth for an IP connection to phone.
3.2.9
Spanning Tree Protocol

Spanning Tree Protocol (STP) is used by Ethernet switches and routers to determine if there are multiple paths on the network between any two endpoints. You must disable STP on any network port that has a ShoreTel Voice Switch or ShoreTel server connected.
3.2.10 Traffic Shaping to Reduce Bottlenecks

Given that more applications are requiring WAN bandwidth, the need to optimize is increasingly important. This is particularly true for enterprises that want to deploy voice over virtual networks where quality of service and traffic shaping are required. With traffic shaping, it is possible to set policies that determine who or what gets top priority. For example, by prioritizing the various flows of traffic, an administrator can make sure that UDP (voice) traffic gets a higher priority than FTP (file download) traffic.
3.2.11 Echo Cancellation

Echo in a voice communication system is caused by signal reflections generated by the electrical circuits called hybrids that convert between two-wire (shared transmit and receive pair) and four-wire circuits (separate transmit and receive pairs). These reflections cause the speakers voice to be heard in the speakers ear as delayed by many milliseconds. Echo is present even in the traditional circuit-switched telephone network, but since the delay in a local circuit-switched call is so low, the echo is not perceivable. On a packet-based voice network, there is more delay, and the speaker may perceive the echo if it is not properly cancelled. The DSP software on the ShoreTel voice switches provides dynamic echo cancellation. When a user places an extension-to-trunk call using an analog trunk on a ShoreTel voice switch, the users voice bounces off the initial four-wire to two-wire
64
conversion in the analog trunk circuit, then off the two-wire to four-wire in the central office, and finally off the called partys telephone. This echo returns from the central office and is cancelled by the echo canceller on the trunk port of the voice switch. The echo from the called partys phone, however, is usually cancelled or suppressed by the central office. If this echo is not cancelled, the user may hear himself or herself talking. In the opposite direction, the external persons voice bounces off the users telephone. This echo returns from the telephone and is cancelled by the echo canceller on the telephone port of the voice switch. If this echo is not cancelled, the external party hears himself or herself talking. This same process of echo cancellation applies to extension-to-extension as well as trunk-to-trunk calls. ShoreTel Voice Switches can cancel echo received up to 16 msecs after being sent.
3.2.12 Resultant Voice Quality

As stated earlier, the ShoreTel system has been recognized for excellent voice quality. This is a result of the excellent hardware and software design that minimizes latency and dynamically adapts to the effects of jitter, packet loss, and echo introduced by the network. There are two subjective testing methods that are used to evaluate voice quality. A method called Mean Opinion Score (MOS) is an open test in which a variety of listeners judge the quality of a voice sample on a scale of 1 (low) to 5 (high). There is general industry agreement on the theoretical maximum MOS value on a per codec basis that can be achieved as shown in Table 3-9. Table 3-9 Codec Linear G.711 ADPCM (G.722) G.729a Theoretical MOS Maximum Scores Data Rate (Kbps) 128 64 32 8 MOS 4.5 4.1 3.85 3.85
Both the MOS test method and an interactive test method were used by Microm. The interactive test focused on the conversational quality of the call. The results are shown in Table 3-10. The ShoreTel MOS scores are higher than the industry-standard values. This is likely a result of the subjective nature of the head-to-head test, which scores a relative ranking rather than an absolute ranking. Table 3-10 Codec Linear G.711 ADPCM G.729a ShoreTel MOS and Interactive Test Results Data Rate (Kbps) 128 64 32 8 MOS Not tested 4.464.87 3.964.05 Not tested Interactive Not tested 4.66 4.33 Not tested
ShoreTel 13.1
65
3.3
3.3.1
WAN Technology Choices

Minimum Bandwidth Requirements
The minimum WAN bandwidth required to deploy a voice switch at a site depends on the number of calls expected. With ADPCM, a single call consumes 52 Kbps, and if this call becomes a conference call, another 52 Kbps is needed, yielding a total of 104 Kbps. From a broadband perspective, the first available technology is 128 Kbps (ISDN), which leaves only 24 Kbps for other IP traffic. For teleworking applications, where only a single call is needed, 128 Kbps can be used. For other sites on the voice network, the minimum bandwidth recommended is 384 Kbps. Various technologies are available from different service providers to provide IP connectivity between locations, as shown in Table 3-11. Table 3-11 IP Connectivity Chart Downstream Bandwidth Kbps 1544 Varies 1544 1024 768 512 384 144 1,000 (varies) 1,000 (varies) 128 28.856 Calls with ADPCMa 26 Varies 26 17 13 8 6 1 call only 1 call only 1 call only Not supported Not supported
Upstream Technology Bandwidth Kbps T1 SDSL SDSL SDSL SDSL SDSL IDSL ADSL Cable ISDN BRI Dial-up modem 1544 1544 1024 768 512 384 144 128 128 (varies) 128 28.856 Frame Relay Varies
a. Your bandwidth will vary, based on the WAN overhead for your particular system.
3.3.2
Leased T1
Leased T1 facilities are the most robust WAN technology available. Leased T1s are point-to-point links that inherently meet the network requirements for toll-quality voice since no ISP is involved. Dedicated T1s are priced on a per unit distance basis, making this a very cost-effective option over short distances.
3.3.3
Frame Relay
Frame Relay is a viable option as long as you get a committed information rate (CIR) that meets the bandwidth and network requirements for toll-quality voice communications.
66
3.3.4
SDSL
SDSL is considered business-to-business DSL in which you can negotiate a service level agreement with the service provider. Unlike T1, SDSL is priced on a flat bandwidth basis, making the price distance insensitive and cost-effective over long distances. Although this is an excellent option, especially moving forward, ShoreTel has found the use of SDSL challenging, since the service providers often commit to a Service Level Agreement (SLA) they cannot fulfill. Many service providers have grown very fast, and the IP network is a patchwork of devices. These service providers are usually geared toward providing bandwidth for typical data applications, and a voice application highlights weaknesses in their network. Only with joint troubleshooting of the service providers network, using tools such as ping plotters, has ShoreTel been able to achieve the SLA the service provider promised.
3.3.5
IDSL
IDSL modems, which have an uplink and downlink speed of 144 Kbps, can be considered for teleworking applications. The actual performance will vary based on your service provider and your applications.
3.3.6
ADSL
ADSL modems, which have an uplink speed of 128 Kbps, can be considered for teleworking applications. The actual performance will vary based on your service provider and your applications.
3.3.7
Cable Modems
Cable modems, which can have an uplink speed of 128 Kbps, can be considered for teleworking applications. The actual performance will vary based on your service provider and your applications.
3.3.8 3.3.9
ISDN BRI Dial-Up Modems

Because of their inherent latency and low bandwidth, dial-up modems are not supported.
3.4
IP Address Assignment
Each ShoreTel Voice Switch must have an IP address, and each ShoreTel server must have a static IP address. Use one of the following ways to assign an IP address to a voice switch:
DHCP on a network server (ShoreTel does not support DHCP on its servers). The BOOTP server that ShoreTel Director has in its records. The maintenance port on the front of the ShoreTel Voice Switch. See Appendix
F in this guide for all switch models or refer to the ShoreTel quick install guide
ShoreTel 13.1
67
for a specific ShoreTel Voice Switch model for information about the location of the maintenance port on the switch. If a voice switch has been configured to request a dynamic IP address, it puts a DHCP/BOOTP request on the network when powered on. If the voice switch receives a response, it uses the new IP address. If no response is received, it reverts to the previous IP address. If there is no previous IP address, the voice switch continues trying to get an IP address. If the network has a DHCP server, we recommend that you reserve IP addresses so that the IP addresses of the voice switches do not dynamically change. If the network does not have a DHCP server, the integrated BOOTP server within ShoreTel Director lets you assign IP addresses. The maintenance port is for configuring the networking parameters. The following recommendations can assist with the assignment of IP addresses:
Ensure that only one DHCP server is on the network. Multiple DHCP servers
public network in other situations. For example:
can unexpectedly change IP addresses and disrupt operation of voice switches.
The ShoreTel system must be on a private network in some situations and on a

If the enterprise is using a firewall with Network Address Translation (NAT), all remote facilities must establish VPN connections to headquarters and be on the same private network. If the enterprise is using firewalls but not NAT, all remote locations must use public IP addresses.
Each IP telephone must have a unique IP address. You can configure the IP
telephone through DHCP or manually on the telephone.
Telephones at different sites must be configured on different subnets or

assigned from different address ranges so that the ShoreTel system can properly assign the voice switch for the IP telephone site.
3.5
Configuring DHCP for ShoreTel IP Phones

The ShoreTel server provides the latest application software and configuration information to the ShoreTel IP Phones. To receive this information, the ShoreTel IP Phone must have the servers IP address. The configuration task in this section is for specifying the IP address and other necessary information. The phone receives the necessary information through a vendor-specific DHCP option. ShoreTel IP Phones have a built-in configuration to seek the ShoreTel servers address as Vendor Specific DHCP option 156. If these options are not available, ShoreTels IP phones use option 66. Model numbers of ShoreTel IP Phones that support DHCP option 156 are ShoreTel IP Phone models IP110/115/212k/230/230g/ 265/560/560g/655. NOTE The ShoreTel IP Phone 8000 does not support option 156 for this application. The configuration task in this section involves a number for the country of the network or subnet where the phones reside. If necessary, find the number for a country in Table 3-12.
68
If the customers network has separate subnets, be sure to select the correct subnet. For example, if a multi-national organization needs the DHCP server to deliver Spanish tones and cadences to the IP phones in an office in Spain, specify the subnet for that office. Without this specification, all phones that boot from this DHCP server receive Spanish tones and cadences. Another value for the configuration task is a number that points to a language by its country. Although this number refers to a language, it is bound to a country, not a language. For this reason, some countries with different languages have the same language number in the configuration of DHCP option 156. Table 3-13 is the list of language numbers. (As Table 3-13 shows, language number 4 is a good example.) Selecting the correct language code ensures that the phone shows text in the desired language. Examples of this text are abbreviations for days and months and messages that say a requested service is unavailable. To set up DHCP option 156 for ShoreTel IP Phone models IP110/115/212k/230/230g/ 265/560/560g/655 on a Microsoft DHCP server: Step 1 Open DHCP Manager on the Microsoft DHCP server. Step 2 Right-click the DHCP server, and then select Set pre-defined options. Step 3 Click Add. Step 4 Set Name to IP Phone Boot Server. Step 5 Set Data Type to String. Step 6 Set Code to 156 and add a description, if desired. Step 7 Navigate to the scope options and add option 156. Step 8 Type the values for option 156 with the following syntax: ftpservers=ip_address, country=n, language=n, layer2tagging=n, vlanid=n where
ip_address is the IP address of the ShoreTel headquarters server. n in country=n corresponds to the country number in Table 3-12. n in language=n corresponds to the language number in Table 3-13. Country Numbers for Option 156
Table 3-12 1 2 3 4 5 6 7
Number Country United States of America Canada France Italy Germany Spain United Kingdom
ShoreTel 13.1
69
Table 3-12 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 28 29 30 31 32 33 34 35 36 37 38 39 41 42 44
Country Numbers for Option 156 (Continued)
Number Country Australia Hong Kong Malaysia Singapore Brazil Netherlands New Zealand Portugal Ireland Belgium Mexico Denmark Sweden Switzerland Austria India China Norway United Arab Emirates Japan Taiwan South Korea Luxembourg Finland Philippines Thailand Poland Czech Republic South Africa Costa Rica Greece Monaco (France) Israel Indonesia
70
Table 3-12 46 48 49
Country Numbers for Option 156 (Continued)
Number Country Hungary Fiji Mongolia Table 3-13 1 2 3 4 Language Numbers by Country for Option 156
Number Language (Country) U.S., Canada, Mongolia, Philippines, Thailand Spain (CALA) Germany, Austria English (UK), Czech Republic, Ireland, Malaysia, Greece, Hong Kong, New Zealand, Poland, India, Romania, Singapore, South Africa, United Arab Emirates, Indonesia, Finland France (Parisian), Belgium, Luxembourg, Switzerland, Monaco (France) Netherlands Mexico, Cost Rica, Chile Denmark Italy Sweden China Norway, Finland Brazil (Portuguese) Japan South Korea Taiwan (Mandarin) Portugal Bulgaria Australia, Fiji
6 7 8 9 10 11 12 13 14 15 17 18 22 23
Step 9 Connect an Ethernet cable to the data jack on the back of the IP phone. The IP phone downloads the latest bootROM and firmware from the ShoreTel server. During the whole configuration process, an IP phone reboots
ShoreTel 13.1
71
more than once. When the phone displays the date and time, the boot and upgrade processes have finished.
3.6
Configuring Automatic VLAN Assignment through DHCP

You can configure an IP phone to automatically determine its VLAN id via DHCP. When the phone boots for the first time, it will acquire an IP address via DHCP similar to any other network device. However, the DHCP response will also specify (using a proprietary DHCP option), the VLAN id for the phone to use. Then, the phone will release the IP address originally assigned to it and will reboot. After reboot, all packets are tagged with the VLAN id specified in the original DHCP response. The following phones are unaffected by this features: AP100 and AP110. The Automatic VLAN Assignment feature is not configured through ShoreTel Director. Configuration changes are performed at the DHCP server. Parameters related to Automatic VLAN Assignment (along with their supporting text) have been italicized in the procedure that follows to make them easier to spot. To configure Automatic VLAN Assignment via DHCP on a Microsoft DHCP server: Step 1 Open DHCP Manager on your Microsoft DHCP server. Step 2 Right-click the DHCP server and select Set pre-defined options. Step 3 Click Add. Step 4 Set Name to IP Phone Boot Server. Step 5 Set Data Type to String. Step 6 Set Code to 156 and add a description, if desired. Step 7 Navigate to the scope options and add option 156. Step 8 Set the value of option 156 to: ftpservers=ip address, Layer2Tagging=N, VlanId=X FtpServers always needs to be set to a ShoreTel server and is a pre-existing parameter. Layer2Tagging is a new parameter.
Purpose: enable/disable 802.1Q, default is disabled Format: Layer2Tagging=N
where N=0 is disable, N=1 is enable VlanId is a new parameter.
Purpose: VLAN id when 802.1Q is enabled, default is zero Format: VlanId=X
where X is a VLAN id between 0 and 4094 E.g., the following would enable VLAN tagging using a VLAN id of 10:
72
FtpServers=192.168.0.13,Layer2Tagging=1,VlanId=10
3.7
Time Services
For ShoreTel IP Phones, time services must be available to provide the telephones date and time display. This requires a server that supports Simple Network Time Protocol (SNTP). If an organization does not have an NTP server, it can use a publicly accessible time server that the NIST Internet Time Service (ITS) supports. See Table 3-14. In addition, you must configure the DHCP server to provide the correct GMT offset to the ShoreTel IP Phones at each site. See "Associating a User Group with Unassigned IP Phones" section on page 246 for more information. Table 3-14 Name time-a.nist.gov time-b.nist.gov NTP Time Servers IP Address 129.6.15.28 129.6.15.29 Location NIST, Gaithersburg, Maryland NIST, Gaithersburg, Maryland NIST, Boulder, Colorado NIST, Boulder, Colorado NIST, Boulder, Colorado University of Colorado, Boulder NCAR, Boulder, Colorado Microsoft, Redmond, Washington Symmetricom, San Jose, California Abovenet, Virginia Abovenet, New York City Abovenet, San Jose, California TrueTime, AOL facility, Sunnyvale, California TrueTime, AOL facility, Virginia
time132.163.4.101 a.timefreq.bldrdoc.gov time132.163.4.102 b.timefreq.bldrdoc.gov time132.163.4.103 c.timefreq.bldrdoc.gov utcnist.colorado.edu time.nist.gov time-nw.nist.gov nist1.symmetricom.co m nist1-dc.glassey.com nist1-ny.glassey.com nist1-sj.glassey.com nist1.aolca.truetime.com nist1.aolva.truetime.com 128.138.140.44 192.43.244.18 131.107.1.10 69.25.96.13 216.200.93.8 208.184.49.9 207.126.98.204 207.200.81.113 64.236.96.53
3.8
Virtual Private Network (VPN)

With the increasing desire to leverage the public Internet, and the concern about security, IP VPNs (Internet Protocol Virtual Private Networks) are becoming the secure access of choice. IP VPNs establish secure communications between employees, branches, or partners by using strong IP-based encryption and authentication techniques for transport security over the public Internet.
ShoreTel 13.1
73
IP VPNs are typically viewed as falling into three major categories: remote access VPNs, intranets (company site-to-site), and extranets (business-to-business). These services are being adopted by companies of all sizes as a result of the powerful combination of high-speed access links and public networks. An example is the use of high-speed, low-cost broadband DSL connectivity to enable teleworkers or branch offices to link securely with the company network via the Internet, as if they were accessing the LAN at the office including all network applications. A sample VPN configuration is shown in Figure 3-1.
Figure 3-1
VPN Topology
IP VPNs can be provided via hardware or software solutions located at the remote facility (branch office or teleworkers home) and the customer premises. These devices or solutions use technologies such as tunneling, encryption, and authentication to guarantee secure communications across a public infrastructure. All the components of your ShoreTel system must exist in the same enterprise private network. VPNs can be used to bridge your private networks across the Internet so that the networks for two buildings are both part of the same private network. For multiple locations that share a private network, bandwidth calculations should include the effective bandwidth inside the private network, rather than the raw bandwidth.
3.8.1
Tunneling
Tunneling encapsulates one type of data packet into the packet of another protocol. Multiple tunneling protocols are used today on the market:
PPTP (Point-to-Point Tunneling Protocol): PPTP includes compression

and encryption techniques. This protocol was introduced by Microsoft to
74
support secure dial-up access for its desktop, which corresponds to a large share of the desktop market.
L2F (Layer 2 Forwarding): Introduced by Cisco Systems, L2F was primarily

used to tunnel traffic between two Cisco routers. It also allows IPX traffic to tunnel over an IP WAN. Point Protocol) that merges the best features of L2F and PPTP. L2TP is an emerging IETF (Internet Engineering Task Force) standard.
L2TP (Layer 2 Tunneling Protocol): L2TP is an extension the PPP (Point-to IPSEC: This is a collection of security protocols from the Security Working
Group of the IETF. It provides ESP (Encapsulating Security Payload), AH (Authentication Header), and IKE (Key Exchange Protocol) support. This protocol, mature but still technically in a draft format, is currently considered the standard for encryption and tunneling support in VPNs.
For PPTP, IP VPN tunneling adds another dimension to the tunneling. Before encapsulation takes place, the packets are encrypted so that the data is unreadable to outsiders. Once the encapsulated packets reach their destination, the encapsulation headers are separated, and packets are decrypted and returned to their original format. The L2TP tunneling protocol does not encrypt before encapsulation. It requires the IPSEC protocol to take the encapsulated packet and encrypt it before sending it over the Internet.
3.8.2
Encryption
See "Media Encryption" section on page 78 for more information about ShoreTels proprietary media encryption methods. Encryption is the marking, transforming, and reformatting of messages to protect them from disclosure and maintain confidentiality. The two main considerations with encryption are the algorithm, such as Triple Pass DES (112 bits), RCA (128 bits), and Triple DES (168 bits), and the management of the distribution of encryption keys (IKE and PKI). These more recent keys, which support more than 100 bits, have been a major driver in the success of IP VPNs. They make it extremely difficult to hack into enterprise computer systems without an investment of millions of dollars in equipment. Encryption starts with a key exchange that must be conducted securely. The IKE (ISAKMP/Oakley) protocol has been considered the most robust and secure key exchange protocol in the industry to date. It is also a de facto standard for service providers and product vendors requiring the highest level of security for their VPN solutions. PKI (Public Key Infrastructure), new to the key management scene, is currently thought to be the long-term solution to simplifying the management of VPNs. The industry is still evaluating and testing PKI, with some initial deployments beginning to occur.
3.8.3
Performance
In the context of an IP VPNs performance, encryption can be a CPU-intensive operation. Therefore, an enterprise must answer two questions about encryption when it evaluates VPN products:
With encryption, does the maximum throughput substantially decrease? With encryption, can the network have a consistent level of throughput?
ShoreTel 13.1 75
Typically, a business considers the tradeoffs between performance, price, and the characteristics of is software-based and hardware-based encryption. NOTE Although a VPN is useful for data, for VoIP a VPN might not offer enough protection against latency and packet loss.
3.8.4
Integrated Security Appliances

A number of major vendors provide integrated broadband security appliances to eliminate security concerns. These devices use custom ASICs to deliver wire-speed firewall, Triple DES IPSec VPN, and traffic shaping in an easy-to-deploy, costeffective solution. Installing a security appliance, such as a NetScreen-5, eliminates the need to deal with complex PC software installations and allows IT to centrally manage the security policies of these remote offices and teleworkers. The firewall protection secures sensitive data at the remote site and can prevent both U-turn attacks and the launching of denial-of-service attacks from these computers. By combining broadband access technologies with an integrated security appliance, enterprises and service providers can safely and securely capitalize on all of the benefits of the broadband Internet.
3.9
Firewalls
A firewall is the first major purchase and the foundation of network security (Figure 3-2). It prevents unauthorized access to the network or web site by examining both incoming and outgoing traffic. Based on the predefined security policies, each individual packet is inspected and processed. Any type of traffic that is deemed to be illegal (based on rules that specify protocol type, source or destination IP address, and so on) is not allowed through the firewall. Using this tool, administrators can achieve tight control over the activities they allow into and out of their corporate network or e-business site. In a corporate network, a firewall prevents intruders from accessing corporate resources while allowing employees Internet access. In an ebusiness site, it allows outside access to the web server while preventing unauthorized access or attacks.
Figure 3-2
Firewalls
76
Often, a typical network access point, called a DMZ (demilitarized zone), is implemented to offer an outside presence for e-commerce clients, e-business partners, and web surfers. The DMZ acts as the gateway through which all Internet communications with the company or site transpire. It allows for controlled access to front-end web servers while protecting mission-critical resources (databases, routers, servers, and so on). Thus, the DMZ needs to be flexible, reliable, and available. The firewall is often the first line of defense in this environment. Always vigilant, this device must look into all traffic for the site. As part of its duty, the firewall recognizes and deals with denial-of-service attacks, such as TCP SYN flood and Ping of Death. In each of these attacks, the hackers are simply attempting to overwhelm the devices that provide an Internet presence for the company. With a TCP SYN flood, a stream of TCP SYN packets is sent to the receiving device (often the firewall). The finite memory and size of the TCP entry tables can be overrun by spurious SYN packets, preventing any real users from making a TCP connection required for HTTP communications. An ICMP flood attack also floods a device, by streaming ICMP echo packets at a recipient destination. This flood of packets requires the device to process and respond to these pings, burning precious resources and preventing other traffic from being serviced. By examining the sites traffic patterns, advanced firewalls can apply logical rules that prevent the device from trying to keep up with the denial-ofservice attack traffic. They also prevent this traffic from reaching the valuable web, application, and database servers that create your Internet presence and service your customers. By using firewalls in conjunction with the DMZ design technique, many businesses and service providers are striving to present as much information without permitting unwanted access to the corporate resources. One way to keep your mission-critical resources as private as possible, while still allowing for a strong Internet presence, is to use Network Address Translation (NAT). NAT offers the outside world one, or a few, IP addresses. This allows a manager to set up whatever internal IP addressing scheme may be required by corporate policies and business needs. An internal resources IP address (source IP) is changed as it passes through the NAT function to one of the outside IP addresses. Thus, the external world does not know any of the enterprises internal IP addresses. Only the NAT device presents an IP address that is known, and used by external devices. The NAT device keeps track of these conversations and performs the IP address translation as needed. Extending the private network of the corporate LAN to remote sites via VPN is a proven method of deploying a ShoreTel system across multiple sites. All IP telephony endpoints (such as ShoreTel servers), ShoreTel Voice Switches, and IP telephones) should participate in the same private network, with firewalls between ShoreTel equipment and the public Internet. If needed, you can elect to open access to the ShoreTel server to access ShoreTel Director via HTTP using the same precautions you would when exposing any critical web services server to the public network. Configuring firewalls to function correctly with VoIP traffic is very difficult. ShoreTel does not recommend deploying ShoreTel equipment across firewalls.
ShoreTel 13.1
77
3.10 Media Encryption

In addition to using a VPN or a firewall, another method of enhancing the security on your network is to enable the ShoreTel media encryption feature. Media encryption, as the name suggests, encrypts calls between users on a ShoreTel system. The encryption scrambles communications between callers so an intruder on the network cannot eavesdrop on the conversation. The ShoreTel encryption algorithm utilizes dynamically generated keys to encrypt the RTP data for the media stream. The payload inside the RTP packets is encrypted by the sending party, and the transmission is decrypted by the receiving party. The ShoreTel algorithm was selected due to its reliability, simplicity and its efficiency it places very little burden on the switch's CPU even during maximum loads.
3.10.1 Details:
TCP/IP and UDP packet headers are not encrypted. Only calls inside a ShoreTel network will be encrypted. Once the call passes
through TDM or analog trunks or via SIP, the encryption is stripped away and the conversation is no longer encrypted. receiving parties at the time of call setup. If the call starts off without encryption, and encryption is enabled during the middle of a call, the call will remain unencrypted. calls. Encryption is essentially transparent, and the user will not know if the call is being encrypted or not. attendant are not encrypted.
The encryption algorithm handles the key exchange between the sending and
There is no difference in the user experience for encrypted and unencrypted Encryption is not supported on the SoftSwitch, so calls to voice mail or auto
3.10.2 Supported Platforms

The media encryption feature is supported on the hardware shown in Table 3-15. Table 3-15 Platform Type Switches Platforms Supporting Media Encryption Model ShoreTel 1U Half-width voice switches ShoreTel 1U Full-width voice switches
78
Table 3-15 Platform Type IP Phones
Platforms Supporting Media Encryption Model IP110 IP115 IP212k IP230 IP230g IP265 IP560 IP560g IP565g IP655
For instructions on enabling media encryption, refer to the section on Call Control Options in the ShoreTel System Administration Guide.
3.11 Session Initiation Protocol (SIP)

Deploying SIP does not involve special network requirements. The general system requirements should be adequate for SIP support. Note the following points:
If SIP devices (SIP phones) have a static configuration, they are supported
behind NAT (Network Address Translation).
To communicate with a SIP device or service provider providing IP trunks over

the Internet, the network must be able to pass SIP traffic through a firewall. This requires a SIP application layer gateway a feature provided by some firewall vendors.
SIP signaling uses UDP port 5060. When using SIP, the RTP port for the voice media stream is dynamic and the SIP
endpoints may not always use the same ports to exchange information (in contrast with ShoreTels proprietary protocol, which always uses port 5004). Thus, if you are using SIP, you must deselect the Always Use Port 5004 for RTP check box on the Call Control Options page in Director so that it is not fixed at 5004.
3.12 Example Network Topologies

3.12.1 Single-Site Implementation
Figure 3-3 is an example of a simple, single-site implementation.
ShoreTel 13.1
79
Figure 3-3
Single Site
3.12.2 Multisite Implementation

Figure 3-4 is an example of a multisite implementation with various WAN technology choices.
Figure 3-4
MultiSite Options
80
3.13 Computing Admission Control Bandwidth

This section discusses how to compute the admission control bandwidth for the site you are configuring on the Site edit pagethat is, the appropriate value for the Admission Control Bandwidth parameter. If you want to determine the admission control bandwidth for your site and the information is not available in this section, use one of the following formulas:
To determine the admission control bandwidth:

Bandwidth = (# of calls) x (bandwidth/call)
To determine the number of calls supported with a specific admission control

bandwidth value: # of calls = (admission control bandwidth) / (bandwidth/call) ShoreTel automatically negotiates the proper voice encoder at call setup. For calls between sites, the call control software requests the voice encoder based on what is selected for inter-site voice encoding as defined on the Call Control Options edit page. The call control software will then make sure both endpoints on the call can support the requested voice encoder. For instance, for G.729a voice encoding to be used between two sites, the inter-site voice encoding must be set to G.729a and the ShoreTel voice switches at each end of the call must be G.729a-capable.
3.13.1 WAN Bandwidth per Call (Full Duplex) Without cRTP

Table 3-16 defines the bandwidth, including IP overhead, that is used for each voice call between sites when RTP Header Compression (cRTP) is not being used. The bandwidth depends on the voice encoding used. For example:
If you want to support 10 calls between this site and all other sites, and G.729a If you set your admission control bandwidth to 768 Kbps and G.729a voice
voice encoding is used, set the admission control bandwidth to 260 Kbps. Before you enter this value, make sure the bandwidth is available at this site. encoding is used, you can support up to 29 calls between this site and all other sites.
ShoreTel recommends that you configure the admission control bandwidth to be less than the bandwidth of the actual WAN link. This provides sufficient bandwidth for call control signaling and other data traffic. Table 3-16 Bandwidth in Kbps per Number of Calls 1 2 3 4 5
ShoreTel 13.1
Bandwidth Without cRTP
Linear 146 292 438 584 730
G.711 82 170 255 340 425
ADPCM 52 104 156 208 260
G.729a 26 52 78 104 130

81
Table 3-16 Bandwidth in Kbps per Number of Calls 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
Bandwidth Without cRTP (Continued)
Linear 876 1022 1168 1314 1460 1606 1752 1898 2044 2190 2336 2482 2628 2774 2920 3066 3212 3358 3504 3650 3796 3942 4088 4234 4380
G.711 510 595 680 765 850 935 1020 1105 1190 1275 1360 1445 1530 1615 1700 1785 1870 1955 2040 2125 2210 2295 2380 2465 2550
ADPCM 312 364 416 468 520 572 624 676 728 780 832 884 936 988 1040 1092 1144 1196 1248 1300 1352 1404 1456 1508 1560
G.729a 156 182 208 234 260 286 312 338 364 390 416 442 468 494 520 546 572 598 624 650 676 702 728 754 780
3.13.2 WAN Bandwidth per Call (Full Duplex) with cRTP

Some routers support a feature called RTP Header Compression (cRTP) that significantly reduces the amount of IP overhead associated with voice over IP. Table 3-17 defines the bandwidth used between sites when cRTP is being used. For example:
If you want to support 10 calls between this site and all other sites, and G.729a
voice encoding is used, set the admission control bandwidth to 120 Kbps. Before you enter this value, make sure the bandwidth is available at this site.
82
If you set the admission control bandwidth to 256 Kbps and G.729a voice
encoding is used, you can support up to 21 calls between this site and all other sites.
ShoreTel recommends that you configure the admission control bandwidth to be less than the bandwidth of the actual WAN link. This provides sufficient bandwidth for call control signaling and other data traffic. Table 3-17 Bandwidth with cRTP
Bandwidth in Kbps per Number of Calls Linear 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 132 264 396 528 660 792 924 1056 1188 1320 1452 1584 1716 1848 1980 2112 2244 2376 2508 2640 2772 2904 3036 3168 3300 3432 3564
G.711 68 136 204 272 340 408 476 544 612 680 748 816 884 952 1020 1088 1156 1224 1292 1360 1428 1496 1564 1632 1700 1768 1836
ADPCM 38 76 114 152 190 228 266 304 342 380 418 456 494 532 570 608 646 684 722 760 798 836 874 912 950 988 1026
G.729a 12 24 36 48 60 72 84 96 108 120 132 144 156 168 180 192 204 216 228 240 252 264 276 288 300 312 324
ShoreTel 13.1
83
Table 3-17
Bandwidth with cRTP (Continued)
Bandwidth in Kbps per Number of Calls Linear 28 29 30 3696 3828 3960
G.711 1904 1972 2040
ADPCM 1064 1102 1140
G.729a 336 348 360
To set admission control, determine the expected number of simultaneous intra-site calls for a site and multiply this number by the bandwidth required for each call for your selected inter-site encoding. When admission control is set this way, calls routing between sites will be blocked if placing the call would exceed the number of calls supported by the configured bandwidth. For information about ShoreTels Admission Control feature, see "Admission Control in the Wide Area Network" section on page 64.
3.13.3 Setting Admission Control

The Admission Control Bandwidth parameters are set in the Site edit page of ShoreTel Director. For information on setting this parameter, see the chapter on configuring sites in the ShoreTel System Administration Guide.
84
Chapter 4
Routing Calls
The purpose of this chapter is to help with identifying the appropriate routing for inbound and outbound calls. This information is important for determining the requirements for configuration and trunking. The topics discussed include:
Recommendations on page 85 Hunt Groups on page 86 Direct All Calls to an Auto-Attendant on page 86 Direct All Calls to a Live Operator on page 88 Direct All Calls to Extensions on page 92 Blended Call Routing on page 93 Analyze Outbound Call Routing on page 96
Before installing a voice communications system, one of the most important decisions to make is how to route incoming calls. The voice communications includes the inbound calls to the ShoreTel customer, its individual employees, or a group of employees. The consideration is important for routing calls to their intended destination and also routing calls when they cannot reach their destination. Calls that fail to reach the intended person or group can then go to an AutoAttendant, operator, off-site number, pager, cell phone, or voice mail? Another consideration is the outbound call routing. Every site has trunks that support outbound and inbound calls, and the outbound calling behavior also needs planning. At least one trunk at a site must also be able to support emergency calls. For information about other aspects of designing a voice communications network, see Planning and System Design on page 23, Call routing for a ShoreTel Enterprise Contact Center Solution is a separate task. This document does not describe Enterprise Contact Center. For more information on the ShoreTel Enterprise Contact Center Solution, refer to the ShoreTel Enterprise Contact Center Solution Administration Guide.
4.1
Recommendations
Consider the following recommendations when designing your call flow plan:
Determine how calls should reach employees and workgroups. You need to
identify the desired call routing for inbound calls at each site.
Identify contingencies, such as alternate plans in the event that the receptionist
has an unplanned absence, or the physical phone fails. For example, creating
ShoreTel 13.1
85
Chapter 4: Routing Calls
hunt groups can ensure an operator is available if the receptionist or workgroup is unavailable.
Consider the inter-site call flow, such as your operators or receptionists role in Identify call flow early. Do not wait until the last minute, or try to identify the
call flow the day of cut-over.
handling inbound calls, and the role of others who are not physically present at the main site.
Interview the key members of your organization (workgroups, operators, Create an off-hours call routing plan.
assistants, and executives) to determine their individual preferences and needs, and make sure they agree with any decisions that affect their respective areas.
4.2
Hunt Groups
Hunt groups allow you to route calls to a list of extensions. Hunt groups can be accessed through an extension, DID, and/or DNIS. Hunt groups are supported by ShoreTel Voice Switches and remain available even when connectivity to the Headquarters server is lost. A single switch can host up to 8 hunt groups and a maximum of 16 hunt group extensions per switch. A hunt group can be used as the backup destination for an operator or workgroup, so that basic hunting occurs even when the operator or workgroup is not reachable. To maximize reliability, assign hunt groups to a switch close to the majority of the members and/or trunks associated with the hunt group. Hunt groups can be used for:
Backup Routing for a workgroup

Hunt groups can be used when the workgroup server is not reachable because of a network outage or admission control. When the hunt group is set to offer each member a single call at a time, then call offering is similar to a workgroup.
Hunt Group as a Call Forward Destination

In a small office where individuals generally receive calls directly, users may want someone in the office to answer calls when they are unable to answer. Hunt groups can provide alternate destinations in this case.
Distribution of Calls to Backup Operators

A hunt group can provide backup operators for the primary operator who handles calls to a main company number.
Common Line Monitoring

A hunt group can enable users to monitor a phone line. For example, multiple operators can monitor a line and answer calls at the same time.
4.3
Direct All Calls to an Auto-Attendant

You can direct all inbound calls to the automated attendant, and prompt the calling party to route the call, based on menu options. Auto-attendant answering is typically used by smaller companies and smaller locations that do not choose to use direct inward dial (DID) numbers. See Figure 4-1 for an illustration of auto-attendant call flow.
86
Figure 4-1
Auto-Attendant Call Routing
Organize the auto-attendant with options for various departments. In addition, include an out for callers if they must speak to a live attendant or have a rotary telephone. This destination must be one that will always be answered. In many cases, it is a receptionists extension that is staffed at all times, or a night bell that can be answered by any employee. If you route calls to a receptionists position that is not always staffed or the receptionist needs to be mobile, consider installing a cordless telephone for the receptionist to wear while roaming around the office. If this is not an option, make sure the receptionists call handling modes are set up appropriately.
4.3.1
Trunk Considerations
An auto-attendant menu can be reached through analog loop-start, digital loop-start, and T1/E1 PRI trunks by pointing the trunk group at the desired menu. You can also reach a specific menu using DID or DNIS entries received over analog wink-start, digital wink-start, or T1/E1 PRI trunks. The ShoreTel system supports International Caller ID, Caller ID Name, Caller ID Number, ANI, and DNIS. The Caller ID and trunk group or DNIS information is provided to the user to assist in answering the call.
ShoreTel 13.1
87
4.3.1.1
Call Routing and Collecting Caller ID Information

The switch delays each inbound loop-start call by 1.5 rings to collect caller ID information before ringing the users telephone. This allows caller ID information to reach the users client at the time the call rings the extension, rather than after it rings the extension. Features available on trunks vary by trunk type. See Trunk Planning and Ordering on page 97, for more information.
4.3.2
After-Hours Call Routing

For after hours, weekends, and holidays, consider how your call flow will change. Typically, a different prompt is played, since callers are routed directly to voice mail rather than to workgroups or the operator.
4.3.3
Example of Auto-Attendant Call Routing

In the call flow example shown in Figure 4-1 on page 87, all calls are received by the auto-attendant. The calling party can choose to be directed to:
The support workgroup by dialing a digit.

Calls are presented to the support workgroup with a mailbox that provides coverage. The calling party can dial 0 in the mailbox to reach the workgroup assistant, or 9 to return to the auto-attendant.
An employee using Dial by Number or Dial by Name.

Calls are presented to the employee with a mailbox that provides coverage. The calling party can dial 0 in the mailbox to reach the employees personal assistant, or 9 to return to the auto-attendant.
The operator by dialing the digit 0.

Calls are presented to the operator. If the operator does not answer, a backup operator provides coverage using the operators call handling modes. If the backup operator does not answer, a mailbox provides coverage, and the calling party can dial 0 in the mailbox to reach the operators personal assistant, or 9 to return to the auto-attendant. In this example, the workgroup, users, and operator route calls directly to voice mail after hours.
4.4
Direct All Calls to a Live Operator

Some companies choose to answer all inbound calls during business hours with a live operator to give callers a more personal experience. If you use a live operator, the most important thing to remember is that the operators telephone must always be staffed. ShoreTel recommends the following:
Use the ShoreTel Communicator - Operator Access software, because the
standard telephone without ShoreTel Communicator manages only a single call at a time. When a second call arrives, using the Flash button invokes call waiting, generating a swap hold situation in which calls cannot be transferred. This problem is eliminated when you use the ShoreTel Communicator Operator Access software. button box. The button box provides additional shortcut functions for ShoreTel
If the organization is a large one, consider using the ShoreTel IP Phone -BB24
88
IP Phone multiline phones. The button box behaves like an additional set of 24 custom buttons that can be used by the operator to quickly and easily route calls to executives and to other employees who receive a high volume of phone calls. A maximum of 4 BB24 devices can be connected to each multiline phone.
If the operator does not receive a lot of telephone calls and is required to roam
around the office to deliver mail, pick up faxes, make copies, and so on, a twoline cordless telephone can be used. The first line is reserved for incoming calls, while the second line is the operators personal extension. call.
Create hunt groups to ensure someone is always available to take an incoming You can choose to have calls initially routed to the operator and then forwarded
to the auto-attendant after a fixed number of rings. Operators work in either of two modes: Answer all calls and transfer them to the appropriate destination. Answer all calls and hold them until the parties are found. If your operator works in the second mode, you should consider installing an overhead paging system or should consider using the Paging Groups feature (see the ShoreTel System Administration Guide for details on Paging Groups). The ShoreTel system supports single-zone overhead paging on a per-site basis, using the audio output jack on the switches supplied with the jack. When you need multiple-zone paging, please use ShoreTels online knowledge base, to access the application note on paging on ShoreTels web site at www.shoretel.com.
4.4.1
The operator can be reached through analog loop-start, digital loop-start, and T1/E1 PRI trunks by pointing the trunk group directly at the operator. You can also reach the operator using DID or DNIS entries received over analog wink-start, digital winkstart, or T1/E1 PRI trunks. The ShoreTel system supports International Caller ID, Caller ID Name, Caller ID Number, ANI, and DNIS. The Caller ID and trunk group or DNIS information is provided to the user to assist in answering the call. Features available on trunks vary by trunk type. See Trunk Planning and Ordering on page 97, for more information.
4.4.2

If you route all calls to the operators extension, auto-attendant scheduling does not apply; only those calls routed to the auto-attendant use the schedule. Therefore, if you want to use the off-hours, holiday, and custom schedules, set the operators call handling mode to forward all calls to the auto-attendant when the operator is unavailable.
4.4.3
Example Using Hunt Groups

To route calls to a prioritized list of backup operators, create hunt groups with users who can serve as backup operators. In this scenario, a primary operator who handles calls to a main company number requires one or more secondary operators to receive the calls when the primary operator becomes too busy.
ShoreTel 13.1
89
To create a hunt group to back up the primary operator:
Create a hunt group with backup operators. Enter the main operator and all the backups as members of the hunt group in
the order in which they are to serve as backups.
Set the hunt group for multiple calls to be hunted to a given member.
she can receive. When there are incoming calls to the hunt group, the primary operator is offered the calls first. The operator may be offered multiple calls concurrently up to the limit of his or her call stack. If a members call stack is full, the member is skipped and that particular call is not be offered again (unless the hunt group is set to hunt forever and no member picks up the call before the member is reached again in the hunt list). If a member of the operator group does not answer the hunt call, the call is offered to the next member after the number of configured rings. Thus, even if the primary operator has room on his or her call stack, the call is offered to the next member in the list when the operator does not answer the call in time. For more information on Hunt Groups, see the "Hunt Groups" section on page 152.
Set the call stack size for each of the users to control the number of calls he or
4.4.4
Example of Operator Call Routing

In the example call flow shown in Figure 4-2, all calls are received by the operator, who then transfers the calls to the appropriate destination.
90
Figure 4-2
Operator Call Routing
Calls are transferred to the support workgroup with a mailbox that provides
coverage. The calling party can dial 0 in the mailbox to reach the workgroup assistant, or 9 to return to the auto-attendant.
Calls are transferred to the employees with a mailbox that provides coverage.
The calling party can dial 0 in the mailbox to reach his or her personal assistant, or 9 to return to the auto-attendant.
If the operator does not answer, a backup operator provides coverage, using the
operators call handling modes. If the backup operator does not answer, a mailbox provides coverage and the calling party can dial 0 in the mailbox to reach the operators personal assistant, or 9 to return to the auto-attendant. In this example, after-hours call routing is handled by an auto-attendant in a very similar fashion to the previous example (Figure 4-1 on page 87). To start after-hours call handling, the operator changes his or her call handling mode. This can be done
ShoreTel 13.1
91
automatically using Microsoft Outlook Calendar in conjunction with Automated Call Handling (although it does require the operators personal computer to remain connected with Microsoft Outlook running on it).
4.5
Direct All Calls to Extensions

ShoreTel recommends using Direct Inward Dial (DID) trunks so that callers can dial extensions directly without having to go through the operator. This provides the most efficient, professional call handling experience to your customers. In the event that an individual is not available, preconfigured call handling modes route callers. This routing might include a cellular telephone, a pager, an alternate extension, or a personal assistant. Additionally, consider using the voice mail notification capabilities of the ShoreTel system when employees are not able to answer the telephone but need to stay in touch. Even if you choose to direct all calls to extensions, you should still configure the auto-attendant for Dial by Number, Dial by Name, and zero out to an operator.
4.5.1
When using Direct Inward Dial, you must use analog wink-start, digital wink-start, SIP or T1/E1 PRI trunks. The ShoreTel system can receive Automatic Number Identification (ANI) over analog and digital wink-start trunks as well as Caller ID Number over T1/E1 PRI. Features available on trunks vary by trunk type. See Trunk Planning and Ordering on page 97, for more information.
4.5.2

By routing all calls to the individual extensions, each individual user and workgroup defines its after-hours call handling.
4.5.3
Example of Direct Inward Dial Call Routing

In the illustration shown in Figure 4-3, all calls are received by workgroups or by individuals.
92
Figure 4-3
Direct Inward Dial Call Routing
Calls are routed directly to the support workgroup with a mailbox that
provides coverage. The calling party can dial 0 in the mailbox to reach the workgroup assistant or 9 to return to the auto-attendant.
Calls are routed directly to the employees with a mailbox that provides
coverage. The calling party can dial 0 in the mailbox to reach his or her personal assistant, or 9 to return to the auto-attendant. mailboxes or the automated attendant. In this example, after-hours call routing is received by the workgroups and individual employees.
An operator provides limited call handling functions from individual
4.6
Blended Call Routing

Communication systems typically use a mix of automated, live, and DID call routing to maximize user satisfaction as well as efficiency and flexibility. This usually includes taking a published main telephone number and routing it to the autoattendant, as well as installing DID lines that route calls directly to different workgroups and individual employees.
ShoreTel 13.1
93
4.6.1
An auto-attendant menu can be reached through analog loop-start, digital loop-start, SIP, and T1/E1 PRI trunks by pointing the trunk group at the desired menu. You can also reach a specific menu using DID or DNIS entries received over analog wink-start, digital wink-start, or T1/E1 PRI trunks. The operator can be reached through analog loop-start, digital loop-start, and T1/E1 PRI trunks by pointing the trunk group directly at the operator. You can also reach the operator using DID or DNIS entries received over analog wink-start, digital winkstart, or T1/E1 PRI trunks. The ShoreTel system supports International Caller ID, Caller ID Name, Caller ID Number, ANI, and DNIS. The Caller ID and trunk group or DNIS information will be provided to the user to assist in answering the call. When using Direct Inward Dial, you must use analog wink-start, digital-wink start, or T1/E1 PRI trunks. The ShoreTel system can receive Automatic Number Identification (ANI) over analog and digital wink-start trunks as well as Caller ID Number over T1/E1 PRI. Features available on trunks vary by trunk type. See Trunk Planning and Ordering on page 97, for more information.
4.6.2

For after hours, weekends, and holidays, you should consider how your call flow will change. Typically, a different prompt should be played, since callers are routed directly to voice mail rather than to workgroups or the operator. If you route all calls to the operators extension, auto-attendant scheduling does not apply; only those calls routed to the auto-attendant use the schedule. Therefore, when you want to use the off-hours, holiday, and custom schedules, set the operators call handling mode to forward all calls to the auto-attendant when unavailable. By routing all calls to the individual extensions, each individual user and workgroup defines its after-hours call handling.
4.6.3
Example of Blended Call Routing

In the example shown in Figure 4-4, a mix of inbound call routing is used.
94
Figure 4-4
Blended Call Routing
Calls are routed directly to the support workgroup using DID and DNIS entries
and routed through the auto-attendant with a mailbox that provides coverage. The calling party can dial 0 in the mailbox to reach the workgroup assistant, or 9 to return to the auto-attendant.
Calls are routed directly to the employees using DID and routed through the
The calling party can dial 0 in the mailbox to reach his or her personal assistant, or 9 to return to the auto-attendant.
auto-attendant using Dial by Number and Dial by Name with a mailbox that provides coverage.
mailboxes or the auto-attendant. In this example, after-hours call routing changes at the auto-attendant and for each of the workgroups, employees, and the operator, because each workgroup defines its own after-hours call routing.
An operator provides limited call handling functions from individual
ShoreTel 13.1
95
4.7
Analyze Outbound Call Routing

In general, you should have trunks at every site that support both outbound and inbound calling. Here are some general comments about outbound trunking:
ISDN PRI provides the most feature-rich inbound and outbound calling
experience. This includes the support for Caller ID, DID, and DNIS. Caller ID Number is supported for both inbound and outbound calls. Caller ID Name is supported only on inbound NI-2 trunks (with the exception of outbound calls to offsystem extensions).
SIP trunks can be used to place outbound calls. Analog wink-start trunks do not support outbound calls. You may want to purchase some analog loop-start trunks for emergency dial
tone in case of total power failure. For more information, see "Analog Loop-Start Trunks (North America)" section on page 98. the Network Call Routing feature. (This allows users to access local and nearby area codes at one site from another site.) voice system.
Calls can be automatically routed across your wide area network (WAN) using You need to plan for emergency calls (such as 911 in the United States) on your
The ShoreTel system supports all the necessary signaling for emergency calls. Please see the appendix on emergency 911 operations in the ShoreTel System Administration Guide for information on how to configure your system for emergency calls. If your system uses three-digit extensions, ShoreTel recommends that you do not assign x11 extensions to users. For more information, see Trunk Planning and Ordering on page 97, and .
96
Chapter 5
Trunk Planning and Ordering

This chapter explains the features and functionality of trunks on the ShoreTel system, so you can plan and order your service. The topics discussed include:
Recommendations on page 97 Reviewing and Selecting Trunk Types on page 97 Understanding Trunk Features on page 103 Performing Traffic Calculations on page 108 Ordering Telephone Service on page 108
5.1
Recommendations
The following recommendations assist you in determining your trunk requirements and ordering your trunks from your service provider:
Make sure you order telephone service early. T1 and PRI service can take up to
one or two months to install.
If you are reusing Centrex lines, be sure to change your old service and remove
call waiting, call forwarding, and voice mail.
When provisioning PRI service, be sure to confirm the protocol being used (NI2, 4ESS, 5ESS, or DMS-100). Make sure that neither Non-Facility Associated Signalling (NFAS) nor the Call-by-Call feature of the 4ESS is being used, since they are not supported on the ShoreTel system.
5.2
Reviewing and Selecting Trunk Types

Trunks provide a connection from the ShoreTel system to a service provider for the purpose of making and taking calls to and from external parties. Table 5-1 shows which trunk types are supported on individual ShoreTel Voice Switches. The next section provides more detailed information about the various trunk features.
ShoreTel 13.1
97
Chapter 5: Trunk Planning and Ordering
Table 5-1
Supported Trunk Types Analo g LoopStart (Nort h.Ame r.) Yes No Yes Yes No No Yes No Yes Yes Yes No No
Voice Switch ShoreTel 90 ShoreTel 90BRI ShoreTel 50 ShoreTel 30 ShoreTel 220E1 ShoreTel 220T1 ShoreTel 220T1A ShoreTel T1k ShoreTel 120 ShoreTel 60 ShoreTel 40 ShoreTel E1 ShoreTel T1
Analo g LoopStart EMEA Yes No Yes Yes No No No No No No No No No
Anal Digit og al Win Loop k-Start Start No No No No No Yes Yes Yes No No No No Yes Yes No Yes Yes No No No No Yes Yes Yes No No
Digit al Win kT1 Start PRI No No No No No Yes Yes Yes No No No No Yes No No No No No Yes Yes Yes No No No No Yes
E1 PRI No No No No Yes No No No No No No Yes No
SIP Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes No No
BRI No Yes No No No No No No No No No No No
5.2.1
Analog Loop-Start Trunks (North America)

Analog loop-start trunks are typically used for inbound calls to a main telephone number that are directed to an auto-attendant menu, company operator, or workgroup. A caller can route a call from the auto-attendant to a user extension by entering the extension number or by spelling the users name from the telephone keypad. Analog loop-start trunks are also used to make outbound calls. Analog loop-start trunks support:
Inbound calls Outbound calls Caller ID number Caller ID name Caller ID blocking
98
Analog provisioning is provided by the loop-start protocol and Dual-Tone MultiFrequency (DTMF) signaling. Analog loop-start trunks are used to provide power-fail transfer to selected telephones for instance, to the operator, security station, executives, and so on. When there is a complete power failure, including loss of UPS power backup, powerfail transfer connects a specified trunk port to a specified extension port. This powerfail transfer ability provides a dial tone for making and taking critical calls in the event of power failure. Refer to the ShoreTel System Administration Guide for more information about the power-fail transfer port on each ShoreTel Voice Switch that supports this feature. Centrex lines are analog lines that can be used as analog loop-start trunks. Your organization may already have these installed, and want to use them instead of ordering new loop-start trunks. If you have Centrex lines and do not want to change your primary company telephone number, you can keep Centrex lines. Centrex lines support Caller ID. Be sure to remove the Centrex features, including call waiting, call forward, and voice mail. EMEA analog loop start trunk support, based on the TBR 21 standard, is supported on all 1U Half Width ShoreTel voice switches. BT type 1 (on hook) caller ID support is based on SIN 227 and SIN 242 standards in the UK.
5.2.2
Analog Loop-Start Trunks (EMEA)

Analog Loop-Start trunks are supported in Europe, the Middle East, and Africa. These trunks use the TBR 21 standard. Analog Loop-Start Trunks (EMEA) are typically used for inbound calls to a main telephone number that are directed to an auto-attendant menu, company operator, or workgroup. A caller can route a call from the auto-attendant to a user extension by entering the extension number or by spelling the users name from the telephone keypad. Analog loop-start trunks are also used to make outbound calls. Analog loop-start trunks (EMEA) support:
Inbound calls Outbound calls

BT type 1 (on hook) caller ID support is based on SIN 227 and SIN 242 standards in the UK. Analog provisioning is provided by the loop-start protocol and Dual-Tone MultiFrequency (DTMF) signaling. Analog loop-start trunks are used to provide power-fail transfer to selected telephones for instance, to the operator, security station, executives, and so on. When there is a complete power failure, including loss of UPS power backup, the ShoreTel Voice Switches provides power-fail transfer. Refer to the ShoreTel System Administration Guide for the power-fail transfer port on each ShoreTel Voice Switch that supports this feature. This power-fail transfer ability provides a dial tone for making and taking critical calls in the event of power failure. Centrex lines are analog lines that can be used as analog loop-start trunks on the ShoreTel Voice Switches. Your organization may already have these installed, and want to use them instead of ordering new loop-start trunks. If you have Centrex lines
ShoreTel 13.1 99
and do not want to change your primary company telephone number, you can keep Centrex lines. Centrex lines support Caller ID. Be sure to remove the Centrex features, including call waiting, call forward, and voice mail.
5.2.3
Digital Loop-Start Trunks

Digital loop-start trunks are typically used for inbound calls to the main telephone number that are directed to an auto-attendant menu, company operator, or workgroup. A caller can route a call from the auto-attendant to a user extension by entering the extension number or by spelling the users name from the telephone keypad. Digital loop-start trunks are also used to make outbound calls. Digital loop-start trunks support:
Inbound calls Outbound calls Caller ID number Caller ID name Caller ID blocking
Digital provisioning is provided by the loop-start protocol and Dual-Tone MultiFrequency (DTMF) signaling. ShoreTel Voice Switches support
ESF or D4 framing formats B8ZS or AMI line coding.
5.2.4
Analog Wink-Start Trunks (Analog DID)

Analog wink-start trunks allow external callers to dial a users phone number directly, without having to use an auto-attendant or operator. Analog wink-start trunks support only inbound calls; they are not capable of handling outbound calls. Analog wink-start trunks support:
Inbound calls (outbound calls are not supported) ANI DID DNIS
Analog provisioning is provided by the wink-start protocol and Dual-Tone MultiFrequency (DTMF) signaling. If ANI is being used, the star (*) key must be used to delimit the ANI digits from the DID/DNIS digitsthat is:
<DID> <DNIS> *<ANI>*<DID/DNIS>*

100
5.2.5
Digital Wink-Start Trunks

Digital wink-start trunks allow external callers to dial a users phone number directly, without having to use an auto-attendant or operator. Digital wink-start trunks support both inbound and outbound calls. Digital wink-start trunks support:
Inbound calls Outbound calls ANI DID DNIS

Digital provisioning is provided by the wink-start protocol (often called E&M winkstart) and Dual-Tone Multi-Frequency (DTMF) signaling. ShoreTel Voice Switches support
ESF or D4 framing formats B8ZS or AMI line coding

If ANI is being used, the star (*) key must be used to delimit the ANI digits from the DID/DNIS digitsthat is:
5.2.6
BRI Trunks
BRI trunks are flexible trunks that support both inbound and outbound calls. PRI trunks support:
Inbound calls Outbound calls DID DNIS Caller ID number Caller ID name is supported for NI-2 configured trunks QSIG Calling name is supported if the standard is similar to NI2 Inbound calling name is fully supported, but outbound calling name is only
supported for Off-System Extension calls
ShoreTel 13.1
101
Digital provisioning is provided by the PRI protocol and D-channel signaling. ShoreTel Voice Switches support:
DMS-100, 4ESS, 5ESS, and NI-2 signaling types ESF or D4 framing formats B8ZS or AMI line coding.
The NFAS and Call-by-Call features are not supported.
5.2.7
T1 PRI Trunks
T1 PRI trunks are flexible trunks that support both inbound and outbound calls. PRI trunks support:
Inbound calls Outbound calls DID DNIS Caller ID number Caller ID name is supported for NI-2 configured trunks QSIG Calling name is supported if the standard is similar to NI2 Inbound calling name is fully supported, but outbound calling name is only
supported for Off-System Extension calls Digital provisioning is provided by the PRI protocol and D-channel signaling. ShoreTel Voice Switch supports
DMS-100, 4ESS, 5ESS, and NI-2 signaling types ESF or D4 framing formats B8ZS or AMI line coding.
The NFAS and Call-by-Call features are not supported.
5.2.8
E1 PRI Trunks
E1 PRI trunks are flexible trunks that support both inbound and outbound calls for international locations. E1 PRI trunks support:
Inbound calls Outbound calls DID DNIS

102
Caller ID number Caller ID name is supported for NI-2 configured trunks QSIG Calling name is supported if the standard is similar to NI2 Inbound calling name is fully supported, but outbound calling name is only
supported for Off-System Extension calls The ShoreTel Voice Switches support PRI signaling using Euro-ISDN as well as other international protocols. See International Planning and Installation on page 311.
5.2.9
SIP Trunks
SIP trunks are flexible trunks that support both inbound and outbound calls. SIP trunks are logical trunk end points that only handle SIP call control. Media flows directly between the call initiator and the call terminator. SIP trunks support:
Inbound calls Outbound calls Extension, Tandem, and default destinations for inbound calls Caller ID name Caller ID number DID DNIS
By default, the Enable SIP Info for G711 DTMF signaling check box is off. This check box must be enabled for ShoreTel-to-ShoreTel SIP tie trunks or for SIP devices that do not support RFC 2833 for G711.
5.3
Understanding Trunk Features

The ShoreTel system supports several different trunk types and trunk features. It is very important to understand the features available on these trunks, since some services are mutually exclusive. Table 5-2 shows each trunk type and the associated features.
ShoreTel 13.1
103
Table 5-2
Trunk Features Analo g LoopStart N.Am. Yes Yes No No Analo g LoopStart EMEA No No No No Digita l LoopStart Yes Yes No No Analo g WinkStart Yesa No Yes Yes Digita l Wink- T1 E1 Start PRI PRI SIP Yesa No Yes Yes Yes Yes
b
Feature Inbound:
Caller ID Number Caller ID Name Direct Inward Dial (DID) Dialed Number Identification Service (DNIS)
BRI Yes Yes Yes Yes
Yes Yes Yes Yes
Yes Yes Yes Yes
Yes Yes
Outbound:
Caller ID Blocked Caller ID Unblocked Caller ID Blocking Override (*67, *82)
Yes (CO) Yes (CO) Yesc
Yes (CO) Yes (CO) No
Yes (CO) Yes (CO) Yesc
N/A N/A N/A
Yes (CO) Yes (CO) No
Yes Yes Yes
Yes Yes No
Yes Yes Yes
Yes Yes No
a. Via Automatic Number Identification (ANI). b. Caller ID Name is supported for NI-2 configured trunks. c. *67 and *82 codes do not work if the CO requires a pause between the code and the dialed number.
Legend to Table 5-2
YesFeature is supported. NoFeature is not supported. Yes (CO)Feature is provided by the central office (CO) or legacy PBX. N/AOutbound calls are not supported on analog wink-start trunks.
5.3.1
Caller ID Number
Caller ID Number delivers to the ShoreTel system the number of the calling party, which is displayed in the ShoreTel Communicator as well as on Caller ID compatible telephones. The delivery of the caller ID number can be blocked by the calling party. The caller ID number is delivered unless the calling party has blocked the call (in which case the call is marked as Blocked), or the service provider does not have the information (in which case the call is marked as Unavailable).
104
Caller ID Number has the following limitations:
The calling party may block his or her caller ID number. The calling party may be calling from a business and the calling number may
be incorrect.
The calling party may be calling from someone elses number.

Caller ID Number is available on analog loop-start, digital loop-start, SIP, T1 PRI, and E1 PRI trunks. Two different Caller ID Number formats are used to deliver caller information via loop-start trunks: Single Data Message Format (SDMF) and Multiple Data Message Format (MDMF). SDMF provides the calling number, while MDMF provides any combination of calling name and number. The ShoreTel voice switches support both SMDF and MDMF dynamically, without the need for configuration. When PRI is used, the caller ID number is delivered as a D-Channel message. ShoreTel supports International Caller ID, ensuring that when a switch is configured for a certain site (e.g. Spain), the International ID information is automatically filled in as appropriate for that country. The feature is transparent from the user's standpoint, and no configuration is necessary.
5.3.2
Caller ID Name
Caller ID Name delivers the name of the calling party to the ShoreTel system. The name is displayed in the ShoreTel Communicator as well as on any telephones that support caller ID Name. By default, the caller ID name is delivered unless the calling party has blocked the transfer of this information (in which case the call is marked as Blocked). If the service provider does not have the information, the call is marked as Unavailable. Caller ID Name is available on analog loop-start and digital loop-start trunks, as well as SIP, T1 PRI, and E1 PRI trunks and is only supported on IP phone and analog phones in North America. This feature is not supported on analog phones in other countries. When using NI-2 signaling on PRI trunksfor example in a tie-trunk scenario Caller-ID Name is now also captured when available on all inbound calls. For outbound calls, Caller-ID Name is delivered for calls that are made to off-system extensions, but not for outbound calls.
5.3.3
Automatic Number Identification (ANI)

Automatic Number Identification (ANI) delivers the number of the calling party to the ShoreTel system. Although similar to Caller ID Number, ANI is tariffed differently and is not subject to the same blocking restrictions as Caller ID Number. For example, when you purchase ANI services from your service provider, you are always delivered the calling number for 800-number calls. Business practices can vary from region to region. ANI is available on analog wink-start and digital wink-start trunks.
ShoreTel 13.1
105
When ANI is being used, the star key (*) must be used to delimit the ANI digits from the DID/DNIS digitsthat is, *<ANI>*<DID/DNIS>*.
5.3.4
Direct Inward Dial (DID)

Direct Inward Dial (DID) allows extensions (users, menus, workgroups, route points, etc.) on the system to be accessed directly, without the need of an auto-attendant or operator. This is particularly useful when users on the system want their own telephone number. DID is available on analog wink-start, digital wink-start, PRI and SIP trunks. DID numbers are ordered in blocks of 20 or more 10-digit telephone numbers. These numbers are assigned to a customer and are routed to a wink-start, PRI or SIP trunk connected to a voice switch. When a call is made, the service provider sends a predefined set of digits (from 3 to 10 digits) via the wink-start, PRI, or SIP trunk. The voice switches capture the digits and route the calling party to the called party. If ANI is not being used on wink-start trunks, only the DNIS digits need to be delivered. If ANI is being used, the star (*) key must be used to delimit the ANI digits from the DID/DNIS digitsthat is:
5.3.5
Dialed Number Identification Service (DNIS)

Dialed Number Identification Service (DNIS) allows extensions (users, menus, workgroups, route points, etc.) on the system to be accessed directly, without the need of an auto-attendant or operator. This is particularly useful for workgroup and other call center applications. The DNIS information is delivered to the ShoreTel Communicator - Personal Access and stored in the call detail record. DNIS is available on analog wink-start, digital wink-start, PRI and SIP trunks. DNIS numbers are ordered individually and map to a dialed number. When a calling party dials a specific telephone number, the service provider routes the call to a wink-start or PRI trunk connected to a voice switch. The service provider sends a predefined set of digits (from 3 to 10 digits)the DNIS digitsusing DTMF signaling (or a D-Channel message or SIP message). The voice switches capture the digits and route the calling party to the called party. If ANI is not being used on wink-start trunks, only the DNIS digits need to be delivered. If ANI is being used, the star (*) key must be used to delimit the ANI digits from the DID/DNIS digitsthat is:
106
5.3.6
Outbound Caller ID
ShoreTel sends the users DID number as the caller ID number for outbound calls over PRI or SIP trunks. If the DID number is unavailable, the site Caller Emergency Service ID (CESID) is used. If that number is unavailable, no caller ID is sent. Additionally, the outbound caller ID can be configured on a per-user basis such that the configured value can take precedence over the user's DID number or the site CESID. Note that this feature is only available on outbound calls using a T1 PRI trunk.
To send a single main number rather than individual user DID numbers, assign
DNIS entries instead of DID numbers to each user. The Site Contact Number will be sent on outbound calls. PRI trunk group to always block the caller ID number. service provider.
To block all outbound caller ID numbers from being sent, you can configure the On wink-start and loop-start trunks, the outbound caller ID is defined by the On T1 PRI and loop-start trunks, users can override the Caller ID Blocking
configuration on a call-by-call basis by using commands at the telephone (*67, *82). Users cannot override the Caller ID Blocking configuration of wink-start and E1 PRI trunks.
For more information on configuring outbound caller ID, please refer to the ShoreTel System Administration Guide.
5.3.7
Tandem Trunking
Tandem trunking allows legacy voice systems to utilize a ShoreTel system for outbound dialing. The ShoreTel system supports both user-side and network-side PRI, allowing ShoreTel systems to flexibly support digital tie trunks to other systems. You can enable tandem trunking support for any PRI trunk group with a check box in ShoreTel Director. Tandem calls are associated with a user group for outbound trunk selection. Inbound calls recognized as tandem calls are redirected to an outbound trunk based on user group call permissions and trunk group access. When needed, a dial-in prefix can be specified that is prepended to digits collected on tandem calls. The concatenated set of digits is then used in outbound trunk selection for the tandem call.
5.3.8
Tie Trunks
The addition of network-side PRI support makes PRI tie trunks easier and more compelling to deploy. ShoreTel Voice Switches that support T1 PRI can act as either the user-side or network-side of a PRI tie trunk. The tie trunk may be used to tie a ShoreTel system to a legacy voice system, or potentially to another independent ShoreTel system.
ShoreTel 13.1
107
5.4
Performing Traffic Calculations

The number of trunks required on your system will vary depending on the number of users and your specific application needs. It is important to order your trunking correctly; too few can lead to blocked calls when all trunks are busy, and too many trunks can lead to wasted money on monthly access charges. For information about calculating the trunk requirements, see Planning and System Design on page 23.
5.5
Ordering Telephone Service

Once you have determined the types of trunks you need, you will have to either place a new order or make a change order. You can use the associated Telephone Service Order Forms that are available on the ShoreTel DVD or on the ShoreTel support web site. Three order forms are provided for your use:
Analog Service T1 Service T1 PRI Service

ShoreTel does not provide an E1 PRI form because this service varies by country. Instead, we provide a table of the E1 PRI parameters that must be set. See International Planning and Installation on page 311, for more information. When the form is completed, arrange a meeting with your telephone company service representative to order the new telephone services. The forms contain specific information that the service representative must have before services can be ordered. Before ordering your telephone service, pay special attention to the installation date and time, as follows:
If you are ordering new service, it should be installed one week before the
planned cut-over date. This allows the services to be terminated on the ShoreTel system and tested before cut-over. might render your existing service unusable. You must schedule these changes outside normal business hours and work closely with your service provider for a seamless transition.
If you are changing existing service, any changes before the cut-over date
When ordering DID service, the last digits of the DID numbers should match your extension numbers for ease of use. You must make sure your extension numbers do not begin with a trunk access code, zero, or any emergency numbers such as 911 in North America. Please see the appendix on emergency 911 operations in the ShoreTel System Administration Guide for information on how to configure your system for emergency calls.
108
5.5.1
Analog Service
Note the following before requesting analog service from a telephone service provider:
Caller ID Name and Number are supported on loop-start trunks. ANI is supported on wink-start trunks. ANI on wink-start trunks must be delivered as *<ANI>*<DNIS>*.
Figure 5-1
Telephone Service Order FormAnalog Trunks
5.5.2
T1 Service
Use the T1 Telephone Service Order form (Figure 5-2) to order T1 trunks. Note the following about T1 service:
Caller ID Name and Number are supported on loop-start trunks. ANI is supported on wink-start trunks. ANI on wink-start trunks must be delivered as *<ANI>*<DNIS>*A channel service unit (CSU) is built into the voice switch.
ShoreTel 13.1
109
Figure 5-2
Telephone Service Order FormT1 Trunks
5.5.3
T1 PRI Service
Use the T1 PRI Telephone Service Order form (Figure 5-3) to order T1 PRI trunks. Note the following about T1 PRI service:
Caller ID Number is supported on T1 PRI trunks. (Caller ID Name is supported

in NI-2 configured trunks.)
A channel service unit (CSU) is built into the voice switch.
110
Figure 5-3
Telephone Server Order FormPRI Trunks
5.5.4
Ordering Service
When you order service, be sure to do the following:
State that a new ShoreTel system is being installed. State the date and time the new telephone service must be cut over. Review all the items on the telephone service order form with the service
representative.
Review any existing and new telephone numbers and have the telephone
company representative confirm the order.
5.5.5
E1 PRI Service
See International Planning and Installation on page 311, for more information about ordering E1 PRI service.
ShoreTel 13.1
111
112
Chapter 6
Dialing Plan
This chapter provides an overview of the dialing, call routing, and digitmanipulation capabilities of the ShoreTel system. The information in this chapter is useful for administrators of larger, multisite installations. The topics include:
Overview on page 113 Define Digit Collection on page 113 Define Digit Manipulation on page 119 On-Net Dialing on page 121 Quick Reference of Star Codes on page 127
6.1
Overview
When a phone number is dialed in a ShoreTel system, the system performs two distinct operations on a telephone number: Digit collection. Voice switches collect the digits in a telephone number. Digit manipulation. The switches manipulate the dialed numbers before outpulsing them to the service provider. In this chapter you will learn how to define what happens at each of these steps. Once you are familiar with these concepts, we will introduce you to On-Net Dialing, a feature that allows users to divide phone numbers into two separately-managed parts for a more flexible dialing plan.
6.2
Define Digit Collection

When someone picks up a telephone in a ShoreTel system and begins dialing a telephone number, the voice switch software examines each digit in the number and determines whether digit collection should continue or be terminated.
6.2.1
Configuring Internal Numbers

In a ShoreTel system where users dial internal numbers without an access code, the rules for digit collection are relatively straightforward. Digit collection rules are configured through ShoreTel Director. To view the Dialing Plan edit page, click Dialing Plan under System Parameters. Figure 6-1 shows the Dialing Plan edit page.
ShoreTel 13.1
113
Chapter 6: Dialing Plan
Figure 6-1
Dialing Plan Edit Page
6.2.1.1
Planning Your Dialing Configuration

When setting up a dialing plan for internal numbers, you need to consider the following:
Choose an extension length. ShoreTel supports 3-, 4-, and 5-digit dialing for
internal numbers (4-digit dialing works for most enterprises). Use an extension number scheme that conforms to your companys size and the convenience of your users. blocks of numbers for use by extension, starting with the first number.
Map extension ranges. After choosing the extension length, you can allocate
For example, if you want to reserve the range of numbers 3000-3999 for extension assignment, you allocate the 3 number block for extensions. For maximum usability, map extension numbers to the final digits of your DID (if DID is used). NOTE Extensions cannot begin with 911 (911, 911x, or 911xx).
6.2.1.2
Digit Collection Rules

When routing calls, the ShoreTel system follows the digit collection rules specified on the Dialing Plan edit page in ShoreTel Director. For the first digit collected, specific rules are in effect.
114
Table 6-1 Digit
Digit Collection Rules Rule
0 The digit configured Digit collection is stopped and the call is routed to the site in the dialing plan as the operator. operator digit. # Any other digit Digit collection is stopped and the call is routed to voice mail login. Digit collection continues until a complete extension number is dialed. If the number is valid, the call is routed to the extension. valid off-system extensions the call is routed to a trunk. invalid extensions the call is routed to the Backup Automated Attendant. Rule does not apply to trunk access codes.
6.2.1.3
Exception for 911 Emergency Calls

Emergency calls do not require an access code. The following rules apply only to emergency 911 calls:
If 911 is dialed, the switch routes the call to a 911-capable trunk group
associated with the callers User Group. insurance against accidental 911 calls. If any digit is entered during the timeout, the switch routes the call to the Backup Automated Attendant. Although this section focuses on emergency calls made within the United States, the same rules apply in other countries. See the appendix on emergency 911 operations in the ShoreTel System Administration Guide for information on how to configure your system for emergency calls. To define digit collection for internal numbers:
Before switching the emergency call, the switch invokes a brief timeout for
In ShoreTel Director, go to the Dialing Plan edit page under System Parameters
and edit the dialing plan parameters. See the ShoreTel System Administration Guide for a description of the parameters on this page.
6.2.1.4
Changing Extension Length

The ShoreTel system supports 3-, 4-, and 5-digit extensions. To change the extension length: Step 1 Click Increase Extension Length. Step 2 Specify 4 or 5 digits for the increased length. After applying your edits, you cannot decrease an extension length. For example, once it is increased to 4, the minimum is 4.
ShoreTel 13.1
115
If your system uses three-digit extensions, ShoreTel recommends that you do not assign x11 extensions to users.
6.2.2
Configuring External Numbers

The ShoreTel system supports 1-, 2-, and 3-digit trunk access codes. When an access code is dialed, the system looks for a valid digit in the parameters. If an invalid number is dialed, the system plays a recording to the calling party. There are several types of valid telephone numbers, which are described in the following sections. The ShoreTel system allows the system administrator to provide users at each site with a unique dialing plan to match the dialing plan of the sites geographic region. The ShoreTel system supports 7-digit local dialing, 10-digit local dialing, and mixed local dialing. External numbers are converted into a standard canonical format by call control software to provide a globally consistent way of handling phone numbers. The canonical format starts with a + representing the international prefix, followed by the country code, area code, and subscriber number.
External numbers that can be converted into canonical format are considered External numbers that are unique to the country (n11, 112, 911, and so on) are
routable and will leverage the network call routing feature of the call control software. considered unroutable and will not leverage the network call routing software. These calls will be placed from the local site or the associated proxy site.
6.2.2.1
Configuring 7-Digit Local Dialing

The Local Area Code on the Site edit page, shown in Figure 6-2, defines 7-digit dialing for all users at the site. When a user dials an access code followed by 7 digits, the switching software assumes the site local area has been dialed. The switching software then converts the 7-digit number into canonical format before checking call permissions and doing network call routing.
116
Figure 6-2
Site Edit Page
The Local Area Code and Additional Local Area Codes set on the Site edit page have nothing to do with the Local Area Code, Additional Local Area Codes, and Nearby Area Codes on the Trunk Group edit page. Area codes on the Site edit page relate only to digit collection, whereas those on the Trunk Group edit page relate only to Network Call Routing and Digit Manipulation. To define 7-digit dialing: Step 1 Open the Site edit page in ShoreTel Director. Step 2 Enter the 3-digit area code in the Local Area Code field. See the ShoreTel System Administration Guide for more information about the Site edit page.
6.2.2.2
Configuring 10-Digit Local Dialing

If the site is in a location with overlay area codes, it can be configured to support 10digit dialing for all the local area codes. The Additional Local Area Codes field on the Site edit page defines the area codes for 10-digit dialing. When a user dials an access code followed by a local area code, the system collects 7 additional digits (10 digits total) before stopping digit collection. The switching software then converts the 10digit number into canonical format before checking call permissions and doing network call routing. To define 10-digit dialing: Step 1 Open the Site edit page in ShoreTel Director. Step 2 Click Edit next to the Additional Local Area Codes field.
ShoreTel 13.1
117
The Additional Local Area Codes dialog box, shown in Figure 6-3, appears.
Figure 6-3
Additional Local Area Codes Dialog Box
See the ShoreTel System Administration Guide for more information about the Additional Local Area Codes field on the Site edit page.
6.2.2.3
Configuring Mixed Dialing in the Same Area

In locations where users are forced to dial 7 digits for some prefixes and 1+10 digits for other prefixes in the same area, the ShoreTel system supports permissive dialing that is, you can dial these numbers either as 7 digits or as 1+10 digits. It also supports permissive dialing in locations with mixed 10-digit and 1+10 digit dialing in the same area. From a digit-manipulation (or outpulsing) point of view, the trunk group must be configured properly since some service providers do not support permissive dialing. See "Define Digit Manipulation" section on page 119.
6.2.2.4
1+10 Digit Long-Distance Dialing

The ShoreTel system supports long-distance dialing. When a user dials an access code followed by 1, the software collects 10 additional digits before stopping digit collection.
6.2.2.5
International Dialing
The ShoreTel system supports international dialing. If the user dials a trunk access code followed by an international access code, digit collection is terminated after a timeout. The timeout can be bypassed by dialing pound (#).
6.2.2.6
n11 Dialing
The ShoreTel system supports n11 dialing, including 411 (information) and 611 (support). If the user dials an access code followed by n11, digit collection is terminated after a brief timeout and the call is routed to a trunk. If your system uses three-digit extensions, ShoreTel recommends that you do not assign x11 extensions to users.
6.2.2.7
911 Dialing
The ShoreTel system supports 911 dialing to emergency services. If the user dials an access code followed by 911, digit collection is terminated immediately and the call is routed to a trunk.
118
911 calls are routed out of the local sites associated trunks. If there are no 911 trunks available at the local site, the call is routed via the designated proxy site. Please see the appendix on emergency 911 operations in the ShoreTel System Administration Guide for information on how to configure your system for emergency calls.
6.2.2.8
Explicit Carrier Selection (101xxxx) Dialing

The ShoreTel system supports explicit carrier selection. If the user dials an access code followed by 101, the next four digits collected are for explicit carrier selection (101xxxx). The carrier information is retained and passed to the trunk.The digits collected are treated as unroutable calls; the digits are routed as-is out either local site or proxy site trunks only.
6.2.2.9
Operator-Assisted (0, 00) Dialing

The ShoreTel system supports operator-assisted dialing. If the user dials an access code followed by 0x, digit collection is terminated after a brief timeout and the call is routed to a trunk.
6.2.2.10 Vertical Service Code (*67, *82) Dialing

The ShoreTel system supports some vertical service codes for feature activation. If the user dials an access code and then the star (*) button, the system collects the subsequent digits and then terminates after a brief timeout. The digits collected are treated as unroutable calls they are routed as-is out either local site or proxy site trunks only. If the trunk is a PRI or SIP trunk, the trunk strips and interprets *67 to block outbound Caller ID, and *82 to unblock outbound Caller ID.
6.2.2.11 End Digit Collection (#)

In some cases, digit collection ends after a timeout period. To bypass the timeout and immediately send the call, the caller presses the (#) button.
6.3
Define Digit Manipulation

Once the route decision has been made, the call is passed to the trunk. The dialed number, which is normally passed within the system in canonical format, is examined and manipulated based on the trunk group configuration. This ensures that the number can be properly received by the service provider. First, the trunk access code dialed by the user is removed. If the number is in canonical format (local, long distance, ERC, international), digit manipulation can occur. If the number is unroutable (n11, ECS, operator, and vertical service code numbers) digit manipulation (other than the dial-out prefix) is not applied. To specify trunk digit manipulation: Step 1 Open the Trunk Digit Manipulation page, shown in Figure 6-4.
ShoreTel 13.1
119
Figure 6-4
Digit Manipulation on the Trunk Group Edit Page
Step 2 Select the options and specify numbers as needed, using Table 6-2 as a guide. Table 6-2 Option Remove leading 1 from 1+10D Remove leading 1 for Local Area Codes Digit Manipulation Options Description This option is required by some longdistance service providers that only accept numbers dialed as 10 digits. This option is required by some local service providers that have mixed 10-digit and 1+10 digit dialing in the same area code. Local Area Codes include both the Local Area Code and Additional Local Area Codes configured against the trunk group. Example AT&T typically only supports 10digit dialing. Atlanta has three local area codes that must be dialed as 10 digits. This could also be called Dial 10 digits for Local Area Codes.
Dial 7 digits for Local Area Code
This option is required by some local Massachusetts and service providers that have mixed 10-digit Maine. and 1+10 digit dialing in the same area code.
120
Table 6-2 Option
Digit Manipulation Options (Continued) Description Example
Prepend this Dial The Dial Out Prefix is prepended to the Not applicable. Out Prefix number. This feature is typically used when connecting the ShoreTel system to a legacy PBX system using a ShoreTel voice switch. The Dial Out Prefix enables the ShoreTel system to seize a trunk on the legacy PBX. The Dial Out Prefix is not applied to Off-System Extensions. Vertical Service Codes If a Vertical Service Code was dialed, digit Not applicable. manipulation rules do not apply. Vertical Service Codes work with ISDN PRI and SIP trunks and some loop-start trunks. With PRI and SIP trunks, Vertical Service Codes for Caller ID Blocking control will be converted to D-Channel messages. With loop-start trunks, the service provider must be able to accept the outpulsed digits with only 50 msecs of pause between each digit, including the service codes. Vertical Service Codes are typically not supported by service providers on winkstart trunks. If you have outbound access on wink-start trunks and you dial a vertical service code, you will likely get an error message from the service provider. Off System Extensions Not applicable. Off System Extensions define ranges of extensions that when dialed will be routed out of this trunk group. This is typically used to interface to a legacy PBX system using a T1 or E1 circuit provided by a ShoreTel voice switch. Off-system extensions digits can be manipulated using a translation table. Digit manipulation, including the Dial Out Prefix, will not be applied to these calls.
6.4
On-Net Dialing
ShoreTel supports On-Net Dialing (OND), an enhancement that allows users to create more flexible dialing plans than before. The On-Net Dialing feature allows users to divide phone numbers into two separately-managed parts:
ShoreTel 13.1
121
Extension prefix - typically 3 digits in length; similar in concept to a site code

to reach other users in your organization By dividing phone numbers into two parts, the OND feature provides customers with a more seamless method of migrating from their legacy phone systems to the newer ShoreTel system. OND allows customers to preserve their existing dialing plans when integrating ShoreTel equipment with their legacy equipment. While previous releases allowed customers to integrate ShoreTel equipment with their legacy PBX, the configurations needed to maintain the customer's existing dialing plan were complex and the complexity increased with the number of people and extensions involved. For example, if one company acquired another company and the two companies wanted to merge their phone systems, then no two users could have the same user extension, even if they were at different sites with different prefixes. With OND, users can call other users within a site by dialing only the user extension. For inter-site calls, the users press the numbers of the prefix and the user number. Legacy PBX systems still use off-system extensions (OSEs) to route inbound calls. How It Works
User extension - typically 4 digits in length; acts as the number you would dial
Figure 6-5
Abbreviated Four-digit Dialing with Extension Prefix
As Figure 6-5 shows, On-Net Dialing assigns extension prefixes to each site or to a group of sites. All calls are placed on the network if they are within the same prefix, and the user need only dial the user extension. Calls preceded with the trunk access code (usually 9) are sent to the PSTN. Benefits of On-Net Dialing:
Scalability For larger organizations, On-Net Dialing enables the creation of a
common and consistent cookie cutter dialing plan that can be replicated throughout an organization that has many offices. For example, a department store might have a phone in each of its different departments with one for clothing, furniture, kitchenware, etc. With On-Net Dialing, a user can assign the
122
extensions of 4000, 5000, 6000, and 7000 to each of these departments. By modifying the 3-digit site code/extension prefix at each location, this approach of assigning 4-digit extensions to departments can be replicated across an entire department store, nationwide, so that a user who knows the extension for the automotive department in one city could travel to another city and would know how to reach the automotive department if he knew the site code.
Preserve existing legacy dialing plans You can preserve the existing dialing
plans when adding ShoreTel equipment to a deployment with legacy equipment by assigning a new prefix to each new site or to users on the new ShoreTel system. legacy PBXs from the ShoreTel system.
Legacy integration via OSEs (Off-System Extensions) Ability to call multiple Multi-tenant On-Net Dialing allows a landlord to maintain one phone system
at a building that houses two or more businesses or organizations in such a way that neither organization is aware that the infrastructure or trunk lines are being shared. Despite the fact that both organizations are in the same building, you can assign different prefixes to each company and could then hide one organization's phone numbers from the other group so that neither group would see the other.
6.4.1
Configuration
The process of configuring On-Net Dialing consists of the following tasks:
Planning and configuring the dialing plan Adding sites Associating an extension prefix with a site Assigning user extensions
The subsections that follow provide details on each of these tasks. NOTE ShoreTels Small Business Edition does not support On-Net Dialing. NOTE Enabling On-Net Dialing is an irreversible process. It permanently changes the database. Therefore, plan carefully before proceeding with the configuration.
6.4.1.1
Planning and Configuring the Dialing Plan

Assigning extension prefixes to a specific digit must be done all at once. Once the dialing plan window (shown below) has been configured and saved, there is no way to make changes to the extension prefix assignments without erasing the database and starting all over. Therefore, we recommend carefully planning and reviewing your dialing plans before configuring the dialing plan window. To configure the dialing plan via Director, follow the procedure below: Step 1 Launch ShoreTel Director and enter the user ID and password. Step 2 Click on the Administration link to expand the list (if it has not already been expanded). Step 3 Click on the System Parameters link and then the Dialing Plan link to display the Edit Dialing Plan window, as shown below:
ShoreTel 13.1
123
Figure 6-6
Configuring dialing plan
Step 4 Click on the drop-down menu to the right of the desired digit and select the number of digits you would like the extension prefix (i.e. site code) to contain. Extension prefixes can range from 1 to 7 digits in length. The leading digit determines the length of the prefix. Extension prefixes with different leading digits do not have to contain the same number of digits. Step 5 Repeat this process for any other extension prefixes, unused extensions, or trunk access codes. Step 6 Click Save to store your changes. The Configure Extension Prefix Warning dialog box (similar to the one shown below) appears with a list of each of the sites in your system.
124
Figure 6-7
Make sure to back up your system before clicking Save
The Extension Prefix Warning message lists each site in your system. Next to the list of sites you will find a blank field that requires you to enter the desired extension prefix. NOTE This prefix will be applied to every dialable number at that particular site, so if the site is an existing one, they will see their phone numbers converted to the new prefix. System extensions are not associated with a hard port in the system. They are always global and will have a user number and a null extension prefix. Therefore, these system extensions are not affected by changes made to the extension prefix in the Edit Dialing Plan window. Only dialed numbers (user extensions, menus, workgroups, distribution lists) are affected by changes to the extension prefix. Step 7 Click the Save button to store your changes.
6.4.1.2
Adding Sites
You can add the sites via ShoreTel Director before configuring your dialing plan (or alternatively, you can configure your dialing plan and then add sites at a later time). To add a site via Director, follow the procedure below: Step 1 Launch ShoreTel Director and enter the user ID and password. Step 2 Click on the Administration link to expand the list (if it has not already been expanded). Step 3 Click on the Sites link. Step 4 Click on the Add a new site in drop-down menu and select the country where the site will be added. Step 5 Click the Go link to display a window similar to the one shown below.
ShoreTel 13.1
125
Figure 6-8
Add a new site
Step 6 Enter the name of the site, along with all other relevant information, in the appropriate fields. (Refer to the ShoreTel Sites chapter in the ShoreTel System Administration Guide for additional information on con-figuring this window.) The Extension Prefix field will not appear in this window until after you have modified the Dialing Plan window (which is our next task). Step 7 Click Save to store your changes. Step 8 Repeat this process to add any other sites that you would like to include in the dialing plan. Once you have created the dialing plan and saved your dialing plan configurations, you can return to the Edit Sites window in Director to verify that the changes have been propagated throughout the system. By clicking on the name of the site, you will see an Extension Prefix field. The field should be populated with the value entered in the Extension Prefix Warning window, as shown in the window below:
Figure 6-9
Extension Prefix field now populated
126
6.4.1.3
Adding Users to the System

When the On-Net Dialing feature has been enabled and the extension prefix for a site has been updated, the first new user added to the system may not receive the site's new prefix. (This is due to cookies in the system populating the new user's extension with old and outdated information.) However, after this first user has been added, subsequent users will have their extensions automatically populated with the correct site prefix. NOTE User numbers can vary in length from 3 to 5 digits. All user numbers in the system must be the same length.
6.5
Quick Reference of Star Codes

Certain features and functions can be performed via the telephone interface through the use of star codes. By pressing the star key (i.e. asterisk) on your phones keypad, followed by a combination of numbers, you can perform many tasks that would otherwise require the use of a soft key, option button, or programmable button.
6.5.1
Common Star Codes

Park a call UnPark a call Picking Up a Remote Extension Picking Up the Night Bell Using the Intercom Barge In Silent Monitor Toggling the Hunt Group Status Whisper Page Changing Call Handling Mode and Forwarding Changing Extension Assignment Unassign Extension Assignment Assign Extension to External Number *11 + ext. *12 + ext. *13 + ext. *14 *15 + ext. *16 + ext. *17 + ext. *18 + Hunt Group ext. *19 + ext. VoiceMail + password + # + 72 VoiceMail + password + # + 731 VoiceMail + password + # + 732 VoiceMail + password + # + 733
6.5.2
Extension Assignment Star Codes

Transfer a call Conference a call Hold a call Hang up ** + destination + # # ** + destination + ** ** ##
ShoreTel 13.1
127
Access other common star codes
** + *star code (between 11 and 19) + ext.
6.5.3
Trunk Star Codes

Blocking and Caller ID
*67 + ext.
When a user places an external call, they can block their Caller ID using the *67 command. The user dials the trunk access code, followed by *67, followed by the external number. When dialing in this manner, the call will be considered non-routable and will only access trunks at the local site. The number is dialed as is (i.e. as if a user dialed it). No digit manipulation will be performed.
Unblocking Caller ID
*82 + ext.
When a user places an external call, they can unblock their Caller ID delivering using the *82 command. The user dials the trunk access code, followed by *82, followed by the external number. When dialing in this manner, the call will be considered non-routable and will only access trunks at the local site. The number is dialed as is (i.e. as if a user dialed it). No digit manipulation will be performed.
128
Chapter 7
Network Call Routing

This chapter provides an overview of call routing, and digit-manipulation capabilities of the ShoreTel system. The information in this chapter is particularly useful for administrators of larger, multisite installations. The topics discussed include:
Overview on page 129 Define Network Call Routing on page 129
7.1
Overview
When a phone number is dialed in a ShoreTel system, the system performs three distinct operations on telephone numbers: Digit collection. Voice switches collect the digits in a telephone number. Network call routing. After collecting the digits, the switch checks the number against a users call permissions, adds trunks to the route list, and makes a final route decision for the call. Digit manipulation. The switches manipulate the dialed numbers before outpulsing them to the service provider. In this chapter you will learn how to plan your network call routing.
7.2
Define Network Call Routing

Once an external telephone number has been collected, the switching software checks the number against the users call permissions, finds the list of available trunks, and then makes a routing decision based on several criteria.
7.2.1
Call Permissions
Each dialed number is compared against the users call permissions. If the call is denied, the calling party will be routed to a fast busy intercept tone. If the call is allowed, the routing continues. To define call permissions: Step 1 Open the Call Permissions edit page (Figure 7-1).
ShoreTel 13.1
129
Chapter 7: Network Call Routing
Figure 7-1
Call Permissions Edit Page
Step 2 Specify a Scope. Scope allows you to set a general permission level and is presented from the most restrictive to the most permissive. The Restrictions and Permissions listed are applied in addition to the general scope setting for the Class of Service.
Internal Only allows calls only to internal extensions and to the

configured emergency number.
Local Only allows calls only to local or additional local area codes, as National Long Distance also allows calls to long-distance numbers
within the country, as defined on the Site edit page. with caller pays billing plans.
defined on the site edit page. The call permission does not apply to any of the trunk group area codes.
National Mobile allows calls to mobile phones in countries (e.g. Ireland) International Long Distance also allows calls to international
numbers, as defined on the Site edit page.
All Calls allows calls to any number, including 1900, Operator Assisted,
and Carrier Select numbers, as well as use of Vertical Service Codes. This is the default. Step 3 Enter restriction and permission rules. The Restrictions and Permissions listed are applied in addition to the general scope setting. The comma separated restriction expressions are limited to a total of 50 characters. Follow these guidelines for entering restrictions:
In general, numbers must be entered in canonical format including the

international designation + and country code. For example, to restrict calls to the 408 area code in the U.S., use +1408. All 7-digit and 10-digit numbers must be entered in canonical format (+Country Code, Area Code, and Subscriber Number).
Non-routable calls (311, 411, etc.) for a country must be designated by the Each field can contain multiple entries as long as they are separated by
commas or semicolons.
country code plus the / character. For example, to restrict 311 in the U.S., use 1/311.
Each entry must consist of numbers only.

130
Access codes, such as 9, must not be included. To simplify the entering of call permissions, the wild-card character x
can be used to represent any number. For instance, to block all calls to 976 prefixes, enter +1xxx976 as a restriction. When a call is both restricted and permitted, it is permitted. For example, restricting +1 408 and permitting +1 408 331 restricts all calls to the 408 area code except those to 408 331-xxxx.
7.2.2
Account Codes
If Account Code Collection Service is enabled, when a user dials a number that is outside the scope of his or her call permissions, the call is automatically routed to the Account Code Collection Service extension on the headquarters (HQ) server or Distributed Voice Server (DVS). The Account Code Collection Service captures call details that can be reviewed in the call detail reports. For more information on these reports, see the ShoreTel System Administration Guide. The collection of account codes is enabled on a per-user group basis and can be set to be one of three states: disabled, optional, or forced. The Account Code Collection Service is associated with a configurable extension and has a dedicated user group that defines ultimate call permissions and trunk group access. When account code collection is enabled or forced for a member of the user group, calls placed via the telephone or the ShoreTel Communicator are first filtered by call permissions. Calls restricted by call permissions are automatically routed to the extension associated with the Account Code Collection Service. Upon receiving the call, the Account Code Collection Service prompts the user to enter an account code and press the pound (#) key. If the user enters an account code that does not match the digits in a stored account code, the system plays a message explaining the problem and prompts the user to reenter the account code. When the user enters an account code that matches one of the stored codes, the code is collected, and the call is completed. Call Permissions specifies the dialed numbers that are directed to the Account Code Collection Service for any user groups configured for account codes. Calls redirected to the account codes extension are completed using the trunk access and call permissions associated with the Account Code Collection Service. The Account Code Collection Service examines outbound calls against two sets of permissions: 1. Checks call permissions for the callers user group to determine if an account code must be collected. 2. If user group permissions specify the collection of an account code, a check is performed on the call permissions for the Account Code Collection Service to determine whether call will be permitted or rejected. If the call is rejected, the intercept tone is played. The Account Code Collection Service is associated with a system extension hosted on a SoftSwitch that runs on the headquarters server or users managing DVS.
ShoreTel 13.1
131
If the SoftSwitch is unavailable to the ShoreTel Voice Switch from which a call originates, the call is handled according to the permissions set for the callers user group. Calls placed by users who are configured for optional account code collection are placed. Calls placed by users who are configured for forced account code collection are rejected. Wildcard characters (represented with a question mark) can be used in place of DTMF digits in the account code. When wildcards are used, a length check is performed instead of a more thorough validation of the code. Although this reduces the stringency of the validation process, it allows the system to support far more than 50,000 account codes the previous account code limitation. Refer to the chapter on Call Control in the ShoreTel System Administration Guide for more information about account codes and account code wildcards.
7.2.3
Trunk Availability
For a trunk to be included in the list of possible trunks that can be hunted, the following conditions must apply:
The trunk must have an access code that matches the access code dialed. The trunk must be assigned to the user. (Trunk groups are assigned to user
groups.)
The trunk must be capable of the requested service (Local, Long Distance,
International, n11, 911, Easily Recognizable Codes, Explicit Carrier Selection, and Operator Assisted). These services are defined on the Trunk Group edit page as shown in Figure 7-2.
Figure 7-2
Trunk Services on the Trunk Group Edit Page
The trunk must be in service. The trunk must not already be in use. The trunk must be on a switch that the users switch can reach. (The network is
up and running.)
For multisite calls, the admission control must be met at both sites. Admission
control is defined on the Site edit page.
If call is long distance from the trunk, it was not local to the caller. For example,
network call routing will not send a local call via a trunk in another state.
132
To define trunk services: Step 1 Open the Trunk Services dialog box on the Trunk Group edit page. Step 2 Select the services that will be available for the selected trunk. See the ShoreTel System Administration Guide for more information about the Trunk Group edit page. To define admission control: Step 1 Open the Site edit page. Step 2 Enter the proper amount in the Admission Control Bandwidth field. See the ShoreTel System Administration Guide for more information about the Site edit page and for instructions about computing Admission Control Bandwidth.
7.2.4
Specifying Parameters for the Routing Decision

Once the available set of trunks is established, the switching software makes a routing decision, with the goal of minimizing toll charges and WAN bandwidth. The Network Call Routing algorithm bases the routing decision on the Local Area Code, Additional Local Area Codes, and Nearby Area Codes defined on the Trunk Group edit page.
7.2.4.1
Network Call Routing Algorithm

When multiple trunks meet the same criteria, a trunk is seized randomly. In general, trunks that are configured last are hunted first. Over time, however, as trunks are deleted and added, hunting becomes increasingly random. SIP trunks are given precedence over Digital trunks, which are given precedence over analog trunks in all routing decisions. To make the routing decision, the algorithm poses the following questions. For the number dialed, is there: 1. A trunk at the originating site for which the call is local? 2. A trunk at the proxy site for which the call is local? 3. A trunk at any other site for which the call is local? 4. A trunk at the originating site for which the call is considered nearby? 5. A trunk at the proxy site for which the call is considered nearby? 6. A trunk at any other site for which the call is considered nearby? 7. A trunk at the originating site designated for long distance? 8. A trunk at any proxy site designated for long distance? 9. A trunk at any other site designated for long distance? 10. Any remaining trunk available at originating site? 11. Any remaining trunk available at the proxy site?
ShoreTel 13.1
133
To specify parameters for the routing decision: Step 1 Open the Network Call Routing page on the Trunk Group edit page, shown in Figure 7-3
Figure 7-3
Network Call Routing on the Trunk Group Edit Page
Step 2 Enter values into the Local Area Code, Additional Local Area Codes, and Nearby Area Codes fields. Step 3 Open the Trunk Group edit page and, toward the bottom of the page, click Go to Local prefixes. The Local Prefixes dialog box appears. It allows you to enter prefix exceptions against a local area code. The Network Call Routing algorithm handles prefix exceptions for the local area code as long distance, which minimizes toll charges. See the ShoreTel System Administration Guide for more information about the Trunk Group edit page and the Local Prefixes dialog box. The area codes on the Site edit page have no impact on call routing decisions.
134
Chapter 8
Planning Applications and Services

This chapter reviews the key applications and services of the ShoreTel system to assist you in planning your system configuration, and to determine the equipment you need for completing deployment. The topics discussed include:
Account Code Collection Service on page 135 Planning Fax Handling on page 141 Private Numbers on page 148 Automated Attendant on page 149 Call Handling Delegation on page 150 ShoreTel Communicator for Windows on page 150 ShoreTel Communicator for Mac on page 150 ShoreTel Communicator for Web on page 151 Bridged Call Appearances on page 151 Hunt Groups on page 152 Pickup Groups on page 154 Workgroups on page 156 Enterprise Telephony Features on page 159 ShoreTel Enterprise Contact Center Solution on page 163
8.1
Account Code Collection Service

ShoreTel supports account codes for external calls when you enable the Account Code Collection Service. When a user dials a number that is not included in the scope of his or her call permissions, the call is routed to the Account Code Collection Service extension, where the user is prompted to enter a valid account code. Account code collection is enabled on a per-user group basis and can be set to be one of three states: disabled, optional, or forced. The Account Code Collection Service is associated with a configurable extension and has a dedicated user group that defines ultimate call permissions and trunk group access. A new user group is created during installation for use by the Account Code Collection Service. This user group is named Account Codes Service. Since it is only intended for use by the Account Code Collection Service, this group does not appear in drop-down lists for the assignment of User Groups to users and other objects such
ShoreTel 13.1
135
Chapter 8: Planning Applications and Services
as workgroups. You can, however, change all attributes of the Account Codes Service User Group except the fields indicating whether Account Codes are disabled, optional, or required. The Account Code Collection Service is distributed across all headquarters and DVS servers and is associated with a system extension that is hosted on the SoftSwitches running on each headquarters and DVS server. If the SoftSwitch is not reachable by the originating ShoreTel Voice Switch, the call is handled according to the setting on the callers user group. Specifically, during such a connectivity outage, calls placed by users who have optional account code collection are automatically placed, and calls placed by users who have forced account code collection are automatically rejected.
8.1.1
Account Codes
Account Code Collection Service supports up to 50,000 account codes of a maximum of 20 characters. You can include non-numeric characters (such as hyphens and slashes) in the account codes; however, non-numeric characters are not used in account code collection or in the account code reports. An account code can be the same as a prefix for another account code. For example, the account codes 1234 and 12345 can coexist. Table 8-1 gives example account codes and how the Account Code Collection Service interprets the code. Table 8-1 Account Code Interpretation Example Recorded Code 200 10013 1234 30002
Sample Account Code Sales 200 1001-3 1.234A 3000 Exec 2
Account codes can also have user-friendly names of up to 50 characters.
8.1.2
Call Permissions
The call permissions define what dialed numbers are directed to the Account Codes Service for user groups configured with account codes. For calls that are redirected to the account codes extension, the call is completed with the trunk access and call permissions of the Account Codes Service. This structure imposes two sets of permissions on outbound calls:
The call permissions for the user group of the user who places the call are used
to determine if an account code must be collected or not. finally placed, or if the intercept tone is to be played.
The call permissions for the Account Codes Service determine whether calls are
136
8.1.3
Distributed Voice Mail

ShoreTel has Distributed Voice Mail to provide greater availability. Each ShoreTel Distributed Voice Server (DVS) has an instance of the telephony platform, allowing full functionality of voice mail and auto-attendant services at that location during WAN outages. The Distributed Voice Mail feature allows users with mailboxes on that server to receive and pickup voice mail messages without having to depend on a WAN connection to the headquarters server that hosts the configuration database. The message waiting indicator (MWI) lights correctly update local users about voice mail with or without WAN connectivity. Additionally, incoming calls reach the auto-attendant, access the dial-by-name directory, and reach their intended local party during a WAN outage. If a party cannot be reached directly and his call handling setting would send unanswered calls to voice mail, the call is handled by the local voice mail server. If the users voice mailbox resides on a different voice mail server, the local ShoreTel server will accept, store and forward the message when connectivity to the proper voice mail server is restarted. The caller hears a generic greeting including the intended party's recorded name and the caller has the option to leave a message. This message will be forwarded at a later time to the home voice mail server for the addressee via SMTP. Although each voice mail server is autonomous in delivering voice services, it must have connectivity to the headquarters server in order to carry out configuration changes. Specifically, users on an isolated remote server are not able to change call handling modes or make other changes that require modification to the configuration database on the headquarters server. The ShoreTel Communicator applications may provide limited call control access and may not display some contents on IP phones at a remote site during WAN outages. These both require connectivity to the headquarters server for full service. For users who have their ShoreTel Communicator application running at the time of a WAN outage, graphical access to their voice mail box is provided, including the ability to compose and playback messages, but ShoreTel Communicator may not display the corresponding call activity associated with any actions. You should provision a DVS at any site with more than 100 users to effectively manage your WAN bandwidth between that site and the headquarters or main site. In addition, you must add a distributed server with the voice mail application at any site where the required number of mailboxes exceeds 1,000. Users should be configured for the server that is located at their home or most frequent site. If that site does not have a server, the nearest server or headquarters server should be used. When there are multiple voice mail servers, the system-wide voice mail extension automatically maps to the extension of the local server. Voice mail media streams are therefore recorded in the CDR reports by the voice mail extension that actually handles the call. The ShoreTel system provides each user with five call handling modes, and workgroups with four call handling modes, allowing employees and workgroups to customize how calls are routed. Employees typically use Standard call handling mode to route calls to voice mail after three or four rings, and use Out of the Office call handling mode to route calls directly to voice mail. Users should consider:
Forwarding calls to a cell phone
ShoreTel 13.1
137
workgroups) You must enable external call handling as part of the class of service for users who want to use these options. The Message Notification feature delivers a notice to users that a message has arrived for them. Notifications can be sent upon receipt of all messages, or only upon receipt of urgent messages. The system can deliver a notification to the following destinations:
Forwarding calls to an external answering service (for critical users or
An E-mail address (can also include a voice mail attachment in WAV format). A pager (a pager model that allows message notification). An extension (if the extension allows message playback). An external number, such as a cell phone (if it allows message playback). Users who address and compose voice mail through the Telephone User
Interface (TUI), the Visual Voicemail application, or the Outlook Voicemail form can mark their messages with a request for a return receipt.
8.1.4
Escalation Notifications
Similarly, the ShoreTel system can send any of these notifications types to specific members of an escalation profile, in support of an Escalation Notification feature. The Escalation Notifications feature is a traditional voice mail feature that allows support groups to offer round-the-clock service to their customers. For example, if a customer calls into the ShoreTel system and leaves a message, the voice mail system sends out a page, phone call, or email to a designated employee in the support department. If this first employee ignores his beeping pager, the next designated employee within the escalation profile list is contacted, and so on. Employees in the escalation profile will continue to be contacted sequentially until someone listens to the voice mail. (See the section on configuring users in the ShoreTel System Administration Guide for more information.)
8.1.5
Auto-deletion of Voice Mail Messages

The ShoreTel system also supports the ability to automatically delete user voicemail messages that are older than a specified time limit. The system administrator can set a maximum time limit for the storage of voice mail messages, and if this time limit is exceeded, messages are automatically deleted. The tool can be used to encourage users to better manage their voice mailboxes.
8.1.6
Mailbox Full Notifications

The ShoreTel system can be configured to notify users when their voice mailboxes are almost full. This features warns users of the impending lack of storage space to give them ample time to delete messages, as opposed to logging into their voice mailbox only to discover that the mailbox is full. Once a users mailbox has passed a threshold, the system sends a notice informing them that their mailbox is almost full and that there is only enough room for 10 additional messages. Thusly, users are not caught off-guard by an unexpected (and unwanted) mailbox full notification. For more information, refer to the section on configuring users in the ShoreTel System Administration Guide.
138
8.1.7
AMIS Protocol Support

The ShoreTel system can send and receive voice mail messages to and from legacy voice mail systems that use the AMIS protocol Version 1 - Specification; February 1992. To send voice mail messages to remote AMIS sites, ShoreTel dials the access phone number for the remote system. Likewise, to receive voice messages from a remote system, the remote system must know the number to dial into the ShoreTel system. To reach the ShoreTel system, the remote system must be configured to dial any number that reaches an auto-attendant menu. NOTE The ShoreTel Small Business Edition system does not support AMIS. ShoreTel enables AMIS call support by default. Incoming AMIS voice mail is delivered in the same manner as other voice mail; however, replies cannot be sent. To send outbound AMIS voice mail, you must create AMIS systems in ShoreTel Director. ShoreTel negotiates the setup, handshaking, and teardown of AMIS system calls. Each voice mail requires a call over the AMIS delivery and call-back numbers. To simplify AMIS systems, and increase usability:
Use the same extension length across your enterprise. Use off system extensions to match remote users mail boxes with their
extension numbers.
To identify the remote site location, assign each system a System ID.
For more information on AMIS systems, refer to the ShoreTel System Administration Guide.
8.1.8
SMDI Protocol Support

The ShoreTel system supports the SMDI protocol. Two modes of operation are supported:
In the first mode of operation, the ShoreTel system acts as a PBX for a legacy
voice mail system. The ShoreTel system provides call information for forwarded or direct calls to the legacy voice mail system, and receives incoming message waiting indication from the legacy voice mail system.
system for a number of users on a legacy PBX. Both configurations require a serial link between a ShoreTel server and the legacy voice mail system, as this is the medium required by the SMDI protocol. If using the first mode mentioned above, a group of analog trunks must be used to connect the ShoreTel system to the legacy voice mail system (the ShoreTel system is on the extension side of the trunks). The ShoreTel voice mail application manages the group of outgoing extensions. The ShoreTel server can provide digit translation if the legacy voice mail and ShoreTel system have different extension lengths. It is possible to have some ShoreTel users on the ShoreTel voice mail and some on the legacy voice mail. However, these users will not be able to send messages to each other unless AMIS is implemented between the two systems. Voice mailboxes for workgroups and agents must be on the ShoreTel voice mail system. ShoreTel Communicator operates the same way it does when a user has no mailbox:
In the second mode of operation, the ShoreTel system acts as the voice mail
Voice mail viewer is not available
ShoreTel 13.1
139
Windows Control Panel does not contain Voice Mail tab Find Me and Notification features are not available Dial Mailbox and Transfer to Mailbox are not available for this user from other
users clients system voice mail extension. For more information about using a serial link and SMDI protocol to integrate the ShoreTel system with a legacy voice mail system, see "SMDI Protocol Support" on page 284.
To Voice Mail button on ShoreTel Communicator transfers the call to the
8.1.9
Find Me Call Handling

Find Me and Auto Find Me call handling allow callers to find users at other locations when they reach the users voice mail. When Find Me is enabled for the current Call Handling Mode, inbound callers that reach a ShoreTel user's voice mail box can activate Find Me call handling by pressing 1. If the caller activates Find Me call handling, the system plays a prompt indicating that it is now finding the called party: Please hold while I try to find your party. ShoreTel users can specify two Find Me destinations, which can be internal or external numbers. These numbers can be enabled or disabled for each Call Handling Mode. If a call is forwarded to the first number and is not answered within a configurable number of rings, the call can either be forwarded to a second Find Me destination or can be returned to voice mail. The Caller ID that appears on Find Me calls is the voice mail Caller ID and not the ID of the original caller. However, if the source of the original call is external to the system, then the Caller ID will be displayed. Personal Assistant (pressing 0) also works when Find Me forwarding is enabled. The voice mail system dials the configured Find Me numbers in sequence. When a Find Me call is answered, voice mail announces the call through a sequence of prompts. The party that answers a Find Me call hears prompts similar to the following:
I have a call for Sam Smith from 4085551212. To accept this call, press one. To send this call to voice mail, press two. To repeat the caller ID, press three.
The party at the Find Me number has three options for directing the call:
Pressing 1 connects the original caller with the intended party at the Find Me
destination.
Pressing 2 directs the voice mail system to immediately start taking a message
for the intended party from the original caller. also extends the timeout by 1 ring (6 seconds). The voice mail system does not automatically notify callers of the Find Me call handling option. ShoreTel users can elect to tell callers of the Find Me option in their recorded greeting (i.e. they can tell callers to press 1 to Find Me). If the user does not tell callers about the Find Me option in their greeting, the Find Me option can remain
140
Pressing 3 repeats the Caller ID information available on the call, if any. This
a hidden capability available only to selected callers. Conversely, users can automate the Find Me behavior so that when a call enters voice mail (and Auto Find Me is enabled), the call is immediately sent to the Find Me destination numbers without requiring any action on the part of the caller.
8.1.10 Call Sender

Users can place a return call to the originator of a voice mail by pressing 5 from the phone during message playback. Users can also call back the voice mail sender from ShoreTel Communicator, Agent Monitor, or Microsoft Outlook, if the user is so provisioned. To use this feature, the user must belong to a user group with trunk-totrunk transfer Class of Service enabled. For more information, see the ShoreTel System Administration Guide. The user has the option of replying with either a voice message or a phone call if Caller ID information is available on the call. If no Caller ID information is available for the call (for example, on calls from an outside caller), the reply with a call option is not available for that message. When the user chooses to reply with a phone call, the call is transferred to the number of the originating party. When the originating party is an external caller, the message recipient must have the dialing permission to dial the Caller ID number. Once the message recipient is transferred to the number of the message originator, there is no option to return to the mailbox.
8.1.11 Time Stamps

The time stamp of the message is relative to the time on the server where the message is taken. For example:
When the user views messages in the Voice Mail Viewer or Outlook Form, the
user interface will adjust the time stamp based upon the time of the users computer. will be based on the time of the server.
When the user dials into voice mail to retrieve their messages, the time stamp
8.2
Planning Fax Handling

The ShoreTel system supports fax calls. There are several ways to configure your fax service.
A direct fax number for each site Direct fax numbers for each user (using either individual fax machines or a fax
server)
Redirect faxes that are sent to the sites main number to a fax machine
extension at the site
Redirect faxes that are sent to a users extension to users local fax extension
Figure 8-1 shows how to plan your fax options.
ShoreTel 13.1
141
Figure 8-1
Planning Fax Service
How you configure your fax service with ShoreTel Director depends on which method of fax call handling you have chosen. The following provides a basic outline of the steps involved: If you plan to use the main number for voice and fax calls, and the main number goes to an auto-attendant: Step 1 Configure the fax extension through the User edit page of ShoreTel Director. Make sure that fax redirection is disabled for fax extension users. Step 2 Enter a fax extension you created in Step 1 in the FAX Redirect Extension field from the Site edit page. If you plan to use the main number for voice and fax calls, and the main number goes to an operator: Step 1 Configure the fax extension through the User edit page of ShoreTel Director. Step 2 Assign a direct number as the fax number. Step 3 From the Trunk Group edit page (on the DNIS map page), set the destination to the fax extension. If your users have their own faxes or fax service: Step 1 Configure the fax extensions through the User edit page of ShoreTel Director. Step 2 Assign a range of direct fax numbers.
142
Step 3 From the Trunk Group edit page (on the DNIS map page), set the destination for each fax number to the appropriate fax extension. If you plan for each user to have a single number for both voice and fax: Step 1 Configure the fax extensions through the User edit page of ShoreTel Director. Step 2 Enable fax redirection from the User edit page and enable fax redirect for the site by entering a fax extension on the site edit page. For more information on these settings, see the ShoreTel System Administration Guide.
8.2.1
Using a Fax Server

A fax server improves services available to your users, helping them be more productive. With a fax server, users can:
Send faxes directly from the desktop eliminating the need to print faxes to send. Receive faxes directly on the desktop. Integrate fax communications with e-mail and voice mail applications. Have individual fax numbers Maintain soft copies of all faxes for easy printing and document management.
Using a fax server with the ShoreTel system allows you to:
Share inbound and outbound trunks for fax services. Reduce toll charges by leveraging your VoIP network for outbound faxes.
For inbound fax support, users can be assigned a personal fax number from the DID range of one of the trunk groups and this DID number can be the same as the users regular telephone extension. When a call is received, if the fax redirect feature is enabled, the system can differentiate between voice calls and fax calls and react appropriately. Outbound faxes are queued by the server and then sent across the IP network to the best available trunk. Fax Server Requirements
Sufficient ports on ShoreTel voice switches Sufficient ShoreTel User Licenses Sufficient DID trunks to support both fax and voice DID for all users 8.2.1.1 Network Requirements
The network requirements for faxing over IP are more stringent than for voice over IP. For voice communications, a 1% packet loss has negligible impact on voice quality. However, a 1% packet loss for fax communications means a loss of approximately 3 lines per fax page. ShoreTel recommends that packet loss not exceed 0.1% across the LAN and WAN when using fax servers with the ShoreTel system.
ShoreTel 13.1
143
Fax communications are also impacted by voice compression. Since fax machine typically require 19.2 Kbps, ShoreTel recommends that you use G.711 voice encoding for fax calls. For more information on fax requirements, see the "ShoreTel IP Phones" on page 167. NOTE The fax redirect feature will not work with calls that come in on SIP trunks.
8.2.1.2
Fax Server Integration Details

Instead of requiring users to have two separate DID numbers (one for voice and one for fax) a single DID line can handle voice calls and inbound/outbound faxing. A user's extension (which can be 3, 4, or 5 digits) is sent to a fax server via in-band Dual Tone Multi Frequency (DTMF) digits. The fax server uses this information to create a mapping between the user's extension and his or her e-mail address. Once configured, incoming fax calls are received at the user's phone extension. The fax server listens for the fax tone, takes over the call (assuming the fax redirect radio button has been selected in Director). When the fax transmission is complete, the loop current is automatically turned off to terminate the fax call, and the and fax is forwarded to the associated e-mail address. Figure 8-2 shows the flow for a fax call.
1. Fax Call
3. Call is redirected to fax redirect extension
4. Fax server answers
PSTN
2. User or voice mail answers Fax call
5. DTMF of dialed number invokes Fax Mailbox
Figure 8-2
Fax server integration call flow
8.2.1.3
Enhanced FAX Server Integration

The ShoreTel system delivers digits to a Fax Server for DID calls routed directly to a FAX server, thus allowing the call to go directly to the fax extension and provide DID/DNIS digits, instead of to an extension number and then to the fax server.
8.2.1.4
Configuring Fax Server Integration

At a high level, the process of setting up the Fax Server Integration feature involves three tasks:
Connecting the hardware (i.e. connecting the fax server ports to the analog ports
on the switch)
Creating a user account to represent each analog port Enabling the Fax Server Integration feature for each user account
144
To configure the Fax Server Integration feature: Step 1 Configure a fax server per the manufacturer's instructions. Step 2 Connect the fax server to one of the analog ports on a ShoreTel Voice Switch that supports analog. Next, you will create user accounts to represent each analog switch port that connects to the fax server. Step 3 Launch ShoreTel Director. Step 4 Click on the Administration > Users > Individual Users. Step 5 Click Add a New User. The Edit User window appears, as shown in Figure 8-3. (Arrows in the illustration point to fields that must be configured. Refer to the bulleted list below the illustration for details.)
Figure 8-3
Creating a user account for the fax server
Step 6 Enter information for each of the fields as shown below for each field:
License Type: Extension-Only User Group: You must create a User Group appropriately configured for
a fax server. The User Group should have the Class of Service for Call Permissions set to No Restrictions to transfer inbound and outbound faxes.
Home Port: Select the Ports radio button and then use the drop-down
menu to select the switch where the fax server will be connected. because the port will not be assigned a mailbox.
Accept Broadcast Messages: Should appear grayed-out or be deselected
ShoreTel 13.1
145
Include in System Dial By Name Directory: Check box may be
selected if you want callers to be able to locate the fax number using the Dial by Name feature.
Fax Support: This Extension is Connected to a Fax Server radio button

must be selected. Step 7 Click the Save button to store your changes. Step 8 Click the Personal Options tab and enter 1 in the Current call stack size field. Step 9 Click Save to store your changes. Next, configure the call handling mode for each of the user account associated with a port connected to the fax server. Step 10 In Director, select the user account representing the fax server connection. Step 11 Click the Personal Options tab. Step 12 Click the Standard link under Edit Call Handling Modes. Step 13 Under Call Forward Condition, select the No Answer/Busy radio button as shown in Figure 8-4.
Figure 8-4
Configuring Call handling mode for Busy/No Answer failover
Step 14 In the Busy Destination and No Answer Destination radio buttons, select Extension and specify the analog port where incoming fax calls will be directed if the first fax port is busy. For example, if you have set up three ports to receive fax calls, you might configure the first port in this series to redirect to the second port, and the second port would specify the third as a failover. Step 15 Click Save to store your changes. This configuration assumes multiple analog ports will be used to connect the switch to the fax server. If only one fax server port will be used to connect to
146
the fax server, then the call forwarding must be set to Never. Similarly, if this port is the last one in a chain of ports dedicated to the fax server, then the call forwarding must be set to Never. If you are using multiple analog switch ports to connect to the fax server you must specify the first redirect extension in that chain. (This is the site's fax redirect extension.) Step 16 Under the Administration link, click Sites. Step 17 Click on the site where the switch and fax server are located (i.e. either Headquarters or Remote). The Edit Site page appears as shown in Figure 8-5.
Figure 8-5
Configuring Fax Redirect extension for primary fax server port
Step 18 Under FAX Redirect Extension (near the bottom of the Site window), enter the extension associated with the first port in the chain of fax server ports. (This is the first place incoming faxes will be sent.)Click Save to store your changes. Next, you must configure settings for each user that will be using the new Fax Server Integration feature. Step 19 Click the Users link and then the Individual Users link. Step 20Click on the name of a user who will be using the enhanced Fax Server Integration feature. Step 21 The Edit User window appears as shown in Figure 8-6.
ShoreTel 13.1
147
Figure 8-6
Enabling Fax Redirect For a User
Step 22Select Redirect Inbound Fax Calls to Site Fax Extension for the Fax Support radio button. Step 23Click the Save button to store your changes.
8.3
Private Numbers
Users can have private numbers that are not listed in the System Directory or in ShoreTel Communicator Quick Dialer, and for which Caller ID information suppressed. Private Numbers are enabled through a check box on the User edit page in ShoreTel Director. When checked, the user's extension becomes a Private Number.
148
The following conditions apply to private numbers:
Private Numbers do not appear in the QuickDialer for dial-by-name operations

or in the ShoreTel Directory Viewer.
Calls placed from a Private Number to an internal party show the caller's name
but not his or her number to the dialed party.
Calls placed from a Private Number to an external party do not deliver a DirectInward-Dial (DID) number as Caller ID when PRI trunks are used for the outbound call. The site CESID number is used for the outbound Caller ID. signaling deliver calling name information but not calling number information. Number user's name but not his or her extension number. Monitor extension selection dialog box.
Calls from a Private Number to an off-system extension on PRI trunks with NI2 Routing slips and the ShoreTel Communicator History viewer show the Private The Private Number users are listed with name and number in the Extension The Private Number user can be dialed directly via the telephone or the
ShoreTel Communicator if his or her extension is known. visible in the ShoreTel Communicator Quick Dialer.
Contacts imported from Outlook or Exchange are never private and are fully CDR database records show both number and name for Private Number users.
However, the Caller-ID Flags field indicates that only the name is valid. inbound or outbound calls.
CDR legacy log files show the number of Private Number user calls that are ShoreTel Director shows number information for Private Number users as with
other users, for example on the User list page.
8.4
Automated Attendant
The ShoreTel system comes bundled with an automated attendant feature that runs on the headquarters server and DVS. The system supports up to 1000 menus, with every server having all menus and with four scheduled modes, providing a simple, flexible solution. Some useful applications for the auto-attendant menus are:
Answering the main number Routing calls to workgroups (for example, sales, support, and so on) Providing automated directions Providing a way for users to log into voice mail (we recommend the # button)
Although the automated attendant is a useful tool, you should take care to design a menu structure that does not frustrate your callers. Here are some helpful hints to keep in mind:
Do not create more than two or three levels of menus. Provide a zero-out option on every menu, so the call can go to a live person (we
recommend 0).
ShoreTel 13.1 149
Remember to provide an option to return to the previous menu (we recommend

the * button).
Try to keep prompts short, quick, and efficient.

Users can record AA menu prompts from their own telephone, instead of having to go through Director. This ability frees the system administrator from having to be involved with the task of recording AA menus, allowing him or her to delegate the task to more appropriate team members. For details on enabling this feature, please see the ShoreTel System Administration Guide.
8.5
Call Handling Delegation

Some users of the ShoreTel system, particularly senior management, often have an administrative assistant who helps them manage items such as their e-mail, calendar, and voice communication. The ShoreTel system administrator can grant permission from ShoreTel Director to individual users to change anothers current call handling mode (CHM) settings. Users who have been delegated to change CHM settings can make changes to the current CHM settings for other users using Operator ShoreTel Communicator. For more information on configuring call handling delegation, see the ShoreTel System Administration Guide.
8.6
ShoreTel Communicator for Windows

ShoreTel Communicator for Windows is the Windows-based client application that runs on the computer of users. This application allows users to access and manage their ShoreTel extension. Examples of tasks that a Communicator user can perform are:
View and manage the content of their voice mailbox. View and manage the call history of their extension. Change their call handling mode. Configure extension options. Initiate and end a phone call. Start conferences. For conferencing, ShoreTel Presenter is automatically installed with
ShoreTel Communicator. For a list of all the capabilities and other details about ShoreTel Communicator, see ShoreTel Communicator for Windows Guide or other platform-specific Communicator guide. The configuration details are in the ShoreTel System Administration Guide.
8.7
ShoreTel Communicator for Mac

ShoreTel Communicator for Mac is a native Mac OS X application, which offers the features available through Communicator for Web, plus additional Mac specific features.
150
8.8
ShoreTel Communicator for Web

Communicator for Web is the browser-based interface that lets users access and manage their ShoreTel extension. Communicator for Web has a subset of the functions in Communicator for Windows. Examples of tasks a Communicator user can perform are:
View and manage the content of their voice mailbox. View and manage the call history of their ShoreTel extension. Change their call handling mode. Configure extension options. Initiate and end calls.
To access ShoreTel Communicator for Web from within your network: Step 1 Open a browser. Step 2 In the URL address field type:
http://<servername>/
where <servername> is the name of your ShoreTel server. You can also use the IP address of the ShoreTel server. Step 3 Press Enter. Step 4 If prompted, enter your client ID and password. Step 5 The ShoreTel Communicator page appears in your browser.
8.9
Bridged Call Appearances

The Bridged Call Appearances (BCA) feature provides bridged information between many separate IP phones, offering the benefit of faster call handling between users. The feature is intended for key system environments, such as a small office with a moderate number of trunks, ShoreTel IP Phones, and users. Custom buttons are configured on each IP phone so that information about incoming calls to a BCA extension is shared among the phones via blinking colored LEDs. Similarly, IP phones can share information about outbound calls placed from a BCA extension by blinking green or red on each phone (see the ShoreTel System Administration Guide for details). Custom buttons can be programmed on IP phone such that each button represents a position in the call stack. Pressing the top-most BCA custom button for outbound calls does not necessarily access trunk 1. There is no one-to-one correlation between the custom buttons programmed for BCA extensions and a particular trunk. Trunks can be associated with BCA extensions in any random manner desired by the system administrator.
8.9.1
Switch Support for Bridged Call Appearances

The ShoreTel voice switches support BCA functionality, with the following caveats:
Up to 24 BCA extensions can be configured per switch.

ShoreTel 13.1 151
The sum of all the trunks that are assigned to a BCA, plus the call stack size of
all BCAs used for extension appearances on a switch cannot exceed 24. For example, you may configure 8 BCAs, each targeted with 3 trunks on the same switch. extension.
A maximum of 32 phones can be configured to point to the same BCA Up to 128 BCA extensions (on other switches) can be monitored.
For details on configuring the BCA feature, please refer to the ShoreTel System Administration Guide.
8.10
Hunt Groups
Hunt groups allow you to route calls to a list of extensions. Hunt groups can be accessed through an extension, DID, and/or DNIS. Hunt groups are supported by ShoreTel Voice Switches and remain available when connectivity to the ShoreTel servers are lost. The hunt group can be used as the backup destination for a workgroup, so that some basic hunting can be done even when the workgroup server is not reachable. To maximize reliability, assign hunt groups to a switch close to the majority of the members and/or trunks associated with the hunt group. A maximum of 8 hunt groups can be assigned to a single switch. A total of 16 user numbers can be assigned to hunt groups on a single switch (i.e., 8 hunt groups with 2 extensions each, 2 hunt groups with 8 extensions, or 1 hunt group with 16 extensions). Hunt groups have scheduled call handling modes similar to route points (for more information about route points, refer to section about setting call control options in the ShoreTel System Administration Guide). There are call handling modes for on-hours and off-hours/holiday (combined). For on-hours, destinations can be set for Always, Busy, and No Answer. For the other call handling modes, only a call forward always destination is provided. When the hunt group is in a call handling mode other than on-hours, the hunt group forwards calls to the Call Forward Always destination. A hunt group can be a destination anywhere in the system where a workgroup is allowed as a destination. This includes call forward destinations from users, workgroups, route points, personal assistants, site operators, site fax redirect extensions, and Find Me destinations.
8.10.1 Hunt Group Busy State

The hunt group can be set as busy from both the switch maintenance page in Director and with a star code from the Telephone User Interface. This feature allows hunt group members to disable hunt group routing when they are temporarily unavailable or leave work early. The busy state of the hunt group is maintained by the hunt groups switch and is not saved in the configuration database or to flash memory. When a switch boots or reboots, the hunt group is in the available state. Use the star code *18 followed by the hunt group extension, to toggle the busy state of the hunt group from a telephone. A class of service setting controls whether a user can change the hunt group busy state. When the hunt group is in the busy state during on-hours, calls are forwarded to the busy destination.
152
8.10.2 Configurable Hunting

There are two types of hunting available with hunt groups: top down or simultaneous ring. All hunt group members are hunted for each call received. For example, in top-down hunting, if the switch is hunting members for an initial call when a second call is received, the second call hunts through all the members again. In other words, each call is hunted independently and in the case of top down, hunting starts at the top. You can also configure:
The number of rings per member (the same number of rings are used for each
member to whom the call is offered).
Whether calls should go to a no answer destination after all members have

been hunted once or whether members are hunted again.
Whether multiple calls are offered to a member simultaneously when the hunt
group receives multiple calls. Calls are not offered to members with full call stacks. Call Forward Always (DND).
Whether members should be hunted when the members call handling is set to
8.10.3 Hunt Group Applications

Hunt groups provide solutions to a several call routing scenarios.
8.10.3.1 Backup Routing for Workgroup

To use a hunt group as a backup when the workgroup server cannot be reached, create a hunt group with workgroup members who will serve as backup members. To use the hunt group when the workgroup server is not reachable because of a network outage, admission control, or a server outage, set the workgroups backup number to the hunt group. When the hunt group is set to offer each member a single call at a time, then call offering is similar to a workgroup. Hunt group members are hunted even though they are logged out or in wrap-up with respect to the workgroup.
8.10.3.2 Hunt Group as a Call Forward Destination

In a small office where individuals generally receive calls directly, users may want someone in the office to answer calls when they are unable to answer. To handle this situation, create a hunt group with everyone in the small office as a member. Individual users can set their call forward destinations to this hunt group. The hunt group can be configured with simultaneous ring, to hunt members only once, and to go to voice mail with Call Forward Busy and Call Forward No Answer conditions. When configured as described above, if a user's call was forwarded to the hunt group after it wasn't answered, the hunt switch hunts everyone in the office. If the call was not answered after the maximum number of rings, the call is forwarded to voice mail where the caller can leave a message in the original target's mailbox.
8.10.3.3 Distribution of Calls to Backup Operators

In this scenario, a primary operator who handles calls to a main company number requires one or more secondary operators to receive the calls when the primary operator becomes too busy.
ShoreTel 13.1
153
To create a hunt group to back up the primary operator, create a hunt group with backup operators. Enter the main operator and all the backups as members of the hunt group in the order in which they are to serve as backups. Set the hunt group for multiple calls to be hunted to a given member, and set the call stack size for each of the users to control the number of calls he or she can receive. When there are incoming calls to the hunt group, the primary operator is offered the calls first. The operator may be offered multiple calls concurrently up to the limit of his or her call stack. If a member's call stack is full, the member is skipped and that particular call is not be offered again (unless the hunt group is set to hunt forever and no member picks up the call before the member is reached again in the hunt list). If a member of the operator group does not answer the hunt call, the call is offered to the next member after the number of rings configured for call forwarding. Thus, even if the primary operator has room on his or her call stack, the call is offered to the next member in the list when the operator does not answer the call in time. If you want calls to go directly to a backup when the primary operator is not available, then set the hunt group not to hunt the members when their current call handling mode is set to Call Forward Always (DND). Operators can use this configuration to pass calls to other hunt group members by changing their call handling mode to Call Forward Always. You may wish to have a hunt group that goes immediately to voice mail or another number during non-working hours. The hunt group can be configured with an offhours schedule. Setup a schedule for on-hours during which the call handling mode for the hunt group is configured to forward calls to another number only if the hunt group is busy or no one answers. For off-hours, set the hunt group to call forward always to voice mail or another number. The auto-attendant automatically changes the hunt group's current call handling mode based upon the configured schedule.
8.10.3.4 Common Line Monitoring

A hunt group can be used for line monitoring. For example, several operators may wish to monitor the same line and all have an opportunity to answer calls at the same time. For this case, set up a hunt group with simultaneous ring. When a call is received, the hunt switch rings all operators in the hunt group whose call stack is not full to the number of rings configured. If the hunt group is set to hunt forever, when the number of rings is reached the hunt switch hunts the same users again. However, the members who have room on their call stack for additional calls may have changed, so each additional hunt may result in different phones ringing.
8.11
Pickup Groups
Group Pickup is a traditional PBX and key system feature used in group environments. The feature allows users in a pickup group to answer any ringing phone in that group, and the feature works best in places where several people work together on a daily basis, such as design firms. If a group member is away from her desk and across the room while her phone rings, she can quickly answer the call from another person's IP phone by pressing the relevant soft key or programmable button, or by using a simple star command from an analog phone. The following example may help illustrate how this feature is used.
154
Assume three hypothetical users (e.g. Mike, Joe, and Sarah) work together and have jobs that require extensive collaboration. They also sit near one another. Their extensions (x1001, x1002, x1003, respectively) would be added to an extension list, and then this list would be associated with a pickup group. The pickup group would have its own extension (e.g. x3755). Note that this extension is invalid and cannot be dialed, and thus acts more like a code than an extension. This non-dialable extension could be programmed into a ShoreTel Communicator toolbar button or an IP phone programmable button on Mike's, Joe's, and Sarah's phones. So, assume Joe's phone rings (x1002) while he is having a conversation with Sarah at her desk. He would hear his phone ringing at his desk, yet he could press the preprogrammed button on Sarah's IP phone in order to answer his own call. Alternatively, if Sarah had an analog phone, Joe could press *13 + 3755 to answer the call. Pickup groups can include the following types of extensions:
User extensions Workgroup extensions Bridged Call Appearance (BCA) extensions

Details
Pickup groups can be associated with a programmable toolbar button, or with a

programmable button on an IP phone, and can work with Extension Assignment.
The user whose phone will be picked up must have class of service Call Pickup
Allowed to use this feature. However, other users need not be members of the pickup group to pickup a call.
This feature is not supported on the ShoreTel T1 and ShoreTel E1 voice switches. The call pickup feature will support:
24 members per group 16 groups per switch The sum of all members assigned to all Pickup Groups on a switch cannot exceed 80 A single user can be a member of up to 5 Pickup Groups
A single switch can host a combined total of up to 24 Hunt Groups, Bridged Call
Appearances, and Pickup Groups.
Users can use this feature in several different ways:

IP Phone If a programmable button has been configured for Pickup Groups, the user can press the button, or key, and enter the extension for the Pickup Group to answer the call. IP Phone If a soft key has been programmed, the user can press the pickup soft key and enter the extension to answer the call. ShoreTel Communicator If one of the pre-programmed buttons in ShoreTel Communicator has been set up for Pickup Groups, a user can enter the extension of the Pickup Group to answer the call. If the key has
ShoreTel 13.1 155
already been programmed with the extension of the Pickup Group, then it is not necessary to enter the extension. ShoreTel Communicator Alternatively, the user can access the pickup command from the Call Menu, followed by the extension. Analog Phone The user can enter the *13 command, followed by the Pickup Group extension to answer calls from an analog phone.
8.12
Workgroups
The ShoreTel system supports up to 256 workgroups, with up to 300 members per workgroup, with a maximum of 300 agents total in the ShoreTel system. A workgroup enables a group of users to appear as a single unit to calling parties. Calls can be routed in top-down, longest-idle, round-robin, and simultaneous-ring fashion (the Simultaneous Ring feature is limited to workgroups of a maximum of 16 members.) Workgroups are typically used by support and sales groups to help automate call handling. The ShoreTel system provides a ShoreTel Communicator - Workgroup Agent Access and ShoreTel Communicator - Workgroup Supervisor Access with the proper software licenses. In addition, you can run workgroup reports on the server to help you understand and assess workgroup activity and performance. ShoreTel analog phones do not display Caller ID for calls forwarded from a workgroup.
8.12.1 Agent Multiplicity

Users can be members of multiple workgroups. The workgroups can be configured for any hunt pattern and can have queuing enabled. A single agent status is applied to all workgroups of which the user is a member. With one status, an agent is either logged-in, logged-out, or in wrap-up for all workgroups of which he or she is a member. In order to manage their own logged in status, users must be provisioned with ShoreTel Communicator - Workgroup Agent. Agents can manage their logged-in state via ShoreTel Communicator, or through the TUI menu in their voice mailbox or via their IP phone programmable button. When an agent is a member of more than one workgroup, that agent can receive calls from any of the workgroups. When an agent is available to take calls from more than one workgroup, and the workgroup would select that agent based on the current hunt pattern for a call, the oldest call is offered to the agent. Queue Monitor shows calls from all the queues of which the user is a member. If the user is a member of only one queue, there is no change to the interface. However, if the user is a member of multiple workgroups, the Queue Monitor shows statistics for each workgroup, and for all workgroups. The user can specify a filter to show only a subset of the queues. The filter only changes the information displayed and does not alter the hunting behavior; the user will still be offered calls from all workgroups of which the user is a member. For workgroup supervisors the Agent Monitor shows all agents from the workgroups of which the supervisor is a member. The Agent Monitor also allows supervisors to filter agents being monitored by selecting individual workgroups.
156
8.12.2 Call Monitor and Barge In

Call Monitor creates a limited conference call where the monitoring party hears the other parties, but the monitored parties do not hear the monitoring party. When a call is being monitored, a warning tone may be played to the participants of the call. The warning tone can be disabled using an option for an Auto-Attendant Menu. Call center administrators typically disable the warning tone to silently evaluate agent performance. When the warning tone is disabled, the menu prompt typically informs the caller that their conversation may be monitored or recorded. Barge In allows one party to join an existing call as a fully conferenced participant. When Barge In is initiated, a brief intrusion tone is played to the other participants. A recording warning tone may be played to the customer during silent monitor. The warning tone is enabled from ShoreTel Director. No tone is played during a Barge In call. WARNINGShoreTel, Inc. does not warrant or represent that your use of silent monitoring or barge in features of the Software will be in compliance with local, state, federal or international laws that you may be subject to. ShoreTel, Inc. is not responsible for ensuring your compliance with all applicable laws. Before configuring the call monitoring features, you may wish to consult with legal counsel regarding your intended use. To simplify discussion of this feature, we will refer to three parties: the supervisor, the agent, and the customer. The supervisor initiates the silent monitor by selecting an agent. The agent is on a call with the customer. The customer may be an internal or external caller, but supervisors and agents must be on extensions. In Silent Monitor, a supervisor hook flash is ignored. However, a hook flash by the other parties works the same as in a two-party call. In particular, an agent flash puts the call on hold and allows a consultative transfer or conference. Because there is a limit of three parties in a conference call, if the agent or customer makes a consultative transfer or conference, the supervisor is automatically dropped. Similarly, if another party barges in a monitored extension, then the silent monitor is dropped. If a conference call is already in progress, it cannot be monitored. If a silent monitor is already in progress, no one else can monitor the call. The supervisor can barge in on a call he or she is silent monitoring. It is not possible to revert a barge in call to a monitored call. If desired, the supervisor can hang up and restart monitoring. After a barge in, the agent remains the controlling party of the call. A subsequent agent hook flash disconnects the supervisor, who is the last party added.
8.12.2.1 Barge In and Silent Monitor Telephony COS Configuration

Each telephony class-of-service (COS) permissions has several additional check boxes and radio buttons in ShoreTel Director to configure Intercom/Paging, Barge In, Call Recording, and Silent Monitor. Allow initiation for Intercom/PagingIf this check box is selected, users within this COS may place an intercom call or page to other system users. If cleared, then no intercom/paging can be initiated. Accept Intercom/PagingRadio button choices are:
ShoreTel 13.1
157
Accept None: If selected, users within this COS may not receive intercom calls
or pages.
Accept All: If selected, users within this COS may receive intercom calls or
pages from anyone in the COS. intercom calls or pages from the person specified in the associated field. Allow initiation for barge inIf this check box is selected, users within this COS may barge in on the calls of other system users. If cleared, then no barge in can be initiated. Accept barge inRadio button choices are:
Accept Only From: If selected, users within this COS may only receive
Accept None: If selected, users within this COS may not receive barge-ins
from anyone.
Accept All: If selected, users within this COS may receive barge-ins from
anyone else with this COS permission. ins from the person specified in the field accosted with this radio button. Allow initiation for record others callsIf this check box is selected, users within this COS may record the calls of other system users. If cleared, then no call recording of others can be initiated. Accept record others callsRadio button choices are:
Accept Only From: If selected, users within this COS may only receive barge-
Accept None: If selected, users within this COS may not have their calls
recorded from anyone.
Accept All: If selected, users within this COS may have their calls recorded
from anyone else with this COS permission. recorded by the person specified in the field associated with this radio button. Allow initiation for silent monitorIf this check box is selected, users within this COS may monitor other system users. If cleared, then no monitoring of others can be initiated. Accept silent monitorRadio button choices are:
Accept Only From: If selected, users within this COS may only have their calls
Accept None: If selected, users within this COS cannot be monitored by

anyone.
Accept All: If selected, users within this COS can be monitored by anyone else
with this COS permission. by the person specified in the field associated with this radio button. There are no special permissions for ShoreTel Enterprise Contact Center agents or supervisors. They must have these same COS permissions with appropriate settings to enable contact center silent monitoring and barge in.
Accept Only From: If selected, users within this COS can only be monitored
158
8.13
Enterprise Telephony Features

ShoreTel provides two options for implementing music on hold (MOH).
8.13.1 Music on Hold

Jack-Based Music on Hold: Audio is provided through the audio input port on
the ShoreTel Voice Switches that support MOH. A site needs only one MOH source. Appendix F describes the switches that support MOH.
File-Based Music on Hold: Audio is provided through a digital file. 8.13.1.1 Jack-Based Music on Hold
Connecting the desired music source to the selected ShoreTel Voice Switch provides MOH. The source can be recorded music or custom music, with prerecorded announcements or other information for callers. Each site with music on hold must have its own music source. To conserve bandwidth, music is not sent across the WAN between sites, and MOH is selected by the ShoreTel Voice Switch where the CO trunks are configured (i.e., the holding party). IP phone users do not receive MOH when they are on an internal call. See the ShoreTel System Administration Guide for additional information. Before installing the system, confirm that you have music sources for each site, including the music and the required equipment for playback. Details related to MOH over SIP Trunks:
Music On Hold for SIP trunks is offered for environments where external users
reach the ShoreTel system through SIP trunks (such as BRI via a SIP gateway).
If there is a MOH source at the same site as a SIP trunk, these trunks are The existing rules for MOH also apply to MOH for SIP Trunks:
MOH is not sent across sites.
connected to that source when placed on hold, and the device at the other end of the trunk connects directly to the MOH switch.
The MOH source must be at the same site as the SIP trunk that utilizes it.
If one of the parties in a conversation places the other party on hold, only the
person who was placed on hold hears MOH.
MOH is supported on a SIP tie trunk to IP Phones in the following scenarios:

From an IP phone to another IP phone. From an analog phone to an IP phone (i.e. putting the call on hold from an analog phone). From any trunk (PRI/analog) while placing an IP phone caller on hold. From any phone type to a SIP trunk device such as a Hitachi phone over the SIP tie trunk and onto the SIP trunk device.
ShoreTel 13.1
159
8.13.1.2 File-Based Music on Hold

Music on hold audio files can be added to the system using ShoreTel Director. The file can be recorded music or custom music, with prerecorded announcements or other information for callers. When file-based MOH is enabled, files can be played to all endpoints, except SIP-tie trunks. To enable file-based MOH, MOH source(s) must be configured to play the uploaded music files. Any combination of Headquarters Server, DVS Server(s), or V-Switch(es) can be configured as MOH sources. When an MOH file is added to the system, the file is stored on the Headquarters server, and is then automatically distributed to each server in the system that has file-based MOH enabled. An MOH music file can be assigned to a specific user or group of users via Director. See the ShoreTel System Administration Guide for additional information. When a call is put on hold with file-based MOH enabled, the streaming source is selected from the configured sources for the site. Sources with a higher maximum concurrent call limit are selected more frequently. After a source reaches the maximum call limit, the source is no longer available for additional MOH calls. In this case, another configured MOH source for the site is tried. If all the sources at a site are unavailable or unreachable, MOH falls back to the parent sites and repeats the process. If all file-based MOH sources for the site and all its parents are exhausted, the call attempts to fall back to jack-based MOH using the rules described in Jack-Based Music on Hold on page 159. The resources used to generate MOH are shared with other voicemail services on these sources. When planning, it is important to consider if a source will be able to handle concurrent usage of MOH calls, VM, and AA activity. If more resources are required, an additional source dedicated to MOH can be added to the ShoreTel system. For example, a DVS can be added with file-based MOH enabled and no voice mailboxes or other server features configured. For more information, see "General Feature Limitations" on page 328.
8.13.1.3 Which File is Played When a Call is Put On Hold?

The file played when a call is put on hold is selected using the following rules: 1. If the call is incoming through DNIS and an MOH file is configured for that DNIS number, the MOH file is played for the duration of the call, even after a transfer. 2. If the first rule does not apply and an MOH file is configured for the User Group of the user holding the call, that User Group's MOH file is played. 3. If neither of the rules above applies and an MOH file is configured for the default system MOH file, the system MOH file is played. 4. If none of the rules above applies, MOH uses the Jack-based MOH according to the rules described in Jack-Based Music on Hold on page 159.
160
8.13.1.4 Jack-Based MOH vs. File-Based MOH

Table 8-2 MOH Feature Can control music to be played? Can stream music crosssite? Can stream music to internal phones? Can stream music to SIP extensions? Music streaming source? When call is first held, does music start from beginning? If call is held a second time, does music resume from where it last ended? Does each stream use its own bandwidth? Jack-Based MOH vs. File-Based MOH Jack-Based MOH Yes, per site. No. No, external only. No, external only. MOH Jack on switches. No. File-Based MOH Yes, by DNIS, User Group or System Default. Yes. Yes. Yes. File saved on server or voicemail model switches. Yes.
No.
Yes.
No, bandwidth is used only once per switch, except for SIP trunks.
Yes.
8.13.2 Overhead Paging

The ShoreTel system can provide single-zone overhead paging for each site by using the audio output port on those ShoreTel voice switches that provide an audio output port. For sites that require overhead paging, you must designate one of the ShoreTel voice switches to provide paging. In addition, you must provision your selected paging equipment for connection to the ShoreTel system.
8.13.3 Multi-site Paging Groups

As an alternative to a paging system, you can designate groups of system extensions that can be paged by dialing a single system extension. In this way, audio is routed to a group of phones and played on the phone speaker as opposed to playing the audio announcement on an overhead paging system. You can also add a paging extension (associated with a sites overhead paging system) to a paging group in order to simultaneously play audio on a group of phones and also an overhead paging system. Refer to the ShoreTel System Administration Guide for details.
ShoreTel 13.1
161
Additionally, if more than one server is installed in the ShoreTel system, an administrator can choose to record and deliver the group page to another site using that sites DVS. This will decrease WAN bandwidth consumption if there is a need to deliver a page to users at a remote site. Pages to on-hook IP phones will automatically be announced on the IP phone speaker. Pages to IP phones or analog phones that are already on a call are treated as a normal call. Call handling modes do not apply to page calls. A maximum of 100 extensions can be paged at one time. Group paging is not available to external callers. Refer to the ShoreTel System Administration Guide for more information about establishing and managing paging groups.
8.13.4 Night Bell

The ShoreTel system can provide an overhead night bell on a per site basis using the audio output port associated with ShoreTel Voice Switches that provide an audio output port.
8.13.5 Intercom
A user can initiate an intercom call through a programmable button on an IP phone that has been programmed with the Intercom feature, via the ShoreTel Communicator, or via the phone by entering *15 + extension number. Users must be configured to use the intercom feature through ShoreTel Director. All intercom calls defeat the user's call coverage (Call Handling Mode settings) and cannot be forwarded. An intercom call to an idle IP phone is auto-answered and connected through the called party's speakerphone. Immediately after the call is auto-answered, the called party hears an announcement tone and the calling party hears a beep tone. If the called phone was taken off-hook automatically, the switch puts the phone back onhook when the intercom call terminates. An intercom call to an analog phone or SoftPhone that is off-hook with no active call (for example, in hands-free mode) is auto-answered through the audio device that is currently active. If the called party is on-hook or is on an active call, the call is offered as an ordinary call, except that call coverage is still defeated. An intercept tone (fast-busy) is played if the calling user does not have the appropriate permissions. If the called party does not accept intercom calls due to CoS permissions, the call is offered as an ordinary call.
8.13.5.1 Intercom Telephony COS Configuration

Each telephony class-of-service permissions has two additional check box settings in ShoreTel Director to configure intercom permissions. Allow initiation for Directed Intercom/PagingIf enabled, users with this COS may make intercom calls to other users of the system. If disabled, then intercom calls cannot be made. Accept Directed Intercom/PagingIf enabled, users with this COS may accept intercom calls. If disabled, then intercom calls are received as normal calls.
162
8.13.6 Call Recording

The ShoreTel system provides the capability for users to record calls. To be available, call recording must be configured in ShoreTel Director by a system administrator. Refer to the ShoreTel System Administration Guide for details on configuring this feature. Users can use ShoreTel Communicator -Personal Access to request that a call be recorded to voice mail. Supervisors may use Agent Monitor to record an agents call. Ordinarily, both ShoreTel Communicator and Agent Monitor will indicate when a call is being recorded, (although this behavior can be overridden with the Silent Recording feature to prevent agents from knowing that their calls are being recorded.) With Silent Recording, if the call is recorded by the workgroup supervisor, the indicator does not appear in Agent Monitor. (The person invoking the recording sees the indicator other parties do not.) In this way, calls can be silently recorded to allow operators and supervisors to hide the fact that they are recording agents' calls. This hidden behavior may be desirable when a supervisor is monitoring the telephone manners of a new employee. When the recording is silent or hidden, ShoreTel Communicator offers no visual or audible indication that the call is being recorded, and the periodic beeping sound (used to notify call participants that their calls are being recorded) is suppressed. The maximum number of simultaneous recordings equals the number trunk ports. The following limitations apply to call recording:
Call recording is only available via ShoreTel Communicator - Personal Access

or a programmable button on IP phones.
Only calls on trunks (not extensions-to-extensions) can be recorded. 2-way and 3-way calls can be recorded if one of the legs of the call is a trunk. Calls to a legacy ShoreTel Conference Bridge cannot be recorded Recording stops when the call is parked, unparked, or transferred
ShoreTel, Inc. does not warrant or represent that your use of call monitoring or recording features of the software will be in compliance with local, state, federal or international laws that you may be subject to. ShoreTel, Inc. is not responsible for ensuring your compliance with all applicable laws. Before configuring the call recording feature, you may wish to consult with legal counsel regarding your intended use.
8.14
ShoreTel Enterprise Contact Center Solution

If you purchased the ShoreTel Enterprise Contact Center Solution, you must configure an appropriate number of route points with adequate call stacks. Route points are a licensed feature. Ensure that you have sufficient licenses to support your planned deployment. For information on route points, see the ShoreTel System Administration Guide. For information on the ShoreTel Enterprise Contact Center Solution, please review the ShoreTel Enterprise Contact Center Solution Installation Guide and the ShoreTel Enterprise Contact Center Solution Administration Guide.
ShoreTel 13.1
163
164
Chapter 9
Telephone Planning and Ordering

This chapter provides information on the types of telephones supported by the ShoreTel system and what to consider when planning phones for your system. The topics discussed include:
Recommendations on page 165 Application Considerations on page 165 ShoreTel IP Phones on page 167 Analog Phone Requirements on page 173 Fax Machines and Modems on page 176 Fax Machines and Modems on page 176
9.1
Recommendations
The following recommendations will assist you with planning, ordering, and installing your telephones:
Select your telephones based on user requirements, your wiring infrastructure,

and system objectives.
Order your telephones early. If you need a large quantity of them, you will need
to order them several weeks in advance.
Have your cabling contractor place and test all your telephones. Have the
contractor unpack, assemble, place, and test every telephone so that you can avoid this simple but time-consuming task. outlet at each location.
If the telephone you choose requires local power, make sure there is an available
9.2
Application Considerations
This section describes considerations for a business to consider before ordering telephones.
9.2.1
Operators, Receptionists, and Call Center Agents

Employees who typically answer and transfer large numbers of calls should have a comfortable headset. Also, they can use the Handsfree Mode feature to turn off audible dial tone. With these supports, employees can use ShoreTel Communicator to answer and transfer calls rapidly without the need to touch the telephone.
ShoreTel 13.1
165
Chapter 9: Telephone Planning and Ordering
If an operator is using one of the ShoreTel IP Phone multiline models, the Automatic Off-Hook Preference feature allows the user to select which audio path (speakerphone or headset) is automatically activated when a call is placed or when an incoming phone call is received. The featured can be configured from Director, ShoreTel Communicator, or from the IP phone. Operators may also benefit from the programmable buttons feature, which allows users to assign functions to the custom keys on the multiline phones, and on the BB24 device. The programmable buttons feature allows a user to assign the extension monitoring feature to one of the custom buttons. The Programmable Toolbars feature allows a system administrator to program common functions and operations to buttons in a users ShoreTel Communicator window so that an operator can perform many common tasks (e.g. answer call, transfer call, invoke URL, etc.) at the click of a button. Some operators will benefit from a cordless telephone or a cordless headset, which gives them greater mobility.
9.2.2
Receptionists
Receptionists are typically satisfied with a standard desk telephone that supports Caller ID and Message Waiting with a speakerphone and mute button.
9.2.3
General Users
Typically, most users will be satisfied with a standard desk telephone that has a speakerphone and mute button, and supports Caller ID and Message Waiting. ShoreTel IP phones are fully featured and appropriate for most users. IP phones come with the ShoreTel features available on preprogrammed buttons, and they can be deployed in areas where there are no computers to run the ShoreTel Communicator Personal Access.
9.2.4
Conference Rooms
Most conference rooms need a speakerphone. Because conference rooms do not have a ShoreTel Communicator client in the room, a ShoreTel IP phone can support conference rooms discussions. The ShoreTel IP phone provides single-button access to features such as transferring and conferencing calls. ShoreTel designed the IP 655 to fulfill the needs of meetings in small to medium-size conference rooms.
9.2.5
Lobby Phones
A cost-effective wall-mount, slim-line, or desk telephone is adequate for most lobby phones, hall phones, and the like. The IP110/115 models offer a cost-effective telephone that is ideal for use in lobbies, lounges, or other common areas.
9.2.6
Multi-line Phones
ShoreTel offers extension monitoring from an IP phone. With this feature, an administrative assistant or workgroup supervisor can monitor up to five system extensions. The extension monitor feature can be enabled for ShoreTel IP phones from the User edit pages of ShoreTel Director. For more information, see the ShoreTel System Administration Guide.
166
9.2.7
Teleworkers
Both analog and IP phones can be included in a ShoreTel system as remote phones. Analog phones require use of the Extension Assignment, while IP phones are supported by setting an IP address range through ShoreTel Director.
9.3
ShoreTel IP Phones
This section describes the different models of ShoreTel IP Phones. The subsection for each phone models lists the features of the phone to help network planners decide which phones to buy for the different uses within the customers business. The ShoreTel Voice Switches control the ShoreTel IP Phones. The ShoreTel IP Phone multiline models offer user-programmable buttons so that users can assign common operations to the buttons on their phones. These phones also support the Automatic Off-Hook Preference feature. This feature lets the user select the audio output when the user initiates or receives a call. The audio output can be the handset, built-in loudspeaker, or headset. Similarly, the multiline models support the Plantronics CS50 wireless headset. Users can answer or end calls by pressing the activation button on this headset when they hear their phone ring. The 565g model offers support for use with some Bluetooth wireless headsets. NOTE Multiline models: IP560g and newer IP560 models support this feature while older IP560 models do not. To determine an IP560s compatibility, look at the model number on the back of the phone. If the model number ends with -03 or higher, the phone supports this feature. If the model number ends with 01 or -02, the phone does not support the feature. The ShoreTel IP Phone BB24 (button box) is a unit that plugs into a phone and adds 24 extension buttons to a phone. Additionally, it has an Ethernet switch port, allowing connection of a PC or the connection of an additional BB24 or IP Phone. All ShoreTel IP Phone models can use custom ring tones. The system administrator can load a pair of internal and external ring tones in WAV file format onto each phone. Each user can have a unique ring tone. For instructions on how to load ringtones, refer to the Configuring IP Phones chapter in the ShoreTel System Administration Guide.
9.3.1
ShoreTel IP Phone 110

The ShoreTel IP Phone 110 phone is a phone for general use. Its features include:
Single-line display for caller information Six function keys (Conference, Hold, Intercom, Redial, Transfer, Voice Mail) Ethernet Switch port for connecting a PC to the back of the phone Support for basic media encryption for calls inside a ShoreTel network Ability to load custom ring tones in WAV file format
9.3.2

The ShoreTel IP Phone 115 phone is based on the IP110 model with the addition of an external microphone to support speakerphone functionality.
ShoreTel 13.1
167
Its features include:
External microphone to support speakerphone Single-line display for caller information Six function keys (Conference, Hold, Intercom, Redial, Transfer, Voice Mail) Ethernet Switch port for connecting a PC to the back of the phone Support for basic media encryption for calls inside a ShoreTel network Ability to load custom ring tones in.wav file format
9.3.3
ShoreTel IP Phone 212k

The 212k IP phone is designed to function as a key phone and offers 12 custom buttons that can be used for line appearance and other functions. The 212k is ideal for small offices and branch offices that require key system functionality. Its features include:
Scrolling text that allows for the display of more information. Menu and Select buttons that provide services similar to soft keys and scroll
bar, and that assist in phone navigation and programming.
Eight function keys (Voice Mail, Transfer, Options, Conference, Directory,
Intercom, Redial, Hold). InstaDial functionality in which calls are automatically transferred after digit collection stops and a configurable timeout period has expired. Automatic Off-Hook Preference that lets users select which audio path. (speakerphone or headset) is auto-activated when calls are sent or received. Ethernet Switch port for connecting a PC to the back of the phone. A first (upper left-most) custom button that is reserved for line appearance only and cannot be configured to perform other functions. Support for basic media encryption for calls inside a ShoreTel network. Ability to load custom ring tones in.wav file format. Built-in handset lifting functionality to support certain Plantronics wireless headset models.
9.3.4
ShoreTel IP Phone 230/230g

The ShoreTel IP230 Phone is a full-featured IP phone with the added functionality of programmable buttons. The ShoreTel IP Phone 230g offers all features of the IP Phone 230 with the addition of switchable 10BaseT, 100BaseT, and 1000BaseT support for users with gibabit network requirements for their desktop workstation. Its features include:
The IP230 has 3 custom buttons that can be programmed for extension
monitoring, speed dial, and other functions. Note that the top-most button is reserved for line appearance. (Each button is an LED-enabled hard key and has an associated 6 character label on the LCD.) Eight function keys (Voice Mail, Transfer, Options, Conference, Directory, Intercom, Redial, Hold). InstaDial functionality in which calls are automatically transferred after digit collection stops and a configurable timeout period has expired. Monochrome black and white display.
168
Automatic Off-Hook Preference that lets users select which audio path
(speakerphone or headset) is auto-activated when calls are sent or received. Ethernet Switch port for connecting a PC to the back of the phone. Support for basic media encryption for calls inside a ShoreTel network. Support for two-line caller ID display feature, which displays the caller name and number on two separate lines for in-coming calls and outbound calls. Ability to load custom ring tones in.wav file format. Built-in handset lifting functionality to support certain Plantronics wireless headset models. Integrated VPN client (IP 230g only).
9.3.5

The ShoreTel IP265 Phone is a full-featured IP phone that is similar to the ShoreTel IP230 phone but with three additional programmable buttons and a color LCD display. Its features include:
2.7-inch TFT-LCD Color display with backlighting. Ability to download and display a 24-bit.bmp wallpaper file. Six custom buttons that can be programmed for extension monitoring, speed
dial, and other functions. Note that the top-most button is reserved for line appearance. (Each button is a tri-color LED-enabled hard key and has an associated 6-character label on the LCD.) Eight function keys (Voice Mail, Transfer, Options, Conference, Directory, Intercom, Redial, Hold). InstaDial functionality, in which calls are automatically transferred after digit collection stops and a configurable timeout period has expired. Automatic Off-Hook Preference that lets users select which audio path (speaker, headset, wireless headset) is auto-activated when calls are sent or received. Ethernet Switch port for connecting a PC to the back of the phone. Support for basic media encryption for calls inside a ShoreTel network. Support for two-line caller ID display feature, which displays the caller name and number on two separate lines for in-coming calls and outbound calls. Ability to load custom ring tones in.wav file format. Built-in handset lifting functionality to support certain Plantronics wireless headsets.
9.3.6

The ShoreTel IP Phone 560 is for managers, assistants, and operators who have high call volumes and share call flows with other users. Its features include:
Caller ID display for up to six calls simultaneously. Backlit display. Monitoring support for up to five extensions. Eight function keys. Four soft keys. Ethernet Switch port for connecting a PC to the back of the phone. InstaDial functionality in which calls are automatically transferred after digit collection stops and a configurable timeout period has expired.
169
ShoreTel 13.1
Automatic Off-Hook Preference that lets users select which audio path
(speakerphone or headset) is auto-activated when calls are sent or received. Support for basic media encryption for calls inside a ShoreTel network. Support for programmable buttons and extension monitoring. Support for two-line caller ID display feature, which displays the caller name and number on two separate lines for in-coming calls and outbound calls. Ability to load custom ring tones in.wav file format. Built-in handset lifting functionality to support certain Plantronics wireless headsets.
9.3.7
ShoreTel IP Phone 560g

The ShoreTel IP Phone 560g is a high-end phone designed for executives, assistants, and operators who handle high call volumes and share call flows with other users yet require the benefit of 1000BaseT operations. Its features include:
Intercom, Redial, Hold). Four soft keys. Gigabit Ethernet Switch port for connecting a PC to the back of the phone. Caller ID displayed for up to six calls simultaneously. Backlit display. Monitoring for up to five extensions. InstaDial functionality in which calls are automatically transferred after digit collection stops and a configurable timeout period has expired. Automatic Off-Hook Preference that lets users select which audio path (speakerphone or headset) is auto-activated when calls are sent or received. Support for basic media encryption for calls inside a ShoreTel network. Support for programmable buttons and extension monitoring. Support for two-line caller ID display feature, which displays the caller name and number on two separate lines for in-coming calls and outbound calls. Ability to load custom ring tones in.wav file format. Built-in handset lifting functionality to support certain Plantronics wireless headsets. Integrated VPN client. Installation Notes:
Supports 10BaseT, 100BaseT, and 1000BaseT operations. Six custom buttons that can be used for line appearance and other functions. Eight function keys (Voice Mail, Transfer, Options, Conference, Directory,
The ShoreTel IP560g telephone requires a gigabit-compatible Power over
Ethernet (POE) power supply that complies with IEEE802.af. The 560g phone is a Class 3 device with a maximum consumption of 8.2 watts. Please use 8.2 watts for capacity planning with Gig POE switches on multiple deployments. The 560g model requires more power than the other ShoreTel models, and thus the 560g phone is not compatible with the ShoreTel IP Phone power adapter used with other ShoreTel phone models. The 560g model cannot be daisy-chained from the Button Box (BB24). The BB24 pass-through power is limited to Class 2 devices and the 560g is a Class 3 device. This means the BB24 cannot forward adequate power to an IP 560g phone. The ShoreTel IP560g telephone uses Category 5e or Category 6 Ethernet cables. We do not certify the use of Category 5 Ethernet cables because they can lead to
170
lower connection speed or performance problems during high data-rate transfers.
9.3.8
ShoreTel IP Phone 565g

The ShoreTel IP Phone 565g is a high-end phone designed for executives, assistants, and operators who handle high call volumes and share call flows with other users. The ShoreTel IP Phone 565g supports 1000BaseT operations and Bluetooth wireless headsets. Its features include: 3.5-inch TFT-LCD Color display with backlighting. Ability to download and display a 24-bit.bmp wallpaper file. Support for some Bluetooth wireless headset models. Supports 10BaseT, 100BaseT, and 1000BaseT operations. The first button is the Extensions Call Appearance button. It cannot be changed. Other tri-color custom buttons can be used for line appearance and other functions. Eight function keys (Voice Mail, Transfer, Options, Conference, Directory, Intercom, Redial, Hold). Four soft keys. Gigabit Ethernet Switch port for connecting a PC to the back of the phone. Caller ID displayed for up to six calls simultaneously. Monitoring for up to five extensions. InstaDial functionality in which calls are automatically transferred after digit collection stops and a configurable timeout period has expired. Automatic Off-Hook Preference lets a user select the audio outlet to activate when initiating or receiving calls (speaker, headset, wireless headset, or Bluetooth). Support for basic media encryption for calls inside a ShoreTel network. Support for programmable buttons and extension monitoring. Support for two-line caller ID display feature, which displays the caller name and number on two separate lines for in-coming calls and outbound calls. Ability to load custom ring tones in.wav file format. Built-in handset lifting functionality to support certain Plantronics wireless headsets. Integrated VPN client. Installation Notes:
The ShoreTel IP565g telephone requires a gigabit-compatible Power over
Ethernet (POE) power supply that complies with IEEE802.af. The 565g phone is a Class 3 device with a maximum consumption of 8.2 watts. Please use 8.2 watts for capacity planning with Gig POE switches on multiple deployments. The 565g model requires more power than the other ShoreTel models, and is thus not compatible with the ShoreTel IP Phone power adapter used with other ShoreTel phone models. The 565g model cannot be daisy-chained from the Button Box (BB24). The BB24 pass-through power is limited to Class 2 devices and the 565g is a Class 3 device. This means the BB24 cannot forward adequate power to an IP 565g phone. The ShoreTel IP565g requires the use of Category 5e or Category 6 Ethernet cables. We do not certify the use of Category 5 Ethernet cables. They can lead to
ShoreTel 13.1
171
lower connection speed or performance problems during high-data transfer conditions.
9.3.9

The ShoreTel IP Phone 655 is a high-end IP phone for executives and executive assistants. It also functions as a highly capable speakerphone for use in executive offices and small to medium-size conference rooms. The ShoreTel IP Phone 655 offers advanced audio performance and IP telephony functionality. The ShoreTel IP Phone 655 provides a touch screen interface that enhances productivity. Advanced applications enabled by the large color touch screen display include enhanced directory and call history applications with real-time telephony presence information and visual voicemail with both playback and composition capabilities. For more details about the ShoreTel IP Phone 655, see the ShoreTel IP Phone 655 Installation and User Guide. Its features include: feedback. Connectors for up to two remote microphones for better conference room coverage. 10/100/1000 Ethernet. Five capacitive touch keys (mute, headset, redial, volume control and speakerphone). Beam-forming microphone array with noise-canceling capabilities for offices and small to medium-size conference rooms. An optional pair of extension microphones enhance the microphone pickup in larger rooms. Visual voicemail and enhanced Directory with telephony presence. Virtual keyboard for text entry for additional user capabilities. Easy personalization - wallpaper images and ring tones. Supports 10BaseT, 100BaseT, and 1000BaseT operations. 12 line buttons that can be used for line appearance and other functions. 6 function and audio control keys (Voice Mute, Speaker, Headset, Redial, Call Volume +/-). Gigabit Ethernet Switch port for connecting a PC to the back of the phone. InstaDial functionality in which calls are automatically transferred after digit collection stops and a configurable timeout period has expired. Automatic Off-Hook Preference that lets users select which audio path (speaker, headset) is auto-activated when calls are sent or received. Support for secure RTP with AES encryption for calls inside a ShoreTel network. Support for programmable buttons and extension monitoring. Integrated VPN client. Installation Notes:
5.7-inch TFT-LCD color touch-screen display with backlighting and haptic
The ShoreTel IP Phone 655 telephone requires a gigabit-compatible Power over
Ethernet (POE) power supply that complies with IEEE802.af. The phone is a Class 3 device with a maximum consumption of 9.1 watts. Please use 9.1 watts for capacity planning with Gig POE switches on multiple deployments. The ShoreTel IP Phone 655 model requires more power than the other ShoreTel models, and is thus not compatible with the ShoreTel IP Phone power adapter used with other ShoreTel phone models. The ShoreTel IP Phone 655 model cannot be deployed with a Button Box (BB24).
172
The ShoreTel IP Phone 655 requires the use of Category 5e or Category 6
Ethernet cables when deployed in 1000 BaseT networks. Using Category 5 Ethernet cables is not officially supported and may lead to lower connection speed and/or performance issues during high-data transfer scenarios.
9.3.10 ShoreTel IP Phone BB24

The ShoreTel 24 IP Button Box provides additional shortcut functions for users of the multiline phones. The BB24 behaves like an additional set of 24 programmable buttons in additional to the buttons that already exist on the multiline phones. Its features include: Twenty-four programmable buttons. Ability to assign up to four Button Boxes to a multiline phone. Support for programmable buttons feature. Ability for each user to define layouts for up to four BB24s allowing a maximum of almost 100 programmable buttons for most phones (exact number varies depending on which phone the BB24 is connected). Custom buttons in which each is an LED-enabled hard key and has an associated six character label on the LCD. Ethernet switch port for connecting a PC to the back of the phone. Ability to forward power to one additional unpowered device to support a daisy-chain configuration. For detailed information on available options and how to use them, refer to the ShoreTel Programmable Buttons User Guide.
For installation instructions, refer to the ShoreTel 24 IP Button Box Quick Install Guide.
9.4
Analog Phone Requirements

The ShoreTel system supports standard analog 2500-type telephones, including the CLASS (Custom Local Area Signaling Services) features of Caller ID Name, Caller ID Number, and Message Waiting in the United States and Canada. Outside the United States and Canada, the ShoreTel system supports the local standard analog telephones that support DTMF signaling. Analog Caller ID Number and Message Waiting are supported in the following countries:
France Germany Italy Spain United Kingdom

Outside of the United States, Canada, and the countries mentioned in the bulleted list above, the features of Caller ID Name, Caller ID Number, and Message Waiting are not supported. See International Planning and Installation on page 311, for more information. The following list summarizes key requirements for analog phones:
2500-type telephones: The ShoreTel system supports standard 2500-type

telephones. (It does not support 500-type rotary telephones.)
ShoreTel 13.1
173
DTMF signaling, even during power failure: The ShoreTel system uses
DTMF tones for signaling with telephones and trunks. It is mandatory that the telephone support DTMF signaling even when power is interrupted, to allow users to make calls in emergency situations.
control features from the telephone, including transfer, conference, pickup, and park. ShoreTel does not recommend using the hook switch to simulate the Flash button, since this can lead to accidental hang-ups. If a speakerphone is required: speakerphone have a mute button. Since telephones are often designed with the residential market in mind, some speakerphones do not have a mute button, which may lead to end-user complaints. If message waiting is required (United States and Canada only): compatible telephones provide a highly reliable method for turning message waiting lights on and off. Telephones that rely on a stutter dial tone to control the message waiting light are unreliable and should be avoided. ShoreTel does not support telephones that use voltage-driven message-waiting lights. Select telephones from a reputable manufacturer. Although most phones on the market have good quality, we recommend that customers avoid stay clone or lowend phones. Here are some additional considerations:
Flash button: A Flash button is required on analog phone sets to activate call
Mute button: Users in the enterprise typically demand that their
CLASS (FSK) message waiting indicator: CLASS message waiting
Not too many buttons: Some telephones come with lots of complicated
buttons and options that drive up the price of the device. The ShoreTel system delivers advanced features through desktop applications that are integrated with your enterprise tools. Telephones with lots of features and buttons are not necessary. mail system for all users at all sites. Telephones with integrated answering machines are not necessary.
No answering machine: The ShoreTel system includes an integrated voice No hold button: Telephones with a hold button do not actually put the caller
on system hold, so the caller will not hear music on hold or have the correct call control status details.
9.4.1
Caller ID Standard Support

Table 9-1 lists the callerID standards the ShoreTel system supports for analog telephones by country. Table 9-1 Caller ID Standard Support for Analog Phones by Country Country United States Canada Hong Kong Singapore
Caller ID Standard BELLCORE BELLCORE BELLCORE BELLCORE
174
Table 9-1
Caller ID Standard Support for Analog Phones by Country Country Mexico China United Arab Emirates South Korea Philippines South Africa Costa Rica Israel Indonesia Fiji Mongolia France **Luxembourg Monaco **Saudi Arabia Romania Chile Hungary Germany Switzerland Austria Norway **Taiwan **Thailand Poland **Czech Republic Italy Spain *Argentina United Kingdom Ireland Australia Malaysia Brazil Netherlands New Zealand Portugal Belgium Denmark Sweden India Japan
175
Caller ID Standard BELLCORE BELLCORE BELLCORE BELLCORE BELLCORE BELLCORE BELLCORE BELLCORE BELLCORE BELLCORE BELLCORE ETSI ETSI ETSI ETSI ETSI ETSI ETSI ETSI ETSI ETSI ETSI ETSI ETSI ETSI ETSI ETSI ETSI ETSI BT BT NONE NONE NONE NONE NONE NONE NONE NONE NONE NONE NONE
ShoreTel 13.1
Table 9-1
Caller ID Standard Support for Analog Phones by Country Country Finland (unsupported DTMF variation) Greece Bulgaria
Caller ID Standard NONE NONE NONE
**Indicates uncertainty as to whether country supports configured standard.
9.5
Fax Machines and Modems

The ShoreTel system supports fax machines and modems in the United States and Canada (and not elsewhere). Fax and modem calls are more sensitive to network problems than voice conversations. The human ear does not notice a lost packet during a voice conversation, but when a packet is lost during a fax transmission the line may be dropped. During a modem call, a lost packet can cause a retransmission. In the worst case, fax machines and modems will not establish a connection or may drop the call altogether. In general, fax and modem calls work across a local area network, but work on wide area networks only when there is virtually no packet loss and little jitter. The ShoreTel system automatically detects both fax and modem tones, and boosts the voice encoding to a higher value to increase throughput. (G.711 at 64 Kbps is recommended.) It also stops the nonlinear processing of the echo canceller and fixes the size of the jitter buffer to a preset level. In addition, for modems, the echo canceller is frozen or stopped, since the modems use their own network echo cancellers.
9.5.1
Fax Machines
Fax machines require a high-quality IP network for proper operation. The ShoreTel system supports distinctive ringing for inbound calls: calls from external parties have the classic single ring, whereas calls from internal parties have a distinctive double ring. Some fax machines detect the ringing pattern before answering and might not answer internal calls because of the distinctive ring pattern. In particular, you must turn off the Intelligent Ring Mode on some Hewlett-Packard fax machines to receive calls from internal parties.
9.5.2
Modems
The ShoreTel system supports moderate-use modem applications on the system. This is generally considered to be modem calls up to 28.8 Kbps that do not last longer than 15 minutes. If your application demands greater performance, you should bypass the ShoreTel system or move your modem application to a pure IP-based solution. The expected modem performance in different configurations is as follows:
Analog connection speeds will not exceed 33.6 Kbps and could be lower.
External factors, including poor-quality trunk lines, ISP limitations, and multiple analog-to-digital conversions in the network, can have a significant impact on connection speeds.
176
Modem calls demand a high-quality network with virtually no packet loss.

Packet loss should not exceed 0.1%, which can be achieved on a local area network or in a wide area network using leased T1 facilities.
Analog trunk ports should not be used if a digital trunk (T1) is available, since
performance will be limited to 28.8 Kbps maximum. Digital trunks should be used instead.
Connection speeds are significantly affected by multiple packet-to-circuit
conversions (including modem calls from one ShoreTel system to another). If a T1 line is used, modems should be able to connect at K56Flex/V.90 or approximately 48 Kbps.
ShoreTel 13.1
177
178
Chapter 10
Server Requirements
This chapter helps with the specific hardware and software requirements for the ShoreTel headquarters server main and the distributed ShoreTel servers. The topics in include:
General Recommendations on page 179 Requirements for ShoreTel Enterprise Systems on page 179 Requirements for ShoreTel Enterprise Systems on page 179 Requirements for VMware Environments on page 185 Hard Disk Requirements on page 187 Preparing Your Server for the ShoreTel Installation on page 189 ShoreTel Mobility Support on page 198 Third-Party Applications Support on page 198
10.1 General Recommendations

The following recommendations can help the customer to select the servers to buy:
Buy a server from a reputable manufacturer to host ShoreTels software. We

advise against using servers from clone manufacturers for business-critical applications.
Be sure each server that runs ShoreTel server software has enough processing
capacity to support the planned telephony workload. ShoreTel servers perform call control (call setup and tear-down functions) and provide the services of voicemail, automated attendant, workgroup management, configuration databases, and more. The headquarters server also hosts the system configuration tool, Web pages for the user-interface and conferencing; and maintains call records and the history database.
Do not use a ShoreTel server as a domain controller.
10.2 Requirements for ShoreTel Enterprise Systems

This section provides information necessary to provision servers on which to install ShoreTel Enterprise software. The ShoreTel Enterprise Edition system is scalable. In the spirit of economy and efficiency, ShoreTel Enterprise customers provide their own server hardware allowing them to build the optimum phone system for their environment. To assist
ShoreTel 13.1
179
Chapter 10: Server Requirements
in creating the optimum system, ShoreTel has defined a tier system based on the number of users the system is to support and set minimum server requirements for each tier. The tiers ShoreTel defines are:
Branch office bundle (functions only as a DVS server) or an SBE server the Small servers that support up to 500 users. Medium servers that support up to 2,500 users. Large servers that support up to 10,000 users. Very large servers that support up to 20,000 users.
customer has upgraded to Enterprise Editionboth support up to 100 users.
NOTE If a planned upgrade to the current release means that the current server cannot adequately support the new release of ShoreTel software, upgrade the server to a model with greater capacity before doing the server software upgrade. NOTE SBE systems upgraded to Enterprise support the same capacities as the small Enterprise system.
10.2.1 Capacity and Hardware Requirements for Headquarters Servers

Table 10-1 shows information about system capacity for each tier of the headquarters (HQ) servers. The table shows the number of users, calls, and reports that the server can support for each tier. Table 10-2 shows our recommendations for each tier of headquarters server. Use these tables to determine the needs for headquarters servers in the ShoreTel deployment. You can mix servers of different capacities, but choose the right servers for the telephony environment. Table 10-1 Headquarter Server Capacity for Enterprise System Maximum number of users Maximum assigned System BHCC1 to HQ Server 100 500 Maximum BHCC per server2Reports run outside business hours Not Recommended3 Maximum BHCC per server2 Reports run during
business hours
Size
Maximum number of users per System
If an 500 upgrade from SBE Small 500
Not Recommended3
500 1,000 1,000 1,000 5004 or
5,000 25,000 50,000 100,000
1,000 5,000 10,000 10,000
Not Recommended3 1,000 5,000 10,000
Medium 2,500 Large Very Large 10,000 20,000
180
including internal and external calls, calls terminated to desk phones, softphones, trunks or server applications such as voicemail. 2 BHCC per server is based on the number of calls actually handled by the server during the busy hour including workgroup calls in menus and queues, auto-attendant calls and calls to the voicemail service. 3 By default, the ShoreTel report generation tools that run on the server have a lower priority than other, more critical services. Low-demand report generation should have little or no affect on a server with adequate performance specifications. If you are a heavy report user or experience any degradation of voicemail or other server prompts on an underpowered server, you must move up to the next tier level of servers.
1 BHCC (Busy Hour Call Completion) per system is the total number of system calls during the busy hour
NOTE Report generation has an impact on system performance. ShoreTel recommends that
customers run reports outside of business hours. If a customer needs reports during business hours, the supported calls per server for the medium and large server tiers is reduced as noted in the table.
For very large system deployments (10K to 20K), the number of ShoreTel Communicator for Windows users is 500. The number of ShoreTel Communicator for Web and mobile users in 1000.
Table 10-2 displays the minimum hardware requirement for ShoreTel Headquarters servers. Table 10-2 Size Small Medium Large Very Large Processor Headquarter Server Hardware Recommendations for Enterprise System RAM Network 100 Base-T 100 Base-T or Gigabit Ethernet Gigabit Ethernet
Intel Core 2 Duo E8400, Single Dual Core 3.00 GHz or 4 GB Intel Core i3-540 Processor (4M Cache, 3.06 GHz) Intel Xeon 5520 Single Quad Core 2.27 GHz Intel Xeon 5520 Dual Quad Core 2.27 GHz Intel Xeon 5680 Dual Six Core 3.33 GHz 8 GB 8 GB
12GB Gigabit Ethernet
Table 10-3 displays maximum usage ShoreTel DVS supports by usage type per server type.
10.2.2 Capacity and Hardware Requirements for Distributed Voice Servers

Table 10-3 provides information about system capacity for each of the tiers for ShoreTel Distributed Voice Servers (DVSs). The table provides information about the number of users and calls that a DVS in each tier can support. Table 10-4 shows the minimum equipment capacities for each tier for DVSs. Use these tables to calculate the requirements for the DVSs in the ShoreTel deployment. You can mix servers of different capacities. Choose the right servers that for the entire telephony environment. Maximum Users per DVS Server Distributed Voice Server (DVS) Capacity
Size
Table 10-3
ShoreTel 13.1
181
Branch Office Bundle Small Medium Large Very Large
100
500 1,000 1,000 5001or 1,000 Distributed Voice Server (DVS) Capacity (Continued)
Table 10-3
1
For very large system deployments (10K to 20K), the number of ShoreTel Communicator for Windows users is 500. The number of ShoreTel Communicator for Web and mobile users in 1000.
Table 10-4 Size Branch Office Bundle Small Medium Large Very Large
DVS Hardware Minimums RAM 2 GB Networks 100 Base-T
Processor Intel Pentium G680, DualCore 2.7 Ghz.
Intel Core 2 Duo E8400, Single DualCore 3.00 GHz Intel Xeon 5520 Single QuadCore 2.27 GHz Intel Xeon 5520 Dual QuadCore 2.27 GHz Intel Xeon 5520 Dual QuadCore 2.27 GHz
4 GB 8 GB 8 GB 8 GB
100 Base-T 100 Base-T or Gigabit Ethernet Gigabit Ethernet Gigabit Ethernet
10.2.3 Operating System Requirements for All Servers

This section lists the operating systems that ShoreTel 13.1 supports on the headquarters server and distributed voice servers. If you are upgrading a system to ShoreTel 13.1, refer to ShoreTel 13.1 Release Notes for special instructions that might apply. ShoreTel 13.1 supports the following operating systems in enterprise environments:
Windows Server 2008 32-bit, SP2 (Standard, Enterprise) Windows Server 2008 R2, SP1, 64-bit, (Standard, Enterprise)
NOTE ShoreTel servers (headquarters and DVS) on the same ShoreTel network can have different operating systems.
10.3 ShoreTel SBE System

SBE does not support DVS, SMDI, AMIS, QSIG, or on-net dialing. SBE reports should be run outside normal business hours. SBE is available on a ShoreTel server or a Customer server.
NOTE Server supplied by customer must meet SBE server requirements.
182
SBE can be upgraded to Enterprise Edition (EE).
10.3.1 Summary of SBE Requirements

ShoreTel can ship its Small Business Edition (SBE) with or without a server. If ShoreTel ships an SBE with a server, the server has the embedded Microsoft Windows Server OS for Telecommunications Systems. Furthermore, ShoreTel configures, tests, and prepares the server for ShoreTel Director Small Business Edition software. Microsoft Windows Server OS for Telecommunications Systems is an embedded operating system for standalone telecommunication products. Because this OS is an embedded operating system, it cannot support a keyboard, mouse, or monitor, so the customer must use a remote desktop application or an embedded Web tool to manage the system. This consequence of using Microsoft Windows Server OS for Telecommunications Systems applies to any SBE regardless of who sells the server to the customer. NOTE ShoreTels SBE server usually is appropriate up to 50 users. However, some customers might have plans to grow fast, for example, to more than 50 users by buying an SBE upgrade to Enterprise license. Also, some customers might plan for more expensive uses of the ShoreTel SBE, such as paging to multiple phones, using more than 10 workgroups simultaneously, or running Web Reports. These customers should consider buying their own server with at least 4 GB of RAM.
10.3.1.1 ShoreTel SBE Option with the ShoreTel Server

The server that ShoreTel currently uses for its SBE meets or exceeds the following specifications:
Processor: Intel Celeron E3400, DualCore 2.6 Ghz, 1MB Cache, and 800FSB Memory: 2.0GB, Non-ECC, 800 MHz DDR2 Keyboard: No Keyboard Monitor: No Monitor Option Hard Drive: 80GB, SATA Floppy Disk Drive: No Floppy Drive Operating System: Microsoft Windows Server 2003 for Telecommunications
Systems
Mouse: No Mouse Option NIC: On board Network Adapter Optical Drive: 16X DVD-ROM SATA 10.3.1.2 ShoreTel SBE Requirements without the ShoreTel Server
For customers who buy their own server, the server must meet or exceed the following specifications:
Celeron Dual Core 2.5 GHz or higher

ShoreTel 13.1 183
2 GB or more of RAM 80 GB or more on the hard disk 10/100 Ethernet NIC or higher 1 or more USB ports Only Microsoft Windows Server 2008 Standard or Enterprise edition is
supported
10.3.1.3 Using ShoreTel SBE Server in the Enterprise Setup

If an SBE customer gains more than 50 phone users, an upgrade from a ShoreTel SBE to the ShoreTel Enterprise edition is mandatory. The customer can use the SBE server in the Enterprise system as either a headquarters server or a DVS server. Option1: Using the SBE server as a Headquarters server. With this configuration, the number of users in the system cannot exceed 100. Other restrictions include:
Simultaneous media paths have a limit of 10 (media paths provide access for
voice mail and workgroups)
Busy hour completion has a limit 500. The SBE does not support Web Reports.
Option 2: Using the SBE server as a Distributed Voice Server (DVS) With this configuration, the number of users in the system cannot exceed 500, and the maximum number of users on the DVS cannot exceed 100. Other characteristics include:
Simultaneous media paths have a limit of 10 (media paths provide access for
voice mail and workgroups)
Busy hour completion has a limit 500. SBE supports Web Reports because these reports run on the headquarters
server.
10.3.2 Capacity for Small Business Edition

Table 10-5 describes the capacities for all Small Business Edition installations. Table 10-5 Maximum number of users per System License 50 Server Capacity for Small Business Edition Maximum BHCC per server2 Reports run outside business hours 500 N/A Maximum BHCC per server2 Reports run during business hours Not Recommended Not Recommended
Maximum number of users Maximum assigned per System BHCC1 Server 50 500 500
100 (HQ and DVS) 100
184
including internal and external calls, calls terminated to desk phones, softphones, trunks or server applications such as voicemail. 2 BHCC per server is based on the number of calls actually handled by the server during the busy hour including workgroup calls in menus and queues, auto-attendant calls and calls to the voicemail service. 3 By default, the ShoreTel report generation tools run at a lower priority than other, more critical services. A light demand of report generation should have little or no affect on a server with adequate minimum performance specifications. However, customers that rely very much on reports and experience a degradation of voicemail or other services during report generation might need a more powerful server.
1 BHCC (Busy Hour Call Completion) per system is the total number of system calls during the busy hour
NOTE The generation of reports affects the servers performance. ShoreTel recommends that you run reports outside of business hours. If reports are needed during business hours, then the supported calls per server for the medium and large server tiers is reduced as noted in the table.
10.3.3 SBE Operating System Requirements

For SBE, ShoreTel supports the operating systems listed in Section 10.3.3.1 and Section 10.3.3.2.
10.3.3.1 Servers Shipped by ShoreTel Windows Server 2003, Embedded Telecom Edition Windows Server 2008 R2, 64-bit, Embedded Telecom Edition 10.3.3.2 Servers Shipped by End-Customer Windows Server 2008, 32-bit, SP2 (Standard, Enterprise) Windows Server 2008 R2, 64-bit, SP1 (Standard, Enterprise)
10.4 Requirements for VMware Environments

This section provides information required to install the ShoreTel system software on servers running VMware. ShoreTel supports the core telephony platform on VMware. Service applications such as ShoreTel Call Center are not supported on VMware.
10.4.1 ShoreTel Capacity in VMware Environments

Table 10-6 lists the capacities for ShoreTel systems installed on servers running VMware. Table 10-6 Maximum Users per DVS Server 50 ShoreTel System Capacity in VMware Environment Maximum DVS per Server BHCC Reports run outside business hours 500 Maximum BHCC per Server Reports run during business hours Not Recommended
System Size SBE
ShoreTel 13.1
185
Table 10-6 Small Medium Large 500 2,500 10,000
ShoreTel System Capacity in VMware Environment 5,000 25,000 50,000 10001 5,000 10,000
10.4.2 Hardware Requirements for VMware Installation

Table 10-7 lists the requirements for installing ShoreTel on headquarters servers and distributed voice servers running VMware. Table 10-7 ShoreTel System Hardware Requirements in VMware Environment Hard Disk for HQ VMware Server 60 GB 60 GB 150 GB 260 GB Hard Disk Size for DVS VMware Server 40GB 40 GB 80 GB 130 GB
System Size SBE Small Medium Large
Cores per VM Processor 2 Quad-core Intel Xeon X550, 2.66 GHz 2 Intel Core 2 Duo E8400, Single DualCore 3.00 GHz 4 Intel Xeon 5520 Single QuadCore 2.27 GHz 8 Intel Xeon 5520 Dual QuadCore 2.27 GHz
RAM 4 GB 4 GB 8 GB 8 GB
10.4.3 Operating System Requirements for VMware

This section lists the operating systems supported by ShoreTel in a VMware environment. You can install these operating systems on both headquarters servers and distributed voice servers. ShoreTel 13.1 supports the following operating systems in enterprise environments:
Windows Server 2008 32-bit, SP2 (Standard, Enterprise) Windows Server 2008 R2, SP1, 64-bit, (Standard, Enterprise)
10.4.4 VMware Software Requirements

ShoreTel supports the use of VMware on both headquarters servers and distributed voice servers. You can install the following versions of VMware on the headquarters servers and distributed voice servers:
VMware ESX 4.1 for High Availability or VMotion configurations. VMware ESXi 5.0 for High Availability or VMotion configurations.
186
10.5 Double-Take Availability Software for Failover

For system failover in the current release, ShoreTel supports Double-Take Availability software version 5.3 only. This section describes how ShoreTel supports the upgrade of different releases of Double-Take Availability software for the current release.
If upgrading the system to ShoreTel 13.1, you can directly upgrade Double-Take
Availability version 5.1 or later to Double-Take Availability version 5.3.
If the system currently is using Double-Take Availability version 5.0 or earlier:

1. Uninstall the Double-Take Availability software after finishing the ShoreTel installation. 2. Install Double-Take Availability version 5.3.
10.6 Hard Disk Requirements

This section provides the hard disk requirements for ShoreTel servers and clients, as well as information about the hard disk utilization of critical ShoreTel functions. Consider the utilization of these resources before selecting a hard drive for the server. Table 10-8 shows the minimum amount of hard disk space required for ShoreTel applications. In addition, the dynamic files for voice mail, call detail records on the headquarters server only, and log files need hard disk space. NOTE The space required to install the client might be necessary if you are installing from off the network. In this situation, the process creates a copy of the installer. Table 10-8 Hard Disk Space Requirements for ShoreTel Servers and Clients Space Required 1600 MB 800 MB 600 MB
Type ShoreTel Headquarters Server ShoreTel Distributed Voice Server ShoreTel Client
ShoreTel 13.1
187
10.6.1 Voicemail Utilization

The space used for user voicemail messages on the server hard drive depends on the number of users, the number of messages per user, and the duration of each message. You need approximately 30 MB of hard disk space per hour for voice mail storage. Table 10-9 provides some conservative guidelines to estimate the amount of hard disk space used for voice mail, assuming each user has 15 one-minute voice messages. Table 10-9 # Users 100 500 1,000 2,000 3,000 4,000 5,000 Voice Mail Hard Disk Space Storage (hours) 25 125 250 500 750 1,000 1,250 Storage (GB) 0.8 GB 3.8 GB 7.5 GB 15.0 GB 22.5 GB 30.0 GB 37.5 GB
# Length Messages (minutes) 15 15 15 15 15 15 15 1 1 1 1 1 1 1
10.6.2 Call Detail Records

For each call on the system, call detail records are generated on the headquarters server. The hard disk space used on the server for call detail records varies depending on the call load on the system. The amount of hard disk space for a typical system is shown in Table 10-10. Table 10-10 Call Detail Records # Calls/ Day 100 1,000 10,000 50,000
a.
# Calls/Month (20 daysa) 2,000 20,000 200,000 100,0000
Storage/ Month 3 MB 30 MB 300 MB 1,500 MB
Storage/ 3 Months 9 MB 90 MB 900 MB 4,500 MB
20 working days per month (i.e. 4 weeks/month * 5 days/week = 20)
10.6.3 Log Files

Log files are generated on the system for the purposes of technical support. The hard disk space used on the server for log files varies greatly, depending on the overall system activity. The size of the log files on the server depends on the parameters in ShoreTel Director. Log files can remain 130 days (default 7 days) with a size in the range 0.5 GB5 GB (the default is 4 GB). Table 10-11 shows the hard disk space that log files need.
188
Table 10-11 File Size Minimum Default Maximum
Log File Hard Disk Space Storage (GB) 0.5 GB 4.0 GB 30.0 GB
10.7 Preparing Your Server for the ShoreTel Installation

This section describes how to prepare the server for installation in the ShoreTel telephony network.
10.7.1 Server IP Address

The ShoreTel server should have a static IP address. If the server suddenly gets a new IP address, system operation can be unpredictable.
10.7.2 Workgroup Mode

The server should be configured as a Workgroup rather than as part of the domain to avoid having group policies impact the DCOM/COM permissions. It is possible to place the server on the domain after installation of the server software.
10.7.3 DHCP on the ShoreTel Server

ShoreTel recommends that the ShoreTel server not be used as a Dynamic Host Configuration Protocol (DHCP) server. If you want to use the ShoreTel server to assign IP addresses to the ShoreTel voice switches, you should use the BOOTP server included in ShoreTel Director.
10.7.4 Windows Server 2008 Configuration

Before installing ShoreTel server software, you must prepare Windows Server 2008 to run ShoreTel services. You must enable IIS, COM+, SMTP, and FTP. Other required tasks include changing the SMTP and FTP startup type to automatic. The following subsections describe the selections required at pivotal steps in the installation process:
Configure Application Server Roles (Section 10.7.4.1) Configure Application Server Role Services (Section 10.7.4.2) Configure Web Server (IIS) Role Services (Section 10.7.4.3) Install Microsoft Services (SMTP and FTP) (Section 10.7.4.4) Configure SMTP and FTP (Section 10.7.4.5)
ShoreTel 13.1
189
These steps must be completed before installing or upgrading IIS, COM+, SMTP, and FTP. NOTE Windows Server 2008 must be activated through Microsoft before installing the ShoreTel server software.
10.7.4.1 Configure Application Server Roles

The Application Server Roles required for ShoreTel services are Application Server and Web Server (IIS). Selecting IIS and COM+ ensures the installation of these services. Step 1 On the Windows desktop, click Start > Programs > Administrative Tools > Server Manager. The Server Manager is launched (Figure 10-1). Step 2 In the Server Manager, right-click Roles and select Add Roles from the pop-up menu. The Add Roles Wizard is opened. NOTE You can also open the Add Roles Wizard by clicking the Add Roles icon in the pane on the right Step 3 In the Add Roles Wizard, click Server Roles in the pane on the left. The Roles menu panel is opened, displaying the available options (Figure 10-2). Step 4 In the Roles menu, click/check Application Server and Web Server (IIS). Step 5 Click Next. Now, configure the Application Server Role Services (Section 10.7.4.2).
Figure 10-1
Server Manager: Add Roles
190
Figure 10-2 Add Roles Wizard: Select Server Roles
10.7.4.2 Configure Application Server Role Services

Step 1 In the Add Roles Wizard, click Application Server: Role Services in the pane on the left. The Select Role Services panel is opened (Figure 10-3). Step 2 Select the following Role Services: .NET Framework 3.5.1 Web Server (IIS) Support COM+ Network Access TCP Port Sharing Windows Process Activation Service Support:

HTTP Activation Message Queuing Activation TCP Activation Named Pipes Activation Incoming Remote Transactions Outgoing Remote Transactions WS-Atomic Transactions
Distributed Transactions:

Step 3 Click Next. Now, configure the Web Server (IIS) Role Services (Section 10.7.4.3).
ShoreTel 13.1 191
Figure 10-3 Add Roles Wizard: Select Application Server Role Services
10.7.4.3 Configure Web Server (IIS) Role Services

Step 1 In the Add Roles Wizard, click Web (IIS) Server: Role Services in the pane on the left. The Select Role Services panel is opened (Figure 10-4). Step 2 Select the following Role Services: NOTE You may have to scroll down the Web Role Server panel to see all the available options. Select all Common HTTP Features. Select all Application Development Features. Select the following Health and Diagnostics Features:

HTTP Logging Logging Tools Request Monitor Tracing
Select all Security options. Select all Performance options. Select all Management Tools options. Select all FTP Publishing Service options.
192
Step 3 Click Next. The Confirm Installation Selections window is opened. Step 4 Click Install. The Roles and Role Services are configured.
Figure 10-4 Add Rules Wizard: Select Web Server Role Services
10.7.4.4 Install Microsoft Services: SMTP and FTP

Step 1 In the Service Manager window, click Features in the pane on the left. The Features panel is displayed (Figure 10-5). Step 2 Click Add Features. The Add Features Wizard is opened. Step 3 Select Features in the menu in the pane on the left. The Features pane is displayed. Step 4 Click/check SMTP Server. Step 5 Click Next. The Confirm Installation Selections window is opened. Step 6 Click Install.
ShoreTel 13.1
193
Figure 10-5 Add Features Wizard: Select Features: SMTP
10.7.4.5 Configure SMTP and FTP

After SMTP and FTP are installed, the startup type for each one must be changed from manual to automatic. NOTE Verify that the FTProot folder in the Inetpubs directory has at least read access. Change SMTP Startup Type Step 1 Access the Services table by selecting Server Manager > Configuration > Services (Figure 10-6). Step 2 Right click SMTP, then select Properties on the menu. The SMTP Properties window is opened (Figure 10-7). Step 3 In the Startup Type drop-down menu, select Automatic, then click OK. The startup type for SMTP is changed to automatic. Change FTP Startup Type on 2008 32-Bit Server Step 1 Access the Services table by selecting Server Manager > Configuration > Services. Step 2 Right-click FTP Publishing Service, then select Properties.
194
The FTP Publishing Service properties panel is opened. Step 3 In the Startup Type drop-down menu, select Automatic, then click OK. The startup type for FTP on a 2008 32-bit server is changed to automatic. Change FTP Startup Type on 2008 R2 64-Bit Server Step 1 Access the Services table by selecting Server Manager > Configuration > Services. Step 2 Right-click Microsoft FTP service, then select Properties. The Microsoft FTP Service properties panel is opened. Step 3 In the Startup Type drop-down menu, select Automatic, then click OK. The startup type for FTP on a 2008 R2 64-bit server is changed to automatic.
Figure 10-6 Server Manager: Services: SMTP Properties
ShoreTel 13.1
195
Figure 10-7 SMTP Properties: Select Automatic
10.7.5 Additional Considerations

This section discusses additional recommendations and requirements for installing the ShoreTel server.
10.7.5.1 Maximum Transmission Unit (MTU) Size for Connections

The default Maximum Transmission Unit (MTU) setting for PPP (Point-to-Point Protocol) clients, VPN (Virtual Private Network) clients, PPP servers, or VPN servers running Routing and Remote Access on ShoreTel systems is 1400. To change the MTU value, you must edit the registry. For further information, contact ShoreTel TAC.
10.7.5.2 Adobe Acrobat Reader

Install Adobe Acrobat Reader on the server if you do not already have it, so that you can access the online documentation. You can install Adobe Acrobat Reader from the ShoreTel DVD Browser or download it from the Adobe web site.
10.7.5.3 Internet Information Server (IIS) Default Web Site

The web site for ShoreTel Director is <server_name>/ShoreTelDirector. You should not change the default IIS web site of the server to redirect to ShoreTel Director, since this will cause navigation problems within ShoreTel Director.
196
10.7.5.4 Access to the Distributed Server Maintenance Page

If you are using Microsoft Internet Explorer and the distributed server is configured with an IP address rather than a server name, you must enable session cookies on your client computer to access the Distributed Server Maintenance Page. To enable session cookies: Step 1 Launch Internet Explorer. Step 2 Click Tools > Internet Options. The Internet Options dialog box appears. Step 3 Click the Privacy tab then the Advanced button. The Advanced Privacy Settings dialog box appears. Step 4 Check the Override automatic cookies check box. Step 5 Select Always allow session cookies. Step 6 Click OK to save the change.
10.7.5.5 Microsoft Updates on the Shoreware Server

When releasing a new build, ShoreTel publishes build notes listing the Microsoft patches that are certified against the build. ShoreTel also highlights software changes required by the Microsoft patches. Note that no additional Microsoft updates should be applied to your Shoreware server between ShoreTel builds. If you install Microsoft updates between ShoreTel builds, they may have an adverse effect on your telephone system.
10.7.5.6 Virus Protection on the Main and Distributed Servers

ShoreTel allows the use of industry standard virus protection software on the main and distributed servers. ShoreTel Anti-Virus Folder Exclusions The following folders and sub folders MUST be excluded from Virus checker software or disk backup/restore software:
Communicator Client
32-Bit: Drive:\Program Files\Shoreline Communications Drive:\Documents and Settings\%User%\Application Data\Shoreware Client\ 64-Bit: Drive:\Program Files (x86)\Shoreline Communications Drive:\Users\%User%\AppData\Roaming\ShoreWare Client
Contact Center Agent Toolbar

32-bit:
ShoreTel 13.1 197
Drive:\Documents and Settings\%User%\Application Data\ShoreTel Contact Center Drive\Documents and Settings\%User%\Local Settings\Application Data\ShoreTel Contact Center 64-bit: Drive:\Users\%user%\AppData\Roaming\ShoreTel Contact Center Drive:\Users\%user%\AppData\Local\ShoreTel Contact Center
HQ/ DVS Server

32-Bit: Drive:\Program Files\Shoreline Communications Drive:\Shoreline Data\ 64-Bit: Drive:\Program Files (x86)\Shoreline Communications Drive:\Shoreline Data\
Contact Center
32-Bit: Drive:\Program Files\ShoreTel 64-Bit: Drive:\Program Files (x86)\ShoreTel WARNING If the folders listed above are not excluded before installation, your installation of ShoreTel 13.1 will fail and your system will rollback to the previous version of ShoreTel. This will also result in a corrupted database if you perform nightly backups.
10.8 ShoreTel Mobility Support

ShoreTel 13.1 supports ShoreTel Mobility 4.8, 5.0, and 6.0.
10.9 Third-Party Applications Support

ShoreTel 13.1 supports the following third-party applications:
Microsoft OCS 2007 R2 Microsoft Lync 2010 IBM SameTime
198
Chapter 11
ShoreTel Server Installation

This chapter describes installation procedures for main and distributed ShoreTel servers. The topics discussed in this chapter include:
Checking Server for Compatibility on page 199 "Installing the Headquarters Server Software" section on page 200 Installing the Distributed Server Software on page 209 Verifying the Installation on page 211 Installing Licenses on page 212 Upgrading the Server Operating System on page 213 Ensuring Proper Server Performance on page 221
11.1 Checking Server for Compatibility

A compatibility checker is available for identifying potential issues prior to installing or upgrading the ShoreTel Server software. The compatibility checker is included as part of the installer and as a separate utility. When running the compatibility checker on a system that does not currently have the ShoreTel Server software installed, the utility checks for the following:
Roles and features needed for HQ and DVM Supported OS and service packs VBScript issues that may occur during installation Amount of space needed for the installation
When running the compatibility checker prior to upgrading the ShoreTel Server software, the utility checks for the following:
Roles and features needed for HQ and DVM Supported OS and service packs Supported upgrade paths Amount of space needed for the installation State of MySQL services and ShoreTel services
ShoreTel 13.1
199
Chapter 11: ShoreTel Server Installation
11.1.1 Running the Compatibility Checker

The compatibility checker is included as part of the installer and as a separate utility. Step 1 Insert the ShoreTel DVD into the DVD drive. Step 2 Navigate to the DVD drive on your computer, open the Sever folder and then open the Compatibility Checker folder. Step 3 Double-click CompatibilityChecker.exe. The Compatibility Checker window appears. Step 4 Click Compatibility Checker. All components and any compatibility issues are listed. NOTE You must address all compatibility issues before beginning the software installation. NOTE The compatibility checker is also available as part of the installer and can be run from the installation wizard.
11.2 Installing the Headquarters Server Software

This section describes how to install the ShoreTel headquarters server software. Use this procedure for new installations and upgrades. Before beginning software installation or upgrade, do the following:
Make sure that the server meets the physical requirements for the Close all programs on the server.
implementation. For more information, see Server Requirements on page 179.
Verify that no anti-virus software or endpoint software is running during

installation
Connect the server to the Ethernet network.

The server must be connected to the network with the correct IP address before installing the software.
Install Shoreware Server software on an NTFS partition. (Optional) Run the compatibility checker.
The compatibility checker is available as part of the server installation and as a standalone utility. For information about using the compatibility checker, see "Checking Server for Compatibility" section on page 199.
200
11.2.1 Upgrading the Headquarters Server Software

You can directly upgrade to the current release of the ShoreTel software from one of the following versions:
ShoreTel 11 ShoreTel 11.1 ShoreTel 11.2 ShoreTel 12
ShoreTel 12.1 ShoreTel 12.2 ShoreTel 12.3 ShoreTel 13
If upgrading an earlier version of ShoreTel software to the current release, you might have to make intermediate upgrades to one of the versions in the above list before upgrading to ShoreTel 13.1.
11.2.1.1 Preparing to Upgrade the Headquarters Server Software

Before starting the upgrade, do the following:
Back up the server (see below). Make sure that Windows 2008 Server is installed.
Backing up a ShoreTel Server There are multiple ways to perform a backup. Two ways take the system down during the backup, while the third halts the system for 10-20 seconds (but can degrade voice quality over a long period of time). Option 1. Run the Stop all script and copy the Shoreline Data folder. Step 1 Stop and disable all ShoreTel services, then reboot after confirming services are stopped:
C:\Program Files\Shoreline Communications\ShoreWare Server\Scripts\hq_shoretel-stop-svcs.bat
Step 2 Copy the Shoreline Data folder to a safe location, and label the version and build in the folder in which it is located. Step 3 Run the start services script to get the phone system services running:
C:\Program Files\Shoreline Communications\ShoreWare Server\Scripts\hq_shoretel-start-svcs.bat
Option 2. Run the ShoreTel backup scripts, which can be automated via Task Scheduler. Step 1 Navigate to the following:
C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\Scripts\Sample_Backup_Restore
Step 2 Edit the following file: sw_backup_restore.ini. If you are running a 64-bit Operating System, then change Program Files to Program Files (x86).
ShoreTel 13.1
201
Make sure Shoreware.Drive = is correct for where you have the Shoreline Communications folder. If you have V-switches, enter those in the VMB.ip.list = section (comma-separated). If you have a Conference Bridge, enter it in the UCB.ip.list = section (comma-separated). Make sure the backup is labeled how you want it, and on the correct drive and folder location. [Backup Options] Backup.Drive = C: Backup.Root.Directory = \Shoreware Backup\Backup Backup.ShoreWare.Directory = Shoreline Data\ Backup.Archive.Size = 2 folders NOTE If you chose a network drive for your backup, be sure the user profile that runs the task has permissions to write to that drive and directory. Step 3 Open Task Scheduler by clicking Start > Programs > Accessories > System Tools > Task Scheduler. (Figure 11-1 on page 203) Step 4 Right click and click Create new Task. (Figure 11-2 on page 203) Step 5 Name the task accordingly. Step 6 Change the general options to the following settings: Run whether user is logged on or not Run with highest privileges Configure for: Windows 7, Windows Server 2008 R2 Configure Change User or Group. to be a user you created for the backup user, or the server admin. You will have to enter your password for this user.
Step 7 Click the Triggers tab. (Figure 11-3 on page 204) Step 8 Fill out the schedule for when you want the process to run. Step 9 Click the Actions tab. (Figure 11-4 on page 205) Step 10 Browse for the script. The path will show up in the Program/ script area, but it is incorrect. Step 11 Move the path to the Start in (optional): box. (Figure 11-5 on page 206) Be sure the script is in the Program/ script area. Remember to remove the quotation marks. Step 12 Click the Conditions tab. (Figure 11-6 on page 206) Step 13 Fill out this form according to how you want your conditions set. Remember, every business environment is different.
202
Step 14 Click the Settings tab. (Figure 11-7 on page 207) Step 15 Fill out this form according to how you want your settings configured. Remember, every business environment is different. Step 16 Click OK to save the task. NOTE During non-business hours, be sure to right-click the script task and run it to ensure that it works.
Figure 11-1
Select User or Group
Figure 11-2
Create Task
ShoreTel 13.1
203
Figure 11-3
Create Task: Triggers
204
Figure 11-4
ShoreTel 13.1
205
Figure 11-5
Figure 11-6
Create Task: Conditions
206
Figure 11-7
Create Task: Settings
Option 3. If you are running Vmware, you can run a Snapshot during the middle of the night when the system is at idle. CAUTION Do not take Snapshots during business hours (according to VMware documentation) because, over time, taking Snapshots can degrade the voicemail quality of your phone system. Taking a Snapshot when the system is at idle and rebooting every 1-3 months should be a safe alternative.
11.2.1.2 Upgrading the Headquarters Server Software

To upgrade the server software, follow the instructions in Section 11.2.2. Setup will automatically determine that an upgrade is in process, and you will be presented with a subset of the installation wizard screens. (There is no need to change the destination folders of the ShoreTel files.) Setup looks for the ShoreTel database. If an older version of the database is found, Setup makes a backup copy and converts the database to the latest version. Setup will not overwrite an existing database. NOTE If during the installation process the installer discovers unsupported characters in user names, the installation will halt. A pop-up window will open showing the user names that contain unsupported characters. You must remove the unsupported characters before the installation can proceed. You can remove the unsupported characters from user names using the Individual Users page in ShoreTel Director. Supported username characters include the alphanumerics (a-z, 0-9), dash (-), underscore (_), dot (.), and @. Extra spaces are not supported and can cause the install to fail. All voice applications (voice mail, automated attendant, workgroups, and so on) are affected until the upgrade is complete. The installation will stop all ShoreTel services.
ShoreTel 13.1
207
11.2.2 Installing the Headquarters Server Software

The default parameters presented by the ShoreTel installer are recommended. However, if ShoreTel software is to be located in a different location, select the correct installation path during the install process. Step 1 Insert the ShoreTel DVD into the DVD drive. The installer launches automatically. NOTE If the installer does not launch automatically, navigate to the DVD drive on your computer, open the Server and Setup folders, and then double-click setup.exe. Step 2 Click Install ShoreTel Server. The ShoreTel installation software performs an initial check of your system. You are prompted to install any required software that is not already installed. You must install the required software before continuing. The ShoreTel Server InstallShield Wizard appears. Step 3 To run the compatibility checker, do the following: Step a Click Compatibility Checker at the bottom-left of the page. The Compatibility Checker window appears. Step b Click Compatibility Checker. All components and any compatibility issues are listed. NOTE You must address all compatibility issues before continuing with the installation. Step c Close the Compatibility Checker window to return to the installation wizard. Step 4 Follow the instructions in the wizard to install the server software. NOTE The data files are unique to your system and include your system configuration, voice messages, and automated attendant prompts. These files will be stored in a ShoreTel data folder and should be included as part of your backup plan for the server Step 5 When the installation completes, you are prompted to restart your server. Click Finish to restart. After the server restarts, you may be prompted to configure a TAPI service provider. Enter the appropriate area code and access code and continue. Step 6 If upgrading, restart the ShoreTel Voice Switches to finish the upgrade. This process upgrades the firmware on the switches but also affects all calls in progress.
208
11.3 Installing the Distributed Server Software

The Distributed ShoreTel server must be a dedicated server with no other applications installed. This means you should not use this server for any of the following: Windows Domain controller, Terminal Server, Database Server (with MySQL), Web server, nor exchange server. This DVS server must be exclusively dedicated to supporting ShoreTel. A distributed ShoreTel server has the same software prerequisites as the main ShoreTel server. Before beginning software installation, do the following:
Make sure that the server meets the physical requirements for the Close all programs on the server. Verify that no anti-virus software is running.
implementation. For more information, see Server Requirements on page 179.
Verify that the System Performance Settings have been set to Turn on DEP for
essential Windows and program services only.
Microsoft Visual C ++ with SP1 Redistributable Package (x86). Install the remote server software on an NTFS partition. Connect the server to the Ethernet network.
The server must be connected to the network with the correct IP address before installing the software.
(Optional) Run the compatibility checker to check for any compatibility issues.
The compatibility checker is available as part of the server installation and as a standalone utility. For information about using the compatibility checker, see "Checking Server for Compatibility" section on page 199.
11.3.1 Upgrading the Distributed Server Software

To upgrade the server software, follow the instructions in the "Installing the Distributed Server Software" section on page 209. Setup will automatically determine that an upgrade is in process, and you will be presented with a subset of the installation wizard screens. (There is no need to change the destination folders of the ShoreTel files.)
11.3.2 Installing the Distributed Server Software

ShoreTel supports the use of a remote desktop to install the remote server software.
ShoreTel 13.1
209
11.3.2.1 Installing the Software from the ShoreTel DVD

Step 1 Insert the ShoreTel DVD into the DVD drive on the distributed server. The installer launches automatically and the ShoreTel Intelligent Phone Systems splash screen appears NOTE If the installer does not launch automatically, navigate to the DVD drive on the server, open the Server and Setup folders, and then double-click setup.exe. Step 2 Click Install ShoreTel Remote Server. The ShoreTel Server InstallShield Wizard appears. Step 3 To run the compatibility checker, do the following: Step a Click Compatibility Checker at the bottom-left of the page. The Compatibility Checker window appears. Step b Click Compatibility Checker. All components and any compatibility issues are listed. NOTE You must address all compatibility issues before continuing with the installation. Step c Close the Compatibility Checker window to return to the installation wizard. Step 4 Follow the instructions in the wizard to install the server software. NOTE The wizard prompts you to enter the IP address for the Headquarters server. Make sure that the IP address for the remote server does not conflict with the IP address for the Headquarters server. Step 5 When the installation completes, click Finish. A dialog box appears, prompting you to restart the server. Step 6 Click Yes. After the server restarts, all the necessary software restarts automatically. It typically takes about 30 to 60 seconds after the operating system is up and running for the Microsoft Internet Information Services (IIS) and ShoreTel voice services to be running.
11.3.2.2 Installing the Software from the Web

Step 1 Start the Web browser. Step 2 In the URL field enter support.shoretel.com. The ShoreTel Support page appears. Step 3 Under By Release, click ShoreTel 13.1. The Customers and Partners login page appears. Step 4 Enter your login information, and then click Sign In. The ShoreTel 13.1 page appears.
210
Step 5 Under Downloads, click ShoreTel 13.1 Remote Server to download the remote server software. Step 6 Navigate to the file on your computer and double-click to launch the installer. The ShoreTel Intelligent Phone Systems splash screen appears. Step 7 Click Install ShoreTel Remote Server. The ShoreTel Server InstallShield Wizard appears. Step 8 To run the compatibility checker, do the following: Step a Click Compatibility Checker at the bottom-left of the page. The Compatibility Checker window appears. Step b Click Compatibility Checker. All components and any compatibility issues are listed. NOTE You must address all compatibility issues before continuing with the installation. Step c Close the Compatibility Checker window to return to the installation wizard. Step 9 Follow the instructions in the wizard to install the server software. NOTE The wizard prompts you to enter the IP address for the Headquarters server. Make sure that the IP address for the remote server does not conflict with the IP address for the Headquarters server. Step 10 When the installation completes, click Finish. A dialog box appears, prompting you to restart the server. Step 11 Click Yes. After the server restarts, all the necessary software restarts automatically. It typically takes about 30 to 60 seconds after the operating system is up and running for the Microsoft Internet Information Services (IIS) and ShoreTel voice services to be running.
11.4 Verifying the Installation

It typically take about 30 to 60 seconds after the operating system is up and running for the Microsoft Internet Information Services (IIS) and ShoreTel voice services to be running. You can do the following to verify that these applications are running. Step 1 Click the ShoreTel Director desktop icon to launch ShoreTel Director. If IIS is not running, an error message appears. If IIS is running, the ShoreTel Director log in page appears. Step 2 To log in to ShoreTel Director, do the following:
ShoreTel 13.1
211
NOTE For instructions about logging in to and registering ShoreTel Director, refer to the ShoreTel 13.1 System Administration Guide. Step a In the User ID field, enter the user name that you want to use. The default user ID is admin. Step b In the Password field, enter the password for the user. The default password is changeme. Step c Click Login. The Welcome page appears. Step d Click Later in regards to the registration. The navigation menu and Quick Look panel appear. Step e Ensure that the Services column in the Server/Appliance section displays Running for the status of the headquarters server.
11.5 Installing Licenses

Obtain Conference License Install License
11.5.1 Obtaining Conference License

To obtain a conference license: Step 1 Contact the ShoreTel partner or reseller and purchase the number and type of needed licenses. The partner or reseller will give you a purchase order number. Step 2 Launch ShoreTel Director and then log in. Step 3 Navigate to Administrator > System Parameters >Licenses > Keys. The License Keys page is opened. Step 4 Click the Register and Request System Key button at the top of the page. The Contact Information page is opened. Step 5 Enter the information requested in the Register and request system key section. Be sure to include the Sales order number from the purchase order and the customers primary contact information. Step 6 Click the Now button above the information fields. The system sends the request to ShoreTel for processing. After processing the request, ShoreTel sends the licenses.
212
11.5.2 Installing the License

To install the license: Step 1 View the license packet that you received from ShoreTel. Step 2 Launch ShoreTel Director and in the ShoreTel Director menu click Administration > System Parameters >Licenses > Keys. The License Key Info panel is opened. Step 3 Click the New button at the top of the page. The License Key Info panel is opened. Step 4 In the Key field, enter the license key that you received from ShoreTel. Step 5 In the Comment field, enter a description of the license. Step 6 Click Save. The license activates and the licensing information is posted in the License Key panel.
11.6 Upgrading the Server Operating System

NOTE On ShoreTel Server 12.x, you should run the Disk Reclaim tool. For information on using the tool, see the ShoreTel 13.1 System Administration Guide.
Preparing to Upgrade from Windows 2003 to Windows 2008 R2 (64-bit),

Section 11.6.1 on page 213
Upgrading the Uboot Version, Section 11.6.2 on page 214 Upgrading Servers from Windows 2003 (32-bit) to Windows 2008 (32-bit or
64-bit R2), Section 11.6.3 on page 215 Section 11.6.4 on page 218
Upgrading Servers from Windows 2008 (32-bit) to Windows 2008 R2 (64-bit), Upgrading the System to New Hardware (Same OS), Section 11.6.5 on page 219
11.6.1 Preparing to Upgrade from Windows 2003 to Windows 2008 R2 (64-bit)

Upgrading your Windows Server 32-bit operating system to a Windows Server 64bit operating system can cause your ShoreTel switches to not re-connect. To ensure a seamless migration without disruptions in your telephone services, you must make sure that your entire ShoreTel installation is compatible with the Windows Server 64-bit operating system. NOTE On ShoreTel Server 12.x, you should run the Disk Reclaim tool. For information on using the tool, see the ShoreTel 13.1 System Administration Guide.
ShoreTel 13.1
213
NOTE After the ShoreTel software is installed on the server, the server is considered a Telephony Appliance. As a Telephony Appliance, it does not adhere to the same policies, procedures, or security as a data server. NOTE For new installations of the 64-bit OS, the steps below are not necessary.
11.6.1.1 Upgrade Preparation

Before upgrading the server operating system, perform the following intermediate steps; otherwise, the ShoreTel switches will not reconnect and connectivity will be lost. Step 1 Make sure ShoreTel server software version 11 (Build Number 16.5.8506.0) or later is installed on the Headquarters server and all Distributed servers in the system. See Section 11.1 on page 199 and Section 11.3 on page 209 for more information. Step 2 Reboot all switches in the system. Step 3 Confirm that all half-width switches in the ShoreTel network are running Uboot version 1.1.3.27 or higher (see Section 11.6.2.1). Uboot version 1.1.3.27 or higher supports FTP service on both port 150 (for the 64-bit OS) and port 125 (for the 32-bit OS). Step 4 See Section 11.6.4 on page 218 for more details on upgrading from Windows 2003 to Windows 2008 R2 (64-bit).
11.6.2 Upgrading the Uboot Version

ShoreTel 11 (Build 16.5.8506.0) or higher automatically updates the Uboot code on the Voicemail Model Switches (voice switches that also provide voicemailthe ShoreTel Voice Switch 90V, for example) as part of the installation. If you have a ShoreTel VxWorks-based switch (not a voice mailbox switch), you must update the Uboot version to 1.1.3.27 (see Section 11.6.2.2).
11.6.2.1 View the Uboot Version Information for a Switch

Step 1 Launch Director and then click Quick Look. Step 2 Under Sites, click a site to view. Step 3 Under Switch/Appliance, click the switch to view. The Uboot version running on the switch is displayed as Boot ROM Version under Details.
214
11.6.2.2 Upgrade the Uboot Version

Step 1 Telnet or SSH to the half-width switch (non V-switch). Step 2 Go to Shell. Step 3 Enter the command uboot_update on the CLI. NOTE Do not turn off the unit during this process. Step 4 Reboot the switch after the update is complete.
11.6.3 Upgrading Servers from Windows 2003 (32-bit) to Windows 2008 (32-bit or 64-bit R2)
The following procedure is required when upgrading the operating system to Windows Server 2008 (32-bit) on a server that is running ShoreTel server software. NOTE On ShoreTel Server 12.x, you should run the Disk Reclaim tool. For information on using the tool, see the ShoreTel 13.1 System Administration Guide. NOTE After the ShoreTel software is installed on the server, the server is considered a Telephony Appliance. As a Telephony Appliance, it does not adhere to the same policies, procedures, or security as a data server. IMPORTANT Disable a user's Active Directory settings before proceeding with the upgrade process. If a user's Active Directory setting is not disabled, you will not be able to log into ShoreTel Director after upgrading. Step 1 Ensure that the server meets the hardware requirements as set forth in the Build Notes. Step 2 Disable a user's Active Directory setting (if enabled). This is an administrator's account into Director. Step 3 Perform the upgrade during a time window that allows you between 3-8 hours. Systems with only 1-5 switches usually take anywhere between 1-3 hours. The time frame depends on the size of your ShoreTel system. NOTE You will be taking services down in order to perform this backup and upgrade. Be sure to perform this during a maintenance window. Step 4 Take a backup of the following databases: CDR, Config, WebBridge, and Archive SQL (if your system has an archived database). NOTE The \Database folder is excluded from the backup because, in a few rare cases, Windows 2008 is unable to read database files after they are moved from Windows 2003. To avoid this scenario, it is best to backup and restore the databases. The default location for the database dumps is C:\. Be sure the file size is more than 0KB.
ShoreTel 13.1
215
To back up the CDR database, run the following batch file: C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\MySQL\MySQL Server\Examples\BackupCDR.bat To back up the Configuration database, run the following batch file: C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\MySQL\MySQL Server\Examples\BackupConfig.bat To back up the WebBridge database, run the following batch file: C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\MySQL\MySQL Server\Examples\BackupWebBridge.bat To back up the Archive database on ShoreTel 12.3 and before (if your system has an archived database), run the following command: C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\MySQL\MySQL Server 5.0\bin\mysql.exe --user=root -password=shorewaredba --port=4309 --database databasename > "c:\ArchiveCDRdump.sql" 2>>C:\\RestoreArchiveCDR.log To back up the Archive database on ShoreTel 13 and above (if your system has an archived database), run the following command: C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\MySQLConfig\MySQL Server\bin\mysql.exe --user=root -password=shorewaredba --port=4309 --database databasename > "c:\ArchiveCDRdump.sql" 2>>C:\\RestoreArchiveCDR.log Step 5 Stop and disable all ShoreTel services by running the following batch file: C:\Program Files\Shoreline Communications\ShoreWare Server\Scripts\hq_shoretel-stop-svcs.bat Step 6 Confirm that all ShoreTel services have stopped. Step 7 Reboot. Step 8 Copy the Shoreline Data folder (excluding the \Database folder) to a safe location and label the version and build in the folder in which it is located. It is recommended that you copy off the server to a safe location. Step 9 Restart the ShoreTel services by running the following command: C:\Program Files\Shoreline Communications\ShoreWare Server\Scripts\hq_shoretel-start-svcs.bat Step 10 Ensure that everything is up and running properly. Step 11 Reboot. Step 12 Pull off to a safe location the ShoreTel Director Installation files and any other files that you may want to keep. Step 13 After everything is off the server, reboot and boot from the Windows 2008 (32-bit) CD-ROM.
216
Step 14 Format the hard drive and install Windows 2008 (32-bit). Step 15 Log in via the local Admin Account. Step 16 Adjust the NIC so that it has the same static IP and name that it did before. Step 17 Add the server to the domain (be sure that it is placed in an empty Organizational Unit (OU) with Block Inheritance). No Group Policies should be applied. If Group Policies do need to be applied, be sure that they have already been tested against ShoreTel. WARNING Do not install any Anti-Virus software or Network security software. The ShoreTel Server is a Telephony Appliance. If you absolutely need AntiVirus software or Network security software due to security regulations, use KB16704 to configure this properly. Step 18 Turn off User Access Control (UAC). Step 19 Ensure that all of the Application Server Roles and Web Server Roles are installed. Step 20 Install the SMTP Role under Features. Step 21 Set DEP to Windows Programs and Services. Step 22 Install all of the Windows updates approved to the date specified in the Build Notes for the build on your system. Step 23 Disable Windows updates. Step 24 Disable Internet Explorer Enhanced Security. Step 25 Disable the pop-up blocker. Step 26 Copy your old Shoreline Data folder back to the drive where you want to install the software. Step 27 Install overtop the old Shoreline Data folder the exact same version of the ShoreTel Server software that was installed before. NOTE When installing the ShoreTel server on Windows Server 2008 (32-bit), you must launch Setup.exe using Run as Administrator. Step 28 Copy the following database dumps to the C:\ directory. Step 29 CDR, Config, WebBridge, and Archive SQL (if your system has an archived database). Step 30 Import the SQL database dumps. To import the CDR database dump, run the following command: C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\MySQL\MySQL Server\Examples\RestoreCDR.bat
ShoreTel 13.1
217
To import the Config database dump, run the following command: C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\MySQL\MySQL Server\Examples\RestoreConfig.bat To import the WebBridge database dump, run the following command: C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\MySQL\MySQL Server\Examples\RestoreWebBridge.bat To import the Archive database dump on ShoreTel 12.3 and before (if your system has an archived database), run the following command: C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\MySQL\MySQL Server 5.0\bin\mysql.exe --user=root -password=shorewaredba --port=4309 --database databasename > "c:\ArchiveCDRdump.sql" 2>>C:\\RestoreArchiveCDR.log To import the Archive database dump on ShoreTel 13 and above (if your system has an archived database), run the following command: C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\MySQLConfig\MySQL Server\bin\mysql.exe --user=root -password=shorewaredba --port=4309 --database databasename > "c:\ArchiveCDRdump.sql" 2>>C:\\RestoreArchiveCDR.log Step 31 Log into Director.
11.6.4 Upgrading Servers from Windows 2008 (32-bit) to Windows 2008 R2 (64-bit)
ShoreTel supports a particular 64-bit version of the Windows Server 2008 operating system. Specifically, support for Windows Server 2008 R2 64-bit only (no non-R2 versions) began with the first release of ShoreTel Release 11 (Build Number 16.5.8506.0) and continues in subsequent builds. NOTE On ShoreTel Server 12.x, you should run the Disk Reclaim tool. For information on using the tool, see the ShoreTel 13.1 System Administration Guide. NOTE After the ShoreTel software is installed on the server, the server is considered a Telephony Appliance. As a Telephony Appliance, it does not adhere to the same policies, procedures, or security as a data server. NOTE Release 11 Build 16.5.8506.0 and higher supports heterogeneous environments. For example, ShoreTel Release 11 software or higher supports a mix of the Headquarters Server and DVMs running either the 32-bit OS or the R2 64-bit OS until you get to version 13. In ShoreTel 13, Windows 2003 is no longer supported. IMPORTANT Verify that the version of the Uboot code on all switches is 1.1.3.27 or later prior to the installation of Windows Server 2008 R2 on the headquarters system. Use Quick Look to confirm the version of boot ROM on each switch. Only ShoreTel 12.3 and above has this new Uboot code. IMPORTANT If you are not on ShoreTel 12.3 or above and you are upgrading to Windows 2008 R2 (64-bit), follow the procedure in Section 11.6.3 on page 215.
218
11.6.5 Upgrading the System to New Hardware (Same OS)

NOTE This procedure will take down all services performed by the server. It is highly recommended that you perform this procedure during non-business hours. NOTE After the ShoreTel software is installed on the server, the server is considered a Telephony Appliance. As a Telephony Appliance, it does not adhere to the same policies, procedures, or security as a data server. Perform the Following Steps on the New Server Step 1 Ensure that the server meets the hardware requirements as set forth in the Build Notes. Step 2 Format the hard drive and install Windows 2008 (64-bit). Step 3 Log in via the local Admin Account. Step 4 Add the server to the domain (be sure that it is placed in an empty Organizational Unit (OU) with Block Inheritance). No Group Policies should be applied. If Group Policies need to be applied, be sure that they have already been tested against ShoreTel. WARNING Do not install any Anti-Virus software or Network security software. The ShoreTel Server is a Telephony Appliance. If you absolutely need AntiVirus software or Network security software due to security regulations, use KB16704 to configure this properly. Step 5 Turn off User Access Control (UAC). Step 6 Ensure that all of the Application Server Roles and Web Server Roles are installed. Step 7 Install the SMTP Role under Features. Step 8 Set DEP to Windows Programs and Services. Step 9 Install all of the Windows updates approved to the date specified in the Build Notes for the build on your system. Step 10 Disable Windows updates. Step 11 Disable Internet Explorer Enhanced Security. Step 12 Disable the pop-up blocker. Perform the Following Steps on the Old Server Step 13 Disable a user's Active Directory setting (if enabled). This is an administrator's account into Director. Step 14 Stop and disable all ShoreTel services by running the following batch file: C:\Program Files\Shoreline Communications\ShoreWare Server\Scripts\hq_shoretel-stop-svcs.bat
ShoreTel 13.1
219
Step 15 Confirm that all ShoreTel services have stopped: Go to the Run menu (WIN + R). Type services.msc. Review all of the ShoreTel services to ensure that they show Manual and that the services are stopped. Step 16 Reboot. Step 17 Copy the Shoreline Data folder (excluding the \Database folder) to a safe location and label the version and build in the folder in which it is located. It is highly recommended that you copy off the server to a safe location. NOTE ShoreTel recommends that you back up these files to a storage device separate from the server that you intend to upgrade. Step 18 Restart the ShoreTel services by running the following batch file: C:\Program Files\Shoreline Communications\ShoreWare Server\Scripts\hq_shoretel-start-svcs.bat Step 19 Confirm that all ShoreTel services are up and running: Go to the Run menu (WIN + R). Type services.msc. Review all of the ShoreTel services to ensure that they show Automatic and that the services are started. Step 20 Change the name of the server. Step 21 Change the IP of the server to something different. Step 22 Reboot. Perform the Following Steps on the New Server Step 23 Change the IP of the new server to the IP of the original server. Step 24 Change the Name of the new server to the Name of the original server. Step 25 Reboot. Step 26 Copy the Shoreline data folder that you copied from Step 17 to the new server. Step 27 Install overtop the old Shoreline Data folder the exact same version of the ShoreTel Server software that was installed before. NOTE When installing the ShoreTel server on Windows Server 2008 (64bit), you must launch Setup.exe using Run as Administrator. Step 28 Log into Director.
220
11.7 Ensuring Proper Server Performance

The following are some guidelines for ensuring the best performance from your ShoreTel server. This list is not exhaustive. Refer to Microsoft's system recommendations for more server maintenance information (www.microsoft.com).
Verify the server meets the hardware requirements, especially memory. Regularly defrag your hard drive and perform disk checks at least every other month. Optimize server performance for background services rather than for applications. The voice services running on the server are real-time services that could be negatively affected by having an application running in the foreground. Perform the steps below to optimize server performance: Step a On the ShoreTel server desktop click Start > Control Panel > System. Step b Select the Advanced tab or click Advanced system settings. Step c Depending on your system, do one of the following:
Click Performance Options. Under Performance, click Settings, and then select the Advanced tab.
The Performance Options dialog box is opened.
Step d Select the Background services radio button. Step e Make sure the paging file size (virtual memory) on the server is large enough. NOTE The paging file size should be 1 to 3 times larger than the physical memory on the server. If you have 512 MB of memory, the paging file size should be between 512 MB and 1536 MB. To increase the paging file size, click Change.
11.7.1 Setting the Server to Maximize for Network Performance

Step 1 On the ShoreTel server desktop click Start > Control Panel > Network and Internet Connections > Network Connections. Step 2 Depending on your system, do one of the following:
Right-click the Local Area Connection icon, and then choose Properties. Click Local Area Connection, and then click Properties.
The Local Area Connection Properties dialog box appears. Step 3 Select the File and Printer Sharing for Microsoft Networks check box, and then click OK.
ShoreTel 13.1
221
222
Chapter 12
Site Requirements and Preparation

This chapter provides information about preparing a site for the ShoreTel system Information includes physical space, environment, and cabling. The topics are:
Recommendations on page 223 Voice Switch Requirements on page 224 Racks and Cabling on page 230
12.1 Recommendations
The following recommendations can assist in the planning and preparation of a site for a ShoreTel system.
Hire a cabling contractor to install the equipment racks, patch panels, and
cabling.
Have RJ-48C cables available for each ShoreTel Voice Switch.
12.1.1 Switch Models

You can locate the model number of your switches on the rear panel as shown in Figure 12-1. This document distinguishes between switches based on the model number and the number of RUs the switch occupies.
Figure 12-1
ShoreTel 120 Model Number Label
See for a information on all ShoreTel Voice Switches. The information describes phone capabilities, connectors, and LED behavior.
ShoreTel 13.1
223
Chapter 12: Site Requirements and Preparation
12.2 Voice Switch Requirements

This section includes requirements for mounting the ShoreTel voice switches, along with other switch-related requirements and specifications.
12.2.1 Physical Requirements

The ShoreTel voice switches are designed to be mounted in a standard 19-inch rack. Table 12-1 shows the specifications for each voice switch. For more information refer to the Quick Install Guide, included with each ShoreTel voice switch. Table 12-1 ShoreTel Voice Switch Physical Specifications ShoreTel 120 ShoreTel 60 ShoreTel 40 ShoreTel T1 ShoreTel E1
Parameter Dimensions (H x W x D) Rack mount units Mounting position Weight
1.72 x 17.16 x 14.28 1.72 x 17.16 x 14.28 43.68 x 435.86 x 362.71 mm 43.68 x 435.86 x 362.71 mm 1 RU Front, Center 9 lbs 4.08 kg 1 RU Front, Center 8 lbs 3.62 kg 3 switches
Maximum stacked per 3 switches shelf
Table 12-2 shows the latest hardware line, designed to increase port density. Table 12-2 Parameter Dimensions (H x W x D) Rack mount units Mounting position Weight Maximum stacked per shelf Half-Width ShoreTel Voice Switch Physical Specifications Dimension 1.69 x 8.39 x 14.28 43 x 213 x 378 mm 1 RU Front, Center 5.3 lbs 2.4 kg 6 switches
12.2.2 Input Power

For backup purposes, ShoreTel recommends that all ShoreTel voice switches and the ShoreTel server be connected to an uninterruptable power supply (UPS). This ensures that telephone service will continue in the event of a power interruption. Table 12-3 shows the power requirements for the full-width ShoreTel voice switches.
224
Table 12-3
ShoreTel Voice Switch Power Input (Full-Width Switches) ShoreTel 120 ShoreTel 60 ShoreTel 40 100240 VAC 5060 Hz 2A max 1 90W typical ShoreTel T1 ShoreTel E1
Parameter Input voltage
100240 VAC 100240 VAC 5060 Hz 5060 Hz 1A max 1 50W typical 1A max 1 50W typical
Current consumption @110 VAC (maximum) Number of grounded 110 VAC outlets per switch Power consumption (typical)
Table 12-4 shows the power requirements for the half-width ShoreTel voice switches. Table 12-4 ShoreTel Voice Switch Power Input (Half-Width Switches) ShoreTel 220T1 ShoreTel 220T1A ShoreTel 220E1 ShoreTel T1k
Parameter Input voltage Current consumption @110 VAC (maximum)
ShoreTel 90 ShoreTel 90BRI ShoreTel 50 ShoreTel 30
100240 VAC 100240 VAC 5060 Hz 5060 Hz 1A max 1A max 1 17W
Number of grounded 110 VAC outlets per 1 switch Power consumption (typical) 40W
12.2.3 Power and Heat Dissipation

The voice switches dissipate power and heat. ShoreTel recommends that you use the information in Table 12-5 and Table 12-6 to help calculate the ventilation requirements of the room that contains the switches. Table 12-5 Parameter Power dissipation (typical) Heat dissipation ShoreTel Voice Switch Power and Heat Dissipation (FullWidth Switches) SG 120/24 SG 60/12 90 W typ 215 BTU/ hour 90 W typ 140 BTU/ hour SG 40/8 50 W typ 85 BTU/ hour SG T1 50 W typ 61 BTU/ hour SG E1 50 W typ 65 BTU/ hour
225
ShoreTel 13.1
Table 12-6
ShoreTel Voice Switch Power and Heat Dissipation (HalfWidth Switches) SG 90 SG 90BRI SG 50 SG 30 40 W typ
Parameter Power dissipation (typical) Heat dissipation
SG 220T1 SG 220T1A 40 W typ
ShoreTel 220E1 17 W typ 58 BTU/hour
137 BTU/hour 137 BTU/hour
12.2.4 Environmental Requirements

The ShoreTel voice switches require that the environmental specifications provided in Table 12-7 be met. Table 12-7 Parameter Operating temperature Storage temperature ShoreTel Environmental Specifications Specification 0 to 50 C (32 to 122 F) 30 C to 70 C (-34.4 to 158 F)
Operating humidity (non-condensing) 10% to 90%
12.2.5 Reliability and Availability

Each ShoreTel voice switch is an embedded product with a highly reliable fan. In addition, the power supply contained within the voice switch has a very high individual mean time before failure (MTBF), as shown in Table 12-8. Table 12-8 ShoreTel Voice Switch Dependability Predicted MTBF Demonstrated MTTR (hours) MTBF (hours) (hours) 190,606 172,659 132,300 190,606 175,803 91,000 171,493 159,416 172,659 162,931 n/a n/a 515,581 n/a n/a 519,359 n/a n/a n/a n/a 1 1 1 1 1 1 1 1 1 1
Voice Switch ShoreTel 24A ShoreTel 30 ShoreTel 30BRI ShoreTel 40/8 ShoreTel 50 ShoreTel 50V ShoreTel 60/12 ShoreTel 90 ShoreTel 90V ShoreTel 90BRI ShoreTel 90BRIV
226
Availability 99.9994% 99.9994% 99.9997% 99.9994% 99.9994% 99.9993% 99.9994% 99.9994% 99.9994% 99.9994%
Table 12-8
ShoreTel Voice Switch Dependability (Continued) Predicted MTBF Demonstrated MTTR (hours) MTBF (hours) (hours) 84,500 158,229 189,373 154,229 189,373 189,373 163,516 189,373 518,134 312,709 n/a 312,709 n/a n/a n/a n/a 1 1 1 1 1 1 1 1
Voice Switch ShoreTel 120/24 ShoreTel T1 ShoreTel T1K ShoreTel E1 ShoreTel E1K ShoreTel 220T1 ShoreTel 220T1A ShoreTel 220E1
Availability 99.9997% 99.9997% 99.9994% 99.9997% 99.9994% 99.9994% 99.9994% 99.9994%
MTBF = Mean time before failure MTTR - Mean time to repair Availability = %uptime/time = MTBF/(MTBF+MTTR) Since the ShoreTel system is plug-and-play, a switch can be replaced in minutes. Distributed call control software means there is no system-wide single point of failure. If a single ShoreTel voice switch fails, all the other voice switches continue to operate. Table 12-9 shows the reliability information for the ShorePhone phones. Hourly numbers shown are based on demonstrated reliability (as opposed to calculated). Table 12-9 Phone IP110 IP115 IP212k IP230 IP265 IP560 IP560g IP565g IP 655 BB24 ShorePhone IP Phone Dependability MTBF hours (calculated) 64,800 N/A 58,200 58,200 N/A 56,300 56,400 N/A TBD 72,600 MTBF hours (demonstrated) 490,000 TBD 350,000 350,000 TBD 360,000 TBD TBD TBD TBD
12.2.6 Memory and Processing

Each ShoreTel voice switch has the same memory and processing (see Table 12-10).
ShoreTel 13.1
227
Table 12-10 ShoreTel Voice Switch Memory and Processing Type Flash Memory Random Access Memory Main Processor Digital Signal Processor Details 16 MB 128 MB PowerPC 8245 Texas Instruments 5409A
12.2.7 Connectors
Table 12-11 summarizes all of the connectors on the ShoreTel voice switches. Diagrams showing where these connectors are located are provided later in this chapter. Table 12-11 ShoreTel Voice Switch Connectors SG 120/24 SG 60/12 SG 40/8 110 VAC 2 RJ-45 RJ-21X male 02,000 feeta 3.5 mini-mono SGT1/ 220T1 SG E1/ 220E1 110 VAC 2 RJ-45 RJ-48C RJ-48C 3.5 minimonob 3.5 minimonob
Port/Connector Power Ethernet Analog telephone/trunk Digital trunk T1 trunk monitor Audio input (Music on Hold)
SG 220T1A 110 VAC 2 RJ-45 RJ-21X male 02,000 feeta RJ-48C RJ-48C 3.5 minimono 3.5 minimono
Audio output (Paging, Night 3.5 mini-mono Bell) Maintenance DB-9 female
DB-9 female DB-9 female
a. 2000 ft. length uses 26AWG wire b Audio input/output on 220T1 and 220E1, but not T1/E1
12.2.7.1 Power Cabling

Each ShoreTel voice switch comes equipped with a standard 110 VAC modular power cord. A localized modular power cord can be ordered from ShoreTel. ShoreTel recommends that every ShoreTel voice switch, as well as the ShoreTel server, be connected to an uninterruptable power supply (UPS).
12.2.7.2 Ethernet Cabling

Each ShoreTel voice switch has two RJ-45 connectors that provide an auto-sensing 10/100M Ethernet interface. These are connected to the local area network using standard Category 5 cabling.
228
ShoreTel voice switches come with two network interfaces, LAN1 and LAN2, allowing for a network fault tolerant deployment. You can connect to either or both connectors; there is no primary/secondary relationship. When both are connected, only one will be active at any time. If the currently active interface loses the link, the alternate interface becomes active. Both interfaces will use the same MAC Ethernet address, and IP address. There are two levels of fault tolerance. To protect against Ethernet switch failure, connect LAN1 and LAN 2 to separate Ethernet switches. To protect against port or cable failure, connect LAN1 and LAN2 to separate ports on the same Ethernet switch. 10 Base-T and 100 Base-T can typically support up to 100 meters.
12.2.7.3 IP Phone Cabling

Each ShorePhone IP phone has an RJ-45 connector that provides an auto-sensing 10/100M Ethernet interface. This is connected to the local area network using standard Category 5 cabling. 10 Base-T and 100 Base-T can typically support up to 100 meters.
12.2.7.4 Analog Telephone and Trunk Cabling

ShoreTel voice switches that support analog protocols provide an RJ-21X male connector for mass termination of the telephones and trunks. This should be connected using a standard 25-pair cable. ShoreTel recommends using the RJ-21X and connecting to a patch panel to provide simple moves, adds, and changes. Telephones can be supported from 0 to 2,000 feet from the voice switch over standard cabling. Use larger gauge wires for longer distances. It is recommended that an analog telephone be provisioned in the equipment room for troubleshooting purposes. Pinout information for ShoreTel Voice Switches is provided in the quick install guide for each voice switch.
12.2.7.5 Digital Trunk and Trunk Monitor Cabling

ShoreTel voice switches that support digital trunks have an RJ-48C connector as the telco interface to the T1/E1 trunk from the telephone service provider. These voice switches provide an internal Channel Service Unit (CSU). ShoreTel voice switches that support T1 and E1 trunks have an additional RJ-48C connector that is wired to the telco interface for the purpose of troubleshooting the T1 or E1 interface with specialized test equipment. This connector is normally not used.
12.2.7.6 Audio Input (Music on Hold) Cabling

Various ShoreTel voice switches have a 3.5 mm mini-stereo input connector that provide music or some other recording to callers when they are on hold. The input port supports low-level line audio from a preamplifier or mini-CD player, at 47 k nominal impedance. The audio input cable can be up to 10 feet long. Refer to the ShoreTel quick install guide for your voice switch to determine whether your switch provides the 3.5 mm mini-stereo input connector. The audio input port on the ShoreTel voice switches is a mono connection. If you connect a stereo input, the stereo signal is converted to a mono signal.
ShoreTel 13.1 229
To minimize bandwidth, music on hold is not streamed across the wide area network, so you will need one music source per site. The music and music source are not included with the ShoreTel system. WARNINGIn accordance with United States copyright laws, a license may be required from the American Society of Composers, Authors, and Publishers, or a similar organization, if radio or TV broadcasts are played for music on hold. As an alternative, an ASCAP-approved CD or tape can be used. ShoreTel, Inc. disclaims any liability out of failure to obtain such a license.
12.2.7.7 Audio Output (Paging and Night Bell) Cabling

Various ShoreTel voice switches have a 3.5 mm mini-stereo audio output connector for overhead paging and night bell on a per site basis. The audio output port provides low-level line audio with a sufficient input level for a typical amplifier. The paging port output is about one volt peak to peak, similar to the line output of a CD player, and can drive inputs that are 600 ohms or higher. Refer to the ShoreTel quick install guide for your voice switch to determine whether your switch provides the 3.5 mm mini-stereo input connector. The audio output is mono signal. If you use a stereo jack, the signal is available on one channel, but the other channel will be silent. This is a single-zone paging system. If more zones are required, see the application note on ShoreTels online knowledge base.
12.2.7.8 Maintenance Cabling

ShoreTel voice switches support a maintenance port for connection terminal using a standard, straight-through DB-9 female connector. This maintenance port is typically used only when assigning networking parameters if DHCP or BOOTP is not being used.
12.3 Racks and Cabling

12.3.1 General Cabling Overview
The diagram in Figure 12-2 highlights the key components with respect to cabling for your voice network.
230
Figure 12-2 Cabling Overview Starting from the lower left in this diagram, the telephone cabling is organized as follows:
A telephone jack (RJ-11) is provided for each telephone. Telephone cabling (Category 3 or better) is terminated on the telephone jack
and runs back to the equipment room to a modular connector (RJ-21X) on a telephone patch panel. the telephone cabling. The patch panel has RJ-21X connections for the telephone cabling and RJ-11 connections on the front. switch patch panel (RJ-11).
The telephone patch panel provides a flexible cable management solution for Patch cords are connected from the telephone patch panel (RJ-11) to the voice
for the voice switches. The patch panel has RJ-21X connections running to the voice switches and RJ-11 connections on the front. Starting from the right in Figure 12-2, the trunk cabling is organized as follows:
The voice switch patch panel provides a flexible cable management solution
The digital (T1/E1) and analog trunks are terminated on a punch-down block. The digital service is further terminated at a service provider demark with an
RJ-48 connector. An RJ-48 cable from the T1/E1 demark connects to the ShoreTel T1 or ShoreTel E1. A telco cable is connected to the modular (RJ-21X) punch-down jack and runs to a modular connector (RJ-21X) on an analog trunk patch panel. Like the telephone cabling, patch cords are connected from the analog trunk patch panel (RJ-11) to the voice switch patch panel (RJ-11).
ShoreTel 13.1 231
The analog service is cross-connected to a modular (RJ-21X) punch-down block.
As an alternative, patch panels can be replaced with punch-down blocks. This may be more cost-effective but is less flexible.
12.3.2 Rack Overview

Figure 12-3 shows a typical rack installation.
Figure 12-3 Rack Installation A 19-inch data rack, shelf, and modular patch panels can be purchased from most major electrical suppliers.
232
Chapter 13
Installing ShoreTel Voice Switches

This chapter provides planning and installation information for the ShoreTel voice switches. Information on switch connectors and LEDs can be found in Site Requirements and Preparation on page 223. The topics discussed include:
Planning on page 233 Mounting the ShoreTel Voice Switches on page 233 Installing ShoreTel Voice Switches on page 234 ShoreTel Director Switch Configuration on page 235 Reference on page 235
13.1 Planning
In the ShoreTel system switches perform vital roles in connecting endpoints in a call whether the endpoints are located on the ShoreTel network, another private network, or the PSTN. Every IP phone on the ShoreTel network must register with a switch. The switch provides dial and ring tone to the phone when required, performs call setup and teardown task, sets up call legs, communicates with other switches and devices. ShoreTel switches also provide the physical and logical interface that allows the system to connect with external service providers and other phone networks. When you plan for switches, consider the following:
The number of IP phone that will connect to the switch. The type of interface you provision from the external service provider. Failover.
13.2 Mounting the ShoreTel Voice Switches

To stack the ShoreTel voice switch in a rack: Step 1 Remove the voice switch from its shipping container. Step 2 Place the switch on a flat platform, such as a shelf. Step 3 Up to three switches can be stacked on top of each other. To mount a full-width ShoreTel voice switch in a rack with brackets: Step 1 Remove the voice switch from its shipping container. Step 2 Attach the two included mounting brackets by using the screws we provide.
ShoreTel 13.1 233
Chapter 13: Installing ShoreTel Voice Switches
Step 3 Use standard screws to mount the switch in the rack. To mount a half-width ShoreTel voice switch in a rack with brackets follow the steps below. Refer to the Quick Install Guide for the ShoreTel Dual Tray (included with half-width switches) for details. Step 1 Remove the voice switch from its shipping container. Step 2 Mount a ShoreTel Dual Tray into the rack with the screws provided. Step 3 Install the half-width switch into the tray on either the left or right side of the tray. Two half-width switches can be placed in the same tray. Step 4 Use standard screws to mount the switch in the tray.
13.3 Installing ShoreTel Voice Switches

Before applying power to a new ShoreTel voice switch, configure the DHCP/BOOTP server. To install a ShoreTel Voice Switch: Step 1 Connect the switch to the appropriate LAN segment (such as a LAN switch) with the Category 5 RJ-45 interface cable. For guaranteed voice quality, all ShoreTel voice switches can be connected to an isolated LAN segment. Step 2 Plug an AC surge protector into a grounded AC power source (not provided). Electrical surges, typically lightning transients, are very destructive to equipment connected to AC power sources. Step 3 Plug the power cord into the power receptacle on the switchs back panel and then into an available socket on the AC surge protector. Most ShoreTel Voice Switch models do not have a power switch. They turn on when you connect the switch to a power source. The power LED flashes momentarily, and remains lit. If the LED is not lit, ensure that the power cord is plugged into the switch and the power source. If the LED continues flashing, there is an internal error. Unplug the switch to power it off, then power it back on. Refer to the ShoreTel System Administration Guide for a description of the flash patterns and their meaning. Once network communications are established, the network LEDs will indicate that the switch is connected to a 10 Mbps or 100 Mbps Ethernet environment, and that the switch is receiving and transmitting data. Step 4 If applicable, connect the music-on-hold source to the audio input port. Step 5 If applicable, connect your site's paging system to the audio output port. Step 6 Refer to the ShoreTel System Administration Guide to configure the ShoreTel voice switch according to your sites requirements. Step 7 Connect your trunk and telephone lines using the appropriate connector for your switch. Refer to the quick install guide for your ShoreTel switch for connector pinout information.
234
13.3.1 RJ-21X Cable Retainer Installation

A cable retainer for the RJ-21X port is included with some ShoreTel voice switches. The retainer consists of a metal bracket with a velcro strap. To install the retainer: Step 1 Using a number 1 Phillips screwdriver, remove the two black Phillips head screws on either side of the RJ-21X port. Step 2 Place the retainer in the recessed area around the RJ-21X port. Step 3 Reinstall the two screws. Step 4 Plug in the RJ-21X cable. Step 5 Pull the velcro strap tightly around the connector on the RJ-21X cable, and fasten it.
13.4 ShoreTel Director Switch Configuration

To complete the installation, you need to configure the ShoreTel voice switches with ShoreTel Director. For more information, see the chapter on configuring switches in the ShoreTel System Administration Guide.
13.5 Reference
13.5.1 Environmental Requirements
The ShoreTel voice switches require that the environmental specifications provided in Table 13-1 be met. Table 13-1 Parameter Operating temperature Storage temperature Storage humidity (non-condensing) ShoreTel Voice Switch Environmental Specifications Specification 0 C to 50 C 30 C to 70 C 20% to 95%
Operating humidity (non-condensing) 0% to 90%
13.5.2 Packaging Requirements

Table 13-2 lists the packaging requirements for the following ShoreTel voice switches:
Full-width switches (ST-120/24, ST-60/12, ST-40/8, ST-T1/E1) Half-width switches (ST-90, ST-50, ST-220T1/E1/T1A)
ShoreTel 13.1
235
Table 13-2 Parameter Vibration Power:
ShoreTel Voice Switch Packaging Specifications Specification 0.4 Grms, 1h per axis 5-500Hz @ 0.000323303 g2/Hz 1.5G RMS 5-500Hz @ 0.00454645 g2/Hz 275 C Brown 21+1/8 x 19 x 5+3/4 19+1/8 x 12+1/2 x 6+1/2 80 Gs non-operating 8-corner standard drop test
Spectral Density: Operation Power: Spectral Density: Packaged Transportation Material: Dimensions (full-width switches): Dimensions (half-width switches): Mechanical Shock: Packaged Bounce:
13.5.3 Regulatory Compliance

Table 13-3 Parameter Safety EMI ST-E1 Voice Switch Physical Specifications ShoreTel-24 UL 60950, 3rd Edition, CAN/CSA 22.2 No. 60950, EN60950 (2000) FCC Part 15, ICES-003, EN 55022, Class A/Class B Radio and Telecommunications Terminating Device Directive (R&TTE) 99/5/EC Low Voltage Directive 73 / 23 / EEC EMC Directive 89 / 336 / EEC With Amendment 93 / 68 / EEC GS Mark from TUV Rheinland (Notified Body) EN 55024: 1998 +A1:2001 +A2:2003 Table 13-4 Parameter Safety Telephony Registration EMI ST 120/24, ST 90, ST 60/12, ST 50, ST 40/8, ST 30Voice Switch Physical Specifications Physical Specification UL 60950, 3rd Edition, CAN/CSA 22.2 No. 60950, EN60950 (2000) FCC Part 68, Canada CS-03 FCC Part 15, ICES-003, EN 55022, Class A
236
Table 13-4 Parameter
ST 120/24, ST 90, ST 60/12, ST 50, ST 40/8, ST 30Voice Switch Physical Specifications (Continued) Physical Specification Radio and Telecommunications Terminating Device Directive (R&TTE) 99/5/EC Low Voltage Directive 73 / 23 / EEC EMC Directive 89 / 336 / EEC With Amendment 93 / 68 / EEC GS Mark from TUV Rheinland (Notified Body) EN 55024: 1998 +A1:2001 +A2:2003
13.5.4 Physical Specifications

Table 13-5 Parameter Safety Telephony Registration EMI ST T1, ST-220T1, ST 220T1A, ST T1k Voice Switch Physical Specifications Physical Specification UL 60950, 3rd Edition, CAN/CSA 22.2 No. 60950, EN60950 (2000) FCC Part 68, Canada CS-03 FCC Part 15, ICES-003, EN 55022, Class A Radio and Telecommunications Terminating Device Directive (R&TTE) 99/5/EC Low Voltage Directive 73 / 23 / EEC EMC Directive 89 / 336 / EEC With Amendment 93 / 68 / EEC
13.5.5 General Specifications

Table 13-6 Parameter Power Supply ST-120/24, ST-90, ST-60/12, ST-50, ST-40/8, ST-E1/T1, and ST-220T1/E1/T1A Voice Switch Specifications ShoreTel-24 100-240 VAC 50-60 Hz 2A max (full-width switches) 1A max (half-width switches) Mounting Options Integrated OA&M 19 inch rack mount
ShoreTel 13.1
237
238
Chapter 14
IP Phone Installation
With ShoreTel IP Phones, you can deploy the phones with the wiring that already exists in the building. ShoreTel pre-configures its IP phones to work with a ShoreTel system and the networks Dynamic Host Configuration Protocol (DHCP) server. After configuring the servers, you plug the phones into the network; the ShoreTel system automatically adds them to the network. If the network does not have a DHCP server or it is currently offline, you can set a static IP address and other startup parameters directly at the IP phone. See the ShoreTel System Administration Guide for more information. The topics discussed in this chapter include:
Recommendations on page 239 Preparing Your ShoreTel System for IP Phones on page 239 Associating a User Group with Unassigned IP Phones on page 246
The following recommendations will help you install your IP phones.
Make sure you have reviewed your network bandwidth and Quality of Service Make sure you have configured DHCP vendor option 156 with boot server
(QoS) strategies and configured your network for your IP phones as described in "Understanding the Requirements for Toll-Quality Voice" on page 42. information. The phones may not boot properly if incorrect configuration data is present in the telephone. This can occur if the telephones were previously used in an environment where DHCP and automatic provisioning was not used, or the telephone is from a vendor other than ShoreTel. See the ShoreTel System Administration Guide, for information about changing the telephone to the correct settings.
14.2 Preparing Your ShoreTel System for IP Phones

This section provides the information you need to prepare your ShoreTel system for IP phones.
ShoreTel 13.1
239
Chapter 14: IP Phone Installation
14.2.1 Configuring Voice Switches for IP Phone Support

To provide PSTN local dialing for IP phone users, every site where IP phones are in use must have a ShoreTel Voice Switch configured to support the number of IP phones at the site, plus local analog or T1 trunks. The ShoreTel voice switches send a heartbeat to the IP phones every 60 seconds. If the heartbeat is not acknowledged within approximately four seconds, the switch considers the IP phone to be offline or unavailable. The voice switches continue to broadcast the heartbeat every minute. Any currently-offline IP phone that returns an acknowledgement is considered online and available. To configure IP phone support on a ShoreTel voice switch, you must reserve ports for IP phone support on the ShoreTel Voice Switch edit page in the ShoreTel Director. See the chapter on configuring switches in the ShoreTel System Administration Guide for additional information.
14.2.2 Configuring Teleworker IP Phones

To configure an IP phone as a teleworker phone: Step 1 Define a range of IP addresses set aside for IP phone teleworkers as described in "Setting IP Address Ranges" on page 241. Step 2 Set a static IP address for the IP phone included in the range you defined in Step 1. For instructions on setting a static IP address for an IP phone, see "Manually Configuring ShorePhones" on page 259. Step 3 Connect the IP phone to your Ethernet connection to the Internet.
14.2.3 Assigning the Configuration Switches

You need to designate a switch for handling initial service requests from IP phones installed on your ShoreTel system. You have the option of assigning two switches to this function, to provide a backup in case of network problems. Every IP phone installation must have at least one configuration switch. If you do not assign a switch, the ShoreTel system automatically assigns the first two ShoreTel Voice Switches added to the system that are managed by the HQ server. IP phones must be able to contact at least one of the assigned configuration switches when first connected to the network. If the IP phone cannot reach a configuration switch, the telephone will not be added to the system. To assign configuration switches: Step 1 From the ShoreTel Director navigation pane, click IP Phones.
Click IP Phones Options. Figure 14-1 shows the IP Phones Options edit
page.
240
Figure 14-1
IP Phones Options Edit Page
This page has several configurable parameters:
IP Phone Configuration Switch 1 IP Phone Configuration Switch 2 User Group for Unassigned IP Phones IP Phone Announcement IP Phone Password Enable IP Phone Failover Delay After Collecting Digits
Step 2 Select an available switch from the pull-down lists for configuration switches 1 and 2. For information on the other IP phone options, see the ShoreTel System Administration Guide.
14.2.4 Setting IP Address Ranges

If your system consists of more than one site, you must define an IP address range for IP phones at each site in the system. Setting ranges for each site ensures that new phones added to the system will be associated with the correct voice switch at the telephones site. You can view the IP address range for each site from the IP Address Map list page, shown in Figure 14-2. The page lists the sites and associated IP address ranges.
ShoreTel 13.1
241
Figure 14-2 IP Address Map List and IP Address Range Edit Pages To add a site with IP phones, click New and enter the information on the Site IP Address Range edit page. To delete a site from the list, click the check box to the left of the site and click the Delete button. To edit the IP address range for a site: Step 1 On the IP Address Map List page, in the Site column, click the site for which you are setting a range. The Site IP Address Range edit page appears. NOTE If you are setting the IP address range for a site other than shown in the Site field, select it from the list. Step 2 Enter the lowest IP address in the Low IP Address field. Step 3 Enter the highest IP address in the High IP Address field. Step 4 If you are setting a range for teleworker IP phones, click the Teleworkers check box. Step 5 To set the new range, click Save. You can set ranges for other sites in the system by clicking Previous or Next. If a phone is added with an address that is not within a specified range for any site, or there are no IP address ranges defined for any site, the telephone will be automatically assigned to the headquarters site. This causes sevendigit numbers dialed from the IP phone to be dialed as numbers within the area code of the headquarters site. In addition, this causes all telephone calls to users who are not at the headquarters to use the configured inter-site voice encoding for that system.
14.3 Installing a ShoreTel IP Phone

This section provides information about installing ShoreTel IP phones.
242
14.3.1 Boot Sequence

The boot sequence to follow is: 1. DHCP on default VLAN. Reboot 2. DHCP on voice VLAN. Reboot. 3. Connect to HQ for firmware code. Reboot. NOTE The headquarters server uploads the latest phone firmware code to the phone. When the firmware code on the phone is an old version, the server uploads each successive firmware update until the firmware code on the phone is the current version. The phone reboots after each update. The update can take several minutes if the system makes many updates. 4. Connect to Media Gateway Control Protocol (MGCP).
14.3.2 802.1x Authentication

Most ShoreTel IP phones support 802.1x network authentication. ShoreTel IP phones that support 802.1x authentication are shipped with the feature enabled and are required to present a user id and a password the first time the phone connects to a network that has 802.1x enabled. If the authentication fails, the phone does not boot. ShoreTel IP phones deployed on networks where 802.1x authentication is not enabled boot when they connect to the Ethernet switch. ShoreTel provides a default user ID for the phones that support 802.1x. The default user ID is the last six characters in the MAC address assigned to the phone. The MAC address is the 12-digit number on the barcode label attached to the back of the phone. ShoreTel IP phones support the following aspects of 802.1x authentication:
MD-5 challenge method only. Multicast and unicast frames. Devices attached to the second Ethernet port (PC port) using 802.1x PAE
multicast frames.
EAPOL frames can be prioritized. EAPOL VLAN tags are not supported.
device endpoints. 802.1x. The default SID (supplicant user id) is the last 6 characters of the MAC address of the phone. The password must be entered manually (no default) the first time the phone boots and is then cached if authentication succeeds. If upgrading from another firmware that supports 802.1x (3.3.x or 3.4.x), the previous settings (802.1x on/off, SID, password) will be preserved. If upgrading from a firmware that does not support 802.1x (2.2, 2.3, 3.1, 3.2) Logical Link Discovery Protocol (LLDP) will be turned on by default and a default SID of the last 6 characters of the MAC address will be applied. ShoreTel IP phones that do not support 802.1x authentication include:
Ma nd i tory TIA-1057 LLDP-Med functionality for Class III communication
ShoreTel IP 110 ShoreTel IP 210
ShoreTel 13.1
243
14.3.3 DHCP Settings

ShoreTel IP phones are pre-configured to use the networks DHCP server for addressing. In addition to its address and standard network addresses, the DHCP servers response also provides the following:
ShoreTel server address: The ShoreTel servers address is used to access and
download the latest telephone application software and the configuration information for the ShoreTel system. to maintain the telephones displayed time and date. ShoreTel highly recommends that you use your internal NTP server for all your ShoreTelrelated Time and Date requirements.
SNTP (NTP) server: The SNTP (NTP) server provides a standard network time
14.3.3.1 ShoreTel Server Address

The ShoreTel server provides the IP phones with the latest application software and the configuration information that enables the IP phone to be automatically added to the ShoreTel system. The ShoreTel servers address must be provided to the phone as a vendor-specific option. Shore Phones are pre-configured to look for the ShoreTel servers address to be specified as Vendor Specific DHCP Option 156. If these options are not available, the ShoreTel IP phones will use Option 66. For help on configuring these DHCP Options, see "Configuring DHCP for ShoreTel IP Phones" on page 68.
14.3.3.2 SNTP Server

The DHCP server should be configured to provided the address of your networks SNTP (NTP) server to provide date information to the IP phones.
14.3.4 Manually Configuring the ShoreTel IP Phones

If you are not using a DHCP server to provide the IP address and configuration parameters to the phone, you need to manually set configuration parameters on the phone. You can enter the phone configuration menu at bootup or by entering a key sequence from the phones keypad. To manually configure a ShoreTel IP Phone at bootup: Step 1 Connect the Ethernet cable to the data jack on the back of the IP phone or BB24. Step 2 At the Password prompt, enter the default password 1234, or the password provided by your system administrator, followed by the # key. You have four seconds to enter the password, after which the phone enters normal operation with its current settings. The default password can be changed in ShoreTel Director. For more information, see the ShoreTel System Administration Guide. The BB24 setup screen can be accessed by pressing the upper left-most and lower right-most buttons. Step 3 Enter the values listed in Table 14-1 when prompted. Step 4 Press # to advance to the next settings or * to exit.
244
Table 14-1 Prompt Clear All Values? DHCP= FTP= MGC= SNTP= 802.1Q Tagging=off VLAN ID= Country= Language= Save all Changes
Configuration Values Value Press #. (No) Press * to toggle to the off position and then press #. Enter the IP address of your ShoreTel server. Press #. Press #. (The phone obtains the address from configuration files on the ShoreTel server). Enter the IP address of your time server. Press #. Press #. Consult your network administrator before changing this value. Press #. Enter the country code (see Table 3-12 on page 69). Enter the language code (see Table 3-13 on page 71). Press #. (Yes)
The phone downloads the latest bootROM and firmware from the ShoreTel server and in the process, reboots several times. When the phone displays the date and time, the boot and upgrade process is complete. To manually configure an operational ShorePhone from the keypad: Step 1 With the phone on hook, press the MUTE key followed by 73887# (SETUP#). Step 2 At the Password prompt, enter 1234, or the password provided by your system administrator, followed by the # key. The default password can be changed in ShoreTel Director. For more information, see the ShoreTel System Administration Guide. Step 3 Enter the values listed in Table 14-1 when prompted. Press # to advance to the next settings or * to exit. The phone downloads the latest bootROM and firmware from the ShoreTel server and in the process, reboots several times. When the phone displays the date and time, the boot and upgrade process is complete.
14.4 Displaying ShoreTel IP Phone Settings

You can display the phones current IP parameter settings by pressing a sequence of buttons on the phones number pad. To display the phones IP parameter settings: Step 1 With the phone on hook, press the MUTE key followed by 4636# (INFO#). The phone will display the first two parameters. Step 2 Press # to advance the display or * to exit. The phone will resume normal operation after the last parameter has been displayed.
ShoreTel 13.1
245
14.4.1 Resetting a ShoreTel IP Phone

You can reset the phone by entering a key sequence from the phones keypad. To reset the phone, place the phone on hook, press the MUTE key followed by 73738# (RESET#). The phone will reboot.
14.5 Associating a User Group with Unassigned IP Phones

Unassigned IP phones are available for users configured for Any IP Phone. Select the user group that will have access to unassigned IP phones from the pull-down list. Since unassigned IP phones are not associated with a user, you cannot report on calls made from these telephones and associate them with an individual user. It is recommended that unassigned IP phones be configured with a class of service with minimal calling privileges.
246
Chapter 15
Desktop Requirements
This chapter describes the hardware and software requirements for installing ShoreTel client software (ShoreTel Communicator for Windows) on desktop and laptop computers. The topics discussed include:
Recommendations on page 247 Hardware Requirements on page 247 Software Requirements on page 249
The installation procedures are covered in Chapter 10.
The following recommendations will assist you in planning and installing your desktop computers for the ShoreTel Communicator applications.
Verify that each computer meets the minimum hardware and software
requirements.
Install the Client for the Microsoft Networking component. Close all applications before installing software. Users must have local administrative privileges to install the ShoreTel software. Microsoft Outlook must be configured in Corporate or Workgroup mode for
Microsoft Outlook Integration to function properly. Internet Only mode is not supported. will be using.
Users should be informed of which ShoreTel Communicator application they During a fresh install or upgrade to the ShoreTel client, Visual Studio Tools for
Office (VSTO) pre-requisites need to be installed first. The VSTO pre-requisites will be installed automatically during the ShoreTel client installation.
15.2 Hardware Requirements

The requirements for running ShoreTel Communicator on the computers of endusers depend on the version of ShoreTel Communicator Client you want to install and the video call resolution. Table 15-1 provides information about the processor requirements for different configurations of ShoreTel Communicator. Table 15-2 provides information about the minimum memory requirements for different configurations of ShoreTel Communicator. Table 15-3 provides information about the requirements for installing different configurations of ShoreTel Communicator for end-users in a Microsoft Windows terminal server (WTS) environment.
ShoreTel 13.1 247
Chapter 15: Desktop Requirements
Table 15-1 ShoreTel Communicator Version
Client Device Hardware Requirements Windows XP and Vista Windows 7 Pentium 3, 800 MHz Pentium 4 - 1.6 GHz Max Presence Load No Presence supported
Communicator with Personal Access Communicator with Professional Access Communicator with Agent, Supervisor, Operator Access (<40 extension presences) Communicator with Agent, Supervisor, Operator Access (<500 extension presences) All Versions, VGA Video All Versions, XGA Video
Pentium 4, 3.0 GHz Pentium 4, 3.0 GHz 1 Event/Second w/HT or Dual w/HT or Dual Core 1.6GHz Core 1.6GHz Pentium 4, 3.0 GHz Pentium 4 - 3.0 1 Event/Second w/HT or Dual GHz with HT or Core 1.6GHz Dual Core 1.6 GHz Dual-Core 1.6 GHz Dual Core 1.6 GHz 1 Event/Second
Dual-Core 1.6 GHz Dual-Core 1.6 GHz 1 Event/Second Core 2 Quad, 2.4 GHz Core 2 Quad 2.4 GHz 1 Event/Second
Table 15-2
Client Hardware - Hard Disk Drive and Memory Requirements Hard Disk Space1 XP Vist Wi a n7 RAM2 XP Vist Wi a n7 Available RAM2 XP Vist a Win 7
ShoreTel Communicator Version Communicator with Personal Access: Presence On Communicator with Personal Access: Presence Off
1GB
1GB
1GB
1GB
2GB
2GB
100MB 100MB 150MB
Communicator with Professional 1GB Access

1GB Communicator with Agent, Supervisor, Operator Access (<40 extension presences)
1GB
1GB
1GB
2GB
2GB
150MB 150MB 250MB
1GB
1GB
1GB
2GB
2GB
150MB 150MB 250MB
Communicator with Agent, Supervisor, Operator Access (<500 extension presences) All Versions, VGA Video All Versions, XGA Video
1GB
1GB
1GB
1GB
2GB
2GB
150MB 150MB 250MB
1GB 1GB
1GB 2GB
1GB 2GB
1GB 1GB
2GB 2GB
2GB 2GB
150MB 150MB 250MB 150MB 150MB 250MB
1Disk space requirement is for installation on a system without .NET Framework previously installed. Otherwise, Communicator
requires less than 100 MB hard disk space. 2ShoreTel Communicator memory requirements are during normal operation. When running other Microsoft Office applications on the PC in addition to Communicator, additional memory recommendations are 512 MB (XP), 1 GB (Vista/Windows 7). If Microsoft Outlook contacts are imported, memory requirements will increase in relation to the number of contacts imported.
248
Table 15-3 WTS Version
WTS Server Minimum Hardware Requirements RAM Memory Minimum required per Processor 2 client within the WTS 100 MB Single DualCore E5410 @ 2.33 GHZ / 16GB RAM Single QuadCore E5410 @ 2.33 GHZ / 32 GB RAM Dual QuadCore E5520 @ 2.26 GHZ / 32 GB RAM Dual QuadCore E5520 @ 2.26 GHZ / 32 GB RAM
Max Max Presence/ Number of Call Load 1 Users per WTS 50 2400
W2008, 32-bit, SP2, Enterprise W2008, 64-bit SP2 (non R2) (Standard and Enterprise) W2008, R2
100
5000 BHCC
200 MB
100
5000 BHCC
150 MB
W2008 R2 with 100 XenApp-6 Platinum

1Presence 2
5000 BHCC
175
events refers to the Presence status displayed in the Contacts viewer of ShoreTel Communicator. Please consider that other applications and environments such as Microsoft Office, etc. could also run within the same server. The CPU/RAM used must be dimensioned according to ALL applications running and not only ShoreTel. The above specifications were validated only for the ShoreTel user count and call load depicted in the table
15.3 Software Requirements

This section discusses the software requirements for installing the ShoreTel Communicator client software on computers end-users use.
15.3.1 Operating Systems

In the current release, the following operating systems support ShoreTel Communicator client software:
Windows Operating Systems

Windows XP Professional, 32 bit, SP3 Windows Vista Business, 32-bit, SP2 Windows Vista Enterprise, 32-bit, SP2 Windows Vista Enterprise, 64-bit, SP2 Windows 7 Professional, 32-bit, SP1 Windows 7 Enterprise, 32-bit, SP1 Windows 7 Professional, 64-bit, SP1 Windows 7 Enterprise, 64-bit, SP1 Unicode support (Double Byte Character)
Mac OS X 10.7
ShoreTel 13.1
249
Windows Server (terminal license server)

Windows 2008 Server, 32-bit, SP2 (Enterprise) Windows 2008 Server, 64-bit, SP2 (non R2)Standard and Enterprise Windows 2008 Server, 64-bit, R2
Citrix XenApp: For platform details on Windows Terminal Server and Citrix
XenApp, see Appendix C, Installing ShoreTel Communicator on Citrix and Windows Terminal Servers.
15.3.2 .NET Framework

On Windows-based computers, ShoreTel Communicator requires the installation of .NET Framework version 3. 5 or higher. When .Net Framework is not already installed on the target computer, the Communicator installer will automatically install (or update) the software if a copy is available in the Communicator installation files on the server (.Net Framework is not shipped with the product) or trigger a download from Microsoft before installing Communicator. The person doing the installation will be prompted to accept the end user license agreement from Microsoft to proceed with the .NET installation.
15.3.3 ShoreTel Communicator for Web Browser Requirements

ShoreTel Communicator for Web can be accessed and controlled via web browser. The following browser versions are supported in ShoreTel 13.1:
Safari 5.0 on Macintosh. Microsoft Internet Explorer 9.0. Firefox 12.0 on Windows and Mac OS. Adobe Flash 9 or higher should also be installed.
15.3.4 Microsoft Outlook Integration

This section discusses different ways ShoreTel Communicator integrates with Microsoft Outlook.
15.3.4.1 Integrating with E-mail

ShoreTel Communicator supports e-mail integration with the following products:
Microsoft Outlook 2007, SP2. Microsoft Outlook 2010 (32 bit). Microsoft Outlook 2010 (64 bit)
NOTE ShoreTel 13.1 does not support Microsoft Outlook 2003. Additional Requirements for Microsoft Outlook Integration include:
Microsoft Outlook must already be installed as the user's e-mail before

installing Outlook integration features.
Microsoft Outlook must be configured for workgroup mode (supporting
multiple mail service providers) and not for Internet-only mode before installing Microsoft Outlook integration features.
250
Automatic Call Handling with the Microsoft Outlook Calendar requires an

optional component of Microsoft Office called Collaborative Data Objects. calendar integration to work.
The Collaboration Data Object must be installed in order for Microsoft Outlook 15.3.4.2 Integrating with Call Handling
ShoreTel can integrate with Microsoft Outlook 2007 and Microsoft Outlook 2010 to allow Offline Call Handling Modes (CHM). Once configured, a users CHM will automatically change, based on the users Microsoft Outlook calendar even when Microsoft Outlook is not currently opened. Microsoft Outlook 2007 Plug-in with Offline Call Handling Modes requires the installation of the following components on the client system:
NET Framework 3.5 Microsoft Outlook 2007 Primary Interop Assemblies Visual Studio Tools for Office Runtime 3.
Microsoft Outlook 2010 Plug-in with Offline Call Handling Modes requires the installation of the following components on the client system:
NET Framework 3.5 Microsoft Outlook 2010 Primary Interop Assemblies Visual Studio Tools for Office Runtime 3
ShoreTel 13.1
251
252
Chapter 16
Desktop Installation
This chapter describes the procedure for installing ShoreTel Communicator on PC and Mac computers. You can install ShoreTel Communicator or have users install ShoreTel Communicator, in which case the server can notify them with information on their extensions and how to install the ShoreTel Communicator. The topics discussed in this chapter include:
Recommendations on page 253 Notifying Users via Email on page 254 Installation Procedure on page 254 Installing Outlook Integration on page 268 Upgrade Procedures on page 271 User Licensing on page 271 User Licensing on page 271
See Planning Applications and Services on page 135 for all hardware and software requirements for the ShoreTel Communicator application.
The following information can help with the installation of the ShoreTel Communicator application on a desktop computer.
Have the following information: the server name, user name, password, and Close all applications before starting the ShoreTel software installation.
extension number. This information must be available before the first-time use of the ShoreTel Communicator application.
With the Silent Client Install feature, the client software upgrade process on
remote machines do not require administrative rights by the person installing or upgrading software on client machines. Administrators can upgrade the software on all client machines using Active Directory Group Policies regardless of the permissions associated with those machines or the users who log into those machines. Outlook must be configured in Corporate or Workgroup mode for Outlook integration to function properly. Internet Only mode is not supported.
Many of the changes are reliant on Microsoft Active Directory. Microsoft
ShoreTel 13.1
253
Chapter 16: Desktop Installation
16.2 Notifying Users via Email

To simplify installation, the ShoreTel system provides an integrated software distribution feature. Using ShoreTel Director, the system administrator can send an e-mail message to each user configured with an e-mail address. You can send all users, some users, or just one user an e-mail message using the Notify Users page (Figure 16-1).
Figure 16-1
Notify Users page
16.3 Installation Procedure

This section provides the most typical steps associated with installing the ShoreTel Communicator application. There are two methods of installing ShoreTel Communicator software:
Silent Client Upgrade Standard Integrated Software Distribution
16.3.1 Silent Client Upgrade

The Silent Client Upgrade allows the ShoreTel client software to be installed or upgraded on a client machine from a remote machines without the need for administrative rights. An administrator can easily upgrade the software on all client machines regardless of the permissions associated with those machines or the users who log into those machines. Many of the changes are reliant on Microsoft Active Directory. The Microsoft Active Directory software handles the following tasks:
Create a Group Policy Object to use to distribute the software package Assign a package to a group of computers running Windows XP Professional, or
Windows Vista
Publish a package Remove a package

You will need to have the following files from the Client DVD accessible with file permissions set to Share and File level Access by group <everyone>:
Data1.cab Setup.exe ShoreTel Call Manger.msi
254
Enabling the new Remote Client Upgrade functionality requires performing a number of tasks using Microsoft Active Directory. For information on performing those tasks, refer to the following Microsoft Reference articles:
How To Use Group Policy to Remotely Install Software in Windows 2003. Article # 816102 (for Windows 2003)
ShoreTel recommends selecting the Prevent Users from Initiating Client Upgrades check box in the Edit System Parameters window. For details about other parameters, refer to the ShoreTel System Administration Guide.
16.3.2 Installation Requirements

This section provides information about the operating system and hardware requirements for installing ShoreTel Communicator for Windows on and client computers.
16.3.2.1 .NET Installation

Communicator requires the installation of version 3.5 (or higher) of .NET Framework. The Communicator installer automatically downloads the correct .NET Framework version if it is not present during the upgrade or install. Users are then prompted to accept the End User License Agreement from Microsoft to proceed with the .NET installation. Internet connectivity is required during the installation process.
16.3.2.2 64-bit Platform Support

ShoreTel Communicator for Windows supports Windows 2008 R2 running Windows Terminal Server, 64-bit. To install ShoreTel Communicator for Windows on 64-bit Windows 2008 Terminal Server: Step 1 Install .Net Framework for 64-bit Windows machines Version 3.5 or higher. NOTE .Net Framework is not supplied with the ShoreTel installation software. This software is available from Internet sources or from your software vendor. Step 2Install Communicator for Windows. Step 3Access Control Panel > Phone and Modem > Advanced (tab) and remove ShoreTel Remote TAPI Service Provider. Step 4Run TSPInstall.exe TSPInstall.exe is provided with the ShoreTel installation software. Installing ShoreTel Communicator for Windows on a 64-bit platform places files in the following folders:
The default location is C:\Program Files (x86) The location of 32-bit client dll files is C:\Windows\SysWow64
ShoreTel 13.1
255
16.3.2.3 Installation in a Large Deployment that Uses Active Directory

Some unique requirements exist for the installation of ShoreTel Communicator in a large deployment that uses Active Directory. This section outlines both the manual and the automated installation of ShoreTel Communicator in a large site with Active Directory. The decision for how to proceed depends on the following key factors:
Whether manual (local) or remote installation is used. Presence on the server of .NET Framework version 3.5 or higher. Access to the World Wide Web (if .NET Framework 3.5 is not on the server).
The version of .NET Framework that is used should be the 32-bit version for a 32-bit server or the 64-bit version for a 64-bit server. Manual Installation Manual installation of .NET Framework can be in one of two scenarios. In one scenario, the Prerequisites folder contains .NET Framework 3.5 (or higher). In the other scenario, .NET Framework 3.5 does not exist at all on the ShoreTel server. If the required version of .NET Framework does not exist on the system, Web connectivity is required during installation. Automated Setup If the system administrator is using automated (remote) installation to set up ShoreTel Communicator in a large network that uses Active Directory, the administrator must push the following packages in the order listed below by using Microsoft Corporations Group Policy Object (GPO) or another deployment tool: 1. Microsoft .NET Framework 3.5 (not located in the Prerequisites folder). Either .NET Framework exists on the system or the system must be connected to the Web (so that initiation of setup.exe causes a download of .NET Framework.) 2. Interop Assemblies (located in the Prerequisites folder) should contain Primary Interop Assemblies for 2007 and VSTO (Visual Studio Tools for Office). This resides in the Prerequisites folder. Communicator (CMWin), located in the Setup folder.
16.3.3 Prerequisites for ShoreTel Communicator Installation in a Large Deployment

This section discusses large-scale ShoreTel Communicator deployments that use Active Directory. This section provides procedures manual and automated installations.
16.3.3.1 Manual Installation

This section contains instructions for manual installation in two scenarios. In one scenario, the Prerequisites folder contains .Net Framework 3.5. In the other scenario, .Net Framework 3.5 does not exist at all on the ShoreTel server.
256
16.3.3.2 Manual Setup with .Net Framework in Prerequisites

The ability to install ShoreTel software manually depends on the availability of .Net Framework 3.5. If the Prerequisites folder contains .Net Framework 3.5 and other, correct files, the system administrator can run setup.exe while the system is disconnected from the Internet. If the system does not already have .Net Framework, the system must have an operational connection to the Internet.
16.3.3.3 Manual Setup with .Net Framework Absent

If the Prerequisites folder does not contain .Net Framework 3.5, the system must have Internet connectivity because, when the system administrator runs setup.exe, the system automatically downloads .Net Framework 3.5.
16.3.3.4 Automated Setup

For Communicator in a large-scale deployment that includes Active Directory, the remedy is for system administrators to install individual items in the order listed below. The administrator must push the following packages in the order shown through GPO or any other deployment tool: Step 1 Microsoft .Net Framework 3.5 (not located in the Prerequisites folder). Either .Net Framework exists on the system or the system must be connected to the Web (so that initiation of setup.exe causes a download of .Net Framework.) Step 2 Interop Assemblies (in the Prerequisites folder) should contain Primary Interop Assemblies for 2007 and Visual Studio Tools for Office (VSTO). This resides in the Prerequisites folder. Step 3 Communicator (CMWin), located in the Setup folder.
16.3.4 Standard Integrated Software Distribution Overview

ShoreTel systems integrated software distribution feature simplifies installation. Although the process presents a number of screens, there is a default installation that requires no input; you click through the screens until you are prompted to restart your desktop. Users receive an e-mail message from the ShoreTel system containing the information they need to install the ShoreTel Communicator application. The installation program is accessed using the URL listed in the e-mail notification. Notice that the e-mail notification includes the server name and the user name: Users will need this information when they start the ShoreTel Communicator application for the first time. The software can also be installed from the ShoreTel Communicator CD.
16.3.5 Installing ShoreTel Communicator on a Windows PC

NOTE Administrative rights on the client PC is required to install ShoreTel Communicator for Windows Step 1 Open the e-mail notification from the ShoreTel administrator containing the instructions for installing the ShoreTel client. Step 2 Click on the link to the ShoreTel software.
ShoreTel 13.1 257
From there, you can initiate the ShoreTel client installation. NOTE You can also reach the software by copying and pasting the address in the URL field of an open browser. An example link is below: http://<server_IPaddress>/ShorewareResources/ClientInstall The ShoreTel Client Install page shown in Figure 16-2 appears.
258
Step 3 After reviewing the information on this page, click the Install button. The InstallShield Wizard downloads the installation files (showing the progress of the download), unpacks the installation files, and configures the Windows Installer. The Welcome screen for the InstallShield Wizard appears as shown in Figure 16-3. The version number of the ShoreTel software is shown at the bottom of the screen. Step 4 To proceed, click Next. The ShoreTel End User License Agreement appears as shown in Figure 16-4. Step 5 If you agree to the license terms, select the option I accept the terms in the license agreement and click Next. The InstallShield Wizard presents a default destination folder as shown in Figure 16-5 ). Step 6 Click Change if you want to place the ShoreTel Communicator application software in a different location. Step 7 Click Next to continue. The Ready to Install screen appears as shown in Figure 16-6. InstallShield has gathered enough information about your system to proceed. Step 8 Click Install to continue. During the final installation process, a status screen appears as shown in Figure 16-7. Installation may take a few minutes. Step 9 When installation is complete, click Next. Software installation is complete when the InstallShield Wizard Completed screen appears as shown in Figure 16-8. Step 10 Click Finish.
ShoreTel 13.1
259
Step 11 When prompted to restart your computer as shown in Figure 16-9, click Yes. The InstallShield Wizard shuts down your computer, and restarts it. When your desktop reappears, you will notice a new shortcut icon called Shortcut to ShoreTel Communicator.
Figure 16-2 Client Install page
Figure 16-3 Welcome from InstallShield Wizard for ShoreTel Communicator
260
Figure 16-4 ShoreTel Software License Agreement
Figure 16-5
InstallShield Wizard Destination Folder
ShoreTel 13.1
261
Figure 16-6 Ready to Install
Figure 16-7
InstallShield Wizard Installation Status
262
Figure 16-8 InstallShield Wizard Installation Completed
Figure 16-9 InstallShield Wizard Restart Prompt
ShoreTel 13.1
263
16.3.6 Installing ShoreTel Communicator on a Mac

Step 1 Open the e-mail notification from the ShoreTel administrator containing the instructions for installing the ShoreTel client. (Figure 16-10) Step 2 Follow the instructions in the message: Click the link. (Figure 16-11) From there, you can initiate the ShoreTel client installation. NOTE: You can also reach the software by copying and pasting the address in the URL field of an open browser. An example link is below: http://<server_IPaddress>/ShorewareResources/ClientInstall Download the software. (Figure 16-12) Install the software (drag & drop). (Figure 16-13) Log into Communicator.(Figure 16-14) NOTE: If you do not have a user name and password, obtain them from your System Administrator. Communicator is opened on your desktop. (Figure 16-15)
Figure 16-10 E-Mail Notification from ShoreTel Administrator
264
Figure 16-11 Click the Link
Figure 16-12 Download the Software
ShoreTel 13.1
265
Figure 16-13 Install the Software
Figure 16-14 Log into Communicator
266
Figure 16-15 Communicator Open on Your Desktop
ShoreTel 13.1
267
16.3.7 Configure the TAPI Dialing Parameters

The installation of the ShoreTel Communicator application will require the user to provide his area code and dialing rules if not previously configured. When this is required, the Phone and Modem Options control panel applet will start during the installation to prompt for the necessary configuration information. To continue, specify the location and area code information. Additionally, configure the dialing rules section with the appropriate information for dialing external and long distance numbers. When the information is configured and the OK button is pressed, the installation will continue.
16.3.8 Starting the ShoreTel Communicator Application

The ShoreTel Communicator application can be started in one of three ways:
Automatically upon system startup. From the Shortcut to ShoreTel Communicator icon on the desktop. From the Start > Programs > ShoreTel menu item.
The first time the ShoreTel Communicator application is started, a wizard appears prompting you to configure your ShoreTel Communicator server, voice mail box If you have Microsoft Outlook installed on your computer, ShoreTel Communicator will offer to install Outlook integrated voice mail. Click Yes to have your voice mail delivered to your Microsoft Outlook Inbox. You will also be prompted to configure AutoStart. At this point you have completed the most typical steps associated with installing the ShoreTel Communicator application. Additional procedures are described in the following sections.
16.4 Installing Outlook Integration

You can integrate Outlook to ShoreTel Communicator in three areas: voice mail, call handling, and memorized phone number management. You can install these integrated components from the Outlook tab of the ShoreTel System dialog box. NOTE When using Vista or Windows 7, users who do not have local administrative rights will not be able to install Communicator for Windows nor Outlook voice Mail/Calendar Integration.
16.4.1 Installing Voice Mail Integration

After you have installed voice mail integration, you have the option to:
Use Outlook as the default voice mail client Attach voice mail to messages when moved Delete voice mail from messages when moved
16.4.1.1 Attach Voice Mail to Message when Moved

Check this option for your voice mail message to be saved in your Outlook folders for archival purposes. If you move a message to an Outlook folder when this option is in effect (and the Delete Voice Mail from Message when Moved option, described below, is not selected), a copy of the message is still stored on the voice mail server. If you delete the message in the voice mail interface, the Outlook copy is still available.
268
If you move a message without this option in effect and delete the message in the voice mail interface, the message information is still in Outlook, but the message itself is unavailable.
16.4.1.2 Delete Voice Mail from Message when Moved

Check this option to delete your voice mail messages from the ShoreTel System if you move a voice mail message to an Outlook folder. This is used to store messages in Outlook and free your voice mailbox for more messages. To install voice mail integration: Step 1 In the ShoreTel Communicator tool bar, click the ShoreTel icon. A shortcut menu appears. Step 2 Click Configure ShoreTel System. The ShoreTel System dialog box appears. Step 3 Click the Outlook tab as shown in Figure 16-16.
Figure 16-16 ShoreTel System Control Panel (Outlook Tab) Step 4 Click Install. In some cases, a warning appears requesting that you close running applications before continuing. Close the applications as requested.
16.4.2 Activating the Integration of Voice Mail with Microsoft Outlook

This section describes the steps that an end-user performs in Communicator to activate the integration of ShoreTel Voice Mail with Microsoft Outlook. After a user has the ShoreTel Communicator application, an activation step is still necessary
ShoreTel 13.1 269
within SHoreTel Communicator. The steps in this section contain information that administrators give to users, or the users can find this information in one of the Communicator guides, such as ShoreTel Communicator for Windows User Guide. No application program except ShoreTel Communicator should be running on a users computer before the user begins the following steps: Step 1 Navigate to the Options and Preferences window (for example, through Tools > Options at the top of the Communicator interface). Step 2 Click Outlook. in the command navigation panel on the left side of this window. Step 3 Click the Install button to the right Voice Mail. NOTE If one or more applications are running when the administrator clicks Install, a request appears that tells the system administrator to all close running applications before continuing with the installation. If any application is running during the installation, the user must restart Outlook to make the changes apply.
16.4.3 Memorized Phone Number Management

ShoreTel Communicator Quick Dial has an option for importing Outlook contacts. To set the option under Memorized Phone Number Management: Step 1 In the Memorized Phone Number Management section, click Read phone numbers from Outlook on startup option. Step 2 If you want to exclude FAX numbers from the search, click Don't include FAX numbers. Step 3 If you want Outlook Contact to appear when you have an incoming call, click Pop Outlook contacts on incoming call. Step 4 Click More Options to select which Outlook contacts to import. The MAPI Import Options dialog box appears. Step 5 Click Enable Disk Caching if you want Outlook contacts to be available without delay when ShoreTel Communicator starts. When you have enabled disk caching, you can set when ShoreTel Communicator imports contacts. If disk caching is not enabled, ShoreTel Communicator imports contacts every time it starts. Step 6 Click the Import Configurator tab. Step 7 Click the locations where you want ShoreTel Communicator to search for contact information. To select individual folders, click Details and check the folders you want searched for contact information. Step 8 Click OK. Step 9 If you want to import contacts now, return to the Disk Cache Options tab and click Read Contacts Now. If you do not click this button, the Outlook contacts will be imported the next time you start ShoreTel Communicator.
270
It will take some time for the ShoreTel Personal ShoreTel Communicator to load your Microsoft Outlook Contacts. Your Outlook Contacts will not be available until loading has been completed.
16.5 Upgrade Procedures

When the ShoreTel system is upgraded, users running older versions of ShoreTel Communicator or Call Manager may be informed that they must upgrade. Upgrades of the system may not require client upgrades. Refer to the online knowledge base on the ShoreCare web site to determine if a system upgrade requires client modifications.
16.6 User Licensing

ShoreTel offers three user license types:
Extension and mailbox Extension-only Mailbox-only
These new choices allow users to request a phone extension license without having to purchase a mailbox at the same time. This additional flexibility may be helpful in situations where a fax machine, a modem, or a lobby phone is desired and a mailbox for voice mail was not needed. Similarly, users can purchase a mailbox without having to purchase a phone extension. Earlier releases of the ShoreTel product offered Single Site and Multi-Site Enterprise license keys. In this release, the Single Site key is no longer available. For existing users, the Single Site key can still be used and will be renamed as a Single Site Extension and Mailbox license. Previous Multi-Site Enterprise keys become Extension and Mailbox licenses.
16.6.1 Purchasing User Licenses

Each user must be configured with one of those three license types. A license must be purchased for each user, based upon the needs of that user. To see if an installation is in compliance with the number of licenses purchased, all Extension-Only, MailboxOnly, and Mailbox-and-Extension users are counted and compared against the sum of the licenses purchased.
Extension and mailbox: Purchase of this license entitles the user to be

assigned to both a physical extension and a ShoreTel mailbox.
Extension-only: Purchase of this license entitles the user to be assigned to a Mailbox-only: Purchase of this license allows the user to be assigned to a
ShoreTel voice mail-box.
physical extension, either via explicit assignment or via Extension Assignment.
16.6.2 Language Licenses

ShoreTel supports multiple languages in addition to US English (which will remain the default language for new installations). One or more languages can be running at a site by purchasing a language license.
ShoreTel 13.1
271
If only one language is needed at a single site, there is no need to purchase a language license. For instructions on configuring the User Licenses or Language Licenses via Director, please refer to the ShoreTel System Administration Guide.
16.6.3 License Control

License Control adds enforcement and branding to the ShoreTel product and provides tighter enforcement (via MAC address-based node locking) on existing licensing. When an existing ShoreTel system is upgraded to the current software release, an enforcement scheme requires entry of a system key. When launching ShoreTel Director, you are asked to enter either a Small Business Edition (SBE) or Enterprise Edition (EE) key (see below for details on the differences between these two). You can request a key online via Director. If an invalid key is entered or if the field is left empty, you will be allowed to log into the system for 45 days. If no action is taken within the 45-day grace period, ShoreTel Director will be locked and you will be unable to make any configuration changes to the system (although the phones will continue to work). This 45-day period allows for unplanned, ad hoc changes that may cause you to exceed license limits while providing time to comply with the license requirements by either removing unneeded configurations or by ordering additional licenses. You will be forced to purchase one of two keys available:
SBE key required for Small Business Edition

This key is for smaller businesses. Use of this key results in the display of SBE branding (on the initial login page above the navigation pane). The SBE license allows a maximum of 50 users with an extension and mailbox, and the customer can add up to 50 users who have only a mailbox.
EE key required for Enterprise Edition

This is for larger businesses with more than three sites. The existing branding appears. System behaves as it does today, except that number of sites is enforced via nagging. Block adding an additional SBE or EE key. Details:
For an SBE system, the following features are not available:

AMIS SMDI On-net Dialing SBE does not support integration with another ShoreTel system or any 3rd party PBX.
272
Refer to the ShoreTel System Administration Guide for instructions on configuring licenses in ShoreTel Director or for more information about the following types of Keyed License Types and Self-Audited License Types:
Keyed License Types:

ShoreWare System License (Enterprise) ShoreWare Additional Site License ShoreWare Extension License ShoreWare Mailbox License ShoreWare SoftPhone License ShoreWare Additional Language License Mobile Access License ShoreWare SIP Trunk License ShoreWare SIP Phone License ShoreWare Standard Resolution Video License ShoreWare High Resolution Video License Professional Access License Operator Access License Workgroup Agent Access License Workgroup Supervisor Access License ShoreWare External Unified Messaging SIP Link License Audio Conference License Web Conference License
Self-Audited License Types:

ShoreTel Communicator with Personal Access Remote Server Software License TAPI Application Server License Phone API License
ShoreTel 13.1
273
274
Chapter 17
ShoreTel Integration with External Applications

To work with some external applications, additional setup may be required after you have installed the system. This chapter identifies and describes some setups that allow the system to integrate with external applications. Topics include:
"Importing Public Contacts" on page 275 "Installing the ShoreTel Telephony Interface (STI)" on page 277
17.1 Importing Public Contacts

A new batch utility on the headquarters server allows you to import public contacts. It can be run once, or you can set up a Task Scheduler on the server to run this batch file at a regular interval. The batch utility can be found under the default installation path:
C:\Program Files (x86)\Shoreline Communications\ShoreWare Server\ImportContacts\ImportPublicContacts.bat
The utility connects to your Microsoft Exchange (2007 or 2010) server via the Exchange Web Services with an account that is allowed to read contacts in the Exchange public folders (contact list). The utility reads the contacts from the specified public folders and places them in a CSV (Comma Separated Value). The batch file then invokes the dbimport tool to import these contacts into the ShoreTel system directory. These contacts are then displayed in any end points able to access the system directory, such as the phones and ShoreTel Communicator. The batch utility xml config file must be adjusted to specify the Exchange account, the Exchange location, and the folders to import. NOTE This utility does not allow contacts to be imported from the GALs.
ShoreTel 13.1
275
Chapter 17: ShoreTel Integration with External Applications
17.1.1 Creating a CSV File

You can use CSV files for importing public directory information into the ShoreTel system for end users. Use the following parameters to create CSV files used by ShoreTel to import public directory information:
File name must have a .csv extension. Standard CSV formatting supported. First line in file must start with Source= or Volume=. You can include both. If
a value for source is used, it overrides the file name as the name of the file.
The next populated line contains the field names used for this file. Field names can include any of the following:
Contact ID First Name Middle Name Last Name Business Phone Business Phone 2 Home Phone Home Phone 2 Mobile Phone Pager Business Fax Company Department E-mail Address E-mail Address 2 IM Address Contact ID
276
17.2 Installing the ShoreTel Telephony Interface (STI)

ShoreTel 13.1 does not automatically install the ShoreTel Telephony Interface (STI) during installation. If you are using third-party or supplementary ShoreTel applications that interact with the ShoreTel system, you may have to manually install the STI. This section describes how to install STI on Windows clients with third-party applications that integrate with ShoreTel Communicator for Windows. For information on installing STI on Citrix terminal servers, see Appendix C.
17.2.1 Requirements
Close all open programs (reboot is required). ShoreTel Communicator for Windows is installed. Location of ShoreTel system software is known.
17.2.2 Installation Procedure

Step 1 Install (or upgrade) ShoreTel Communicator for Windows. Step 2 Launch Windows Explorer. Step 3 Enter the following URL:
http://serverIP/shorewareresources/shoreteltelephonyinterface
The ShoreTel Telephony Interface Install site is opened. Step 4 Click the link to install the ShoreTel Telephony Interface (download and install the interface on the client computer). Step 5 Reboot the client computer. Step 6 Verify that the interface is installed: Step a Open Control Panel. Step b Click Phone and Modem Options. Step c Click Advanced. Step d Verify that ShoreTel Remote TAPI Service Provider is installed. Step e Select ShoreTel Remote TAPI Service Provider. Step f Click Configure. The ShoreTel Remote TSP dialog is opened. Step g In Provider Usage, verify that the provider is enabled. Step 7 Launch ShoreTel Communicator for Windows. The TAPI service registers the ID, password, and address of the user for transactions with the third-party application.
ShoreTel 13.1
277
278
Chapter 18
Legacy Integration
ShoreTel provides a way to convert a TDM-based voice network into the ShoreTel system. Integrating the ShoreTel system with an old PBX allows a customer with different systems to support phone and voice mail communication between systems. An integrated voice network can:
Simplify communications for your users with an enterprise-wide coordinated

dialing plan using extension dialing.
Exchange voice mail messages between users on different sites using different Consolidate trunks with different traffic types. Reduce service costs by redirecting inter-site calls across your IP network.
This chapter describes how to migrate your legacy system to the ShoreTel system. The topics include:
voice mail systems. Standard commands such as compose, forward, and replay extend the value of your different voice mail systems.
Introduction on page 280 Coordinated Dialing on page 280 Trunk Requirements on page 280 Coordinated Dialing Plan on page 281 PSTN Services on page 282 Multi-Site Integration on page 282 Single Site Integration on page 282 Consolidated Long Distance on page 283 Voice Mail Integration on page 283 System Requirements on page 300 Connection Cable on page 300 Administration and Configuration on page 301 Trunk Configuration on page 302
ShoreTel 13.1
279
Chapter 18: Legacy Integration
18.1 Introduction
A digital trunk tie line integrates the ShoreTel system with a legacy PBX. The connection is between the legacy systems PRI interface and the PRI interface of a ShoreTel Voice Switch located anywhere in your IP network. There are four different types of activities that occur on the interface.
Calls from ShoreTel users or applications to an extension located on the other
system are routed across the tie trunk. When a call is placed, the trunk is accessed and the ShoreTel system sends the configured number of digits to the PBX identifying the called extension. the legacy PBX, are routed across this interface. When the legacy user places their call, the legacy system accesses the trunk and then sends the digits as DNIS.
Calls from users on the legacy system or from trunks, or other applications on
Outbound calls from users or applications on the ShoreTel system can be
routed across the trunk to the legacy PBX. When a call is placed, the trunk access code or trunk configuration of the connection to the legacy PBX indicates the outbound call is to be placed to the PBX.
carried across the trunk connecting the two systems. The voice mail systems make calls to configured destinations on the other system to send voice mail messages to users on the other system. A tie trunk is not required to enable voice mail or AMIS integration. The two voice mail systems can communicate by dialing each other via the PSTN. In general, when a tie trunk is in place, AMIS calls should be routed via the trunk to reduce PSTN costs. The connection between the two systems can be provided by either T1 trunks, PRI or SIP interface. ShoreTel recommends that you use PRI or SIP to enable calling number information exchanges between the two systems.
Calls between the ShoreTel and legacy system's voice mail applications are
18.2 Coordinated Dialing

Coordinated dialing allows users to dial between the systems using extension-toextension dialing as well as enabling consolidation of inbound and outbound services. To effectively plan the integration, consider the following items:
Expected call traffic between the two systems to provide sufficient trunking Current numbers of extensions and extension lengths at both systems Service plans to determine which PSTN services are provided at each voice
system
The type of legacy PBX equipment integrated with the ShoreTel system
18.3 Trunk Requirements

The number of digital trunks required between the ShoreTel system and the legacy PBX depends on the expected traffic between the two systems. To determine the number of trunks, you need to estimate the number of calls per hour that are placed between the two systems. When estimating the call volume between the two systems, consider the following:
280
The volume of direct calls between users on the two systems Traffic related to Automated Call Distributor (ADC) calls Outbound call volume (i.e. when outbound trunking to the PSTN is provided by
one of the systems for all users, such as a PSTN trunk connected to the legacy PBX that provides long distance services for users on both the legacy and ShoreTel system)
all users) Additionally, you can rely on the estimated calls-per-hour number to determine the number of trunks to configure between the two systems.
Inbound call volume (i.e. when inbound services are provided by one system to
For more information on trunk requirements, see "Trunk Planning and Ordering" on page 97.
18.4 Coordinated Dialing Plan

With legacy integration, users on both systems can dial one another using abbreviated or extension dialing. This includes dialing from applications on the systems, such as the ShoreTel voice mail application, and would also include forwarding a call to an assistant at an extension on the legacy PBX. To determine the coordinated dialing plan configuration, you must identify the current numbering of users on both systems. For example:
When the systems are located together, extensions can normally be assigned
from a single numbering plan, or from a single DID number range provided by the local carrier. In this case, the extensions on the two systems are assigned such that there is no overlap using the desired extension length.
based on the DID range supplied by the local telephone company. In this case, overlap of the extension ranges can occur at the currently used extension length. For example, consider the following situation.
When systems are at different locations, each systems numbering plan is often
One location is assigned DID range 408-555-2000 through 2999 The second location is assigned range 650-333-2500 through 2799
the DID numbers. In this case, there are users on both systems currently assigned extension 2500. To provide a coordinated dialing plan across the systems, the extensions must be adjusted to make them unique system-wide. In the integration, four-digit extensions that overlap are made unique by increasing the extension length across the system. When the extension length is increased, the first digit becomes the system number and the remaining digits are the extension. In the above example, the extension length would be increased to five-digit dialing, and at the first location would be extensions 52000 through 52999, while users at the second location would be assigned extensions 32500 through 32799. The extensions on all systems that are integrated together should be configured to be the same length.
The systems currently use four-digit dialing matching the trailing 4 digits of
ShoreTel 13.1
281
Be sure to document the planned integrated dialing plan prior to configuring the systems to streamline the configuration process. Information to take note of is provided in the following template:
Table 18-1 Dial Plan template
System One Location DID Range Local Extensions (Prefix + Number) Remote Extensions (Prefix + Number)
System Two
18.5 PSTN Services

The number of trunks, your integration plan, and the overall system design includes the provisioning of services across the network. PSTN services can be provided at both systems in the integration or consolidated together on one system.
18.6 Multi-Site Integration

When the systems are located at different sites, both systems should have local trunking for both inbound and outbound calls. Local inbound numbers make it easy for nearby customers to reach you, while local outbound trunks allow you to save on telephone charges by using local services at the site. In this configuration, the trunk lines connecting the systems are used for the intersite calling between extensions or applications on the two systems. The interfaces on the two systems are configured to dial out to the remote or off-system extensions, and to accept incoming calls using DNIS. The ShoreTel voice switch that connects to the legacy PBX should be located at the site with the legacy PBX. This leverages the IP network to extend the calls to the other sites with the ShoreTel system.
18.7 Single Site Integration

When the systems are located at the same site, it is not required that both systems be connected to the PSTN. The systems can be configured to best match your requirements. In a single site configuration, the PSTN connections for inbound calls can be connected to each system. In this environment, the trunks connecting the two systems are configured to dial out the remote or off-system extensions and to accept incoming calls using DNIS. Alternatively, inbound services can be consolidated on either the ShoreTel system or the legacy PBX. In this environment, calls to users on the other systems are forwarded to the remote or off-system extensions through the trunk lines connecting the systems.
282
When all inbound trunks are consolidated on the ShoreTel system, the trunks are configured to support off-system extensions within the range of extensions on the other PBX. When all inbound trunks are configured on the legacy PBX, the trunks on the ShoreTel system are configured to support inbound services with call routing to the extensions on the ShoreTel system. When DID numbers are already in place on one of the PBXs which will be connected, ShoreTel recommends that the inbound DID service not be moved or split between the systems but configured to remain on the system where they are currently configured and have calls to users on the other system forward across the connecting trunks. In the single site configuration, ShoreTel recommends that services for outbound calls be connected to the legacy PBX. In this configuration the trunk interfaces on the s system are configured to support outbound local and long distance dialing while the interface on the PBX is configured to route the received outbound calls.
18.8 Consolidated Long Distance

Long distance calls can be consolidated into a single PSTN interface across both the ShoreTel system and the integrated legacy PBX. In this configuration, you gain the benefits of reduced long distance rates by consolidating all your enterprise's long distance calls into a single carrier. When it is required, the outbound long distance trunks are connected to the legacy PBX and the ShoreTel system is configured to route long distance calls outbound across the digital trunk connecting the systems.
18.9 Voice Mail Integration

The primary issue with voice mail integration is they are often proprietary and the interfaces defined to connect the same and disparate systems are very old, complex and difficult to implement. In fact, many voice systems from the same vendor are not connected. The interface with which most customers are familiar is AMIS. This is an analog interface that has been around for a long time, but is a real challenge to implement and can be very expensive from legacy voice mail providers. It is not uncommon to pay $10,000 per site for this capability. Another widely-used interface, Simplified Message Desk Interface (SMDI), was developed in the days when the PBX and voice mail systems were separate systems. It operates on a serial link between a PBX and voice mail system and allows them to work together. ShoreTel supports both AMIS and SMDI protocols for voice mail integration.
18.9.1 AMIS Protocol Support

The ShoreTel system sends and receives voice mail messages to and from legacy voice mail systems using AMIS protocol Version 1 - Specification February 1992. To send voice mail messages to remote AMIS sites, ShoreTel dials the access phone number for the remote system. Likewise, to receive voice messages from a remote system, the remote system must know the number to dial into the ShoreTel system. To reach the ShoreTel system, the remote system must be configured to dial any number that reaches an auto-attendant menu.
ShoreTel 13.1
283
AMIS call support is enabled by default. Incoming AMIS voice mail is delivered in the same manner as other voice mail; however, users cannot send replies. To send outbound AMIS voice mail, you must define AMIS System profiles in ShoreTel Director. ShoreTel negotiates the setup, handshaking, and teardown of AMIS system calls. Each voice mail requires a call over the trunk group defined for the AMIS delivery and call-back numbers. To simplify AMIS systems and increase usability:
Use the same extension length across your enterprise. Use off-system extensions to match remote users mail boxes with their
extension numbers.
Assign each system a System ID to identify the remote site location

For more information on AMIS systems, see the ShoreTel System Administration Guide.
18.9.2 SMDI Protocol Support

The ShoreTel product supports the SMDI protocol, enabling seamless integration of ShoreTel equipment with legacy phone systems and enabling a smooth migration toward an all-IP telephony solution.
18.9.2.1 A little history

The SMDI protocol evolved at a time when voice mail services and PBX services were provided by separate physical devices. Over the years, manufacturers have managed to offer both PBX and voice mail services within a single device, and the need for SMDI has diminished. However, the protocol can still be useful in situations where newer equipment will be integrated into a network of older devices.
18.9.2.2 How it works

SMDI enables the separate devices that provide PBX and voice mail services to share information over an out-of-band serial cable connection. The PBX shares information with the voice mail system about incoming calls. The following information is passed to the voice mail system:
Who the call is from Where the call is going (i.e. user extension) The reason the call is going to voice mail instead of being answered
In response, the voice mail system returns a notification to the PBX that a message was left on the voice mail server. The PBX system then uses this information to alert the user by turning on the message waiting light on his or her phone.
18.9.2.3 Configurations of integrated equipment

With SMDI support, there are essentially two possible ways the ShoreTel and legacy equipment can be configured: External Voice Mail Configuration The legacy system provides voice mail services while the ShoreTel system acts as the PBX.
284
ShoreTel Voice Mail Configuration The ShoreTel system provides voice mail services while the legacy system acts as the PBX.
18.9.2.4 Additional details

A group of analog trunks from the ShoreTel system is used to access the legacy voice mail system (the ShoreTel system is on the extension side of the trunks). The ShoreTel voice mail application manages the group of outgoing extensions. The ShoreTel server can provide digit translations if the legacy voice mail and ShoreTel system have different extension lengths. Figure 18-1 shows the ShoreTel system providing PBX services and the legacy equipment providing voice mail services.
Figure 18-1
External Voice Mail with ShoreTel as PBX
Figure 18-2 shows the legacy system providing PBX services and the ShoreTel equipment providing voice mail services.
ShoreTel 13.1
285
Figure 18-2 ShoreTel Voice Mail with legacy PBX
18.9.2.5 Details Figure 18-2 shows a ShoreTel Voice Switch connected to a legacy PBX through
several analog trunks. These phone lines carry voice information from the PBX to the voice mail server. Signaling information is carried out-of-band on the separate serial line (near the bottom of the illustration). device. (The PBX link device provides the basic SMDI services that were not included in some of the older legacy PBX devices. This device must be purchased separately and configured per the manufacturer's instructions.)
A ShoreTel voice mail server is connected through a serial cable to a PBX link
The ShoreTel server and PBX link exchange information. The PBX link sends
call data to the ShoreTel voice mail server, and the call data contains information related to the source and destination of the phone call, and provides information about why the call is going to voice mail (e.g. user did not answer, line was busy, etc.). information that is used by the legacy PBX to turn on the message-waiting mechanism on a user's phone to let her know she has received a message.
The ShoreTel server, in return, sends MWI (Message Waiting Indicator)
18.9.2.6 Information Transferred via SMDI

The COM port is used to send call information between the ShoreTel system and the legacy voice mail system. The SMDI protocol transmits the following call information from the ShoreTel system to the legacy system:
Message desk number: 1-999 Logical Terminal number (terminal identifier): 1-9999 Call type (All, Busy, Direct, No Answer, Unknown)
286
Called party Calling party

The SMDI MWI protocol transmits the following information from the legacy voice mail system to the ShoreTel system:
Message waiting indication control Extension On/Off indication
18.9.3 Configuring Legacy Voice Mail Integration Using SMDI

As mentioned before, there are two modes of operation with respect to integrating a ShoreTel system and a legacy system:
External Voice Mail Configuration - In this configuration, the legacy
system provides voice mail services while the ShoreTel system acts as PBX for users.
system provides voice mail services while the legacy system acts as a PBX for users. The former of these two operational modes (External voice mail) is discussed below, while the procedure for the latter configuration (ShoreTel voice mail) follows in "Configuring ShoreTel Voice Mail Integration Using SMDI" section on page 293. To integrate a legacy voice mail system with ShoreTel, you need to perform the following basic tasks:
ShoreTel Voice Mail Configuration - In this configuration, the ShoreTel
Configure the servers COM port for SMDI connections to the legacy system. Configure interface options from ShoreTel Director. Create a user group for users with access to the integration extensions. 18.9.3.1 COM Port Setup
To establish the SMDI link between the ShoreTel server and the legacy voice mail system, connect one end of a DB-9 serial cable to the COM port on the ShoreTel server and the other end of the cable to a COM port on the legacy voice mail server. The COM port settings on the ShoreTel server must match the settings of the COM port on the legacy voice mail server. Obtain the legacy voice mail COM port settings from the legacy voice mail servers administration guide or from your system integration manager. You need the following information:
Baud rate Data bits Parity Stop bits Flow control
ShoreTel 13.1
287
To configure COM port communication: Step 1 From the Start menu on the Windows server connected to the legacy voice mail server, select Settings, and then Control Panel. Step 2 In the Control Panel, open the Computer Management folder. Step 3 Open the Device Manager. Step 4 From the right pane in the window, expand the item Ports (COM & LTP). Step 5 Right-click the COM port used to connect the ShoreTel server and legacy voice mail system, and select Properties from the menu. Ask your server administrator if you need help in determining the correct COM port. Step 6 In the Properties window, enter the settings for the legacy voice mail server COM port. Step 7 Click OK to save the settings. Step 8 In ShoreTel Director, open the Server edit page. Step 9 Enter the COM port the server will use for SMDI communications in the COM Port (1-10) text box. Step 10 Click Save. The ShoreTel system will not read the COM port settings until you have saved the changes to the Server edit page or until the voice mail service is restarted.
18.9.3.2 Analog Trunk Port Setup

The ShoreTel system sends calls to the legacy voice mail server over analog trunks connecting the two systems. The extensions are on the ShoreTel side, and the legacy voice mail system is the trunk side. The ShoreTel system sends calls made to these extensions to the legacy voice mail system when voice mail is needed. Before the call is sent, the SMDI protocol sends information about the call to the legacy voice mail system via the SMDI serial link. This allows the legacy voice mail system to handle the call correctly. To configure the extensions, you need to do the following:
Create a list of the extensions and include the Logical Terminal Number for
each extension.
Configure the extensions with a new dial number (DN) type and marked as
private users with no mail box.
Assign a physical port to each extension in Director. Configure the extensions to

forward to the Backup Auto Attendant on no answer or busy.
18.9.3.3 Configuring the ShoreTel Server

Follow these steps to set up communication between ShoreTel Director and the legacy voice mail server. To set up ShoreTel Director to communicate with the legacy voice mail server: Step 1 From ShoreTel Director, click Servers in the navigation frame.
288
Step 2 Select the server connected to the legacy voice mail system. Step 3 In the Edit Server page under Simplified Message Desk Interface, change the settings as follows: Step a Make sure that the ShoreTel as PBX box is selected. Step b In the COM Port field, enter the port on the server that will be used for SMDI communication. Step c In the Message Desk Number field, enter the Message Desk number (range is 1-999, with a default of 1). This number identifies a specific voice mail system and must be set to the value the voice mail system expects. In configurations where a number of SMDI links are daisy chained together, this value is used to allow each system to known what data belongs to it. Since most systems use only one SMDI link, this parameter is normally set to 1. Step d In the Number of Digits field, enter the extension length. (range 2-32 digits). This value is used to determine how many digits the ShoreTel system sends in SMDI extension fields. This value needs to be set to the value the voice mail system expects. The most common values are either 7 or 10. If the system extension length is less than the number of SMDI digits then the extension number will be padded. For example, if the ShoreTel system needs to send extension 456 and the number of SMDI digits is set to 7, extension 0000456 is sent. If no padding is desired, the number of digits should be set to 2. In the above example with the number of SMDI digits set to 2 only 456 will be sent. Step e In the Translation Table field, select a translation table. Translation tables are created in ShoreTel Director. If you are using a translation table, make sure the Use for Call Data and Use for MWI Data check boxes are selected. For more information on building translation tables, see the ShoreTel System Administration Guide. Step f Click Save.
18.9.3.4 Digit Translation

If ShoreTel system extensions and legacy voice mail system extensions differ in length, you need to create digit translation tables that map the ShoreTel extensions to legacy system extensions. The digit translation tables must be added as a group of named tables from the Voice Mail section of ShoreTel Director. For more information see the ShoreTel System Administration Guide. Table 18-2 shows a digit translation table mapping shorter ShoreTel extensions to longer legacy system extensions. For example, ShoreTel extensions in the range of 5xx will be in the 65xx range on the PBX, and the original digit 5 will be replaced by 65.
Table 18-2 Digit Translation Mapping
Extension Mapping ShoreTel 5xx 3xx 2xx Legacy 65xx 73xx 83xx
Digit Translation Table Original Digits 5 3 2 Replacement Digits 65 73 83
ShoreTel 13.1
289
Table 18-3 shows a digit translation table mapping longer ShoreTel extensions to shorter legacy system extensions. For example, ShoreTel extensions in the range of 75xx will be in sent. to extensions in the 3xx range on the legacy voice mail system, and the original digit 75 will be replaced by 3.
Table 18-3 Digit Translation Mapping
Extension Mapping ShoreTel 65 66xx 75xx Legacy 5xx 6xx 3xx
Digit Translation Table Original Digits 65 66 75 Replacement Digits 5 6 3
Figure 18-3 illustrates how digit translation functions between the ShoreTel server and legacy voice system.
Figure 18-3 Mixed Extension Length SMDI Integration
290
To create a digit translation table, follow the procedure below: Step 1 Launch ShoreTel Director and enter the user ID and password. Step 2 Click Administration > System Parameters. Step 3 Click Digit Translation Tables. Step 4 Click the New button. Step 5 Enter a name in the Name field and click Save to store your digit translation table. Step 6 Click the New button again to display the Digit Translation window (Figure 18-4).
Figure 18-4 Leave Original Digits blank to add a digit to all legacy extensions Next, you must select the digit translation mapping that you just created at the server. Step 7 Click on the Application Servers link and click on the name of the ShoreTel server that will be handling the digit translation. Step 8 In the Simplified Message Desk Interface section of the Application Servers window, select ShoreTel Voice Mail from the Mode drop-down menu. The Translation Table drop-down menu appears. Step 9 Click on the arrow-button and select the name of the digit translation table that you just created. Step 10 Select the Use for Call Data check box and Use for MWI Data check box by placing a check mark in each one (as shown below). Doing so allows for the digit translation to occur when:
Data about a call is transferred between the legacy and ShoreTel systems. Message Waiting Indicator information is transferred between the two
systems to notify the legacy PBX that a message was left on the ShoreTel voice mail.
ShoreTel 13.1
291
Step 11 By default, the Use Flash to Route Calls check box is enabled. Leave this as is. Note that this check box only appears when ShoreTel Voice Mail is selected in the Mode drop-down menu in the Simplified Message Desk Interface section of the window. If selected, calls sent to the ShoreTel Auto Attendant from the SMDI trunk group are automatically transferred to the dialed extension using flash. If not selected, calls will be routed using other lines. The extension length must be the same on each of the systems for the Transfer Using Flash feature to work as no translation is applied.
Figure 18-5
Enabling digit translation for MWI and call data, and flash routing
Step 12 Click the Save button to store your changes.
18.9.3.5 Setting Up the User Group in ShoreTel Director

Follow these steps to set up a user group for those users who will have their voice mail re-directed to the legacy voice mail system. To set up the user group: Step 1 Open ShoreTel Director. Step 2 From the navigation frame, click Users and then User Groups. Step 3 Select an existing user group or create a new user group.
292
Step 4 Change the Simplified Message Desk Interface Mode option to ShoreTel as PBX by selecting this setting from the drop-down menu. Step 5 Click Save.
18.9.4 Configuring ShoreTel Voice Mail Integration Using SMDI

As mentioned before, there are two modes of operation with respect to integrating a ShoreTel system and a legacy system:
External Voice Mail Configuration - In this configuration, the legacy
system provides voice mail services while the ShoreTel system acts as PBX for users.
system provides voice mail services while the legacy system acts as a PBX for users. The former of these two operational modes (External voice mail) is discussed in "Configuring Legacy Voice Mail Integration Using SMDI" section on page 287. The procedure for the latter configuration (ShoreTel voice mail) follows. Configuring the ShoreTel Voice Mail Configuration consists of the following major tasks:
ShoreTel Voice Mail Configuration - In this configuration, the ShoreTel
Creating a Trunk Group Creating Trunks Configuring the ShoreTel Server for SMDI Creating a User Group Adding an Individual User Configuring the Serial Connection Configuring Digit Translation Tables PBX link 18.9.4.1 Creating a Trunk Group
One of the first tasks involved in configuring SMDI is to create a trunk group. The trunk group is used to manage the individual trunk lines between the ShoreTel Voice Switch and the legacy PBX. Instructions for creating the trunk group are provided below. For additional details on setting up trunk groups, refer to the ShoreTel System Administration Guide. To create a trunk group for SMDI trunks, follow the procedure below: Step 1 Launch ShoreTel Director and enter the user ID and password. Step 2 Click on the Administration link to expand the list (if it has not already been expanded). Step 3 Click on the Trunks link to expand the list. Step 4 Click on the Trunk Groups link to display the Trunk Groups window. Step 5 Select the trunk group site, and select Analog Loop Start for the type. Then click the Go link.
ShoreTel 13.1 293
Step 6 Enter a name for the trunk group in the Name field, as shown below.
Figure 18-6 Creating a trunk group Step 7 Enter a voice mail extension in the Inbound Destination field to direct inbound calls to the ShoreTel Auto Attendant system. Step 8 Click the Save button to store your changes.
18.9.4.2 Creating Trunks

After creating the trunk group, the next step is to create one or more trunk lines representing each data connection between the ShoreTel Voice Switch and the legacy PBX. The lines between the PBX and ShoreTel voice mail must be trunk lines with ShoreTel being the trunk side and the PBX being the extension side, (i.e. calls leaving the PBX for the voice mail system will leave on extensions). The PBX-tovoice mail connection might also be a T1 trunk that uses a channel bank to provide extensions to the legacy PBX. To create a trunk line, follow the procedure below: Step 1 With ShoreTel Director still open, click on the Trunks link to expand the list. Step 2 Click on the Individual Trunks link. Step 3 Select the trunk line site (i.e. Headquarters or Remote) from the drop-down menu, and use the drop-down menu to find and select the name of the trunk group you just created. Step 4 Click the Go link to display the Edit Trunk window, similar to the one shown below.
294
Figure 18-7 Creating a trunk line Step 5 In the Number field, enter the Logical Terminal Number. This value can range from 1 to 9999. For many systems the extension number of the port is used. The Logical Terminal Number identifies the port the PBX will use to send the call to the ShoreTel voice mail system. It is very important that the LTN match what the PBX will send. You must check with your PBX vendor to determine what will be sent. Step 6 Click the Save button to store your changes.
18.9.4.3 Configuring the ShoreTel Server for SMDI

After creating the trunk lines, you will configure the ShoreTel voice mail server. Configuration involves setting up the various SMDI parameters. To configure the ShoreTel voice mail server for SMDI operations, follow the procedure below: Step 1 With ShoreTel Director still open, click on the Application Servers link. Step 2 Click on the name of the server (Headquarters or Remote) that will be acting as the voice mail server for the legacy PBX. Step 3 In the Simplified Message Desk Interface section of the Application Servers window, click on the drop-down menu and select ShoreTel Voice Mail. A new set of fields and menus related to SMDI appear.
ShoreTel 13.1
295
Figure 18-8 Configuring ShoreTel voice mail server Step 4 In the Trunk Group drop-down menu, select the name of the SMDI trunk group that you created earlier. This tells the server the name of the trunk group from which it should expect to receive voice mail calls. Step 5 In the COM Port field, enter the numerical value (from 1-10) that corresponds to the serial port of the ShoreTel server where you will be connecting the serial port. (This serial port will be used to route out-of-band SMDI signaling information between the PBX link device and the ShoreTel server.) Step 6 The Message Desk Number, which has a range of 1-999, is optional and can be set to the default value of 1. Check with the vendor for this value. The Message Desk Number is used to indicate a specific system in situations where a number of SMDI links have been daisy-chained together. This value allows each system to known which data belongs to it. In most case this parameter is set to 1, since only one system will be using the SMDI link. Step 7 The Number of Digits field, which has a range of 2-32, is optional. This value determines how many digits the ShoreTel system will send in SMDI extension fields. This value needs to be set to the value the voice mail system expects. The most common values are either 7 or 10. If the system extension length is less than the number of SMDI digits, then the extension number will be padded. For example, if the ShoreTel system needs to send extension 456 and the number of SMDI digits is set to 7, extension 0000456 will be sent. If no padding is desired the number of
296
digits should be set to 2. In the above example with the number of SMDI digits set to 2 only 456 will be sent. Step 8 The translation table is optional and can be left as is for now. We will be returning to the related topic of digit translation tables later. Step 9 Click the Save button to store your changes.
18.9.4.4 Creating a User Group

After setting up the ShoreTel voice mail server for SMDI, the next step is to add users to the system. You will create a user group, and in this user group you will specify that all members will use ShoreTel Voice Mail. Once this is done, then you will modify user profiles at the individual level. For now, we will talk about creating the user group. To create a user group for users on the legacy PBX system, follow the procedure below: Step 1 With ShoreTel Director still open, click on the Users link to expand the list. Step a Click on the User Groups link. Step b Click on the Add New link to display the User Groups window.
Figure 18-9 Creating a user group for legacy users Step 2 Enter a Name for the user group in the Name field. Step 3 In the Simplified Message Desk Interface Mode drop-down window, select ShoreTel Voice Mail from the list.
ShoreTel 13.1 297
Step 4 Click the Save button to store your changes.
18.9.4.5 Adding an Individual User

After creating the user group, you can create user profiles for the legacy PBX users. To do so, follow the procedure below: Step 1 With ShoreTel Director still open, click on the Users link to expand the list. Step 2 Click on the Individual Users link. Step 3 In the Add new user at site field, select the server where you configured the ShoreTel voice mail for the PBX link device. Step 4 Click the Go link to display the Edit User window, shown below.
Figure 18-10 Creating a user record for a legacy user Step 5 Enter a name for the user in the First Name and Last Name fields. Step 6 In the License Type drop-down menu, click on the arrow-button and select Mailbox-Only. The user is located on the legacy system and thus, he or she does not require a ShoreTel extension. Step 7 In the User Group drop-down menu, click on the arrow-button and find and select the name of the user group you just created. Step 8 Click the Save button to store your changes.
298
18.9.4.6 Configuring the Serial Connection

The ShoreTel voice mail system will only support one serial link per application server. To support another legacy PBX, you will need another ShoreTel distributed application server. A serial cable (i.e. null modem) should be used to connect the legacy PBX to one of the COM ports of the ShoreTel server. Note that the ShoreTel system will extract the serial port settings, such as baud rate and parity bit values, from the Windows COM port settings. These settings can be verified by following the procedure below: Step 1 Right-click My Computer. Step 2 Select Manage. Step 3 Select Device Manager. Step 4 Left-click on Ports (COM & LPT). Step 5 Right-click Communications Port (COM1) and select Properties. Step 6 Left-click on the Port Settings tab. Step 7 Verify that the settings match those suggested by the documentation that came with your legacy PBX device.
18.9.4.7 PBX
Table 18-4 Supported PBXs
Manufacturer Nortel Avaya Mitel
Model
Meridian 1 Nortel Norstar System 75/85 Definity SX50 SX200 SX2000
Siemens NEC
300S NEAX
18.9.4.8 PBX link

A PBXLink device may be needed to provide SMDI services for a legacy PBX that does not offer support for SMDI. The PBXLink devices, manufactured by CTL, provides integration services to allow certain digital PBXs to interface seamlessly with a Voice Messaging System. The PBXLink connects to the PBX using a digital telephone line and to the Voice Messaging System using an RS-232 link. The PBXLink uses information appearing on the emulated digital set to determine the original source and destination of the calls being forwarded to the voice mail system. This information is then communicated to the voice mail system on an RS-232 serial link using the industry standard Centrex SMDI protocol. The PBXLink is compatible with SMDI-compatible voice mail systems. When using SMDI, ShoreTel voice mail configuration, the following features will not be supported:
Extension Assignment
ShoreTel 13.1 299
Setting call handling mode Setting agent state

The following features will be supported:
Recording greeting and name Setting TUI password Enable/disable envelope information Email voice message options Find Me Message functions including call back Message sending functions Workgroup ShoreTel voice mail Agents cannot be extensions in the legacy PBX System configuration Configuration parameters
18.10 System Requirements

The following are required on the ShoreTel system, or on the legacy PBX to enable the integration of the two systems:
ShoreTel system
ShoreTel Voice Switch that supports a T1 circuit.
Legacy PBX
T1 or PRI card for the PBX Available card slot and capacity for the added trunks Required software or licenses to support the desired trunk interface If PRI is used in the integration interface, the legacy PBX must emulate the CO or support Network Side PRI.
18.11 Connection Cable

18.11.1Special Considerations - Nortel PBX
When integrating with a Nortel Meridian PBX, a T1 connection must be used since the legacy system does not support Network Side PRI.
300
18.11.2Special Considerations - Avaya/Lucent PBX

Universal Dial Plan (UDP) Must be Active - This capability enables transparent dialing between the Avaya/Lucent PBX and the ShoreTel system. If this is not active, users on the PBX will either have to dial a trunk access code to reach the users on the ShoreTel system, or configure forwarding from an extension in the legacy system to the ShoreTel extension using the trunk access code and the extension. In some cases, this feature must be purchased separately from Avaya/Lucent.
18.12 Administration and Configuration

18.12.1Tie Trunk Configuration
The following summary describes the administration and configuration of the digital trunk for connecting the ShoreTel system to the legacy system.
18.12.2Services Summary
Before starting, a summary of the required configuration should be made based on the required services in the interface.
Table 18-5 Service Configuration Requirements
Desired Service Extension-to-Extension Calling
Required Configuration Enable inbound services on the trunk. Direct inbound calls using extension routing to the ShoreTel extensions. Enable off-system extensions. Define off-system extension range to match extensions on the remote PBX.
Inbound Trunks on Remote PBX
Enable inbound services on the trunk. Direct inbound calls using extension routing to the ShoreTel extensions. Outbound trunks on the remote PBX enable outbound services on the trunk. Configure any required access code for the trunk and the local area code for the trunks connected to the remote PBX. Configure the desired trunk services such as local, long distance, and so on. Configure the dialing format and any required digit sequences that are to be pre-pended to the dialed numbers. Users require trunk group access rights to use the trunk for outbound calls.
ShoreTel 13.1
301
Table 18-5
Service Configuration Requirements (Continued)
Desired Service Consolidated Long Distance
Required Configuration Enable outbound services on the trunk. Configure any required access code for the trunk and the local area code for the trunks connected to the remote PBX. Configure trunk services, such as long distance and international. Configure the dialing format and any required digit sequences that are to be pre-pended to the dialed numbers. Users require trunk group access rights to use the trunk for outbound calls.
18.13 Trunk Configuration

The following steps describe how to configure the trunk for integrating the legacy PBX and the ShoreTel system. Some steps are optional depending on the types of services desired as summarized above. To create a new trunk group Step 1 In the ShoreTel Director, select Trunk Groups from the navigation frame to open the Trunk Groups list page. Step 2 Select the site where the trunk will be integrated and the type of trunk to configure - Digital Wink Start for T1 or PRI for PRI - and select Go. The new trunk group is created and the Trunk Group Edit page appears. Step 3 Click Save to store the trunk group configuration changes. To configure inbound services with extension routing Step 1 In ShoreTel Director, open the Trunk Group edit page for the tie trunk. Step 2 Configure the number of digits received to match the number of digits sent by the remote PBX. This must match the extension length. Step 3 Enable Extension Routing by checking the box. This directs all the received calls to the configured ShoreTel extension that matches the received DNIS digits. Step 4 Select a Destination to provide a back-up when the received digits do not match an extension in the ShoreTel system. Step 5 Click Save to save the trunk group configuration. To configure off-system extensions Step 1 In ShoreTel Director, open the Trunk Group edit page for the tie trunk. Step 2 Select the Edit button by the off-system Extensions. The Off Systems Extension Range dialog is displayed. Step 3 Click New and define the extension ranges for the extension off the remote PBX.
302
Step 4 Click Save to save the trunk group configuration. To configure outbound call routing (via the remote PBX) Step 1 In ShoreTel Director, open the Trunk Group edit Page for the tie trunk. Step 2 Enable outbound services by selecting the Outbound check box. Step 3 Configure the access code and areas codes for the trunk to match the PSTN connection of the remote PBX. Step 4 Select the desired trunk services to match the services provided via the remote PBX. Step 5 Select the desired Trunk Digit Manipulations to match the tie trunk and the required dialing for the PSTN connection to your legacy PBX. Step 6 As needed, configure the local prefixes and pre-pend digits to match the tie trunk and the required dialing for the PSTN connection to your legacy PBX. For additional information on trunk configuration and information on configuration options, refer to the ShoreTel System Administration Guide.
ShoreTel 13.1
303
304
Chapter 19
Cut-Over
This chapter provides the requirements and other information for implementing the cut-over from your existing telephone system to the ShoreTel system. The topics discussed in this chapter include:
Cut-Over Requirements on page 305 Cut-Over Implementation on page 306 Cut-Over Worksheet on page 308
19.1 Cut-Over Requirements

As cut-over approaches, you should review and confirm your plan, assemble the cutover tools, and line up resources to support the cut-over.
19.1.1 Cut-Over Worksheet

The cut-over worksheet is used by the installer during the cut-over to move all endusers from the old system to the new. It is extremely important that the cut-over worksheet be prepared before the cut-over begins. You can use the cut-over worksheet at the end of this chapter to document all new and existing connections. A soft copy of this form is available in a planning and installation workbook from ShoreTel. Make copies as necessary. Use a pencil when preparing the cut-over worksheets, to allow for changes that may occur during the cut-over.
19.1.2 New Trunks

New trunks should be installed before cut-over. This allows time for them to be terminated, configured, and tested with the ShoreTel system.
19.1.3 Cut-Over Coverage

There are two aspects to cut-over coverage:
The team involved with planning the ShoreTel system must be on site before,
during, and after cut-over.
Appropriate coverage must be scheduled to monitor the newly installed
ShoreTel system for errors and last-minute configuration changes, and to help end-users with any questions they might have. ShoreTel recommends that you have support personnel on site before the first users arrive, to ensure that the system is functional and that telephone calls are processed properly.
ShoreTel 13.1
305
Chapter 19: Cut-Over
19.2 Cut-Over Implementation

Once planning is completed, it is time to bring the ShoreTel system into service. Use the checklists in this section to implement the cut-over, starting with the top-level checklist below. Table 19-1 Description Complete the tasks listed on the basic cut-over checklist. Cut-over and test all trunks. Cut-over and test the remaining devices (telephone, fax machines, modems, and so on). Confirm the cut-over coverage. Cutover Implementation Checklist Complete d
19.2.1 Basic Cut-Over Checklist

Table 19-2 Description Secure the telephone companys contact names, telephone numbers, and pager numbers for testing. Set up a command center to support cut-over activities. Ensure that copies of the floor plans and cut-over worksheets are available. Secure access to building and office areas that require ShoreTel voice switch telephones. Ensure that a telephone is installed next to the ShoreTel voice switch for testing. Ensure that music-on-hold is installed and tested. Record and test the auto-attendant greeting for on-hours and offhours. Test all telephones. Test paging and night bell features, if applicable. Basic Cut-Over Checklist Completed
19.2.2 Trunking Cut-Over

For existing trunking, use the cut-over worksheets to identify the trunks that are used from the old system (if applicable), and terminate them on the voice switches. Use a test telephone to dial in and out of each trunk, verify that it routes to the correct location, and listen closely to the voice quality. When preparing new trunks for installation, use the following checklist. When all of the trunks have been tested, have the telephone companys tester open the trunk group, and allow the callers to use the new trunks.
306
Table 19-3 Description
Trunking Cut-Over Checklist Complete d
Identify the new trunks. Terminate the new trunks on the ShoreTel voice switches. Contact the telephone companys tester, and test each trunk (one at a time). Agree on the specific trunk that is being tested. Have the tester dial in on the new trunk. Answer the incoming call on a test telephone. Observe overall voice quality. Go through this checklist until all trunks are tested.
19.2.3 Cut-Over of Remaining Devices

Use the following checklist to test each new end-user device that is being installed. Table 19-4 Description Place an internal call from the new device. Place an external call from the new device. If applicable, place a DID call. If the device is for a user with voice mail, leave a welcome message similar to the following: This is <your_name> from <company_ name>. Welcome to your new, revolutionary, IP-based communications system. You will find the following materials on your desk... Leave a user guide on the users desk. This provides information about the ShoreTel systems commonly used features as well as general system information. Remaining Devices Cut-over List Complete d
19.2.4 Cut-Over Coverage

It is recommended that the cut-over team arrive on site before the beginning of the next business day after cut-over, to answer questions from end-users as they begin to use the ShoreTel system.
ShoreTel 13.1
307
19.3 Cut-Over Worksheet

Table 19-5 Name Extension/ DID Cut-Over Worksheet ShoreTel Port # Patch Panel # IDF # Station Cable #
308
Table 19-5 Name Extension/ DID
Cut-Over Worksheet (Continued) ShoreTel Port # Patch Panel # IDF # Station Cable #
ShoreTel 13.1
309
Table 19-5 Name Extension/ DID
Cut-Over Worksheet (Continued) ShoreTel Port # Patch Panel # IDF # Station Cable #
310
Appendix A
International Planning and Installation

This chapter provides information about voice switches, operating systems, and features that are supported when the ShoreTel system operates outside the United States of America. The topics in this appendix include:
Software and Feature Support on page 311 Language Packs on page 311 Analog Telephones, Tones, Cadences, and Impedances on page 314 Dialing Plan Considerations on page 314 Carrier Codes on page 315
A.1
Software and Feature Support

For information about our worldwide support for software and features, contact a ShoreTel Sales Partner or refer to the ShoreTel Country Availability Web page at: http://www.shoretel.com/international/
A.2
Language Packs
Language packs determine the language in the following parts of the system:
Voice prompts (Voice mail, Auto Attendant, system announcements) Telephone User Interface (telephone display and ShoreTel Communicator
interface)
Online help for ShoreTel Communicator

Language pack availability affects the behavior of the system in the following areas:
Site Trunk Workgroup Auto Attendant Voice Mail User ShoreTel Communicator
ShoreTel 13.1 311
Appendix A: International Planning and Installation
Director panels that program language options include:
Edit Site panel: The Edit Site panel, shown in Figure A-1, specifies the language
pack used by the Backup Auto-Attendant (BAA). To access the Edit Site panel, select Administration > Site from the main menu, then click on the name of the desired site.
Figure A-1
Language set at Site level
Workgroup panel: The Workgroup panel, shown in Figure A-2, specifies the
language that the system uses for playing prompts to inbound callers. To access the Edit Workgroup panel, select Administration > Workgroups from the main menu, then click on the name of the desired site.
Figure A-2
Language set at Workgroup level
Edit Trunk Group panel: The Edit Trunk Group panel, shown in Figure A-3,
specifies the language prompts are played to incoming callers. To access the Edit Trunk Group panel, select Administration > Trunks > Trunk Groups from the main menu, then click on the name of the desired trunk group.
312
Figure A-3
Language set at Trunk Group level
Edit User panel: The Edit User panel, shown in Figure A-4, specifies the
language prompts used for the users telephone interface and voicemail prompts. To access the Edit User panel, select Administration > Users > Individual Users from the main menu, then click on the name of the desired user.
Figure A-4
Language set at User level
In language priority, a workgroup language overrides the language associated with a trunk, which in turn overrides the language associated with an individual user.
ShoreTel 13.1 313
A.3
Analog Telephones, Tones, Cadences, and Impedances

For all supported countries, standard analog telephones are available on a percountry basis. The main difference between telephones in different countries is the line impedance. The ShoreTel Distributed Call Control software will provide the appropriate impedance required for each supported country. Tones, cadences, and impedance requirements are matched on a per-country basis.
A.4
Dialing Plan Considerations

When planning a global voice network, remember that the ShoreTel system is a single image system and that you must consider all countries and locations when designing the international dialing plan. The ShoreTel system can match the dialing plan requirements of the local service provider for the supported countries.
A.4.1 A.4.2
Single-Extension Plan
Across the global voice network, all extensions must be unique and cannot overlap.
Trunk Access Codes

Across the global voice network, when you configure trunk access codes, that portion of the dialing plan will be reserved so you will be sacrificing one digit. Typically in the US, customers use 9 as a trunk access code. Internationally, those in the EMEA, for instance, often use 0 as a trunk access code. The following are some things to consider when you create a trunk access code:
Using two different trunk access codes will limit users to only being able to
access certain trunk groups.
If you use a single trunk access code, some users will need to be retrained. Alternatively, 8 could be defined for the trunk access code globally.
ShoreTel recommends proper identification from the beginning. The trunk access code should not be changed later.
A.4.3
Operator Digit
The leading digit of 0 is typically reserved for dialing the operator in the US. The operator digit is configurable. Similarly, EMEA customers are accustomed to dialing 9 to reach the operator. ShoreTel recommends choosing a single digit for the trunk access code and selecting a different single digit for the operator.
A.4.4
Emergency Numbers
The ShoreTel system allows dialing of emergency numbers with and without trunk access codes. For this reason, you should architect the dialing plan for this feature.
911 is used in the US. 112 is used in Europe and other countries. Check for other countries and regions for local requirements.
314
Thus, extensions should not begin with 0, 1, or 9 to make use of this feature. Each site can have a maximum of ten emergency numbers to accommodate locations where multiple emergency service numbers are required. For more information about emergency numbers, see the appendix in the ShoreTel System Administration Guide about emergency 911 operations.
A.4.5
DID Numbers
DID numbers are related to the trunk group in which they are associated. You should strive to match the last digits of the DID number to the users extension number.
A.5
Carrier Codes
Certain countries provide an option for requiring one or two numbers that the ShoreTel user must press after the trunk access code (usually a 9 or an 8) and before an area code or another nations country code. The purpose of this option is to get the lowest-cost route for long-distance or international calls. When the user presses this code, the call goes out a trunk to a carrier that the system administrator has specified. If the user makes a long-distance or international call without this code, the ShoreTel system selects the trunk. This section defines the carrier codes that certain countries use and lists the numbers that the user presses to utilize the associated trunks. The two definitions that readers need for this description are as follows: Carrier code: This number specifies a carrier. The system administrator assigns this code to a trunk group so that calls go to that carrier when the user prepends the country code to a phone number. System administrators in applicable countries must know the code for the carriers they want to give preferential business. The user does not see this carrier code. Country code: This country code is a nation-wide number that a user presses to direct long-distance or international calls to the carrier that the carrier code specifies. This country code is not the number that callers from outside a country use to reach the country. For example, the country code that callers outside of Singapore use to reach that country is 65, but from inside Singapore, the country code that a caller presses to direct an international call to a specific carrier is 01. Using the Singapore example: if a trunk access code is 9 and the ShoreTel user with international calling permission initiates a call to India, the number sequence is as follows: 9 01 91 <telephone number> As of the current release, six countries use this code function. Table A-1 lists the carrier code and application for the countries that use them.
Table A-1 Carrier Code by Country
Code 55 1 2
Country and Application Brazil, all calls Hong Kong, international calls South Korea, international calls
ShoreTel 13.1
315
Code 01 2 1
Country and Application Singapore, international calls Taiwan, international calls Thailand, international calls
316
Appendix B
Regulatory and Safety Information

This chapter provides detailed information regarding compliance of the ShoreTel system with the international regulatory bodies. The chapter also addresses safety as it relates to installation, operation, and regular use of the ShoreTel system. The topics discussed in this appendix include:
Agency Approvals on page 317 EMC Compliance Statements (SG-8/12/24 and T1) on page 318 Safety on page 319
B.1
Agency Approvals
Table B-1 Category EMC Agency Approvals Regulatory Compliance / Agency Approval EN 55022 Class A (SG-12, SG-8, SG-24, SG-T1) EN 55022 Class B/Class A (SG-E1) FCC Part 15 Class A (SG-12, SG-8, SG-24, SG-T1) EN 55024:1998 including amendments A1:2001 and A2:2003 (SG-24, SG-E1) Electrical Safety FCC Part 68 for SG-24, SG-T1 IEC 60950:1999 3rd ed. SG-8, SG-12, SG-24, SG-T1, SG-E1 EN60950:2000 SG-8, SG-24, SG-T1, SG-E1 AS/NZ 60950:2000 SG-8, SG-24, SG-T1, SG-E1 UL60950 3rd ed. 2000 SG-8, SG-12, SG-24, SG-T1, SG-E1
ShoreTel 13.1
317
Appendix B: Regulatory and Safety Information
Table B-1 Category
Agency Approvals (Continued) Regulatory Compliance / Agency Approval ACA TS001-1997: SG-8, SG-24, SG-T1, SG-E1 FCC Part 68: SG-8, SG-12, SG-24
Telecom
ETSI TS 103 021-1 V1.1 (2003-08) SG-8, SG-12, SG-24 ETSI TS 103 021-2 V1.2 (2003-09) SG-8, SG-12, SG-24 ETSI TS 103 021-3 V1.2 (2003-09) SG-8, SG-12, SG-24 ETSI TBR4 Nov. 1995 SG-E1 ETSI TBR4/A1 Dec. 1997 SG-E1 ETSI TS 102 119 V.1.1.1 Aug. 2001 SG-E1 Bellcore GR-499-CORE, issue 2, Dec. 1998 SG-T1
Telecom Homologation
NZ PTC 220/06/016 through PTC 220/06/023 SG-8, SG-12, SG-24, SG-T1, SG-E1 and IP 560 Phones
B.2
B.2.1
EMC Compliance Statements (SG-8/12/24 and T1)

United States
This equipment has been tested and found to comply with the limits for Class A digital devices, 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 a 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. Changes or modifications to this equipment not expressly approved by the party responsible for compliance to FCC part 15 could void the user's authority to operate the equipment.
318
B.2.2
European Union
This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.
B.2.3
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.
B.2.4
Restricted Access Location

This product is intended to be installed only in a RESTRICTED ACCESS LOCATION. A RESTRICTED ACCESS LOCATION is defined as an area where access can be gained only by SERVICE PERSONNEL who have been instructed about the reasons for the restrictions applied to the location and about any precautions that must be taken. RESTRICTED ACCESS LOCATIONS can be accessed only through the use of a tool or lock and key or other means of security, and are controlled by the authority responsible for the location. SERVICE PERSONNEL are defined as persons having appropriate technical training and experience necessary to be aware of hazards to which they are exposed in performing a task and of measures to minimize the danger to themselves or other persons.
B.2.5
WEEE Information
In accordance with the requirements of council directive 2002/96/EC on Waste of Electrical and Electronic Equipment (WEEE), ensure that at end-of-life you separate this product from other waste and scrap and deliver to the WEEE collection system in your country for recycling.
B.3
Safety
The following information is included in this publication for the use and safety of installation and maintenance personnel. WARNINGThis equipment uses a three-conductor power cord with safety grounding conductor. Ensure that this is connected to an AC outlet with provision for grounding. Ensure the permanent earthing protector is connected as directed in the installation instructions. Consult a licensed electrician if necessary.
B.3.1
Important Safety Instructions

Read all of the instructions before attempting to operate the equipment and
before connecting the power supply. shock, and injury to persons.
Always follow basic safety precautions to reduce the risk of fire, electrical To prevent fire or shock hazard, do not expose the unit to rain, moisture, or
install this product near water. Never spill liquid of any kind on this product.
319
ShoreTel 13.1
Never push objects of any kind into this product through openings, as they may
touch dangerous voltage points or short out parts, which could result in the risk of fire or electrical shock. servicing to qualified service personnel.
Do not open the cabinet, as there are high voltage components inside. Refer Do not attach the power supply cord to building surfaces. Do not allow
anything to rest on the power cord or allow the cord to be abused by persons walking on it. housing that are provided for ventilation.
To protect this equipment from overheating, do not block the openings in the
B.3.2
Electrical Safety
WARNINGDo not take chances with your life. Follow these guidelines carefully:
Observe all safety regulations and read the warnings, cautions, and notes posted
on the equipment.
Never assume that the power is turned off. Always check to ensure that a circuit
does not have power.
Connect all power before installing changes in systems or wiring. Use caution when installing or modifying telephone lines. Never install
telephone wiring during an electrical storm.
Never touch uninsulated telephone wires or terminals unless the telephone line
has been disconnected at the network interface. in order to minimize risk of fire.
Telephone connections to the unit should be made with number 26 AWG wire
320
Appendix C
Installing Communicator on Citrix XenApp and Windows Terminal Servers

You can install ShoreTel Communicator for Windows on Citrix XenApp and Windows terminal servers to provide ShoreTel Communicator functionality to terminal server clients. ShoreTel Communicator for Windows supports desktop and published modes in standard environments, but does not support isolation environments. This appendix describes how to install ShoreTel Communicator for Windows on Citrix XenApp and Windows terminal servers. For information on Citrix XenApp and Windows terminal servers, refer to the documentation from the manufacturer. The topics discussed in this appendix include:
XenApp Support Considerations on page 321 WTS Support Considerations on page 322 Installing ShoreTel Communicator on Citrix XenApp or WTS on page 323 Using Third-Party Applications with ShoreTel Communicator on a Citrix
Terminal Server on page 324
C.1
XenApp Support Considerations

This section provides information about best practices and restrictions when installing ShoreTel Communicator for Windows in a Citrix XenApp environment.
C.1.1
Citrix XenApp Environment Best Practices

ShoreTel recommends the following best practice guidelines for computers running ShoreTel on XenApp servers:
Use only Citrix-ready anti-virus software on XenApp servers. Run XenApp and ShoreTel servers on a Citrix-qualified server platform. Perform frequent defragmentation of the XenApp server disk. Co-locate the Citrix/WTS server with the headquarters server or the DVS
servicing the ShoreTel Communicator clients.
ShoreTel 13.1 321
Planning and Installation Guide Appendix C: Installing Communicator on Citrix XenApp and Windows Terminal
C.1.2
Citrix XenApp Restrictions

ShoreTel Communicator for Windows does not support the following XenApp operations:
Streaming mode. Application Isolation Environment (AIE). Virtual deployment.

The following ShoreTel Communicator for Windows features are not supported in the Citrix XenApp environment:
Automatic import of Microsoft Outlook contacts. Voicemail integration in Microsoft Outlook. Call handling mode integration in Microsoft Outlook. Conferencing integration in Microsoft Outlook. SoftPhone. Video. Presenter for Java must be used because ShoreTel does not support Presenter for
Windows (ShoreTel Conferencing). Right).
Docking in Seamless Mode (Docked Top, Docked Bottom, Docked Left, Docked
NOTE Microsoft Outlook integration may work when properly configured on the XenApp/terminal server side, but this configuration is not officially supported by ShoreTel.
C.2
WTS Support Considerations

This section provides information about restrictions when installing ShoreTel Communicator for Windows in a WTS environment.
C.2.1
WTS Restrictions
The following ShoreTel Communicator for Windows features are not supported in the WTS environment:
Automatic import of Microsoft Outlook contacts. Voicemail integration in Microsoft Outlook. Call handling mode integration in Microsoft Outlook. Conferencing integration in Microsoft Outlook. SoftPhone. Video.
322
Appendix C: Installing Communicator on Citrix XenApp and Windows Terminal Servers Planning and Installation
C.3
Installing ShoreTel Communicator on Citrix XenApp or WTS

ShoreTel 13.1 supports ShoreTel Communicator on the following platforms:
XenApp 5.0 on Windows Server 2008 for Terminal Licensing, 32-bit, SP2
(Isolation mode is not supported). mode is not supported).
XenApp 6.0 on Windows Server 2008 for Terminal Licensing, R2 (Isolation Windows Server 2008 for Terminal Licensing, 32-bit, SP2 (Enterprise). Windows Server 2008 for Terminal Licensing, 64-bit, SP2 (non R2) (Standard
and Enterprise).
Windows Server 2008 for Terminal Licensing, 64-bit, R2.
C.3.1
Preliminary Steps for Upgrading ShoreTel Communicator on 64-bit Platforms

ShoreTel Communicator for Windows requires .NET Framework version 3.5 or higher on 64-bit Windows terminal server platforms. ShoreTel does not ship the .NET Framework as part of the software package. The first time the .NET Framework is required, Communicator prompts you to download and save it to a file on the ShoreTel server. NOTE If the .NET Framework is not installed on the target terminal server and the .NET Framework file in the ShoreTel folder is empty, the target terminal server must be able to access the Internet so that the .NET Framework can be downloaded during the Communicator installation process.
C.3.2
Installing ShoreTel Communicator for Windows on a Terminal Server

NOTE Administrative rights on the terminal server are required in order to install ShoreTel Communicator for Windows. Step 1 Open a browser on the terminal server. Step 2 Enter the following URL:
http://<ShoreTel_server_name>/ShoreWareresources/clientinstall
ShoreTel_server_name is the name or IP address of the ShoreTel headquarters server or DVS that manages the client software on the terminal server. The ShoreTel Communicator Install page for Windows computers is opened (Figure C-1). Step 3 Review the information on this page, then click Click Here to Install ShoreTel Communicator. The download process starts, and the InstallShield Wizard is launched. Step 4 Follow the prompts to install Communicator.
ShoreTel 13.1
323
When installation is complete, the terminal server is restarted automatically. The ShoreTel Communicator is opened on the desktop. NOTE The installation process places files in the following folder by default: C:\Program Files (x86).
Figure C-1
ShoreTel Communicator Install Page for Windows
C.4
Using Third-Party Applications with ShoreTel Communicator on a Citrix Terminal Server

Third-party applications can interact with ShoreTel Communicator for Windows on a Citrix terminal server only if the terminal server is running the ShoreTel Telephony Interface (STI). This section describes how to set up the Citrix terminal server to use third-party applications with ShoreTel Communicator for Windows.
C.4.1
Installing ShoreTel Telephony Interface (STI) on a Citrix Terminal Server

Step 1 Install (or upgrade) ShoreTel Communicator. Step 2 Install ShoreTel Telephony Interface: Step a Launch Windows Explorer. Step b Enter the following URL:
http://serverIP/shorewareresources/shoreteltelephonyinterface
324
Appendix C: Installing Communicator on Citrix XenApp and Windows Terminal Servers Planning and Installation
The ShoreTel Telephony Interface Install site is opened. Step c Click the link to install the ShoreTel Telephony Interface (download and install the interface on the client computer). Step 3 Reboot the terminal server. Step 4 Launch the Control Panel. Step 5 Select Phone and Modem Options. The Phone and Modem Options dialog is opened. NOTE If this is the first time this option is activated, another dialog box is opened first, requiring outbound dialing information. Step 6 Click Advanced. Step 7 Remove all ShoreTel providers. Step 8 Click OK. The changes are saved and the dialog is closed. Step 9 On the terminal server, click Start > Run. Step 10Type cmd, then click OK. The Command Prompt is opened. Step 11 Navigate to the directory where the ShoreTel Telephony Interface is installed (\Program Files\ShoreTel\ShoreTel 3rd Party). Step 12At the prompt, type the following:
TSPinstall -i StServer HQ servername
HQ servername is the hostname or IP address of your ShoreTel HQ server. The TSPinstall utility is launched (Figure C-2). Step 13Close the cmd prompt and reboot the server. Step 14Verify that multiple lines are provided for the ShoreTel Telephony Interface: Step a On the terminal server, navigate to the Phone and Modem Options Advanced tab. Step b In the Provider list, select the ShoreTel provider, then click Configure. The ShoreTel Remote TSP dialog is opened (Figure C-3). If the ShoreTel Remote TAPI Service Provider is connected to the ShoreTel Server, the fields are populated automatically. If an error message is posted in Provider Status and Server Name and Login are blank, the ShoreTel Remote TAPI Service Provider must be removed.
ShoreTel 13.1
325
To remove the provider: Go to the Control Panel and open Phone and Modem Options Advanced. Click ShoreTel Remote TAPI Service Provider. Click Remove.
Figure C-2
TSPInstall Command Line
Figure C-3
ShoreTel Remote TSP Dialog Box
326
Appendix D
Session Initiation Protocol

This chapter provides information about the Session Initiation Protocol (SIP). You should refer to this chapter for help in planning a SIP deployment on your ShoreTel system. NOTE Configuration steps and significant details for SIP exist in the Session Initiation Protocol chapter in the ShoreTel System Administration Guide. The topics discussed in this appendix include:
Overview on page 327 General SIP Comments on page 328
D.1
Overview
The protocol, which works at the application layer, allows users to initiate interactive sessions between any network devices that support the protocol. SIP is capable of initiating or terminating Internet telephony calls and other multimedia applications such as video or gaming. The protocol is based on a client-server model. With support for redirection services, networked users can initiate a call or receive a call, regardless of their physical location. In its networking negotiations SIP takes into account the following pieces of information:
The address of the end system The physical media The call recipient's acceptance to the invitation
The protocol then configures the parameters for the session and handles the call setup and tear-down. SIP allows two discrete ShoreTel systems to be integrated with any IP connection, without the need for physical tie trunking. (Note that care should be taken to make sure that the extension numbering plans in the two systems do not overlap, and that if they do overlap, translation tables need to be used to resolve conflicts.) In the current release of the ShoreTel system, the SIP trunks and SIP tie-trunks support the SIP capabilities. Like other trunk, the SIP trunk assignments are switches, so that SIP calls into and out of the ShoreTel system traverse these SIP trunks. However, up to five SIP trunks can be associated with one analog switch port, meaning that there will be no physical channel/port associated with each SIP trunk.
ShoreTel 13.1 327
Appendix D: Session Initiation Protocol
The SIP trunk is a logical trunk end point which only handles call control responsibilities. The media flows directly between the end-point SIP devices (i.e. call initiator and the call terminator), freeing the switch from the burden of controlling media flow.
D.2
D.2.1
General SIP Comments

Conferencing
Ports for MakeMe conferences must be available on the initiating side of a 3way conference call involving a SIP end-point.
MakeMe conference ports are needed even for 3-way conference. Note that
configuration of any Make Me conferencing support in Director requires a minimum of 4 available conference ports.
ShoreTel SIP trunks support from 4-way up to a maximum of 6-way
conferences. This conferencing relies on ShoreTels MakeMe capability. Endusers can set up MakeMe conference calls by using their ShoreTel Communicator. Like extensions with support of Media Gateway Control Protocol (MGCP), SIP extensions require permissions and a minimum of 4 MakeMe ports to set up MakeMe conference call.
An individual SIP trunk must be provisioned for each call to the SIP device
(including conference-in or transferred calls). Thus, static SIP trunks must be provisioned with additional trunks in line with the highest anticipated number of such calls.
D.2.2
DTMF
ShoreTel supports RFC2833 (DTMF) for users calling over SIP trunks regardless of the negotiated voice codec. ShoreTel can be configured to use SIP INFO for DTMF signaling in environments where out-of-band DTMF is needed but RFC 2833 is not applicable. SIP INFO for DTMF signaling is available on only SIP trunks.
D.2.3
Foreign Language Support

In addition to English, ShoreTel support other languages (for Caller Name,
Called Name, User Name, and so on) over SIP tie trunks and service provider trunks. Some third-party devices might not be able to display all of a languages characters.
D.2.4
General Feature Limitations

A file-based music-on-hold source shares its resources with the other voicemail
services on the switch/appliance. The maximum configurable streams usable by file-based MOH are: HQ/DVS: 250 90V/BRI90V: 9 50V: 5
328
The configured number of streams is the maximum number of connections used by file-based MOH, leaving the remaining streams available for other voicemail connections.
A music on hold (MOH) switch supports 15 streams of MOH, but some of these Three-way conference on a SIP trunk call uses Make Me conference ports. A
minimum of 3 Make Me ports must be configured to support 3-way conferencing.
can be used to fan out MOH to other trunk switches. If some MOH streams go to other switches, the actual number of MOH streams on SIP trunks is less than 15.
A SIP trunk can be a member of a 3-party conference but cannot initiate a 3way conference (unless the SIP device merges the media streams itself). (consultative transfers).
ShoreTel SIP supports basic transfers (blind transfers) and attended transfers In the current release, the following features are supported by SIP only if the
trunk has a SIP trunk profile with hairpinning and the trunk is on a half-width switch: Silent Coach Silent Monitor Barge-In Call recording
Silence detection on trunk-to-trunk transfers is not supported because it

requires a physical trunk.
Extension Assignment is limited using SIP trunks. Either DTMF over INFO Fax (and modem) redirection on SIP trunks is supported if T.38 is used.
must be used, or inthe absence of such supportthe features that use DTMF are not supported (including Accept call by pressing 1.)
D.2.5
Additional Configuration Considerations

Overlapping number plans are not allowed between two systems tied with SIP
trunks unless digit translation is used.
When translating digits between two ShoreTel systems tied with SIP trunks,
even system extensions like VM, AA should be properly translated.
Multiple trunks (SIP and non-SIP trunks) can be created or deleted at one time.
ShoreTel 13.1
329
330
Appendix E
Reverse Proxy Servers for ShoreTel Communicator on iPhone

ShoreTel Communicator for iPhone can communicate with the ShoreTel UC system via the cellular data network or WIFI. A VPN connection must be used unless the system uses a configured reverse proxy server. The data transmitted through the server is not encrypted by default. An option to configure secure communication using SSL is available, and requires an additional reverse proxy server. A VPN connection is not required in this configuration. To fully set up a reverse proxy you need an Apache server version 2.2 or higher, and an SSL certificate from a root certificate authority. The system supports a self-signed certificate, however, the users will receive a warning each time the application is launched. This is not recommended for production deployments. Topics discussed in this appendix include:
"Reverse Proxy Settings" on page 331 "Example Reverse Proxy Configuration for Apache 2.2 On a Linux Server" on page 333 "Example Reverse Proxy Configuration for Apache 2.2 On a Microsoft Windows Server" on page 337
E.1
Reverse Proxy Settings

Each ShoreTel user is associated with a ShoreTel HQ or DVS Server defined by the user's association to a site in Director. The server handles ShoreTel Communicator requests to perform telephony, voicemail, and other actions. In a reverse proxy configuration, a user must use the proxy configuration which will connect the user directly to his server. In the case where the user re-assigns his extension to a phone associated to a server different from the server associated with the proxy definition, Communicator for iPhone will not display call history. The reverse proxy maps public IPs/ports on specific paths with internal IPs/ports and paths. The data received by the Reverse Proxy is routed to the internal ShoreTel Services.
ShoreTel 13.1
331
Appendix E: Reverse Proxy Servers for ShoreTel Communicator on iPhone
Figure E-1
Reverse Proxy Data Routing with ShoreTel
Each user must provision ShoreTel Communicator for iPhone with the appropriate reverse proxy IP address/port. For example: User 1 is on HQ at 10.0.0.1 User 2 is on DVS at 10.0.0.2 Reverse proxy is 10.0.0.64 (64.0.0.1 internally) using ports 5500 and 5501 Reverse proxy for User 1 is on HQ could be configured by the administrator: 10.0.0.64:5500/authenticate mapped to 10.0.0.1:80 10.0.0.64:5500/cas mapped to 10.0.0.1:5447 10.0.0.64:5500/director2 mapped to 10.0.0.1:5449 Reverse proxy for User 2 is on DVS could be configured by the administrator: 10.0.0.64:5501/authenticate mapped to 10.0.0.2:80 10.0.0.64:5501/cas mapped to 10.0.0.2:5447 10.0.0.64:5501/director2 mapped to 10.0.0.2:5449 When setting up an account in ShoreTel Communicator, User 1 must use the reverse proxy connection: 10.0.0.64 port: 5500 and User 2 must use the reverse proxy connection: 10.0.0.64 port: 5501.
332
A single reverse proxy server can be configured to provide services for multiple ShoreTel Services.
Figure E-2
Reverse Proxy and Multiple Services
In all cases, the IT administrator must make sure that the reverse proxy can be accessed internally and externally. NOTE The reverse proxy configuration uses SSL. A valid SSL certificate signed by a root certificate authority, such as Verisign, must be installed on the reverse proxy server for communication over SSL to be secure.
E.2
Example Reverse Proxy Configuration for Apache 2.2 On a Linux Server

The following script example illustrates how to configure a Linux server to provide reverse proxy on port 5500 for connection to the HQ server at 10.0.0.1. Step 1 Modify httpd.conf to specify proxy port to be used for HTTP+SSL:
# # Listen: Allows # ports, instead # directive. # # Change this to # prevent Apache # Listen 5500
you to bind Apache to specific IP addresses and/or of the default. See also the <VirtualHost>
Listen on specific IP addresses as shown below to from glomming onto all bound IP addresses.
Step 2 Verify in httpd.conf that the following modules are enabled (uncommented):
LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule rewrite_module modules/mod_rewrite.so
ShoreTel 13.1
333
LoadModule ssl_module modules/mod_ssl.so
Step 3 Edit conf\extra\ httpd-vhosts.conf: Step 4

# # Use name-based virtual hosting. # NameVirtualHost *:5500 <VirtualHost *:5500> # necessary for rewriting RewriteEngine on # uncomment the logging for problem trace only # RewriteLog logs/ciproxy.localhost-rewrite.log # RewriteLogLevel 3 # NOTE the rewrite rules have a proxy redirect RewriteRule ^/theme/(.+)$ /director2/theme/$1 [P] RewriteRule ^/yui_2.7.0/(.+)$ /director2/yui_2.7.0/$1 [P] RewriteRule ^/js/(.+)$ /director2/js/$1 [P] ProxyPass /authenticate/ http://10.0.0.1/ ProxyPassReverse /authenticate/ http://10.0.0.1/ ProxyPass /cas/ http://10.0.0.1:5447/ ProxyPassReverse /cas/ http://10.0.0.1:5447/ ProxyPass /director2/ http://10.0.0.1:5449/ ProxyPassReverse /director2/ http://10.0.0.1:5449/ # These are Optional ErrorLog logs/ciproxy.localhost-error.log CustomLog logs/ciproxy.localhost-access.log combined # SSL Engine Switch: # Enable/Disable SSL AND PROXYING OF SSL for this virtual host. SSLEngine on SSLProxyEngine on # SSL Cipher Suite: # List the ciphers that the client is permitted to negotiate. # See the mod_ssl documentation for a complete list. SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL # Server Certificate: # Point SSLCertificateFile at a PEM encoded certificate. If # the certificate is encrypted, then you will be prompted for a # pass phrase. Note that a kill -HUP will prompt again. Keep # in mind that if you have both an RSA and a DSA certificate you # can configure both in parallel (to also allow the use of DSA # ciphers, etc.) #SSLCertificateFile conf/ssl.crt/server-dsa.crt SSLCertificateFile conf/ssl.crt/server.crt # # Server Private Key: If the key is not combined with the certificate, use this
334
# directive to point at the key file. Keep in mind that if # you've both a RSA and a DSA private key you can configure # both in parallel (to also allow the use of DSA ciphers, etc.) #SSLCertificateKeyFile conf/ssl.key/server-dsa.key SSLCertificateKeyFile conf/ssl.key/server.key # Server Certificate Chain: # Point SSLCertificateChainFile at a file containing the # concatenation of PEM encoded CA certificates which form the # certificate chain for the server certificate. Alternatively # the referenced file can be the same as SSLCertificateFile # when the CA certificates are directly appended to the server # certificate for convenience. #SSLCertificateChainFile conf/ssl.crt/server-ca.crt # Certificate Authority (CA): # Set the CA certificate verification path where to find CA # certificates for client authentication or alternatively one # huge file containing all of them (file must be PEM encoded) # Note: Inside SSLCACertificatePath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCACertificatePath conf/ssl.crt #SSLCACertificateFile conf/ssl.crt/ca-bundle.crt # Certificate Revocation Lists (CRL): # Set the CA revocation path where to find CA CRLs for client # authentication or alternatively one huge file containing all # of them (file must be PEM encoded) # Note: Inside SSLCARevocationPath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCARevocationPath conf/ssl.crl #SSLCARevocationFile conf/ssl.crl/ca-bundle.crl # Client Authentication (Type): # Client certificate verification type and depth. Types are # none, optional, require and optional_no_ca. Depth is a # number which specifies how deeply to verify the certificate # issuer chain before deciding the certificate is not valid. #SSLVerifyClient require #SSLVerifyDepth 10 # Access Control: # With SSLRequire you can do per-directory access control based # on arbitrary complex boolean expressions containing server # variable checks and other lookup directives. The syntax is a # mixture between C and Perl. See the mod_ssl documentation # for more details. #<Location /> #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \ # and %{SSL_CLIENT_S_DN_O} eq Snake Oil, Ltd. \ # and %{SSL_CLIENT_S_DN_OU} in {Staff, CA, Dev} \ # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \ # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \ # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/ #</Location> # # SSL Engine Options: Set various options for the SSL engine.
ShoreTel 13.1
335
# o FakeBasicAuth: # Translate the client X.509 into a Basic Authorisation. This means that # the standard Auth/DBMAuth methods can be used for access control. The # user name is the `one line' version of the client's X.509 certificate. # Note that no password is obtained from the user. Every entry in the user # file needs this password: `xxj31ZMTZzkVA'. # o ExportCertData: # This exports two additional environment variables: SSL_CLIENT_CERT and # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the # server (always existing) and the client (only existing when client # authentication is used). This can be used to import the certificates # into CGI scripts. # o StdEnvVars: # This exports the standard SSL/TLS related `SSL_*' environment variables. # Per default this exportation is switched off for performance reasons, # because the extraction step is an expensive operation and is usually # useless for serving static content. So one usually enables the # exportation for CGI and SSI requests only. # o StrictRequire: # This denies access when SSLRequireSSL or SSLRequire applied even # under a Satisfy any situation, i.e. when it applies access is denied # and no other module can change it. # o OptRenegotiate: # This enables optimized SSL connection renegotiation handling when SSL # directives are used in per-directory context. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire <FilesMatch \.(cgi|shtml|pl|asp|php)$> SSLOptions +StdEnvVars </FilesMatch> <Directory C:/xampp/cgi-bin> SSLOptions +StdEnvVars </Directory> # SSL Protocol Adjustments: # The safe and default but still SSL/TLS standard compliant shutdown # approach is that mod_ssl sends the close notify alert but doesn't wait for # the close notify alert from client. When you need a different shutdown # approach you can use one of the following variables: # o ssl-unclean-shutdown: # This forces an unclean shutdown when the connection is closed, i.e. no # SSL close notify alert is send or allowed to received. This violates # the SSL/TLS standard but is needed for some brain-dead browsers. Use # this when you receive I/O errors because of the standard approach where # mod_ssl sends the close notify alert. # o ssl-accurate-shutdown: # This forces an accurate shutdown when the connection is closed, i.e. a # SSL close notify alert is send and mod_ssl waits for the close notify # alert of the client. This is 100% SSL/TLS standard compliant, but in # practice often causes hanging connections with brain-dead browsers. Use # this only for browsers where you know that their SSL implementation # works correctly. # Notice: Most problems of broken clients are also related to the HTTP # keep-alive facility, so you usually additionally want to disable # keep-alive for those clients, too. Use variable nokeepalive for this. # Similarly, one has to force some clients to use HTTP/1.0 to workaround # their broken HTTP/1.1 implementation. Use variables downgrade-1.0 and # force-response-1.0 for this. BrowserMatch .*MSIE.* nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0 # Per-Server Logging:
336
# # #
The home of a custom SSL log file. Use this when you want a compact non-error SSL logfile on a virtual host basis. CustomLog logs/ssl_request.log %t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \%r\ %b
</VirtualHost>
E.3
Example Reverse Proxy Configuration for Apache 2.2 On a Microsoft Windows Server
This section provides information about setting up an Apache reverse proxy for the ShoreTel system. An example script setting up Apache 2.2 for reverse proxy operation on a Windows server is used. The example is created for the ShoreTel HQ server which uses port 5500 to connect to the reverse proxy server. The HQ server is assigned IP address 10.0.0.1.
E.3.1
Check List
Identify the machine name you will be using for the proxy server. This is the name that the certificate authority will use to create your SSL and your end users will use to setup their iPhones. Do not include hyphens or underscore in this name.
Contact ISP or Name Server to create the DNS record that points to the external IP given to the proxy server. If you cannot ping the address from the Internet, then you will not be able to get to the internal address.
Order your SSL from the certificate authority. You should ha a certificate file and a private file. Install Apache 2.2 on the server that you have prepared to be you proxy server. Copy the Httpd-vhosts.conf fild from the %Apache Software Foundation\Apache2.2\conf\extra folder and place it in the %\Apache Software foundation\Apache2.2\conf folder. This will be where the system will look for the required config files. Copy the certificate files that you get from the certificate authority to the % \Apache Software Foundation\Apache2.2\conf folder.
Follow the instructions given to prepare the httpd.conf and the httpd-vhosts.conf files.
E.3.2
About the Security Certificate

To use Apache for the reverse proxy, you must use an SSL certificate for Apache. You can order an SSL certificate from a root certificate authority. If the certificate authority does not provide a certificate for Apache (Apache SSL certificate have a different format than the Microsoft Windows SSL certificate), you can convert a Windows certificate to the Apache format.
ShoreTel 13.1
337
NOTE The certificate you purchase must match the machine name that you want the proxy to be. We highly recommend that you change the machine name to something that reflects this machine as your proxy because it will also be the name that your users enter on their iPhone for the server name (e.g.: proxy.yourdomain.com or gateway.yourdomain.com wherein the name of the server would be proxy or gateway which would also reflect the same exact name on the certificate that you order.) You must also contact your name server provider so that you can ping the machine name from the internet. Before you create a script, make sure that your SSL certificates conform to the Apache format. If you are ordering an SSL certificate for this application, ask for the Apache format. NOTE You must also contact your name server provider so that you can ping the Apache server from the Internet. Network propagation of a machine names can take some time, upwards of 3 hours for some ISP providers. Please remember this when contacting your ISP. This section provides information about the Windows and Apache certificate formats and describes how to convert the Windows format to Apache format.
E.3.2.1
Identifying Windows SSL Certificates

SSL certificates for Windows usually use one of the following formats:
PCKS#12/PFX file format with a .pfx or .p12 extension. PCKS#7/PFX (or P7B) file format with a .p7b or .p7c extension.
PCKS#12/PFX is a binary formats that imbeds the certificate, intermediate certificates, and the private key into one encrypted file.
E.3.2.2
Identifying Apache SSL Certificates

SSL certificates for Apache usually use the PEM format and have one of the following extensions:
.pem .crt .cer .key
This format is a Base64 encoded ASCIIfile.
E.3.2.3
Converting a PFX Certificate to a PEM Certificate

This section describes a process you can use to convert the format an SSL certificate for Windows uses to a format the Apache server can use. For more information about converting formats, refer to OpenSSL user guide. To convert the format an SSL certificate for Windows uses to a format that Apache can use, do the following: Step 1 On the Apache server, open the command line in Windows. Step 2 Navigate to the OpenSSL installation. Typically it is located at: C:\Apache Software Found\Apache2.2\bin
338
Step 3 At the command line, type: openssl pkcs12 -in filename.pfx -nocerts -out key.pem Press Enter. This exports the private key file from the pfx file. Step 4 At the command line, type openssl pkcs12 -in filename.pfx -clcerts -out key.pem Press Enter. This exports the certificate file from the pfx file. Step 5 At the command line, type: openssl rsa -in key.pem -out server.key Press Enter. This removes the passphrase from the private key so that Apache does not prompt you for a password when it is starting. Step 6 In each of the exported files, change the extension from .pem to .crt.(??)
E.3.3
Example Script
This section describes how to configure the Windows server. The certificate files used in this example include following:
Server.crtThis is the actual certificate. NetworkSolutions_CA.crt This is the intermediate certificate provided by NetworkSolutions. This certificate is optional and not all certificate providers provide this certificate. Server.keyThis is the private key.
These file names apply to the example and may be different than those used in your environment. Also, your setup may not have an intermediate certificate. Step 1 Modify httpd.conf to specify proxy port to be used for HTTP+SSL:
# # Listen: Allows # ports, instead # directive. # # Change this to # prevent Apache # Listen 5500 you to bind Apache to specific IP addresses and/or of the default. See also the <VirtualHost>
Listen on specific IP addresses as shown below to from glomming onto all bound IP addresses.
Step 2 Verify in httpd.conf that the following modules are enabled (uncommented):
LoadModule LoadModule LoadModule LoadModule proxy_module modules/mod_proxy.so proxy_http_module modules/mod_proxy_http.so rewrite_module modules/mod_rewrite.so ssl_module modules/mod_ssl.so
Step 3 Verify that the following line is also enabled (uncommented)

Include conf/httpd-vhosts.conf
Step 4 Edit conf/httpd_vhosts.conf:

Listen 5500
ShoreTel 13.1
339
# Use name-based virtual hosting. # NameVirtualHost *:5500 <VirtualHost *:5500> RewriteEngine on RewriteLog "logs/devnosproxy.localhost-rewrite.log" RewriteLogLevel 3 RewriteRule ^/theme/(.+)$ /director2/theme/$1 [P] RewriteRule ^/yui_2.7.0/(.+)$ /director2/yui_2.7.0/$1 [P] RewriteRule ^/js/(.+)$ /director2/js/$1 [P] ProxyPass /authenticate/ http://10.0.0.1/ ProxyPassReverse /authenticate/ http://10.0.0.1/ ProxyPass /cas/ http://10.0.0.1:5447/ ProxyPassReverse /cas/ http://10.0.0.1:5447/ ProxyPass /director2/ http://10.0.0.1:5449/ ProxyPassReverse /director2/ http://10.0.0.1:5449/ ErrorLog "logs/devnosproxy.localhost-error.log" CustomLog "logs/devnosproxy.localhost-access.log" combined # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on # SSL Cipher Suite: # List the ciphers that the client is permitted to negotiate. # See the mod_ssl documentation for a complete list. SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL # Server Certificate: # Point SSLCertificateFile at a PEM encoded certificate. If # the certificate is encrypted, then you will be prompted for a # pass phrase. Note that a kill -HUP will prompt again. Keep # in mind that if you have both an RSA and a DSA certificate you # can configure both in parallel (to also allow the use of DSA # ciphers, etc.) SSLCertificateFile "C:/Apache Software Foundation/Apache2.2/conf/server.crt" #SSLCertificateFile "C:/Apache Software Foundation/Apache2.2/conf/server-dsa.crt" # Server Private Key: # If the key is not combined with the certificate, use this # directive to point at the key file. Keep in mind that if # you've both a RSA and a DSA private key you can configure # both in parallel (to also allow the use of DSA ciphers, etc.) SSLCertificateFile "C:/Apache Software Foundation/Apache2.2/conf/server.key" #SSLCertificateKeyFile "C:/Apache Software Foundation/Apache2.2/conf/server-dsa.key" # # # # # # # Server Certificate Chain: Point SSLCertificateChainFile at a file containing the concatenation of PEM encoded CA certificates which form the certificate chain for the server certificate. Alternatively the referenced file can be the same as SSLCertificateFile when the CA certificates are directly appended to the server certificate for convenience.
340
SSLCertificateChainFile "C:/Apache Software Foundation/Apache2.2/conf/servr-ca.crt
SSLCertificateChainFile "C:/Apache Software Foundation/Apache2.2/conf/ NetworkSolutions_CA.crt" # Certificate Authority (CA): # Set the CA certificate verification path where to find CA # certificates for client authentication or alternatively one # huge file containing all of them (file must be PEM encoded) # Note: Inside SSLCACertificatePath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCACertificatePath "C:/Apache Software Foundation/Apache2.2/conf/ssl.crt" #SSLCACertificateFile "C:/Apache Software Foundation/Apache2.2/conf/ssl.crt/ca-bundle.crt" # Certificate Revocation Lists (CRL): # Set the CA revocation path where to find CA CRLs for client # authentication or alternatively one huge file containing all # of them (file must be PEM encoded) # Note: Inside SSLCARevocationPath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCARevocationPath "C:/Apache Software Foundation/Apache2.2/conf/ssl.crl" #SSLCARevocationFile "C:/Apache Software Foundation/Apache2.2/conf/ssl.crl/ca-bundle.crl" # Client Authentication (Type): # Client certificate verification type and depth. Types are # none, optional, require and optional_no_ca. Depth is a # number which specifies how deeply to verify the certificate # issuer chain before deciding the certificate is not valid. #SSLVerifyClient require #SSLVerifyDepth 10 # Access Control: # With SSLRequire you can do per-directory access control based # on arbitrary complex boolean expressions containing server # variable checks and other lookup directives. The syntax is a # mixture between C and Perl. See the mod_ssl documentation # for more details. #<Location /> #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \ # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \ # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \ # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \ # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \ # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/ #</Location> # # # # # # # # # # # # SSL Engine Options: Set various options for the SSL engine. o FakeBasicAuth: Translate the client X.509 into a Basic Authorisation. This means that the standard Auth/DBMAuth methods can be used for access control. The user name is the `one line' version of the client's X.509 certificate. Note that no password is obtained from the user. Every entry in the user file needs this password: `xxj31ZMTZzkVA'. o ExportCertData: This exports two additional environment variables: SSL_CLIENT_CERT and SSL_SERVER_CERT. These contain the PEM-encoded certificates of the server (always existing) and the client (only existing when client
ShoreTel 13.1
341
# authentication is used). This can be used to import the certificates # into CGI scripts. # o StdEnvVars: # This exports the standard SSL/TLS related `SSL_*' environment variables. # Per default this exportation is switched off for performance reasons, # because the extraction step is an expensive operation and is usually # useless for serving static content. So one usually enables the # exportation for CGI and SSI requests only. # o StrictRequire: # This denies access when "SSLRequireSSL" or "SSLRequire" applied even # under a "Satisfy any" situation, i.e. when it applies access is denied # and no other module can change it. # o OptRenegotiate: # This enables optimized SSL connection renegotiation handling when SSL # directives are used in per-directory context. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire <FilesMatch "\.(cgi|shtml|pl|asp|php)$"> SSLOptions +StdEnvVars </FilesMatch> <Directory "C:/Apache Software Foundation/Apache2.2/conf/cgi-bin"> SSLOptions +StdEnvVars </Directory> # SSL Protocol Adjustments: # The safe and default but still SSL/TLS standard compliant shutdown # approach is that mod_ssl sends the close notify alert but doesn't wait for # the close notify alert from client. When you need a different shutdown # approach you can use one of the following variables: # o ssl-unclean-shutdown: # This forces an unclean shutdown when the connection is closed, i.e. no # SSL close notify alert is send or allowed to received. This violates # the SSL/TLS standard but is needed for some brain-dead browsers. Use # this when you receive I/O errors because of the standard approach where # mod_ssl sends the close notify alert. # o ssl-accurate-shutdown: # This forces an accurate shutdown when the connection is closed, i.e. a # SSL close notify alert is send and mod_ssl waits for the close notify # alert of the client. This is 100% SSL/TLS standard compliant, but in # practice often causes hanging connections with brain-dead browsers. Use # this only for browsers where you know that their SSL implementation # works correctly. # Notice: Most problems of broken clients are also related to the HTTP # keep-alive facility, so you usually additionally want to disable # keep-alive for those clients, too. Use variable "nokeepalive" for this. # Similarly, one has to force some clients to use HTTP/1.0 to workaround # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and # "force-response-1.0" for this. BrowserMatch ".*MSIE.*" \ nokeepalive ssl-unclean-shutdown\ downgrade-1.0 force-response-1.0 # Per-Server Logging: # The home of a custom SSL log file. Use this when you want a # compact non-error SSL logfile on a virtual host basis. CustomLog "C:/Apache Software Foundation/Apache2.2/logs/ssl_request.log"\ "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" </VirtualHost>
342
Checklist:
Identify the machine name you will be using for the proxy server . Remember this is the name that will be used by your end users when they setup their iPhones and the certificate authority to create your SSL. Do not include under-scores or hyphens. Contact ISP or Name Server to create the DNS record that points to the external IP given to the Proxy Server. If you cannot ping the address from the internet then you will not be able to get to the internal address. Order your SSL from the Certificate Authority. You should have a certificate and a private key file. Install Apache 2.2 on the server that you have prepared to be your Proxy Server. Copy the httpd-vhosts.conf file from the %\Apache Software Foundation\Apache2.2\conf\extra folder and place it in the %\Apache Software Foundation\Apache2.2\conf folder this will be where the system will look for the required config files. Copy the certificate files that you get from your certificate authority to the %\Apache Software Foundation\Apache2.2\conf folder as well. Follow the instructions given to prepare the httpd.conf and the httpdvhosts.conf files. Test.
ShoreTel 13.1
343
344
Appendix F
ShoreTel Voice Switches

This appendix describes the ShoreTel voice switches. Switch model numbers are located on the rear panel, as shown in Figure F-1.
Figure F-1
Switch Model Number Label
F.1
Switch Models
The classification of ShoreTel Voice Switch models is in three switch families that depend on the chassis type of the switch:
1-U Half Width Switches 1-U Full Width Switches IPBX Switches
The following is a brief description of each switch family.
F.1.1
ShoreTel 1-U Half Width Voice Switches

The ShoreTel 1-U Half Width Switch family is the most recent ShoreTel switch design. 1-U Half Width have a smaller footprint, use less power, and have lower heat dissipation requirements than earlier ShoreTel switches. These switches offer higher granularity in the number of IP users supported, allowing customers to precisely program the switch to satisfy their requirements. The switches can be stacked or mounted in a standard 19-inch rack. Rack mounting 1-U Half Width Switches requires the ShoreTel Dual Tray. One or two switches are inserted into the Dual Tray, which is then mounted into the 19-inch rack. Two switches are mounted side by side Rack mounting the switches require the ShoreTel Dual Tray
ShoreTel 13.1
345
Appendix F: ShoreTel Voice Switches
ShoreTel 1-U Half Width Voice Switch models include:
ShoreTel 30 (SG 30) ShoreTel 30BRI (SG 30BRI) ShoreTel 50 (SG 50) ShoreTel 90 (SG 90) ShoreTel 90BRI (SG 90BRI) ShoreTel 220T1 (SG 220T1) ShoreTel 220T1A (SG 220T1A) ShoreTel T1k (SG T1k) ShoreTel 220E1 (SG 220E1) ShoreTel E1k (SG E1k)
F.1.2
ShoreTel Voicemail Model Voice Switches

Voicemail Model Switches are ShoreTel switches that provide voicemail services and access to auto attendant menus for extensions hosted by the switch. Voicemail Model (V Model) switches provide local access to voicemail while being controlled by a Distributed server at a different location. The switches can be stacked or mounted in a standard 19-inch rack. Rack mounting 1-U Half Width Switches requires the ShoreTel Dual Tray. One or two switches are inserted into the Dual Tray, which is then mounted into the 19-inch rack. Two switches are mounted side by side Rack mounting the switches require the ShoreTel Dual Tray ShoreTel V Model Switch models include:
ShoreTel 90V (SG 90V) ShoreTel 50V (SG 50V) ShoreTel 90BRIV (SG 90BRIV) F.1.2.1 Capacity
Number of V Model switches allowed per system A ShoreTel system supports a maximum of 100 V Model Switches. There are no restrictions concerning the allocation of switches among the sites defined by the system. Simultaneous Combined Voicemail Calls and File-based MOH Calls Voicemail Model Switches support the following number of simultaneous voicemail calls.
SG50V Maximum of 5 Voicemail calls per switch

G711 calls: 5 G729 calls: 2
346
SG90V Maximum of 9 Voicemail calls per switch

G711 calls: 9 G729 calls: 4
SG90BRIV Maximum of 9 Voicemail calls per switch

G711 calls: 9 G729 calls: 4 Call Load Voicemail Model Switches call load capacity is as follows:
5400 BHCC when supporting 90 MGCP IP Phones or 90 SIP Trunks 3600 BHCC when supporting 90 SIP IP Phones or 90 SIP Trunks
Compact Flash Memory Voicemail Model switches store voicemail and Auto Attendant files on compact flash. Flash card capacity for V Model Switches is:
SG50V: 1 Gb SG90V: 2 Gb SG90BRIV: 2 Gb

Media Support Voicemail Model Switches support the following media streams:
G711
Jack-based Music on Hold (MOH): 15 calls Backup Auto Attendant (BAA): 50 calls
G729
Music on Hold (MOH): none Backup Auto Attendant (BAA): none SIP support Voicemail Model Switches support the following SIP media streams:
G711 Ringback tone (Hunt Groups and Work Group calls): 50 media streams G729 Ringback tone (Hunt Groups and Work Group calls): no support
F.1.3
ShoreTel 1-U Full Width Voice Switches

The ShoreTel 1-U Full Width Switch family includes three models that support analog, IP, SIP, T1, and E1 voice data streams. Full width switch models can be stacked or mounted directly into a standard 19-inch equipment rack. These switches are all 1 RU and have an RJ21X connector for connection to analog phones and trunks. They also feature redundant Ethernet LAN connections for greater availability and reliability. ShoreTel 1-U Full Width Voice Switch models include:
ShoreTel 13.1
347
ShoreTel 120 (SG 120) also referred to as ShoreTel 120/24 (SG 120/24) ShoreTel 60 (SG 60) also referred to as ShoreTel 60/12 (SG 60/12) ShoreTel 40 (SG 48) also referred to as ShoreTel 40/8 (SG 40/8) ShoreTel T1 (SG T1) ShoreTel E1 (SG E1) ShoreTel 24A (SG 24A)
F.1.4
ShoreTel IPBX Voice Switches

The ShoreTel IPBX Switch family is the earliest ShoreTel switch design. Although ShoreTel no long markets IPBX switches, existing switches are supported and can be used in a ShoreTel network configuration. IPBX switches are full width and varying heights, depending on the switch model. ShoreTel IPBX Voice Switch models include:
ShoreTel 24 (IPBX 24) Voice Switch (2 RU) ShoreTel T1 (IPBX T1) Voice Switch (1.5 RU) ShoreTel E1 (IPBX E1) Voice Switch (1.5 RU)
F.2
F.2.1
Specifications SG 1-U Half-Width Switches

ShoreTel 90 Voice Switch
The following sections describe ShoreTel 90 resource capacity, LED behavior, and connectors. Figure F-2 displays the ShoreTel 90 front plate.
Audio Input Port (music on hold) Status LED Network LEDs LAN 1 Connector
Default Switch
Power LED
Network LEDs
LAN 2 Connector
RS-232C Maintentance Port
RJ-21X Telco Port
Audio Output Port (night bell)
Figure F-2
ShoreTel 90 Front Plate
F.2.1.1
Switch Capacity Analog Circuit Resources
348
Ports 1-8: Eight Loop Start Trunks Ports 9-12: Four Extensions or DID Trunks. A single command configures all ports as either Extensions or DID trunks. Power Failure Transfer Unit: Trunk Port 1 to Extension Port 12
Make Me Conference Resources: 12 ports

Ports 1-12
Maximum IP Phone Resources: 90 devices

Analog Port Reallocation: 60 Built-in Resources: 30
F.2.1.2
LED Descriptions
Power LED The ShoreTel 90 has one power LED, which indicates the following:
On: The switch is operating normally. Off: The switch has no power. Flashing:
2 flashesThe switch failed its internal self-test. This indicates a hardware failure. Replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel 90 network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity.
ShoreTel 13.1
349
When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
Link/Activity: When lit, this LED indicates that the switch is connected to an
Ethernet network. This LED indicates network activity, as follows: When flashing, network activity is detected. When on (not flashing), the switch is connected to an Ethernet network. When off, the switch cannot detect an Ethernet network.
This LED is not directly related to any switchs individual network activity. For example, if three switches are connected to the same hub and one switchs Traffic LED shows activity, the other switches will indicate the same activity.
100M:
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Status LED The ShoreTel 90 has one status LED to provide general information about the ports. The color and blink pattern of the LED indicate the port function:
Status LED (Green)

When on steady, no ports are handling active calls. When flashing fast, at least one port is handling an active call.
Status LED (Yellow)

When on steady, no ports are handling active calls and at least one port is out of service. When flashing slow, the switch is not connected (or has lost connection) to a ShoreTel server. When flashing fast, at least one port is handling an active call and at least one port is out of service.
Off: No ports are assigned. F.2.1.3 ShoreTel 90 Connectors

The ShoreTel 90 voice switch contains the following components:
1 3.5 mm mono connector for audio input (music on hold) 1 3.5 mm mono connector for audio output (overhead paging and night bell) 1 DB-9 female connector for maintenance 2 RJ-45 connectors for the LAN interface 1 RJ-21X male connector for mass termination of the telephone/trunk ports
Power Failure Transfer Unit: Trunk Port 1 to Extension Port 12 Backup Operator: Extension Port 12 ShoreTel 90 RJ-21X Telephone and Trunk Connector Table F-1 lists the RJ-21X Ring and Tip pin numbers for the SG 90.
350
Table F-1 Port

1 2 3 4 5 6 7 8 9 10 11 12 Trunk Trunk Trunk Trunk Trunk Trunk Trunk Trunk
ShoreTel 90 RJ-21X Telephone and Trunk Connector Pins Ring Pin # Cable Color Pin #
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Blue/White Orange/White Green/White Brown/White Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
Type
Tip Cable Color

White/Blue White/Orange White/Green White/Brown White/Slate Red/Blue Red/Orange Red/Green Red/Brown Red/Slate Black/Blue Black/Orange Black/Green Black/Brown Black/Slate Yellow/Blue Yellow/Orange Yellow/Green Yellow/Brown Yellow/Slate Violet/Blue Violet/Orange Violet/Green Violet/Brown Violet/Slate
Extension - DID
17 18
Extension - DID
19 20
Extension - DID
21 22
Extension - DID
23 24 25
F.2.2
ShoreTel 90BRI Voice Switch

The following sections describe ShoreTel 90BRI resource capacity, LED behavior, and connectors. Figure F-3 displays the ShoreTel 90BRI front plate.
ShoreTel 13.1
351
Audio Input Port (music on hold) Status LED RS-232C Maintentance BRI Port LEDs
BRI Ports
BRI LEDs
Default Switch Network LEDs Network LEDs
Power LED
LAN Connectors
BRI Ports
RJ-21X Telco Port
Figure F-3
ShoreTel 90BRI Front Plate
F.2.2.1

Ports 9-12: Extensions
Digital Circuit Resources

Four BRI Spans, each comprising two channels: Eight channels maximum
Make Me Conference Resource: None Maximum IP Phone Resources: 90 devices

Analog Port Reallocation: 20 Digital Channel Reallocation: 40 Built-in Resources: 30
F.2.2.2
LED Descriptions
Power LED The ShoreTel 90BRI has one power LED, which indicates the following:
On: The switch is operating normally. Off: The switch has no power. Flashing
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will
352
automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel 90BRI network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
100M
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Status LED The ShoreTel 90BRI has one status LED to provide general information about the ports. The color and blink pattern of the LED indicate the port function:
Status LED (Green)

When on steady, no ports are handling active calls. When flashing fast (100 msec on/off), at least one port is handling an active call.
Status LED (Yellow)
ShoreTel 13.1
353
When on steady, no ports are handling active calls and at least one port is out of service. When flashing slow (1 sec. on/off), the switch is not connected (or has lost connection) to a ShoreTel server. When flashing fast (100 msec on/off), at least one port is handling an active call and at least one port is out of service.
Off: No ports are assigned.

BRI LED Each BRI connector has two LEDs to indicate port activity. The color and blink pattern of the LED indicate the port function:
LED 1: Off, LED 2 Off Port not configured in Director LED 1: Yellow, LED 2 Off Port inactive or not connected LED 1: Off, LED 2 Off Layer 1 active. Layer 2 not established LED 1: Off, LED 2 Green Layer 1 active. Layer 2 active. LED 1: Off, LED 2 Green flashing Call in progress (Layer 1, Layer 2, and
Layer 3 active).
F.2.2.3
ShoreTel 90BRI Connectors

The ShoreTel 90BRI voice switch contains the following components:
1 3.5 mm mono connector for audio input (music on hold) 1 3.5 mm mono connector for audio output (overhead paging and night bell) 1 DB-9 female connector for maintenance 2 RJ-45 connectors for the LAN interface 1 RJ-21X male connector for mass termination of the telephone/trunk ports 4 RJ-45 T1 telco port
ShoreTel 90BRI RJ-21X Telephone and Trunk Connector Table F-2 lists the RJ-21X Ring and Tip pin numbers for the SG 90BRI. Table F-2 ShoreTel 90BRI RJ-21X Telephone and Trunk Connector Pins Ring Pin # Cable Color Pin #
1 2 3 4 5 6 Blue/White Orange/White Green/White Brown/White Slate/White Blue/Red 26 27 28 29 30 31
Port

Type
Tip Cable Color

White/Blue White/Orange White/Green White/Brown White/Slate Red/Blue
354
Table F-2
ShoreTel 90BRI RJ-21X Telephone and Trunk Connector Pins (Continued) Ring Pin # Cable Color Pin #
7 8 9 10 11 12 13 14 15 16 Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
Port
9 10 11 12
Type
Tip Cable Color

Red/Orange Red/Green Red/Brown Red/Slate Black/Blue Black/Orange Black/Green Black/Brown Black/Slate Yellow/Blue Yellow/Orange Yellow/Green Yellow/Brown Yellow/Slate Violet/Blue Violet/Orange Violet/Green Violet/Brown Violet/Slate
Extension
17 18
Extension
19 20
Extension
21 22
Extension
23 24 25
F.2.3

Default Switch
Power LED
Network LEDs
LAN 2 Connector
RJ-21X Telco Port
Figure F-4
ShoreTel 13.1
355
F.2.3.1

Ports 1-4: Four Loop Start Trunks Ports 11-12: Two Extensions or DID Trunks. A single command configures all ports as either Extensions or DID trunks. Power Failure Transfer Unit: Trunk Port 1 to Extension Port 12
Make Me Conference Resources: six ports

Ports 1-4, 11-12

F.2.3.2
LED Descriptions
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration.
356
Network LEDs The ShoreTel 50 network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
100M
Status LED (Green)

Status LED (Yellow)


Power Failure Transfer Unit: Trunk Port 1 to Extension Port 12 Backup Operator: Extension Port 12
ShoreTel 13.1 357
ShoreTel 50 RJ-21X Telephone and Trunk Connector Table F-3 lists the RJ-21X Ring and Tip pin numbers for the SG 50. Table F-3 Port
1 2 3 4 11 12 Extension - DID Extension - DID Trunk Trunk Trunk Trunk
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Blue/White Orange/White Green/White Brown/White Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
Type
Tip Cable Color

F.2.4

358
Default Switch
Power LED
Network LEDs
LAN 2 Connector
RJ-21X Telco Port
Figure F-5
F.2.4.1

Ports 1-2: Two Loop Start Trunks Ports 11-12: Two Extensions or DID Trunks. A single command configures all ports as either Extensions or DID trunks. Power Failure Transfer Unit: Trunk Port 1 to Extension Port 12
Make Me Conference Resources: none Maximum IP Phone Resources: none

F.2.4.2
LED Descriptions
2 flashesThe switch failed its internal self-test. This indicates a hardware failure. Replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/
ShoreTel 13.1
359
DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel 30 network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
100M:
Status LED (Green)

Status LED (Yellow)

When on steady, no ports are handling active calls and at least one port is out of service.
360
When flashing slow, the switch is not connected (or has lost connection) to a ShoreTel server. When flashing fast, at least one port is handling an active call and at least one port is out of service.

Power Failure Transfer Unit: Trunk Port 1 to Extension Port 12 Backup Operator: Extension Port 12 ShoreTel 30 RJ-21X Telephone and Trunk Connector Table F-4 lists the RJ-21X Ring and Tip pin numbers for the SG 30. Table F-4 Port
1 2 Trunk Trunk
ShoreTel 30 RJ-21X Telephone and Trunk Connector Pins Ring Tip Pin #
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
Type Pin # Cable Color

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Blue/White Orange/White Green/White Brown/White Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow
Cable Color
White/Blue White/Orange White/Green White/Brown White/Slate Red/Blue Red/Orange Red/Green Red/Brown Red/Slate Black/Blue Black/Orange Black/Green Black/Brown Black/Slate Yellow/Blue Yellow/Orange Yellow/Green
ShoreTel 13.1
361
Table F-4 Port

11 12
44 45 46 47 48 49 50

19 20 Extension - DID 21 22 Extension - DID 23 24 25 Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet
Cable Color
Yellow/Brown Yellow/Slate Violet/Blue Violet/Orange Violet/Green Violet/Brown Violet/Slate
F.2.5
ShoreTel 30BRI Voice Switch

The following sections describe ShoreTel 30BRI resource capacity, LED behavior, and connectors. Figure F-6 displays the ShoreTel 30BRI front plate.
Audio Input Port (music on hold) Status LED RS-232C Maintentance Port BRI Port
Default Switch
Power LED
Network LEDs
Network LEDs LAN Connectors BRI LEDs
RJ-21X Telco Port
Figure F-6
ShoreTel 30BRI Front Plate
F.2.5.1


One BRI Span comprising two channels: two channels maximum
Make Me Conference Resource: None Maximum IP Phone Resources: 30 devices

362
F.2.5.2
LED Descriptions
Power LED The ShoreTel 30BRI has one power LED, which indicates the following:
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel 30BRI network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
ShoreTel 13.1
363
100M
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Status LED The ShoreTel 30BRI has one status LED to provide general information about the ports. The color and blink pattern of the LED indicate the port function:
Status LED (Green)

Status LED (Yellow)


Layer 3 active).
F.2.5.3
ShoreTel 30BRI Connectors

The ShoreTel 30BRI voice switch contains the following components:
364
ShoreTel 30BRI RJ-21X Telephone and Trunk Connector Table F-5 lists the RJ-21X Ring and Tip pin numbers for the SG 30BRI. Table F-5 ShoreTel 30BRI RJ-21X Telephone and Trunk Connector Pins Ring Pin # Cable Color Pin #
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Extension 17 18 Extension 19 20 Extension 21 22 Extension 23 24 25 Blue/White Orange/White Green/White Brown/White Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
Port
9 10 11 12
Type
Tip Cable Color

F.2.6
ShoreTel 220T1 Voice Switch

The following sections describe ShoreTel 220T1 resource capacity, LED behavior, and connectors. Figure F-7 displays the ShoreTel 220T1 front plate.
ShoreTel 13.1
365
Audio Input Port (music on hold) Status LED Network LEDs LAN 1 Connector Telco Port
T1 LEDs
Default Switch
Power LED
Network LEDs
RS-232C Maintentance Port LAN 2 Connector
Monitor Port
Figure F-7
ShoreTel 220T1 Front Plate
F.2.6.1
Switch Capacity Digital Circuit Resources: 24 channels maximum

One T1 circuit, 24 channels per circuit: 24 channels maximum
Make Me Conference Resource: None Maximum IP Phone Resources: 220

Digital Channel Reallocation: 120 Built-in Resources: 100
F.2.6.2
LED Descriptions
Power LED The ShoreTel 220T1 has one power LED, which indicates the following:
On: The switch is operating normally. Off: The switch has no power. Flashing 2 flashesThe switch failed its internal self-test. This indicates a hardware
failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a DHCP server that
366
supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel 220T1 network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
100M
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Status LED TheShoreTel 220T1 has one status LED to provide general information about the ports. The color and blink pattern of the LED indicate the port function:
Status LED (Green)

Status LED (Yellow)

ShoreTel 13.1
367
Monitor and Telco LEDs The Monitor and Telco LEDs indicate line coding, network framing, and loopback status. These LEDs are color codedgreen, yellow, and red. The Monitor and Telco LED descriptions follow. Telco and Monitor LED alarms and errors are logged as switch events in ShoreTel Directors event log.
Line Coding: This LED indicates line coding status, as follows:

When green, the line coding signal is good. When yellow, bipolar violations (BPV) are being received at one second intervals. When red, a loss of signal (LOS) has occurred. When flashing red, loopback is active (local or CO). When off, the switch has no power.
Framing: This LED indicates network framing status, as follows:

When green, the T1/E1 signal is in frame; the signal is synchronized. When yellow, a yellow alarm has been received from the Central Office. When flashing yellow, the frame-bit error rate has exceeded its limits. A small number of frame-bit errors (>1 per million) have occurred; this state will take up to 10 minutes to clear. When flashing fast yellow, a series of frame-bit errors (>1 per 1000) have occurred. When red, the T1/E1 signal is out-of-frame (OOF). The received signal cannot be framed to the Extended Superframe (ESF) or D4 format. When flashing red, loopback is active (local or CO). When off, the switch has no power.
F.2.6.3
ShoreTel 220T1 Connectors

The ShoreTel 220T1 voice switch contains the following components:
1 3.5 mm mono connector for audio input (music on hold) 1 3.5 mm mono connector for audio output (overhead paging and night bell) 1 DB-9 female connector for maintenance 2 RJ-45 connectors for the LAN interface 1 RJ-45 T1 telco port 1 RJ-45 T1 monitor port for connecting test equipment
F.2.7
ShoreTel 220T1A Voice Switch

The following sections describe ShoreTel 220T1A resource capacity, LED behavior, and connectors. Figure F-8 displays the ShoreTel 220T1A front plate.
368
Audio Input Port (music on hold) Status LED Network LEDs LAN 1 Connector T1 Telco Port
T1 LEDs
Default Switch
Power LED
Network LEDs
T1 LEDs
RJ-21X Telco Port
T1 Monitor Port
Figure F-8
ShoreTel 220T1A Front Plate
F.2.7.1

Ports 1-2: Two Loop Start Trunks Ports 9-12: Four Extensions or DID Trunks. A single command configures all ports as either Extensions or DID trunks. Power Failure Transfer Unit: Trunk Port 1 to Extension Port 12
Digital Circuit Resources: 24 channels maximum

One T1 circuit, 24 channels per circuit
Make Me Conference Resource: Six ports

Ports 1-2, 9-12

Analog Channel Reallocation: 30 Digital Channel Reallocation: 120 Built-in Resources: 70
F.2.7.2
LED Descriptions
Power LED The ShoreTel 220T1A has one power LED, which indicates the following:
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in
ShoreTel 13.1 369
nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel 220T1A network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
100M
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Status LED The ShoreTel 220T1A has one status LED to provide general information about the ports. The color and blink pattern of the LED indicate the port function:
Status LED (Green)

370
Status LED (Yellow)



When green, the line coding signal is good. When yellow, bipolar violations (BPV) are received at one second intervals. When red, a loss of signal (LOS) has occurred. When flashing red, loopback is active (local or CO). When off, the switch has no power. When green, the T1/E1 signal is in frame; the signal is synchronized. When yellow, a yellow alarm has been received from the Central Office. When flashing yellow, the frame-bit error rate has exceeded its limits. When flashing slow yellow, a small number of frame-bit errors (>1 per million) have occurred; this state will take up to 10 minutes to clear. When flashing fast yellow, a series of frame-bit errors (> 1 per 1000) have occurred. When red, the T1/E1 signal is out-of-frame (OOF). The received signal cannot be framed to the Extended Superframe (ESF) or D4 format. When flashing red, loopback is active (local or CO). When off, the switch has no power.
F.2.7.3
ShoreTel 220T1A Connectors

The ShoreTel 220T1A voice switch contains the following components:
1 3.5 mm mono connector for audio input (music on hold) 1 3.5 mm mono connector for audio output (overhead paging and night bell) 1 DB-9 female connector for maintenance 1 RJ-21X male connector for mass termination of the telephone/trunk ports 2 RJ-45 connectors for the LAN interface 1 RJ-45 T1 telco port 1 RJ-45 T1 monitor port for connecting test equipment
ShoreTel 13.1
371
ShoreTel 220T1A RJ-21X Telephone and Trunk Connector Table F-6 lists the RJ-21X Ring and Tip pin numbers for the SG 220T1AI. Table F-6 ShoreTel 220T1A RJ-21X Telephone and Trunk Connector Pins Ring Port
1 2 9 10 11 12 Extension Extension Extension Extension Trunk Trunk
Tip Pin #
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Blue/White Orange/White Green/White Brown/White Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet
Cable Color
F.2.8
ShoreTel-220E1 Voice Switch

The following sections describe ShoreTel-220E1 resource capacity, LED behavior, and connectors. Figure F-9 displays the ShoreTel-220E1 front plate.
372
Audio Input Port (music on hold) Status LED Network LEDs LAN 1 Connector E1 LEDs Telco Port
Default Switch
Power LED
Network LEDs
Monitor Port
Figure F-9
ShoreTel-220E1 Front Plate
F.2.8.1

One E1 circuit, 30 channels per circuit
Make Me Conference Resource: none Maximum IP Phone Resources: 220

Digital Channel Reallocation: 150 Built-in Resources: 70
F.2.8.2
LED Descriptions
Power LED The ShoreTel-220E1 has one power LED, which indicates the following:
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a
ShoreTel 13.1 373
DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel-220E1 network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
100M
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Status LED The ShoreTel-220E1 has one status LED to provide general information about the ports. The color and blink pattern of the LED indicate the port function:
Status LED (Green)

Status LED (Yellow)

374


When green, the T1/E1 signal is in frame; the signal is synchronized. When yellow, a yellow alarm has been received from the Central Office. When flashing yellow, the frame-bit error rate has exceeded its limits. When flashing slow yellow, a small number of frame-bit errors (10e-6) have occurred; this state will take up to 10 minutes to clear. When flashing fast yellow, a series of frame-bit errors (10e-3) have occurred. When red, the T1/E1 signal is out-of-frame (OOF). The received signal cannot be framed to the Extended Superframe (ESF) or D4 format. When flashing red, loopback is active (local or CO). When off, the switch has no power.
F.2.8.3
ShoreTel-220E1 Connectors
The ShoreTel-220E1 voice switch contains the following components:
F.2.9
ShoreTel T1k Voice Switch

The following sections describe ShoreTel T1k resource capacity, LED behavior, and connectors. Figure F-10 displays the ShoreTel T1k front plate.
ShoreTel 13.1
375
Audio Input Port (music on hold) Status LED Network LEDs LAN 1 Connector Telco Port
T1 LEDs
Default Switch
Power LED
Network LEDs
Monitor Port
Figure F-10 ShoreTel T1k Front Plate
F.2.9.1

One T1 circuit, 24 channels per circuit
Make Me Conference Resource: None Maximum IP Phone Resources: None F.2.9.2 LED Descriptions
Power LED The ShoreTel T1k has one power LED, which indicates the following:
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the
376
ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel T1k network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
100M
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Status LED The ShoreTel T1k has one status LED to provide general information about the ports. The color and blink pattern of the LED indicate the port function:
Status LED (Green)

Status LED (Yellow)

ShoreTel 13.1
377


When green, the T1/E1 signal is in frame; the signal is synchronized. When yellow, a yellow alarm has been received from the Central Office. When flashing yellow, the frame-bit error rate has exceeded its limits. A small number of frame-bit errors (>1 per million) have occurred; this state will take up to 10 minutes to clear. When flashing fast yellow, a series of frame-bit errors (>1 per 1000) have occurred. When red, the T1/E1 signal is out-of-frame (OOF). The received signal cannot be framed to the Extended Superframe (ESF) or D4 format. When flashing red, loopback is active (local or CO). When off, the switch has no power.
F.2.9.3
ShoreTel T1k Connectors

The ShoreTel T1k voice switch contains the following components:
F.2.10 ShoreTel E1k Voice Switch

The following sections describe ShoreTel E1k resource capacity, LED behavior, and connectors. Figure F-11 displays the ShoreTel E1k front plate.
378
Audio Input Port (music on hold) Status LED Network LEDs LAN 1 Connector E1 LEDs Telco Port
Default Switch
Power LED
Network LEDs
Monitor Port
Figure F-11
ShoreTel E1k Front Plate
F.2.10.1 Switch Capacity Digital Circuit Resources: 30 channels maximum

One E1 circuit, 30 channels per circuit
Make Me Conference Resource: None Maximum IP Phone Resources: None F.2.10.2 LED Descriptions
Power LED The ShoreTel E1k has one power LED, which indicates the following:
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a
ShoreTel 13.1 379
DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel E1k network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
100M
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Status LED The ShoreTel E1k has one status LED to provide general information about the ports. The color and blink pattern of the LED indicate the port function:
Status LED (Green)

Status LED (Yellow)

380


When green, the E1 signal is in frame; the signal is synchronized. When yellow, a yellow alarm has been received from the Central Office. When flashing yellow, the frame-bit error rate has exceeded its limits. A small number of frame-bit errors (>1 per million) have occurred; this state will take up to 10 minutes to clear. When flashing fast yellow, a series of frame-bit errors (>1 per 1000) have occurred. When red, the T1/E1 signal is out-of-frame (OOF). The received signal cannot be framed to the Extended Superframe (ESF) or D4 format. When flashing red, loopback is active (local or CO). When off, the switch has no power.
F.2.10.3 ShoreTel E1k Connectors

The ShoreTel E1k voice switch contains the following components:
F.3
F.3.1
Specifications SG Voice Model Switches

ShoreTel 90V Voice Switch
The following sections describe ShoreTel 90V resource capacity, LED behavior, and connectors. Figure F-12 displays the ShoreTel 90V front plate.
ShoreTel 13.1
381
Audio Input Port (music on hold) Status LED Network LEDs LAN 1 Connector RS-232C Auxilary Port
Default Switch
Power LED
Network LEDs
LAN 2 Connector
RJ-21X Telco Port
Figure F-12 ShoreTel 90V Front Plate
F.3.1.1

Ports 1-8: Eight Loop Start Trunks Ports 9-12: Four Extensions or DID Trunks. A single command configures all ports as either Extensions or DID trunks. Power Failure Transfer Unit: Trunk Port 1 to Extension Port 12
Make Me Conference Resources: 12 ports

Ports 1-12

F.3.1.2
LED Descriptions
Power LED The ShoreTel 90V has one power LED, which indicates the following:
2 flashesThe switch failed its internal self-test. This indicates a hardware failure. Replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will
382
automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel 90V network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
100M:
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Status LED The ShoreTel 90V has one status LED to provide general information about the ports. The color and blink pattern of the LED indicate the port function:
Status LED (Green)

ShoreTel 13.1
383
Status LED (Yellow)

Off: No ports are assigned. F.3.1.3 ShoreTel 90V Connectors

The ShoreTel 90V voice switch contains the following components:
Power Failure Transfer Unit: Trunk Port 1 to Extension Port 12 Backup Operator: Extension Port 12 ShoreTel 90V RJ-21X Telephone and Trunk Connector Table F-7 lists the RJ-21X Ring and Tip pin numbers for the ShoreTel 90V. Table F-7 ShoreTel 90V RJ-21X Telephone and Trunk Connector Pins Ring Port
1 2 3 4 5 6 7 8 Trunk Trunk Trunk Trunk Trunk Trunk Trunk Trunk
Tip Cable Color

White/Blue White/Orange White/Green White/Brown White/Slate Red/Blue Red/Orange Red/Green Red/Brown Red/Slate Black/Blue Black/Orange Black/Green Black/Brown Black/Slate
Type
Pin Pin # Cable Color #

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Blue/White Orange/White Green/White Brown/White Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black Green/Black Brown/Black Slate/Black 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
384
Table F-7
ShoreTel 90V RJ-21X Telephone and Trunk Connector Pins Ring Tip Cable Color
Yellow/Blue Yellow/Orange Yellow/Green Yellow/Brown Yellow/Slate Violet/Blue Violet/Orange Violet/Green Violet/Brown Violet/Slate
Port
9 10 11 12
Type
Extension - DID
Pin Pin # Cable Color #

16 17 18 Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet 41 42 43 44 45 46 47 48 49 50
Extension - DID
19 20
Extension - DID
21 22
Extension - DID
23 24 25
F.3.2
ShoreTel 90BRIV Voice Switch

The following sections describe ShoreTel 90BRIV resource capacity, LED behavior, and connectors. Figure F-13 displays the ShoreTel 90BRIV front plate.
Audio Input Port (music on hold) Status LED RS-232C Maintentance BRI Port LEDs
BRI Ports
BRI LEDs
Default Switch Network LEDs Network LEDs
Power LED
LAN Connectors
BRI Ports
RJ-21X Telco Port
Figure F-13 ShoreTel 90BRIV Front Plate
F.3.2.1


Four BRI Spans, each comprising two channels: Eight channels maximum
Make Me Conference Resource: None

ShoreTel 13.1 385

F.3.2.2
LED Descriptions
Power LED The ShoreTel 90BRIV has one power LED, which indicates the following:
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel 90BRIV network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity.
386
When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
100M
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Status LED The ShoreTel 90BRIV has one status LED to provide general information about the ports. The color and blink pattern of the LED indicate the port function:
Status LED (Green)

Status LED (Yellow)


Layer 3 active).
ShoreTel 13.1
387
F.3.2.3
ShoreTel 90BRIV Connectors

The ShoreTel 90BRIV voice switch contains the following components:
ShoreTel 90BRIV RJ-21X Telephone and Trunk Connector Table F-8 lists the RJ-21X Ring and Tip pin numbers for the SG 90BRIV. Table F-8 ShoreTel 90BRIV RJ-21X Telephone and Trunk Connector Pins Ring Pin # Cable Color Pin #
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Extension 17 18 Extension 19 20 Extension 21 22 Blue/White Orange/White Green/White Brown/White Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
Port
9 10 11
Type
Tip Cable Color

White/Blue White/Orange White/Green White/Brown White/Slate Red/Blue Red/Orange Red/Green Red/Brown Red/Slate Black/Blue Black/Orange Black/Green Black/Brown Black/Slate Yellow/Blue Yellow/Orange Yellow/Green Yellow/Brown Yellow/Slate Violet/Blue Violet/Orange
388
Table F-8
ShoreTel 90BRIV RJ-21X Telephone and Trunk Connector Pins (Continued) Ring Pin # Cable Color Pin #
23 24 25 Green/Violet Brown/Violet Slate/Violet 48 49 50
Port
12
Type
Extension
Tip Cable Color

Violet/Green Violet/Brown Violet/Slate
F.3.3
ShoreTel 50V Voice Switch

The following sections describe ShoreTel 50V resource capacity, LED behavior, and connectors. Figure F-14 displays the ShoreTel 50V front plate.
Audio Input Port (music on hold) Status LED Network LEDs LAN 1 Connector RS-232C Auxilary Port
Default Switch
Power LED
Network LEDs
LAN 2 Connector
RJ-21X Telco Port
Figure F-14 ShoreTel 50V Front Plate
F.3.3.1

Ports 1-4: Four Loop Start Trunks Ports 11-12: Two Extensions or DID Trunks. A single command configures all ports as either Extensions or DID trunks. Power Failure Transfer Unit: Trunk Port 1 to Extension Port 12
Make Me Conference Resources: six ports
Ports 1-4, 11-12

ShoreTel 13.1
389
F.3.3.2
LED Descriptions
Power LED The ShoreTel 50V has one power LED, which indicates the following:
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsk/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsk/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Network LEDs The ShoreTel 50V network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
390
100M
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Status LED The ShoreTel 50V has one status LED to provide general information about the ports. The color and blink pattern of the LED indicate the port function:
Status LED (Green)

Status LED (Yellow)

Off: No ports are assigned. F.3.3.3 ShoreTel 50V Connectors

The ShoreTel 50V voice switch contains the following components:
Power Failure Transfer Unit: Trunk Port 1 to Extension Port 12 Backup Operator: Extension Port 12 ShoreTel 50V RJ-21X Telephone and Trunk Connector Table F-9 lists the RJ-21X Ring and Tip pin numbers for the SG 50V. Table F-9 Port
1 2 Trunk Trunk
ShoreTel 50V RJ-21X Telephone and Trunk Connector Pins Ring Pin # Cable Color Pin #
1 2 3 4 Blue/White Orange/White Green/White Brown/White 26 27 28 29
Type
Tip Cable Color

White/Blue White/Orange White/Green White/Brown
ShoreTel 13.1
391
Table F-9 Port

3 4 9 10 11 12 Trunk Trunk
ShoreTel 50V RJ-21X Telephone and Trunk Connector Pins Ring Pin # Cable Color Pin #
5 6 7 8 9 10 11 12 13 14 15 16 Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
Type
Tip Cable Color

White/Slate Red/Blue Red/Orange Red/Green Red/Brown Red/Slate Black/Blue Black/Orange Black/Green Black/Brown Black/Slate Yellow/Blue Yellow/Orange Yellow/Green Yellow/Brown Yellow/Slate Violet/Blue Violet/Orange Violet/Green Violet/Brown Violet/Slate
Extension - DID
17 18
Extension - DID
19 20
Extension - DID
21 22
Extension - DID
23 24 25
F.4
F.4.1
Specification SG 1U Full Width Switches

The following sections describe ShoreTel 120 resource capacity, LED behavior, and connectors.Figure F-15 displays the ShoreTel 120 front plate. The ShoreTel 120 is often referred to as the ShoreTel 120/24 (SG 120/24).
392
Audio Input Port (music on hold) Power LED Network LEDs

ShoreGear- 120/24
Analog Phone RJ-11
Default Switch
LAN Connectors
RS-232C Maintentance Port Switch Port LEDs
RJ-21X Telco Port
Figure F-15 ShoreTel 120 Front Plate
F.4.1.1

Ports 1-8: Eight Loop Start Trunks, DID Trunks, or Extensions Ports 9-24: Sixteen Extensions. Power Failure Transfer Unit: Trunk Port 8 to Extension Port 9
Make Me Conference Resource: 24 Ports

Ports 1-24

Analog Port Reallocation: 120
F.4.1.2
LED Descriptions
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five
ShoreTel 13.1 393
seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsa/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsa/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Switch Port LEDs The ShoreTel 120 has 24 telephone/trunk port LEDs. The color of the LED indicates the port function:
Green when the port is a telephone port. Yellow when the port is a trunk port.
configured. The following describes the switch port LED behavior and meaning:
Off indicates the port is reserved for IP phones, for conferencing, or is not
Telephone Port LEDs (Green)

When on steady, the port is configured as a telephone port and the telephone is idle. When flashing with ring cadence, the telephone is ringing. When flashing slowly, the telephone is off hook. When flashing fast, the port is in use (call in progress).
Trunk Port LED (Yellow):

When on steady, the port is configured as a trunk port and the trunk is idle. When flashing slowly, the trunk is off hook. When flashing fast, the trunk is in use (call in progress).
Port LED Alternating Green/Yellow: The port is out of service. The LED
periodically alternates green/yellow or yellow/green. The color of the LED between alternating colors indicates the port type: green for phone and yellow for trunk. conferencing, or is not configured.
Off (IP phone): When the LED is off, the port is reserved for IP phones, for
Network LEDs The network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port. The network LED descriptions are as follows:
394
Ethernet network. This LED indicates network activity, as follows: When flashing, network activity is detected. When on (not flashing), heavy network activity is detected. When off, the switch has no power.
100M
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network.
F.4.1.3
ShoreTel 120 Connectors

1 3.5 mm mono connector for audio input (music on hold) 1 3.5 mm mono connector for audio output (overhead paging and night bell) 1 DB-9 female connector for maintenance 2 RJ-45 connectors for the LAN interface 1 RJ-11 connector for connecting an analog phone (extension 9) 1 RJ-21X male connector for mass termination of the telephone/trunk ports
Power Failure Transfer Unit: Trunk Port 8 to Extension Port 9 Backup Operator: Extension Port 9 ShoreTel 120 RJ-21X Telephone and Trunk Connector Table F-10 lists the RJ-21X Ring and Tip pin numbers for the SG 120I. Table F-10 Port
1 2 3 4 5 6 7 8 9 10 11 12
1 2 3 4 5 6 7 8 9 10 11 12 Blue/White Orange/White Green/White Brown/White Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black 26 27 28 29 30 31 32 33 34 35 36 37
Type
Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Extension Extension Extension Extension
Tip Cable Color

White/Blue White/Orange White/Green White/Brown White/Slate Red/Blue Red/Orange Red/Green Red/Brown Red/Slate Black/Blue Black/Orange
ShoreTel 13.1
395
Table F-10 Port

13 14 15 16 17 18 19 20 21 22 23 24
13 14 15 16 17 18 19 20 21 22 23 24 25 Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet 38 39 40 41 42 43 44 45 46 47 48 49 50
Type
Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension
Tip Cable Color

Black/Green Black/Brown Black/Slate Yellow/Blue Yellow/Orange Yellow/Green Yellow/Brown Yellow/Slate Violet/Blue Violet/Orange Violet/Green Violet/Brown Violet/Slate
F.4.2
ShoreTel 24A Voice Switch

The following sections describe ShoreTel 24A resource capacity, LED behavior, and connectors. Figure F-16 displays the ShoreTel 24A front plate.
ShoreGear- 24A
Analog Phone RJ-11
Default Switch
LAN Connectors
RJ-21X Telco Port
Figure F-16 ShoreTel 24A Front Plate
F.4.2.1

Ports 1-24: Twenty four extensions
Make Me Conference Resource: 24 Ports

Ports 1-24
396
Maximum IP Phone Resources: None F.4.2.2 LED Descriptions

Power LED The ShoreTel 24A has one power LED, which indicates the following:
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsa/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsa/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Switch Port LEDs The ShoreTel 24A has 24 telephone/trunk port LEDs. The color of the LED indicates the port function:
configured. The following describes the switch port LED behavior and meaning:
ShoreTel 13.1
397
Trunk Port LED (Yellow):

100M
F.4.2.3
ShoreTel 24A Connectors

The ShoreTel 24A voice switch contains the following components:
398
ShoreTel 24A RJ-21X Telephone and Trunk Connector Table F-11 lists the RJ-21X Ring and Tip pin numbers for the SG 24AI. Table F-11 Port
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension Extension
ShoreTel 24A RJ-21X Telephone and Trunk Connector Pins Ring Tip Pin #
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Blue/White Orange/White Green/White Brown/White Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet
Cable Color
F.4.3

The following sections describe ShoreTel 60 resource capacity, LED behavior, and connectors. Figure F-17 displays the ShoreTel 60 front plate. The ShoreTel 60 is often referred to as the ShoreTel 60/12 (SG 60/12).
ShoreTel 13.1
399

ShoreGear- 60/12
Analog Phone RJ-11
Default Switch
LAN Connectors
RJ-21X Telco Port
Figure F-17 ShoreTel 60 Front Plat
F.4.3.1

Ports 1-8: Eight Loop Start Trunks, DID Trunks, or Extensions Ports 9-12: Four Extensions. Backup Operator: Extension Port 9 Power Failure Transfer Unit: Trunk Port 8 to Extension Port 9
Make Me Conference Resource: 12 ports

Ports 1-12

F.4.3.2
LED Descriptions
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address.
400
5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsa/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsa/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Switch Port LEDs The ShoreTel 60 has 12 telephone/trunk port LEDs. The color of the LED indicates the port function:
Green when the port is a telephone port. Yellow when the port is a trunk port. Off indicates the port is reserved for IP phones, for conferencing, or is not configured.
The following describes the switch port LED behavior and meaning:

Trunk Port LED (Yellow)

Port LED Alternating Green/Yellow: The port is out of service. The LED Off (IP phone): When the LED is off, the port is reserved for IP phones, for
conferencing, or is not configured. Network LEDs The network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity.
periodically alternates green/yellow or yellow/green. The LED color between alternating colors indicates the port type: green for phone and yellow for trunk.
When both LAN connectors are connected into a redundant network configuration, one network port is active while the other is in standby mode. If one LAN connection fails, the switch activates the other port.
ShoreTel 13.1
401
The network LED descriptions are as follows:
100M
F.4.3.3
ShoreTel 60 voice switch contains the following components:
Power Failure Transfer Unit: Trunk Port 8 to Extension Port 9 Backup Operator: Extension Port 9 ShoreTel 60 RJ-21X Telephone and Trunk Connector Table F-12 lists the RJ-21X Ring and Tip pin numbers for the SG 60. Table F-12 Port
1 2 3 4 5 6 7 8 9 10 11
1 2 3 4 5 6 7 8 9 10 11 Blue/White Orange/White Green/White Brown/White Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black 26 27 28 29 30 31 32 33 34 35 36
Type
Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Trunk, DID, Extension Extension Extension Extension
Tip Cable Color

White/Blue White/Orange White/Green White/Brown White/Slate Red/Blue Red/Orange Red/Green Red/Brown Red/Slate Black/Blue
402
Table F-12 Port

12
12 13 14 15 16 17 18 19 20 21 22 23 24 25 Orange/Black Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet 37 38 39 40 41 42 43 44 45 46 47 48 49 50
Type
Extension
Tip Cable Color

Black/Orange Black/Green Black/Brown Black/Slate Yellow/Blue Yellow/Orange Yellow/Green Yellow/Brown Yellow/Slate Violet/Blue Violet/Orange Violet/Green Violet/Brown Violet/Slate
ShoreTel 13.1
403
F.4.3.4

The following sections describe ShoreTel 40 resource capacity, LED behavior, and connectors. Figure F-18 displays the ShoreTel 40 front plate. The ShoreTel 40 is often referred to as the ShoreTel 40/8 (SG 40/8).
ShoreGear- 40/8
Analog Phone RJ-11
Default Switch
LAN Connectors
RJ-21X Telco Port
Figure F-18 ShoreTel 40 Front Plate
F.4.3.5

Ports 1-2: Two Loop Start Trunks, DID Trunks, or Extensions Ports 3-4: Two Loop Start Trunks. Ports 5-8: Four Extensions Power Failure Transfer Unit: Trunk Port 4 to Extension Port 5
Make Me Conference Resource: eight ports

Ports 1-8

F.4.3.6
LED Descriptions
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory might be corrupted. Go to the Quick Look page to ensure that the system is running properly.
404
4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. You can use BOOTP or DHCP to tell the switch where the files are. If you are using BOOTP, set the BOOTP server to the IP address of the ShoreTel server, and set the boot file to /tsa/vxworks. If you are using a DHCP server that supports options 66 and 67, set option 66 to the ShoreTel servers IP address, and set option 67 to /tsa/vxworks. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration. Switch Port LEDs The ShoreTel 40 has 8 telephone/trunk port LEDs. The color of the LED indicates the port function:
configured. The following describes the switch port LED behavior and meaning.

Trunk Port LED (Yellow)

ShoreTel 13.1
405
Ethernet network. This LED indicates network activity, as follows: When flashing, network activity is detected. When on (not flashing), heavy network activity is detected. When off, network activity is not detected.
100M
F.4.3.7
Power Failure Transfer Unit: Trunk Port 4 to Extension Port 5 Backup Operator: Extension Port 5 ShoreTel 40 RJ-21X Telephone and Trunk Connector Table F-13 lists the RJ-21X Ring and Tip pin numbers for the SG 40I. Table F-13 Port

26 27 28 29

1 2 3 4 Blue/White Orange/White Green/White Brown/White
Cable Color
White/Blue White/Orange White/Green White/Brown
406
Table F-13 Port

1 2 3 4 5 6 7 8
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50

Trunk, DID, Extension Trunk, DID, Extension Trunk Trunk Extension Extension Extension Extension 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Slate/White Blue/Red Orange/Red Green/Red Brown/Red Slate/Red Blue/Black Orange/Black Green/Black Brown/Black Slate/Black Blue/Yellow Orange/Yellow Green/Yellow Brown/Yellow Slate/Yellow Blue/Violet Orange/Violet Green/Violet Brown/Violet Slate/Violet
Cable Color
White/Slate Red/Blue Red/Orange Red/Green Red/Brown Red/Slate Black/Blue Black/Orange Black/Green Black/Brown Black/Slate Yellow/Blue Yellow/Orange Yellow/Green Yellow/Brown Yellow/Slate Violet/Blue Violet/Orange Violet/Green Violet/Brown Violet/Slate
F.4.4
ShoreTel-T1 and ShoreTel E1 Voice Switches

The following sections describe ShoreTel-T1 and ShoreTel E1 resource capacity, LED behavior, and connectors. Figure F-19 displays the ShoreTel-T1 front plate. The ShoreTel E1 front plate is identical to the ShoreTel-T1 except for the E1 labeling.
Power LED Network LEDs
ShoreGear- T1
T1 Port (RJ-48C)
Default Switch
LAN Connectors
T1 Monitor Port (RJ-48C)
Figure F-19 ShoreTel-T1 Front Plate

ShoreTel 13.1 407
The ShoreTel-T1 provides higher-density trunking to the central office using CAS or PRI signaling. The ShoreTel-T1 can also be used as a gateway to legacy PBX systems. The ShoreTel E1 provides higher-density trunking to the central office using PRI signaling. The ShoreTel E1 can also be used as a gateway to legacy PBX systems.
F.4.4.1
Switch Capacity Digital Circuit Resources

SG T1 One T1 circuit, 24 channels per circuit: 24 channels maximum. SG E1 One T1 circuit, 30 channels per circuit: 30 channels maximum.
Make Me Conference Resources: None Maximum IP Phone Resources: None F.4.4.2 LED Descriptions
Power LED The ShoreTel-T1 and ShoreTel E1 voice switches have one power LED, which indicates the following:
2 flashesThe switch failed its internal self-test. This indicates a hardware failure; replace the unit and submit a Return Material Authorization (RMA) to ShoreTel, Inc. 3 flashesBooting via FTP. Flash memory may be corrupted. Go to the Quick Look page to make sure that the system is running properly. 4 flashesThe IP address is unavailable. DHCP and BOOTP did not respond to the IP address request, and the IP address is not available in nonvolatile memory to continue boot process. The switch will automatically reboot in five seconds and try again. Check the BOOTP/ DHCP server and the network configuration to ensure that the voice switch is receiving a valid IP address. 5 flashesThe operating system is not available. The switch is booting from FTP but cannot find the boot files. It automatically reboots in five seconds. 6 flashesUsing a previously stored IP address. A BOOTP/DHCP transaction was attempted, but the BOOTP/DHCP server did not respond. The switch continues to use the IP address stored in nonvolatile memory until it receives a valid response. If the switch receives a response that provides a different IP address, it reboots using the new IP address. If the switch receives a response that matches the IP address stored in nonvolatile memory, it continues operation, and the power LED stops flashing. If the problem persists, check the BOOTP/DHCP server and network configuration.
408
Network LEDs The network LEDs (LAN1 and LAN2) indicate the speed at which the switch is communicating with the network and whether there is network activity. The network LED descriptions are as follows:
Ethernet network. This LED indicates network activity, as follows: When flashing, network activity is detected. When on (not flashing), heavy network activity is detected. When off, network activity is not detected.
100M
When green, the switch is connected to a 100BaseT network. When off, the switch is connected to a 10BaseT network. Monitor and Telco LEDs The Monitor and Telco LEDs indicate line coding, network framing, and loopback status. These LEDs are color codedgreen, yellow, and red. The Monitor and Telco LED descriptions follow. Telco and Monitor LED alarms and errors are logged as switch events in ShoreTel Directors event log.


When green, the T1/E1 signal is in frame; the signal is synchronized. When yellow, a yellow alarm has been received from the Central Office. When flashing yellow, the frame-bit error rate has exceeded its limits. When flashing slow yellow, a small number of frame-bit errors (>1 per million) have occurred; this state will take up to 10 minutes to clear. When flashing fast yellow, a series of frame-bit errors (>1 per 1000) have occurred. When red, the T1/E1 signal is out-of-frame (OOF). The received signal cannot be framed to the Extended Superframe (ESF) or D4 format. When flashing red, loopback is active (local or CO). When off, the switch has no power.
ShoreTel-T1 and ShoreTel E1 Connectors The ShoreTel-T1 and ShoreTel E1 voice switches contain the following components:
1 DB-9 female connector for maintenance 2 RJ-45 connectors for the LAN interface
ShoreTel 13.1 409
1 RJ-45 T1 telco port 1 RJ-45 T1 monitor port for connecting test equipment
410
Glossary
Administrator The office manager or IS professional responsible for installing and
configuring the system.
All Trunks Busy The situation in which a user tries to make an outside call through a
telephone system and receives a fast busy signal (twice as many as normal in the same amount of time), indicating that no trunks are available to handle the call.
API Application programming interface; software that an application program uses to
request and carry out lower-level services performed by the computers or telephone systems operating system. For Windows, the API also helps applications manage windows, menus, icons, and other graphical user interface elements.
Automated Attendant A device that answers callers with a recording and allows callers to route themselves to an extension; also called an auto-attendant. BOOTP Boot Protocol, a standard protocol for assigning networking information to
client workstations over the network; similar to but less sophisticated than DHCP.
Call Control The dynamic, transactional servicing of calls, usually via a graphical user
interface with call information. For example, an attendant can use a GUI application to transfer calls based on CallerID information. in order to obtain certain expected results. Examples of call handling features include call forwarding on busy, call forwarding on no answer, and do not disturb.
Call Handling The predetermined, pre-configured features for servicing incoming calls
Call Handling Mode A set of telephony and call handling features that are enabled depending on the business conditions of the user (for example, in the office or out of the office). Call handling modes, which are enabled manually by the user, include features such as call forwarding on busy, call forwarding on no answer, and the selection of the voice mail greeting to use for a particular mode. Call History The visual records in ShoreTel Desktop, documenting all incoming and
outgoing calls to the users extension.
Call Notification A set of features that inform the user of the arrival of a new call, such as
ringing the telephone or playing a sound on the workstation speakers.
Call Routing A methodology of delivering calls to destinations based on a situation or
system status. Call routing can also refer to the automatic delivery of an incoming call to a particular extension, such as in DID or dedicated CO lines.
ShoreTel 13.1
411
Glossary
Call Stack The list of calls in ShoreTel Desktop associated with an extension, including active calls and calls that have been put on hold or are being managed in some other way by the user. Call Waiting Usually for single-line telephones, a feature that lets a second call arrive to
the line by delivering a call-waiting tone to the user and a ring-back to the caller.
Call-Waiting Tone The tone that is presented to a user with call waiting when a second
call arrives.
Caller For documentation purposes, an outside caller a person calling the telephone system from outside. See also End User. CallerID A technique for transmitting the calling partys telephone number and (optionally) name to equipment enabled to handle this feature; also called CLI in Europe. Centrex A name for advanced telephone services provided by the local telephone company. It usually requires a connection to a special telephone system but provides services such as voice mail and call forwarding. CLASS Custom Local Area Signalling Services, a family of telephone services offered
from local telephone companies, usually for a monthly fee; includes features such as CallerID, Call Waiting, call return, repeat dialing, call rejection, call trace, priority ringing, and selective call forwarding.
Class of Service Abbreviated as CoS or COS; a set of features and privileges associated with a particular user or extension, used for grouping similar users together. CO Central Office; the building where the telephone companys telephone switching
equipment that services the local area is located.
CO Line See Trunk. Conference Three or more parties joined together in a single call, such that each party can hear and be heard by the others. DHCP Dynamic Host Configuration Protocol, a protocol for downloading network
information (such as IP addresses) to client workstations.
DID Direct Inward Dial, a signaling mechanism used by telephone companies to
indicate to a customers PBX what telephone number was dialed by the calling party. It can be used with analog lines but is used mostly with digital (that is, T-1) connections.
DTMF Dual-Tone Multi-Frequency, a technique of providing two tones for each button
on a telephone to signal dialing digits; also known as Touch Tone.
End User For documentation purposes, a person using the telephone system from the
inside, such as from an extension or a call control application, as opposed to a caller who dials in from outside the system; often shortened to user. See also Caller.
412
Glossary

Erlang Formula A mathematical way of predicting a randomly arriving workload (such
as telephone calls) based on known information (such as average call duration). Although traditionally used in telephone traffic engineering to determine the required number of trunks, Erlang formulas have applications in call center staffing as well. the Public Switched Telephone Network (PSTN).
External Call A telephone call directed to or from outside the telephone system, and over FSK Frequency Shift Key, a modulation technique used with low-speed modems; also used with CallerID and message-waiting lamp indicators. FXO Foreign Exchange Office. An FXO interface connects to the public switched telephone network (PSTN) central office and is the interface offered on a standard telephone. An FXO interface is used for trunks, tie lines, or connections to a PSTN CO or PBX that does not support E&M signaling (when local telecommunications authority permits). FXS Foreign Exchange Station. An FXS interface supplies ring, voltage and dial tone for basic telephone equipment, keysets, and PBXs. The FXO interface is useful for offpremises station applications. Greeting The voice recording sent to the caller when a call is answered by voice mail or
by the auto-attendant; usually a single file, and not the concatenation of smaller phrases. part of the software application that runs on the users workstation.
GUI In ShoreTel documentation, the graphical user interface presented to the user as Handled Call A call answered by an employee or a device, such as an auto-attendant or voice mail, as opposed to being blocked or abandoned. Hang Up The act of putting the telephone receiver back on the hook to indicate to the
telephone system that the user is done with the call.
Hold As in on hold; the situation in which a caller is placed in the users call management stack for later handling. Internal Call A telephone call dialed between internal extensions. Java The platform-independent programming language developed by Sun Microsystems for providing complete programs, including animated graphics. Line See Trunk. Loop Start One of the mechanisms used to signal the telephone system that the calling party wants to make a call. Loop start is a completion of the circuit using a set load between the two wires (tip and ring). Message Notification A set of features that inform the user that a new message has arrived
in his or her voice mailbox, such as lighting the call-waiting lamp, paging the user, or dialing a telephone number.
ShoreTel 13.1
413
Glossary
Music-on-Hold (MOH) Background music heard when callers are put on hold, letting them know they are still connected. Most telephone systems have the ability to connect to any sound-producing device (for example, a radio, a cassette player, or a CD player). ShoreTel also supports file-based MOH. On Hook/Off Hook The state of the telephone as being either on the hook (hung up) or off
the hook and seizing the line.
Operator The person who monitors the telephone system and transfers calls to the
appropriate extensions.
Outside Caller See Caller. PBX Private Branch Exchange; a term used by telephone companies to indicate equipment that is located on the customers premises and that can route telephone calls. Permissions Privileges granted to each user with respect to what data, features, menus,
or calling options may be used. Permissions are under the control of the system administrator. telephone.
Physical Extension A common internal extension with an assigned physical port and Prompt For an auto-attendant menu, the result of playing (concatenating) a series of phrases together. PSTN Public Switched Telephone Network; another name for the public telephone
network.
Remote Caller See Caller. Ringback Tone The audible signal given to the caller by the telephone company (or telephone system) to indicate that the remote telephone is ringing. RJ-11 Registered Jack number 11; one of the series of registered jacks and cabling
developed originally by AT&T to standardize the cabling between the telephone and the telephone company lines.
telephone hardware.
Service Provider Interface (SPI) An interface between the operating system and the
Status Bar A text and mini-graphics area, usually at the bottom of a software application window, that is normally used for showing the status of the application or other pertinent information. Stutter Tone An intermittent dial tone provided by the telephone system (as opposed to
the usual constant dial tone); sometimes used to indicate to the user that there are messages in his or her voice mailbox or that a feature (such as call forwarding) is enabled.
T-1 A digital transmission link with a capacity of 1.554 Mbps (1,544,000 bits per
second). A T-1 trunk can normally handle 24 voice conversations, each digitized at 64 Kbps. T-1 lines are used for connecting networks across remote distances.
Telco An abbreviation for telephone company.
414
Glossary

Telephony Application Programming Interface (TAPI) A telephony software interface included in
Microsoft Windows 95, 98, and NT; the operating system that lets applications incorporate telephony control.
Tip and Ring Telephony jargon for the two wires from the telephone system to the
telephone set; also indicates polarity
Trunk Sometimes used synonymously with line or CO line. Traditionally, a trunk from the telephone company connects to a PBX only, and not to a telephone, whereas a line from the telephone company connects to a telephone. For documentation purposes, either term can be used when referring to voice connections from the telephone company. Trunk Hunt Group A term sometimes used to indicate a group of telephone lines
configured by the telephone company to rotate incoming calls among all the lines in search of the next available one. In this way, a company can give out one main number, and all calls to that number will hunt for the next available line or trunk. that are used to execute commands to either the telephony switch, voice mail, or the automated attendant.
TUI Telephone User Interface; a set of defined keystrokes on the telephone keypad
Workstation A personal computer (PC) or similar computer.
ShoreTel 13.1
415
Glossary
416
Index
Symbols
"Use Flash to Route Calls" check box . . . . . . . . . . . . . . . . . 292 analog phone requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 analog service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 analog telephone and trunk cabling . . . . . . . . . . . . . . . . . . 229 analog trunk port setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 analog trunk ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 analog wink-start trunks . . . . . . . . . . . . . . . . . . . . . . . . . .92, 100 ANI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 applet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 area code, configuring for a user . . . . . . . . . . . . . . . . . . . . . . 268 area codes, local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 attach voice mail to message when moved . . . . . . . . . . . 268 audio conference license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 audio input (music on hold) cabling . . . . . . . . . . . . . . . . . . 229 audio output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 audio output (paging and night bell) cabling . . . . . . . . 230 authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Auto-Attendant Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . 88 auto-attendants, multiple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Automated Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 automated call distributor (ADC) calls . . . . . . . . . . . . . . . 281 Automatic Number Identification . . . . . . . . . . . . . . . . . . . . . 92 Automatic Number Identification (ANI) . . . . . . . . . . . . . 105 Avaya PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 avoiding exposure to rain or moisture . . . . . . . . . . . . . . . . 319
Numerics
10 Base-T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 100 Base-T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 10-digit local dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 110 VAC modular power cord . . . . . . . . . . . . . . . . . . . . . . . . . 228 19-inch data rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 26 AWG wire, to avoid risk of fire . . . . . . . . . . . . . . . . . . . . 320 28.8 Kbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176 900 calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 911 calls, planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 dialing plan considerations . . . . . . . . . . . . . . . . . . . . . . .114 emergency calls, exception . . . . . . . . . . . . . . . . . . . . . . . . 115
A
surge protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 account code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 configurable extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 examining outbound calls . . . . . . . . . . . . . . . . . . . . . . . . 131 account code collection service call detail reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 account codes states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 admission control bandwidth, and WANs . . . . . . . . . . . . . 81 Admission Control Bandwidth, calculating . . . . . . . . . . . 81 admission control, defining . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 admission control, two ways to set . . . . . . . . . . . . . . . . . . . . 84 Adobe Acrobat Reader, installing . . . . . . . . . . . . . . . . . . . . . .196 ADSL, and WANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 after-hours call routing . . . . . . . . . . . . . . . . . . . . 88, 89, 92, 94 algorithm, network call routing . . . . . . . . . . . . . . . . . . . . . . .133 allocation, blocks of numbers . . . . . . . . . . . . . . . . . . . . . . . . . .114 American Society of Composers . . . . . . . . . . . . . . . . . . . . . . 230 AMIS protocol support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 protocol support and voice mail . . . . . . . . . . . . . . . . . 283 protocol version 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 send outbound voice mail . . . . . . . . . . . . . . . . . . . . . . . . 284 simplification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 analog connection speeds, modems . . . . . . . . . . . . . . . . . . . .176 analog DID trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 AC
B
bandwidth WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 bandwidth calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 bandwidth management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 client bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 distributed call control signaling . . . . . . . . . . . . . . . . . 64 LANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 virtual LANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 WANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 bandwidth requirements for network . . . . . . . . . . . . . . . . . 42 batch utility public contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 BHCA call volumne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 BHCC call load capacity for switches . . . . . . . . . . . . . . . . . . . . .37 BOOTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67, 68 bootROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 bootROM, downloading for phone . . . . . . . . . . . . . . . . . . . 245 bottlenecks, and traffic shaping . . . . . . . . . . . . . . . . . . . . . . . 64 broadband DSL connectivity, and VPNs . . . . . . . . . . . . . . 74
ShoreTel 13.1
417

bytes per packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Index
components, system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 conference rooms, planning for . . . . . . . . . . . . . . . . . . . . . . . 166 configuration switches, assigning . . . . . . . . . . . . . . . . . . . . .240 configuring SMDI parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Configuring Automatic VLAN Assignment through DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Configuring DHCP for IP phones . . . . . . . . . . . . . . . . . . . . . . 68 configuring external numbers . . . . . . . . . . . . . . . . . . . . . . . . .116 configuring internal numbers . . . . . . . . . . . . . . . . . . . . . . . . . . 113 configuring local area codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 configuring mixed dialing in the same area . . . . . . . . . . .118 configuring networking parameters . . . . . . . . . . . . . . . . . . . 68 configuring ShoreTel voice mail integration using SMDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 configuring the serial connection . . . . . . . . . . . . . . . . . . . . . 299 configuring the ShoreTel server for SMDI . . . . . . . . . . . . 295 configuring voice switches for IP phone . . . . . . . . . . . . .240 connectivity between locations . . . . . . . . . . . . . . . . . . . . . . . . .66 connector pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 consolidated long distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Contact Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 conversation, and latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 coordinated dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 coordinated dialing plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 copyright laws, US . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 cost-effective phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 country code applied in some countries for directing calls to a trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315 country codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 CPU, and media encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 creating a trunk group, SMDI . . . . . . . . . . . . . . . . . . . . . . . . . . 293 creating a user group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 creating trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Cut-Over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 cut-over coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 monitoring personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 scheduling on-site team . . . . . . . . . . . . . . . . . . . . . . . . . . 305 cut-over implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 cut-over worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 cut-over, to ShoreTel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
C
cable modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 cabling contractor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 cabling installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 cabling, general overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 call centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Call Detail Records, and disk usage . . . . . . . . . . . . . . . . . . . 188 Call Handling Delegation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150 call permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 all calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 commas or semicolons . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 internal only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 wild cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Call permissions parameters International Long Distance . . . . . . . . . . . . . . . . . . . . . 130 Local Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 National Long Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 call permissions, restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . 130 call routing after hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88, 89 auto attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 blended . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 DID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 call sender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 call volume estimates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 caller ID name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 outbound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 caller ID information collecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 caller ID number, international support for . . . . . . . . . .173 canonical format, converting to . . . . . . . . . . . . . . . . . . . . . . . . 117 canonical format, external numbers . . . . . . . . . . . . . . . . . . 116 carrier code definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315 in selected countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315 Carrier Select numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 category 5 cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 CD player . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Centrex lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 channel service unit (CSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 checklist, for trunking cut-over . . . . . . . . . . . . . . . . . . . . . . . 306 Citrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321 Citrix servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 CLASS message waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 client bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 client software install procedure . . . . . . . . . . . . . . . . . . . . . 254 COM port baud rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 COM port setup, SMDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 command center, setting up for cut-over . . . . . . . . . . . . . 306 communications, encrypting . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
D
data network, integrating with . . . . . . . . . . . . . . . . . . . . . . . . . .41 Data-entry fields conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 defining 10-digit dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 defining admission control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 defining trunk services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 delay in the PSTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 delete voice mail from message when moved . . . . . . . 269 demilitarized zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 denial-of-service attacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 deployment team Electrician . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 IT Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
418
Index
project manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Service Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 ShoreTel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 System Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 determining the number of trunks . . . . . . . . . . . . . . . . . . . . .28 DHCP automatic VLAN assignment . . . . . . . . . . . . . . . . . . . . . .72 country and language numbers for option 156 . . .69 option 156 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 DHCP configuration for IP phones . . . . . . . . . . . . . . . . . . . . .68 DHCP on the ShoreTel Server . . . . . . . . . . . . . . . . . . . . . . . . . .196 DHCP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 DHCP server, and IP phones . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 DHCP server, IP address assignment . . . . . . . . . . . . . . . . . . . .67 DHCP vendor option 155 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Dialed Number Identification Service (DNIS) . . . . . . . 106 dialing 911 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 dialing configuration, planning . . . . . . . . . . . . . . . . . . . . . . . .114 dialing coordinated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 dialing parameters, TAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 dialing plan considerations for international deployment . . 314 dialing plan, coordinated . . . . . . . . . . . . . . . . . . . . . . . . .279, 281 dialing rules, for a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Dial-Up Modems, and WANs . . . . . . . . . . . . . . . . . . . . . . . . . . .67 DID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 DID numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315 Digit collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 digit collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 digit collection rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 digit collection, defining for internal numbers . . . . . . . 115 digit collection, ending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Digit manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 digit manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119, 129 Digit Manipulation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 digit manipulation, defining . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 digit translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 digit translation table, creating . . . . . . . . . . . . . . . . . . . . . . . .291 digit translation, functionality . . . . . . . . . . . . . . . . . . . . . . . . 290 Digital Loop-Start Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 digital trunk tie line integration . . . . . . . . . . . . . . . . . . . . . . 280 digital trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 Digital Wink-Start Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Direct Inward Dial (DID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Direct Inward Dial call routing . . . . . . . . . . . . . . . . . . . . . . . . .92 Direct Inward Dial trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 disk caching, enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Displaying ShoreTel IP Phone Settings . . . . . . . . . . . . . . . 245 Distributed Call Control Signaling . . . . . . . . . . . . . . . . . . . . 64 distributed server maintenance page, accessing . . . . . .197 distributed server, software installation . . . . . . . . . . . . . 209 Distributed ShoreWare Servers . . . . . . . . . . . . . . . . . . . . . . . . .25 distributed voice mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 DNIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 DTMF signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

echo cancellation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 echo canceller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 echo packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 e-commerce, and security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 electrical storm, postponing installation . . . . . . . . . . . . . 320 electricity, safety with . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 email, for notifying users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 emergency 911 calls, exceptions . . . . . . . . . . . . . . . . . . . . . . . . 115 emergency calls, planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 emergency numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74, 75 enabling during a call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 no support with SoftSwitch . . . . . . . . . . . . . . . . . . . . . . . .78 end digit collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119 End User License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . 259 engineering an IP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 enterprise telephony features . . . . . . . . . . . . . . . . . . . . . . . . . .159 enterprise-wide coordinated dialing plan . . . . . . . . . . . . 279 Environmental and Infrastructure Analysis . . . . . . . . . . . 17 Environmental Requirements, ShoreTel voice switch . . 226 environmental specifications . . . . . . . . . . . . . . . . . . . . . . . . . 226 estimating call volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Ethernet framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 Ethernet cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Ethernet network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 explicit carrier selection dialing . . . . . . . . . . . . . . . . . . . . . . .119 extension and mailbox license . . . . . . . . . . . . . . . . . . . . . . . . 271 extension length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 extension lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114, 115 extension-only license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 external numbers, configuring . . . . . . . . . . . . . . . . . . . . . . . . .116
F
fault tolerance, two levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 fax and modem calls, zero packet loss . . . . . . . . . . . . . . . . . . 61 fax handling, planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 fax machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Hewlett-Packard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 IP network quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 fax server integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 fax server integration, configuring . . . . . . . . . . . . . . . . . . . 144 Fax Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 fax server, using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Find Me call handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 firewalls, and corporate networks . . . . . . . . . . . . . . . . . . . . . .76 firewalls, and VoIP traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 firmware, phone download . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 flash button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 four seconds password entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244 frame relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 frame relay, and WANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 France, supported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 front-end web servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 FtpServers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
E
E1 PRI service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 E1 PRI trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
ShoreTel 13.1
419
Index
189 installing ShoreTel Communicator on Citrix or WTS . . 323 installing voice mail integration . . . . . . . . . . . . . . . . . . . . . . 269 InstallShield Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259, 323 integrated voice mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 integrating legacy voice mail with SMDI . . . . . . . . . . . . . 287 integration plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 integration with data network . . . . . . . . . . . . . . . . . . . . . . . . . .41 internal numbers, configuring . . . . . . . . . . . . . . . . . . . . . . . . . 113 Internal Only call permissions . . . . . . . . . . . . . . . . . . . . . . . . 130 international dialing plan considerations . . . . . . . . . . . . . . . . . . . . . . 314 telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 international (01x) dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118 international deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 International Long Distance call permission . . . . . . . . 130 international planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Internet information server (IIS) default web site . . . 196 inter-site calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 IP address outside of range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 IP address assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 DHCP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 firewalls with NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 IP Address Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 IP address range, defining for IP phone . . . . . . . . . . . . . . . 241 IP address, static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 IP networks, ready for VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 IP parameters, displaying for phone . . . . . . . . . . . . . . . . . . 245 IP phone installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 IP phone cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 IP phone support, and voice switches . . . . . . . . . . . . . . . . .240 IP phones recommendations for installation . . . . . . . . . . . . . . . 239 IP phones, associating with user group . . . . . . . . . . . . . . . 246 IPSEC, and tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 ISDN BRI, and WANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 ISDN PRI, call routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 ISP limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 issues with voice traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Italy, supported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
G
G.711 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 176 G.729a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 G.729a voice encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81, 83 gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 geographic region, dialing plan . . . . . . . . . . . . . . . . . . . . . . . . 116 Germany, supported features . . . . . . . . . . . . . . . . . . . . . . . . . .173 global voice network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 GMT Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 GPO use with ShoreTel Communicator installation . 256 group policy object, see GPO . . . . . . . . . . . . . . . . . . . . . . . . . . 256
H
hairpinning supported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 hard disk space utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187 hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . .179, 247 headsets for operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166 heartbeat interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Hewlett-Packard fax machines . . . . . . . . . . . . . . . . . . . . . . . .176 high voltage components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 higher-density trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 hold button, MOH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 hostname, HQ server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 humidity, operating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Hunt Group Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153 as a Call Forward Destination . . . . . . . . . . . . . . . . . . . . .153 busy state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152 common line monitoring . . . . . . . . . . . . . . . . . . . . . . . . . 154 configurable hunting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153 distribution of calls to backup operators . . . . . . . .153 Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 hunt groups, call routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 Hypertext links conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
I
ICMP flood attacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 IDSL, and WANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 illegal traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 implementing cut-over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 import public contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 important safety instructions . . . . . . . . . . . . . . . . . . . . . . . . . .319 importing Outlook contacts to quick dial . . . . . . . . . . . . 270 inbound and outbound services, consolidation . . . . . . 280 Input Power, ShoreTel voice switch . . . . . . . . . . . . . . . . . . 224 Installation Assembling the Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 installation IP phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 installation procedure, desktop . . . . . . . . . . . . . . . . . . . . . . . 254 Installation Readiness Review . . . . . . . . . . . . . . . . . . . . . . . . . 20 installing Microsoft Windows Server 2003 components
J
jitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42, 58, 176 and latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 changing buffer size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 compensating for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 underflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 jitter buffer, non-configurable . . . . . . . . . . . . . . . . . . . . . . . . . 60 jitter for voice switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
K
K56Flex/V.90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 key components, cabling voice network . . . . . . . . . . . . . 230 key considerations addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
420
Index
bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 service levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

media encryption security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 supported hardware platforms . . . . . . . . . . . . . . . . . . . .78 memorized phone number management . . . . . . . . . . . . 270 message waiting indicator (MWI) . . . . . . . . . . . . . . . . . . . . 286 Microsoft Outlook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253, 268 mini-stereo input connector, 3.5 mm . . . . . . . . . . . 229, 230 mission-critical resources, protection . . . . . . . . . . . . . . . . . .77 mixed dialing, configuring in same area . . . . . . . . . . . . . .118 model number, ShoreTel switch . . . . . . . . . . . . . . . . . . . . . . 223 modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 MOH source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159 multi-line phones, extension monitoring . . . . . . . . . . . . 166 multi-site enterprise keys, renaming . . . . . . . . . . . . . . . . . 271 Multisite Implementation, topologies . . . . . . . . . . . . . . . . . 80 multi-site integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 multi-vendor network environment . . . . . . . . . . . . . . . . . . 42 music on hold, streaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Music-on-hold audio input port . . . . . . 368, 371, 375, 395, 398, 402 music-on-hold source, audio input port . . . . . . . . . . . . . . 234 music-on-hold, testing for cut-over . . . . . . . . . . . . . . . . . . . 306 mute button, and speakerphone . . . . . . . . . . . . . . . . . . . . . . 174
L
L2F, and tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 L2TP, and tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 language licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 language number for DHCP option 156 . . . . . . . . . . . . . . . .69 language numbers for configuring DHCP option 156 .69 LANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58, 59 end-to-end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 traversing switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 latency and jitter requirements . . . . . . . . . . . . . . . . . . . . . . . . 42 Layer 2 IP Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Layer 3 - DiffServ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Layer 4 UDP 5004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Layer2Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 leased T1, and WANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 legacy integration external voice mail configuration . . . . . . . . . . . . . . . 293 ShoreTel voice mail configuration . . . . . . . . . . . . . . 293 legacy PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 legacy systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 license audio conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Service Appliance 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 web conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 license agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 license types, three . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 licenses, purchasing for users . . . . . . . . . . . . . . . . . . . . . . . . . .271 linear broadband encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 live operator, directing calls to . . . . . . . . . . . . . . . . . . . . . . . . . .88 lobby phones, planning for . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166 local area codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Local Area Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Local Only call permission . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 local trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 log files, and disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 logical terminal number, and extensions . . . . . . . . . . . . 288 logical terminal number, identifying PBX port . . . . . . 295 long distance, consolidated . . . . . . . . . . . . . . . . . . . . . . 283, 302 long-distance dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 lost packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176 lower-density trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Lucent PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
N
n11 dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118 National Long Distance call permission . . . . . . . . . . . . . . 130 NetScreen-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 Network Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . .77 network call routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 network call routing algorithm . . . . . . . . . . . . . . . . . . . . . . . 133 Network Call Routing page . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 network outages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 network performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 network requirements bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 jitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 packet loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 network requirements, for fax . . . . . . . . . . . . . . . . . . . . . . . . 143 Network Topologies, examples . . . . . . . . . . . . . . . . . . . . . . . . .79 network topology, determining . . . . . . . . . . . . . . . . . . . . . . . . 24 night bell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Nightbell audio output port . . . . . 368, 371, 375, 395, 398, 402 Nortel PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 notification, via email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
M
MAC Ethernet address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 mailbox, purchasing license without phone extension . 271 mailbox-only license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 maintenance cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 maintenance port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 maintenance port, switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 map extension ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 mean time before failure (MTBF) . . . . . . . . . . . . . . . . . . . . . 226 Media Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
O
online documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 operating humidity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 operating temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 operating, call directing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Operator Assisted calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 operator call routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 operator digit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 operator-assisted dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
ShoreTel 13.1
421

operators, headsets for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166 option 155 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 option 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 ordering service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 outbound caller ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 outbound calls, and analog wink-start . . . . . . . . . . . . . . . . .96 Outlook folder, moving messages . . . . . . . . . . . . . . . . . . . . . 268 Outlook, Microsoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 overhead paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Index
Q
quick dial, importing Outlook contacts . . . . . . . . . . . . . . 270
R
rack installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223, 232 rack overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 racks and cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 receptionists, telephony needs . . . . . . . . . . . . . . . . . . . . . . . . 166 recommendations for installing server . . . . . . . . . . . . . . . 179 reliability and availability, ShoreTel voice switch . . 226 requirements of toll-quality voice . . . . . . . . . . . . . . . . . . . . . 42 RESET# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Resource Scheduling and Tracking . . . . . . . . . . . . . . . . . . . . . 18 restart desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 restrictions, call permissions . . . . . . . . . . . . . . . . . . . . . . . . . . 130 resultant voice quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 return call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 RJ-21X cable retainer installation . . . . . . . . . . . . . . . . . . . . . 235 RJ-48C cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 routing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 routing, specify parameters for . . . . . . . . . . . . . . . . . . . . . . . 134 RS-232 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 RTP data, encrypting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 RTP header compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 RTP packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 rules, digit collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
P
packet loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 packet loss requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 packet loss, for fax and modem calls . . . . . . . . . . . . . . . . . . . 61 packet loss, zero tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 packets, lost during conversation . . . . . . . . . . . . . . . . . . . . . .176 packet-to-circuit conversions . . . . . . . . . . . . . . . . . . . . . . . . . .177 Paging system audio output port . . . . 368, 371, 375, 395, 398, 402 paging system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 parity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 patch panel installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 PBX link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286, 299 PBXLink, connecting to the PBX . . . . . . . . . . . . . . . . . . . . . . 299 PBXs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 performance, network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 phillips screwdriver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 phone and modem options control panel applet . . . . 268 phone extension license, requesting without mailbox . . 271 Physical Requirements, ShoreTel voice switch . . . . . . 224 pinouts, connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 planning dialing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 planning fax handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 poor voice quality, causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Power and Heat Dissipation, ShoreTel voice switch . 225 Power Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 power cord, protecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 power failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 power loss, IP phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 PPTP, and tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 preventing fire or shock hazard . . . . . . . . . . . . . . . . . . . . . . . .319 PRI trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 PRI, and calling number information . . . . . . . . . . . . . . . . 280 prioritizing voice traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 private numbers, not in System Directory . . . . . . . . . . . 148 proxy sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 PSTN services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 PSTN, delay in the . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 public contacts batch utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 public key infrastructure, encryption . . . . . . . . . . . . . . . . . . 75 punch-down blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 purchasing a language license . . . . . . . . . . . . . . . . . . . . . . . . 272
S
safety considerations, voice switch installation . . . . . 319 safety, electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 SDSL, and WANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 secure communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 security media encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 security appliances, integrated . . . . . . . . . . . . . . . . . . . . . . . . . .76 security policies, firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 serial connection, configuring . . . . . . . . . . . . . . . . . . . . . . . . . 299 serial link, and voice mail integration . . . . . . . . . . . . . . . . 299 serial port settings, extracting from Windows . . . . . . . 299 server performance, optimizing . . . . . . . . . . . . . . . . . . . . . . . 221 server, distributed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 servers, terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 service level agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 service provider, SLAs with . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 service, analog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 service, E1 PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 service, T1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 service, T1 PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 services telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 services, recommendations for ordering . . . . . . . . . . . . . . 111 seven-digit local dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 ShorePhone-IP110 manually configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . .244 resetting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 ShorePhone-IP210
422
Index
manually configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 resetting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 ShorePhone-IP530/560 manually configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 resetting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 ShorePhones simplified design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 ShoreTel remote TAPI service provider . . . . . . . . . . . . . . . . . . . . 325 ShoreTel 220E1 switch telephone ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 ShoreTel 220T1 switch telephone ports . . . . . . . . . . . . . . . . . . . . . . . . .365, 375, 378 ShoreTel 220T1A switch telephone ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 ShoreTel 50 switch telephone ports . . . . . . . . . . . . . . . . . . . 351, 355, 362, 385 ShoreTel 90 switch telephone ports . . . . . . . . . . . . . . . . . . . . . . . . .348, 358, 381 ShoreTel Communicator, starting . . . . . . . . . . . . . . . . . . . . 268 ShoreTel Conference Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . .163 ShoreTel server IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189 ShoreTel server, configuring for legacy voice mail . . 288 ShoreTel system, plug-and-play . . . . . . . . . . . . . . . . . . . . . . 227 ShoreTel voice switch, address assignment . . . . . . . . . . . .67 signaling overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 simplified message desk interface (SMDI) . . . . . . . . . . . 283 simplified message desk interface mode ShoreTel as PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 single site integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 single site key, renaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 single-extension plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 single-site implementation, topologies . . . . . . . . . . . . . . . . .79 SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 barge-in on SIP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 call recording on SIP trunks . . . . . . . . . . . . . . . . . . . . . . 329 silent coach on SIP trunks . . . . . . . . . . . . . . . . . . . . . . . . 329 silent monitor on SIP trunks . . . . . . . . . . . . . . . . . . . . . 329 SIP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Site page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Sites and Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 smart Ethernet switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 SMDI functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 supported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 SMDI mode ShoreTel voice mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 SMDI parameters, configuring . . . . . . . . . . . . . . . . . . . . . . . . 295 SMDI protocol support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 SMDI protocol support, and voice mail . . . . . . . . . . . . . . . 284 SMDI, configuring legacy voice mail integration . . . . 287 SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 SNTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189 Spain, supported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 Spanish language license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 Spanning Tree protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 start bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 starting the ShoreTel Communicator application . . . 268

static IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 static IP addresses, and servers . . . . . . . . . . . . . . . . . . . . . . . . . .67 status screen, client installation . . . . . . . . . . . . . . . . . . . . . . . 259 stereo jack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 storage temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 supported PBXs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Avaya . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Mitel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 NEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Nortel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Siemens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 surge protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 switch configuration, and Director . . . . . . . . . . . . . . . . . . . 235 switch models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 switched Ethernet network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 system components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 system control panel (Outlook tab) . . . . . . . . . . . . . . . . . . . 269 System Load and Configuration . . . . . . . . . . . . . . . . . . . . . . . . 19
T
T1 lines, for modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 T1 PRI service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 T1 service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 tandem trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 TAPI dialing parameters, configuring . . . . . . . . . . . . . . . . 268 TDM filtering, and media encryption . . . . . . . . . . . . . . . . . .78 team, for monitoring cut-over . . . . . . . . . . . . . . . . . . . . . . . . . 307 telco cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 telephone patch panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Telephone requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 telephone requirements, determining . . . . . . . . . . . . . . . . . .27 telephone service, ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 telephones, testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Telephony Features call recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 intercom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Make Me conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Music on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159 night bell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 overhead paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161 paging groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161 telephony features, enterprise . . . . . . . . . . . . . . . . . . . . . . . . . .159 teleworker sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24, 26 teleworkers check box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 teleworkers, telephony needs . . . . . . . . . . . . . . . . . . . . . . . . . 167 temperature operating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 terminal servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Citrix and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 tie trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Time Services, SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 toll-quality voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 toll-quality voice, requirements . . . . . . . . . . . . . . . . . . . . . . . . 42 topology diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 topology, VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 traffic calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 traffic calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 traffic shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
ShoreTel 13.1
423

traffic shaping, reduce bottlenecks . . . . . . . . . . . . . . . . . . . . 64 transfer using flash feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 trunk access codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Trunk Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 trunk considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89, 94 trunk digit manipulation, specifying . . . . . . . . . . . . . . . . . . 119 trunk features, understanding . . . . . . . . . . . . . . . . . . . . . . . . 103 trunk group edit page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 Trunk Group edit page, call routing . . . . . . . . . . . . . . . . . . 134 trunk ports 348, 351, 355, 358, 362, 365, 368, 372, 375, . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378, 381, 385 Trunk requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 trunk requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 trunk services, defining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 trunking cut-over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 trunking, tandem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 trunks analog wink-start . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92, 100 digital loop-start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 digital wink-start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92, 101 E1 PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 T1/E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 trunks, conditions for availability to hunt groups . . .132 trunks, determining requirements . . . . . . . . . . . . . . . . . . . . . .28 trunks, digital . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 trunks, installing before cut-over . . . . . . . . . . . . . . . . . . . . . 305 TSPinstall utility, running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Index
virtual LANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Virtual Private Network (VPN) . . . . . . . . . . . . . . . . . . . . . . . . .73 VLAN Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Voice Communications System Analysis . . . . . . . . . . . . . . 16 voice encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 G.729a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Voice encoding scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 voice mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 COM port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 message waiting light . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 voice mail integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 voice mail storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 voice mail systems, multiple . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 voice mail, AMIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 voice mail, and disk usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 voice mail, SMDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 voice quality, resultant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 voice switch requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 VPNs extranets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 intranets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 remote access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
W
WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 bandwidth requirements . . . . . . . . . . . . . . . . . . . . . . . . . . .66 connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 connectivity between locations . . . . . . . . . . . . . . . . . . . .66 outages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 WAN bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 WAN links, flooding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 WANs ADSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 cable modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 dial-up modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 frame relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 ISDN BRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 WANs managing bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . .63 WANs, and IDSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 WANs, and leased T1s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 WANs, SDSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 web conference license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 wild-card characters, with call permissions . . . . . . . . . . 131 Windows servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Windows Server 2003 components, installing . . . . . . 189 Wizard, for client installation . . . . . . . . . . . . . . . . . . . . . . . . . 259 Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156 agent multiplicity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156 call monitor and barge in . . . . . . . . . . . . . . . . . . . . . . . . . .157
U
unassigned IP Phones, associating with user group . . 246 uninterruptable power supply (UPS) . . . . . . . . . . . . . . . . . 228 unique dialing plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 United Kingdom, supported features . . . . . . . . . . . . . . . . . .173 United State, outside of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 unroutable numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 upgrade procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 UPS, uninterruptable power supply . . . . . . . . . . . . . . . . . . 224 user license types extension and mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 extension-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 mailbox-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 user licenses, purchasing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 user licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 using a fax server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 utilization, hard disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
V
variation of latency, jitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 velcro strap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 vendor specific DHCP option 156 . . . . . . . . . . . . . . . . . . . . . 244 ventilation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 vertical service code dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Vertical Service Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 viewing IP address range for a site . . . . . . . . . . . . . . . . . . . . 241
424
Index
ShoreTel 13.1
425
Index
426

Shoretel 13.1 Install Guide

Uploaded by

Copyright:

Available Formats

Shoretel 13.1 Install Guide

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

Shoretel 13.1 Install Guide

Uploaded by

Copyright:

Available Formats

ShoreTel 13.

1 Planning and Installation Guide

Document and Software Copyrights

2.4 2.5 2.6 2.7

CHAPTER 3: NETWORK REQUIREMENTS AND PREPARATION . . . . . . . . . . . . 41

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Understanding the Requirements for Toll-Quality Voice . . . . . . . . . . . . 42

WAN Technology Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Planning and Installation Guide 3.3.7 3.3.8 3.3.9

3.4 3.5 3.6 3.7 3.8

3.9 3.10 3.11 3.12 3.13

3.12.1 3.12.2 3.13.1 3.13.2 3.13.3

Computing Admission Control Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

CHAPTER 4: ROUTING CALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Direct All Calls to a Live Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Direct All Calls to Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Blended Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Analyze Outbound Call Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Planning and Installation Guide

CHAPTER 5: TRUNK PLANNING AND ORDERING . . . . . . . . . . . . . . . . . . . . 97

Understanding Trunk Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Performing Traffic Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 Ordering Telephone Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

CHAPTER 6: DIALING PLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

CHAPTER 7: NETWORK CALL ROUTING . . . . . . . . . . . . . . . . . . . . . . . . . 129

Planning and Installation Guide

CHAPTER 8: PLANNING APPLICATIONS AND SERVICES . . . . . . . . . . . . . . . 135

8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.10

Planning Fax Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Using a Fax Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Switch Support for Bridged Call Appearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

8.11 8.12 8.13

Pickup Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

8.13.1 8.13.2 8.13.3 8.13.4 8.13.5 8.13.6

Enterprise Telephony Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

ShoreTel Enterprise Contact Center Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 163

CHAPTER 9: TELEPHONE PLANNING AND ORDERING . . . . . . . . . . . . . . . . 165

Planning and Installation Guide

ShoreTel IP Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Analog Phone Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Fax Machines and Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

CHAPTER 10: SERVER REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . 179

ShoreTel SBE System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182

Requirements for VMware Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

10.6.1 10.6.2 10.6.3

10.7.1 10.7.2 10.7.3 10.7.4 10.7.5

Preparing Your Server for the ShoreTel Installation . . . . . . . . . . . . . . . . . . 189

ShoreTel Mobility Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Third-Party Applications Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Planning and Installation Guide

CHAPTER 11: SHORETEL SERVER INSTALLATION . . . . . . . . . . . . . . . . . . . 199

Checking Server for Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

11.2.1 11.2.2 11.3.1 11.3.2

Installing the Headquarters Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . 200

Running the Compatibility Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Installing the Distributed Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

11.6.1 11.6.2 11.6.3

11.6.4 11.6.5 11.7.1

Ensuring Proper Server Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221

Setting the Server to Maximize for Network Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . .221

CHAPTER 12: SITE REQUIREMENTS AND PREPARATION . . . . . . . . . . . . . . 223

Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Voice Switch Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224