SMS IN

Introduction

Incoming SMS service allows you to receive messages to SMS-enabled DIDs, and deliver those messages to the pre-configured destinations. 4 types of SMS trunks are supported:

SMS to Email
SMS to HTTP
SMS to SMPP ESME
SMS to SMPP SMSC

SMS via HTTP

HTTP Trunk supports both encrypted (HTTPS) and non-encrypted (HTTP) connection types for SMS data exchange. Supported HTTP Methods: PUT, POST, GET

Available variables for Path, Headers, and Request Body:

{SMS_SRC} - Source number of SMS sender. RFC 3986 encoded.
{SMS_DST} - Destination number to which SMS is received. RFC 3986 encoded.
{SMS_TEXT} - The SMS Message body. Encrypted using Base 64 encoding.
{SMS_TIME} - message receive date and time. RFC 1123 encoded.

Failover

DIDWW will re-attempt to deliver the SMS message until TTL expires. TTL Expiration is set to 172800 seconds.

Concatenated Messages

The maximum size of the SMS message is 64 KB. Concatenated messages will be assembled using User Data Header (UDH). Information about fragmentation will not be transmitted.

SMS via SMPP

DIDWW supports The Short Message Peer-to-Peer (SMPP) v3.4. protocol for SMS forwarding to external gateways and applications. DIDWW network is capable to serve as a Short Message Service Center (SMSC) or an External Short Messaging Entity (ESME). When creating a trunk customer can choose either of them ESME or SMSC indicating in which way both systems will communicate to each other.

  • External Short Messaging Entity (ESME) is an external application that connects to a Short Message Service Center (SMSC) to engage in the sending and/or receiving SMS messages

  • Short Message Service Center (SMSC) is a network element in the mobile telephone network. Its purpose is to store, forward, convert and deliver SMS messages.

When external ESME application attempts to connect to DIDWW SMSC entity, binding must be sent to: 46.19.209.213:34846

When creating the SMSC trunk, the following SMPP connection modes are available:

  • Transmitter (if Transceiver mode = Disabled), the ESME (DIDWW) can only submit messages to the SMSC.

  • Transceiver, the ESME (DIDWW) can both send and receive messages to and from the SMSC.

In case DIDWW acts as ESME, messages are send via submit_sm, while the SMSC sends messages via deliver_sm and respectively awaits for responses (deliver_sm_resp and submit_sm_resp).

Mandatory Bind Parameters

Name

Description

system_id

Provided via DIDWW user-panel.

password

Provided via DIDWW user-panel.

system_type

Defined while creating SMPP trunk.

host

46.19.209.213

port

· ESME trunk types 34846.
· SMSC port could be defined via user-panel.

Encoding

Default encoding (data_coding) used, also called DCS (Data Coding Scheme) for short messages is GSM-7 (DCS = 0). All DIDWW SMPP server supported DCS options include:

DCS value

Encoding

Max characters per SMS

0

Default value. With the SMPP Server this is GSM-7.

160

1

US-ASCII.

160

3

Latin1 (ISO-8859-1).

160

8

Unicode / UCS-2 (ISO/IEC-10646).

70

SMS length depends on the type of data_coding used. If you use standard GSM-7 or ASCII characters, an SMS has a limit of 160 characters. Unicode (UCS-2) 16-bit encoding supports a great range of characters and languages, but the message length is reduced to 70 characters.

Concatenated Messages

Every additional character after the first 160 characters (or 70 unicode characters) is referred to as a concatenated message part.

The maximum number of concatenated message parts supported by DIDWW in a single text message is 255 parts.

The maximum length per concatenated message part is slightly reduced due to the inclusion of concatenation headers:

  • 153 characters for 7-bit encoding (e.g. Latin-1/9 and GSM-7).

  • 67 characters for 16-bit encoding (Unicode).

Incoming SMS Restrictions

If you are unable to receive the incoming SMS to your DID numbers, please review the following:

  • Local Traffic - the DID numbers are optimized to receive the SMS within the country. International message delivery may be influenced by factors such as:

    • Local country restrictions for international SMS Traffic.

    • The origination network routing database is out of date with the numbering plan of the destination country.

  • A2P - the DID numbers are designed for two-way communication. Certain in-country regulations may restrict A2P traffic to DID numbers.

Important

A2P messages may also be subjected to number validation tools by the originator to reduce costs. The number validation database may be unaware of DID number prefix and consider it an invalid number for messaging.

Important

The use of the DID numbers for SMS verification purposes is not recommended. The same DID number can be obtained by other parties who will gain access to your personal data.

If the above reasons were excluded already, please contact the DIDWW Technical Support with the following data:

  • Date&Time UTC - when SMS was sent.

  • Originating Number - the number that SMS was sent from.

  • Destination DID - the DID number that SMS was sent to.