Mitel 3300 ICP Hardware

Download

Page 1

HARDWARE GUIDE

Page 2

Page 3

Table of Conten

Chapter 1 - Before You Begin

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Printing the Hardware User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

What’s New in this Release? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Copyright . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Safety Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2 - Specifications

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Technical Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Technical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Transmission Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Loss and Level Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Tone Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Networking Voice Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

LAN/WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

LAN Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

WAN Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Plan the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3300 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Mitel Networks™ 3300 Controller Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

250 User System without Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

250 User System with 32 Compression Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

250 User System with 64 Compression Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

700 User System without Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

700 User System with 32 Compression Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

700 User System with 64 Compression Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

E2T Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Mitel Networks 3300 Controller Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

3300 Controller Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

3300 Controller Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

3300 Controller IRQ Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

3300 Controller PCB Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

3300 Network Services Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Mitel Networks 3300 Universal NSU Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

3300 Universal NSU Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

3300 Universal NSU DIP Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Mitel Networks 3300 R2 NSU Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

3300 R2 NSU Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

3300 R2 NSU DIP Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Mitel Networks 3300 BRI NSU Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

3300 BRI NSU Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Release 3.2 i

Page 4

300 ICP Hardware User Guide

Mitel Networks 3300 NSU Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3300 NSU Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3300 NSU Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

3300 NSU Pin Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

3300 Analog Services Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Mitel Networks 3300 Universal ASU Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Mitel Networks 3300 ASU Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

3300 ASU and Universal ASU Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3300 ASU and Universal ASU Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3300 ASU and Universal ASU Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

3300 ASU and Universal ASU Pin Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

ONS Line Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

LS Trunk Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Music On Hold (3300 Universal ASU only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Paging (3300 Universal ASU only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

System Fail Transfer (3300 Universal ASU only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Peripheral Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Peripheral Unit Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Peripheral Unit Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Peripheral Unit Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Peripheral Unit Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Peripheral Unit Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

SUPERSET™ HUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Digital Service Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Digital Service Unit Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Digital Service Unit Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Digital Service Unit Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Digital Service Unit Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Digital Service Unit Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Telephone Power Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Telephone Power Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

3300 In-line Power Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

3300 Power Dongle (cisco compliant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

PowerDsine In-line Power Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Chapter 3 - Installing

Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Required Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Installation Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Parts and Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Information and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Uninterruptible Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

System Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Installation Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

iv Release 3.2

Page 5

Table of Conten

Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Install the 3300 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Install the System ID Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Configure the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Set the 3300 Controller IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Install the 3300 Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Install and Configure the Java Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Install the 3300 Universal NSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Install the 3300 Universal NSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Install for PRI/Q.SIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Install Direct Connect Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Driver for Windows 95 and Windows 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Driver for Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Create a Dial-up Network Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Dial-up Connection for Windows 95 or Windows 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Dial-up Connection for Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Install the 3300 R2 NSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Install the 3300 BRI NSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Setting Up the Maintenance PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

NSU Chaining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5

Install the 3300 Universal ASU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Install the 3300 ASU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Install the Peripheral Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Overview of the Peripheral Unit Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Unpack, Position, and Ground the Peripheral Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Peripheral Unit Card Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Connect Fiber Cable to the Peripheral Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Peripheral Unit Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Power Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Install Peripheral Interface Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Cable the Unit to the MDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Peripheral Interface Cabling Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

USOC Connector Pin Designations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Card Connections to Cross-Connect Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Card Slot 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Card Slot 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Card Slot 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Card Slot 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Card Slot 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Card Slot 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Card Slot 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Card Slot 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Card Slot 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Card Slot 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Release 3.2

Page 6

300 ICP Hardware User Guide

Card Slot 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6

Card Slot 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 7

Install the SUPERSET HUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Overview of the SUPERSET Hub Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Install the Peripheral Slot FIM Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Install the SUPERSET HUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Install the Digital Service Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Overview of the Digital Service Unit Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Unpack, Position, and Ground the DSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

DSU Card Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Connect Fiber Cable to the DSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Install DSU Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Interface Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

DS1 Interface Assembly and Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

CEPT Interface Assembly and Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Install Wireless Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Install Symbol NetVision MiNET Phone Administrator Tool . . . . . . . . . . . . . . . . . . . . . 174

Install 3300 ICP as a Stand-alone IP Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Install 3300 ICP as a Stand-alone Voice Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Install the 3300 In-Line Power Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Rack Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Shelf Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Powering Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Connecting Cables to the In-Line Power Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Connecting Cables to End Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Install the 3300 In-Line Power Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Install 3300 Power Dongle (cisco compliant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Install 3300 Power Dongle (cisco compliant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Pre-Release 3.2 IP Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Mixed Release 3.1 and 3.2 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Chapter 4 - Install Upgrades and FRUs

Install Upgrades and FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Controller Upgrade Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

250 User to 700 User System - No Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

250 User System - Add 32 Compression Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

250 User System - Add 64 Compression Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

700 User System - Add 32 Compression Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

700 User System - Add 64 Compression Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Upgrade SX-2000

Upgrade SX-2000 MICRO LIGHT to 3300 ICP Hardware . . . . . . . . . . . . . . . . . . . . . . 194

Upgrade 3200 ICP to 3300 ICP Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

vi Release 3.2

LIGHT to 3300 ICP Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Page 7

Table of Conten

Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Upgrade Procedure (Release 3.0 to 3.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Upgrade SX-2000 LIGHT to 3300 ICP Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Upgrade SX-2000 MICRO LIGHT to 3300 ICP Software . . . . . . . . . . . . . . . . . . . . . . . 197

Upgrade 3200 to 3300 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Field Replaceable Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Peripheral Node FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Chapter 5 - Programming

Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Overview of Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Use IMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Chapter 6 - Troubleshooting

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Troubleshoot the 3300 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

System Hardware Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Troubleshoot the 3300 Universal NSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Troubleshoot the 3300 R2 NSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Troubleshoot the 3300 BRI NSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Troubleshoot the 3300 Universal ASU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Troubleshoot the 3300 ASU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Troubleshoot the 3300 In-Line Power Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Peripheral Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Troubleshoot Fiber Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Troubleshoot the DID Loop/Tie Trunk Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Troubleshoot the DNI Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Troubleshoot the DTMF Receiver Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Troubleshoot E&M Trunk Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Troubleshoot LS/GS Trunk Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Troubleshoot the ONS Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Troubleshoot the ONS CLASS/CLIP Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Troubleshoot the OPS Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

DSU Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Troubleshoot Fiber Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Troubleshoot the BRI Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Troubleshoot the CEPT/DS1 Formatter Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Troubleshoot the Conference Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Troubleshoot the PRI Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Troubleshoot the R2 Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Release 3.2 v

Page 8

300 ICP Hardware User Guide

viii Release 3.2

Page 9

Chapter 1

Before You Begin

Page 10

300 ICP Hardware User Guide

Release 3.2

Page 11

Before You Begin

Printing the Hardware User Guide

Y ou can access a printable version of the Hardware User Guide from the System Administration

Tool Help and from our web site.

Note: Y ou must have Adobe Acrobat® Reader to view and print the Hardware User Guide. If you need a copy of Adobe Acrobat Reader, it is available for download at http://www.adobe.com/acrobat.

Go to What’s New in this Release? to find a list of changes to software and hardware from one

product version to the next.

What’s New in this Release?

3300 ICP Release 3.2:

Before You Beg

• Single software build: select your country to set the appropriate language, dialing plan, tone plan, and loss & level plan.

• IP-TDM (E2T) G.729 compression

• Optimized system performance: 300 MHz E2T and RTC

• Symbol wireless telephones

• 3300 ICP as a Stand-alone Wireless Gateway

• 3300 ICP as a Stand-alone Voice Mail

• Range programming to simplify the addition, change, or deletion of repetitive or incremental values

• Telephone power options

• Personal and Corporate Directories on the 5140 IP Appliance

• System Hardware Profile to view information about installed hardware

• Controller upgrade options for capacity, version, and/or compression

• ASU and Universal ASU to support the European market

3300 ICP Release 3.1:

• Migration of SX-2000

LIGHT to 3300 ICP

• Migration of SX-2000 MICRO LIGHT to 3300 ICP

• Migration of 3200 ICP to 3300 ICP

• Peripheral Node suppo rt

• Digital Service Unit support

Release 3.2

Page 12

300 ICP Hardware User Guide

• NSU Chaining

• 5001 IP Phone and 5005 IP Phone

• Security

Disclaimer

The information contained in this document is believed to be accurate in all respects but is not warranted by Mitel Networks Corporation (MITEL®). The information is subject to change without notice and should not be construed in any way as a commitment by Mitel or any of its affiliates or subsidiaries. Mitel and its affiliates and subsidiaries assume no responsibility for any errors or omissions in this document. Revisions of this document or new editions of it may be issued to incorporate such changes.

Trademarks

Mitel Networks, MiTAI, SUPERSET, SX-2000 are trademarks of Mitel Networks Corporation.

Windows and Microsoft are trademarks of Microsoft Corporation.

Java is a trademark of Sun Microsystems Incorporated.

Adobe Acrobat Reader is a registered trademark of Adobe Systems Incorporated.

Other product names mentioned in this document may be trademarks of their respective companies and are hereby acknowledged.

Safety Instructions

You can access a printable version of the Safety Instructions from the Hardware User Guide Help and from our web site.

Note: You must have Adobe Acrobat® Reader to view and print the Safety Instructions. If you need a copy of Adobe Acrobat

http://www.adobe.com/acrobat

Reader, it is available for download at

Release 3.2

Page 13

Chapter 2

Specifications

Page 14

300 ICP Hardware User Guide

Release 3.2

Page 15

Specifications

Technical Information

Technical Characteristics

Signaling and Supervisory Tones

The standard range of programmed tones are composed of

• 12 DTMF sets of tones

• 1 set of tones that form part of the call progress tone plan

• 1 test of 1004 Hz (digital milliwatt).

DTMF Signaling

Input Signaling: The system is capable of accepting and repeating the standard DTMF tones as specified in EIA/TIA 464-B.

Specification

Output Signaling: The Mitel Networks 3300 ICP meets the output signaling requirements as

specified in EIA/TIA 464-B .

DTMF Output Signaling as specified by EIA/TIA 464-B

frequency deviation 1 percent tone duration greater than 40 ms interdigit time greater than 40 ms level, low group greater than -10 dbm level, high group greater than -8 dbm level, low group and high group combined less than +2 db level, third greater than 40 db frequency below dtmf signal twist less than 4 db

Time-Out Information

The system is capable of responding to, or providing, the following supervisory conditions:

• Switchhook flashes having a duration of between 160 ms and 1500 ms (as programmed) to activate Transfer/Consultation/Hold/Add-On features.

• Call transfer dial tone can be obtained by generating a calibrated flash. This method is recognized internationally and is generated in one of three ways:

- use a flash-hook for telephones connected to ONS circuits. Upper and lower detection

thresholds for switchhook flash are programmable between 60 ms and 500 ms, and between 60 ms and 1500 ms respectively.

- use the calibrated flash button (for equipped telephones)

Release 3.2

Page 16

300 ICP Hardware User Guide

- dial the digit ‘1’ on an ordinary rotary telephone.

• Station switchhook flashes of less than the maximum programmed switchhook flash time will not be repeated towards the central office.

• An open Tip lead condition of 500 ms (optional 100 ms) or more duration on a CO trunk will release the system connection.

• Momentary open loop conditions of up to 350 ms (optional 100 ms) generated by the central office on outgoing system calls will not release calls.

• Station on-hook conditions will release a trunk connection after the selected maximum time.

Feature Time-Out Period Description

No Answer Recall Timer

Camp-On Recall Timer 0 - 180 s Incoming calls camped-on to a busy station

Call Hold Timer 10 - 600 s Calls placed on hold ring b ack to the stat ion u ser

Attendant Busyout Timer

First Digit Timer 5 - 60 s This is the time the system will wait for the first

Interdigit Timer 3 - 60 s Time between dialed digits. Delay Ring Timer 5 - 60 s Time before line rings on key set. Callback Cancel Timer 1 - 24 hrs Time after which callba ck function s are reset and

Call Forward - No Answer Timer

Switchhook Flash 60 - 1500 ms Length of time that a switchhook can be flashed

Ringing Timer 60 - 300 s The length of tim e a st ation rings another sta tio n

Time-Out Information

0 - 125 s If there is no answer at the extension after

time-out expires, it will ringback at the attendant console or transfer station.

before being returned to the attendant, if not answered before time-out expires.

upon expiry.

1 - 1440 min System switches to night service if there is no

activity at the attendant console after calls are received.

digit after going offhook at a station.

cleared, or cancelled.

0 - 125 s Length of time a station rings before the call is

forwarded or rerouted.

without dropping the trunk or line.

before the call is terminated.

Line and Trunk Support Characteristics (NA)

The North American variant of the system supports the following line and trunk parameters:

• Station Loop - The industry standard station loop range, including the station apparatus, can be up to a maximum of 600 ohms (ONS Line).

• DNI Device Ranges - Any device which interfaces to a DNI line card has a loop length of 2 kilometers (6600 ft) with 24 (0.6mm) or 26 (0.45mm) AWG twisted pair cable with no bridge taps, and one kilometre with a maximum of one bridge tap of any length. A maximum of 50 m (162.5 ft) of 22 AWG (0.7mm) quad cable may also be used.

Release 3.2

Page 17

Specification

• CO Trunk Loop - The system operates with CO Trunks up to a maximum of 1600 ohms loop resistance.

• CO Trunk Seizure - The nominal seizure resistance is 265 ohms at 20 mA.

• CO Trunk Resistance - The on-hook dc input resistance of the LS trunks is not less than 5M ohms.

Transmission Characteristics

Compliance

The transmission characteristics for the North American and Latin American variants comply with:

• ANSI/EIA/TIA 464-C 'Requirements for Private Branch Exchange (PBX) Switching Equipment'.

• TIA-912 'Voice Ga teway Transmission Req uirements'.

The transmission characteristics for the United Kingdom variants comply with:

• ETSI ES 202 020 'Harmonized Pan-European/North American loss and level plan for voice gateways to IP based networks'.

Mitel Networks digital telephones meet the requirements of:

• ANSI/TIA/EIA-810-A 'Transmission Requirements for Narrowband Voice over IP and Voice over PCM Digital Wireline Telephones'.

Loss and Level Matrices

Requirements Specifications

Each country has stipulated requirements concerning acceptable transmission performance for telephone systems. The loss plan matrices provide the correct electrical losses in decibels (dB) for each connection to meet the specified requirement.

Loss plans have a direct effect on the acoustic levels provided at the set. Part of meeting the requirements is to identify the reference set requirements for all standard and proprietary sets to be used in each country. It is generally desirable to achieve the same relative loudness levels for all standard and proprietary telephones for a specified loss plan, taking into account loop lengths, transmission format (analog or digital), different transducers in use, line/trunk impedances, and terminating impedances.

Loss and Level Requirements Specifications

Country Requirement Document

Canada CS03, T520, T512 North America TIA/EIA 464-B, TIA/EIA TSB 116 United Kingdom BTR1050, BTR1080, BTR 1181, NCOP(86)42 and BS6450 Pt 4

Release 3.2

Page 18

300 ICP Hardware User Guide

Implementation

In the loss plans, positive values are losses and negative values are gains. The losses are shown in one direction only (outgoing, from the specified port type); the reverse path loss can be found by using a second look up (e.g. In North America, OPS to WAN is a -3dB gain and WAN to OPS is a 9dB loss).

Note: Mitel Networks digital telephones meet the following ITU-T recommended loudness rating: - Send Loudness Rating (SLR) 8 dB - Receive Loudness Rating (RLR) 2 dB.

In interpreting loss plans, refer to the following legend:

Port Abbreviation

IP On Premise Station iONS On Premise Station ONS IP Off Premise Station iOPS Off Premise Station OPS Digital Station DGS Wide Area Network WAN Digital CO Trunk DCO IP Analog CO Trunk iACO IP Analog CO Trunk (short) iACOs Analog CO Trunk ACO Analog CO Trunk (short) ACOs Analog Tie Trunk ATT Note: iONS, iACO, and iACOs apply to the new analog interface designs that comply with the IP

connected half-channel loss plan. The first instances of these is on the 3300 ASU.

North America

Loss Plan Matrix

iONS → ONS → iOPS → OPS → DGS → WAN → DCO → iACO → iACOs → ACO → ACOs → ATT →

iONS

ONS

↑

6 6 3 3 0 0 3 0 3 0 3 3 6 6 3 3 0 0 3 0 3 0 3 3 3 3 0 0 -3 -3 0 0 0 0 0 3 3 3 0 0 -3 -3 0 0 0 0 0 3 9 9 6 6 0 0 0 2 3 0 3 3 9 9 6 6 0 0 0 3 0 3 0 3 9 9 6 6 0 0 0 3 0 3 0 3 0 0 0 0 -9 -6 -3 0 0 0 0 0 3 3 0 0 -6 -3 -3 0 0 0 0 0 0 0 0 0 -9 -3 -3 0 0 0 0 0 3 3 0 0 -6 0 0 0 0 0 0 0 3 3 0 0 -3 -3 -3 0 0 0 0 0

iOPS

↑

OPS↑DGS↑WAN ↑DCO ↑iACO ↑iACOs ↑ACO ↑ACOs ↑ATT

↑

0 Release 3.2

Page 19

United Kingdom

Specification

Loss Plan Matrix

iONS ONS iOPS OPS DGS WAN DCO iACO iACOs ACO ACOs ATT

iONS ONS iOPS OPS DGS WAN DCO iACO iACOs ACO ACOs

ATT

→ → → → → → → → → → → →

iONS

↑

11 11 11 11 5 5 5 3 6 3 6 6 11 11 11 11 5 5 5 3 6 3 6 6

8 6 6 6 0 2 2 0 1 0 1 2 8 6 6 6 0 2 1 0 1 0 1 2 7 4 7 7 0 0 0 1 -2 -3 -2 0 7 7 7 7 0 0 0 1 4 4 4 4 7 7 7 7 0 0 0 1 1 4 1 4 3 3 1 1 -4 -4 -2 0 1 1 1 2 2 2 1 1 1 0 -3 3 1 1 1 4 0 -2 1 1 -1 -3 -2 0 1 1 1 4 2 2 1 1 1 0 -3 3 1 1 1 4 2 2 2 2 -2 -2 1 0 4 4 4 4

Latin America

→ → → → → → → → → → →

→

iONS

↑

ONS

↑

ONS

↑

iOPS

↑

iOPS

↑

OPS↑DGS↑WAN ↑DCO ↑iACO ↑iACOs ↑ACO ↑ACOs ↑ATT

↑

Loss Plan Matrix

OPS↑DGS↑WAN ↑DCO ↑iACO ↑iACOs ↑ACO ↑ACOs ↑ATT

↑

Release 3.2 1

Page 20

300 ICP Hardware User Guide

Germany

Loss Plan Matrix

iONS ONS iOPS OPS DGS WAN DCO iACO iACOs ACO ACOs ATT

iONS

→ → → → → → → → → → → →

ONS

↑

13 13 10 10 4 4 4 2 2 3 3 3 13 13 10 10 3 3 3 0 2 1 3 3 10 10 7 7 1 1 1 -1 -1 0 0 0 10 10 7 7 0 0 0 -1 1 0 0 0 10 10 7 7 0 0 0 -1 1 0 0 0 10 10 7 7 0 0 0 -1 1 0 0 0 10 10 7 7 0 0 0 -1 1 0 2 1

2 2 -1 0 -6 -6 -6 -7 -5 -6 -6 -6 4 4 1 1 -6 -6 -6 -7 -5 -6 -6 -6 2 2 -1 0 -6 -6 -6 -7 -5 -6 -6 -6 4 4 1 1 -6 -6 -6 -7 -5 -6 -4 -5 8 8 5 5 -2 -2 -2 -3 -1 -2 0 -1

iOPS

↑

OPS↑DGS↑WAN ↑DCO ↑iACO ↑iACOs ↑ACO ↑ACOs ↑ATT

↑

Italy

Loss Plan Matrix

iONS → 19 17 16 16 7 7 7 6 6 6 6 5 ONS → 17 13 14 12 3 3 3 6 6 6 6 7 iOPS → 16 14 13 13 4 4 4 3 3 3 3 6 OPS → 16 12 13 11 2 2 2 1 3 3 3 6 DGS → 12 10 7 9 0 0 0 -1 -1 -1 -1 2 WAN → 12 10 7 9 0 0 0 -1 -1 -1 -1 2 DCO → 14 10 10 9 0 0 0 -1 2 2 2 4 iACO → 4 4 -1 1 -6 -6 -6 -7 -7 -7 -7 -4 iACOs → 4 4 1 1 -6 -6 -6 -7 -7 -7 -7 -4 ACO → 5 4 2 1 -2 -2 -2 -3 -3 -5 -5 -4 ACOs → 5 4 2 1 -2 -2 -2 -3 -3 -5 -5 -4 ATT → 10 10 7 7 0 0 0 -1 -1 -1 -1 2

iONS

ONS

↑

iOPS

↑

OPS↑DGS↑WAN ↑DCO ↑iACO ↑iACOs ↑ACO ↑ACOs ↑ATT

↑

2 Release 3.2

Page 21

Netherlands

Specification

Loss Plan Matrix

iONS → 10 10 7 7 1 1 1 1 1 1 1 1 ONS → 10 10 7 7 3 3 3 2 3 3 3 3 iOPS → 7 7 4 4 -2 -2 -2 -2 -2 -2 -2 -2 OPS → 7 7 4 4 0 0 0 -1 0 0 0 0 DGS → 7 7 4 4 0 0 0 -1 0 0 0 0 WAN → 7 7 4 4 0 0 0 -1 0 0 0 0 DCO → 7 7 4 4 0 0 0 -1 0 0 0 0 iACO → 1 1 -2 -2 -6 -6 -6 -7 -6 -6 -6 -6 iACOs → 1 1 -2 -2 -6 -6 -6 -7 -5 -6 -6 -5 ACO → 1 1 -2 -2 -6 -6 -6 -7 -6 -6 -6 -6 ACOs → 1 1 -2 -2 -6 -6 -6 -7 -6 -6 -6 -5 ATT → 5 5 2 2 -2 -2 -2 -2 0 -2 -2 0

iONS

ONS

↑

iOPS

↑

OPS↑DGS↑WAN ↑DCO ↑iACO ↑iACOs ↑ACO ↑ACOs ↑ATT

↑

Spain

Loss Plan Matrix

iONS → 15 15 12 12 5 5 5 2 4 3 5 5 ONS → 13 13 10 10 3 3 3 2 4 3 5 5 iOPS → 12 12 9 9 2 2 2 -1 1 0 2 2 OPS → 10 10 7 7 0 0 0 -1 1 0 2 2 DGS → 10 10 7 7 0 0 0 -1 1 0 0 0 WAN → 10 10 7 7 0 0 0 -1 1 0 0 0 DCO → 10 10 7 7 0 0 0 -1 1 0 2 1 iACO → 2 2 -1 0 -6 -6 -6 -7 -5 -6 -6 -6 iACOs → 4 4 1 1 -6 -6 -6 -7 -5 -6 -6 -6 ACO → 2 2 -1 0 -6 -6 -6 -7 -5 -6 -6 -6 ACOs → 4 4 1 1 -6 -6 -6 -7 -5 -6 -4 -4 ATT → 6 6 3 3 -4 -4 -4 -5 -3 -4 -2 -2

iONS

ONS

↑

iOPS

↑

OPS↑DGS↑WAN ↑DCO ↑iACO ↑iACOs ↑ACO ↑ACOs ↑ATT

↑

Portugal

Loss Plan Matrix

iONS

ONS

↑

iOPS

↑

OPS↑DGS↑WAN ↑DCO ↑iACO ↑iACOs ↑ACO ↑ACOs ↑ATT

↑

Release 3.2 1

↑

Page 22

300 ICP Hardware User Guide

Tone Plans

Tone plans permit the station user to distinguish different stages of call progress and different types of calls. Each tone is assigned a level which ensures an acceptable quality.

North America

Tone Plan

Tone Frequency Cadence

ARS 2nd Dial 350/440 Hz Continuous Busy 480/620 Hz .5s on, .5s off, repeat Camp-on 440 Hz .1s on, .05s off, repeat 2 times Conference 440 Hz 1s on, off Confirmation 350/440 Hz Continuous Dial Tone 350/440 Hz Continuous Feature Active Dial 350/440 Hz .1s on, .1s off 8 times, then continuous on Interrupted Dial 350/440 Hz .1s on, .1s off 8 times, then continuous on Message Notification 350/440 Hz (350/440, 0.1s on, 0.1s off, four times), (440 , 0.2s on, 0.2s o ff, two times),

(350/440 0.1s on, 0.1s off, four times), then 350/440 continuous on Modem Answer 2025 Hz .95s on, .05s off, repeat Override 440 Hz .8s on, off Paging 440 Hz .2s on, off Reorder 480/620 Hz .25s on, .25s off, repeat Ringback 440/480 Hz 1s on, 3s off, repeat Special Busy 480/620 Hz .5s on, .5s off, repeat Special Ringback 440/480 Hz .5s on, .5s off, .5s on, 2.5s off, repeat Transfer Dial 350/440 Hz .1s on, .1s off, 3 times, then continuous on Voice Mail 440 Hz .6s on, off

Tone Output Level

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

ARS 2nd Dial -23 -23 -23 -20 -20 -20 -20 -20 -20 -20 Busy -27 -27 -27 -24 -24 -24 -24 -24 -24 -24 Dial -23 -23 -23 -20 -20 -20 -20 -20 -20 -20 Camp-on -17 -17 -17 -14 -14 -14 -14 -14 -14 -14 Conference -19 -19 -19 -16 -16 -16 -16 -16 -16 -16 Confirmation -23 -23 -23 -20 -20 -20 -20 -20 -20 -20 Feature Active Dial -22 -22 -22 -19 -19 -19 -19 -19 -19 -19 Interrupted Dial -23 -23 -23 -20 -20 -20 -20 -20 -20 -20 Message Notification -17 -17 -17 -14 -14 -14 -14 -14 -14 -14 Modem Answer -20 -20 -20 -17 -17 -17 -17 -17 -17 -17 Override -17 -17 -17 -14 -14 -14 -14 -14 -14 -14 Paging -17 -17 -17 -14 -14 -14 -14 -14 -14 -14 Reorder -27 -27 -27 -24 -24 -24 -24 -24 -24 -24 Ringback -22 -22 -22 -19 -19 -19 -19 -19 -19 -19 Special Busy -27 -27 -27 -24 -24 -24 -24 -24 -24 -24 Special Ringback -22 -22 -22 -19 -19 -19 -19 -19 -19 -19 Transfer Dial -23 -23 -23 -20 -20 -20 -20 -20 -20 -20 Voice Mail -17 -17 -17 -14 -14 -14 -14 -14 -14 -14

4 Release 3.2

Page 23

Specification

Note: DTMF Tones are supported. Note: DGS and WAN Tones are conveyed as RTP Packets. Note: "---" indicates that this interface is not supported in this country.

United Kingdom

Tone Plan

Tone Frequency Cadence

ARS 2nd Dial 350/440 Hz Continuous Busy 400 Hz .35s on, .35s off, repeat Camp-on 400 Hz .1s on, off Conference 400 Hz .1s on, off Confirmation 350/4 40 H z Continuous Dial 350/440 Hz Continuous Feature Active Dial 350/440 Hz .75s on, .75s off, repeat Interrupted 1400 Hz .1s on, off Message Notificatio n 350/440 Hz (350/440, .75s on, .75s off, two tim es), (440, .1s on, .75s off, one

time), (350/440 .75s on, .75s off, repeat) Modem Answer 2025 Hz .95s on, .05s off, repeat Number Unobtainable 400 Hz Continuous Paging 440 Hz .2s on, off Ringing (External) 400/450 Hz 1s on, 2s off, repeat Special Busy 400 Hz .35s on, .35s off, repeat Special Ringing

(Internal) Transfer Dial 350/440 Hz .75s on, .75s off, repeat Interrupted Dial 350/440 Hz .75s on, .75s off, repeat Voice Mail 440 Hz .6s on, off

400/450 Hz .4s on, .2s of, .4s on, 2s off, repeat

Tone Output Level

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

ARS 2nd Dial -8

-12

-17

-22

Busy -9

-14

-19

Dial -8

-12

-17

-22

Camp-on -9

-14

-19

Conference -14 -13 -11 -16 -10 -9 -10 -10 -11 -10

-7

-11

-16

-21

-8

-13

-18

-7

-11

-16

-21

-8

-13

-18

-5

-9

-14

-19

-6

-11

-16

-5

-9

-14

-19

-6

-11

-16

-10

-14

-19

-24

-11

-16

-21

-10

-14

-19

-24

-11

-16

-21

-4

-8

-13

-18

-5

-10

-15

-4

-8

-13

-18

-5

-10

-15

-3

-7

-12

-17

-4

-9

-14

-3

-7

-12

-17

-4

-9

-14

-4

-8

-13

-18

-5

-10

-15

-4

-8

-13

-18

-5

-10

-15

-4

-8

-13

-18

-5

-10

-15

-4

-8

-13

-18

-5

-10

-15

-5

-9

-14

-19

-6

-11

-16

-5

-9

-14

-19

-6

-11

-16

-4

-8

-13

-18

-5

-10

-15

-4

-8

-13

-18

-5

-10

-15

Release 3.2 1

Page 24

300 ICP Hardware User Guide

Tone Output Level

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

Confirmation -8

-12

-17

-22

Feature Active Dial -8

-12

-17

-22

Interrupted Dial -8

-12

-17

-22

Message Notification -9

-14 Modem Answer -20 -19 -17 -22 -16 -15 -16 -16 -17 -16 Override -18 -17 -15 -20 -14 -13 -14 -14 -15 -14 Paging -19 -18 -16 -21 -15 -14 -15 -15 -16 -15 Reorder -9

-14

-19 Ringback -12

-17

-22 Special Busy -8

-12

-17

-22 Special Ringback -12

-17

-22 Transfer Dial -8

-12 Voice Mail -19 -18 -16 -21 -15 -14 -15 -15 -16 -15

-7

-11

-16

-21

-7

-11

-16

-21

-7

-11

-16

-21

-8

-13

-8

-13

-18

-11

-16

-21

-7

-11

-16

-21

-11

-16

-21

-7

-11

-5

-9

-14

-19

-5

-9

-14

-19

-5

-9

-14

-19

-6

-11

-6

-11

-16

-9

-14

-19

-5

-9

-14

-19

-9

-14

-19

-5

-9

-10

-14

-19

-24

-10

-14

-19

-24

-10

-14

-19

-24

-11

-16

-11

-16

-21

-14

-19

-21

-10

-14

-19

-24

-14

-19

-24

-10

-14

-4

-8

-13

-18

-4

-8

-13

-18

-4

-8

-13

-18

-5

-10

-5

-10

-15

-8

-13

-18

-4

-8

-13

-18

-8

-13

-18

-4

-8

-3

-7

-12

-17

-3

-7

-12

-17

-3

-7

-12

-17

-4

-9

-4

-9

-14

-7

-12

-17

-3

-7

-12

-17

-7

-12

-17

-3

-7

-4

-8

-13

-18

-4

-8

-13

-18

-4

-8

-13

-18

-5

-10

-5

-10

-15

-8

-13

-18

-4

-8

-13

-18

-8

-13

-18

-4

-8

-4

-8

-13

-18

-4

-8

-13

-18

-4

-8

-13

-18

-5

-10

-5

-10

-15

-8

-13

-18

-4

-8

-13

-18

-8

-13

-18

-4

-8

-5

-9

-14

-19

-5

-9

-14

-19

-5

-9

-14

-19

-6

-11

-6

-11

-16

-9

-14

-19

-5

-9

-14

-19

-9

-14

-19

-5

-9

-4

-8

-13

-18

-4

-8

-13

-18

-4

-8

-13

-18

-5

-10

-5

-10

-15

-8

-13

-18

-4

-8

-13

-18

-8

-13

-18

-4

-8

Note: DTMF Tones are supported. Note: DGS and WAN Tones are conveyed as RTP Packets.

Note: "---" indicates that this interface is not supported in this country.

6 Release 3.2

Page 25

Specification

Latin America

Tone Plan

Tone Frequency Cadence

ARS 2nd Dial 425 Hz Continuous Busy 480/620 Hz .5s on, .5s off, repeat Camp-on 440 Hz .1s on, .05s off, repeat 2 times Conference 440 Hz 1s on, off Confirmation 350/440 Hz Continuous Dial 350/440 Hz Continuous Feature Active Dial 350/440 Hz .1s on, .1s off, 8 times, then continuous on Interrupted Dial 350/440 Hz .1s on, .1s off, 8 times, then continuous on Message Notificatio n 350/440 Hz (350/440, .1s on, .1s off, four t imes), (440, .2s on, .2s off , two

times), (350/440 .1s on, .1s off, four times), then 350/440

continuous on Modem Answer 2025 Hz .95s on, .05s off, repeat Override 440 Hz .8s on, off Paging 440 Hz .2s on, off Reorder 480/620 Hz .25s on, .25s off, repeat Ringback 440/480 Hz 1s on, 3s off, repeat Special Busy 480/620 Hz .5s on, .5s off, repeat Special Ringback 440/480 Hz .5s on, .5s off, .5s on, 2.5s off, repeat Transfer Dial 350/440 Hz .1s on, .1s off, 3 times, then continuous on Voice Mail 440 Hz .6s on, off

Tone Output Level

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

Release 3.2 1

Page 26

300 ICP Hardware User Guide

Tone Output Level

Transfer Dial -23 -23 -23 -20 -20 -20 -20 -20 -20 -20 Voice Mail -17 -17 -17 -14 -14 -14 -14 -14 -14 -14

Note: DTMF Tones are supported. Note: DGS and WAN Tones are conveyed as RTP Packets. Note: "---" indicates that this interface is not supported in this country.

Germany

Tone Frequency Cadence

ARS 2nd Dial 425 Hz Continuous Busy 425 Hz .1s on, .4s off, repeat Camp-on 425 Hz .25s on, off Conference 425 Hz .25s on, off Confirmation 425 Hz .1s on, .1s off, .1s on, .7s off, repeat Dial 425 Hz .1s on, .1s on, .1s off, .1s on, .7s off, repeat External Camp-on 425 Hz .1s on, .05s off, .1s on, .05s off Feature Active Dial 425 Hz (.95s on, .05s off) x 2, then (.1s on, .1s off, .1s on, .7s off,

Interrupted Dial 425 Hz (.95s on, .05s off) x 2, then (.1s on, .1s off, .1s on, .7s off,

Message Notificatio n 425 Hz (.95s on, .05s off) x 2, then (.1s on, .1s off, .1s on, .7s off,

Modem Answer 2025 Hz .95s on, .05s off, repeat Override 1400 Hz .2s on, off Paging 425 Hz .25s on, off Reorder 425 Hz .2s on, .5s off, repeat Ringback 425 Hz 1s on, 4s off, repeat Special Busy 425 Hz .35s on, .35s off, repeat Special Ringback 425 Hz 1s on, 4s off, repeat Transfer Dial 425 Hz .1s on, .1s off, .1s on, .7s off, repeat Voice Mail 440 Hz .6s on, off

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

Tone Plan

repeat forever)

8 Release 3.2

Page 27

Specification

Tone Output Level

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

ARS 2nd Dial -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Busy -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Dial -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Camp-on -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Conference -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Confirmation -15 -15 -12 --- -10 -13 -10 -10 -8 -12 External Camp-on -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Feature Active Dial -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Interrupted Dial -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Message Notificatio n -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Modem Answer -24 -24 -21 --- -19 -22 -19 -19 -17 -21 Override -27 -27 -24 --- -22 -25 -22 -22 -20 -24 Paging -21 -21 -18 --- -16 -19 -16 -16 -14 -18 Reorder -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Ringback -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Special Busy -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Special Ringback -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Transfer Dial -15 -15 -12 --- -10 -13 -10 -10 -8 -12 Voice Mail -21 -21 -18 --- -16 -19 -16 -16 -14 -18

Note: DTMF Tones are supported. Note: DGS and WAN Tones are conveyed as RTP Packets. Note: "---" indicates that this interface is not supported in this country.

Italy

Tone Plan

Tone Frequency Cadence

ARS 2nd Dial 425 Hz .2s on, .2s off, .6s on, 1s off, repeat forever Busy 425 Hz .2s on, .2s off, repeat forever Camp-on 425 Hz .2s on, .1s off, .2s on, .1s off Conference 425 Hz .2s on, off Confirmation 425 Hz .1s on, .1s off, .1s on, .7s off, repeat Dial 350/425 Hz Continuous Feature Active Dial 350/425 Hz .7s on, .7s off, repeat forever Interrupted Dial 425 Hz .9s on, .1s off then (.1s on, .1s off, .1s on, .7s off, repeat

forever) Message Notification 425 Hz .7s on, .7s off Modem Answer 2025 Hz .95s on, .05s off, repeat Override 425 Hz .2s on, off Paging 425 Hz .2s on, off Reorder 425 Hz .2s on, .2s off, repeat forever Ringback 425 Hz 1s on, 4s off, repeat Special Busy 425 Hz .2s on, .2s off, repeat forever Special Ringback 425 Hz 1s on, 4s off, repeat Transfer Dial 350/425 Hz .75s on, .75s off, repeat Voice Mail 440 Hz .6s on, off

Release 3.2 1

Page 28

300 ICP Hardware User Guide

Tone Output Levels

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

ARS 2nd Dial -17

-20

Busy -17

-20

Dial -17

-20

Camp-on -17

-20 Conference -17 -13 -14 -12 -12 -15 -16 -15 -10 -16 Confirmation -17

-20 Feature Active Dial -17

-20 Interrupted Dial -17

-20 Message Notificatio n -17

-20 Modem Answer -24 -20 -21 -19 -19 -22 -23 -22 -17 -23 Override -27 -23 -24 -22 -22 -25 -26 -25 -20 -26 Paging -20 -16 -17 -15 -15 -18 -19 -18 -13 -19 Reorder -17

-20 Ringback -17

-20 Special Busy -17

-20 Special Ringback -17

-20 Transfer Dial -17

-20 Voice Mail -21 -17 -18 -16 -16 -19 -20 -19 -14 -20

-13

-16

-13

-16

-13

-16

-13

-16

-13

-16

-13

-16

-13

-16

-13

-16

-13

-16

-13

-16

-13

-16

-13

-16

-13

-16

-14

-17

-14

-17

-14

-17

-14

-17

-14

-17

-14

-17

-14

-17

-14

-17

-14

-17

-14

-17

-14

-17

-14

-17

-14

-17

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-12

-15

-16

-19

-15

-18

-15

-18

-15

-18

-16

-19

-16

-19

-15

-18

-16

-19

-15

-18

-15

-18

-15

-18

-16

-19

-15

-18

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-15

-18

-15

-18

-15

-18

-15

-18

-15

-18

-15

-18

-15

-18

-15

-18

-15

-18

-15

-18

-15

-18

-15

-18

-15

-18

-10

-13

-10

-13

-10

-13

-10

-13

-10

-13

-10

-13

-10

-13

-10

-13

-10

-13

-10

-13

-10

-13

-10

-13

-10

-13

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

-16

-19

Note: DTMF Tones are supported. Note: DGS and WAN Tones are conveyed as RTP Packets.

Note: "---" indicates that this interface is not supported in this country.

0 Release 3.2

Page 29

Specification

Netherlands

Tone Plan

Tone Frequency Cadence

ARS 2nd Dial 425 Hz Continuous Busy 425 Hz .5s on, .5s off, repeat Camp-on 425 Hz .5s on, off Conference 425 Hz .1s on, off Confirmation 425 Hz Continuous Dial 425 Hz Continuous Feature Active Dial 425 Hz .75s on, .75s off, repeat Interrupted Dial 425 Hz .4s on, .04s off, repeat forever Message Notificatio n 425/400/425 Hz (.75s on, .75s off x2), (.1s on, .75s of f), (.75s on, .75s off ,

repeat) Modem Answer 2025 Hz .95s on, .05s off, repeat Override 425 Hz .2s on, off Paging 425 Hz .2s on, off Reorder 425 Hz .07s on, .07s off, repeat Ringback 425 Hz 1s on, 4s off, repeat Special Busy 425 Hz .5s on, .5s off, repeat Special Ringback 425 Hz 1s on, 4s off, repeat Transfer Dial 425 Hz .75s on, .75s off, repeat Voice Mail 440 Hz .6s on, off

Tone Output Levels

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

ARS 2nd Dial -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Busy -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Dial -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Camp-on -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Conference -18 -18 -15 --- -13 -16 -13 -13 -11 -15 Confirmation -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Feature Active Dial -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Interrupted Dial -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Message Notification -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Modem Answer -24 -24 -21 --- -19 -22 -19 -19 -17 -21 Override -22 -22 -19 --- -17 -20 -17 -17 -15 -19 Paging -23 -23 -20 --- -18 -21 -18 -18 -16 -20 Reorder -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Ringback -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Special Busy -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Special Ringback -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Transfer Dial -16 -16 -13 --- -11 -14 -11 -11 -9 -13 Voice Mail -23 -23 -20 --- -18 -21 -18 -18 -16 -20

Release 3.2 2

Page 30

300 ICP Hardware User Guide

Note: DTMF Tones are supported. Note: DGS and WAN Tones are conveyed as RTP

Packets. Note: "---" indicates that this interface is not supported in this country.

Spain

Tone Frequency Cadence

ARS 2nd Dial 425 Hz Continuous Busy 425 Hz .2s on, .2s off, repeat Camp-on 425 Hz .6s on, .2s off, .6s on, off Conference 1400 Hz .4s on, off Confirmation 425 Hz Continuous Dial 425 Hz Continuous Feature Active Dial 425 Hz .1s on, .1s off, repeat 8 times, then continuous Interru pted Dial 425 Hz .1s on, .1s off, repeat 8 times, then continuous Message Notification 425/440/425 Hz (.1s on, .1s off x 4), (.2s on, .2 s o ff x 2), (.1 s o n, .1 s o ff x 4),

Modem Answer 2025 Hz .95s on, .05s off, repeat Override 1400 Hz .2s on, off Paging 440 Hz .2s on, off Reorder 425 Hz .2s on, .2s off, .2s on, .6s off, repeat Ringback 425 Hz 1.5s on, 3s off, repeat Special Busy 425 Hz .2s on, .2s off, repeat Special Ringback 425 Hz .5s on, .5s off, .5s on, 2.5s off, repeat Transfer Dial 425 Hz .1s on, .1s off, .1s on , .1s off, . 1s on, .1s of f, then contin uous Voice Mail 440 Hz .6s on, off

Tone Plan

(425 continuous)

Tone Output Levels

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

ARS 2nd Dial -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Busy -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Dial -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Camp-on -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Conference -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Confirmation -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Feature Active Dial -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Interrupted Dial -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Message Notificatio n -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Modem Answer -24 -24 -21 --- -19 -22 -19 -19 -17 -21 Override -27 -27 -24 --- -22 -25 -22 -22 -20 -24 Paging -21 -21 -18 --- -16 -19 -16 -16 -14 -18 Reorder -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Ringback -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Special Busy -17 -17 -14 --- -12 -15 -12 -12 -10 -14

2 Release 3.2

Page 31

Specification

Tone Output Levels

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

Special Ringback -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Transfer Dial -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Voice Mail -21 -21 -18 --- -16 -19 -16 -16 -14 -18

Note: DTMF Tones are supported. Note: DGS and WAN Tones are conveyed as RTP Packets. Note: "---" indicates that this interface is not supported in this country.

Portugal

Tone Plan

Tone Frequency Cadence

ARS 2nd Dial 400 Hz Continuous Busy 425 Hz .2s on, .2s off, repeat Camp-on 425 Hz .2s on, .1s off, .2s on, .1s off Conference 425 Hz .2s on, off Confirmation 425 Hz .1s on, .1s off, .1s on, .7s off, repeat Dial 350/425 Hz Continuous Feature Active Dial 350/425 Hz .7s on, .7s off, repeat Interrupted Dial 425 Hz .9s on, .1s off then

(.1s on, .1s off, .1s on, .7s off, repeat forever) Message Notificatio n 425 Hz .7s on, .7s off Modem Answer 2025 Hz .95s on, .05s off, repeat Override 425 Hz .2s on, off Paging 425 Hz .2s on, off Reorder 425 Hz .2s on, .2s off, repeat Ringback 425 Hz 1s on, 4s off, repeat Special Busy 425 Hz .2s on, .2s off, repeat Special Ringback 425 Hz 1s on, 4s off, repeat Transfer Dial 350/425 Hz Continuous Voice Mail 440 Hz .6s on, off

Tone Output Levels

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

Release 3.2 2

Page 32

300 ICP Hardware User Guide

Tone Output Levels

Override -27 -27 -24 --- -22 -25 -22 -22 -20 -24 Paging -20 -20 -17 --- -15 -18 -15 -15 -13 -17 Reorder -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Ringback -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Special Busy -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Special Ringback -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Transfer Dial -17 -17 -14 --- -12 -15 -12 -12 -10 -14 Voice Mail -21 -21 -18 --- -16 -19 -16 -16 -14 -18

Note: DTMF Tones are supported. Note: DGS and WAN Tones are conveyed as RTP Packets. Note: "---" indicates that this interface is not supported in this country.

Networking Voice Switches

Overview

iONS ONS iOPS OPS iACO iACOs ACO ACOs DCO ATT

Networked MITEL Systems

A network of Mitel Networks systems consists of two or more systems, each referred to as a network element.

By using OPS Manager, you can manage a network of Mitel Networks systems from a single centralized station.

Terminology

Network: a group of systems interconnected through DPNSS.

Network Element: a system that is a member of a network.

Cluster: a group of MITEL or Mitel Networks systems interconnected through DPNSS. All systems in a Cluster share the same primary node identifier.

Cluster Element: a single MITEL or Mitel Networks system which is a member of a cluster.

Portable Directory Number (PDN): a call processing feature available in a cluster of systems. This feature allows you to move a user’s telephone directory number to any extension in the network (i.e., you can move a user’s telephone directory number to an extension on any other system in the cluster and allow the user to retain the same directory number).

Advantages of a Network

A network of telephone systems is a highly functional communications system that provides a greater line size than a single system. A MITEL or Mitel Networks systems network

• Acts as a highly functional, virtual system for both local and wide area applications

4 Release 3.2

Page 33

Specification

• Can be customized and sized to meet long term growth requirements

• Can grow to a theoretical unlimited line size

• Provides enhanced MSDN network feature functionality

• Has an extremely effective digital/analog networking capability

• Can be fiber-distributed and workgroup focused

• Is standards-based and open to Computer Telephony Integration (CTI) development.

Each 3300 ICP network element will support up to 700 lines or up to 100 ACD agents. Two sizes of 3300 Controller are available. These units will support up to 250 IP telephones or 700 IP telephones.

Network elements can be geographically dispersed providing a high level of security to those organizations who maintain critical operations that might be interrupted due to some disastrous consequence. The element dispersal and the fiber optic connectivity of the nodes making up an element allow the terminating nodes to be located near the terminal devices, and they allow for savings in copper distribution cables and their associated protective devices.

Customers requiring ISDN or other broadband network connectivity can switch various voice, data, and video services to both the enterprise and desktop by utilizing other manufacturers equipment together with MITEL and Mitel Networks systems.

As the functionality, reliability, geographical coverage, and price points of virtual private networking (VPN) services improv e, greate r pres su re will be placed on the private networ k. This trend will continue through the evolution of ISDN services. Network customers will be able to select products that can interface with a combination of products and services. For example, a typical customer may choose to use MITEL SUPERSWITCH Digital Network (MSDN) between major centers and VPN between smaller or more remote locations.

Selecting a Suitable Configuration

When building a network, the final design should provide the most effective communications at the lowest cost (impacted only by business and geographical constraints). Additions to existing networks, although complicated by what is already in place, should reflect the configuration design concepts.

Network Configurations

A network can consist of all MITEL and Mitel Networks systems or combinations of MITEL and Mitel Networks products and systems from other vendors. This combination can also be a mixture of various smart (digital systems) and dumb (electronic and electromechanical) systems. To have full MSDN functionality, all the systems in a MITEL or Mitel Networks MSDN/DPNSS North American network must be SX-2000 systems or Mitel Networks 3300 Integrated Communications Platforms.

Note: In this section, the term system describes a MITEL or Mitel Networks system or another vendor's system serving normally as a hub switch.

Release 3.2 2

Page 34

300 ICP Hardware User Guide

There are three basic network configurations:

• linear network

• non-linear network

• combination network.

Linear Network

A linear network is a network in which a number of systems are strung in a line. Networks of this type are typically used by railroads. An advantage of the linear network is that the design is simple. Some disadvantages are that as large numbers of systems are added, dialing can become complex with a tandem connection involved at each intermediate system in the connection; also, if all connections are routed through each intermediate system, a single facility system failure could seriously impact network operation.

Non-Linear Network

A non-linear network is a network in which every system has direct connections to every other system. This configuration has the advantage of a minimum of systems involved in each tandem call connection. Also, alternate routing can be used in cases where inter-switch facilities are busy or disabled. The disadvantage is the increased trunking requirements.

Combination Network

A combination network is a network that is a combination of both linear and non-linear networks. The combination network applies to most large network configurations. Maximum utilization is made of the advantages of both while minimizing the disadvantages. This configuration evolves into the following mesh, star, double star, and hierarchical star configurations used in more complex networks:

• The mesh network is one in which each and every system is connected by trunks to each and every other system. Mesh networks are trunk intensive and are used when there are comparatively high traffic levels between systems and the geographical or economical conditions allow the expensive trunking required.

• The star network utilizes an intervening system called a tandem switch. Each and every system is connected via a single tandem switch. Star configurations are normally applied when traffic levels between systems are comparatively low.

• The double star network includes single star sub-networks that are connected via higher order tandem switches. The factor that leads to star and multiple star network configurations is network complexity in the trunking outlets (and inlets) of a system in a full mesh. For example, the typical mesh network requires that each of the five systems be minimally equipped with four trunk groups or a total of 10 trunk groups reserved for inter-network traffic. In practice, most large networks are a compromise between mesh and star configurations.

• The hierarchical star network has evolved to eliminate confusion. That is, a systematic network was developed that reduces the trunk group outlets (and inlets) of a system, permits the handling of high traffic intensities where necessary, and allows for overflow and a means of restoration.

6 Release 3.2

Page 35

Specification

A hierarchical network provides levels of importance to the systems making up the network. Call traffic restrictions can be placed on traffic flow based on the designated level of importance. For example, in the illustrated hierarchical star network, there are three hierarchical levels of systems. The smallest symbols in the diagram have been marked with a "C" to indicate the lowest level. Note the restrictions (or rules) of traffic flow. As the figure is drawn, traffic from C8 bound for C9 would have to flow through system B2. Likewise, traffic from system B2 to B3 would have to flow through system A1. Carrying the concept somewhat further, traffic from any "A" system to any "B" system would have to be routed through an "A" system.

The high-usage route is the next consideration. For instance, if we found that there was high traffic intensity between B4 and B5 trunks, a switch gear might be saved by establishing a high-usage route between the two systems. We could call the high-usage route a high traveled shortcut.

High-usage routes could be established between any pair of systems in the network if traffic intensities and distances involved proved this strategy economical. When high-usage routes are established, traffic between the systems involved is first offered to the high-usage route and overflow when the route is busy or unavailable. If routing is through the highest level in the hierarchy, we call this route the final route. Hierarchical Network shows traffic routed between systems B4 and B5 via system A2 (the final route in this case).

Cluster Network Configurations

A cluster network is composed of two or more Mitel Networks systems.

A typical cluster network can function independently or as part of a larger network or networks. Cluster elements are categorized as follows:

• Main element

• Satellite element

• Hub element

• Remote main element

• Remote satellite element

• Remote hub element.

In the Typical Distribution of Network Elements illustration, the hub element is connected to both the Public Switched Telephone Network (PSTN) with both local exchange (LEC) and inter-exchange carrier (IXC) connections. It also serves as the gateway to the remote network. The main element has connections to the local exchange carrier (LEC) and the satellite element has no PSTN trunking. Each element is connected to every other element with MSDN/DPNSS to minimize multiple tandem connections.

Network Element Relationship shows the relationship between different types of network elements.

Release 3.2 2

Page 36

300 ICP Hardware User Guide

Main Element

Main Elements can perform the following functions:

• Originate and receive calls

• Serve as intermediate switches in which they can function as tandem points for receiving and passing calls and information

• Serve as terminating switches for most outside world trunking such as Central Office (CO), common carrier trunking, and tie trunks from the remote cluster network and/or other networks (note that the hub supports applications requiring tandeming capabilities)

• Support centralized attendants, ACD, and centralized voice mail.

Note: Each cluster network requires a minimum of one main element terminating all outside world trunking that supports access transparency.

Satellite Element

Satellite Elements can perform the following functions:

• Originate and receive calls

• Serve as intermediate switches in which they can function as tandem points for receiving and passing calls and information.

Notes:

1. Special application trunking can be terminated on a node within this switch.

2. Each network supports up to nine satellites with a minimum of one main or hub

element for a maximum of ten elements. For Mitel Networks 3300 Software Release

3.0, physical restraints will limit this to 8 physical connections. XNET will allow further connections through amortisation of calls onto a common connection through the PSTN, i.e. traffic to multiple nodes could be carried through common physical links.

3. Satellite elements do not support centralized attendants, centralized voice mail, or ACD.

Hub Element

Hub Elements can perform the following functions:

• Provide extensive trunking if applications such as remote network, PSTN, LEC or IXC are to be located on a single element

• Serve as intermediate switches in which they can function as tandem points for receiving and passing calls and information between other cluster elements and the remote network, other networks as the PSTN (LEC and/or IXC), or other private networks

• Originate and receive calls

• Provide a centralized voice mail connection point

• Provide centralized attendants and/or ACD services (note that applications can support some lines, but the major function is trunking).

8 Release 3.2

Page 37

Specification

System Distribution

Campus or Contiguous Applications

These applications involve placing cluster elements in a single campus or contiguous location. Normally, all of the real estate parcels are adjacent to or touch each other. All inter-element transmission facilities are the responsibility of the customer (not the telephone company).

Note: The recommendations for campus environments apply to multi-element cluster applications within a single building.

• Provide more lines, trunks, and/or digital stations than are provided by a single system

• Overcome electrical/fiber optic distance limitations

• Disperse equipment minimizing total outages in the event of cable cuts or power failures.

Networks used in campus environments normally have two characteristics. First, customer-owned facilities (such as copper, fiber, and microwave) are used to provide the network transmission medium. Second, the geographical areas served by the network nodes are normally contiguous.

Take advantage of the following factors when designing a campus environment:

• Identify communities of interest. Where possible, meet the telephone needs of a community of interest with a single network system node. This approach keeps calling patterns within the node requiring fewer trunk facilities to connect to other system nodes.

• T ake advantage of existing or planned fiber optic cable. When the fiber distances are short enough, DSU nodes from each of the network systems can be centralized. When distances are too long for this type of configuration, fiber optic multiplexers can be used to provide DS-1 (T1) or CEPT facilities.

• Look for opportunities to coordinate telephone and data services, and operations. Explore these opportunities carefully and, when possible, present and implement integrated solutions.

Remote Networking

The cluster can be installed with some or all of the cluster elements remotely dispersed. When designing a remote network involving all elements or cluster elements and other network systems, the information contained in this section applies. When designing a remote network involving mixed networks, cluster elements and other systems, the cluster should be designed as an entity, and then the connections to the other network systems should be considered.

Note: A cluster can be applied within a locality, across local, state and international boundaries.

Network Transmission Guidelines

A network consists of three parts:

1. Dedicated transmission facilities (tie trunks)

2. Exchange facilities (such as FX, Sprint/MCI/AT&T, and local exchange DDD/DID)

Release 3.2 2

Page 38

300 ICP Hardware User Guide

3. Switching equipment (such as a MITEL or Mitel Networks system).

Quality and Performance Guidelines are Required

Since the quality and stated performance characteristics of dedicated transmission and exchange facilities are most often controlled by common carriers, the number of creative or complex arrangements utilizing a combination of these three elements requires guidelines to ensure proper operation in the field. Off-net calling in a private network, multi-tandem on-net calling, and RADs are capabilities for which transmission guidelines are also required.

Maximize the Use of Digital Facilities

You can minimize transmission problems by using digital facilities. Use digital facilities when connecting the system nodes together and when connecting Local Exchange (LEC) and Inter-Exchange (IXC) carriers to the system nodes.

Private Network Calling

Off-Net Calling

Calls which originate in a private tandem network and extend through the public switched or other networks for completion are commonly called off-net calls. A frequent application of off-net calling occurs when long distance (LD) trunks are hubbed on one network switch and accessed through this hub switch by other (satellite) switches in the private, tandem networks. A second application involves the use of ARS routing over tie-trunks tandeming through multiple systems to complete off-net calls. Finally, switches can provide for off-net calling automatically at a distant network system location. These applications must be examined carefully prior to implementation to assure business operation compliance, transmission integrity, and documented economic savings.

Off-Net Trunks - The Public Switched Network (PSTN) trunks carry off-net traffic. In some cases calls may be carried as far as possible on-net and then be routed to off-net trunks. In other cases the call may access the public network at the closest system from which the call originated.

Off-Network Routing - The routing method to the public network depends on ARS and how the routing patterns are administered at each system involved in the connection. Calls that utilize the customer’s private tandem network and DDD network are commonly called off-net calling, double-tandeming, or tail-end-hop-off. A frequent application of off-net calling occurs when a customer concentrates WA TS lines in a system tandem switch which serves as a hub for these services with access via satellite systems. A second application involves the use of ARS routing over tie lines tandeming through multiple systems to complete off-net calls. Finally, the system can provide off-net calling automatically at a distant hub location.

Off-net trunks and off-network routing each offer economic and transmission quality compromises. In certain situations, transmission is satisfactory although there are times when the complexity of tandem switching, the quality of the trunks, and the common carrier involved, do not allow for successful transmission. Care must be taken in network design to identify potential transmission problem areas.

0 Release 3.2

Page 39

Specification

The three types of off-network routing methods are defined as follows:

1. Tail-End-Hop-Off (TEHO) routes an off-net call through the private network and hops off at the tandem switch closest to the destination of the call. As an example, a tandem switch in Atlanta which is connected to New Y ork originates a call to Philadelphia. The call is first routed on-net over the inter-tandem trunks between Atlanta and New York and then hops off on the FX trunk to Philadelphia.

2. Head-End-Hop-Off (HEHO) routes an off-net call to the closest tandem switch from where the call originated. As an example, a private system in New York originates a call to Dallas. The call tandems to an on-net system in Washington, D.C., and hops off using WATS to complete the call.

3. Best-End-Hop-Off (BEHO) routes off-net calls using the most economical facility and departure point within the private network. The call may hop off the private network at the originating, intermediate, or terminating tandem switch depending on how the routing patterns are administered.

Tandem and On-Network Calling

To minimize network management problems where there are more than three systems in a network, consult MITEL. For networks in North America contact MITEL Dallas Systems Engineering. For networks in the UK, contact the MITEL Technical Advice Center.

The following factors must be taken into consideration with respect to tandem and on-network calling:

• Engineering Constraints - The availability of access codes and ARS routes at each network system and the digit outpulsing limit are engineering constraints. With careful engineering, you can design networks to include a considerable number of system nodes. Ideally, networks should be in a non-linear configuration.

• General Network Data - A network consists of tandem switches that accept and pass call traffic, inter-switch tie-trunks and transmission facilities that connect the tandem switches, and access or bypass access tie-trunks from a tandem switch to another tandem or end switch.

• Simple Networks - Simple networks are normally designed as symmetrical networks. The characteristics of a symmetrical network are tandem switches are of an equal level, all routes (trunk groups) are high usage, and circular call routing is prevented.

• Complex Networks - Complex networks can be configured hierarchically for call routing. The characteristics of a hierarchical network are each tandem switch has an assigned level (upper and lower), each lower level system connects to an upper level system, upper level systems are completely interconnected, and there is a routing plan that prevents circular call routing.

• Hierarchical Ranking - The hierarchical ranking allows an orderly routing of on-net access calls. The switching portion of the network is represented by the upper-level and lower-level tandem switches connected by inter-switch tie-trunks. The tandem switches can accept voice/data calls from any connected point and pass the calls to another connected point. The upper-level systems have a large amount of call traffic and the lower-level systems normally have small amounts of call traffic. Lower-level systems can be administered to

Release 3.2 3

Page 40

300 ICP Hardware User Guide

overflow to upper-level systems, in most cases. Calls from upper-level systems do not overflow to lower-level systems because of the large volume of traffic.

Network Trunks (MSDN, Non-MSDN)

The tie-trunks that connect the systems within the private network are named according to function. That is, names like inter-tandem/inter-machine, access, and by-pass access denote function (type of routing) rather than hardware differences. The off-net trunks that provide access to Direct Distance Dialing (DDD), Foreign Exchange (FX), or Inter-exchange Carrier (IXC) are used by ARS to complete calls to the destination. IXC trunks provide access to Other Common Carrier (OCC) facilities. An off-net call may be carried by on-net trunks part way to its final destination before accessing off-net facilities to complete the call.

Inter-tandem/Inter-machine Tie-trunks - As its name implies, an inter-tandem tie-trunk interconnects to tandem switches. It can be one-way incoming, one-way outgoing, or two-way . Inter-tandem tie-trunks are further classified as primary high-usage, intermediate high-usage, or final, depending on the routing of calls and overflow routing of calls. The complexity of network, customer requirements, and economic factors determine trunk type and classification.

On-Network Routing - The overflow routing characteristics for inter-tandem tie-trunks are as follows:

• Primary High-Usage (PHU) Inter-tandem Tie-trunks - These trunks serve first-choice traffic only. They do not receive any overflow traffic, but may overflow to intermediate or final trunk groups. They are designed to overflow at a present economic load level (see figure).

• Intermediate High-Usage (IHU) Inter-tandem Tie -trunks - These trunks serve first-choice and second-choice traffic and receive overflow traffic from primary high-usage trunk groups. Like PHU trunks, these trunks overflow at a preset economic load level. They direct any overflow traffic to final trunk groups.

• Final Inter-tandem Tie-trunks - These trunks receive overflow traffic from primary and intermediate high-usage trunk groups, but do not overflow to any other trunk group. These trunks block calls when all trunks are busy. When a call is blocked, the caller receives busy or intercept tone, or is placed in queue, depending on how the trunk is administered.

• Overflow Routing - In the inter-tandem Tie-trunk usage (overflow routing) example, a call originating in Los Angeles would, as a first choice, be routed directly from Los Angeles to Atlanta over the (A) primary high-usage trunks. If busy, the second-choice routing would be to New York over the (B) intermediate high-usage trunk and from New Y ork to Atlanta via the (C) final trunks. If the (B) intermediate high-usage trunks connecting Los Angeles to New Y ork were busy, the final route (C) from Los Angeles to Chicago, Chicago to New York, New York to Atlanta would be used. The fourth choice, if the final route was busy, would be to route the Los Angeles caller to busy tone.

Direct Inward System Access (DISA)

DISA is designed to allow local calling area access to a customer's system and its networking capabilities. Take care when supporting long distance inward access, particularly 800 type INWA TS, via DISA for calls that could terminate in OUTWATS or DDD trunks in another distant point.

2 Release 3.2

Page 41

Specification

The primary problem is the uncertainty of the normal loss in the inward WA TS connection, which may not allow users to break dial tone from their DTMF pads.

Even if successful connection has been made, the total amount of loss when connecting INWA TS trunks to an OUTWATS trunk can be such that the user is not likely to hear the called party. The offering of WATS service, inward and outward, further complicates the problem.

These positions are consistent with common carrier transmission practices. It is very important to appreciate the capabilities and limitations of network configurations. Consultation with various common carriers is a required part of network selling and implementation. Any applications of off-net tandem dialing, built-up on-net calling, or remote DISA should be carefully reviewed by local systems engineering prior to any formal customer proposal.

Survivability

Survivability requires that all network operations would not be lost due to the failure of one or more, but not all, network elements. Network applications provide a much higher degree of survivability than a single system solution because networks are modular in design. Customer requirements and economics dictate the level of survivability for the network and the individual network elements.

Different Configurations Provide Different Levels of Survivability

Choose one of the following configurations to provide the required level of survivability:

• Linear configuration - failure of a single element disrupts inter-network calls between some of the elements

• Star configuration - failure of the hub element disrupts inter-network calls between all the elements

• Mesh configuration - failure of one element only affects the subscribers on that element.

Maximize the Survivability of Critical Elements

Any cluster is only as good as its critical element. It is important that you identify critical elements and reinforce their survivability.

To maximize element survivability:

• When possible, facilities for local exchange and common carrier trunking should come from more than one direction. Ideally, as a minimum, entrance facilities from more than one telephone company distribution cable system would be available.

• Equipment should be located in secure, dry, storm hardened building locations. Each system node should have some central office trunking, which can be backed up with cellular facilities to bypass the local CO and/or cable plant.

Survivability of Local Exchange and Common Carrier Trunks Facilities

If possible, locate local exchange and common carrier trunks on more than one element. If the network is a loop with local exchange (LEC) and inter-exchange carrier (IXC) on two (2)

Release 3.2 3

Page 42

300 ICP Hardware User Guide

elements, failure of an element with LEC and IXC trunking would affect only the subscribers located on the element. The rest of the network would only suffer diminished performance.

Designing the Network

To design a network you must complete the following tasks:

• Prepare an engineering plan

• Determine the number and type of elements required

• Determine the MSDN/DPNSS Network Resource Dimension required

• Calculate the trunking requirements

• Determine the method for interconnecting the elements

• Establish the numbering plan.

Prepare an Engineering Plan

Before you begin, prepare an engineering plan for the site consisting of the following information:

• Diagram of customer's existing systems or network

• Diagram of customer requested or proposed network

• Diagram of customer existing data communications

• Diagram of customer requested or proposed data communications

• Network node information sheet (one per node)

• Number plan for existing node and network

• Number plan for proposed node and network

• Common carriers and resp ectiv e offering s

• Local exchange carriers and respective offerings.

Determine the Number and Type of Elements Required

When determining the number of elements required, be sure to take future growth into consideration.

In configurations involving two to ten elements, PSTN trunking is designed with a target of 12% and MSDN trunking with the assumption that every element is connected directly to every other element with a minimum of one MSDN/DPNSS inter-element link. In actual applications, a realistic number of lines will be around 500 for a 3300 ICP system depending on configuration and applications.

Note: The maximum number of elements in a contiguous/campus cluster configuration cannot exceed ten. The following table illustrates absolute line/trunk maximums and peripheral/NSU node quantities. Every available port would be occupied unless otherwise indicated.

4 Release 3.2

Page 43

Specification

The followi ng t abl es illu stra te the conc ept of br eaki ng dow n th e avai la bili ty on a per li ne bas is by trunking, inter-element, and intra-element CCS availability. Actual configurations and traffic information (CCS availability) will be determined and designed on a per case basis by using customer and/or consultant requirements and case studies conducted by MITEL sales and systems engineering staff.

Maximum Line/Trunk Si zes per Cluster (excluding Xnet)

% Cluster

Elements

2 700 96 14% 46 15 3 2* 4** 130 3 700 96 14% 46 15 3 2* 4** 136 4 700 96 14% 92 27 4 3* 4** 141 5 700 96 14% 92 27 4 4* 4** 144 6** N/A N/A N/A N/A N/A N/A N/A N/A N/A 7** N/A N/A N/A N/A N/A N/A N/A N/A N/A 8** N/A N/A N/A N/A N/A N/A N/A N/A N/A 9** N/A N/A N/A N/A N/A N/A N/A N/A N/A 10** N/A N/A N/A N/A N/A N/A N/A N/A N/A Figures are based on Mitel Networks 3300 Software Release 3.0. Traffic Rate is 6CCS per line. Configuration without XNET, i.e. a physical co nnection to each node is required. 60% of internal traff ic is between nodes. PSTN trunks are connected locally at each node.

Note:

* MSDN 2 x 23B + D, assumes one MSDN to every other element ** PSTN 2 x 24 CH *** These combinations not possible with Mitel Networks 3300 Software Release 3.0 without Xnet (insufficient

physical links per node).

Max.

lines per

node

Max.

PSTN

trunks

available

% PSTN

trunks

Max MSDN trunks

available

% Total

Trunks

# NSUs

MSDN

DS1

PSTN

DS1

Total

Trunks

required

per node

Maximum Line/Trunk Sizes per Cluster

(with Xnet and central switching, e.g. PSTN or tandem switching)

% Cluster

Elements

2 700 96 14% 46 15 3 2* 4** 131 3 700 96 14% 46 15 3 2* 4** 138 4 700 96 14% 92 27 4 3* 4** 144

5 700 96 14% 92 27 4 3 4** 148 6** 700 96 14% 92 27 4 3 4 156 7** 700 96 14% 92 27 4 3 4 162 8** 700 96 14% 92 27 4 4 4 166 9** 700 96 14% 92 27 4 4 4 168

10** 700 96 14% 92 27 4 4 4 168

Figures are based on Mitel Networks 3300 Software Release 3.0. Traffic Rate is 6CCS per line. Configuration with XNET, i.e. one physical connection can carry traffic for more than one end node. 60% of internal traffic is between nodes. PSTN trunks are connected locally at each node.

Note:

* MSDN 2 x 23B + D, assumes one MSDN to every other element ** PSTN 2 x 24 CH

Max.

lines per

node

Max.

PSTN

trunks

available

% PSTN

trunks

Max MSDN trunks

available

% Total

Trunks

# NSUs

MSDN

DS1

PSTN

DS1

Total

Trunks

required

per node

Release 3.2 3

Page 44

300 ICP Hardware User Guide

PSTN and MSDN Trunking CCS Allocation at P.01 per link

LINES

(users)

PSTN

Trunks

700 96 2891 4.13 46 1236 1.76 700 96 2891 4.13 69 1987 2.83 700 96 2891 4.13 92 2758 3.94

PSTN Trunks MSDN Trunks

Available

CCS

PSTN CCS

Per Line

Usage

MSDN

Trunks

Available

CCS

MSDN

CCS Per

Line

Usage

Calculate Trunking Requirements

Inter-element Trunking/Links

Inter-element trunking is MSDN/DPNSS, 23B+1D or 30B+2D. MSAN facilities can be used.

The following section is a worked example of how inter-node trunking requirements would be calculated. In practice the numbers to be used may differ, but the principles remain the same.

For elements installed in a campus or within a contiguous area, an inter-element link connects each element to every other element as a minimum. This minimizes tandem connections and involving more than two elements in a call.

This figure illustrates the connectivity between elements in a 10-element cluster installed in a campus/contiguous environment. Each element is connected to every other element by one link. In a campus/contiguous environment the number of elements will not normally exceed ten.

Additional links between specific elements will be provided when required to meet bid traffic requirements or conditions. These links are referred to as high traffic links. This figure shows a typical campus network with a high traffic link installed.

The first step in engineering the quantity of inter-element links is to determine the quantity required to support local traffic between the elements. It is most important that communities of interest/work groups/organization be confined to a single element to minimize inter-element traffic.

Use the following calculations to

• Determine the total CCS/Erlang requirement per line per busy hour

• Determine percentage trunk-in, trunk-out and local, per busy hour.

As an example, 900 seconds of traffic (9 CCS/.25 Erlang) per line will be used with 33.33% trunk-in, 33.33% trunk-out and 33.33% local. Local traffic represents 300 seconds, and for this calculation we assume 120 seconds is intra-element and 180 seconds inter-element. There will be 10 elements in the cluster so the 180-second inter-element traffic will be divided by 9. This allows for 20 seconds of traffic per line to each other element.

6 Release 3.2

Page 45

Traffic Requirements (Example)

TRUNK-IN TRUNK-OUT ELEMENT LOCAL ELEMENT

300 s

Inter-Node Traffic

300 s

Intra-Nodal

120 s

Inter-Nodal

180 s

2 3 4 5 6 7 8 9 10

20 s 20 s 20 s 20 s 20 s 20 s 20 s 20 s 20 s

Assuming 1,000 lines per switch

1,000 lines X 20 seconds = 20,000 seconds 200 CCS/5.56 Erlangs

Using traffic tables at P.01 (one busy per 100 attempts) Grade of Service (GOS) requires 12 channels equal to 195 CCS/5.42 Erlangs. Therefore, 12 channels will be required between each element to support local inter-nodal traffic.

Inter-nodal connections are also required for trunk traffic when the element containing stations does not have LEC, IXC, or network trunking. Ideally, as a minimum, each element should have dedicated outgoing LEC trunks. Providing both incoming and outgoing trunks on each element further minimizes the need for inter-nodal connections. When possible, DID trunks should be obtained from the LEC in groups that provide the numbers as they relate to the element number plan. To do this, each element should, to the highest degree possible, have a unique number plan. Over a period of time, moving portable directory numbers across the cluster will affect the numbering plans at each element.

Specification

To calculate the inter-nodal links required to access or receive calls from external trunking, we will go back to the 900 seconds per line traffic requirement and make the following assumption:

• 40 seconds of the 300 seconds of out-trunking will be outgoing common carrier (IXC) traffic connecting to one element. (In this example, incoming PSTN trunk calls are considered to arrive at the local nodes).

This assumption implies that an additional 40 seconds of traffic per line must be accommodated between elements two through ten to element one. Therefore, for each element, we calculate:

1,000 lines X 40 seconds = 40,000 seconds 400 CCS/11.11 Erlangs

The total is now:

Internodal 200 CCS 5.56 Erlangs

-Outgoing IXC 400 CCS 11.11 Erlangs

--------------------------------------------------------------- ---------------------------- Total 600 CCS 16.67 Erlangs

Using traffic tables at P.01 GOS, each element (elements 2 through 10) requires 22 channels, 600 CCS/16.67 Erlangs to connect to element one.

Release 3.2 3

Page 46

300 ICP Hardware User Guide

The following table shows the total channel requirements:

Channel Requirements (for example)

Elements Number of Channels

Elements 2-10 to Element 1 26 (12+14 for PSTN O/going) Element 2 to Elements 3-10 12 Element 3 to Elements 4-10 12 Element 4 to Elements 5-10 12 Element 5 to Elements 6-10 12 Element 6 to Elements 7-10 12 Element 7 to Elements 8-10 12 Element 8 to Element 9-10 12 Element 9 to Element 10 12

This example illustrates the advantage of using CEPT (30B+2D) for inter-element connectivity in campus/contiguous environments whenever possible. If DS-1 (23B+D) were used between elements 2-10 and element 1, two DS-1 circuits would be required. With CEPT (30B+2D) the 30 B-channels at P.01 provide 675 CCS/18.74 Erlangs with the requirements being local 200 CCS/5.56 Erlangs and trunk 400 CCS/11.11 Erlangs for a total of 600 CCS/16.67 Erlangs, so a single CEPT would suffice. At P.01 30 channels provide 732 CCS/20.34 Erlangs.

Traffic Calculation Data

Total Traffic per Line

total traffic per line = total CCS/Erlangs in seconds per line

Total traffic per line (100%) can be split into: % trunk in plus % trunk out plus % local.

Intra-Element

local seconds per line x percent intra-element = seconds per line intra-element

Inter-Element

% Inter-elements = seconds per line element x # lines per element = total seconds traffic to each other element

CCS/Erlang Formulas

total secondstraffic/100 = CCS

total seconds traffic/3600 = Erlang

8 Release 3.2

Page 47

Specification

Inter-element Trunk Traffic

Seconds Trunk-in Seconds Trunk-out

% Intra-Element % Inter-element % Intra-element % Inter-element

Number elements supporting trunks

Seconds = per line per element

Number elements supporting trunks

Seconds = per line per element

Seconds Trunk-in

Seconds per line x number lines per element = total seconds traffic to each other element

Seconds Trunk-out

Seconds per line per trunk x number lines per element = total seconds traffic to each other element

Total Element-to-Element Traffic

CCS Erlang Local ------------- -------------Trunk-in ------------- -------------Trunk-out ------------- -------------Total ------------- -------------Obtain the number of channels from the following table.

Quick Traffic Reference at P.01 Grade of Service (GOS)

Quantity channels/trunks CCS Erlangs

DS-1

1 23B 521 14.47 2 46B 1236 34.32 3 69B 1987 55.20 4 92B 2758 76.60 5 115B 3535 98.20 6 138B 4324 120.10 7 161B 5119 142.20 8 184B 5915 164.30

CEPT

1 30B 732 20.34 2 60B 1688 46.90 3 90B 2689 74.70 4 120B 3708 103.00 5 150B 4738 131.60 6 180B 5774 160.40 7 210B 6819 189.43 8 240B 7868 218.56

Release 3.2 3

Page 48

300 ICP Hardware User Guide

Trunking Between Elements

A cluster can be provided for a single campus/contiguous location or dispersed on a local, regional, national, or international basis. Many cluster applications will be combinations of one or more campus/contiguous locations and one or more dispersed remote elements.

Some applications will also require connectivity to other networks, or to systems that either are not part of the cluster or are not totally compatible with a cluster or MSDN/DPNSS.

This figure illustrates a regional cluster application, and this figure illustrates a nationally dispersed cluster connected to non-cluster applications.

Connectivity between contiguous and remote cluster elements always consists of MSDN/DPNSS links or MSAN/APNSS circuits. Connectivity between cluster elements and non-cluster systems and/or networks will consist of T1/D4 or analog E&M tie lines in North America, and it will adhere to national standards in CCITT areas.

The quantity of trunks between cluster elements and remote cluster elements, or cluster elements/remote cluster elements and non-cluster systems and/or networks, are engineered to meet actual traffic requirements or the customer specifications using Poisson or Erlang traffic tables. If acceptable to the customer, grades of service lower than P.01 may be used.

The engineer must be aware that this type of connectivity requires economic and/or business requirements to justify recommendations and implementation.

Public Switched Telephone Network Trunking

Public Switch Telephone Network (PSTN) trunking is provided by local exchange carriers (LEC) and common carriers, also known as inter-exchange carriers (IXC). Normally, a cluster element or group of cluster elements in a campus/contiguous application would be served by a single LEC. This is not always the case with common carriers. Multiple IXCs can connect to a single cluster element or group of cluster elements in a campus/contiguous application.

Connectivity from LEC’s and IXC’s can be digital or analog and an exact version will be determined by national standards. Examples are ISDN PRI, T1/D4, E1 with R-2 signaling, DASS, and various analog trunk signaling schemes.

T o minimize inter-element link requirements, each cluster element should, to the highest degree possible, have incoming and outgoing LEC service connected directly to it.

Special trunks, such as ACD, DISA, or dedicated, should connect directly to the cluster element where primary utilization will take place.

Common carrier circuits (IXC) should also connect to the cluster element where primary utilization takes place. Economic reasons may justify the bundling of IXC circuits and connecting to a cluster hub or main element where they would be utilized by more than one cluster element.

Survivability should also be considered in cluster-PSTN trunk engineering.

0 Release 3.2

Page 49

Specification

Determine the Method for Interconnecting Elements

MSDN/DPNSS Connectivity

Refer to the MSDN/DPNSS feature for information on network features.

Digital Signaling

MSDN/DPNSS provides call setup capabilities between systems connected in an MSDN/DPNSS network. MSDN/DPNSS uses a Common-Channel Signaling (CCS) scheme in which the signaling information for a number of traffic channels is passed as addressed messages over a single channel. The traffic information is carried on E&M trunks, and the digital signaling information may be carried on an analog or digital circuit.

Network Applications

MSDN/DPNSS can be utilized in all digital networks.

DS-1 Link

DS-1 offers a full duplex, point-to-point, 1.544 Mbps digital link with defined frame format. Each frame of a DS-1 link consists of 23 voice/data channels and one signaling channel, and it takes 125 microseconds to transmit. A DS-1 digital link cannot be set up between a DS-1 Formatter card and CEPT Formatter card.

The DS-1 digital link complies with the ATT DSX-1 standards. The technical characteristics of the DS-1 link are as follows:

• twenty-four 64 Kbps traffic channels (23B + D)

• one bit for terminal and signaling frame alignment

• each channel has a sampling rate of 8,000 Hz at 8 bits per sample for a total of 64 Kbps. Each frame is then (24 x 8) + 1 = 193 bits. The total bit rate is therefore: 193 x 8000 =

1.544 Mbps.

Fractional T1

The common carriers offer fractional T1 services at a DS-0 rate of 56 Kbps. Using this service, and a voice/data MUX, provides an effective means of providing MSAN connectivity to a remote location (see MSAN Connectivity To A Remote Location).

Various manufacturers provide voice/data MUXs which can provide various combinations of voice and data (for example, 4 data and 4 voice over 56 Kbps DS-0 line).

XNET

XNET allows DPNSS trunks to be allocated to individual nodes on a switching basis. Rather than have dedicated links to each individual node, XNET allows a number of physical trunks to carry all traffic to all required nodes. The switching to appropriate end nodes is carried out at the PSTN or tandem exchange, and it is typically setup in a star configuration. The benefit

Release 3.2 4

Page 50

300 ICP Hardware User Guide

is the increased number of nodes that can be added to the network, and the reduced cost of interconnection tied lines.

CCITT (E1) to NA (T1) Connectivity

Connectivity can be provided between North American (23B+1D) and CCITT (30B+2D) with the common carrier providing proper channel matching. Twenty-three B-channel and one D-channel will be presented at the CCITT end. A DS-1 (E1/T1) Formatter card which inverts D-channel data must be installed in the North American element.

Establish the Numbering Plan

Factors to Consider

When engineering the numbering plan, you must consider the following factors:

• Number of elements in campus/contiguous applications

• Quantity of directory numbers required in campus/contiguous applications

• Remote elements

• Quantity of directory numbers required in remote elements

• Telephone company exchange codes and DID number blocks

• Ability of the telephone company to break down by trunk group DID numbers by thousands digit and hundreds digit

• Any possible numbering conflicts, especially when remote elements are dispersed over wide geographic areas.

Implement Network Applications

This section discusses the implementation of the following network applications (as required):

• Station Message Detail Recording

•Voice Mail

• Data Applications.

Station Message Detail Recording (SMDR)

This section outlines the current methods used to gather SMDR information from multiple systems. These methods apply to either a network of elements or a cluster network.

The following SMDR report parameters are difficult to interpret in a network application:

• Time stamp on the call record

• Trunk number

• Call originating party ID.

2 Release 3.2

Page 51

Specification

Ensuring Accurate Time Stamps

When multiple systems are used, multiple call records are produced. Within the call accounting mechanism, some type of sort criteria is used to "glue" together multiple call records, resulting in a complete model of the call. This model will include all the intermediate transitions in and out of tandem elements. Timing on these calls is very important to get an accurate report from the call accounting system.

Use the OPS Manager time synchronization feature to synchronize the time-of-day clock on all elements in a network to one second precision. This time synchronization feature also allows you to compensate for time zone differences where network elements are geographically dispersed.

Prevent Duplicate Trunk Numbers

Ensure trunk numbering across the network is sequential and unique. Flexible trunk numbering allows you to program trunks with trunk numbers from 1 to 9999.

Note: Do not confuse trunk numbering with the number of trunks.

Identifying Calls

The network node identification and the trunk number are included for incoming trunk calls that are routed across the network (see Network SMDR for details).

Voice Mail

Voice mail services in a network may be provided as follows:

• On an individual node basis. Each node will have its own stand-alone voice mail system which will provide service to the users located on that node.

• Each node could have its own voice mail system providing service to the users located on that particular node. These individual voice mail systems can be networked according to manufacturer's specifications to provide network services such as a broadcast list across the network.

• A centralized system using a single voice mail system to serve either all network node subscribers or those users located on a group of network nodes. When such a system is provided at network nodes, the manufacturer's method of networking their systems can be used to further network these systems for multi-network applications.

Centralized Voice Mail Applications

Systems provide voice mail interfaces by using ONS or E&M Trunk circuits. These circuits can be configured to provide voice mail functionality from a centralized voice mail system.

Full voice mail functionality is obtained by use of the MSDN/DPNSS feature.

Release 3.2 4

Page 52

300 ICP Hardware User Guide

MSDN/DPNSS Voice I

MSDN/DPNSS Voice I provides

• Ability to send forwarding party node identification, directory number, and call forward type information across the DPNSS network

• Ability to display node identification and directory numbers on non-voice mail display sets.

MSDN/DPNSS Voice III

MSDN/DPNSS Voice III provides

• Ability to display the remote forwarder name in addition to the node identification and directory numbers on non-voice mail display sets

• DPNSS callback message cancellation (voice mail usage only).

MSDN/DPNSS Voice V

MSDN/DPNSS Voice V provides

• Ability to display remote node information on COV voice mail sets

• Ability to outpulse remote node, node identification, and extension number to voice mail ports with the ONS interface

• Ability to send and cancel voice mail messages on remote node subscribers via DPNSS callback messaging.

Typical Scenario in a Centralized Voice Mail Application

A trunk call is presented to extension 1234 and is forwarded to extension 5000 (COV voice mail) when no answer is received (see Centralized Voice Mail - Typical Scenario).

The COV voice mail display shows CFNA 1234, when the caller is forwarded to voice mail extension 5000. Voice mail answers the call and the caller leaves a message for extension

1234. The voice mail then goes off-hook, dials the voice mail activate feature access code (i.e., *20) followed by 1234. An ARS route has been established on Node A to route via an MSDN trunk (1 plus 3 digits = MSDN). The system dials 1234 and activates the message waiting lamp.

Note: Do not use *20 for ARS routes as this will cause a conflict with the network voice mail feature.

Message Waiting

Voice Mail Message Waiting indications are set from the main system by accessing the network trunks and outpulsing the Message Waiting activate/deactivate feature access code assigned on the remote system followed by the subscriber's extension number. The same feature access code is assigned on all systems unless the voice mail system can be assigned multiple message activate/deactivate codes; therefore, conflict dialing arises on the main site between the feature access code and ARS leading digits. The ARS leading digits for remote messaging will have to be programmed on the main system before the feature access code is assigned for Message Waiting activate/deactivate functions.

4 Release 3.2

Page 53

Specification

Most voice mail systems require return dial tone after activating/deactivating message indications for confirmation. The conflict dialing timer for subscribers on the main site, may have to be adjusted through programming. Some voice processors are able to insert a "#" tone at the end of the dialed message wait string, which could be interpreted as "end of dial". Return dial tone would be returned immediately after the *#*, allowing quicker voice mail response and more digits to be dialed in setting another message indication without going on hook.

The message wait indications applied on the remote system will be considered "dial message waiting" messages not "callback messages".

Message Answering

Remote subscribers will reroute their calls to a defined ARS leading digit followed by their extension number. ARS will route the call through the network facilities to trunks on the main system where further digits will be outpulsed after accessing the centralized voice mail. The leading digit and extension number is passed through the network which will access the Loop Back or E&M Trunks on the main site. ARS digit modification for the trunks will outpulse the voice mail hunt group pilot number and insert a pause and any necessary tones followed by the extension number after the voice processor has answered. Calls rerouted will be offered the personal greeting of the subscriber.

Message Retrieval

Using "ONS Voice Mail" with "non-MSDN"; subscribers on the remote site may access the voice mail hunt group pilot number directly through ARS, although the user will be required to manually enter the appropriate DTMF tones to access their mailbox.

Alternatively, subscribers could retrieve voice mail messages by dialing a defined ARS leading digit followed by their extension number. This leading digit and extension number are passed through the network which will access the trunks on the main site. ARS digit modification for the trunks will insert the voice mail hunt group access code and outpulse the required codes and extension number to access their mailbox. Users will be prompted for their password.

Note: Advanced Analog Networking enhances message retrieval. ARS Modify Digits could insert the internal calling extension number automatically (i.e., <E>). Subscribers would simply dial a defined ARS digit string for message retrieval.

Using "COV Voice Mail with MSDN", remote subscribers call the voice mail hunt group pilot number directly through ARS. MSDN provides the subscriber’s extension number to the COV voice mail, allowing the voice processor to identify the caller as a subscriber. Voice mail then prompts the user for a password.

Messages can be retrieved external to the system dependent on incoming trunk access to the voice processor. Usually , subscribers will have to manually enter one or two digits followed by their mailbox number to log into their mailbox.

Release 3.2 4

Page 54

300 ICP Hardware User Guide

Trunks for Centralized Voice Mail

The node which provides the centralized voice mail using COV or ONS voice mail interfaces will require Loop Back Trunks regardless of network interfaces. When direct E&M analog connection to the voice mail can be utilized, Loop Back Trunks will not be required.

Call identity information that is required by voice mail systems for telephone answering is NOT presently part of the MSDN protocol. The trunks will be used to provide call identity to the voice processor; therefore, providing an efficient and easy to use voice mail interface for remote sites.

Loop Back Trunks

Any digital or analog E&M Tie Trunk may be used for Loop Back Trunks.

Traffic levels must be considered to determine the number of Loop Back Trunks required. Traffic will typically consist of rerouted calls for COV and ONS voice mail and message retrieval for ONS voice mail. E&M voice mail does not require use of Loop Back Trunks.

MSDN trunks will not ignore answer supervision. When the voice processor answers, an answer supervision signal is passed to the MSDN trunks and no more digits will be outpulsed to the voice processor. DTMF tones will not be received, resulting in improper call handling. Therefore, Loop Back Trunks are used on the Main system to ignore fake answer supervision allowing pauses and DTMF tones to be outpulsed to the voice processor for proper call handling.

In Voice Mail Connection with Loop Back Trunk, extension 5000 on the MAIN system is externally call forwarded to the central voice mail system on the remote system. The subscriber call reroutes to the ARS leading digit followed by his/her extension number "85000". The ARS programming in the MAIN system is programmed not to absorb the leading digit "8" allowing this digit to be outpulsed across the network to access the Loop Back Trunks.

The ARS for the Loop Back Trunks in the remote system is programmed to absorb the leading digit "8" and insert the voice mail hunt group pilot number "3000". The E&M Circuit Descriptor is programmed to insert the necessary pause in dialing before the remaining digits are sent. This will allow the voice mail system time to answer and receive the digits "5000", which route the caller to the associated mailbox.

Extension 5000 will retrieve voice mail messages by dialing the hunt group access code for "3000" on the remote system. No digits are absorbed or deleted on the main system.

Direct Connection to Voice Mail with E&M Trunks

If the voice mail system provided allows for direct E&M Trunk interface, this approach can be used eliminating the requirement for Loop Back Trunks. Analog E&M Trunks must be used to allow for flash transfer of calls.

In Voice Mail Connection with E&M Trunks, we have extension 5000 in system A externally call forwarded to the central voice mail system on system B. The subscriber call reroutes to the ARS leading digit followed by his/her extension number "85000". The ARS programming in system A is NOT to absorb the leading digit "8" allowing this digit to be outpulsed across the network to access the E&M Trunks to voice mail.

6 Release 3.2

Page 55

Specification

The ARS for the E&M Trunks in system B is programmed to absorb the leading digit "8". The E&M Circuit Descriptor is programmed to insert the necessary pause in dialing before the remaining digits are sent. This will allow the voice mail system time to answer and receive the digits "5000", which route the caller to the associated mailbox.

Extension 5000 will retrieve voice mail messages by dialing the ARS digit string defined for message retrieval followed by their extension number "8*5000". The ARS - modify digits in system A will not absorb or insert any digits so the E&M voice mail ports can be accessed on system B. ARS on system B will absorb the leading digit "8". The E&M Circuit Descriptor is programmed to insert the necessary pause in dialing before the remaining digits are sent. This pause allows the voice mail time to answer and receive the digits "*5000", which routes the subscriber’s call to the subscriber’s mailbox. The subscriber on extension 6000 on system B retrieves messages in the same manner by dialing "8*6000".

Data Applications

Refer to Data Applications and Advanced Data feature package for information on data call features.

Third Party Network Devices

The following devices may be used in digital networks with MSDN and non-MSDN applications to support customer data requirements:

• Drop and Insert

• Channel Signaling Unit (CSU)

• Channel Bank

• Multiplexer

• Inverse Multiplexers. Note: This section contains general guidelines for designing configurations that use these

devices. See the manufacturers' specifications for specific instructions.

Drop and Insert (D/I)

Drop and Insert (D/I) provides an economical means to directly access a T1 (1.544 Mbps) transmission system or a CEPT (2.048 Mbps) transmission system. This includes DS-1 or CEPT circuits connecting MSDN network nodes and direct T1 or CEPT connections. Mitel systems connected to other vendor systems with direct digital (T1 or CEPT) connections are also accommodated.

The D/I devices connects to the DS-1 or CEPT line drops/inserts information into the desired time slots and passes the remainder of the channels through on a digital basis.

Voice, data, television, and audio program channels can be dropped/inserted. The data channels can be configured to provide 56/64 x N synchronous data in some versions. The number of channels that can be dropped/inserted depends on the method used, and the manufacturer and the manufacture's model type. In theory, with some devices, 24 channels

Release 3.2 4

Page 56

300 ICP Hardware User Guide

can be dropped/inserted. Note that MSDN DS-1 links are limited to 23 channels because channel 24 is used for signaling.

The only advantage of switched data arrangements over drop/insert is when alternate routing is provided. Switched circuits can be configured to reroute automatically in case of primary route failure.

The following D/I devices are supported:

• Channel Service Unit (CSU)

• Channel Bank

• Multiplexer.

Channel Service Unit Drop/Insert

Drop/Insert Channel Service Units (CSUs) are available from various manufacturers and replace the standard CSUs used to connect the T1 span line to the system. Versions provide for 2 or 4 drop insert connections which are V.35 or RS-232 compatible. Speeds of up to 64 Kbps are supported. Some manufacturers have a 19.2 Kbps version.

Channel Banks for Drop/Insert

Channel Banks can also be used for drop/insert applications because two are required at each end. This can be a costly, not very efficient arrangement. The circuits dropped/inserted can be voice, data, or audio programming with the only limitation being the term sets available.

Drop and Insert Multiplexers

Drop and Insert Multiplexers (D/I MUX) provide an economical means to directly access a standard T1 (1.544 Mbps) digital transmission system. The D/I MUX provides dropping/inserting voice, data, audio program or TV channels. The D/I MUX is more cost-effective and provides better transmission quality than back-to-back channel banks. The D/I MUX can be configured to drop or insert "N" amount of channels (See manufacturer's instructions). Note that MSDN DS-1 links are limited to 23 channels because channel 24 is used for signaling.

The D/I MUX connects to the DS-1 line, drops/inserts information contained into the desired time slots, and passes the remainder of the channels through on a digital basis. The D/I MUX should pass bipolar violations unchanged to accommodate span line testing and 64 Kbps clear channel operation. In the event of an internal failure, the D/I MUX should automatically bypass the line.

The D/I MUX, normally, can be configured for communication up or down the span line, or both. Typically, communication will be toward a network system node where switching equipment and access to other networks is located. The D/I MUX can operate in systems terminated by digital switches or conventional D3 and D4 channel banks. It should be compatible with D1D, D2, D3, and D4 mode 3 frame formats.

The D/I MUX should be designed to be used at customer premises and along cable, digital microwave, and fiber optic span lines. For voice and data channel access, the manufacturers

8 Release 3.2

Page 57

Specification

have a number of different modules which vary depending on circuit type, signaling data rates, etc. Single channel synchronous data rates that are multiples of 56 or 64 Kbps, up to 1.536 Mbps, should be accommodated.

The D/I MUX can be used to drop and insert information for transmission in one direction (unidirectional) or two directions (bidirectional). The number of channels dropped and inserted may be up to 24 depending on the manufacturer’s configuration. The primary function performed by the D/I MUX is to provide access to a T1 line which is a full-duplex transmission medium.

In general, a typical system operates as follows: a T1 line enters the D/I MUX and drops off selected DS-0 channels which are received by the channel units, the channel unit then interfaces the baseband signals with the subscriber. In the reverse direction, the channel unit converts subscriber transmit information into a signal compatible with the D4 channelized T1 format which is then inserted into the T1 bit stream. All DS-0 channels not accessed pass through the D/I MUX.

Inverse Multiplexing

When given a single telephone number, an inverse multiplexer dials multiple digital "calls" between two sites and combines the bandwidth of the individual calls into a single, high-bandwidth channel. The inverse multiplexers at each end perform dialing, delay compensation and reordering tasks, and monitor and maintain the integrity of the connection. Inverse multiplexers can also combine leased and dialed bandwidth.

Inverse multiplexers can provide suitable bandwidth for data and video applications at rates from 56 Kbps to 4 Mbits using dialed and leased services depending on the manufacturer. Inverse multiplexers provide dynamic allocation of frequency and ISDN H-0, H-11 type services.

ISDN Basic Rate (BRI) an d Primary R ate (PRI) li nes provide access to swi tched and de dicated services within the wide area network (WAN), including 56K for T1 lines and 64K for E1 lines.The BRI card provides either 56K or 64K bandwidth per channel but does not perform any channel aggregation. An inverse multiplexer or similar device would be required to combine multiple switched 56K or 64K service channels for higher bandwidth.

Typical features on inverse multiplexers are:

• Field-selectable V.35, RS-449, or X.21 data ports

• RS-366, V.25 bis, X.21, and control-lead dialing

• Dual 56 ports for 112 Kbit/s operation

• Exact clocking and 56-64 Kbit/s rate adaption

• Speed dialing and stored call profiles

• Supports conference scheduling software

• Supports video

• Nx56, Nx64, and Nx384

• 56 Kbit/s to 4Mbit/s

• Built-in CSU/DSU.

Release 3.2 4

Page 58

300 ICP Hardware User Guide

MSDN Applications

Inverse multiplexers will be connected to system network nodes with T1/D4 circuits. When not in use, no circuits will be connected and no MSDN B-Channels will be occupied (see example).

In the example, the inverse multiplexer located in Dallas has dialed digits to set up DS-0 connections in both the Dallas and Kanata nodes. Six bearer (B) Channels on the first MSDN circuit were utilized. A bandwidth of 336/384 Kbps (H-0) is provided. Call set-up is flexible. DS-0 circuits within the system do not have to be sequential or in the same MSDN circuit. The six DS-0 connections required are distributed through both of the connecting MSDN circuits.

With a single MSDN circuit call, call set-up would be restricted to twenty-three DS-0 circuits (B Channels). Channel 24 is reserved for D Channel. When multiple MSDN circuits are available, rates above 23 X 64 Kbps can be set with the appropriate number of DS-0 (B Channels) distributed over the multiple MSDN circuits. Bandwidth Exceeding 23 x 64 Kbps Multiple MSDN Circuits illustrates a 1536/1344 Kbps (H-11) arrangement with twenty-four DS-0 circuits distributed over two MSDN circuits.

LAN/WAN

LAN Guidelines

T o maintain optimum voice quality, it is recommended that voice and data traffic be segregated as much as possible. There are three methods of segregation, depending on the existing LAN configuration:

1. Run Voice and Data on separate physical networks

2. Run Voice and Data on separate Virtual LANs (VLAN).

3. Use a separate subnet for voice traffic.

LAN Recommendations:

• Use Ethernet switches instead of hubs. It is recommended that IP telephones be in a single sub-net incorporating Layer 2 switches.

• Use Full Duplex Fast Ethernet where possible between switches.

• For the single-port telephones (4015 IP Phone/4025 IP Phone), provide two switched Ethernet drops to the desktop -- one for the PC and one for the IP telephone.

• For the dual-port telephones (5010 IP Phone/5020 IP Phone), you have two options. First, provide one switched Ethernet drop to the desktop for the PC/IP Phone. In this case, the PC connects to the network through the IP telephone. Second, provide two switched Ethernet drops, one for the PC and one for the IP telephone. For optimum voice quality, VLANs are highly recommended where only one Ethernet drop to the desktop is used.

• The 3300 ICP system should be installed in the same broadcast domain as the majority of the IP telephones.

• There should be only one active Dynamic Host Configuration Protocol (DHCP) server within the Broadcast Domain. The 3300 ICP system includes a DHCP server.

0 Release 3.2

Page 59

Specification

• Place functional groups on the same switches and/or subnets to reduce traffic across backbones and routers.

• IEEE 802.1 p/Q priority is supported at the telephones but not supported on the Mitel Networks 3300 Controller. Use Layer 2 Switches (port based) to set the voice VLAN default for the 3300 Controller, and to modify the data format to add 802.1 p/Q (tagging).

• When VLANs (802.1 p/Q) are used with the dual-port telephones (5010 IP Phone/5020 IP Phone), the Layer 2 switch ports connected to IP telephones must have the port configured to accept data already tagged for the voice VLAN and a default or native VLAN (typically set to 1) to accept untagged data from an attached PC and convert it to tagged data.

• Do not mix data and voice with the same priority. Set any queues and priority so that voice and data are different priority (for example, High - Voice, Low - Data).

• For mobility of IP telephones, it is recommended that Layer 2 switch ports configured for operation with the 3300 ICP server and IP telephones should have "spanning tree protocol" disabled and/or configured to "Portfast". It is important to ensure that the telephones and 3300 Controller are not connected to the network such that they could introduce a network loop.

• This system supports G711 voice encoding between IP telephones.

WAN Guidelines

Recommendations for connection across a Layer 3 switch or router:

• To forward a DHCP request across a Layer 3 switch or router, activate DHCP forwarding (DHCP Helper) on the router. Alternatively, use a secondary DHCP server on the remote side of the Layer 3 device. This secondary DHCP server must programmed with the same options as the main DHCP server for the telephones to operate properly.

• For optimum performance and voice quality when using IP telephones across routed links the routers should be configured to prioritize voice traffic based on Type Of Service (TOS) using techniques such as Weighted Fair Queuing (WFQ). IP phones are preset to precedence 5 with Minimum Delay. A high priority queue has settings 4, 5, 6, 7; A low priority queue has settings 0, 1, 2, 3. PCs should use low priority. On slow WAN links between routers set the Maximum Transmittable Unit (MTU) appropriately for the speed of the WAN link (a value of 500 is recommended for links using T1/E1 type seeds).

• Not all routers or Layer 3 switches will recognize 802.1p/Q VLAN information. In this situation, it will be necessary to provide a separate physical connection for each VLAN and subnet in use.

• The E2T / RTC Cards support the Internet Control Message Protocol (ICMP) Messages. Enable ICMP Redirect on your layer 3 switches and default gateway. The redirect will forward messages to the correct LAN segment and reduce broadcast messages and LAN usage.

• Minimum recommended WAN link speed is 1.544 Mbps (T1) with Frame Relay, HDLC, PPP, and compressed PPP.

• If the Layer 3 switch or router can support TOS and queue priority, then don't use more than 70% bandwidth. If the Layer 3 switch or router cannot support TOS queue, then no

Release 3.2 5

Page 60

300 ICP Hardware User Guide

more than 40% bandwidth should be used. The usage of the link should be determined before installing IP phones to determine the level of operation possible. A heavily used link may require an upgrade or implementation of TOS and MTU (500) settings.

Plan the Network

The 3300 ICP system is available in four main configurations:

1. IP tel eph one onl y

2. Analog Services Unit only

3. IP tel eph one and Analo g Ser vic es Uni t

4. ICP system with Peripheral and/or DSU Units.

When the 3300 ICP system is installed with the IP telephone option you will need two IP addresses for the system ( E2T, RTC) and a range of IP addresses for the IP telephones.

The 3300 Controller uses a number of fixed IP addresses internally. It is highly recommended that IP addresses in the following range, NOT be present within the network: 192.168.10.X to

192.168.13.X. The 3300 Controller includes an internal Layer 2 switch for local communication. Only one connection is required to connect the unit to the network; this port should be set to Auto Configure, and should be connected to operate with 100BaseT for optimum performance. The remaining connections can be used for voice application devices, or left as spares. They should not be used to carry network traffic, other than that destined for the 3300 Controller. This will minimise unwanted data traffic which would otherwise reduce available connection bandwidth.

Note: The Real Time Complex (RTC) is used for the IP telephones signaling and also DHCP, TFTP, etc. Call progress, device status and screen updated messages are sent between the IP telephones and the RTC. The E2T (Ethernet to TDM) card is where the Ethernet voice is converted to TDM and vice versa.

2 Release 3.2

Page 61

3300 Controller

Mitel Networks™ 3300 Controller Components

Front Panel

• Remote Alarm port (DB-9 connector)

• Two RS-232 ports (DB-9 connectors) (Printer and Maintenance)

• Dual FIM ports to support the NSUs (Network Services Units)

• L2 switch provides four 10/100 Ethernet connections via RJ-45 (8-pin CAT5 cross-over cable)

• Four 2 MB CIM (copper interface module) ports are used to connect to the ASUs (Analog Services Units) with cross-over Category 5 cable

• FIM (fiber interface module), CIM (copper interface module), and Alarm LEDs.

Specification

Rear Panel

• Power connector

• Supplementary ground to ground the chassis to the rack.

Internal Components

• 20 GB EIDE hard drive

• 256 Mbytes of memory on the 300 MHz RTC that provides main control

• Stratum 3 clock

• 64 or 128 channel echo canceller (small and large 3300 Controller)

• 128 Ethernet to Time Division Multiplex (E2T) channels (300 MHz)

• Power fail protected real-time clock

• Digital Signal Processor (DSP) (provides for tone and conference functions)

• Two cooling fans.

Release 3.2 5

Page 62

300 ICP Hardware User Guide

Configurations

There are several configuration opti ons for the 3300 ICP:

• 250 user system without compression

• 250 user system with 32 compression channels

• 250 user system with 64 compression channels

• 700 user system without compression

• 700 user system with 32 compression channels

• 700 user system with 64 compression channels.

The following top view diagram shows the MMC/A slot numbering convention. The diagram also indicates the type of MMC module that will be used in a particular slot. Slots 1 through 4 allow connectors to protrude through the front panel.

4 Release 3.2

Page 63

Specification

250 User System without Compression

This system uses:

• One 300 MHz RTC

• One 300 MHz E2T

• One 64 Channel Echo Canceller

• One Dual FIM

• One 21161 DSP Module for tone and conference support

This provides:

• Four DSP devices, to provide tone and conference functions

• 64 Channels of Echo Cancellation

• Two External FIM connections

• Four ASU connections (integral to unit)

The two external FIM connections are for providing connectivity for up to two Peripheral Units or up to four NSUs. Note that there are two T1/E1 links per NSU.

Release 3.2 5

Page 64

300 ICP Hardware User Guide

250 User System with 32 Compression Channels

This system uses:

• One 300 MHz RTC

• One 300 MHz E2T

• One 64 Channel Echo Canceller

• One Dual FIM

• One Quad DSP Module for tone and conference support

• One Quad DSP for 32 Channels of compression

This provides:

• Four DSP devices, to provide tone and conference functions

• Four DSP devices, to provide 32 channels of compression

• 64 Channels of Echo Cancellation

• Two External FIM connections

• Four ASU connections (integral to unit)

The two external FIM connections are for providing connectivity for up to two Peripheral Units or up to four NSUs. Note that there are two T1/E1 links per NSU.

6 Release 3.2

Page 65

250 User System with 64 Compression Channels

This system uses:

• One 300 MHz RTC

• One 300 MHz E2T

• One 64 Channel Echo Canceller

• One Dual FIM

• One Quad DSP Module for tone and conference support

• Two Quad DSP Modules for 64 Channels of compression

This provides:

• Four DSP devices, to provide tone and conference functions

• Eight DSP devices, to provide 64 channels of compression

• 64 Channels of Echo Cancellation

• Two External FIM connections

Specification

• Four ASU connections (integral to unit)

The two external FIM connections are for providing connectivity for up to two Peripheral Units or up to four NSUs. Note that there are two T1/E1 links per NSU.

Release 3.2 5

Page 66

300 ICP Hardware User Guide

700 User System without Compression

This system uses:

• One 300 MHz RTC

• One 300 MHz E2T

• One 128 Channel Echo Canceller

• Two Dual FIMs

• Two Quad DSP Modules for tone and conference support

This provides:

• Eight DSP devices, to provide tone and conference functions

• 128 Channels of Echo Cancellation

• Two External FIM connections

• Four ASU connections (integral to unit)

The four external FIM connections are for providing connectivity for up to two Peripheral Shelves or up to six NSUs. Note that there are two T1/E1 links per NSU.

8 Release 3.2

Page 67

700 User System with 32 Compression Channels

This system uses:

• One 300 MHz RTC

• One 300 MHz E2T

• One 128 Channel Echo Canceller

• Two Dual FIMs

• Two Quad DSP Modules for tone and conference support

• One Quad DSP Module for 32 Channels of Compression

This provides:

• Eight DSP devices, to provide tone and conference functions

• Four DSP devices, to provide 64 channels of compression

• 128 Channels of Echo Cancellation

• Four External FIM connections

Specification

• Four ASU connections (integral to unit)

The four external FIM connections are for providing connectivity for up to two Peripheral Units or up to six NSUs. Note that there are two T1/E1 links per NSU.

Release 3.2 5

Page 68

300 ICP Hardware User Guide

700 User System with 64 Compression Channels

This system uses:

• One 300 MHz RTC

• One 300 MHz E2T

• One 128 Channel Echo Canceller

• Two Dual FIMs

• Two Quad DSP Modules for tone and conference support

• Two Quad DSP Modules for 64 Channels of Compression

This provides:

• Eight DSP devices, to provide tone and conference functions

• Eight DSP devices, to provide 64 channels of compression

• 128 Channels of Echo Cancellation

• Four External FIM connections

• Four ASU connections (integral to unit)

The four external FIM connections are for providing connectivity for up to two Peripheral Units or up to six NSUs. Note that there are two T1/E1 links per NSU.

0 Release 3.2

Page 69

Specification

E2T Compression

The 3300 ICP provides the option of G.729a voice compression. Licenses and the 21161 Quad DSP Modules enable this feature to a maximum 64 compression channels. Compression is carried out by the 21161 DSP under the control of the E2T.

IP phone to IP phone calls also support compression. Compression for this scenario is applied by DSP resources in the phones and does not require compression licenses.

The compression of a standard call effectively reduces the bandwidth required per call from 64kbps to approximately 8kbps plus packet overhead.

Note: Only IP phones can be put in separate compression zones. The TDM resource of the system is always left in the default zone.

In the following example, when an IP device (assigned to a non-default zone) calls a TDM device, G.729ac compression will be invoked on the LAN or WAN side of the call providing there are adequate compression resources available in the controller. The same applies to calls originate from a TDM device and terminate on an IP device.

Release 3.2 6

Page 70

300 ICP Hardware User Guide

Mitel Networks 3300 Controller Dimensions

Height 2.625 in. (6.66 cm) (1.5 U) Width 17.75 in. (45.1 cm) (1 9" rack mount able) Depth 15.5 in. (39.4 cm) Weight 15.8 lb (7.17 kg)

3300 Controller Environment

Condition Specification

Temperature -40º to 140º F (-40º to +60º C) Humidity 15-95% Relative Humidity, non-condensing Vibration

Mechanical Stress One 15.3 cm (6 in.) drop, each edge and corner adjacent to the rest face –

0.5 g, 7 to 100 Hz, any orthogonal axis

1.5 g, 100 to 500 Hz, any orthogonal axis

unpackaged One 76.2 cm (30 in.) drop, each edge and corner packaged in cardboard &

foam.

Physical Dimensions

Storage Environment

Operational Environment

Condition Specification

Temperature 41º to 95º F (5º to 35º C) Humidity 40-90% Relative Humidity, non condensing Maximum Heat Dissipation - fully

loaded (see Note) Air Flow 46 cubic feet per minute at maximum output of the fans Acoustic Emissions Max imum 50 dBA continuous, 75 d B intermittent (<10% dut y

Conversion factors: 1 watt is equal to 3.412 BTUs per hour, 1 ton of refrigeration is equal to 12,000 BTUs per hour or 3.516 Kilowatts, and 3/4 Kilowatt-hour is equal to 1 ton of refrigeration.

750 BTUs per hour

cycle)

3300 Controller Power

Power Supply

Input / disconnect IEC 320 AC connector Operation 120 Vac/230 Vac or auto selectable Maximum input power 200 W AC source 90 - 264 Vac; 47 - 63Hz

Output Power

Output Voltage Max Current +3.3 +/- 1.5% 30.0A +5.0V +/- 1% 8.0A (Total power of 3.3V and 5.0V not to exceed 100W) +12.0V +/- 7% 3.0A (Hard Disk Drive)

2 Release 3.2

Page 71

3300 Controller IRQ Assignments

IRQ Signal Comment

IRQ0 PSI NMI - comes from Power supply via Midplane IRQ1 None (PCI -

Optional)

IRQ2 IRQ_HI_MMC_N Higher priority interrupt from Midplane, filtered through

IRQ3 CKSTP_OUT_IRQ3 From COP interface - not used, pulled up IRQ4 IRQ_LO_MMC_N Lower priority interrupt from Midplane, filtered through

IRQ5 FP_N Frame Pulse interrupt for TestEng., pulled up IRQ6 ATA2_IRQ_N from Hard Drive, filtered through CPLD_8260_ATA IRQ7 - Not used, pulled up

IRQ Assignments

---comes from Power supply via Midplane - stuffing option if it cannot be handled under IRQ0

CPLD_8260_MMC

3300 Controller PCB Interfaces

PCB (Printed Circuit Board) Interfaces

Specification

Connector

Function

RS-232 DB9 2 Txd, Rxd, (RTS), (CTS),

EIDE 40 pin male 1 Internal Hard Disk Drive Internal to box. (On RTC) 10/100

Ethernet CIM 8-pin Mod- jack 4 Txlink, Rxlink

Power Per power supply Per power

Alarm Drive DB9 1 Contact closures, Critical,

Type Quantity Signals Comments

DCE pinout. (DTR), (CD), DSR, Gnd (parenthesis indicates operational function, dependent upon application)

8-pin Mod- jack 4 TxP, TxN , RxP, RxN

(Cross-over DX connect ions)

(all differential pairs) +5v, +3.3v, +12v, -12v, Gnd,

supply

Power-good

Major, Minor alarms

Female style.

Supports rates to 115K.

Default setting 9600, 8

bits, No Parity, 1 Stop-bit,

Txd, Rxd, Gnd

User side pinout

Pinout is based on

standard IT cable pairs.

Internal to box, AC to

integral PSU, or DC to

external PSU

DB9 connection (female

connection)

Release 3.2 6

Page 72

300 ICP Hardware User Guide

3300 Network Services Units

Mitel Networks™ 3300 Universal NSU Components

Front panel

• RS-232 serial port (DB9 connector to a PC) for maintenance purposes such as field installation, database upgrade, access to logs, and modem connection for remote access

• Ethernet port (RJ-45 connector) for future use

• Faceplate LEDs - Miscellaneous, Link Status, and Message Link Controlled

• FIM port for fiber connection to the 3300 Controller

• Two CIM ports

• Reset pin.

Rear panel

• DIP switch up (1) position for FIM connection; down (2) for CIM connection

• Two T1/ E1 ports (RJ-45 connectors for T1; RJ-45 or ground and coax for E1) for network connection

• Two hybrid port status LEDs

• Two hybrid port DIP switch complexes

• Power connector

• Supplementary ground (to ground the chassis).

4 Release 3.2

Page 73

Specification

3300 Universal NSU Protocols

The 3300 Universal NSU provides T1 or E1 connectivity and supports up to two links per unit. The protocols supported by the interfaces are:

• T1 - PRI, Q.Sig, DPNSS, T1/D4

• E1 - PRI, Q.Sig, DPNSS, DASSII

• PRI variant - DMS-250, DMS-100, 4ESS, NI-2, 5ESS, and Euro ISDN (NET5, Q.SIG) Protocol variant - EURO_STANDARD, EURO_NUMERIS, EURO_CAYMAN, NI2_STANDARD, NI2_5ESS, NI2_GTD5, QSIG_ISO, QSIG_ETSI)

Note: Q.SIG uses Master/Slave. All others use User/Network. T1/E1 running PRI or Q.SIG will support XNET over PRI, NFAS, D-Channel Backup, and Min/Max functionality.

3300 Universal NSU DIP Switch Settings

DIP Switch Use Notes

1 Tx Ground Ground when down; floating when up. 2 Rx Ground Ground when down; floating when up. 3 Impedance selector #1 120 ohm (enabled when down) 4 Impedance selector #2 100 ohm (enabled when down) 5 Impedance selector #3 75 ohm (enabled when down) 6 LT/NT selecto r Up for NT; down for LT.

Hybrid Port DIP Switch Settings

PRI/T1 Mode Connector DIP Switch Settings

I #1

Gnd

Impedance 1 Tx Gnd 2 Rx Gnd

100 Up Up Up Down Up Down

BNC Adapter

Required

No 120 Up Up Down Up Up Up

No 120 Up Up Down Up Up Down Yes 75 Not e Note Up Up Down Up Yes 75 Not e Note Up Up Down Down

Note: Site dependant - normally Tx is grounde d and Rx is not grou nd ed, bu t that dep ends on which remote connection is grounded.

E1/MF-R2 Mode/Connector DIP Switch Settings

Impedance

Gnd

I #2

3 120 ohm

100

ohm

I #3

ohm

LT/NT

Release 3.2 6

Page 74

300 ICP Hardware User Guide

Mitel Networks™ 3300 R2 NSU Components

Front panel

• RS-232 serial port (DB9 connector to a PC) for maintenance purposes such as field installation, database upgrade, access to logs, and modem connection for remote access

• Ethernet port (RJ-45 connector) for future use

• Faceplate LEDs - Miscellaneous, Link Status, and Message Link Controlled

• FIM port for fiber connection to the 3300 Controller

• Two CIM ports

• Reset pin.

Rear panel

• DIP switch up (1) position for FIM connection; down (2) for CIM connection

• Two E1 ports (RJ-45 connectors) for network connection

• Two hybrid port status LEDs

• Two hybrid port DIP switch complexes

• Power connector

• Supplementary ground (to ground the chassis).

3300 R2 NSU Protocols

R2 is a protocol converter that allows the 3300 R2 NSU to access an R2 National Public Switched T elephone Network (PSTN) using MF-R2 digital trunk signaling. The 3300 Controller also receives and processes Calling Line Identification (CLI) and allows the information to be displayed on the user's telephone display screen.

The 3300 R2 NSU supports the CCITT Blue Book, Volume VI, Fascicle VI.4, Specifications of Signaling System R2, Recommendations Q.440 to Q.490 (with the exception of Echo Suppression (Q.479), Test Calls (Q.490) and international signals).

The 3300 R2 NSU converts the following:

• Incoming MF-R2 signals from the PSTN into Digital Private Network Signaling System (DPNSS) signals for the system

• Outgoing DPNSS signals from the system into MF-R2 signals for the PSTN.

6 Release 3.2

Page 75

Specification

3300 R2 NSU DIP Switch Settings

DIP Switch Use Default Setting Notes

1 Tx Ground Up Tx shield ground when down 2 Rx Ground Up Rx shield ground when do wn 3 Impedance selector #1 Up 120 ohm 4 Impedance selector #2 Up 100 ohm 5 Impedance selector #3 Up 75 ohm 6 LT/N T selector Up Up for NT, down for LT

E1/MF-R2 Mode/Connector DIP Switch Setting

MF-R2 Port DIP Switch Se tt in gs

BNC Adapter

Required

No 120 NT Up Up Down Up Up Up

No 120 LT Up Up Down Up Up Down Yes 75 NT Note Note Up Up Down Up Yes 75 LT Note Note Up Up Down Down

Note: Site dependent - normally Tx is grounded and Rx is not grounded, but that depends on which remote connection is grounded.

Imped

ance

LT/NT

Mode1 Tx Gnd2 Rx Gnd

120

ohm

100

ohm

LT/NT

Mitel Networks™ 3300 BRI NSU Components

Front panel

• RS-232 serial port (DB9 connector) for installation, configuration, and maintenance

• BRI Circuit LEDs

• CEPT link Status LED

• Power LED

• Reset pin.

Rear panel

• Ethernet port (RJ-45 connector) for future use

• E1 port to connect to an NSU that is running E1 DPNSS

• E1 port DIP switches

• BRI connector (25-pair male D-type)

Release 3.2 6

Page 76

300 ICP Hardware User Guide

• Supplementary ground to ground the chassis

• Power connector.

Note: UK BRI will drive power to the BRI circuits; the NA BRI will not.

3300 BRI NSU Protocols

Fifteen interfaces are programmed for line support in the NA product and line or trunk support in the UK version. The 3300 BRI NSU protocols are

• Euro-ISDN 2B+D, Basic Rate Interface

• North American National ISDN-1

• North American National ISDN-2.

Mitel Networks 3300 NSU Dimensions

Height 1.75 in. (4.454 cm) (1 U) Width 17.75 in. (45.1 cm) (19" rack mountable) Depth 15.5 in. (3 9.4 cm) Weight 9.41 lb (4.27 kg)

Physical Dimensions

3300 NSU Environment

Condition Specification

Temperature -40º to 140ºF (-40º to +60ºC) Humidity 15-95% Relative Humidity, non-condensing Vibration

Mechanical Stress One 15.3 cm (6 in.) drop, each edge and corner adjacent to the rest face –

0.5 g, 7 to 100 Hz, any orthogonal axis

1.5 g, 100 to 500 Hz, any orthogonal axis

unpackaged One 76.2 cm (30 in.) drop , each edge and corner packaged in cardboard & foam.

Storage Environment

8 Release 3.2

Page 77

Specification

Operational Environment

Condition Specification

Temperature 41º to 122ºF (5º to 50ºC) Humidity 34-95% Relative Humi di ty, non-condensing Maximum Heat Dissipation -

170 BTUs per hour

fully loaded (see Note) Conversion factors: 1 watt is equal to 3.412 BTUs per hour, 1 ton of refrigeration is equal to 12,000

BTUs per hour or 3.516 Kilowatts, and 3/4 Kilowatt-hour is equal to 1 ton of refrigeration.

3300 NSU Power

Input / disconnect IEC 320 AC connector Operation 120 Vac/230 Vac Switch or auto selectable Maximum power output 60 W (Universal and R2)

40 W (BRI)

AC source 90 - 132 Vac; 47 - 63Hz in North America

180 - 264 Vac; 47 - 63Hz in Europe

Power Supply

Output Power

Output Voltage Max Current +5.0V +/- 5% 8.0A

(BRI Note: total power of 12V and 5V not to exceed 60W)

BRI only +12.0V +/- 7% 3.0A (Line power supply)

3300 NSU Pin Allocations

Signal Name RJ-45 Connector Pin

T1 and E1 Connector Allocation

RXRING 1

RXTIP 2

Not used 3

TXRING 4

TXTIP 5 Not used 6 Not used 7 Not used 8

Release 3.2 6

Page 78

300 ICP Hardware User Guide

Signal Name RJ-45 Connector Pin

DTR (data terminal ready)

DCD (data carrier detector)

RXD (receive data) 2

TXD (transmit data) 3

DTR (data terminal ready) 4

RTS (ready to send) 7

CTS (clear to send) 8

RS-232 Maintenance Connector Allocation

GND 5

Not used 6

Not used 9

BRI Connector Allocation

T1 1 T2 2 T3 3 T4 4 T5 5 T6 6 T7 7 T8 8

T9 9 T10 10 T11 11 T12 12 T13 13 T14 14 T15 15

R1 26 R2 27 R3 28 R4 29 R5 30 R6 31 R7 32 R8 33

R9 34 R10 35 R11 36 R12 37 R13 38 R14 39 R15 40

0 Release 3.2

Page 79

3300 Analog Services Uni ts

Mitel Networks™ 3300 Universal ASU Components

Front Panel

• 16 ONS LEDs showing circuit status

• 4 LS trunk LEDs showing circuit status

• 1 CIM Status LED

• RJ-45 connector (CIM connection to the 3300 Controller).

Rear Panel

• D-type 25 pair connector providing connectivity to the LS and ONS Tip/Ring or A/B circuits

Specification

• 8 pin modular jack (RJ-45) for 2 Paging ports

• 8 pin modular jack(RJ-45) for 4 Music on Hold ports (only one MOH port is supported through software on the system)

• Standard Male IEC 320 AC power connector.

Mitel Networks™ 3300 ASU Components

Front Panel

• 24 ONS Circuit LEDs indicate the status of the telephone circuits

• 1 CIM circuit LED indicates the status of the CIM link

• RJ-45 connector (CIM connection to the 3300 Controller).

Release 3.2 7

Page 80

300 ICP Hardware User Guide

Rear Panel

• 25 pair D-type connector provides access to the LS and ONS Tip/Ring or A/B circuits.

• Standard Male IEC AC input connector for power requirement.

3300 ASU and Universal ASU Dimensions

Height 1.75 in. (4.454 cm) (1 U) Width 17.75 in. (45.1 cm) (19" rack mountable) Depth 15.5 in. (39.4 cm) Weight 10.61 lb (4.81 kg)

Physical Dimensions

3300 ASU and Universal ASU Environment

Condition Specification

Temperature -40º to 140ºF (-40º to +60ºC) Humidity 15-95% Relative Humidity, non-condensing Vibration

Mechanical Stress One 15.3 cm (6 in.) drop, each edge and corner adjacent to the rest face –

Condition Specification

Temperature 41º to 122ºF (5º to 50ºC) Humidity 34-95% Relative Humidity, non-condensing Maximum Heat Dissipation -

fully loaded (see Note) Conversion factors: 1 watt is equal to 3.412 BTUs per hour, 1 ton of refrigeration is equal to 12,000

BTUs per hour or 3.516 Kilowatts, and 3/4 Kilowatt-hour is equal to 1 ton of refrigeration.

0.5 g, 7 to 100 Hz, any orthogonal axis

1.5 g, 100 to 500 Hz, any orthogonal axis

unpackaged One 76.2 cm (30 in.) drop, each edge and corner packaged in cardboard & foam.

Storage Environment

Operational Environment

170 BTUs per hour

2 Release 3.2

Page 81

Specification

3300 ASU and Universal ASU Power

Note: Connector is a Standard Male IEC320 AC input. Voltage Universal input design, operating input voltages from 90VAC to 264VAC.

Current < 1.0A RMS at 90VAC and full rated load. Frequency AC input frequencies from 47Hz to 63Hz. Holdover With an input voltage of 120VAC or 240VAC under a full rated load, the

Brown-Out Reco very Recovers from an AC input brown-out or sag condition automatically.

Power Supply Input Specifications

It regulates a +5, -48V, -30V, -5V, 7 0VAC ri ngi ng s ig nal , an d th e –1 15VAC Message Waiting Signal.

power supply outputs remain in regulation for a minimum of 16ms after loss of AC mains input voltage.

3300 ASU and Universal ASU Pin Allocations

Pin Signal Pin Signal

1 RX+ 5 Not Used 2 RX- 6 TX3 TX+ 7 Not Used 4 Not Used 8 Not Used

Note: The 3300 Univ ersal ASU connec ts to the 3 300 Con troller over a Ca tegory 5 Univers al Tw isted Pair (UTP) cross-over cable thro ugh a CI M interfa ce. The Ca tegory 5 c able is of the same type us ed for Ethernet connections and within the cable twisted pairs are arranged as: 1,2: 3,6; 4,5; 7,8. Each tied pair is connected to a 75 ohm resistor. The 3300 Universal ASU can b e lo ca ted up to 30 meters (98.4 feet) away from th e 3300 Controller. Th e interface employ s a single standard 8-pin modular jac k consisting of 2 balanced signal pairs and is located on the front of the unit.

CIM Connector Pin Allocations

25 pair Connector Pin Allocations

Pin Signal Pin Signal

Note: Connection of the Tip and Ring (A and B) leads of the ONS lines and LS trunk circuits are

through a 25 pair female D-type connector.

1 ONS Tip 1 26 ONS Ring 1 2 ONS Tip 2 27 ONS Ring 2 3 ONS Tip 3 28 ONS Ring 3 4 ONS Tip 4 29 ONS Ring 4 5 ONS Tip 5 30 ONS Ring 5 6 ONS Tip 6 31 ONS Ring 6 7 ONS Tip 7 32 ONS Ring 7 8 ONS Tip 8 33 ONS Ring 8

9 ONS Tip 9 34 ONS Ring 9 10 ONS Tip 10 35 ONS Ring 10 11 ONS Tip 11 36 ONS Ring 11 12 ONS Tip 12 37 ONS Ring 12 13 ONS Tip 13 38 ONS Ring 13

Release 3.2 7

Page 82

300 ICP Hardware User Guide

25 pair Connector Pin Allocations (continued)

Pin Signal Pin Signal

14 ONS Tip 14 39 ONS Ring 14 15 ONS Tip 15 40 ONS Ring 15 16 ONS Tip 16 41 ONS Ring 16 17 LS Tip 1 42 LS Ring 1 18 LS Tip 1-1 43 LS Ring 1-1 19 LS Tip 2 44 LS Ring 2 20 LS Tip 1-2 45 LS Ring 1-2 21 LS Tip 3 46 LS Ring 3 22 LS Tip 1-3 47 LS Ring 1-3 23 LS Tip 4 48 LS Ring 4 24 LS Tip 1-4 49 LS Ring 1-4 25 N/C 50 N/C

Music on Hold Connector Pin Allocations (Universal ASU only)

Pin Signal Pin Signal

1 Tip 1 5 Ring 3 2 Ring 1 6 Ring 2 3 Tip 2 7 Tip 4 4 Tip 3 8 Ring 4

Note: The four MOH tips & rings occupy an 8 pin female modular jack located on the rear panel. Note: Only one port is supported through software on the system.

Note: The paging port employs a single sta ndard 8-pin m odular RJ-45 jack located on the rear pan el.

Each paging port has a tip/ring pa ir for audio and a seco nd tip/ri ng pair desig nat ed tip1/ri ng1 contac t closures for zone control.

Paging Connector Pin Assignments (Universal ASU only)

Pin Signal Pin Signal

1 Tip 1 5 Ring 2 2 Ring 1 6 Ring 1-1 3 Tip 1-1 7 Tip 1-2 4 Tip 2 8 Ring 1-2

ONS Line Specifications

ONS Line Features (ASU)

The ONS line circuit has the following features:

• Maximum of 600-Ohm external loop drive capability. This equates to approximately one mile of loop range over 26-gauge cable terminated by a 150-Ohm set. Longer loops are supported but with the characteristics as described by the next bullet item.

4 Release 3.2

Page 83

Specification

• Constant current design with the loop current set at 25mA. If the loop range extends pass 600 Ohm, this circuit will revert to a voltage feed of approximately 2xVdc (design dependant parameter between 22-26 Vdc). The circuit remains active and the loop current will be dependant on the external loop impedance.

• Supports a Ringing Equivalent Number (REN) of 3.

• Capable of on-hook transmission. Used in conjunction with a centralized resource to deliver calling line ID .

• Positive disconnect (removal of battery from the ring lead).

• Battery reversal (UK< LA< EU variants only - used for CLID).

• Ground button detection.

• Message waiting indication (dc voltage method).

• Message waiting indication (class message).

• Status led indicator per circuit.

• Low level diagnostics.

ONS Transmission Parameters (ASU)

Transmission Parameters for NA Parameters for UK

Input Impedance 600 ohms 300R + (1000R // 220uF) Balance Impedance 600 ohms 300R + (1000R // 220uF) Digital Coding ITU µ-law – MT8966 CODEC ITU A-law – MT8967 CODEC

Transmission Parameters for LA Parameters for EU

Input Impedance 600 ohms 270R + (750R // 150uF) Balance Impedance 600 ohms 270R + (750R // 150uF) Digital Coding ITU µ-law – MT8966 CODEC ITU A-law – MT8967 CODEC

ONS DC Supervision Parameters (ASU)

DC Supervision Parameters for NA/LA Parameters for UK/EU

Battery Feed -30Vdc feed, constant current set

at 25mA +/- 1mA Loop Resistance 600 Ohms (includes set) 600 Ohms (includes set) Loop Detect Threshold 12mA 12mA Flash Detect SW timed function from switch

hook detector Ground button detect

threshold Positive Disconnect SW time d function that breaks loo p

13mA Tip or Ring to ground in off

hook state

current

-30Vdc feed, constant current set at 25mA +/- 1mA

SW timed function from SWHK detector

13mA tip or Ring to ground in the off hook state

SW timed function that breaks loop current

Release 3.2 7

Page 84

300 ICP Hardware User Guide

ONS Ringing Parameters (ASU)

Ringing Parameters for NA/LA Parameters for UK/EU

Voltage 65 Vrms sinewave superimposed

Frequency 20Hz 25 Hz Trip Battery

Silent interval Ring Interval

Number of bri dged ringers 3 3 Max. bridged capacitance 3uF//15kOhms 3uF//15Kohms Ring Trip detect time HW detector response <100ms

SW ring trip response t ime Within 50ms of switch hook detec t Within 50ms of switch h ook detect

ONS Message Waiting Parameters (ASU)

Message Waiting Parameters for NA/LA Parameters for UK/EU

Voltage -115Vdc +/- 5V dc -115Vdc +/- 5V dc Source Impedance Between 2k and 4K Between 2k and 4K MSW trip SW control, interlocks with

Flash Rate Cadenced, SW controlled. 300ms

onto –48Vdc

-30Vdc

-50Vdc

HW ring trip overrides ap pli ca tion of ringing signal

application of ringing

on/1500ms off cont.

65 Vrms sinewave superimposed onto –48Vdc

-30Vdc

-50Vdc

HW detector response <100ms HW ring trip overrides application of ringing signal

SW control, interlocks with application of ringing

Cadenced, SW controlled. 300ms on/1500ms off cont.

LS Trunk Specifications

LS Trunk Features (3300 Universal ASU only)

Four Loop Start (LS) trunk circuits are supported by the 3300 Universal ASU with the following features:

• Loop Start trunk capability only

• 50Hz meter pulse detection over a second T/R pair is supported on the UK variant

• Loop disconnect detection

• Loop reversal detection

• Incoming ringing detection

• Status led indicator per circuit

• Low level diagnostics

• Power Cross-protection as specified by CSA/UL 950 Safety Specifications

• Lightning Protection as specified by FCC Part 68/CS-03.

6 Release 3.2

Page 85

Specification

LS Trunk Signaling Protocols (3300 Universal ASU)

LS Trunk Signaling Supported Protocols

ASU Variant LS Protocol

North America (NA) Latin America (LA)

United Kingdom (UK) UK Subscriber / Subsidiary Loop United Kingdom (UK) UK Loop Start Disconnect Clear United Kingdom (UK)

Europe (EU)

TIA/EIA-464-B

CTR-21

LS Trunk Parameters (3300 Universal ASU)

Trunk Functions Parameters for NA/LA Parameters for UK/EU

Input Impedance 600 Ohms 370R + (620R//310uF) (UK)

270R + (750R//150uF) (EU)

Balance Impedance 600 Ohms for short loop

application 350R + (1000R// .21uF) for

long loops Min. operating loop current 18mA 18mA Max operating loop current 100mA 60mA Loop Current Limit None 60mA Ring detector Thresho ld 30Vrms 20Vrms Dummy Ringer load 10kOhms + 2.2uF (NA)

65Ohms + 2.2uF (LA) Reversal detector Detects CO battery polarity Detects CO battery polarity Loop detect for CO d isc. ( no

battery) Meter Pulse Detection None 50Hz longitudinal (UK)

Note: The NA variant is designed according to the performance standard EIA/TIA 464C. The UK Variant is designed i n accordanc e with CTR21, but has desi gn parameters fa voring towa rds BS6305 and BS6450. The EU variant is designed in accordance with CTR21.

< 2V across Tip and Ring < 2V across Tip and Ring

370R + (620R//310uF) (UK) 27 0R + (750R//150uF) (EU)for all loop lengths

10kOhms + 2.2uF

None (EU)

Music On Hold (3300 Universal ASU only)

Four physical ports are supported for Music on Hold (MOH) on the 3300 Universal ASU.

The MOH interface supports the following features:

• 600 Ohm input impedance

• Signal level overload protection as mandated by FCC part 68 on encoded analog content

• Dry Tip/Ring interface (no battery)

• Always active input (no external control required or provided).

Release 3.2 7

Page 86

300 ICP Hardware User Guide

The four MOH tips & rings occupy an 8 pin female modular jack located on the rear panel.

Note: Only one port is supported through software on the system.

Paging (3300 Universal ASU only)

There are two paging ports on the 3300 Universal ASU. The paging port is a transformer coupled interface with 600 ohms input impedance. The port is full duplex and has a complete 2/4 wire hybrid interface. The Balance impedance is set at 600 ohms.

Paging is accomplished by one of two methods:

• Zone control via outpulsed DTMF digits

• Emulates E&M trunks, using the contact closure control.

The 3300 Universal ASU provides two overhead paging outputs. In combination with their relay contacts, two paging zones are supported.

ASU Paging Zone Number

1 1 Off 2 1 On 3 2 Off 4 2 On 0 1 & 2 Off & Off

Paging Audio Circuit

Number

Paging Circuit’s Relay Position

System Fail Transf er (3300 Universal ASU only)

Four System Fail Transfer (SFT) relays are supported, one per LS trunk circuit. Control of the relay is via loss of power (power fail transfer), or software directed transfer (System Fail Transfer).

The SFT switches activate under the following conditions:

• Failure of the 3300 Controller

• Interruption of the system AC power

• Loss of the CIM link between the 3300 Controller and ASUs.

SFT requires fixed mapping between four ONS ports and LS trunks as follows:

LS Trunk ONS Port

1 13 2 14 3 15 4 16

8 Release 3.2

Page 87

Note: When the 3300 Universal ASU is in reset condition it goes into System Fail Transfer

mode. While in this mode, the 4 ONS pre-defined circuits and the corresponding LS circuits will be connected together by hardware relays allowing callers to make calls without any local call control intervention (telephones are connected directly to the CO or exchange).

Peripheral Node

Peripheral Unit Components

Each peripheral cabinet holds up to 12 Peripheral Interface Cards and provides up to 192 ONS or DNI ports. With the Peripheral Unit Expansion, a slave cabinet can be added that expands the unit up to a total of 384 ports and 24 Peripheral Interface cards (the number of voice channels remains the same). One Peripheral Switch Controller (PSC) card and one Fiber Interface Module (FIM ) is inst alled in t he master cabinet of each Peri pheral Uni t. The PSC card prov ides control for all Peripheral Interface cards, and fiber optic cable connects the FIM to the main control.

The 3300 Peripheral Cabinet fits into a 19" rack. All components are the same as for existing peripheral cabinet s, onl y the cabi net fram e is slight ly smalle r . This cabinet is d ark grey in color and cannot be used with peripheral stacking brackets.

Specification

Release 3.2 7

Page 88

300 ICP Hardware User Guide

The peripheral cabinet consists of the following components:

• Peripheral Interface Cards: The Peripheral Interface cards connect telephone trunks and peripheral devices (such as SUPERSET™ telephones) to the system. They are located in slots 1 through 12.

• Power Converter (AC): The AC power converter converts AC input power to the voltages required by the circuit cards and FIMs (+5 Vdc, +12 Vdc, -27 Vdc, -48 Vdc and 80 Vac ringing). It is installed in slots 13 to 15.

• Peripheral Switch Controller card (PSC): The PSC card performs all peripheral switch functions for up to 12 Peripheral Interface cards (or 24 cards with the addition of a peripheral slave cabinet. It is installed in slot 16 of the master peripheral cabinet.

• Fiber Interface Module (FIM): The FIM connects the peripheral node to the control node. It is installed in slot 17 of the master peripheral cabinet.

• Cabinet Frame: Each peripheral cabinet has 17 slots numbered from left to right. Slots 1 to 12 support Peripheral Interface cards and slots 13 to 15 hold the Power Converter. A master peripheral cabinet also holds a PSC card in slot 16, a FIM in slot 17, and a Peripheral Interconnect card in slot 16B (if your unit is expanded). A peripheral slave cabinet holds a Peripheral Interconnect card in slot 16, in addition to the Peripheral Interface cards and Power Converter. Slots 16B and 17 of the slave cabinet are not programmable.

Note: 3300 peripheral cabinets with a slightly smaller frame are available for stacking in a 19" rack.

• Power Distribution Unit (PDU) (AC): The AC PDU filters and switches the 120/240 Vac input power to the Power Converter and fan assembly.

• Power Distribution Unit (PDU) (DC): The DC PDU filters and switches the -48 Vdc input power to the Power Converter and fan assembly. Note that the server is available in AC version only.

• Fan Assembly: Two fans in the removable fan assembly cool the cabinet.

• Rear Panel: The following switches and connectors are located on the rear panel of the cabinet:

- A power on/off switch

- A fuse to protect the line lead on the input power (AC systems) or circuit breaker (DC

systems)

- A 3-conductor male receptacle to connect AC input power

- A sliding door for the Tx and Rx fiber optic cabl es

- An RS-232 Maintenance Terminal port for remote access (remote maintenance con-

nections will only work on the master cabinet of a peripheral pair)

- Nine 25-pair male, filtered, Amphenol connectors are located on the rear panel. All

lines and trunks from the main distribution frame connect to the eight horizontally positioned connectors using 25-pair cable. The single vertically positioned 25-pair D-phone connector provides power and contact closure to an optional external system fail transfer unit.

0 Release 3.2

Page 89

Specification

- A 3-conductor female plug is recessed in the rear panel behind a small cover plate

(AC systems only). The plug connects to the power connector on the AC Power converter.

- A ground connector.

Peripheral Unit Dimensions

Height 19 inches (48.0 cm) Width 18 inches (45.8 cm) Depth 16.5 inches (42.0 cm) Weight 95 lbs (43.2 kg)

Physical Dimensions

Peripheral Unit Environment

Condition Specification

Temperature -40º to 150ºF (-40º to 66ºC) Humidity 5-95% Relative Humidity, non-condensing Vibration

Mechanical Stress One 20.3 cm (8 inch ) drop, eac h edge and corn er adjac ent to the rest

Horizontal Transportation Impact Stress

Storage Environment

0.5 g, 5 to 100 Hz, any orthogonal axis

1.5 g, 100 to 500 Hz, any orthogonal axis

face – unpackaged One shock pulse applied on each face perpendicular to the direction

of motion of the transporting vehicle; the shock pulse is a half-sine acceleration 30 g peak, 20 ms duration

Operational Environment

Condition Specification

Temperature 32º to122ºF (0º to 50ºC) Humidity 5-95% Relative Humidity, non-condensing Maximum Heat Dissipation

- fully loaded (see Note) Air Flow 150 cubic feet per minute at maximum output of the fans Radiated Emissions The system meets Class A limits as outlined in FCC Rules, Part 15,

Conducted Emissions The system meets Class A limits as outlined in FCC Rules, Part 15,

Acoustic Emissions Maximum 50 dBA continuous, 75 dB intermittent (<10% duty cycle) Static Discharge Withstands 50 discharges of each polarity through a 10 k resistor

724 BTUs per hour

Subpart J

Subpart J, and complies with conducted emissions standards as outlined in BS800

connected to a 60 pF capaci tor c harg ed to 20 kV, and 20 discharges of each polarity through 500 ohm resistor connected to a 100 pF capacitor charged to 10 kV

Release 3.2 8

Page 90

300 ICP Hardware User Guide

Condition Specification

Lightning Surge 2.5 kV peak, with a maximum rise time of 2 µs and minimum decay

Induction (Normal) 50 Vrms at 60 Hz, open circuit, longitudinal mode (Tip and Ring to

Power line Faults and Line Crosses (Abnorma l)

Flammability Minimum oxygen index: 28%, as outlined in ASTM D2863-70 and

Conversion factors: 1 watt is equal to 3.412 BTUs per hour, 1 ton of refrigeration is equal to 12,000 BTUs per hour or 3.516 Kilowatts, and 3/4 Kilowatt-hour is equal to 1 ton of refrigeration.

Peripheral Unit Power

Operation 120 Vac/230.120 Vac Maximum AC power input Watts 212 W

Operational Environment (continued)

time of 10 µs applied to power lead term in als , an d 800 V peak w ith a maximum rise time of 10 ms and minimum decay time of 560 ms applied to outside plant interface terminals

ground) 600 Vrms between Tip and Ring or to ground

ASTM D28664-74; meets all safety specifications for product type (CSA, UL, and BT) for use in office environment

Power Supply

Equipment Power Requirements

AC Cabinet 120 Vac, 6 amps

240 Vac The input power is converted to ±5, ±12, -27 and -48 Vdc, and 80 Vac ringing voltage by the power converter (AC)

The AC input power connects to the PDU on the back of the Peripheral Unit by an AC power cord. An internal power cord extends AC power to the AC power converter and DC power to the backplane. A fan power connector at the rear of the PDU provides power to the fans. See Peripheral Cabinets for views of the power system components.

At the Peripheral Unit, the power entry point is one 250 V removable fuse. In 120 Vac systems, this fuse must be a 10 A slow blow fuse. In 240 Vac systems, the fuse must be a 5 A slow blow fuse.

Peripheral Unit Cards

• DID/Loop Tie trunk card The Direct Inward Dialing/Loop Tie (DID/LT) trunk card can terminate up to four DID and/or Loop Tie trunks.

• DNI line card The Digital Network Interface (DNI) line card provide 16 circuits to interface with Mitel digital telephones and consoles.

• DTMF Receiver The DTMF receiver card provides 16 circuits to support DTMF telephone keypads and end-to-end signaling equipment.

• E&M trunk card The Ear and Mouth (E&M) trunk card provides four circuits to interface E&M Trunks to the system.

2 Release 3.2

Page 91

Specification

• Fiber Interface Module The FIM, with 16 circuits, provides for the interface with the 3300 ICP Controller.

• LS/GS trunk card The Loop Start/Ground Start (LS/GS) trunk card can terminate eight analog CO trunks.

• ONS line card and ONS CLASS/CLIP line card The On-Premises (ONS) line card and the ONS Custom Local Area Signaling Service (CLASS)/Caller Line Identification Presentation (CLIP) line card provides 16 circuits for industry-standard rotary dial and DTMF telephones.

• OPS line card The Off-Premises (OPS) line card provides eight circuits for industry-standard telephones where the external loop resistance exceeds 600 ohms or where lightning surge protection is required.

Note: AC15 Trunk Cards and COV Line Cards are not supported.

LS/GS Trunk Card

The LS/GS trunk card is used to terminate eight central office (CO) trunks. The LS/GS trunk card connects to any Peripheral Interface card slot on the peripheral shelf via connectors J1 and J2.

The alternate LS/GS trunk card Layout is currently only available in Germany.

LS/GS Trunk Card Specifications

Variants Available: µ-law (NA), A-law (UK), N.Z./UK, Italy, Germany) Number of Circuits per Card: 8 LS/GS trunk circuits Power Consumption: NA, UK, NZ, Italy: 4.20 watts

Germany: 3.36 watts

External Loop Resistance: 2367 ohms (includes CO feed resistance and is measured based on

-48 V @ 18mA)

Features Provided: 2-wire/4-wire conversion

A-D/D-A conversion address Signaling: MF-R1, DTMF or dial pulse programmable loop start or ground start mode balanced network selection gain control/circuit descriptor tip ground and ring ground detection metering: 12 kHz (Italy), 16 kHz (Germany), 50 kHz (UK) or dc message registration (NA) self test capability automatic card identification

Compliance: Complies with all pertinent sections of EIA Standard

RS-464 (NA), BTR Spec 1050 (UK and NZ), and FTZ 123 R-1 standards for Germany.

Operation The LS/GS trunk card interfaces with analog central office (CO) trunks on either a -48 Vdc loop

start (LS) or -48 Vdc ground start (GS). The preferred interface is GS.

Release 3.2 8

Page 92

300 ICP Hardware User Guide

The German variant has LS function only. The trunk circuits on the LS/GS trunk card are configured during the initial system programming

process. Each trunk circuit can be programmed to operate in an LS or GS mode. LS or GS options can be changed at any time via the System Administration Tool.

When GS mode is selected, incoming trunk calls are initiated by a ground on the Tip lead, or by a ringing source applied to the trunk by the CO. Outgoing calls are initiated by seizing an idle trunk (via the DATA IN link of the trunk circuit) and by placing a ground on the Ring lead.

When LS mode is selected, incoming trunk calls are initiated by a ringing source applied to the trunk by the CO. Outgoing calls are initiated by first seizing an idle trunk (via the DATA IN link on an LS/GS trunk card circuit) and by placing a low resistance loop across the Tip and Ring leads.

Dictation equipment used on a trunk can indicate a busy or idle status by interconnecting a third wire lead to either the T(MR) or R(MR) termination at the 3300 ICP system. The actual configuration that should be used is dependent upon the type of centralized dictation equipment used and its busy status (i.e., whether a busy condition is indicated by a voltage or ground condition on the third wire; see Dictation Access in Troubleshooting, Hardware, Peripheral Unit, LS/GS Trunk Card).

In addition, T(MR) and R(MR) leads can be connected to the CO for message registration purposes. The system can record message registration pulses either by polarity reversal over the Tip and Ring leads (when the called party answers) or by loop signaling from the CO over the second pair of leads. Various types of terminations can be used for message registration pulses transmitted from the CO. In each case, M and MM leads terminate respectively on the T(MR) and R(MR) leads. A message registration signal is given when the MR contact at the CO is closed.

E & M Trunk Card

The E&M Trunk card provides a means of interfacing four external trunk circuits to the system. E&M trunk cards connect to any Peripheral Interface card slot on the peripheral shelf via connectors J1 and J2.

E&M Trunk Card Specifications

Variants Available: A-law (UK), µ-law (NA) Number of Circuits per Card: 4 E&M trunk circuits Power Cons umption: Type I, mechanical CO: 21.45 watts

Type I, electronic CO: 8.01 watts Type V: 4.83 watt

External Loop Resistance : Type I: 150 ohms

Type V: 4000 ohms

4 Release 3.2

Page 93

Specification

Features Provided: 2-wire/4-wire conver si on

A-D/D-A conversion E&M signaling leads 2 dB software-switchable VNL pads software-selectable standard carrier levels switch-selectable 2-wire or 4-wire operation protection/isolation against foreign potentials switch-selectable E&M types self-test capability automatic card identification

Compliance: Complies with all pertinent sections EIA Standard RS-464.

E&M Trunk Card Settings The E&M trunk card accommodates E&M interface circuits Types I through V . The configuration

of the four trunk circuits on the E&M trunk card to accommodate these five interface types is accomplished by using DIP switches SN-1 and SN-2. These DIP switches must be set on-site as follows:

SN-1 and SN-2 Switch Settings

Types of Interface Cards Switch Positions

Signal/carrier set

types

TYPE I NONE A B

TYPE II TYPE II B A

TYPE IV TYPE IV B A

TYPE V TYPE I B B TYPE V TYPE III B B TYPE V TYPE V B B

Note: Positions are SN-1 and SN-2 where N is the particular trunk circuit number on the card (1 through 4).

Co-located trunk

types

SN-1 SN-2

Operation

In addition to the E&M trunk types that can be configured by using DIP switches, it is also possible to configure various software options via system programming. The software options can be changed at any time using the System Administration Tool.

Fiber Interface Module (FIM)

Guidelines for Handling Fiber Optic Cable

• Never touch the tip of a fiber connector. Cleanliness of the connector ferrule (tip) is important for error free transmission.

• Always place the dust caps onto the connectors immediately after disconnecting.

• You can clean the ferrule tips on the connectors with ethyl-alcohol.

Release 3.2 8

Page 94

300 ICP Hardware User Guide

• Fiber optic cables are often more easily installed and pulled than copper because of their light weight and flexibility. However , take care not to exceed the minimum bend radius or maximum tensile strength.

• Procedures for the repairing, splicing, or assembling fiber optic cables are available from fiber component manufacturers (many offer training courses).

WARNING: Fiber optic sources emit infrared light that is invisible to the human eye. Never look directly into a source or into the end of a fiber energized by a source because it can damage the retina. When working with raw fiber optic cable, be careful of the fiber ends or slivers that can puncture the skin or cause irritation.

Specifications

At each end of a fiber optic cable is a Fiber Interface Module (FIM). At the transmitting end, the FIM converts electrical signals into pulses of light to be transmitted over the cable. At the receiving end, the FIM converts the pulses of light back into electrical signals usable by the node.

The FIM connects the 3300 Controller to a peripheral unit or DSU. These FIMs cannot be installed in the Applications Gateway. Each FIM variant may be identified by its optical wavelength and fiber type (indicated on the FIM faceplate). The same FIM variant must be used at each end of a fiber optic cable. However, a node may be equipped with different FIM variants to suit the length of each cable run.

Fiber Interface Module Specifications (9400-300-301-NA)

Approximate maximum fiber cable run length (See Note 1) 1km (0.62 miles) Power consumption (Watts) 2.5 Number of fiber links per FIM 1 Tx, 1 Rx Fiber connector type ST (See Note 2) Electrical interface

(See Note 3) Optical wavelength (nm) 820 Optical budget (See Note 4) 6 db Date rate (Mbits/second) 16.384 Bit rate after encoding (Mbaud) 20.48 Fiber optic cable type 62.5/125 um

Notes:

1. The run length is the one-way length of fiber optic cable between nodes.

2. ST is a registered trademark of AT&T.

3. Some channels of the electrical interface are not available.

4. The optical budget is the allowable loss through fiber optic cable, splices, and connectors. The

optical budget applies to the run length.

8 serial ST links

Multimode

6 Release 3.2

Page 95

Specification

Operation

The FIM has three functional sections: a transmitter, a receiver, and a control section.

The transmitter section accepts data from the node in which it is installed. The data is converted to byte-interleaved format, and a checksum is calculated. The checksum byte is combined with the data and the frame synchronization information. The frame is encoded as serial data and transmitted on the fiber.

The receiver section converts the incoming data to parallel format, extracts the frame synchronization information, and decodes the data. Control and status information are extracted and further decoded. The checksum is verified and an error counter updated. The status information and data are combined, frame-aligned, and re-formatted for output.

The control section generates control signals and the transmit clocks. This section also regenerates the telephony clocks for the peripheral nodes, and provides status information for the Main Controller.

Two LEDs indicate the detection of local and remote clocks.

DID/Loop Tie Trunk Card

The DID/LT T runk card terminates up to four trunks. These trunks can be Direct Inward Dialing (DID) trunks, Loop Tie (LT) trunks, or any combination of DID and LT Trunks. Direct Inward Dialing provides direct access to system subscriber lines from the public telephone network. Loop Tie provides a means of connecting two systems together over a common trunk.

The assignment of trunk types is programmed through the System Administration Tool. Programmable parameters include Dial-In Trunk versus Non-Dial-In Trunk and Loop Pulsing versus Battery Ground Pulsing.

DID/Loop Tie Trunk Card Specif ic ati ons

Variants Available: A-law (UK), µ-law (NA) Number of Circuits per Card: 4 DID/Loop Tie trunk circuit s Power Cons umption: Incoming mode (DID/DDI): 15.01 watts

Outgoing mode (Loop Tie): 5.28 watts

Mixed/Both ways: 10.14 watts External Circuit Resistanc e: 2450 ohms External Loop Length: 7986 meters (25955 ft.), 26 AWG (27 IWG)

19995 meters (64984 ft.), 22 AWG (23 IWG) Minimum Conductor Leakag e: 30000 ohms

Release 3.2 8

Page 96

300 ICP Hardware User Guide

Features Provided: 2-wire/4-wire conversion

Compliance: Complies with all pertinent sections of EIA Standard RS-464.

Operation

The DID/LT trunk card is software-controlled by the Main Controller. The DID/L T trunk card can maintain voice and data communications through four trunks supported by the DID/LT trunk card in both incoming and outgoing modes. For example, the DID/LT trunk card interfaces incoming DID trunks from a CO, and incoming and outgoing trunks between co-related systems. Any combination of these applications can be handled by the DID/LT trunk card.

A-D/D-A conversion address signaling: MF-R1, DTMF or dial pulse incoming/outgoin g/bo th way sel ec t io n independent gain control for incoming and outgoing mode software-selectable balance networks tip ground and ring ground sensing protection/isolation against foreign potentials forward/reverse loop voltage sensing incoming DC loop supervision and debounced dial pulse collection incoming forward or reverse battery feed battery/ground pulsing (optional) backwards busying self-test capability automatic card identification

DNI Line Card

The Digital Network Interface (DNI) Line Card provides 16 voice and data lines. The DNI line card provides an interface for MITEL digital network devices including SUPERSET telephones, and attendant consoles.

The DNI line card features devices that are compatible with MITEL SUPERSWITCH™ DIGITAL NETWORK (MSDN) data transmission protocols. MSDN technology allows simultaneous 2-way transmission of digitized voice and data over a twisted copper pair. The DNI line card supports voice/data transmission at the rate of 128 kb/s (64 kb/s on each of two voice channels) and 16 kb/s on one signaling channel over a loop length of up to 1000 meters (using 24 - 26 AWG wire (25 - 27 IWG)).

DNI Line Card Specifications

Number of Circuits per Card: 16 DNI circuits (up to 32 channels) Power Cons umption: 17.24 watts External Loop Length: Up to 1000 meters; 24 or 26 AWG (25 or 27 IWG) twisted pair,

including up to 50 meters (162.5 ft) 22 AWG (23 IWG) quad wire

and up to 3 m modular line cord without bridge taps. External Loop Resistance : 300 ohms Data Error Rate: Better than 1 in 10,000,000 bits, in the presence of an interfering

signal (ringing).

8 Release 3.2

Page 97

Specification

Features Provided: Interface for MIT EL digital teleph one sets, and attendant consoles

2-wire / 4-wire conversion full DX chip on-board high-level data link controller (HDLC) on-board 32 K of on-board RAM memory 16 K of on-board PROM self-test capability, including power-up diagnostics automatic card identification

Compliance to Standards: Meets all ONS-type requirements for North America and the

United Kingdom meets Harmful Voltages requirement of POR1065.

Operation

The DNI line card provides full duplex digital transmission of both voice and data. The DNI line card is a "smart" card capable of downloading information to and from peripheral devices.

ONS Line Card

The ONS line card connects up to 16 standard telephone sets with line loop resistances usually not exceeding 400 ohms. As such, the ONS line card is used to connect internal telephone extensions close to the system. The ONS line card installs in any Peripheral Interface card slot, and is hot-swappable.

ONS Line Card S pecifications (all var iants)

Note: The following variants apply to the ONS and ONS CLASS/CLIP line cards.

Number of Circuits per Card: 16 ONS circuits Loop Detector Threshold: 15 mA (+1 mA) (ONS line card)

13 mA (+1 mA) (ONS CLASS/CLIP line card) Trip Battery Ringing Interval: -48 Vdc nominal Bridged Ringers: 5 (C4 or equivalent) Features Provided: 2-wire/4-wire conversion

A-D/D-A conversion

DC loop supervision and dial pulse collection

ringing and ring trip detection up to 5 telephones per circuit

ground button detection

self-test capability

automatic card identification

constant current feed

Release 3.2 8

Page 98

300 ICP Hardware User Guide

ONS Line Card Variant Specifications

Note: The ONS CLASS/CLIP line card is available in NA and the UK only.

Feature NA Germany China UK Int’l*

MC320 Card Variants

PCM Coding µ-law A-law A-law A-law A-law External Loop

Resistance (see Note 1)

External Wire Resistance (see Note 2)

Power Consumption

Message Waiting (see Note 4)

Calibrated Flash

Nominal Ringing Voltage

Nominal Trip Battery

Silent Interval External Loop

Length: 22 AWG (23 IWG) 26 AWG (27

IWG * International = Caribbean, Cuba, Europe, Middle East and Africa

Notes:

1. Stations whose line loop resistances range between 400 and 1600 ohms must terminate on an

OPS line card.

2. External wire resistance measurements are based on the assumption that a 200 ohm set was used.

3. The German variant al so pro vides impe dance match ing, fi xed an d varia ble ga ins, as wel l as Tip and Ring protection, with selectable fuse or EMI choke option.

4. The message waiting circ uit for the ONS CLASS/CLI P line card has a v oltag e below 120v on t he ring lead.

BD, BE for ONS line card; EA for ONS CLASS/CLIP line card

600 ohms 850 ohms

400 ohms 650 ohms 400 ohms 400 ohms 400 ohms

BD: 9.09 W BE: 9.82 W

Yes Yes Yes Yes Yes

No Yes Yes Yes Yes

80 Vrms @ 20 Hz65 Vrms @ 25 Hz80 Vrms @ 25 Hz80 Vrms @ 25 Hz80 Vrms @ 25

-27 Vdc -30 Vdc -27 Vdc -27 Vdc -27 Vdc

3800 m (12350 ft.) 1500 m (4875 ft.)

CH CG CD for ONS

line card; EB for ONS CLASS/CLIP line card

600 ohms 600 ohms 600 ohms

@ 23mA

9.64 W 9.82 W 9.82 W 9.82 W

3700 m

(12025 ft.)

3700 m (12025 ft.)

Operation

Incoming analog calls are converted to digital (PCM) signals by one of 16 line circuit modules on the ONS line card. Calls are switched by the Main Controller and the two parties are

0 Release 3.2

Page 99

Specification

connected. Outgoing calls are converted from PCM digital signals to analog signals by one of the 16 line circuit modules on the ONS line card. Calls are switched by the Main Controller and the two parties connected.

All signals are passed through the 2-wire to 4-wire hybrid circuit on the line circuit module. The line busy status LED remains lit while the call is in progress. When calls are terminated, receipt of an on-hook condition turns off the line status LED. The call is disconnected from the circuit switch and the line circuit reverts to an idle condition.

The ONS line card provides for “Ground button” signaling. A ground button, on a telephone extension so equipped, provides a means of connecting ground to the ring lead. In addition to ground button support, the ONS line card features a calibrated flash function. Unlike telephone installations using ground button signaling, telephone extensions using calibrated flash signaling do not require a third wire connected to ground. Calibrated flash is also the only method recognized internationally for recall simulation. The minimum calibrated flash duration that can be detected by the ONS line card is 40 milliseconds.

ONS CLASS/CLIP Line Card

The ONS CLASS/CLIP line card supports the same functionality as the ONS line card, but also provides CLASS/CLIP functionality when enabled by the software. The ONS CLASS line card is available in North America, and the ONS CLIP line card is available in the UK. The ONS CLASS/CLIP line card installs in any Peripheral Interface card slot, and is hot-swappable.

Note: Sending CLASS/CLIP information to an ONS line card will not harm the card.

ONS CLASS Line Card Specifications (North America)

The ONS CLASS line card (NA) supports ONS CLASS sets (NA) that meet the following specifications:

- ANSI/TIA/EIA-716 Standard "T elecommunications T elephone T erminal Equipment - Type 1 Caller Identity Equipment Performance Requirements"

- ANSI/TIA/EIA-777 Standard "T elecommunications T elephone T erminal Equipment - Type 2 Caller Identity Equipment Performance Requirements".

For more information on ONS CLASS/CLIP line card specifications, see ONS Line Card.

OPS Line Card

The OPS line card connects to any Peripheral Interface card slot. The OPS line card is a digital card intended to be used to interface up to eight outside telephone extensions with the system. The card is meant to interface telephone extensions whose line loop resistance exceeds 400 ohms. As such, the OPS line card is used to connect external telephone systems whose loop resistance is anywhere from 400 to 1600 ohms (external resistance from 600 to 1800 ohms).

Release 3.2 9

Page 100

300 ICP Hardware User Guide

OPS Line Card Specifications

Variants Available: A-law (UK), µ-law (NA) Number of Circuits per Card: 8 OPS Circuits Power Cons umption: UK: 8.53 Watts

External Loop Resistance : 1800 ohms maximum External Wire Resistance: 1600 ohms maximum External Loop Length: 5853 meters (19022 ft.), 26 AWG (27 IWG)

Minimum Conductor Leakage: 1500 ohms Loop Detector Threshold: 12 mA (+1 mA) Trip Battery Silent Interval: -50 Vdc nominal Trip Battery Ringing Interval: -50 Vdc nominal Bridged Ringers: 5 (C4 or equivalent) Ringing Voltage and Frequency: 82 to 90 Vrms, 17 to 25 Hz Features Provided: 2-wire/4-wire conversion

Compliance: Complies with all pertinent sections of EIA Standard RS-464.

NA: 8.67 Watts

15240 meters (49530 ft.), 22 AWG (23 IWG)

A-D/D-A Conversion DC Loop Supervision and Dial Pulse Collection Ground Button Detection and Ring Lead Current Limiting Self-Test Capability Automatic Card Identification

OPS Line Card Message Waiting Switches

Eight message waiting switches (S1 through S8) are mounted on the OPS card. These switches are used to select the type of message-waiting signaling employed on each of the eight OPS line card circuits. Each circuit provides two message-waiting switch types.

Setting Description

A Circuits are connected to OPS lines. Loop extended over the Message-Waiting Answer

(MWA)/ Message-Waiting Busy (MWB) pair to the called extension.

B Circuits are connected to ONS lines. Cons ists of a -140 Vdc source de livered at a v ariable

rate to the Ring lead of the called extension. Rate is custom programmed to be continuously on through 80 Hz .

Message-Waiting Switch Types

Operation

Calls inco ming to th e OPS line c ard are converted from ana log to dig ital sig nals by a line circ uit module. The call is then switched and the two parties connected. All signals are passed through the 2-wire to 4-wire hybrid circuit on the line circuit module. The line busy status LED is turned on (lit) while the call is in progress.

Calls outgoing on the OPS line card are converted from digital signals to analog signals by a line circuit module. The main control processor oversees the connection between the two

2 Release 3.2