Flyinglink Alarm: What It Does for MSPs Who Need to Carry Alarm Traffic Over IP
Posted by: Flyingvoice
Nov 17, 2026
Views:4582

When an MSP replaces a POTS line that was carrying alarm panel traffic, the hardware part is usually straightforward. You install a gateway, register it to a SIP trunk, and voice calls work. The trouble starts when the alarm panel behind that line tries to communicate with the central station.


Alarm panels do not send voice in the way a person does. They send encoded data tones — Contact ID, SIA, Pulse, FSK — over an analog line, and the central station's receiver decodes those tones and logs the event. When you move that line onto an IP network, the tones become RTP packets subject to latency, jitter, and packet loss. The receiver may still hear something, but the handshake and kiss-off tones that the panel expects to receive back can arrive too late, or distorted, or not at all. The alarm fails silently. Nobody knows until someone checks the log, or until a missed event turns into a liability.


Flyinglink Alarm is the layer Flyingvoice built to solve this. It is a combined software-and-hardware solution that sits between the alarm panel and the central station, and it gives the MSP control over how alarm messages are carried, verified, and delivered.



What Flyinglink Alarm is

Flyinglink Alarm consists of three parts: the Flyingvoice hardware at the customer site (PR12, PR18, LM150, or AGW series), a software component called the CSR-Gateway, and the Flyinglink management platform.


The hardware connects to the alarm panel the same way copper did. The panel dials, the device picks up, and the alarm tones travel between the panel and the device over the FXS port. What happens after that is where things change. Instead of forwarding raw audio over a SIP call and hoping the receiver can decode it, the device parses the alarm message according to the protocol the panel is using, converts it into a structured digital format, and sends it to the CSR-Gateway over HTTPS.


The CSR-Gateway then takes that digital alarm message and delivers it to the central station. How it delivers depends on what the receiving end accepts. The current options are SIA DC-09 (the standard IP-based alarm reporting protocol), a SIP call that mimics the original PSTN path, and HTTPS. The MSP chooses the delivery method based on what the monitoring company's receiver supports.



What problem it solves

The core problem is that alarm communication over IP is unreliable when it relies on carrying analog tones through a VoIP call. The white paper Flyingvoice published on this topic lists four failure modes: kiss-off tones arriving too late because of latency, signal overlap when the panel retries before the receiver responds, audio distortion from packet loss, and DTMF format conversion between different VoIP systems. Any of these can cause an alarm to fail without generating an error that anyone notices.


Flyinglink Alarm addresses this by removing the dependency on voice-quality transmission for the alarm message itself. In the IP Communicator mode, the alarm tones exist only between the panel and the device. The device decodes them, and what travels over the network is a digital message, not audio. This means latency, jitter, and packet loss on the IP path no longer affect whether the alarm data arrives intact. The network only needs to be good enough to carry an HTTPS request, which is a much lower bar than carrying machine-generated audio tones within tight timing tolerances.

The solution works across any network environment the device might be installed on: broadband, LTE, fixed wireless, or a mix. The alarm message reaches the CSR-Gateway as long as the device has IP connectivity. It does not matter whether that connectivity is fast, stable, or voice-grade.



What makes it different

Five things set Flyinglink Alarm apart from a standard ATA-and-SIP-trunk approach to alarm replacement.


It supports the alarm protocols already in the field. The device can parse Contact ID, SIA DC-03, Pulse 3+1/4+2, Silent Knight FSK1/FSK2, BFSK, and High Speed DTMF. These cover the protocols used by Honeywell, Bosch, DSC, Radionics, Silent Knight, and Ademco panels that have been installed over the past two decades. The MSP does not need to know in advance which protocol a given panel uses. The device reads the handshake when the panel dials, works out the protocol automatically, and processes the message accordingly. There is no per-panel protocol setting to look up or get wrong.


The CSR-Gateway runs on the MSP's own infrastructure. It is a Docker container deployed on a server the MSP already controls. It is multi-tenant by design, so one instance can serve multiple customers and multiple sites, and capacity scales with the hardware underneath it. There is no per-message fee. Alarm volume does not become a metered cost line, so the cost of running a site does not grow every time its traffic does. That is a different commercial model from a relay service that bills per event or per device.


Missed alarms do not disappear. When an alarm message arrives at the CSR-Gateway, it is logged in Flyinglink regardless of whether it was successfully delivered to the central station. If the SIP call to the receiver fails, or the DC-09 delivery times out, the event is still visible in the platform's event log. The MSP can see what came in, when it arrived, and what happened when the gateway tried to forward it. If delivery fails, the system can notify the administrator through API callbacks, email, or web notifications. The alarm is not lost just because the second hop failed.

It speaks to central stations in more than one way. Some monitoring companies still expect alarm traffic to come in as a phone call. Others have IP receivers that accept DC-09 over TCP. Some have HTTPS endpoints. Flyinglink Alarm supports all three delivery methods, and the MSP can configure which one to use per client or per site. This matters because an MSP working with multiple monitoring companies cannot standardize on a single delivery path. The gateway adapts to what the receiving end accepts, rather than forcing the monitoring company to change.


It works with Flyingvoice hardware out of the box. For PR12, PR18, LM150, and AGW series devices, enabling alarm mode is a configuration change, not a hardware swap. The MSP selects the FXS port, sets the terminal type to Alarm, points the device at the CSR-Gateway URL, and the device begins forwarding alarm events. There is no separate alarm communicator to install, no additional wiring, and no need to replace the panel itself.



Where it fits in the MSP's operation

For an MSP that is already replacing POTS lines for voice, alarm traffic is the part that turns a straightforward deployment into a project that requires testing and validation. The customer's alarm panel was certified on copper. Moving it to IP changes the transmission characteristics, and the monitoring company may not accept the new path without evidence that it works.


Flyinglink Alarm gives the MSP a way to carry that traffic without betting on whether a VoIP call can faithfully transport DTMF and FSK tones under real network conditions. The alarm message is digitized at the device, delivered as data to a gateway the MSP controls, and forwarded to the central station using whatever protocol the receiver expects. If the forward fails, the event is still recorded and the MSP is notified.


That is the difference between replacing a phone line and replacing an alarm path. A phone line either carries voice or it does not. An alarm path has to carry a specific message, from a specific panel, to a specific receiver, within a specific timing window, and it has to do it on the worst day of the year. Flyinglink Alarm is built to make that work regardless of what network the device is sitting on.