Mitel MIVOICE OFFICE 250 Manual

MiVoice Office 250
ENGINEERING GUIDELINES
RELEASE 6.2

NOTICE
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.
No part of this document can be reproduced or transmitted in any form or by any means - electronic or
mechanical - for any purpose without written permission from Mitel Networks Corporation.
For additional information and/or technical assistance in North America, certified technicians may contact:
Mitel Networks Corporation
Technical Support Department (USA)
1146 North Alma School Road
Mesa, AZ 85201
1-888-777-EASY (3279)
Trademarks
The trademarks, service marks, logos and graphics (collectively "Trademarks") appearing on Mitel's
Internet sites or in its publications are registered and unregistered trademarks of Mitel Networks
Corporation (MNC) or its subsidiaries (collectively "Mitel") or others. Use of the Trademarks is prohibited
without the express consent from Mitel. Please contact our legal department at [email protected] for
additionalinformation.Fora list ofthe worldwide Mitel Networks Corporation registered trademarks, please
refer to the website: http://www.mitel.com/trademarks.
MiVoice Office 250 Engineering Guidelines
Release 6.2
June 2016
®,™ Trademark of Mitel Networks Corporation
© Copyright 2016, Mitel Networks Corporation
All rights reserved

Table of Contents
iii
Chapter 1:
New Features
What’s New in this Release? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
MiVoice Office 250 Release 6.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
system park . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Import Audio Files for Audiotex Recording Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . .2
MiVoice 5624 Wireless Phone Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Discontinuation of support for CS platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Other Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
More Features in Release 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
MOH (Music on Hold) for parked destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Group Pickup Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Other Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
MiVoice Office 250 v6.1 SP1 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Engineering Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
multi-Node video support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
SIP Phone Group – Password Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
MiVoice Office 250 Release 6.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Product Re-branding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
New PS1 Hardware Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
MiVoice Office 250 Attendant Console Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Digital Telephone Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Virtualized PS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Video Support for SIP to SIP Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
BT CLIP CLID Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
SIP ACD Agent Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
MiVoice Office 250 v6.0 SP2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
DTMF Decoding Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Propagation of Original Caller ID to P-Asserted Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Do not use Out-bound Username in REGISTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Support for new DDM16 and DEM16 circuit board revisions . . . . . . . . . . . . . . . . . . . . . . . . .8
MCD Interoperability Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Microsoft Lync Integration Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Support for New Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
UPS Monitoring Support Changes on 6.0 SP2 and later software . . . . . . . . . . . . . . . . . . . . .8
MiVoice Office 250 v6.0 SP1 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Engineering Guidleines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Mid Call Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
MBG SIP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Chapter 2:

MiVoice Office 250 Engineering Guidelines
iv
Engineering Guidelines
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
When to Add a Processor Expansion Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Oversubscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
DSP Resource Costs and Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
System Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
IP Phone Percentage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
High Priority vs. Shared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
High Priority Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Shared Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Phones to Devices Percentage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
IP Phones to Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
When to add a Processing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
High Call Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
All-Ring Hunt Group Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
All-Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
IP Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Hub Node in a Networked System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Voice Mail Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Enhanced Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Processing Server Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Using the System Calculator to Determine the need for a Processing Server . . . . . . . . . . . . .23
Call Load (calls per hour) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
OAI Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Heavy Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Light Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
CT Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
OAI Applications Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
UVM Coexisting with NuPoint UM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Determining the Correct Compact Flash-Type Card Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Basic vs. Advanced Ad Hoc Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Table of Contents
v
Video Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Peripheral Devices for MiVoice Conference/Video Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
High Definition Multimedia Interface Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Ethernet Cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Codecs compatibility matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Bandwidth usage considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Video phone bandwidth limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Network configuration and bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Bandwidth requirements for MiVoice Conference/Video Phone . . . . . . . . . . . . . . . . . . . . . . . .35
General Information on IP Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Video Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Database Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
SIP clients configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Soft client camera settings to control bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
MiVoice Conference/Video Phone settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
MiVoice Border Gateway configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Teleworker Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Bandwidth requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Mid-Call Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Impacts to System Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
System Limitations and Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
System Calculator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
System Calculator Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
System Calculator Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
System Calculator Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
System Recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Phones to Devices Percentage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
IP Phones to Shared Percentage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Digital HX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
IP Phone HX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
IP Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
IP Phones/SIP Trunks HX w/ PEC-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Large number of IP Phones, Trunks and UVM ports HX w/ PEC-1 . . . . . . . . . . . . . . . . . . .50

MiVoice Office 250 Engineering Guidelines
vi
Digital HX w/ PS-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Digital and IP Phones HX w/ PS-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Fully-Loaded Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Exceeds All System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Chapter 1
NEW FEATURES

MiVoice Office 250 Engineering Guidelines
2
WHAT’S NEW IN THIS RELEASE?
This section briefly describes the new features, hardware, and enhancements available on the
MiVoice Office 250.
MIVOICE OFFICE 250 RELEASE 6.2 NEW FEATURES
SYSTEM PARK
System Park is a feature that allows calls to be parked by a phone, then either retrieved again
by that phone, or retrieved by another phone.
• The Park/Pickup key with the same destination may be configured on several phones.
• then any of these phones can park or retrieve calls from the same destination.
• Multiple calls may be parked on the same destination.
• If in a call, the call will be added to the queue of parked calls.
• If not in a call, the first parked call on this destination will be retrieved.
• Parked calls will recall the person who parked the call after a timeout
• Phantom destinations use the new Park Recall Timer (default 180s, range 30-600s)
• HuntGroupsuse theexistingHuntGroupRecallTimer (default 180s, range 1-65'535s)
• If a call is parked on a Park/Pickup key, the key will flash.
• except if the Hunt Group has the ‘Group Call Pick-up’ flag disabled.
• Additional Notes:
• PhoneswithoutaPark/Pickup key can usethefeatures'transfer'and'reversetransfer'
to park and retrieve calls from destinations like "Park Location 1". Therefore it is rec-
ommended to give simple numbers to such Phantom or Hunt Group destinations.
• Assigning a Park/Pickup key to a Hunt Group destination is an enhancement to the
existingGroup Pick-upfeature, allowingGroupPick-upusingasinglekeypress,whilst
also allowing for a visual indication.
IMPORT AUDIO FILES FOR AUDIOTEX RECORDING ENHANCEMENT
Audiotex Recordings are custom recordings used by the MiVoice Office 250 Unified Voice
Messaging (UVM) applications like the Auto Attendant (AA) and Call Routing Announcement
(CRA) features.
Until now, Audiotex recordings could only be recorded using a phone with access to the Voice
Mail System Administrator’s Mailbox. Each recording is associated with a recording number
and assigned to the application(s) in Database Programming.
From release 6.2, you can now import audio files and use them for Audiotex applications,
including Auto Attendant (AA) and Call Routing Announcement (CRA) features. This will
improve the quality and fidelity of the recordings and allow pre-recorded, professional
recordings for auto attendant greetings and announcements.

New Features
3
Recording requirements are as follows:
• At this time, only WAV files are supported.
• Recordings must be less than 5 minutes in length.
MIVOICE 5624 WIRELESS PHONE SUPPORT
The MiVoice 5624 Wireless Phone seamlessly blends the wireless needs of the user with a
wide range of critical applications like voice messaging and integrates with fixed legacy
applications within the organization.
The MiVoice 5624 Wireless Phone is Mitel’s first VoWiFi (Voice over Wi-Fi) handset operating
on 802.11n network; it supports the deployment of voice over a Wireless LAN (WLAN) without
degrading the performance of an existing .11n network capacity. A MiVoice 5624 Wireless
Phone-based solution delivers trouble-free WLAN vendor interoperability and scalability, as
well as the capacity to integrate and communicate with a comprehensive range of external
sources.
Notes:
• MiVoice 5624 Wireless Phone is already available outside North America.
• In North America the regulatory approval and introductionis in progress with MiVoice Busi-
ness and will then also be available for MiVoice Office 250
• MiVoice 5624 Wireless Phone is Mitel’s rebranding of the earlier certified Ascom i62 and
is technically the same. (Mitel SIP Center of Excellence specifications, 14-4940-00310).
DISCONTINUATION OF SUPPORT FOR CS PLATFORM
With Release 6.2, CS platform is not supported.
OTHER ENHANCEMENTS
• Security improvements for SSL connections (Webserver, SSH) used on the system.
• Open SSH 7.1
• OpenSSL 1.0.2a
• Web services are only accessible via TLS 1.2 encryption
MORE FEATURES IN RELEASE 6.2
MOH (Music on Hold) for parked destinations
To change from Ringback to MOH for Parked Calls, two configurations are needed:
1. Change the ‘Audio for Calls Ringing at this Device’, from Ringback to Music, at the Park
Phantom(s)
2. Change the ‘Audio for Transfer to Ring’ from ‘Ringback’, to ‘Use Next Device’s Audio
Source’, at the Trunk Group.”

MiVoice Office 250 Engineering Guidelines
4
Group Pickup Enhancement
Assigning a Park/Pickup key to a Hunt Group destination is an enhancement to the existing
Group Pick-up feature, allowing Group Pick-up using a single key press, whilst also allowing
for a visual indication.
Other Enhancements
MiVoice Office 250 Release 6.2 supports Exchange 2016.
MIVOICE OFFICE 250 V6.1 SP1 NEW FEATURES
ENGINEERING GUIDELINES
The Engineering Guidelines (this document) is now a stand-alone document. It was previously
contained as an appendix in the MiVoice Office 250 Installation Manual.
MULTI-NODE VIDEO SUPPORT
MiVoice Office 250 Release 6.1 SP1 supports video calls between SIP clients connected to
different nodes. A SIP device connected to Node 1 can now make a video call to a SIP device
connected to Node 2.This is achieved by using the Peer-to-Peer (P2P) connection between
two SIP endpoints for the video calls for the endpoints connected to MiVoice Office 250.
The MiVoice Office 250 Release 6.1 SP1 supports the following features.
• Video calls between SIP clients connected to different nodes.
• Backwardcompatibility.AP2P video call from6.1SP1node to 6.1/6.0/5.1nodeismodified
to an audio call.
• SIP video devices as remote extensions via MBG.
• Video calls across the network like any other desktop device.
SIP PHONE GROUP – PASSWORD ALARM
MiVoice Office 250 Release 6.1 SP1 provides a new System Flag. This field is located in
System\Flags.
When enabled, Alarm 149 will be generated each time a SIP Phone registers with the MiVoice
Office 250, where the password used for the registration is either the same as the SIP Phone
extension number or it is left empty. The alarm is raised against the SIP phone group to which
theSIPPhonebelongs.The SIPPhone will still abletoregisterandoperate,howeverthealarm
will notify the Administrator that security needs to be reviewed immediately for this SIP Phone
Group. This alarm will be cleared automatically by the system as soon as the SIP Phone
registersagainusingnewcredentials.NotethattheAdministratorfirsthastomakethepassword
secure and cannot simply clear this alarm.

New Features
5
This feature is enabled by default. Mitel recommends that you do not disable this feature. The
Alarms Notification Feature within System Administration and Diagnostics is used to send an
email to an administrator when a System Alarm is generated.
MIVOICE OFFICE 250 RELEASE 6.1 NEW FEATURES
PRODUCT RE-BRANDING
Mitel has introduced new product naming as follows:
There-brandedinterfacesforDatabaseProgramming,SystemAdministrationandDiagnostics,
Administrator Web Portal, and the User Web Portal are updated with the new Mitel logo and
color scheme. Additionally, the re-branding includes, but is not limited to, the following other
MiVoice Office 250 interfaces:
• MiVoice Office 250 Installation Wizards
• MiVoice Office 250 Private Networking
• MiVoice Office 250 PS1 Server
NEW PS1 HARDWARE SERVER
The existing PS1 software supported hardware platform is limited to two server types the Dell
R210 and Dell R220. Both server types are capable of running the 32-bit Debian 4.0 based
distribution with the MiVoice Office 250 components.
As of May 2014, Dell retired the R210 Server and replaced it with the PowerEdge R220 Server.
MiVoice Office 250 PS1 software runs on the Dell R220 Server.
PREVIOUS NAME CURRENT NAME
Mitel 5000/5000 CP/Mitel 5000 Communications
Platform MiVoice Office 250
Mitel Database Programming MiVoice Office 250 Database Programming.
Mitel System Administration and Diagnostics MiVoice Office 250 System Administration and
Diagnostics
Mitel 5000 Administrator Web Portal MiVoice Office 250 Administrator Web Portal
Mitel 5000 User Web Portal MiVoice Office 250 User Web Portal
Mitel Attendant Console MiVoice Office 250 Attendant Console
Mitel Applications Suite (MAS) MiCollab
Mitel Unified Communicator Advanced (UCA) MiCollab Client
Mitel Border Gateway MiVoice Border Gateway
NuPoint Unified Messaging MiCollab Unified Messaging
NOTE For products related to releases prior to 6.1, naming will reference their previous,
non re-branded names.

MiVoice Office 250 Engineering Guidelines
6
MIVOICE OFFICE 250 ATTENDANT CONSOLE REFRESH
Duetoitshistoricalheritage,earlierversionsoftheAttendantConsolesupportedolderoperating
systems such as Windows 98 and old drivers for HASP keys. These drivers do not support
64-bit versions of the Microsoft Windows.
As of 2014 new drivers for the Sentinel HASP are available from SafeNet Inc., and are
compatible with a variety of 64-bit Windows versions, including Windows 7, Windows 8, and
Windows 10.
The MiVoice Office 250 Attendant Console Release 3.5 can read data from valid HASP keys
on the following Windows Operating systems:
• Windows 7 (32- and 64-bit)
• Windows 8 (32- and 64-bit)
• Windows 8.1 (32- and 64-bit)
• Windows 10 (32- and 64-bit)
DIGITAL TELEPHONE REFRESH
TheDigitalTelephonerefreshredesignstheexisting8568and8528DigitalTelephonehardware
to eliminate the potential for obsolete parts with the new redesigned Digital Telephones.
No new features are added to the refreshed seriesof Digital Telephones. To the end-user there
are no differences in the installation and operation between the refreshed Digital Telephones
and the previous versions.
The refreshed MiVoice 8568 and 8528 Digital Telephones are supported on all Mitel 5000 CP
/ MiVoice Office 250 systems that currently support these phones.
VIRTUALIZED PS1
ThePS1cannowbedeployedasavirtualappliancerunningina VMwareenvironment.Please
seetheMiVoiceOffice250InstallationManualfordetailsregardingtheinstallationandupgrade
to virtualized PS1.
VIDEO SUPPORT FOR SIP TO SIP CALLS
MiVoiceOffice250Release6.1supportsvideocapableSIPendpointsconnectedtothesystem
when one SIP endpoint tries to establish a video call or escalate an established audio call to
video.Thepeer-to-peer(P2P)functionalityenablesnewSIPPeerendpointstosendandreceive
video packets directly to another IP device. It also allows support for Mid-Call escalation of
SIP-to-SIP calls using signaling from voice calls to video.
In Database Programming, Peer-to-Peer Audio has been renamed Peer-To-Peer Media.
NOTE
Debian is a Linux distribution that is composed primarily of free and open-source
software, most of which is under the GNU General Public License, and packaged by
a group of individuals known as the Debian project. The Debian Stable distribution is
one of the most popular for personal computers and network servers, and has been
used as a base for several other Linux distributions.

New Features
7
BT CLIP CLID ENHANCEMENTS
MiVoice Office 250 Release 6.1 allows the decoding of Calling Line Identification (CLID)
information in countries which use variations of BT CLIP (British Telecom Calling Line
Identification Presentation) signaling on analog trunks.
BT CLIP supports the delivery of Caller ID information on analog trunks in the UK, and the
standard is commonly known as BT CLIP. BT CLIP is an on-hook capability that provides the
user with information about the caller before actually answering a call.
A new trunk Service Type and timer parameters are added in MiVoice Office 250 Database
Programming to support BT CLIP.
SIP ACD AGENT LOGIN
SIP endpoints - including a SIP DECT, SIP Softphone, and a Mitel Phone Manager Softphone
to login in to and logout from an ACD queue is supported.
SIPphonescanbeaddedtoaBasicorUCDHuntGroupmemberlist.Callsroutedtoaparticular
Hunt Group may be directed to a SIP phone.
For a SIP phone to use the ACD features (Log in, Log out, Wrap-Up Terminate), an OAI
application must be used in conjunction with the SIP phone. Mitel Phone Manager is the
recommended application.
The ACD feature codes cannot be dialled using a SIP phone.
MIVOICE OFFICE 250 V6.0 SP2 NEW FEATURES
DTMF DECODING PAYLOAD
SIP Peers in Database Programming can be configured with the necessary custom payload
type value, depending on the supported payload type of the far end SIP provider. In previous
releases, this value was configured in IP Settings. In Release 6.0 SP2 and up, the DTMF
Decoding Payload is now located in the individual configurations for SIP Phone Groups, SIP
Trunk Groups, and SIP Voice Mails. The payload type is typically negotiated between carriers
and devices, but in some cases the SIP serviceprovider does not accept requests. The DTMF
Payload Type is made available by the SIP trunk service provider.
Database Programming now allows the DTMF Payload type tobe selected for SIP Peers, from
a range of values that correspond to those supported by the SIP service provider.
The default DTMF Decoding Payload value applies to North American, UK, and Australian
systems.
PROPAGATION OF ORIGINAL CALLER ID TO P-ASSERTED IDENTITY
In Database Programming, a new flag, Do not use Out-bound Username in REGISTER, was
added. This flag controls the registration of a SIP call when upgrading to Release 6.0 SP2.

MiVoice Office 250 Engineering Guidelines
8
If the flag is set to No, the to/from/contact headers in the SIP register correspond to the
out-bound username. If the flag is set to Yes, the to/from/contact headers in SIP register
correspond to the trunk group Caller ID.
DO NOT USE OUT-BOUND USERNAME IN REGISTER
In Database Programming, a new flag, Do not use Out-bound Username in REGISTER, was
added. This flag controls the registration of a SIP call when upgrading to Release 6.0 SP2.
SUPPORT FOR NEW DDM16 AND DEM16 CIRCUIT BOARD REVISIONS
New hardware revisions of the DDM16 and DEM16 circuit boards are fully supported by the
Release 6.0 SP2 software.
MCD INTEROPERABILITY SUPPORT
The Mitel 5000 Release 6.0 SP2 maintains all current support with the published MCD
Interoperability.
MICROSOFT LYNC INTEGRATION SUPPORT
TheMitel5000Release6.0SP2nowhassupportforMicrosoftLyncviatheMicollab6.0product.
Refer to the MiCollab 6.0 documentation for details on this integration.
SUPPORT FOR NEW DEVICES
The Mitel 5000 Release 6.0 SP2 supports the following new devices:
• The 5610 IP Dect Phone is now supported via a Media Border Gateway connection to the
Mitwl MiVoice Office 250.
• New models of the 5320e phone have a backlit display. The Mitel 5000 v6.0 SP2 contains
new firmware for the 5320e IP phones.
• AppleIOSsupportviaaMediaBorderGatewayconnectiontotheMiVoiceOffice250.Refer
to the Media Border Gateway and IOS documentation for details.
• Mitel Phone Manager (formerly by Xarios).
UPS MONITORING SUPPORT CHANGES ON 6.0 SP2 AND LATER
SOFTWARE
Effective Release 6.0 SP2, monitoring capabilities for previously approved suppliers of UPS
unitscannotbeguaranteedto becompatible withtheUPSMonitoringfeature.SeetheMiVoice
Office 250 Installation Manual for details.
MIVOICE OFFICE 250 V6.0 SP1 NEW FEATURES
ENGINEERING GUIDLEINES
The Engineering Guidlines (this document) is now a stand-alone document. It was previously
contained as an appendix in the MiVoice Office 250 Installation Manual.

New Features
9
MID CALL FEATURES
Mid-Call Features provide a way for a mobile user to perform hold, transfer, and conferencing
features when the 5000 places a call via Dynamic Extension Express (DEE).
MBG SIP SERVICES
The MBG (Mitel Border Gateway) is a platform for the secure deployment of multiple network
connectivity services in a number of network edge scenarios. New MGB SIP features include:
• SIP device support
• UCA application support
NOTE Mid-Call Features are only supported with other networked MiVoice Office 250 nodes
running Release v6.0 SP1 and higher software.

MiVoice Office 250 Engineering Guidelines
10

Chapter 2
ENGINEERING GUIDELINES

MiVoice Office 250 Engineering Guidelines
12
INTRODUCTION
The MiVoice Office 250 is a versatile system that can be scaled to address the needs of a wide
variety of small and medium-size businesses. To achieve this flexibility, the MiVoice Office 250
offerstwooptionalpiecesofhardware,aProcessorExpansionCard(PEC-1)andaProcessing
Server (PS-1), that may or may not be recommended based on the customer’s specific
installation needs.
Starting with the v4.0 software release and its elimination of the 5200, 5400, and 5600
designation (for both the CS Controller and HX Controller platforms), it is now possible to add
a PS-1 without first having to add a PEC-1. This means that a PEC-1 and a PS-1 can be added
to a system independently of each other.
This document provides engineering guidelines and configuration recommendations on the
following topics:
• “When to Add a Processor Expansion Card“ on page 13
• “When to add a Processing Server“ on page 20
• “OAI Applications“ on page 26
• “UVM Coexisting with NuPoint UM“ on page 28
• “Determining the Correct Compact Flash-Type Card Size“ on page 29
• “Basic vs. Advanced Ad Hoc Conferencing“ on page 31
• “Mid-Call Features“ on page 40
• “System Calculator“ on page 42

Engineering Guidelines
13
WHEN TO ADD A PROCESSOR EXPANSION CARD
The MiVoice Office 250 Base Server has a built-in Processor Module that provides the system
with a limited base number of digital signal processor (DSP) resources. It is important to note
that DSP resources can be used for IP resources (e.g., VoIPs), as well as for other various
non-IP features. These DSP resources can provide the following functionality:
• Connect local IP phones to the system
• Connect remote IP phones to the system
• Connect IP trunks to the system
• Connect Unified Voice Messaging (UVM) ports to the system
• Connect SIP-based voice mail ports (e.g., NuPoint UM) to the system
• Connect IP networking trunks to the system
• T.38 Faxing
• File-Based Music-On-Hold
• Configuration Assistant
• Conference Assistant
• Dynamic Extension Express human-answer-supervision
• Caller ID receivers and transmitters
• Meet-Me Conferencing
• AdHocConferencingplusotherconferencing-relatedfeatures (Record-A-Call,AgentHelp
and Station Monitor).
• MId Call Features
For installations that require more DSP resources, adding an optional PEC-1 to the system
“additively” increases the pool of available DSP resources. Note that adding a PS-1 does not
increase the size of the pool. Also note that adding a PEC-1 to a system does not increase the
call processing power of the system (i.e., the ability to handle high call traffic).
Depending on how a system is configured and/or the actual call traffic experienced on the
system, a PEC-1 may or may not be required. The DSP resources required by a particular
installation are dependent on several factors, including:
• The quantity and types of devices
• The number of concurrent calls

MiVoice Office 250 Engineering Guidelines
14
For systems that are predominantly configured with digital telephones, a PEC-1 is not typically
required. On the other hand, systems that contain a large number of IP phones, IP trunks, IP
networking, or voice mail ports may require a PEC-1 to increase the pool of available DSP
resources.
Beginningwiththe v5.0 software release,thesystem has theabilitytoprovidebuilt-inMeet-Me
Conferencing functionality. This functionality is provided by the Processor Module and the
PEC-1 through DSP resources. The system can provide up to 40 conference ports with a
maximum conference size of 20 parties. The administrator can also configure the Ad Hoc
Conference Type setting under the System\Conference-Related Information folder in DB
Programming. This setting determines whether or not Ad Hoc Conferencing, Record-a-Call,
StationMonitor, and AgentHelpuse the AdvancedDSPresourcesorthetraditionalBasic DSP
resources. When set to Advanced, the Ad Hoc Conference features share the 40 conference
ports with the Meet-Me Conference feature, thus possibly reducing the number of available
Meet-Me Conference ports; however, the Ad Hoc Conferencing party limit also increases from
four parties to twenty parties. When set to Basic, the Ad Hoc Conferencing features share 20
portsofconferencingusingthetraditionalBasicDSPresources,andtheMeet-MeConferencing
feature has 40ports ofconferencing using the Advanced DSP resources; however, an Ad Hoc
Conference is limited to four parties.
OVERSUBSCRIPTION
Historically,PBXsprovideddedicatedswitchinghardwareandwiringforeverydevice.Although
this allowed all devices to be in use at the same time, much of the hardware was idle most of
the time. IP telephony borrows the shared resource approach of data networks to switch calls
more cost effectively. Looking back, even traditional PBXs shared things like trunks, voice mail
ports,etc.,sosharingisnothingnew.Infact,moreefficientsharingofresourcestypicallyresults
in direct cost savings. Note that a properly engineered system can be “oversubscribed” yet
never encounter contention for shared resources.
Technically, an oversubscribed system means that there are not enough resources available
for every device in the system to acquire a resource at the same time. To determine whether
or not a system is oversubscribed, we have to consider the worst-case scenario of every IP
device being on a call at the same time, as well as using other call-related features like
File-Based Music-On-Hold or T.38 Faxing. Because there are a lot of variables that go into this
calculation, determining the precise point at which a PEC-1 is required is not trivial. However,
in most scenarios, the decision can be made fairly easily.
IP phones, IP trunks, IP networking, and IP voice mail typically consume IP resources only
when they are actively on a call. Therefore, making certain that a system is not oversubscribed
may not be necessary because most sites will unlikely use or need to use all IP devices
simultaneously. However, sites that have call-critical scenarios (e.g., hospitals or call centers)
are generally not good candidates for deploying oversubscription.
Some features of the system consume DSP resources without an active call. For example, the
backgroundmusicandpagingfeaturesonanIPphoneeachuseaDSPresourcefortheduration
ofthefeature;therefore,ifthe site usesthebackgroundmusicfeatureforcompanyconference
calls or paging to a large number of IP phones, then the site might not be a good candidate for
oversubscription.
It is important to note that the system does not guarantee that 40 ports of conferencing are
always available. These ports are provided by the DSP resource pool; therefore, if the site