When your monitoring company contacts you with a “failed to communicate,” “runner test failed,” or no-signal notice, it means the central supervising station cannot reach your fire alarm panel — and that, for now, a real alarm in your building may not result in a dispatch. This is the monitoring company’s view of a gap in your coverage; it is distinct from the panel-side communicator trouble your own panel displays, which is covered separately at fire alarm communicator/dialer trouble. Vector Fire is a referral service, not a contractor — so there is nothing to sell on this page; the honest answer is that some quick checks are safe to run yourself, but restoring communication or correcting programming requires a licensed technician or your monitoring company’s help.
What the Notice Actually Means
Commercial fire alarm systems on supervised communication paths are required to confirm they can reach the monitoring station on a regular cycle — typically every 24 hours — by transmitting a test signal. The station expects that signal; when it doesn’t arrive, or when a station-initiated check (a “runner test”) gets no response from the panel, the station records a failure to communicate and is obligated to notify you.
The practical consequence is significant: during the gap, the station cannot receive alarm signals, trouble reports, or supervisory conditions from your panel. If a smoke detector activates, a sprinkler flows, or a manual pull station is triggered at 2 a.m., the fire department may not be notified. Monitored coverage exists precisely to provide that automatic response — a failed communication path suspends it.
Monitoring company’s view vs. the panel’s view. Your fire alarm panel may also show its own communicator trouble on the display — that is the panel reporting a problem with its outbound path. This article covers the monitoring station’s notice that it cannot reach you. The two often have the same root cause (a broken comm path), but are surfaced at different ends. See the dialer/communicator trouble article for the panel-side signal.
Common Causes, Ranked
Most failed-to-communicate notices trace to one of these causes. They are ordered by how frequently they appear in commercial buildings, but any one of them creates the same coverage gap.
1. Traditional phone line cut or a VoIP swap
Older commercial panels use a DACT (digital alarm communicator transmitter) that dials the monitoring station over a standard analog phone line. When a property replaces its copper telephone service with a VoIP line — a very common change as carriers phase out traditional lines — the DACT may silently stop communicating. VoIP services do not always reliably carry the analog tones and protocols the DACT uses, even when the phone itself rings and receives calls normally. A physical line cut — intentional or accidental during nearby construction — produces the same result immediately.
2. Cellular path disruption
Many commercial systems communicate over a cellular radio module — a common upgrade from phone-line DACT and the dominant path on newer installs. Cellular communication can fail when: the antenna or module loses signal (physical obstruction, a moved panel or antenna, building renovation), the cellular carrier retires a frequency band the module depended on, or the monitoring company’s cellular account associated with that communicator has a provisioning issue. The panel may show no local trouble at all, but the station cannot receive signals. Major U.S. carriers completed their 3G network shutdowns between 2022 and 2023, which left a significant number of older fire alarm cellular modules unable to reach the monitoring station; if your building’s cellular communicator was installed before 2018 and has never been evaluated since, confirm with your fire alarm company that it is on a currently supported network. A module stranded by a 3G shutdown generally cannot be fixed with a software update — it needs a hardware replacement with a communicator that supports the current cellular network.
3. IP/network path outage or reconfiguration
IP-based communicators send signals over the property’s local network and internet connection. An extended internet outage, a router replacement, a network reconfiguration that changed the IP address or blocked the communicator’s outbound port, or a firewall rule added by an IT team can all sever the path without any visible change at the panel. Dual-path communicators (cellular + IP) are designed to survive a single-path failure, but a single-path IP communicator goes dark whenever the network does.
4. Account left on test after service
This is the most important cause to understand because it creates a gap that is invisible to everyone in the building. When a fire alarm technician services your system, standard practice is to call the monitoring company at the start of the visit to place the account “on test” — test mode tells the station to suppress dispatch so that activation of devices during testing doesn’t roll fire trucks. On test does not mean the system is off. Signals still travel from your panel to the monitoring station. The station simply logs them as test events rather than dispatching.
The problem arises when the technician does not call the station at the end of the visit to take the account off test. The account stays in test mode — for hours, days, or longer — and no one at the building is aware of it. A real fire alarm during that window will be received by the station and suppressed, because the account is still flagged as on test. This is a silent coverage gap: the panel is armed, the communication path is working, but emergency response has been quietly suspended.
5. Billing or account lapse
If a monitoring service contract expires, is not renewed, or is suspended for non-payment, the supervising station may deactivate the account. Signals may still technically reach the station’s receiver, but with no active account they are not processed and no dispatch occurs. Some monitoring companies send notices in advance; others act on the contract end date without further warning. The building’s panel typically continues to function normally — there is no local indicator that the monitoring account is inactive.
What You Can Safely Check as the Building Manager
There is a short list of things you can confirm yourself — all of it is look-and-ask, none of it is operating the panel or equipment. These checks help you identify the likely cause and give your technician or monitoring company the information they need to restore service quickly.
Check whether recent service might have left the account on test
The safe check: Look at your service records or contact whoever manages your fire alarm maintenance. Was there a service visit in the past day or two — an inspection, a repair, a device replacement, or a smoke-detector cleaning? If so, the technician may not have taken the account off test when they left. Call your monitoring company’s subscriber line (not 911, not the dispatch center — the monitoring company’s regular business number), explain that you received a notice, and ask whether the account is currently on test. If it is, they can take it off test over the phone.
STOP: Do not attempt to “clear” the on-test condition by entering panel programming or pressing keys to reinitialize the communicator. Only the monitoring company can toggle the account’s test status in their system — panel-side actions will not change it.
Check whether phone, internet, or network service has changed
The safe check: Ask your office or facilities team whether there have been any changes to the building’s phone or internet service — new VoIP provider, a new router, an ISP change, a network reconfiguration. If your panel communicates over a phone line, confirm that the dedicated alarm line still has dial tone (pick up a handset on that line, or ask your telecom provider). If the panel uses IP, confirm the router serving that network path is online. Document what you find and pass it to the technician: these are the inputs they need to diagnose quickly.
STOP: Do not reset, replace, or reconfigure the router or network equipment in order to restore fire alarm communication. Networking changes that affect the communicator’s IP settings require the technician to coordinate with you — a router factory-reset without that coordination can break the path further or affect other building systems.
Confirm your monitoring account is current
The safe check: Verify with your accounting or facilities team that the monitoring contract is paid and active. Look for any lapse notices from the monitoring company. If there is a billing issue, contact the monitoring company directly to reinstate the account — they can confirm whether an account suspension caused the failure to communicate.
STOP: Do not treat a failed-to-communicate notice as routine correspondence to be filed and handled later. The gap in dispatch coverage is active for as long as the condition persists. Respond to every notice the monitoring company sends, on the day it arrives.
Keep the monitoring company’s subscriber number in your files
The safe check: Your monitoring company’s subscriber service line — distinct from their emergency dispatch center — is the first call to make when you receive any notice. They can tell you exactly what their system shows: whether the account is on test, when the last successful signal was received, and what type of failure they are logging. Write that number down and keep it posted near the panel and in your fire protection records.
When to Call a Licensed Technician
The checks above help you identify the cause. Fixing it — restoring the communication path, updating programming, replacing or re-provisioning a communicator module — requires a licensed fire alarm technician or your monitoring company’s technical team. Call one when:
- The monitoring company confirms the account is not on test but still cannot receive signals — the communication path itself has failed and needs diagnosis.
- The panel has a DACT or cellular communicator and the phone line or cellular path has changed, degraded, or the carrier retired the frequency band the module uses — the module may need replacement or re-provisioning.
- The panel’s own display shows a communicator or dialer trouble in addition to the monitoring company’s notice — both ends of the path are flagging a problem.
- The account was left on test and has been off test before, but the path still fails after the monitoring company clears the test status — an underlying comm fault needs investigation.
- You cannot identify or confirm the cause within a few minutes of checking — uncertainty about a life-safety coverage gap is a reason to call, not a reason to wait.
Never ignore a failed-to-communicate notice and assume the next test cycle will pass on its own. The path that was broken yesterday will be broken tonight — and if a fire occurs during that window, the monitoring company’s dispatch coverage is not there.
How This Ties to Code & Cost
NFPA 72 requires that supervised communication paths between a panel and a supervising station be tested on a schedule — the standard maximum interval for a test signal is 24 hours for most path types — so that a broken path is detected within one day rather than discovered only when a real alarm fails to dispatch. For how those monitoring requirements apply to commercial properties and what a properly supervised system is expected to do, see our overview of commercial fire alarm monitoring in Houston.
On the cost side, communication path failures sometimes mean a communicator module needs to be replaced or upgraded — particularly when a DACT loses its phone line permanently or a cellular module’s frequency band is retired. For how monitoring service and path upgrades are priced in this market, see our guide to fire alarm monitoring costs in Houston.
A failed-to-communicate condition is one reason a commercial fire alarm panel may show a trouble signal or beep. This article covers the monitoring company’s view of the gap; the panel-side communicator trouble — where your own panel displays the fault — is covered at fire alarm communicator/dialer trouble. For the full list of reasons a commercial panel beeps, start at why your commercial fire alarm panel is beeping — a comm failure is one of the common causes covered there.