Symptom
Activation of an external rule intended to block traffic from specific originators results in the blocking of all traffic.
Potential Causes
-
Incomplete Originator List: The
tp_walkallutility does not display the list of specific originators intended to be blocked. This can be verified by examining the settings, where the conditions for SMS and originators might appear empty or incorrectly set, as shown below:-
mtiExtCondRuleSmscCondition.7 = STRING:(expected to contain SMS center identifiers) -
mtiExtCondRuleOriginatorCondition.7 = STRING:(expected to contain originator identifiers)
-
-
Incorrect Filter Configuration: Initially configuring the filter with a "Return False" action without setting the desired conditions can lead to the blocking of all messages. This occurs because the filter, lacking conditions, immediately returns "false" to the RTR (Routing and Transfer Rules), resulting in a universal message block.
Recommended Solutions
-
Verify and Update Originator List: Ensure that the list of specific originators to be blocked is correctly added to the external rule. This may involve revisiting the rule configuration and correctly specifying the originators in the
mtiExtCondRuleOriginatorConditionparameter. -
Adjust Filter Creation Process:
- Step 1: When creating a new filter, initially select "Return True" as the filter action. This setting will allow traffic through while you are setting up the filter conditions.
- Step 2: After defining and activating the necessary conditions to identify the traffic to be blocked, change the filter action to "Return False". This adjustment will ensure that only the traffic meeting the specified conditions is blocked.
Additional Notes
- It is crucial to carefully review the filter conditions and actions during setup to prevent unintended blocking of traffic.
- Consider testing the rule in a controlled environment before deploying it in a live setting to verify its behavior and ensure it aligns with the intended traffic filtering objectives.