[openobex-users] BUG :obexftp and M341i just connect and put files but did'nt get and list

[surfzoid s. <sur...@ho...>]

A way for the Obexftp Develloper :
In article news:BAY...@ph...l, surfzoid
surfzoid wrote:
>Very good, there no more crash anyway, but unluky my big problem is
>alaws here and i know it's not a irda problem, the folder listing
>dont work because the phone answer with a unknow response, can you
>say me wath is the unknox response ?

Good, we're getting there... :-)

>From now on when running irdadump you can lose the "-p", and thus get
the two types of irdadump output combined -- I'll simulate that below by
hand.  In fact "-x" may be better than "-b" as that'll include a text
conversion too, and thus the strings eg "/IMAGES" will be obvious in the
data. So: "irdadump -x -s
64".


Anyway...

>16:07:07.885999 i:cmd  > ca=c8 pf=1 nr=3 ns=4 LM slsap=2c dlsap=05 TTP
>credits=0
>        OBEX CONNECT len=26 (31)
>        c9 78 05 2e 00 80 00 1a 10 00 04 00 46 00 13 f9
>        ec 7b c4 95 3c 11 d2 98 4e 52 54 00 dc 9e 09
An OBEX connect to Target=Folder-Browsing

>16:07:07.909970 i:rsp  < ca=c8 pf=1 nr=5 ns=3 LM slsap=05 dlsap=2c TTP
>credits=1
>        OBEX SUCCESS (36)
>        c8 b6 2e 05 01 a0 00 1f 10 00 03 f7 4a 00 13 f9
>        ec 7b c4 95 3c 11 d2 98 4e 52 54 00 dc 9e 09 cb
>        00 00 00 00
Success, from service=Folder-Browsing.  It includes a Connection ID
header, indicating: "Please use Connection ID zero (0) in every request
packet from now on."

>16:07:08.729866 i:cmd  > ca=c8 pf=1 nr=4 ns=5 LM slsap=2c dlsap=05 TTP
>credits=1
>        OBEX GET final=1 len=47 Type="x-obex/folder-listing"
>Name="/IMAGES" (52)
>        c9 9a 05 2e 01 83 00 2f 42 00 19 78 2d 6f 62 65
>        78 2f 66 6f 6c 64 65 72 2d 6c 69 73 74 69 6e 67
>        00 01 00 13 00 2f 00 49 00 4d 00 41 00 47 00 45
>        00 53 00 00
So this may well be the real problem we're seeing now.

There's *no* Connection ID in the packet.  That's a bug.  As above, it
must include ConnId=0 as its first header.

>16:07:08.773827 i:rsp  < ca=c8 pf=1 nr=6 ns=5 LM slsap=05 dlsap=2c TTP
>credits=0
>        OBEX Unknown response 51 (8)
>        c8 da 2e 05 00 d1 00 03
Beause the specified ConnId wasn't included in the request, the GET
request went to the default 'Inbox' service, which only supports PUT, so
response code=0xD1=(0x51)=NotImplemented is correct!


>16:07:08.793853 i:cmd  > ca=c8 pf=1 nr=6 ns=6 LM slsap=2c dlsap=05 TTP
>credits=1
>        OBEX DISC (13)
>        c9 dc 05 2e 01 81 00 08 cb ff ff ff ff
DISCONNECT, ConnId=0xFFFFFFFF.  Ehhh?  Where did that value come from?
Again it must be value zero (0).  (BTW per the spec: "0xFFFFFFFF is
reserved and is considered invalid.")

>16:07:08.813821 i:rsp  < ca=c8 pf=1 nr=7 ns=6 LM slsap=05 dlsap=2c TTP
>credits=1
>        OBEX Unknown response 53 (8)
>        c8 fc 2e 05 01 d3 00 03
And the phone responds 0x83=(0x53)=ServiceUnavailable.  Again that's
what one would expect.  The phone knows nothing about that ID!


So obexftp needs to revisit its support for Connection IDs, following
OBEX13.pdf sections 2.2.11 Connection Id, and 4.6 Directed Operations
and Connections.
--
Alan J. McFarlane
http://www.alanjmcf.me.uk/
Please follow-up in the newsgroup for the benefit of all.


Original post :
Hi
I have two phones, a K750i (bluetooth/irda) and a mitsubishi M341i(irda).
There is about two years i try to list the folder of my M341i and get all
the pictures of it.
With K750i there isn't any problem.
With M341i i can put a file on the phone with obexftp -i -p myfile, but with
obexftp -i -l / i have :
[root@surfzoidPC linux-2.6.17-4mdv]# obexftp -i -l /
Connecting...done
Receiving "/"... Sending ""... failed: /
failed: /
Disconnecting...done
[root@surfzoidPC linux-2.6.17-4mdv]# obexftp -i -S -l /
Connecting...done
Receiving "/"... failed: /
Disconnecting...done
[root@surfzoidPC linux-2.6.17-4mdv]#

i read somewere on the web M341i haven't got a standard command to go in
obex mode but AT+CPROT=0 .
It 's the source of my problem ? someone have a M341i too and same problem's 
?
Helpppp please more of two years is so long.
Thanks

_________________________________________________________________
Découvrez Windows Live Messenger : le futur de MSN Messenger ! 
www.windowslivemessenger.fr