Source note · DNS SRV and service discovery for SIP
Under RFC 3263 a client treats a 503 response, a transport failure, or expiry of timer B or timer F as failure and should send a new request to the next element in the resolved list.
Checked 2026-09-24
- Vendor
- IETF
- Product
- SIP
- Subsystem
- failover
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3263 (June 2002)
- Checked
- 2026-09-24
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 24). DNS SRV and service discovery for SIP: source note dns-srv-voice-rfc3263-failover-triggers. WarmTransfer. https://warmtransfer.net/knowledge/claims/dns-srv-voice-rfc3263-failover-triggers
BibTeX
@misc{warmtransfer-claim-dns-srv-voice-rfc3263-failover-triggers,
title = {DNS SRV and service discovery for SIP: source note dns-srv-voice-rfc3263-failover-triggers},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/dns-srv-voice-rfc3263-failover-triggers},
note = {Source note dns-srv-voice-rfc3263-failover-triggers, checked 2026-09-24}
}