Source note · Enterprise dial plan design and normalization
RFC 3966 local numbers, such as PBX extensions, are unique only within a context and must carry a phone-context parameter that identifies the scope where they are valid.
Checked 2026-09-23
- Vendor
- IETF
- Product
- tel URI
- Subsystem
- number representation
- Deployment
- standard
- Region
- not restricted
- Release range
- RFC 3966
- Checked
- 2026-09-23
Sources
- RFC 3966: The tel URI for Telephone Numbers — IETF / RFC Editor · tier 1 standards and regulators · Section 5.1.5
Cite this note
APA
WarmTransfer. (2026, September 23). Enterprise dial plan design and normalization: source note dial-plan-design-rfc3966-local-context. WarmTransfer. https://warmtransfer.net/knowledge/claims/dial-plan-design-rfc3966-local-context
BibTeX
@misc{warmtransfer-claim-dial-plan-design-rfc3966-local-context,
title = {Enterprise dial plan design and normalization: source note dial-plan-design-rfc3966-local-context},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/dial-plan-design-rfc3966-local-context},
note = {Source note dial-plan-design-rfc3966-local-context, checked 2026-09-23}
}