From: Charles-Edouard Ruault <ce@ruault.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Nokia 6680 services....
Date: Thu, 06 Oct 2005 15:40:22 +0200 [thread overview]
Message-ID: <43452946.6060603@ruault.com> (raw)
In-Reply-To: <1128593198.5492.28.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2377 bytes --]
Marcel Holtmann wrote:
>Hi Charles,
>
>
>
>>Here you go !
>>
>>
>
>this is weird. We ask for the FTP record handle only. The handle is not
>important. We need the channel number:
>
>< ACL data: handle 46 flags 0x02 dlen 22
> L2CAP(d): cid 0x0040 len 18 [psm 1]
> SDP SSA Req: tid 0x0 len 0xd
> pat uuid-16 0x1106 (OBEXObjTrnsf)
> max 65535
> aid(s) 0x0000 (SrvRecHndl)
> cont 00
>
>
>>ACL data: handle 46 flags 0x02 dlen 24
>>
>>
> L2CAP(d): cid 0x0040 len 20 [psm 1]
> SDP SSA Rsp: tid 0x0 len 0xf
> count 12
> record #0
> aid 0x0000 (SrvRecHndl)
> uint 0x10005
> cont 00
>
>If you use obexftp then this is a bug. However this is not the big
>problem. The problem is the FTP service itself. We get a service
>unavailable response:
>
>< ACL data: handle 46 flags 0x02 dlen 36
> L2CAP(d): cid 0x0041 len 32 [psm 3]
> RFCOMM(d): UIH: cr 1 dlci 20 pf 0 ilen 28 fcs 0x31
> OBEX: Get cmd(f): len 28
> Type (0x42) = Sequence length 22
> 0000: 78 2d 6f 62 65 78 2f 66 6f 6c 64 65 72 2d 6c 69 x-obex/folder-li
> 0010: 73 74 69 6e 67 00 sting.
>
>
>>ACL data: handle 46 flags 0x02 dlen 12
>>
>>
> L2CAP(d): cid 0x0041 len 8 [psm 3]
> RFCOMM(d): UIH: cr 0 dlci 20 pf 1 ilen 3 fcs 0xf7 credits 1
> OBEX: Get rsp(f): status 503 len 3
> Status 503 = Service unavailable
>
>This means another problem. Maybe it is in obexftp or in the phone
>itself. I don't know. Maybe you wanna try btftp from the obex CVS
>repository of BlueZ. Or someone has to send me such a phone for testing.
>
>
Ok i've compiled btftp, it looks better with this software ( see
attached dump file ).
I've been able to connect to the phone and run the following commands:
Connected to 00:12:62:a3:80:a5.
ftp> put Makefile.am
300 bytes sent
ftp> ls
-rw-r--r-- 300 Oct 6 15:25 Makefile.am
ftp> get Makefile.am
300 bytes received
ftp> quit
Disconnected.
Now what's puzzling me is that i don't see the exepected filesystem from
the phone, but that's go nothing to do with bluez :)
So i guess that from the bluez's standpoint, everything seems to be fine
when using btftp.
Thanks a lot for your support !
>Regards
>
>Marcel
>
>
>
>
>
>
--
Charles-Edouard Ruault
GPG key Id E4D2B80C
[-- Attachment #2: btftp.dump --]
[-- Type: application/octet-stream, Size: 7257 bytes --]
prev parent reply other threads:[~2005-10-06 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 8:56 [Bluez-users] Nokia 6680 services Charles-Edouard Ruault
2005-10-03 11:37 ` Marcel Holtmann
2005-10-05 8:56 ` Charles-Edouard Ruault
2005-10-05 11:26 ` Marcel Holtmann
2005-10-05 15:20 ` Charles-Edouard Ruault
2005-10-05 17:52 ` Marcel Holtmann
2005-10-06 8:04 ` Charles-Edouard Ruault
2005-10-06 10:06 ` Marcel Holtmann
2005-10-06 12:55 ` Charles-Edouard Ruault
2005-10-06 13:40 ` Charles-Edouard Ruault [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43452946.6060603@ruault.com \
--to=ce@ruault.com \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).