Operating system name and version: Ubuntu 16.04
Version of smsd: 3.1.21
Smsd installed from: sources
Name and model of a modem / phone: D-link
Interface: serial / USB

devices = GSM1 logfile = /var/log/smsd.log loglevel = 7 sent = /var/spool/sms/sent store_received_pdu = 3 report = /var/spool/sms/report store_sent_pdu = 3 stats = /var/spool/sms/stats [queues] GSM1 = /var/spool/sms/queue/GSM-QUEUE1 [GSM1] report_device_details = yes routed_status_report_cnma = no report = yes init = AT+CNMI = 1,0,0,1,0 device = /dev/ttyUSB0 incoming = high baudrate = 9600 primary_memory = SM secondary_memory = ME regular_run_interval = 30 regular_run = /var/spool/sms/regular_run/GSM1.sh regular_run_cmdfile = /var/spool/sms/regular_run/GSM1.cmdfile queues=GSM1

When I send the ussd code to retrieve the balance of my credit, I get the following error:

2017-09-16 23:56:36,6, GSM1: Running a regular_run (PRE_RUN) 2017-09-16 23:56:36,7, GSM1: Running regular_run (modem): /var/spool/sms/regular_run/GSM1.sh PRE_RUN "" GSM1 2017-09-16 23:56:36,7, GSM1: Done: regular_run (modem), execution time 0 sec., status: 0 (0) 2017-09-16 23:56:36,7, GSM1: -> AT+CUSD=1,"*140*11#" 2017-09-16 23:56:36,7, GSM1: Command is sent, waiting for the answer. (15) 2017-09-16 23:56:52,7, GSM1: Incorrect answer, put_command expected (\+CUSD:.*",)|(ERROR), timeout occurred. 1. 2017-09-16 23:56:52,7, GSM1: <- OK 2017-09-16 23:56:52,5, GSM1: CMD: AT+CUSD=1,"*140*11#": OK

Is there other port than ttyUSB0 provided by the modem? If there is, try to use another port. Some modems provide multiple ports, and USSD does not work with all ports.

Here's the output of wvdialconf:

Scanning your serial ports for a modem. Modem Port Scan<*1>: S0 S1 S2 S3 S4 S5 S6 S7 Modem Port Scan<*1>: S8 S9 S10 S11 S12 S13 S14 S15 Modem Port Scan<*1>: S16 S17 S18 S19 S20 S21 S22 S23 Modem Port Scan<*1>: S24 S25 S26 S27 S28 S29 S30 S31 WvModem<*1>: Cannot get information for serial port. ttyUSB0<*1>: ATQ0 V1 E1 -- OK ttyUSB0<*1>: ATQ0 V1 E1 Z -- OK ttyUSB0<*1>: ATQ0 V1 E1 S0=0 -- OK ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK ttyUSB0<*1>: Modem Identifier: ATI -- MTK2 ttyUSB0<*1>: Speed 9600: AT -- OK ttyUSB0<*1>: Max speed is 9600; that should be safe. ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK WvModem<*1>: Cannot get information for serial port. ttyUSB1<*1>: ATQ0 V1 E1 -- OK ttyUSB1<*1>: ATQ0 V1 E1 Z -- ATQ0 E1 Z ttyUSB1<*1>: ATQ0 V1 E1 S0=0 -- Q0 V1 E ttyUSB1<*1>: ATQ0 V1 E1 &C1 -- OK ttyUSB1<*1>: ATQ0 V1 E1 &C1 &D2 -- OK ttyUSB1<*1>: ATQ0 V1 E1 &C1 &D2 +FCLASS=0 -- OK ttyUSB1<*1>: Modem Identifier: ATI -- MOLY.WR8.W1244.DNR.WG.MP.V7 ttyUSB1<*1>: Speed 9600: AT -- OK ttyUSB1<*1>: Max speed is 9600; that should be safe. ttyUSB1<*1>: ATQ0 V1 E1 &C1 &D2 +FCLASS=0 -- ATQ0 V1 2 +FCLAS ttyUSB1<*1>: failed with 9600 baud, next try: 9600 baud ttyUSB1<*1>: ATQ0 V1 E1 &C1 &D2 +FCLASS=0 -- OK WvModem<*1>: Cannot get information for serial port. ttyUSB2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyUSB2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud ttyUSB2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. WvModem<*1>: Cannot get information for serial port. ttyUSB3<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyUSB3<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud ttyUSB3<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Found a modem on /dev/ttyUSB0. Modem configuration written to /etc/wvdial.conf. ttyUSB0<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" ttyUSB1<Info>: Speed 9600; init "ATQ0 V1 E1 &C1 &D2 +FCLASS=0"

It seems there are two ports ttyUSB0 and ttyUSB1.

I checked both ports with miniterm.py. The output of port ttyUSB0 is as follows:
AT OK at+cusd=1, "*140*11#" OK

and there is no correct output!! And for port ttyUSB1 I cannot send any AT commands and I get error.

I did some more tests. I think I should send the USSD code via /dev/ttyUSB0 and receive the result from /dev/ttyUSB1!! The problem is that how can I make use of this behavior in smstools?? I mean how can I use both ports in smstools3 to send and receive the result of the USSD codes?

All,

I have a language problem and a provider problem and your help solving them will be much appreciated.

My modem is a ZTE MF112, my provider is the German e-plus. When querying the prepaid balance using
AT+CUSD=1,"*100#"
I get error 258 (device busy). This is true for both smsd via GSM1.sh and a direct AT-command based conversation with the modem.

However, I can get an answer by requesting the German character set in a third argument (15) to CUSD:
AT+CUSD=1,"*100#",15 +CUSD: 0,"00490068007200200047007500740068006100620065006E0020006200650074007200E400670074003A00200039002C003700370020002E",72

This can be decoded to "Ihr Guthaben beträgt: 9,77 ."


Questions:

1.) what is a good way of splicing the extra argument in? The proposed GSM1.sh does not appear to support this. Maybe there is a general AT command I could use for setting the character set in all modem responses?

2.) the answer is funny in that it contains '00' as every second byte, potentially making decoding fail. Any thoughts on this?

3.) the response does not yield the remaining time for using the SIM card. For this I need to use *102#. A sample answer would then be (after removing zeroes and decoding): "Das aktuelle Aktivitätszeitfenster Ihrer SIM-Karte endet am 24.08.2018 und kann durch weitere Aufladungen verlängert werden." Nice and clean.

I could configure a first script for balance (say GSM1.sh) and a second one (GSM2.sh) for time. Can anybody think of a more elegant way to check both figures in one go?

Kind regards

birnbacs

birnbacs,

The response is hexadecimal representation of UCS2 encoding. Use a modem setting ussd_convert = 1 to decode it.

You could just handle the expiration manually, as it does not change all the time.

Quote

I did some more tests. I think I should send the USSD code via /dev/ttyUSB0 and receive the result from /dev/ttyUSB1!! The problem is that how can I make use of this behavior in smstools?? I mean how can I use both ports in smstools3 to send and receive the result of the USSD codes?

Dear Keke, Do you have any idea for the above issue?
Thanks.

keke wrote

birnbacs,

The response is hexadecimal representation of UCS2 encoding. Use a modem setting ussd_convert = 1 to decode it.

You could just handle the expiration manually, as it does not change all the time.

Thanks a ton but this did not make much differende. GSM1.balance still reads:
Last_query: 2017-09-21 08:05:31 Messages: Balance: -1 2017-09-21 08:05:31,5, GSM1: CMD: AT+CUSD=1,"*100#": OK +CME ERROR: 258 (Phone is busy)

keke wrote

birnbacs,

The response is hexadecimal representation of UCS2 encoding. Use a modem setting ussd_convert = 1 to decode it.

You could just handle the expiration manually, as it does not change all the time.

Thanks Keke,

I will work on problems 2 and 3 as soon as I get there, I am sure I will find a solution.
I am still blocked by problem #1 though. Do you have any idea on fixing the problems issuing the USSD command?

birnbacs wrote

I am still blocked by problem #1 though. Do you have any idea on fixing the problems issuing the USSD command?

Did you try this:

ussd_command="AT+CUSD=1,\"*100#\",15"

keke wrote

birnbacs,

The response is hexadecimal representation of UCS2 encoding. Use a modem setting ussd_convert = 1 to decode it.

You could just handle the expiration manually, as it does not change all the time.

I found a solution to problem 1 and it is embarrassingly straightforward:
GSM1.sh now contains the line
ussd_command="AT+CUSD=1,\"*100#\",15

sinai wrote

Quote

I did some more tests. I think I should send the USSD code via /dev/ttyUSB0 and receive the result from /dev/ttyUSB1!! The problem is that how can I make use of this behavior in smstools?? I mean how can I use both ports in smstools3 to send and receive the result of the USSD codes?

Dear Keke, Do you have any idea for the above issue?
Thanks.

Smstools3 cannot use dual ports for single modem. As this issue is rare, and you likely will have problems with delivery reports too, I'm not willing to create dual-port facility to this software. I recommend to buy a better modem.