SMS Server Tools 3
 Menu
Basic information:
Additional information:
Support:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

 Search
Custom Search

 Visitor locations
 
 SMS Server Tools 3 Community
Welcome, Guest. The forum is currently read-only, but will open soon. Fri Aug 29, 2025 21:25
SMSTools3 Community » Search Bottom

Page:  1

Keywords:
Mode: All keywords (AND)
blueeye: Another Cable >> No problem. Thank you!
blueeye: Hello keke, the changes doesn't fix the Problem. I think i have to look for another Cable. Thank you for the fast answer. Kind Regards
blueeye: Operating system name and version: Suse Linux Enterprise Server 10 SP2 Version of smsd: v3.1.6 Smsd installed from: sources Name and model of a modem / phone: Cinterion Siemens TC35i Interface: serial Hi@all, when i start the sms3 service i receive following error: 2010-03-01 16:34:42,2, smsd: Smsd v3.1.6 started. 2010-03-01 16:34:42,2, smsd: Running as root:root. 2010-03-01 16:34:42,7, smsd: Running startup_check (shell): /tmp/smsd_script.gFSuMd /tmp/smsd_data.dlDqcy 2010-03-01 16:34:42,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0) 2010-03-01 16:34:42,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2010-03-01 16:34:42,5, GSM1: Modem handler 0 has started. PID: 6746. 2010-03-01 16:34:42,5, GSM1: Using check_memory_method 1: CPMS is used. 2010-03-01 16:34:42,6, GSM1: Checking device for incoming SMS 2010-03-01 16:34:42,6, GSM1: Checking if modem is ready 2010-03-01 16:34:42,5, smsd: Outgoing file checker has started. PID: 6745. 2010-03-01 16:34:43,7, GSM1: -> AT 2010-03-01 16:34:43,7, GSM1: Command is sent, waiting for the answer 2010-03-01 16:34:48,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1. 2010-03-01 16:34:48,7, GSM1: <- 2010-03-01 16:34:48,7, GSM1: -> 2010-03-01 16:34:48,7, GSM1: Command is sent, waiting for the answer 2010-03-01 16:34:53,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 2. 2010-03-01 16:34:53,7, GSM1: <- 2010-03-01 16:34:54,7, GSM1: -> AT 2010-03-01 16:34:54,7, GSM1: Command is sent, waiting for the answer 2010-03-01 16:34:59,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 3. 2010-03-01 16:34:59,7, GSM1: <- 2010-03-01 16:34:59,7, GSM1: -> 2010-03-01 16:34:59,7, GSM1: Command is sent, waiting for the answer 2010-03-01 16:35:04,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 4. 2010-03-01 16:35:04,7, GSM1: <- 2010-03-01 16:35:04,7, GSM1: -> AT 2010-03-01 16:35:04,7, GSM1: Command is sent, waiting for the answer 2010-03-01 16:35:09,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 5. 2010-03-01 16:35:09,7, GSM1: <- 2010-03-01 16:35:10,7, GSM1: -> . . . aso. my Config-File is: devices = GSM1 logfile = /var/log/smsd.log loglevel = 7 failed = /var/spool/sms/failed [GSM1] device = /dev/ttyS0 incoming = yes init = AT+CNMI=1,2,0,1,1 #init = AT+CNMI=2,0,0,2,1 baudrate = 115200 regular_run_cmd = AT+CSQ regular_run_cmd = AT+CREG? regular_run_cmd = AT+COPS? regular_run_cmd = AT&V regular_run_cmd = AT^SCKS? regular_run_interval = 60 regular_run_statfile = /var/log/smstools/smsd_stats/modem_status The LED of the Moden is blinking like it is connected. But the Modem doesn't answer. I also tried the other init-command (from the TC35) but it doesn't help. Thank you for Helping!

Page:  1

SMSTools3 Community » Search Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.