Extraneous Characters are being Appended to Non-Final Segments of a Concatenated Short Message
Last updated on NOVEMBER 14, 2013
Applies to:Oracle Communications Network Charging and Control - Version 3.2.0 to 4.3.0 [Release 3.2.0 to 4.3]
Information in this document applies to any platform.
In Messaging Manager, incoming segments of a Concatenated Short Message (SM) may arrive with a User Data (UD) which is shorter than the maximum permissible length of 140 octets (an octet is a grouping of 8 bits).
When the equivalent SM segment leaves the Service Logic Controller (SLC), it can be seen in network traces that the UD has been padded to the full 140 octet limit with extraneous characters (the character(s) used will depend on the data coding scheme of the message).
As the characters are being padded to the end of a non-final segment, once all the segments have been delivered to the destination handset and reassembled, the message will not make sense and possibly be unrecognisable (if it was a picture or melody message for example).
NOTE: This padding will only affect non-final segments of a concatenated (or long) SM.
No changes were made to the Network Charging and Control (NCC) platform directly, but concatenated short messages may have been introduced to the platform.
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