Interface information

tyntec’s Inter-Carrier Messaging Service (ICMS) SMPP interface is a service that enables you to exchange SMS with all operators listed on tyntec’s reach list by using the SMPP protocol. tyntec supports the SMPP protocol version 3.4.

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

The connection and features are configurable, thanks to the flexibility provided by our SMPP interface. The following illustrates an example of the workflow for sending/receiving SMS:

Outbound SMS

Inbound SMS

Send an SMS message from your own system to the tyntec platform. The message will be delivered to the subscriber through the operator network.

Receive an SMS message from the subscriber through the tyntec platform connected to the operator network.

 

 

 

SMPP session types

Description

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 for both ways above

 

SMPP operation

Initiator

Role

Answered by the other party with

bind_transmitter

Customer/tyntec

Establish a transmitter session

bind_transmitter_resp

bind_receiver

Customer/tyntec

Establish a receiver session

bind_receiver_resp

bind_transceiver

Customer/tyntec

Establish a transceiver session

bind_transceiver_resp

unbind

Customer/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

Customer/tyntec (depends on bind direction)

Send an SMS. Works with transmitter and transceiver sessions

submit_sm_resp (contains a unique message ID)

deliver_sm

Customer/tyntec (depends on bind direction)

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)

data_sm

Customer/tyntec (depends on bind direction)

Can transport either an SMS or a DLR

data_sm_resp

enquire_link

Customer/tyntec

Check if a session is still working

tyntec sends an enquire_link through an open session every 30 seconds if the session is idle. You should answer this with an “enquire_link_resp.” If the response is not received for three 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 closed.