Source note · SIP registration failures
Under RFC 8760 a UAS may send several WWW-Authenticate or Proxy-Authenticate headers in order of preference, and a UAC seeing several for the same realm should use the topmost one it supports.
Checked 2026-09-25
- Vendor
- not restricted
- Product
- SIP
- Subsystem
- authentication
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 8760
- Checked
- 2026-09-25
Sources
- RFC 8760: The Session Initiation Protocol (SIP) Digest Access Authentication Scheme — RFC Editor / IETF · tier 1 standards and regulators · sentences beginning 'The UAS MUST add these header fields' and 'When the UAC receives a response with multiple WWW-Authenticate'
Cite this note
APA
WarmTransfer. (2026, September 25). SIP registration failures: source note sip-registration-failures-multi-challenge-order. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-registration-failures-multi-challenge-order
BibTeX
@misc{warmtransfer-claim-sip-registration-failures-multi-challenge-order,
title = {SIP registration failures: source note sip-registration-failures-multi-challenge-order},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-registration-failures-multi-challenge-order},
note = {Source note sip-registration-failures-multi-challenge-order, checked 2026-09-25}
}