Under RFC 3325 a proxy must not pass on a P-Asserted-Identity received from an element it does not trust as-is; it either replaces the asserted value with its own or removes the header.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- P-Asserted-Identity
- Deployment
- multi-tenant, on-premises
- Region
- not restricted
- Release range
- RFC 3325
- Checked
- 2026-10-02
Sources
- RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks — IETF / RFC Editor · tier 1 standards and regulators · Section 5 (Proxy behavior)
Cite this note
APA
WarmTransfer. (2026, October 2). SIP identity headers: P-Asserted-Identity and Diversion and History-Info: source note sip-identity-headers-pai-untrusted-source. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-identity-headers-pai-untrusted-source
BibTeX
@misc{warmtransfer-claim-sip-identity-headers-pai-untrusted-source,
title = {SIP identity headers: P-Asserted-Identity and Diversion and History-Info: source note sip-identity-headers-pai-untrusted-source},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-identity-headers-pai-untrusted-source},
note = {Source note sip-identity-headers-pai-untrusted-source, checked 2026-10-02}
}