Overview

It forms the final link in Olarm’s signal delivery chain, ensuring reliable communication between Olarm-connected alarm systems and your ARC.

Key features include:

• Encrypted WebSocket signal delivery

• Runs locally on the ARC network or monitoring server, with all external connections secured via encrypted, authenticated WebSocket links.

• Dual routing support (Olarm Cloud + Base Station, where available)

• Multiple connection support for failover and redundancy

• ARC-controlled connection prioritisation

• Real-time loss detection within seconds

• Self-managed setup – no tickets required

• Full audit logging and connection history in Command Centre
  
  

Minimum Requirements

Note: Older Windows versions are not supported due to known security vulnerabilities.

Make sure the panels are correctly programmed to allow devices to transmit signals. You can find the setup guides here.

Step 1: Installing Olarm SIGNALS PROXY

Download and Install

• Log in to Command Centre

• Go to Settings > Connections

• Download and install the Olarm SIGNALS PROXY

Open the Application

• Launch Olarm SIGNALS PROXY from your desktop or Start menu

Step 2: Add a Signal Path

• Click ‘Add Signal Path’

• Name the Signal Path
  Use a clear, recognisable name (e.g. Main Office TCP Link)

• Select the Connection Type

  • If your monitoring software is a TCP Server, choose TCP Client

  • If your monitoring software is a TCP Client, choose TCP Server

Important:
The Olarm SIGNALS PROXY must be configured as the opposite of your monitoring software.

All configuration within the monitoring software must be performed by your monitoring company or authorised service provider.

Step 3: TCP Configuration

If using TCP Client mode:

• The monitoring software must be set up as a TCP Server

• You must enter the IP address or domain hostname and port where the monitoring software is listening

• The SIGNALS PROXY will initiate the TCP connection

If using TCP Server mode:

• The monitoring software must be configured as a TCP Client

• You must choose a local port for the SIGNALS PROXY to listen on

• The monitoring software will initiate the TCP connection to the proxy

In both cases, the SIGNALS PROXY will forward signals from the Olarm Cloud to the monitoring software over this TCP link.

Step 4: Creating a Connection in Command Centre

To securely link the SIGNALS PROXY to the Olarm Cloud:

• In Command Centre, go to Settings > Connections

• Click ‘Add Connection’

• Enter the following:

  • Connection Name

  • Protocol – SIA DC09 or CID

  • Priority – 1 = highest

  • Connection Key Name

• Click ‘Create’

• Copy the Connection Key from the connection details page

Step 5: Finalising the Signal Path

• Return to Olarm SIGNALS PROXY

• Paste the Connection Key

• Confirm the connection type, protocol, and port

• Save the Signal Path

Once saved, the Olarm SIGNALS PROXY will establish a secure WebSocket connection and begin routing signals.

Email Alerts

Olarm sends automatic alert emails to help monitor connection health:

• No Secondary Connection Configured (In Progress)
  Sent monthly to encourage signal redundancy

• Incompatible Connection Type
  Sent daily or every 12 hours if a signal path cannot receive data due to a mismatch

• Failed to Process Signals
  Sent daily or every 12 hours if a connection is failing due to configuration or network issues

All alert emails include a direct link to Command Centre for resolving issues quickly.