From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 4 13:51:08 2008 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEEF31065686 for ; Tue, 4 Nov 2008 13:51:08 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (megatron.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id 0BFF18FC22 for ; Tue, 4 Nov 2008 13:51:07 +0000 (UTC) (envelope-from mad@madpilot.net) Received: by megatron.madpilot.net (Postfix, from userid 1000) id 161CB130C39; Tue, 4 Nov 2008 14:51:07 +0100 (CET) Date: Tue, 4 Nov 2008 14:51:07 +0100 From: Guido Falsi To: Iain Hibbert Message-ID: <20081104135107.GA64776@megatron.madpilot.net> References: <20081104111947.GB62907@megatron.madpilot.net> <1225799105.807983.1164.nullmailer@galant.ukfsn.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline In-Reply-To: <1225799105.807983.1164.nullmailer@galant.ukfsn.org> X-Operating-System: FreeBSD 7.1-PRERELEASE User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-bluetooth@freebsd.org Subject: Re: RFComm behaviour with nokia mobiles X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2008 13:51:08 -0000 --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Nov 04, 2008 at 11:45:05AM +0000, Iain Hibbert wrote: > On Tue, 4 Nov 2008, Guido Falsi wrote: > > > I completed the gnokii adaption to talk to freebsd sdp and it tries > > to connwect to rf channel 15 on both phnes, the same rfcomm_sppd > > tries. It loooks like the correct one in fact, but even after > > associating the phone with hcsecd I can't really connect. > > can you show what the output of sdpcontrol is when examining this service? > > (try search for protocol 0x0003 should give all RFCOMM channels) I'm attaching the output from the 6233. The problem is not finding the channel, but that the only channel which looks correct is not acting the way it should(ie. accept at commands...) > > IIRC if you are connecting to a serial port service then it is not always > the case that there will be an AT command interpreter at the other end.. Sure, but I thought it standard to have at least una port accepting at commands. Also because it's the only standard interface to talk to mobiles from PCs (Nokia PC suite and other proprietary software not being standard IMHO). > > also, the patch below adds support to print out the primary language > ServiceName to the port of sdpcontrol I made for NetBSD. It might not > apply cleanly to original sdpcontrol but should not be too difficult to > adapt and it seems quite useful.. > > I haven't committed it here because its not really complete as the string > that is produced is not guaranteed to be ASCII (the spec recommends using > UTF-8) but I would have to examine the languagebase settings and do some > iconv magic to get it 100% correct. I've written something simlar to adapt the gnokii sdp functions. The channel choosen is 15 because it looks like an rfcomm modem like port.Perhaps these phones don't have such a port. I'll try with my older sony-ericsson, which I know for sure used to accept at commands via bluetooth. -- Guido Falsi --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sdpcontrol.txt" Record Handle: 0x00010000 Service Class ID List: Dial-Up Networking (0x1103) Generic Networking (0x1201) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 1 Bluetooth Profile Descriptor List: Dial-Up Networking (0x1103) ver. 1.0 Record Handle: 0x00010001 Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 15 Record Handle: 0x00010002 Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 3 Record Handle: 0x00010003 Service Class ID List: Handsfree Audio Gateway (0x111f) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 13 Bluetooth Profile Descriptor List: Handsfree (0x111e) ver. 1.5 Record Handle: 0x00010004 Service Class ID List: Headset Audio Gateway (0x1112) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 12 Bluetooth Profile Descriptor List: Headset (0x1108) ver. 1.0 Record Handle: 0x0001000b Service Class ID List: OBEX Object Push (0x1105) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 9 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX Object Push (0x1105) ver. 1.0 Record Handle: 0x0001000c Service Class ID List: OBEX File Transfer (0x1106) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 10 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX File Transfer (0x1106) ver. 1.0 Record Handle: 0x0001000e Service Class ID List: 0x00000002-0000-1000-8000-0002ee000002 Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 11 OBEX (0x0008) Record Handle: 0x0001000f Service Class ID List: SIM Access (0x112d) Generic Telephony (0x1204) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 4 Bluetooth Profile Descriptor List: SIM Access (0x112d) ver. 1.1 --+HP7ph2BbKc20aGI--