USSD decoding in EG915U-EU

Hi,

I develop a new version of a product with EG915U-EU modem that replaced the M95FB (previously used with a great success).
The EG915 module connects to LTE network, sends and receives SMS without any problems, looks allright.

In the “EC200U&EG915U_Series_AT_Commands_Manual” we can find that it also should support USSD operations (AT+CUSD command, page 186).

However, when I send the USSD request, the response appears as some raw binary data with unknown encoding:

  • when my MCU sends the request:
    AT+CUSD=1,"101#"
  • no “OK” response is returned from the module,
  • 11 seconds later, here comes the following result code, with some sort of binary data:
    +CUSD: 2, "Y^UadT:bfMX2r@$“$Z9 =#aD]0lR” ,0

What is the coding scheme of this data? Shouldn’t it be in 7-bit ASCII encoding?

The previous module (M95FB) with the same SIM card, always returns, to the same request, a human-readable, plain ASCII string in +CUSD result code, exactly as it is displayed in a mobile phone.

In the EG915U manual (page 188) we can only find one sentence regarding the USSD result code:
For an USSD response from the network, or a network-initiated operation, the format is: +CUSD: status[,rspstr, [dcs]].
where:
rspstr String type. Unstructured Supplementary Service Data (USSD) received from the network.

… but rspstr= "Y^UadT:bfMX2r@$“$Z9 =#aD]0lR” does not look like a string,
and also dcs=0 looks weird and makes no sense (German language, according to 3GPP TS 23.038 ? - not possible in my network and location).

Best regards,
Pablo

What’s your AT+CSCS? command result? If it’s “HEX”, try AT+CSCS="IRA" instead.

See 3GPP 27.007, sections 5.5 and 7.15.

Hi,
Unfortunatelly,this setting looks irrelevant to the format of USSD result code from EG915U-EU.
“GSM” was the initial setting.
Then I tried different values of +CSCS but with the same effect - unchanged binary data:

18:01:16.054, +CSCS: “GSM”
18:01:16.054, +QCSQ: “LTE”,91,-124,42,-16
18:01:18.490, AT+CUSD=1,“*101#”
18:01:24.992, +CUSD: 2, “Y^UadT:bf
18:01:25.055, MX2r@$“$Z9 =#aD]0lR” ,0
18:01:25.055, OK

18:02:19.240, +CSCS: “PCCP936”
18:02:22.616, AT+CUSD=1,”*101#"
18:02:28.804, +CUSD: 2, “Y^UadT:bf
18:02:28.804, MX2r@$“$Z9 =#aD]0lR” ,0
18:02:28.866, OK

18:05:36.427, +CSCS: “HEX”
18:05:44.177, AT+CUSD=1,”*101#"
18:05:53.429, +CUSD: 2, “Y^UadT:bf
18:05:53.429, MX2r@$“$Z9 =#aD]0lR” ,0
18:05:53.429, OK

18:06:13.991, +CSCS: “IRA”
18:06:17.054, AT+CUSD=1,”*101#"
18:06:24.240, +CUSD: 2, "Y^UadT:bf
18:06:24.240, MX2r@$“$Z9 =#aD]0lR” ,0
18:06:24.240, OK

Best regards,
Pablo

It’s certainly looking like a problem with the new modem itself.