FAQs: UUI header
If I have remote stations reached by a BYOC Cloud or BYOC Premises External SIP Trunk with UUI enabled on the trunk, will the other end of the trunk receive the UUI data?
That depends on what type of telephony device you have on the trunk. If you have a PBX or an SBC on the other side of the trunk, you can receive the UUI data. However, if your remote station is reached through the PSTN, it is unlikely the UUI data will persist through to the station.
Why is the User-to-User data appearing in the SIP message but not in Architect or Scripter?
The most common cause for this is if the UUI data in the SIP header doesn’t match what is specified by the encoding format. There are three situations where this can occur.
- If you specify ASCII as the encoding format, but your UUI data is Hex.
- If you specify Hex as the encoding format, but your UUI data is ASCII.
- If you do not specify an encoding format and your UUI data is ASCII.
The first two situations are pretty straightforward: the UUI data and the encoding format are not the same. However, the third situation is a little trickier to uncover because if you do not specify an encoding format, Genesys Cloud assumes the encoding format is Hex. So, if your UUI data is ASCII and Genesys Cloud is looking for Hex UUI data, then there isn’t a match.
For more information, see User to User Information (UUI) overview.