Re: [Opensync-users] how to diagnose/trace problem

[matthias j. <jah...@fr...>]

Am Dienstag, 13. Juni 2006 17:29 schrieb Jim Maas:
> I'm almost there .... :-)
>
>   msynctool --sync maassync
> Synchronizing group "maassync"
> The previous synchronization was unclean. Slow-syncing
> Member 2 of type sunbird-sync just connected
> Member 1 of type syncml-obex-client had an error while connecting: Link
> Error
> Member 2 of type sunbird-sync just disconnected
> All clients have disconnected
> The sync failed: Unable to connect one of the members
> Error synchronizing: Unable to connect one of the members


> Can you please remind me again how to trace and/or diagnose the error?
> There are several settings in the syncml-obex-client plugin for
> connection to may motorola a925 ...


> any suggestions for
>
> interface
> identifier
> version

have you first tried to check your phone withe the 
syncml-obex-client from the libsyncml-utils package?


(http://libsyncml.opensync.org/wiki/obex-guide)
<<<<<<<<<<<<<<<<<
First you should connect your device with the usb cable. 
 Then make sure that the lsusb command lists your device. 
 Now we can enumerate the interface available on your device. To do this type 
(as root!): 
syncml-obex-client -u

 This should generate some output like this: 
Found 2 USB OBEX interfaces
Interface 0:
        Manufacturer: Nokia
        Product: Nokia 6680
        Interface description: SYNCML-SYNC
Interface 1:
        Manufacturer: Nokia
        Product: Nokia 6680
        Interface description: PC Suite Services

 It is important that you have an interface with the 
description "SYNCML-SYNC". This is the interface we are going to use.
>>>>>>>>>>>>>>>>>

Matthias