SMSC SMPP User Guide

1 Index

• Change history
• Introduction
• Supported commands
  • Bind
  • Unbind
  • Enquire link
  • Submit
    • Recommended TON and NPI
    • Supported encodings
• Quota
  • Quota Overview
  • Status 106 – Quota Exceeded
• Delivery report
  • Extended delivery report format
• Supported TLS versions
• Error codes

2 Change history

3 Introduction

LINK Mobility has been a SMS distributor since 2001 and has much experience in working with both operators and connection aggregators. This platform is designed to handle large traffic volumes, maintain a high availability and make it easy to route traffic via multiple connections.

This document describes the SMPP interface to the SMSC-platform and which parameters and commands that are required and which parameters are supported.

This document will not handle specific use cases as concatenated messages, WAP-push, Flash SMS, etc. More information about those cases can be provided by contacting support.

4 Supported commands

LINK Mobility's server should be treated as SMPP 3.4. The official specification can be found at https://smpp.org/SMPP_v3_4_Issue1_2.pdf. All methods are not supported, and all differences are specified below.

4.1 Bind

The following bind commands are supported:

• Transmitter
• Transciever
• Receiver

Required parameters:

• system_id – obtained from support
• password – obtained from support

Optional parameters:

• addr_ton – default value if TON is set to Unknown during submit.
• addr_npi – default value if NPI is set to Unknown during submit.

Unsupported parameters:

• address_range

4.2 Unbind

The unbind command is supported.

4.3 Enquire link

The enquire link command is supported and should be called every 60 seconds.

4.4 Submit

The submit method should be used for delivering messages.

Required parameters:

• source_addr_ton
• source_addr_npi
• source_addr
• dest_addr_ton
• dest_addr_npi
• dest_addr
• esm_class
• data_coding
• sm_length
• short_message

Unsupported parameters:

• service_type
• protocol_id
• priority_flag
• schedule_delivery_time
• replace_if_present_flag
• sm_default_msg_id

Note that the payload tag is not supported and only one SMS may be delivered per call and it is recommended that the validity_period tag has a value of 15 minutes long at least.

4.4.1 Recommended TON and NPI

The following TON and NPI should be used when sending messages using submit command.

4.4.1.1 Source

The following TON and NPI combinations are supported for source address. All other combinations will be treated as invalid. The default TON from bind command will be used if TON is set to Unknown (0). The default NPI from bind command will be used if NPI is set to Unknown (0).

4.4.1.2 Destination

The following TON and NPI combinations are supported for destination address. All other combinations will be treated as invalid. The default TON from bind command will be used if TON is set to Unknown (0). The default NPI from bind command will be used if NPI is set to Unknown (0).

4.4.2 Supported encodings

The following encodings are supported. X may contain any value.

5 Quota

5.1 Quota Overview

A quota defines the maximum number of SMS messages that can be sent within a specified time interval (such as per day, week, month, or indefinitely). Each quota is uniquely identified by a quotaId (UUID) and is reset according to the customer's time zone. Quotas can be assigned at the country, region, or default level through a QuotaProfile. Quota can also be dynamically assigned using QuotaMapping. This maps a parentQuotaId (UUID) and a unique quotaKey (e.g., sender or user) to a specific quotaId.

A quota is set in accordance with your local support, your assigned account manager or by default if nothing is specified.

5.2 Status 106 – Quota Exceeded

An SMS message may be blocked with status code 106 ("quota exceeded") when:

• The message exceeds the defined limit for its corresponding quotaId within the current interval.
• The destination country or region has no quota assigned (i.e., is explicitly blocked with a null quota mapping in the profile).
• There is no matching quota and no default quota is defined, resulting in rejection.

In these cases, the system prevents further message processing to enforce customer or destination-based limits and avoid misuse.

6 Delivery report

Only none or final delivery with successful/failure result are supported.

Format on delivery report:

id: xxxxxxxxxxxxxxxx sub:000 dlvrd:000 submit date: yyMMddHHmm done date: yyMMddHHmm stat: <status> err: <error code> text:

Available values in status:

• DELIVRD
• EXPIRED
• REJECTD
• UNDELIV
• DELETED

"sub" and "dlvrd” fields will always be set to 000, and “text” field will always be empty.

See chapter Error codes for values for the “err” field.

6.1 Extended delivery report format

Extended information in delivery reports may be requested in contact with your sales representative.

Format on delivery report:

7 Supported TLS versions

TLS 1.2 or TLS 1.3 is required for all TLS connections over SMPP.

Support for TLS 1.0 and 1.1 is discontinued since 2020-11-15. Versions 1.0 and 1.1 of TLS are older protocols that have been deprecated and are considered as security risks in the Internet community.

LINK strongly recommend to use TLS if unencrypted SMPP connections are being used today. Unencrypted SMPP connections are deprecated as of 2020-09-01 by LINK, and will be removed in the future. Date for unencrypted connections removal is not yet decided.

Connections towards the SMPP server for TLS is at port 3601 instead of unencrypted at port 3600.

You may still use TLS even if your SMPP implementation doesn't support TLS using stunnel, see https://www.stunnel.org/

8 Error codes

The following error codes may be replied in the err field if the field is enabled.