|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Thu Mar 13, 2025 20:00 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Mon Aug 21, 2017 07:55
|
bor: smsd: 3.1.21
Platform: Raspian, Linux <hostname> 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
If SMS comes in, the filename in eventhandler and the folder looks like /home/sms/spool/incoming_copy/smsserver.07aBp8
The filename in /home/sms/spool/incoming/smsserver.2017-08-21.zKVjqD had a different filename with the wanted date in it; but also a different extention. The filename in the incoming_copy-folder would not "renamed" after all. No difference between "normal SMS" and "REPORTs".
Sometimes, e.g. after complete processing a M2M-task, it is neccessary to handle both incoming files, e.g. for removing or archiving. No big deal, but you have alway open both files for searching message_id and phonenumber instead handle both files by filename.
smsd.conf
outgoing = /home/sms/spool/outgoing
incoming = /home/sms/spool/incoming
incoming_copy = /home/sms/spool/incoming_copy
checked = /home/sms/spool/checked
sent = /home/sms/spool/sent
sent_copy = /home/sms/spool/sent_copy
failed = /home/sms/spool/failed
failed_copy = /home/sms/spool/failed_copy
phonecalls = /home/sms/spool/phonecalls
eventhandler_use_copy = yes
date_filename = 2
Is there something I'v done wrong?
|
|
Wed May 17, 2017 14:27
|
bor: A couple of weeks ago, I sent a Ping-SMS with Validity ~14 days to one of my numbers, remove the SIM and forgot it. Today I put the SIM into a modem and the SMSC sent me the requested feedback.
Immediately after the SMS is written to the disk, smsd dies w/o further notice. After restarting the same procedure. A "new" file is created in the incoming-folder, smsd crash.
SMS-Report:
From: nnnnnnnnnnnn
From_TOA: 91 international, ISDN/telephone
From_SMSC: yyyyyyyyyy
Sent: 17.05.2017 12:32:06
Received: 17.05.2017 15:17:30
Subject: SMSServer
Modem: SMSServer
Report: no
Alphabet: ISO
Length: 118
UDH: no
SMS STATUS REPORT
Message_id: 195
Discharge_timestamp: 17.05.2017 12:37:08
Status: 70,Error,SM validity period expired
Modem-Logfile:
...
2017-05-17 15:22:05,7, SMSServer: ## End of device details
2017-05-17 15:22:05,5, SMSServer: SMS received (report, Message_id: 195, Status: 70,Error,SM validity period expired), From: nnnnnnnnnnnn
Checking the SIM:
AT+CMGF=1
AT+CMGL="ALL"
+CMGL: 0,"REC READ",6,195,"+nnnnnnnnnnnn",145,"17/05/17,12:32:06+08","17/05/17,12:37:08+08",70
+CMGL: 1,"REC READ","+nnnnnnnnnnnn",,"17/05/17,14:44:22+08"
Some text ...
OK
AT+CMGD=0
To fix the problem I had to delete the Report-SMS in the SIM. Now smsd starts as expected w/o problems. Is this prob known?
regards, bor
|
|
Sun Apr 23, 2017 10:20
|
bor: Thank you for your fast reaction!
|
|
Wed Mar 29, 2017 23:24
|
bor: If I configure in smsd.conf
datetime_format = %d.%m.%Y %T
the format appears in reports Sent and Received section, not in Discharge_timestamp
From: nnnnnn
...
Sent: 30.03.2017 00:29:14 <-- OK
Received: 30.03.2017 00:29:43 <-- OK
...
SMS STATUS REPORT
Message_id: 151
Discharge_timestamp: 17-03-30 00:29:18 <-- not OK
Status: 0,Ok,short message received by the SME
Is this known? I have to fix this by code and need to know if this would be fixed in a next release to remove the code in my sources.
|
|
Wed Mar 29, 2017 23:02
|
bor: @keke
I have the same problem. Thank you for take care.
|
|
Wed Mar 29, 2017 13:22
|
bor: Your hint will fix the problem:
primary_memory = ME
secondary_memory = SR
So I am set. My post describes no bug.
BTW: The modem is a ZTE MF112
Since years I was waiting to find a software who handles silent SMS in this way so i can remove my own home brewed solutions. So you and all others supporting SMSServerTools had done a great job.
Thank you all
|
|
Tue Mar 28, 2017 18:19
|
bor: I tried to use the "Ping: yes" parameter. The target phone is switched "on" and work well.
To: 431234567890
Ping: yes
Test
smsd.conf:
...
memory_start = 0
init = ATE0+CPMS="ME","ME","ME"
...
The log tells, that the SMS is sent, the sent-counter increase, but ther is no answer coming back to the incoming-folder. Looking to the log w/ loglevel=8 shows, that there is an increase of the ME-counter.
2017-03-28 18:44:41,7, SMSServer: -> AT+CPMS?
2017-03-28 18:44:41,7, SMSServer: Command is sent, waiting for the answer. (5)
2017-03-28 18:44:41,7, SMSServer: <- +CPMS: "ME",0,100,"ME",0,100,"ME",0,100 OK
2017-03-28 18:44:41,6, SMSServer: Checking memory size
2017-03-28 18:44:41,7, SMSServer: -> AT+CPMS?
2017-03-28 18:44:41,7, SMSServer: Command is sent, waiting for the answer. (5)
2017-03-28 18:44:41,7, SMSServer: <- +CPMS: "ME",0,100,"ME",0,100,"ME",0,100 OK
2017-03-28 18:44:41,6, SMSServer: Used memory is 0 of 100 <-- before sending first Ping-SMS
... <-- sending first Ping-SMS; logtext supressed
2017-03-28 18:45:33,7, SMSServer: -> AT+CPMS?
2017-03-28 18:45:33,7, SMSServer: Command is sent, waiting for the answer. (5)
2017-03-28 18:45:33,7, SMSServer: <- +CPMS: "ME",1,100,"ME",1,100,"ME",1,100 OK
2017-03-28 18:45:33,6, SMSServer: Used memory is 1 of 100 <-- first increase of ME-storage
2017-03-28 18:45:33,6, SMSServer: Trying to get stored message 0
2017-03-28 18:45:33,7, SMSServer: -> AT+CMGR=0
2017-03-28 18:45:33,7, SMSServer: Command is sent, waiting for the answer. (5)
2017-03-28 18:45:33,7, SMSServer: <- OK
2017-03-28 18:45:33,6, SMSServer: Trying to get stored message 1
2017-03-28 18:45:34,7, SMSServer: -> AT+CMGR=1
... and so on
Each new Ping-SMS sent increases the ME-storage-counter, decreases the providers SMS-counter (so the SMS is recognized by the provider), but no incoming SMS with the ACK from the providers servicecenter (must be the increased ME-SMS-counter) ist extracted from the SIM and written to the incoming(_copy)-folder(s). After disconnecting the modem from USB (power off) the ME-counter starts with 0 (zero).
Anything I can do by myself?
regards, rob
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
