System failures

System failures are special alarms that monitor the operation of the Octalarm alarm dialler. You can configure these alarms as required, similar to input alarms. However, you cannot change the alarm text or delays.

Recorded system failures

• Grid failure
• Internal failures
• Multiple alarms at once
• Internet error: Eth0, Eth1 and/or GSM (Eth1¹)
• Watchdog alarm²
• Alarm Unknown location²
• No one scheduled

Note: By default, the call list/service group All contacts is linked to all system failures. Change this to the desired call list/service group to ensure correct notification.

Grid failure

When the voltage drops, the alarm dialler immediately sends an alert. This alert, called grid failure, is always reported separately. After completing the current call, the alarm system reports the mains failure without mentioning any other active alarms.

Internal failures

Internal failures are faults that can impede alarm handling.

GSM module

The GSM module triggers a failure when:

• it cannot detect a connection to the Octalarm alarm dialler;
• 5 consecutive calls via GSM fail. You receive the message Mobile telephony, multiple call attempts failed;
• there is a problem with the SIM card.

SIP

A SIP failure triggers an alert when there is no connection to the server for several minutes. Possible causes include:

• firewalls;
• incorrect login details;
• the server being offline;
• 5 consecutive calls via VoIP fail. You receive the message VoIP, multiple call attempts failed.

PSTN

The PSTN connection fails when:

• the Octalarm alarm dialler does not detect line voltage for some time;
• 5 consecutive calls via PSTN fail. You receive the message Landline telephony, multiple call attempts failed.

Good to know: about the message '...., multiple call attempts failed'

1. You receive this message when 5 or more calls fail for a given communication interface (mobile telephony, VoIP, or landline telephony). This alarm ensures that the system monitors all dial-out capabilities.
   
   
2. An unaccepted or incorrectly accepted alarm also counts as a failed call attempt.
   
   
3. Please note: if the alarm call is not accepted in time and goes to voicemail, this is also considered a failed call attempt.
   
   
4. Always take action on this system failure. An interface is not working correctly.
   
   
5. To resolve this message: the counter resets to zero only after a successful call via the affected communication interface. Make a test call from Contacts using the interface that gave the error. See Contacts | Add and edit: Run test call for further explanation. When the interface works, the system displays Call successful and the alarm notification disappears.

External IO (EM-8001)

The EM-8001 (external module) is inaccessible in the event of an external IO fault. Possible causes include:

• an incorrect client ID (message: External IO multiple modules with same ID);
• loss of voltage on the module (message: External IO communication error);
• excessive noise on the bus.

Battery failure

This failure occurs when:

• the battery is removed or defective (message text: Battery failure). Check the battery connection as soon as possible by disconnecting and reconnecting it;
• the maximum battery age has been reached (message text: Maximum battery age reached). Replace the battery to resolve this. The repeat delay after accepting this alarm is 30 days.

Multiple alarms (at once)

When 6 or more alarms within a call list/service group are active simultaneously, the Octalarm alarm dialler reports this as a single alarm. You will receive the notification: Multiple alarms. There are more than 5 alarms.

Combining alarms keeps communication clear and ensures proper alarm handling.

Note: If the alarm dialler has the system failure Multiple alarms, it will not call out new alarms. Therefore, link this system failure to an urgent call list/service group. Always take immediate action by reducing the number of active alarms as quickly as possible.

Good to know: When you connect external systems via a REST API (ARA and Octalarm Link), the system increases the maximum number of active alarms for the system failure Multiple alarms from 5 to 20.

Internet error: Eth0, Eth1 and/or GSM

If a check on the interface connection (Eth0, Eth1¹, and/or GSM) fails, the system can report this as a system failure. A system failure only occurs on interfaces selected for Report as system failure. See Settings | General | Network: internet check for further explanation on configuring this system failure, internet detection, and viewing the internet status of the various interfaces.

Watchdog alarm

The REST API is protected with a Watchdog timer². If the dialler does not receive a message within the set time, it sends an alarm to the selected call list.

Alarm Unknown location

When the REST API sends an unknown alarm to the alarm dialler², the dialler reports this alarm as Unknown location to the selected call list/service group. The default is All contacts.

No one scheduled

This failure occurs when:

• there is no one in the relevant call list/service group;
• all contacts in the relevant service group are set to Absent³.

Note: To ensure smooth alarm processing, always include enough contacts in a call list/service group.

The alarm dialler reports the system failure No one scheduled to the call list/service group Administrators.

Note: You must add contacts with the role Administrator to the alarm dialler and enter their phone numbers.

1. NOT applicable to Touch. ↩ ↩2

2. Only applicable to ARA and diallers with an Octalarm Link licence (LINK). ↩ ↩2 ↩3 ↩4

3. Only applicable to ARA and diallers licensed for duty schedule module (DUTY). ↩