Error message unhelpful when VoIP unsupported

[bignose-debian]

The error message (added in merge request #26) is not helpful to the user trying to trouble-shoot the problem.

VoIP is unsupported

You cannot place VoIP calls in this browser.

This gives no information to lead the user to what might be the problem, or what can be done to remedy it.

Steps to reproduce

• Disable WebRTC.
  • For example, in Firefox: Visit about:config and set media.peerconnection.enabled to false.
• Visit a Matrix room.
• Attempt to start a voice call.
  • The above error message appears.
  • No further information is given to help find out why “You cannot place VoIP calls in this browser”.

Expected:

• Useful suggestions for what could be wrong (e.g. information about checking for WebRTC features, or any other things that might be blocking the VoIP feature).

Version information

• Platform: Riot:

matrix-react-sdk version: riot-web version: 0.16.6 olm version: 2.2.1

• Browser: Firefox 52.9.0 (64-bit)
• OS: GNU+Linux

[bignose-debian]

This bug continues in Riot, when I upgrade to Firefox “68.2.0esr (64-bit)”. I have explicitly set permissions “Use the camera” and “Use the microphone” for the ‘riot.im’ domain.

[LinuxOnTheDesktop]

On my system the problem does indeed seem to owe to WebRTC; when I set the WebRTC back to default, the error message goes away. (Now I just have the problem that sometimes notifications appear behind other notifications. I would file a bug report for that, but I see that you over 4, 000 to deal with already!) EDIT: actually, no - rather, on Windows, I get the message 'you cannot place a call with yourself' and on the Linux computer with which I am trying to communicate, I continue to get the message about an unsupported browser. Also, my VPN complains if I enable WebRTC. So: I give up.

[MortezaBashsiz]

Hi I faced to this bug when i install the Matrix,Riot,Jitsi in local (private) network with self signed SSL/TLS , But everything works fine when i install in public (Internet) Network with valid domain and certificates. I had a lot of searching about this problem but there is no good solution to solve it

[kittykat]

First step to solving this issue is to propose a better error message and get it approved by the Design Team - leaving as Help Wanted because be are happy to take proposals from the community.

[bignose-debian]

First step to solving this issue is to propose a better error message

Agreed. The message will need to be written by people who have that information: those who know what are the plausible causes of the error, and what can be done by the user.

happy to take proposals from the community.

That's my proposal: People in the development team need to provide the detailed information for the message.

[florianduros]

Before requesting a design for this, we need to list the possible errors than make the VoIP failed. To be able to display a proper error message for each of them.

Check with design when it's ready.