c# - USSD command translation -


I need help decoding this received response.

  OK + CUSD: 0, AR @? $ @ 9 d ?? @ ??? (D ??) @@ 1 PD? "? T? HC @? Amp;? @D ???? @ ?? 5 41 IA? R", 17 OK + CUSD: 0, "AR? Hb ?? '10? @? Hb @? J @ @ @. @ @ @ @ @ @ @ @ Mp3. @ @ @ @ @ @ @ @ Jaquintsonline.com When I was looking for the price of DCS on other network providers, it was a value of 17 Do not understand how to decode it  

after the result:

  + CSCS AT = "UCS2" + CUSD = 1, "002a003100350030002a0032002a00330032003300390031002a00360039003100370037002a00310023" OK, 15+ CUSD: 0, "00610072003f00680062003f0020003f00270020002000310030003f00400020003f0020003f006800620040003f004a00400040003f0040003f003f0020004000660040003f003f0040003f00400053004000640024 0040 ", 17 AT + CSMP + CSMP: 17,167,0,0 OK   

The way it is when I set it on my + CSCS =" UTF-8 "report this error but it is The report is back with this command AT + CSCS =?

The format of the response is as follows: / p>

  + CUSD = [& LT; N & gt; [& Lt; Str & gt; [& Lt; DCS & gt;]]]   

The third parameter is thus . & Lt; DCS & gt; Its format just stops:

  & lt; DCS & gt;: 3GPP TS 23.038 [25] Cell Broadcasting Data Coding In Sch integer format IME (default 0)   

Chapter "5 CBS Data Coding Scheme" in 23.038 This code can also be used for USSD

17, binary 0001 0001:

  • Bit 7..4 coding group Bits = 0001
  • bit 3..0 = 0001 - - & gt; UCS2; Before the message language sign

    and it has been said that

    Introducing an MS UCS2 identifier two character language after the user data interpreted inappropriately Will not support coding

    which is actually in the case of its production (for example ar after meaning Arabic garbage)

    For 72, binary 0100 1000 .:

    • Bit 7..4 coding group bits = 01xx
    • bit 5 = 0 - & gt; Uncompressed,
    • bit 4 = 0 - & gt; No squares mean
    • bit 3 & amp; 2 = 1 & amp; 0 - & gt; UCS2 (16bit)

      The above mentioned part may not be supporting that you are using limited character set encoding (PCCP 437). In any case, unless your modem does not support UTF-8, you should actually use it and not PCCP437. Or you can use USC2 if your modem lacks those two letters, then you have guessed about what I saw while checking the hex (this answer, maybe you have & lt; dcs & gt; parameter will be set to AT + CSMP to do this work?).

      Note that after selecting UCS2, each string should be encoded in that way, including switching to other character sets, for example see.

Comments

Popular posts from this blog

Verilog Error: output or inout port "Q" must be connected to a structural net expression -

jasper reports - How to center align barcode using jasperreports and barcode4j -

c# - ASP.NET MVC - Attaching an entity of type 'MODELNAME' failed because another entity of the same type already has the same primary key value -