|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Thu Mar 13, 2025 21:38 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Sun Feb 18, 2018 22:47
|
lambda: Finally got around to look into this a bit. Surprisingly there seems to be no portable way to check if the parent process is still around. The only portable way I found to fix the problem of left over modem processes is to turn them into threads.
As this would be quite a deep change, I went for a non-portalbe linux solution. See this patch, that I proposed for inclusion in OpenWRT: https://github.com/haraldg/packages/blob/smstools3/utils/smstools3/patches/004-modem-processes.patch
This also makes the init script a lot simpler.
HTH,
Harald
|
|
Sat Sep 16, 2017 13:28
|
lambda: Hi,
I finally got around to release the set of simple scripts to send alarm calls over the telephone network, I have been working on. See:
http://repo.or.cz/gsmalarm.git
I hope this is useful for some people. Thanks for making this task almost trivial by providing smstools3!
Harald
|
|
Sun Jul 30, 2017 18:12
|
lambda: Hi!
It seems when a modem process terminates (oom_killer, faulty hardware, admin error, etc.) the main process just keeps running patiently for ever. Ie the system stops responding to incoming messages at all. AFAICS there is no configuration option to change this. Likewise when the main process dies in one of the hard ways, the modem processes keep running, though I guess this is a lesser problem.
ATM I use an alarm handler to terminate the main process in such cases, but this get's messy, when there are multiple instances of smsd running.
I also note that the default init script 'sms3' uses some quirky combinations of ps, grep and awk to find all processes that need killing. That can easily go wrong when there are other processes with unlucky names, running. (I had to rename my alarm hander from smsd_alarmhandler to something else, because it kept killing itself via the init script ...)
I'm not sure what the best solution is. A few ideas for features that might help:
* an option to make the main process terminate when a modem process terminates
* an option to just restart a terminated modem process
* modem processes terminating by default when the main process is gone
* a pid file per modem process or some other reliable way to get to pids
In case you are wondering: I'm not doing anything fancy: Just trying to improve the OpenWRT package of smstools3 and thinking of possible use cases.
Harald
|
|
Wed Jun 14, 2017 15:24
|
lambda: Thanks for your input. The setup was already in production, when I read this, so I couldn't test this yet. I will come back to this when there is an opporunity (the setup needs maintainance or I get a new modem).
One unrelated request though: There is a patch in OpenWRT to compile smstools3:
https://github.com/haraldg/packages/blob/smstools3/utils/smstools3/patches/002-Makefile.patch
I don't think the current patch is the best way to handle this, but maybe you can improve the Makefile of smstools instead of me improving the patch in OpenWRT.
Thanks for your help,
Harald
|
|
Mon May 22, 2017 19:59
|
lambda: Hi,
this is somewhat related to this post:
http://smstools3.kekekasvi.com/topic.php?id=825
I'm on OpenWRT/LEDE (using custom built 3.1.21 package) and my modem has 3 devices:
/dev/ttyUSB[0-2] by default. I'm using ttyUSB2.
On the smsd side everything works fine, but the HW is used in an industrial environment with lots of EMI. This causes the usb bus to disconnect/reconnect the modem every now and then. (It can be simulated by unplugging/repluging the modem, I think.)
When this happens smsd recieves EIO, but insists on using the non-existent device. Ie I get a line of
2017-05-22 16:41:48,3, GSM: write_to_modem: error 5: Input / output error
every second without smsd ever recovering.
And what's even worse: It seems since ttyUSB2 is still "in use" after reconnecting the modem, the linux kernel assigns the modem to the devices ttyUSB0, ttyUSB1 and ttyUSB3.
I managed to work around this with an alarmhandler, that detects the EIO error and a startup script that links /dev/modem to the right device node, but it is clumsy and has some annoying side effects. I think smsd could handle this much better:
* do something sane on EIO - probably closing the device and following the usual startup procedure
* maybe also provide an option to use the highest number ttyUSB*, whatever it might be.
|
|
Tue May 16, 2017 19:51
|
lambda: Hi,
I have been able to fix all remaining issues with voice calls by using /dev/ttyUSB2 instead of /dev/ttyUSB0. Looks like the latter is only good for pppd, but not for smsd.
Maybe somebody else finds this information useful.
|
|
Sat May 06, 2017 10:56
|
lambda: Operating system name and version: Debian testing
Version of smsd: 3.1.20
Smsd installed from: sources
Name and model of a modem / phone: E1750
Interface: /dev/ttyUSB0
Hi, not sure if this is a bug report, a feature request or just a modem that is completely bonkers ...
Sending / receiving SMS with this modem seems to work fine.
Handling incoming voice calls also started to work after I enabled CLIP.
However outgoing calls cause a lot of trouble:
Since ATD returns OK immediatly, I first tried
voicecall_cpas = yes
however this only caused a minor delay before answering with +CPAS: 4 OK (before the call was answered at the other and), so the commands to send DTMF tones returned errrors.
Next I tried voicecall_clcc = yes, which works a bit better (smsd waits for the other side), but when the oder side either accepts or denys the call, the final CLCC command doesn't return a result and the modem stops responding like it did on incoming calls before I used CLIP. I guess it is in some call_is_active state, where normal command processing is disabled.
However in rare cases the final CLCC command does report an active call, in which case the voice call procedure is executed normally, so I guess some race is involved as well. (Only saw that once so far, so not clear how frequent this is.)
This is the relevant part of the configuration:
[GSM1]
init = AT+CNMI=0,0,0,0,0
device = /dev/ttyUSB0
incoming = yes
pin = xxxx
baudrate = 115200
#check_memory_method = 2
report_device_details = yes
memory_start = 0
phonecalls = clip
voicecall_clcc = yes
And this is an example log of a session where the other side accepts the call, but the connection to the modem gets stuck (some boring lines in the middle omitted):
2017-05-06 11:20:53,2, smsd: Smsd v3.1.20 started.
2017-05-06 11:20:53,2, smsd: Running as rld:rld (1000:1000).
2017-05-06 11:20:53,7, smsd: Running startup_check (shell): /home/lambda/gsmalarm/sms/incoming/smsd_script.D4QMQM /tmp/smsd_data.YQvNDk
2017-05-06 11:20:53,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2017-05-06 11:20:53,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2017-05-06 11:20:53,5, smsd: Outgoing file checker has started. PID: 1623.
2017-05-06 11:20:53,7, smsd: All PID's: 1623,1624
2017-05-06 11:20:53,5, GSM1: Modem handler 0 has started. PID: 1624.
2017-05-06 11:20:53,5, GSM1: Using check_memory_method 1: CPMS is used.
2017-05-06 11:20:53,6, GSM1: Checking device for incoming SMS
2017-05-06 11:20:53,6, GSM1: Checking if modem is ready
2017-05-06 11:20:53,7, GSM1: -> AT
2017-05-06 11:20:53,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:20:54,7, GSM1: <- OK
2017-05-06 11:20:54,6, GSM1: Pre-initializing modem
2017-05-06 11:20:54,7, GSM1: -> ATE0+CMEE=1;+CLIP=1;+CREG=2
2017-05-06 11:20:54,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:20:54,7, GSM1: <- OK
2017-05-06 11:20:54,6, GSM1: Checking if modem needs PIN
2017-05-06 11:20:54,7, GSM1: -> AT+CPIN?
2017-05-06 11:20:54,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:20:54,7, GSM1: <- +CPIN:READY OK
2017-05-06 11:20:54,6, GSM1: Initializing modem
2017-05-06 11:20:54,7, GSM1: -> AT+CNMI=0,0,0,0,0
2017-05-06 11:20:54,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:20:54,7, GSM1: <- OK
2017-05-06 11:20:54,7, GSM1: -> AT+CSQ
2017-05-06 11:20:54,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:20:54,7, GSM1: <- +CSQ: 31,99 OK
2017-05-06 11:20:54,6, GSM1: Signal Strength Indicator: (31,99) -51 dBm (Excellent), Bit Error Rate: not known or not detectable
2017-05-06 11:20:54,6, GSM1: Checking if Modem is registered to the network
2017-05-06 11:20:54,7, GSM1: -> AT+CREG?
2017-05-06 11:20:54,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:20:54,7, GSM1: <- +CREG: 2,5, 2E3AD5, 105 OK
2017-05-06 11:20:54,6, GSM1: Modem is registered to a roaming partner network
2017-05-06 11:20:54,6, GSM1: Location area code: 2E3AD5, Cell ID: 105
2017-05-06 11:20:54,7, GSM1: -> AT+CSQ
2017-05-06 11:20:54,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:20:54,7, GSM1: <- +CSQ: 31,99 OK
2017-05-06 11:20:54,6, GSM1: Signal Strength Indicator: (31,99) -51 dBm (Excellent), Bit Error Rate: not known or not detectable
2017-05-06 11:20:54,6, GSM1: Selecting PDU mode
2017-05-06 11:20:54,7, GSM1: -> AT+CMGF=0
2017-05-06 11:20:54,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:20:54,7, GSM1: <- OK
2017-05-06 11:20:54,7, GSM1: -> AT+CGSN
2017-05-06 11:20:54,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:20:54,7, GSM1: <- 351753035069029 OK
2017-05-06 11:20:54,5, GSM1: IMEI: 351753035069029
2017-05-06 11:20:55,7, GSM1: -> AT+CIMI
2017-05-06 11:20:55,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:20:55,7, GSM1: <- 232122000256622 OK
2017-05-06 11:20:55,5, GSM1: IMSI: 232122000256622
2017-05-06 11:20:55,6, GSM1: Checking if reading of messages is supported
2017-05-06 11:20:55,7, GSM1: -> AT+CPMS?
2017-05-06 11:20:55,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:20:55,7, GSM1: <- +CPMS: "ME",0,255,"ME",0,255,"ME",0,255 OK
2017-05-06 11:20:55,7, GSM1: ## Start of device details
2017-05-06 11:20:55,7, GSM1: # Manufacturer identification:
2017-05-06 11:20:55,7, GSM1: -> AT+CGMI
2017-05-06 11:20:55,7, GSM1: <- QUALCOMM INCORPORATED
OK
2017-05-06 11:20:55,7, GSM1: # Model identification:
2017-05-06 11:20:55,7, GSM1: -> AT+CGMM
2017-05-06 11:20:55,7, GSM1: <- E1750
OK
2017-05-06 11:20:55,7, GSM1: # Revision identification:
2017-05-06 11:20:55,7, GSM1: -> AT+CGMR
2017-05-06 11:20:55,7, GSM1: <- +CGMR:01.02262013.354G
OK
2017-05-06 11:20:55,7, GSM1: # New message indications, list of supported modes:
2017-05-06 11:20:55,7, GSM1: -> AT+CNMI=?
2017-05-06 11:20:55,7, GSM1: <- +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1)
OK
2017-05-06 11:20:55,7, GSM1: # New message indications, current settings:
2017-05-06 11:20:55,7, GSM1: -> AT+CNMI?
2017-05-06 11:20:55,7, GSM1: <- +CNMI: 0,0,0,0,0
OK
2017-05-06 11:20:55,7, GSM1: # Preferred message storage, list of supported mem's:
2017-05-06 11:20:55,7, GSM1: -> AT+CPMS=?
2017-05-06 11:20:55,7, GSM1: <- +CPMS: ("ME","MT","SM","SR"),("ME","MT","SM","SR"),("ME","MT","SM","SR")
OK
2017-05-06 11:20:55,7, GSM1: # Phonebook storage, available mem's:
2017-05-06 11:20:56,7, GSM1: -> AT+CPBS=?
2017-05-06 11:20:56,7, GSM1: <- +CPBS: ("SM","DC","FD","MC","ME","RC","EN","ON")
OK
2017-05-06 11:20:56,7, GSM1: # List messages, list of supported stat's:
2017-05-06 11:20:56,7, GSM1: -> AT+CMGL=?
2017-05-06 11:20:56,7, GSM1: <- +CMGL: (0-4)
OK
2017-05-06 11:20:56,7, GSM1: # Delete message, list of supported values:
2017-05-06 11:20:56,7, GSM1: -> AT+CMGD=?
2017-05-06 11:20:56,7, GSM1: <- +CMGD: (),(0-4)
OK
2017-05-06 11:20:56,7, GSM1: # Phone activity status, list of supported stat's:
2017-05-06 11:20:56,7, GSM1: -> AT+CPAS=?
2017-05-06 11:20:56,7, GSM1: <- +CPAS: (0,3,4)
OK
2017-05-06 11:20:56,7, GSM1: # TE character set, list of supported charset's:
2017-05-06 11:20:56,7, GSM1: -> AT+CSCS=?
2017-05-06 11:20:56,7, GSM1: <- +CSCS: ("IRA","GSM","UCS2")
OK
2017-05-06 11:20:56,7, GSM1: # TE character set, current setting:
2017-05-06 11:20:56,7, GSM1: -> AT+CSCS?
2017-05-06 11:20:56,7, GSM1: <- +CSCS: "IRA"
OK
2017-05-06 11:20:56,7, GSM1: ## End of device details
2017-05-06 11:20:56,6, GSM1: Checking memory size
2017-05-06 11:20:56,7, GSM1: -> AT+CPMS?
2017-05-06 11:20:56,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:20:56,7, GSM1: <- +CPMS: "ME",0,255,"ME",0,255,"ME",0,255 OK
2017-05-06 11:20:56,6, GSM1: Used memory is 0 of 255
2017-05-06 11:20:56,6, GSM1: No SMS received
2017-05-06 11:21:06,6, GSM1: Checking device for incoming SMS
2017-05-06 11:21:06,6, GSM1: Checking if modem is ready
2017-05-06 11:21:06,7, GSM1: -> AT
2017-05-06 11:21:06,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:21:06,7, GSM1: <- OK
2017-05-06 11:21:06,6, GSM1: Pre-initializing modem
2017-05-06 11:21:07,7, GSM1: -> ATE0+CMEE=1;+CLIP=1;+CREG=2
2017-05-06 11:21:07,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:21:07,7, GSM1: <- OK
2017-05-06 11:21:07,6, GSM1: Checking if modem needs PIN
2017-05-06 11:21:07,7, GSM1: -> AT+CPIN?
2017-05-06 11:21:07,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:21:07,7, GSM1: <- +CPIN:READY OK
2017-05-06 11:21:07,6, GSM1: Initializing modem
2017-05-06 11:21:07,7, GSM1: -> AT+CNMI=0,0,0,0,0
2017-05-06 11:21:07,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:21:07,7, GSM1: <- OK
2017-05-06 11:21:07,7, GSM1: -> AT+CSQ
2017-05-06 11:21:07,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:21:07,7, GSM1: <- +CSQ: 31,99 OK
2017-05-06 11:21:07,6, GSM1: Signal Strength Indicator: (31,99) -51 dBm (Excellent), Bit Error Rate: not known or not detectable
2017-05-06 11:21:07,6, GSM1: Checking if Modem is registered to the network
2017-05-06 11:21:07,7, GSM1: -> AT+CREG?
2017-05-06 11:21:07,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:21:07,7, GSM1: <- +CREG: 2,5, 2E3AD5, 105 OK
2017-05-06 11:21:07,6, GSM1: Modem is registered to a roaming partner network
2017-05-06 11:21:07,6, GSM1: Selecting PDU mode
2017-05-06 11:21:07,7, GSM1: -> AT+CMGF=0
2017-05-06 11:21:07,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:21:07,7, GSM1: <- OK
2017-05-06 11:21:07,6, GSM1: Checking memory size
2017-05-06 11:21:07,7, GSM1: -> AT+CPMS?
2017-05-06 11:21:07,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:21:07,7, GSM1: <- +CPMS: "ME",0,255,"ME",0,255,"ME",0,255 OK
2017-05-06 11:21:07,6, GSM1: Used memory is 0 of 255
2017-05-06 11:21:07,6, GSM1: No SMS received
2017-05-06 11:22:34,6, GSM1: Checking device for incoming SMS
2017-05-06 11:22:34,6, GSM1: Checking if modem is ready
2017-05-06 11:22:34,7, GSM1: -> AT
2017-05-06 11:22:34,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:22:34,7, GSM1: <- OK
2017-05-06 11:22:34,6, GSM1: Pre-initializing modem
2017-05-06 11:22:34,7, GSM1: -> ATE0+CMEE=1;+CLIP=1;+CREG=2
2017-05-06 11:22:34,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:22:34,7, GSM1: <- OK
2017-05-06 11:22:34,6, GSM1: Checking if modem needs PIN
2017-05-06 11:22:34,7, GSM1: -> AT+CPIN?
2017-05-06 11:22:34,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:22:34,7, GSM1: <- +CPIN:READY OK
2017-05-06 11:22:34,6, GSM1: Initializing modem
2017-05-06 11:22:35,7, GSM1: -> AT+CNMI=0,0,0,0,0
2017-05-06 11:22:35,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:22:35,7, GSM1: <- OK
2017-05-06 11:22:35,7, GSM1: -> AT+CSQ
2017-05-06 11:22:35,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:22:35,7, GSM1: <- +CSQ: 31,99 OK
2017-05-06 11:22:35,6, GSM1: Signal Strength Indicator: (31,99) -51 dBm (Excelle
nt), Bit Error Rate: not known or not detectable
2017-05-06 11:22:35,6, GSM1: Checking if Modem is registered to the network
2017-05-06 11:22:35,7, GSM1: -> AT+CREG?
2017-05-06 11:22:35,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:22:35,7, GSM1: <- +CREG: 2,5, 2E3AD5, 105 OK
2017-05-06 11:22:35,6, GSM1: Modem is registered to a roaming partner network
2017-05-06 11:22:35,6, GSM1: Selecting PDU mode
2017-05-06 11:22:35,7, GSM1: -> AT+CMGF=0
2017-05-06 11:22:35,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:22:35,7, GSM1: <- OK
2017-05-06 11:22:35,6, GSM1: Checking memory size
2017-05-06 11:22:35,7, GSM1: -> AT+CPMS?
2017-05-06 11:22:35,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:22:35,7, GSM1: <- +CPMS: "ME",0,255,"ME",0,255,"ME",0,255 OK
2017-05-06 11:22:35,6, GSM1: Used memory is 0 of 255
2017-05-06 11:22:35,6, GSM1: No SMS received
2017-05-06 11:22:44,5, smsd: SMS To: 436506731041. Moved file /home/lambda/gsmalarm/sms/outgoing/voicecall to /home/lambda/gsmalarm/sms/checked
2017-05-06 11:22:44,6, GSM1: I have to send 1 short message for /home/lambda/gsmalarm/sms/checked/voicecall
2017-05-06 11:22:44,6, GSM1: Checking if modem is ready
2017-05-06 11:22:44,7, GSM1: -> AT
2017-05-06 11:22:44,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:22:44,7, GSM1: <- OK
2017-05-06 11:22:44,6, GSM1: Pre-initializing modem
2017-05-06 11:22:44,7, GSM1: -> ATE0+CMEE=1;+CLIP=1;+CREG=2
2017-05-06 11:22:44,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:22:44,7, GSM1: <- OK
2017-05-06 11:22:44,6, GSM1: Checking if modem needs PIN
2017-05-06 11:22:44,7, GSM1: -> AT+CPIN?
2017-05-06 11:22:44,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:22:44,7, GSM1: <- +CPIN:READY OK
2017-05-06 11:22:44,6, GSM1: Initializing modem
2017-05-06 11:22:44,7, GSM1: -> AT+CNMI=0,0,0,0,0
2017-05-06 11:22:44,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:22:44,7, GSM1: <- OK
2017-05-06 11:22:44,7, GSM1: -> AT+CSQ
2017-05-06 11:22:44,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:22:44,7, GSM1: <- +CSQ: 31,99 OK
2017-05-06 11:22:44,6, GSM1: Signal Strength Indicator: (31,99) -51 dBm (Excellent), Bit Error Rate: not known or not detectable
2017-05-06 11:22:44,6, GSM1: Checking if Modem is registered to the network
2017-05-06 11:22:44,7, GSM1: -> AT+CREG?
2017-05-06 11:22:44,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-06 11:22:44,7, GSM1: <- +CREG: 2,5, 2E3AD5, 105 OK
2017-05-06 11:22:44,6, GSM1: Modem is registered to a roaming partner network
2017-05-06 11:22:44,6, GSM1: Selecting PDU mode
2017-05-06 11:22:44,7, GSM1: -> AT+CMGF=0
2017-05-06 11:22:44,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:22:44,7, GSM1: <- OK
2017-05-06 11:22:44,6, GSM1: I have to make a voice call to 436506731041, with (3 times) DTMF 1,1,1,#,0,0,0,#,1,1,0,0,1
2017-05-06 11:22:44,7, GSM1: -> ATD+436506731041;
2017-05-06 11:22:44,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:44,7, GSM1: <- OK
2017-05-06 11:22:45,7, GSM1: -> AT+CLCC
2017-05-06 11:22:45,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:45,7, GSM1: <- +CLCC: 1,0,2,0,0,"+436506731041",145 OK
2017-05-06 11:22:45,7, GSM1: -> AT+CLCC
2017-05-06 11:22:45,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:45,7, GSM1: <- +CLCC: 1,0,2,0,0,"+436506731041",145 OK
2017-05-06 11:22:46,7, GSM1: -> AT+CLCC
2017-05-06 11:22:46,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:46,7, GSM1: <- +CLCC: 1,0,2,0,0,"+436506731041",145 OK
2017-05-06 11:22:46,7, GSM1: -> AT+CLCC
2017-05-06 11:22:46,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:46,7, GSM1: <- +CLCC: 1,0,2,0,0,"+436506731041",145 OK
2017-05-06 11:22:47,7, GSM1: -> AT+CLCC
2017-05-06 11:22:47,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:47,7, GSM1: <- +CLCC: 1,0,2,0,0,"+436506731041",145 OK
2017-05-06 11:22:47,7, GSM1: -> AT+CLCC
2017-05-06 11:22:47,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:47,7, GSM1: <- +CLCC: 1,0,2,0,0,"+436506731041",145 OK
2017-05-06 11:22:48,7, GSM1: -> AT+CLCC
2017-05-06 11:22:48,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:48,7, GSM1: <- +CLCC: 1,0,2,0,0,"+436506731041",145 OK
2017-05-06 11:22:48,7, GSM1: -> AT+CLCC
2017-05-06 11:22:48,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:48,7, GSM1: <- +CLCC: 1,0,2,0,0,"+436506731041",145 OK
2017-05-06 11:22:49,7, GSM1: -> AT+CLCC
2017-05-06 11:22:49,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:49,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:49,7, GSM1: -> AT+CLCC
2017-05-06 11:22:49,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:49,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:50,7, GSM1: -> AT+CLCC
2017-05-06 11:22:50,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:50,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:50,7, GSM1: -> AT+CLCC
2017-05-06 11:22:50,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:50,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:51,7, GSM1: -> AT+CLCC
2017-05-06 11:22:51,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:51,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:51,7, GSM1: -> AT+CLCC
2017-05-06 11:22:51,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:52,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:52,7, GSM1: -> AT+CLCC
2017-05-06 11:22:52,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:52,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:53,7, GSM1: -> AT+CLCC
2017-05-06 11:22:53,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:53,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:53,7, GSM1: -> AT+CLCC
2017-05-06 11:22:53,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:53,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:54,7, GSM1: -> AT+CLCC
2017-05-06 11:22:54,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:54,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:54,7, GSM1: -> AT+CLCC
2017-05-06 11:22:54,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:54,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:55,7, GSM1: -> AT+CLCC
2017-05-06 11:22:55,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:55,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:55,7, GSM1: -> AT+CLCC
2017-05-06 11:22:55,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:55,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:56,7, GSM1: -> AT+CLCC
2017-05-06 11:22:56,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:22:56,7, GSM1: <- +CLCC: 1,0,3,0,0,"+436506731041",145 OK
2017-05-06 11:22:56,7, GSM1: -> AT+CLCC
2017-05-06 11:22:56,7, GSM1: Command is sent, waiting for the answer. (120)
2017-05-06 11:24:56,7, GSM1: No answer, put_command expected (OK)|(NO CARRIER)|(BUSY)|(NO ANSWER)|(ERROR)|(DELAYED), timeout occurred. 1.
2017-05-06 11:24:56,7, GSM1: <-
2017-05-06 11:24:56,6, GSM1: The result of a voice call was Hangup
2017-05-06 11:24:56,6, GSM1: SMS To: 436506731041. Moved file /home/lambda/gsmalarm/sms/checked/voicecall to /home/lambda/gsmalarm/sms/sent/voicecall
2017-05-06 11:24:56,7, GSM1: Running eventhandler: /home/lambda/gsmalarm/eventhandler-logger SENT /home/lambda/gsmalarm/sms/sent/voicecall
2017-05-06 11:24:56,7, GSM1: Done: eventhandler, execution time 0 sec., status: 0 (0)
2017-05-06 11:24:56,6, GSM1: Checking device for incoming SMS
2017-05-06 11:24:56,6, GSM1: Checking if modem is ready
2017-05-06 11:24:56,7, GSM1: -> AT
2017-05-06 11:24:56,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:25:01,7, GSM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 2.
2017-05-06 11:25:01,7, GSM1: <-
2017-05-06 11:25:01,7, GSM1: -> ^Z
2017-05-06 11:25:01,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:25:06,7, GSM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 3.
2017-05-06 11:25:06,7, GSM1: <-
2017-05-06 11:25:06,7, GSM1: -> AT
2017-05-06 11:25:06,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:25:11,7, GSM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 4.
2017-05-06 11:25:11,7, GSM1: <-
2017-05-06 11:25:11,7, GSM1: -> ^Z
2017-05-06 11:25:11,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:25:16,7, GSM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 5.
2017-05-06 11:25:16,7, GSM1: <-
2017-05-06 11:25:16,7, GSM1: -> AT
2017-05-06 11:25:16,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-06 11:25:21,7, GSM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 6.
|
|
Wed May 03, 2017 12:07
|
lambda: Hi,
I know this was changed just recently, but the new pre_init string doesn't work with my modem:
2017-05-02 11:01:18,5, GSM1: Using check_memory_method 1: CPMS is used.
2017-05-02 11:01:18,6, GSM1: Checking device for incoming SMS
2017-05-02 11:01:18,6, GSM1: Checking if modem is ready
2017-05-02 11:01:19,7, GSM1: -> AT
2017-05-02 11:01:19,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-02 11:01:19,7, GSM1: <- AT OK
2017-05-02 11:01:19,6, GSM1: Pre-initializing modem
2017-05-02 11:01:19,7, GSM1: -> ATE0;+CMEE=1;+CREG=2
2017-05-02 11:01:19,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-02 11:01:19,7, GSM1: <- ATE0;+CMEE=1;+CREG=2 ERROR
2017-05-02 11:01:19,3, GSM1: Modem did not accept the pre-init string
However this works:
2017-05-03 11:52:57,5, GSM1: Using check_memory_method 1: CPMS is used.
2017-05-03 11:52:57,6, GSM1: Checking device for incoming SMS
2017-05-03 11:52:57,6, GSM1: Checking if modem is ready
2017-05-03 11:52:58,7, GSM1: -> AT
2017-05-03 11:52:58,7, GSM1: Command is sent, waiting for the answer. (5)
2017-05-03 11:52:58,7, GSM1: <- OK
2017-05-03 11:52:58,6, GSM1: Pre-initializing modem
2017-05-03 11:52:58,7, GSM1: -> ATE0+CMEE=1;+CREG=2
2017-05-03 11:52:58,7, GSM1: Command is sent, waiting for the answer. (10)
2017-05-03 11:52:58,7, GSM1: <- OK
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
