Closed Bug 1060757 Opened 10 years ago Closed 10 years ago

Notify user when remote party not reachable

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jaoo, Assigned: jaoo)

References

Details

Attachments

(1 file)

Want to be notified that the remote party could not be reached. Moreover the caller want to have the opportunity to share a callback URL with him.
Assignee: nobody → josea.olivera
Blocks: Loopmov_1_1, 1007681
No longer blocks: 1036490
Attachment #8485109 - Flags: review?(borja.bugzilla)
The screen we show to let the user share a callback URL with the remote party when this is not a hello user contains the following string 'Not a Firefox Hello user yet'. As we use that screen here we would need either a string valid for both cases (which are not hello user and unreachable) or a string for the unreachable case. Moreover we are wondering if we should play the failed tone when calling a non hello user, should we?
Flags: needinfo?(hello)
"Not available right now" works for both cases, but if it's simple to implement, I'd rather have both options: not a user (existing string) *and* unreachable (the new one). Not a biggie either way!
Flags: needinfo?(hello)
(In reply to Rafael Rebolleda from comment #4)
> "Not available right now" works for both cases, but if it's simple to
> implement, I'd rather have both options: not a user (existing string) *and*
> unreachable (the new one). Not a biggie either way!

what about the tone? Jose Antonio asked also in comment 3 if when calling a non hello user, should we played the failed tone?
Flags: needinfo?(jorge.munuera)
Flags: needinfo?(hello)
Yes, a call to a non-hello user should play fail.
Flags: needinfo?(hello)
(In reply to Rafael Rebolleda from comment #4)
> "Not available right now" works for both cases, but if it's simple to
> implement, I'd rather have both options: not a user (existing string) *and*
> unreachable (the new one). Not a biggie either way!

The last one, I promise ;) In the AC of the US bug 1007681, we specified for this case:

 The other user was unreachable (e.g. no connection at that time or a server timeout occur without alerting the user). Call does not reach alerting state or server sends a “connection-failure” terminate reason or callee sends a “media-fail” one. In any of these cases I will be notified that the other user can’t be reached and message "Unavailable" and Call failed tone will be played. User has also the opportunity to share a callback URL with him.

So we should use the same string for the call screen and the Share URL screen... Unavailable or Unreachable, that is the question :)

Thanks a lot!
Flags: needinfo?(hello)
Attachment #8485109 - Flags: review?(borja.bugzilla) → review+
Landed at:

https://github.com/mozilla-b2g/firefoxos-loop-client/commit/a6d78986b07a72518907c92f5199264cb5fa7006

Thanks Borja!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Flags: needinfo?(hello)
Flags: needinfo?(jorge.munuera)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: