Interface information

tyntec’s  two-way SMS, based on SMPP, is a service that enables you to send and receive SMS to and from all operators listed on tyntec’s coverage list using the SMPP protocol. tyntec supports SMPP protocol version 3.4.

Authentication is done during the setup of the SMPP connection. After the initial authentication, the session between your system and ours (i.e. the peers) is kept open and alive.

The following illustrates the workflow for sending and receiving SMS:

Outbound SMS (SMS-MT)

Inbound SMS (SMS-MO)

Send an SMS message from your own system to the tyntec platform, through the operator network and to the subscriber.

Receive an SMS message from the subscriber through the operator network and tyntec platform to your own system.


 

SMPP session types

Transmitter session

Used for you to send SMPP requests to tyntec

Receiver session

Used by tyntec to send SMPP requests to you

Transceiver session

Used in both the ways above

 

Supported SMPP operations

SMPP operation

Initiator

Role

Answered by the other party with

bind_transmitter

You

Establish a transmitter session

bind_transmitter_resp

bind_receiver

You

Establish a receiver session

bind_receiver_resp

bind_transceiver

You

Establish a transceiver session

bind_transceiver_resp

unbind

You or tyntec

Close a session

unbind_resp

generic_nack

tyntec

Negative answer to a faulty request, or if the service is currently unavailable

N/A

submit_sm

You

Send an SMS. Works with transmitter and transceiver sessions.

submit_sm_resp (contains a unique message ID)

deliver_sm

tyntec

Provide a delivery receipt (DLR). Works with receiver and transceiver sessions.

deliver_sm_resp (if the customer doesn’t answer with this, tyntec will retry the deliver_sm)

enquire_link

You and/or tyntec

Check if a session is still working

tyntec sends an enquire_link through an open session every 30 seconds. You should answer this with an “enquire_link_resp”. If this doesn’t happen for five times in a row, tyntec will terminate the respective session.

tyntec answers with an enquire_link_resp to any incoming enquire_link. If you don’t see the enquire_link_response, the session is likely to be dead.