Editing Short Message Peer-to-Peer (section)

===PDU body===
 'service_type',                 () ... 00
 'source_addr_ton',             (2) ... 02
 'source_addr_[[Numbering plan|npi]]',             (8) ... 08
 'source_addr',               (555) ... 35 35 35 00
 'dest_addr_ton',               (1) ... 01
 'dest_addr_[[Numbering plan|npi]]',               (1) ... 01
 'dest_addr',           (555555555) ... 35 35 35 35 35 35 35 35 35 00
 'esm_class',                   (0) ... 00
 'protocol_id',                 (0) ... 00
 'priority_flag',               (0) ... 00
 'schedule_delivery_time',      (0) ... 00
 'validity_period',             (0) ... 00
 'registered_delivery',         (0) ... 00
 'replace_if_present_flag',     (0) ... 00
 'data_coding',                 (3) ... 03
 'sm_default_msg_id',           (0) ... 00
 'sm_length',                  (15) ... 0F
 'short_message', (Hello Wikipedia) ... 48 65 6C 6C 6F 20 57 69 6B 69 70 65 64 69 61

Note that the text in the short_message field must match the data_coding. When the data_coding is 8 (UCS2), the text must be in UCS-2BE (or its extension, [[UTF-16|UTF-16BE]]). When the data_coding indicates a 7-bit encoding, each septet is stored in a separate octet in the short_message field (with the most significant bit set to 0). SMPP 3.3 data_coding exactly copied TP-DCS values of [[Data Coding Scheme|GSM 03.38]], which make it suitable only for GSM 7-bit default alphabet, UCS2 or binary messages; SMPP 3.4 introduced a new list of data_coding values:

{| class="wikitable"
! <code>data_coding</code> !! Meaning
|-
| style="text-align:center" | 0 || SMSC Default Alphabet (SMPP 3.4) / MC Specific (SMPP 5.0)
|-
| style="text-align:center" | 1 || IA5 ([[ITU T.50|CCITT T.50]])/[[ASCII]] (ANSI X3.4)
|-
| style="text-align:center" | 2 || Octet unspecified (8-bit binary)
|-
| style="text-align:center" | 3 || Latin 1 ([[ISO-8859-1]])
|-
| style="text-align:center" | 4 || Octet unspecified (8-bit binary)
|-
| style="text-align:center" | 5 || JIS ([[JIS X 0208|X 0208-1990]])
|-
| style="text-align:center" | 6 || Cyrillic ([[ISO-8859-5]])
|-
| style="text-align:center" | 7 || Latin/Hebrew ([[ISO-8859-8]])
|-
| style="text-align:center" | 8 || UCS2 ([[Universal Coded Character Set|ISO/IEC-10646]])
|-
| style="text-align:center" | 9 || Pictogram Encoding
|-
| style="text-align:center" | 10 || [[ISO-2022-JP]] (Music Codes)
|-
| style="text-align:center" | 11 || Reserved
|-
| style="text-align:center" | 12 || Reserved
|-
| style="text-align:center" | 13 || Extended Kanji JIS (X 0212–1990)
|-
| style="text-align:center" | 14 || [[KS C 5601]]
|-
| style="text-align:center" | 15-191 || reserved
|-
| style="text-align:center" | 192-207 || GSM MWI control - see [[Data Coding Scheme|GSM 03.38]]
|-
| style="text-align:center" | 208-223 || GSM MWI control - see [[Data Coding Scheme|GSM 03.38]]
|-
| style="text-align:center" | 224-239 || reserved
|-
| style="text-align:center" | 240-255 || GSM message class control - see [[Data Coding Scheme|GSM 03.38]]
|}

The meaning of the <code>data_coding=4</code> or <code>8</code> is the same as in SMPP 3.3. Other values in the range 1-15 are reserved in SMPP 3.3. Unfortunately, unlike SMPP 3.3, where data_coding=0 was unambiguously GSM 7-bit default alphabet, for SMPP 3.4 and higher the GSM 7-bit default alphabet is missing in this list, and <code>data_coding=0</code> may differ for various [[Short message service center]]s—it may be [[ISO-8859-1]], [[ASCII]], GSM 7-bit default alphabet, [[UTF-8]] or even configurable per ESME. When using <code>data_coding=0</code>, both sides (ESME and SMSC) must be sure they consider it the same encoding. Otherwise it is better not to use <code>data_coding=0</code>. It may be tricky to use the GSM 7-bit default alphabet, some [[Short message service center]]s requires <code>data_coding=0</code>, others e.g. <code>data_coding=241</code>.