|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Thu Mar 13, 2025 05:16 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Sat Mar 30, 2024 05:04
|
25802855: However, my original question still stands. Why does some sending take 30-80 seconds, while some take 3-8 seconds, on the same network. Appreciate.
|
|
Sat Mar 30, 2024 04:43
|
25802855: After looking into modeminit.c, it is easy to understand; read_timeout_pdu (5) * read_timeout (5) = 25
|
|
Sat Mar 30, 2024 03:48
|
25802855: The
You have been very helpful. Thank you upfront. Have one more question regarding a situation that I was not able to resolve myself.
Situation 1)
Sending an SMS to client that has not updated his phone number in our database.
The status report is understandable. The important part I'm referring to is the sending time 4sec.
2024-03-30 04:31:04,5, GSM2: SMS sent, Message_id: 151, To: xxxx, sending time 4 sec.
2024-03-30 04:31:04,6, GSM2: SMS To: xxxx. Moved file /home/smsd/sms/queues/q2/20240330-04:30:56.187317291.txt to /home/smsd/sms/sent/20240330-04:30:56.187317291.txt
2024-03-30 04:31:04,7, GSM2: Running eventhandler: /home/smsd/scripts/event.sh SENT /home/smsd/sms/sent/20240330-04:30:56.187317291.txt 151
2024-03-30 04:31:04,7, GSM2: Done: eventhandler, execution time 0 sec., status: 0 (0)
2024-03-30 04:31:04,6, GSM2: Checking device for incoming SMS
...
2024-03-30 04:31:09,6, GSM2: Handling saved routed messages / status reports
2024-03-30 04:31:09,5, GSM2: SMS received (report, Message_id: 151, Status: 99,Error,service rejected), From: xxxx
2024-03-30 04:31:09,6, GSM2: Wrote an incoming message file: /home/smsd/sms/report/GSM2.NdFjdH
2024-03-30 04:31:09,7, GSM2: Running eventhandler: /home/smsd/scripts/event.sh REPORT /home/smsd/sms/report/GSM2.NdFjdH
2024-03-30 04:31:09,7, GSM2: Done: eventhandler, execution time 0 sec., status: 0 (0)
Situation 2)
Another client has an old phone number in our database, however in this case we have sending time 24 sec. There is no 99 status report like in previous situation. No status report at all.
2024-03-30 04:33:04,5, GSM2: SMS sent, Message_id: 152, To: xxxx, sending time 24 sec.
2024-03-30 04:33:04,6, GSM2: SMS To: xxxx. Moved file /home/smsd/sms/queues/q2/20240330-04:32:30.936930537.txt to /home/smsd/sms/sent/20240330-04:32:30.936930537.txt
2024-03-30 04:33:04,7, GSM2: Running eventhandler: /home/smsd/scripts/event.sh SENT /home/smsd/sms/sent/20240330-04:32:30.936930537.txt 152
2024-03-30 04:33:04,7, GSM2: Done: eventhandler, execution time 0 sec., status: 0 (0)
2024-03-30 04:33:04,6, GSM2: Checking device for incoming SMS
Phone numbers from both situations are in the same network.
$ cd sent; for file in ./*; do time=$(grep 'Sending_time' $file | awk '{print $2}'); if [ "$time" -gt 20 ]; then cat $file | grep -E 'To|Modem|Sending_time|Sent|Received'; echo; fi; done
To: +
Modem: GSM1
Sent: 24-03-29 18:46:58
Sending_time: 87
To: +
Modem: GSM1
Sent: 24-03-29 18:48:03
Sending_time: 61
Received: 24-03-29 18:51:27
To: +
Modem: GSM1
Sent: 24-03-29 18:54:27
Sending_time: 26
Why does the '24 sec' timeout happen and where is this defined, and modified if possible? I was not able to find information in smstools handbook, nor the module at commands. Is this something related to network itself?
I'd like to avoid module hanging for larger amount of seconds.
Much appreciated.
|
|
Thu Mar 14, 2024 16:20
|
25802855: Thank you! You are correct!
Switching default +CNMI=2,1,0,0,0 to +CNMI=2,1,2,1,0 works and status reports are retrieved.
I believe the important part is the <ds> value.
0 No SMS-STATUS-REPORTs are routed to the TE
1 SMS-STATUS-REPORTs are routed to the TE by using unsolicited result code:+CDS: <length><CR><LF><pdu> (PDU mode enabled) or +CDS: <fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st> (Text mode enabled)
Just for future reference for other people here is my config;
devices = GSM1, GSM2
outgoing = /home/smsd/sms/outgoing
checked = /home/smsd/sms/checked
incoming = /home/smsd/sms/incoming
failed = /home/smsd/sms/failed
sent = /home/smsd/sms/sent
phonecalls = /home/smsd/sms/calls
report = /home/smsd/sms/report
infofile = /home/smsd/smsd/smsd.info
pidfile = /home/smsd/smsd/smsd.pid
stats = /home/smsd/smsd/stats
# logging
loglevel = 7
logfile = /home/smsd/smsd/smsd.log
# privileges
user = smsd
group = dialout
umask = 077
# see exact data which is received from the modem
log_read_from_modem = yes
# timestamp and uptime are printed to the end of status file
status_include_uptime = yes
# empty the first SIM card memory before sending SM
receive_before_send = no
#blacklist = /etc/smstools/blacklist
#whitelist = /etc/smstools/whitelist
# messages using iso or gsm are stored as utf8
incoming_utf8 = yes
[queues]
MAIN = /home/smsd/sms/queues/main
GSM1 = /home/smsd/sms/queues/gsm1
GSM2 = /home/smsd/sms/queues/gsm2
[default]
init = AT+CPMS="SM","SM","SM"
#init = AT+CPMS="SM","ME","MT"
#init = AT+CPMS="ME","ME","ME"
# 0 = no | 1 = normal | 2 = high
incoming = 2
baudrate = 115200
# CMGL is used to check messages, message is deleted after it is read
check_memory_method = 3
# 1 = network registration is always checked | 2 = network registration is checked only when preparing to send messages
check_network = 1
pin = ignore
read_timeout = 10
report = yes
report_device_details = yes
send_retries = 1
decode_unicode_text = yes
# calls
phonecalls = clip
hangup_incoming_call = yes
# event
eventhandler = /home/smsd/scripts/event.sh
[GSM1]
device = /dev/ttyACM0
queues = GSM1, MAIN
[GSM2]
device = /dev/ttyACM1
queues = GSM2, MAIN
Model identification:
GSM1 <- Quectel_Ltd
Quectel_M35
Revision: MTK 0828
OK
Revision identification:
GSM1: <- Revision: M35AR01A36
|
|
Tue Mar 12, 2024 01:26
|
25802855: after many hours of debugging, i have not managed to figure out why SMS status reports are not being received.
report=yes is inside config.
decoded PDU for outgoing SMS holds TP-SRR: 20
decoded PDU for incoming SMS holds TP-SRI: 20
according to https://www.discoverytelecom.eu/upload/iblock/7c7/m35_at_command.pdf
'SMS status report is supported under text mode if <fo> is set to 49'
AT+CSMP?
+CSMP: 17,169,0,0
AT+CSMP=49,169,0,0
AT+CMGF=1
AT+CMGS="+xxxx"
however no status report is received.
one thing that might be happening is because the network gives one SMS central number, which works for sending and receiving, however a completely different SMSC is actually the official one.
thank you
|
|
Sat Mar 09, 2024 16:53
|
25802855: just to let community know. ordered quectel m35. working good. configuration below for reference. still fiddling around and improving.
devices = GSM1, GSM2
outgoing = /home/smsd/sms/outgoing
checked = /home/smsd/sms/checked
incoming = /home/smsd/sms/incoming
failed = /home/smsd/sms/failed
sent = /home/smsd/sms/sent
infofile = /home/smsd/smsd/smsd.working
pidfile = /home/smsd/smsd/smsd.pid
stats = /home/smsd/smsd/stats
# logging
loglevel = 7
logfile = /home/smsd/smsd/smsd.log
# permissions
user = smsd
group = dialout
# see exact data which is received from the modem
# log_read_from_modem = yes
# timestamp and uptime are printed to the end of status file
# status_include_uptime = yes
# empty the first SIM card memory before sending SM
receive_before_send = no
#blacklist = /etc/smstools/blacklist
#whitelist = /etc/smstools/whitelist
[default]
init = AT+CPMS="SM","SM","SM"
incoming = high
baudrate = 115200
# CMGL is used to check messages, message is deleted after it is read
check_memory_method = 3
# 1 = network registration is always checked | 2 = network registration is checked only when preparing to send messages
check_network = 1
pin = ignore
read_timeout = 10
report = yes
report_device_details = yes
[GSM1]
device = /dev/ttyACM0
[GSM2]
device = /dev/ttyACM1
|
|
Fri Feb 16, 2024 00:07
|
25802855: Operating system name and version: Linux 6.x
Version of smsd: /
Smsd installed from: /
Name and model of a modem / phone: https://www.aliexpress.com/item/4001198507801.html
Interface: USB
Hello.
I have looked into hardware compatibility page but have not found my answer, and have also searched community forums.
Will above mentioned device with sim7600e-h module work with smstools3?
Thank you
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
