For the Sender ID and Message text entities, special functions can be used to replace the pattern with arbitrary symbols. You can create a translation rule in the SMS/Routing/Translation interface, set the Entity parameter as Sender ID or Message text depending on your needs and use one of the following functions in the Translation field:
•RANDINT(X): generate an integer with the length of X digits. If a non-numerical symbol is specified instead of X, the default value 7 is used. If a fractional number is specified, the number is rounded downward;
•RAND(X): similar to the RANDINT function;
•RANDHEX(X): generate an arbitrary hex string with the length of X symbols (the employed ranges of symbols are a - f and 0-9). It is more advisable to use it rather than RANDTEXT;
•RANDTEXT(X): generate an arbitrary text string with the length of X symbols (the employed ranges of symbols are a - Z and 0-9);
•RANDLETTERS(X): generate an arbitrary text string with the length of X symbols (the employed ranges of symbols are a - Z).
These functions can be used one after another. They can be used in full regular expressions, an example:
Entity: Text
Pattern: ^(.*)$
Translation:\g<1>RANDHEX(7)
Will translate “Let's see some randomness:” to "Let's see some randomness:bcf7175"
Alternatively, you can just put those functions alone in the Translation field:
Entity: Sender ID
Pattern: ^(.*)$
Translation:RANDINT(13)
Will translate "Facebook" to "4905709347346" (or any other 13-digit random value)
Also, these functions can be applied to replace the sender ID from the Sender ID tag(s) list as in this example:
It is also possible to change Sender IDs into one of the Sender ID present in a chosen tag. A random SID will be selected from the tag values instead of the original SID:
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 a successfully applied translation:
Applying translation rules, stage 0, time 2024-03-18 15:21:10, cProd 1155, vProd None, ANI 123(ToN 1, NPI 1), DNIS 7840(ToN 1, NPI 1):
ANI: rule 10352 found, rule translation applied, <123> -> <RANDINT(13)>, RANDINT function has been applied, value - 5652823314469
Final result: <5652823314469>Please note that when you 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. 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. To learn more, please find this article.
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
How to translate text to random letters.
How to translate Sender ID to random values.
How to translate Sender ID to one of the values from the list.
Translation to arbitrary values.
Changing texts to random values.
Dynamic translations.
Link to this Article: https://helpdesk.alarislabs.com/en/knowledge_base/article/280/category/134/