Source note · Troubleshooting SIP 403 Forbidden from a carrier
RFC 8224 allows a STIR verification service to send a 403 response, optionally with the reason phrase Stale Date, when a request's Date header field value is older than local freshness policy permits.
Checked 2026-09-30
Finally, a 403 response may be sent when the verification service receives a request with a Date header field value that is older than the local policy for freshness permits.
- Vendor
- IETF
- Product
- STIR
- Subsystem
- verification service
- Deployment
- any
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP) — IETF / RFC Editor · tier 1 standards and regulators · section 6.2.2 (Failure Response Codes Sent by a Verification Service), final paragraph
Cite this note
APA
WarmTransfer. (2026, September 30). Troubleshooting SIP 403 Forbidden from a carrier: source note sip-403-forbidden-troubleshooting-rfc8224-stale-date. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-403-forbidden-troubleshooting-rfc8224-stale-date
BibTeX
@misc{warmtransfer-claim-sip-403-forbidden-troubleshooting-rfc8224-stale-date,
title = {Troubleshooting SIP 403 Forbidden from a carrier: source note sip-403-forbidden-troubleshooting-rfc8224-stale-date},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-403-forbidden-troubleshooting-rfc8224-stale-date},
note = {Source note sip-403-forbidden-troubleshooting-rfc8224-stale-date, checked 2026-09-30}
}