Free BBB Access

[girish]

@doodlemania2 hopefully soon. https://git.cloudron.io/cloudron/box/-/issues/764 is the issue

[cyberfreakde]

@doodlemania2 Hey is the offer still there?

[doodlemania2]

@cyberfreakde Yep - I offer free 30 day access to US or EU BBB instance. Send me a DM and I'll set you up!

[micmc]

@brutalbirdie said in Free BBB Access:

Single or Cluster?
And more important what about a turn server?

• I've fully installed BBB on a powerful dedicated server at Hetzner. (not to compete against @doodlemania2 though lol )

• Then, I've fully installed a TURN server (coturn for instance) on its own server on a quite powerful enough VPS server. (didn't want to use the one on CR to keep it for its own use)

• I've setup ufw on both and doubled, if not tripled, verified on both both were having the correct UDP ports open. No hardware FW is active.

• I've had previously installed Greenlight from my CR.

Everything connects together and seems to be running perfectly for video and screen sharing, except for the AUDIO, for which I keep getting the 1007 error, which is supposed to be caused by UDP configuration.
I've checked my ufw on both servers several times and it seems I cannot see where the 'fault' is in the firewall config I've set according to:
https://docs.bigbluebutton.org/admin/setup-turn-server.html
AND
https://docs.bigbluebutton.org/2.3/install.html

Anyone of you have a clue I've overlooked not in the 'manual' (these are not always accurate, I know) can maybe tell what I may have missed, or know by experience what the glitch could be (even if the glitch is me loll)

Thanks.

[luckow]

@micmc the easiest way is to use https://github.com/ebbba-org/ansible-role-bigbluebutton It is also possible to install the latest version 2.4.rc5, which works like a charm.

[jdaviescoates]

@luckow I believe @BrutalBirdie here maintains that ansible role too

[robi]

@micmc I'm getting to check port expectations.

[BrutalBirdie]

@robi
my official Ansible Role version can be tested here https://meet.bigbluebutton.dev/ deployed with https://github.com/ebbba-org/ansible-role-bigbluebutton

[micmc]

@luckow said in Free BBB Access:

@micmc the easiest way is to use https://github.com/ebbba-org/ansible-role-bigbluebutton It is also possible to install the latest version 2.4.rc5, which works like a charm.

As well as @robi and @BrutalBirdie in essence what you are saying is I'm fu..ed up and should restart from scratch and wasted time to do it all manually? loll
Well, nevertheless I haven't wasted too much time anyway, because as usual with such things we always learn a thing or two "au passage" while struggling, this is how we become better. I wouldn't be here I haven't had started with 'dockerology" on AWS a few years back

Now, one last question folks after going through quickly reading the Ansible script as an overview, I'll take a deeper look now but I was under the impression that the TURN is installed on the same server as BBB am I dreaming or missing something? ...

Cheers!

[BrutalBirdie]

@micmc sorry but the variables are so big for errors.
https://docs.bigbluebutton.org/support/troubleshooting.html#webrtc-errors-1001-1002

1007: ICE negotiation failed - The browser and FreeSWITCH try to negotiate ports to use to stream the media and that negotiation failed. Possible Causes:

NAT is blocking the connection
Firewall is blocking the UDP connection/ports

I am never running coturn on the same server as BBB, since I want my coturn to run on port 443 for very restrictive networks.
For example state agencies who only allow outgoing 80,443,25,465,587 and some more.

You can check your turn server here: https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/
When starting a BBB Session press F12 go to the console and search for turn you will the credentials for this session which you can use for testing with trickle-ice.

Looks something like this

Sun Nov 28 2021 10:46:52 GMT+0100 (Central European Standard Time) | sip.UserAgent | · sessionDescriptionHandlerFactoryOptions: {"peerConnectionConfiguration":{"iceServers":[{"urls":"stun:turn.DOMAIN.TLD"},{"urls":"turns:DOMAIN.TLD:443?transport=tcp","credential":"N0ABNdyp4PaFQLowdq8sekjgGjI=","username":"1638179212:w_mcllm4lvdd4y"}],"sdpSemantics":"unified-plan"}}

Also a good place to look in firefox is about:webrtc to see where the connection between your client and the server the error occurs.

Like I said, many variables

edit:
Also you can force the usage of turn in firefox by going to about:config and setting media.peerconnection.ice.relay_only to true this way turn is forced.