Source record · tier 1 standards and regulators
47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication)
- Publisher
- Legal Information Institute, Cornell Law School (republishing eCFR)
- URL
- https://www.law.cornell.edu/cfr/text/47/9.16
- Published
- 2020-12-03
- Updated
- unknown
- Accessed
- 2026-09-24
- HTTP status
- 200
- License
- US government work (public domain); LII presentation; public domain text; short excerpts and locators only by corpus convention
Source notes citing this source
- 47 CFR 9.16(b)(1) requires that an MLTS user be able to call 911 directly without dialing any extra digit, code, prefix or suffix. in context
- 47 CFR 9.16(b)(3) required automated dispatchable location for on-premises fixed telephones by 2021-01-06 and for on-premises non-fixed and off-premises devices by 2022-01-06. in context
- 47 CFR 9.16(b)(2) requires MLTS notification of a 911 call to a central location or other person, sent at the same time as the call where feasible, without delaying the call, and to a place where someone is likely to see or hear it. in context
- Inference: at a US site that uses 9 as the outside code, the 9.911 pattern has to be added alongside a working bare 911, not instead of it, because 9.16(b)(1) forbids requiring a prefix; Cisco's example keeps both 911 and 9.911 translation patterns. inferred in context
- Inference: Emergency Responder onsite alerts (phone, web, email) are the built-in mechanism a CER deployment can use toward the 9.16(b)(2) notification requirement; whether a given alert setup satisfies the rule depends on where alerts are seen, which Cisco's guide does not assess. inferred in context
- US rules for multi-line telephone systems require that a user can dial 911 directly from any station, without any additional digit, code, prefix or post-fix. in context
- US MLTS rules require automated dispatchable location for fixed on-premises devices, and for non-fixed and off-premises devices automated dispatchable location where technically feasible, otherwise location from an end-user manual update (or enhanced location information off-premises). in context
- US MLTS rules require that a user can dial 911 directly from any station without any additional digit, code, prefix or post-fix. in context
- US MLTS rules require automated dispatchable location from on-premises fixed phones (from 6 January 2021) and, for non-fixed and off-premises devices, automated dispatchable location where technically feasible or else a manually updated one (from 6 January 2022). in context
- US MLTS rules require the system to send a notification to a central location at the facility, or to another person or organization, when 911 is called. in context
- 47 CFR 9.16(b)(1) requires an MLTS to be installed and configured so a user can directly initiate a 911 call from any station without dialing an additional digit, code, prefix or post-fix. in context
- 47 CFR 9.16(b)(3) requires MLTS dispatchable location to be conveyed with 911 calls from on-premises fixed devices by January 6, 2021, and from on-premises non-fixed and off-premises devices by January 6, 2022. in context
- The text of 47 CFR 9.16 as read for this packet contains no requirement to perform or document 911 or 933 test calls, so test cadence and records are set by vendor, carrier or state guidance rather than this federal section. inferred in context
- 47 CFR 9.16(b)(2) requires MLTS notification to be initiated contemporaneously with the 911 call, not to delay the call, and to go to a location where someone is likely to see or hear it. in context
- 47 CFR 9.16(b)(1) requires an MLTS to let a user dial 911 directly from any station with dialing facilities, without any additional digit, code, prefix or post-fix. in context
- 47 CFR 9.16(b)(3) requires automated dispatchable location from fixed on-premises MLTS devices by 2021-01-06, and sets 2022-01-06 for non-fixed on-premises and off-premises devices, with alternative location information allowed where automation is not technically feasible. in context
- 47 CFR 9.16(b)(2) requires MLTS notification to a central location at the facility; the notification must be contemporaneous with the 911 call and must not delay it. in context
- A person installing, managing or operating an MLTS must configure it so a user can directly initiate a 911 call from any station without dialing any additional digit, code, prefix or post-fix, including a trunk-access code such as 9. in context
- An on-premises fixed telephone associated with an MLTS must provide automated dispatchable location no later than January 6, 2021. in context
- An MLTS installer may not install a system in the United States unless it can be programmed with and convey the caller's dispatchable location to the PSAP with 911 calls. in context
- From January 6, 2022 an on-premises non-fixed MLTS device must provide automated dispatchable location when technically feasible, and otherwise dispatchable location based on end-user manual update or alternative location information. in context
- MLTS notification must be initiated at the same time as the 911 call where technically feasible, must not delay the 911 call, and must go to a location where someone is likely to see or hear it. in context
- From January 6, 2022 an off-premises MLTS device must provide automatic dispatchable location if technically feasible, and otherwise dispatchable location based on end-user manual update or enhanced location information. in context
- Under 47 CFR 9.16(b)(1), an MLTS must let users dial 911 directly without any prefix, suffix or trunk-access code such as 9. in context
- 47 CFR 9.16(b)(3) required automated dispatchable location for fixed MLTS devices by January 6, 2021 and for on-premises non-fixed and off-premises devices by January 6, 2022, with manual or alternative location allowed where automatic is not technically feasible. in context
- Under 47 CFR 9.16(b)(2), MLTS notification must start at the same time as the 911 call where technically feasible, must not delay the call, and must reach a place where someone is likely to see or hear it. in context
- 47 CFR 9.16(b)(1) and (b)(2) require MLTS to be configured so 911 can be dialled directly without any prefix or extra code, and to send notification at the same time as the 911 call, without delaying it, to a place where someone is likely to see or hear it. in context
- Under 47 CFR 9.16(b)(3)(i), on-premises fixed MLTS telephones had to provide automated dispatchable location no later than January 6, 2021. in context
- Under 47 CFR 9.16(b)(3)(ii), from January 6, 2022 an on-premises non-fixed MLTS device must give automated dispatchable location when technically feasible, and otherwise a dispatchable location based on the end user's manual update or alternative location information. in context
- Under 47 CFR 9.16(b)(3)(iii), from January 6, 2022 an off-premises device on a multi-line telephone system must give the PSAP automatic dispatchable location if technically feasible, and otherwise either a dispatchable location based on the end user's manual update or enhanced location information, which may be coordinate-based. in context
- 47 CFR 9.16(b)(1) requires an MLTS to be configured so users can call 911 directly from any station with dialing facilities, without dialing any additional digit, code, prefix or post-fix. in context
- 47 CFR 9.16(b)(3) requires an MLTS to convey dispatchable location to the PSAP, with compliance dates of January 6, 2021 for fixed devices and January 6, 2022 for non-fixed on-premises and off-premises devices. in context
- 47 CFR 9.16(b)(2) requires an MLTS that can do so without an improvement to its hardware or software to notify a central location or another person when a 911 call is made, at the same time as the call and without delaying it. in context
- 47 CFR 9.16 requires a multi-line telephone system to be configured so a user can dial 911 directly from any station without any additional digit, code, prefix or post-fix. in context
- 47 CFR 9.16(b)(3) requires automated dispatchable location from on-premises fixed MLTS telephones by 6 January 2021, and from on-premises non-fixed and off-premises devices by 6 January 2022 where technically feasible, otherwise allowing end-user manual update or alternative or enhanced location information. in context
- 47 CFR 9.16(b)(3) requires fixed on-premises MLTS devices to provide automated dispatchable location from January 6, 2021, and non-fixed on-premises and off-premises devices from January 6, 2022; for non-fixed devices automated location is required where technically feasible, otherwise a manual end-user update or alternative/enhanced location information. in context
- Under 47 CFR 9.16(b)(2), MLTS notification of a 911 call must start at the same time as the call where technically feasible, must not delay the call, and must be sent to a place where someone is likely to see or hear it. in context
- Anyone installing, managing or operating an MLTS in the US must configure it so users can dial 911 directly without any prefix such as a trunk-access 9. in context
- An on-premises fixed telephone on an MLTS must provide automated dispatchable location, required no later than January 6, 2021. in context
- MLTS operators must configure the system to send MLTS notification to a central location at the facility or to another person or organisation, where the system can do so without hardware or software improvement. in context
- MLTS notification must be initiated contemporaneously with the 911 call where technically feasible. in context
- From January 6, 2022, an off-premises MLTS device must provide automatic dispatchable location if technically feasible, otherwise dispatchable location via manual update or enhanced location information. in context
- From January 6, 2022, an on-premises non-fixed MLTS device must provide automated dispatchable location when technically feasible, otherwise dispatchable location via manual user update or alternative location information. in context
Cite this source record
APA
WarmTransfer. (2020, December 3). 47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication). WarmTransfer. https://warmtransfer.net/knowledge/sources/cornell-lii-47-cfr-9-16
BibTeX
@misc{warmtransfer-cornell-lii-47-cfr-9-16,
title = {47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication)},
author = {{WarmTransfer}},
year = {2020},
url = {https://warmtransfer.net/knowledge/sources/cornell-lii-47-cfr-9-16},
note = {Legal Information Institute, Cornell Law School (republishing eCFR), accessed 2026-09-24}
}