State MLTS 911 laws beyond Kari's Law

See also

Sources

1. 1
   560 CMR 4.05 requires an MLTS operator to update the ALI or NG911 location database when a fixed device moves, as soon as practicable for new systems and within one business day after relocation for existing systems.

   560 CMR, § 4.05 - ALI Database Maintenance · 560 CMR 4.05 · Checked 2026-10-14
2. 2
   560 CMR 4.04 requires new or substantially renovated MLTS in Massachusetts, beginning July 1, 2009, to provide the same level of enhanced 911 service as other end users, including ALI and ANI, a call back number and dispatchable location.

   560 CMR, § 4.04 - Standards Governing Multi-line Telephone Systems · 560 CMR 4.04, opening paragraph and (a)-(c) · Checked 2026-10-14
3. 3
   560 CMR 4.03 treats an MLTS as substantially renovated if its incoming line or station capacity rises by more than 50% on or after July 1, 2009, or if all or substantially all of its hardware, structural or operating components are upgraded or replaced on or after that date.

   560 CMR, § 4.03 - Definitions · 560 CMR 4.03, definition of 'Substantially Renovated' · Checked 2026-10-14
4. 4
   560 CMR 4.04 requires an instructional sticker adjacent to each non-compliant device with outbound dialing, printed in at least 12-point boldface type in a contrasting color and in English and Spanish.

   560 CMR, § 4.04 - Standards Governing Multi-line Telephone Systems · 560 CMR 4.04, instructional sticker paragraph · Checked 2026-10-14
5. 5
   Maine §2934 was last amended by PL 2025, c. 167, §36, after earlier amendments by PL 2017 c. 48 and PL 2019 c. 339.

   Title 25, §2934. Multiline telephone systems · §2934 section history · Checked 2026-10-14
6. 6
   Maine §2934-A was enacted by PL 2017, c. 48, §2.

   Title 25, §2934-A. Emergency calling from multiline telephone systems · §2934-A section history · Checked 2026-10-14
7. 7
   Maine 25 M.R.S. §2934-A(1) requires an entity that installs or operates a multiline telephone system to configure it so a 9-1-1 call connects to the public safety answering point without the user dialing any other number first.

   Title 25, §2934-A. Emergency calling from multiline telephone systems · §2934-A, sub-§1 Direct dialing of 911 · Checked 2026-10-14
8. 8
   Maine §2934-A(1) does not apply to a local unit of government where compliance would require additional expenditures from local revenues.

   Title 25, §2934-A. Emergency calling from multiline telephone systems · §2934-A, sub-§1 · Checked 2026-10-14
9. 9
   Maine §2934-A(2) gives entities one year after the section's effective date to comply, or, if their system cannot comply, until the system is next upgraded to one that can.

   Title 25, §2934-A. Emergency calling from multiline telephone systems · §2934-A, sub-§2 Compliance period · Checked 2026-10-14
10. 10
    Maine 25 M.R.S. §2934(1) authorizes the Public Utilities Commission to adopt rules for locating 9-1-1 calls and initiating emergency responses from multiline telephone systems, including network-based, premises-based and VoIP systems.

    Title 25, §2934. Multiline telephone systems · §2934, sub-§1 · Checked 2026-10-14
11. 11
    Maine §2934(1)(C) requires the rules to include standards, exemptions and waivers that balance location benefits against cost and to allow, where appropriate, location methods that do not use ALI and ANI standards.

    Title 25, §2934. Multiline telephone systems · §2934, sub-§1, ¶C · Checked 2026-10-14
12. 12
    Rules adopted under Maine §2934 apply only to multiline telephone systems installed, introduced, established or replaced after the rules' effective date.

    Title 25, §2934. Multiline telephone systems · §2934, sub-§1, ¶B · Checked 2026-10-14
13. 13
    Michigan county guidance that still cites 7,000-square-foot or 20-device MLTS thresholds probably reflects the rescinded R 484.901-906 rules rather than current state law, which now points to the federal rules.inferred

    MCL 484.1413 Rules; applicability to service suppliers; multiline telephone system compliance with federal regulations; multiline telephone system defined · MCL 484.1413(5) and compiler's note · Checked 2026-10-14
14. 14
    Michigan MCL 484.1413(5) requires a multiline telephone system to comply with the most current version of 47 CFR 9.15 to 9.17.

    MCL 484.1413 Rules; applicability to service suppliers; multiline telephone system compliance with federal regulations; multiline telephone system defined · MCL 484.1413(5) · Checked 2026-10-14
15. 15
    MCL 484.1413 is repealed by Michigan Public Act 126 of 2021 effective December 31, 2027.

    MCL 484.1413 Rules; applicability to service suppliers; multiline telephone system compliance with federal regulations; multiline telephone system defined · MCL 484.1413 status note · Checked 2026-10-14
16. 16
    Enacting section 2 of Michigan Public Act 30 of 2019 rescinded the state's MLTS administrative rules, R 484.901 to R 484.906.

    MCL 484.1413 Rules; applicability to service suppliers; multiline telephone system compliance with federal regulations; multiline telephone system defined · MCL 484.1413 compiler's note · Checked 2026-10-14
17. 17
    Minnesota 403.15 subd. 8 applies subds. 4, 5 and 6 only to new systems purchased after December 31, 2004, while subds. 2 and 3 and the subd. 7 exemptions apply regardless of when the system was installed.

    Minnesota Statutes 403.15 Multiline Telephone System 911 Requirements · 403.15 subd. 8 · Checked 2026-10-14
18. 18
    For a single employer's business multiline system, Minnesota 403.15 subd. 5(a) accepts any of three outcomes for 911 calls: ALI for each emergency response location, an alternative means of directing responders, or a switchboard operator, attendant or other on-site designee.

    Minnesota Statutes 403.15 Multiline Telephone System 911 Requirements · 403.15 subd. 5(a) · Checked 2026-10-14
19. 19
    Minnesota 403.15 subd. 4 requires hotel and motel multiline system operators to allow 911 dialing and to ensure 911 calls identify the caller's address and specific location.

    Minnesota Statutes 403.15 Multiline Telephone System 911 Requirements · 403.15 subd. 4 · Checked 2026-10-14
20. 20
    Minnesota 403.15 subd. 2 requires each multiline telephone system operator to demonstrate or otherwise inform each new user how to call for emergency assistance from that system.

    Minnesota Statutes 403.15 Multiline Telephone System 911 Requirements · 403.15 subd. 2 · Checked 2026-10-14
21. 21
    Minnesota Statutes 403.15 subd. 1 requires every owner and operator of a new multistation or PBX multiline telephone system purchased after December 31, 2004 to design and maintain it to provide a callback number and an emergency response location.

    Minnesota Statutes 403.15 Multiline Telephone System 911 Requirements · 403.15 subd. 1 · Checked 2026-10-14
22. 22
    Minnesota 403.15 subd. 7 exempts systems with a single emergency response location and systems using alternative enhanced 911 methods from subds. 1 and 3 to 6, and lets an operator request an exemption from the chief officer of each serving PSAP.

    Minnesota Statutes 403.15 Multiline Telephone System 911 Requirements · 403.15 subd. 7(a)-(c) · Checked 2026-10-14
23. 23
    Minnesota 403.15 subd. 6 puts systems operated by public or private educational institutions, including dormitory systems, under their own subdivision rather than the shared-residential rule in subd. 3.

    Minnesota Statutes 403.15 Multiline Telephone System 911 Requirements · 403.15 subd. 6 · Checked 2026-10-14
24. 24
    Minnesota 403.15 subd. 3 requires shared residential multiline systems to connect to the public switched network so 911 calls produce at least one distinctive ANI and ALI per residential unit, unless the facility uses ALI per emergency response location, an alternative such as a 24-hour private answering point, or an on-site attendant.

    Minnesota Statutes 403.15 Multiline Telephone System 911 Requirements · 403.15 subd. 3 · Checked 2026-10-14
25. 25
    Minnesota 403.15 subd. 5(c) requires only one emergency response location when an employer's work space is less than 40,000 square feet on a single floor of one contiguous property.

    Minnesota Statutes 403.15 Multiline Telephone System 911 Requirements · 403.15 subd. 5(c)(1) · Checked 2026-10-14
26. 26
    Minnesota 403.15 subd. 5(c) also requires only one emergency response location when the work space is less than 7,000 square feet spread over multiple floors of one contiguous property, or is a single-floor facility with a single public entrance.

    Minnesota Statutes 403.15 Multiline Telephone System 911 Requirements · 403.15 subd. 5(c)(2)-(3) · Checked 2026-10-14
27. 27
    Texas 771A.001(d) requires a business service user that provides residential or business facilities to configure its system to notify a central location on the site when a person dials 9-1-1.

    Health and Safety Code Chapter 771A, Sec. 771A.001 Direct Access to 9-1-1 Service Required · Sec. 771A.001(d) · Checked 2026-10-14
28. 28
    Texas Health and Safety Code 771A.001(c) requires a business service user that owns or controls a telephone system or equivalent Internet Protocol enabled system with outbound dialing to configure it so a caller reaches 9-1-1 by dialing only 9-1-1, with no added code, digit, prefix, postfix or trunk-access code.

    Health and Safety Code Chapter 771A, Sec. 771A.001 Direct Access to 9-1-1 Service Required · Sec. 771A.001(c) · Checked 2026-10-14
29. 29
    Texas Health and Safety Code 771A.001 was added by Acts 2015, 84th Legislature, Chapter 21 (S.B. 788), effective May 15, 2015.

    Health and Safety Code Chapter 771A, Sec. 771A.001 Direct Access to 9-1-1 Service Required · Sec. 771A.001 history note · Checked 2026-10-14
30. 30
    Texas 771A.001(b) applies the section only to the extent it is consistent with, and not preempted by, federal law.

    Health and Safety Code Chapter 771A, Sec. 771A.001 Direct Access to 9-1-1 Service Required · Sec. 771A.001(b) · Checked 2026-10-14
31. 31
    The Texas on-site notification duty in 771A.001(d) applies only if it can be met without hardware improvements, and it does not require anyone to be present at the central location to receive the notification.

    Health and Safety Code Chapter 771A, Sec. 771A.001 Direct Access to 9-1-1 Service Required · Sec. 771A.001(d) · Checked 2026-10-14
32. 32
    A Texas waiver requires the business service user to file an affidavit by September 1 each year stating the system manufacturer and model number and that it made a good-faith attempt to reprogram or replace the system.

    Health and Safety Code Chapter 771A, Sec. 771A.001 Direct Access to 9-1-1 Service Required · Sec. 771A.001(e) · Checked 2026-10-14
33. 33
    Under Texas 771A.001(e), the Commission on State Emergency Communications or the applicable emergency communication district must grant a one-year waiver of the direct-dial requirement when compliance would be unduly and unreasonably cost prohibitive.

    Health and Safety Code Chapter 771A, Sec. 771A.001 Direct Access to 9-1-1 Service Required · Sec. 771A.001(e) · Checked 2026-10-14
34. 34
    During a Texas waiver, the user must place an instructional sticker next to each non-compliant telephone, in at least 16-point boldface type in a contrasting color, explaining how to reach 9-1-1.

    Health and Safety Code Chapter 771A, Sec. 771A.001 Direct Access to 9-1-1 Service Required · Sec. 771A.001(e) · Checked 2026-10-14
35. 35
    Virginia Code § 56-484.23(C) requires ALI database updates for each station as soon as practicable for new installations and within one business day of record completion of changes for existing systems, and puts that duty on the MLTS service provider where one is used.

    Code of Virginia § 56-484.23. Provision of emergency call information · § 56-484.23(C) · Checked 2026-10-14
36. 36
    Virginia Code § 56-484.19 deems an alternative method of providing call location information to be provided when calling party information covers a contiguous area of fewer than 7,000 square feet on one or more floors.

    Code of Virginia § 56-484.19. Definitions · § 56-484.19, definition of 'Alternative method of providing call location information' · Checked 2026-10-14
37. 37
    Virginia Code § 56-484.23(A) requires an MLTS acquired or installed on or after July 1, 2009 to deliver, for each emergency call from any station, either calling party information to the 9-1-1 network or an alternative method of providing call location information.

    Code of Virginia § 56-484.23. Provision of emergency call information · § 56-484.23(A) · Checked 2026-10-14
38. 38
    Meeting Virginia § 56-484.22 alone does not establish federal compliance, because its text still contemplates an access digit before 9-1-1 while the federal Kari's Law rule requires direct dialing without a prefix.inferred

    Code of Virginia § 56-484.22. Access to PSAPs from telephone stations on MLTS · § 56-484.22 · Checked 2026-10-14
39. 39
    Commencing July 1, 2009, Virginia Code § 56-484.21 requires an MLTS provider either to demonstrate or give written emergency-calling instructions to each new user or to post written instructions at each station, including the station's street address and enough detail for responders to find it.

    Code of Virginia § 56-484.21. Instructions for emergency calling · § 56-484.21 · Checked 2026-10-14
40. 40
    Virginia Code § 56-484.20 requires the MLTS provider to maintain and operate the system so a person placing an emergency call from any station is not charged for the call.

    Code of Virginia § 56-484.20. Charges for emergency calls · § 56-484.20 · Checked 2026-10-14
41. 41
    For an MLTS using portable VoIP services, Virginia Code § 56-484.23(B) requires only reasonable efforts to meet the emergency call information requirement.

    Code of Virginia § 56-484.23. Provision of emergency call information · § 56-484.23(B) · Checked 2026-10-14
42. 42
    Virginia Code § 56-484.22, as printed, requires from July 1, 2009 that a call dialed as 9-1-1 plus any additional digit needed to reach the public network be routed to a PSAP.

    Code of Virginia § 56-484.22. Access to PSAPs from telephone stations on MLTS · § 56-484.22 · Checked 2026-10-14
43. 43
    The Vermont rule defines an enterprise communications system to include circuit-switched, IP-based and cloud-based systems serving two or more stations or living units, across businesses, government, shared residential facilities and schools.

    31-004 Code Vt. R. 31-010-004-X - 9-1-1 Requirements for Enterprise Communications Systems · Rule § 3.3 · Checked 2026-10-14
44. 44
    The Vermont rule requires ALI to be validated against the Vermont LVF or a Board-approved GIS process, discrepancies resolved within two business days, and location data audited at least annually.

    31-004 Code Vt. R. 31-010-004-X - 9-1-1 Requirements for Enterprise Communications Systems · Rule §§ 5.1, 5.3, 5.4 · Checked 2026-10-14
45. 45
    The Vermont rule requires each station's ALI to carry a call back number and a dispatchable location (verified street address and community name plus floor if applicable and the more granular of suite, apartment or room) that matches a location physically posted in the facility.

    31-004 Code Vt. R. 31-010-004-X - 9-1-1 Requirements for Enterprise Communications Systems · Rule §§ 3.5, 4.3, 4.4 · Checked 2026-10-14
46. 46
    The Vermont Enhanced 911 Board rule '9-1-1 Requirements for Enterprise Communications Systems', adopted under 30 V.S.A. § 7057, took effect July 1, 2019.

    31-004 Code Vt. R. 31-010-004-X - 9-1-1 Requirements for Enterprise Communications Systems · Rule § 1.0 and page notes (Rule Log #19-025) · Checked 2026-10-14
47. 47
    For remote or mobile ECS users, the Vermont rule requires that users be able to dial 9-1-1 through the device's native phone app and mobile network where capable, and that an accurate dispatchable location be provided if 9-1-1 is reachable only through the ECS.

    31-004 Code Vt. R. 31-010-004-X - 9-1-1 Requirements for Enterprise Communications Systems · Rule § 4.7 · Checked 2026-10-14
48. 48
    Under the Vermont rule, any single room larger than 10,000 square feet needs additional location detail such as a number, cubicle number, signage or other landmark.

    31-004 Code Vt. R. 31-010-004-X - 9-1-1 Requirements for Enterprise Communications Systems · Rule § 3.5 · Checked 2026-10-14
49. 49
    30 V.S.A. § 7057 requires any enterprise communications system to provide its end users the same level of 911 service that other end users receive.

    30 V.S.A. § 7057. Enterprise communications system · 30 V.S.A. § 7057 · Checked 2026-10-14
50. 50
    30 V.S.A. § 7057 requires enterprise communications systems to provide ANI signaling, station identification data including dispatchable location, and E911 database updates under Enhanced 911 Board rules, and lets the Board waive these for a system working toward compliance.

    30 V.S.A. § 7057. Enterprise communications system · 30 V.S.A. § 7057 · Checked 2026-10-14
51. 51
    Washington RCW 38.52.505 directs the adjutant general to adopt rules setting minimum information requirements for automatic location identification for 911 calls.

    RCW 38.52.505 Statewide 911 emergency service—Automatic location identification—Rules · RCW 38.52.505 · Checked 2026-10-14
52. 52
    Under RCW 38.52.505, the local fire chief, chief fire protection officer or another person the city or county designates may approve the accuracy of location information for 911 calls from facilities in their service area.

    RCW 38.52.505 Statewide 911 emergency service—Automatic location identification—Rules · RCW 38.52.505 · Checked 2026-10-14
53. 53
    Chapter 118-68 WAC was last amended by WSR 24-13-025, filed June 7, 2024 and effective July 8, 2024, under RCW 38.52.520.

    Chapter 118-68 WAC Required for automatic location identification · Chapter 118-68 WAC statutory authority and filing history · Checked 2026-10-14
54. 54
    WAC 118-68-040 required facilities to comply by May 1, 2001, and additionally requires compliance with the FCC MLTS order (34 FCC Rcd 6607) by August 1, 2019.

    Chapter 118-68 WAC Required for automatic location identification · WAC 118-68-040 · Checked 2026-10-14
55. 55
    For congregate residences, hotels and motels, WAC 118-68-050(2)(b) accepts either the minimum ALI fields (customer name, street address and city, building unit identifier, call back number) or simultaneous connection of the caller, the PSAP and a designated individual who can supplement the location.

    Chapter 118-68 WAC Required for automatic location identification · WAC 118-68-050(2)(a)-(b) · Checked 2026-10-14
56. 56
    WAC 118-68-050(2)(c) requires 911 calls from systems serving multiple unaffiliated business users to display the business name, address, building unit identifier or more specific location, and call back number.

    Chapter 118-68 WAC Required for automatic location identification · WAC 118-68-050(2)(c) · Checked 2026-10-14
57. 57
    Chapter 118-68 WAC applies to facilities for which a certificate of occupancy is to be or has been approved by the authority having jurisdiction.

    Chapter 118-68 WAC Required for automatic location identification · WAC 118-68-030 · Checked 2026-10-14
58. 58
    WAC 118-68-050(3) requires covered entities also to follow the FCC rules under section 506 of RAY BAUM'S Act on dispatchable location regardless of technology platform.

    Chapter 118-68 WAC Required for automatic location identification · WAC 118-68-050(3) · Checked 2026-10-14
59. 59
    WAC 118-68-060 leaves fines and penalties to the local governing body and recommends $100 per day per telephone system until compliance.

    Chapter 118-68 WAC Required for automatic location identification · WAC 118-68-060 · Checked 2026-10-14

Documents

Cite this page

WarmTransfer. (2026, October 14). State MLTS 911 laws beyond Kari's Law. WarmTransfer. https://warmtransfer.net/knowledge/mlts-state-911-laws

@misc{warmtransfer-mlts-state-911-laws,
  title  = {State MLTS 911 laws beyond Kari's Law},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/mlts-state-911-laws},
  note   = {Verified 2026-10-14}
}