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. Thu Nov 21, 2024 20:55
SMSTools3 Community » Help and support Bottom

AT request not being received, or just not being returned

Login and Post Reply

Page:  1

Author Post
Member
Registered:
Mar 2013
Location: San Luis Obispo CA, United States of America
Operating system name and version: Debian Squeeze
Version of smsd: 3.1.11
Smsd installed from: apt-get, likely the standard repository
Name and model of a modem: Indosat IM2
Interface: USB

Below I've posted the log file of what's been happening. I put a file in /outgoing/, it gets moved to checked. Then nothing happens. I'll be honest I don't know what's going on very well, but from what i can tell, the AT command is being sent, and the modem isn't responding. I'm using the standard config file that came with smstools. I will however paste the config if I need to.

I appreciate any help in advance. Also, the issue I'm having is near the bottom, this log paste is a little larger than it needs to be.

2013-02-28 15:58:01,2, smsd: Smsd v3.1.11 started.
2013-02-28 15:58:01,2, smsd: Running as smsd:dialout.
2013-02-28 15:58:01,2, smsd: There was 1 error while reading the config file:
2013-02-28 15:58:01,2, smsd: - Unknown global setting: device
2013-02-28 15:58:01,2, smsd: Incoming directory yes cannot be opened.
2013-02-28 15:58:01,7, smsd: Running startup_check (shell): /tmp/smsd_script.uTcbpV /tmp/smsd_data.ZCiiS9
2013-02-28 15:58:01,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2013-02-28 15:58:01,2, smsd: There was 2 major problems found.
2013-02-28 15:58:01,2, smsd: Smsd mainprocess terminated.
2013-02-28 15:58:51,2, smsd: Smsd v3.1.11 started.
2013-02-28 15:58:51,2, smsd: Running as smsd:dialout.
2013-02-28 15:58:51,2, smsd: There was 1 error while reading the config file:
2013-02-28 15:58:51,2, smsd: - Unknown global setting: device
2013-02-28 15:58:51,2, smsd: Incoming directory yes cannot be opened.
2013-02-28 15:58:51,7, smsd: Running startup_check (shell): /tmp/smsd_script.BGK1pJ /tmp/smsd_data.V7B4da
2013-02-28 15:58:51,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2013-02-28 15:58:51,2, smsd: There was 2 major problems found.
2013-02-28 15:58:51,2, smsd: Smsd mainprocess terminated.
2013-02-28 16:05:31,2, smsd: Smsd v3.1.11 started.
2013-02-28 16:05:31,2, smsd: Running as root:root.
2013-02-28 16:05:31,7, smsd: Running startup_check (shell): /tmp/smsd_script.B5REsZ /tmp/smsd_data.g4Nc6L
2013-02-28 16:05:31,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2013-02-28 16:05:31,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2013-02-28 16:05:31,5, smsd: Outgoing file checker has started. PID: 1605.
2013-02-28 16:05:31,5, GSM1: Modem handler 0 has started. PID: 1606.
2013-02-28 16:05:31,5, GSM1: Using check_memory_method 1: CPMS is used.
2013-02-28 16:05:31,6, GSM1: I have to send 1 short message for /var/spool/sms/checked/test.sms
2013-02-28 16:05:31,6, GSM1: Sending SMS from to 18057045518
2013-02-28 16:05:31,6, GSM1: Checking if modem is ready
2013-02-28 16:05:31,7, GSM1: -> AT
2013-02-28 16:05:32,5, smsd: Moved file /var/spool/sms/outgoing/1.sms to /var/spool/sms/checked
2013-02-28 16:09:53,2, smsd: Smsd mainprocess is awaiting the termination of all modem handlers. PID: 1605.
2013-02-28 16:10:08,7, GSM1: Command is sent, waiting for the answer
2013-02-28 16:10:12,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2013-02-28 16:10:12,7, GSM1: <-
2013-02-28 16:10:12,6, GSM1: Moved file /var/spool/sms/checked/test.sms to /var/spool/sms/failed/test.sms
2013-02-28 16:10:13,2, GSM1: Modem handler 0 terminated. PID: 1606, was started 13-02-28 16:05:31.
2013-02-28 16:10:48,2, smsd: Smsd v3.1.11 started.
2013-02-28 16:10:48,2, smsd: Running as smsd:dialout.
2013-02-28 16:10:48,7, smsd: Running startup_check (shell): /tmp/smsd_script.JOAY97 /tmp/smsd_data.vNP31D
2013-02-28 16:10:48,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2013-02-28 16:10:48,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2013-02-28 16:10:48,5, smsd: Outgoing file checker has started. PID: 1077.
2013-02-28 16:10:49,5, GSM1: Modem handler 0 has started. PID: 1078.
2013-02-28 16:10:49,5, GSM1: Using check_memory_method 1: CPMS is used.
2013-02-28 16:10:49,6, GSM1: I have to send 1 short message for /var/spool/sms/checked/2.sms
2013-02-28 16:10:49,6, GSM1: Sending SMS from to 18057045518
2013-02-28 16:10:49,6, GSM1: Checking if modem is ready
2013-02-28 16:10:49,7, GSM1: -> AT
2013-02-28 16:11:49,5, smsd: Moved file /var/spool/sms/outgoing/something.sms to /var/spool/sms/checked
2013-02-28 16:12:54,2, smsd: Smsd mainprocess is awaiting the termination of all modem handlers. PID: 1077.
2013-02-28 16:13:51,7, GSM1: Command is sent, waiting for the answer
2013-02-28 16:13:55,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2013-02-28 16:13:55,7, GSM1: <-
2013-02-28 16:13:55,6, GSM1: Moved file /var/spool/sms/checked/2.sms to /var/spool/sms/failed/2.sms
2013-02-28 16:13:56,2, GSM1: Modem handler 0 terminated. PID: 1078, was started 13-02-28 16:10:48.
2013-02-28 16:15:23,2, smsd: Smsd v3.1.11 started.
2013-02-28 16:15:23,2, smsd: Running as smsd:dialout.
2013-02-28 16:15:23,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).

Member
Registered:
Mar 2013
Location: San Luis Obispo CA, United States of America
Topic owner
Also I should say that the modem is GSM.

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
You could try some other sofware, like Minicom, for testing the communication. Adjust the baudrate, and if the modem provices more than one port, try with other ports.

Member
Registered:
Mar 2013
Location: San Luis Obispo CA, United States of America
Topic owner
So, I managed to determine that I had the wrong port selected (Thanks to minicom). I can get an AT (OK) and AT+CREG? (OK). I am, however, getting "modem not ready to accept commands". I've done some googling, and can't figure out where the problem could be. Is the modem's driver not installed properly? If so, why am I getting successful AT and AT+CREG? responses? Can you point me in the right direction?

Member
Registered:
Jun 2013
Location: Palmas/Tocantins, Brazil
Hello guys. I'm having similar problem.
I have smstools 3.1.15 (compiled from sources)
at a Linux Mint 14 with a kernel 3.5.0-17 x64
I have a 3g ZTE MF190 modem connected via USB.

I connect the modem, I enable the Mobile Broadband connection from my graphic environment (LXDE) and I wait
the green light of the modem be turned on (At graphical environment I see the notification "You are now registered on the home network").

So, using the comand
dmesg | grep ttyUSB
I get different USB ports
at diferent times that I run dmesg.
Sometimes, I get ttyUSB0, ttyUSB1 and ttyUSB2,
other times I get ttyUSB1, ttyUSB2 and ttyUSB3, and so on.

Below is a dmesg command return,
showing the ports ttyUSB0, ttyUSB2 and ttyUSB3:
usb 1-2: >GSM modem (1-port) converter now attached to ttyUSB0
usb 1-2: >GSM modem (1-port) converter now attached to ttyUSB2
usb 1-2: >GSM modem (1-port) converter now attached to ttyUSB3

I'm running smsd with root and I try every USB port listed by dmesg.

Sometimes, some usb ports works, other times I try every port
and nothing works. I try to connect the modem at different USB ports,

I run dmesg again, I try all ports again (restarting smsd) and nothing works.

At smsd.log I get:
GSM1: -> AT
GSM1: Command is sent, waiting for the answer
GSM1: put_command expected (OK)|(ERROR), timeout occurred.

What I don't understand is that, sometimes, only changing the USB port at smsd.conf and restarting smsd, it works.

My smsd.conf is below:

devices = GSM1
logfile = /var/log/smsd.log
group = manoelcampos
loglevel = 7
sent = /var/spool/sms/sent
incoming_utf8 = yes
internal_combine = yes
receive_before_send = yes

[GSM1]
read_timeout = 10
incoming = yes
device = /dev/ttyUSB3

I apreciate any help.

Login and Post Reply

Page:  1

SMSTools3 Community » Help and support Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.