RIMS Doesn't Pass VMSC to xmsTrigger and RLV Rejected the Mo-forwardsm Request With Error "transientFailure"

(Doc ID 1459034.1)

Last updated on OCTOBER 31, 2012

Applies to:

Oracle Communications Network Charging and Control - Version 4.0.0 to 4.4.0 [Release 4.0.0 to 4.4]
Information in this document applies to any platform.


RLV (Roaming Location Validation) as XMS Screening rules in MM is rejecting the sent SMS-MO request while roaming although the defined rules in RLV are matched with the retrieved data in SRI_SM response.


1- RLV Screen Rule is defined to compare the 3 digits of Originating Global Title of the MO_FSM request versus the VMSC address returned by the HLR to RIMS which the originating handset is currently residing on:

2- Snoop Trace shows correct matching bewteen Originating Global Title of the MO_FSM request and the VMSC address returned in the SRI_SM response from HLR:


SRI_SM Response

3- Eventually the EDR shown that the RLV rejected the SMS using screen rules 438 as mentioned above.


4- And xmsTrigger logs shown error "transientFailure":

2012/04/29 13:29:25       xmsiMapFSM_SMSMO.cc  1967 [13608]             SRIExtra MO-awaitingRIMS: Received MAP RIMS response. timeStamp = {1336044843,473067}
2012/04/29 13:29:25       xmsiMapFSM_SMSMO.cc  1967 [13608]             SRIExtra status = transientFailure
2012/04/29 13:29:25       xmsiMapFSM_SMSMO.cc  1967 [13608]             SRIExtra tcapErrorId = 0
2012/04/29 13:29:25       xmsiMapFSM_SMSMO.cc  1967 [13608]             SRIExtra abortCause = -13142396
2012/04/29 13:29:25       xmsiMapFSM_SMSMO.cc  1967 [13608]             SRIExtra abortType = 0
2012/04/29 13:29:25       xmsiMapFSM_SMSMO.cc  1967 [13608]             SRIExtra resultsFromCache = 1


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