Concatenated (Long) SMS Message Reference Always "0" When Using a SSMN Node

(Doc ID 1984494.1)

Last updated on MARCH 24, 2015

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.1 and later
Oracle Solaris on SPARC (64-bit)

Symptoms

With the release of Oracle Network Charging and Control (NCC) 5.0.1.0, there is a new 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) where the unique segmented message reference is always set to 0 in the outgoing message.  This can be seen in the following ways:

1. The SEGR XMS EDR tag is always 0

TYPE=1|DATE=20150119181445|IPRN=Wrapper|OAID=Internal Adapter|OADR=tel:W|DADR=tel:X|IPRI=PriorityNormal|MTYP=0|MSGD=0|USRD=...|ALPH=UTF-8|ULEN=0|RECT=0|RECN=0|EDELT=1421662484|TLEN=153|PRID=0|STRR=0|NRQ=0|RRR=0|VP=0|SEGN=1|SEGT=2|SEGR=0|DELTS=20150119181445|ASPDF=SMPP SMSC RS1.S.SMSC 5|OPRN=SMPP|TAID=SMPP Adapter Outbound Routing|DPATH=SMPP SMSC RS1|OADR=tel:Y|DADR=tel:Z|OPRI=PriorityNormal|MSGD=1|PRES=1|STRR=0|RESL=0

TYPE=1|DATE=20150119181448|IPRN=Wrapper|OAID=Internal Adapter|OADR=tel:W|DADR=tel:X|IPRI=PriorityNormal|MTYP=0|MSGD=0|USRD=...|ALPH=UTF-8|ULEN=0|RECT=0|RECN=0|EDELT=1421662487|TLEN=17|PRID=0|STRR=0|NRQ=0|RRR=0|VP=0|SEGN=2|SEGT=2|SEGR=0|DELTS=20150119181448|ASPDF=SMPP SMSC RS1.S.SMSC 5|OPRN=SMPP|TAID=SMPP Adapter Outbound Routing|DPATH=SMPP SMSC RS1|OADR=tel:Y|DADR=tel:Z|OPRI=PriorityNormal|MSGD=1|PRES=1|STRR=0|RESL=0

TYPE=1|DATE=20150119181841|IPRN=Wrapper|OAID=Internal Adapter|OADR=tel:W|DADR=tel:X|IPRI=PriorityNormal|MTYP=0|MSGD=0|USRD=...|ALPH=UTF-8|ULEN=0|RECT=0|RECN=0|EDELT=1421662720|TLEN=201|PRID=0|STRR=0|NRQ=0|RRR=0|VP=0|SEGN=1|SEGT=3|SEGR=0|DELTS=20150119181841|ASPDF=SMPP SMSC RS1.S.SMSC 5|OPRN=SMPP|TAID=SMPP Adapter Outbound Routing|DPATH=SMPP SMSC RS1|OADR=tel:Y|DADR=tel:Z|OPRI=PriorityNormal|MSGD=1|PRES=1|STRR=0|RESL=0

TYPE=1|DATE=20150119182711|IPRN=Wrapper|OAID=Internal Adapter|OADR=tel:W|DADR=tel:X|IPRI=PriorityNormal|MTYP=0|MSGD=0|USRD=...|ALPH=UTF-8|ULEN=0|RECT=0|RECN=0|EDELT=1421663230|TLEN=153|PRID=0|STRR=0|NRQ=0|RRR=0|VP=0|SEGN=1|SEGT=2|SEGR=0|DELTS=20150119182711|ASPDF=SMPP SMSC RS1.S.SMSC 5|OPRN=SMPP|TAID=SMPP Adapter Outbound Routing|DPATH=SMPP SMSC RS1|OADR=tel:Y|DADR=tel:Z|OPRI=PriorityNormal|MSGD=1|PRES=1|STRR=0|RESL=0

TYPE=1|DATE=20150119182715|IPRN=Wrapper|OAID=Internal Adapter|OADR=tel:W|DADR=tel:X|IPRI=PriorityNormal|MTYP=0|MSGD=0|USRD=...|ALPH=UTF-8|ULEN=0|RECT=0|RECN=0|EDELT=1421663234|TLEN=147|PRID=0|STRR=0|NRQ=0|RRR=0|VP=0|SEGN=2|SEGT=2|SEGR=0|DELTS=20150119182715|ASPDF=SMPP SMSC RS1.S.SMSC 5|OPRN=SMPP|TAID=SMPP Adapter Outbound Routing|DPATH=SMPP SMSC RS1|OADR=tel:Y|DADR=tel:Z|OPRI=PriorityNormal|MSGD=1|PRES=1|STRR=0|RESL=0

2. The Incoming and matching Outgoing message have different segment references and outgoing it is always 0

Incoming

Outgoing

Please note that although the data is encoded in a different manner, the values should be the same.

It is possible this issue is never noticed as the segment reference is used to uniquely identify different message segments belonging to the same concatenated short message. Unless the recipient is receiving multiple concatenated short messages at the same time, then it unlikely this issue will have any effect to the user experience.

Changes

Installation of NCC 5.0.1.0 to utlise the ability to set the outgoing TON/NPI and concatenated SMS traffic is triggering to NCC.

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