Closed Bug 900882 Opened 11 years ago Closed 11 years ago

CALL_STATE_ALERTING is missing when making an outgoing call

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: echou, Unassigned)

Details

Attachments

(1 file)

I tried to answer a phone call while a Bluetooth headset was connected, but I found that my Unagi would not send indicator "Call=1" even if the call has been picked up. 

The root cause is that Gecko Blueooth received the CallStateChanged event which indicates the phone call state was changed from 'CALL_STATE_DIALING' to 'CALL_STATE_CONNECTED'. This is not what we expected. The state should be changed as

  CALL_STATE_DIALING -> CALL_STATE_ALERTING -> CALL_STATE_CONNECTED

I've talked to RIL peer HsinYi, and she will help us to confirm RIL implementation and GSM spec.
Thanks for Shawn's support. Shwan just reviewed the gsm spec again, and according to the spec it's an acceptable path that call state jumps from 'dialing' directly to 'connected.' You might refer to attachment #784890 [details]. The flow of an outgoing call is on the left-hand side. One path, U0 -> U0.1 -> U1 -> U10, is the case of no alerting. 

I'll mark the issue as WONTFIX. Thank you for reporting, Eric. :)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: