How to decode Concatenated SMS received via Receive API

[Francesco Disoteo]

Hi,

I use a servlet to receive the XML POST of the Receive API.

In case of Concatenated SMS I receive 7 bytes headers which only in part adheres to the rules at:

http://en.wikipedia.org/wiki/Concatenated_SMS

More precisely, the bytes received ar (for a 3 parts message):

1st msg: E9 40 6F 28 31 20 40

2nd msg: E9 40 6F 28 31 A1 40

3rd msg: E9 40 6F 28 31 BF 40

The only rules matched as reported by wiki are:

“Field 4” is the same for all parts.

The “Field 5” should contain the total number of parts, but it seems a bit too much for 3 message parts.

The “Field 6” is the only variable parts, but should evaluate from 1 to N (where N is the number of parts) while in my tests it seems to be random.

Where am I wrong ? Cold you please help me ?

Thanks

Francesco

[Steve Tuckner]

The iSMS doesn’t support PDU mode, so we don’t pass the PDU headers to the receive API. We only pass the message contents. So a three part message will appear as three separate messages.

[Francesco Disoteo]

Thank you Steve,

but what is the meanings of the “strange” characters I can see in the first 7 bytes ?

For example, each part of a long message is sent in XML as follows (the YYY… sequence is the text body part of the text I sent):

“é@oHt¿£YYYYYYYYY”

but the first 7 characters ? Apart from different values, it seems that the rules for the UDH reported from wiki should fit, at least at a semantical level.

Thanks again

[Author]

Posts