Outbound SMS feature



Freely configurable sender ID type


You can freely define the sender ID as alphanumeric, numeric or short code. An alphanumeric sender ID can have up to 11 characters.

Swap sender and receiver in the DLR

On request

In the tyntec DLRs, the sender and receiver parameters are set to the same values as in the matching message. If this feature is activated, the content is swapped, i.e. the sender parameter of the original message becomes the receiver in the DLR and the other way round. The former behaviour is common practice in the industry, while the latter matches the SMPP 3.4 specifications.

TON/NPI settings

On request

If this feature is activated, you can set TON/NPI for the originator. As an exception, tyntec will set the TON to 5 for an alphanumeric originator. If the feature is not activated, tyntec will automatically set the TON/NPI parameters based on the analysis of the originator.

Protocol ID / Over The Air (OTA)


This feature enables the setting of the protocol ID as per GSM 3.40 documentation. It is commonly used for sending binary SMS.

WAP push


A WAP push message is a special type of binary SMS, so the message type parameter needs to be set to “sms_raw”.

Example request:


The binary encoded content in detail:
06 PDU type (Push PDU)
01 Header Length (just leave it at 01)
AE Content Type=application/vnd.wap.sic (0x80 | 0x2E)
6A <charset=utf-8>
0C http://
03 (next is an ASCII string for the URL, terminate with 00)
hex encoding for „www.tyntec.com“
00 terminate string with 00
03 (next is an ASCII string for title, terminate with 00)
hex encoding for „tyntec“
00 terminate string with 00
01 true

GSM return codes


The GSM return codes are four-digit hexadecimal codes which give visibility on the non-delivery reason. A list of GSM return codes is available in the Service section.

Intermediate DLRs


The intermediate DLR is sent to you if the first delivery attempt of an SMS fails. By reading the GSM return code in it, the non-delivery reason can be identified. A message that cannot be delivered at the first attempt will have a “BUFFERD” state.

Dynamic sender ID replacement

On request

This feature can replace the original sender ID with a random numeric one. It is particularly useful to overcome certain sender ID restrictions.

Geographic time stamp

On request

This feature adapts the time stamp to the local time of the home network. This is not linked to the MSC, so if the subscriber is roaming the message will not show local time, but home network time.

Concatenated SMS


The maximum length of an SMS is 160 characters in GSM-7, 140 in ASCII and 70 in Unicode (UCS-2). This feature enables the transmission of messages over this length as a concatenation of several segments. You need to split the concatenated message into segments.

The first six bytes of the content of a concatenated message contain information on the parts of the message.



Value, Hex encoded


Total header length



Header type: concat 8 bit



Header length of 8 bit concat header



Reference number, used by the handset
for identifying the same message

Anything, as long it fits into one byte and is Hex encoded.
It has to be the same throughout all parts of one concatenated message.


Total number of parts in the concat message

Total number of parts, Hex encoded.


Part number of the short message

Part number of the short message, Hex encoded. 

A typical concat header would look like this: 050003010201 for the first part of the message and 050003010202 for the second part, leaving 153 characters in the first part and 153 in the second part. Here is an example:

Part 1:


Part 2:


Deferred delivery


The SMS can be scheduled for delivery in the future.

Validity setting


The default SMS validity is 48 hours. tyntec makes several delivery attempts during this timeframe if the first one fails. You can set the validity to values lower than 48 hours.

Especially for One Time Password, we recommend setting the validity to several minutes. This will make the message expire when the content is no longer relevant and will force more retries within a short time frame after sending the message, hence increasing the chance of delivery.

Number Portability check


tyntec checks if the recipient number is ported before each SMS delivery. The message is routed to the true home network.

MCC/MNC and TTID of recipient operator


Identifies the receiving operator in the DLR by its MCC/MNC and TTID (tyntec operator ID).

Price in the DLR


Shows the price applicable for the respective SMS.

SMS Sorter

On demand

If this feature is activated, you can set an identifier (HTTP parameter) called “userContext” to a value of your choice. Tyntec stores this identifier while the SMS is transmitted and then returns it in the DLR for each message. You can use this parameter for tracking, differentiating or sorting your SMS traffic, for example per department or customer.