Closed Bug 881858 Opened 11 years ago Closed 11 years ago

[leo-pre-iot-br] Conditional Call Forwarding not working by menu

Categories

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

x86_64
Windows 7
defect
Not set
normal

Tracking

(blocking-b2g:leo+)

RESOLVED DUPLICATE of bug 882978
blocking-b2g leo+

People

(Reporter: dpalomino, Unassigned)

References

Details

(Whiteboard: [leo-pre-iot-br] TaipeiWW)

Attachments

(1 file)

Device: leo
buildid: 20130529095707 (brazilian variant)

build 06/07:
Gecko revision : 08e8a7bbebec924c24a5187a3c0b2ef1ef6d08da
Gaia revision : e2346ca0297f40547e64a7eebc4bd2e4a4cdaf86
QC commercial RIL : AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.115

We have observed that Conditional Call Forwarding is not working when trying to enable by menu: 

1. Go to Settings > Calls
2. Current forwarding status checking: ok
3. Select any of the conditional forwardings (CF if busy, CF if not reply, CF if not reachable)
4. User can enable/disable the call forwarding
5. BUT it's not possible to configure the phone number to be forwarded

However, CF (always option) is working fine.
Attached file dmc file
Activation/Deactivation of conditional CF is determined by network. 
How about the other device behavior using same SIM?
To find the root cause exactly, please capture the ddms and qxdm logs (You can use attached dmc file for qxdm log.)
Thanks.
Could you share the qxdm log by my mail (joypark9@gmail.com), not in bugzilla?
Flags: needinfo?(dpv)
David, any updates yet?
Flags: needinfo?(dpv)
Flags: needinfo?(dpv)
Sorry for the delay. As previously discussed by mail: 

Unconditional CF was not enabled, and indeed user could change other conditional CF options, but not modifying the MSISDN to be forwarded. 

We are not based in SP (just doing pre-IOT testing the last two weeks), so we cannot take new logs. I’d suggest to ask for support to your team in SP. 

Thanks!
David
Flags: needinfo?(dpv)
QA: can we test if this works for whichever network we're able to test ourselves?

Thanks
Flags: needinfo?(atsai)
Keywords: qawanted
Whiteboard: [leo-pre-iot-br] → [leo-pre-iot-br] TaipeiWW
Tested with AT@T SIM, 2G-E connection

Unconditional CF (Always forward) works fine on both devices Leo and Unagi:
 - the user is able to activate/dis-activate it and use any desired(valid) number as forwarding
 - able to change forward number at any time
 - when "Always forward" is activated all incoming calls are forwarded to the forwarding number right away


Conditional CF (CF when busy, CF when unanswered, CF when unreachable) work fine on Unagi and user is able modify it, unable to modify on Leo

Unagi:
1. When "Always forward" is disabled its possible to set forwarding number and enable CF
2. When "Always forward" is enabled its not possible to set conditional CF, when attempting to do so the user will get "Call settings error" at the confirmation screen

Leo:
1. When "Always forward" is disabled conditional CF options are pre-set to forward voice calls to +12096078210. User is unable to modify, either change the number (grayed out) or disable "Forward" option - "Call settings error" at the confirmation screen 
2. When "Always forward" is enabled conditional CF options are displayed with the note "Voice calls to null"


Leo build info:
Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/3e144cc723d3
Gaia   c507ff65b51194383da65f8927164f078a3e1f79
Build  20130620070209
RIL    01.01.00.019.133
Version 18.1

Unagi build info:
Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/3e144cc723d3
Gaia   c507ff65b51194383da65f8927164f078a3e1f79
Build  20130619230208
Version 18.1
Keywords: qawanted
blocking-b2g: leo? → leo+
Modifying number issue is arguing Bug 882978. Please refer it.
However, can't you see the pre-set number on Unagi even if you use same SIM which you've tested on Leo?
FYI the carrier might not let the user disable/enable conditional call forwarding rules. The behavior could be different between carriers.
(In reply to leo.bugzilla.gecko from comment #8)
> Modifying number issue is arguing Bug 882978. Please refer it.
> However, can't you see the pre-set number on Unagi even if you use same SIM
> which you've tested on Leo?

you right, it is not Unagi/Leo difference, but SIM 
the SIM card I have used for Unagi test (in comment 7) did not have a voicemail box set up, after setting it up Unagi has the same behavior as Leo
As you said, the difference is come from SIM difference.

The only concern of this issue is number editing when forwarding option is enabled.
It is duplicated with Bug 882978.

So this should be marked as duplicate.

Thanks!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
remove as Comment 7 reply
Flags: needinfo?(atsai)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: