SMS Forum Support
SMS Forum Support
This topic details errata found in the SMPP V5.0 specification since its release.
Section 220.127.116.11 submit_sm Syntax
Message Submission TLVs referenced at the end of PDU table should read "Message Submission Optional TLVs" to better define these TLVs as optional. The same issue applies to PDU definitions for submit_sm_resp, deliver_sm, deliver_sm_resp, data_sm, data_sm_resp, replace_sm & replace_sm_resp
Section 18.104.22.168 submit_multi Syntax
dest_address max size for distribution list is listed as 23. However the maximum length of the dl_name is 21 and dl_flag is 1.. totals 22 and not 23 as printed.
Section 22.214.171.124 query_broadcast_sm_resp Syntax
message_id is incorrectly marked as Integer type, should be C-octet string.
message_state is listed as the TLV form but refers incorrectly to section 4.7.15 instead of section 126.96.36.199.
Section 4.7.12 esm_class
esm_class field is described in a single table intended to depict the usage across all submission & delivery operations. However 2nd paragraph does not reflect this.
The esm_class parameter is encoded as follows in the submit_sm, submit_multi and data_sm (ESME -> MC) PDUs:
The esm_class parameter is encoded as follows in the submit_sm, submit_multi, deliver_sm and data_sm PDUs:
Section 4.7.21 registered_delivery
Table 4-52 describes all settings for registered_delivery field. The settings for "SME originated Acknowledgement (bits 3 and 2)" are not listed as CDMA/TDMA only features.
For clarity, these rows should have the side label updated to "ANSI-41 SME originated Acknowledgement (bits 3 and 2)"
Section 188.8.131.52 Relative Time Format
Relative value ranges for Month and Day should include 0 to allow for relative times of 0 months, 0 days. Otherwise it is possible to interpret all relative times as requiring a minimum of 1 month, 1 day which restricts the feature.. that was never the intention.
YY year (00-99)
MM month (01-12) << should be 00-12
DD day (01-31) << should be 00-31
hh hour (00-23)
mm minute (00-59)
ss second (00-59)
Section 184.108.40.206 broadcast_message_class
Value of class 1 should be 0x01 and not 0x02 as printed.