Skip to main content

DC09 Alarm Management System Integration

What DC09 Alarm Management System Integration Does​

GCXONE supports direct integration with third-party Alarm Management Systems (CMS) from the Marketplace. This guide covers two newly supported integrations: DC09-based CMS receivers — including Amwin, Lisa, Immix, and other SIA DC-09 compatible systems — and Evalink Talos, a cloud-based alarm management platform. Both integrations can be configured entirely from within GCXONE without any manual protocol setup.

Why It Matters​

Without a direct CMS integration, alarms require manual forwarding — introducing delays, human error, and gaps in incident response. DC09 and Talos integrations ensure alarms reach the monitoring station automatically the moment they trigger, with full video evidence attached.

How It Works​

DC09 CMS Integration​

What is SIA DC-09?​

SIA DC-09 is an industry-standard protocol used for transmitting alarm signals from a monitoring system to a Central Monitoring Station (CMS) or Alarm Receiving Centre (ARC). It operates over IP networks (TCP/IP) and is the backbone of modern alarm communication, replacing older PSTN-based formats. When an alarm event is triggered in GCXONE, the platform acts as the sending endpoint — packaging the alarm data and forwarding it to the CMS receiver at the configured IP address and port.

GCXONE extends the standard DC-09 signal by attaching a secure event link. When the operator at the CMS opens the link, they see a rich evidence view: pre-event footage, the event frame, post-event footage, and an animated GIF of the event — all fully configurable per deployment.

Step 1 — Navigate to the Marketplace​

Go to Marketplace in the left navigation panel. Click the Alarm Management System tab to filter the view to CMS-compatible integrations.

The Alarm Management System section displays all supported receivers — currently Amwin, Lisa Security, Immix, and Other CMS System (for any DC-09 compatible receiver not listed explicitly). Each card shows its configuration status — Configured or Not Configured.

Step 2 — Configure the CMS Receiver​
Click Explore on the CMS you want to configure, then click Configure to open the connection setup dialog.​

The configuration dialog requires two fields:

  • DC09 Receiver IP Address — the IP address of the CMS server where GCXONE will push alarm data.
  • DC09 Receiver Port — the TCP port the CMS server is listening on for incoming DC-09 signals.

Once submitted, GCXONE establishes the initial TCP connection. The integration card updates its status to Configured. Alarms will only be forwarded once individual sites are mapped in the next step.

Step 3 — Map Sites in the Alarm Management System Table​

Navigate to Configuration → [Your Service Provider] → Alarm Management System to open the site mapping table.

This table lists every site under the service provider, showing the Customer, Site name, DC09 Account ID, CMS system assigned, and connection status:

  • Red indicator — site not yet mapped.
  • Green indicator — site successfully mapped and connected.
Step 4 — Edit Site Configuration (DC09 Account ID)​

Click the edit icon on any site row to open the Edit IP Configuration dialog:

  • DC09 Account ID — must exactly match the site name as registered on the CMS. This is the identifier the CMS uses to attribute incoming alarms to the correct account.
  • Encryption Key — an optional shared secret for encrypted DC-09 communication. Leave blank if the CMS does not require encryption.

Click Update to save. Once mapped, GCXONE will begin forwarding alarms from that site to the CMS using DC-09, with a secure event link attached.

Evalink Talos is a cloud-native alarm management platform used by monitoring centres to receive, process, and dispatch alarm events. Unlike DC-09 receivers that accept pushed signals over TCP, Talos uses a REST API for integration. GCXONE connects to Talos by authenticating with an API key — no network-level firewall configuration required on the Talos side.

In the Marketplace, click Explore on the Evalink Talos card, then click Configure.

The configuration requires two values from your Talos account:

  • API Key — a Talos-generated API key with full access permissions.
  • Company ID — the unique identifier for your organisation within Talos.

Both values are available in your Evalink Talos account settings under API Access. Paste them into the configuration form and click Submit. Once active, alarms are forwarded to Talos automatically — no additional site-level mapping is required.

Key Capabilities​

FeatureDC-09Evalink Talos
ProtocolSIA DC-09 over TCP/IPREST API
Site Mapping RequiredYes — per siteNo — auto-sync
Firewall ConfigurationRequiredNot required
Video EvidenceSecure event link attachedVia GCXONE integration
Supported SystemsAmwin, Lisa, Immix, Other DC-09Evalink Talos

Real-World Use Cases​

  • A monitoring centre using Immix configures the DC-09 integration in minutes — operators receive alarm signals with pre-event footage links without any manual forwarding.
  • A service provider switches to Evalink Talos — API credentials are pasted once and all sites sync automatically with no per-site mapping needed.
  • A CMS not listed in the Marketplace uses the Other CMS System option — any SIA DC-09 compatible receiver connects using the same configuration fields.

Best Practices​

  • Always verify the DC09 Account ID matches exactly with the CMS — a single character mismatch silently drops alarms.
  • Use the Encryption Key for deployments requiring secure DC-09 communication.
  • For Talos, ensure the API Key has full access permissions before submitting — limited keys cause silent integration failures.
  • After configuration, send a test alarm to confirm end-to-end delivery before going live.

Additional Details​

Both integrations are designed to be configured entirely within GCXONE without any manual protocol configuration or external scripting.

For support or configuration assistance, contact NXGEN Technology AG through the GCXONE support portal.

Download PDF
Loading...