|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Tue Jul 01, 2025 01:34 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Tue Aug 22, 2017 18:32
|
fips: Is there already a fix for the "not enough storage space" error?
|
|
Tue Aug 22, 2017 16:10
|
fips: Operating system name and version: Debian 9.1
Version of smsd: 3.1.15-2
Smsd installed from: debian repo
Name and model of a modem / phone: ericsson pci-e card
Interface: pci-e
Hi,
I changed my sms gateway from an pc engines apu to an Intel nuc.
I installed a fresh debian 9 and installed smstools from repo.
Afterwards I removed the ericsson modem from the old hardware and installed it in the intel nuc.
I copied content of /etc/smsd.conf to the new hardware and start the service.
As it look for me in the statfile its connected to the cellular network:
2017-08-22 18:04:41,5, GSM1: CMD: AT+CREG?;+CSQ;+COPS?: +CREG: 2,5,"2F1E","0000E07D" +CSQ: 29,99 +COPS: 0,0,"3-AT",0 OK
But if I sent an sms smsd.log throw:
2017-08-22 18:00:00,6, GSM1: I have to send 1 short message for /var/spool/sms/checked/Test-SMS
2017-08-22 18:00:00,6, GSM1: Sending SMS from to 436991234567
2017-08-22 18:00:00,6, GSM1: Checking if modem is ready
2017-08-22 18:00:00,7, GSM1: -> AT
2017-08-22 18:00:00,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:01,7, GSM1: <- OK
2017-08-22 18:00:01,6, GSM1: Pre-initializing modem
2017-08-22 18:00:01,7, GSM1: -> ATE0+CMEE=1;+CREG=2
2017-08-22 18:00:01,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:01,7, GSM1: <- OK
2017-08-22 18:00:01,6, GSM1: Initializing modem
2017-08-22 18:00:01,7, GSM1: -> AT+CFUN=1
2017-08-22 18:00:01,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:02,7, GSM1: <- OK
2017-08-22 18:00:02,7, GSM1: -> AT+CPMS="ME","ME","ME"
2017-08-22 18:00:02,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:02,7, GSM1: <- +CPMS: 30,30,30,30,30,30 OK
2017-08-22 18:00:02,7, GSM1: -> AT+CSQ
2017-08-22 18:00:02,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:03,7, GSM1: <- +CSQ: 22,99 OK
2017-08-22 18:00:03,6, GSM1: Signal Strength Indicator: (22,99) -69 dBm (Excellent), Bit Error Rate: not known or not detectable
2017-08-22 18:00:03,6, GSM1: Checking if Modem is registered to the network
2017-08-22 18:00:03,7, GSM1: -> AT+CREG?
2017-08-22 18:00:03,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:03,7, GSM1: <- +CREG: 2,1,"0C26","0000779B" OK
2017-08-22 18:00:03,6, GSM1: Modem is registered to the network
2017-08-22 18:00:03,6, GSM1: Location area code changed: 07DC -> 0C26
2017-08-22 18:00:03,6, GSM1: Cell ID changed: 8353 -> 779B
2017-08-22 18:00:03,7, GSM1: -> AT+CSQ
2017-08-22 18:00:03,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:04,7, GSM1: <- +CSQ: 22,99 OK
2017-08-22 18:00:04,6, GSM1: Signal Strength Indicator: (22,99) -69 dBm (Excellent), Bit Error Rate: not known or not detectable
2017-08-22 18:00:04,6, GSM1: Selecting PDU mode
2017-08-22 18:00:04,7, GSM1: -> AT+CMGF=0
2017-08-22 18:00:04,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:04,7, GSM1: <- OK
2017-08-22 18:00:04,7, GSM1: -> AT+CMGS=34
2017-08-22 18:00:04,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:05,7, GSM1: <- >
2017-08-22 18:00:05,7, GSM1: -> 0011000D91349619730900F90000FF15C4F01C949ED341E5B41B442DCFE9AD6973EA02
2017-08-22 18:00:05,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:05,7, GSM1: <- +CMS ERROR: 322 (Memory full)
2017-08-22 18:00:05,3, GSM1: The modem answer was not OK: +CMS ERROR: 322 (Memory full)
2017-08-22 18:00:05,5, GSM1: Waiting 10 sec. before retrying
2017-08-22 18:00:15,6, GSM1: Checking if modem is ready
2017-08-22 18:00:15,7, GSM1: -> AT
2017-08-22 18:00:15,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:16,7, GSM1: <- OK
2017-08-22 18:00:16,6, GSM1: Pre-initializing modem
2017-08-22 18:00:16,7, GSM1: -> ATE0+CMEE=1;+CREG=2
2017-08-22 18:00:16,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:16,7, GSM1: <- OK
2017-08-22 18:00:16,6, GSM1: Initializing modem
2017-08-22 18:00:16,7, GSM1: -> AT+CFUN=1
2017-08-22 18:00:16,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:17,7, GSM1: <- OK
2017-08-22 18:00:17,7, GSM1: -> AT+CPMS="ME","ME","ME"
2017-08-22 18:00:17,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:17,7, GSM1: <- +CPMS: 30,30,30,30,30,30 OK
2017-08-22 18:00:17,7, GSM1: -> AT+CSQ
2017-08-22 18:00:17,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:18,7, GSM1: <- +CSQ: 21,99 OK
2017-08-22 18:00:18,6, GSM1: Signal Strength Indicator: (21,99) -71 dBm (Excellent), Bit Error Rate: not known or not detectable
2017-08-22 18:00:18,6, GSM1: Checking if Modem is registered to the network
2017-08-22 18:00:18,7, GSM1: -> AT+CREG?
2017-08-22 18:00:18,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:18,7, GSM1: <- +CREG: 2,1,"0C26","0000779B" OK
2017-08-22 18:00:18,6, GSM1: Modem is registered to the network
2017-08-22 18:00:18,6, GSM1: Selecting PDU mode
2017-08-22 18:00:18,7, GSM1: -> AT+CMGF=0
2017-08-22 18:00:18,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:19,7, GSM1: <- OK
2017-08-22 18:00:19,7, GSM1: -> AT+CMGS=34
2017-08-22 18:00:19,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:19,7, GSM1: <- >
2017-08-22 18:00:19,7, GSM1: -> 0011000D91349619730900F90000FF15C4F01C949ED341E5B41B442DCFE9AD6973EA02
2017-08-22 18:00:19,7, GSM1: Command is sent, waiting for the answer
2017-08-22 18:00:20,7, GSM1: <- +CMS ERROR: 322 (Memory full)
2017-08-22 18:00:20,3, GSM1: The modem answer was not OK: +CMS ERROR: 322 (Memory full)
2017-08-22 18:00:20,5, GSM1: Waiting 10 sec. before retrying
What does "The modem answer was not OK: +CMS ERROR: 322 (Memory full)" mean??
How can I solve it??
|
|
Fri Oct 14, 2016 08:17
|
fips: Thanks for your reply.
Issue was simple: Antenna was broken ;-)
Now it works like a charm.
|
|
Mon Oct 10, 2016 16:32
|
fips: Operating system name and version: Debian 8.6
Version of smsd: 3.1.5
Smsd installed from: Debian package repository
Name and model of a modem / phone: Ericsson F3507g
Interface: mPCIe
Output smsd.log:
GSM1: Modem handler 0 has started. PID: 11534. Will only send messages.
2016-10-10 18:28:04,6, GSM1: Checking if modem is ready
2016-10-10 18:28:04,7, GSM1: -> AT
2016-10-10 18:28:04,7, GSM1: Command is sent, waiting for the answer
2016-10-10 18:28:04,7, GSM1: <- OK
2016-10-10 18:28:04,6, GSM1: Pre-initializing modem
2016-10-10 18:28:04,7, GSM1: -> ATE0+CMEE=1;+CREG=2
2016-10-10 18:28:04,7, GSM1: Command is sent, waiting for the answer
2016-10-10 18:28:05,7, GSM1: <- OK
2016-10-10 18:28:05,6, GSM1: Checking if modem needs PIN
2016-10-10 18:28:05,7, GSM1: -> AT+CPIN?
2016-10-10 18:28:05,7, GSM1: Command is sent, waiting for the answer
2016-10-10 18:28:05,7, GSM1: <- +CPIN: READY OK
2016-10-10 18:28:05,6, GSM1: Initializing modem
2016-10-10 18:28:05,7, GSM1: -> AT+CFUN=1
2016-10-10 18:28:05,7, GSM1: Command is sent, waiting for the answer
2016-10-10 18:28:06,7, GSM1: <- OK
2016-10-10 18:28:06,7, GSM1: -> AT+CPMS="ME","ME","ME"
2016-10-10 18:28:06,7, GSM1: Command is sent, waiting for the answer
2016-10-10 18:28:06,7, GSM1: <- +CPMS: 0,30,0,30,0,30 OK
2016-10-10 18:28:06,7, GSM1: -> AT+CSQ
2016-10-10 18:28:06,7, GSM1: Command is sent, waiting for the answer
2016-10-10 18:28:07,7, GSM1: <- +CSQ: 99,99 OK
2016-10-10 18:28:07,6, GSM1: Signal Strength Indicator: not present of not measurable, Bit Error Rate: not known or not detectable
2016-10-10 18:28:07,6, GSM1: Checking if Modem is registered to the network
2016-10-10 18:28:07,7, GSM1: -> AT+CREG?
2016-10-10 18:28:07,7, GSM1: Command is sent, waiting for the answer
2016-10-10 18:28:07,7, GSM1: <- +CREG: 2,4 OK
2016-10-10 18:28:07,5, GSM1: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 1. TIME
2016-10-10 18:28:08,7, GSM1: -> AT+CSQ
2016-10-10 18:28:08,7, GSM1: Command is sent, waiting for the answer
2016-10-10 18:28:09,7, GSM1: <- +CSQ: 99,99 OK
2016-10-10 18:28:09,5, GSM1: Signal Strength Indicator: not present of not measurable, Bit Error Rate: not known or not detectable
2016-10-10 18:28:09,7, GSM1: -> AT+CREG?
2016-10-10 18:28:09,7, GSM1: Command is sent, waiting for the answer
2016-10-10 18:28:09,7, GSM1: <- +CREG: 2,4 OK
2016-10-10 18:28:09,5, GSM1: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 2. TIME
2016-10-10 18:28:10,7, GSM1: -> AT+CSQ
My config:
#
# /etc/smsd.conf
#
# Description: Main configuration file for the smsd
#
devices = GSM1
outgoing = /var/spool/sms/outgoing
checked = /var/spool/sms/checked
incoming = /var/spool/sms/incoming
logfile = /var/log/smstools/smsd.log
infofile = /var/run/smstools/smsd.working
pidfile = /var/run/smstools/smsd.pid
outgoing = /var/spool/sms/outgoing
checked = /var/spool/sms/checked
failed = /var/spool/sms/failed
incoming = /var/spool/sms/incoming
sent = /var/spool/sms/sent
stats = /var/log/smstools/smsd_stats
receive_before_send = no
loglevel = 7
autosplit = 3
[GSM1]
init = AT+CFUN=1
device = /dev/ttyACM0
incoming = no
keep_open = yes
cs_convert = yes
report = no
#report_device_details = yes
init2 = AT+CPMS="ME","ME","ME"
#rtscts = no
regular_run_interval = 60
regular_run_cmd = AT+CREG?;+CSQ;+COPS?
regular_run_statfile = /dev/shm/sms_stat
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
