Under RFC 3261 a UAC that receives a timeout error from its transaction layer treats it as if a 408 Request Timeout response had been received, so a 408 reported by a UAC need not have crossed the wire.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- SIP transaction layer
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3261, current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- RFC 3261 — SIP: Session Initiation Protocol — IETF / RFC Editor · tier 1 standards and regulators · Section 8.1.3.1 Transaction Layer Errors
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-rfc3261-timeout-as-408. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-rfc3261-timeout-as-408
BibTeX
@misc{warmtransfer-claim-sip-408-timeout-troubleshooting-rfc3261-timeout-as-408,
title = {Troubleshooting SIP 408 Request Timeout and calls that get no response: source note sip-408-timeout-troubleshooting-rfc3261-timeout-as-408},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-rfc3261-timeout-as-408},
note = {Source note sip-408-timeout-troubleshooting-rfc3261-timeout-as-408, checked 2026-10-02}
}