RFC 5922 requires SIP domain names in certificates to be matched in their entirety and does not permit wildcard or suffix matching.
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 7.2
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-no-wildcard-match. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-rfc5922-no-wildcard-match
BibTeX
@misc{warmtransfer-claim-sip-trunk-authentication-models-rfc5922-no-wildcard-match,
title = {SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-rfc5922-no-wildcard-match},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-rfc5922-no-wildcard-match},
note = {Source note sip-trunk-authentication-models-rfc5922-no-wildcard-match, checked 2026-10-02}
}