Mattermost supports voice calling and screen sharing functionality in channels, group messages, and direct messages from Mattermost v7.0 for Mattermost Cloud and Mattermost self-hosted deployments.
Starting from Mattermost v7.0, you can:
Start or join a call from desktop and mobile apps in addition to web browsers.
Share screen (not available on mobile), raise hands, chat in a thread, and even switch between products in the Mattermost suite (i.e., Channels, Boards, and Playbooks) while on a call.
Start a call using the
/call startslash command or Start call in the channel header.
Starting from Mattermost v7.7 you can:
Record calls (Mattermost Enterprise only).
React using emojis.
Mattermost Cloud users can start calling right out of the box. For Mattermost self-hosted deployments, System Admins need to enable the plugin and adjust configurations in the System Console.
To start a call, select Start call in the channel header. Any active team member in the channel can join a call, whether it’s a public or private channel. If someone from outside of the organization wants to join a call, you’ll need to provide them with a guest account, and add them to the channel. Users who are archived or not registered can’t join a call.
You can share a call’s link to use in a meeting request or share with other team mates. The link is unique to each channel, and contains the channel’s ID, so it doesn’t change between calls. Use the
/call link slash command to generate a shareable link.
The call link is valid for long as the channel is active. When a channel is archived or deleted the link will become invalid.
The host of a meeting can record the call. The recording includes audio as well as any screen sharing during the call. The default setting for a recording is 60 minutes, but your system admin may adjust that as needed. Ten minutes before the time limit, the host will receive a reminder that the recording limit will be reached soon.
If your call is going to continue and you still want to record, once the first recording is complete you can start a new one immediately after.
Call recordings are posted by the Calls bot directly in the call thread as normal file attachment and can be accessed by all users in the channel.
The integration currently supports only voice calling and screen sharing. We’re considering video support in the future.
No. Any member with sufficient permission to access the channel will be able to join the call.
Media (audio/video) is encrypted using security standards as part of WebRTC. It’s mainly a combination of DTLS and SRTP. It’s not e2e encrypted in the sense that in the current design all media needs to go through Mattermost which acts as a media router and has complete access to it. Media is then encrypted back to the clients so it’s secured during transit. In short: only the participant clients and the Mattermost server have access to unencrypted call data.
The only external service used is Mattermost official STUN server (
stun.global.calls.mattermost.com) which is configured as default. This is primarily used to find the public address of the Mattermost instance. The only information sent to this service is the IP addresses of clients connecting as no other traffic goes through it. It can be removed in case the
ICE Host Override setting is provided.
My call is disconnected after a few seconds and I can’t transmit voice nor hear anything.
This is usually a sign that the underlying UDP channel has not been established and the connection times out after ~10 seconds. When the connection has been established correctly an
rtc connected line should appear in the client-side logs (JS console). There isn’t a single solution as it depends on the infrastructure/deployment specifics. However, if you’re a system or network admin, you may need to open up the UDP port or configure the network accordingly.
If you experience issues with calls, collecting information is helpful as you can share it with us for debugging purposes.
As with any other issue, but more importantly with calls, it’s very useful to provide date and time of when some problem occurred, with as much detail as possible so that information can be cross-checked with server logs as well. Also please include any reproduction steps if applicable. Other important information includes:
Operating system type and version
Chrome: CMD+OPTION+J (macOS)/CTRL+SHIFT+J (Windows, Linux, ChromeOS)
Firefox: CMD+SHIFT+J (macOS)/CTRL+SHIFT+J (Windows, Linux, ChromeOS).
In cases where there are audio/video issues, difficulty in hearing other participants, and/or stuttering video and/or choppy audio, run the
/call stats slash command in the channel where the call is currently active. This returns a JSON object via an ephemeral message.
You can run this command in an active call or after leaving the call in question. However, we will only save data for the last joined call so joining again will delete the previous call’s feedback.
This is an additional method for Chrome and Firefox users in cases where there are audio/video issues, difficulty in hearing other participants, and/or stuttering video and/or choppy audio.
chrome://webrtc-internals/ in the browser that you’re using for the active call.