🛰️ Alarm Forwarding Configuration
GCXONE provides a modular pipeline for receiving, enriching, and forwarding alarms to any monitoring backend. This guide explains how to configure the three categories of alarm forwarders.
🏗️ Architecture Overview
GCXONE is the "Field Intelligence Layer." It processes raw device signals (AI verification, health checks) and then forwards the enriched event to your Monitoring Station (CMS).
Multi-Forwarding: You can enable multiple forwarders simultaneously (e.g., Talos for operators + Webhook for a custom dashboard + Email for the site manager).
📋 Forwarder Categories
Native API integration. Tight coupling for bi-directional sync of sites, health, and video clips.
- Current Support: Evalink Talos.
- Use Case: When you want a seamless experience where operators never leave the CMS interface.
⚙️ How to Configure
1. Webhook Forwarder (Custom Apps)
- Go to Settings → Forwarders → Technological.
- Enter your Endpoint URL.
- Select the HTTP Method (Standard is POST).
- Add any required Auth Headers (API Keys or Bearer Tokens).
2. Primary CMS (Talos)
- Go to Settings → Forwarders → Primary CMS.
- Toggle Evalink Talos to ON.
- Authenticate with your Talos API credentials.
- Enable Site Auto-Sync to ensure new GCXONE sites are instantly created in Talos.
🚀 Common Use Cases
The "Migration" Strategy
If you are moving from a legacy system (like AmWin) to the cloud (Talos):
- Enable the AmWin (Traditional) forwarder initially.
- Enable the Talos (Primary) forwarder in parallel.
- Gradually move sites to Talos and eventually disable the AmWin forwarder.
The "Tech-Forward" Strategy
For developers building a custom mobile app for field guards:
- Enable the MQTT or Webhook forwarder.
- Filter the events to only forward "Verified Human Detected" signals to the custom app.