RFC 5806 says existing Diversion headers received in a request or response must not be removed or changed when the message is forwarded.
Checked 2026-10-02
Existing Diversion headers received in an incoming request MUST NOT be removed or changed in forwarded requests.
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- Diversion
- Deployment
- multi-tenant, on-premises
- Region
- not restricted
- Release range
- RFC 5806
- Checked
- 2026-10-02
Sources
- RFC 5806: Diversion Indication in SIP — IETF / RFC Editor · tier 1 standards and regulators · Section 3.1 (When Is the Diversion Header Used?)
Cite this note
APA
WarmTransfer. (2026, October 2). SIP identity headers: P-Asserted-Identity and Diversion and History-Info: source note sip-identity-headers-diversion-preserve. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-identity-headers-diversion-preserve
BibTeX
@misc{warmtransfer-claim-sip-identity-headers-diversion-preserve,
title = {SIP identity headers: P-Asserted-Identity and Diversion and History-Info: source note sip-identity-headers-diversion-preserve},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-identity-headers-diversion-preserve},
note = {Source note sip-identity-headers-diversion-preserve, checked 2026-10-02}
}