|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Fri Mar 14, 2025 10:58 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Thu Jun 22, 2017 13:56
|
fredclement91: Ok, let me do that this evening, I will tell you tomorrow what happens.
|
|
Thu Jun 22, 2017 13:47
|
fredclement91: I have no more than that :
2017-06-22 15:46:08.910,2, smsd: Smsd v3.1.19 started.
2017-06-22 15:46:08.912,2, smsd: Running as root:root (0:0).
2017-06-22 15:46:08.914,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.yzh1Sk /tmp/smsd_data.OwFKNi
2017-06-22 15:46:08.924,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2017-06-22 15:46:08.924,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2017-06-22 15:46:08.924,6, smsd: Using logtime format "%Y-%m-%d %H:%M:%S.timems". It produces "2017-06-22 15:46:08.924".
2017-06-22 15:46:08.927,5, smsd: Outgoing file checker has started. PID: 28981.
2017-06-22 15:46:08.928,7, smsd: All PID's: 28981,28982
2017-06-22 15:46:08.928,5, GSM1: Modem handler 0 has started. PID: 28982.
2017-06-22 15:46:08.928,5, GSM1: Using check_memory_method 1: CPMS is used.
2017-06-22 15:46:08.940,6, GSM1: I have to send 1 short message for /var/spool/sms/checked/test
2017-06-22 15:46:08.940,6, GSM1: Sending SMS from to 33661032721
2017-06-22 15:46:08.940,6, GSM1: Checking if modem is ready
2017-06-22 15:46:09.040,7, GSM1: -> AT
2017-06-22 15:46:09.051,7, GSM1: Command is sent, waiting for the answer. (5)
2017-06-22 15:46:09.051,7, GSM1: <- AT OK
2017-06-22 15:46:09.051,6, GSM1: Pre-initializing modem
2017-06-22 15:46:09.151,7, GSM1: -> ATE0;+CMEE=1;+CREG=2
2017-06-22 15:46:09.171,7, GSM1: Command is sent, waiting for the answer. (10)
2017-06-22 15:46:09.171,7, GSM1: <- ATE0;+CMEE=1;+CREG=2 OK
2017-06-22 15:46:09.171,6, GSM1: Checking if modem needs PIN
2017-06-22 15:46:09.271,7, GSM1: -> AT+CPIN?
2017-06-22 15:46:09.291,7, GSM1: Command is sent, waiting for the answer. (10)
2017-06-22 15:46:09.291,7, GSM1: <- +CPIN: SIM PIN OK
2017-06-22 15:46:09.291,5, GSM1: Modem needs PIN, entering PIN...
2017-06-22 15:46:09.391,7, GSM1: -> AT+CPIN="1234"
2017-06-22 15:46:09.411,7, GSM1: Command is sent, waiting for the answer. (30)
2017-06-22 15:46:09.491,7, GSM1: <- OK
2017-06-22 15:46:09.491,6, GSM1: Spending sleep time after PIN entering (2 sec)
2017-06-22 15:46:11.692,7, GSM1: -> AT+CPIN?
2017-06-22 15:46:11.711,7, GSM1: Command is sent, waiting for the answer. (10)
2017-06-22 15:46:21.108,7, GSM1: No answer, put_command expected (READY)|( PIN)|( PUK)|(ERROR), timeout occurred. 1.
2017-06-22 15:46:21.108,7, GSM1: <-
2017-06-22 15:46:21.108,2, GSM1: PIN handling: expected READY, modem answered
2017-06-22 15:46:21.108,2, GSM1: Modem handler 0 terminated abnormally. PID: 28982, was started 17-06-22 15:46:08, up 0 min.
2017-06-22 15:46:21.110,2, smsd: Modem handler 0 (GSM1) terminated while mainprocess is still running. Exited, status 1.
|
|
Thu Jun 22, 2017 13:44
|
fredclement91: What details do you want me to show ? the complete log file ?
|
|
Thu Jun 22, 2017 13:34
|
fredclement91: I already have it enabled, my complete config file is :
devices = GSM1
logfile = /var/log/smsd.log
loglevel = 7
logtime_ms = yes
[GSM1]
init = ATZ
init2 = ATE0
device = /dev/ttyAMA0
incoming = yes
pin = 1234
report_device_details = yes
#memory_start = 0
mode = new
report = no
pinsleeptime = 2
|
|
Thu Jun 22, 2017 13:27
|
fredclement91: I don't really remember the model (I am not on site). It's a chinese SIM adapter.
The strange thing is that it has been working for months.
But you are surely right, I have to test without a pin.
I will give you a reply ASAP.
Thanks.
|
|
Thu Jun 22, 2017 13:00
|
fredclement91: Thanks for your suggestion, but it still doesn't work (but apparently for a different reason)
Strange, no ?
2017-06-22 14:59:05.761,7, GSM1: <- AT+CPIN? +CPIN: SIM PIN OK
2017-06-22 14:59:05.761,3, GSM1: Modem did not accept this PIN
root@raspberrypi:/usr/src/smstools3# /etc/init.d/sms3 restart
2017-06-22 14:58:53.845,2, smsd: Smsd mainprocess terminated. PID: 27980, was started 17-06-22 14:58:30, up 0 min.
Starting SMS Daemon: 2017-06-22 14:58:54.962,2, smsd: Smsd v3.1.19 started.
2017-06-22 14:58:54.965,2, smsd: Running as root:root (0:0).
2017-06-22 14:58:54.967,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.eIVOPH /tmp/smsd_data.AV56mB
2017-06-22 14:58:54.977,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2017-06-22 14:58:54.978,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2017-06-22 14:58:54.979,6, smsd: Using logtime format "%Y-%m-%d %H:%M:%S.timems". It produces "2017-06-22 14:58:54.979".
2017-06-22 14:58:54.982,5, smsd: Outgoing file checker has started. PID: 28021.
2017-06-22 14:58:54.982,7, smsd: All PID's: 28021,28022
2017-06-22 14:58:54.982,5, GSM1: Modem handler 0 has started. PID: 28022.
2017-06-22 14:58:54.982,5, GSM1: Using check_memory_method 1: CPMS is used.
2017-06-22 14:58:54.983,6, GSM1: Checking device for incoming SMS
2017-06-22 14:58:54.983,6, GSM1: Checking if modem is ready
2017-06-22 14:58:55.084,7, GSM1: -> AT
2017-06-22 14:58:55.101,7, GSM1: Command is sent, waiting for the answer. (5)
2017-06-22 14:58:55.101,7, GSM1: <- AT OK
2017-06-22 14:58:55.101,6, GSM1: Pre-initializing modem
2017-06-22 14:58:55.201,7, GSM1: -> ATE0;+CMEE=1;+CREG=2
2017-06-22 14:58:55.221,7, GSM1: Command is sent, waiting for the answer. (10)
2017-06-22 14:58:55.221,7, GSM1: <- ATE0;+CMEE=1;+CREG=2 OK
2017-06-22 14:58:55.221,6, GSM1: Checking if modem needs PIN
2017-06-22 14:58:55.321,7, GSM1: -> AT+CPIN?
2017-06-22 14:58:55.341,7, GSM1: Command is sent, waiting for the answer. (10)
2017-06-22 14:58:55.341,7, GSM1: <- +CPIN: SIM PIN OK
2017-06-22 14:58:55.341,5, GSM1: Modem needs PIN, entering PIN...
2017-06-22 14:58:55.441,7, GSM1: -> AT+CPIN="1234"
2017-06-22 14:58:55.461,7, GSM1: Command is sent, waiting for the answer. (30)
2017-06-22 14:58:55.541,7, GSM1: <- OK
2017-06-22 14:58:55.541,6, GSM1: Spending sleep time after PIN entering (10 sec)
smsd.
root@raspberrypi:/usr/src/smstools3# 2017-06-22 14:59:05.743,7, GSM1: -> AT+CPIN?
2017-06-22 14:59:05.761,7, GSM1: Command is sent, waiting for the answer. (10)
2017-06-22 14:59:05.761,7, GSM1: <- AT+CPIN? +CPIN: SIM PIN OK
2017-06-22 14:59:05.761,3, GSM1: Modem did not accept this PIN
2017-06-22 14:59:05.761,2, GSM1: Modem handler 0 terminated abnormally. PID: 28022, was started 17-06-22 14:58:54, up 0 min.
2017-06-22 14:59:05.763,2, smsd: Modem handler 0 (GSM1) terminated while mainprocess is still running. Exited, status 1.
|
|
Thu Jun 22, 2017 12:24
|
fredclement91: Operating system name and version: Raspberry with SMS Serial adapter
Version of smsd: 2
Smsd installed from: sources / package repository / from elsewhere...
Name and model of a modem / phone:
Interface: serial / USB / some adapter... /dev/ttyAMA0
Hi,
My system has been working for a long time, but now I have a new message, juste after entering the pin (see above:
When I enter the commands manually using minicom, it works correctly. My feeling is that to AT+CPIN? is arriving too quickly.
2017-06-22 14:12:42,6, GSM1: Checking if modem is ready
2017-06-22 14:12:42,7, GSM1: -> AT
2017-06-22 14:12:42,7, GSM1: Command is sent, waiting for the answer. (5)
2017-06-22 14:12:42,7, GSM1: <- AT OK
2017-06-22 14:12:42,6, GSM1: Pre-initializing modem
2017-06-22 14:12:42,7, GSM1: -> ATE0;+CMEE=1;+CREG=2
2017-06-22 14:12:42,7, GSM1: Command is sent, waiting for the answer. (10)
2017-06-22 14:12:43,7, GSM1: <- ATE0;+CMEE=1;+CREG=2 +CPIN: SIM PIN OK
2017-06-22 14:12:43,6, GSM1: Checking if modem needs PIN
2017-06-22 14:12:43,7, GSM1: -> AT+CPIN?
2017-06-22 14:12:43,7, GSM1: Command is sent, waiting for the answer. (10)
2017-06-22 14:12:43,7, GSM1: <- +CPIN: SIM PIN OK
2017-06-22 14:12:43,5, GSM1: Modem needs PIN, entering PIN...
2017-06-22 14:12:43,7, GSM1: -> AT+CPIN="1234"
2017-06-22 14:12:43,7, GSM1: Command is sent, waiting for the answer. (30)
2017-06-22 14:12:43,7, GSM1: <- OK
2017-06-22 14:12:43,7, GSM1: -> AT+CPIN?
2017-06-22 14:12:43,7, GSM1: Command is sent, waiting for the answer. (10)
2017-06-22 14:12:43,7, GSM1: <- +CME ERROR: 14 (SIM busy)
2017-06-22 14:12:43,2, GSM1: PIN handling: expected READY, modem answered +CME ERROR: 14 (SIM busy), SIM busy
2017-06-22 14:12:43,2, GSM1: Modem handler 0 terminated abnormally. PID: 26610, was started 17-06-22 14:12:42, up 0 min.
|
|
Wed Apr 05, 2017 10:15
|
fredclement91: You are absolutely right, it works with international format.
Thanks !
|
|
Wed Apr 05, 2017 08:02
|
fredclement91: Operating system name and version:
Version of smsd:
Smsd installed from: sources / package repository / from elsewhere...
Name and model of a modem / phone:
Interface: serial / USB / some adapter...
Hi,
I am using a small modem connected on a raspberry pi to send SMS messages. It was working like a charm for months, but suddenly, I get an new error message :
2017-04-05 09:59:52,7, GSM1: Command is sent, waiting for the answer. (10)
2017-04-05 09:59:52,7, GSM1: <- +CREG: 2,5,"2201","54E6" OK
2017-04-05 09:59:52,6, GSM1: Modem is registered to a roaming partner network
2017-04-05 09:59:52,6, GSM1: Selecting PDU mode
2017-04-05 09:59:52,7, GSM1: -> AT+CMGF=0
2017-04-05 09:59:52,7, GSM1: Command is sent, waiting for the answer. (5)
2017-04-05 09:59:52,7, GSM1: <- OK
2017-04-05 09:59:52,7, GSM1: -> AT+CMGS=14
2017-04-05 09:59:52,7, GSM1: Command is sent, waiting for the answer. (10)
2017-04-05 09:59:52,7, GSM1: <- >
2017-04-05 09:59:52,7, GSM1: -> 0011000A91601630x2xx0000FF010A
2017-04-05 09:59:52,7, GSM1: Command is sent, waiting for the answer. (60)
2017-04-05 10:00:07,7, GSM1: <- +CMS ERROR: 97 (Message type non-existent or not implemented)
2017-04-05 10:00:07,3, GSM1: The modem answer was not OK: +CMS ERROR: 97 (Message type non-existent or not implemented)
2017-04-05 10:00:07,5, GSM1: Waiting 10 sec. before retrying
2017-04-05 10:00:17,6, GSM1: Checking if modem is ready
2017-04-05 10:00:17,7, GSM1: -> AT
2017-04-05 10:00:17,7, GSM1: Command is sent, waiting for the answer. (5)
2017-04-05 10:00:17,7, GSM1: <- OK
2017-04-05 10:00:17,6, GSM1: Pre-initializing modem
Do you think that the carrier (Free Mobile) has changed something on his side ?
I would be very happy if you had ideas about that !.
Fred
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
