xira.irxira.ir/wp-content/uploads/2019/09/mivoice_business_9.1_mg.pdf · Contents Chapter:1...

MiVoice Business ConsoleMiVoice Business Migration Guidelines RELEASE 9.1July 2019

NoticeThe 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 commit-ment 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.

TrademarksThe trademarks, service marks, logos and graphics (collectively “Trademarks”) appearing on Mitel's Internet sites or in its publi-cations 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 additional information. For a list of the worldwide Mitel Networks Corporation registered trademarks, please refer to the website: http://www.mitel.com/trademarks.

®,™ Trademark of Mitel Networks Corporation© Copyright 2019, Mitel Networks Corporation

All rights reserved

http://www.mitel.com/trademarks

http://www.mitel.com/trademarks

Contents

Chapter: 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1What’s new . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2About the documentation set . . . . . . . . . . . . . . . . . . . . . . . . 2

Accessing product documentation . . . . . . . . . . . . . . . . . 3Contacting technical support . . . . . . . . . . . . . . . . . . . . . . . . 3Migration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Supported Software Release for Migration . . . . . . . . . . . . 5Supported platforms and minimum hardware requirements . . 5Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Devices with firmware support . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Devices with no firmware support . . . . . . . . . . . . . . . . . . . . . . . . 8

Unsupported hardware and devices . . . . . . . . . . . . . . . . 9Unsupported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Impacted programming . . . . . . . . . . . . . . . . . . . . . . .11About Server Manager and Server Console . . . . . . . . . . . .16About the EX controller . . . . . . . . . . . . . . . . . . . . . . .16

Chapter: 2 Pre-Migration Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18About the MiVoice Business Migration Tool . . . . . . . . . . . . . . . .18

Prerequisites for a pre-migration audit . . . . . . . . . . . . . . .19

Chapter: 3 Prepare your System for Migration . . . . . . . . . . . . . . . . . . . 21Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Minimum HDD/CF and RAM Requirements Not Met on a 3300 ICP Controller 21

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Before your begin . . . . . . . . . . . . . . . . . . . . . . . . . .21Upgrade HDD/CF or RAM . . . . . . . . . . . . . . . . . . . . . .22

Unsupported IP device . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Replace unsupported IP device with a supported IP device . . .25

Unsupported 5550 IP console . . . . . . . . . . . . . . . . . . . . . . . .25Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Convert 5550 IP console to MiVoice Business Console . . . . . .25

Analog device on an ASU is not supported on an EX controller . . . . . .26Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Analog device on FD PER or SX-200 Bay is not supported . . . . . . . . .26Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Migrate an analog device on to a supported ASU . . . . . . . . .26Replace an analog device with an IP or SIP device . . . . . . . .27

Loudspeaker pager not supported on an EX controller . . . . . . . . . .28Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Loudspeaker pager on an FD PER or SX-200 BAY is not supported . . . .28Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Replace a loudspeaker pager with an IP or SIP device . . . . . .28

Multi-line DNIC set on FD PER or SX-200 Bay is not supported . . . . . .29Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Convert a multi-line DNIC set to a multi-line IP phone . . . . . .29

Trunks not supported on an x86-based controller . . . . . . . . . . . . .31Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Trunk on FD PER or SX-200 Bay is not supported . . . . . . . . . . . . .31Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Replace a trunk with an embedded digital trunk . . . . . . . . .31Replace a trunk with a SIP Peer . . . . . . . . . . . . . . . . . . .32

Unsupported Digital Trunking Mitel Mezzanine Cards (MMC) . . . . . .32Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

ASU is not supported on x86 based controllers . . . . . . . . . . . . . .32Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Digital Trunking Interface (including R2 Trunk) is not supported on x-86 based con-trollers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Unsupported cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Unsupported interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Deprogramming procedures . . . . . . . . . . . . . . . . . . . . . . . . .34

Deprogramming an IP device, a 5550 IP device, an Analog de-vice, or a multi-line DNIC set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Deprogramming a loudspeaker pager . . . . . . . . . . . . . . .35Deprogramming a trunk . . . . . . . . . . . . . . . . . . . . . . .35Deprogramming a Digital Trunking Mitel Mezzanine Card . . . .35Deprogramming an Analog Service Unit (ASU) . . . . . . . . . .36Deprogramming a digital trunking interface . . . . . . . . . . . .36Deprogramming a cabinet . . . . . . . . . . . . . . . . . . . . . .37Deprogramming an interface . . . . . . . . . . . . . . . . . . . .37

Chapter: 4 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Migration guidelines for an unsupported 3300 ICP controller . . . . . .40

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Migration guidelines for a supported 3300 ICP controller . . . . . . . .44Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Migration guidelines for a MiVoice Business Virtual or MiVoice Business-ISS 46Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Chapter: 5 Post-Migration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Convert an analog device to a SIP device . . . . . . . . . . . . . . . . . .49Convert a trunk to a gateway trunk . . . . . . . . . . . . . . . . . . . . .49

Chapter: 6 Appendix A : Reverse Migration . . . . . . . . . . . . . . . . . . . . . 50Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Reverse migration for a CX II, CXi II, and an MXe III controller . . . . . .50

Reverse migration by manually flashing Bootrom over U-Boot .50Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . .50Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Reverse migration of an E2T card . . . . . . . . . . . . . . . . . .53

Reverse migration for an AX controller . . . . . . . . . . . . . . . . . . .54Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . .54Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Chapter: 7 Appendix B: Manual Migration of an AX Controller . . . . . . . . . . 59Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

1

ABOUT THIS GUIDECHAPTER 1 INTRODUCTION

dita topic title Introduction / title

body section title About this guide / title

p This guide provides guidelines for preparing and migrating your MiVoice Business system to MiVoice Business Release 9.0 or later. / p / section

section title What’s new / title

p table tgroup / table / p / section / bodyTable 1.1:Issue 0.01

Feature/Enhancement Description Location

AX Controller Support Updated the procedure for two new options;

b Migration / b and b Bootloader Upgrade

only / b options to the Migration with Media Replacement option in the MiVoice Business Migration Tool.

fm-xref Migration guidelines for a supported 3300 ICP controller / fm-xref

Added a new procedure that describes performing reverse migration of an AX controller to a pre-9.0 release.

fm-xref Reverse migration for an AX controller / fm-xref

Added a new appendix for manual migration of an AX controller.

fm-xref Appendix B: Manual Migration of an AX Controller / fm-xref

Extended firmware support Removed content related to extended firmware support

Global

2

INTENDED AUDIENCECHAPTER 1 INTRODUCTION

topic title Intended audience / title

body p This guide is intended for technicians who plan, install, and configure MiVoice Business software on a 3300 ICP controller, an EX controller, an Industry Standard Server (ISS), or as a software blade on a Virtual Appliance created with VMware or Hyper-V. / p / body / topic

topic title Related Documents / title

body table tgroup / table / body / topic

topic title About the documentation set / title

body p To access the documentation pages at Mitel OnLine, go to xref https://edocs.mitel.com / xref . You must have a Mitel OnLine user name and password to

access the documents on this web site. / p

Document Title Description Location

MiVoice Business Migration Tool Help

Provides instructions to use the MiVoice Business Migration Tool to perform migration.

Available with the MiVoice Business Migration Tool. You can download the tool from the

b Downloads / b page on xref Mitel MiAccess / xref .

MiVoice Business Technician’s Handbook

Provides instructions to install, upgrade, maintain, and troubleshoot the MiVoice Business software on the supported 3300 ICP controllers and the EX controller.

xref edocs.mitel.com/ xref

MiVoice Business Installation and Administration Guide for Industry Standard Servers (ISS) and Virtual MiVoice Business.

Provides instructions to install and configure the MiVoice Business software on an Industry Standard Server (ISS), or as a software blade on a virtual appliance created with VMWare or Hyper-V.

xref edocs.mitel.com/ xref

https://connect.mitel.com/


http://edocs.mitel.com


https://edocs.mitel.com

3

CONTACTING TECHNICAL SUPPORTCHAPTER 1 INTRODUCTION

p The MiVoice Business documentation suite is available on the Communications platforms page. Information about Virtual Appliances is available on the Solution Guides & Blueprints page. / p / body

topic title Accessing product documentation / title

1. body ol li Go to ph xref http://edocs.mitel.com / xref / ph . / li

2. li p Select a documentation suite from one of the following drop-down menus: / p

– ul li p Communications Platforms / p / li

– li p Applications / p / li

– li p Solutions Guides / p / li

– li p Software Development / p / li

– li p Blueprints / p / li

– li p MiCloud / p / li

– li p End User Documents / p / li / ul / li

3. li p Log in when prompted and click ph b eDocs / b / ph . / p

note NOTE: p For Technical Bulletins (TB) and Release Notes (RNs), click ph b Knowledge Base / b / ph in the ph b Other Resources / b / ph

window in the navigation pane. / p / note / li

4. li p To access IP Phone documentation, select ph b PDF Guides / b / ph from the ph b End User Documents / b / ph drop-down menu at the top of the page. / p / li

5. li p To view a document, click the document title. / p / li

6. li p To download a document, right-click the document title, and click ph b Save Target As / b / ph . / p / li / ol / body / topic / topic

topic title Contacting technical support / title

body p Contact your local Mitel dealer for technical assistance. If you are unable to find a solu-tion, have the following information ready when you call: / p

• ul li p the product serial number / p / li

• li p the nature of the problem / p / li

• li p what you were doing with the application when the problem occurred / p / li


4

MIGRATION OVERVIEWCHAPTER 1 INTRODUCTION

• li p troubleshooting results / p / li / ul

p For information about contacting Mitel Technical Support: / p

1. ol li p Go to ph Mitel MiAccess / ph , and in the left navigation pane, click ph b InfoChannel / b / ph . / p / li

2. li p In the ph b Select Infochannel / b / ph drop-down, click ph b Mitel - Worldwide / b / ph . / p / li

3. li p In the left navigation pane, click ph b Services and Support > Technical Support / b / ph . / p / li

4. li p Under ph b Technical Support / b / ph , click ph b Contacting Mitel Technical Support / b / ph . / p / li / ol / body / topic

topic title Migration overview / title

body p MiVoice Business Release 9.0 introduces architectural changes to the MiVoice Business system, including replacement of the VxWorks operating system with Wind River Linux (WRL) and intro-duction of Server Manager (see ph fm-xref / fm-xref ) / ph for 3300 ICP controllers. Due to these changes, certain 3300 ICP platforms, devices, and interfaces are not supported (see

ph fm-xref Unsupported hardware and devices / fm-xref ) / ph , and programming of several forms (see ph fm-xref Impacted programming / fm-xref ) / ph in the MiVoice Business System Administration Tool have been impacted. As a result, to upgrade your MiVoice Business system to MiVoice Business Release 9.0 or later, you must perform a ph b Migration / b / ph , which involves: / p

1. ol li p Performing a pre-migration audit on your MiVoice Business system’s database to generate a pre-migration audit report that outlines unsupported hardware and invalid system pro-gramming in your system’s database, and provides available actions you must take to make your system’s database compatible with MiVoice Business Release 9.0 or later. See ph fm-xref Pre-Migration Audit / fm-xref / ph . / p / li

2. li Implementing the actions suggested in the pre-migration audit report on your MiVoice Busi-ness system’s database. After you implement the actions, your MiVoice Business system database will be compatible with MiVoice Business Release 9.0 or later. See ph fm-xref Prepare your system for migration / fm-xref . / ph / li

3. li p Performing a migration to MiVoice Business Release 9.0 or later and restoring a compatible database. See ph fm-xref Migration / fm-xref . / ph / p / li

5


4. li p Performing post migration tasks depending on the target platform to which you have migrated. See ph fm-xref Post-migration tasks / fm-xref . / ph / p / li / ol / body

topic title Supported Software Release for Migration / title

body p You can migrate to MiVoice Business Release 9.0 or later from Mitel Communications Director Release (MCD) 6.0 SP3 or a later release. / p

note NOTE: p If your MiVoice Business system release is older than MCD 6.0 SP3, upgrade your system to a supported software release. / p / note / body / topic

topic title Supported platforms and minimum hardware require-ments / title

body p The following table lists: / p

• ul li p The supported platforms in MiVoice Business Release 9.0 or later and the minimum hardware requirements / p / li

• li p The unsupported platforms and the recommended replacement / ptable tgroup / table / li

Platform Supported

p Minimum / p

p RAM/ p

Minimum HDD

p Supported / pp replace

ment / p Recommended

replacement

AX sup 3

/ sup

Yes 512 MB 16 GB Compact Flash in Compact Flash slot 2

NA NA

CX sup 2

/ sup

No NA NA CX II, MXe III, EX

EX sup 1

/ sup

CXi sup 2

/ sup

No NA NA CXi II, EX EX

CX II Yes 1 GB 16 GB NA NA

6


CXi II Yes 1 GB 16 GB NA NA

LX No NA NA MXe III, EX EX

MXe No NA NA MXe III, EX EX

MXe II sup 2

/ sup

No NA NA MXe III, EX EX

MXe III Yes 1 GB 60 GB NA NA

MXe Server No NA NA MiVoice Business Virtual

NA

Stratus No NA NA MiVoice Business Virtual

NA

MiVoice Business Virtual

Yes NA NA NA NA

MiVoice Business for ISS

Yes NA NA NA NA

Multi-instance Communications Director

Not until MiVoice Business Release 9.1

NA NA NA NA

MiVoice Business - Express

Not until MiVoice Business Release 9.1

NA NA NA NA

Platform Supported

p Minimum / p

p RAM/ p

Minimum HDD

p Supported / pp replace

ment / p Recommended

replacement

7


• li p sup ph 1 / ph / sup EX is a new controller introduced in MiVoice Business Release 9.0. For more information, see ph fm-xref About the EX controller / fm-xref . / ph / p / li

• li p sup ph 2 / ph / sup For CX, CXi, and MXe II controllers with PRI MiVoice Call Recording (MiVCR) recording, you must migrate to CX II, CXi II, and MXe III controllers respec-tively. If you migrate to an EX controller, then MiVCR Line Side recording is recom-mended. / p / li

• li sup ph 3 / ph / sup The AX controller support was discontinued in MiVoice Busi-ness Release 9.0. The support is continued from MiVoice Business Release 9.1 or later. / li / ul / body / topic

topic title Supported devices / title

body section title Devices with firmware support / title / section

p The following lists the devices that you can migrate to MiVoice Business Release 9.0 or later, with its firmware support provided either through the MiVoice Business 9.0 software or an alternate source. / p

• ul li p 5010 IP phone / p / li

• li p 5020 IP phone / p / li



• li p 5215 IP phone Dual Mode / p / li


• li p 5220 IP phone Dual Mode / p / li






• li p 5320e IP phone / p / li





8




• li p 5485 IP Pager / p / li

• li p 5505 SIP phone / p / li

• li p 5540 IP Console / p / li

• li p 5560 IPT / p / li





• li p 5624 Wifi Phone / p / li

• li p 612 SIP-DECT / p / li







• li p Citel Link 1 / p / li

• li p Citel Link 2 / p / li

• li p Generic SIP phone / p / li

• li p MiVoice Business Console / p / li

• li p Navigator / p / li

• li p Netvision IP / p / li

• li p OpenPhone 26/27 / p / li

• li p Spectralink (wireless) / p / li / ul / body

topic title Devices with no firmware support / title

body p The following lists the devices that you can migrate to MiVoice Business Release 9.0 or later, but its firmware is ph b not / b / ph included in the MiVoice Business 9.0 software. These devices can connect to the MiVoice Business system only if the device has its firmware or if the firmware is provided through a server: / p

• ul li p 5001 / p / li

9


• li 5005 / li

• li p 5140 / p / li

• li p 5201 / p / li

• li 5205 / li

• li 5207 / li

• li 5230 / li

• li p 5302 IP phone (SIP support only) / p / li / ul

note NOTE: p Mitel reserves the right to ph b not / b / ph fix specific issues related to the following devices in MiVoice Business Release 9.0 or later:

• ul li 5001 IP phone / li

• li 5005 IP phone / li








• li 5215 IP phone Dual Mode / li


• li 5220 IP phone Dual Mode / li





• li 5240 IP phone / li / ul / p / note / body / topic / topic

topic title Unsupported hardware and devices / title

body section title Unsupported hardware / title / section

p The following lists the unsupported hardware in MiVoice Business Release 9.0 or later. / p

• ul li p Analog Service Unit (ASU) if migrating to an x86-based system or an EX controller / p / li

10


• li p Digital Service Unit (DSU) / p / li

• li p Dual Fiber Interface Module (FIM) / p / li

• li p Digital Trunking Mitel Mezzanine Cards (MMC) if migrating to an x86-based system or an EX controller / p / li

• li p FD PER / p / li

• li p Network Service Unit (NSU) / p / li

• li p SX-200 Bay / p / li / ul

p The following lists the unsupported devices in MiVoice Business Release 9.0 or later. / p

• ul li p Analog devices on an unsupported hardware / p / li

• li p Analog trunks on unsupported hardware / p / li

• li p Cards on unsupported hardware / p / li

• li p Digital Network Interface Card (DNIC) sets on an unsupported hardware / p / li

• li p Digital trunks on unsupported hardware / p / li

• li p DNIC console: / p

– p ul li SuperConsole 1000 / li / ul / p / li

• li p IP devices: / p

– p ul li 5410 IP phone / li

– li 5550 IP Console / li

– li 6600 Your Assistant Pro / li

– li 6600 Your Assistant Pro / li

– li 6600 Your Assistant Pro / li / ul / p / li

• li p Loudspeaker pagers on unsupported hardware / p / li

• li p Multi-line DNIC sets on unsupported hardware: / p

– p ul li Superset 410 / li

– li Superset 420 / li





– li Superset 4150 / li / ul / p / li

• li p Single line DNIC sets on unsupported hardware: / p

– p ul li Superset 401 / li

11



– li DNIC Music on Hold/Pager Unit (DMP) / li / ul / p / li / ul / body / topic

topic title Impacted programming / title

body p The following table lists the programming that is impacted due to migration to MiVoice Business Release 9.0 or later. / p

table tgroup / table / body / topic

Form Impact

Date and Time The form is discontinued in the MiVoice Business System Administration Tool and the functionality is moved to

ph b Configuration > Date and Time / b / ph in Server Manager.

DHCP IP Address Range p The form is discontinued in the MiVoice Business System Administration Tool and / p

p the functionality is moved to ph b IP Range Table / b / ph in the ph b Subnets / b / ph tab, in ph b Configuration > DHCP / b / ph in Server Manager. / p

p Other fields are ignored. / p

DHCP Lease Viewer p The form is discontinued in the MiVoice Business System Administration Tool and / p

p the functionality is moved to the ph b Lease View / b / ph tab in ph b Configuration > DHCP / b / ph in Server Manager. / p

DHCP Server The form is discontinued in the MiVoice Business System Administration Tool and the functionality is moved to the

ph b Enable DHCP Service / b / ph field in the ph b DHCP Service / b / ph tab, in ph b Configuration > DHCP / b / ph in Server

Manager.

12


DHCP Static IP p The form is discontinued in the MiVoice Business System Administration Tool and the functionality is moved to the

ph b Static Hosts / b / ph tab in ph b Configuration > DHCP / b / ph in Server

Manager. / pp The ph b Protocol / b / ph field is not moved

to Server Manager. Only MAC address is supported for hardware address. / p

DHCP Subnet The form is discontinued in the MiVoice Business System Administration Tool and the functionality is moved to

ph b Subnet List / b / ph in the ph b Subnets / b / ph tab, in ph b Configuration > DHCP / b / ph in Server

Manager.

DHCP Options p The form is discontinued in the MiVoice Business System Administration Tool and the functionality is moved to the

ph b Options / b / ph tab in ph b Configuration > DHCP / b / ph in Server

Manager. / pp Any legacy Mitel option is migrated to DHCP option 125. The

options 78-79, 116-117, and 199-121 are not migrated. / pp The option 67 is used for providing bootfile name to DHCP

clients associated with E2T cards in earlier releases. This option is migrated (if programmed) but ignored in MiVoice Business Release 9.0. You can optionally delete the programming of this option in the Server Manager. / p

Form Impact

13


SNMP Configuration p The form is discontinued in the MiVoice Business System Administration Tool and the functionality is moved to

ph b Configuration > SNMP / b / ph in Server Manager. / p

p Refer to the following table for fields mapping: / p

b Field in the SNMP Configuration Form / b

b Field in Configuration > SNMP in Server Manager / b

Enable SNMP Agent SNMP service status

Contact System contact address

Location System location

Read Only Community SNMPv2c community string for read-only access

Read/Write Community SNMPv2c community string for read-write access

Accept Requests From All Managers

p Yes / pp / pp No (and the Accept

Requests from the following Managers table has entries) / p

p / pp No (and the Accept

Requests from the following Managers table is empty) / p

SNMPv2c network access setting

p All configured trusted network / p

p / pp / p

All configured trusted networkp / pp / p

Localhost only


Form Impact

14


SNMP Trap Forwarding p The form is discontinued in the MiVoice Business System Administration Tool. / p

p If the ph b ER Notification / b / ph field for an entry is enabled, then the corresponding values are migrated to the ph b Shared System Options / b / ph form. Refer to the following table for fields mapping: / p

b Field in the SNMP Trap Forwarding Form / b

b Field in the Shared System Option Form / b

ER Notification Enable ER TRAPS

IP Address Trap host or address for ER Notification

Trap Community TRAP Community String

p The entries which has ph b ER Notification / b / ph field is disabled, are migrated to

ph b Configuration > SNMP / b / ph in Server Manager. / p

b Field in the SNMP Trap Forwarding Form / b

b Field in Configuration > SNMP in Server Manager / b

IP Address Trap host or address

note NOTE: p Entries are migrated separately by a comma / p / note

Trap Community SNMP v2c Trap community string

note NOTE: p Only the first b Trap Commu-nity / b string is migrated. / p / note


Form Impact

15


System IP Properties p The form is continued in the MiVoice Business System Administration Tool with the following changes: / p

p The ph b Host Name / b / ph , ph b System IP Address / b / ph , and ph b Gateway IP Address / b / ph fields are

read-only, and must be specified from Server Console. The ph b Domain Name Service (DNS) / b / ph section is

removed. / pp Refer to the following table for fields mapping: / p

b Field in the System IP Properties Form / b

b Field in Configuration > Review Configuration in Server Manager / b

Domain Name Primary domain (For all 3300 ICP Controllers)

Primary DNS Server Primary DNS Server

Secondary DNS Server Secondary DNS Server

p Other fields are retained in the ph b System IP Properties / b / ph form. / p

Form Impact

16


topic title About Server Manager and Server Console / title

body p The MiVoice Business Release 9.0 introduces Server Manager and Server Console to 3300 ICP controllers that you can use to perform certain platform and security related configuration, including server administration tasks. For more information, see ph b Server Manager / b / ph and ph b Server Console / b / ph in the ph i MiVoice Business System Administration Tool / i / ph , Release 9.0. / p / body / topic

topic title About the EX controller / title

body p The MiVoice Business Release 9.0 introduces a new controller EX. The EX controller runs a Virtual MiVoice Business instance inside Kernel-based Virtual Machine (KVM). For technical spec-ifications, see the ph i Hardware Technical Reference Manual / i / ph document. For

Web Server Certificate p The form is discontinued in the MiVoice Business System Administration Tool and the functionality is moved to

ph b Security > Web Server / b / ph in Server Manager. / p

p In MiVoice Business Release 9.0, the web server certificate is migrated to Server Manager as third-party certificate. / p

p If the third-party certificate expires, then you can: / pp • ph / ph use your enterprise certificate / pp • ph / ph use a certificate obtained from a Certificate

Authority / pp • ph / ph un-install the third-party certificate using

Server Manager. See the ph b Uninstall a Let’s Encrypt SSL Certificate / b / ph section in the ph b Manage Third-Party Certificates from Let's Encrypt / b / ph topic under ph Security > Web Server / ph in the ph Server Manager Help / ph . / p

p • ph / ph use a third-Party certificate from an alternate certificate authority. See ph b Third Party Certificates / b / ph under ph b Security > Web Server / b / ph in the ph Server Manager Help / ph . / p

Form Impact

17


installation instructions, see the ph i MiVoice Business Technician's Handbook / i / ph document. / p / body / topic / topic / topic / dita

18

OVERVIEWCHAPTER 2 PRE-MIGRATION AUDIT

dita topic title Pre-Migration Audit / title

body section title Overview / title

p To migrate your MiVoice Business system to MiVoice Business Release 9.0 or later, you must qualify your system through a pre-migration audit. You must perform a pre-migration audit on your MiVoice Business system’s database using the ph b MiVoice Business Migration Tool / b / ph . The pre-migration audit generates a pre-migration audit report that identifies unsup-ported hardware and invalid system programming in your system’s database, and provides available options you must take to make your system’s database compatible with MiVoice Business Release 9.0 or later. ph / ph / p

note NOTE:

1. ol li You can perform the pre-migration audit on any MiVoice Business system. / li

2. li It is mandatory to run the pre-migration audit for your MiVoice Business system and ensure that the database is compatible with MiVoice Business Release 9.0 or later. / li

3. li An attempt to restore an incompatible database results in a default data-base. / li / ol / note

p After you implement an option, you must rerun the pre-migration audit to ensure that your system’s database is compatible with MiVoice Business Release 9.0 or later. / p / section / body

topic title About the MiVoice Business Migration Tool / title

body p MiVoice Business Release 9.0 introduces the b MiVoice Business Migration Tool / b that helps you: / p

• p ul li Perform a pre-migration audit and generate a pre-migration audit report. / li

• li Migrate 3300 ICP controllers to MiVoice Business Release 9.0 or later. / li / ul / p

p The b MiVoice Business Migration Tool / b supports the following operations:

• ul li Pre-migration audit - This operation generates a pre-migration audit report that iden-tifies unsupported hardware and invalid system programming in your system’s database, and provides available actions you must take to make your system’s database compatible with MiVoice Business Release 9.0 or later. / li

• li Migration with media replacement: This operation migrates the bootloader on your 3300 ICP controller. After the migration, you must manually replace the drive (Hard Disk Drive (HDD) or Compact Flash (CF) on the 3300 ICP controller with a drive containing the MiVoice Business 9.0 or

19

ABOUT THE MIVOICE BUSINESS MIGRATION TOOLCHAPTER 2 PRE-MIGRATION AUDIT

later software. After replacing the drive, you can license the system and restore a compatible data-base either manually or using the tool. This operation is available only when your controller does not meet the minimum drive requirements or when you the replacement drive with the MiVoice Business 9.0 or a later software readily available. If minimum requirements of the drive are met and the RAM is insufficient, then you must upgrade the RAM and continue with the full migration oper-ation.

p This operation supports two sub-operations: / p

– ul li Migration: This operation performs the complete migration. After the bootloader migration, you must manually replace the drive with a drive containing the MiVoice Business 9.0 or a later software. After replacing the drive, the tool proceeds with licensing the system and restoring the database. / li

– li Bootloader upgrade only: This operation migrates only the bootloader on your 3300 ICP controller. After the bootloader migration, you must manually replace the drive with a drive containing the MiVoice Business 9.0 or a later software, license the system and restore the database. / li / ul / li

• li Full migration - This operation performs a full migration on your 3300 ICP controller. This oper-ation is available when your controller meets the minimum requirements of HDD/CF and the RAM. / li / ul

note NOTE: p The full migration option is not supported for an AX controller. / p / note / p

note NOTE:

1. ol li You can download the b MiVoice Business Migration Tool / b from the b Downloads / b page on xref Mitel MiAccess / xref . For PC requirements and instal-

lation instructions, see the i MiVoice Business Technician’s Handbook / i document. / li

2. li For more information on the MiVoice Business Migration Tool, see the i MiVoice Business Migration Tool Help / i available with the MiVoice Business Migration Tool. / li / ol / note / body

topic title Prerequisites for a pre-migration audit / title

body p Before you begin the pre-migration audit: / p

• ul li p Ensure that your MiVoice Business system release is MCD 6.0 SP3 or later. / p / li

• li p Ensure that you have downloaded the MiVoice Business Migration Tool. / p / li

• li p Ensure a LAN connection between the PC and MiVoice Business system. / p / li


20

ABOUT THE MIVOICE BUSINESS MIGRATION TOOLCHAPTER 2 PRE-MIGRATION AUDIT

• li p Ensure that you have configured the networking requirements on the PC running the ph MiVoice Business Migration Tool / ph to connect to the Mitel Application Management

Center (AMC) for License and Options configuration. / p / li

• li p Ensure that you have the IP address of the MiVoice Business system. / p / li

• li p Ensure that you have the login ID with ph system / ph access and password of the MiVoice Business system. / p / li

• li p Ensure that the ph b License and Option Selection / b / ph form in the MiVoice Business System Administration Tool reflects accurate license allocation. / p

note NOTE: p If the information in the ph b License and Option Selection / b / ph form is not accurate, then the MiVoice Business Migration Tool might recommend inaccurate system licenses in the pre-migration audit report, which might result in devices not being restored after the migra-tion. / p / note / li / ul / body / topic / topic / topic / dita

21

OVERVIEWCHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

dita topic title Prepare your System for Migra-tion / title


p The pre-migration audit report outlines hardware and system programming that is incompatible with MiVoice Business Release 9.0 or later, and provides a list of available options you can take to prepare your system's database for migration to MiVoice Business Release 9.0 or later. / p

p The chapter describes the available options listed in the pre-migration audit report that must be implemented to make your MiVoice Business system’s database compatible for migration to MiVoice Business Release 9.0 or later. / p

note NOTE: p Before your proceed, ensure to back up the database. In the event of an issue after migration, you might have to perform a reverse migration and restore the backed up data-base. / p / note / section / body

topic title Minimum HDD/CF and RAM Requirements Not Met on a 3300 ICP Controller / title

body section title Overview / title / section

p Your 3300 ICP controller must meet the fm-xref minimum drive or RAM require-ments / fm-xref for migration. If your controller does not meet the fm-xref minimum drive or RAM requirements / fm-xref , you must upgrade the HDD/CF and RAM. / p / body

topic title Before your begin / title

body p Ensure that you have procured the minimum HDD or RAM. See ph fm-xref Supported platforms and minimum hardware require-

ments / fm-xref . / ph / p / body / topic

22

UNSUPPORTED IP DEVICECHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

topic title Upgrade HDD/CF or RAM / title

body p To upgrade HDD or RAM on your 3300 ICP controller: / p

1. ol li p To upgrade the HDD/CF on CX II, CXi II and MXe III controllers, see ph b Chapter 7 Install and Replace Units > Hard Drives / b / ph in the ph i MiVoice Business Technician’s Handbook / i / ph document. / p

p Or, to upgrade a CF on an AX controller, see b Chapter 7 Install and Replace Units > Flash Cards / b in the ph i MiVoice Business Technician’s Handbook / i / ph docu-ment. / p / li

2. li p To upgrade the RAM, see b Chapter 7 Install and Replace Units > Memory Module / b in the ph i MiVoice Business Technician’s Handbook / i / ph docu-ment. / p / li / ol / body / topic / topic

topic title Unsupported IP device / title


p Certain IP devices are not supported in MiVoice Business Release 9.0 or later. For more informa-tion, see ph fm-xref Unsupported hardware and devices / fm-xref / ph . / p

p Before migration, do one of the following to make your MiVoice Business system’s database compatible for migration to MiVoice Business Release 9.0 or later. / p

note NOTE: p The 5020 IP, 5220 IP, and 5240 IP phones if used by applications, such as MiCollab, NuPoint, and so on, do not download the firmware, and hence no action is required for these phones. / p / note

23


table tgroup / table / body

If you want to Then perform Applicable IP Devices Supported

Replacement IP Device

Replace the unsupported IP device with a supported IP device

fm-xref Replace unsupported IP device with a supported IP device / fm-xref

p 5001 IP phone / p

p 5005 IP phone / p

p 5010 IP phone / p

p 5020 IP phone / p

p 5140 IP phone / p

p 5201 IP phone / p

p 5205 IP phone / p

p 5207 IP phone / p

p 5215 IP phone (Non-Dual Mode) / p

p 5220 IP phone (Non-Dual Mode) / p

p 5230 IP phone / p

p 5240 IP phone / p

69xx series IP phones or 53xx series IP phones

24


Deprogram the IP device

fm-xref Deprogramming an IP device, a 5550 IP device, an anlog device, or a multi-line DNIC set / fm-xref

p 5001 IP phone / p

p 5005 IP phone / p

p 5010 IP phone / p

p 5020 IP phone / p

p 5140 IP phone / p

p 5201 IP phone / p

p 5205 IP phone / p

p 5207 IP phone / p

p 5215 IP phone (Dual and Non-Dual Mode) / p

p 5220 IP phone / p

p 5230 IP phone / p

p 5240 IP phone / p

p 5401 IP phone / p

p 6600 Your Assistant Pro / p

p App Server Port / p

NA

If you want to Then perform Applicable IP Devices Supported

Replacement IP Device

25

UNSUPPORTED 5550 IP CONSOLECHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

topic title Replace unsupported IP device with a supported IP device / title

body p Before you begin, ensure that you have the replacement IP device. / p

p To replace an unsupported IP device with a supported device: / p

1. ol li p In the MiVoice Business System Administration Tool, change ph b Device Type / b / ph in the b User and Services Configuration / b form.

See b System Programming > Users > Changing a User Profile / b in the ph i MiVoice Business System Administration Tool Help / i / ph . / p / li

2. li p Install the replacement IP device. Refer to the installation instructions provided with the IP device. / p / li

3. li p Register the IP device. See b Chapter 3 Installation and programming > Register IP devices from the telephones / b in the ph i MiVoice Business Technician’s Hand-book / i / ph document. / p / li / ol / body / topic / topic

topic title Unsupported 5550 IP console / title


p The 5550 IP Console is not supported in MiVoice Business Release 9.0 or later. Before migration, do one of the following to make your MiVoice Business system’s database compatible for migration to MiVoice Business Release 9.0 or later: / p

• ul li fm-xref Convert 5550 IP console to MiVoice Business Console / fm-xref / li

• li fm-xref Deprogramming an IP device, a 5550 IP device, an Analog device, or a multi-line DNIC set / fm-xref / li / ul / body

topic title Convert 5550 IP console to MiVoice Business Console / title

body p Before you begin, ensure that the system release is MiVoice Business Release 7.0 or later. / p

p To convert the 5550 IP Console to a MiVoice Business Console: / p

• ul li p See ph i 5550 IP Console To MiVoice Business Console Transition Guide / i / ph , MiVoice Business Release 7.0. / p / li / ul / body / topic / topic

26

ANALOG DEVICE ON AN ASU IS NOT SUPPORTED ON AN EX CONTROLLERCHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

topic title Analog device on an ASU is not supported on an EX controller / title


p If you are migrating to an EX controller, analog devices programmed on an ASU are not supported. You must do one of the following to make your MiVoice Business system’s database compatible for migra-tion to MiVoice Business Release 9.0 or later: / p

• ul li p fm-xref Convert an analog device to a SIP device / fm-xref / p / li

• li p fm-xref Deprogramming an IP device, a 5550 IP device, an Analog device, or a multi-line DNIC set / fm-xref / p / li / ul / body / topic

topic title Analog device on FD PER or SX-200 Bay is not supported / title


p Analog devices programmed on FD PER or SX-200 Bay are not supported in MiVoice Business Release 9.0 or later. You must do one of the following to make your MiVoice Business system’s database compatible for migration to MiVoice Business Release 9.0 or later: / p

• ul li fm-xref Migrate an analog device on to a supported ASU / fm-xref / li

• li fm-xref Replace an analog device with an IP or SIP device / fm-xref / li

• li fm-xref Deprogramming an IP device, a 5550 IP device, an analog device, or a multi-line DNIC set / fm-xref / li / ul / body

topic title Migrate an analog device on to a supported ASU / title

body p Before you begin, ensure that you have one of the following supported ASU procured and installed: / p

• ul li p 3300 Universal ASU / p / li

• li p 3300 ASU / p / li

• li p ASU II / p / li

• li p 3300 Embedded Analog / p / li / ul

27

ANALOG DEVICE ON FD PER OR SX-200 BAY IS NOT SUPPORTEDCHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

p To migrate an analog device to a supported ASU: / p

1. ol li p Install the ASU. See b Appendix A: Hardware reference > Analog Services Unit / b in the ph i MiVoice Business Technician’s Handbook / i / ph docu-ment. / p / li

2. li p Program the ASU. See ph b Forms Reference > Forms A to C > Analog Services Units / b / ph in the ph i MiVoice Business System Administration Tool Help / i / ph . / p / li

3. li p Program a dummy analog device. See b System Programming > Devices > Programming Analog Telephones / b in the ph i MiVoice Business System Administra-tion Tool Help / i / ph . / p / li

4. li p Run the MOVE SWAP command to swap the obsolete analog device with the dummy analog set. / p / li

5. li p Delete the dummy analog set. / p / li / ol / body / topic

topic title Replace an analog device with an IP or SIP device / title

body p Before you begin, ensure that you have the replacement IP or SIP device. / p

p To replace an analog device with an IP or SIP device: / p

1. ol li p fm-xref Deprogramming an IP device, a 5550 IP device, an Analog device, or a multi-line DNIC set / fm-xref . / p / li

2. li p Install the replacement device. Refer to the installation instructions provided with the device. / p / li

3. li p Do one of the following: / p / li / ol

• ul li p Register the IP device. See b Chapter 3 Installation and programming > Register IP devices from the telephones / b in the i MiVoice Business Technician’s Hand-book / i document. / p / li

• li p Program the SIP device. See b System Programming > Devices > Programming SIP Phones / b in the ph i MiVoice Business System Administration Tool Help / i / ph . / p / li / ul / body / topic / topic

28

LOUDSPEAKER PAGER NOT SUPPORTED ON AN EX CONTROLLERCHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

topic title Loudspeaker pager not supported on an EX controller / title


p If you are migrating to an EX controller, loudspeaker pagers are not supported. You must ph / ph fm-xref Deprogramming a loudspeaker page / fm-xref ph / ph to make your

MiVoice Business system’s database compatible for migration to MiVoice Business Release 9.0 or later. / p / body / topic

topic title Loudspeaker pager on an FD PER or SX-200 BAY is not supported / title


p Loudspeaker pagers programmed on FD PER or SX-200 Bay are not supported in MiVoice Busi-ness Release 9.0 or later. You must do one of the following to make your MiVoice Business system’s database compatible for migration to MiVoice Business Release 9.0 or later: / p

• ul li fm-xref Replace a loudspeaker pager with an IP or SIP device / fm-xref / li

• li p i fm-xref Deprogramming a loudspeaker pager / fm-xref / i / p / li / ul / body

topic title Replace a loudspeaker pager with an IP or SIP device / title

body p Before you begin, ensure that you have the replacement IP or SIP device. / p

p To replace an analog device with an IP or SIP device: / p

1. ol li p i fm-xref Deprogramming a loudspeaker pager / fm-xref / i . / p / li

2. li p Install the replacement device. Refer to the installation instructions provided with the device. / p / li

3. li p Do one of the following: / p

– ul li p Register the IP device. See b Chapter 3 Installation and program-ming > Register IP devices from the telephones / b in the ph i MiVoice Busi-ness Technician’s Handbook / i / ph document. / p / li

29

MULTI-LINE DNIC SET ON FD PER OR SX-200 BAY IS NOT SUPPORTEDCHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

– li p Program the SIP device. See b System Programming > Devices > Programming SIP Phones / b in the ph i MiVoice Business System Administra-tion Tool Help / i / ph . / p / li / ul / li / ol / body / topic / topic

topic title Multi-line DNIC set on FD PER or SX-200 Bay is not supported / title


p Multi-line Digital Network Interface Card (DNIC) sets programmed on FD PER or SX-200 Bay are not supported in MiVoice Business Release 9.0 or later You must do one of the following to make your MiVoice Business system’s database compatible for migration to MiVoice Business Release 9.0 or later: / p

• ul li fm-xref Convert a multi-line DNIC set to a multi-line IP phone / fm-xref / li

• li p fm-xref Deprogramming an IP device, a 5550 IP device, an Analog device, or a multi-line DNIC set / fm-xref / p / li / ul / body

topic title Convert a multi-line DNIC set to a multi-line IP phone / title

body p You can convert a multi-line DNIC set to a supported multi-line IP phone. / p

p The following table lists the replacement IP phones for multi-line DNIC sets. / ptable tgroup / table

note NOTE: p To revert the conversion, you must delete the IP phone and reprogram the multi-line DNIC set. / p / note

p Before you begin, ensure that: / p

Multi-line DNIC Set Replacement IP phone

p • ph / ph Superset 410 / pp • ph / ph Superset 420 / pp • ph / ph Superset 430 / pp • ph / ph Superset 4015 / pp • ph / ph Superset 4025 / pp • ph / ph Superset 4125 / pp • ph / ph Superset 4150 / p

p • ph / ph 5330 IP / pp • ph / ph 5330e IP / pp • ph / ph 5340 IP / pp • ph / ph 5340e IP / pp • ph / ph 5360 IP / pp • ph / ph 6920 IP / pp • ph / ph 6930 IP / pp • ph / ph 6940 IP / p

30

MULTI-LINE DNIC SET ON FD PER OR SX-200 BAY IS NOT SUPPORTEDCHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

• ul li p The release is MiVoice Business Release 8.0 SP3. / p / li

• li p If the multi-line DNIC set is configured with an Analog Interface Module (AIM), then depro-gram the AIM. Multi-line DNIC set configured with an AIM cannot be converted to an IP phone. / p / li

• li p The lines on the multi-line DNIC set or its Programmable Key Module (PKM) are not busy. / p / li

• li p The replacement IP phone is procured. / p / li / ul

p To convert a multi-line DNIC set to an IP phone: / p

1. ol li p Change the DNIC set device type to a replacement IP phone. See b System Programming > Users > Changing a User Profile / b in the ph i MiVoice Business System Administration Help / i / ph . / p / li

2. li p If you have a PKM configured with the DNIC set, and if you are converting the DNIC set to a: / p

– ul li p 5330 IP, 5330e IP, 5340 IP, 5340e IP, or a 5360 IP phone, then you can retain the PKM, and the system automatically configures and labels the keys based on number of keys on the IP phone. / p / li

– li p 6920 IP, 6930 IP, or a 6940 IP phone, then you must change the PKM. The system automatically migrates the keys, labels, and statuses to the new PKM. / p / li / ul / li

3. li p If you have configured MiCollab with the MiVoice Business system, the system does not automatically sync the updates introduced by the conversion of multi-line DNIC to IP phone with MiCollab. You must manually perform the System Data Synchronization (SDS) sync with MiCollab to share the updates. For more information, see ph b SDS - Synchronizing Data / b / ph in the ph i MiVoice Business System Administration Tool Help / i / ph . / p / li

4. li p Install the replacement IP phone. Refer to the installation guide provided with the IP phone, and b Chapter 3 Installation and programming > Install telephones / b in the

ph i MiVoice Business Technician’s Handbook / i / ph document. / p / li

5. li p Register the IP device. See b Chapter 3 Installation and programming > Register IP devices from the telephones / b in the ph i MiVoice Business Technician’s Hand-book / i / ph document. / p / li / ol / body / topic / topic

31

TRUNKS NOT SUPPORTED ON AN X86-BASED CONTROLLERCHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

topic title Trunks not supported on an x86-based controller / title


p If you are migrating to an x86-based controller (MiVoice Business Virtual, MiVoice Business for ISS, MiVoice Business Multi-Instance, and EX controller), analog trunks programmed on Analog Main Board (AMB) and Analog Option Board (AOB), and digital trunks programmed on MMC are not supported. You must see ph / ph fm-xref Deprogramming a trunk / fm-xref ph / ph to make your MiVoice Business system’s database compatible for migration to MiVoice Business Release 9.0 or later. / p / body / topic

topic title Trunk on FD PER or SX-200 Bay is not supported / title


p Trunks (analog trunks programmed on AMB and Analog Option Board AOB, and digital trunks programmed on MMC) programmed on FD PER or SX-200 Bay are not supported in MiVoice Business Release 9.0 or later. You must do one of the following to make your MiVoice Business system’s database compatible for migration to MiVoice Business Release 9.0 or later: / p

• ul li fm-xref Convert a trunk to a gateway trunk / fm-xref / li

• li fm-xref Replace a trunk with an embedded digital trunk / fm-xref / li

• li p fm-xref Deprogramming a trunk / fm-xref / p / li / ul / body

topic title Replace a trunk with an embedded digital trunk / title

body p To replace a trunk with an embedded digital trunk: / p

1. ol li p Do one of the following. / p

– ul li p Programming Embedded MSDN/DPNSS Trunk / p / li

– li p Programming Embedded PRI/QSIG Trunk / p / li

– li p Programming Embedded T1/D4 Trunks / p

p See b System Programming > Trunks > Digital Trunks > Programming Digital Trunks / b in the ph i MiVoice Business System Administration Tool Help / i / ph . / p / li / ul / li

32

UNSUPPORTED DIGITAL TRUNKING MITEL MEZZANINE CARDS (MMC)CHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

2. li p Add the new trunk to the same trunk group as the trunk group. / p / li

3. li p Test whether the new trunk is working. / p / li

4. li p Mark the trunk as out-of-service. See ph b Forms Reference > Forms S to Z >Trunk Circuit Descriptor / b / ph in the ph i MiVoice Business System Administra-tion Tool Help / i / ph . / p / li

5. li p fm-xref Deprogramming a trunk / fm-xref / p / li / ol / body / topic

topic title Replace a trunk with a SIP Peer / title

body p To replace a trunk with a SIP Peer: / p

1. ol li p Program a SIP trunk. Do one of the following. See b System Programming > Trunks > Programming SIP Trunks / b in the ph i MiVoice Business System Administra-tion Tool Help / i / ph . / p / li

2. li p Modify the ARS route to use the SIP Peer instead of the trunk group. See ph b Forms Reference > Forms A to C > ARS Routes / b / ph in the ph i MiVoice Business System Administration Tool

Help / i / ph . / p / li / ol / body / topic / topic

topic title Unsupported Digital Trunking Mitel Mezzanine Cards (MMC) / title


p Digital Trunking Mitel Mezzanine Cards (MMC) are not supported, if you are migrating to an EX controller or if the cards are programmed on FD PER or SX-200 Bay. You must fm-xref Deprogram-ming a Digital Trunking Mitel Mezzanine Card / fm-xref to make your MiVoice Business system’s data-base compatible for migration to MiVoice Business Release 9.0 or later. / p / body / topic

topic title ASU is not supported on x86 based control-lers / title


p If you are migrating to an x86-based controller (MiVoice Business Virtual, MiVoice Business for ISS, MiVoice Business Multi-Instance, and EX controller), ASUs are not supported. You must

33

DIGITAL TRUNKING INTERFACE (INCLUDING R2 TRUNK) IS NOT SUPPORTED ON X-86 BASED CONTROLLERSCHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

ph / ph fm-xref Deprogramming an Analog Service Unit (ASU) / fm-xref ph / ph to make your MiVoice Business system’s database compatible for migration to MiVoice Business Release 9.0 or later: / p / body / topic

topic title Digital Trunking Interface (including R2 Trunk) is not supported on x-86 based controllers / title


p If you are migrating to an x86-based controller (MiVoice Business Virtual, MiVoice Business for ISS, and MiVoice Business Multi-Instance, excluding EX controller), digital trunking interfaces, including R2 trunks are not supported. You must first perform fm-xref Deprogramming a digital trunking inter-face / fm-xref to make your MiVoice Business system’s database compatible for migration to MiVoice Business Release 9.0 or later. / p / section / body / topic

topic title Unsupported cabinet / title


p Certain cabinets are not supported in MiVoice Business Release 9.0 or later. You must ph / ph fm-xref Deprogramming a cabinet / fm-xref ph / ph to make your MiVoice

Business system’s database compatible for migration to MiVoice Business Release 9.0 or later. / p / body / topic

topic title Unsupported interface / title


p Certain interfaces are not supported in MiVoice Business Release 9.0 or later. You must ph / ph fm-xref Deprogramming an interface / fm-xref ph / ph to make your MiVoice

Business system’s database compatible for migration to MiVoice Business Release 9.0 or later. / p / body / topic

34

DEPROGRAMMING PROCEDURESCHAPTER 3 PREPARE YOUR SYSTEM FOR MIGRATION

topic title Deprogramming procedures / title

body section title Deprogramming an IP device, a 5550 IP device, an Analog de-vice, or a multi-line DNIC set / title / section

p If your MiVoice Business system release is earlier than MiVoice Business 8.0 SP1, then perform the following procedure to deprogram a device: / p

1. ol li p Ensure that you have the Directory Number (DN) of the device you want to deprogram. / p / li

2. li p Log in to the System Administration Tool. / p / li

3. li p Manually delete the reference of the DN from the following forms: / p

– ul li p ACD Express Groups / p

• ul li Interflow Point Directory Number / li

• li Unavailable Answer Point Directory Number / li / ul / li

– li p Associated Directory Numbers / p / li

– li p Call Rerouting Always Alternative / p / li

– li p Cal Rerouting First Alternative / p / li

– li p Call Rerouting Second Alternative / p / li

– li p Guest Rooms / p / li

– li p Hotel Options / p

• ul li Wake-up Call – Expiration Routing / li

• li Wake-up Call – Wake-Up Directory Number / li / ul / li

– li p Intercept Handling / p / li

– li p Page Groups / p / li

– li p Remote Busy Lamps / p / li

– li p Suites / p / li

– li p System Access Points / p

• ul li Night Bell Directory Number / li

• li MNMS: Event Indication Routing Number / li

• li MNMS: Event Indication Number / li / ul / li

– li p Trunk Attributes / p / li / ul / li

4. li p Delete the DN programming from the ph b User and Services Configura-tion / b / ph form. / p / li / ol

35


p If your MiVoice Business system release is MiVoice Business 8.0 SP1 or later, then perform the following procedure to deprogram a device: / p

1. ol li p Ensure that you have the DN of the device you want to deprogram. / p / li


3. li p In the ph b Maintenance Commands / b / ph form, do either of the following: / p

– ul li p Run the b DN REF DELETE < Directory Number > / b to delete all the references of the DN from the forms in the System Administration Tool. Continue with step 4. / p / li

– li p Run the b DN DELETE < Directory Number > / b to delete all the refer-ences of the DN from the forms and the ph b User and Services Configuration / b / ph form in the System Administration Tool. / p / li / ul / li

4. li p Delete the DN programming from the ph b User and Services Configura-tion / b / ph form. / p / li / ol / body

topic title Deprogramming a loudspeaker pager / title

body p To deprogram a loudspeaker pager: / p

1. ol li p Log into the System Administration Tool. / p / li

2. li p Deprogram the loudspeaker pager in the ph b Loudspeaker Paging / b / ph form. See ph b System Programming > Devices > Programming Loudspeaker Paging (Analog) / b / ph in the ph i MiVoice Business System Adminis-tration Help / i / ph for more information on programming a loudspeaker pager. / p / li / ol / body / topic

topic title Deprogramming a trunk / title

body p To deprogram a trunk, perform the reverse of the procedure for programming a trunk. / p / body / topic

topic title Deprogramming a Digital Trunking Mitel Mezzanine Card / title

body p To deprogram an embedded digital trunking Mitel Mezzanine Card (MMC): / p

1. ol li p Log in to the System Administration Tool. / p / li

2. li p Deprogram digital trunks programmed on the MMC. To deprogram a digital trunk, perform the reverse of the procedure for programming a digital trunk. See ph b System

36


Programming > Trunks > Digital Trunks / b / ph in the ph i MiVoice Business System Administration Help / i / ph for more information on programming digital trunks. / p / li

3. li p Deprogram the MMC. To deprogram an MMC, perform the reverse of the procedure for programming an MMC. See ph b System Programming > Programming Controller Modules / b / ph in the ph i MiVoice Business System Administration Help / i / ph for more information on programming MMC. / p / li / ol / body / topic

topic title Deprogramming an Analog Service Unit (ASU) / title

body p To deprogram an ASU: / p


2. li p Depending on the ASU programmed, perform the reverse of one of the following program-ming procedures described in the ph i MiVoice Business System Administration Help / i / ph :

– ul li p b System Programming > Programming a Universal ASU / b / p / li

– li p b System Programming > Programming an ASU II / b / p / li

– li p ph b System Programming > Programming an ASU / b / ph / p / li / ul / p / li / ol / body / topic

topic title Deprogramming a digital trunking interface / title

body p To deprogram a digital trunking interface: / p


2. li p Perform the reverse of the procedure for programming a digital trunking interface. See ph b System Programming > Trunks > Digital Trunks / b / ph in the ph i MiVoice Business System Administration Help / i / ph for more information on

programming a digital trunking interface. / p / li

3. li p If you are migrating an R2 trunk to an EX controller, then continue with ph fm-xref / fm-xref . / ph / p / li / ol / body / topic

37


topic title Deprogramming a cabinet / title

body p To deprogram a cabinet: / p


2. li p Perform the reverse of the procedure for programming a cabinet. See ph b System Programming > Initial Configuration / b / ph in the ph i MiVoice Business System Administration Help / i / ph for more information on

programming a cabinet. / p / li / ol / body / topic

topic title Deprogramming an interface / title

body p You must deprogram an interface if it is programmed on an unsupported hard-ware. / p / body / topic / topic / topic / dita

38

OVERVIEWCHAPTER 4 MIGRATION

dita topic title Migration / title


p This chapter provides migration guidelines for your MiVoice Business system: / p

• ul li fm-xref Migration guidelines for an unsupported 3300 ICP controller / fm-xref / li

• li fm-xref Migration guidelines for a supported 3300 ICP controller / fm-xref / li

• li fm-xref Migration guidelines for a MiVoice Business Virtual or MiVoice Busi-ness-ISS / fm-xref / li / ul / section / body

topic title Before you begin / title

body p Before you begin migration: / p

• ul li p Ensure that your MiVoice Business system release is MCD 6.0 SP3 or later. / p / li

• li Ensure that you have downloaded the MiVoice Business Migration Tool. / li

• li p Ensure that you have run the pre-migration audit on your MiVoice Business system, implemented the actions suggested in the pre-migration audit report, and the system’s database is compatible for migration to MiVoice Business Release 9.0 or later. / p / li

• li p If you have an unsupported 3300 ICP controller, ensure that you have a replacement platform procured and installed. See the i MiVoice Business Technicians Handbook / i for more information. / p / li

• li p For CX II, CXi II, and MXe III controller, ensure that HDD requirements (see ph / ph fm-xref Supported platforms and minimum hardware requirements / fm-xref )

are met. Otherwise, procure the replacement HDD with MiVoice Business 7.2 SP2 soft-ware. / p / li

• li For an AX controller, ensure that you have the replacement 16 GB CF with MiVoice Business Release 9.1 or later software. / li

• li p If you are migrating a 3300 ICP controller, ensure that you have downloaded the MiVoice Business Release 9.0 or later software and copied the file to an external or a local reposi-tory. The software can be downloaded from the ph b Software Download Center / b / ph on ph Mitel MiAccess / ph . / p / li

39

BEFORE YOU BEGINCHAPTER 4 MIGRATION

• li p Ensure that there is a LAN connection between the PC and MiVoice Business system. / p / li

• li p Ensure that you have configured the networking requirements on the PC running the ph b MiVoice Business Migration Tool / b / ph to connect to the Mitel Application

Management Center (AMC) for License and Options configuration. / p / li

• li p Ensure that you have the IP address of the MiVoice Business system. / p / li

• li p Ensure that you have the login ID with system access and password of the MiVoice Busi-ness system. / p / li

• li p If you are migrating an expanded MXe III controller, ensure that the E2T and the RTC cards have 1 GB RAM. / p / li

• li p For CX II and CXi II controllers with 16 GB drive (SSD), ensure that the voice mail size in the compatible database does not exceed 30 hours. / p / li

• li p Ensure that the ph b Host Name / b / ph field in the ph b System IP Properties / b / ph form in the MiVoice Business System Administra-

tion Tool is not blank and has a valid entry. / p / li

• li p If you are restoring a compatible database file during the migration, ensure that the user credentials in the database file contains the same user credentials that is used in the MiVoice Business Migration Tool for connecting to the MiVoice Business system. / p / li

• li p Ensure that the ph b License and Option Selection / b / ph form in the MiVoice Business System Administration Tool reflects accurate license allocation. / p

note NOTE: p If the information in the ph b License and Option Selection / b / ph form is not accurate, then the MiVoice Business Migration Tool might recommend inaccurate system licenses in the pre-migration audit report, which might result in devices not being restored after the migration. / p / note / li

• li p Note that during the migration, your system will be out-of-service. There will be a downtime when performing the migration, unless you have a resilient system. / p / li / ul / body / topic

40

MIGRATION GUIDELINES FOR AN UNSUPPORTED 3300 ICP CONTROLLERCHAPTER 4 MIGRATION

topic title Migration guidelines for an unsupported 3300 ICP controller / title


p The following section provides guidelines for migrating a MiVoice Business system installed on an unsupported 3300 ICP controller. See ph fm-xref Supported platforms and minimum hardware requirements / fm-xref / ph for unsupported platforms and supported replacements. / p

section title Procedure / title

p table tgroup / table

Step Action Document reference

1 1. ol li Perform the pre-migration audit of your MiVoice Business system installed on the unsupported plat-form. / li

2. li Select a target plat-form for migra-tion. / li / ol

See ph b Performing a pre-migration audit / b / ph in the

ph i MiVoice Business Migration Tool Help / i / ph .

2 p Prepare your MiVoice Business system by implementing the actions suggested in the pre-migration audit report. / p

p Repeat steps 1 and 2 to ensure that the system’s database is compatible. / p

See ph fm-xref Prepare your System for Migration / fm-xref . / ph

41


3 Back up the compatible database.

See ph b Maintenance

> Procedures > Database Maintenance > Backing up a Database / b / ph in the

ph i MiVoice Business System Administration Tool Help / i / ph .


42


4 Install the MiVoice Business Release 9.0 or later software on the supported platform.

If your replacement (target) platform is a 3300 ICP controller, then see the

ph i MiVoice Business Technicians Handbook / i / ph for installing, initial set up and migration to MiVoice Business 9.0 or later.

If your replacement (target) platform is an EX controller, see

ph b Chapter 4 Software installation > Software installation on an EX controller / b / ph in the

ph i MiVoice Business Technician’s Handbook / i / ph document.

If your replacement (target) platform is MiVoice Business Virtual or MiVoice Business-ISS, see the ph i MiVoice Business Installation and Administration Guide for Industry Standard Servers (ISS) and Virtual MiVoice Business / i / ph document.


43


5 p Log in to Server Manager and activate the license for the system. / p

note NOTE: p The default password for Server Manager deployed on an EX Controller is ph pass-word / ph / p / note

See ph b ServiceLink > View ServiceLink Status / b / ph in the

ph i Server Manager Help / i / ph .

6 Log in to the MiVoice Business System Administration Tool.

See ph b Chapter 3 Installation and programming > Programming system > Log into the programming tools > Embedded system management tools / b / ph in the

ph i MiVoice Business Technician’s Handbook / i / ph documen t ph / ph .

7 Restore the compatible database.

See ph b Maintenance > Procedures > Database Maintenance > Restoring a Database / b / ph in the

ph i MiVoice Business System Administration Tool Help. / i / ph

8 If you are migrating to an EX Controller, then additional configuration is required.

See ph b Chapter 4 Software Installation > Additional Configuration / b / ph in the ph i MiVoice Business Technician’s Handbook / i / ph document . ph / ph


44

MIGRATION GUIDELINES FOR A SUPPORTED 3300 ICP CONTROLLERCHAPTER 4 MIGRATION

note NOTE: p If the migration fails or if the database in the MiVoice Business System Adminis-tration Tool is blank after the migration, you might have to perform a reverse migration as a recovery measure. See ph fm-xref Reverse Migra-tion / fm-xref . / ph / p / note / p / section / body / topic

topic title Migration guidelines for a supported 3300 ICP controller / title


p The following section provides guidelines for migrating a MiVoice Business system installed on a supported 3300 ICP controller. See ph fm-xref Supported platforms and minimum hardware requirements / fm-xref . / ph / p / section


table tgroup / table


1 1. p ol li Perform the pre-migration audit of your MiVoice Business system. / li

2. li Ensure to select the current platform as the target for migra-tion. / li / ol / p



2 p Prepare your MiVoice Business system by implementing the actions suggested in the pre-migration audit report / p



45

MIGRATION GUIDELINES FOR A SUPPORTED 3300 ICP CONTROLLERCHAPTER 4 MIGRATION

note NOTE: p If the migration fails or if the database in the MiVoice Business System Administra-tion Tool is blank after the migration, you might have to perform a reverse migration as a recovery measure. See ph fm-xref Reverse Migra-tion / fm-xref . / ph / p / note / section / body / topic

3 Back up the database. See ph b Maintenance



4 Perform migration.

note NOTE: p Ax controller supports on the

b Migration with media replacement / b option. / p / note

See ph b Performing a migration with media replacement / b / ph or

ph b Performing a full migration / b / ph in the



See ph b Chapter 3 Installation and programming > Programming system > Log into the programming tools > Embedded system management tools / b / ph in the

ph i MiVoice Business Migration Tool Help. / i / ph


46

MIGRATION GUIDELINES FOR A MIVOICE BUSINESS VIRTUAL OR MIVOICE BUSINESS-ISSCHAPTER 4 MIGRATION

topic title Migration guidelines for a MiVoice Business Virtual or MiVoice Business-ISS / title


p The following section provides guidelines for migrating a MiVoice Business Virtual or a MiVoice Business system installed on an ISS. / p


table tgroup / table / section


1 1. p ol li Perform the pre-migration audit of your MiVoice Business system. / li

2. li Ensure to select the current platform as the target for migra-tion. / li / ol / p



2 p Prepare your MiVoice Business system by implementing the actions suggested in the pre-migration audit report / p



47


3 Back up the compatible database.

See ph b Maintenance



4 Install the MiVoice Business Release 9.0 or a later software.

See the ph i MiVoice Business Installation and Administration Guide for Industry Standard Servers (ISS) and Virtual MiVoice Business / i / ph document.

5 Log in to Server Manager and activate the license for the system.

See ph b ServiceLink > View ServiceLink Status / b / ph in the



See the ph i MiVoice Business Installation and Administration Guide for Industry Standard Servers (ISS) and Virtual MiVoice Business / i / ph document.


48


note NOTE: p If the migration fails or if the database in the MiVoice Business System Administra-tion Tool is blank after the migration, you might have to perform a reverse migration as a recovery measure . See fm-xref Reverse Migra-tion / fm-xref . / p / note / body / topic / topic / dita

7 Restore the compatible database.

p See ph b Administration >

Restore / b / ph in the ph i Server Manager

Help / i / ph . / pp If you are restoring the

database from a MiVoice Business Virtual system in to an EX controller, then after the restore, access the server console, select ph b 2. Configure this server / b / ph , navigate to

ph b Select local network adapters / b / ph , and then select

ph b eth1 virtio_net - <IP address of the adapter> [eth1: UP] / b / ph . / p

8 Log in to Server Manager and reboot the system.

See ph b Administration >

Shutdown or Reboot / b / ph in the



49

OVERVIEWCHAPTER 5 POST-MIGRATION TASKS

dita topic title Post-Migration Tasks / title


p This chapter provides the post-migration tasks required for an EX controller. / p

• ul li fm-xref Convert an analog device to a SIP device / fm-xref / li

• li fm-xref Convert a trunk to a gateway trunk / fm-xref / li / ul / section / body

topic title Convert an analog device to a SIP device / title

body p During the database restore conversion of the MiVoice Business system on x86-based platforms (MiVoice Business Virtual, MiVoice Business for ISS, MiVoice Business Multi-Instance, and EX controller), all supported analog devices are migrated to generic SIP device using single line user license. For more information, see ph b System Applications > SIP > SIP Phone Support > Descrip-tion > Single Line Phone Support / b / ph in the ph i MiVoice Business System Adminis-tration Tool Help / i / ph . / p

p When the MiVoice Business 9.0 system is up and running, the administrator must associate the generic SIP devices with the appropriate ONS ports by configuring the directory number (DN) of the generic SIP device. For more information, see ph b Forms Reference > Forms D to G > Gateway Sets / b / ph in the ph i MiVoice Business System Administration Tool Help / i / ph . / p / body / topic

topic title Convert a trunk to a gateway trunk / title

body p During the database restore conversion of the MiVoice Business system on x86-based platforms (EX controller), all the analog trunk and digital trunk configurations are cleared resulting in any trunk groups that are added to be empty. As a result, the ARS Routes point to empty trunk groups. / p

p When the MiVoice Business 9.0 system is up and running, the administrator must create a SIP Peer profile for EX controller using the b Gateway Trunk Profiles / b form, and then modify the ARS routes using Trunk Groups to the use the EX SIP Peer profiles. For more information, see

ph b Forms Reference > Gateway Trunk Profiles / b / ph in the ph i MiVoice Business System Administration Tool Help / i / ph . / p

p If you are migrating an R2 trunk to an EX controller, then refer to b Chapter 25 R2 CAS Configuration / b in the i Software Configuration Guide / i at xref https://documenta-tion.media5corp.com/ / xref . / p / body / topic / topic / dita

https://documentation.media5corp.com/

https://documentation.media5corp.com/

50

OVERVIEWCHAPTER 6 APPENDIX A : REVERSE MIGRATION

dita topic title Appendix A : Reverse Migra-tion / title


p This appendix describes the procedure to reverse migrate to the pre-9.0 software release from which you migrated to MiVoice Business Release 9.0 or later. / p / section / body

topic title Reverse migration for a CX II, CXi II, and an MXe III controller / title

body section title Reverse migration by manually flashing Bootrom over U-Boot / title

p This procedure is based on U-Boot’s ability to upgrade itself and U-Boot commands to flash bootrom over U-Boot. After you successfully capture the target in the U-Boot’s command prompt, execute U-Boot command to flash in bootrom, reset the target, capture the target in the bootrom command prompt, and then modify the bootline through the ph b c / b / ph command to perform a full manual installation of the pre-9.0 software. / p

p This procedure is applicable: / p

• ul li p If the bootrom files are present in the recovery partition of the 3300 ICP controller’s HDD/SSD. / p / li

• li p Regardless of whether the MiVoice Business system is licensed or not. / p / li / ul / section / body

topic title Before you begin / title

body p You will require: / p

• ul li p A maintenance PC and a serial cable. / p / li

• li p Baud rate of your controller’s serial port. / p

note NOTE: If you do not know the baud rate for which your controller’s serial port was config-ured, try connecting the application to the controller’s serial port with different baud rates until you determine the correct baud rate. The default baud rate is b 9600 / b . The supported rates are 9600, 38400, 57600, and 115200. / note / li

51

REVERSE MIGRATION FOR A CX II, CXI II, AND AN MXE III CONTROLLERCHAPTER 6 APPENDIX A : REVERSE MIGRATION

• li p Access to the controller’s serial port (Maintenance port). / p / li

• li p Database backup file of the pre-9.0 release. / p / li

• li p ph i MiVoice Business Technician’s Handbook / i / ph document (appro-priate release). / p

note NOTE: p This procedure erases the MiVoice Business 9.0 or later content in the HDD. It is recommended to back up the database before proceeding with this proce-dure. / p / note / li / ul / body / topic

topic title Procedure / title

1. body ol li p Connect a serial cable from the controller’s serial port to the mainte-nance PC. / p / li

2. li p Open the communication application and enter the connection parameters as follows: / p

– ul li b Port / b : Select any COM port. For example, COM1. / li

– li b Bits Per Second / b : Set the baud rate to U-Boot’s baud rate. / li

– li b Data Bits / b : 8 / li

– li b Parity / b : None / li

– li b Stop Bits / b : 1 / li

– li b Flow Control / b : None / li

– li b Emulation / b : VT100 / li / ul / li

3. li p Do one of the following:

– ul li If the controller is powered off, power on the controller. / li

– li If the MiVoice Business system is already up and running, then log in to the Server Manager, and reboot the controller b (Administration > Shutdown or reboot) / b . / li / ul / p / li

4. li p In the communication application, stop the auto-boot sequence by pressing the SPACE key three or more times consecutively within seven seconds at the following message: / p

p systemoutput Press <SPACE> key 3 times within 7 seconds to stop au-

toboot / systemoutput / p

p The system displays b => / b prompt when the auto-boot sequence stops. / p / li

5. li p From the U-Boot command prompt, run the following command to reflash the VxWorks bootrom over U-Boot: / p

52


p cmdname run upd_bootrom_fromdisk / cmdname / p / li

6. li p After the bootrom is successfully flashed in, run the following command to reset the system: / p

p cmdname reset / cmdname / p / li

7. li p Stop the auto-boot sequence by pressing the SPACE key three or more times consecu-tively within seven seconds at the following message: / p

p systemoutput Press <SPACE> <SPACE><SPACE> to stop autoboot AFTER

countdown starts / systemoutput / p

p ph The system displays systemoutput [VxWorks Boot]: / systemoutput prompt. / ph / p

note NOTE: p If you have the original HDD/SSD with the pre-9.0 software, then:

a. ol li Power off the controller. / li

b. li Install the HDD/SSD. See b Chapter 6 Install and Replace Units > Disk Drives / b in the i MiVoice Business Technicians Handbook / i , pre-9.0 release. / li

c. li Power on the controller. / li

d. li Continue from step 3 in b Chapter 4 Software Installation > Install System Soft-ware Manually / b in the i MiVoice Business Technicians Handbook / i , pre-9.0 release. / li / ol / p / note / li

8. li p Type ph b c / b / ph and press ENTER to configure the bootline to perform manual installation of the pre-9.0 software, and then reboot the system. See

b Chapter 4 Software Installation > Install System Software Manually / b in the ph i MiVoice Business Technician’s Handbook / i / ph document (appropriate

release) for details. After the system reboots, and the software installation is complete, proceed with the next step. / p / li

9. li p For an MXe III Expanded controller (equipped with an E2T card), perform ph fm-xref Reverse migration of an E2T card / fm-xref . / ph Otherwise, skip this step,

and continue with the next step. / p / li


11. li p Navigate to the ph b Maintenance Commands / b / ph form, and run the ph b UPGRADEBOOTROM ALL / b / ph command. / p

p i For an MXe III Expanded controller, the system updates the bootloader on both the RTC and E2T cards. / i / p / li

53


12. li p In the ph b Maintenance Commands / b / ph form, run the ph b RESET SYSTEM / b / ph command to reset the system. / p / li

13. li p After the MiVoice Business system reboots, log in to the System Administration Tool, and verify the following: / p

– ul li p there is no ph b Bootrom / b / ph alarm. / p / li

– li p the ph b Hardware Compute Cards / b / ph form shows that the E2T card is connected. / p / li / ul / li / ol / body / topic

topic title Reverse migration of an E2T card / title

body p The following procedure requires access to the RTC card either through FTP or through its serial port. Access through FTP is available only after the RTC card boots the pre-9.0 software. / p

1. ol li p Copy ph b E2T8260 / b / ph from the i /sysro / i directory to the i /sysro/tftp / i directory in the controller. You can do this in one of the following ways: / p

– ul li p Using a file transfer application (for example, FileZilla), copy ph b E2T8260 / b / ph from the ph i /sysro / i / ph directory in the

controller to your PC, and then copy ph b E2T8260 / b / ph from your PC to the i /sysro/tftp / i directory in the controller. / p

p note NOTE: p Ensure that files are copied in the ph binary / ph mode. If you are using FileZilla, then clear the ph b Treat files without extension as ASCII file / b / ph check box in ph b Settings > Transfers > File Types / b / ph on the b Edit / b menu. / p / note / p / li

– li p Connect to the RTC card’s serial port, and run the VxWorks shell copy command: / p / li / ul

p ph cmdname cp "/sysro/E2T8260","/sys-

ro/tftp/E2T8260" / cmdname / ph / p

p ph The E2T card eventually boots itself and connects to the RTC card. / ph / p / li

2. li p Log in to the System Administration Tool, and navigate to the b Hardware Compute Cards / b form to view the details of the E2T card in the slot ID 2 and the details of the RTC card in the slot ID 1. / p / li

3. li p Verify that the E2T card is in the connected state (that is, it does not show b Not responding / b ). / p / li

54

REVERSE MIGRATION FOR AN AX CONTROLLERCHAPTER 6 APPENDIX A : REVERSE MIGRATION

4. li p Access the E2T Card shell through one of the following ways: / p

a. ol li p Using a secure telnet: Start a secure telnet session and type b telnet <IP address of the MiVoice Business system>2007 / b or b <IP address of the E2T Card>2002 / b . Log in using your MiVoice Business system user credentials. / p / li

b. li Using a serial connection: Using a communication application (for example, PuTTy), establish a serial connection by connecting a serial cable from the controller’s printer port to your maintenance PC, and run the b redirectPrinter3 / b command from the RTC Card’s shell.

note NOTE: p To enable connection between the E2T card’s serial port and the b Printer / b port, you must first connect to the RTC card’s shell through secure telnet or b Maintenance / b port. / p / note / li / ol / li

5. li In the E2T card’s shell, run the version command and verify whether the bootline parameters are correct, depending on whether you want to use static IP or DHCP. If the bootline configuration is incorrect, run the bootChange command to modify the bootline parameters. See

b Appendix B: Installation Planner > Programming E2T via Debug Cable or Secure Telnet / b in the i MiVoice Business Technician’s Handbook / i , appropriate release. / li

6. li p Continue with step 10 of the ph / ph fm-xref Reverse Migration by Manually Flashing Bootrom over U-Boot / fm-xref proce-dure. / p / li / ol / body / topic / topic

topic title Reverse migration for an AX controller / title


p This section describe the procedure to reverse migrate an AX controller. / p

note NOTE: p This procedure does not modify the contents of the 16 GB CF. You can reuse the 16 GB CF for migration as described in fm-xref Appendix B: Manual Migration of an AX Controller / fm-xref . / p / note / section

section title Before you begin / title

p You will require: / p

• ul li 2 GB/4 GB Compact Flash (CF) combo with pre-9.0 MiVoice Business software. / li

• li Knowledge of the active partition number in the 2 GB/4 GB Compact Flash combo.

55


note NOTE: p If you are using a new 2 GB/4 GB CF combo, then the active partition is 1. If you are reusing a 2 GB/4 GB CF combo removed from the controller before migration, then you must refer to the bootline parameters recorded before migration for the active partition number. If you have not recorded the bootline parameter before migration, then to determine the partition number: / p

– ul li Refer to the cmdname version / cmdname section in the i state-dump.txt / i file in the system diagnostics file generated before the migration. For example:

p cmdname version / cmdname / p

p cmdname ======= / cmdname / p

p cmdname VxWorks (for Mitel MMC-C PPC83XX F2500) version

5.5.2. / cmdname / p

p cmdname Kernel: WIND version 2.6. / cmdname / p

p cmdname Made on Dec 26 2017, 21:16:24. / cmdname / p

p cmdname Boot line: / cmdname / p

p cmdname ata=0(0,0):/partition4/RTC8260

e=10.38.72.230:ffffff00 h=10.35.5.73 g=10.38.72.1 u=ftp pw=@

tn=ax230 o=qefcc / cmdname / p / li

– li Refer to the i AppStartup / i log section in the i MSP / i log file, generated before the migration. For example:

p cmdname INFO 2019/04/11 18:02:01:170 AppStartup General

Maintenance(0 / cmdname / p

p cmdname Progress Monitor->SysServices::appStartupPart2

(10.38.72.230) / cmdname / p

p cmdname Boot Device: ata=0 / cmdname / p

p cmdname Host Name: / cmdname / p

p cmdname Target Name: ax230 / cmdname / p

p cmdname Target IP address:

10.38.72.230:ffffff00 / cmdname / p

p cmdname Host IP address: 10.35.5.73 / cmdname / p

p cmdname Gateway IP address: 10.38.72.1 / cmdname / p

p cmdname Boot File: /partition4/RTC8260 / cmdname / p

p cmdname Boot Flag: 0x0 / cmdname / p / li / ul / note / li

• li p Database backup file of the pre-9.0 release. / p / li

• li p A maintenance PC and a serial cable. / p / li

56


• li p U-Boot’s baud rate. / p

note NOTE: If you do not know the baud rate for which your controller’s serial port was config-ured, try connecting the application to the controller’s serial port with different baud rates until you determine the correct baud rate. The default baud rate is b 9600 / b . The supported baud rates are 9600, 38400, 57600, and 115200. / note / li

• li p Access to the controller’s serial port (Maintenance port). / p / li

• li p ph i MiVoice Business Technician’s Handbook / i / ph document (appro-priate release) for reference. / p / li / ul / section


1. ol li p Connect a serial cable from the controller’s serial port to the maintenance PC. / p / li

2. li p Open the communication application and enter the connection parameters as follows: / p








3. li p Do one of the following:

– ul li If the controller is powered off, power on the controller. / li

– li If the MiVoice Business system is already up and running, then log in to the Server Manager, and reboot the controller b (Administration > Shutdown or reboot) / b . / li / ul / p / li

4. li p From the communication application, stop the auto-boot sequence by pressing the SPACE key three or more times consecutively within seven seconds at the following prompt: / p

p systemoutput Press <SPACE> key 3 times within 7 seconds to stop au-

toboot / systemoutput / p

p The system displays b => / b prompt when the auto-boot sequence stops. / p / li

5. li p From the U-Boot command prompt, run the following command to reflash the VxWorks bootrom over U-Boot: / p

57


p cmdname run upd_bootrom_fromdisk / cmdname / p

p The system flashes in the VxWorks bootrom over U-Boot from a file on the 16 GB CF. / p / li

6. li After the cmdname run upd_bootrom_fromdisk / cmdname is run successfully, power off the controller, and then do the following: (For more information, refer to b Chapter 6 Install and Replace Units > Flash Cards / b in the i MiVoice Business Technician’s Hand-book / i , appropriate release)

a. ol li Remove the controller card. / li

b. li Remove the 16 GB CF from the b COMPACT FLASH 2 / b slot. / li

c. li Insert the 2 GB CF in the b COMPACT FLASH 2 / b slot. / li

d. li Insert the 4 GB CF in the b COMPACT FLASH 1 / b slot. / li

e. li Insert the controller card. / li

f. li Power on the controller. / li / ol / li

7. li p From the communication application, stop the auto-boot sequence by pressing the SPACE key three or more times consecutively within seven seconds at the following prompt: / p

p systemoutput Press <SPACE> <SPACE><SPACE> to stop autoboot AFTER

countdown starts / systemoutput / p

p ph The system displays systemoutput [VxWorks Boot]: / systemoutput prompt. / ph / p / li

8. li p Type ph b c / b / ph and press ENTER to configure the bootline. / p

– ul li If you are reusing a 2 GB/4 GB CF combo removed from the controller before migration, then:

i) ol li Modify the bootline to boot the pre-9.0 software from the active partition number determined. / li

ii) li Type cmdname @ / cmdname to boot the pre-9.0 soft-ware. / li / ol / li

– li If you are using a new 2 GB/4 GB CF combo, then:

i) ol li Modify the bootline to boot the pre-9.0 software from the active partition 1. / li

ii) li Type cmdname @ / cmdname to boot the pre-9.0 software. / li

iii) li Using the MiVoice Business Software Installer tool, upgrade the software to the required version. / li / ol

58


note NOTE: p Alternatively, you can configure the bootline to perform a full manual installation. See b Chapter 4 Software Installation > Install System Software Manually / b in the

ph i MiVoice Business Technician’s Handbook / i / ph document (appropriate release) for details. / p / note / li / ul / li / ol

/ section / body / topic / topic / dita

59

OVERVIEWCHAPTER 7 APPENDIX B: MANUAL MIGRATION OF AN AX CONTROLLER

dita topic title Appendix B: Manual Migration of an AX Controller / title


p This section describe the procedure to manually migrate (without using the MiVoice Business Migration Tool) an AX controller to MiVoice Business 9.1 or later. / p / section

section title Purpose / title

p You can use this procedure for: / p

• ul li Greenfield installations / li

• li Field replacement of the controller card / li / ul / section

section title Before you begin / title

p You will require: / p

• ul li An AX controller with pre-9.0 software (MCD 6.0 SP3 - MiVoice Business 8.0 SP3) / li

• li A 16 GB Compact Flash (CF) preloaded with MiVoice Business 9.1 or later software. / li

• li p A maintenance PC and a serial cable. / p / li

• li p U-Boot’s baud rate. / p

note NOTE: If you do not know the baud rate for which your controller’s serial port was config-ured, try connecting the application to the controller’s serial port with different baud rates until you determine the correct baud rate. The default baud rate is b 9600 / b . The recommended baud rates are 9600, 38400, 57600, and 115200. / note / li

• li p Access to the controller’s serial port (Maintenance port). / p / li / ul / section


1. ol li Connect a serial cable from the controller’s serial port to the maintenance PC. / li

2. li Open the communication application and enter the connection parameters as follows:



60

PROCEDURECHAPTER 7 APPENDIX B: MANUAL MIGRATION OF AN AX CONTROLLER






3. li Determine the active partition number (2 or 3) by accessing the controller through the Main-tenance port, as user i root / i , and then running the following command:

p cmdname version / cmdname / p

p You will observe the following system response: / p

p systemoutput VxWorks (for Mitel MMC-C PPC83XX F2500) ver-

sion5.5.2. / systemoutput / p

p systemoutput Kernel: WIND version 2.6. / systemoutput / p

p systemoutput Made on Nov 26 2018, 17:09:58. / systemoutput / p

p systemoutput Boot line: ata=0(0,0)mn24:/parti-

tion1/RTC8260 / systemoutput / p

p systemoutput e=10.211.26.78:ffffff00 b=0

h=10.211.26.201 / systemoutput / p

p systemoutput g=10.211.26.1 u=14-0-3-51 pw=mcdve tn=MN78

s=c / systemoutput / p

p systemoutput o=qefcc / systemoutput / p

p systemoutput value = 145 = 0x91 / systemoutput / p

p In the above system response, the text partition1 indicates that partition 1 is the active par-tition. / p / li

4. li Shut down the system by running the following shell command:

p cmdname appShutdown 3 / cmdname / p / li

5. li Observe the output on the serial port. When the system informs that it safe to shut down the controller, power off the controller. / li

6. li Remove the controller card. See b Chapter 7 Install and replace Units > E2T or RTC Processor / b in the i MiVoice Business Technician’s Handbook / i . / li

7. li Remove the 2 GB /4 GB CF combo. Using a marker, label the 2 GB CF with the active partition number determined in fm-xref step 3 / fm-xref . / li

61


8. li Insert the 16 GB CF in the b Compact Flash 2 / b slot. See b Chapter 7 Install and replace Units > Flash Cards (AX) / b in the i MiVoice Business Technician’s Hand-book / i . / li

9. li Insert the controller card. See b Chapter 7 Install and replace Units > Controller Card (AX) / b in the i MiVoice Business Technician’s Handbook / i . / li

10. li Power on the controller.

p The boorom boots the VxWorks development image from partition 1. / p

note NOTE: p If the active partition was set to 4, then the bootrom fails to boot. To recover, do the following: / p

a. ol li From a communication application, stop the auto-boot sequence by pressing the SPACE key three or more times consecutively within seven seconds at the following prompt:

p systemoutput Press <SPACE><SPACE><SPACE> to stop autoboot AF-

TER countdown starts / systemoutput / p / li

b. li Enter the command b c / b , and change the systemoutput file

name / systemoutput parameter to b partition1/RTC8260 / b . / li

c. li Enter b @ / b , and press Enter to boot the VxWorks development load. / li / ol / note

p The system displays the systemoutput -> / systemoutput prompt. / p / li

11. li From communication application, enter the following VxWorks shell commands:

p cmdname Upgrade_Xilinx / cmdname / p

p cmdname Upgrade_Bootrom / cmdname / p

p cmdname reboot / cmdname / p

p The U-Boot copies the VxWorks bootline parameters and automatically boots the software from partition 2, and the Server Console is displayed. / p / li

12. li (Applies only for field replacement of controller card) From a communication application, stop the auto-boot sequence by pressing the SPACE key three or more times consecutively within seven seconds, and then enter the following command:

p cmdname setenv ata_active_part n / cmdname / p

p where n is the active partition number (2 or 3) / p / li

13. li Configure the server using the Server Console. Refer to b Server Console / b in the i MiVoice Business System Administration Tool Help, 9.x / i . / li

62


14. li After the MiVoice Business system is up and running, log in to the Server Manager as user i admin / i , license the system ( b ServiceLink >

Status / b ). / li / ol / section / body / topic / dita

xira.irxira.ir/wp-content/uploads/2019/09/mivoice_business_9.1_mg.pdf · Contents Chapter:1...

Documents

Transcript of xira.irxira.ir/wp-content/uploads/2019/09/mivoice_business_9.1_mg.pdf · Contents Chapter:1...