Under RFC 8760 a SIP server must always send the qop parameter in digest challenges and both UAC and UAS must handle it.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- digest authentication
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 8760 (March 2020) onward
- Checked
- 2026-10-02
Sources
- RFC 8760: The Session Initiation Protocol (SIP) Digest Access Authentication Scheme — RFC Editor / IETF · tier 1 standards and regulators · Section 2.6
Cite this note
APA
WarmTransfer. (2026, October 2). SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-rfc8760-qop-always-sent. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-rfc8760-qop-always-sent
BibTeX
@misc{warmtransfer-claim-sip-trunk-authentication-models-rfc8760-qop-always-sent,
title = {SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-rfc8760-qop-always-sent},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-rfc8760-qop-always-sent},
note = {Source note sip-trunk-authentication-models-rfc8760-qop-always-sent, checked 2026-10-02}
}