Alaris SMS platform allows billing via dial codes. To achieve that, Column with dial codes should be marked as 'Sender ID' during rate import:
It can also be changed in Rate editor:
This value serves 2 purposes:
1) In case sender ID fully matches the value in 'Dial code' field, SMS will be billed based on Sender ID, e.g.
System has the following rates:
MCCMNC 289067; Dial code 'Google'; Rate 0,1 USD
MCCMNC 289067; Dial code '1234'; Rate 0,15 USD
MCCMNC 289067; Dial code '7940974'; Rate 0,05 USD
MCCMNC 289067; Dial code empty; Rate 0,2 USD
If SMS was sent to MCCMNC 289067 with SID 'Google' and DNIS '79409749143' , it will be billed according to the first rate due to SID matching rate's Dial code and will cost 0,1.
If SMS was sent to MCCMNC 289067 with SID '1234' and DNIS '79409749143' , it will be billed according to the second rate due to SID matching rate's Dial code and will cost 0,15.
2) In other cases 'Dial code' field is treated as prefix
If SMS was sent to MCCMNC 289067 with SID '79409741781' and DNIS '79409749143' , it will be billed according to the third rate due to SID matching rate's Dial code and will cost 0,05.
But if another SMS is sent to DNIS 79409739143 in the same network, it will be billed according to fourth rate and will cost 0,2 USD, as the number didn't match any dial codes.
Note: during routing Sender ID matching has higher priority that dial code matching.
More information on rate search logic can be found in Alaris SMS Platform Manual.
So, this feature can be used to create detailed billing schemes within a single MCCMNC.
AKBSMS - Alaris Knowledge Base
Related Questions:
Bill by prefix
ANI based billing
Rates for prefixes
Rates for dial codes
Sender ID billing
Many rates within MCCMNC
Rates for number ranges
Link to this article: https://helpdesk.alarislabs.com/en/knowledge_base/article/291/category/138/