D. Alert Codes¶
In the course of operation, the recorder may generate a variety of alerts, which are messages about aspects of the system operation. These messages have different severity levels that range from informational messages to severe errors. You can configure how alert notification is handled, as well as other alert features.
This section describes how to configure alert notification, including where to display and email the alerts. It also provides the following information about alert messages:
Table D.1 — Alert Severity Levels: A list of alert severity levels and descriptions.
Table D.2 — Alert Messages: A list of alert messages, including the alert code, severity level, & message text.
Resolved alerts are not new alerts (and are not Info alerts). MediaWorks receives only active alerts. Active alerts are resolved by a system process (e.g., when you replace a RAID), and are established by the RequireResolution flag (system centric name). Non-active alerts are one-time alerts that are not resolved by the system and may require user intervention. Most alerts are active alerts (~30 non-active).
Level | Name | Description |
|---|---|---|
1 | Info | An informational message or notice that does not require acknowledgement. Example: Alert #8, “Recorder Startup.” |
2 | Warning | Indicates trouble. Example: Alert #6004, “Primary RAID mount failed and the recorder recovered when secondary mount succeeded.” |
3 | Error | Indicates an error that could result in possible loss of data. Example: Alert #5010, “The UPS on recorder <name> was found but is not functioning properly.” |
4 | Severe Error | Indicates a serious problem. Example: Alert #9024, “Analog input Board <name> has malfunctioned and has been disabled.” |
CODE | ALERT TEXT | SEVERITY |
|---|---|---|
0 | blank | INFO |
1 | The system has received a test alert | INFO |
2 | The system has received a test alert(Auto Resolution) | INFO |
3 | The system has received a test alert(Manual Resolution) | INFO |
5 | The recorder <~1~>, has lost the network connection | WARNING |
7 | the <~110~> archive drive has been removed or is not functioning. | ERROR |
8 | Recorder Startup | INFO |
9 | The process <~110~> has malfunctioned on recorder <~1~>. No data loss or user intervention is expected. | INFO |
10 | The process <~110~> has malfunctioned on recorder <~1~>. Secondary systems may temporarily behave unexpectedly. No data loss or user intervention is expected | ERROR |
11 | The process <~110~> has malfunctioned on recorder <~1~>. The system is attempting to recover. Recent Data may have been lost | ERROR |
14 | The recorder was not properly shut down. This can cause serious loss of data. The shutdown time was approximately <~110~>. | WARNING |
15 | Recorder Shutdown | INFO |
16 | An error occurred while shutting down the system. Current archived data may be damaged. | WARNING |
18 | The system has detected a time change on the recorder. The time has changed from <~110~> to <~111~> in the elapsed time of <~112~> seconds. This may be normal. | INFO |
21 | Recorder time is not synchronized to any configured time source. | INFO |
22 | At least one configured time source is not currently reachable. | INFO |
23 | The process <~110~> has been manually terminated | INFO |
24 | <~110~><~111~><~112~><~113~> | INFO |
25 | This is a test email sent from recorder <~1~> at facility <~2~> | INFO |
26 | The system temperature of recorder <~1~> has exceeded the normal operating range. The system temperature is <~110~> C. | ERROR |
27 | Network cable unplugged | INFO |
27 | Network cable unplugged | INFO |
28 | Unable to contact ntpd. | INFO |
50 | Initial version <~110~> installed at <~111~> | INFO |
51 | Upgrade to version <~110~> from version <~111~> completed at <~112~> | INFO |
52 | The recorder does not have a valid license key. You are currently on day <~110~> of your 7 day grace period. | WARNING |
53 | The recorder does not have a valid license key. After a 7 day grace period, certain recorder functionality will be blocked until a valid license key is entered. | ERROR |
54 | The recorder has recorded calls that are later than the current recorder time. These calls will not get archived and may cause problems when you attempt to display them. Check the system clock and time zone. Contact Eventide for further info. | INFO |
55 | A valid license key has been entered. | INFO |
56 | An Integrated Metadata feed went <~110~> minutes without providing data. | WARNING |
57 | Configured Feature Add-on “<~110~>” exceeds the capabilities licensed | WARNING |
58 | Push upgrades to previous versions are not supported. Current version is “<~110~>” and an upgrade was attempted to version “<~111~>” | WARNING |
59 | The Metadata feed for channel <~110~> appears to be missing. <~111~> calls were recorded without providing metadata. | ERROR |
60 | Local RTP Engine Config Issue: <~110~> | ERROR |
61 | Recorder running inside VMWare, but no Keylok Dongle Found or No License key allowing Virtualization installed on Recorder. | SEVERE |
62 | The system hardware is not in the configuration database. The hardware has been identified as <~110~> | ERROR |
63 | Configured Feature Add-on “<~110~>” exceeds the capabilities licensed | WARNING |
64 | The operating system detected a fault and needed to be restarted. | ERROR |
65 | Remote vocoder is not responding: host <~110~>’ | INFO |
66 | Remote vocoder encounterd an error: <~110~>’ | INFO |
67 | The Recorder is contains an expired temporary addon license key | INFO |
100 | Kernel stopped process <~110~> : <~111~> | SEVERE |
100 | Kernel stopped process <~110~> : <~111~> | SEVERE |
101 | Initialization Error for Component: <~110~> : <~111~> | ERROR |
102 | The CPU temperature of recorder <~1~> has exceeded the normal operating range. The CPU temperature is <~110~> C. | ERROR |
1002 | A database record event failed. This is likely the result of a misconfigured integration. Please contact your dealer for assistance. Type: <~111~> ,Error: <~110~><~112~><~113~> | WARNING |
1003 | Calls are being removed from the hard disk without ever having being archived. The calls currently being deleted started on <~110~> | INFO |
1004 | Space used on hard disk has reached an upper limit. Normal operation continues, with new recordings now replacing the oldest recordings on disk, starting with <~110~> | INFO |
1005 | A small amount of data may have been lost from channel <~110~> on the call that started at <~111~>. This data loss may not be noticeable. | WARNING |
1006 | Calls are not being recorded due to a recording problem. Error:<~110~> | WARNING |
1007 | Failed to read configuration from the database. A possible corruption exists. Please contact Eventide. Error:<~110~> | SEVERE |
1008 | Data inconsistent on channel <~110~>. This may have occured because of process restart or delayed read of data. Last block read was <~111~> but found <~112~>. | ERROR |
1009 | Failed to upgrade the database. The system will continue to run with an older version of the database. Please contact Eventide to resolve this issue. Error:<~110~> | WARNING |
1010 | The system has pending database activity that has been queued for more than two minutes. Recordings may not appear in real time but are being recorded. | INFO |
1011 | The system has pending database activity that has been queued for more than two hours. Recordings may not appear in real time but are being recorded. | INFO |
1012 | A processing timeout has occured while recording data. | ERROR |
1013 | Recordings that are scheduled for preservation are close to being deleted. | WARNING |
1014 | The user storage partion for <~110~> is full. This must be resolved by either deleting stored items or increasing storage settings via the Configuration Manager → Recording → Retention Settings. You will not be able to <~111~> until this is resolved. This issue does not affect recording. | WARNING |
2001 | The media in the <~111~> archive drive is almost full | INFO |
2002 | The media with id <~110~> in the <~111~> archive drive of recorder <~1~> is full | INFO |
2004 | Warning: the operation of <~110~> was performed when the drive was in a bad state. Please retry the operation | INFO |
2005 | System configuration saved to the <~110~> archive drive | INFO |
2006 | System configuration was NOT saved to the <~110~> archive drive: <~111~> | WARNING |
2006 | System configuration was NOT saved to the <~110~> archive drive: <~111~> | WARNING |
2007 | System Logs have been successfully saved to the <~110~> archive drive | INFO |
2008 | System Logs were NOT saved to the <~110~> archive drive: <~111~> | WARNING |
2009 | System configuration was restored. | INFO |
2010 | System configuration was NOT loaded from the <~110~> archive drive because of the error: <~111~> | WARNING |
2011 | Metadata backup failed for backup type <~110~>. Error: <~111~><~112~>. | WARNING |
2014 | Writing archive to the <~110~> archive drive failed. Please dismiss this message by hitting the ‘OK’ soft key, insert new media into the <~110~> archive drive and then hit the ‘resume’ soft key to retry. | INFO |
2016 | The current archive time has been changed on the recorder from <~110~> to <~111~>. | INFO |
2017 | <~110~> archive drive action: <~111~>. | INFO |
2019 | Call Meta Information saved to the <~110~> archive drive | INFO |
2020 | Call Meta Information was NOT saved to the <~110~> archive drive: <~111~> | WARNING |
2021 | Call Meta Information was loaded from the <~110~> archive drive. | INFO |
2022 | Call Meta Information was NOT loaded from the <~110~> archive drive because of the error: <~111~> | WARNING |
2024 | The <~110~> archive drive medium was improperly removed and may be damaged. The recorder will attempt to recover but some data loss is possible. In the future please use the Eject soft key and wait for the drive status to read “Safe To Remove Media”. | ERROR |
2025 | The recorder <~1~> is not archiving. | INFO |
2026 | The recorder <~1~> does not appear to be archiving properly. The recorder is recording calls, but they do not appear to be archived. This may be because of a time change on the system or other normal activity. If you believe this is a problem, please stop archiving and restart it. | WARNING |
2027 | All media on the recorder <~1~> is either full or in the wrong state to continue archiving | INFO |
2030 | The media loaded in the <~110~> archive drive is damaged. Error: <~111~> | INFO |
2031 | The media in the <~110~> archive drive with the start time of <~111~> and the end time of <~112~> has encountered a problem while saving data. The archive media may be faulty or damaged. Please insert new media and archive again. The system archive time has not been changed. | WARNING |
2032 | Archive media format failed on the <~110~> archive drive. Please check that the media is not write protected or damaged. Error: <~111~> | INFO |
2033 | A media error was encountered while loading the <~110~> archive drive to browse mode. The archive media may be damaged and have missing or incomplete calls. This error could be caused by defective media or an improper system shutdown. The archive has the start time <~111~> and end time <~112~> | INFO |
2033 | A media error was encountered while loading the <~110~> archive drive to browse mode. The archive media may be damaged and have missing or incomplete calls. This error could be caused by defective media or an improper system shutdown. The archive has the start time <~111~> and end time <~112~> | INFO |
2200 | Failsafe is not active for the recorder group <~110~>. | WARNING |
2201 | Archive Failsafe is armed for the recorder group <~110~> | INFO |
2202 | Archive Failsafe has been triggered on the recorder group <~110~> at archive position <~111~>. Error: <~112~> | WARNING |
2203 | The recorder <~1~> has been placed in standby mode for the group <~110~>. | INFO |
2204 | Archive Restore complete on the <~110~> drive of recorder <~1~> | INFO |
2300 | Network Archive connected to address <~110~>, share <~111~> | INFO |
2301 | Network Archive to address: <~110~>, share: <~111~> is NOT active. <~112~><~113~> | WARNING |
2302 | Network Archiving connection to address: <~110~>, share: <~111~> is not active. Error: <~112~><~113~> | WARNING |
2400 | Centralized Archiving is not connected to <~110~>. Error: <~111~> | ERROR |
2401 | The recorder at <~110~> is transferring duplicate calls. This may be because the archive pointer was reset. | ERROR |
2402 | The Centralized Archive source with serial number <~110~> is not connected | ERROR |
3001 | Channel <~110~> was active for more than <~111~> seconds. | INFO |
3002 | Channel <~110~> was inactive for more than <~11~> days <~12~> hours <~13~> minutes. | INFO |
5000 | Communications with the UPS backup power supply has been lost on the recorder <~1~> in facility <~2~>. Please ensure that the UPS is properly connected to the recorder | WARNING |
5002 | Power has been lost on the recorder <~1~> in the facility <~2~>. The UPS is currently providing power | WARNING |
5005 | Power has not been restored on the recorder <~1~> in the facility <~2~> and will be shut down shortly | WARNING |
5008 | The battery on UPS <~110~> has been exhausted. Recorder <~1~> is being shut down. | WARNING |
5010 | The UPS on recorder <~1~> was found but is not functioning properly | ERROR |
5013 | UPS is attached and functioning normally | INFO |
5014 | UPS is not attached to the recorder or not working properly | INFO |
5014 | UPS is not attached to the recorder or not working properly | INFO |
5015 | UPS battery is not functioning properly. Please test battery to ensure proper functionality. | INFO |
6000 | The hard disk <~110~> has failed on the recorder <~1~>. Please fix it | SEVERE |
6001 | RAID on recorder <~1~> is degraded. Replace the failed drive to correct the issue. | SEVERE |
6002 | The RAID has been changed: <~110~> | INFO |
6003 | The recorder <~1~> has a storage partition(<~110~>) that is dangerously close to being full(<~111~>). This is not a normal condition and should be resolved immediately to prevent possible data loss. | WARNING |
6004 | Primary RAID mount failed, and the recorder recovered when secondary mount succeeded. | WARNING |
6005 | The recorder <~1~> had a bad file system journal on volume group <~110~>. The problem was automatically fixed, but this condition is not normal and may have resulted in data loss. | WARNING |
6006 | The hard disk <~110~> is close to failure on <~1~>. Please replace it as soon as possible. | ERROR |
6007 | The hard disk <~110~> has timed out responding to the RAID controller on <~1~>. Please replace it as soon as possible. | ERROR |
6008 | The RAID Controller Write Cache is Disabled. | ERROR |
6009 | The RAID Controller Battery Backup for recorder <~1~> is reporting excessive heat. | ERROR |
6010 | The RAID Controller Battery Backup voltage is low. | ERROR |
6011 | The RAID Controller Battery Backup is offline and not providing backup to the RAID. | ERROR |
6012 | The RAID Controller Battery Backup is reporting a bad status. | ERROR |
6016 | RAID rebuild in progress. | INFO |
6020 | RAID on recorder <~1~> is degraded, there is a mismatch between drives defined and drives found. | SEVERE |
7000 | A problem occurred while sending email. Error <~110~>: <~111~> | INFO |
7001 | An unknown error code of <~110~> was received | INFO |
7002 | An email has been sent to <~110~><~111~> with the subject “<~112~>” | INFO |
7003 | The alert <~110~> has been acknowledged by user <~111~> | INFO |
8001 | The user <~110~> has requested a system shutdown | INFO |
8002 | The user <~110~> has been automatically logged out | INFO |
8002 | The user <~110~> has been automatically logged out | INFO |
8003 | Client login with username <~110~>, version <~111~>, client string <~112~> | INFO |
8004 | Client has logged out with username <~110~> | INFO |
8005 | Client login has failed with username <~110~> | INFO |
8006 | The system time has been changed on recorder <~1~> by user <~110~>. The old time was <~111~>. The new time is <~112~> | INFO |
8007 | Configuration change by user <~110~>: <~111~> | INFO |
8008 | Shutdown requested via key. Please wait. | INFO |
8009 | Archive Failsafe Mode Canceled by user <~110~>. | INFO |
8010 | One or more PC Workstations configured for monitoring are not responding to network requests. <~110~> | WARNING |
8011 | One or more PC Workstations has an outdated screen capture service. This may result in service instability and loss of data on <~110~> | WARNING |
9000 | The board of type <~110~> has failed on recorder <~1~>. The failed board is board number <~111~>. It has failed <~112~> times | SEVERE |
9001 | A recording board has been removed or is missing from the system | SEVERE |
9002 | Failed to open the board of type <~110~> in position <~111~>. Error: <~112~> | SEVERE |
9003 | Failed to configure the board of type <~110~> in position <~111~>. Error <~112~> | SEVERE |
9004 | DSP sync Error on the board of type <~110~> in position <~111~>. Sync error count is <~112~>. Over run count is <~113~> | WARNING |
9005 | Failed to configure port <~112~> on the board of type <~110~> in position <~111~>. Error <~113~> | SEVERE |
9006 | Signal lost on port <~112~> on the board of type <~110~> in position <~111~> | ERROR |
9007 | Frames lost on port <~112~> on the board of type <~110~> in position <~111~> | ERROR |
9008 | AIS alarm on port <~112~> on the board of type <~110~> in position <~111~> | WARNING |
9009 | Yellow alarm on port <~112~> on the board of type <~110~> in position <~111~> | WARNING |
9010 | LOSMF alarm on port <~112~> on the board of type <~110~> in position <~111~> | WARNING |
9010 | LOSMF alarm on port <~112~> on the board of type <~110~> in position <~111~> | WARNING |
9011 | LOCRC4MF alarm on port <~112~> on the board of type <~110~> in position <~111~> | WARNING |
9012 | TS16RAI alarm on port <~112~> on the board of type <~110~> in position <~111~> | WARNING |
9013 | Failed to open channel <~111~> on the board of type <~110~>. Error: <~112~> | WARNING |
9014 | Failed to configure channel <~111~> on the board of type <~110~>. Error: <~112~> | WARNING |
9016 | No signal present on channel <~111~> on the board of type <~110~>. | WARNING |
9017 | Recording could not be started on channel <~111~> on the board of type <~110~>. | WARNING |
9018 | Recording could not be stopped on channel <~111~> on the board of type <~110~>. | WARNING |
9019 | Read timeout on channel <~111~> on the board of type <~110~>. | ERROR |
9020 | Read fail on channel <~111~> on the board of type <~110~>. | ERROR |
9021 | Continuity check error on channel <~110~>. | ERROR |
9022 | The continuity number is not being updated on channel <~110~>. | SEVERE |
9023 | <~110~>(<~111~>) has not been heard from in <~112~> seconds. The recorder may not be recording. | SEVERE |
9024 | Analog Telephony Board <~110~> has malfunctioned and has been disabled | SEVERE |
9025 | Recording Interface is configured as disabled and not recording. Enable the device to begin recording | SEVERE |
9026 | One or More Digital PBX Channels are receiving a large number of line errors. Please check your wiring and phonesets | WARNING |
9100 | The recorder is experiencing a connection error with the remote gateway at address <~110~>. Error: <~111~> | ERROR |
9101 | The recorder lost the connection to the remote gateway at address <~110~>. | ERROR |
9102 | The Remote Gateway at address <~110~> contains a backlog of data that is <~111~> minutes old. The data is currently being uploaded | ERROR |
9103 | The time on the Remote Gateway at address <~110~> differs from the recorder time by <~111~> seconds. Please insure that NTP is running on the Remote Gateway and recorder | ERROR |
9104 | The screen channel with name “<~110~>”:<~111~> at address <~112~> is not connected. Error: <~113~> | ERROR |
9104 | The screen channel with name “<~110~>”:<~111~> at address <~112~> is not connected. Error: <~113~> | ERROR |
9105 | Screen Agent @<~110~>: <~111~> | WARNING |
9110 | The recorder is experiencing a connection error to the bridged recorder at address <~110~>. Error: <~111~> | ERROR |
9150 | Info from CT Gateway: <~110~> | INFO |
9151 | Error from CT Gateway: <~110~> | ERROR |
9152 | Fatal Error from CT Gateway: <~110~> | SEVERE |
9160 | Harris Connection Warning: <~110~> | INFO |
9161 | Harris Connection Error: <~110~> | ERROR |
9170 | MOTOTRBO Connection Warning: <~110~> | INFO |
9171 | MOTOTRBO Connection Error: <~110~> | ERROR |
9172 | RFSS has not acknowleged all ISSI Group Registration Requests | WARNING |
9200 | The local RTP Engine is receiving inconsistent data. <~110~> channels received inconsistent data. First channel is <~111~>, Error: <~112~> | INFO |
9201 | More simultaneous calls occurred than channels are configured. Excess calls are not being recorded. | ERROR |
9202 | More G.729 encoded calls in progress than recorder is licensed for. Excess calls are not being recorded. | ERROR |
9203 | Unable to Decrypt P25 Call with key <~110~> | ERROR |
9204 | OTAR Registration Unsuccessful: <~110~> | ERROR |
9205 | Recorder Received An Error Condition from KMF: <~110~> | WARNING |
9206 | OTAR Info: <~110~> | INFO |
9207 | TCP Connection to <~110~> failed to connect | ERROR |
9208 | Recorder has sent a certificate to the Mitel system at <~110~>. Recording can not begin until the administrator approves the certificate on the Mitel system. | ERROR |
9209 | Error: <~110~> | ERROR |
9209 | Error: <~110~> | ERROR |
9300 | AIS could not provide audio stream for transmissions. Reason is <~110~> | ERROR |
9301 | AIS Proxy has entered an error state: <~110~> | ERROR |
9302 | AIS Proxy received an error condition from AIS: <~110~> | WARNING |
9303 | AIS Proxy Info: <~110~> | INFO |
9305 | Recorder has not received Heartbeats from AIS Proxy for at least 30 seconds | ERROR |
9306 | AIS Proxy version is less than 2.7.0. Recommend upgrading. | ERROR |
9307 | AIS Proxy version does not match the authorized version - Contact your Eventide Reseller. | ERROR |
10000 | This Recorder, which is currently acting as the Cluster Master, is experiencing a failure to contact the Cluster Node at ip <~110~>. Error: <~111~> | ERROR |
10001 | This Recorder, which is currently acting as the Cluster Master, has lost its connection to the recorder at ip <~110~>. | INFO |
10002 | This Recorder is currently unable to synchronize to the cluster master at <~110~>. | INFO |