[turba] additional contact fields and activesync

[Michael J Rubinsky]

Ulli <ulli_um at arcor.de> wrote:

>
>Why do we not go with the following proposal of Simon Brereton
>
>email1 = Home
>email2 = Work
>email3 = Spare
>
>With this configuration the clients which supports preferred emails
>will identify the home address as preferred and work as additional. The
>other devices just show the two email entry.

The majority of Turba installs (and in fact the default SQL source uses this) only use a single email field, known simply as 'email'. I don't want to make assumptions about what email address this represents.


>Regarding the additional cell phone number. I have found the following
>two entry in the attributes.php file of turba/config.
>
>     $attributes['homePhone'] = array(
>         'label' => _("Home Phone"),
>         'type' => 'phone',
>         'required' => false
>     );
>     $attributes['workPhone'] = array(
>         'label' => _("Work Phone"),
>         'type' => 'phone',
>         'required' => false
>     );
>
Right, those are work and home phone numbers, both of which are already supported in our AS implementation.


>what is the "carPhone*" entry about? is this the additional field which
>
>will be supported by the activesync protocol?

AS supports both a carPhone and mobilePhone, yes. The issue being discussed is the original poster wants a workMobile and homeMobile.

>
>Is there a version available which I could use for a first try if the 
>fix works?

Not sure what 'fix' you are referring to? The enhancement of adding the additional fields? I haven't even added this yet, so no.

--
Mike
Sent from mobile