Source note · SIP trunk redundancy and failover design
On such a failure RFC 3263 says the client SHOULD build a new request with a new Via branch ID and send it to the next element in the RFC 2782 ordered server list.
Checked 2026-09-25
- Vendor
- IETF
- Product
- SIP
- Subsystem
- server location
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3263 (June 2002), current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers — RFC Editor / IETF · tier 1 standards and regulators · Section 4.3 Details of RFC 2782 Process
Cite this note
APA
WarmTransfer. (2026, September 25). SIP trunk redundancy and failover design: source note sip-trunk-redundancy-design-rfc3263-retry-next. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-redundancy-design-rfc3263-retry-next
BibTeX
@misc{warmtransfer-claim-sip-trunk-redundancy-design-rfc3263-retry-next,
title = {SIP trunk redundancy and failover design: source note sip-trunk-redundancy-design-rfc3263-retry-next},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-redundancy-design-rfc3263-retry-next},
note = {Source note sip-trunk-redundancy-design-rfc3263-retry-next, checked 2026-09-25}
}