Overview

The SRIforSM_Ack from HLR by an SRISM Response rule whose action is No Home routing, doesn't count up the Mib counter sripRtgRuleAppliedCounter.8. The CgPA of the returned SRIforSM_Ack to the originator, SMSC is the same as the NNN of SRIforSM_Ack from the HLR, and only this rule has the action of No Home Routing.

Information

Below is an example of what would be seen in the tp_walkall_textpass_after.txt logfile:

sripRtgRuleName.8 = STRING: <RULE_NAME>
sripRtgRuleAction.8 = INTEGER: releaseForOriginatorDelivery(4)
sripRtgRuleRecipientCondition.8 = STRING: L21
sripRtgRuleSccpCallingPaCondition.8 = STRING: L10
...
listAdminState.21 = INTEGER: active(1)
listName.21 = STRING: <LIST_NAME>
listCondition.21.1 = STRING: I45896*
listCondition.21.2 = STRING: I45896*
...
listAdminState.10 = INTEGER: active(1)
listName.10 = STRING: <LIST_NAME>
listCondition.10.1 = STRING: M101587369558

Based on the above information, we can note that SRI-Response Rule (8) <RULE_NAME> shall be applicable only when both sripRtgRuleRecipientCondition and sripRtgRuleSccpCallingPaCondition match. 

When only the recipient condition matches whereas the SCCP CgPa condition for this rule does not match, this rule is not a match, and action of this is not carried out. As a result, the counter for this rule sripRtgRuleAppliedCounter.8 is also not incremented.

The reason why the behavior of the RTR is No Home Routing is because:

If no rule matches and the RTR successfully queried the HLR previously, the RTR behaves as
if a rule with the routing action "no home routing" action had matched.

This is documented in the RTR Operator Manual in section 10.5.1 (SRI-SM Response Rule Evaluation)