Source note · SIP retransmission timers and transaction state
Because all four retransmission timers are 0 on a reliable transport, a capture taken over TCP or TLS contains no request retransmission at all, so the absence of retransmissions in such a capture is a property of the transport and is not evidence about the network or the peer.
inferred · Checked 2026-09-15
- Vendor
- IETF
- Product
- Session Initiation Protocol
- Subsystem
- Transaction timers
- Deployment
- not restricted
- Region
- not restricted
- Release range
- RFC 3261
- Status
- inferred
- Checked
- 2026-09-15
Sources
- RFC 3261 — SIP: Session Initiation Protocol — IETF / RFC Editor · tier 1 standards and regulators · RFC 3261 section 17 timer table, transport column
Cite this note
APA
WarmTransfer. (2026, September 15). SIP retransmission timers and transaction state: source note siprt-no-request-retransmission-on-a-stream-transport. WarmTransfer. https://warmtransfer.net/knowledge/claims/siprt-no-request-retransmission-on-a-stream-transport
BibTeX
@misc{warmtransfer-claim-siprt-no-request-retransmission-on-a-stream-transport,
title = {SIP retransmission timers and transaction state: source note siprt-no-request-retransmission-on-a-stream-transport},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/siprt-no-request-retransmission-on-a-stream-transport},
note = {Source note siprt-no-request-retransmission-on-a-stream-transport, checked 2026-09-15}
}