SMS Message is Not Sent by MMX when using MRQ Feature Node
Last updated on NOVEMBER 07, 2016
Applies to:Oracle Communications Network Charging and Control - Version 6.0.0 and later
Information in this document applies to any platform.
We have the following scenario:
A MO (mobile originated) message is submitted through MAP to MMX(Messaging Manager), MMX is configured to trigger an ACS(Advanced Control Services) control plan.
MRQ=Map RIMS Query
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms