1048234 - [Loop] The user is not notified when the other party is not available

Status: RESOLVED DUPLICATE of bug 1060757

(Firefox OS Graveyard :: Gaia::Loop, defect)

Description

[mbarone]

Device: Flame
Loop ID: f6c5f47
Acceptance Criteria: 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. (US https://bugzilla.mozilla.org/show_bug.cgi?id=1007933)

STR
1. Device A (User A logged into Loop) make a call to device B (User B with valid Loop ID but not logged into the Loop app)

ACTUAL RESULT
The Device A try to establish the call (attention screen is shown and add the call in the Call log)

EXPECTED RESULT
As per AC, the Loop app should inform that the user B is not available

Comment 2

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

This issue still occurs on the latest 2.0 build with the v165 KK base.  The user is not informed that the other user is available.  The call just ends without notification.

Environmental Variables:
Device: Flame 2.0
BuildID: 20140820030000
Gaia: 806d37a264743e04a3e1493136486f3e00124e1e
Gecko: 6329352ca531b977979451e77e5862af485388b2
Version: 32.0 (2.0) 
Firmware Version: v165
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Loop version: 8c71431

Comment 3

[Borja Salguero [:borjasalguero]]

For testing this, 'B' should not be logged in *any* device, regardless if it's switched off or not (because if it is, we have a valid endpoint to contact). Could you check this again following that rule?

Comment 4

[Maria Angeles Oteo (:oteo)]

Borja, does the current protocol allow to distinguish between the situation when a contact has a contact available but it's not reachable?