Source note · Passing call context with SIP UUI and custom headers
Genesys advises encoding UUI as ASCII rather than hex when the data uses extended ASCII characters 128-255, because hex causes problems with those characters.
Checked 2026-10-02
If your UUI data must use characters from the extended ASCII character set (character 128-255), encode your UUI data using ASCII format.
- 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
- UUI data formats — Genesys · tier 2 current vendor documentation · Section 'Encodings' and warning note
Cite this note
APA
WarmTransfer. (2026, October 2). Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-genesys-ascii-extended-chars. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-genesys-ascii-extended-chars
BibTeX
@misc{warmtransfer-claim-sip-uui-context-passing-genesys-ascii-extended-chars,
title = {Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-genesys-ascii-extended-chars},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-genesys-ascii-extended-chars},
note = {Source note sip-uui-context-passing-genesys-ascii-extended-chars, checked 2026-10-02}
}