When a cloud or carrier returns 404 for a number that is provisioned, the first check is whether the Request-URI user part matches the provisioned format (typically +E.164), since documented lookups key on the Request-URI.
inferred · Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- Diagnosis
- Deployment
- any
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Status
- inferred
- Checked
- 2026-10-02
Sources
- SIP 404 and Microsoft response codes - Microsoft Teams — Microsoft · tier 2 current vendor documentation · Section '511404 ...', generalised with ms-learn-dr-protocols-sip 'Request-URI' section
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-ruri-format-first-check. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-ruri-format-first-check
BibTeX
@misc{warmtransfer-claim-sip-404-484-troubleshooting-ruri-format-first-check,
title = {Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-ruri-format-first-check},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-ruri-format-first-check},
note = {Source note sip-404-484-troubleshooting-ruri-format-first-check, checked 2026-10-02}
}