Under RFC 3261 a UAS whose Request-URI does not identify an address it is willing to accept should reject the request with 404 Not Found.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- UAS request processing
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3261 as published
- Checked
- 2026-10-02
Sources
- RFC 3261 — SIP: Session Initiation Protocol — IETF / RFC Editor · tier 1 standards and regulators · Section 8.2.2.1 (To and Request-URI)
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-uas-404-unaccepted-ruri. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-uas-404-unaccepted-ruri
BibTeX
@misc{warmtransfer-claim-sip-404-484-troubleshooting-uas-404-unaccepted-ruri,
title = {Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-uas-404-unaccepted-ruri},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-uas-404-unaccepted-ruri},
note = {Source note sip-404-484-troubleshooting-uas-404-unaccepted-ruri, checked 2026-10-02}
}