When you create a rule in the SMS/Routing/Translation rules to translate a Sender ID from one type to another, for example, from numeric to alpha values or vice versa, you also need to create a translation rule for Sender TON, otherwise, after applying the Sender ID translation, the SMS will be sent to the vendor with the sender's type of number which differs from the real one, and it will lead to routing issues.
For instance, converting Sender ID from "12345" to "Facebook" will require two separate translation rules:
a rule with Entity=Sender ID:
a rule with Entity=Sender TON to translate the sender's type of number from International (1) to Alphanumeric (5):
As you may have noticed in the examples above, if both Sender ID and Sender TON translations are taking place at one stage, which is highly advised (both are either pre- or post-routing ones) OR if Sender ID translation is a pre-routing one while Sender TON translation is a post-routing one, it is required to use the translated version of the Sender ID in the Sender ID pattern parameter for the Sender TON translation rule. It is also possible (but not advisable) to have a Sender TON translation as a pre-routing one while Sender ID as a post-routing one, but in this case, logically, it is required to use the initial version of the Sender ID in the Sender ID pattern parameter for the Sender TON translation rule.
As for NPI value, it is also not changed automatically after Sender ID translation and may require a separate translation rule to be changed according to the SID's changes. It happens less often than in case with TON translations, since the Unknown (0) value is often used for NPI that is not allocated to any particular numbering plan. However, if this is not the case, the same principles apply for NPI translations as described above for TON translations.
In order to check your configured translations, you can use the SMS/Routing/Simulation interface, creating a simulation with required parameters and checking its log. You should search for the "Applying translation rules" line, below is an example of successfully applied post-routing translations (it would have been stage 0 instead of stage 1 if the translations were pre-routing):
Applying translation rules, stage 1, time 2024-03-18 16:35:25, cProd 1153, vProd 1166, ANI 12345(ToN 1, NPI 0), DNIS 7840(ToN 1, NPI 0):
ANI: rule 10353 found, rule translation applied, <12345> -> <Facebook>
ANI ToN: rule 10354 found, rule translation applied, <1> -> <5>If you have any remaining questions, feel free to contact the support team and provide as much detail as possible regarding your issue, including Translation rule ID and Simulation ID.
AKBSMS - Alaris Knowledge Base
SID translation.
Sender NPI translation.
Sender ID translation requirements.
Changing Sender TON.
Checking Sender ID translation.
Setting Sender ID pattern parameter for the Sender TON translation.
Link to this Article: https://helpdesk.alarislabs.com/en/knowledge_base/article/281/category/134/