Skip to content

fix: read the TAR of 03.48 response packets at the right offset - #3

Merged
mjfelis merged 1 commit into
mainfrom
fix/por-tar-offset
Sep 17, 2026
Merged

mjfelis merged 1 commit into
mainfrom
fix/por-tar-offset

Conversation

@mjfelis

@mjfelis mjfelis commented Sep 16, 2026

Copy link
Copy Markdown
Member

Part of the RAM (applet install over the air) campaign work. Library version 1.0.23.

PacketUtil.getCommandPacketTar reads the TAR at offset 10, which is correct for a command packet (IEI 0x70: UDH, CPL, CHL, SPI, KIc, KID, TAR). A response packet / Proof of Receipt (IEI 0x71: UDH, RPL, RHL, TAR) carries the TAR at offset 6 (ETSI TS 102 225 section 5.2; etsi102225's PacketBuilderImpl places the response counters at offset 6 after the 3 byte TAR, i.e. TAR at 3 without UDH).

Added, without changing existing methods:

  • isResponsePacket(msg)
  • getResponsePacketTar(msg)
  • getPacketTar(msg): picks the offset from the UDH IEI, null when the message is not a packet
  • stripUdh(msg)

Used by mno-adapters-smpp-client (PoR classification) and mno-adapters-ustk (PoR decoding). Merge before those.

A command packet (IEI 0x70) carries the TAR at offset 10, a response packet /
Proof of Receipt (IEI 0x71) at offset 6, right after RPL and RHL. Add
isResponsePacket, getResponsePacketTar, getPacketTar (IEI aware) and stripUdh.
Version 1.0.23.
@mjfelis
mjfelis merged commit 462f09f into main Sep 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant