|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. Please login or register. |
Sun May 19, 2024 22:25 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Thu Sep 03, 2009 18:24
|
shir0:
Yes, the port looks correct.
Probably the cable is broken, or it needs some special driver. Can you test this cable on Windows?
Now that you mention it, there was a drivers cd included. I've got windows on my lappy, perhaps I'll try it tomorrow. I doubt the cable's broken since its brand new, on the other hand, it did require some force to connect it to the phone. Probably the worst connector I've ever seen :mrgreen:
|
|
Tue Sep 01, 2009 19:01
|
shir0: How did you verify that it's working completely? Using some terminal program like minicom? Did you get the OK response for AT command?
I thought that the line in smsd.log with the hex character was a reply from the phone (though not interpreted correctly). But now that you told me it was a "ctrl-z" sent from smsd I guess it isn't working after all.
Another thing that i thought was a good indication was that with rtscts = yes I got:
2009-09-01 20:39:59,6, GSM1: Checking if modem is ready
2009-09-01 20:40:02,3, GSM1: Modem is not clear to send
And with rtscts = no I got:2009-09-01 20:42:30,6, GSM1: Checking if modem is ready
2009-09-01 20:42:30,7, GSM1: -> AT
2009-09-01 20:42:30,7, GSM1: Command is sent, waiting for the answer
And therefore I assumed that the connection was working.
But all my assumptions seems to be based on a misunderstanding since i thought the "GSM1: -> AT" parts were replies from the phone. :oops: I just read about wvdialconf briefly and when I ran it I got Scanning your serial ports for a modem.
WvModem<*1>: Cannot set information for serial port.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
WvModem<*1>: Cannot set information for serial port.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S2 S3
WvModem<*1>: Cannot get information for serial port.
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
According to dmesg the phone is suppose to be connected on ttyUSB0. From the looks of it I guess its the cable right? Maby the serial cable might do the trick? :mrgreen:
|
|
Tue Sep 01, 2009 16:26
|
shir0: Hi all!
I've been trying to setup an sms server for quite a while now without success :|
My first guess was that I couldn't use a usb cable to connect my phone (nokia 35101) but after some configuring that part seems to be working. So, my second guess was that the baudrate could be the error, I've tried 9600, 19200 and a few more with no success.
Now I have no idea of what to try. Here's my smsd log:
2009-09-01 18:02:41,2, smsd: Smsd v3.1.5 started.
2009-09-01 18:02:41,2, smsd: Running as root:root.
2009-09-01 18:02:41,7, smsd: Running startup_check (shell): /tmp/smsd_script.u2D7QR /tmp/smsd_data.Jofwt3
2009-09-01 18:02:41,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0
2009-09-01 18:02:41,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2009-09-01 18:02:41,5, smsd: Outgoing file checker has started. PID: 28409.
2009-09-01 18:02:41,5, GSM1: Modem handler 0 has started. PID: 28410.
2009-09-01 18:02:41,5, GSM1: Using check_memory_method 1: CPMS is used.
2009-09-01 18:02:41,6, GSM1: Checking device for incoming SMS
2009-09-01 18:02:41,6, GSM1: Checking if modem is ready
2009-09-01 18:02:41,7, GSM1: -> AT
2009-09-01 18:02:41,7, GSM1: Command is sent, waiting for the answer
2009-09-01 18:02:46,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2009-09-01 18:02:46,7, GSM1: <-
2009-09-01 18:02:46,7, GSM1: -> .
2009-09-01 18:02:46,7, GSM1: Command is sent, waiting for the answer
2009-09-01 18:02:50,2, smsd: Smsd mainprocess is awaiting the termination of all modem handlers. PID: 28409.
2009-09-01 18:02:51,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 2.
2009-09-01 18:02:51,7, GSM1: <-
2009-09-01 18:02:51,2, GSM1: Modem handler 0 terminated. PID: 28410, was started 09-09-01 18:02:41.
2009-09-01 18:02:51,2, smsd: Smsd mainprocess terminated. PID 28409, was started 09-09-01 18:02:41.
On the line "2009-09-01 18:02:46,7, GSM1: ->" there is a strange symbol, a box with two zeros and a "1" and an "A" so I'm guessing the smsd has a problem interpreting the messages from the mobile, right?
And my smsd conf:devices = GSM1
outgoing = /var/spool/sms/outgoing
checked = /var/spool/sms/checked
failed = /var/spool/sms/failed
incoming = /var/spool/sms/incoming
report = /var/spool/sms/report
logfile = /var/log/smsd.log
loglevel = 7
alarmlevel = 4
delaytime = 10
errorsleeptime = 10
blocktime = 3600
receive_before_send = no
decode_unicode_text = yes
incoming_utf8 = yes
receive_before_send = yes
store_sent_pdu = 3
executable_check = yes
hangup_incoming_call = yes
log_charconv = yes
[queues]
OTHER = /var/spool/sms/OTHER
[provider]
OTHER = 0,1,2,3,4,5,6,7,8,9
[GSM1]
device = /dev/ttyUSB0
incoming = yes
queues = OTHER
mode = new
baudrate = 9600
send_delay = -1
rtscts = no
cs_convert = no
report = no
memory_start = 0 Thanks in advance! SHiR0
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
