Source note · SIP 503 and trunk out-of-service failures
After a 503, the client SHOULD NOT forward any other requests to that server for the duration given in the Retry-After header field, if one is present.
Checked 2026-09-25
It SHOULD NOT forward any other requests to that server for the duration specified in the Retry-After header field, if present.
- Vendor
- IETF
- Product
- SIP
- Subsystem
- Retry-After
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3261 as quoted in RFC 5390; current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- RFC 5390: Requirements for Management of Overload in the Session Initiation Protocol — IETF / RFC Editor · tier 1 standards and regulators · Section 4 (quotation of RFC 3261)
Cite this note
APA
WarmTransfer. (2026, September 25). SIP 503 and trunk out-of-service failures: source note sip-503-trunk-failures-retry-after-holdoff. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-503-trunk-failures-retry-after-holdoff
BibTeX
@misc{warmtransfer-claim-sip-503-trunk-failures-retry-after-holdoff,
title = {SIP 503 and trunk out-of-service failures: source note sip-503-trunk-failures-retry-after-holdoff},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-503-trunk-failures-retry-after-holdoff},
note = {Source note sip-503-trunk-failures-retry-after-holdoff, checked 2026-09-25}
}