Eagle Problems With SMS When Larger Than 160 Characters

Asset ID:	1-72-2159382.1
Update Date:	2016-07-12
Keywords:

Solution Type Problem Resolution Sure

Solution 2159382.1 : Eagle Problems With SMS When Larger Than 160 Characters

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 46.0 and later
Tekelec

Symptoms

Customer Reported that when the Long SMS, it failed to deliver. The same is working OK if sent to B number without Country Code.

Changes

Cause

Customer has Eagle running on 46.0.1-65.26.26 and MO FSM configured with TCAP segmentation support ON in GSMSMSOPTION. Home SMSC table has Virtual GT configured. The behavior of MSS while sending the Long SMS and the use of virtual SMSC GT in the network seems the main cause of the issue.

NPP rules verified and seems ok. As the Long SMS was working ok with the B-party without the country code, it rules out any issue with the NPP rule configuration.

All the long sms are the class 0 SCCP messages. The Long SMS is being sent in two segment by MSS with different TCAP transactions. When the first segment was sent the TCAP begin do not have any MAP component, while the second segment was being sent with the TCAP begin which has the MAP component and B-party number present.

MO FSM features was not able to get any MAP component (B-party) info in the Begin transaction where the home smsc is matched in the configuration, while sending the long SMS.

The continue part of the same message has the MAP portion but the home SMSC GT is the real one which was not configured in the Eagle as Home SMSC which prevents the trigger of MOFSM feature and TCAP continue was sent to SDP platform without any RN added to Bparty which result in to failure of delivery.

Solution

Configuration of real GT in the home SMSC table of Eagle solve the issue.

Attachments

This solution has no attachment