Panel cannot reach the supervising station
very common
“Panel's showing a communicator trouble or a failure to communicate. Everything in the building tests fine but nothing's getting to the monitoring company, and it's been sitting like that for weeks.”
Likely causes
-
POTS line gone after a carrier change or a building phone system swap
~30%Trouble timestamped to the week the phone service changed. The line is now VoIP, a hosted PBX extension or simply disconnected. A managed VoIP path may pass a manual test and still fail on a real event, so passing once proves less than the customer thinks.
-
IP or cellular path down: network change, firewall rule, dead switch port, or poor signal
~25%Only one path is in trouble and the other still reports. IT changed a VLAN, a firewall rule or a DHCP scope, or the cellular radio has lost signal after a building fit-out put steel between it and the window.
-
Account, programming or supervising station side problem
~15%The panel dials or connects successfully but the station rejects or cannot match the signal. Account number wrong after a panel swap, the receiver number changed, or the account was suspended for non-payment. Call the station before you pull the communicator.
-
Periodic test signal failing while alarms still get through
~10%The station has no record of the scheduled test but has your manual alarm tests. Points at the test timer being disabled or reprogrammed, or a clock that drifted after a power event.
-
Communicator hardware or its connection to the panel failed
~10%No path works, the communicator shows no link light or a fault code, and the panel reports the communicator itself missing rather than reporting a path failure.
-
Power or supervision problem at the communicator, not the path
~10%The communicator is fed from a separate supply or a shared transformer that has failed, or its supervised connection back to the panel is open. Check power and the interconnect before the path.
What to bring
- Phone, and the supervising station's number and account details
- Panel and communicator manuals
- Laptop for the communicator's network interface
- Line test set or a known-good analogue handset for telephone paths
- Network cable tester
- Photos of the trouble text and communicator status
Safety
Licence and AHJ coordination as required. A panel that cannot reach the supervising station is an impaired system even though everything in the building works. Notify the owner and the AHJ, log the impairment, and arrange the interim measures your jurisdiction requires for the duration. Do not leave this on the trouble list as somebody else's problem; it is the fault most likely to sit unaddressed until the night it matters.
Steps
-
Step 1: Call the supervising station first and ask what they actually see
Free, takes five minutes, and it splits the problem in half. Ask what signals they have received and when, what the account status is, and whether they show a path failure from their side. Get the account number and receiver details from them while you have them on the line.
If that doesn’t do it
Station has no record of the account at all: this is an account or contract problem, not a wiring one; escalate to the owner before you troubleshoot hardware.
-
Step 2: Read exactly which path the panel is calling in trouble
Panels distinguish between primary and secondary path failures, communicator missing, and failure to communicate. Those are different faults. Photograph the trouble text and the communicator's own status display or LEDs before you change anything.
If that doesn’t do it
Trouble text is generic: read the communicator's own diagnostics or its web interface.
-
Step 3: Verify power and the supervised connection to the panel
Confirm the communicator has its power source and that the connection between panel and communicator is intact and supervised. A communicator reported missing is almost never a path problem.
If that doesn’t do it
Power and interconnect good: move to the path.
-
Step 4: Test the physical path end to end
For a telephone path, confirm what the line actually is now: a carrier change from copper to VoIP is the single most common cause on this entry and the owner usually does not know it happened. For IP, confirm link, address and that the firewall permits the destination and port the station requires. For cellular, read the signal level the communicator reports and check whether recent construction changed what is between it and the outside.
If that doesn’t do it
Path present and healthy: the problem is account or programming at the station end.
-
Step 5: Send a manual test on each path separately and confirm receipt
Test each path on its own, not both at once, and have the station confirm receipt of each. A dual-path communicator that passes overall can be hiding one dead path for months.
If that doesn’t do it
One path passes and the other does not: that is your fault; do not close the call on a single passing path.
-
Step 6: Verify the periodic test signal is enabled and scheduled
Confirm the timer is programmed and the panel's clock is right, then ask the station to confirm the next scheduled test arrives. The supervising station arrangements and the required testing are in NFPA 72 Ch. 26 and Ch. 14. Confirm against the edition your AHJ enforces.
If that doesn’t do it
Test signal still not arriving with alarms getting through: the programming or the station's expected schedule is wrong; resolve with the station rather than by guesswork.
-
Step 7: Fix the path as a documented change and re-test both paths
If a path has to be replaced (copper to cellular, a new IP route, a second path added) treat it as a change to the monitoring arrangement: document it, confirm with the station, notify the owner and the AHJ, and update the record. Then re-test both paths and get written confirmation of receipt for the job file.
If that doesn’t do it
Owner will not fund a replacement path: the system is not communicating as approved; document the deficiency in writing to the owner and notify the AHJ, and do not sign the system off as normal.
References
- NFPA 72, Ch. 26
- NFPA 72, Ch. 10
- NFPA 72, Ch. 14
- IFC 901.7