Mitel Interaction Recorder Alarms

The following MIR alarms appear most often on the Mitel Performance Analytics Alarms panel and the Alarm Analytics panel. Additional device alarms are possible.

Detailed MIR alarm information is available at: https://www.mitel.com/document-center/applications/contact-center/call-recording/mitel-interaction-recording-powered-by-asc.

Alarm Message	Action
The service <name> on server <IP address or server name> is not available.	Restart the recorder.
The server is not available	Check the server
The module ASC <application> for the PBX <name> is not ready for operation	Restart the recorder.
Recording Control is not connected.	Restart the recorder.
An error has occurred while backing up the database.	Restart the recorder.
The module <name> is not available. <Description.>	Restart the recorder.
The configuration is not correct. Please check the configuration parameters.	Restart the recorder.
The directories <directory list> do not exceed the preconfigured value.	Restart the recorder.
The employee <employee> has logged off from <IP_ADDRESS> in the application <application>.	Restart the recorder.
The connection to the following NTP server could not be established: <ntp_server>.	Restart the recorder.
Opening stream <stream_name> in conversation <conversation_name> for tenant <tenant_name> with participants <participants_list> has failed.	Restart the recorder.
One or several streams are missing the conversation <conversation ID>.	Restart the recorder.
Monitoring in module <ASC application> has failed for <extension>.	Restart the recorder.
Activating the recorder extensions in module <ASC application> has failed for <extension>.	Restart the recorder.
An error with code <error code> for <CTI-ID> in conversation <conversation ID> has occurred.	Restart the recorder.
Drive <name> has reached the storage capacity of <free> storage GB. The deletion process now starts to delete not archived/expanded/transferred calls.	To make more storage capacity available: • assign the tenant more storage capacity or • archive the data or • transfer data to a storage expansion.
The package <name> is invalid.	Restart the recorder.
While executing the job <job name> of job type <job type> the following error occurred. The job execution announced: <description>.	Restart the recorder.
While executing the job <job name> of job type <job type> an unknown error occurred. The job execution announced: <description>.	Restart the recorder.
Optional: Only if LDAP is used. The connection to the LDAP server could not be established. The cause is filled dynamically	Contact your IT Administrator to check which error affects the LDAP connection.
The license file is invalid.	Request a new license file. Warning: A missing license file will cause loss of data after 30 days after having received this notification.
The authentication server is not connected. You need an authentication server for key management or VM support. The system will expire in <number with unit>. The connection to the authentication server could not be established. Please check the connection data and the configuration of the firewall. The authentication server is not connected. You need an authentication server for key management or VM support.	If a dongle has been configured, check whether the dongle is connected. If licensing has been configured via a direct Internet connection to the LMS (ASC Licensing Management Service), check whether the IP address of the LMS has been connected. Restart the service DongleManConnector.
Disk Swap Space Usage threshold exceeded.	The configured disk swap space usage threshold has been exceeded. See "Threshold Configuration".
Unsupported trap event: Unknown Subject or Unsupported trap event: [name_of_trap]	An unidentified trap or issue occurred.