Alarm icon System failures

System failures are separate alarms that protect the operation of the Octalarm alarm dialler. Like the input alarms, you can configure them as you wish, except for the alarm text and delays. These cannot be adjusted.

Recorded system failures

Note: by default, the call list All contacts is associated with all system failures. It is important to change this to the desired call list.

Grid failure

When the voltage drops, the alarm dialler sends an alert. This alert is called grid failure and has the special feature that it always sends alerts separately. This means that after completing the current call, the dialler calls out the grid failure without mentioning any other active alarms.

Internal failures

Internal failures is a collection of faults that threaten alarm processing.

GSM module

The GSM module fails when:

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

SIP

The SIP failure sends an alert when there has been no connection to the server for several minutes. Possible causes are:

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

PSTN

The PSTN connection fails when:

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

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

1. You will get this message when five or more calls have failed for a given communication interface (mobile telephony, VoIP or landline telephony). This alarm ensures that all dial-out capabilities are monitored.

2. An unaccepted or incorrectly accepted alarm is also considered a failed call attempt.

3. Please note when using voicemail: If the alarm call is not accepted before a certain time then it goes to voicemail. This is also considered a failed call attempt.

4. ALWAYS take action on this system failure. After all, there is an interface that is not working correctly.

5. Resolving this message: the counter is reset to zero only when there has been another successful call over this communication interface. To do this, make a test call from Contacts via the communication interface that gives the error message. See Contacts|Add and edit: Run test call for further explanation. When the interface is OK, this is displayed with ‘call successful’. This drops the alarm notification.

External IO (EM-8001)

With the external IO fault, the EM-8001 (external module) is inaccessible. Possible causes are:

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

Battery failure

This failure occurs when:

  • the battery is removed or defective (message text Battery failure). As soon as possible, check the battery connection by disconnecting and reconnecting it;
  • the maximum battery age has been reached (message text Maximum battery age reached). You solve this by replacing the battery. 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 at the same time, the Octalarm alarm dialler reports this as 1 alarm. You will then receive the notification: Multiple alarms. There are more than 5 alarms.

Combining the volume of alarms keeps the conversation clear and does not compromise alarm processing.

Tip: ALWAYS take action on this failure. We strongly recommend linking this system failure to an urgent call list.

Internet error: Eth0, Eth1 and/or GSM

When a check on the interface connection (Eth0, Eth1[^note-touch] and/or GSM) fails, this can be reported as a system failure. A system failure occurs only at the interfaces ticked for Report as system failure. See Settings|General|Network: internet check for further explanation on setting up this system failure, internet detection and viewing the internet status of the various interfaces.

Watchdog alarm

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

Alarm Unknown location

When the REST API sends an unknown alarm to the alarm dialler[^note-touch], the dialler reports this alarm as Unknown location out to the selected call list. 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 Absent3.

Note: to ensure smooth processing of alarms, it is important that there are always 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: it is necessary that there are contacts with the role Administrator in the alarm dialler and that their phone number is entered.

1

NOT applicable to Touch.

3

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