MLTS stands for multi-line telephone system. It's the legal term for almost any business phone system, from a hotel's PBX to Microsoft Teams. If your organization runs one, federal 911 rules decide how it has to handle emergency calls. This guide explains what counts as an MLTS, what the rules require, who is responsible, and what's changing as 911 moves to IP.
The short answer
An MLTS is a phone system that serves more than one line, typically in a hotel, office, retail store, school, or campus (FCC). If people at your organization can call each other by extension and also call outside numbers through a shared system, you almost certainly have one.
The legal definition
Federal law defines an MLTS as a system made up of common control units, telephone sets, control hardware and software, and adjunct systems. That includes network-based and premises-based systems such as Centrex and VoIP, as well as PBX, hybrid, and key telephone systems. It covers systems owned or leased by government agencies and nonprofits, not just businesses (47 U.S.C. 1471). The FCC's 911 rules use the same definition (FCC).
Two parts of that definition matter most in practice. First, it isn't limited to hardware in a closet: cloud and hosted systems count. Second, it isn't limited to companies: a city hall, a public university, or a nonprofit hospital is covered the same way a corporation is.
What counts as an MLTS
In practice, most enterprise calling platforms fall within the definition, including:
- On-premises call control, such as Cisco Unified Communications Manager and traditional PBXs.
- Cloud and hosted calling, such as Webex Calling and platforms built on Cisco BroadWorks.
- Collaboration platforms with calling. The FCC says that under some circumstances an MLTS can include platforms such as Microsoft Teams (FCC).
- Hospitality and campus systems that serve guest rooms, dorms, or patient rooms.
Softphones, desk phones, and wireless handsets on these systems are all part of the MLTS. So are users who connect from home, which is why the rules treat on-premises and off-premises devices differently.
Why MLTS 911 calls need their own rules
An MLTS sits between your users and the public phone network. That's what makes extension dialing and shared outside lines possible, but it also creates two problems for 911.
The first is dialing. Many systems were set up to require a prefix like 9 for an outside line. In 2013, Kari Hunt's 9-year-old daughter tried four times to call 911 from a Texas motel room and never got through, because the phone system required dialing 9 first (FCC).
The second is location. A 911 call from an MLTS has often carried only the number of the system's outgoing trunk, not the extension or the caller's actual location (Federal Register). A dispatcher might see the main address of a campus with dozens of buildings and no way to tell which one.
What the 911 rules require
Kari's Law and Section 506 of RAY BAUM's Act, as implemented by the FCC, require that an MLTS:
- Allows direct 911 dialing, with no prefix or access code such as 9.
- Sends a notification to a central location, such as a front desk or security office, when someone dials 911.
- Delivers the caller's location with the 911 call, so responders can find them (FCC).
The location requirement is called dispatchable location: the street address plus details such as floor and room. The rules differ for fixed desk phones, on-premises mobile devices, and off-premises devices. Our plain-English guide to Kari's Law and RAY BAUM's Act covers each requirement and deadline, and what counts as a dispatchable location goes deeper on location.
Who is responsible
The rules apply to MLTS manufacturers, importers, sellers, and lessors, and to the people who install, manage, and operate the systems (FCC). Manufacturers and vendors must ship systems pre-configured for direct 911 dialing. Installers, managers, and operators must make sure the system actually works that way once it's running (FCC).
For most organizations, that means the responsibility sits with you, your IT team, or the service provider that manages your system for you. Buying a compliant platform isn't the same as running a compliant one. The FCC has also made clear that when a service provider only carries 911 traffic and doesn't operate or manage the MLTS, the organization running the MLTS is responsible for meeting the 911 requirements (FCC DA 26-1043).
Older systems and the upgrade trigger
The rules are forward-looking. They apply to systems manufactured, imported, offered for first sale or lease, first sold or leased, or installed after February 16, 2020 (FCC). A system installed on or before that date may be exempt as a legacy MLTS, though state 911 laws may still apply.
That exemption is narrower than it sounds. The FCC says that upgrades to core MLTS software or hardware functions generally would be enough to bring an older system under the rules, even though not every minor improvement would (FCC). A cloud migration, a platform replacement, or a major version upgrade can end a system's legacy status. If you're planning one, read how a phone system migration resets your 911 compliance.
What NG911 means for older MLTS
As 911 networks move to Next Generation 911, some older systems are running into a new problem. On September 28, 2026, the FCC's Public Safety and Homeland Security Bureau issued guidance on NG911 for multi-line telephone systems (FCC DA 26-1043).
The guidance grew out of Verizon's NG911 testing in Massachusetts. Verizon found that 911 calls from some MLTS customers using a third-party Private Switch/Automatic Location Identification (PS/ALI) service were being delivered to a national call center instead of directly to the state's NG911 provider. The affected customers ran older TDM-based systems, and Verizon didn't have their location information (FCC DA 26-1043).
The notice has direct advice for MLTS operators and managers. If you run a TDM system with a third-party PS/ALI service, work with your carrier to make sure your 911 calls will be routed correctly and with enough caller location information. The FCC points out that operators and managers may be the only ones who have that location information. It also encourages TDM-based MLTS users to consider moving to IP-based systems, warning that they may be left behind as the country moves to all-IP networks (FCC DA 26-1043).
If your organization still runs a TDM-based system with a separate location service, ask your carrier and your location provider how your 911 calls will be routed as NG911 arrives in your state. Our explainer on what NG911 is covers the bigger picture.
A quick self-check
- Identify your system. List every calling platform you run, including softphones, collaboration tools with calling, and any hosted or carrier-managed service.
- Check the dates. Was each system installed, replaced, or substantially upgraded after February 16, 2020? If so, assume the federal rules apply.
- Dial 911 the way a visitor would. From each type of phone, plain 911 should work with no prefix.
- Confirm notification. Someone who will actually see or hear it should get an alert when 911 is dialed.
- Confirm location for every device type. Desk phones, wireless handsets, softphones, and remote users each follow different rules. See 911 compliance for remote workers.
- Test. Use 933 for quick checks of the address and callback number on file, and schedule live test calls with your 911 center. Our 911 testing guide explains both.
- Check your state. Some states have their own MLTS 911 laws on top of the federal rules.
Frequently asked questions
What does MLTS stand for?
Multi-line telephone system. It's the term federal law and the FCC use for business phone systems that serve more than one line.
Is Microsoft Teams an MLTS?
It can be. The FCC says that under some circumstances an MLTS can include communications platforms such as Microsoft Teams.
Do the rules apply to government agencies and nonprofits?
Yes. The legal definition covers systems owned or leased by government agencies and nonprofits as well as for-profit businesses.
Our phone system was installed before 2020. Do the rules apply?
Systems installed on or before February 16, 2020 may be exempt as legacy systems. But upgrades to core MLTS hardware or software generally bring a system under the rules, and state laws may still apply.
Who is responsible for MLTS 911 compliance?
Manufacturers and vendors must ship systems pre-configured for direct 911 dialing. The organizations and providers that install, manage, and operate the system must make sure it actually supports direct dialing, notification, and location.
How 9Line helps
9Line Dispatch brings Kari's Law and RAY BAUM's Act compliance to Cisco Unified CM, Microsoft Teams, and Cisco BroadWorks. It sends dispatchable location for desk phones, softphones, and remote users, and alerts your team the moment someone dials 911. Talk to us about your environment.
Sources
- Federal Communications Commission, FCC 911 Requirements for Multi-Line Telephone Systems (Public Safety and Homeland Security Bureau fact sheet).
- Federal Communications Commission, Multi-line Telephone Systems: Kari's Law and RAY BAUM'S Act 911 Requirements.
- 47 U.S.C. 1471, Definitions.
- Federal Register, Implementing Kari's Law and RAY BAUM'S Act, 84 FR 66716 (December 5, 2019).
- Federal Communications Commission, Public Notice DA 26-1043 (September 28, 2026).



