Voice Mailbox
From Openmoko
| Not implemented: This article or section documents one or more features that are not implemented and which may never be implemented. |
| TODO: Voice Mailbox (See: To-Do List) |
Contents |
Overview
The Voice Mailbox application/widget (?) is to replace a mobile service provider's (msp in the following) voice mailbox by recording unanswered calls on the phone.
Reasons for replacing the voice mailbox service with an application are:
- Some msp charge the user for checking their voicemail (as done so in Germany and Sweden)
- Usually voice mailbox has a dial or voice interface. Those interfaces are laborious to use and do not provide functions as pause, rewind or forward. Voice messages may be automatically deleted after are while. If the voice interface is mandatory, this can lead to unwanted activating of mailbox functions as 'delete' or 'forward' by surrounding noise.
- Some msp send you a short message upon arrival of new voice messages. Those short messages do not give information like caller id or time of calling.
Features
- Recording of incoming voice calls when switched silent (Main feature)
- Automated Retrieving of voice messages from the msp's voice mailbox (e.g. if the phone has had no service)
- Profile dependent away messages. If your profile says 'work' you can use a voice mailbox message that says so
- Caller ID dependent away messages. Have different answering machine messages depending on who the caller is. Make the Voice supported menu (described below) Caller ID dependent too, so different callers get different menus.
- Voice supported menu: When a call is not answered the mailbox first can give the caller some options like Additional reachability information (e.g. home adress, company phone number, etc.) or Record a message and maybe after recording Re-record message or Save message
Usage Cases
- Describe where and how the widget gets used in an application
Appearance & Interaction
- If there are modes, then repeat for each mode
On Tap
- Textual description with a picture
- Describe how widget reacts to tap events
On Tap with Hold
- Textual description with a picture
- Describe how widget reacts to tap with hold events
Constraints
- Describes limitations and available of functional aspects
Architectural Details
- Items to clear up non-trivial functionality. For instance, diagrams for event / communication flow, data structures, timing details, etc...
Use and reference open standards whenever appropriate
Implementation Recommendations
- Recommendations on libraries, data structures, etc.. for implementation
Use and reference open standards whenever appropriate
Cross-Widget Interactions
- Details of any cross-widget interactions
Unresolved Issues
- List any unresolved issues, topics, functionality, etc...
Questions and Answers
- List very common questions with their answers here. Everything else should use the Wiki's discussion feature.
