Help - Search - Members - Calendar
Full Version: Bluetooth Dun Problems
OESF Forums > General Forums > General Support and Discussion > Security and Networking
Grimmy
I finally got my Billionton Bluetooth card working on my SL-5500 with a little help from Merlin ROM (Thanks Merli!) and can now scan for devices... (I installed the pinned Bluez drivers and am following the instructions in the HOWTO).

I have an Orange SPV C500 (on Orange UK) which is based on MS Smartphone 2003SE (Booo!). When Bluetooth is enabled and set to discoverable on the phone, I can successfully pair the devices from the phone, and if I use the Bluetooth Network Applet to create a DUN connection, when I click connect on the Zaurus, the phone pairs, but the Zaurus stays on "initialising modem". I suspect this is because I am using the wrong channel number (default 1).

(Inncidently I dug out my old Nokia 6310i and put my SIM in that just to see if it would work with that, it pairs and dials up fine.)

So the problem with the SPV is that if I use "sdptool browse" it only returns the MAC address of the phone and no other information. (With the Nokia it provides a couple of services, and if I attempt it on the train it comes back with loads of service information from other peoples nokias, sony erricsons etc...)

I know the SPVC500 is supposed to work as a bluetooth modem: There are several reports on forums people have it working with IPAQs running PocketPC and I scanned for services on the phone from Windows XP and it reports Dial Up Networking and Serial Port as being available - of course these are both Microsoft Environments.

So... Now I am stuck:

Is there any other way to find the channel required for the phone?
Is it worth trying each channel number until it works or is it likely not to work with the Zaurus? I know the COM ports the phone uses if that is any help?
speculatrix
QUOTE(Grimmy @ Jun 16 2005, 04:49 PM)
Is there any other way to find the channel required for the phone? 
Is it worth trying each channel number until it works or is it likely not to work with the Zaurus?  I know the COM ports the phone uses if that is any help?
*


thoughts...

"hcitool scan" to get the MAC addr of the phone.

"sdptool browse xx:xx:xx:xx:xx:xx" to verify pairing.

"rfcomm bind 0 xx:xx:xx:xx:xx:xx" to set up the device /dev/rfcomm0

"minicom -s", set the serial device to /dev/rfcomm0, comms params are 115200 baud, 8, n 1. Save/exit set up.

Your phone should then tell you the Z is connecting and ask for confirmation

Type "AT" followed by return and you should get an OK. If you don't

Type "AT+CRC=1" to turn on extended ring messages. Ring the phone and it'll tell you it's a voice, data or fax call.

Here's some more commands to try:
http://www.gsm-modem.de/gsm-modem-faq.html


HTH
Paul
Grimmy
QUOTE(speculatrix @ Jun 17 2005, 09:18 PM)
Your phone should then tell you the Z is connecting and ask for confirmation

Type "AT" followed by return and you should get an OK. If you don't

Type "AT+CRC=1" to turn on extended ring messages. Ring the phone and it'll tell you it's a voice, data or fax call.


Ok I finally got some time to try this. The when I do the minicom command the phone states the Zaurus is trying to connect, but before I have time to respond minicom returns saying file rfcomm0 doesn't exist. I tried to initiate the pairing using the phone and this seemed to work. minicom says "initialising modem" then goes to a screen that says "T102" at the bottom, At this point any key pressed on the Zaurus keypad results in the following appearing at the bottom (in inverted video):

CODE
Online 00:00
    Offline


Note: I also tried this with my Nokia 6310i and it worked as expected. I could issue AT commands fine and get the response back ok.

(Incidently I managed to obtain an Anycom BT card [LSE039] and the results are the same.)

On a forum for the SPV and other smartphones someone suggested that I tried using "sdptool search" and I achieved the following results:-

For Serial
CODE
bash-2.05# sdptool search --bdaddr 11:22:33:44:55:66 SP

Searching for SP on 11:22:33:44:55:66 ...
Service Name: Serial Port COM6
Service RecHandle: 0x10002
Service Class ID List:
 "Serial Port" (0x1101)
Protocol Descriptor List:
 "L2CAP" (0x0100)
 "RFCOMM" (0x0003)
   Channel: 3    


for DUN
CODE
bash-2.05# sdptool search --bdaddr 11:22:33:44:55:66 DUN

Searching for DUN on 11:22:33:44:55:66 ...
Service Name: Dial-up Networking
Service RecHandle: 0x10003
Service Class ID List:
 "Dialup Networking" (0x1103)
Protocol Descriptor List:
 "L2CAP" (0x0100)
 "RFCOMM" (0x0003)
   Channel: 7
Language Base Attr List:
 code_ISO639: 0x656e
 encoding:    0x6a
 base_offset: 0x100
Profile Descriptor List:
 "Dialup Networking" (0x1103)
   Version: 0x0100  


I've tried putting both channels 3 and 7 in the rfcomm.conf file, but both just hang on "initialising modem".

I've read somewhere on these forums about enabling logging, would this help me diagnose the problem? I guess I should also see if I can get the phone to dial from my windows machine using the bluetooth dongle.
stwizard
QUOTE(Grimmy @ Jul 20 2005, 06:10 AM)
QUOTE(speculatrix @ Jun 17 2005, 09:18 PM)
Your phone should then tell you the Z is connecting and ask for confirmation

Type "AT" followed by return and you should get an OK. If you don't

Type "AT+CRC=1" to turn on extended ring messages. Ring the phone and it'll tell you it's a voice, data or fax call.


Ok I finally got some time to try this. The when I do the minicom command the phone states the Zaurus is trying to connect, but before I have time to respond minicom returns saying file rfcomm0 doesn't exist. I tried to initiate the pairing using the phone and this seemed to work. minicom says "initialising modem" then goes to a screen that says "T102" at the bottom, At this point any key pressed on the Zaurus keypad results in the following appearing at the bottom (in inverted video):

CODE
Online 00:00
    Offline


Note: I also tried this with my Nokia 6310i and it worked as expected. I could issue AT commands fine and get the response back ok.

(Incidently I managed to obtain an Anycom BT card [LSE039] and the results are the same.)

On a forum for the SPV and other smartphones someone suggested that I tried using "sdptool search" and I achieved the following results:-

For Serial
CODE
bash-2.05# sdptool search --bdaddr 11:22:33:44:55:66 SP

Searching for SP on 11:22:33:44:55:66 ...
Service Name: Serial Port COM6
Service RecHandle: 0x10002
Service Class ID List:
 "Serial Port" (0x1101)
Protocol Descriptor List:
 "L2CAP" (0x0100)
 "RFCOMM" (0x0003)
   Channel: 3    


for DUN
CODE
bash-2.05# sdptool search --bdaddr 11:22:33:44:55:66 DUN

Searching for DUN on 11:22:33:44:55:66 ...
Service Name: Dial-up Networking
Service RecHandle: 0x10003
Service Class ID List:
 "Dialup Networking" (0x1103)
Protocol Descriptor List:
 "L2CAP" (0x0100)
 "RFCOMM" (0x0003)
   Channel: 7
Language Base Attr List:
 code_ISO639: 0x656e
 encoding:    0x6a
 base_offset: 0x100
Profile Descriptor List:
 "Dialup Networking" (0x1103)
   Version: 0x0100  


I've tried putting both channels 3 and 7 in the rfcomm.conf file, but both just hang on "initialising modem".

I've read somewhere on these forums about enabling logging, would this help me diagnose the problem? I guess I should also see if I can get the phone to dial from my windows machine using the bluetooth dongle.
*



I was able to connect to my phone with the laptop and a BT dongle. that worked fine. I believe it is an initialization string issue or something to do with rfcomm setup on the zaurus. I am using sprint pcs and have enabled dun on the phone and paired it with the zaurus and the laptop. I could use some help setting up the connection from the Zaurus to the phone. I am using Cacko 1.23 full. I have the addons for BT DUN and BT PAN and have a socket BT card that i can scan with and connect with the laptop with PAN (however samba is not browsing the zaurus from windows, pinging works both ways, but that is another story.) I am using a zaurus SL-C1000. Please help.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.