Type Property: Phone
The vCard 3.0 Type property supports the Siebel contact's Phone LOV type (child component) as follows:
The VOICE and FAX Type property is supported.
The Phone Number property is supported.
The iOS-specific iPhone type is supported.
Alphanumeric phone and fax numbers are supported.
Custom labels for the TEL/VOICE type sent from the client are supported.
If the custom label is not a Siebel Type entry, then the type is stored as Personal in Siebel and the custom label is stored in the Description field.
Both iOS and Android CardDAV clients do not support the custom label for the Phone/Fax type.
If a Siebel user creates a fax number with a non-default type in Siebel (for example: Personal, Campus, or Dormitory), it becomes other fax type/label in the iOS and Android CardDAV client after synchronization. Eventually on the Siebel side, the Phone/Fax type is updated to other fax type implicitly.
The Primary entry is handled as follows when synchronizing Siebel Phone/Fax data to the CardDAV client:
In the CardDAV/vCard client, there is only one TEL with type=pref entry (primary). In Siebel, TEL is split into Phone and Fax child components and each one has its own primary record.
When data comes from the CardDAV client into Siebel, the type=pref (VOICE or FAX) entry is honored as the primary in Siebel. The first non pref of another type is assigned as the Primary in Siebel.
When data is returned back to the CardDAV client, determining which Phone or Fax's primary entry is the original primary (type=pref entry) on the CardDAV client-side is difficult. Currently, the Phone's primary is chosen as the TEL's type=pref entry - however, this might unexpectedly change the user's setting.
Updating a contact's Work Phone, Home Phone #, Cell Phone #, and Main Fax # is supported during CardDAV download synchronization, provided those numbers do not exist in the child Phone or Fax entries.
Download Synchronization
The supported behavior for download synchronization is as follows:
The child Phone/Fax's existing primary entry based on the Contact's phone number will not be altered.
The child Phone or Fax number will automatically be created in the CardDAV client (vCard) with the appropriate type only if no such number entry exists in the child Phone or Fax. If a child Phone or Fax number exists but the type is different, then another child Phone or Fax number will not be created.
Create a phone entry with label as work (iOS) or Work (Android) on client based on Contact's Work Phone #
vCard: TEL;type=WORK;type=VOICECreate a phone entry with label as home (iOS) or Home (Android) on client based on Contact's Home Phone #
vCard: TEL;type=HOME;type=VOICECreate a phone entry with label as mobile (iOS) or Mobile (Android) on client based on Contact's Cell Phone #
vCard: TEL;type=CELL;type=VOICECreate a fax entry with label as work fax (iOS) or Work Fax (Android) on client based on Contact's Main Fax #
vCard: TEL;type=WORK;type=FAXNote: Users will not be able to remove all phone entries from the CardDAV client if the server-side contact has at least one single value for Work Phone #, Home Phone #, Cell Phone #, and Main Fax #. The subsequent synchronization recreates the child phone entry based on the contact's single value phone/fax number.
Upload Synchronization
The supported behavior for upload synchronization is as follows:
The Work Phone #, Home Phone #, Cell Phone #, and Main Fax # for contacts will be updated on the server only for newly created contacts.
If a user updates an existing contact, the server-side Work Phone #, Home Phone #, Cell Phone # and Main Fax # data for the contact will not be modified.