Closed Bug 932050 Opened 12 years ago Closed 12 years ago

[B2G][Buri][Dialer] - Making call using "*31#" while CLIR is configured still displays phone number on recieving device

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:koi+)

RESOLVED INVALID
1.2 C4(Nov8)
blocking-b2g koi+

People

(Reporter: tnguyen, Unassigned)

Details

(Whiteboard: burirun3 ,FT:RIL)

Attachments

(1 file)

Attached file logcat
When user attempts to use the CLIR code "*31#" before dialing a number, the recieving device will still see the phone number of the device making the call. Repro Steps: 1) Updated Buri v 1.2 COM RIL to BuildID: 20131025004000 2) Launch the Dialer app 3) Enter the CLIR code "*31" and then an activated phone number 4) Tap the Call button and observe phone that is recieving call Actual: Phone number of device with CLIR code "*31#" is not hidden Expected: Phone number of device with CLIR code "*31#" is hidden Environmental Variables: Device: Buri v1.2 COM RIL BuildID: 20131025004000 Gaia: 606517ceafe0950c2b89822d5f13353743334f2c Gecko: 5eabd267ef04 Version: 26.0a2 Firmware Version: US_20131015 RIL Information: 01.02.00.019.082 Notes: Repro frequency: 100% See attached: logcat
blocking-b2g: --- → koi?
Actually, can someone confirm if this reproduces on 1.1 or not? Or find out a build in general when this used to work?
blocking-b2g: koi? → ---
This was not a feature for 1.1. There were a couple of the new test cases that needed to be updated, and this one looks like it may need to be updated too. Setting a needinfo for myself to double check.
Flags: needinfo?(ahubenya)
Keywords: qawanted, regression
(In reply to Angela Hubenya from comment #2) > This was not a feature for 1.1. There were a couple of the new test cases > that needed to be updated, and this one looks like it may need to be updated > too. > Setting a needinfo for myself to double check. Can you include the actual test case that was used to file this bug?
Here's the test case that was used to file this bug: https://moztrap.mozilla.org/manage/case/9915
Al - How important of a use case is this? I can't tell how important this bug is to figure out how bad of a bug this is.
Flags: needinfo?(atsai)
We should support the function in v1.2. Without the feature, we cannot hide the outgoing call number. We should mark it as koi+. Mark it as koi? for triage.
blocking-b2g: --- → koi?
Flags: needinfo?(atsai)
Clearing my needinfo flag since the test case and bug are valid.
Flags: needinfo?(ahubenya)
Taipei triage result: koi+. It looks like something we need to fix in commercial RIL.
blocking-b2g: koi? → koi+
Component: Gaia::Dialer → RIL
Whiteboard: burirun3 → burirun3 ,FT:RIL
Hi Anshul, can you please check this bug?
Flags: needinfo?(anshulj)
This bug should be invalid. *31# means show number, #31# means hide number // 3GPP 22.030 Annex B (normative): In temporary mode, to suppress CLIR for a single call, enter: ' * 31 # <called number> SEND ' In temporary mode, to invoke CLIR for a single call enter: ' # 31 # <called number> SEND ' 10-28 14:12:35.590: I/Gecko(140): -*- QCContentHelper_QC_B2G: _parseMMI dialstring: *31#6509336976 10-28 14:12:35.600: D/PHONE_QC_B2G(140): dialing w/ mmi MmiCode { action=* serviceCode=31 poundString=*31# dialingNumber=6509336976}
Tony, can you please check if your description is right?
Flags: needinfo?(tnguyen)
(In reply to Ken Chang from comment #11) > Tony, can you please check if your description is right? Tony - Can you also confirm that the behavior in comment 10 works on device on a 1.2 build?
Hi all, The behaviors from comment 10 is what I'm experiencing on Buri 1.2 BuildID 20131106004004. The description of the bug was written up in accordance to test case 9915 - which appears to have the incorrect expected result of: "The phone number is not displayed in the device who received the call." BuildID: 20131106004004 Gaia: 2140c987fdde1c99097018f7e93b0bbd43d2125d Gecko: 6a831fcb96f4 Version: 26.0
Flags: needinfo?(tnguyen)
Sounds like this is invalid then. We should update the test case to follow comment 10.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Flags: needinfo?(anshulj)
Target Milestone: --- → 1.2 C4(Nov8)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: