RFC 8224 says its guidance also applies when local policy takes the originator's identity from P-Asserted-Identity instead of From.
Checked 2026-10-02
The guidance in this specification also applies to extracting the URI containing the originator's identity from the P-Asserted-Identity header field value instead of the From header field value.
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- Identity header
- Deployment
- multi-tenant, on-premises
- Region
- not restricted
- Release range
- RFC 8224
- Checked
- 2026-10-02
Sources
- RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP) — IETF / RFC Editor · tier 1 standards and regulators · Section 8 (Identity Types)
Cite this note
APA
WarmTransfer. (2026, October 2). SIP identity headers: P-Asserted-Identity and Diversion and History-Info: source note sip-identity-headers-stir-pai-allowed. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-identity-headers-stir-pai-allowed
BibTeX
@misc{warmtransfer-claim-sip-identity-headers-stir-pai-allowed,
title = {SIP identity headers: P-Asserted-Identity and Diversion and History-Info: source note sip-identity-headers-stir-pai-allowed},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-identity-headers-stir-pai-allowed},
note = {Source note sip-identity-headers-stir-pai-allowed, checked 2026-10-02}
}