Source note · SIP trunk redundancy and failover design
RFC 2782 says administrators should use weight 0 when there is no server selection to do, and that weight-0 records should have a very small chance of selection when weighted (>0) records are present at the same priority.
Checked 2026-09-25
- Vendor
- IETF
- Product
- DNS
- Subsystem
- SRV record
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 2782 (February 2000), current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- RFC 2782: A DNS RR for specifying the location of services (DNS SRV) — RFC Editor / IETF · tier 1 standards and regulators · The format of the SRV RR, Weight field
Cite this note
APA
WarmTransfer. (2026, September 25). SIP trunk redundancy and failover design: source note sip-trunk-redundancy-design-srv-weight-zero. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-redundancy-design-srv-weight-zero
BibTeX
@misc{warmtransfer-claim-sip-trunk-redundancy-design-srv-weight-zero,
title = {SIP trunk redundancy and failover design: source note sip-trunk-redundancy-design-srv-weight-zero},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-redundancy-design-srv-weight-zero},
note = {Source note sip-trunk-redundancy-design-srv-weight-zero, checked 2026-09-25}
}