Revision history [back]
This GSM SMS message really seems to be malformed. It's header indicates that the TP-User-Data-Header is present. So the TP-User-Data 20 58 0E 86 c3 01 starts with a User Data Header. Per 3GPP 23.040 chapter 9.2.3.24, the first byte (here 0x20) is the length of the header. But there are only 5 bytes remaining in the payload and not 32, thus the decoding failure. What was the expected content of the SMS message?
This GSM SMS message really seems to be malformed.
It's header indicates that the TP-User-Data-Header is present. So the TP-User-Data 20 58 0E 86 c3 01 starts with a User Data Header. Per 3GPP 23.040 chapter 9.2.3.24, the first byte firs tbyte (here 0x20) is the length of the header. But there are only 5 bytes remaining in the payload and not 32, thus the decoding failure.
32.
What was the expected content of the SMS message?
This GSM SMS message really seems to be malformed.
It's header indicates that the TP-User-Data-Header is present. So the TP-User-Data 20 58 0E 86 c3 01 starts start with a User Data Header. Per 3GPP 23.040 chapter 9.2.3.24, the firs tbyte (here 0x20) is the length of the header. But there are only 5 bytes remaining in the payload and not 32.
What was the expected content of the SMS message?