RFC 5922 places a SIP server's domain identity in the certificate subjectAltName and allows the subject CN to be examined only when no subjectAltName is present.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- TLS certificates
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 5922
- Checked
- 2026-10-02
Sources
- RFC 5922: Domain Certificates in the Session Initiation Protocol (SIP) — RFC Editor / IETF · tier 1 standards and regulators · Section 6; Section 7.1
Cite this note
APA
WarmTransfer. (2026, October 2). SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-rfc5922-san-preferred. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-rfc5922-san-preferred
BibTeX
@misc{warmtransfer-claim-sip-trunk-authentication-models-rfc5922-san-preferred,
title = {SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-rfc5922-san-preferred},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-rfc5922-san-preferred},
note = {Source note sip-trunk-authentication-models-rfc5922-san-preferred, checked 2026-10-02}
}