| Keywords: Mode: All keywords (AND) |
|
Wed May 26, 2010 11:24
|
lithium: Thank you very much for the help! :)
|
|
Wed May 26, 2010 09:19
|
lithium: I need only last (big) patch, or a patch from #2 message (small) also is necessary?
If I have correctly understood, in the following version (3.1.9?) there will be all necessary changes and there will be no necessity of patches from this topic?
|
|
Wed May 26, 2010 08:07
|
lithium: It works (even without the first patch), but in log periodically there are records:
2010-05-26 11:58:21,3, GSM1: Serial write: transmitter busy, waiting
2010-05-26 11:58:21,3, GSM1: Serial write: transmitter ready
|
|
Tue May 25, 2010 11:26
|
lithium: I do not know, I use standard minicom from the CentOS. I start it as 'minicom usb0', but simple 'minicom' works too.
Contents minirc.usb0:
pr port/dev/ttyUSB0
pu baudrate 9600
Contents minirc.dfl:
pr port/dev/ttyUSB0
pu baudrate 9600
pu bits 8
pu parity N
pu stopbits 1
|
|
Tue May 25, 2010 10:52
|
|
|
|
Tue May 25, 2010 10:33
|
lithium: I have sent output of 'strace -o strace.log -ff -s 1024 -v smsd -t'
|
|
Tue May 25, 2010 08:46
|
lithium: I made changes in modeminit.c, but nothing has changed
|
|
Mon May 24, 2010 13:32
|
lithium: Operating system name and version: RHEL 5.5
Version of smsd: 3.1.8
Smsd installed from: sources (build with spec-file from smstools-3.1.5-4.fc13.src.rpm)
Name and model of a modem / phone: Huawei E220
Interface: USB
Hi.
I have found that if to plug in the modem in the working computer and to start smsd, all works well, but if send computer to reboot, without unplug the modem, after reboot in the smsd logs there is a message:
2010-05-24 16:52:03,3, GSM1: Modem is not clear to send
And smsd does not work.
However, if before start smsd to run minicom, it (minicom) communicate to the modem and if to quit from minicom (Ctrl+A, X), after that smsd normally communicates with the modem. Also, helps ' rtscts = no '.
I have tried to find solution in Google and search at this forum, but have found nothing.
My config:
devices = GSM1
logfile = /var/log/smsd/smsd.log
stats = /var/log/smsd/smsd_stats
loglevel = 5
smart_logging = yes
delaytime = 3
checked = /var/spool/sms/checked
failed = /var/spool/sms/failed
incoming = /var/spool/sms/incoming
outgoing = /var/spool/sms/outgoing
sent = /var/spool/sms/sent
internal_combine = yes
autosplit = 3
checkhandler = /root/bin/smsd/out-convert.pl
eventhandler = /root/bin/smsd/in-convert.pl
alarmhandler = /root/bin/smsd/alarmhandler.pl
[default]
incoming = yes
[GSM1]
device = /dev/ttyUSB0
memory_start=0
check_memory_method=2
init = AT^CURC=0
#rtscts = no
I have not found how to attach files to message, if it is necessary, I can send strace outputs for working and not working smsd and for minicom. For smsd the main (excuse me, if I was mistaken, I not the programmer) difference which I have found:
Working smsd:
open("/dev/ttyUSB0", O_RDWR|O_NOCTTY|O_NONBLOCK) = 5
[...]
ioctl(5, TIOCMGET, [TIOCM_DTR|TIOCM_RTS|TIOCM_CTS|TIOCM_CAR|TIOCM_DSR]) = 0
Not working:
open("/dev/ttyUSB0", O_RDWR|O_NOCTTY|O_NONBLOCK) = 5
[...]
ioctl(5, TIOCMGET, [TIOCM_DTR|TIOCM_RTS]) = 0
nanosleep({0, 100000000}, NULL) = 0
(ioctl and nanosleep repeats some times)
[...]
write(3, "2010-05-24 14:58:04,3, GSM1: Modem is not clear to send\n", 56) = 56
Can you help me, it is possible to solve this problem without using ' rtscts = no'?
|
