Supported SMPP Operations

Overview

The following diagram shows the relationship of SMPP operations to each other.

Connecting and Authenticating

Initiate a Bind request

A Bind request establishes a connection with OpenMarket. Once we authenticate your connection, it's registered and open for message transmittal. You can open a bind session for either one-way or two-way messaging.

There are no custom TLVs. The supported PDUs are:

  • bind_receiver
  • bind_receiver_resp
  • bind_transmitter
  • bind_transmitter_resp
  • bind_transceiver
  • bind_transceiver_resp

For details see Initiate a bind request to register a connection.

Unbind a registered connection

The Unbind operation un-registers the connection and then closes it. Either you or OpenMarket can initiate the operation when an open connection is no longer needed.

There are no custom TLVs. Supported PDUs are:

  • unbind
  • unbind_resp

For details see Unbind a connection.

Enquire link

Allows you to check the communication between you and OpenMarket. Only you can initiate this operation.

There are no custom TLVs. Supported PDUs are:

  • enquire_link
  • enquire_link_resp

For detail see Check the link between you and OpenMarket.

Sending and Receiving Messages and Delivery Receipts

Mobile Terminated (MT)

This operation submits a short message to the SMSC for transmission to the SME. New optional TLVs include operator ID, interaction, promotional, program ID, and note 1 and 2, while support for a number of TLVs has been removed. Supported PDUs are submit_sm and submit_sm_resp.

For details see Send a mobile-terminated message.

Mobile Originated (MO)

This operation sends messages from OpenMarket to you. A TLV, operator ID, has been added, which identifies the mobile operator. Supported PDUs are deliver_sm and deliver_sm_resp.

For details see Receive a mobile-originated message.

Delivery Receipt (DR)

This operation returns feedback about the final status of an MT message. A delivery receipt will be populated with information about the submitted date, the delivery date, message state, ticket ID, and a status code. Custom TLVs are operator ID, note 1 and 2, and status code with associated description, which are then returned in the delivery receipt. Supported PDUs are deliver_sm and deliver_sm_resp.

For details see Receive a delivery receipt.

Generic NACK

This operation returns a negative acknowledgment for an invalid message header. There are no custom TLVs. The supported PDU is generic_nack.

For details see Receive a negative acknowledgment.