niklabh / mattermost-plugin-webrtc-video

A webrtc video call plugin for mattermost
Apache License 2.0
86 stars 17 forks source link

Not working #1

Open uhlhosting opened 4 years ago

uhlhosting commented 4 years ago

This is not working in any mattermost version i had 5.1.7 5.1.8

ElNovi commented 4 years ago

Not working for me either on 5.17.1. There is only blank popup: image

PackElend commented 4 years ago

same here on

Mattermost Enterprise Edition

Modern communication from behind your firewall. Mattermost Version: 5.18.1 Database Schema Version: 5.18.0 Database: postgres

jasonblais commented 4 years ago

FYI @niklabh on the feedback above if you have a chance to take a look :)

niklabh commented 4 years ago

will take a look

simak111 commented 4 years ago

Works sometimes, sometimes does not. Mattermost Team edition 5.18.0

Klagio commented 4 years ago

will take a look

same for me. But I guess is a matter of opening and forwarding the correct ports?

Can yuou please explain which are the ports needed?

blacoste commented 4 years ago

Using a STUN or TURN server could fix those issues if NAT is responsible. But I don't see where to set them in mattermost config or this plugin config.

Klagio commented 4 years ago

Using a STUN or TURN server could fix those issues if NAT is responsible. But I don't see where to set them in mattermost config or this plugin config.

yes, agreed. And maybe also https/certificates/encryption?

PackElend commented 4 years ago

Using a STUN or TURN server could fix those issues if NAT is responsible

You may losing other reporter as me, are you talking about https://www.html5rocks.com/en/tutorials/webrtc/infrastructure/

Https clear but isn't mattermost's certificate used?

Sent from a fair mobile

niklabh commented 4 years ago

I am using following servers: export default { iceServers: [ {url: 'stun:stun.l.google.com:19302'}, {url: 'stun:stun1.l.google.com:19302'}, {url: 'stun:stun2.l.google.com:19302'}, {url: 'stun:stun3.l.google.com:19302'}, {url: 'stun:stun4.l.google.com:19302'}, {url: 'stun:stun01.sipphone.com'}, {url: 'stun:stun.ekiga.net'}, {url: 'stun:stun.fwdnet.net'}, {url: 'stun:stun.ideasip.com'}, {url: 'stun:stun.iptel.org'}, {url: 'stun:stun.rixtelecom.se'}, {url: 'stun:stun.schlund.de'}, {url: 'stun:stunserver.org'}, {url: 'stun:stun.softjoys.com'}, {url: 'stun:stun.voiparound.com'}, {url: 'stun:stun.voipbuster.com'}, {url: 'stun:stun.voipstunt.com'}, {url: 'stun:stun.voxgratia.org'}, {url: 'stun:stun.xten.com'}, { url: 'turn:numb.viagenie.ca', credential: 'muazkh', username: 'webrtc@live.com', }, { url: 'turn:192.158.29.39:3478?transport=udp', credential: 'JZEOEt2V3Qb0y27GRntt2u2PAYA=', username: '28224511:1379330808', }, { url: 'turn:192.158.29.39:3478?transport=tcp', credential: 'JZEOEt2V3Qb0y27GRntt2u2PAYA=', username: '28224511:1379330808', }, ], };

niklabh commented 4 years ago

i am using signalhub to signal webrtc. I wanted to use mattermost infrastructure to signal. Bu i was not able to figure out how to signal using mattermost.

blacoste commented 4 years ago

How come you distribute these credentials (TURN servers) in your package? Lots of STUN servers are available publicly as it does not consume a lot of ressource, but that's not the case of TURN which requires large amount of bandwidth. I would not be surprised if users are denied to connect to these servers. Maybe that's the cause of such troubles.

Should TURN (and STUN) servers rather be configurable by the user?

mikebakke commented 4 years ago

Not working for me either. In the desktop app I get a window open but no attempt to call or use the camera/mic.

uhlhosting commented 4 years ago

Any plans to fix this?

derekdon commented 4 years ago

Same here on Mattermost Enterprise Edition 5.13.2.

Happy to fork this and try to fix it if someone can point me in the right direction as to what might be the problem. I'm pretty new to mattermost and its plugin setup.

Or if anyone has an alternative product... let me know.

bhartvigsen commented 4 years ago

Same issue here

niklabh commented 4 years ago

Same here on Mattermost Enterprise Edition 5.13.2.

Happy to fork this and try to fix it if someone can point me in the right direction as to what might be the problem. I'm pretty new to mattermost and its plugin setup.

Or if anyone has an alternative product... let me know.

Hi derekdon thankyou very much for the help. Would appreciate if you can debug the problem

ulab commented 4 years ago

I am having the same issue here on Mattermost-Version: 5.19.1 that is included in the gitlab-ce omnibus package. I get a "User X calling" window when someone calls, can accept the call and then only have the white window with camera, hangup and mic icons. There is no difference if it's a local network or one or both partners having a NAT connection.

I noticed this in the Javascript console in a browser.

Screenshot 2020-03-17 at 14 41 56
discostur commented 4 years ago

also just getting the empty, white window :/ mattermost-server 5.19.1

franckadil commented 4 years ago

Same issue on Mattermost Version: 5.16.3.

benjym commented 4 years ago

Same issue on mattermost-server 5.21, just get a blank white window.

niklabh commented 4 years ago

hi guys sorry for being so late with support. make is not working anymore for build

make
go: github.com/mattermost/mattermost-server@v5.12.0+incompatible requires
    willnorris.com/go/imageproxy@v0.8.1-0.20190326225038-d4246a08fdec: invalid pseudo-version: does not match version-control timestamp (2019-04-22T23:49:45Z)
make: build/bin/manifest: Command not found
build/setup.mk:13: *** "Cannot parse id from plugin.json".  Stop.

Anybody can help me with this?

niklabh commented 4 years ago

i have published a new release:

https://github.com/niklabh/mattermost-plugin-webrtc-video/releases/tag/0.2.0

To call go to direct message and click video icon on top right

other person need to pick call for it to work Screenshot from 2020-03-19 12-44-21

franckadil commented 4 years ago

Hi @niklabh , thank you so much for your prompt reply, I really appreciate. I'll test the new release. asap.

niklabh commented 4 years ago

Not working for me either on 5.17.1. There is only blank popup: image

The user you are calling need to pick up the call Screenshot from 2020-03-19 12-49-57

Sorry for all the blank screen. I was planning to add user profile picture in the middle.

Guys please help here and Add some PRs. I would very much appreciate it. Seems like there is lot of interest in the plugin. I am busy with my day job nowadays too much. Sorry for late replies.

franckadil commented 4 years ago

@niklabh would it be helpful to spread the word on mainstream mattermost Repo ? And Maybe Some Dev events (Hackatlons, Community Development events...) ?

If that's helpful for your project and the community, let me know so I can start looking for extra community members willing to help out.

Yours sincerely,

niklabh commented 4 years ago

@niklabh would it be helpful to spread the word on mainstream mattermost Repo ? And Maybe Some Dev events (Hackatlons, Community Development events...) ?

If that's helpful for your project and the community, let me know so I can start looking for extra community members willing to help out.

That would be great. Thank you very much. Yes I would very much like some help from community members. Please spread the word.

niklabh commented 4 years ago

@niklabh would it be helpful to spread the word on mainstream mattermost Repo ? And Maybe Some Dev events (Hackatlons, Community Development events...) ?

If that's helpful for your project and the community, let me know so I can start looking for extra community members willing to help out.

Yours sincerely,

You can find me on community.mattermost.com with @niklabh

franckadil commented 4 years ago

@niklabh Thank you, I'll start spreading the word and look for opportunities to connect you/project with our community event manager to try to leverage on the community's potential.

This Project is really awesome and should get some extra love to boost things.

discostur commented 4 years ago

i just tried the new 0.2 release and it is still not working :/ same behaviour like old 0.1.

I just extracted the tar, put it to mattermost plugins dir and acitvated it via mattermost console. When i try to call someone, he gets a popup with incoming call. After accepting the call nothing happens :/

franckadil commented 4 years ago

@discostur Hi :smiley: , I have just tested and it works, here is the steps I followed:

The user needs also to turn on his cam and accept permissions.

I hope it helps.

franckadil commented 4 years ago

@niklabh The only thing that I noticed that doesn't is muting the microphone.

niklabh commented 4 years ago

@niklabh The only thing that I noticed that doesn't is muting the microphone.

Yes muting mocrophone is not setup right now. I'ill add a issue

niklabh commented 4 years ago

i just tried the new 0.2 release and it is still not working :/ same behaviour like old 0.1.

I just extracted the tar, put it to mattermost plugins dir and acitvated it via mattermost console. When i try to call someone, he gets a popup with incoming call. After accepting the call nothing happens :/

Can you try to follow franckadil steps

Could be beacause of webrtc signaling issues(which are hard to debug). Do you know if there is any error in console. Can you try to do on same computer different browsers.

franckadil commented 4 years ago

@niklabh for me it works, tested on 2 different laptops. But I can still see webrtc signal errors:

Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
2mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 signalling ukwgew5sbirezcacm1y3u1dszy
2/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 signalling ukwgew5sbirezcacm1y3u1dszy
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 signalling ukwgew5sbirezcacm1y3u1dszy
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 signalling ukwgew5sbirezcacm1y3u1dszy
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 message from ukwgew5sbirezcacm1y3u1dszy Connected with ukwgew5sbirezcacm1y3u1dszy
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 connected with ukwgew5sbirezcacm1y3u1dszy
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
2/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 Uncaught Error: cannot signal after peer is destroyed
    at f (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at c.signal (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.<anonymous> (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.s.emit (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at E (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at b (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at v.push (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
    at EventSource.n.onmessage (mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8)
mattermost-webrtc-video_e3d12b7180c82ed3_bundle.js:8 received signal Object
3/api/v4/logs:1 Failed to load resource: the server responded with a status of 401 ()
niklabh commented 4 years ago

@niklabh for me it works, tested on 2 different laptops. But I can still see webrtc signal errors:

will fix

MatthiasDamm commented 4 years ago

is there something to take care about when running mattermost in docker container and the plugin installed? it appears only white screen. Using the Desktop Mattermost App for Windows

discostur commented 4 years ago

ok im testing on mac os and windows - we both used the official mattermost desktop client. i didn't get any request to allow microphone / video.

if i try on mac os with chrome browser i get a request from the browser to allow microphone / camera after i accept the call. but then i still cant hear or see the other caller.

i looked in chrome debug consol but i didn't get any errors ... can you tell me what requests i have to look for?

i see requests to herokuap but that looks good:

Request URL: https://baatcheet.herokuapp.com/v1/baatcheet_video/1aukw8gw3fbzinbz88erkio7ey
Request Method: GET
Status Code: 200 OK
Remote Address: 34.236.76.223:443
Referrer Policy: no-referrer

Our mattermost server is not public (private lan) but all clients are in the same IP range.

ulab commented 4 years ago

Seems like there is lot of interest in the plugin.

I guess we'll have to thank Corona for the massive development of internet infrastructure and video conferencing...

niklabh commented 4 years ago

ok im testing on mac os and windows - we both used the official mattermost desktop client. i didn't get any request to allow microphone / video.

if i try on mac os with chrome browser i get a request from the browser to allow microphone / camera after i accept the call. but then i still cant hear or see the other caller.

i looked in chrome debug consol but i didn't get any errors ... can you tell me what requests i have to look for?

i see requests to herokuap but that looks good:

Request URL: https://baatcheet.herokuapp.com/v1/baatcheet_video/1aukw8gw3fbzinbz88erkio7ey
Request Method: GET
Status Code: 200 OK
Remote Address: 34.236.76.223:443
Referrer Policy: no-referrer

Our mattermost server is not public (private lan) but all clients are in the same IP range.

Desktop client i think will not work as they have a webview which does not prompt for allowing video and camera. Need to check if permissions needs to be added for the same in the plugin.

For webrtc signalling i am using https://github.com/mafintosh/signalhub deployed at https://baatcheet.herokuapp.com/ without access to internet it will not work. I wanted to move signalling to mattermost itself but coudn't found a way to send data from one client to another without showing them as messages.

discostur commented 4 years ago

ok so as far as the mattermost server and all clients can reache the internet it should work? that should work in our environment ... i will do another test with both clients running inside chrome browser

discostur commented 4 years ago

ok just did another test from chrome <-> chrome and on both laptops the camera led is green (which stands for activity) but i cannot see anything - just a white screen. audio is also not working. no errors in chrome console :/

franckadil commented 4 years ago

Hi everyone, I know it is confusing but we tested internally on a docker build, kubernetes and normal deployment. With the same result:

So here is how it works, the order is important:

1- refresh your browser if you already have attempted to call some one. otherwise it will not work 2- call you user and avoid clicking on the blue camera icon. 3- the user takes the call then they have to click on their blue video icon once and wait few seconds

It only works when following these steps, anything else breaks the call.

Make sure you don't have an adblocker.

discostur commented 4 years ago

ok we just did another test and we got it working! we followed @franckadil 's step by step guide and it is working.

we only got it working with both, client and caller running mattermost inside chrome. if we mix browsers it is not working anymore ...

franckadil commented 4 years ago

@discostur we need to spread the word and help. When this solution will be working correctly, it will be a very helpful and important peace of Mattermost for many people. I wish you success @niklabh and hope your work will attract many community folks who can land us some help with maintaining and adding features.

niklabh commented 4 years ago

@discostur we need to spread the word and help. When this solution will be working correctly, it will be a very helpful and important peace of Mattermost for many people. I wish you success @niklabh and hope your work will attract many community folks who can land us some help with maintaining and adding features.

Thanks @franckadil that is certainly the intention. I will also try to fix the reported bugs.

ltsavar commented 4 years ago

Thanks for the work you've done. At the moment the plugin won't work for me. I'm not able to answer a call. And also getting a blank window with 0.2.0 and mattermost version 5.19.1

milekz commented 4 years ago

v0.2.0 MM 5.21.0 (as docker container, behind nginx proxy) - blank screen, no connection.

franckadil commented 4 years ago

@ltsavar @milekz , Hi :smile: , please don't try several time in the same browser window, as it will keep failing. You need to refresh your browser and start with a fresh test following these steps:

https://github.com/niklabh/mattermost-plugin-webrtc-video/issues/1#issuecomment-601112892

Please also note that the browsers that are more likely to work are Chromium based (Microsoft Edge and Google Chrome).

Cheers,

Bables55 commented 4 years ago

I just introduced it for the first time. The video icon works as a single person in direct messages on my iPhone. However, users can't touch the camera or microphone icon to make a call. No video icon is displayed for each channel. On my Windows 10(Firefox, Vivaldi, (new)Edge), each channel has a video icon at the top. And it just says "Start Video Call" and doesn't work. Video icons isn't displayed in direct messages.

Is this plug-in supposed to use the old version of Mattermost (the one that was officially equipped with WebRTC)? In other words, isn't it possible to use the version that removes the WebRTC function from Mattermost?


Mattermost team 5.21.0