opensync-users

[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

Re: [Opensync-users] SyncML over bluetooth/obex again

[kevin j. <rin...@kj...>]

I've been trying to sync my Nokia 6680 with opensync, first trying the
syncml-http-server, until I realised that it is only inbound and my
laptop doesn't have a "real" IP address.

Then I tried using the obex-client - some info on the mailing list
archive (from around November time) says it's still not working, don't
know if that's changed yet. Also I couldn't find any info on what the
config needs to be.

One thing (I think) I did find out is that the obex-client is also
inbound only, so you will need to test it with:

$ msynctool --sync testsync --wait

so that it will wait for a connection.

I am still having problems at the phone end trying to use bluetooth/obex
so I have no messages from opensync saying if anything has worked or
not. I saw someone mention that some of the devs have 6680's - do any of
them have any advice?

Cheers,
KEv.
On Mon, 2006-01-23 at 01:11 +0100, Martin Schulze wrote:
> 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
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
> 

Re: [Opensync-users] SyncML over bluetooth/obex again

[kevin j. <rin...@kj...>]

Just realized that first part might have been misleading - I was trying
to sync from openSync to a SyncML server using the syncml-http-server
connector (and then from the SyncML server to my 6680) firstly - hope
that makes a bit more sense :)
On Mon, 2006-01-23 at 11:32 +0000, kevin james wrote:
> I've been trying to sync my Nokia 6680 with opensync, first trying the
> syncml-http-server, until I realised that it is only inbound and my
> laptop doesn't have a "real" IP address.
> 
> Then I tried using the obex-client - some info on the mailing list
> archive (from around November time) says it's still not working, don't
> know if that's changed yet. Also I couldn't find any info on what the
> config needs to be.
> 
> One thing (I think) I did find out is that the obex-client is also
> inbound only, so you will need to test it with:
> 
> $ msynctool --sync testsync --wait
> 
> so that it will wait for a connection.
> 
> I am still having problems at the phone end trying to use bluetooth/obex
> so I have no messages from opensync saying if anything has worked or
> not. I saw someone mention that some of the devs have 6680's - do any of
> them have any advice?
> 
> Cheers,
> KEv.
> On Mon, 2006-01-23 at 01:11 +0100, Martin Schulze wrote:
> > 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
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> > _______________________________________________
> > Opensync-users mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensync-users
> > 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
> 

Re: [Opensync-users] SyncML over bluetooth/obex again

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

$ msynctool --sync testsync --wait

This doesn't seem to work for the Samsung - at least I have no idea how
to initiate the sync from the SGH-D600, then, so the msynctool waits ad
infinitum.

What changes are needed in libsyncml to trigger the syncronization from
the pc side?

Regards,

  Martin


Am Montag, den 23.01.2006, 11:25 +0000 schrieb kevin james:
> I've been trying to sync my Nokia 6680 with opensync, first trying the
> syncml-http-server, until I realised that it is only inbound and my
> laptop doesn't have a "real" IP address.
> 
> Then I tried using the obex-client - some info on the mailing list
> archive (from around November time) says it's still not working, don't
> know if that's changed yet. Also I couldn't find any info on what the
> config needs to be.
> 
> One thing (I think) I did find out is that the obex-client is also
> inbound only, so you will need to test it with:
> 
> $ msynctool --sync testsync --wait
> 
> so that it will wait for a connection.
> 
> I am still having problems at the phone end trying to use bluetooth/obex
> so I have no messages from opensync saying if anything has worked or
> not. I saw someone mention that some of the devs have 6680's - do any of
> them have any advice?
> 
> Cheers,
> KEv.
> 
> 
> On Mon, 2006-01-23 at 01:11 +0100, Martin Schulze wrote:
> > 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
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> > _______________________________________________
> > Opensync-users mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensync-users
> > 
> 

Re: [Opensync-users] SyncML over bluetooth/obex again

[kevin j. <rin...@kj...>]

And I have the exact opposite problem with my phone - there seems to be
no way to accept an incoming sync on my 6680.

Excuse my ignorance on this, but can anyone confirm/deny if there is
currently any way to accept incoming sync over bluetooth with opensync?

Cheers,
KEv.


On Mon, 2006-01-23 at 17:47 +0100, Martin Schulze wrote:
> $ msynctool --sync testsync --wait
> 
> This doesn't seem to work for the Samsung - at least I have no idea how
> to initiate the sync from the SGH-D600, then, so the msynctool waits ad
> infinitum.
>  
> What changes are needed in libsyncml to trigger the syncronization from
> the pc side?
> 
> Regards,
> 
>   Martin
> 
> 
> Am Montag, den 23.01.2006, 11:25 +0000 schrieb kevin james:
> > I've been trying to sync my Nokia 6680 with opensync, first trying the
> > syncml-http-server, until I realised that it is only inbound and my
> > laptop doesn't have a "real" IP address.
> > 
> > Then I tried using the obex-client - some info on the mailing list
> > archive (from around November time) says it's still not working, don't
> > know if that's changed yet. Also I couldn't find any info on what the
> > config needs to be.
> > 
> > One thing (I think) I did find out is that the obex-client is also
> > inbound only, so you will need to test it with:
> > 
> > $ msynctool --sync testsync --wait
> > 
> > so that it will wait for a connection.
> > 
> > I am still having problems at the phone end trying to use bluetooth/obex
> > so I have no messages from opensync saying if anything has worked or
> > not. I saw someone mention that some of the devs have 6680's - do any of
> > them have any advice?
> > 
> > Cheers,
> > KEv.
> > 
> > 
> > On Mon, 2006-01-23 at 01:11 +0100, Martin Schulze wrote:
> > > 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
> > > 
> > > 
> > > 
> > > 
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> > > for problems?  Stop!  Download the new AJAX search engine that makes
> > > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> > > _______________________________________________
> > > Opensync-users mailing list
> > > Ope...@li...
> > > https://lists.sourceforge.net/lists/listinfo/opensync-users
> > > 
> > 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
> 

Re: [Opensync-users] SyncML over bluetooth/obex again

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

$ msynctool --sync testsync --wait
                            ^^^^^^

As it turns out, this was _not_ the way to go for the SGH-D600.


Instead, I had to insert a hack in

libsyncml/libsyncml/transport/obex_client.c

that sends an AT command

AT+CPROT=0

to the pseudo serial device and listens for the answer

CONNECT

_before_ sending the OBEX connect request. Then, the SGH-D600 answers
with a connect response with connection ID 2. Am OBEX put (final)
request follows and gets a success respone.

Unfortunately, nothing more happens. After while, msynctool quits with
the message

Member 2 of type syncml-obex-client had an error while connecting:
Timeout while waiting for a reply to message "CONNECT"
...

What exactly it is msynctool waiting for? Any ideas why it doesn't get
what it awaits?


Regards,

  Martin


Am Montag, den 23.01.2006, 17:47 +0100 schrieb Martin Schulze:
> $ msynctool --sync testsync --wait
> 
> This doesn't seem to work for the Samsung - at least I have no idea how
> to initiate the sync from the SGH-D600, then, so the msynctool waits ad
> infinitum.
> 
> What changes are needed in libsyncml to trigger the syncronization from
> the pc side?
> 
> Regards,
> 
>   Martin
> 
> 
> Am Montag, den 23.01.2006, 11:25 +0000 schrieb kevin james:
> > I've been trying to sync my Nokia 6680 with opensync, first trying the
> > syncml-http-server, until I realised that it is only inbound and my
> > laptop doesn't have a "real" IP address.
> > 
> > Then I tried using the obex-client - some info on the mailing list
> > archive (from around November time) says it's still not working, don't
> > know if that's changed yet. Also I couldn't find any info on what the
> > config needs to be.
> > 
> > One thing (I think) I did find out is that the obex-client is also
> > inbound only, so you will need to test it with:
> > 
> > $ msynctool --sync testsync --wait
> > 
> > so that it will wait for a connection.
> > 
> > I am still having problems at the phone end trying to use bluetooth/obex
> > so I have no messages from opensync saying if anything has worked or
> > not. I saw someone mention that some of the devs have 6680's - do any of
> > them have any advice?
> > 
> > Cheers,
> > KEv.
> > 
> > 
> > On Mon, 2006-01-23 at 01:11 +0100, Martin Schulze wrote:
> > > 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
> > > 
> > > 
> > > 
> > > 
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> > > for problems?  Stop!  Download the new AJAX search engine that makes
> > > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> > > _______________________________________________
> > > Opensync-users mailing list
> > > Ope...@li...
> > > https://lists.sourceforge.net/lists/listinfo/opensync-users
> > > 
> > 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users

Re: [Opensync-users] SyncML over bluetooth/obex again

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

I have the impression that the SGH-D600 doesn't support the full syncml
specification. In particular, http://www.traud.de/gsm/samsung.htm names
some restictions on the sync alert sent by the server. Therefore, I'm
trying to gain a more detailed understanding of the libsyncml code.

Currently, I don't understand the following point:

  libopensync obviously waits for a feedback on the notification request
(which my mobile phone doesn't give; see last email). As far as I can
gather from the code, the execution flow should be like this:

  smlTransportReceive() -> smlSessionReceive() ->
smlSessionDispatchCommand() -> [chain of callbacks] ->
osync_context_report_success()

If osync_context_report_success() is not called within 60s after the
notification request, a timeout error is reported (which is what I get).

However, even if the SGH-D600 _would_ send an answer, I don't understand
how the above call chain can be triggered: smlTransportReceive() doesn't
get called from the OBEX transport layer, neither gets
smlDsServerRegister() which registers the first callback in [chain of
callbacks]. (Both functions get called from the http transport layer.)
Is the OBEX transport layer incomplete? Did I miss something?

Regards,

  Martin


Am Donnerstag, den 26.01.2006, 00:45 +0100 schrieb Martin Schulze:
> $ msynctool --sync testsync --wait
>                             ^^^^^^
> 
> As it turns out, this was _not_ the way to go for the SGH-D600.
> 
> 
> Instead, I had to insert a hack in
> 
> libsyncml/libsyncml/transport/obex_client.c
> 
> that sends an AT command
> 
> AT+CPROT=0
> 
> to the pseudo serial device and listens for the answer
> 
> CONNECT
> 
> _before_ sending the OBEX connect request. Then, the SGH-D600 answers
> with a connect response with connection ID 2. Am OBEX put (final)
> request follows and gets a success respone.
> 
> Unfortunately, nothing more happens. After while, msynctool quits with
> the message
> 
> Member 2 of type syncml-obex-client had an error while connecting:
> Timeout while waiting for a reply to message "CONNECT"
> ...
> 
> What exactly it is msynctool waiting for? Any ideas why it doesn't get
> what it awaits?
> 
> 
> Regards,
> 
>   Martin
> 
> 
> Am Montag, den 23.01.2006, 17:47 +0100 schrieb Martin Schulze:
> > $ msynctool --sync testsync --wait
> > 
> > This doesn't seem to work for the Samsung - at least I have no idea how
> > to initiate the sync from the SGH-D600, then, so the msynctool waits ad
> > infinitum.
> > 
> > What changes are needed in libsyncml to trigger the syncronization from
> > the pc side?
> > 
> > Regards,
> > 
> >   Martin
> > 
> > 
> > Am Montag, den 23.01.2006, 11:25 +0000 schrieb kevin james:
> > > I've been trying to sync my Nokia 6680 with opensync, first trying the
> > > syncml-http-server, until I realised that it is only inbound and my
> > > laptop doesn't have a "real" IP address.
> > > 
> > > Then I tried using the obex-client - some info on the mailing list
> > > archive (from around November time) says it's still not working, don't
> > > know if that's changed yet. Also I couldn't find any info on what the
> > > config needs to be.
> > > 
> > > One thing (I think) I did find out is that the obex-client is also
> > > inbound only, so you will need to test it with:
> > > 
> > > $ msynctool --sync testsync --wait
> > > 
> > > so that it will wait for a connection.
> > > 
> > > I am still having problems at the phone end trying to use bluetooth/obex
> > > so I have no messages from opensync saying if anything has worked or
> > > not. I saw someone mention that some of the devs have 6680's - do any of
> > > them have any advice?
> > > 
> > > Cheers,
> > > KEv.
> > > 
> > > 
> > > On Mon, 2006-01-23 at 01:11 +0100, Martin Schulze wrote:
> > > > 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
> > > > 
> > > > 
> > > > 
> > > > 
> > > > -------------------------------------------------------
> > > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> > > > for problems?  Stop!  Download the new AJAX search engine that makes
> > > > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> > > > _______________________________________________
> > > > Opensync-users mailing list
> > > > Ope...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/opensync-users
> > > > 
> > > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> > _______________________________________________
> > Opensync-users mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensync-users
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users

Re: [Opensync-users] SyncML over bluetooth/obex again

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

Am Freitag, den 27.01.2006, 12:43 -0200 schrieb =C1drian L=EDvio:
> Hi
>    I am also studing the libsyncml.
>=20
>    Which version of the libsyncml are you studing, the libsyncml
> (trunk) or libsyncml-threaded (branch)?

I have checked out the trunk version (following the instructions in the
wiki). I will try the libsyncml-threaded version ...

>    Do you have any problem building the lib?

trunk compiles out-of-the-box.

> Thanks.
>=20
> --=20
> =C1drian L=EDvio
> Universidade Federal de Campina Grande - UFCG - www.ufcg.edu.br
> Centro de Engenharia El=E9trica e Informatica - CEEI
> Unidade Acad=EAmica de Engenharia El=E9trica - UAEE - www.ee.ufcg.edu.br
> Laborat=F3rio de Sistemas Embarcados e Computa=E7=E3o Pervasiva -
> www.embeddedacademy.org
>=20
>=20
> 2006/1/26, Martin Schulze <mar...@hi...>:
>         I have the impression that the SGH-D600 doesn't support the
>         full syncml
>         specification. In particular,
>         http://www.traud.de/gsm/samsung.htm names
>         some restictions on the sync alert sent by the server.
>         Therefore, I'm=20
>         trying to gain a more detailed understanding of the libsyncml
>         code.
>        =20
>         Currently, I don't understand the following point:
>        =20
>           libopensync obviously waits for a feedback on the
>         notification request
>         (which my mobile phone doesn't give; see last email). As far
>         as I can=20
>         gather from the code, the execution flow should be like this:
>        =20
>           smlTransportReceive() -> smlSessionReceive() ->
>         smlSessionDispatchCommand() -> [chain of callbacks] ->
>         osync_context_report_success()=20
>        =20
>         If osync_context_report_success() is not called within 60s
>         after the
>         notification request, a timeout error is reported (which is
>         what I get).
>        =20
>         However, even if the SGH-D600 _would_ send an answer, I don't
>         understand=20
>         how the above call chain can be triggered:
>         smlTransportReceive() doesn't
>         get called from the OBEX transport layer, neither gets
>         smlDsServerRegister() which registers the first callback in
>         [chain of
>         callbacks]. (Both functions get called from the http transport
>         layer.)=20
>         Is the OBEX transport layer incomplete? Did I miss something?
>        =20
>         Regards,
>        =20
>           Martin
>        =20
>        =20
>         Am Donnerstag, den 26.01.2006, 00:45 +0100 schrieb Martin
>         Schulze:
>         > $ msynctool --sync testsync --wait
>         >                             ^^^^^^
>         >
>         > As it turns out, this was _not_ the way to go for the
>         SGH-D600.
>         >
>         >
>         > Instead, I had to insert a hack in
>         >
>         > libsyncml/libsyncml/transport/obex_client.c
>         >
>         > that sends an AT command=20
>         >
>         > AT+CPROT=3D0
>         >
>         > to the pseudo serial device and listens for the answer
>         >
>         > CONNECT
>         >
>         > _before_ sending the OBEX connect request. Then, the
>         SGH-D600 answers
>         > with a connect response with connection ID 2. Am OBEX put
>         (final)=20
>         > request follows and gets a success respone.
>         >
>         > Unfortunately, nothing more happens. After while, msynctool
>         quits with
>         > the message
>         >
>         > Member 2 of type syncml-obex-client had an error while
>         connecting:=20
>         > Timeout while waiting for a reply to message "CONNECT"
>         > ...
>         >
>         > What exactly it is msynctool waiting for? Any ideas why it
>         doesn't get
>         > what it awaits?
>         >
>         >
>         > Regards,=20
>         >
>         >   Martin
>         >
>         >
>         > Am Montag, den 23.01.2006, 17:47 +0100 schrieb Martin
>         Schulze:
>         > > $ msynctool --sync testsync --wait
>         > >
>         > > This doesn't seem to work for the Samsung - at least I
>         have no idea how=20
>         > > to initiate the sync from the SGH-D600, then, so the
>         msynctool waits ad
>         > > infinitum.
>         > >
>         > > What changes are needed in libsyncml to trigger the
>         syncronization from
>         > > the pc side?=20
>         > >
>         > > Regards,
>         > >
>         > >   Martin
>         > >
>         > >
>         > > Am Montag, den 23.01.2006, 11:25 +0000 schrieb kevin
>         james:
>         > > > I've been trying to sync my Nokia 6680 with opensync,
>         first trying the=20
>         > > > syncml-http-server, until I realised that it is only
>         inbound and my
>         > > > laptop doesn't have a "real" IP address.
>         > > >
>         > > > Then I tried using the obex-client - some info on the
>         mailing list=20
>         > > > archive (from around November time) says it's still not
>         working, don't
>         > > > know if that's changed yet. Also I couldn't find any
>         info on what the
>         > > > config needs to be.
>         > > >=20
>         > > > One thing (I think) I did find out is that the
>         obex-client is also
>         > > > inbound only, so you will need to test it with:
>         > > >
>         > > > $ msynctool --sync testsync --wait=20
>         > > >
>         > > > so that it will wait for a connection.
>         > > >
>         > > > I am still having problems at the phone end trying to
>         use bluetooth/obex
>         > > > so I have no messages from opensync saying if anything
>         has worked or=20
>         > > > not. I saw someone mention that some of the devs have
>         6680's - do any of
>         > > > them have any advice?
>         > > >
>         > > > Cheers,
>         > > > KEv.
>         > > >
>         > > >=20
>         > > > On Mon, 2006-01-23 at 01:11 +0100, Martin Schulze wrote:
>         > > > > Hi!
>         > > > >
>         > > > > Encouraged by
>         > > > >
>         > > > >
>         http://sourceforge.net/mailarchive/forum.php?thread_id=3D9428612&=
forum_id=3D44467
>         > > > >
>         > > > > I've configured a synchronizing group between my
>         evolution environment
>         > > > > (plugin evo2-sync) and /dev/rfcomm0 (plugin
>         syncml-obex-client) which is=20
>         > > > > 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:=20
>         > > > >
>         > > > > <config>
>         > > > >   <username></username>
>         > > > >   <password></password>
>         > > > >   <path>/dev/rfcomm0</path>=20
>         > > > >   <type>1</type>
>         > > > >   <usestringtable>2</usestringtable>
>         > > > >   <onlyreplace>0</onlyreplace>
>         > > > >   <contact_db>addressbook</contact_db>=20
>         > > > >   <calendar_db>calendar</calendar_db>
>         > > > >   <task_db>tasks</task_db>
>         > > > > </config>
>         > > > >
>         > > > > However, I run into the same troubles discussed in=20
>         > > > >
>         > > > >
>         http://sourceforge.net/mailarchive/forum.php?thread_id=3D8902424&=
forum_id=3D44467=20
>         > > > >
>         > > > > E.i.
>         > > > >
>         > > > > $ msynctool --sync testsync
>         > > > >
>         > > > > yields:
>         > > > >
>         > > > > Synchronizing group "testsync"=20
>         > > > > 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=20
>         > > > > All clients have disconnected
>         > > > > The sync failed: Unable to connect one of the members
>         > > > > Error synchronizing: Unable to connect one of the
>         members
>         > > > >=20
>         > > > > 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
>         +++++++++=20
>         > > > > [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=20
>         > > > > 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=20
>         > > > > 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=20
>         > > > > 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,=20
>         > > > >
>         > > > >   Martin
>         > > > >
>         > > > >
>         > > > >
>         > > > >
>         > > > >
>         -------------------------------------------------------=20
>         > > > > This SF.net email is sponsored by: Splunk Inc. Do you
>         grep through log files
>         > > > > for problems?  Stop!  Download the new AJAX search
>         engine that makes
>         > > > > searching your log files as easy as surfing
>         the  web.  DOWNLOAD SPLUNK!=20
>         > > > >
>         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D2304=
86&dat=3D121642
>         > > > > _______________________________________________=20
>         > > > > Opensync-users mailing list
>         > > > > Ope...@li...
>         > > > >
>         https://lists.sourceforge.net/lists/listinfo/opensync-users
>         > > > >
>         > > >
>         > >
>         > >
>         > >
>         > > -------------------------------------------------------
>         > > This SF.net email is sponsored by: Splunk Inc. Do you grep
>         through log files
>         > > for problems?  Stop!  Download the new AJAX search engine
>         that makes
>         > > searching your log files as easy as surfing
>         the  web.  DOWNLOAD SPLUNK!=20
>         > >
>         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D2304=
86&dat=3D121642
>         > > _______________________________________________=20
>         > > Opensync-users mailing list
>         > > Ope...@li...
>         > >
>         https://lists.sourceforge.net/lists/listinfo/opensync-users
>         >
>         >
>         >
>         > -------------------------------------------------------
>         > This SF.net email is sponsored by: Splunk Inc. Do you grep
>         through log files=20
>         > for problems?  Stop!  Download the new AJAX search engine
>         that makes
>         > searching your log files as easy as surfing
>         the  web.  DOWNLOAD SPLUNK!
>         >
>         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D2304=
86&dat=3D121642
>         > _______________________________________________
>         > Opensync-users mailing list
>         > Ope...@li...
>         > https://lists.sourceforge.net/lists/listinfo/opensync-users
>        =20
>        =20
>        =20
>         -------------------------------------------------------=20
>         This SF.net email is sponsored by: Splunk Inc. Do you grep
>         through log files
>         for problems?  Stop!  Download the new AJAX search engine that
>         makes
>         searching your log files as easy as surfing
>         the  web.  DOWNLOAD SPLUNK!=20
>         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D2304=
86&dat=3D121642
>         _______________________________________________=20
>         Opensync-users mailing list
>         Ope...@li...
>         https://lists.sourceforge.net/lists/listinfo/opensync-users
>=20
>=20
>=20
>=20

Re: [Opensync-users] SyncML over bluetooth/obex again

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

Am Samstag, den 28.01.2006, 01:36 +0100 schrieb Martin Schulze:
> Am Freitag, den 27.01.2006, 12:43 -0200 schrieb =C1drian L=EDvio:
> > Hi
> >    I am also studing the libsyncml.
> >=20
> >    Which version of the libsyncml are you studing, the libsyncml
> > (trunk) or libsyncml-threaded (branch)?
>=20
> I have checked out the trunk version (following the instructions in the
> wiki). I will try the libsyncml-threaded version ...
>=20
> >    Do you have any problem building the lib?
>=20
> trunk compiles out-of-the-box.

So does libsyncml-threaded (with current cvs versions of openobex and
libsoup). However, sycml-plugin doesn't compile with
libsyncml-threaded  ...

Regards,

  Martin

> > Thanks.
> >=20
> > --=20
> > =C1drian L=EDvio
> > Universidade Federal de Campina Grande - UFCG - www.ufcg.edu.br
> > Centro de Engenharia El=E9trica e Informatica - CEEI
> > Unidade Acad=EAmica de Engenharia El=E9trica - UAEE - www.ee.ufcg.edu.b=
r
> > Laborat=F3rio de Sistemas Embarcados e Computa=E7=E3o Pervasiva -
> > www.embeddedacademy.org
> >=20
> >=20
> > 2006/1/26, Martin Schulze <mar...@hi...>:
> >         I have the impression that the SGH-D600 doesn't support the
> >         full syncml
> >         specification. In particular,
> >         http://www.traud.de/gsm/samsung.htm names
> >         some restictions on the sync alert sent by the server.
> >         Therefore, I'm=20
> >         trying to gain a more detailed understanding of the libsyncml
> >         code.
> >        =20
> >         Currently, I don't understand the following point:
> >        =20
> >           libopensync obviously waits for a feedback on the
> >         notification request
> >         (which my mobile phone doesn't give; see last email). As far
> >         as I can=20
> >         gather from the code, the execution flow should be like this:
> >        =20
> >           smlTransportReceive() -> smlSessionReceive() ->
> >         smlSessionDispatchCommand() -> [chain of callbacks] ->
> >         osync_context_report_success()=20
> >        =20
> >         If osync_context_report_success() is not called within 60s
> >         after the
> >         notification request, a timeout error is reported (which is
> >         what I get).
> >        =20
> >         However, even if the SGH-D600 _would_ send an answer, I don't
> >         understand=20
> >         how the above call chain can be triggered:
> >         smlTransportReceive() doesn't
> >         get called from the OBEX transport layer, neither gets
> >         smlDsServerRegister() which registers the first callback in
> >         [chain of
> >         callbacks]. (Both functions get called from the http transport
> >         layer.)=20
> >         Is the OBEX transport layer incomplete? Did I miss something?
> >        =20
> >         Regards,
> >        =20
> >           Martin
> >        =20
> >        =20
> >         Am Donnerstag, den 26.01.2006, 00:45 +0100 schrieb Martin
> >         Schulze:
> >         > $ msynctool --sync testsync --wait
> >         >                             ^^^^^^
> >         >
> >         > As it turns out, this was _not_ the way to go for the
> >         SGH-D600.
> >         >
> >         >
> >         > Instead, I had to insert a hack in
> >         >
> >         > libsyncml/libsyncml/transport/obex_client.c
> >         >
> >         > that sends an AT command=20
> >         >
> >         > AT+CPROT=3D0
> >         >
> >         > to the pseudo serial device and listens for the answer
> >         >
> >         > CONNECT
> >         >
> >         > _before_ sending the OBEX connect request. Then, the
> >         SGH-D600 answers
> >         > with a connect response with connection ID 2. Am OBEX put
> >         (final)=20
> >         > request follows and gets a success respone.
> >         >
> >         > Unfortunately, nothing more happens. After while, msynctool
> >         quits with
> >         > the message
> >         >
> >         > Member 2 of type syncml-obex-client had an error while
> >         connecting:=20
> >         > Timeout while waiting for a reply to message "CONNECT"
> >         > ...
> >         >
> >         > What exactly it is msynctool waiting for? Any ideas why it
> >         doesn't get
> >         > what it awaits?
> >         >
> >         >
> >         > Regards,=20
> >         >
> >         >   Martin
> >         >
> >         >
> >         > Am Montag, den 23.01.2006, 17:47 +0100 schrieb Martin
> >         Schulze:
> >         > > $ msynctool --sync testsync --wait
> >         > >
> >         > > This doesn't seem to work for the Samsung - at least I
> >         have no idea how=20
> >         > > to initiate the sync from the SGH-D600, then, so the
> >         msynctool waits ad
> >         > > infinitum.
> >         > >
> >         > > What changes are needed in libsyncml to trigger the
> >         syncronization from
> >         > > the pc side?=20
> >         > >
> >         > > Regards,
> >         > >
> >         > >   Martin
> >         > >
> >         > >
> >         > > Am Montag, den 23.01.2006, 11:25 +0000 schrieb kevin
> >         james:
> >         > > > I've been trying to sync my Nokia 6680 with opensync,
> >         first trying the=20
> >         > > > syncml-http-server, until I realised that it is only
> >         inbound and my
> >         > > > laptop doesn't have a "real" IP address.
> >         > > >
> >         > > > Then I tried using the obex-client - some info on the
> >         mailing list=20
> >         > > > archive (from around November time) says it's still not
> >         working, don't
> >         > > > know if that's changed yet. Also I couldn't find any
> >         info on what the
> >         > > > config needs to be.
> >         > > >=20
> >         > > > One thing (I think) I did find out is that the
> >         obex-client is also
> >         > > > inbound only, so you will need to test it with:
> >         > > >
> >         > > > $ msynctool --sync testsync --wait=20
> >         > > >
> >         > > > so that it will wait for a connection.
> >         > > >
> >         > > > I am still having problems at the phone end trying to
> >         use bluetooth/obex
> >         > > > so I have no messages from opensync saying if anything
> >         has worked or=20
> >         > > > not. I saw someone mention that some of the devs have
> >         6680's - do any of
> >         > > > them have any advice?
> >         > > >
> >         > > > Cheers,
> >         > > > KEv.
> >         > > >
> >         > > >=20
> >         > > > On Mon, 2006-01-23 at 01:11 +0100, Martin Schulze wrote:
> >         > > > > Hi!
> >         > > > >
> >         > > > > Encouraged by
> >         > > > >
> >         > > > >
> >         http://sourceforge.net/mailarchive/forum.php?thread_id=3D942861=
2&forum_id=3D44467
> >         > > > >
> >         > > > > I've configured a synchronizing group between my
> >         evolution environment
> >         > > > > (plugin evo2-sync) and /dev/rfcomm0 (plugin
> >         syncml-obex-client) which is=20
> >         > > > > 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:=20
> >         > > > >
> >         > > > > <config>
> >         > > > >   <username></username>
> >         > > > >   <password></password>
> >         > > > >   <path>/dev/rfcomm0</path>=20
> >         > > > >   <type>1</type>
> >         > > > >   <usestringtable>2</usestringtable>
> >         > > > >   <onlyreplace>0</onlyreplace>
> >         > > > >   <contact_db>addressbook</contact_db>=20
> >         > > > >   <calendar_db>calendar</calendar_db>
> >         > > > >   <task_db>tasks</task_db>
> >         > > > > </config>
> >         > > > >
> >         > > > > However, I run into the same troubles discussed in=20
> >         > > > >
> >         > > > >
> >         http://sourceforge.net/mailarchive/forum.php?thread_id=3D890242=
4&forum_id=3D44467=20
> >         > > > >
> >         > > > > E.i.
> >         > > > >
> >         > > > > $ msynctool --sync testsync
> >         > > > >
> >         > > > > yields:
> >         > > > >
> >         > > > > Synchronizing group "testsync"=20
> >         > > > > 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=20
> >         > > > > All clients have disconnected
> >         > > > > The sync failed: Unable to connect one of the members
> >         > > > > Error synchronizing: Unable to connect one of the
> >         members
> >         > > > >=20
> >         > > > > 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
> >         +++++++++=20
> >         > > > > [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=20
> >         > > > > 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=20
> >         > > > > 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=20
> >         > > > > 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,=20
> >         > > > >
> >         > > > >   Martin
> >         > > > >
> >         > > > >
> >         > > > >
> >         > > > >
> >         > > > >
> >         -------------------------------------------------------=20
> >         > > > > This SF.net email is sponsored by: Splunk Inc. Do you
> >         grep through log files
> >         > > > > for problems?  Stop!  Download the new AJAX search
> >         engine that makes
> >         > > > > searching your log files as easy as surfing
> >         the  web.  DOWNLOAD SPLUNK!=20
> >         > > > >
> >         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D23=
0486&dat=3D121642
> >         > > > > _______________________________________________=20
> >         > > > > Opensync-users mailing list
> >         > > > > Ope...@li...
> >         > > > >
> >         https://lists.sourceforge.net/lists/listinfo/opensync-users
> >         > > > >
> >         > > >
> >         > >
> >         > >
> >         > >
> >         > > -------------------------------------------------------
> >         > > This SF.net email is sponsored by: Splunk Inc. Do you grep
> >         through log files
> >         > > for problems?  Stop!  Download the new AJAX search engine
> >         that makes
> >         > > searching your log files as easy as surfing
> >         the  web.  DOWNLOAD SPLUNK!=20
> >         > >
> >         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D23=
0486&dat=3D121642
> >         > > _______________________________________________=20
> >         > > Opensync-users mailing list
> >         > > Ope...@li...
> >         > >
> >         https://lists.sourceforge.net/lists/listinfo/opensync-users
> >         >
> >         >
> >         >
> >         > -------------------------------------------------------
> >         > This SF.net email is sponsored by: Splunk Inc. Do you grep
> >         through log files=20
> >         > for problems?  Stop!  Download the new AJAX search engine
> >         that makes
> >         > searching your log files as easy as surfing
> >         the  web.  DOWNLOAD SPLUNK!
> >         >
> >         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D23=
0486&dat=3D121642
> >         > _______________________________________________
> >         > Opensync-users mailing list
> >         > Ope...@li...
> >         > https://lists.sourceforge.net/lists/listinfo/opensync-users
> >        =20
> >        =20
> >        =20
> >         -------------------------------------------------------=20
> >         This SF.net email is sponsored by: Splunk Inc. Do you grep
> >         through log files
> >         for problems?  Stop!  Download the new AJAX search engine that
> >         makes
> >         searching your log files as easy as surfing
> >         the  web.  DOWNLOAD SPLUNK!=20
> >         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D23=
0486&dat=3D121642
> >         _______________________________________________=20
> >         Opensync-users mailing list
> >         Ope...@li...
> >         https://lists.sourceforge.net/lists/listinfo/opensync-users
> >=20
> >=20
> >=20
> >=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users

Re: [Opensync-users] SyncML over bluetooth/obex again

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

I've had a look at the libsyncml-threaded version this evening. From the
sparse information that I could get, this seems to be the actively
maintained branch. Attached are patches to this branch and the
sycml-plugin from trunk.

With these patches applied to current svn, sycml-plugin compiles and
runs with the libyscml-threaded version. There is no ChangeLog, so I
have enclosed a short description of the changes below.

msynctool still doesn't work with my mobile phone. It doesn't seem to
react on the SAN. I gather so much that SAN requires syncml 1.2 (at
least the way it is currently implemented in libsyncml) and the SGH-D600
only support syncml 1.1.

Regards,

  Martin

_____________________________________________

libsyncml-2006_01_29.diff:

	libsyncml/sml_queue.c: Rename the callback functions. Before, the
callback functions from libopensync/osengine/osengine_queue.c were
called on my testing platform (leading to SEGFAULT).
	libsyncml/sml_transport.c: Fix typo in the documentation.
	libsyncml/sml_manager.c: Enhance _smlManagerDataHandler() to handle to
only event type SML_TRANSPORT_EVENT_DATA. TODO: Probably, events of type
SML_TRANSPORT_EVENT_CONNECT_DONE should also be forwarded to
manager->eventCallback(). However, there is no SML_MANAGER* macro for
this, yet.
	smlManagerSessionRemove() now calls manager->eventCallback() with
SML_MANAGER_SESSION_END.
	smlManagerNew(): Fix typo.
	libsyncml/sml_support.c: The idle callback doesn't get called when a
new thread is started. Work around: _start_main_loop().

syncml-plugin-2006_01_29.diff:

	src/syncml_plugin.[hc]: Make it work with the libsyncml-threaded branch
of libsyncml. Use smlManager to manage sessions. I'm not sure whether
SmlDsSession is used correctly in batch_commit().
	src/syncml-obex-client: Rename 'path' to 'url'. Add new parameter
'port'.


Am Samstag, den 28.01.2006, 02:18 +0100 schrieb Martin Schulze:
> Am Samstag, den 28.01.2006, 01:36 +0100 schrieb Martin Schulze:
> > Am Freitag, den 27.01.2006, 12:43 -0200 schrieb =C1drian L=EDvio:
> > > Hi
> > >    I am also studing the libsyncml.
> > >=20
> > >    Which version of the libsyncml are you studing, the libsyncml
> > > (trunk) or libsyncml-threaded (branch)?
> >=20
> > I have checked out the trunk version (following the instructions in the
> > wiki). I will try the libsyncml-threaded version ...
> >=20
> > >    Do you have any problem building the lib?
> >=20
> > trunk compiles out-of-the-box.
>=20
> So does libsyncml-threaded (with current cvs versions of openobex and
> libsoup). However, sycml-plugin doesn't compile with
> libsyncml-threaded  ...
>=20
> Regards,
>=20
>   Martin
>=20
> > > Thanks.
> > >=20
> > > --=20
> > > =C1drian L=EDvio
> > > Universidade Federal de Campina Grande - UFCG - www.ufcg.edu.br
> > > Centro de Engenharia El=E9trica e Informatica - CEEI
> > > Unidade Acad=EAmica de Engenharia El=E9trica - UAEE - www.ee.ufcg.edu=
.br
> > > Laborat=F3rio de Sistemas Embarcados e Computa=E7=E3o Pervasiva -
> > > www.embeddedacademy.org
> > >=20
> > >=20
> > > 2006/1/26, Martin Schulze <mar...@hi...>:
> > >         I have the impression that the SGH-D600 doesn't support the
> > >         full syncml
> > >         specification. In particular,
> > >         http://www.traud.de/gsm/samsung.htm names
> > >         some restictions on the sync alert sent by the server.
> > >         Therefore, I'm=20
> > >         trying to gain a more detailed understanding of the libsyncml
> > >         code.
> > >        =20
> > >         Currently, I don't understand the following point:
> > >        =20
> > >           libopensync obviously waits for a feedback on the
> > >         notification request
> > >         (which my mobile phone doesn't give; see last email). As far
> > >         as I can=20
> > >         gather from the code, the execution flow should be like this:
> > >        =20
> > >           smlTransportReceive() -> smlSessionReceive() ->
> > >         smlSessionDispatchCommand() -> [chain of callbacks] ->
> > >         osync_context_report_success()=20
> > >        =20
> > >         If osync_context_report_success() is not called within 60s
> > >         after the
> > >         notification request, a timeout error is reported (which is
> > >         what I get).
> > >        =20
> > >         However, even if the SGH-D600 _would_ send an answer, I don't
> > >         understand=20
> > >         how the above call chain can be triggered:
> > >         smlTransportReceive() doesn't
> > >         get called from the OBEX transport layer, neither gets
> > >         smlDsServerRegister() which registers the first callback in
> > >         [chain of
> > >         callbacks]. (Both functions get called from the http transpor=
t
> > >         layer.)=20
> > >         Is the OBEX transport layer incomplete? Did I miss something?
> > >        =20
> > >         Regards,
> > >        =20
> > >           Martin
> > >        =20
> > >        =20
> > >         Am Donnerstag, den 26.01.2006, 00:45 +0100 schrieb Martin
> > >         Schulze:
> > >         > $ msynctool --sync testsync --wait
> > >         >                             ^^^^^^
> > >         >
> > >         > As it turns out, this was _not_ the way to go for the
> > >         SGH-D600.
> > >         >
> > >         >
> > >         > Instead, I had to insert a hack in
> > >         >
> > >         > libsyncml/libsyncml/transport/obex_client.c
> > >         >
> > >         > that sends an AT command=20
> > >         >
> > >         > AT+CPROT=3D0
> > >         >
> > >         > to the pseudo serial device and listens for the answer
> > >         >
> > >         > CONNECT
> > >         >
> > >         > _before_ sending the OBEX connect request. Then, the
> > >         SGH-D600 answers
> > >         > with a connect response with connection ID 2. Am OBEX put
> > >         (final)=20
> > >         > request follows and gets a success respone.
> > >         >
> > >         > Unfortunately, nothing more happens. After while, msynctool
> > >         quits with
> > >         > the message
> > >         >
> > >         > Member 2 of type syncml-obex-client had an error while
> > >         connecting:=20
> > >         > Timeout while waiting for a reply to message "CONNECT"
> > >         > ...
> > >         >
> > >         > What exactly it is msynctool waiting for? Any ideas why it
> > >         doesn't get
> > >         > what it awaits?
> > >         >
> > >         >
> > >         > Regards,=20
> > >         >
> > >         >   Martin
> > >         >
> > >         >
> > >         > Am Montag, den 23.01.2006, 17:47 +0100 schrieb Martin
> > >         Schulze:
> > >         > > $ msynctool --sync testsync --wait
> > >         > >
> > >         > > This doesn't seem to work for the Samsung - at least I
> > >         have no idea how=20
> > >         > > to initiate the sync from the SGH-D600, then, so the
> > >         msynctool waits ad
> > >         > > infinitum.
> > >         > >
> > >         > > What changes are needed in libsyncml to trigger the
> > >         syncronization from
> > >         > > the pc side?=20
> > >         > >
> > >         > > Regards,
> > >         > >
> > >         > >   Martin
> > >         > >
> > >         > >
> > >         > > Am Montag, den 23.01.2006, 11:25 +0000 schrieb kevin
> > >         james:
> > >         > > > I've been trying to sync my Nokia 6680 with opensync,
> > >         first trying the=20
> > >         > > > syncml-http-server, until I realised that it is only
> > >         inbound and my
> > >         > > > laptop doesn't have a "real" IP address.
> > >         > > >
> > >         > > > Then I tried using the obex-client - some info on the
> > >         mailing list=20
> > >         > > > archive (from around November time) says it's still not
> > >         working, don't
> > >         > > > know if that's changed yet. Also I couldn't find any
> > >         info on what the
> > >         > > > config needs to be.
> > >         > > >=20
> > >         > > > One thing (I think) I did find out is that the
> > >         obex-client is also
> > >         > > > inbound only, so you will need to test it with:
> > >         > > >
> > >         > > > $ msynctool --sync testsync --wait=20
> > >         > > >
> > >         > > > so that it will wait for a connection.
> > >         > > >
> > >         > > > I am still having problems at the phone end trying to
> > >         use bluetooth/obex
> > >         > > > so I have no messages from opensync saying if anything
> > >         has worked or=20
> > >         > > > not. I saw someone mention that some of the devs have
> > >         6680's - do any of
> > >         > > > them have any advice?
> > >         > > >
> > >         > > > Cheers,
> > >         > > > KEv.
> > >         > > >
> > >         > > >=20
> > >         > > > On Mon, 2006-01-23 at 01:11 +0100, Martin Schulze wrote=
:
> > >         > > > > Hi!
> > >         > > > >
> > >         > > > > Encouraged by
> > >         > > > >
> > >         > > > >
> > >         http://sourceforge.net/mailarchive/forum.php?thread_id=3D9428=
612&forum_id=3D44467
> > >         > > > >
> > >         > > > > I've configured a synchronizing group between my
> > >         evolution environment
> > >         > > > > (plugin evo2-sync) and /dev/rfcomm0 (plugin
> > >         syncml-obex-client) which is=20
> > >         > > > > 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:=20
> > >         > > > >
> > >         > > > > <config>
> > >         > > > >   <username></username>
> > >         > > > >   <password></password>
> > >         > > > >   <path>/dev/rfcomm0</path>=20
> > >         > > > >   <type>1</type>
> > >         > > > >   <usestringtable>2</usestringtable>
> > >         > > > >   <onlyreplace>0</onlyreplace>
> > >         > > > >   <contact_db>addressbook</contact_db>=20
> > >         > > > >   <calendar_db>calendar</calendar_db>
> > >         > > > >   <task_db>tasks</task_db>
> > >         > > > > </config>
> > >         > > > >
> > >         > > > > However, I run into the same troubles discussed in=20
> > >         > > > >
> > >         > > > >
> > >         http://sourceforge.net/mailarchive/forum.php?thread_id=3D8902=
424&forum_id=3D44467=20
> > >         > > > >
> > >         > > > > E.i.
> > >         > > > >
> > >         > > > > $ msynctool --sync testsync
> > >         > > > >
> > >         > > > > yields:
> > >         > > > >
> > >         > > > > Synchronizing group "testsync"=20
> > >         > > > > Member 1 of type evo2-sync just connected
> > >         > > > > Member 2 of type syncml-obex-client had an error whil=
e
> > >         connecting: No
> > >         > > > > success
> > >         > > > > Member 1 of type evo2-sync just disconnected=20
> > >         > > > > All clients have disconnected
> > >         > > > > The sync failed: Unable to connect one of the members
> > >         > > > > Error synchronizing: Unable to connect one of the
> > >         members
> > >         > > > >=20
> > >         > > > > 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
> > >         +++++++++=20
> > >         > > > > [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=20
> > >         > > > > 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=20
> > >         > > > > 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=20
> > >         > > > > 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,=20
> > >         > > > >
> > >         > > > >   Martin
> > >         > > > >
> > >         > > > >
> > >         > > > >
> > >         > > > >
> > >         > > > >
> > >         -------------------------------------------------------=20
> > >         > > > > This SF.net email is sponsored by: Splunk Inc. Do you
> > >         grep through log files
> > >         > > > > for problems?  Stop!  Download the new AJAX search
> > >         engine that makes
> > >         > > > > searching your log files as easy as surfing
> > >         the  web.  DOWNLOAD SPLUNK!=20
> > >         > > > >
> > >         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D=
230486&dat=3D121642
> > >         > > > > _______________________________________________=20
> > >         > > > > Opensync-users mailing list
> > >         > > > > Ope...@li...
> > >         > > > >
> > >         https://lists.sourceforge.net/lists/listinfo/opensync-users
> > >         > > > >
> > >         > > >
> > >         > >
> > >         > >
> > >         > >
> > >         > > -------------------------------------------------------
> > >         > > This SF.net email is sponsored by: Splunk Inc. Do you gre=
p
> > >         through log files
> > >         > > for problems?  Stop!  Download the new AJAX search engine
> > >         that makes
> > >         > > searching your log files as easy as surfing
> > >         the  web.  DOWNLOAD SPLUNK!=20
> > >         > >
> > >         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D=
230486&dat=3D121642
> > >         > > _______________________________________________=20
> > >         > > Opensync-users mailing list
> > >         > > Ope...@li...
> > >         > >
> > >         https://lists.sourceforge.net/lists/listinfo/opensync-users
> > >         >
> > >         >
> > >         >
> > >         > -------------------------------------------------------
> > >         > This SF.net email is sponsored by: Splunk Inc. Do you grep
> > >         through log files=20
> > >         > for problems?  Stop!  Download the new AJAX search engine
> > >         that makes
> > >         > searching your log files as easy as surfing
> > >         the  web.  DOWNLOAD SPLUNK!
> > >         >
> > >         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D=
230486&dat=3D121642
> > >         > _______________________________________________
> > >         > Opensync-users mailing list
> > >         > Ope...@li...
> > >         > https://lists.sourceforge.net/lists/listinfo/opensync-users
> > >        =20
> > >        =20
> > >        =20
> > >         -------------------------------------------------------=20
> > >         This SF.net email is sponsored by: Splunk Inc. Do you grep
> > >         through log files
> > >         for problems?  Stop!  Download the new AJAX search engine tha=
t
> > >         makes
> > >         searching your log files as easy as surfing
> > >         the  web.  DOWNLOAD SPLUNK!=20
> > >         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D=
230486&dat=3D121642
> > >         _______________________________________________=20
> > >         Opensync-users mailing list
> > >         Ope...@li...
> > >         https://lists.sourceforge.net/lists/listinfo/opensync-users
> > >=20
> > >=20
> > >=20
> > >=20
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=12164=
2
> > _______________________________________________
> > Opensync-users mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensync-users
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users

Re: [Opensync-users] SyncML over bluetooth/obex again

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

Samsung answered that the SyncML-version supported by the SGH-D600 would
be "SyncML DS (Localsync)". Does this mean anything to anybody?

Regards,

  Martin


Am Montag, den 23.01.2006, 01:11 +0100 schrieb Martin Schulze:
> 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
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users

Re: [Opensync-users] SyncML over bluetooth/obex again

[<nhd...@gm...>]

Hi
   I solved my problem using the CVS version of the openobex.

 $ cvs -d:pserver:ano...@cv...:/cvsroot/openobex login
*No password, just press <enter>*
$ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/openobex co -P
openobex

 $ cd openobex
$ ./bootstrap
$ ./configure
$ make
$ su
$ make install
 Thanks,
 =C1drian L=EDvio

Universidade Federal de Campina Grande - UFCG - www.ufcg.edu.br
Centro de Engenharia El=E9trica e Informatica - CEEI
Unidade Acad=EAmica de Engenharia El=E9trica - UAEE - www.ee.ufcg.edu.br
Laborat=F3rio de Sistemas Embarcados e Computa=E7=E3o Pervasiva -
www.embeddedacademy.org


2006/1/30, =C1drian L=EDvio <nhd...@gm...>:
>
> Hi
>
>    I'm trying to build the libyscml-threaded version,  I instaled the
> libsoup-2.2.9, and patched the libwbxml with the patch in the
> libyscml-threaded dir, I have also instaled the openobex-dev package, but
> when I run the configure script:
>
> ./configure --prefix=3D/home/local/workspace/syncml-testdir
> --with-wbxml=3D/home/local/workspace/syncml-testdir
>
>    I got:
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>   Unit Tests:             Enabled
>   Tracing:                Enabled
>   Tools:                  Enabled
>   Libwbxml:               Enabled
>
> The transports are:
>   Http Client:            Enabled
>   Http Server:            Enabled
>   Obex Client:            Disabled
>   Obex Server:            Disabled
>
> Done configuring.
> Please review the settings above
> If they are ok, build libsyncml and install it.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
>     I noticide that there is no openobex.pc file in /usr/lib/pkgconfig/
> then I create one:
>
> # Package Information for pkg-config
>
> prefix=3D/usr
> exec_prefix=3D${prefix}
> libdir=3D${exec_prefix}/lib
> includedir=3D${prefix}/include
>
> Name: openobex
> Description: openobex adricionado por mim
> Version:1.0
> Libs: -L${libdir} -lopenobex
> Cflags: -I${includedir}
>
>    but the configure script don't work, in the configure.ac file I notice=
d
> that the required version is the 1.1,
>
> PKG_CHECK_MODULES(LIBOPENOBEX, openobex >=3D 1.1, HAVE_OPENOBEX=3Dyes,
> HAVE_OPENOBEX=3Dno)
>
> Someone can help me?
>
> Regards,
> =C1drian L=EDvio
> Universidade Federal de Campina Grande - UFCG - www.ufcg.edu.br
> Centro de Engenharia El=E9trica e Informatica - CEEI
> Unidade Acad=EAmica de Engenharia El=E9trica - UAEE - www.ee.ufcg.edu.br
> Laborat=F3rio de Sistemas Embarcados e Computa=E7=E3o Pervasiva - www.emb=
eddedacademy.org
>
>
>

Re: [Opensync-users] SyncML over bluetooth/obex again

[kevin j. <rin...@kj...>]

Did you have any success with it? I got it to compile successfully, but
when I try to sync with my Nokia 6680 the phone asks for the pin number,
then opensync reports:

Member 2 of type syncml-obex-client had an error while connecting:
Unable to setup transport

Cheers,
KEv.


On Mon, 2006-01-30 at 16:34 -0200, Ádrian Lívio wrote:
> Hi
>    I solved my problem using the CVS version of the openobex.
> 
> $ cvs -d:pserver:ano...@cv...:/cvsroot/openobex
> login 
> No password, just press <enter> 
> $ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/openobex
> co -P openobex
> 
> 
> 
> $ cd openobex 
> $ ./bootstrap 
> $ ./configure 
> $ make 
> $ su   
> $ make install
> 
> 
> Thanks,
> Ádrian Lívio
> 
> Universidade Federal de Campina Grande - UFCG - www.ufcg.edu.br
> Centro de Engenharia Elétrica e Informatica - CEEI 
> Unidade Acadêmica de Engenharia Elétrica - UAEE - www.ee.ufcg.edu.br
> Laboratório de Sistemas Embarcados e Computação Pervasiva -
> www.embeddedacademy.org
> 
> 2006/1/30, Ádrian Lívio <nhd...@gm...>:
>         Hi 
>         
>            I'm trying to build the libyscml-threaded version,  I
>         instaled the libsoup-2.2.9, and patched the libwbxml with the
>         patch in the libyscml-threaded dir, I have also instaled the
>         openobex-dev package, but when I run the configure script:
>         
>         ./configure --prefix=/home/local/workspace/syncml-testdir
>         --with-wbxml=/home/local/workspace/syncml-testdir
>         
>            I got:
>         
>         ===============================================
>           Unit Tests:             Enabled
>           Tracing:                Enabled
>           Tools:                  Enabled
>           Libwbxml:               Enabled
>         
>         The transports are:
>           Http Client:            Enabled
>           Http Server:            Enabled
>           Obex Client:            Disabled
>           Obex Server:            Disabled
>         
>         Done configuring.
>         Please review the settings above
>         If they are ok, build libsyncml and install it.
>         ===============================================
>         
>             I noticide that there is no openobex.pc file
>         in /usr/lib/pkgconfig/ then I create one:
>         
>         # Package Information for pkg-config
>         
>         prefix=/usr
>         exec_prefix=${prefix}
>         libdir=${exec_prefix}/lib
>         includedir=${prefix}/include
>         
>         Name: openobex
>         Description: openobex adricionado por mim
>         Version:1.0
>         Libs: -L${libdir} -lopenobex
>         Cflags: -I${includedir}
>         
>            but the configure script don't work, in the configure.ac
>         file I noticed that the required version is the 1.1,
>         
>         PKG_CHECK_MODULES(LIBOPENOBEX, openobex >= 1.1,
>         HAVE_OPENOBEX=yes, HAVE_OPENOBEX=no)
>         
>         Someone can help me?
>         
>         Regards, 
>         Ádrian Lívio
>         Universidade Federal de Campina Grande - UFCG -
>         www.ufcg.edu.br
>         Centro de Engenharia Elétrica e Informatica - CEEI 
>         Unidade Acadêmica de Engenharia Elétrica - UAEE -
>         www.ee.ufcg.edu.br
>         Laboratório de Sistemas Embarcados e Computação Pervasiva -
>         www.embeddedacademy.org
>         
> 
> 

Re: [Opensync-users] SyncML over bluetooth/obex again

[<nhd...@gm...>]

SGksCiAgTm90IHlldCwgdG9kYXkgSSB3aWxsIHN0YXJ0IHRvIHN0dWR5IHRoZSBjb2RlIHNlYXJj
aGluZyBieSB0aGUgcG9pbnRzIG5vdAppbXBsZW1lbnRlZCB5ZXQsIHVzaW5nIHRoZSBsaWJ5c2Nt
bC10aHJlYWRlZCB0aGUgc3luY21sLXBsdWdpbiBkb24ndApjb21waWxlLgogIEkgd2lsbCB0cnkg
dGhlIE1hcnRpbiBTY2h1bHplIHBhdGNoIHRoYXQgc29sdmUgdGhlIGJ1aWxkIGVycm9yLgoKICBD
aGVlcnMsCiAgwWRyaWFuCgoyMDA2LzEvMzAsIGtldmluIGphbWVzIDxyaW5jZXdpbmRAa2phbWVz
Lm5ldD46Cj4KPiBEaWQgeW91IGhhdmUgYW55IHN1Y2Nlc3Mgd2l0aCBpdD8gSSBnb3QgaXQgdG8g
Y29tcGlsZSBzdWNjZXNzZnVsbHksIGJ1dAo+IHdoZW4gSSB0cnkgdG8gc3luYyB3aXRoIG15IE5v
a2lhIDY2ODAgdGhlIHBob25lIGFza3MgZm9yIHRoZSBwaW4gbnVtYmVyLAo+IHRoZW4gb3BlbnN5
bmMgcmVwb3J0czoKPgo+IE1lbWJlciAyIG9mIHR5cGUgc3luY21sLW9iZXgtY2xpZW50IGhhZCBh
biBlcnJvciB3aGlsZSBjb25uZWN0aW5nOgo+IFVuYWJsZSB0byBzZXR1cCB0cmFuc3BvcnQKPgo+
IENoZWVycywKPiBLRXYuCj4KPgo+IE9uIE1vbiwgMjAwNi0wMS0zMCBhdCAxNjozNCAtMDIwMCwg
wWRyaWFuIEztdmlvIHdyb3RlOgo+ID4gSGkKPiA+ICAgIEkgc29sdmVkIG15IHByb2JsZW0gdXNp
bmcgdGhlIENWUyB2ZXJzaW9uIG9mIHRoZSBvcGVub2JleC4KPiA+Cj4gPiAkIGN2cyAtZDpwc2Vy
dmVyOmFub255bW91c0BjdnMuc291cmNlZm9yZ2UubmV0Oi9jdnNyb290L29wZW5vYmV4Cj4gPiBs
b2dpbgo+ID4gTm8gcGFzc3dvcmQsIGp1c3QgcHJlc3MgPGVudGVyPgo+ID4gJCBjdnMgLXozIC1k
OnBzZXJ2ZXI6YW5vbnltb3VzQGN2cy5zb3VyY2Vmb3JnZS5uZXQ6L2N2c3Jvb3Qvb3Blbm9iZXgK
PiA+IGNvIC1QIG9wZW5vYmV4Cj4gPgo+ID4KPiA+Cj4gPiAkIGNkIG9wZW5vYmV4Cj4gPiAkIC4v
Ym9vdHN0cmFwCj4gPiAkIC4vY29uZmlndXJlCj4gPiAkIG1ha2UKPiA+ICQgc3UKPiA+ICQgbWFr
ZSBpbnN0YWxsCj4gPgo+ID4KPiA+IFRoYW5rcywKPiA+IMFkcmlhbiBM7XZpbwo+ID4KPiA+IFVu
aXZlcnNpZGFkZSBGZWRlcmFsIGRlIENhbXBpbmEgR3JhbmRlIC0gVUZDRyAtIHd3dy51ZmNnLmVk
dS5icgo+ID4gQ2VudHJvIGRlIEVuZ2VuaGFyaWEgRWzpdHJpY2EgZSBJbmZvcm1hdGljYSAtIENF
RUkKPiA+IFVuaWRhZGUgQWNhZOptaWNhIGRlIEVuZ2VuaGFyaWEgRWzpdHJpY2EgLSBVQUVFIC0g
d3d3LmVlLnVmY2cuZWR1LmJyCj4gPiBMYWJvcmF083JpbyBkZSBTaXN0ZW1hcyBFbWJhcmNhZG9z
IGUgQ29tcHV0YefjbyBQZXJ2YXNpdmEgLQo+ID4gd3d3LmVtYmVkZGVkYWNhZGVteS5vcmcKPiA+
Cj4gPiAyMDA2LzEvMzAsIMFkcmlhbiBM7XZpbyA8bmhkZXpvaXRvQGdtYWlsLmNvbT46Cj4gPiAg
ICAgICAgIEhpCj4gPgo+ID4gICAgICAgICAgICBJJ20gdHJ5aW5nIHRvIGJ1aWxkIHRoZSBsaWJ5
c2NtbC10aHJlYWRlZCB2ZXJzaW9uLCAgSQo+ID4gICAgICAgICBpbnN0YWxlZCB0aGUgbGlic291
cC0yLjIuOSwgYW5kIHBhdGNoZWQgdGhlIGxpYndieG1sIHdpdGggdGhlCj4gPiAgICAgICAgIHBh
dGNoIGluIHRoZSBsaWJ5c2NtbC10aHJlYWRlZCBkaXIsIEkgaGF2ZSBhbHNvIGluc3RhbGVkIHRo
ZQo+ID4gICAgICAgICBvcGVub2JleC1kZXYgcGFja2FnZSwgYnV0IHdoZW4gSSBydW4gdGhlIGNv
bmZpZ3VyZSBzY3JpcHQ6Cj4gPgo+ID4gICAgICAgICAuL2NvbmZpZ3VyZSAtLXByZWZpeD0vaG9t
ZS9sb2NhbC93b3Jrc3BhY2Uvc3luY21sLXRlc3RkaXIKPiA+ICAgICAgICAgLS13aXRoLXdieG1s
PS9ob21lL2xvY2FsL3dvcmtzcGFjZS9zeW5jbWwtdGVzdGRpcgo+ID4KPiA+ICAgICAgICAgICAg
SSBnb3Q6Cj4gPgo+ID4gICAgICAgICA9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PQo+ID4gICAgICAgICAgIFVuaXQgVGVzdHM6ICAgICAgICAgICAgIEVuYWJs
ZWQKPiA+ICAgICAgICAgICBUcmFjaW5nOiAgICAgICAgICAgICAgICBFbmFibGVkCj4gPiAgICAg
ICAgICAgVG9vbHM6ICAgICAgICAgICAgICAgICAgRW5hYmxlZAo+ID4gICAgICAgICAgIExpYndi
eG1sOiAgICAgICAgICAgICAgIEVuYWJsZWQKPiA+Cj4gPiAgICAgICAgIFRoZSB0cmFuc3BvcnRz
IGFyZToKPiA+ICAgICAgICAgICBIdHRwIENsaWVudDogICAgICAgICAgICBFbmFibGVkCj4gPiAg
ICAgICAgICAgSHR0cCBTZXJ2ZXI6ICAgICAgICAgICAgRW5hYmxlZAo+ID4gICAgICAgICAgIE9i
ZXggQ2xpZW50OiAgICAgICAgICAgIERpc2FibGVkCj4gPiAgICAgICAgICAgT2JleCBTZXJ2ZXI6
ICAgICAgICAgICAgRGlzYWJsZWQKPiA+Cj4gPiAgICAgICAgIERvbmUgY29uZmlndXJpbmcuCj4g
PiAgICAgICAgIFBsZWFzZSByZXZpZXcgdGhlIHNldHRpbmdzIGFib3ZlCj4gPiAgICAgICAgIElm
IHRoZXkgYXJlIG9rLCBidWlsZCBsaWJzeW5jbWwgYW5kIGluc3RhbGwgaXQuCj4gPiAgICAgICAg
ID09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Cj4gPgo+ID4g
ICAgICAgICAgICAgSSBub3RpY2lkZSB0aGF0IHRoZXJlIGlzIG5vIG9wZW5vYmV4LnBjIGZpbGUK
PiA+ICAgICAgICAgaW4gL3Vzci9saWIvcGtnY29uZmlnLyB0aGVuIEkgY3JlYXRlIG9uZToKPiA+
Cj4gPiAgICAgICAgICMgUGFja2FnZSBJbmZvcm1hdGlvbiBmb3IgcGtnLWNvbmZpZwo+ID4KPiA+
ICAgICAgICAgcHJlZml4PS91c3IKPiA+ICAgICAgICAgZXhlY19wcmVmaXg9JHtwcmVmaXh9Cj4g
PiAgICAgICAgIGxpYmRpcj0ke2V4ZWNfcHJlZml4fS9saWIKPiA+ICAgICAgICAgaW5jbHVkZWRp
cj0ke3ByZWZpeH0vaW5jbHVkZQo+ID4KPiA+ICAgICAgICAgTmFtZTogb3Blbm9iZXgKPiA+ICAg
ICAgICAgRGVzY3JpcHRpb246IG9wZW5vYmV4IGFkcmljaW9uYWRvIHBvciBtaW0KPiA+ICAgICAg
ICAgVmVyc2lvbjoxLjAKPiA+ICAgICAgICAgTGliczogLUwke2xpYmRpcn0gLWxvcGVub2JleAo+
ID4gICAgICAgICBDZmxhZ3M6IC1JJHtpbmNsdWRlZGlyfQo+ID4KPiA+ICAgICAgICAgICAgYnV0
IHRoZSBjb25maWd1cmUgc2NyaXB0IGRvbid0IHdvcmssIGluIHRoZSBjb25maWd1cmUuYWMKPiA+
ICAgICAgICAgZmlsZSBJIG5vdGljZWQgdGhhdCB0aGUgcmVxdWlyZWQgdmVyc2lvbiBpcyB0aGUg
MS4xLAo+ID4KPiA+ICAgICAgICAgUEtHX0NIRUNLX01PRFVMRVMoTElCT1BFTk9CRVgsIG9wZW5v
YmV4ID49IDEuMSwKPiA+ICAgICAgICAgSEFWRV9PUEVOT0JFWD15ZXMsIEhBVkVfT1BFTk9CRVg9
bm8pCj4gPgo+ID4gICAgICAgICBTb21lb25lIGNhbiBoZWxwIG1lPwo+ID4KPiA+ICAgICAgICAg
UmVnYXJkcywKPiA+ICAgICAgICAgwWRyaWFuIEztdmlvCj4gPiAgICAgICAgIFVuaXZlcnNpZGFk
ZSBGZWRlcmFsIGRlIENhbXBpbmEgR3JhbmRlIC0gVUZDRyAtCj4gPiAgICAgICAgIHd3dy51ZmNn
LmVkdS5icgo+ID4gICAgICAgICBDZW50cm8gZGUgRW5nZW5oYXJpYSBFbOl0cmljYSBlIEluZm9y
bWF0aWNhIC0gQ0VFSQo+ID4gICAgICAgICBVbmlkYWRlIEFjYWTqbWljYSBkZSBFbmdlbmhhcmlh
IEVs6XRyaWNhIC0gVUFFRSAtCj4gPiAgICAgICAgIHd3dy5lZS51ZmNnLmVkdS5icgo+ID4gICAg
ICAgICBMYWJvcmF083JpbyBkZSBTaXN0ZW1hcyBFbWJhcmNhZG9zIGUgQ29tcHV0YefjbyBQZXJ2
YXNpdmEgLQo+ID4gICAgICAgICB3d3cuZW1iZWRkZWRhY2FkZW15Lm9yZwo+ID4KPiA+Cj4gPgo+
Cj4KCgotLQrBZHJpYW4gTO12aW8KVW5pdmVyc2lkYWRlIEZlZGVyYWwgZGUgQ2FtcGluYSBHcmFu
ZGUgLSBVRkNHIC0gd3d3LnVmY2cuZWR1LmJyCkNlbnRybyBkZSBFbmdlbmhhcmlhIEVs6XRyaWNh
IGUgSW5mb3JtYXRpY2EgLSBDRUVJClVuaWRhZGUgQWNhZOptaWNhIGRlIEVuZ2VuaGFyaWEgRWzp
dHJpY2EgLSBVQUVFIC0gd3d3LmVlLnVmY2cuZWR1LmJyCkxhYm9yYXTzcmlvIGRlIFNpc3RlbWFz
IEVtYmFyY2Fkb3MgZSBDb21wdXRh5+NvIFBlcnZhc2l2YSAtCnd3dy5lbWJlZGRlZGFjYWRlbXku
b3JnCgotLS0tCgogICAgTuNvIGV4aXN0ZSBlbW/n428sIGUgc2ltIHBhei4KICAgIE7jbyBleGlz
dGUgaWdub3LibmNpYSwgZSBzaW0gY29uaGVjaW1lbnRvLgogICAgTuNvIGV4aXN0ZSBwYWl4428s
IGUgc2ltIHNlcmVuaWRhZGUuCiAgICBO428gZXhpc3RlIGNhb3MsIGUgc2ltIGhhcm1vbmlhLgog
ICAgTuNvIGV4aXN0ZSBtb3J0ZSwgZSBzaW0gYSBGb3LnYS4KICAgIJdPIEPzZGlnbyBKZWRpCgoK
CgoKCgoKRk5PUkQK

Re: [Opensync-users] SyncML over bluetooth/obex again

[<nhd...@gm...>]

Hi

   I'm trying to build the libyscml-threaded version,  I instaled the
libsoup-2.2.9, and patched the libwbxml with the patch in the
libyscml-threaded dir, I have also instaled the openobex-dev package, but
when I run the configure script:

./configure --prefix=3D/home/local/workspace/syncml-testdir
--with-wbxml=3D/home/local/workspace/syncml-testdir

   I got:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
  Unit Tests:             Enabled
  Tracing:                Enabled
  Tools:                  Enabled
  Libwbxml:               Enabled

The transports are:
  Http Client:            Enabled
  Http Server:            Enabled
  Obex Client:            Disabled
  Obex Server:            Disabled

Done configuring.
Please review the settings above
If they are ok, build libsyncml and install it.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

    I noticide that there is no openobex.pc file in /usr/lib/pkgconfig/ the=
n
I create one:

# Package Information for pkg-config

prefix=3D/usr
exec_prefix=3D${prefix}
libdir=3D${exec_prefix}/lib
includedir=3D${prefix}/include

Name: openobex
Description: openobex adricionado por mim
Version:1.0
Libs: -L${libdir} -lopenobex
Cflags: -I${includedir}

   but the configure script don't work, in the configure.ac file I noticed
that the required version is the 1.1,

PKG_CHECK_MODULES(LIBOPENOBEX, openobex >=3D 1.1, HAVE_OPENOBEX=3Dyes,
HAVE_OPENOBEX=3Dno)

Someone can help me?

Regards,
=C1drian L=EDvio
Universidade Federal de Campina Grande - UFCG - www.ufcg.edu.br
Centro de Engenharia El=E9trica e Informatica - CEEI
Unidade Acad=EAmica de Engenharia El=E9trica - UAEE - www.ee.ufcg.edu.br
Laborat=F3rio de Sistemas Embarcados e Computa=E7=E3o Pervasiva -
www.embeddedacademy.org


2006/1/28, Martin Schulze <mar...@hi...>:
>
> I've had a look at the libsyncml-threaded version this evening. From the
> sparse information that I could get, this seems to be the actively
> maintained branch. Attached are patches to this branch and the
> sycml-plugin from trunk.
>
> With these patches applied to current svn, sycml-plugin compiles and
> runs with the libyscml-threaded version. There is no ChangeLog, so I
> have enclosed a short description of the changes below.
>
> msynctool still doesn't work with my mobile phone. It doesn't seem to
> react on the SAN. I gather so much that SAN requires syncml 1.2 (at
> least the way it is currently implemented in libsyncml) and the SGH-D600
> only support syncml 1.1.
>
> Regards,
>
>   Martin
>
> _____________________________________________
>
> libsyncml-2006_01_29.diff:
>
>         libsyncml/sml_queue.c: Rename the callback functions. Before, the
> callback functions from libopensync/osengine/osengine_queue.c were
> called on my testing platform (leading to SEGFAULT).
>         libsyncml/sml_transport.c: Fix typo in the documentation.
>         libsyncml/sml_manager.c: Enhance _smlManagerDataHandler() to
> handle to
> only event type SML_TRANSPORT_EVENT_DATA. TODO: Probably, events of type
> SML_TRANSPORT_EVENT_CONNECT_DONE should also be forwarded to
> manager->eventCallback(). However, there is no SML_MANAGER* macro for
> this, yet.
>         smlManagerSessionRemove() now calls manager->eventCallback() with
> SML_MANAGER_SESSION_END.
>         smlManagerNew(): Fix typo.
>         libsyncml/sml_support.c: The idle callback doesn't get called whe=
n
> a
> new thread is started. Work around: _start_main_loop().
>
> syncml-plugin-2006_01_29.diff:
>
>         src/syncml_plugin.[hc]: Make it work with the libsyncml-threaded
> branch
> of libsyncml. Use smlManager to manage sessions. I'm not sure whether
> SmlDsSession is used correctly in batch_commit().
>         src/syncml-obex-client: Rename 'path' to 'url'. Add new parameter
> 'port'.
>
>
> Am Samstag, den 28.01.2006, 02:18 +0100 schrieb Martin Schulze:
> > Am Samstag, den 28.01.2006, 01:36 +0100 schrieb Martin Schulze:
> > > Am Freitag, den 27.01.2006, 12:43 -0200 schrieb =C1drian L=EDvio:
> > > > Hi
> > > >    I am also studing the libsyncml.
> > > >
> > > >    Which version of the libsyncml are you studing, the libsyncml
> > > > (trunk) or libsyncml-threaded (branch)?
> > >
> > > I have checked out the trunk version (following the instructions in
> the
> > > wiki). I will try the libsyncml-threaded version ...
> > >
> > > >    Do you have any problem building the lib?
> > >
> > > trunk compiles out-of-the-box.
> >
> > So does libsyncml-threaded (with current cvs versions of openobex and
> > libsoup). However, sycml-plugin doesn't compile with
> > libsyncml-threaded  ...
> >
> > Regards,
> >
> >   Martin
> >
> > > > Thanks.
> > > >
> > > > --
> > > > =C1drian L=EDvio
> > > > Universidade Federal de Campina Grande - UFCG - www.ufcg.edu.br
> > > > Centro de Engenharia El=E9trica e Informatica - CEEI
> > > > Unidade Acad=EAmica de Engenharia El=E9trica - UAEE - www.ee.ufcg.e=
du.br
> > > > Laborat=F3rio de Sistemas Embarcados e Computa=E7=E3o Pervasiva -
> > > > www.embeddedacademy.org
> > > >
> > > >
> > > > 2006/1/26, Martin Schulze <mar...@hi...>:
> > > >         I have the impression that the SGH-D600 doesn't support the
> > > >         full syncml
> > > >         specification. In particular,
> > > >         http://www.traud.de/gsm/samsung.htm names
> > > >         some restictions on the sync alert sent by the server.
> > > >         Therefore, I'm
> > > >         trying to gain a more detailed understanding of the
> libsyncml
> > > >         code.
> > > >
> > > >         Currently, I don't understand the following point:
> > > >
> > > >           libopensync obviously waits for a feedback on the
> > > >         notification request
> > > >         (which my mobile phone doesn't give; see last email). As fa=
r
>
> > > >         as I can
> > > >         gather from the code, the execution flow should be like
> this:
> > > >
> > > >           smlTransportReceive() -> smlSessionReceive() ->
> > > >         smlSessionDispatchCommand() -> [chain of callbacks] ->
> > > >         osync_context_report_success()
> > > >
> > > >         If osync_context_report_success() is not called within 60s
> > > >         after the
> > > >         notification request, a timeout error is reported (which is
> > > >         what I get).
> > > >
> > > >         However, even if the SGH-D600 _would_ send an answer, I
> don't
> > > >         understand
> > > >         how the above call chain can be triggered:
> > > >         smlTransportReceive() doesn't
> > > >         get called from the OBEX transport layer, neither gets
> > > >         smlDsServerRegister() which registers the first callback in
> > > >         [chain of
> > > >         callbacks]. (Both functions get called from the http
> transport
> > > >         layer.)
> > > >         Is the OBEX transport layer incomplete? Did I miss
> something?
> > > >
> > > >         Regards,
> > > >
> > > >           Martin
> > > >
> > > >
> > > >         Am Donnerstag, den 26.01.2006, 00:45 +0100 schrieb Martin
> > > >         Schulze:
> > > >         > $ msynctool --sync testsync --wait
> > > >         >                             ^^^^^^
> > > >         >
> > > >         > As it turns out, this was _not_ the way to go for the
> > > >         SGH-D600.
> > > >         >
> > > >         >
> > > >         > Instead, I had to insert a hack in
> > > >         >
> > > >         > libsyncml/libsyncml/transport/obex_client.c
> > > >         >
> > > >         > that sends an AT command
> > > >         >
> > > >         > AT+CPROT=3D0
> > > >         >
> > > >         > to the pseudo serial device and listens for the answer
> > > >         >
> > > >         > CONNECT
> > > >         >
> > > >         > _before_ sending the OBEX connect request. Then, the
> > > >         SGH-D600 answers
> > > >         > with a connect response with connection ID 2. Am OBEX put
> > > >         (final)
> > > >         > request follows and gets a success respone.
> > > >         >
> > > >         > Unfortunately, nothing more happens. After while,
> msynctool
> > > >         quits with
> > > >         > the message
> > > >         >
> > > >         > Member 2 of type syncml-obex-client had an error while
> > > >         connecting:
> > > >         > Timeout while waiting for a reply to message "CONNECT"
> > > >         > ...
> > > >         >
> > > >         > What exactly it is msynctool waiting for? Any ideas why i=
t
>
> > > >         doesn't get
> > > >         > what it awaits?
> > > >         >
> > > >         >
> > > >         > Regards,
> > > >         >
> > > >         >   Martin
> > > >         >
> > > >         >
> > > >         > Am Montag, den 23.01.2006, 17:47 +0100 schrieb Martin
> > > >         Schulze:
> > > >         > > $ msynctool --sync testsync --wait
> > > >         > >
> > > >         > > This doesn't seem to work for the Samsung - at least I
> > > >         have no idea how
> > > >         > > to initiate the sync from the SGH-D600, then, so the
> > > >         msynctool waits ad
> > > >         > > infinitum.
> > > >         > >
> > > >         > > What changes are needed in libsyncml to trigger the
> > > >         syncronization from
> > > >         > > the pc side?
> > > >         > >
> > > >         > > Regards,
> > > >         > >
> > > >         > >   Martin
> > > >         > >
> > > >         > >
> > > >         > > Am Montag, den 23.01.2006, 11:25 +0000 schrieb kevin
> > > >         james:
> > > >         > > > I've been trying to sync my Nokia 6680 with opensync,
> > > >         first trying the
> > > >         > > > syncml-http-server, until I realised that it is only
> > > >         inbound and my
> > > >         > > > laptop doesn't have a "real" IP address.
> > > >         > > >
> > > >         > > > Then I tried using the obex-client - some info on the
> > > >         mailing list
> > > >         > > > archive (from around November time) says it's still
> not
> > > >         working, don't
> > > >         > > > know if that's changed yet. Also I couldn't find any
> > > >         info on what the
> > > >         > > > config needs to be.
> > > >         > > >
> > > >         > > > One thing (I think) I did find out is that the
> > > >         obex-client is also
> > > >         > > > inbound only, so you will need to test it with:
> > > >         > > >
> > > >         > > > $ msynctool --sync testsync --wait
> > > >         > > >
> > > >         > > > so that it will wait for a connection.
> > > >         > > >
> > > >         > > > I am still having problems at the phone end trying to
> > > >         use bluetooth/obex
> > > >         > > > so I have no messages from opensync saying if anythin=
g
> > > >         has worked or
> > > >         > > > not. I saw someone mention that some of the devs have
> > > >         6680's - do any of
> > > >         > > > them have any advice?
> > > >         > > >
> > > >         > > > Cheers,
> > > >         > > > KEv.
> > > >         > > >
> > > >         > > >
> > > >         > > > On Mon, 2006-01-23 at 01:11 +0100, Martin Schulze
> wrote:
> > > >         > > > > Hi!
> > > >         > > > >
> > > >         > > > > Encouraged by
> > > >         > > > >
> > > >         > > > >
> > > >         http://sourceforge.net/mailarchive/forum.php?thread_id=3D94=
28612&forum_id=3D44467
>
> > > >         > > > >
> > > >         > > > > 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=3D8902424&forum_id=
=3D44467
> > > >         > > > >
> > > >         > > > > 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 clien=
t
> > > >         #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 messag=
e
> > > >         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? T=
o
> > > >         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 thin=
g
> > > >         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 fin=
d
> > > >         the correct values
> > > >         > > > > of the XXX_db parameters in the configuration of th=
e
> > > >         syncml-plugin?
> > > >         > > > >
> > > >         > > > > Regards,
> > > >         > > > >
> > > >         > > > >   Martin
> > > >         > > > >
> > > >         > > > >
> > > >         > > > >
> > > >         > > > >
> > > >         > > > >
> > > >         -------------------------------------------------------
> > > >         > > > > This SF.net email is sponsored by: Splunk Inc. Do
> you
> > > >         grep through log files
> > > >         > > > > for problems?  Stop!  Download the new AJAX search
> > > >         engine that makes
> > > >         > > > > searching your log files as easy as surfing
> > > >         the  web.  DOWNLOAD SPLUNK!
> > > >         > > > >
> > > >
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> > > >         > > > > _______________________________________________
> > > >         > > > > Opensync-users mailing list
> > > >         > > > > Ope...@li...
> > > >         > > > >
> > > >         https://lists.sourceforge.net/lists/listinfo/opensync-users
> > > >         > > > >
> > > >         > > >
> > > >         > >
> > > >         > >
> > > >         > >
> > > >         > > -------------------------------------------------------
> > > >         > > This SF.net email is sponsored by: Splunk Inc. Do you
> grep
> > > >         through log files
> > > >         > > for problems?  Stop!  Download the new AJAX search
> engine
> > > >         that makes
> > > >         > > searching your log files as easy as surfing
> > > >         the  web.  DOWNLOAD SPLUNK!
> > > >         > >
> > > >
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> > > >         > > _______________________________________________
> > > >         > > Opensync-users mailing list
> > > >         > > Ope...@li...
> > > >         > >
> > > >         https://lists.sourceforge.net/lists/listinfo/opensync-users
> > > >         >
> > > >         >
> > > >         >
> > > >         > -------------------------------------------------------
> > > >         > This SF.net email is sponsored by: Splunk Inc. Do you gre=
p
> > > >         through log files
> > > >         > for problems?  Stop!  Download the new AJAX search engine
> > > >         that makes
> > > >         > searching your log files as easy as surfing
> > > >         the  web.  DOWNLOAD SPLUNK!
> > > >         >
> > > >
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> > > >         > _______________________________________________
> > > >         > Opensync-users mailing list
> > > >         > Ope...@li...
> > > >         >
> https://lists.sourceforge.net/lists/listinfo/opensync-users
> > > >
> > > >
> > > >
> > > >         -------------------------------------------------------
> > > >         This SF.net email is sponsored by: Splunk Inc. Do you grep
> > > >         through log files
> > > >         for problems?  Stop!  Download the new AJAX search engine
> that
> > > >         makes
> > > >         searching your log files as easy as surfing
> > > >         the  web.  DOWNLOAD SPLUNK!
> > > >
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> > > >         _______________________________________________
> > > >         Opensync-users mailing list
> > > >         Ope...@li...
> > > >         https://lists.sourceforge.net/lists/listinfo/opensync-users
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through lo=
g
> files
> > > for problems?  Stop!  Download the new AJAX search engine that makes
> > > searching your log files as easy as surfing the  web.  DOWNLOAD
> SPLUNK!
> > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=121=
642<http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid%103432&bid#0486&dat%12164=
2>
> > > _______________________________________________
> > > Opensync-users mailing list
> > > Ope...@li...
> > > https://lists.sourceforge.net/lists/listinfo/opensync-users
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=12164=
2<http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid%103432&bid#0486&dat%121642>
> > _______________________________________________
> > Opensync-users mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensync-users
>
>
>

Re: [Opensync-users] SyncML over bluetooth/obex again

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

You need a recent cvs checkout of openobex.

Martin


Am Montag, den 30.01.2006, 15:27 -0200 schrieb =C1drian L=EDvio:
> Hi=20
>=20
>    I'm trying to build the libyscml-threaded version,  I instaled the
> libsoup-2.2.9, and patched the libwbxml with the patch in the
> libyscml-threaded dir, I have also instaled the openobex-dev package,
> but when I run the configure script:
>=20
> ./configure --prefix=3D/home/local/workspace/syncml-testdir
> --with-wbxml=3D/home/local/workspace/syncml-testdir
>=20
>    I got:
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>   Unit Tests:             Enabled
>   Tracing:                Enabled
>   Tools:                  Enabled
>   Libwbxml:               Enabled
>=20
> The transports are:
>   Http Client:            Enabled
>   Http Server:            Enabled
>   Obex Client:            Disabled
>   Obex Server:            Disabled
>=20
> Done configuring.
> Please review the settings above
> If they are ok, build libsyncml and install it.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>     I noticide that there is no openobex.pc file
> in /usr/lib/pkgconfig/ then I create one:
>=20
> # Package Information for pkg-config
>=20
> prefix=3D/usr
> exec_prefix=3D${prefix}
> libdir=3D${exec_prefix}/lib
> includedir=3D${prefix}/include
>=20
> Name: openobex
> Description: openobex adricionado por mim
> Version:1.0
> Libs: -L${libdir} -lopenobex
> Cflags: -I${includedir}
>=20
>    but the configure script don't work, in the configure.ac file I
> noticed that the required version is the 1.1,
>=20
> PKG_CHECK_MODULES(LIBOPENOBEX, openobex >=3D 1.1, HAVE_OPENOBEX=3Dyes,
> HAVE_OPENOBEX=3Dno)
>=20
> Someone can help me?
>=20
> Regards,=20
> =C1drian L=EDvio
> Universidade Federal de Campina Grande - UFCG - www.ufcg.edu.br
> Centro de Engenharia El=E9trica e Informatica - CEEI=20
> Unidade Acad=EAmica de Engenharia El=E9trica - UAEE - www.ee.ufcg.edu.br
> Laborat=F3rio de Sistemas Embarcados e Computa=E7=E3o Pervasiva -
> www.embeddedacademy.org
>=20
> 2006/1/28, Martin Schulze <mar...@hi...>:
>         I've had a look at the libsyncml-threaded version this
>         evening. From the
>         sparse information that I could get, this seems to be the
>         actively
>         maintained branch. Attached are patches to this branch and the
>         sycml-plugin from trunk.=20
>        =20
>         With these patches applied to current svn, sycml-plugin
>         compiles and
>         runs with the libyscml-threaded version. There is no
>         ChangeLog, so I
>         have enclosed a short description of the changes below.
>        =20
>         msynctool still doesn't work with my mobile phone. It doesn't
>         seem to=20
>         react on the SAN. I gather so much that SAN requires syncml
>         1.2 (at
>         least the way it is currently implemented in libsyncml) and
>         the SGH-D600
>         only support syncml 1.1.
>        =20
>         Regards,
>        =20
>           Martin
>        =20
>         _____________________________________________=20
>        =20
>         libsyncml-2006_01_29.diff:
>        =20
>                 libsyncml/sml_queue.c: Rename the callback functions.
>         Before, the
>         callback functions from libopensync/osengine/osengine_queue.c
>         were
>         called on my testing platform (leading to SEGFAULT).=20
>                 libsyncml/sml_transport.c: Fix typo in the
>         documentation.
>                 libsyncml/sml_manager.c: Enhance
>         _smlManagerDataHandler() to handle to
>         only event type SML_TRANSPORT_EVENT_DATA. TODO: Probably,
>         events of type=20
>         SML_TRANSPORT_EVENT_CONNECT_DONE should also be forwarded to
>         manager->eventCallback(). However, there is no SML_MANAGER*
>         macro for
>         this, yet.
>                 smlManagerSessionRemove() now calls
>         manager->eventCallback() with=20
>         SML_MANAGER_SESSION_END.
>                 smlManagerNew(): Fix typo.
>                 libsyncml/sml_support.c: The idle callback doesn't get
>         called when a
>         new thread is started. Work around: _start_main_loop().
>        =20
>         syncml-plugin-2006_01_29.diff:=20
>        =20
>                 src/syncml_plugin.[hc]: Make it work with the
>         libsyncml-threaded branch
>         of libsyncml. Use smlManager to manage sessions. I'm not sure
>         whether
>         SmlDsSession is used correctly in batch_commit().
>                 src/syncml-obex-client: Rename 'path' to 'url'. Add
>         new parameter=20
>         'port'.
>        =20
>        =20
>         Am Samstag, den 28.01.2006, 02:18 +0100 schrieb Martin
>         Schulze:
>         > Am Samstag, den 28.01.2006, 01:36 +0100 schrieb Martin
>         Schulze:
>         > > Am Freitag, den 27.01.2006, 12:43 -0200 schrieb =C1drian
>         L=EDvio:=20
>         > > > Hi
>         > > >    I am also studing the libsyncml.
>         > > >
>         > > >    Which version of the libsyncml are you studing, the
>         libsyncml
>         > > > (trunk) or libsyncml-threaded (branch)?=20
>         > >
>         > > I have checked out the trunk version (following the
>         instructions in the
>         > > wiki). I will try the libsyncml-threaded version ...
>         > >
>         > > >    Do you have any problem building the lib?=20
>         > >
>         > > trunk compiles out-of-the-box.
>         >
>         > So does libsyncml-threaded (with current cvs versions of
>         openobex and
>         > libsoup). However, sycml-plugin doesn't compile with
>         > libsyncml-threaded  ...=20
>         >
>         > Regards,
>         >
>         >   Martin
>         >
>         > > > Thanks.
>         > > >
>         > > > --
>         > > > =C1drian L=EDvio
>         > > > Universidade Federal de Campina Grande - UFCG -
>         www.ufcg.edu.br
>         > > > Centro de Engenharia El=E9trica e Informatica - CEEI
>         > > > Unidade Acad=EAmica de Engenharia El=E9trica - UAEE -
>         www.ee.ufcg.edu.br
>         > > > Laborat=F3rio de Sistemas Embarcados e Computa=E7=E3o
>         Pervasiva -
>         > > > www.embeddedacademy.org
>         > > >
>         > > >=20
>         > > > 2006/1/26, Martin Schulze <mar...@hi...>:
>         > > >         I have the impression that the SGH-D600 doesn't
>         support the=20
>         > > >         full syncml=20
>         > > >         specification. In particular,
>         > > >         http://www.traud.de/gsm/samsung.htm names
>         > > >         some restictions on the sync alert sent by the
>         server.=20
>         > > >         Therefore, I'm
>         > > >         trying to gain a more detailed understanding of
>         the libsyncml
>         > > >         code.
>         > > >
>         > > >         Currently, I don't understand the following
>         point:=20
>         > > >
>         > > >           libopensync obviously waits for a feedback on
>         the
>         > > >         notification request
>         > > >         (which my mobile phone doesn't give; see last
>         email). As far=20
>         > > >         as I can
>         > > >         gather from the code, the execution flow should
>         be like this:
>         > > >
>         > > >           smlTransportReceive() -> smlSessionReceive()
>         ->=20
>         > > >         smlSessionDispatchCommand() -> [chain of
>         callbacks] ->
>         > > >         osync_context_report_success()
>         > > >
>         > > >         If osync_context_report_success() is not called
>         within 60s=20
>         > > >         after the
>         > > >         notification request, a timeout error is
>         reported (which is
>         > > >         what I get).
>         > > >
>         > > >         However, even if the SGH-D600 _would_ send an
>         answer, I don't=20
>         > > >         understand
>         > > >         how the above call chain can be triggered:
>         > > >         smlTransportReceive() doesn't
>         > > >         get called from the OBEX transport layer,
>         neither gets=20
>         > > >         smlDsServerRegister() which registers the first
>         callback in
>         > > >         [chain of
>         > > >         callbacks]. (Both functions get called from the
>         http transport
>         > > >         layer.)=20
>         > > >         Is the OBEX transport layer incomplete? Did I
>         miss something?
>         > > >
>         > > >         Regards,
>         > > >
>         > > >           Martin
>         > > >
>         > > >=20
>         > > >         Am Donnerstag, den 26.01.2006, 00:45 +0100
>         schrieb Martin
>         > > >         Schulze:
>         > > >         > $ msynctool --sync testsync --wait
>         > > >         >                             ^^^^^^
>         > > >         >
>         > > >         > As it turns out, this was _not_ the way to go
>         for the
>         > > >         SGH-D600.
>         > > >         >
>         > > >         >=20
>         > > >         > Instead, I had to insert a hack in
>         > > >         >
>         > > >         > libsyncml/libsyncml/transport/obex_client.c
>         > > >         >
>         > > >         > that sends an AT command=20
>         > > >         >
>         > > >         > AT+CPROT=3D0
>         > > >         >
>         > > >         > to the pseudo serial device and listens for
>         the answer
>         > > >         >=20
>         > > >         > CONNECT
>         > > >         >
>         > > >         > _before_ sending the OBEX connect request.
>         Then, the
>         > > >         SGH-D600 answers
>         > > >         > with a connect response with connection ID 2.
>         Am OBEX put=20
>         > > >         (final)
>         > > >         > request follows and gets a success respone.
>         > > >         >
>         > > >         > Unfortunately, nothing more happens. After
>         while, msynctool=20
>         > > >         quits with
>         > > >         > the message
>         > > >         >
>         > > >         > Member 2 of type syncml-obex-client had an
>         error while
>         > > >         connecting:=20
>         > > >         > Timeout while waiting for a reply to message
>         "CONNECT"
>         > > >         > ...
>         > > >         >
>         > > >         > What exactly it is msynctool waiting for? Any
>         ideas why it=20
>         > > >         doesn't get
>         > > >         > what it awaits?
>         > > >         >
>         > > >         >
>         > > >         > Regards,
>         > > >         >
>         > > >         >   Martin
>         > > >         >
>         > > >         >
>         > > >         > Am Montag, den 23.01.2006, 17:47 +0100 schrieb
>         Martin
>         > > >         Schulze:
>         > > >         > > $ msynctool --sync testsync --wait
>         > > >         > >
>         > > >         > > This doesn't seem to work for the Samsung -
>         at least I
>         > > >         have no idea how=20
>         > > >         > > to initiate the sync from the SGH-D600,
>         then, so the
>         > > >         msynctool waits ad
>         > > >         > > infinitum.
>         > > >         > >
>         > > >         > > What changes are needed in libsyncml to
>         trigger the
>         > > >         syncronization from
>         > > >         > > the pc side?
>         > > >         > >
>         > > >         > > Regards,=20
>         > > >         > >
>         > > >         > >   Martin
>         > > >         > >
>         > > >         > >
>         > > >         > > Am Montag, den 23.01.2006, 11:25 +0000
>         schrieb kevin=20
>         > > >         james:
>         > > >         > > > I've been trying to sync my Nokia 6680
>         with opensync,
>         > > >         first trying the
>         > > >         > > > syncml-http-server, until I realised that
>         it is only
>         > > >         inbound and my
>         > > >         > > > laptop doesn't have a "real" IP address.
>         > > >         > > >=20
>         > > >         > > > Then I tried using the obex-client - some
>         info on the
>         > > >         mailing list
>         > > >         > > > archive (from around November time) says
>         it's still not
>         > > >         working, don't
>         > > >         > > > know if that's changed yet. Also I
>         couldn't find any
>         > > >         info on what the
>         > > >         > > > config needs to be.
>         > > >         > > >
>         > > >         > > > One thing (I think) I did find out is that
>         the=20
>         > > >         obex-client is also
>         > > >         > > > inbound only, so you will need to test it
>         with:
>         > > >         > > >
>         > > >         > > > $ msynctool --sync testsync --wait=20
>         > > >         > > >
>         > > >         > > > so that it will wait for a connection.
>         > > >         > > >
>         > > >         > > > I am still having problems at the phone
>         end trying to
>         > > >         use bluetooth/obex
>         > > >         > > > so I have no messages from opensync saying
>         if anything
>         > > >         has worked or
>         > > >         > > > not. I saw someone mention that some of
>         the devs have
>         > > >         6680's - do any of
>         > > >         > > > them have any advice?
>         > > >         > > >
>         > > >         > > > Cheers,=20
>         > > >         > > > KEv.
>         > > >         > > >
>         > > >         > > >
>         > > >         > > > On Mon, 2006-01-23 at 01:11 +0100, Martin
>         Schulze wrote:
>         > > >         > > > > Hi!
>         > > >         > > > >
>         > > >         > > > > Encouraged by
>         > > >         > > > >
>         > > >         > > > >
>         > > >
>         http://sourceforge.net/mailarchive/forum.php?thread_id=3D9428612&=
forum_id=3D44467
>         > > >         > > > >
>         > > >         > > > > I've configured a synchronizing group
>         between my
>         > > >         evolution environment
>         > > >         > > > > (plugin evo2-sync) and /dev/rfcomm0
>         (plugin
>         > > >         syncml-obex-client) which is=20
>         > > >         > > > > 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:
>         > > >         > > > >=20
>         > > >         > > > > <config>
>         > > >         > > > >   <username></username>
>         > > >         > > > >   <password></password>=20
>         > > >         > > > >   <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=3D8902424&=
forum_id=3D44467
>         > > >         > > > >
>         > > >         > > > > E.i.
>         > > >         > > > >=20
>         > > >         > > > > $ msynctool --sync testsync
>         > > >         > > > >
>         > > >         > > > > yields:
>         > > >         > > > >=20
>         > > >         > > > > 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=20
>         > > >         > > > > 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]
>         > > >         >>>>>>>=20
>         > > >         > > > >
>         osync_context_report_osyncerror(0x8077e08,
>         > > >         0xb6b99244:(No success))
>         > > >         > > > > [1137969741.854070]
>         > > >         [CLI] WARNING:=20
>         > > >         > > > > 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=20
>         > > >         > > > > [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
>         > > >         > > > >=20
>         > > >         > > > > 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,
>         > > >         > > > >=20
>         > > >         > > > >   Martin
>         > > >         > > > >
>         > > >         > > > >
>         > > >         > > > >
>         > > >         > > > >=20
>         > > >         > > > >
>         > > >
>         -------------------------------------------------------
>         > > >         > > > > This SF.net email is sponsored by:
>         Splunk Inc. Do you
>         > > >         grep through log files
>         > > >         > > > > for problems?  Stop!  Download the new
>         AJAX search
>         > > >         engine that makes
>         > > >         > > > > searching your log files as easy as
>         surfing
>         > > >         the  web.  DOWNLOAD SPLUNK!
>         > > >         > > > >=20
>         > > >
>         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D2304=
86&dat=3D121642
>         > > >         > > > >
>         _______________________________________________=20
>         > > >         > > > > Opensync-users mailing list
>         > > >         > > > > Ope...@li...
>         > > >         > > > >=20
>         > > >
>         https://lists.sourceforge.net/lists/listinfo/opensync-users
>         > > >         > > > >
>         > > >         > > >=20
>         > > >         > >
>         > > >         > >
>         > > >         > >
>         > > >         > >
>         -------------------------------------------------------
>         > > >         > > This SF.net email is sponsored by: Splunk
>         Inc. Do you grep
>         > > >         through log files
>         > > >         > > for problems?  Stop!  Download the new AJAX
>         search engine
>         > > >         that makes
>         > > >         > > searching your log files as easy as surfing
>         > > >         the  web.  DOWNLOAD SPLUNK!
>         > > >         > >
>         > > >
>         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D2304=
86&dat=3D121642
>         > > >         > >
>         _______________________________________________=20
>         > > >         > > Opensync-users mailing list
>         > > >         > > Ope...@li...
>         > > >         > >=20
>         > > >
>         https://lists.sourceforge.net/lists/listinfo/opensync-users
>         > > >         >
>         > > >         >=20
>         > > >         >
>         > > >         >
>         -------------------------------------------------------
>         > > >         > This SF.net email is sponsored by: Splunk Inc.
>         Do you grep
>         > > >         through log files=20
>         > > >         > for problems?  Stop!  Download the new AJAX
>         search engine
>         > > >         that makes
>         > > >         > searching your log files as easy as surfing
>         > > >         the  web.  DOWNLOAD SPLUNK!
>         > > >         >
>         > > >
>         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D2304=
86&dat=3D121642
>         > > >         >
>         _______________________________________________=20
>         > > >         > Opensync-users mailing list
>         > > >         > Ope...@li...
>         > > >         >
>         https://lists.sourceforge.net/lists/listinfo/opensync-users
>         > > >
>         > > >
>         > > >
>         > > >
>         -------------------------------------------------------
>         > > >         This SF.net email is sponsored by: Splunk Inc.
>         Do you grep
>         > > >         through log files
>         > > >         for problems?  Stop!  Download the new AJAX
>         search engine that
>         > > >         makes
>         > > >         searching your log files as easy as surfing
>         > > >         the  web.  DOWNLOAD SPLUNK!
>         > > >
>         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D2304=
86&dat=3D121642
>         > > >         _______________________________________________
>         > > >         Opensync-users mailing list
>         > > >         Ope...@li...
>         > > >
>         https://lists.sourceforge.net/lists/listinfo/opensync-users
>         > > >
>         > > >
>         > > >
>         > > >
>         > >
>         > >
>         > >
>         > > -------------------------------------------------------
>         > > This SF.net email is sponsored by: Splunk Inc. Do you grep
>         through log files=20
>         > > for problems?  Stop!  Download the new AJAX search engine
>         that makes
>         > > searching your log files as easy as surfing
>         the  web.  DOWNLOAD SPLUNK!
>         > >
>         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=
=121642
>         > > _______________________________________________
>         > > Opensync-users mailing list
>         > > Ope...@li...
>         > >
>         https://lists.sourceforge.net/lists/listinfo/opensync-users
>         >
>         >
>         >
>         > -------------------------------------------------------=20
>         > This SF.net email is sponsored by: Splunk Inc. Do you grep
>         through log files
>         > for problems?  Stop!  Download the new AJAX search engine
>         that makes
>         > searching your log files as easy as surfing
>         the  web.  DOWNLOAD SPLUNK!=20
>         >
>         http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=
=121642
>         > _______________________________________________=20
>         > Opensync-users mailing list
>         > Ope...@li...
>         > https://lists.sourceforge.net/lists/listinfo/opensync-users
>        =20
>        =20
>=20

Re: [Opensync-users] SyncML over bluetooth/obex again

[Armin B. <arm...@de...>]

Hi,

thanks for the patches! i will integrate them in libsyncml branch and
the plugin once i find some time (probably means: after my exams :)

Martin Schulze wrote:
> I've had a look at the libsyncml-threaded version this evening. From the
> sparse information that I could get, this seems to be the actively
> maintained branch. 

That is correct. All development is currently done in the threaded-branch.

> Attached are patches to this branch and the
> sycml-plugin from trunk.
> 
> With these patches applied to current svn, sycml-plugin compiles and
> runs with the libyscml-threaded version. There is no ChangeLog, so I
> have enclosed a short description of the changes below.
> 
> msynctool still doesn't work with my mobile phone. It doesn't seem to
> react on the SAN. I gather so much that SAN requires syncml 1.2 (at
> least the way it is currently implemented in libsyncml) and the SGH-D600
> only support syncml 1.1.

SAN was not defined prior to syncml 1.2 so there is no chance that a 1.1
phone can make any sense of it. in syncml 1.1 you just have to send a
normal alert to the phone to trigger the synchronization. I havent
tested yet if this is correctly done (at least not with a real phone).

> 
> Regards,
> 
>   Martin
> 
> _____________________________________________
> 
> libsyncml-2006_01_29.diff:
> 
> 	libsyncml/sml_queue.c: Rename the callback functions. Before, the
> callback functions from libopensync/osengine/osengine_queue.c were
> called on my testing platform (leading to SEGFAULT).

right. i think we should declare them static so that naming conflicts
like this cannot happen (or use the proper prefix)

> 	libsyncml/sml_transport.c: Fix typo in the documentation.
> 	libsyncml/sml_manager.c: Enhance _smlManagerDataHandler() to handle to
> only event type SML_TRANSPORT_EVENT_DATA. TODO: Probably, events of type
> SML_TRANSPORT_EVENT_CONNECT_DONE should also be forwarded to
> manager->eventCallback(). However, there is no SML_MANAGER* macro for
> this, yet.
> 	smlManagerSessionRemove() now calls manager->eventCallback() with
> SML_MANAGER_SESSION_END.
> 	smlManagerNew(): Fix typo.
> 	libsyncml/sml_support.c: The idle callback doesn't get called when a
> new thread is started. Work around: _start_main_loop().

i dont really understand why this is necessary. i used this code quite
often now and it worked very well.

> 
> syncml-plugin-2006_01_29.diff:
> 
> 	src/syncml_plugin.[hc]: Make it work with the libsyncml-threaded branch
> of libsyncml. Use smlManager to manage sessions. I'm not sure whether
> SmlDsSession is used correctly in batch_commit().

looks ok from the very first glance. the idea is that the syncml session
is used to control the commands that are sent and received. it also
handles stuff like the fragmentation. then there might be one or more
datasync session inside the syncml session where each ds session is
responsible for synchronizing a single format. so a synchronization
looks like this:

-> the syncml session is received
-> the ds servers get called and return the ds session(s)
-> the work is done on the ds sessions (like requesting data, sending
changes etc).
-> once each step is called for all ds sessions you call smlSessionFlush
to flush all remaining commands in the syncml session

Best Regards,
Armin Bauer

> 	src/syncml-obex-client: Rename 'path' to 'url'. Add new parameter
> 'port'.
> 

Re: [Opensync-users] SyncML over bluetooth/obex again

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

More comprehensive patches including server alerts compliant to SyncML
1.1 are now in ticket #146. The problem with the idle command I don't
understand either. I will look at it again this weekend.


Am Donnerstag, den 02.02.2006, 02:12 +0100 schrieb Armin Bauer:
> Hi,
> 
> thanks for the patches! i will integrate them in libsyncml branch and
> the plugin once i find some time (probably means: after my exams :)
> 
> Martin Schulze wrote:
> > I've had a look at the libsyncml-threaded version this evening. From the
> > sparse information that I could get, this seems to be the actively
> > maintained branch. 
> 
> That is correct. All development is currently done in the threaded-branch.
> 
> > Attached are patches to this branch and the
> > sycml-plugin from trunk.
> > 
> > With these patches applied to current svn, sycml-plugin compiles and
> > runs with the libyscml-threaded version. There is no ChangeLog, so I
> > have enclosed a short description of the changes below.
> > 
> > msynctool still doesn't work with my mobile phone. It doesn't seem to
> > react on the SAN. I gather so much that SAN requires syncml 1.2 (at
> > least the way it is currently implemented in libsyncml) and the SGH-D600
> > only support syncml 1.1.
> 
> SAN was not defined prior to syncml 1.2 so there is no chance that a 1.1
> phone can make any sense of it. in syncml 1.1 you just have to send a
> normal alert to the phone to trigger the synchronization. I havent
> tested yet if this is correctly done (at least not with a real phone).
> 
> > 
> > Regards,
> > 
> >   Martin
> > 
> > _____________________________________________
> > 
> > libsyncml-2006_01_29.diff:
> > 
> > 	libsyncml/sml_queue.c: Rename the callback functions. Before, the
> > callback functions from libopensync/osengine/osengine_queue.c were
> > called on my testing platform (leading to SEGFAULT).
> 
> right. i think we should declare them static so that naming conflicts
> like this cannot happen (or use the proper prefix)
> 
> > 	libsyncml/sml_transport.c: Fix typo in the documentation.
> > 	libsyncml/sml_manager.c: Enhance _smlManagerDataHandler() to handle to
> > only event type SML_TRANSPORT_EVENT_DATA. TODO: Probably, events of type
> > SML_TRANSPORT_EVENT_CONNECT_DONE should also be forwarded to
> > manager->eventCallback(). However, there is no SML_MANAGER* macro for
> > this, yet.
> > 	smlManagerSessionRemove() now calls manager->eventCallback() with
> > SML_MANAGER_SESSION_END.
> > 	smlManagerNew(): Fix typo.
> > 	libsyncml/sml_support.c: The idle callback doesn't get called when a
> > new thread is started. Work around: _start_main_loop().
> 
> i dont really understand why this is necessary. i used this code quite
> often now and it worked very well.
> 
> > 
> > syncml-plugin-2006_01_29.diff:
> > 
> > 	src/syncml_plugin.[hc]: Make it work with the libsyncml-threaded branch
> > of libsyncml. Use smlManager to manage sessions. I'm not sure whether
> > SmlDsSession is used correctly in batch_commit().
> 
> looks ok from the very first glance. the idea is that the syncml session
> is used to control the commands that are sent and received. it also
> handles stuff like the fragmentation. then there might be one or more
> datasync session inside the syncml session where each ds session is
> responsible for synchronizing a single format. so a synchronization
> looks like this:
> 
> -> the syncml session is received
> -> the ds servers get called and return the ds session(s)
> -> the work is done on the ds sessions (like requesting data, sending
> changes etc).
> -> once each step is called for all ds sessions you call smlSessionFlush
> to flush all remaining commands in the syncml session
> 
> Best Regards,
> Armin Bauer
> 
> > 	src/syncml-obex-client: Rename 'path' to 'url'. Add new parameter
> > 'port'.
> > 

Re: [Opensync-users] SyncML over bluetooth/obex again

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

I have opened a discussion about the necessary changes to openobex on
their mailing list and patches tracker:

http://sourceforge.net/mailarchive/forum.php?forum_id=9713 (the archive
will need some hours to get in sync)
http://sourceforge.net/tracker/index.php?func=detail&aid=1424504&group_id=8960&atid=308960

Still, I have no idea, why the idle callback in sml_support.c is not
called after starting the new thread. Maybe a bug in glib? I'm using
version 2.8.6.

Regards,

  Martin


Am Donnerstag, den 02.02.2006, 09:41 +0100 schrieb Martin Schulze:
> More comprehensive patches including server alerts compliant to SyncML
> 1.1 are now in ticket #146. The problem with the idle command I don't
> understand either. I will look at it again this weekend.
> 
> 
> Am Donnerstag, den 02.02.2006, 02:12 +0100 schrieb Armin Bauer:
> > Hi,
> > 
> > thanks for the patches! i will integrate them in libsyncml branch and
> > the plugin once i find some time (probably means: after my exams :)
> > 
> > Martin Schulze wrote:
> > > I've had a look at the libsyncml-threaded version this evening. From the
> > > sparse information that I could get, this seems to be the actively
> > > maintained branch. 
> > 
> > That is correct. All development is currently done in the threaded-branch.
> > 
> > > Attached are patches to this branch and the
> > > sycml-plugin from trunk.
> > > 
> > > With these patches applied to current svn, sycml-plugin compiles and
> > > runs with the libyscml-threaded version. There is no ChangeLog, so I
> > > have enclosed a short description of the changes below.
> > > 
> > > msynctool still doesn't work with my mobile phone. It doesn't seem to
> > > react on the SAN. I gather so much that SAN requires syncml 1.2 (at
> > > least the way it is currently implemented in libsyncml) and the SGH-D600
> > > only support syncml 1.1.
> > 
> > SAN was not defined prior to syncml 1.2 so there is no chance that a 1.1
> > phone can make any sense of it. in syncml 1.1 you just have to send a
> > normal alert to the phone to trigger the synchronization. I havent
> > tested yet if this is correctly done (at least not with a real phone).
> > 
> > > 
> > > Regards,
> > > 
> > >   Martin
> > > 
> > > _____________________________________________
> > > 
> > > libsyncml-2006_01_29.diff:
> > > 
> > > 	libsyncml/sml_queue.c: Rename the callback functions. Before, the
> > > callback functions from libopensync/osengine/osengine_queue.c were
> > > called on my testing platform (leading to SEGFAULT).
> > 
> > right. i think we should declare them static so that naming conflicts
> > like this cannot happen (or use the proper prefix)
> > 
> > > 	libsyncml/sml_transport.c: Fix typo in the documentation.
> > > 	libsyncml/sml_manager.c: Enhance _smlManagerDataHandler() to handle to
> > > only event type SML_TRANSPORT_EVENT_DATA. TODO: Probably, events of type
> > > SML_TRANSPORT_EVENT_CONNECT_DONE should also be forwarded to
> > > manager->eventCallback(). However, there is no SML_MANAGER* macro for
> > > this, yet.
> > > 	smlManagerSessionRemove() now calls manager->eventCallback() with
> > > SML_MANAGER_SESSION_END.
> > > 	smlManagerNew(): Fix typo.
> > > 	libsyncml/sml_support.c: The idle callback doesn't get called when a
> > > new thread is started. Work around: _start_main_loop().
> > 
> > i dont really understand why this is necessary. i used this code quite
> > often now and it worked very well.
> > 
> > > 
> > > syncml-plugin-2006_01_29.diff:
> > > 
> > > 	src/syncml_plugin.[hc]: Make it work with the libsyncml-threaded branch
> > > of libsyncml. Use smlManager to manage sessions. I'm not sure whether
> > > SmlDsSession is used correctly in batch_commit().
> > 
> > looks ok from the very first glance. the idea is that the syncml session
> > is used to control the commands that are sent and received. it also
> > handles stuff like the fragmentation. then there might be one or more
> > datasync session inside the syncml session where each ds session is
> > responsible for synchronizing a single format. so a synchronization
> > looks like this:
> > 
> > -> the syncml session is received
> > -> the ds servers get called and return the ds session(s)
> > -> the work is done on the ds sessions (like requesting data, sending
> > changes etc).
> > -> once each step is called for all ds sessions you call smlSessionFlush
> > to flush all remaining commands in the syncml session
> > 
> > Best Regards,
> > Armin Bauer
> > 
> > > 	src/syncml-obex-client: Rename 'path' to 'url'. Add new parameter
> > > 'port'.
> > > 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users