Menu

#65 Synchronisation with mobical.net fails

closed-out-of-date
5
2009-05-14
2009-02-10
dmaphy
No

Problem description:

I can not see all data which should be synchronized. E.g. when synchronizing the addressbook, syncevolution successfully uploads all the contacts. When synchronizing my mobile (SEMC W880i) with mobical then, i can see all contacts from evolution. This is the expected behavior so far. But when doing this, the mobile uploads the contacts which were on the mobile before the first sync. Expected behavior too. Now i try syncing with syncevolution again to get the contacts from mobile to the PC. syncevolution now does nothing and the evolution addressbook doesn't change anything. I have attached the output from syncevolution, see addressbook.log.
As you can see there were no activities on client site. (I expected syncevolution would download data
from the mobile to client, so this should be listed there.)

I already have had some mail traffic with the mobical.net-Support a few weeks ago (They successfully fixed another server-side problem.). Regarding to this issue, i unfortunately got this answer:

----------
Hi,

There is a bug in syncevolution (it does not follow the SyncML protocol properly), this prevents the server from sending the contacts to syncevolution.
Unfortunately this is not trivial to patch on the server side and I don't think it will be done very soon (if at all).

BR
Björn
----------

Discussion

  • dmaphy

    dmaphy - 2009-02-10

    adressbook.log

     
  • Patrick Ohly

    Patrick Ohly - 2009-02-11

    I'm not surprised anymore that the Funambol SyncML client library has issues with non-Funambol servers, as Funambol only tests with Funambol. Usually I try to fix this myself when something comes up.

    As Bjoern seems to have identified the issue already, can you get me in touch with him? Please mail him with CC: patrick.ohly@gmx.de and a link to this issue, then I will continue the discussion with him.

     
  • Patrick Ohly

    Patrick Ohly - 2009-02-15

    Björn Isaksson correctly identified where the Funambol C++ client library replies incorrectly to the server. This confused the server enough to not send items to the client later on. This needs to be fixed in the client library.

    ------------------------
    This is the start of the first message from the server:
    <SyncML xmlns="SYNCML:SYNCML1.1">
    <SyncHdr>
    <VerDTD>1.1</VerDTD>
    <VerProto>SyncML/1.1</VerProto>
    <SessionID>1234464259</SessionID>
    <MsgID>1</MsgID>
    <Target><LocURI>sc-api-nat</LocURI></Target>
    <Source><LocURI>https://www.mobical.net/sync/server</LocURI></Source>
    <RespURI>https://www.mobical.net/sync/server;jsessionid=58E64F3845970485CFCFC24F0136F327?bsid=f1c81af5</RespURI>
    </SyncHdr>
    <SyncBody>...</SyncBody>
    </SyncML>

    An the start of the clients next message:
    [DEBUG] data out: <SyncML>
    [DEBUG] data out: <SyncHdr><VerDTD>1.1</VerDTD>
    [DEBUG] data out: <VerProto>SyncML/1.1</VerProto>
    [DEBUG] data out: <SessionID>1234464259</SessionID>
    [DEBUG] data out: <MsgID>2</MsgID>
    [DEBUG] data out: <Target><LocURI>https://www.mobical.net/sync/server</LocURI>
    [DEBUG] data out: </Target>
    [DEBUG] data out: <Source><LocURI>sc-api-nat</LocURI>
    [DEBUG] data out: </Source>
    [DEBUG] data out: </SyncHdr>
    [DEBUG] data out: <SyncBody><Status><CmdID>1</CmdID>
    [DEBUG] data out: <MsgRef>1</MsgRef>
    [DEBUG] data out: <CmdRef>0</CmdRef>
    [DEBUG] data out: <Cmd>SyncHdr</Cmd>
    [DEBUG] data out: <TargetRef>https://www.mobical.net/sync/server</TargetRef>
    [DEBUG] data out: <SourceRef>sc-api-nat</SourceRef>
    [DEBUG] data out: <Data>200</Data>
    [DEBUG] data out: </Status>
    ...

    Target and source reference should be:
    <TargetRef>sc-api-nat</TargetRef>
    <SourceRef>https://www.mobical.net/sync/server</SourceRef>
    The target reference refers to the Target of the command/item the Status is for, the same goes for source ref.
    ------------------------

     
  • dmaphy

    dmaphy - 2009-02-23

    So, since this client library is from funambol if i understood that correctly, is there something to be done do let the funambol-developers know? E.g. should i file a bug there or something?

     
  • Nobody/Anonymous

    I reported the problem on the Funambol dev list and Funambol acknowledged that this is a generic problem in the client library. You might also report it in the Funambol bug tracker, as a reminder.

     
  • Patrick Ohly

    Patrick Ohly - 2009-05-14
    • status: open --> closed-out-of-date
     
  • Patrick Ohly

    Patrick Ohly - 2009-05-14

    This should no longer occur with 0.9 beta 1, which switched to the Synthesis SyncML Engine.

     

Log in to post a comment.