Smpp

SMPP Gateway

This paper describes the use of the SMPP gateway for sending SMS messages.
Our SMPP Server is based on SMPP 3.4 from SMS forum.

Connection

To connect to our SMPP servers, you should use the following.

There is no limit on the number of connected clients.
Note that the number of connected clients does not affect the LAC totals for your account.
You can connect as both Transmitter, Receiver and Transceiver.
Timeout is set to 60 seconds, so it is recommended that you send a ENQUIRE_LINK every 30 seconds.

TON / NPI Settings

TON and NPI for the recipient's address should be set as an international number

TLV Fields

SUBMIT_SM

The following additional fields are supported:

• source_port
• destination_port
• sar_msg_ref_num
• sar_total_segments
• sar_segment_seqnum
• dest_addr_subunit
• message_payload
• user_message_reference
• registered_delivery

DELIVER_SM

The following additional fields are specified:

• user_message_reference
• message_state
• receipted_message_id
• network_error_code

With network_error_code UCP errorcodes are used.

UDH IEI ELEMENTS AND LINKING

The following elements are supported

For some destinations combined messages are not sent until all parts of the message is received on the server, only then will the message be assembled into a complete message.
For the same reason it's the last message that holds the message ID. There will not be any IDs on the other parts of an combined message.

It is also possible to send the message immediately, with the use of message_payload to send the message data. Without using UDH splitting, then our SMSC will split the message for you.

MO incoming SMS

Incoming SMS will be delivered in message_payload - this is to avoid any problems with combined messages.

OBS! that means that SMS body will be blank, we recommed if SMS body is blank always to look in message_payload.

Charset

The following charsets are supported in data_coding