Source note · Passing call context with SIP UUI and custom headers
The Amazon Connect telephony call metadata table does not list User-to-User or arbitrary X- headers, which suggests inbound PSTN calls to Connect do not expose caller-supplied UUI as a standard attribute.
inferred · Checked 2026-10-02
- Vendor
- Amazon
- Product
- Amazon Connect
- Subsystem
- contact attributes
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Status
- inferred
- Checked
- 2026-10-02
Sources
- Use caller identification to personalize customer interaction — Amazon Web Services · tier 2 current vendor documentation · Section 'Use telephony call metadata attributes' table (absence)
Cite this note
APA
WarmTransfer. (2026, October 2). Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-connect-no-uui-in-metadata-list. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-connect-no-uui-in-metadata-list
BibTeX
@misc{warmtransfer-claim-sip-uui-context-passing-connect-no-uui-in-metadata-list,
title = {Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-connect-no-uui-in-metadata-list},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-connect-no-uui-in-metadata-list},
note = {Source note sip-uui-context-passing-connect-no-uui-in-metadata-list, checked 2026-10-02}
}