Incorrect Alphabet used by Extract Content Node to Decode User Data from an SMS
(Doc ID 2479565.1)
Last updated on JANUARY 28, 2020
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 and later
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) up to 22.214.171.124 inclusive, inbound Short Message Peer to Peer (SMPP) Short Message Service (SMS) messages with Data Coding Scheme (DCS) value 0x01 fail to have the user data correct extracted by the Extract Content (XCNT) feature node.
For example, when a SMS contains the following user data:
it is instead being extracted as:
As a result, any service logic that requires the actual user data will fail.
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