SMPP Message PDU
Last updated
Last updated
bind_transmitter
bind_receiver
bind_transceiver
unbind
submit_sm
deliver_sm
enquire_link
You can bind as a transmitter, receiver or a transceiver. However, if you want to receive delivery reports, you must bind as a transceiver or a receiver.
We use SMPP command status as per the SMPP v 3.4 standard. Below are some of the Moyamas's specific command_status response codes:
Command Status | Description |
---|---|
The short_message field will contain the contents relevant information on the delivery status of your message for DLR and contents of the messaage for MO.
The format is as below:
An example below:
Below is the description of each field:
id - the unique message ID allocated to the message, this will be hexadecimal in most case except if otherwise required by the upsream MNO.
sub - the number of short messages originally submitted
dlvrd - the number of short messages delivered
submit date - the date and time at which the short message was submitted in YYMMDDHHMMSS
done date - the date and time at which the short message reached its final state in YYMMDDHHMMSS
stat - the final status of the message
err - SMPP DLR error code.
text - none
DELIVRD
UNDELIV
EXPIRED
ACCEPTD
UNKNOWN
ENROUTE
REJECTD
0x00000400
Message Not Routeable
0x00000401
Out of Credit
0x00000402
Maximum Credit Exceeded
0x00000403
Account Frozen
0x00000404
Bad Data
0x00000405
ESME Client Error
0x0000040a
Subscriber on DND or Restricted SenderID
0x00000430
Invalid Payload Length. Used to Limit Short_message and Message_payload to GSM PDU Length.
0x00000431
Internal Error
0x00000432
Restricted PDU. Means Message Denied in SPAM Filter
0x00000433
DCS Inconsistency. Which Means the the Data_coding Value Does not Seem to Match the Encoding in the Payload.
0x000004ff
Internal Error
0x00000045
Subscriber on DND
0x00000058
Throughput Exceeded