SMPP PROTOCOL #
The SMPP standard is a protocol specifically developed for sending SMS via TCP/IP connections.
The types of connections (BIND) supported are:
- Transmitter (TX – sending messages only)
- Receiver (RX – receiving delivery notifications only)
- Transceiver (TRX – sending messages + receiving notifications)
By default, Agile Telecom’s policy allows up to 4 active connections, which can be considered as 4 TX + 4 RX or 4 TRX. If necessary, you can request additional connections.
The parameters for the connection are as follows:
HOST | smpp.agiletelecom.com |
PORT | 2776 (TLS) |
SYSTEM ID | username of the account |
PASSWORD | password of the account |
MODE | TX, RX o TRX |
Login-AddrRange | <leave empty> |
Login-SystemType | <leave empty> |
Login-TON | 1 |
Login-NPI | 1 |
Login-DCS | 0 |
SMPP ERRORS #
Following the possible errors managed by our SMPP server:
ERROR TYPE | ERROR NUMBER | VALORE HEX | DESCRIPTION |
ESME_RINMSGLEN | 1 | 0x01 | Invalid package length |
ESME_RINVCMDLEN | 2 | 0x02 | Invalid command |
ESME_RINVBNDSTS | 4 | 0x04 | Not yet logged in |
ESME_RSYERR | 8 | 0x08 | System error |
ESME_RINVSRCADR | 10 | 0x0A | Invalid sender |
ESME_RINVDSTADR | 11 | 0x0B | Invalid recipient |
ESME_RINVPASWD | 13 | 0x0E | Incorrect credentials |
ESME_RINVSERTYP | 21 | 0x15 | Invalid SYSTEM_TYPE |
ESME_RSUBMITFAIL | 69 | 0x45 | Text decoding failed |
ESME_RTHROTTLED | 88 | 0x58 | Throughput limit exceeded |
ESME_RINVSCHED | 97 | 0x61 | Scheduling date sent invalid |
ESME_RINVEXPIRY | 98 | 0x62 | invalid VALIDITY_PERIOD |
ESME_RSERTYPDENIED | 259 | 0x103 | Insufficient credit |
SMS SENDER #
Max 16 characters for exclusively numeric sender (e.g. +391234567890123) or max 11 characters for alphanumeric sender (e.g. COMPANY ABC).
As of 10/16/2013, the resolution provides: no. 42/13/CIR of Agcom.
MESSAGE_ID FOR NOTIFICATION #
The message_id returned by the SUBMIT_SM_RESP package and used by the DELIVER_SM operation for delivery of notifications uses by default a UUID with the following format: AGILE-XXXXXXXX-XXXXXX-XXXXXX-XXXXXX
If the client’s platform does not support this format, the different format may be required to be agreed upon.
DATE FORMAT IN THE DELIVERY NOTIFICATION #
In the DELIVER_SM package, the string indicating the message delivery date also contains the seconds information and is in this format: yyMMddHHmmss
CONSTRAINT OF SENDING FROM IP #
By default, the platform is open to all IPs, but if necessary the client can request to bind the use of the account only from certain IP addresses or subnets.