Source note · Cisco Emergency Responder setup
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 · Checked 2026-09-24
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- dial plan for Emergency Responder
- Deployment
- on-premises
- Region
- us
- Release range
- current as of 2026-09-24
- Status
- inferred
- Checked
- 2026-09-24
Sources
- 47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication) — Legal Information Institute, Cornell Law School (republishing eCFR) · tier 1 standards and regulators · 47 CFR 9.16(b)(1), read with Cisco CER 15 admin guide translation patterns for 9.911
Cite this note
APA
WarmTransfer. (2026, September 24). Cisco Emergency Responder setup: source note cisco-emergency-responder-setup-inf-911-plus-9911. WarmTransfer. https://warmtransfer.net/knowledge/claims/cisco-emergency-responder-setup-inf-911-plus-9911
BibTeX
@misc{warmtransfer-claim-cisco-emergency-responder-setup-inf-911-plus-9911,
title = {Cisco Emergency Responder setup: source note cisco-emergency-responder-setup-inf-911-plus-9911},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cisco-emergency-responder-setup-inf-911-plus-9911},
note = {Source note cisco-emergency-responder-setup-inf-911-plus-9911, checked 2026-09-24}
}