1035289 - Desktop client needs "something went wrong" visual and audio notification in URL call-back scenarios - GMP plugin specific

Status: RESOLVED INCOMPLETE

(Hello (Loop) :: Client, enhancement, P2)

Description

[Romain Testard [:RT]]

This applies only to URL call-back scenarios where the UX won't allow the user to call the other peer back.

Comment 1

[Romain Testard [:RT]]

In this scenario the client user can't practically do much as he experienced a crash on his machine which disconnected the call but he can't call-back the other peer.

It would be good to let the other peer know that the call terminated not because the call generator hung up on his face but had a crash, so that the link clicker has some context to initiate another link call-back. I needInfo Adam about feasibility for this given I assume this has server implications and I'm unsure whether this scenario is supported in the design.

Comment 2

[Adam Roach [:abr]]

The only real way to handle this situation would be to add messaging to normal call tear-down that lets the remote party know that the call is being torn down gracefully. If the call ends prior to receiving such an event, then we know it has failed unexpectedly and can render an error indication to the user.

We wouldn't need to use the Loop servers to implement this functionality; once the session is set up, we can leverage the TokBox API to send such an indication. Basically, when one side is about to down the call gracefully, it would first do something like:

  session.signal({type:"shutdown"}, function(){stopSendingAndReceiving();});

It the remote side stops sending media before a shutdown signal is sent or received, then the call died due to an error condition.

Comment 3

[Mark Banner (:standard8)]

Closing as incomplete for now. When we get to implementing bug 1066019 we'll be doing a fresh breakdown and either re-opening the bugs that block it, or filing new bugs depending on how we plan to do the technical implementation.