RFC 3263 directs a SIP client to try the next server from its DNS-derived list when a transaction times out, when a transport failure occurs, or when a 503 is received.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- SIP DNS server location
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3263, current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers — RFC Editor / IETF · tier 1 standards and regulators · Section 4.3 (failover text following port and address determination)
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-rfc3263-retry-next-on-timeout. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-rfc3263-retry-next-on-timeout
BibTeX
@misc{warmtransfer-claim-sip-408-timeout-troubleshooting-rfc3263-retry-next-on-timeout,
title = {Troubleshooting SIP 408 Request Timeout and calls that get no response: source note sip-408-timeout-troubleshooting-rfc3263-retry-next-on-timeout},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-rfc3263-retry-next-on-timeout},
note = {Source note sip-408-timeout-troubleshooting-rfc3263-retry-next-on-timeout, checked 2026-10-02}
}