Closed Bug 1007924 Opened 11 years ago Closed 10 years ago

[User Story] As a user I would like to be able to make a Loop Call from the Loop application to an entry available in the device address book

Tracking

(Not tracked)

Status:

RESOLVED FIXED

People

(Reporter: oteo, Unassigned)

References

Details

(Whiteboard: [ucid:WebRTC21,2.0, ft:webrtc])

User Story

- In Loop I have the option to start a Loop communication to a user in my Address book. When that option is selected, the Address Book is launched via Activities where I can select the contact I would like to talk to. Depending on the details, multiple options can happen here:

A) The selected contact does not have any e-mail or Phone Number linked to it. In that case the call cannot be established and the user is notified about it.
B) The selected contact has one or more e-mail or Phone Numbers linked to it. In case the device has no connection, when the user selects the contact to start the call, the user will be notified about the lack of connection and the call will not be established, otherwise Loop Application connects to the Loop Server and sends all the possible valid IDs for the user (e-mail(s) or/and Phone Number(s)). The Loop Server checks any of the possible IDs and the following situations may occur:

B.1) None of the IDs is a Loop ID: The user is notified and fall-back mechanism is shown. (See US Bug 1007941). This corresponds with a “user-unknown” terminate reason sent by Loop Server.
B.2) There is at least one ID that is a Loop ID but none of them is logged-in in Loop: The user is notified that the other party is not available at this moment and fall-back mechanism is shown. This corresponds with an “unregistered” terminate reason sent by Loop Server.
B.3) There is one or more IDs that are valid Loop IDs and at least one is logged-in in Loop: The server tries to establish the call to all of them and the call is established with the first one to accept the call (in case one answers the call, the server sends an “answered-elsewhere” terminate reason to the rest so they cannot answer the call too). Besides, in case the first of the parties declines the call, the “answered-elsewhere” terminate reason will be sent also to the rest of devices.

- The call will be audio or audio+video depending on the setting defined in US bug 1010196

- In any case the server tries to establish a video call, user is notified about that and the progress of the call attempt (See US in bug 1007681)

(UX Details here as a whole UX review is required)

Maria Angeles Oteo (:oteo)

Reporter

Description

•

11 years ago

No description provided.

Maria Angeles Oteo (:oteo)

Reporter