obsy / sms_tool Goto Github PK

I have a tplink mr6400 v5, figured out my usb device is ttyUSB2
Storage type: ME, used: 3, total: 23
Unfortunately I can't send USSD codes nor sms messages. Sending ussd gives me "error: retry operation" and sending sms doesnt actually complete
I have tried various combinations of settings with no luck so far.

Hi, I'm going to use ModemManager for LTE broadband internet access (via QMI).
Can I use sms_tool along with it to handle SMS?

Hi sir!
I am a newbie.
I am wanting to use your tool for SierraWireless EM7565 in openwrt 21.02.1 with Raspberry Pi4 router.
I really don't know what materials are needed in combination with your source code to build the sms-tool.ipk file.
Can you give me detailed instructions please?
Thank you very much!

DUT:
Nexx WT3020 (8M) + huawei E3131

SUT:
OpenWrt 19.07-SNAPSHOT, r10949-c56ed72d2b
Package: sms-tool
Version: 2019-08-25-20030ff6-1
Architecture: mipsel_24kc

Test procedure:
1/ Send short SMS with only one letter 'O' to the 3g modem
2/ Receive SMS: sms_tool -d /dev/ttyUSB2 recv

Observation:
MSG: 0
From: 48x
Date/Time: 06/24/20 13:28:52
Test zwrotny

MSG: 1
error decoding pdu 1: 07918405210077F7000B91848XXXXXXXF5000002604231437380014F

Additional info:
Injecting same pdu buffer into the program on Linux platform gives proper result:
$ ./sms_tool -r test
07918405210077F7000B91848XXXXXXXF5000002604231437380014F
$ ./sms_tool test
From: 48XXXXXXXXX
Date/Time: 06/24/20 13:34:37
O

sms_tool produce no output on AT+QTEMP command on my EM12-G modem:

root@OpenWrt:~# sms_tool -d /dev/ttyUSB2 at "AT+QTEMP"
AT+QTEMP
root@OpenWrt:~#

But if I send this AT command directly to tty port using minicom the output is present:

AT+QTEMP
OK

+QTEMP: "xo_therm_buf","33"

+QTEMP: "mdm_case_therm","33"

+QTEMP: "pa_therm1","33"

+QTEMP: "tsens_tz_sensor0","35"

+QTEMP: "tsens_tz_sensor1","35"

+QTEMP: "tsens_tz_sensor2","35"

+QTEMP: "tsens_tz_sensor3","34"

+QTEMP: "tsens_tz_sensor4","35"

I think the problem appers because this AT command say OK at first

SUT: cda9417 (self-compiled using LEDE SDK)

First of all - thank you for providing this great tool! It works for me basically, however I observed some decoding/encoding issues when using orange.pl:

# sms_tool -d /dev/ttyUSB1 -R ussd "*103*#"
unparsable CUSD response: "Zlecenie zostalo przyjete do realizacji. O jego wyniku poinformujemy Cie osobnym SMSem.", 15

Without using -R, the output is just unparsable CUSD response: without any details.

Now, when reading the received SMS, it seems it can't be decoded:

# sms_tool -d /dev/ttyUSB1 -f "%Y-%m-%d %H:%M" recv
MSG: 1
From: Orange@�qc
Date/Time: 2017-12-31 22:32

MSG: 2
From: Orange@�
Date/Time: 2015-06-05 11:05
Twoje konto zostalo doladowane. Dodatkowo otrzymales bonus na polaczenia z internetem. Masz lacznie 12095,8 MB na polaczenia z internetem wazne do 08.11.2015.

Using the operators -R and -r it seems there is some content in the message (I don't want to post it here because I don't know if it may contain sensitive data).

Interestingly, the issue does not arise for way older messages from the same operator (where the FROM did not contain a name but just a number):

MSG: 19
From: 7095
Date/Time: 2015-11-05 10:02
W dniu 08.11.2015 konczy sie okres waznosci twojego bonusu na start i za doladowanie. Pozostalo Ci jeszcze 7311 MB do wykorzystania. Szczegoly na www.orange.pl

The examples on the web site also use messages with numbers in the "FROM" field, so I suspect it could be related to that.

Thank you and all the best for the coming year!

我测试发送中文短信，对方接收显示全是？？？？？？乱码

I have installed OpenWRT on the TP-Link TL-MR6400. Unfortunately SMS reception does not work (the command sms_tool -d /dev/ttyUSB0 recv shows nothing). But the SMS sending works.

Output sms_tool -d /dev/ttyUSB0 status:

Storage type: SM, used: 0, total: 20

Output sms_tool -s ME -d /dev/ttyUSB0 status:

Storage type: ME, used: 0, total: 23

What could be the cause of this? What troubleshooting information do you need?

Hi, sms_tool binary does fail to be executed on a Turris Omnia (Marvell 385 Armada, armv7 arch with dual-core ARM Cortex-A9) with system TurrisOS (openWRT based) up-to-date until today, with following message:

Error relocating /usr/bin/sms_tool: __gmtime64: symbol not found
Error relocating /usr/bin/sms_tool: __timegm_time64: symbol not found

Using latest github sms-tool_2021-12-03-d38898f4-1_arm_cortex-a9_vfpv3-d16.ipk from https://github.com/4IceG/luci-app-sms-tool releases page package.

I also opened an issue at that repo there but author pointed me to ask here about: 4IceG/luci-app-sms-tool#11

Any hints?

My mobile operator, MTS Russia, supports the '*100#' USSD code as a way to check balance. However, this code doesn't work with sms_tool.

root@R7800:~# sms_tool -D ussd '*100#'
debug: AT+CUSD=1,"AA180C3602",15

debug: +CUSD: 0,"04110430043B0430043D0441003A0032003200320030002C003700360440",72

"

So, as you can see, the PDU is decoded to ", while it should decode to Баланс:2220,76р.