SMSTools3 Search

Welcome, Guest. The forum is currently read-only, but will open soon.

Tue Oct 14, 2025 02:51

• SMSTools3 Community » Search

Page: 1

Keywords: Mode: All keywords (AND)
Wed Oct 16, 2013 05:14 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: 2013-10-16 00:12:22,6, GSM1: Checking device for incoming SMS 2013-10-16 00:12:22,6, GSM1: Checking if modem is ready 2013-10-16 00:12:22,7, GSM1: -> AT 2013-10-16 00:12:22,7, GSM1: Command is sent, waiting for the answer 2013-10-16 00:12:23,7, GSM1: <- OK 2013-10-16 00:12:23,6, GSM1: Pre-initializing modem 2013-10-16 00:12:23,7, GSM1: -> ATE0+CMEE=1;+CREG=2 2013-10-16 00:12:23,7, GSM1: Command is sent, waiting for the answer 2013-10-16 00:12:23,7, GSM1: <- OK 2013-10-16 00:12:23,6, GSM1: Initializing modem 2013-10-16 00:12:23,7, GSM1: -> AT^SYSCFG=13,1,3FFFFFFF,1,2 2013-10-16 00:12:23,7, GSM1: Command is sent, waiting for the answer 2013-10-16 00:12:24,7, GSM1: <- OK 2013-10-16 00:12:24,7, GSM1: -> AT+CSQ 2013-10-16 00:12:24,7, GSM1: Command is sent, waiting for the answer 2013-10-16 00:12:24,7, GSM1: <- +CSQ: 19,99 OK 2013-10-16 00:12:24,6, GSM1: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable 2013-10-16 00:12:24,6, GSM1: Checking if Modem is registered to the network 2013-10-16 00:12:24,7, GSM1: -> AT+CREG? 2013-10-16 00:12:24,7, GSM1: Command is sent, waiting for the answer 2013-10-16 00:12:25,7, GSM1: <- +CREG: 2,1, 520C, D0C1 OK 2013-10-16 00:12:25,6, GSM1: Modem is registered to the network 2013-10-16 00:12:25,6, GSM1: Selecting PDU mode 2013-10-16 00:12:25,7, GSM1: -> AT+CMGF=0 2013-10-16 00:12:25,7, GSM1: Command is sent, waiting for the answer 2013-10-16 00:12:25,7, GSM1: <- OK 2013-10-16 00:12:25,6, GSM1: Checking memory size 2013-10-16 00:12:25,7, GSM1: -> AT+CPMS? 2013-10-16 00:12:25,7, GSM1: Command is sent, waiting for the answer 2013-10-16 00:12:30,7, GSM1: put_command expected (\+CPMS:.*OK)\|(ERROR), timeout occurred. 1. 2013-10-16 00:12:30,7, GSM1: <- 2013-10-16 00:12:30,6, GSM1: Command failed. 2013-10-16 00:12:30,6, GSM1: No SMS received (reading interrupted) 2013-10-16 00:12:41,6, GSM1: Checking device for incoming SMS 2013-10-16 00:12:41,6, GSM1: Checking if modem is ready 2013-10-16 00:12:41,7, GSM1: -> AT
Wed Oct 16, 2013 03:10 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: Okay, so I decided to get the E368 which actually works, however after it runs for about 30-45 minutes it stops functioning... This is in the log: 2013-10-15 16:01:28,6, GSM1: No SMS received 2013-10-15 16:01:39,6, GSM1: Checking device for incoming SMS 2013-10-15 16:01:39,6, GSM1: Checking if modem is ready 2013-10-15 16:01:39,7, GSM1: -> AT 2013-10-15 16:01:39,7, GSM1: Command is sent, waiting for the answer 2013-10-15 16:01:44,7, GSM1: put_command expected (OK)\|(ERROR), timeout occurred. 1. 2013-10-15 16:01:44,7, GSM1: <- 2013-10-15 16:01:44,7, GSM1: -> 2013-10-15 16:01:44,7, GSM1: Command is sent, waiting for the answer 2013-10-15 16:01:49,7, GSM1: put_command expected (OK)\|(ERROR), timeout occurred. 2. 2013-10-15 16:01:49,7, GSM1: <- 2013-10-15 16:01:49,7, GSM1: -> AT 2013-10-15 16:01:49,7, GSM1: Command is sent, waiting for the answer 2013-10-15 16:01:54,7, GSM1: put_command expected (OK)\|(ERROR), timeout occurred. 3. 2013-10-15 16:01:54,7, GSM1: <- 2013-10-15 16:01:55,7, GSM1: -> 2013-10-15 16:01:55,7, GSM1: Command is sent, waiting for the answer 2013-10-15 16:02:00,7, GSM1: put_command expected (OK)\|(ERROR), timeout occurred. 4. 2013-10-15 16:02:00,7, GSM1: <- 2013-10-15 16:02:00,7, GSM1: -> AT 2013-10-15 16:02:00,7, GSM1: Command is sent, waiting for the answer 2013-10-15 16:02:05,7, GSM1: put_command expected (OK)\|(ERROR), timeout occurred. 5. 2013-10-15 16:02:05,7, GSM1: <- 2013-10-15 16:02:05,7, GSM1: ->
Fri Oct 04, 2013 23:31 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: I'm aware how the networks work, and the frequencies. The problem isn't with the SIM as it works in multiple other devices AND other AT&T SIMs don't work. I dunno what more I can do or say.
Fri Oct 04, 2013 14:34 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: I've done as you stated and it showed 3G Prefered was selected, and all bands were enabled, however it never connects to anything. It never wants to acknowledge AT&T's towers, but it shows T-Mobile. I have two of these, they are both unlocked, and both are doing the exact same thing. My only other option is to order a totally different device that will allow me to use SMS on my server, on AT&T's network.
Fri Oct 04, 2013 10:57 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: Okay, so I've tested the Huawei E220 a little more. I used my laptop and drove around and no matter where I went, it never picked up the AT&T tower. I even drove right past the tower, and it never picked it up at all. However, it has picked up the T-Mobile towers all over the area. As I said, the device lost the ability to use the AT&T tower the day they upgraded to 4G. I have a powered USB hub, so "power" isn't an issue here. My phone also has 4 bars (out of 5) where I'm sitting, on AT&T. The problem isn't with signal, or power, or the carrier, it's the Huawei E220.
Thu Oct 03, 2013 22:53 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: I located a different device and this is what happens when I try to use it... 2013-10-03 17:52:27,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.w4wR6s /tmp/smsd_data.Q4JjvI 2013-10-03 17:52:27,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0) 2013-10-03 17:52:27,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2013-10-03 17:52:27,5, smsd: Outgoing file checker has started. PID: 46901. 2013-10-03 17:52:27,7, smsd: All PID's: 46901,46903 2013-10-03 17:52:27,5, GSM1: Modem handler 0 has started. PID: 46903. 2013-10-03 17:52:27,5, GSM1: Using check_memory_method 1: CPMS is used. 2013-10-03 17:52:27,6, GSM1: Checking device for incoming SMS 2013-10-03 17:52:27,6, GSM1: Checking if modem is ready 2013-10-03 17:52:27,7, GSM1: -> AT 2013-10-03 17:52:27,7, GSM1: Command is sent, waiting for the answer 2013-10-03 17:52:28,7, GSM1: <- OK 2013-10-03 17:52:28,6, GSM1: Pre-initializing modem 2013-10-03 17:52:28,7, GSM1: -> ATE0+CMEE=1;+CREG=2 2013-10-03 17:52:28,7, GSM1: Command is sent, waiting for the answer 2013-10-03 17:52:28,7, GSM1: <- OK 2013-10-03 17:52:28,6, GSM1: Checking if modem needs PIN 2013-10-03 17:52:28,7, GSM1: -> AT+CPIN? 2013-10-03 17:52:28,7, GSM1: Command is sent, waiting for the answer 2013-10-03 17:52:29,7, GSM1: <- +CPIN: PH-NET PIN OK 2013-10-03 17:52:29,2, GSM1: PIN handling: expected READY, modem answered +CPIN: PH-NET PIN OK 2013-10-03 17:52:29,2, GSM1: Modem handler 0 terminated abnormally. PID: 46903. Any idea what to do to get past this point?
Thu Oct 03, 2013 21:48 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: Also, something a little odd... +COPS: (1,"T-Mobile","TMO","31026",0),,(0,1,3,4),(0,1,2) It doesn't show AT&T.
Thu Oct 03, 2013 21:43 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: When I put the SIM in an AT&T Phone, it shows great signal, works great, can call and SMS. I put it back in the Huawei E220 and it fails to work. Remember, this all worked perfectly until our area upgraded to 4G/LTE. The SIM works in both 4G and non-4G devices. When sitting here sometimes it shows no signal, other times it shows signal ranging from Workable to Marginal. So, if the problem is the E220, what device should I buy that supports SMS, and will work on AT&T in the USA on EDGE, 3G, and 4G signals?
Thu Sep 26, 2013 17:31 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: I've used all four of these as (init = ) and no matter what, it doesn't make a difference... 2G only : AT^SYSCFG=13,1,3FFFFFFF,2,4 3G only : AT^SYSCFG=14,2,3FFFFFFF,2,4 2G preferred : AT^SYSCFG=2,1,3FFFFFFF,2,4 3G preferred : AT^SYSCFG=2,2,3FFFFFFF,2,4
Thu Sep 26, 2013 13:44 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: I'm aware it isn't a 4G/LTE device, however that shouldn't prevent it from using EDGE or 3G. So the problem is, what is preventing it from using EDGE or 3G?
Fri Sep 20, 2013 14:04 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: bump?
Wed Sep 18, 2013 20:58 smsd fails to register but has signal - SIM works in phone (Help and support)
interex83: Operating system name and version: FreeBSD 8.4 Version of smsd: smstools3-3.1.15 Smsd installed from: ports Name and model of a modem / phone: Huawei E220 Interface: USB Everything was working perfectly until recently in which for some reason everything stopped working. I know our local area just recently enabled 4G on AT&T but not sure if that has anything to do with it. I've removed and reinstalled smstools3 and I've checked the SIM card in multiple other devices and it seems to be just fine. I'm really not sure what could be causing my device to fail to register now. I do not have any INIT commands in my .conf but if you know any I should use, please help. 2013-09-18 15:27:21,2, smsd: Smsd v3.1.15 started. 2013-09-18 15:27:21,2, smsd: Running as root:wheel. 2013-09-18 15:27:21,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.oD7dDe /tmp/smsd_data.2E1z62 2013-09-18 15:27:21,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0) 2013-09-18 15:27:21,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2013-09-18 15:27:21,5, smsd: Outgoing file checker has started. PID: 17484. 2013-09-18 15:27:21,7, smsd: All PID's: 17484,17485 2013-09-18 15:27:21,5, GSM1: Modem handler 0 has started. PID: 17485. 2013-09-18 15:27:21,5, GSM1: Using check_memory_method 1: CPMS is used. 2013-09-18 15:27:21,6, GSM1: Checking device for incoming SMS 2013-09-18 15:27:21,6, GSM1: Checking if modem is ready 2013-09-18 15:27:21,7, GSM1: -> AT 2013-09-18 15:27:21,7, GSM1: Command is sent, waiting for the answer 2013-09-18 15:27:22,7, GSM1: <- OK 2013-09-18 15:27:22,6, GSM1: Pre-initializing modem 2013-09-18 15:27:22,7, GSM1: -> ATE0+CMEE=1;+CREG=2 2013-09-18 15:27:22,7, GSM1: Command is sent, waiting for the answer 2013-09-18 15:27:22,7, GSM1: <- OK 2013-09-18 15:27:22,6, GSM1: Checking if modem needs PIN 2013-09-18 15:27:22,7, GSM1: -> AT+CPIN? 2013-09-18 15:27:22,7, GSM1: Command is sent, waiting for the answer 2013-09-18 15:27:23,7, GSM1: <- +CPIN: READY OK 2013-09-18 15:27:23,7, GSM1: -> AT+CSQ 2013-09-18 15:27:23,7, GSM1: Command is sent, waiting for the answer 2013-09-18 15:27:23,7, GSM1: <- +CSQ: 10,99 OK 2013-09-18 15:27:23,6, GSM1: Signal Strength Indicator: (10,99) -93 dBm (Workable), Bit Error Rate: not known or not detectable 2013-09-18 15:27:23,6, GSM1: Checking if Modem is registered to the network 2013-09-18 15:27:23,7, GSM1: -> AT+CREG? 2013-09-18 15:27:23,7, GSM1: Command is sent, waiting for the answer 2013-09-18 15:27:24,7, GSM1: <- +CREG: 2,2,99E8,94FE OK 2013-09-18 15:27:24,5, GSM1: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 1. TIME 2013-09-18 15:27:25,7, GSM1: -> AT+CSQ 2013-09-18 15:27:25,7, GSM1: Command is sent, waiting for the answer 2013-09-18 15:27:25,7, GSM1: <- +CSQ: 10,99 OK 2013-09-18 15:27:25,5, GSM1: Signal Strength Indicator: (10,99) -93 dBm (Workable), Bit Error Rate: not known or not detectable 2013-09-18 15:27:25,7, GSM1: -> AT+CREG? 2013-09-18 15:27:25,7, GSM1: Command is sent, waiting for the answer 2013-09-18 15:27:26,7, GSM1: <- +CREG: 2,2,99E8,94FE OK 2013-09-18 15:27:26,5, GSM1: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 2. TIME 2013-09-18 15:27:27,7, GSM1: -> AT+CSQ 2013-09-18 15:27:27,7, GSM1: Command is sent, waiting for the answer 2013-09-18 15:27:27,7, GSM1: <- +CSQ: 10,99 OK 2013-09-18 15:27:27,5, GSM1: Signal Strength Indicator: (10,99) -93 dBm (Workable), Bit Error Rate: not known or not detectable 2013-09-18 15:27:27,7, GSM1: -> AT+CREG? 2013-09-18 15:27:27,7, GSM1: Command is sent, waiting for the answer 2013-09-18 15:27:28,7, GSM1: <- +CREG: 2,2,99E8,94FE OK 2013-09-18 15:27:28,5, GSM1: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 3. TIME
Sun Aug 04, 2013 22:10 [solved] Question about executing command and returning results to new outgoing sms. (Help and support)
interex83: Disregard. After a few hours of searching and reading other posts, I was able to set it up exactly how I wanted with using a PHP script as my event handler. So far things are working great.
Sat Aug 03, 2013 18:05 [solved] Question about executing command and returning results to new outgoing sms. (Help and support)
interex83: Operating system name and version: FreeBSD 8.1 Version of smsd: 3.1.14 Smsd installed from: ports Name and model of a modem / phone: Huawei E220 Interface: USB Hello, I've tested my Huawei E220 with FreeBSD using 'cu' and with SMS Server Tools 3 and I can successfully send and receive SMS messages. Now I would like to figure out (or hire someone) how to execute an external command once an SMS has been received with data from the text message, and once the external command has executed, send a returning SMS to the originating number with the results of the external command. For instance as an example only, if one were to send an incoming SMS with the message "server uptime", I'd like to check the uptime and respond to that individual with a text of the current uptime, or if an incoming message were to say "server uname", then the sender would receive a response of the command "uname -sr". I'm very new here and do not completely understand the event-handler and alarm-handler but am willing to try and willing to pay for the help received, via PayPal. Thank you.

Page: 1

• SMSTools3 Community » Search

Top

Time in this board is UTC.