Unification of communication messages

Provision of a standard model for all communications which can then be threaded together and handled using a standard view and features (such as searching or conversion e.g. communication->issue,task,lead...) etc.

type=email, phone, web, direct....
from
to
name
date
description
partner_id
partner_address_id
user_id
message_ids

Perhaps this core could then be extended with communication specific fields depending on the communication type. Possibly a shared base class may provide the required functionality.

type==phone
status=answered,voicemail,missed...
length
cid (to store original number the call came from which can be different to the number for the contact)
....

type==email
status=read/unread
priority
cc