Bluetooth pairing phones

[r31griffo]

G'day everyone,

I'm trying to connect my Nokia N95 to my Debian Lenny computer through a USB Bluetooth dongle. The Bluetooth appears to be working fine as it can see itself and all devices within its range, the problem is that I cannot connect to my phone (or others that I've tried).

The bluetooth adaptor appears to work fine:

workshop:/# hciconfig              
hci0:	Type: USB
	BD Address: 00:10:60:56:0D:FF ACL MTU: 310:10 SC0 MTU: 64:8
	UP RUNNING PSCAN ISCAN
	RX bytes:3904 acl:0 sco:0 events:184 errors:0
	TX bytes:745 acl:0 sco:0 commands:46 errors:0


workshop:/# hcitool scan
Scanning ...
	00:1D:E9:F4:A4:FF	Griffo

l2ping -f 00:1D:E9:F4:A4:FF
0 bytes from 00:1D:E9:F4:A4:FF id 0 time 7.66ms
0 bytes from 00:1D:E9:F4:A4:FF id 1 time 30.49ms
0 bytes from 00:1D:E9:F4:A4:FF id 2 time 26.50ms
0 bytes from 00:1D:E9:F4:A4:FF id 3 time 26.61ms
0 bytes from 00:1D:E9:F4:A4:FF id 4 time 24.57ms

When I try and connect with a device I get the following error:

hcitool cc auth 00:1D:E9:F4:A4:FF
Can't create connection: Input/output error

I do not want to have to program each device into rfcomm.conf, the end result I would like is for every new device that enters the reception area to automatically recieve a pairing notification and then send an SMS/MMS/file/text/etc.

Cheers,

Griffo

[r31griffo]

I've decided to try a different tact, my goal was to send a file when my phone comes into range, I believe obexftp should do the trick, however I get the following response when I try and use it:

workshop:/# obexftp -b 00:1D:E9:F4:A4:FF -p ./test.txt
Browsing 00:1D:E9:F4:A4:FF
Channel: 11
Connecting...failed: connect
Still trying to connect
Connecting...failed: connect
Still trying to connect
Connecting...failed: connect
Still trying to connect

My phone recieves a notification that Debian is trying to connect (I am prompted for a passkey, I've tried 1234 and 0000 but I've had no luck). Does anyone know what to look at next for this?

Thanks in advance for any advice you might have.

Griffo

[unlimitedscolobb]

obexftp manages to connect to my phone, although it fails to send files with a very informative error code 68, while in your case it cannot even connect. You might try what I suggest in the following paragraphs; it really might work.

I am currently using obexfs to mount my phone (Nokia 6120c) and navigate it as a regular filesystem. The command looks like this:

# obexfs -b <device> <mount-point>

For me it has the following drawbacks, but that might be me:

1. I haven't figured a way to make <mount-point> accessible to a normal user (but I've never tried hard).
2. Mysteriously, the mv command doesn't work in the mounted filesystem. Instead I have to copy and delete the old version.

[r31griffo]

I found a solution before I saw your post, but I will keep it in mind if I ever want 2 way traffic...I'm now using ussp-push. No pairing is necessary, it asks if you wish to receive a message from: (setting in /etc/bluetooth/hcid.conf)

syntax:

ussp-push macaddress@channelnumber localfilename remotefilename

there is no need to use the channel number, if it is left blank it will discover it using hcitool. I use it with this command:

ussp-push 00:1D:E9:F4:A4:FF@ schedule.txt schedule.txt

I will eventually setup Bluemon so that it sends me this file when I come into the reception area.