Communications Systems Request for Proposal Specificationsx

pogonotomyeyrarΔίκτυα και Επικοινωνίες

26 Οκτ 2013 (πριν από 4 χρόνια και 12 μέρες)

587 εμφανίσεις




<Customer logo here>

<Mitel entity here>

Page
1

of
112

Customer Proposal



Prepared by:

[SALESPERSON]

Prepared for:

[ENDCUSTFULL]

[ENDCUSTADD1]

[ENDCUSTADD2]

[ENDCUSTTOWN] [ENDCUSTSTATE] [ENDCUSTZIP]

[ENDCUSTCOUNTRY]

Date

[DATE]

Quote
Reference:

[QUOTEID]







<Customer logo here>

<Mitel entity here>

Page
2

of
112

Mitel Communications Director (MCD) Platform

................................
.............

6

Mitel Communications Director (MCD) Overview

................................
................................
........

6

Architecture

................................
................................
................................
................................
..

8

Migration, Preservation of Telecom Investments

................................
................................
.........

9

Hardware Platform

................................
................................
................................
.......................

9

3300 CX II/CXi II
................................
................................
................................
.........................

10

3300 AX

................................
................................
................................
................................
......

12

3300 MXe

................................
................................
................................
................................
...

13

ASU II

16

Four
-
plus
-
12
-
Port Combo Analog Card

................................
................................
.....................

16

24
-
Port ONS Analog Card

................................
................................
................................
..........

16

Scalability

................................
................................
................................
................................
...

16

Dynamic Extension
................................
................................
................................
.....................

17

Auto Attendant

................................
................................
................................
............................

19

Embedded Voicemail

................................
................................
................................
.................

20

Selected Features

................................
................................
................................
......................

21

ACD (Autom
atic Call Distribution)

................................
................................
.........................

21

Hot Desking

................................
................................
................................
...........................

21

Call Reporting and Cost Management

................................
................................
..................

21

Location Based Accounting

................................
................................
................................
...

22

Account Codes

................................
................................
................................
......................

22

Night Se
rvice Indication

................................
................................
................................
.........

22

Logged in Hotdesk Busy Lamp Field Indication

................................
................................
....

22

Multi
-
colored LEDs

................................
................................
................................
................

22

Record
-
a
-
Call

................................
................................
................................
........................

22

Maintenance Logs

................................
................................
................................
.................

22

Traffic Measurement
................................
................................
................................
..............

23

Security

................................
................................
................................
................................
......

23

System Reliability and Resiliency

................................
................................
..............................

25

LAN Requirements

................................
................................
................................
.....................

25

Station Connectivity

................................
................................
................................
...................

27

Network Connectivity

................................
................................
................................
.................

27

Supporte
d Analog Trunks

................................
................................
................................
......

27






<Customer logo here>

<Mitel entity here>

Page
3

of
112

Supported Digital Trunks

................................
................................
................................
.......

27

ISDN Connectivity

................................
................................
................................
.................

28

SIP Support

................................
................................
................................
................................

28

SIP Trunking Support

................................
................................
................................
............

28

SIP Trun
king Interoperability

................................
................................
................................
.

29

SIP End Points Support

................................
................................
................................
.........

29

Recovery from Power Outage

................................
................................
................................
....

29

Electrical and Physical Specifications

................................
................................
........................

29

System Input Power Requirements for Controllers

................................
...............................

29

Grounding Requirements

................................
................................
................................
......

30

Environmental Requirements

................................
................................
................................
.....

31

Operational Environment Requirements

................................
................................
...............

31

Operational Environment Requirements

................................
................................
...............

31

Virtual Mitel Communications Director

................................
................................
.......................

32

Virtual MCD Benefits

................................
................................
................................
.............

33

Mitel Border Gateway

................................
................................
................................
.................

34

Mitel Multi
-
Instance Communications Director

................................
................................
...........

35

MICD Benefits

................................
................................
................................
.......................

35

Phones and Communication Appliances

................................
.......................

36

Phones and Communication Appliances Overview

................................
................................
...

36

IP Phone SIP Compatibility

................................
................................
................................
........

37

5304 IP Desktop Telephone

................................
................................
................................
.......

37

5312 IP Desktop Telephone

................................
................................
................................
.......

39

53
20 IP Desktop Telephone

................................
................................
................................
.......

40

5324 IP Desktop Telephone

................................
................................
................................
.......

42

5330 IP Desktop Telephone

................................
................................
................................
.......

44

5340 IP Desktop Telephone

................................
................................
................................
.......

45

5360 IP Desktop Telephone

................................
................................
................................
.......

47

UC Advanced Softphone

................................
................................
................................
............

49

5540 I
P Console

................................
................................
................................
.........................

50

5550 IP Console

................................
................................
................................
.........................

53

5560 IP Turret

................................
................................
................................
............................

56

NetLink Wireless Telephones

................................
................................
................................
....

57






<Customer logo here>

<Mitel entity here>

Page
4

of
112

IP DECT

................................
................................
................................
................................
.....

59

IP
-
DECT Components and Accessories

................................
................................
...............

60

IP Phone Accessories

................................
................................
......................

66

5310 IP Conference Unit

................................
................................
................................
............

66

Mitel IP Programmable Key Modules 12 and 48

................................
................................
........

67

Line Interface Module

................................
................................
................................
.................

68

Gigabit Ethernet Stand

................................
................................
................................
...............

69

Plantronics Headsets for Mitel Phones

................................
................................
......................

69

Cordless Handset and Cordless Headset

................................
................................
..................

70

5610 DECT Handset and IP DECT Stand

................................
................................
.................

71

5610 DECT Handset

................................
................................
................................
.............

71

IP DECT Stand

................................
................................
................................
......................

73

HTML ToolKit

................................
................................
................................
.............................

73

Applications and Solutions

................................
................................
.............

77

Mitel Applications Suite

................................
................................
................................
..............

77

MAS Applications

................................
................................
................................
..................

77

Virtual Mitel Applications Suite

................................
................................
................................
...

82

Mitel NuPoint Unified Messaging

................................
................................
...............................

82

NuPoint Un
ified Messaging Standard Edition

................................
................................
.......

83

NuPoint Unified Messaging Single Server Platform

................................
..............................

83

NuPoint Unified Messaging Model 640

................................
................................
.................

84

Unified Communicator Mobile

................................
................................
................................
....

84

UC Mobile BlackBerry Support

................................
................................
................................
..

85

UC Mobile Android Support

................................
................................
................................
.......

86

Audio and Web Conferencing

................................
................................
................................
....

87

Unified Communicator Advanced

................................
................................
...............................

88

Virtual Unified Communicator Advanced

................................
................................
.................

101

Unified Communicator Express

................................
................................
................................

101

Mitel Telecollaboration Solution

................................
................................
...............................

102

Mitel Contact Cent
er Solutions

................................
................................
................................
.

103

Contact Center Business Edition

................................
................................
.........................

105

Contact Center Enterprise Edition

................................
................................
.......................

105

Call Accounting

................................
................................
................................
....................

106






<Customer logo here>

<Mitel entity here>

Page
5

of
112

Mitel Systems Management

................................
................................
..........

107

Mitel Systems Management

................................
................................
................................
.....

107

System Data Synchronization

................................
................................
................................
..

107

Embedded Systems Management

................................
................................
...........................

108

Enterprise Management

................................
................................
................................
...........

111






<Customer logo here>

<Mitel entity here>

Page
6

of
112


Mitel Communications Director (MCD) Platform

Mitel Communications Director (MCD) Overview

Mitel Comm
unications Director (MCD) can be deployed in just about any environment, working with
(rather than replacing) existing processes and systems to enhance them with the latest IP solutions and
features. This attribute protects
[EndCustFull]
’s legacy investmen
t, and also prepares existing systems
for future growth.



Mitel Communications Director (MCD) software allows end users to operate their communications system
with flexibility, ease, and reliability. This powerful software runs on a choice of platforms,
such as the
proprietary Mitel 3300 ICP or industry standard Oracle, HP, and IBM® servers, widening the scope of
businesses and enterprises that will benefit from Mitel's call control software. It can be deployed in a
centralized, distributed, or hosted co
nfiguration to meet specific business needs, and provides the
reliability expected by the most stringent business requirements. Mitel Communications Director
integrates with Mitel’s desktop portfolio and suite of unified communications applications to driv
e
productivity, enhance customer service and reduce costs.


Virtual Mitel Communications Director offers the same MCD functions and capabilities, while being
treated like any other virtualized application in the data center. Mitel and VMware have partner
ed to
allow voice and business applications to run together in a virtualized environment.


Mitel Multi
-
Instance Communications Director (MICD)
l
everages virtualization techniques to allow multiple
instances of Mite
l Communications Director (MCD)

to run on an industry
-
standard server.

MiCD provides

a dense, scalable, and energy efficient communication services platform, while maintaining the flexibility
of completely distinct PBX instances.


Whether a company has 30 users or 65,000, MCD brings powerful call handling, a profusion of features,
simple management and flexible deployment options.



Among MCD’s embedded features are leading
-
edge mobility capabilities and standard unified messaging.

Mitel Dynamic Extension establishes a single identity for users communicating internally or externally.
Dynamic Extension works with any device (desk phone, cellular, remote office, home phone) and extends
the corporate system to any location on any netwo
rk. This improves the accessibility of the user, and also
reduces costs and ensures first
-
call resolution.



MCD also includes inherent auto attendant, automatic call distribution, Wi
-
Fi, and

an IP DECT wireless
gateway. These combined with over 500 telep
hony features such as hot desking and audio conferencing
enrich the user experience and invigorate existing processes. In distributed environments, MCD works
over IP or traditional telephony networks to provide a virtual single system. MCD also provides su
pport for
networking standards such as SIP, QSIG and DPNSS, which facilitate interconnection with third
-
party
PBXs and applications.



Administrators sign on only once to manage all the capabilities of up to 19 other MCD platforms. Through
the same Web
-
ba
sed interface, they can also reach through to various applications to view and change
administration forms on any MCD platform in the system.






<Customer logo here>

<Mitel entity here>

Page
7

of
112



MCD
has no dedicated server hardware, but instead runs
on either Mitel proprietary 3300 Controllers or
industry
-
standard Sun, HP or IBM servers. It operates across virtually any LAN or WAN infrastructure,
regardless of manufacturer. It can also be implemented in a distributed model where call control is
managed at local sites, or in a hosted model where call contro
l servers are collocated with gateways to
deliver resilience and business continuity.



MCD can be configured to provide different services running on separate hardware platforms within a
single solution. For example, it can be configured to run as a call
controller on one hardware platform, a
media gateway on another, and an applications and services gateway on a third controller, all combining
to form a single system.



MCD consistently delivers efficient, seamless call handling. It provides native call
setup, tear down, and
signaling between Ethernet IP
-
connected telephones. For traditional telephony, such as POTS and PSTN
trunks, call handling is also conducted natively by MCD through a conventional TDM circuit
-
switched
subsystem. Using two different sw
itching techniques simultaneously means





all traffic is switched with minimum conversion between packet and traditional telephony to
provide optimum voice quality in all call scenarios



embedded gateway functionality is only required between the IP and non
-
IP networks, optimizing
the use of system resources



migration from traditional PBX to IP telephony is seamless and efficient



MCD’s high level of flexibility revives legacy systems and saves
[EndCustFull]

money and time. MCD is
designed to IP
-
enable the
legacy PBX, which protects existing investments while delivering all the
advantages of a unified communications infrastructure. In addition, features available on Mitel IP phones
can be ported to legacy phones (desktop, wireless, cellular, remote), elimina
ting the need to buy new
phones.



MCD’s flexible design immediately enhances the user experience, and extends high
-
level benefits over
the long term.



The following diagram illustrates a sample MCD converged network for medium to large businesses;
howev
er, it is also easily scalable for smaller organizations.







<Customer logo here>

<Mitel entity here>

Page
8

of
112




Architecture

Using Mitel 3300 Controllers and gateways, MCD can be configured and integrated into any corporate
LAN or WAN infrastructure that supports Quality of Service, regardless of
manufacturer. The IP network
connects IP telephony devices, and simultaneously provides a Time Division Multiplexer (TDM)
subsystem (for digital and analog phones and trunks). This capability means that MCD




supports a complete IP implementation, a TDM imp
lementation, or a combination of IP and TDM



can provide optimum voice quality in all call scenarios due to minimization of conversions
between IP and TDM



offers seamless and efficient migration from traditional PBX to IP telephony



provides native support f
or SIP interoperability with multiple service providers and for a variety of
traditional PSTN interfaces and networking protocols



delivers consistent features and functionality between the TDM and IP domains


The MCD software architecture supports




multipl
e services and capabilities, e.g., as a media gateway, a user gateway, or an applications
and services gateway on a variety of purpose
-
built controllers and gateways and industry
-
standard platforms



scaling from individual sites of 10 users or less up to th
ousands of users on a single controller/site
and hundreds of controllers in a large network



a variety of hardware platforms on a single common stream of software including

o

3300 CX, CXi, AX and MXe controllers and survivable media gateways






<Customer logo here>

<Mitel entity here>

Page
9

of
112

o

Sun Microsystems

Sun Fire servers



resiliency and redundancy in MCD, ensuring there is no single point of failure in the voice
network. For example, should connectivity to a primary 3300 MXe Controller become temporarily
lost, MCD system features and capabilities are prese
rved in a second 3300 MXe Controller. IP
phones and applications are redirected to the secondary controller until connectivity returns to the
primary controller.

Migration, Preservation of Telecom Investments

Completely replacing a legacy system with a new

system, presents several disruptions to cost, business
and efficiency. Instead, our solution can work from any existing architecture, and enables a smooth
transition to IP communications without sacrificing the features and investment of existing equipmen
t.
[EndCustFull]

can customize the migration to maintain its legacy systems while enabling staff to
immediately use IP features and functions, such as messaging, conferencing, and system management.
Ultimately, we intend to generate a maximum return on
[En
dCustFull]
’s existing investment while helping
you recognize substantial savings.



Our migration process works because our solutions adhere to open standards. We have successfully
integrated our IP systems into every leading LAN/WAN communications equipm
ent vendor in the
industry. This ensures that every aspect of our solution is compatible with
[EndCustFull]
’s existing data
infrastructures and PBXs, and enables existing telephony operations to continue with minimal disruption.


Migration to MCD offers minimal risk and provides the opportunity for potential cost savings, productivity
enhancements and business
-
process improvements. As the ideal vehicle for migration to IP telephony,
MCD allows incremental station
-
by
-
station deploym
ent, and provides potential system
-
wide benefits for
[EndCustFull]

and its users. MCD delivers the best attributes of a circuit
-
switched PBX including robust
software, features and digital telephones. It also offers the benefits of a client/server IP
-
PBX i
ncluding a
call control complex server and direct LAN signaling to and from IP telephones.


Hardware Platform

[EndCustFull]

may choose from four Mitel 3300

Controllers (CX, CXi, MXe and AX) or an appropriate
Mitel
-
supported server platform from Sun Microsystems, HP, or IBM. The CX or CXi Controller supports
up to 150 devices and is ideal for small business or branch office solutions. The AX controller suppor
ts up
to 350 devices, which suits solutions that require larger analog densities. User devices can be any
combination of analog, digital, or IP.


Mitel MCD Hardware Platforms


CONTROLLER

ANALOG
EXTENSIONS

IP DEVICES

SIP USERS

TOTAL
DEVICES

CX


150

150

150

150

CXi


150

150

150

150

AX


575

100

150

300

MXe Base

350

300

300

350






<Customer logo here>

<Mitel entity here>

Page
10

of
112


MXe
Expanded


1,500

1,400

1,000

1,500



3300 CX II/CXi II



The CX II/CXi II ships with an embedded Analog Main Board

that supports six analog trunks and four
analog extension ports. The CX II/CXi II includes the required digital signal processing (DSP) in the base
configuration. You only need to add cards and DSP resources for additional functionality, not for
performan
ce scaling.






<Customer logo here>

<Mitel entity here>

Page
11

of
112


The CX II and CXi II Controllers support the following:




Up to 150 IP devices, or up to 150 IP/ONS devices



The Analog Main Board

(AMB) provides six LS trunk ports with Custom Local Area
Signaling Services (CLASS) support (CLASS is available in North America and Latin
American only). We support ETSI CLASS for other applicable regions), four Object Name
Service (ONS) ports, a single

Music
-
on
-
Hold port (one source supported), a single paging
port (one paging zone), and two System Fail Transfer circuits.) The AMB comes as
standard on every CX II and CX II. All standard telephone sets with a loop resistance of
less than 400 ohms interfa
ce to the system through ONS ports. The Tip and Ring pair
from a modem may be connected to an ONS port based on engineering guidelines.)



The Analog Open Board (AOB) provides six loop
-
start (LS) trunks ports with CLASS
support, four ONS ports, one System Fa
il Transfer circuits and one paging circuit. The
AOB is an optional port.



One 10/100 BaseT WAN port (RJ
-
45 connector)



One 10/100/1000 BaseT LAN port (RJ
-
45 connector)



16 10/100 Base T LAN ports connected to an internal Ethernet Layer 2 switch (CXi II
Contr
oller only). Embedded 16
-
port L2 POE switch on the CXi II.



SATA solid state drive or SATA hard drive for software storage



A unique bracket assembly making for easier installation



Embedded voicemail services



Minimum software version: MCD R4.0 (for CX(i) IIs
)



CX(i) II ships with 512 Mbyte of RAM



Universal power (110
-
220V) (power cord is ordered separately, depending on the region)



19” rackmount



19” high x 18” wide x 19” depth



certification, including Canadian Standards Association (CSA), Industry Canada (IC)
,
Federal Communications Commission (FCC), and Commission European (CE)



The Basic Rate Interface (BRI) is only applicable for European standards (not used in
North America). BRI support comes in the form of an optional embedded BRI MMC card.


Optionally yo
u can also install the following:




One DSP II module for FAX Relay (T.38) and compression. The dual DSP is only for
telephony services such as DTMF signaling detection. Compression is by way of the DSP
II only.



One or two T1/E1 Combo modules for digital tr
unking



One or two Quad BRI Framer modules for BRI trunks



A Quad Copper Interface Module (CIM) supporting up to three Analog Service Unit IIs
(ASU IIs)


Note

-

The CX II and CXi II controllers do not support Network Service Units (NSUs) or peripheral
cabine
ts.


Note

-

The power supply is not field replaceable.






<Customer logo here>

<Mitel entity here>

Page
12

of
112



3300 AX



The 3300 AX Controller delivers a high
-
density analog solution that can be deployed anywhere across an
IP infrastructure. It supports a maximum of 350 devices (288 on
-
premises station (ONS) and up to 100
IP).
<<Proposal coordinator: The AX can be configure
d to accommodate low
-
traffic environments (e.g.,
hospitality). If this applies to your customer, substitute with this sentence: It will support a maximum of
576 devices (288 on
-
premises station (ONS) and up to 300 IP).>>

It offers the same software feature
s
and functionality that other 3300 Controllers do, such as networking and station level abilities. This means
that the 3300 AX Controller is a full
-
featured alternative to the MXe and CX Controllers because it works
in any locations that require large ana
log support, while still supporting IP devices.



The AX controller ships with a single Motorola PowerQUICC II 8280 450 MHz processor and 512 MB of
RAM. The AX media kit is shipped separately and comes with a 2 GB flash hard drive and 4 GB for voice
mail.
Embedded voice mail is supported by an optional 4 GB flash drive.








<Customer logo here>

<Mitel entity here>

Page
13

of
112

As proposed, we would position the AX Controller in
[Name a branch or remote location]

to deliver analog
services while also having access


through IP networking


into the overall solut
ion. By incorporating
more analog devices into a single controller closer to the end user we would increase the resiliency of
these traditional solutions by reducing the effects of any single point of failure.



The AX Controller supports IP and SIP device
s, and the same two analog cards as the ASU II:





24 protected port ONS card



12
-
port ONS and four
-
port LS trunk



The AX Controller can accommodate 12 of these cards in any configuration.



One externally accessible module position will be provided for di
gital trunk connectivity through the
existing embedded E1/T1 trunk modules (single and dual). For specific trunking requirements, the AX
controller supports Fiber Interface Module (FIM) connectivity to an R2 Network Synchronization Unit
(NSU).

3300 MXe



The Mitel 3300 MXe Controller accommodates from 40 to 1,500 users. Its unique design enables a
smaller system to be expanded to increase capacity rather than requiring a platform upgrade.


The MXe Controller ships with: one RTC/E2T computer card equipped
with a 533 MHz MPC8360 RISC
processor and 512 MB of DDR2 memory, a 160 GB Serial ATA (SATA), and an optional SATA RAID
controller. The RAID hard drives are hot swappable, but the optional RAID controller is not.

To increase capacity to 1,500 users, the MXe

III Expansion Kit includes a second processor and a 128
-
channel echo canceller expansion module.


In its base configuration (one PQII 8280), the MXe Controller is suitable for up to 350 stations per
controller, providing a BHCC rate of 28,800. With two P
QII 8280s installed, it is suitable for up to 1,500
stations per controller, providing a BHCC rate of 40,400.


Stratum 3 clocking is included as well as an embedded analog module, which provides Foreign Exchange
Station/Foreign Exchange Office (FXS/FXO),
Music on Hold, paging, relays and door/gate entry interface
circuits.


Redundancy is available with the addition of an optional SATA RAID controller, two hard disks, and a
second AC PSU (purchased separately). The redundant MXe Controller uses dual 160 GB

SATA hard
drives in a RAID 1 configuration, and dual hot swappable power supplies.







<Customer logo here>

<Mitel entity here>

Page
14

of
112


MXe Controller Front Panel


The 3300

MXe Controller’s front panel copper interface module (CIM) ports are used to connect analog
service units (ASU), providing additional analog telephone support. The controller front panel also
consists of the following components:





Alarm port



Two DB
-
9 po
rts, connected to the RTC, for maintenance and printer purposes



Two 10/100/1G Base
-
T Ethernet LAN ports (RJ
-
45 connector)



One 10/100 Base
-
T Ethernet WAN port (RJ
-
45 connector)



Four CIM ports



Remote alarms on/off



System LEDs: alarm, hard drive, power/statu
s



Status LEDs: Ethernet, CIM, and alarm



Reset pin







<Customer logo here>

<Mitel entity here>

Page
15

of
112


MXe Controller Rear Panel


The controller rear panel consists of the following components:





One or two power supplies



Input power connector (standard male IEC320 AC), one on each power supply)



Protective ground



One or two hard drives



Analog Main Board (AMB) with LS, ONS, Paging, MOH interfaces



Standard Configuration





Six expansion modules (four for external connectivity, two for internal)



One 533 MHz processor (shared by the real
-
time control

and Ethernet
-
to
-
TDM functions)



512 MB of RAM



One embedded Quad DSP



64
-
channel echo canceller (in DSP module)



One 160 GB SATA hard drive



Power supply



AMB (six LS trunks, four ONS ports)



Expanded Configuration



The MXe Expanded configuration is based on

the MXe Standard, but with the following additions:





O
ne
533

MHz processor

separates RTC and E2T functions)



a second 80 G hard drive (both are preloaded with MCD software)







<Customer logo here>

<Mitel entity here>

Page
16

of
112

ASU II


The Mitel ASU II is a common platform for delivering analog trunks and
extension services to all markets .
It comprises a chassis with two card slots: a 24
-
extension or ONS card slot and a four
-
trunk
-
plus
-
12
-
extension card. Any card can fit into any slot and the cards can be inserted while the unit is operational.


The ASU II

chassis can support up to 48 on
-
premises station (ONS) phones and up to eight LS trunks
plus Music on Hold or loudspeaker paging, depending how the unit is configured with peripheral cards.

Four
-
plus
-
12
-
Port Combo Analog Card


The four
-
plus
-
12
-
port comb
o card supports




12 ONS lines for analog phones



four loop start trunks for analog connection to a central office



four system fail transfer relays that provide direct connection between an analog telephone and
an LS trunk in the event of a system or power f
ailure



The North American version supports Custom Local Access Signaling Services (CLASS) on the
ONS circuits. CLASS allows the MCD system to pass calling line ID digits and CLASS name
information to display phones that support caller ID functionality.

24
-
Port ONS

Analog Card

The 24
-
port ONS card supports 24 ONS lines. All ONS circuits on both the combo and 24
-
port ONS line
cards are protected against high
-
voltage surges.


Scalability

Through clustering, our proposed platform extends to more than 65,000 users. Clustering involves
grouping multiple Mitel 3300 ICP Controllers into a seamless network. All controllers in a cluster share
phone information. The cluster provides fallback for a

fully resilient solution.







<Customer logo here>

<Mitel entity here>

Page
17

of
112

Clustering allows us to combine up to 999 platforms together accommodating an increasing user base.
Since the 3300 ICP Controller does not use cards or cabinets as in a legacy PBX, [
ENDCUSTFULL
]
would need only to purchase a te
lephone and license to scale as large as needed.


Licenses can be downloaded from the Mitel Applications Management Center (AMC), which allows for
instant activation of licenses across a network. Phones can be shipped to a location and plugged in, with
li
censes and programming handled remotely.


Dynamic Extension

Mitel Dynamic Extension is an embedded feature of the MCD platform. It will provide seamless converged
mobility across the entire [EndCustFull] organization. [EndCustFull] users can work anywhere

in the world
without limits on device, network or location.



Without the need for client software or additional server hardware, Dynamic Extension will enable
[EndCustFull]’s mobile workforce to





set any number as a hot desk contact point



use any devic
e on any network and still be recognized as part of the internal MCD system



make and receive calls on up to eight numbers/devices (including SIP Wi
-
Fi clients) each as part
of a Personal Ring Group (PRG), yet present a single identity to callers. This enab
les high
availability and offers the opportunity for cost savings.



Dynamic Extension works with any device that has a phone number, including personal phones.
Employees can use a mobile or fixed device. [EndCustFull] no longer needs to standardize device
s or
purchase and maintain mobile phones. Business calls from mobile devices can be routed through the
business PBX and billed to the company. Dynamic Extension does not require complicated SMDR
records, and leaves personal calls as the responsibility of t
he user, not the company.



Dynamic Extension provides users with one centralized mailbox to store all voice messages. This not only
simplifies message management, but also eliminates the expense of multiple voice mail services.



The Mitel components that

enable Dynamic Extension include External Hot Desking and PRGs .



External Hot Desking



External Hot Desking allows external devices (usually identified by an external phone number) to be hot
desk devices. This enables calls made to the user’s hot desk number to ring any device associated with
that user (see Personal Ring Groups below). Exter
nal Hot Desking requires a license for each external
device or number used, This license lets the user choose which external number to log on to.



When a user calls into the business communications system, their device is authenticated and MCD
recognizes
the user as being permanently logged on. The user can then make multiple calls without
leaving the business PBX.


Once logged in, the attributes and features of the user’s Mitel IP desk phone are available. Users can
reach colleagues by dialing the interna
l extension number, make long
-
distance calls over the corporate
network, access voice mail, and, with a single key, use any Mitel telephony feature such as Hold,





<Customer logo here>

<Mitel entity here>

Page
18

of
112

Transfer, Conference, Cancel, or Swap. MCD recognizes the user’s number as a valid member of a

hunt
group or ring group.


MCD’s bidirectional call
-
routing capabilities enable the system to understand the user’s status and
determine if they are available for calls. After the call is finished, the user simply presses a key to return to
dial tone.


In addition to the standard user license, External Hot Desking requires a license for each device. As part
of this license, the user gains the ability to choose which external number to log on to.







<Customer logo here>

<Mitel entity here>

Page
19

of
112




Personal Ring Groups

Personal Ring Groups

(PRG) allow a
collection of devices (directory numbers) to be
associated with a single user. When the user’s
primary number is called, MCD rings all
associated devices (up to eight)
simultaneously. The primary number acts as
the unique PBX identity or dir
ectory number.
Similarly, whichever device in the PRG a
mobile worker uses to make a call or access a
feature will take on the user’s identity including
all their rights and permissions.


The PRG can be configured as One Busy All
Busy. This means, if one d
evice in the PRG is
occupied, MCD would treat any subsequent
calls to the primary number as busy.


PRG’s Handoff feature allows calls to be
pushed or pulled between devices in a group.
A push passes the call to the group, where it
can be answered by any ot
her enabled device.
A pull takes an in
-
progress call away from
another device.



Group Presence



Group Presence lets users indicate which device/identity/number in their groups is available to receive
calls. For example, a user in the office can set up w
ireless, mobile and home numbers as “absent” from a
ring group. This does not remove them from the group, but ensures they do not ring when a call comes in.
Alternatively, a user working at home can make a cellular phone “present” in the group to ensure it

receives any incoming calls.


Group Presence can be selected for voice hunt groups, Name Tag hunt groups, ring groups, Personal
Ring Groups, and ACD agent groups. The Group Presence option is controlled by Class of Service.

Auto Attendant

Embedded within
MCD

is a standard automated attendant function that allows an external caller to dial
through to an extension without going through a live attendant. With this application, customers who call
in to
the
[EndCustFull]

MCD

system can:




p
lace a call to a
number in the corporate directory



transfer to

a department or person specified in the auto attendant voice prompts



s
elect multilevel options

in response to
cascading

voice prompt
s to reach a particular department
(e.g., “Press 1 for Recreation” then “Press

5 for Aquatics”)








<Customer logo here>

<Mitel entity here>

Page
20

of
112

The embedded automated attendant can be programmed to play different greetings during open and
closed business hours
. After
-
hours callers reach a

company directory that
allows them to enter either an
extension number or
choose from a
si
ngle
-
digit option.


In addition, the
m
ultilevel capability embedded in the auto attendant (MLAA) allows

[EndCustFull]

to
program

a hierarchical menu.
As mentioned above, this

provides callers with self
-
service options to reach
individuals, departments,
or
prerecorded information, or to leave voice messages.




Embedded Voicemail

MCD includes a full
-
featured, cost
-
effective integrated voice mail system that supports 750 user
mailboxes, up to 30 ports for voice mail calls, 450 hours of storage time, and a
multi
-
level auto attendant.
Users continue to be provided with voice mail if they are moved to a secondary Mitel 3300 ICP Controller
during resiliency (failover state). MCD also supports integration to external voice mail solutions.


MCD embedded voice ma
il system includes




Standard Unified Messaging:

Users can forward voice messages (includi
ng Record
-
a
-
Call messages) to e
mail. Users can forward individual voice messages manu
ally or all voice
messages to e
mail automatically.




Automated Attendant:

[EndCustF
ull]

can play different greetings during open and
closed business hours. Also provides callers with a company directory that uses extension
numbers or names as the dialing method, as well as single
-
digit multi
-
level option selection.
Multi
-
level auto atten
dant (MLAA) creates a hierarchical menu for users to navigate through
the organization’s services and departments, and to perform tasks such as prerecord
information.




Personal Contacts:

Allows users to create a customized voice menu tree, providing
calle
rs with the ability to reach them by other means such as cellular phone, teleworker
phone or fax.




Record
-
a
-
Call:

User can record conversations and save it in their voice mailbox.




User Mailboxes
: Supports multiple mailbox types such as Extension, Message
-
Only,
Transfer
-
Only, Information
-
Only, Guess and Administrator, a tutorial that assists new
subscribers with mailbox setup and password creation, message retrieval using mnemonic
prompts (P to play, K to keep, D to discard, etc.), easy
-
to
-
use menus that a
llow users to send
urgent, private or certified messages.




Notification of Waiting Messages (MWI):

Provides a message
-
waiting indicator (MWI)
light on the user’s phone. For analog phones or phones without a message
-
waiting light,
message
-
waiting notificati
on can also be obtained when the user has the system call the
Directory Number (DN) associated with the mailbox, an outside number, and a message,
tone
-
only, or digital pager.


<<Proposal coordinator: Include this next paragraph/point only if you are
proposing to a hospitality
customer.>>






<Customer logo here>

<Mitel entity here>

Page
21

of
112




Integration to Hotel Property Management System (PMS):

Provided by an IP
interface to the hotel’s PMS system. This connection allows the hospitality system to notify
the voice mail system when a user is checked in or

checked out (the voice mail system either
creates or deletes a mailbox for the guest based upon this information).

Selected Features

The full list of MCD’s 500 features is described in our technical documentation (available separately).
Selected key featu
res are described briefly below.


<<Proposal coordinator: Add additional features as appropriate to this section.>>

ACD (Automatic Call Distribution)

MCD provides fully integrated ACD functionality that includes call distribution, agent mobility, feature
configuration, administration and recorded announcements. The integrated ACD functionality of MCD is
enhanced by the Mitel Customer Service Manager sui
te of applications, which enables
[EndCustFull]

to
maximize the efficiency of its contact center.

Hot Desking

Hot desking lets users share IP phones. Users can log onto any hot desk
-
enabled Mitel IP phone within a
defined cluster of MCD platforms, regardle
ss of location. For example, a user with a New York home
office can travel to a Chicago office and log in to a hot desk
-
enabled phone, and use that phone to
conduct business from Chicago as though they were still in New York. Personal settings, and voice
m
ailbox, become available when the user logs in. Hot desking includes password protection for personal
security.


Hot desking is invaluable to workers who share desks or facilities. For example, a hot desking ACD agent
can log into any telephone in an agent

group. The system applies the agent’s personal phone profile to
that ACD phone. After logging into the ACD phone, the agent has access to personal speed calls, feature
keys and phone settings. If ACD agent hot desking is enabled in the call center, [
EndCu
stFull
] does not
have to provide a separate phone for each agent’s personal use. Instead, a pool of shared phones is
available to many agents, and any ACD phone that the agent logs into also functions as the agent’s
personal phone.

Call Reporting and Cost
Management

MCD provides a highly flexible Station Message Detail Reporting (SMDR) data collection capability. It
gathers data for outgoing and incoming trunk calls and internal station
-
to
-
station calls. It also allows
extensive SMDR record format changes t
o accommodate items such as international ANI digit strings,
attendant line appearances, or incomplete internal calls.


When used with an external call accounting system, such as the (optional) Mitel Call Accounting software
package, MCD reveals importan
t data for tracking and reporting on telecommunication costs.


With Call Accounting software, users can effectively manage telephone activities and expenses as well as
track telephone system costs and summarize them in reports.







<Customer logo here>

<Mitel entity here>

Page
22

of
112

Location Based Accounting

Location Based Accounting gives MCD administrators the ability to attribute devices, and subsequently
calls, to specific locations. This will allow
[EndCustFull]

to bill those locations when a hot desk user has
logged into different devices and worked at d
ifferent locations. The device location information is provided
in MCD’s SMDR records that contain identifier fields for the calling party and for the called party.

Account Codes

MCD offers 11,000 (default) to 40,000 account codes.

Night Service Indication

The feature access key informs users which mode the system is in. The phone’s key appearance is lit if
the system is in Night Service, and off if it is in Day Service
. If the key is lit, the telephone display informs
the user whether the system is in Night Service 1 or Night Service 2 by pressing the key.

Logged in Hotdesk Busy Lamp Field Indication

A Class of Service option provides a steady green key busy lamp field

indicator when a hot desk user is
logged in. This indicator is off if the Hot desk user is logged out.

Multi
-
colored LEDs

With multiple calls on hold, it is difficult for a user to determine which call pertains to them. Mitel’s phones
offer multi
-
colour
ed LEDs that indicate which line was placed on hold. Rather than guessing which line is
on hold, a green light flashes to indicate call ownership. This is only supported on non
-
programmable key
modules.

Record
-
a
-
Call

Using voice mail as a recorder, this fe
ature allows subscribers to record a live conversation between
themselves and another party, and save the message in voice mail. Recorded calls can be replayed to
ensure accurate information was derived from the conversation or perhaps to monitor harassme
nt. Unlike
regular voice mail messages, Record
-
a
-
Call messages are stored immediately as saved messages, so
they do not trigger message
-
waiting indications


on the user's telephone. When a user activates this
feature, it is accomplished in silence.

Mainten
ance Logs

The MCD system supports a robust set of remote diagnostic commands through an HTTPS
-
based
system administration interface, Telnet CLI interface, or locally through the console port. MCD also
maintains error and event maintenance logs that can be
viewed remotely or retrieved to assist in problem
diagnosis. An additional software diagnostic tool, IP Phone Analyzer, runs on a Windows
-
based PC and
collects trace, status, and statistical information for all Mitel IP phones.






<Customer logo here>

<Mitel entity here>

Page
23

of
112

Traffic Measurement

The Mite
l Traffic Analyzer generates reports on the health of a network. The trunk report covers




Busy hours


highlights the busiest hour of the business day



Traffic by period


reveals when trunks experience either high usage with low call peg count or
low us
age with high call peg count


These reports will also help
[CUSTOMER]

fine
-
tune its routing to take advantage of the lowest rates
provided by its carrier. As part of the Traffic Analyzer, Mitel route reports ascertain whether callers were
able to access th
e appropriate route, route list, and route plan.

Security

MCD delivers rich telephony features, call handling, and networking to users across an organization.
Security has been incorporated into its very design, ensuring everything from the system and eac
h
transmission to user access and administration functions are safeguarded.


Protected Transmissions



MCD safeguards transmissions through encrypted media and signaling paths for all Mitel IP phones. This
is accomplished with secure real
-
time protocol (RTP) using 128
-
bit advanced encryption standard.


Mitel encrypts the media path between multiple MCDs using secure socket layer (SSL) protocol enabling
IP phones to send and receive voice traffic only when instructed by MCD through commands sent in the
encrypted call control stream.






<Customer logo here>

<Mitel entity here>

Page
24

of
112



Secure Management
Interfaces
:

MCD’s set of management tools use SSL security for data encryption and require login credentials for
access. Multiple levels of access control are provided to allow users to divide responsibilities. The Mitel
MiXML API is also SSL
-
encrypted an
d uses a certificate
-
based mechanism to achieve a secure level of
access for applications connecting in to the system. The management access point provides secure
remote administration for VPN or dial
-
up access.


Security for Remote IP Telephony Calls
: Dep
loying the Mitel Teleworker Solution gateway within the
DMZ (demilitarized zone) of the LAN provides SRTP encryption to protect the confidentiality of Internet
-
based teleworker calls. It also provides SSL
-
based security for protecting the call control sign
aling to
prevent eavesdropping on Mitel teleworker calls over the Internet, and protects call control signaling from
being monitored or modified.






<Customer logo here>

<Mitel entity here>

Page
25

of
112


Digital Certificates
: Unauthorized eavesdropping, although not service
-
disrupting, can lead to a breach
in c
onfidence between the caller and called parties. With IP
-
based telephony, voice packets must traverse
the IP network infrastructure which increases the risk of snoopers. Mitel offers public
-
key encryption
through a trusted third party for strong authentica
tion based on digital certificates. User certificates are
encrypted with the private key of the certificate authority and can only be decrypted by those with the key.
The transmission cannot be altered or forged by anyone without the decryption key.


Preve
ntion of Toll Abuse
: Comprehensive toll control is an integral part of MCD call control. It enables
the restriction of user access to trunk routes and specific external directory numbers. It also provides
Class of Restriction (COR) and Class of Service (CO
S) features that substantially reduce the risk of toll
abuse.

System Reliability and Resiliency

Rather than dedicating expensive, robust hardware to resolve temporary and infrequent system failures,
Mitel resiliency makes efficient use of a system’s existi
ng capacity. MCD will increase communication
reliability by maintaining calls in progress, handling new incoming and outgoing calls, and continuing to
provide voice mail services if a controller or network fails. Using distributed resources provides for se
lf
-
healing techniques through routing and the utilization of controller
-
to
-
controller backup configurations. Our
solution ensures there is no single point of failure and optimizes hardware resource usage.


Device resiliency:

If an IP device loses communica
tions with its primary controller, the IP device can
be programmed to automatically register with a secondary controller to receive call control and routing
services. Communication could be lost to the primary controller due to a network outage or problems

with
the primary controller. Once the health of the primary controller (or the network it is connected to) is
restored, the secondary controller will send the IP device back to its primary controller. The transfer of
phone service between primary and seco
ndary controllers, as well as the maintenance of calls in
progress, ensures that the impact of system failures is minimal to desktop users.


Business continuity:
The Mitel solution’s distributed architecture enables a 3300 ICP Controller to be
located at
a remote facility as part of a disaster recovery or business continuity plan. The remote 3300
ICP Controller can be programmed to provide telephony services should the primary site become
unavailable. It can also be kept in synch with the primary controlle
r using system data synchronization.


Mitel also provides the simple
-
to
-
deploy Mitel Border Gateway (MBG) teleworker solution. Through this
solution, remote employees can access office phone settings and extensions.


Redundancy


The 3300 ICP MXe Controller

supports hard drive redundancy, disk mirroring, and power supply
redundancy using an optional RAID controller and two hard disk drives, and an optional redundant power
supply unit.


LAN Requirements

For optimum voice quality when running VoIP networks, we recommend
[E
ndCustFull
]

separate voice
and data traffic as much as possible by following these guidelines:






<Customer logo here>

<Mitel entity here>

Page
26

of
112




Run voice and data on separate VLAN.



Use a separate sub
-
network for voice traffic.



Use Ethe
rnet switches instead of hubs (voice and data should not share the same Ethernet hub).



Use full
-
duplex fast Ethernet for the Mitel 3300 ICP controller ports.



Use full
-
duplex fast Ethernet and Ethernet trunks between switches.



To enable Quality of Service (
QoS) across a network, use the 3300 ICP system to support Type
of Service (ToS) as well as DiffServ and IEEE 802.1 priority queuing for maintaining LAN/WAN
QoS.


As we do not manufacture LAN and WAN equipment, we take ensure that we do not need to use
prop
rietary protocols in the data networking subsystem. We are highly committed to the use of industry
standards in communications operations and functions integrated with LAN and WAN communications
equipment. Our solutions allow voice and signaling to be carr
ied over a multitude of LAN and WAN
transport mechanisms that support IP. This allows the Mitel system to operate independently from the
LAN and WAN connections. Our VoIP systems work with every major LAN/WAN communications
equipment vendor in the industry
.


Listed below are the industry standards required for high
-
integrity operation of the Mitel VoIP solution.


Network equipment should, at minimum, provide connectivity according to




IEEE 802.3 (Ethernet)



IEEE 802.3i 10Base
-
T (subset of 802.3, 2006)


Improvements in operation and installation can be obtained through the application of




IEEE 802.3u
-

100Base
-
T (subset of 802.3, 2006)



IEEE 802.3z
-

1000Base
-
T (subset of 802.3, 2006)



IEEE 802.1d (2006)


MAC Bridges



IEEE 802.1Q (now included in IEEE 802.1
d)
-

Layer 2 VLAN



IEEE 802.1p
-

Layer 2 Priority



RFC 2474
-

DSCP (Differentiated Services Code Point)



IEEE 802.1x
-

Access Authentication



IEEE 802.1w


Rapid Spanning Tree, now included as part of IEEE 802.1d (2006)



IEEE 802.3af
-

Power over Ethernet



IEEE
802.1ab
-

LLDP (Link Layer Discovery Protocol)



TIA 1057
-

LLDP
-

MED (Media Endpoint Discovery)


Voice devices do not connect directly to the WAN, but rather through the LAN. Devices may connect to a
customer LAN network and then via a WAN link to the PSTN
, and Internet. The business must also
deploy MBG (Teleworker) at the public network connection point.


To ensure quality of service information is carried through the network, the routers should also support
the ability to



handle multiple VLANs on a sing
le connection to the LAN, or one connection per
subnet/VLAN



map DSCP values to the WAN priority mechanism and the reverse (e.g., DSCP to
MPLS experimental bits)






<Customer logo here>

<Mitel entity here>

Page
27

of
112

Station Connectivity

MCD supports a range of station connections, including




10/100/1000BASE
-
T
Ethernet connection: for IP phones to connect to the system through an
Ethernet LAN 1000BASE
-
T (supported with the optional Mitel Gigabit Ethernet Stand)



on
-
premises analog station port (24 V per port) for industry
-
standard Dual Tone Multi
-
Frequency
DTMF
analog phones (External loop resistance on these stations is 600 Ohms or less, and the
loop length is 5,000 feet (approximately 1,500 meters) on 26
-
gauge wire.)



digital interface ports for system digital phones and consoles



wireless connection with Wi
-
Fi/8
02.11 to permit the easy addition of wireless IP phones to
existing 3300 Controllers (This will add full wireless IP functionality to an existing PBX in an
incremental fashion, avoiding expensive PBX upgrades.)



IP
-
DECT solution deployment that can deliver
from one to 512 phones per installation through a
maximum of 256 IP LAN
-
connected indoor, outdoor, or combination radio base stations


Network Connectivity

MCD controllers connect to your data network using a 10/100/1000 LAN port. Both the MXe and CX/CXi
C
ontrollers are provided with dual LAN ports and support Rapid Spanning Tree Protocol (RSTP) for data
network level resilience.


Embedded interoperability is a key principle in Mitel’s IP
-
focused development efforts. MCD delivers a
system that supports IP,
wireless, analog, or digital technologies and can easily grow and add
technologies as needed. 3300 Controllers typically have the following network connectivity capabilities.

Supported Analog Trunks



Loop Start trunks



Ground Start trunks (via external
peripheral cabinet)



E&M (via external peripheral cabinet)



Direct Inward Dial (DID)



Loop/Tie trunks


Each 3300 Controller also supports analog devices such as phones, fax machines, and modems, and
offers resources for system fail transfer, paging, and Music

on Hold.

Supported Digital Trunks



T1/D4, E1



R2 (supported via specialized Network Services Unit)



Primary Rate Interface (PRI)



Basic Rate Interface (BRI)

Digital network connectivity is provided through embedded digital trunk modules housed directly in the

3300 Controller. These services can be either full links (T1/E1/PRI) or channeled to where those services
are provided by the carrier.






<Customer logo here>

<Mitel entity here>

Page
28

of
112

ISDN Connectivity

3300 Controllers use multiple ISDN protocols for PRI and BRI connectivity. It provides ISDN
-
specific
support to enable capture and control of costs, analysis of peak periods, and fine
-
tuning of network
resources for both voice and data calls. MCD supports




Automatic Route Selection/Least Cost Routing (ARS/LCR)



ISDN SMDR



minimum/maximum traffic control



pe
r
-
call service selection



limited toll restriction



trunk diagnostics



Non
-
Facility
-
Associated Signaling (NFAS)



remote LAN access



networking feature transparency on switched ISDN calls



IP networking connectivity


SIP Support

SIP Trunking Support

MCD supports
SIP trunking. It acts as a SIP back
-
to
-
back user agent and connects to the carrier SIP
proxy and registrar.


SIP trunking capability is integrated into MCD; no additional hardware, servers or media proxies are
required. SIP trunking is licensed based on ea
ch SIP session.


MCD provides complete interoperation between Mitel IP phones, analog phones, digital trunks, and SIP
end points as well as to SIP trunks.


SIP trunking features include the following:




911 emergency service support: The SIP service provide
r can be chosen as the outgoing
emergency route . Caller’s Emergency Service Identification (CESID) information must also
be programmed.



DNS support: Communications between SIP service providers and at the 3300 ICP can be
configured to use either Fully Qua
lified Domain Names (FQDN) or IP addresses.



Configurable Real
-
time Transport Protocol (RTP) Packetization: 3300 administrators can
configure the voice stream packet rate for SIP trunks to their service providers choosing a
rate between 10ms to 80ms (with 1
0ms increments). IP sets supporting this feature include
the
5302, 5304, 5212, 5224, 5235, 5312, 5324, 5320, 5330, 5340, 5360 IP phones.



Billing and SMDR: The service provider bills calls based on the peer connection to the 3300
ICP. The 3300 ICP records a
re created with a special SMDR tag entered in the SIP Peer
Profile form. An SMDR tag can be enabled for outgoing and incoming calls.



SIP digit detection supports external hot desking across SIP trunks and allows mid
-
call
features over the SIP trunks when M
CD is integrated with Mitel Border Gateway Release 6.0
SP1.






<Customer logo here>

<Mitel entity here>

Page
29

of
112



External hot desk users can dial digits while on a SIP trunk call. This lets them access mid
-
call features, enter their PINs, and initiate user callbacks. Either your outbound proxy or the
servic
e provider’s session border controller is required to detect the digits contained within
the SIP media stream and transmit them to the MCD. This feature is easily programmed by
adding the outbound proxy or session border controller as a network element, an
d then
configuring a SIP peer with Authentication and Key Press Event options.


SIP trunks can also modify the Called and Calling Party Numbers for incoming calls. This means you

can
alter dial strings
contained in inbound SIP calls. After adding substitut
ion rules, you can apply them to the
called party and the calling party SIP headers. This functionality is implemented as part of the initial
system setup when you program SIP trunks and program SIP phones.

SIP Trunking Interoperability

MCD SIP trunking is

compliant to IETF standards and supports a broad range of interoperability. Mitel
and our partners have conducted extensive interoperability testing with SIP soft switches, carrier SIP
services, SIP PBXs, SIP gateways and SIP firewalls.

SIP End Points Sup
port

The MCD gateway provides a standards
-
compliant SIP registrar as well as SIP back
-
to
-
back user agent
functionality embedded in the common control. No additional hardware is required for SIP end point
support; however SIP user licenses are required.

Recovery from Power Outage

In the event of a power failure,
the

MCD

system
will recover automatically upon power restoration to the
affected area.
MCD

can provide your network users with dial tone on their phones in as few as six
minutes after full power restoration to the area.


For greater security from power outages, Mitel recommends the use of a
n uninterruptible power supply
(
UPS) to bridge outages
.


Electrical and Physical Specifications

System Input Power Requirements for Controllers

Input/disconnect


IEC 320
-
C14, Class 1 AC, Receptacle (two receptacles on
MXe with redundant power)

Input voltage/frequency
rating

100 Vac to 120 Vac; 50/60 Hz

200 Vac to 240 Vac; 50/60 Hz

Maximum input power

100 W (100
-
user/MX)

120 W (250
-
user)

150 W (700
-
user/LX)

250 W (CX/CXi)






<Customer logo here>

<Mitel entity here>

Page
30

of
112

200 W (MXe base)

250 W (MXe expanded)

300 W (AX)


AC source range

90 Vac to 264 Vac; 47 Hz to 63 Hz


Grounding
Requirements

The 3300 Controller system grounding conductor is an insulated three
-
wire 15
-
amp AC power cord set
included with the equipment. Its size according to the United States National Electrical Code (NFPA/ANSI
70 Section 250
-
95, Exception No. 1, and

Section 240
-
4, Exception No. 1).


The protective grounding conductor must comply with the general grounding rules contained in Article 250
of the National Electrical Code, NFPA 70, or Section 10 of the Canadian Electrical Code, CSA C22.1.



AX

CX

MXE

Height

13.35 in.

(39.90 cm) (7 U)



3.5 in. (8.9 cm) (2 U)

3.5 in. (8.9 cm) (2 U)

Width

17.4 in.

(44.20 cm)

17.75 in.

(45.1 cm)


17.75 in. (45.1 cm)

Depth

13.87 in.

(35.23 cm)

16.5 in.

(41.9 cm)

20.25 in. (51.4 cm)

Weight

39.70 lb

(18.01 kg)

19.8 lb (8.98 kg)

MXe 28 lb (12.7 kg)


Note: All controllers can be mounted on a 19
-
inch rack.







<Customer logo here>

<Mitel entity here>

Page
31

of
112

Environmental Requirements

Operational Environment Requirements



CONTROLLER

ASU/

UNIVERSAL
ASU

NSU

PERIPHERAL
NODE

DSU

Temperature
(recommended)

40°F to 122°F

(4°C to 50°C)


40°F to
122°F


(4°C to
50°C)

40°F to 122°F


(4°C to 50°C)

40°F to 122°F

(4°C to 50°C)

50°F to 80°F

(10°C to
27°C)


Relative
Humidity
(recommended,
non
-
condensing)


5% to 95%


5% to 95%



5% to 95%



5% to 95%



34% to 80%


Maximum Heat
Dissipation
(fully loaded)

MXe:

750 BTU/hr


CX/CXi:

170 BTU/hr


AX:

1024 BTU/hr


170 BTU/hr


䅓A


㈶〠Bq唯桲r


Apr⁉

㘰⁂q唯桲

㜲㐠Bq唯桲

㈶㘠Bq唯桲

Air⁆ ow
慴
maximum
潵瑰畴u潦⁦慮sF


㐶⁦t
3
/hr



150 ft
3
/hr

150 ft
3
/hr

Maximum
Acoustic
Emissions

(<10% duty
cycle)

50 dBA
continuous


75 dB
intermittent




50 dBA
continuous


75 dB
intermittent

50 dBA
continuous


75 dB
intermittent


Note: Conversion factors: 1 watt is equal to 3.412 BTU/hr. One ton of
refrigeration is equal to 12,000
BTU/hr or 3.516 kilowatts. 3/4 kilowatt/hour is equal to 1 ton of refrigeration.


Operational Environment Requirements


CONDITION

SPECIFICATION

Temperature

39°F to 122°F (4°C to 50°C)

Humidity

5% to 95% relative humidity, non
-
condensing






<Customer logo here>

<Mitel entity here>

Page
32

of
112


Room Requirements



The 3300 Controller should be located in a clean, dry, well
-
ventilated, well
-
lit and easily accessible area. It
cannot be located near sprinkler systems, sweating pipes, steam pipes, steam
vents, corrosive fumes,
exhaust from machinery, electronic equipment that generates strong radio frequency fields (such as
transformers or motors), equipment that generates strong magnetic fields that can corrupt hard or floppy
disk data, or reproducing ma
chines.


Heating, cooling, forced ventilation (and humidification or dehumidification) should be used as necessary
to maintain the required conditions.


Virtual Mitel Communications Director

Virtual Mitel Communications Director (Virtual MCD) is the indust
ry’s first virtualized voice
communications software application. Virtual MCD uses the same MCD software deployed on the Mitel
3300 Controllers industry standard servers (ISS), however it is delivered as a virtual appliance for
VMware enabled virtual data
centers.




Evolution of Communications Solutions


Server virtualization and management tools such as that provided by VMware data centers save costs by
reducing their physical server footprint. Along with power and real estate savings, this results in s
erver
management automation and data center process standardization. The number of applications that can
be virtualized is also increasing.


Mitel offers several communication applications as Virtual Appliances and a few others that are VMware
-
ready. Both

Virtual Appliances and VMware
-
ready applications can be deployed into a VMware enabled
virtual infrastructure. Virtual Appliances, however, come pre
-
packaged as a readily deployable software
package that simplifies installation time and ensures that the v
irtual appliance is correctly configured,
which saves time and avoids potential virtual software installation issues. Virtual Appliances available as
part of Mitel Virtual Solutions include






<Customer logo here>

<Mitel entity here>

Page
33

of
112




Virtual MCD



Virtual MAS, with Nupoint, Audio and Web Conferencing

and UC Mobile



Virtual Mitel Border Gateway, Teleworker service, SIP Trunk proxy service, and Application Web
Proxy service



Virtual Unified Communicator Advanced server


VMware
-
ready applications include Mitel Contact Center Enterprise Edition and Mitel

Contact Business
Edition, and Mitel Enterprise Manager


Mitel enables these applications to run in virtual data center environments with other business
applications so that they fit within
[
ENDCUSTFULL
]’s

established business processes.




Data Center

Virtualization

Virtual MCD Benefits

Virtual MCD offers the following benefits:



Reduced Capital Expenditure


Consolidating telephony and unified communications means that
[CUSTOMER] would no longer require dedicated physical servers or appliances to provi
de
telephony and unified communication services to employees.



Reduced Operations and Maintenance Costs


[CUSTOMER] can reduce time and effort, and the
costs associated with managing servers. Integrating telephony within the VMware virtual
infrastructure r
esults in communication solutions being managed with other virtualized business
applications.






<Customer logo here>

<Mitel entity here>

Page
34

of
112



Reduced Power Consumption


Consolidating business communications applications would
enable [CUSTOMER] to take advantage of the power savings of virtual environme
nts enabled by
VMware server virtualizations


reduced servers and VMware Distributed Power Management.



Improved Application Availability


Integrating with a VMware managed virtual environment
enables Virtual MCD to use VMware vSphere Client and vCenter
to manage application
availability. Applications are not subjected to prolonged downtime for server maintenance.



Integrated Business Continuity


VMware virtualization provides integrated disaster recovery
management. Management methodologies and best prac
tices are consistently applied across all
applications in the data center, including business communication applications, resulting in time
and money savings.



Consistent Feature Set and Licensing


Virtual MCD uses the same communications software
suite a
s that available on 3300 controllers and Industry Standard Servers (ISS). It uses the same
software licensing as MCD. [CUSTOMER] investment would be protected when migrating from
non
-
virtual to virtual environments.



Seamless Telephony Integration


Virtual

MCD integrates seamlessly in a network of MCDs


either 3300 ICP, MCD
-
ISS or other Virtual MCD appliances. Virtual MCD integrates with the
same Mitel desk phone portfolio and applications suite.



Faster System Deployment


Virtual MCD is easy to install i
nto an existing virtualized data center.
Increasing communications capacity and adjusting overall workload is faster than it would be with
traditional dedicated specialized appliances or dedicated servers.


Mitel Border Gateway

The Mitel Border Gateway (MB
G) is a plug
-
and
-
work solution that securely deploys multiple services.