Need Clarification On The 128 Octets Hex Content…
(Doc ID 2872397.1)
Last updated on JUNE 06, 2022
Applies to:Acme Packet 6300 - Version S-Cz8.4.0 and later
Information in this document applies to any platform.
Provide additional details regarding the octet content in the UUI header.
Starting on page 5-180
SIP REFER Call Transfer UUI Relay
The SIP REFER Call Transfer User to User Information (UUI) Relay option assists in the transfer of caller details through using the information in the "Refer-To" header in a new "User to User" header in the INVITE to the Referred-to party.
This feature only works when the refer-call-transfer option is enabled on the realm or session agent where the REFER is received. This behavior change is enabled by default.
This option can be used by a Call Center application to transfer a call with user information to an agent.
The Oracle Communications Session Border Controller supports a maximum of 128 octets hex content in the UUI header field, excluding parameters.
The overall length of the header complies with RFC 3261. If the header length exceeds the maximum, the Oracle Communications Session Border Controller discards the UUI header and cannot relay the call.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document