1182562 - [Aries][RIL] No Voice mail is received when calling a device that enters Airplane mode during mid call.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: RIL, defect)

Description

[John Thomas [:Johnt]]

Attachment: logcat_20150710_1015.txt

Description:
If the user calls a device that enters Airplane mode while the call is being made the user will not receive a voice mail.


Repro Steps:

Prereq: Two devices with active SIMs.

1) Update a Aries to 20150709132856
2) Have device 1 call device 2.
3) While device 2 is receiving a call pull down notification tray and active Airplane mode.

Actual:
No Voice mail is received when calling a device that enters Airplane mode during mid call.

Expected:
It is expected that even though device 2 has entered Airplane mode while they are being called that device one will enter the voice mail message.

Environmental Variables:
Device: Aries 2.5 L
Build ID: 20150709132856
Gaia: ad76c159c641c977d9140c5fedea84aea04e0e60
Gecko: cc42883d641b720223054f29f096175e26a0b5f3
Version: 42.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0


Repro frequency: 100%
See attached: Logcat & Video

Comment 1

[John Thomas [:Johnt]]

This issue does NOT occur on the Flame 2.5, 2.2, 2.2 and the 2.0.

Result: User successfully reaches a voicemail message when the other device enters Airplane mode while receiving call.

Environmental Variables:
Device: Flame 2.5 Kk Full flash (319mb)
BuildID: 20150710010203
Gaia: ad76c159c641c977d9140c5fedea84aea04e0e60
Gecko: 2c91d57441fd
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 42.0a1 (2.5) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Environmental Variables:
Device: Flame 2.2 2.5 Kk Full flash (319mb)
Build ID: 20150710002505
Gaia: 84d0c76370dcd3d25813b00de55194730884355b
Gecko: e002005dc994
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Environmental Variables:
Device: Flame 2.1 Kk Full flash (319mb)
Build ID: 20150710001202
Gaia: d13826b20b4a45e3f5cd4b25a30a737d8be7f1b9
Gecko: e6585848a94a
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 34.0 (2.1)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Environmental Variables:
Device: Flame 2.0 Kk Full flash (319mb)
Build ID: 20150710000209
Gaia: b16ba05481e577bc644ed8966f587a70fe2148e6
Gecko: 2f753ad1ea42
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 32.0 (2.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 2

[John Thomas [:Johnt]]

Regarding Comment 1, I meant to say this also occurs on Flame 2.1. (2.2 was mentioned twice by accident.)

Comment 3

[KTucker [:KTucker][Inactive 3/4/2016]]

[Blocking Requested - why for this release]:

The user should be sent to voicemail so they can leave a message. Nominating 2.5?

Can we check Spark on Flame to see if this issue occurs?

Comment 4

[Pi Wei Cheng [:piwei] (inactive)]

I was unable to reproduce this issue on the reported build as well as on other devices/branches. I get consistent results from Flame 2.5 KK, Aries 2.5 KK, and Aries 2.5 L:

When the abovementioned DUT enters airplane mode while incoming call is ringing, the caller gets a message saying "the wireless customer you're trying to reach is not available at this time. please try again later."

Device: Aries 2.5
BuildID: 20150709132856
Gaia: ad76c159c641c977d9140c5fedea84aea04e0e60
Gecko: cc42883d641b720223054f29f096175e26a0b5f3
Version: 42.0a1 (2.5) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Reporter could you please try again?

Comment 5

[Pi Wei Cheng [:piwei] (inactive)]

After further investigation, this issue seems to be dependent on carrier. I tested further between AT&T and T-Mobile.

Here are some additional testing results:

T-M calling AT, AT enters airplane mode = T-M gets the call hung up (original bug)
AT calling AT, AT enters airplane mode = AT gets unable to reach message (comment 4 result)
AT calling T-M, T-M enters airplane mode = AT gets to actually leave a voicemail message to T-M

Comment 6

[KTucker [:KTucker][Inactive 3/4/2016]]

Hermes is this expected behavior based upon which carrier the user is using? I am not sure who the correct owner for RIL is at this time.

Comment 7

[Hermes Cheng (inactive after July 27, 2015)]

Hsin-Yi, could you help check if this is a RIL issue?

Comment 8

[Hsin-Yi Tsai (she/her) [:hsinyi]]

(In reply to Hermes Cheng[:hermescheng] from comment #7)
> Hsin-Yi, could you help check if this is a RIL issue?

Bevis, please help this, thank you.

Comment 9

[Bevis Tseng[:bevis][:btseng](Exited)]

Hi Hermes,

I wouldn't say that this is a regression according to the information we have so far and there is not much we can impact/access in B2G implementation.
The behaviour varies based upon multiple reasons:
1. The default configuration in carrier side when call is not reachable/not answered.
2. The SIM Subscriber's configuration in the carrier. (Whether the call will be forwarded to the voicemail if not reachable/not answer. You can check this from "Call Forward Settings" to see if the call is forwarded to a number that represents the voice mail number of the carrier.)
3. Did the modem tear down the connection from network properly when call is incoming?

To narrow down the problem, we need reporter to do the following comparison with the same test SIM:
1. Use the same test SIM cards as the same call originator/receiver on flame-kk. (This is useful to identify reason#1 and reason#2.)
2. If the result is different in Test#1, please have the same test SIM cards to run the tests on Aries with original Android Build instead to see if there is any difference. (This is useful to identify readn#3)

NI reporter to clarify this.

Comment 10

[John Thomas [:Johnt]]

Both SIM Cards for the following tests were specifically using AT to AT.

If device 1 is calling and using a SIM card in slot 1 this issue does NOT occur.
Result: User will receive a voice mail after device 2 enters airplane mode.

However, if device one is calling with the SIM card in slot 2 this issue DOES occur.
Result: Device 1 does not receive a voice mail, call is dropped.


Note: Changing the SIM card for Flame device 2 in slots 1 or 2 does not seem to affect the outcome.


Environmental Variables:
Device: Flame 2.5 Kk Full Flash (319mb)
Build ID: 20150713010204
Gaia: e4b63559eba364892867eb381c3002d6518e5d6a
Gecko: eab21ec484bb
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 42.0a1 (2.5)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Environmental Variables:
Device: Flame 2.2 Kk Full Flash (319mb)
Build ID: 20150713002503
Gaia: 84d0c76370dcd3d25813b00de55194730884355b
Gecko: 8d59402ba85a
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Environmental Variables:
Device: Flame 2.1 Kk Full Flash (319mb)
Build ID: 20150713001203
Gaia: d13826b20b4a45e3f5cd4b25a30a737d8be7f1b9
Gecko: 92049b3c4bb5
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 34.0 (2.1)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Environmental Variables:
Device: Flame 2.0 Kk Full Flash (319mb)
Build ID: 20150713000203
Gaia: b16ba05481e577bc644ed8966f587a70fe2148e6
Gecko: 05c79079e217
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 32.0 (2.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 11

[John Thomas [:Johnt]]

However after calling an Aries with an original Android build entering Airplane mode the user on the flame kk will receive a voice mail message regardless of which port the SIM is located in.

Comment 12

[Bevis Tseng[:bevis][:btseng](Exited)]

remove "regression" according to comment 10.

Hi John,

According to comment 11,
to narrow down the problem further between Aries(Android) and Aries(FxOS), 
Can you help to do the follow test twice with both main/radio logcat captured in both 2 run. 
  - The same reference phone with SIM#1 as caller and the same Aries with SIM#2 as callee.
  Where Aries(Android) is for the 1st run and Aries(FxOS) is for the 2nd run.

Note: For Aries(FxOS), please ensure that RIL related debug flag is enabled.
We suppose to see lots of logs tagged with "RIL Worker" in main log for FxOS build.

Thanks!

Comment 13

[Bevis Tseng[:bevis][:btseng](Exited)]

NI for comment 12 and the following question:
Does the caller reach the voicemail if the callee(Aries) reject the incoming call instead of turning airplane mode off with the same test SIMs?

Thanks!

Comment 14

[John Thomas [:Johnt]]

I was using two Spark devices for these tests. Aries to Rejecting Droid and Aries to Rejecting Aries. I am getting a Voicemail message regardless in this case. 8 Logcats have been attached. Please let me know if there is anything else I can do.

Comment 15

[John Thomas [:Johnt]]

Attachment: mainAriesRejecting.log

Comment 16

[John Thomas [:Johnt]]

Attachment: mainDroidRejecting.log

Comment 17

[John Thomas [:Johnt]]

Attachment: radioAriesRejecting.log

Comment 18

[John Thomas [:Johnt]]

Attachment: radioDroidRejecting.log

Comment 19

[John Thomas [:Johnt]]

Attachment: mainAriestoRejectingAries.log

Comment 20

[John Thomas [:Johnt]]

Attachment: mainAriestoRejectingDroid.log

Comment 21

[John Thomas [:Johnt]]

Attachment: radioAriestoRejectingAries.log

Comment 22

[John Thomas [:Johnt]]

Attachment: radioAriestoRejectingDroid.log

Comment 23

[Bevis Tseng[:bevis][:btseng](Exited)]

Hi John,

Thanks for collect the logs.

Unfortunately, I cannot find the scenario from both Aries(Android) and Aries(FxOS) that rejects an incoming call by turning the airplane mode ON.
It seems that both of them hangup the incoming calls from the reject button instead of turning off the airplane mode because the voice registration is still alive all the time. :(

According to comment 11 and comment 14, there seems to be something different when rejecting a call by turning on the airplane mode between Aries(Android) and Aries(FxOS).

Hence, could you do me a favour again to capture the main/radio logs on Aries(Android) and Aries(FxOS) with the test scenario that the user rejects the incoming call by turning on the airplane mode?

Thanks!

Comment 24

[John Thomas [:Johnt]]

Attachment: AriesSettoAirplanemain.log

Comment 25

[John Thomas [:Johnt]]

Attachment: AriesSettoAirplaneradio.log

Comment 26

[John Thomas [:Johnt]]

Attachment: AriestoAirplaneAriesmain.log

Comment 27

[John Thomas [:Johnt]]

Attachment: AriestoAirplaneAriesradio.log

Comment 28

[John Thomas [:Johnt]]

Attachment: AriestoAirplaneDroidmain.log

Comment 29

[John Thomas [:Johnt]]

Attachment: AriestoAirplaneDroidradio.log

Comment 30

[John Thomas [:Johnt]]

Attachment: DroidSettoAirplaneMain.log

Comment 31

[John Thomas [:Johnt]]

Attachment: DroidSettoAirplaneRadio.log

Comment 32

[John Thomas [:Johnt]]

I have attached the Radio and Main logs located for the different scenarios. Hopefully this will provide the information you are looking for. I noticed that regardless of whether the Aries was calling another Aries or Droid that was being set to Airplane mode in mid call that it will result in a voice mail regardless. Has this issue been fixed recently?

Comment 33

[Bevis Tseng[:bevis][:btseng](Exited)]

(In reply to John Thomas [:Johnt] from comment #32)
> I have attached the Radio and Main logs located for the different scenarios.
> Hopefully this will provide the information you are looking for. I noticed
> that regardless of whether the Aries was calling another Aries or Droid that
> was being set to Airplane mode in mid call that it will result in a voice
> mail regardless. Has this issue been fixed recently?

No, we didn't do any fix on this.
I'll treat the priority of this bug lower if it's not reproducible any more.
In addition, it's not a normal use case to reject an incoming call by toggling airplane mode, IMO.

Comment 34

[Hsin-Yi Tsai (she/her) [:hsinyi]]

[triage] non-blocking as it's not a regression and a very abnormal case.

Comment 35

[BMO Automation]

Firefox OS is not being worked on