Messaging Manager Inflexible on SMPP "short_message" Field Length
Last updated on JULY 03, 2018
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Oracle Communications Network Charging and Control - Version 4.3.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), when using Messaging Manager (MM) to send Short Message Peer-to-Peer (SMPP) notifications to subscribers, whether the payload is sent in the short_message parameter or message_payload Tag Length Value (TLV) attribute is hardcoded to 255 octets.
As per the SMPP specifications, the maximum length of the short_message parameter is 255 octets, but the actual limit to be used is determined by the network element which supports the smallest length.
If an incoming message arrives at MM already concatenated (ie. multi-part), MM will treat each individual segment as an independent Short Message Service (SMS) message and deliver it independently. Segmentation information will be preserved per segment.
If MM is configured to assemble the concatenated SMS, this issue will occur as well.
The current behavior of MM around which payload field it will use is as follows:
- If the payload is between 0 and 255 octets, use the short_message parameter
- If the payload is over 255 octets, use the message_payload TLV (the message_payload has a maximum theoretical limit of 64k)
No segmentation information is ever encoded as only a single SMS segment is ever sent.
Due to the hardcoded length (255 octets) of the short_message parameter, network elements which cannot support a short_message up to 255 octets will drop the message.
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