Concatenated (Long) SMS Segmentation Information Always Encoded as Optional "sar_*" Parameters When Using a SSMN Node (Doc ID 1984495.1)

Last updated on MARCH 22, 2015

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.0 to 5.0.2 [Release 5.0]
Oracle Solaris on SPARC (64-bit)

Symptoms

With the release of Oracle Network Charging and Control (NCC) 5.0.1.0, a feature which allows operators to modify the outgoing Originating/Destination Type of Number (TON) and outgoing Originating/Destination Numbering Type Indicator (PI) in an Advance Control Services (ACS) Control Plan.

This is achieved by setting specific Profile Tags (SSMN Originating TON Override, SSMN Destination TON Override, SSMN Originating NPI Override, SSMN Destination NPI Override) which are then used by the Send Short Message Notification (SSMN) node which can be configured to copy the incoming SMS.

More specific information on this can be found in the NCC User Documentation or please feel free to contact Oracle Support.

A problem exists with this feature in NCC when the short message being processed is a long or concatenated SMS (multipart) with a Global Systems for Mobile (GSM) User Data Header (UDH) where the outgoing Short Message Peer to Peer (SMPP) SMS now has the segmentation information encoded in the following SMPP specific fields:

This can be seen, if a network trace is taken, as follows:

Incoming

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