# Managed facilities-based voice network

> A managed facilities-based voice network (MFVN) is NFPA 72's term for a voice network that a provider physically operates and actively manages end-to-end — delivering dial tone and signaling compatibility equivalent to traditional public switched telephone service, including backup power for its field equipment.

- Also known as: MFVN
- Last reviewed: July 30, 2026

## How it works

NFPA 72 allows a DACT to report over an MFVN because the network behaves like the loop-start telephone service the DACT was designed for: real dial tone, compatible signaling, engineered availability, and managed field power. A provider qualifies by how its network is built and operated — over its own facilities with defined management practices — rather than by what marketing name the service carries.

## Why it matters

When a copper POTS line is replaced, whether the replacement path presents MFVN-equivalent service determines whether an existing DACT can keep reporting the way it always has. That makes MFVN one of the quiet load-bearing definitions in alarm-panel POTS migrations — and one worth confirming with the monitoring provider and the authority having jurisdiction.

## Common use cases

- Qualifying a voice service to carry DACT alarm traffic under NFPA 72
- Evaluating POTS-replacement paths for supervised alarm accounts

Whether a specific POTS-replacement service is accepted as MFVN-equivalent for a given alarm
account is a determination made by the code edition in force, the monitoring provider, and
the authority having jurisdiction — not by the equipment vendor.

## Why the determination is not the vendor's to make

MFVN is a term of art from NFPA 72, and whether a given service satisfies it for a given alarm
account is decided by the code edition the jurisdiction has adopted and by the AHJ applying it —
not by a vendor's characterization of its own product.

That has a practical consequence for procurement. A claim that a service "is MFVN" or "meets
MFVN" is not verifiable in the way a certification number is; it is an assertion about how a
code provision applies. Treat it as a starting point for a conversation with the AHJ rather than
as a settled fact.

What you can do is assemble the evidence the determination will rest on: the specific models
proposed and their certification records, how the path is supervised and at what interval, what
backup power is provided and for how long, and how a failure is detected and reported.

Bring that to the AHJ early. A determination obtained in writing before installation is worth
considerably more than an argument made at final inspection.

## Common misconceptions

**Claim:** Any VoIP service counts as an MFVN.

**Correction:** Over-the-top VoIP running on someone else's unmanaged broadband generally does not qualify — the M and the F both matter: the provider must manage the service and provide the facilities, including powering its field equipment during outages.

## Frequently asked questions

**Why does NFPA 72 care how the voice network is built?**

Because a DACT's reporting reliability depends on the line behaving like traditional telephone service under failure conditions — dial tone during a power outage, consistent signaling, and a provider who notices and fixes degradation. The MFVN definition encodes those expectations.

## Sources

- [NFPA 72: National Fire Alarm and Signaling Code](https://www.nfpa.org/codes-and-standards/nfpa-72-standard-development/72) — National Fire Protection Association


---

Canonical page: https://dataremote.com/newsroom/definitions/managed-facilities-based-voice-network
Organization: DataRemote, Inc. — POTS line replacement, cellular failover, and fixed wireless access solutions. https://dataremote.com