Source note · Passing call context with SIP UUI and custom headers
For inbound calls Genesys Cloud looks first for a User-To-User header and only if it is absent for an x-User-To-User header; if both are present it uses User-To-User.
Checked 2026-10-02
When looking for UUI data embedded in inbound calls, Genesys Cloud first looks for the User-To-User header.
- Vendor
- Genesys
- Product
- Genesys Cloud
- Subsystem
- BYOC trunk UUI
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- User to User Information (UUI) overview — Genesys · tier 2 current vendor documentation · Overview body, paragraph on inbound header detection
Cite this note
APA
WarmTransfer. (2026, October 2). Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-genesys-header-precedence. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-genesys-header-precedence
BibTeX
@misc{warmtransfer-claim-sip-uui-context-passing-genesys-header-precedence,
title = {Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-genesys-header-precedence},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-genesys-header-precedence},
note = {Source note sip-uui-context-passing-genesys-header-precedence, checked 2026-10-02}
}