Strobe & Siren Control from Command Centre
Map any Gallagher output to a calibrated Axis strobe/siren profile. The integration runs on the strobe itself - there's no extra server to deploy, harden, or patch.
The Gallagher Strobe Bridge is a native ACAP that runs directly on Axis D4100-series strobe sirens. It subscribes to a configurable set of Gallagher outputs via Command Centre's REST API, and maps each output state to a strobe/siren profile served via the device's siren_and_light.cgi endpoint. Customers configure everything through the camera's web UI - no Windows service, no integration server, no certificate juggling between hosts.

The technical surface.
What it does, said plainly.
Native ACAP - zero footprint
Ships as a signed .eap package. Installs on the strobe itself, with no additional infrastructure. Updates are pushed like any other ACAP.
Long-poll subscription
Uses Gallagher's long-poll subscription model so state changes propagate in well under a second, without polling overhead or open inbound ports.
Profile mapping per output
Each Gallagher output (alarm zone, door, custom trigger) maps to a strobe profile: color, flash pattern, siren tone, intensity, and timeout - all configured through the ACAP UI.
Field-tested
Verified against live Gallagher test servers and production-grade Axis hardware (D4100-VE Mk II, FW 12.10+, aarch64).
How it's wired.
- 01Axis D4100-VE Mk II strobe siren (aarch64, FW 12.10+) - runs ACAP
- 02ACAP subscribes to Gallagher CC REST API outputs endpoint
- 03Output state change → mapped profile → local siren_and_light.cgi call
- 04Status, last-event, and error log surfaced in the ACAP web UI

Real customer scenarios.
Bring Gallagher Strobe Bridge into a deal.
Demo against your customer's actual workflow. Pricing the same day.
