Overview
Customers may experience an issue where a Short Message Service Center (SMSC) is blocking a specific SMS due to an Application Originating (Ao) Routing Rule. The message is discarded with a Non-Acknowledgement (Nak) routing action, and the reject cause is identified as a matching Ao Routing Rule. Despite reviewing the rules, customers may find it challenging to identify which rule is causing the message to be blocked.
Solution
To identify and modify the rule that is blocking the SMS, follow these steps:
- Create an LGV filter containing the `responseInfo_aoRoutingRule` field. This will allow you to find out which rule blocked the message.
- Modify the identified rule accordingly.
If this does not resolve your issue, please provide the following:
- Output of the tp_walkall command
- The common_config.txt file from the `/usr/TextPass/etc` directory
- The hostname_config.txt file from the `/usr/TextPass/etc` directory
- The LGV file containing the message (you can provide screenshots or export and provide the excel file)
- The Syslog: /var/log/messages
Summary
This article provides a solution for customers experiencing an issue where an SMS is being blocked due to an Ao Routing Rule. By creating an LGV filter and modifying the identified rule, customers can resolve this issue.
FAQ
-
What is an Ao Routing Rule?
An Ao Routing Rule is a rule that determines how an application-originating message is routed. -
What is an LGV filter?
An LGV filter is a tool used to filter and analyze log data. -
What is the tp_walkall command?
The tp_walkall command is a command used to display all the information, including routing rules in the system.