Operating system name and version: Fedora 8
Version of smsd: 3.1.6
Smsd installed from: sources
Name and model of a modem / phone: MOXA G2110 oncell
Interface: serial


hello
my sms server was working very well for many days but now it does not I don't no what happened to it.
this is its log file:


010-05-05 11:54:08,7, GSM1: Command is sent, waiting for the answer
2010-05-05 11:54:09,7, GSM1: <- OK
2010-05-05 11:54:09,7, GSM1: -> AT+CPBR=1,10
2010-05-05 11:54:10,7, GSM1: Command is sent, waiting for the answer
2010-05-05 11:54:10,7, GSM1: <- OK
2010-05-05 11:54:10,6, GSM1: No phonecall entries
2010-05-05 11:54:20,6, GSM1: Reading phonecall entries
2010-05-05 11:54:20,7, GSM1: -> AT+CPBS="MC"
2010-05-05 11:54:22,7, GSM1: Command is sent, waiting for the answer
2010-05-05 11:54:22,7, GSM1: <- OK
2010-05-05 11:54:22,7, GSM1: -> AT+CPBR=1,10
2010-05-05 11:54:23,7, GSM1: Command is sent, waiting for the answer
2010-05-05 11:54:24,7, GSM1: <- OK
2010-05-05 11:54:24,6, GSM1: No phonecall entries
2010-05-05 11:54:34,6, GSM1: Reading phonecall entries
2010-05-05 11:54:34,7, GSM1: -> AT+CPBS="MC"
2010-05-05 11:54:35,7, GSM1: Command is sent, waiting for the answer
2010-05-05 11:54:40,7, GSM1: put_command expected (ERROR)|(OK), timeout occurred. 1.
2010-05-05 11:54:40,7, GSM1: <-
2010-05-05 11:54:40,7, GSM1: -> AT+CPBR=1,10
2010-05-05 11:54:42,7, GSM1: Command is sent, waiting for the answer
2010-05-05 11:54:47,7, GSM1: put_command expected (ERROR)|(OK), timeout occurred. 2.
2010-05-05 11:54:47,7, GSM1: <-
2010-05-05 11:54:47,6, GSM1: No phonecall entries
2010-05-05 11:54:57,6, GSM1: Reading phonecall entries
2010-05-05 11:54:57,7, GSM1: -> AT+CPBS="MC"
2010-05-05 11:54:58,7, GSM1: Command is sent, waiting for the answer
2010-05-05 11:55:03,7, GSM1: put_command expected (ERROR)|(OK), timeout occurred. 3.
2010-05-05 11:55:03,7, GSM1: <-
2010-05-05 11:55:03,7, GSM1: -> AT+CPBR=1,10
2010-05-05 11:55:05,7, GSM1: Command is sent, waiting for the answer
2010-05-05 11:55:10,7, GSM1: put_command expected (ERROR)|(OK), timeout occurred. 4.
2010-05-05 11:55:10,7, GSM1: <-
.
.
.
.
.
.
2010-05-05 14:51:43,7, GSM1: put_command expected (ERROR)|(OK), timeout occurred. 938.
2010-05-05 14:51:43,7, GSM1: <-
2010-05-05 14:51:43,6, GSM1: No phonecall entries
2010-05-05 14:51:53,6, GSM1: Reading phonecall entries
2010-05-05 14:51:53,7, GSM1: -> AT+CPBS="MC"
2010-05-05 14:51:54,7, GSM1: Command is sent, waiting for the answer
2010-05-05 14:51:59,7, GSM1: put_command expected (ERROR)|(OK), timeout occurred. 939.
2010-05-05 14:51:59,7, GSM1: <-
2010-05-05 14:51:59,7, GSM1: -> AT+CPBR=1,10
2010-05-05 14:52:01,7, GSM1: Command is sent, waiting for the answer
2010-05-05 14:52:06,7, GSM1: put_command expected (ERROR)|(OK), timeout occurred. 940.

and this is my config file:



devices = GSM1
outgoing = /var/spool/sms/outgoing
incoming = /var/spool/sms/incoming
sent = /var/spool/sms/sent
logfile = /var/log/smsd.log
loglevel = 8
failed = /var/spool/sms/failed
voicecall_hangup_ath = yes
keep_filename = yes



[GSM1]
device = /dev/ttyS0
incoming = no
baudrate = 115200
rtscts = no
send_delay = 100
phonecalls = yes


would you please tell what happened to it?
and I have to say when I restart it it start working very well again.

golden_boy615 wrote

would you please tell what happened to it?

Your device stopped the answering.

What is your device, name and model of a modem / phone?

It may also be useful to know what OS is used, operating system name and version.

golden_boy615 wrote

and I have to say when I restart it it start working very well again.

Do you restart the phone / modem? Or restart smsd without restarting the modem?

If you just restart the smsd, you could try if a modem setting keep_open = no helps.

my OS: Fedora 8
Linux localhost.localdomain 2.6.23.1-42.fc8 #1 SMP Tue Oct 30 13:55:12 EDT 2007 i686 athlon i386 GNU/Linux
modem:
MOXA G2110 oncell
and I restarted smsd:
/etc/init.d/sms3 restart

Thank's for the information, I upgraded your first post in this topic.

Your system has been up and running well about two weeks, but this problem has not occurred before than today. I cannot see the reason why modem stops answering. Perhaps this problem has something to do with a driver of the serial interface. Have you recently installed something which may use the same port simultaneously when smsd is running? For example some another software may change some parameters of a port, and therefore communication stops working. When smsd is restarted, those parameters are set to back and smsd will continue working.

If there is ttyS1 available in your system, you could move modem to that port.

Have you tested if keep_open = no helped? I assume that it may help, but it does not fix the reason why ttyS0 becomes silent.