|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Thu Aug 21, 2025 19:39 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Tue Jul 28, 2020 22:40
|
camro: Hello,
it happens to me, that the /dev/ttyUSBx is not available or dying for whatever reason, but then the smstools as still running is writing to /dev/ttyUSB02, but is not existing to it is creating a file with:
AT-cmd inside. ...
normally i have devices:
/dev/ttyUSB0
/dev/ttyUSB1
/dev/ttyUSB2
/dev/ttyUSB3
and creating a link /dev/modem_sms to /dev/ttyUSB2
so, that works great 8as ttyUSB0 is used for 3G modem connection and ttyUSB3 using to get signal strenght
now i happens that the /dev/ttyUSB2 is not available for whatever reason, and smstools3 is sending a AT cmd to this non existing device, which creates a new file and write into: AT.....
on the other side, i have a smsalarm handler, which regonize that there is a device issue, and this will then restart the whole network to get all /dev/ttyUSB back.
BUt as /dev/ttyUSB2 now existing as file, it will create:
/dev/ttyUSB0
/dev/ttyUSB1
/dev/ttyUSB3
/dev/ttyUSB4
then it is also via start script called: /etc/init.d/device_links i will find and recreate the links to the given new dev name.
but when that happens again, it wil on next round do the same, and then on network restart i have then:
/dev/ttyUSB0
/dev/ttyUSB1
/dev/ttyUSB4
/dev/ttyUSB5
and on enxt round again
/dev/ttyUSB0
/dev/ttyUSB1
/dev/ttyUSB5
/dev/ttyUSB6
and so on ...
that is because smstools is not checking if device is existing.
so, my question: can you add to check if device is existing and only if it existis, then send cmd to sms modem.
or is there an option, to tell smstools to verify if device exists (before sending cmd to it) ?
is like:
if [ ! -e /dev/ttyUSB2 ] && [ ! -f /dev/ttyUSB2 ] ; then .... #device seems to be existing and is not a file
cu Camel
also showing my script to set the links to modem for info, sms, and modem
/etc/init.d/device_links
#!/bin/sh /etc/rc.common
START=17
STOP=90
DEVICE_modem="/dev/modem"
DEVICE_modem_info="/dev/modem_info"
DEVICE_modem_sms="/dev/modem_sms"
#logger -t DeviceLinks "Parameters 1=$1, 2=$2, 3=$3, 4=$4, 5=$5, 6=$6"
reload() {
stop
start
}
restart() {
stop
start
}
boot() {
start
}
start() {
if [ ! -e "$DEVICE_modem" ]; then
logger -t DeviceLinks "Device Start: *MODEM* $DEVICE_modem does not exist"
local try=0
local max=3
while [ $((++try)) -le $max ]; do
rm -f $DEVICE_modem 2> /dev/null || true
# Create link to lowest modem id
if [ -e /dev/ttyUSB0 ]; then
ln -sf /dev/ttyUSB0 "$DEVICE_modem"
elif [ -e /dev/ttyUSB1 ]; then
ln -sf /dev/ttyUSB1 "$DEVICE_modem"
else
logger -t DeviceLinks "Device Start: *MODEM* $DEVICE_modem still not set as no valid modem device found in system"
sleep 3
fi
done
logger -t DeviceLinks "Device Start: *MODEM* $DEVICE_modem now set to: $(readlink "$DEVICE_modem")"
else
logger -t DeviceLinks "Device Start: *MODEM* $DEVICE_modem already existing as: $(readlink "$DEVICE_modem")"
fi
if [ ! -e "$DEVICE_modem_info" ]; then
logger -t DeviceLinks "Device Start: *MODEM_INFO* $DEVICE_modem_info does not exist"
local try=0
local max=3
while [ $((++try)) -le $max ]; do
rm -f $DEVICE_modem_info 2> /dev/null || true
# Create link to higest modem id
if [ -e /dev/ttyUSB6 ]; then
ln -sf /dev/ttyUSB6 "$DEVICE_modem_info"
elif [ -e /dev/ttyUSB5 ]; then
ln -sf /dev/ttyUSB5 "$DEVICE_modem_info"
elif [ -e /dev/ttyUSB4 ]; then
ln -sf /dev/ttyUSB4 "$DEVICE_modem_info"
elif [ -e /dev/ttyUSB3 ]; then
ln -sf /dev/ttyUSB3 "$DEVICE_modem_info"
else
logger -t DeviceLinks "Device Start: *MODEM_INFO* $DEVICE_modem_info still not set as no valid modem_info device found in system"
sleep 3
fi
done
logger -t DeviceLinks "Device Start: *MODEM_INFO* $DEVICE_modem_info now set to: $(readlink "$DEVICE_modem_info")"
else
logger -t DeviceLinks "Device Start: *MODEM_INFO* $DEVICE_modem_info already existing as: $(readlink "$DEVICE_modem_info")"
fi
if [ ! -e "$DEVICE_modem_sms" ]; then
logger -t DeviceLinks "Device Start: *MODEM_SMS* $DEVICE_modem_sms does not exist"
local try=0
local max=3
while [ $((++try)) -le $max ]; do
rm -f $DEVICE_modem_sms 2> /dev/null || true
# Create link to med modem id
if [ -e /dev/ttyUSB2 ]; then
ln -sf /dev/ttyUSB2 "$DEVICE_modem_sms"
elif [ -e /dev/ttyUSB3 ]; then
ln -sf /dev/ttyUSB3 "$DEVICE_modem_sms"
elif [ -e /dev/ttyUSB4 ]; then
ln -sf /dev/ttyUSB4 "$DEVICE_modem_sms"
elif [ -e /dev/ttyUSB5 ]; then
ln -sf /dev/ttyUSB5 "$DEVICE_modem_sms"
elif [ -e /dev/ttyUSB6 ]; then
ln -sf /dev/ttyUSB6 "$DEVICE_modem_sms"
else
logger -t DeviceLinks "Device Start: *MODEM_SMS* $DEVICE_modem_sms still not set as no valid modem_sms device found in system"
sleep 3
fi
done
logger -t DeviceLinks "Device Start: *MODEM_SMS* $DEVICE_modem_sms now set to: $(readlink "$DEVICE_modem_sms")"
else
logger -t DeviceLinks "Device Start: *MODEM_SMS* $DEVICE_modem_sms already existing as: $(readlink "$DEVICE_modem_sms")"
fi
}
stop() {
rm -f $DEVICE_modem 2>/dev/null || true
logger -t DeviceLinks "Device Stop: *MODEM* $DEVICE_modem removed from system"
rm -f $DEVICE_modem_info 2> /dev/null || true
logger -t DeviceLinks "Device Stop: *MODEM_INFO* $DEVICE_modem_info removed from system"
rm -f $DEVICE_modem_sms 2> /dev/null || true
logger -t DeviceLinks "Device Stop: *MODEM_SMS* $DEVICE_modem_sms removed from system"
if [ -f /dev/ttyUSB1 ]; then
logger -t DeviceLinks "Device */dev/ttyUSB1* is a file - not a device type. Need to delete it"
echo "Device */dev/ttyUSB1* is a file - not a device type. Need to delete it"
rm -f /dev/ttyUSB1
fi
if [ -f /dev/ttyUSB2 ]; then
logger -t DeviceLinks "Device */dev/ttyUSB2* is a file - not a device type. Need to delete it"
echo "Device */dev/ttyUSB2* is a file - not a device type. Need to delete it"
rm -f /dev/ttyUSB2
fi
if [ -f /dev/ttyUSB3 ]; then
logger -t DeviceLinks "Device */dev/ttyUSB3* is a file - not a device type. Need to delete it"
echo "Device */dev/ttyUSB3* is a file - not a device type. Need to delete it"
rm -f /dev/ttyUSB3
fi
if [ -f /dev/ttyUSB4 ]; then
logger -t DeviceLinks "Device */dev/ttyUSB4* is a file - not a device type. Need to delete it"
echo "Device */dev/ttyUSB4* is a file - not a device type. Need to delete it"
rm -f /dev/ttyUSB4
fi
if [ -f /dev/ttyUSB5 ]; then
logger -t DeviceLinks "Device */dev/ttyUSB5* is a file - not a device type. Need to delete it"
echo "Device */dev/ttyUSB5* is a file - not a device type. Need to delete it"
rm -f /dev/ttyUSB5
fi
if [ -f /dev/ttyUSB6 ]; then
logger -t DeviceLinks "Device */dev/ttyUSB6* is a file - not a device type. Need to delete it"
echo "Device */dev/ttyUSB6* is a file - not a device type. Need to delete it"
rm -f /dev/ttyUSB5
fi
}
|
|
Sat May 19, 2018 00:49
|
camro: finally, i figured out, that the real problem is, that the "CMGR" do not read the message from storage ..
that means, if the message is very short, then it works.
BUT if the message are longer (concatenated messages) => AT+CMGR always failing ... strange ....
#######
after a break, i checked if the SIM is broken and tried it on a tablet ... and all hanging 20 messages were arrarived and loaded by the tablet to messanger ...
hmm, so, SIM card is OK ...
##
mem_check_method ...
i checked all combinations ...
finally, only 0,1,2 were working ...(if the right device will be used, what i will explain below)
so, I'm using the "2" for huawei me909
###
then i set my focus on parameter howto read from device ....
played around with speed .. and going to 9600 ... but also makes not a real difference ...
####
DEVICE => ??
normally from system (lede project / wrt - linux 3.14)
the udev is creating the modem device links to:
/dev/ttyUSB0 , /dev/ttyUSB1, /dev/ttyUSB2, /dev/ttyUSB3
using /dev/ttyUSB0 for 3g/4g conenction.
as i have sometimes the problem, that the device will be reloaded by the kernel and the udev is then making:
/dev/ttyUSB0 , /dev/ttyUSB1, / dev/ttyUSB3, /dev/ttyUSB4
it is hard to handle that by smstools3 as i need to use the "/dev/ttyUSB2" (/dev/ttyUSB3 can't read long messages, too)
so, i thought i can make simple "ln -s ...." with a if/else script and using the symlink to 2nd highest number
somewhere i read about that i should use the highest number .... but as my tests have shown, on /dev/ttyUSB3 i can not read long messages (concatenated msg's)
####
conclusion: i use:
check_memory_method = 2
device = /dev/modem_sms (which is a symlink to /dev/ttyUSB2)
i have no clue why the /dev/ttyUSB3 is not reading if a message is longer, but that is the case after playing several hours around with it.
maybe that helps also others which are having problems.
thx, this topic can be closed i guess.
cu Erwin
|
|
Fri May 18, 2018 07:43
|
camro: hmm, seems to be not that easy ... i need to test more in detail to see why i get always an alarm handler :(
in he doc of huawei 909 i see:
Issue 02 (2013-12-06)
HUAWEI Proprietary and Confidential
Copyright © HUAWEI Technologies Co., Ltd.
118
7.4 AT+CMGL–List Messages
7.4.1 Command Syntax
AT+CMGL[=<stat>]
Possible Response(s)
If in PDU mode and the command is executed successfully:
[<CR><LF>+CMGL:
<index>,<stat>,[<reserved>],<length><CR><LF><pdu>[<CR><LF>+CMG
L:
<index>,<stat>,[<reserved>],<length><CR><LF><pdu>[...]]<CR><LF>]<
CR><LF>OK<CR><LF>
In case of an MS-related error:
<CR><LF>+CMS ERROR: <err><CR><LF>
AT+CMGL=?
Possible Response(s)
<CR><LF>+CMGL: (list of supported
<stat>s)<CR><LF><CR><LF>OK<CR><LF>
7.4.2 Interface Description
The set command returns messages with status value <stat> from message storage
<mem1> to the TE. If the status of the message is "received unread", status in the
storage changes to "received read" after the set command is executed successfully.
When <stat> is not specified, the set command is equivalent to the command
AT+CMGL=0.
The test command returns a list of supported <stat> values.
7.4.3 Parameter Description
<stat>: message status.
0 Received unread messages (default value)
1 Received read messages
2 Stored unsent messages
3 Stored sent messages
4 All messages
<index>: an integer type value that indicates the storage location of the message.
<reserved>: reserved.
HUAWEI ME909u-521 LTE LGA Module
AT Command Interface Specification SMS Service Interface (WCDMA)
Issue 02 (2013-12-06)
HUAWEI Proprietary and Confidential
Copyright © HUAWEI Technologies Co., Ltd.
119
<length>: an integer type value that indicates the number of bytes of TPDU data.
<pdu>: protocol data unit in the following format.
[<SCA>]
<sc_len> <type_addr> <numbers> TPDU
For the definitions of <SCA>, <sc_len>, <type_addr>, <number> in the previous
table, see section 7.3 AT+CMGS–Send Short Message.
For the TPDU format of messages to be sent, see section 7.3 AT+CMGS–Send Short
Message. The TPDU format for received messages is described in the following table.
1 Oct 2
Oct–12
Oct
1 Oct 1 Oct 7 Oct 1 Oct
TP-MTI MMS 0 0 SRI UDHI RP OA PID DCS SCTS UDL UD
Bit0 Bit1 Bit2 Bit3 Bit4 Bit5 Bit6 Bit7
<MTI>: see the definition in section 7.3 AT+CMGS–Send Short Message.
<MMS>: indicates whether there are still other messages to be sent.
0 No
1 Yes
<SRI>: indicates whether the short message entity (SME) has requested a status
report.
0 No
1 Yes
<UDHI>: see the definition in section 7.3 AT+CMGS–Send Short Message.
<RP>: see the definition in section 7.3 AT+CMGS–Send Short Message.
<OA>: originating address. Its definition is the same as <sca>. There are a total of
2–12 octets. Therefore, the longest address in the <oa> field contains 20 digits.
<PID>: protocol identifier. See the definition in section 7.3 AT+CMGS–Send Short
Message.
<DCS>: use data coding scheme. See the definition in section 7.3 AT+CMGS–Send
Short Message.
<SCTS>: time stamp of the SMSC, consisting of year, month, date, hour, minute,
second and time difference. Time difference is the difference between the local time
and the Greenwich standard time.
HUAWEI ME909u-521 LTE LGA Module
AT Command Interface Specification SMS Service Interface (WCDMA)
Issue 02 (2013-12-06)
HUAWEI Proprietary and Confidential
Copyright © HUAWEI Technologies Co., Ltd.
120
<UDL>: user data length. See the definition in section 7.3 AT+CMGS–Send Short
Message.
<UD>: user data whose length is determined by <UDL>.
|
|
Fri May 18, 2018 07:34
|
camro: hmm, only to be sure:
with check = 31
i got on new SMS:
2018-05-18 09:27:42,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-18 09:27:42,7, GSM: <- OK
2018-05-18 09:27:42,6, GSM: Checking if Modem is registered to the network
2018-05-18 09:27:42,7, GSM: -> AT+CREG?
2018-05-18 09:27:43,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-18 09:27:43,7, GSM: <- +CREG: 2,1,"FFFE","117806",7 OK
2018-05-18 09:27:43,6, GSM: Modem is registered to the network
2018-05-18 09:27:43,6, GSM: Selecting PDU mode
2018-05-18 09:27:43,7, GSM: -> AT+CMGF=0
2018-05-18 09:27:43,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-18 09:27:43,7, GSM: <- OK
2018-05-18 09:27:43,6, GSM: Checking memory size
2018-05-18 09:27:43,7, GSM: -> AT+CMGL=0
2018-05-18 09:27:43,7, GSM: Command is sent, waiting for the answer. (60)
2018-05-18 09:27:43,7, GSM: <- +CMGL: 0,0,,64
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx11111111111111111444444444444......
OK
2018-05-18 09:27:43,3, GSM: CMGL handling error: message 0, Invalid message number
2018-05-18 09:27:43,7, GSM: Running alarmhandler: /etc/smsd_alarmhandler.sh ALARM 2018-05-18 09:27:43 3 GSM "CMGL handling error: message 0, Invalid message number"
it seems to be, that it works better with: 3
modem: HUAWEI ME909u-521 LTE LGA Module (in router: ZBT WG-3526)
my smsd.conf now:
loglevel = 7
logfile = /var/log/smsd.log
delaytime = 30
devices = GSM
incoming = /tmp/sms/incoming
outgoing = /tmp/sms/outgoing
checked = /tmp/sms/checked
failed = /tmp/sms/failed
sent = /tmp/sms/sent
incoming_utf8 = yes
receive_before_send = no
autosplit = 3
store_received_pdu = 3
decode_unicode_text = yes
errorsleeptime = 5
eventhandler = /etc/smsd_eventhandler.sh
alarmhandler = /etc/smsd_alarmhandler.sh
## modem settings ######################################################
[GSM]
loglevel = 8
loglevel_lac_ci = 8
logfile = /var/log/smsd_GSM.log
report_device_details = yes
incoming = yes
rtscts = yes
decode_unicode_text = yes
cs_convert = yes
ussd_convert = 2
send_delay = 10
read_timeout = 5
decode_unicode_text = yes
device = /dev/modem_sms
baudrate = 115200
init = ATE0
keep_open = yes
device_open_errorsleeptime = 6
status_signal_quality = no
signal_quality_ber_ignore = yes
memory_start = 0
check_memory_method = 3
cmgl_value = 0
|
|
Fri May 18, 2018 07:15
|
camro: Mama mia ...admin should be renamed to "amazing keke" !!!!
I made so many tests with different mem check options, but i have overseen that cmgl needs to be set.. As you mentioned, i had to use cmgl 0 :)
Now, i tested with new settings as recommended from you, and now:
Corrupted 2 (hanging) sms where deleted and new sms are working.
On the restart, it purged/deleted the blocked sms and everything in.log looks perfect .
Thx a lot !!!!!
|
|
Wed May 16, 2018 08:15
|
camro: FYI ...
after deleting manually ... then started smstools again .. and all is working fine ...and send new message
OK
2018-05-16 10:09:00,5, GSM: Modem handler 0 has started. PID: 30435.
2018-05-16 10:09:00,5, GSM: Using check_memory_method 1: CPMS is used.
2018-05-16 10:09:00,6, GSM: Checking device for incoming SMS
2018-05-16 10:09:00,6, GSM: Checking if modem is ready
2018-05-16 10:09:00,7, GSM: -> AT
2018-05-16 10:09:00,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:00,7, GSM: <- AT OK
2018-05-16 10:09:00,6, GSM: Pre-initializing modem
2018-05-16 10:09:00,7, GSM: -> ATE0
2018-05-16 10:09:00,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-16 10:09:00,7, GSM: <- ATE0 OK
2018-05-16 10:09:00,7, GSM: -> AT+CMEE=1;+CREG=2
2018-05-16 10:09:00,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-16 10:09:00,7, GSM: <- OK
2018-05-16 10:09:00,6, GSM: Checking if modem needs PIN
2018-05-16 10:09:01,7, GSM: -> AT+CPIN?
2018-05-16 10:09:01,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-16 10:09:01,7, GSM: <- +CPIN: READY OK
2018-05-16 10:09:01,6, GSM: Initializing modem
2018-05-16 10:09:01,7, GSM: -> ATE0
2018-05-16 10:09:01,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-16 10:09:01,7, GSM: <- OK
2018-05-16 10:09:01,6, GSM: Checking if Modem is registered to the network
2018-05-16 10:09:01,7, GSM: -> AT+CREG?
2018-05-16 10:09:01,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-16 10:09:01,7, GSM: <- +CREG: 2,1,"FFFE","117806",7 OK
2018-05-16 10:09:01,6, GSM: Modem is registered to the network
2018-05-16 10:09:01,8, GSM: Location area code: FFFE, Cell ID: 7806
2018-05-16 10:09:01,7, GSM: -> AT+CSQ
2018-05-16 10:09:01,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-16 10:09:01,7, GSM: <- +CSQ: 22,99 OK
2018-05-16 10:09:01,8, GSM: Signal Strength Indicator: (22,99) -69 dBm (Excellent)
2018-05-16 10:09:01,6, GSM: Selecting PDU mode
2018-05-16 10:09:02,7, GSM: -> AT+CMGF=0
2018-05-16 10:09:02,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:02,7, GSM: <- OK
2018-05-16 10:09:02,7, GSM: -> AT+CGSN
2018-05-16 10:09:02,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:02,7, GSM: <- xxxxxxxxxxxxxx OK
2018-05-16 10:09:02,5, GSM: IMEI: xxxxxxxxxxxxxx
2018-05-16 10:09:02,7, GSM: -> AT+CIMI
2018-05-16 10:09:02,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:02,7, GSM: <- yyyyyyyyyyyyyy OK
2018-05-16 10:09:02,5, GSM: IMSI: yyyyyyyyyyyyyy
2018-05-16 10:09:02,6, GSM: Checking if reading of messages is supported
2018-05-16 10:09:02,7, GSM: -> AT+CPMS?
2018-05-16 10:09:03,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:03,7, GSM: <- +CPMS: "SM",1,20,"SM",1,20,"SM",1,20 OK
2018-05-16 10:09:03,7, GSM: ## Start of device details
2018-05-16 10:09:03,7, GSM: # Manufacturer identification:
2018-05-16 10:09:03,7, GSM: -> AT+CGMI
2018-05-16 10:09:03,7, GSM: <- Huawei Technologies Co., Ltd.
OK
2018-05-16 10:09:03,7, GSM: # Model identification:
2018-05-16 10:09:03,7, GSM: -> AT+CGMM
2018-05-16 10:09:03,7, GSM: <- ME909u-521
OK
2018-05-16 10:09:03,7, GSM: # Revision identification:
2018-05-16 10:09:03,7, GSM: -> AT+CGMR
2018-05-16 10:09:03,7, GSM: <- 12.636.11.01.00
OK
2018-05-16 10:09:03,7, GSM: # New message indications, list of supported modes:
2018-05-16 10:09:04,7, GSM: -> AT+CNMI=?
2018-05-16 10:09:04,7, GSM: <- +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1)
OK
2018-05-16 10:09:04,7, GSM: # New message indications, current settings:
2018-05-16 10:09:04,7, GSM: -> AT+CNMI?
2018-05-16 10:09:04,7, GSM: <- +CNMI: 0,0,0,0,0
OK
2018-05-16 10:09:04,7, GSM: # Preferred message storage, list of supported mem's:
2018-05-16 10:09:04,7, GSM: -> AT+CPMS=?
2018-05-16 10:09:04,7, GSM: <- +CPMS: ("SM"),("SM"),("SM")
OK
2018-05-16 10:09:04,7, GSM: # Phonebook storage, available mem's:
2018-05-16 10:09:04,7, GSM: -> AT+CPBS=?
2018-05-16 10:09:05,7, GSM: <- +CPBS: ("SM","EN","ON")
OK
2018-05-16 10:09:05,7, GSM: # List messages, list of supported stat's:
2018-05-16 10:09:05,7, GSM: -> AT+CMGL=?
2018-05-16 10:09:05,7, GSM: <- +CMGL: (0-4)
OK
2018-05-16 10:09:05,7, GSM: # Delete message, list of supported values:
2018-05-16 10:09:05,7, GSM: -> AT+CMGD=?
2018-05-16 10:09:05,7, GSM: <- +CMGD: (0),(0-4)
OK
2018-05-16 10:09:05,7, GSM: # Phone activity status, list of supported stat's:
2018-05-16 10:09:05,7, GSM: -> AT+CPAS=?
2018-05-16 10:09:06,7, GSM: <- +CPAS: (0,3,4)
OK
2018-05-16 10:09:06,7, GSM: # TE character set, list of supported charset's:
2018-05-16 10:09:06,7, GSM: -> AT+CSCS=?
2018-05-16 10:09:06,7, GSM: <- +CSCS: ("IRA","GSM","UCS2")
OK
2018-05-16 10:09:06,7, GSM: # TE character set, current setting:
2018-05-16 10:09:06,7, GSM: -> AT+CSCS?
2018-05-16 10:09:06,7, GSM: <- +CSCS: "IRA"
OK
2018-05-16 10:09:06,7, GSM: ## End of device details
2018-05-16 10:09:06,6, GSM: Checking memory size
2018-05-16 10:09:06,7, GSM: -> AT+CPMS?
2018-05-16 10:09:06,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:06,7, GSM: <- +CPMS: "SM",1,20,"SM",1,20,"SM",1,20 OK
2018-05-16 10:09:06,6, GSM: Used memory is 1 of 20
2018-05-16 10:09:06,6, GSM: Trying to get stored message 0
2018-05-16 10:09:07,7, GSM: -> AT+CMGR=0
2018-05-16 10:09:07,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:07,7, GSM: <- +CMGR: 1,,21 0691zzzzzzzzzzzzzzzzzzzzzzzz24119 OK
2018-05-16 10:09:07,5, GSM: SMS received, From: zzzzzzzzzz
2018-05-16 10:09:07,6, GSM: Wrote an incoming message file: /tmp/sms/incoming/GSM.NhFDMm
2018-05-16 10:09:07,7, GSM: Running eventhandler: /etc/smsd_eventhandler.sh RECEIVED /tmp/sms/incoming/GSM.NhFDMm
2018-05-16 10:09:09,7, GSM: Done: eventhandler, execution time 2 sec., status: 0 (0)
2018-05-16 10:09:09,6, GSM: Deleting message 0
2018-05-16 10:09:09,7, GSM: -> AT+CMGD=0
2018-05-16 10:09:09,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:10,7, GSM: <- OK
2018-05-16 10:09:10,6, GSM: Checking device for incoming SMS
2018-05-16 10:09:10,6, GSM: Checking memory size
2018-05-16 10:09:10,7, GSM: -> AT+CPMS?
2018-05-16 10:09:10,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:10,7, GSM: <- +CPMS: "SM",0,20,"SM",0,20,"SM",0,20 OK
2018-05-16 10:09:10,6, GSM: Used memory is 0 of 20
2018-05-16 10:09:10,6, GSM: No SMS received
2018-05-16 10:09:40,6, GSM: Checking device for incoming SMS
2018-05-16 10:09:40,6, GSM: Checking if modem is ready
2018-05-16 10:09:40,7, GSM: -> AT
2018-05-16 10:09:40,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:40,7, GSM: <- AT OK
2018-05-16 10:09:40,6, GSM: Pre-initializing modem
2018-05-16 10:09:40,7, GSM: -> ATE0
2018-05-16 10:09:40,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-16 10:09:40,7, GSM: <- ATE0 OK
2018-05-16 10:09:40,7, GSM: -> AT+CMEE=1;+CREG=2
2018-05-16 10:09:41,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-16 10:09:41,7, GSM: <- OK
2018-05-16 10:09:41,6, GSM: Initializing modem
2018-05-16 10:09:41,7, GSM: -> ATE0
2018-05-16 10:09:41,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-16 10:09:41,7, GSM: <- OK
2018-05-16 10:09:41,6, GSM: Checking if Modem is registered to the network
2018-05-16 10:09:41,7, GSM: -> AT+CREG?
2018-05-16 10:09:41,7, GSM: Command is sent, waiting for the answer. (10)
2018-05-16 10:09:41,7, GSM: <- +CREG: 2,1,"FFFE","117806",7 OK
2018-05-16 10:09:41,6, GSM: Modem is registered to the network
2018-05-16 10:09:41,6, GSM: Selecting PDU mode
2018-05-16 10:09:41,7, GSM: -> AT+CMGF=0
2018-05-16 10:09:41,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:41,7, GSM: <- OK
2018-05-16 10:09:41,6, GSM: Checking memory size
2018-05-16 10:09:42,7, GSM: -> AT+CPMS?
2018-05-16 10:09:42,7, GSM: Command is sent, waiting for the answer. (5)
2018-05-16 10:09:42,7, GSM: <- +CPMS: "SM",0,20,"SM",0,20,"SM",0,20 OK
2018-05-16 10:09:42,6, GSM: Used memory is 0 of 20
2018-05-16 10:09:42,6, GSM: No SMS received
so, i have to think about to check anyhow if there are messages hanging which can't be read to try deleting them ..
any idea howto automatically handled by SMSTOOLS3 ?
cu Erwin
|
|
Wed May 16, 2018 07:59
|
camro: Operating system name and version:
Model ZBT-WG3526 (16M)
Firmware Version OpenWrt SNAPSHOT r6880-aadca03 / LuCI Master (git-18.133.37847-2f0f456)
Kernel Version 4.14.37
Version of smsd: Version 3.1.21
Smsd installed from: repo of openwrt (trunk) => opkg install smstools3
Name and model of a modem / phone: HUAWEI ME909u-521 LTE LGA Module
Interface: /dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2, /dev/ttyUSB3
=> highest id used for smstools
hello,
as the topic was closed ... see: http://smstools3.kekekasvi.com/topic.php?id=432
i have same problem, that sometimes i get a corrupted message (as I'm also testing to receive binary SMS, which are splitted into multiple parts .. or for whatever reason .. :(
anyhow ...
sometimes it happens that a message on the sim can't be read ...
then it only hangs in logs .. and getting time out .. eg:
2018-05-16 02:51:22,7, GSM: <- AT OK
2018-05-16 02:51:22,6, GSM: Pre-initializing modem
2018-05-16 02:51:22,7, GSM: -> ATE0
2018-05-16 02:51:22,7, GSM: Command is sent, waiting for the answer. (30)
2018-05-16 02:51:22,7, GSM: <- ATE0 OK
2018-05-16 02:51:22,7, GSM: -> AT+CMEE=1
2018-05-16 02:51:22,7, GSM: Command is sent, waiting for the answer. (30)
2018-05-16 02:51:22,7, GSM: <- OK
2018-05-16 02:51:22,6, GSM: Initializing modem
2018-05-16 02:51:22,7, GSM: -> 'AT+CPMS="SM","SM","SM"'
2018-05-16 02:51:23,7, GSM: Command is sent, waiting for the answer. (30)
2018-05-16 02:51:23,7, GSM: <- +CPMS: 4,20,4,20,4,20 OK
2018-05-16 02:51:23,7, GSM: -> ATE0
2018-05-16 02:51:23,7, GSM: Command is sent, waiting for the answer. (30)
2018-05-16 02:51:23,7, GSM: <- OK
2018-05-16 02:51:23,6, GSM: Checking if Modem is registered to the network
2018-05-16 02:51:23,7, GSM: -> AT+CREG?
2018-05-16 02:51:23,7, GSM: Command is sent, waiting for the answer. (30)
2018-05-16 02:51:23,7, GSM: <- +CREG: 0,1 OK
2018-05-16 02:51:23,6, GSM: Modem is registered to the network
2018-05-16 02:51:23,6, GSM: Selecting PDU mode
2018-05-16 02:51:23,7, GSM: -> AT+CMGF=0
2018-05-16 02:51:23,7, GSM: Command is sent, waiting for the answer. (15)
2018-05-16 02:51:23,7, GSM: <- OK
2018-05-16 02:51:23,6, GSM: Checking memory size
2018-05-16 02:51:23,7, GSM: -> AT+CPMS?
2018-05-16 02:51:23,7, GSM: Command is sent, waiting for the answer. (15)
2018-05-16 02:51:23,7, GSM: <- +CPMS: "SM",1,20,"SM",1,20,"SM",1,20 OK
2018-05-16 02:51:23,6, GSM: Used memory is 1 of 20
2018-05-16 02:51:23,6, GSM: Trying to get stored message 0
2018-05-16 02:51:23,7, GSM: -> AT+CMGR=0
2018-05-16 02:51:23,7, GSM: Command is sent, waiting for the answer. (15)
2018-05-16 02:51:38,7, GSM: No answer, put_command expected (\+CMGR:.*OK)|(ERROR)|(OK), timeout occurred. 1.
2018-05-16 02:51:38,7, GSM: <-
2018-05-16 02:51:38,6, GSM: No SMS received (reading interrupted)
as you can see there is a 1 message in storage, but it can't read .. tried also to change timeout for read .. was also not working ....
the only chance what i had was to delete this corrupted MSG manually via "smsd -C GSM"
then tried also to read again manually ....
AT+CMGR=0
no answer .....
then i tried to delete the message,
via:
AT+CMGD=0
and got <= OK
so far, everything fine ....
but ... as this 1 message is blocking all other new incomming message :(
that means the messages are arraiving to the storage, but as the first message (id1=#0) can't be read, it will never go to next message #1, so i miss all messages, finally the 20 storage id's willb e filled up, and then fully can'T get messages to storage, too :(
is it anyhow possible to handle such kind of problem ?
eg: if a message can't be read, then try to delete it via smstools.. or try to read next message ?
or to ignore if a message can'T be read and try to read next message .. something like that ...
is there such kind of options on smstools config settings ?
cu Erwin
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
