Parsing '@' character in 7 bit pdu

salon_sue

Good afternoon everyone. I'm writing an SMS message parser. Everything works fine, except for one thing. In some cases, the '@' character is parsed as 0x00 instead of 0x40. I tried several code samples, and they all returned the same results. The online PDU parser, however, assembles the packet correctly. Here's the code I'm using: uint8_t uArr[] = {0xF0, 0x7B, 0x2F, 0x26, 0x9B, 0xD1, 0x6A, 0xB6, 0x78, 0x94, 0x05, 0x9F, 0xF7, 0x00, 0xA6, 0xDD,...

Originally asked by Mishakol on Stack Exchange (stackoverflow) (CC BY-SA 4.0).

uphilltech

Great question — answering as the UphillTech team:

The decoded output from the code in the question is correct; the correct output is “w=123456qQ,ps= N &;?!-/:;”, where N is the null character, not “@”. The web page you are using displays “@” when the output character is zero. It likely uses “@” as a placeholder in this case because otherwise a zero byte is not printable. This can be test by taking the message data you provided, 07919781340310F1040B919751390289F700006250405143512119F07B2F269BD16AB67894059FF76200D3EE176ABD743B, and replacing the 14 digits starting at that “F0” with zeros, yielding 07919781340310F1040B919751390289F70000625040514351211900000000000000B67894059FF76200D3EE176ABD743B. When we ask the web page you link to to decode...

Full answer by Eric Postpischil: https://stackoverflow.stackexchange.com/a/79935893 (CC BY-SA 4.0).

Need it done for your business? UphillTech.