app specific fields should be removed about voice-metadata-standard

[kemmiso]

Within comChain we leveraged AdditionalProperty for this type of payload. https://schema.org/additionalProperty

[leop-tcto]

Agreed about button name, however we need to define what the minimum metadata items are.

[vitorespindola]

I suggest to rename it to contactName or other generic name where we can store a human friendly name for this callRecord when available, and keep this field as part of the standard as a non required field.

With this generic name we can store the name if it comes from any of these options:

• from the line itself. eg. contact name in the SIP From header
• the application. eg. the button name from c9 or any application specific identification for this line
• 3rd party integrations. eg. exchange or LDAP integration

Keeping this optional we also cover the cases where an identification does not make sense.