What are the parameters for the SMPP deliver_sm and deliver_sm_resp requests?

delivery_sm has the same parameter list as the submit_sm request:

• service_type- indicates SMS application service
• source_addr_ton- type of number for source address
• source_addr_npi- numbering plan indicator for source address
• source_addr- source address
• dest_addr_ton- type of number for destination
• dest_addr_npi- numbering plan indicator for destination
• destination_addr- destination address of the short message
• esm_class- message mode and type
• protocol_id- protocol identifier (network specific)
• priority_flag- sets the priority of the message (this is ignored)
• schedule_delivery_time- set to NULL for immediate delivery (this is ignored)
• validity_period- validity period of message
• registered_delivery- indicator to signify if an SMSC delivery receipt or acknowledgment is required
• replace_if_present_flag- flag indicating if submitted message should replace an existing message (this is ignored)
• data_coding- defines the encoding scheme of the SMS message
• sm_default_msg_id- indicates short message to send from a predefined list of messages stored on SMSC (this is ignored)
• sm_length- length in octets of the short_message user data
• short_message- up to 254 octets of short message user data.

Optional parameters include:

• user_message_reference- user assigned reference number

For more information on the SUBMIT_SM request please consult the SMPP specification available in the What Are SMPP And UCP-EMI? article.

deliver_sm_resp requests require only a message_id parameter.

Delivery receipts are addressed to the originator of the message. The SMSC delivery receipt is carried as the user data payload in the SMPP deliver_sm operation.

For more information please see our article What Is The Format Of SMPP Delivery Receipts?.