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 Mar 14, 2025 10:50
SMSTools3 Community » Search Bottom

Page:  1

Keywords:
Mode: All keywords (AND)
edakacj: The problem is solved! The solution was found in FAQ on your website :) I am very sorry that I did not read it before. process "modemanager" used a serial port. smstools cold not connect modem because the port was busy. I found this process and killed him. sudo lsof | grep USB ps aux | grep Modem sudo kill *PID* after that it worked!
edakacj: my config is very simple: devices = GSM1 logfile = /var/log/smsd.log loglevel = 7 [GSM1] report_device_details = yes device = /dev/ttyUSB3 incoming = yes
edakacj: Operating system name and version: Ubuntu 19.04 Version of smsd: Version 3.1.21 Smsd installed from: zip from site Name and model of a modem / phone: ZTE MF180 Interface: USB I have this a problem too! "No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred." again and again 2019-08-09 11:07:03,2, smsd: Smsd v3.1.21 started. 2019-08-09 11:07:03,2, smsd: Running as root:root (0:0). 2019-08-09 11:07:03,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.H41iNb /tmp/smsd_data.nRzrCX 2019-08-09 11:07:03,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0) 2019-08-09 11:07:03,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2019-08-09 11:07:03,5, smsd: Outgoing file checker has started. PID: 21255. 2019-08-09 11:07:03,7, smsd: All PID's: 21255,21256 2019-08-09 11:07:03,5, GSM1: Modem handler 0 has started. PID: 21256. 2019-08-09 11:07:03,5, GSM1: Using check_memory_method 2: CMGD is used. 2019-08-09 11:07:03,6, GSM1: Checking device for incoming SMS 2019-08-09 11:07:03,6, GSM1: Checking if modem is ready 2019-08-09 11:07:03,7, GSM1: -> AT 2019-08-09 11:07:03,7, GSM1: Command is sent, waiting for the answer. (5) 2019-08-09 11:07:08,7, GSM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 1. 2019-08-09 11:07:08,7, GSM1: <- 2019-08-09 11:07:08,7, GSM1: -> � 2019-08-09 11:07:08,7, GSM1: Command is sent, waiting for the answer. (5) 2019-08-09 11:07:13,7, GSM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 2. 2019-08-09 11:07:13,7, GSM1: <- 2019-08-09 11:07:13,7, GSM1: -> AT 2019-08-09 11:07:13,7, GSM1: Command is sent, waiting for the answer. (5) 2019-08-09 11:07:18,7, GSM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 3. 2019-08-09 11:07:18,7, GSM1: <- 2019-08-09 11:07:18,7, GSM1: -> � 2019-08-09 11:07:18,7, GSM1: Command is sent, waiting for the answer. (5) 2019-08-09 11:07:23,7, GSM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 4. 2019-08-09 11:07:23,7, GSM1: <- 2019-08-09 11:07:23,7, GSM1: -> AT 2019-08-09 11:07:23,7, GSM1: Command is sent, waiting for the answer. (5) 2019-08-09 11:07:28,7, GSM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 5. 2019-08-09 11:07:28,7, GSM1: <- 2019-08-09 11:07:28,7, GSM1: -> � 2019-08-09 11:07:28,7, GSM1: Command is sent, waiting for the answer. (5) 2019-08-09 11:07:33,7, GSM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 6. but other sms tools (gnokii and Modem Manager GUI) send sms successfully. please help.

Page:  1

SMSTools3 Community » Search Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.