Changelog

A chronicle of bits flipped, bytes decoded, and PDUs tamed. Here's what's been happening in the wonderful world of SMPP decoding!

April 2026

April 15, 2026

  • 0x-prefixed Hex Input: You can now paste PDU hex strings with 0x prefixes and spaces, like 0x000000AF 0x00000004 0x00000000 0x000066E4. The decoder will strip the prefixes and whitespace automatically.

December 2025

December 18, 2025

  • Message ID Display for Response PDUs: The submit_sm_resp now proudly displays its Message ID in a dedicated "Response Data" section. No more wondering what ID the SMSC assigned to your message!
  • Changelog Page: You're looking at it! Now you can keep track of all the improvements we make to the decoder.

November 2025

November 17, 2025

  • Delivery Receipt Parsing: We taught the decoder to read delivery receipts! Now it can parse all those cryptic id:xxx sub:001 dlvrd:001 submit date:... strings and display them in a beautiful, structured format.
  • Hex/ASCII Column Separation: The hex dump now lets you select hex bytes and ASCII characters independently. Finally, you can copy just the hex without getting a face full of dots and question marks!
  • TLV Support for deliver_sm: Fixed delivery receipt parsing for PDUs with optional TLV parameters. Because why would the SMSC make things simple?

November 1, 2025 - First Release!

And lo, from the primordial soup of hexadecimal strings, a decoder was born! After countless cups of coffee and even more PDU parsing errors, we're thrilled to release the first version of SMPP PDU Decoder.

  • Core Decoder Engine: Built from scratch with love, TypeScript, and an unhealthy obsession with the SMPP 3.4 specification.
  • Full PDU Support: Decode bind_*, submit_sm,deliver_sm, enquire_link, query_sm, and all their response friends.
  • TLV Parsing: Over 50 optional parameter tags recognized and decoded. We even know what sar_msg_ref_num means!
  • Multi-Encoding Support: GSM-7, GSM-8, Latin-1, ASCII, and UCS-2. Because the world speaks many languages, and so do SMSCs.
  • UDH Parsing: Concatenated messages, port addressing, and all those fancy User Data Header elements? We've got you covered.
  • Beautiful PDU Breakdown: Visual representation of every byte in your PDU, color-coded and tooltipped for your debugging pleasure.
  • 100% Client-Side: Your PDUs never leave your browser. What happens in the decoder stays in the decoder. Vegas would be proud.
  • Example PDU Library: A curated collection of PDUs for testing and learning. Like a petting zoo, but for protocol buffers.