1080459 - Initiating calls to contacts signed-in on multiple devices issues

Status: RESOLVED WONTFIX

(Hello (Loop) :: Client, defect)

Description

[Paul Silaghi, QA [:pauly]]

If I'm signed-in with the same account on multiple profiles (devices) and get called - the incoming call windows shows up on everyone of them. Canceling the call on one device closes the main call on the caller's side.
Don't know what's the solution here - perhaps not to close the call if the callee is still signed-in on other devices ?

Comment 1

[:shell escalante]

check if we can get some help from server on this solution.  breaks our fxos-browser scenarios or multiple devices.

Comment 2

[Maire Reavy [:mreavy]]

This can't wait for clean up in Fx35.

Comment 3

[Maire Reavy [:mreavy]]

Darrin, RT -- When a user presses "cancel" on the screen,should it cancel the call on all devices or should other devices continue to ring?

Comment 4

[Mark Banner (:standard8)]

(In reply to Paul Silaghi, QA [:pauly] from comment #0)
> If I'm signed-in with the same account on multiple profiles (devices) and
> get called - the incoming call windows shows up on everyone of them.
> Canceling the call on one device closes the main call on the caller's side.

I disagree this is a bug. If I'm declining a call (as per the current wording), then I would expect all my devices to stop ringing, e.g. if I was in a room with my phone & desktop, I don't want to have to decline a call on both of them to have them stop ringing.

This would be especially inconvenient if I'm in a meeting for example (although yes, they should already be muted!).

Comment 5

[Darrin Henein [:darrin]]

(In reply to Maire Reavy [:mreavy] (Plz needinfo me) from comment #3)
> Darrin, RT -- When a user presses "cancel" on the screen,should it cancel
> the call on all devices or should other devices continue to ring?

All devices should stop ringing.

Comment 6

[Romain Testard [:RT]]

Agreed all devices should stop ringing.

Comment 7

[Mark Banner (:standard8)]

Per comment 5 & 6, marking as wontfix as this is intended UX.