MiCollab Client is an application that converges Mitel communication platform call control capabilities with Dynamic Status, presence, contact management, and collaboration to simplify and enhance real-time communications.
NOTE: MiCollab Client functionality described in documentation refers to enterprise as a single company entity. In scenarios where multiple server domains are created, it is understood to be within a single company environment where multiple MiCollab Client Services or mixed PBX nodes are required to manage the solution.
Users can access MiCollab Client features from the following interfaces:
Legacy MiCollab Desktop Client 7.3
MiCollab for PC Client 8.0
MiCollab Web Portal
MiCollab for Mobile
MiCollab MAC Desktop Client
User documentation for MiCollab Client is available in the following languages:
MiCollab Client is integrated with other Mitel applications.
See the Administrator Tasks topics for basic administrator and links to task-related instructions.
See the Administrator Interface topic for a description of the UI elements in the MiCollab Client Service Administrator pages.
Note: For instructions on how to integrate the MiCollab Client database into the USP database using the MiCollab Client Integration Wizard, refer to the MiCollab Installation and Maintenance Guide.
This page includes the following sections:
Provides a button that links to the administration tabs and associated pages. Click Configure MiCollab Client Service to access.
Provides the current status for the MiCollab Client Service, and the ability to start, stop, or refresh the server. For Server Status, the name of the server is displayed along with one of the following:
The MiCollab Client client software stored on this server may be upgraded or downgraded without requiring an upgrade of the MiCollab Client.
To perform an upgrade or downgrade of a supported MiCollab Client client:
Under Applications, click MiCollab Client Service.
In the New Client Package field, click the Browse button and navigate to the MiCollab Client client package to be uploaded.
Click Upload MiCollab Client.
The list of installed MiCollab Client client software will automatically be refreshed with the updated version information.
NOTE: The MiCollab Client Service Administration page accepts only .rpm format when uploading MiCollab Client software.
The Diagnostics section of the page provides access to diagnostics tools. Click Perform Server Diagnostics to access diagnostics tools.
NOTE: Do not use the MiCollab Client Service Diagnostic tools unless you are instructed to do so by Mitel technical support personnel.
Allows you to import MiCollab Client Service data from an already backed-up file. If you have a backup file generated on a MiCollab Client Service, use this form to restore the data.
NOTE: MSL configuration information (network information, hostname, and so on) contained in the backup file will be ignored.
Importing data using this option will overwrite all MiCollab Client Service configuration information and reinitialize the MiCollab Client Service database to the values stored in the specified backup file.
To import the data file:
Under Import Data File, click Browse.
Navigate to the backed-up form file, select the file and click Open.
Click Import MiCollab Client Service Data.
Selecting the Reinitialize MiCollab Client Service Configuration, reinitializes the configuration of the MiCollab Client Service.
NOTE: Selecting this option will remove all MiCollab Client Service configuration information and reinitialize the MiCollab Client Service database.
To reinitialize MiCollab Client Service configuration:
Click Reinitialize MiCollab Client Service Configuration.
Click OK.
Rivest Cipher 4 (RC4) is a stream cipher that protects confidential data messages sent to and from secure URLs. However, RC4 has multiple vulnerabilities and the Payment Card Industry Data Security Standard (PCI DSS) recommendation is to disable it.
For MiCollab 8.1 or later, by default, RC4 is disabled. For earlier releases, RC4 is enabled by default and the administrator must disable it to be compliant with Payment Card Industry Date Security Standard (PCI DSS). Enabling or disabling this option may impact presence and ongoing chats, so change this setting outside of business hours. To change the setting:
Clear the box to disable or check the box to enable.
Click Save RC4 Setting.
NOTE: If MBG is acting as a gateway for connections from a MiCollab server, there may be a requirement to enable RC4.
Enable MiVB (MiXML/MiTai) Security Setting to support public and corporate certificate for MiXML and MiTai connections towards MiVoice Business.
Before enabling security setting, make sure prerequisites are met and take note of limitations.
NOTE: If prerequisites are not met, PBX synchronization and MiTai connection will fail.
By default, MiVB (MiXML/MiTai) setting is disabled. To enable the setting:
Check Enable MiXML MiTai Security Setting checkbox.
Click Save MiXML MiTai Security Setting.
NOTE: In public certificate, IP address is not supported. If public certificate is used, administrator must program MiVBs with MiVB FQDN in MiCollab.
NOTE: For MiVB 8.0 release, web server certificate signed by same authority needs to be installed.
NOTE: For MiVB 9.0 release, web server certificate and device certificate, signed by same authority needs to be installed.
Enable MiTAI UTF-8 Support to get UTF-8 characters in CDRs (name fields) from MiVB. Before enabling this setting, make sure all MiVBs connected to this server are running on version 9.0 or later.
By default, MiTAI UTF-8 support setting is disabled. To enable the setting:
Check MiTAI UTF-8 Support checkbox.
Click Save MiTAI UTF-8 Setting.
Click OK on the prompt to restart PBX Proxy. PBX Proxy will automatically restart in the background.
NOTE: If the configured MiVB version is not available or lower than 9.0, administrator cannot enable the MiTAI UTF-8 Support setting.
NOTE: If the MiTAI UTF-8 support setting is enabled and the administrator provisions MiVB (lower than MiVB 9.0), the server will raise a critical alarm during next PBX sync. The administrator must disable this setting or upgrade MiVB version to 9.0 or later. After the configuration is updated, clear the alarm from the event log.