On Mo, 2011-04-11 at 22:06 +0100, Frederik Elwert wrote:
> I am currently looking for a Linux replacement for Gigaset QuickSync
> [1]. QuickSync is a tool to sync contacts with a cordless phone (not a
> cell phone). I thought SyncEvolution might be the obvious candidate for
> this.

I started some similar investigations with a Fritz!Box. The problem was
that that router/phone system doesn't even have locally unique IDs for
each contact, therefore change tracking is a bit difficult. I never
wrote any code for SyncEvolution, but it gave me some ideas. Not that I
have a lack of those... ;-)

> The cordless phone talks BlueTooth, but not SyncML. I just figured out
> that one can feed contacts to it by pushing 2.1 vCards one by one over
> BlueTooth. I am currently only interested Desktop → Phone sync. Since
> SyncEvolution over Bluetooth won’t work, I thought I could at least use
> SyncEvolution to convert my Evolution addressbook to a set of vCard
> files in 2.1 format.
> 
> As far as I understand, I’d normally need backend-to-backend sync
> (Evolution → file). IIRC, that’s not yet implemented.

It's implemented in 1.1.99.3. Here are some untested instructions:

Configure the file backend which will store the vCards:

        dir=<absolute path to vcard dir>
        mkdir -p $dir
        syncevolution --configure \
                      backend=file \
                      database=file://$dir \
                      databaseFormat=text/x-vcard \
                      @gigaset addressbook
        
Configure one-way synchronization from default system address book:

        syncevolution --configure \
                      syncURL=local://@gigaset \
                      peerIsClient=1 \
                      sync=one-way-from-server \
                      gigaset addressbook

Run a sync:

        syncevolution gigaset



>  So I thought about
> setting up a local SyncEvolution server with the file backend. But it
> seems that it isn’t possible to sync syncevolution with
> syncevo-http-server on the same machine.

Yes, that runs into issues with syncevo-dbus-server having to host two
sessions at the same time, which isn't supported. Local sync avoids that
limitation and doesn't depend on syncevo-http-server.


-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to