SMS gateway SMSC / ESME TON / NPI

I am developing an SMS gateway, and I was thinking about the functions that I have to implement in it. So I looked at some SMS gateways (SMSNOW, SMS studio and Ozeki) for an example.

I almost finished the implementation, but found that I have almost all SMS gateways that allow the user to specify TON / NPI for SMSC and ESME.

I understand that when the SMS gateway is preparing to send sms via SMPP, it needs to analyze the sender / receiver number and on this basis indicate TON / NPI. And I understand that this is great so that you can override the defaults and specify your own TON / NPI.

I do not understand why all SMS gateways give you the opportunity to specify your own TON / NPI for the SMS gateway when it acts as an SMSC (when it receives SMS rather than sending them).

What will the SMS gateway do with the specified TON / NPI when it receives smpp-SMS?

+3
source share
1 answer

The full specification of the SMS source address includes 3 attributes:

TON = Type of number.

This indicates whether the number is a full international number (i.e. a + prefix is ​​needed), or a national number, or even an alphanumeric sender (i.e. includes up to 11 characters of text instead of a numerical sender ... very useful for advertising) .

NPI = Numbering Plan Indicator

Indicates which number number corresponds to the number. It can be standard international numbering E164 or personal numbering of the operator (for example, for premium services).

The actual address.

SMSC TON/NPI, , , . , , TON - (5), , , (1), 2, , .

SMPP 3.4 5.2.5 5.2.6 TON/NPI. SMS, , .

+3

Source: https://habr.com/ru/post/1761512/


All Articles