Closed Bug 1050648 Opened 11 years ago Closed 10 years ago

[B2G] UI discussion on temporary CLIR mode

Categories

(Firefox OS Graveyard :: Gaia::Dialer, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1131938

People

(Reporter: hsinyi, Unassigned)

References

Details

Introduction to temporary CLIR mode: When user attempts to use the temp CLIR code "*31#" before dialing a number, e.g. *31#012345678, the recieving device will not see the caller's phone number as the number is hidden. FxOS already supports this this feature already. Nevertheless, while Aknow's working on bug 889737, we encounter some questions that we believe worth being widely discussed with the Comms team and UX. Questions: 1) Which number should be shown on keypad? The whole string or only the phone number? [UX - Carrier] the whole string 2) Which number should be shown on call screen? How to do with the name saved in Contacts App? 3) Which number should be saved on call log? How to do with the name saved in Contacts App? E.g., if A calls B via the string "*31#012345678", do we distinguish the log "*31#012345678" from "012345678"? If so, how?
One more thing to mention -- in gsm, MMI code is firmly defined in the spec, we are able to distinguish the phone number and the prefix code. Things are differentin cdma world, again ;) No standard way to parsing the prefix string which is various to operators. Example: In one Taiwanese cdma carrier, *31#_phone_number_ is used to dial out a call to the phone number with hiding the caller's number. However, the gecko platform has no idea of the rule of parsing the whole string. *31#_phone_number_ is reported as the call number from modem (tested with Wasabi), different from the case in gsm.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.