Long Ussd Messages Encoded In Ucs-2 Are Not Truncated Correctly By Ussdgw Interface

(Doc ID 2414943.1)

Last updated on JULY 12, 2018

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.

Symptoms

On Oracle Communications - Convergent Charging Controller (OC-3C) 6.0.1, when running USSDGW interface with "-u" option (sending unicode characters UCS2) and sending Unstructured Supplementary Service Data (USSD) message with more than 79 text characters, message is truncated at 80 text characters.
As message is UCS-2 encoded, one character is reserved for Byte-Order Mode header, so total size of message is 81 characters (162 bytes).
Because this is more than maximum allowed size of USSD message (which is 160 bytes), message is not displayed by handset.

Changes

 The issue can be reproduced at will with the following steps:
1. open ssh session on SLC node
2. go to /IN/service_packages/UIS/bin/ path
3. edit ussdgw.sh and add "-u" option to the command which is starting USSDGW interface
4. restart USSDGW interface
5. trigger execution of control plan which implies sending USSD message longer than 79 characters
It can be observed that USSD message is not displayed by handset

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms