Confirmed users
398
edits
WebAPI/AppDefinedTeleophony: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 48: | Line 48: | ||
== Calling history == | == Calling history == | ||
There is no API for calling 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 calling history. | There is no API for calling 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 calling history. | ||
== Communication Apps == | |||
The communication apps are invoked through activities or other IPC mechanism. A communication App should provide following functions. | |||
* initiate a voice/video call to a receiver | |||
* reply an existing message in the database of WebSMS | |||
* send a new message to a given receiver | |||
* show a user in contacts | |||
The communicaton apps are responsible for handling incoming calls and messages. But, they store contacts, messages, and calling history in ContactsAPI, WebSMS, and calling history API. | |||