RFC 4320 forbids a transaction-stateful SIP element from sending a 408 response to a non-INVITE request.
Checked 2026-10-02
A transaction-stateful SIP element MUST NOT send a response with Status-Code of 408 to a non-INVITE request.
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- SIP non-INVITE transaction
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 4320 (updates RFC 3261), current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- RFC 4320: Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction — RFC Editor / IETF · tier 1 standards and regulators · Section 4.2
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting SIP 408 Request Timeout and calls that get no response: source note sip-408-timeout-troubleshooting-rfc4320-no-408-non-invite. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-rfc4320-no-408-non-invite
BibTeX
@misc{warmtransfer-claim-sip-408-timeout-troubleshooting-rfc4320-no-408-non-invite,
title = {Troubleshooting SIP 408 Request Timeout and calls that get no response: source note sip-408-timeout-troubleshooting-rfc4320-no-408-non-invite},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-rfc4320-no-408-non-invite},
note = {Source note sip-408-timeout-troubleshooting-rfc4320-no-408-non-invite, checked 2026-10-02}
}