Confirmed users
398
edits
WebAPI/AppDefinedTeleophony: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 68: | Line 68: | ||
Should we provide a way for synchronization between the database of Messaging API and App's local storage? | Should we provide a way for synchronization between the database of Messaging API and App's local storage? | ||
== Make a Voice Call == | == Make a Voice Call == | ||
| Line 95: | Line 92: | ||
Message::receiver, for here, are used by the communication App to determine an account for replying the message if the App supports multiple accounts for an installation. The user may change the sender of a message instead of the value from Message::receiver. For example, some MUAs allow users to assign |From| field while composing a message. | Message::receiver, for here, are used by the communication App to determine an account for replying the message if the App supports multiple accounts for an installation. The user may change the sender of a message instead of the value from Message::receiver. For example, some MUAs allow users to assign |From| field while composing a message. | ||
== Call History == | |||
There is no API for call history. We need a new API for that. It must have the capability of telling what the App can handle an address/number in the call history. | |||
== Communication Apps == | == Communication Apps == | ||