RFC 6357 states that the built-in 503 Service Unavailable mechanism cannot prevent SIP server overload or congestion collapse and may shift load between servers.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- SIP overload
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 6357 (Informational), current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- RFC 6357: Design Considerations for Session Initiation Protocol (SIP) Overload Control — IETF / RFC Editor · tier 1 standards and regulators · Section 1 Introduction
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-rfc6357-503-not-preventive. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-rfc6357-503-not-preventive
BibTeX
@misc{warmtransfer-claim-sip-408-timeout-troubleshooting-rfc6357-503-not-preventive,
title = {Troubleshooting SIP 408 Request Timeout and calls that get no response: source note sip-408-timeout-troubleshooting-rfc6357-503-not-preventive},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-rfc6357-503-not-preventive},
note = {Source note sip-408-timeout-troubleshooting-rfc6357-503-not-preventive, checked 2026-10-02}
}