My Oracle Support Banner

Messaging Manager Truncates Last Character of Inbound SMPP GSM 7-bit (Doc ID 2376008.1)

Last updated on MARCH 22, 2019

Applies to:

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

Symptoms

On Oracle Communication Convergent Charging Controller (OC3C) Applications, 6.0.1 version, it is observed that Messaging Manager (MM) truncates the last character of inbound SMPP when GSM 7-bit is used. 

Consider the below sample xmsTrigger.log which shows that the MM missing the last character of the Short Message Service (SMS) when Global Systems for Mobile communications (GSM) 7-bit is used:

2018/03/08 23:53:59 xmsSMSRequest.cc 69 [27798] genericSM virtual voidxms::SMSRequest::setUserDataAndUserDataHeader(const unsigned char*, size_t,xms::AvailableAlphabets, bool, bool)
2018/03/08 23:53:59 xmsMessageRequest.cc 599 [27798] genericSM virtual voidxms::MessageRequest::setUserDataAndUserDataHeader(const unsigned char*,uint_t, xms::AvailableAlphabets, bool, bool)
2018/03/08 23:53:59 xmsMessageRequest.cc 605 [27798] genericSM 9 characters in alphabet GSM7Bit equates to 8 octets
2018/03/08 23:53:59 xmsMessageRequest.cc 683 [27798] genericSM Storing userData as alphabetGSM7Bit length is: 8

As per the Short Message Peer to Peer (SMPP) specifications, the message length value is the number of octets for the user data.

MM internally stores the characters in UTF8 (8-bit character set) and it loses the last character.

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.