Source note · Calls-per-second limits on SIP trunks and dialers
RFC 7339 states that the 503 mechanism cannot prevent overload of a SIP server or congestion collapse, and can make traffic oscillate between servers.
Checked 2026-10-02
cannot prevent overload of a SIP server, and it cannot prevent congestion collapse
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- SIP overload control
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 7339
- Checked
- 2026-10-02
Sources
- RFC 7339: Session Initiation Protocol (SIP) Overload Control — IETF / RFC Editor · tier 1 standards and regulators · Section 1
Cite this note
APA
WarmTransfer. (2026, October 2). Calls-per-second limits on SIP trunks and dialers: source note sip-trunk-cps-limits-rfc7339-503-insufficient. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-cps-limits-rfc7339-503-insufficient
BibTeX
@misc{warmtransfer-claim-sip-trunk-cps-limits-rfc7339-503-insufficient,
title = {Calls-per-second limits on SIP trunks and dialers: source note sip-trunk-cps-limits-rfc7339-503-insufficient},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-cps-limits-rfc7339-503-insufficient},
note = {Source note sip-trunk-cps-limits-rfc7339-503-insufficient, checked 2026-10-02}
}