A communicator trouble — displayed as “COMM TROUBLE,” “PHONE LINE 1 FAIL,” “PATH FAIL,” “NETWORK FAULT,” or similar wording — means your fire alarm system has lost its link to the central monitoring station. That link is what sends alarm, trouble, and supervisory signals to the people who notify the fire department or alert building contacts; with the communicator in trouble, those signals may not be reaching anyone. Vector Fire is a referral service, not a contractor — there is nothing to sell here; the goal of this page is to help you understand what the panel is telling you and route the problem to the right person as quickly as possible.
What the Panel Is Telling You
A commercial fire alarm panel that connects to a central monitoring station supervises its outgoing communication path — constantly checking that the channel is open and the station is reachable. The moment the panel detects a failure, it generates a trouble signal with an amber/yellow indicator, an intermittent beep, and a display message identifying which path failed.
Read the display carefully. The message typically names both the fault type and the path:
- “PHONE LINE 1 FAIL” / “PHONE LINE 2 FAIL” — the POTS (copper phone line) dialer lost its dial tone or could not complete a call to the monitoring station.
- “PATH FAIL” / “CELLULAR PATH FAIL” — the cellular communicator lost contact with the monitoring station over the cellular network.
- “NETWORK FAULT” / “IP PATH FAIL” / “COMM FAIL” — the IP communicator lost its network connection or can no longer reach the monitoring station’s IP receiver.
The exact wording depends on the panel manufacturer and model — Notifier, Simplex, FireLite, Silent Knight, EST, and others each use their own display text — but all of these messages share the same meaning: the monitoring link is down. Note the exact wording before calling anyone; it tells the technician immediately which path to investigate.
Three Communication Paths — and How Each One Fails
Most commercial fire alarm systems use one or two of these paths to reach the monitoring station. Knowing which path your building has tells you where to look first and who to call.
Path A — POTS Dialer (legacy copper phone line)
A DACT (Digital Alarm Communicator/Transmitter) is the traditional fire alarm dialer: it picks up the copper phone line, dials the monitoring station, and sends tonal data. It requires a live POTS line with a consistent dial tone. When the line goes dead or the call cannot complete, the panel shows “PHONE LINE 1 FAIL” or “PHONE LINE 2 FAIL.”
Common POTS-dialer failure causes:
- The phone line is out of service — carrier outage, a cut cable, or an unpaid phone bill.
- The building switched its phone service to VoIP or a fiber-based voice service. VoIP compresses voice into digital packets; that compression corrupts the tonal handshake a DACT sends, so many VoIP lines simply refuse to pass it. NFPA 72 does not list VoIP as a compliant transmission medium for fire alarm dialers, and many AHJs treat a DACT-over-VoIP setup as a code deficiency.
- The building’s phone system was upgraded (new PBX, new vendor) and the dialer’s dedicated analog line was not carried forward.
The POTS sunset is forcing this issue across the market. AT&T, Lumen, and Verizon are actively retiring copper infrastructure. AT&T began physical wire-center shutoffs in 2026 with a stated goal of retiring most of its copper network by 2029. As carriers wind down copper, buildings with POTS dialers are not choosing to upgrade — they are being forced into it. If a panel started showing POTS dialer trouble and the carrier has been retiring copper in the area, that may be the direct cause rather than any equipment failure. Converting from POTS to cellular or IP is a licensed-technician job.
Path B — Cellular Communicator
A cellular communicator transmits alarm signals over a commercial wireless network (LTE-M or Cat-M1) using a dedicated SIM card, independent of the building’s phone or data infrastructure. It is the most common upgrade path for buildings moving off copper dialers, and because it uses a separate network from the building’s internet, an internet outage does not affect it.
Common cellular communicator failure causes:
- Loss of cellular signal at the communicator’s location — the unit is in a basement, interior electrical room, or other shielded space where signal is marginal. The panel typically shows a cellular path fault — displayed as “PATH FAIL,” “CELLULAR PATH FAIL,” or similar wording depending on the panel manufacturer.
- Carrier network outage in the area — temporary and usually self-resolving, but the path fault shows while it lasts.
- Antenna or cable issue — the external antenna worked loose, was moved, or was damaged during other work in the mechanical room.
- Obsolete radio band. 3G cellular networks were shut down by major US carriers in 2022. A communicator with a 3G-only radio module will show a permanent path fail and must be replaced with a unit supporting LTE-M or 5G.
Path C — IP Communicator (network/internet path)
An IP communicator sends signals over the building’s Ethernet network and internet connection to an IP receiver at the monitoring station. It is typically faster than a cellular path and is often paired with cellular as a dual-path system — IP as the primary, cellular as automatic failover — with each path supervised independently.
Common IP communicator failure causes:
- IT changed the network. This is the most common cause of an IP communicator trouble after a period of stable operation. A VLAN reassignment, a new switch or router, a firewall rule update, a changed DHCP address range, or moving the communicator’s port to a different switch — any of these can sever the path to the monitoring station without anyone in IT realizing the fire alarm is on that network segment.
- Internet or ISP outage. A down ISP connection or failed router takes the IP path with it. On a dual-path (IP + cellular) system the cellular path takes over automatically; on a single IP path the panel shows a fault.
- Monitoring station receiver address or port changed. If the central station makes backend changes and the communicator’s programmed destination is no longer valid, the path fails. This is a programming fix, not a network fix — it requires a licensed technician.
Panel-Side Trouble vs. the Monitoring Station’s “Failed to Communicate”
A communicator trouble on your panel and a “failed to communicate” report from the monitoring station are two views of the same broken link from opposite ends of the line.
Panel-side trouble means the panel detected the failure itself — either it tried to send a signal and could not, or the path supervision check failed (the panel periodically tests whether the path is alive). This is what this article covers.
“Failed to communicate” (monitoring station’s view) means the station stopped receiving scheduled check-ins from your communicator and flagged the account. In many cases the station catches the problem first — the monitoring station’s check-in schedule runs independently of the panel’s own supervision cycle, and the station may notice the absence of an expected signal before the panel’s internal supervision registers a fault.
Both conditions mean the same thing: the communication link is broken and needs to be restored. The monitoring station’s perspective — what they do when check-ins stop arriving, and how they handle account notification — is covered in the companion article on fire alarm monitoring: failed to communicate.
What You Can Safely Check Yourself
A communicator trouble calls for a licensed technician to fix, but there is a small set of safe, look-and-identify steps that can accelerate the diagnosis and confirm who to call. None of these involves opening the panel, touching wiring, or entering programming.
Read and record the display exactly
The safe check: Note the exact message — “PHONE LINE 1 FAIL,” “PATH FAIL,” “COMM TROUBLE,” or whatever the panel shows — and write it down. The wording identifies which path failed (POTS, cellular, or IP) and narrows the cause immediately. This is the single most useful piece of information to have when you call a technician or the monitoring station.
Check whether the building’s phone or network service changed recently
The safe check: Ask facilities, IT, or property management whether anything changed with the building’s phone service or data network in the days before the trouble appeared. A phone-company cutover, a VoIP migration, an IT network change, or routine switch maintenance can directly cause a communicator trouble with no failure in the fire alarm equipment at all. If you can identify a change that lines up with the timing, report it when you call the technician — it tells them exactly where to look.
For a POTS trouble — check whether the phone line is down building-wide
The safe check: If the panel shows a phone line failure, check whether other analog phones in the building have a dial tone. A building-wide outage means the carrier is the problem. Report the outage to the phone carrier and notify your fire alarm monitoring company that communication is interrupted so they can note the account and arrange fire watch if required by the AHJ.
STOP: Do not attempt to trace, patch, or reconnect telephone wiring to the fire alarm panel yourself. The dialer’s dedicated phone connection runs through the panel’s internal board — tracing it requires opening panel wiring, which is licensed-technician work.
For an IP trouble — confirm with IT whether the network changed
The safe check: Contact IT and ask specifically whether the communicator’s network port, VLAN, firewall rules, or the internet connection itself changed. Give IT the communicator’s physical location so they can check that port’s configuration. IT verifying the network environment is appropriate and helpful — but IT should not attempt to modify the fire alarm communicator’s programmed settings.
STOP: Do not enter the panel’s programming menus, attempt to re-enter the communicator’s receiver address, or ask IT to “push new settings” to the fire alarm communicator. Programming a fire alarm communicator requires a licensed technician — incorrect settings can disable the entire communication path and may constitute a code violation.
Notify the monitoring station
The safe check: Call your central monitoring station and tell them the panel is showing a communicator trouble. They can confirm whether they have received recent check-ins from your system and note in your account that communication is currently impaired. This creates a record and ensures the station is aware the path is down while the technician is being arranged.
STOP: Do not silence the trouble beep and treat the communicator issue as a future maintenance item. A communicator in trouble means the monitoring station cannot receive your next alarm. A communicator failure may mean alarms are not reaching help — treat it as same-day urgent.
When to Call a Licensed Technician
A communicator trouble always requires a licensed fire alarm technician to restore — unlike a low battery or AC power fault, you cannot fix a dialer or communicator failure without programming access. Call a licensed contractor when:
- The panel shows any communicator or path fault — same business day. Until the path is restored, alarms may not reach help.
- The panel shows a POTS / phone line failure and the building recently switched to VoIP, fiber, or a new phone vendor — the dialer may need to be replaced or supplemented with a cellular or IP communicator to restore code compliance. This is a licensed-technician job.
- The building still has a POTS/DACT dialer and the phone carrier has retired or is retiring copper in your area — the conversion to cellular or IP is a forced upgrade requiring a licensed technician to reprogram, replace, and re-certify the communicator.
- IT has confirmed the network is intact and the IP communicator still shows a path fault — the problem is in the communicator’s programmed settings or hardware, which is technician work.
- The communicator trouble clears and returns repeatedly — an intermittent fault on a POTS line can indicate deteriorating line quality; on a cellular communicator, it may indicate a marginal signal location needing an antenna change or different placement.
- You are unsure which type of communicator the building has, or what the panel message means — uncertainty about a life-safety communication system is itself a reason to call.
Reprogramming, replacing, or converting a fire alarm communicator is licensed-technician work in every jurisdiction. Attempting it without proper credentials can result in a failed inspection, an unmonitored building, or a code violation.
How This Ties to Code & Cost
NFPA 72 governs how fire alarm communication paths must be supervised and how quickly a failure must be reported. The standard requires communicator supervision at defined intervals — so that a broken path does not go undetected for hours — and on a monitored system it requires that alarm, trouble, and supervisory signals each be transmitted as distinct signal types. The POTS sunset is pushing the entire market through a forced communicator upgrade cycle right now — any building still using a POTS dialer will need to transition to cellular or IP. For a detailed look at what commercial fire alarm monitoring involves, what the monitoring station receives, and why a working communication path is the foundation of the whole system, see our overview of commercial fire alarm monitoring in Houston.
On the cost side, a communicator upgrade from POTS to cellular or IP is one of the more budget-significant service items a commercial building may face in the near term — the copper sunset makes it a matter of when, not if. For how monitoring service contracts and communicator upgrades are priced in the Houston market, see our guide to fire alarm monitoring costs in Houston.
A communicator trouble is one of several conditions that cause a commercial fire alarm panel to beep. For the full symptom-by-symptom walkthrough of all the common causes of a beeping or annunciating panel, start at why your commercial fire alarm panel is beeping — this is one cause among several covered there.