MT SMS Loop Through MM when RIMS Fails to Find Cached Results
(Doc ID 2937092.1)
Last updated on JULY 19, 2024
Applies to:
Oracle Communications Network Charging and Control - Version 5.0.0 to 12.0.6.0.0 [Release 5.0 to 12.0.0]Information in this document applies to any platform.
Symptoms
On all version of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) between 5.0.0.0 and 12.0.6.0 (inclusive), the behavior of Messaging Manager (MM, XMS, or xmsTrigger) has changed when handling Mobile Terminated (MT) Short Message Service (SMS) messages if Messaging Manager Navigator (MMN, RIMS, or rims) does not find the cached Mobile Station International Subscriber Directory Number (MSISDN) to International Mobile Subscriber Identity (IMSI)/Network Node Number (NNN) mapping.
When this occurs, the outbound MT SMS is addressed to loop back to MM, ie. the Signalling Connection Control Part (SCCP) Called Party Global Title (CdGT) is set to MM's own CdGT in the outgoing MT SMS.
The MT SMS would continue looping back to MM until a new MT SMS was sent by the originating network for the same MSISDN.
MM versions before 5.0.0 would return an error back to the Short Message Service Center (SMSC) and throw an error as described in: OCMM (MMX) Limitations When Processing MT-FowardSM Messages Without Proxying SRI-SM (1356069.1)
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 |