[turba] additional contact fields and activesync
Simon Brereton
simon.brereton at dada.net
Wed May 4 17:08:46 UTC 2011
> -----Original Message-----
> From: turba-bounces at lists.horde.org [mailto:turba-
> bounces at lists.horde.org] On Behalf Of Michael Rubinsky
> Quoting Simon Brereton <simon.brereton at dada.net>:
>
> >> -----Original Message-----
> >> From: turba-bounces at lists.horde.org [mailto:turba-
> >> bounces at lists.horde.org] On Behalf Of Michael Rubinsky Quoting
> Simon
> >> Brereton <simon.brereton at dada.net>:
> > <SNIP>
> >> > Stellar work Michael - thanks!
> >> >
> >> > I have one more request - which probably belongs on the sync
> list
> >> (if
> >> > at all, I'm sure it's a client issue and that it shouldn't be
> the
> >> job
> >> > of the server to fix it, but I think I have more chance of a
> server
> >> > fix), so let me know if I should make a feature request
> somewhere..
> >> >
> >> > Essentially, I store all my contact numbers in the +1/+49/etc
> >> format.
> >> > Android, for reasons known only to itself likes to interpret
> only
> >> the
> >> > US numbers and add dashes (so that +1347xxxxxxx on the server
> >> becomes
> >> > +1-347-xxx-xxxx on the phone. Then when the phone tries to do
> >> another
> >> > sync it's duplicating the contacts in Turba. I could just let
> it
> >> and
> >> > delete all the contacts with the old format but this is untidy
> >> since
> >> > numbers from other countries remain
> >> > +49172xxxxxxx or +3462xxxxxx etc. Would it be possible to have
> >> > Turba (I guess) or Sync recognise that +1-347-xxx-xxxx is the
> same
> >> as
> >> > 1347xxxxxxx and not duplicate the contact?
> >>
> >> Contacts are identified by ActiveSync using the contact UID, not
> by
> >> the phone number. I just tried this locally, and I'm not seeing
> this
> >> behavior. I added a new contact in Turba with a phone number of
> >> +13471234567. It was synched to Android, with the dashes added,
> but
> >> was not duplicated in any way on the server or client.
> >
> > I confess I haven't been able to test it with H4/Turba3 yet. I
> should
> > have mentioned that I was using the Funambol client - sorry!
> > Connecting directly to rpc.php
>
> Now you have me completely confused. The fix this email is referring
> to is related to ActiveSync, not Funambol. And ActiveSync was only
> available since H4/Turba 3.
Yeah. Sorry - I should have started a new thread.
Let's leave this now. Once I've completed a migration, if I still have the issue I'll raise it properly.
Sorry again.
Simon
More information about the turba
mailing list