Closed Bug 1046959 Opened 6 years ago Closed 6 years ago

Standalone client should trigger call failed notification on information via the server

Categories

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

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: standard8, Unassigned)

References

Details

(Whiteboard: p=1[standalone-uplift])

User Story

As a WebRTC browser user calling a reachable user who is on a call, I get notified that the callee can't be reached so that I can try again.
As a WebRTC browser user calling a reachable user who refused my call, I get notified that the callee could not be reached so that I can try again.
As a WebRTC browser user calling a non reachable user, I get notified that the other user can't be reached so that I can try again.
As a WebRTC browser user calling a reachable user, I get notified that the other user could not be reached after a one minute timeout so that I can try again.

As a callee, I should be notified when the user rejects a call, or the call times out.

Rough impl:

Depends on bug 1000240 for the UX

* Monitor the websocket connection, when a termination reason from the callee is sent, display the Call Failed UI.

This should cover all of the above cases.
No description provided.
User Story: (updated)
Depends on: 1000240
Priority: -- → P3
Target Milestone: --- → mozilla34
User Story: (updated)
Whiteboard: p=1
This should be a P1, though Jose Antonio or someone on his team may take it.
Priority: P3 → P1
Assignee: nobody → aoprea
Whiteboard: p=1 → p=1[loop-uplift]
Target Milestone: mozilla34 → mozilla35
This is a standalone bug (no uplift required).
Whiteboard: p=1[loop-uplift] → p=1
Whiteboard: p=1 → p=1[standalone-uplift]
Just to separate out client uplifts from standalone-uplifts, I'd like to use a separate whiteboard tag.
backlog: --- → Fx34?
Hi Mark,  when you get a chance - you were going to investigate to see if this needed more work or was already working.
Flags: needinfo?(standard8)
Target Milestone: mozilla35 → ---
I've just checked and we now cover all the elements of the user story.

Its possible the wording could be improved in the different situations (e.g. "Something went wrong" isn't descriptive as it might be - but we haven't had more detail from UX).

In any case, those follow-ups should be done in different bugs.

The only edge case we don't quite cover is network disconnections, which is a separate issue covered by bug 1076794.
Assignee: aoprea → nobody
Status: NEW → RESOLVED
backlog: Fx34? → ---
Closed: 6 years ago
Flags: needinfo?(standard8)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.