From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 4 18:17:03 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 00D491065674 for ; Tue, 4 Nov 2008 18:17:03 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by mx1.freebsd.org (Postfix) with ESMTP id 9F0688FC12 for ; Tue, 4 Nov 2008 18:17:02 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id b6so292481ana.13 for ; Tue, 04 Nov 2008 10:17:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=iulsuCIwuxpTyase2yj/3NUo9z85BBa8t/LqtqC5HAI=; b=ITorvHHeFGssNt8DQ4Qd34RFv8jC8YOf26XV5sWrXXF1R86M01MLgMUWByXw4wB8ql yyYQPvekx8v57OjIKMI0vrGEkDWKXhvdy/zEpDAExp6FxtKufCbABoKddAq9qGxebq54 U43hzHlcISCWoFY49/2j4ssv3eYY3QLYjUqzY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=WffxaPysb0fjb3e7IywG/SydpEax7M4CqoIOliAf4rGk4EXXrU0DDaFfR7Y/VGYyUX 8tnpy4a6GlarHbLFFu+vVkENI0tKA5VdDMLousEamCglo9THzeiXn5OKLjukwLdr/57q Qn+1vPt2AbCLvVxlxZxg/CIOEqgg7DgN31WAE= Received: by 10.86.62.3 with SMTP id k3mr15430fga.6.1225822620446; Tue, 04 Nov 2008 10:17:00 -0800 (PST) Received: by 10.86.9.3 with HTTP; Tue, 4 Nov 2008 10:17:00 -0800 (PST) Message-ID: Date: Tue, 4 Nov 2008 11:17:00 -0700 From: "Maksim Yevmenkin" To: "Guido Falsi" In-Reply-To: <1225821264.107584.759.nullmailer@galant.ukfsn.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081104111947.GB62907@megatron.madpilot.net> <1225799105.807983.1164.nullmailer@galant.ukfsn.org> <20081104135107.GA64776@megatron.madpilot.net> <1225821264.107584.759.nullmailer@galant.ukfsn.org> 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 18:17:03 -0000 On 11/4/08, Iain Hibbert wrote: > On Tue, 4 Nov 2008, Guido Falsi wrote: > > > 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...) > > > btw my 6103 also has similar ports on similar channels: > > 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 > Service Name: > "Dial-up networking" > > 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 > Service Name: > "Nokia PC Suite" > > 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 > Service Name: > "COM 1" > > and I see that connecting to DUN gives me an AT command interpreter as > does SP on 3 (COM 1) but connecting to the SP on 15 (Nokia PC Suite) > doesn't. Thats using NetBSD though the program is not much different. > > can you connect to channel 1 (Dialup Networking) with rfcomm_sppd? That > should definitely take AT commands.. > > btw, didn't you say before that gnokii is supposed to be discarding "Nokia > PC Suite" ? (actually, that was why I added the "Service Name" handling, > so I could see what my phone had :) could you please run hcidump and see what is going on after you connect to the "pc suite" service. some (most/simbian-based?) nokia phones have some sort of the callback mechanism, i.e. pc suite connects to the phone service and then immediately disconnects. this somehow tells the phone to initiate connection back to the pc on serial port service. rfcomm_pppd(8) man page has a little notes on that. Iain is right, using dun service is the best bet to get "modem" serial port. thanks, max