Source note · Passing call context with SIP UUI and custom headers
RFC 7433 allows a sender to include multiple User-to-User header fields in one message and requires receivers to be prepared to receive multiple.
Checked 2026-10-02
A sender MAY include multiple User-to-User header fields, and a receiver MUST be prepared to receive multiple User-to-User header fields.
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- SIP User-to-User header
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 7433
- Checked
- 2026-10-02
Sources
- RFC 7433: A Mechanism for Transporting User-to-User Call Control Information in SIP — IETF / RFC Editor · tier 1 standards and regulators · Section 4.1
Cite this note
APA
WarmTransfer. (2026, October 2). Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-rfc7433-multiple-headers. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-rfc7433-multiple-headers
BibTeX
@misc{warmtransfer-claim-sip-uui-context-passing-rfc7433-multiple-headers,
title = {Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-rfc7433-multiple-headers},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-rfc7433-multiple-headers},
note = {Source note sip-uui-context-passing-rfc7433-multiple-headers, checked 2026-10-02}
}