RFC 3966 says globally unique numbers are unambiguous everywhere and SHOULD be used.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- Telephone number URIs
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3966 as published
- Checked
- 2026-10-02
Sources
- RFC 3966: The tel URI for Telephone Numbers — IETF / RFC Editor · tier 1 standards and regulators · Section 5.1.4 (Global Numbers)
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-rfc3966-global-should. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-rfc3966-global-should
BibTeX
@misc{warmtransfer-claim-sip-404-484-troubleshooting-rfc3966-global-should,
title = {Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-rfc3966-global-should},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-rfc3966-global-should},
note = {Source note sip-404-484-troubleshooting-rfc3966-global-should, checked 2026-10-02}
}