Over a reliable transport such as TCP or TLS, the INVITE client transaction does not retransmit the request, so a trace of a timed-out INVITE over TCP shows a single INVITE rather than a retransmission series.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- SIP INVITE client transaction
- 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 17.1.1.2 Formal Description (Timer A only started for unreliable transport)
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-tcp-no-retransmit. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-rfc3261-tcp-no-retransmit
BibTeX
@misc{warmtransfer-claim-sip-408-timeout-troubleshooting-rfc3261-tcp-no-retransmit,
title = {Troubleshooting SIP 408 Request Timeout and calls that get no response: source note sip-408-timeout-troubleshooting-rfc3261-tcp-no-retransmit},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-rfc3261-tcp-no-retransmit},
note = {Source note sip-408-timeout-troubleshooting-rfc3261-tcp-no-retransmit, checked 2026-10-02}
}