Source note · Passing call context with SIP UUI and custom headers
Under RFC 7433 the User-to-User header field may appear in INVITE and BYE requests and in end-to-end responses to them (1xx other than 100, 2xx and 3xx).
Checked 2026-10-02
- 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 (header field table)
Cite this note
APA
WarmTransfer. (2026, October 2). Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-rfc7433-methods-invite-bye. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-rfc7433-methods-invite-bye
BibTeX
@misc{warmtransfer-claim-sip-uui-context-passing-rfc7433-methods-invite-bye,
title = {Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-rfc7433-methods-invite-bye},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-rfc7433-methods-invite-bye},
note = {Source note sip-uui-context-passing-rfc7433-methods-invite-bye, checked 2026-10-02}
}