How to start WebRTC?

Troubleshooting
#13

@amy.blais thanks for keeping an eye on this problem .

As for me, looks like WebRTC could not handle a connection because of some external reasons. This probably does not depend on the Mattermost platform. May be it is a NAT or STUN issue. At the same time even a browsers could get some restrictions to provide video/voice stream for these 6 months after last WebRTC release.

So I am very waiting for this issue to be solved.

Thanx again.

#14

Hi, @amy.blais!

I made an update of mattermost docker to version 5.0, but still have an issue with video calls. It is very sad fact for me…
Symptoms are similar to the previous

here is log of webrtc
https://pastebin.com/digHwn4x

Which way I should dig to solve it?

#15

Hi @noizzzzy.boy - v5.0 hasn’t been officially released yet, I’ll let you know when v5.0 is available (will be by EOD).

#16

@amy.blais thanks a lot for your attention!

#17

Hi @noizzzzy.boy - v5.0 is now available to download if you’d like to test WebRTC on latest version: https://about.mattermost.com/download/ (it includes a fix for this issue).

#18

hi, @amy.blais
I still do not have progress in the video call, even with the new version of Mattermost.

Mattermost version:

{“level”:“info”,“ts”:1529309168.0687737,“caller”:“commands/server.go:81”,“msg”:“Current version is 5.0.0 (5.0.0-rc1/Tue Jun 5 21:38:10 UTC 2018/ffb1d5d8e3a40c007b8faa152ddc3ae281f2a63a/none)”}

WebRTC version:

root@7a0aec31498f:/janus-gateway# /opt/janus/bin/janus -V
Janus commit: 7a42432c2683879e124f3f99251fb21d8cc37a4e
Compiled on: Thu Nov 30 15:37:15 UTC 2017
janus 0.2.6

some other issue in mattermost log:

------------------------------------ ERROR ------------------------------------------------
The platform binary has been deprecated, please switch to using the new mattermost binary.
The platform binary will be removed in a future version.

#19

Hi @noizzzzy.boy I’m noticing that your current version is 5.0.0-rc1, which is not the final official version (and doesn’t include WebRTC fixes). I’m wondering why it says that? Can you help double-check that you followed all the upgrade steps: https://docs.mattermost.com/administration/upgrade.html.

Can you also help review these important upgrade notes - e.g. there is one note that mentions that platform binary is renamed to mattermost: https://docs.mattermost.com/administration/important-upgrade-notes.html.

I just tested WebRTC on 5.0 final and it’s working for me, so we can start by double-checking if the upgrade process was successful, and then consider next steps for troubleshooting.

#20

Hi, @amy.blais

I changed docker-compose file to get version 5.0.0 of MM.

image

I do not need an upgrade - MM + WebRTC are running from scratch every time to check an ability of Video Call.

Today I was trying to deploy in different zones and on two hosters. The result is the same.

I’m stumped

The error is same:

mwebrtc | [Tue Jun 19 11:11:01 2018] [WARN] [8693122465677053] ICE failed for component 1 in stream 1, but let’s give it some time… (trickle received, answer received, alert not set)
mwebrtc | [Tue Jun 19 11:11:01 2018] [8693122465677053] Creating ICE state check timer with ID 5
mwebrtc | [Tue Jun 19 11:11:01 2018] [61645027977677] Component state changed for component 1 in stream 1: 5 (failed)
mwebrtc | [Tue Jun 19 11:11:01 2018] [WARN] [61645027977677] ICE failed for component 1 in stream 1, but let’s give it some time… (trickle pending, answer received, alert not set)
mwebrtc | [Tue Jun 19 11:11:01 2018] [61645027977677] Creating ICE state check timer with ID 5
mmattermost | {“level”:“debug”,“ts”:1529406661.7588344,“caller”:“migrations/scheduler.go:50”,“msg”:“Scheduling Job”,“scheduler”:“MigrationsScheduler”}
mmattermost | {“level”:“debug”,“ts”:1529406661.7594457,“caller”:“migrations/scheduler.go:89”,“msg”:“All migrations are complete.”,“scheduler”:“MigrationsScheduler”}
mmattermost | {“level”:“debug”,“ts”:1529406661.7600842,“caller”:“jobs/schedulers.go:153”,“msg”:"Next run time for scheduler MigrationsScheduler: "}
mwebrtc | [Tue Jun 19 11:11:06 2018] [ERR] [ice.c:janus_ice_check_failed:1606] [8693122465677053] ICE failed for component 1 in stream 1…

Here is a full log
https://pastebin.com/sGbYLbtJ

My configs are described in How to start WebRTC?

#21

Thanks @noizzzzy.boy, I’ve asked our team + community members to take a look at this.

#22

@noizzzzy.boy A response from an engineer -

Can you try adding this value to the config.json "StunURI": "stun:stun.l.google.com:19302", without updating the Janus server or any code changes.

The ICE problem can be related to that. If the stun server from google does not work, then maybe you can try another one.

Let me know if this helps?

Webrtc audio is ok video not works
#23

@amy.blais
It was there from the very beginning.
I changed a lot of stun servers with no luck

#24

I have the exact same issue and no matter what i try it wont work.

Any updates on this?

Best regards.

1 Like
#25

Hi @ggisx,

Thanks for reaching out. To give you the best help we can, could you review this web page and send us the relevant logs, config files, etc. which will help us diagnose the issue?

#26

Hi Amy,

I did not set the nat mapping in the janus cfg.

It works perfectly now thanks :slight_smile:

Best regards,

Kevin.

#27

Hi,

Could you explain nat mapping, I am trying to setup without success I have webrtc on docker and MM on host directly installed, what I am doing wrong, I got creasy now.
4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux
i set nat to public IP on janus.cfg firewal ports for https opened wss also. I somwere full configuration described with proper config of janus in docker. Additionaly haw to use docker webrts and localy MM installed.

#28

Hi @robertl,

Unfortunately WebRTC is known to be unreliable, and I recommend exploring some other plugin options for video calls, e.g.:

Would one of these options work for you?

#29

zoom works, I will se other, but why webrtc is not working for me, do you have any idea ?

#30

Hi @robertl,

WebRTC might fail for many different reasons - one thing you could check is to try adding this value to the config.json "StunURI": "stun:stun.l.google.com:19302" , without updating the Janus server or any code changes.

#31

Whenever I connect, I get a black screen, and the call drops ~3 seconds after. I never get any voice or video across.
Please let me know if any more info is needed.

configs: https://pastebin.com/PNgR3K6c (I’ve also tried it with nat_1_1_mapping)

What OS and version is the Mattermost server installed?
debian 8

What is your Mattermost server version?
5.4.0

Are you experiencing the issues with the browser webapp, if so which one?
chromium

Can you send a snippet of the Mattermost server logs around the time of the incident?
https://pastebin.com/grvNUNBh - note that these are the janus logs, not mattermost. Mattermost didn’t have anything interesting in it’s log, but let me know if you need to see it anyway.

Are you running Mattermost in a container and/or using container orchestration?
No, but Janus is in a container

#32

Hi @CaptSpify,

We are slowly removing support for WebRTC because it is known to be unstable (Built-in WebRTC video and audio calls removed in v5.6 in favor of open source plugins), so I recommend exploring other options such as Zoom and Big Blue Button - would one of these sound good?