SMS Message is Not Sent by MMX when using MRQ Feature Node
(Doc ID 2195835.1)
Last updated on JULY 28, 2023
Applies to:
Oracle Communications Network Charging and Control - Version 6.0.0 and laterInformation in this document applies to any platform.
Symptoms
We have the following scenario:
A MO (mobile originated) message is submitted through MAP to Messaging Manager (MMX), MMX is configured to trigger an Advanced Control Services (ACS) control plan.
Control Plan: ST-1, ... MRQ-12,DDS-13,ADP-3,END-2
MRQ=Map RIMS Query
DDS=Dynamic Switch
ADP= Attempt Delivery Pending
More details about this nodes can be found in OCNCC 6.0.0 Feature Nodes Reference Guide.
MRQ=Map RIMS Query
DDS=Dynamic Switch
ADP= Attempt Delivery Pending
More details about this nodes can be found in OCNCC 6.0.0 Feature Nodes Reference Guide.
In this control plan there is a MRQ node to do the RIMS query.
- If the RIMS query is executed with NAI = 0(Network Address Identification), the SRI-SM(SendRoutingInfo - ShortMessage) is not routable and the MO message is rejected.
- If the RIMS query is executed with NAI = 4, the SRI-SM is successful and MMX receives a request to deliver the SMS to the end user, but the message never arrives.
MRQ is exiting on branch 1 to DDS feature node
Below is a detailed example with all the possible values that NAI can have and the SS7 level where it can be found.
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 |