From: Keith P. <ke...@ke...> - 2006-10-30 22:27:13
|
On Mon, 2006-10-30 at 20:14 +0100, Ochal Christophe wrote: > When you setup syncml-obex-client over bluetooth, you need to obtain the > hardware address of your phone with hcitool -scan, and the bluetooth > channel with sdptool -browse <hardware address>, syncml should then be > listed. Right, my phone lists SyncML as channel 11: Service Name: SyncML Client Service RecHandle: 0x1000e Service Class ID List: UUID 128: 00000002-0000-1000-8000-0002ee000002 Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 11 "OBEX" (0x0008) Language Base Attr List: code_ISO639: 0x656e encoding: 0x6a base_offset: 0x100 > Also, you might have to configure a username and password on the phone > to be able to initialise communications. Where is this checked on the host side? I've set something on the phone but don't know where the cooresponding host-side setting belongs. > Please post your config of your syncml-obex-client I'm using the syncml-obex-client application directly, having downloaded and built the libsyncml library from subversion a few days ago. I run syncml-obex-client with the following command line: $ syncml-obex-client --sync text/plain Notes -b 00:17:4B:F1:2D:35 11 --wbxm= l The phone reports: Initializing Synchronization Then, it says: Data transfer not possible Finally, it says:=20 =20 Synchronization info: Notes incomplete Unable to process all items. 0 sent. 0 received. Notes updated on other device: New: 0 Removed: 0 Updated: 0 Notes updated on my phone: New: 0 Removed: 0 Updated: 0 Meanwhile, the syncml-obex-client reports: connection with device succeeded Received an Alert for the DS Server at Notes: Type: 201, Last 0, Next 0 Just received a new session with ID 1 Received the DevInf Session 1 reported final. flushing Received an transport error: Request not successfull: 68 --=20 kei...@in... |