10.2 IP, Cellular, and Dual-Path Communications
Key Takeaways
- Listed IP and cellular (typically LTE) communicators are performance-based fire paths: they send the FACU’s signals over a data network instead of depending on analog copper.
- Commonly taught NFPA 72 performance-based supervision for a single communications path (2016 and later, including NFPA 72-22 as referenced by the 2025 Uniform Code) is a check-in at intervals not exceeding 60 minutes, with path failure indicated at the supervising station within that window.
- Multiple independent communications paths are commonly taught as timer-tested at intervals not exceeding 6 hours each; a dual-path IP-plus-cellular design must not share a single point of failure that kills both means.
- Burglary communicators often still use a 24-hour test timer; do not paste that burglary interval onto a fire single-path IP or cellular communicator.
- Programming test timers, backup paths, and failure-to-test is licensed 19 NYCRR 195.1 work even when the technician uses a laptop or a remote programming session.
Why the second half of the 8-hour block is not another phone line
Section 10.1 left the DACT on analog copper. Most New York fire jobs you will see in 2026 do not stop there. Carriers retire POTS. Consumer VoIP breaks seizure and DTMF. Later NFPA 72 teaching already wanted a DACT’s second means to be something other than a second analog pair. Independent OpenExamPrep material for Module 2.III therefore spends this section on Internet Protocol (IP) communicators, cellular communicators (typically Long-Term Evolution (LTE)), and dual-path combinations such as IP + cell.
The DOS bulletin still says alarm transmissions. It does not name a brand. Learn the architecture, the supervision interval, and the independence rule. Leave the catalog slogan in the van.
This is still the statewide Security or Fire Alarm Installer sitting, not an FDNY Certificate of Fitness course. A New York City fire-alarm job can be more restrictive. That does not rewrite 19 NYCRR 195.1 or invent a DOS cellular mandate.
IP communicators
An IP communicator takes the FACU’s reporting traffic and sends it as data packets across a local Ethernet network and the public internet (or a private listed network) to a supervising-station receiver or to a listed network operations center (NOC) that then delivers the signal to the central station.
Two hardware patterns appear on the exam and in the field:
- A native IP communicator listed for fire, with an Ethernet port, that the FACU treats as its off-premises path.
- A DACT-to-IP translator (or “POTS-in-a-box” analog interface) that still presents an analog port to an older DACT while the outbound path is IP or cellular. The FACU thinks it is dialing. The translator is doing the modern path. The translator still has to be listed for that fire use. A consumer analog telephone adapter is not that product.
Installer skills that show up as closed-book facts:
- Use a listed communicator. A spare office router is not a fire communicator.
- Give the communicator primary and secondary power consistent with the FACU chapter — it must survive the same outage the panel survives.
- Do not power a fire communicator from a random Power over Ethernet (PoE) switch unless that arrangement is listed for the fire communicator. PoE that dies with the IT rack is not fire secondary power.
- Coordinate with the building’s information-technology staff: static addressing versus DHCP, firewall rules that must not block the listed ports, and a switch port that will not be “cleaned up” on Monday.
- A virtual LAN (VLAN) can isolate fire traffic. Isolation is not a substitute for listing, supervision, or AHJ acceptance.
IP is fast when the network is up. It is silent when someone unplugs the building switch to “reset the Wi-Fi.” That is why supervision intervals and dual-path designs exist.
Cellular (LTE) communicators
A cellular communicator uses a listed radio and antenna to reach a carrier network, then the supervising station or NOC. LTE is the commonly taught current generation on fire products; older 3G fire radios were sunset by carriers the same way analog copper was sunset. Do not leave a 3G-only communicator in service and call it “still a cell path.”
Field rules you can defend on the exam:
- Antenna location matters. A metal electrical room, a basement FACU closet, or a foil-faced plenum can starve the radio. The installer walks a signal-strength check per the listing instructions, not a guess from the parking lot.
- Antenna cabling is part of the listed assembly. Random coaxial leftovers are not an antenna kit.
- Roaming or dual-SIM features can improve carrier diversity. Two SIMs in one radio still may share one antenna, one power supply, and one enclosure. That can be excellent engineering and still not be two independent NFPA 72 communications paths if a single failure kills both SIMs.
- Monthly carrier service is a subscriber cost. The license question is whether the path is listed, supervised, and accepted — not whether the monitoring rate is cheap.
Cellular as a single fire path is commonly taught as permitted when the communicator meets performance-based NFPA 72 rules and the AHJ accepts it. Dual-path is what many insurers and many local officials still want. Those are different sentences. Do not merge them into “NFPA 72 always requires IP plus cell.”
Dual-path — IP plus cellular as the teaching example
Dual-path means two independent transmission methods. The exam-friendly example is IP primary and cellular backup (or the reverse). Other listed pairs exist: cellular plus radio, IP plus radio. Two flavors of the same technology that share a single point of failure are the exam trap.
Independence, as commonly taught:
- A cut Ethernet cable must not also kill the cellular radio (do not power the cell communicator only from the same uninterruptible IT switch that feeds the Ethernet port).
- A carrier outage must not also kill the IP path.
- A single modem, a single power strip, or a single unlisted translator that both paths must pass through is one means wearing two hats.
- The communicator must be able to select the operable means if the other means has failed.
NFSA and similar NFPA 72 teaching materials put it this way: when multiple communication paths are used, a single point of failure in the monitoring network must not take down the alternative channel. Draw the riser. If one red circle kills both arrows, it is not dual-path.
Dual-path is not a claim that every occupancy in New York must have two technologies. It is the arrangement that satisfies multiple-path supervision (longer check-in) and that many AHJs and insurers expect. Ask the AHJ. Do not invent a DOS dual-path statute.
Supervision intervals — commonly taught NFPA 72 figures, not unique NY minutes
Path supervision is how the supervising station knows the communicator is still there when nothing is in alarm. A missed check-in becomes a trouble (often a failure to test or communications-fail event).
Cite minute and hour values as commonly taught NFPA 72 communicator supervision. Do not fabricate a unique New York minute that does not appear in NFPA 72 or DOS.
| Arrangement | Commonly taught supervision | Where candidates mix it up |
|---|---|---|
| DACT analog, legacy teaching | Automatic test signal at least once every 24 hours | Still true as history; later DACT teaching often uses 6-hour tests of telephone means |
| DACT, two telephone means, later teaching | Each telephone means tested; commonly taught alternating 6-hour tests | Not a burglary 24-hour timer |
| Single communications path (IP or cellular as the sole fire path), NFPA 72 2016 and later, including NFPA 72-22 as referenced by the 2025 Uniform Code | Path monitored at intervals not exceeding 60 minutes; failure indicated at the supervising station within that window; trouble also indicated at the protected premises | Candidates recite 5 minutes from an older edition and call it current |
| Single communications path, older teaching (NFPA 72-2010 is commonly cited) | 5-minute supervision | Still appears in old study notes; not the 2016+ performance-based number |
| Multiple communications paths | Each path timer-tested at intervals not exceeding 6 hours | Not 60 minutes per path and not 24 hours per path |
| Burglary / intrusion communicator (typical security listing practice) | Often a 24-hour test / check-in unless a higher line-security product is specified | Fire single-path IP is not “just use the burg timer” |
Read that table twice. The 5-minute figure is real teaching from an older NFPA 72 single-path rule. The 60-minute figure is the commonly taught current performance-based single-path rule. The 6-hour figure is commonly taught multiple-path (and some DACT telephone-means) testing. The 24-hour figure is the legacy DACT daily test and the usual burglary test. Putting 24 hours on a fire-only IP communicator as its only supervision is the classic miss.
The DOS bulletin does not print these minutes. The 2025 Uniform Code’s reference to NFPA 72—22 is why 60 minutes / 6 hours is the currently adopted New York code-book pair for new work under that code. Local amendments and AHJ conditions can be more restrictive (for example, refusing a single path). They do not create a secret DOS stopwatch.
Fire versus burglary versus panic on the same dual-path box
A combination control may send fire, burglary, and panic/holdup through one listed communicator. The fire path still has to meet fire supervision. A burglary partition that checks in every 24 hours does not relax the fire communicator’s 60-minute or 6-hour job.
Panic and holdup are typically silent at the premises (no siren) and go to police, not to the fire service. Fire waterflow goes to the fire communications center path. Programming the wrong Contact ID family, or mapping a fire zone into a burglary area, is how a smoke detector becomes a police dispatch — or worse, a log-only event. That programming is 195.1 work (Section 10.1 and Chapter 19).
Failure-to-test is a signal, not a suggestion
If the automatic test or heartbeat does not arrive, the supervising station must treat it as a communications trouble. Someone licensed has to investigate. Programming the panel to ignore fail-to-test, stretching a fire timer to a burglary 24-hour interval “to stop the trouble tickets,” or disabling the secondary path because the SIM bill is annoying is not a customer courtesy. It is taking the system off the supervised path the AHJ accepted.
Remote programming of timers, account numbers, and backup paths is still off-site assisting / servicing under 195.1. A monitoring clerk with a dealer portal is not an exemption from the installer license. The licensed business remains responsible.
Exam traps
- Reciting 5-minute single-path supervision as if every NFPA 72 edition still used it.
- Reciting 24-hour fire IP supervision because “all communicators test daily.”
- Calling two SIMs in one radio “dual-path” when they share one power supply and one antenna.
- Powering the fire communicator from the IT PoE switch and calling it secondary power.
- Inventing a New York-only 90-second or 3-minute cellular rule.
- Treating dual-path as a DOS statute rather than NFPA 72 / AHJ / insurer practice.
When you can name IP, LTE, independent dual-path, and the 60-minute / 6-hour / 24-hour / 5-minute teaching set without inventing a NY minute, you have the modern half of alarm transmission. Section 10.3 is who answers the phone and what each signal type means.
For a listed fire communicator used as a single communications path, which interval is commonly taught NFPA 72 performance-based supervision in the 2016 and later editions, including NFPA 72-22 as referenced by the 2025 Uniform Code?
A dual-path fire communicator uses building Ethernet and LTE. Which arrangement matches the commonly taught independent-path idea?
Programming a fire communicator’s automatic test interval and failure-to-test response is which of the following under 19 NYCRR 195.1?