[Opensync-users] SyncML over bluetooth/obex again

[Martin S. <mar...@hi...>]

Hi!

Encouraged by

http://sourceforge.net/mailarchive/forum.php?thread_id=9428612&forum_id=44467

I've configured a synchronizing group between my evolution environment
(plugin evo2-sync) and /dev/rfcomm0 (plugin syncml-obex-client) which is
bound to the serial port bluetooth service of my mobile phone (Samsung
SGH-D600). libsyncml and syncml-plugin are fresh checkouts from svn. The
configuration for the syncml-plugin reads:

<config>
  <username></username>
  <password></password>
  <path>/dev/rfcomm0</path>
  <type>1</type>
  <usestringtable>2</usestringtable>
  <onlyreplace>0</onlyreplace>
  <contact_db>addressbook</contact_db>
  <calendar_db>calendar</calendar_db>
  <task_db>tasks</task_db>
</config>

However, I run into the same troubles discussed in

http://sourceforge.net/mailarchive/forum.php?thread_id=8902424&forum_id=44467

E.i.

$ msynctool --sync testsync

yields:

Synchronizing group "testsync"
Member 1 of type evo2-sync just connected
Member 2 of type syncml-obex-client had an error while connecting: No
success
Member 1 of type evo2-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

The trace output from the syncml-obex-client plugin reads as follows:

[1137969737.641293]     +++++++++ This is the client #2
(syncml-obex-client plugin) of group testsync +++++++++
[1137969737.746230]     >>>>>>>  client_message_handler(0x80638f0,
0x8077aa0, 0x80614e0)
[1137969737.746285]             [CLI] DEBUG: Client message handler
called for message "CONNECT"
[1137969737.746306]             >>>>>>>  osync_member_connect(0x80625c0,
0xb7ebbd70, 0x8077aa0)
[1137969737.746330]                     >>>>>>>
client_connect(0x8077e08)
[1137969741.853995]                             >>>>>>>
osync_context_report_osyncerror(0x8077e08, 0xb6b99244:(No success))
[1137969741.854070]                                     [CLI] WARNING:
Member is replying with message 0x807ef48 to message 0x8077aa0:"CONNECT"
with error 1: No success
[1137969741.854106]                             <<<<<<<
osync_context_report_osyncerror
[1137969741.854126]                     <--- ERROR --- client_connect:
No success
[1137969741.854145]             <<<<<<<  osync_member_connect
[1137969741.854163]     <<<<<<<  client_message_handler

Does anybody have an idea where the problem lies? To start with: is it
more likely from the OBEX transport layer or a SyncML related problem?
Is there anything I can do to help getting the thing to work?

The only information related to SyncML with my mobile phone I've found
up to now is here:

http://www.traud.de/gsm/samsung.htm

I have just e-mailed Samsung about the SyncML version that the SGH-D600
is using. Has it already been clarified, how to find the correct values
of the XXX_db parameters in the configuration of the syncml-plugin?

Regards,

  Martin