Maine ME
Maine has one of the more detailed PBX/MLTS rule sets in the PDF, with hotel, shared residential, alternative-method, signage, ALI update, and waiver concepts.
What matters before you deploy or audit E911 in Maine
- Maine authorizes Public Utilities Commission rules for locating 911 calls from MLTS and VoIP-style systems.
- The statute is less prescriptive than some states, so the operating detail is in Maine PUC/ESCB rules and local process.
- Enterprise sites should verify whether a system was installed, introduced, established, or replaced after applicable rules.
How detailed should the dispatchable location be?
No state square-foot maximum was found in 25 M.R.S. § 2934 itself. Use federal dispatchable-location rules plus Maine PUC/ESCB MLTS rules for site-specific interpretation.
Exact law callouts
Short excerpts are included for orientation. Follow the links for the complete statutory or regulatory text.
Direct 911 dialing
47 C.F.R. § 9.16(b)(1)“without dialing any additional digit, code, prefix, or post-fix”
Covered MLTS environments should support plain 911 dialing from every station with dialing capability. Old PBX habits such as 9-911 are a compliance red flag.
On-site or responsible-party notification
47 C.F.R. § 9.16(b)(2)“must not delay the call to 911”
Security desk, reception, facilities, or crisis teams can be notified, but notification cannot hold or reroute the emergency call before it reaches public safety.
Dispatchable location for MLTS
47 C.F.R. § 9.16(b)(3)“conveying the dispatchable location of the caller to the PSAP”
The enterprise has to maintain usable location records, not merely a billing address or main switchboard number.
Maine MLTS rule authority
25 M.R.S. § 2934(1)“requirements for locating 9-1-1 calls”
Maine compliance depends on both the statute and PUC rules for multiline systems, including VoIP systems.
Maine rule scope
25 M.R.S. § 2934(1)(B)“installed, introduced, established or replaced”
Phone-system refreshes, replacements, and cloud migrations should trigger an E911 review.
911 context
Maine's Chapter 11 material is operationally specific. It recognizes PBX/MLTS environments, emergency response locations, hotel/motel use, shared residential environments, alternative methods, exemptions, and PSAP-facing location data.
911 authority and routing model
MLTS operators should design around direct 911 access, useful callback/location delivery, and documented instructions where location is not automatically distinctive enough. Hotels and similar properties need procedures that connect the caller, PSAP, and knowledgeable staff when required.
Location delivery approach
ALI/database records should be updated promptly after new installations and physical changes. The summary describes updates as soon as practical and, in some cases, within one business day after the relevant record or change is complete.
Dispatchable location area / square-footage rule
Maine uses a 40,000 sq ft workspace rule for business MLTS. A building with 40,000 sq ft or less can generally be represented by one ANI/ALI with the street address. Buildings over 40,000 sq ft need one ANI and one ERL per 40,000 sq ft of workspace; multi-floor, multi-tenant, and multi-building sites may need ERLs by floor, entity, and building.
State-specific differences
Maine is special because it reads like an operational checklist: direct dialing, ERLs, hotel/motel handling, alternative notification, signage or stickers, instructions to stay on the line, exemptions, and waivers all appear in the summary.
Regulatory references
Privacy and records considerations
911 location records, callback numbers, test-call results, and site inventories should be treated as sensitive safety data. Limit access, keep change history, and align retention with state public-records rules, customer contracts, and incident-response needs.