If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[B2G][Emulator] support call number change (e.g. STK call control) scenario

NEW
Unassigned

Status

Firefox OS
Emulator
3 years ago
2 years ago

People

(Reporter: hsinyi, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
My idea is to introduce a new console command, like "gsm stkcall <origNumber> <modifiedNumber>",  to simulate an outgoing call under stk call control.

In emulator,  a call with <origNumber> will be first dialed out, then the number will become <modifiedNumber> along with state change to 'connected/active'.

Sounds good?
I would suggest one console command performs only one action to avoid the potential timing problem [1].
How about separating to two commands and put them in stk grounp?
Like,
1). stk setupcall <number> ====> generate an outgoing call.
2). stk callcontrol <number> <modifiedNumber> ====> modify an existed call to <modifiedNumber>

Note: for changing call state to `active`, we could reuse `gsm accept`.

But I am not sure does this proposal meet the scenario.

[1] Something like bug 823084 comment #4.
(Reporter)

Comment 2

3 years ago
(In reply to Edgar Chen [:edgar][:echen] from comment #1)
> I would suggest one console command performs only one action to avoid the
> potential timing problem [1].
> How about separating to two commands and put them in stk grounp?
> Like,
> 1). stk setupcall <number> ====> generate an outgoing call.
> 2). stk callcontrol <number> <modifiedNumber> ====> modify an existed call
> to <modifiedNumber>
> 
> Note: for changing call state to `active`, we could reuse `gsm accept`.
> 
> But I am not sure does this proposal meet the scenario.
> 
> [1] Something like bug 823084 comment #4.

Offline discussion with Edgar (Thank you :) ):

comment 0 doesn't intend to changing call state automatically. The idea is like Edgar's note, every state transition is controlled on demand. That proposal is just to create an outgoing call via a background (for user) console command not via telephony.dial() API. However, to help marionette-webapi tests closer to UI behaviour, we think it's better to keep using telephony.dial() API for the creation of an outgoing call, and then use another background command to change call number that totally aligns STK call control behaviour. As a result, we just need one new console command "stk callcontrol <number> <newNumber>" to change a call number. And the command would fail if the call state isn't in 'dialing' or 'alerting' to fit the real situation.
Blocks: 791161
(Reporter)

Updated

3 years ago
Blocks: 1092066
(Reporter)

Updated

3 years ago
Assignee: nobody → htsai
(Reporter)

Updated

2 years ago
Assignee: htsai → nobody
You need to log in before you can comment on or make changes to this bug.