> :put [$HexGSM7toCP1252 "C8329BFD065DDF72363904"]
Invalid 7-bit value (200)
It is possible that only the value of the DCS field is missing to determine the encoding method. Perhaps there is something else to pay attention to. Perhaps some other sequence of actions is needed. I would like to understand two options for solving this situation, including when the DCS field is equal to “08”. The first option is how to use the above functions. The second option - what is the general recoding algorithm
> :put [$HexGSM7toCP1252 [$pdutogsm7 ("\D4\F2\9C\0E\6A\97\E7\F3\F0\B9\0C\A2\BF\41\41\2A\68\F8\6E\B7\C3\6E\32\88\5A\9E\D3\CB\72")]]
Test message to AT Command Tester
> :put [$HexGSM7toCP1252 [$pdutogsm7 ("\DC\E5\32\B9\4C\06\CD\DF\6F\37")]]
Invalid PDU data, expected value not provided.
I didn't say I thought it was useless. On the contrary, I assumed that I did not take into account something. But I would like to understand why, in the case of a composite SMS, headers are also needed.
What are these signs? Because if you take a real SMS, then they are not there. Text only
Why these slashes? Is this specific to your function, or is it a prerequisite for decoding in general?
And the question arises, if the DCS field = "08", then what should be done and in what order? Including when to place slashes?
I would also like to mention a solution from someone who is not present on this forum (at least I haven’t seen them here), but their function also works. Currently, I have made some modifications to it, adding optional arguments that might allow adding encoding functions to UCS2/UTF8/url/translit in the future.
Although, as far as I know, the author has a solution for encoding conversion in all directions.