Closed Bug 1028890 Opened 10 years ago Closed 9 years ago

Standalone UI for link clickers needs "call resumed" visual and audio notifications

Categories

(Hello (Loop) :: Client, defect, P5)

Product:
Hello (Loop)
Component:
Client
Type:
defect
Points:
3

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX
Blocking Flags:
backlog backlog-

People

(Reporter: RT, Unassigned)

References

Details

(Whiteboard: [fxos])

User Story

As a standalone UI link clicker in a call with a FFOS user, I get notified that my "on hold" call is being resumed through visual and audio notifications so that I know that I can start communicating again.
This is necessary for FFOS / Clicker UI call scenarios.
On FFOS when on a Loop call if a cellular incoming call occurs, the Loop call is placed on hold in the background and then resumed at the end of the call.

The partner SDK exposes a "resume" feature and this does not require Loop server integration.

The FF desktop user cannot place a call on hold or resume a call manually. 
This bug is only about notifying a user that the call is being resumed.
Assignee: nobody → dhenein
Status: NEW → ASSIGNED
Whiteboard: p=3 s=33.3 [qa-]
No particular UX, the call moves from a UX where it is on hold to an active call.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Why is this marked as resolved?
Flags: needinfo?(mmucci)
Chad informed me it was.
Flags: needinfo?(mmucci)
Chad, we need this for FFOS interrop.
A call can be placed on hold and resumed on FFOS (if incoming cellular cold occurs as a FFOS is on a Loop call) and we need a notification on the clicker side that the call was resumed.

Please confirm you agree?
Flags: needinfo?(cweiner)
Re-opening as needed but for Fx36.
Status: RESOLVED → REOPENED
Flags: needinfo?(cweiner)
Priority: P2 → P1
Resolution: FIXED → ---
Target Milestone: mozilla34 → mozilla36
Un-assigning until its on the backlog.
Assignee: dhenein → nobody
Points: --- → 3
Flags: qe-verify-
Flags: firefox-backlog+
Whiteboard: p=3 s=33.3 [qa-]
putting in 38 because not sure how often hit edge scenario.  if we start getting bugs about it - look at sooner
backlog: --- → Fx38+
Status: REOPENED → NEW
backlog: Fx38+ → backlog
backlog: backlog+ → backlog-
Rank: 59
Priority: P1 → P5
Whiteboard: [fxos]
Target Milestone: mozilla36 → ---
Marking as WON'T FIX since this is not on the agenda anymore (as per bug 1015057)
Status: NEW → RESOLVED
Closed: 10 years ago → 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.