Mitel MiVoice Business (MCD/3300) Requirements

Overview

The system can connect to a Mitel MiVoice Business (MCD/3300) telephone system. Follow the procedures below to provide the required information for a successful implementation.

This process needs to be completed for each MCD controller within the system - even if devices that are to be recorded are not directly connected to it. Failure to do this may result is some calls not been recorded or tagged with the correct information.

PBX System Requirements

The following Mitel MiVoice Business (MCD/3300) versions are currently supported:

Release level: 9.0
Release level: 8.0
Release level: 7.0

The following recording devices are supported:

Primary Rate Interface (PRI)
Basic Rate Interface (BRI)
Analogue
SRC (using MBG version 9.4.0.18 onwards) (See the Mitel SRC Interfaces section for details on supported handsets)

The following MCD Configurations are supported:

Single MCD Cluster with Multiple MCD controllers are supported as long as they are part of the same cluster.
The maximum number of individual controllers that can be connected to is 100.

The maximum number of devices that can be monitored (have the HCI option enabled on their Class of Server) on a single controller for ALL MiTAI applications is dependent on the specific controller hardware:

500 - AX, CX, MX & MXe base
2000 - LX & MXe

5600 - MXe Server

The limit is a combined limit for ALL applications that are connected via MiTAI not just for the Call Recorder. See the Mitel System Engineering Tool for specific limits.

Unique numbering plan across all controllers.
On MiVoice Business 9.0 and above 'CTI Application Authentication' must be Disabled (default setting).

Set up System Administration access

Access to the Mitel MiVoice Business (MCD/3300) System Administration is a requirement for installation. A User Authorization Profile with the readonlySystem Admin Policy is required.

Configure Class of Service

The Class of Service Options for each entry on the Mitel MiVoice Business (MCD/3300) needs to have the HCI options set to "Yes", for both "HCI/CTI/TAPI Call Control Allowed" and "HCI/CTI/TAPI Monitor Allowed".

This needs to be configured for every class of service entry that has devices assigned. Failure to do this may result in some calls not been recorded or tagged with the correct information.

The class of service option for each device can be found on the Station Attributes form.

Export the required forms

The system is required to know about each of the devices that are configured on the Mitel system, without this information calls may not be recorded or tagged with the correct information. To configure this information it must be exported from the Mitel system and imported.

See the Mitel MiVoice Business (MCD/3300) PBX Device Import section for details.

Extension side SRC: Set up the Mitel Border Gateway

When the system is recording via a Mitel Border Gateway (MBG) using the Secure Recording Connection (SRC) a valid certificate is required from the MBG server. Each recording server requests the certificate during the initial installation process. To be able to generate the certificate then the MBG details are required. This includes the IP address, username and password to grant access to the MBG to allow the certificates to be authorized.

See the Mitel Secure Recording Connector (SRC) section for details.

Trunk side: Document trunk configuration

When recording trunk lines the details of the PBX trunk configuration needs to be provided. The following details are required:

Bearer Location: The details of the physical cable that the line is presented on, to enable the engineer to identify this on installation. This can be the slot number and port on the PBX.
Line Type: The type of trunk line to be recorded, this can be either: ISDN30 (PRI), Basic Rate (BRI) or Analogue.
PBX Node: The PBX node number the trunk line is connected to.
Starting Trunk: The starting trunk number that is programmed onto the PBX for this line.
Ending Trunk: The ending trunk number that is programmed onto the PBX for this line.

Ongoing Maintenance

The system relies on the device information configured on the recorder and on the Mitel MiVoice Business (MCD/3300) system to be kept up to date. Without this calls may not be recorded or tagged with the correct information.

Any programming changes that are made to any of the Mitel MiVoice Business (MCD/3300) controllers that are configured on the call recorder needs to be mirrored on the recorder itself.

See the Mitel MiVoice Business (MCD/3300) PBX Device Import section for details.

SIP Peer Configuration

Any SIP peers that are configured need have the exact same name as the associated Network Element. If the SIP peer and Network Element are already configured then simply renaming either will NOT resolve the issue. The SIP peer and Network Element needs to be removed and recreated.