Operating system name and version: Fedora 11
Version of smsd: 3.1.5
Smsd installed from: sources
Name and model of a modem / phone: nokia 6310
Interface: bluetooth

Hello,

Pls help me how to connect this via bluetooth? Is it possible?

Thanks a lot!

It is possible to use smstools3 via bluetooth.

Setting up a bluetooth connection depends on the system, for example what kind of bluetooth manager is used. Your setup should create a virtual serial port for use. I cannot give any detailed instructions for installing bluetooth.

thanks for your response.

What will be put here:

device = /dev/ttyS0

If i want to connect via bluetooth?

Thanks

As said, I cannot give detailed instructions, that's because I do not know how how bluetooth is implemented on Fedora and especially in your system. You could try Google or some Fedora user groups to get better help for this issue.

Basically bluetooth implementation includes some kind of manager software, which is used to create a connection and serial port. The serial port is needed for Smstools3, it does not communicate using other methods. And actually, when a virtual serial port is in use, Smstools3 does not even know what's behind on it. Because of this, remote modems also work.

Hello,

I managed to have a USB to Serial so i can connect the phone on my laptop. I got another question. When i started the smsd, here is the log:

2009-12-11 13:26:51,2, smsd: Smsd v3.1.5 started.
2009-12-11 13:26:51,2, smsd: Running as root:root.
2009-12-11 13:26:51,7, smsd: Running startup_check (shell): /tmp/smsd_script.qDaJnd /tmp/smsd_data.DuINun
2009-12-11 13:26:51,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0
2009-12-11 13:26:51,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2009-12-11 13:26:51,5, 6310: Modem handler 0 has started. PID: 1111.
2009-12-11 13:26:51,5, 6310: Using check_memory_method 1: CPMS is used.
2009-12-11 13:26:51,6, 6310: Checking device for incoming SMS
2009-12-11 13:26:51,6, 6310: Checking if modem is ready
2009-12-11 13:26:51,5, smsd: Outgoing file checker has started. PID: 1110.
2009-12-11 13:26:55,3, 6310: Modem is not clear to send
2009-12-11 13:27:05,7, 6310: -> 
2009-12-11 13:27:05,3, 6310: Could not send string, cause: Input/output error
2009-12-11 13:27:15,7, 6310: -> AT
2009-12-11 13:27:15,3, 6310: Could not send string, cause: Input/output error
2009-12-11 13:27:25,7, 6310: -> 
2009-12-11 13:27:25,3, 6310: Could not send string, cause: Input/output error
2009-12-11 13:27:35,7, 6310: -> AT
2009-12-11 13:27:35,3, 6310: Could not send string, cause: Input/output error


And here is my smsd.conf

devices = 6310
logfile = /var/log/smsd.log
loglevel = 7

[6310]
device = /dev/ttyS0
#device = /dev/rfcomm1
#device = 00:02:EE:16:36:4A
incoming = yes
init = ATE1+CMEE=1
pre_init = no
baudrate = 9600
send_delay = 0
loglevel = notice


Could you please help me what is wrong?

Thanks again in advance.

You are running Windows on your laptop, right?

Assuming that the adapter is assigned to COM1, which still should be verified, try a different baudrate like 19200 or 115200.

Operating system name and version: Fedora 11
Version of smsd: 3.1.5
Smsd installed from: sources
Name and model of a modem / phone: nokia 6310

Okay, I was assuming that you was testing smsd on the another machine...

Plug in your adapter and after couple of seconds use dmesg to see what name of device is in use. For example:

# dmesg
[4846007.456030] usb 2-2: new full speed USB device using uhci_hcd and address 6
[4846007.614449] usb 2-2: configuration #1 chosen from 1 choice
[4846007.621840] pl2303 2-2:1.0: pl2303 converter detected
[4846007.634111] usb 2-2: pl2303 converter now attached to ttyUSB1

dmesg result:

usb 6-1: new full speed USB device using uhci_hcd and address 6
usb 6-1: New USB device found, idVendor=1a86, idProduct=7523
usb 6-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
usb 6-1: Product: USB2.0-Ser!
usb 6-1: configuration #1 chosen from 1 choice
ch341 6-1:1.0: ch341-uart converter detected
usb 6-1: ch341-uart converter now attached to ttyUSB0


Thanks for your help!

Good to see that your system is working now.

Even if the connection with bluetooth is possible to use, it's more complicated to set it up than serial or USB connection. Also it's not very reliable, as the connection can be broken and so on.

With your current device = /dev/ttyUSB0 you could try to use faster baudrate than 9600. This setting defaults to 115200, because many interfaces and devices work better with this speed.

Hi,

I got this new weird error:

Smsd v3.1.5 started.
2009-12-15 09:36:00,2, smsd: Running as root:root.
2009-12-15 09:36:00,7, smsd: Running startup_check (shell): /tmp/smsd_script.cPtVkN /tmp/smsd_data.2C3gJY
2009-12-15 09:36:00,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0
2009-12-15 09:36:00,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2009-12-15 09:36:00,5, 6310: Modem handler 0 has started. PID: 32089.
2009-12-15 09:36:00,5, smsd: Outgoing file checker has started. PID: 32088.
2009-12-15 09:36:00,5, 6310: Using check_memory_method 1: CPMS is used.
2009-12-15 09:36:00,6, 6310: Checking device for incoming SMS
2009-12-15 09:36:00,6, 6310: Checking if modem is ready
2009-12-15 09:36:03,3, 6310: Modem is not clear to send
2009-12-15 09:36:17,3, 6310: Modem is not clear to send
2009-12-15 09:36:30,3, 6310: Modem is not clear to send



What could possibly go wrong this time?

Pls dont give up on me.

It looks like a problem with handshaking.

In the modem settings, define rtscts = no. This may help, but it's not a good choice with higher baudrates.

Hi,

Now i changed my setting with "rtscts = no"

Here is now the new errors:

File mode creation mask: 022 (0644, rw-r--r--).
2009-12-16 09:57:47,5, 6310: Modem handler 0 has started. PID: 31036.
2009-12-16 09:57:47,5, smsd: Outgoing file checker has started. PID: 31034.
2009-12-16 09:57:47,5, 6310: Using check_memory_method 1: CPMS is used.
2009-12-16 09:57:47,6, 6310: Checking device for incoming SMS
2009-12-16 09:57:47,6, 6310: Checking if modem is ready
2009-12-16 09:57:47,7, 6310: -> AT
2009-12-16 09:57:47,7, 6310: Command is sent, waiting for the answer
2009-12-16 09:57:52,7, 6310: put_command expected (OK)|(ERROR), timeout occurred. 1.
2009-12-16 09:57:52,7, 6310: <- AT
2009-12-16 09:57:52,7, 6310: -> 
2009-12-16 09:57:52,7, 6310: Command is sent, waiting for the answer
2009-12-16 09:57:57,7, 6310: put_command expected (OK)|(ERROR), timeout occurred. 2.
2009-12-16 09:57:57,7, 6310: <-
2009-12-16 09:57:58,7, 6310: -> AT
2009-12-16 09:57:58,7, 6310: Command is sent, waiting for the answer
2009-12-16 09:58:03,7, 6310: put_command expected (OK)|(ERROR), timeout occurred. 3.
2009-12-16 09:58:03,7, 6310: <- AT
2009-12-16 09:58:03,7, 6310: -> 
2009-12-16 09:58:03,7, 6310: Command is sent, waiting for the answer
2009-12-16 09:58:08,7, 6310: put_command expected (OK)|(ERROR), timeout occurred. 4.
2009-12-16 09:58:08,7, 6310: <-
2009-12-16 09:58:08,7, 6310: -> AT
2009-12-16 09:58:08,7, 6310: Command is sent, waiting for the answer
2009-12-16 09:58:13,7, 6310: put_command expected (OK)|(ERROR), timeout occurred. 5.
2009-12-16 09:58:13,7, 6310: <- AT
2009-12-16 09:58:13,7, 6310: -> 
2009-12-16 09:58:13,7, 6310: Command is sent, waiting for the answer
2009-12-16 09:58:19,7, 6310: put_command expected (OK)|(ERROR), timeout occurred. 6.
2009-12-16 09:58:19,7, 6310: <-
2009-12-16 09:58:19,7, 6310: -> AT
2009-12-16 09:58:19,7, 6310: Command is sent, waiting for the answer

Have you tried different baudrates?

Also, have you ensured that the port still is /dev/ttyUSB0? What says ls -l /dev/ttyUSB* ?

You could try to communicate with a modem using some terminal program, like Minicom.

 I just checked that Nokia 6310 should work with Smstools3. It's also reported that 6310i is working with DLR-3P cable. 

As you have had troubles with interfaces on Fedora 11, can you try with a Windows machine which has a traditional serial port? Hyperterminal and some AT commands (AT+CPMS?, AT+CREG?, AT+CGSN) can be used to verify that a cable is not faulty.

Also the USB-Serial adapter can be bad or broken, how have you ensured that it's working correctly?

With DLR-3P the baudrate 115200 should be good and handshaking should be used.

If you cannot access a different machine, you could try to install Gnokii and check how your system works with it.

Hi,

I made it to connect via Bluetooth(before was USB to serial cable), but the weird thing is , it has the same error messages with the serial cable connection:

2009-12-28 22:24:53,2, smsd: Smsd v3.1.5 started.
2009-12-28 22:24:53,2, smsd: Running as root:root.
2009-12-28 22:24:53,7, smsd: Running startup_check (shell): /tmp/smsd_script.2TpYQO /tmp/smsd_data.ouwqUE
2009-12-28 22:24:53,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0
2009-12-28 22:24:53,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2009-12-28 22:24:53,5, 6310: Modem handler 0 has started. PID: 1420.
2009-12-28 22:24:53,5, 6310: Using check_memory_method 1: CPMS is used.
2009-12-28 22:24:53,6, 6310: Checking device for incoming SMS
2009-12-28 22:24:53,6, 6310: Checking if modem is ready
2009-12-28 22:24:53,5, smsd: Outgoing file checker has started. PID: 1418.
2009-12-28 22:24:53,7, 6310: -> AT
2009-12-28 22:24:53,7, 6310: Command is sent, waiting for the answer
2009-12-28 22:24:58,7, 6310: put_command expected (OK)|(ERROR), timeout occurred. 1.
2009-12-28 22:24:58,7, 6310: <-
2009-12-28 22:24:59,7, 6310: -> 
2009-12-28 22:24:59,7, 6310: Command is sent, waiting for the answer
2009-12-28 22:25:04,7, 6310: put_command expected (OK)|(ERROR), timeout occurred. 2.
2009-12-28 22:25:04,7, 6310: <-
2009-12-28 22:25:04,7, 6310: -> AT
2009-12-28 22:25:04,7, 6310: Command is sent, waiting for the answer
2009-12-28 22:25:09,7, 6310: put_command expected (OK)|(ERROR), timeout occurred. 3.
2009-12-28 22:25:09,7, 6310: <-
2009-12-28 22:25:09,7, 6310: -> 
2009-12-28 22:25:09,7, 6310: Command is sent, waiting for the answer
2009-12-28 22:25:14,7, 6310: put_command expected (OK)|(ERROR), timeout occurred. 4.
2009-12-28 22:25:14,7, 6310: <-
2009-12-28 22:25:14,7, 6310: -> AT
2009-12-28 22:25:14,7, 6310: Command is sent, waiting for the answer

keke wrote

 I just checked that Nokia 6310 should work with Smstools3. It's also reported that 6310i is working with DLR-3P cable. 

Have you noticed this? Probably your phone is broken. At least it looks like broken because it does not talk to you.I think that 6310i is close enough to 6310, and therefore is a working device, it not broken.

keke wrote

As you have had troubles with interfaces on Fedora 11, can you try with a Windows machine which has a traditional serial port? Hyperterminal and some AT commands (AT+CPMS?, AT+CREG?, AT+CGSN) can be used to verify that a cable is not faulty.

Can you do this test?

keke wrote

If you cannot access a different machine, you could try to install Gnokii and check how your system works with it.

Is this checking possible?

keke wrote

You could try to communicate with a modem using some terminal program, like Minicom.

Could you? I think that Fedora has some terminal program available, like Minicom.

Sorry, I'm repeating myself, but just because you have not answered those questions...

zeratool wrote

I made it to connect via Bluetooth

Forget the Bluetooth. It is a working connection, but not recommended. And I cannot support it because setting it up is a system depended issue.

Please consider to buy a real modem, for example some device based on Wavecom chip with USB connection. Plug it in, use dmesg to see what port should be used, and start to send and receive SMS ...