Menu
▾
▴
Re: [Opensync-users] SyncML over bluetooth/obex again
|
From: Martin S. <mar...@hi...> - 2006-01-28 01:18:36
|
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 |
