Connection failure (ICE error 1107)

[Andrew Brooks]

* Both myself and our service providers are going around in circles on this one. Can anyone advise on any tests that could help diagnose what is going wrong?

Moodle service provider confirms BBB server set up correctly
campus network service provider confirms firewall set up correctly

When creating a BBB session:
audio is OK
sharing a webcam results in Connection failure (ICE error 1107)
sharing screen results in a hang with Your screenshare is loading

about:webrtc log
has these messages:
Skipping STUN server because of address type mis-match
skipping UDP STUN server
failed to create passive TCP host candidate

about:webrtc ICE stats
shows:
ICE state succeeded where local candidate is my public IP address
ICE state failed where local candidate is a 172.17 address which is my vEthernet IP address
ICE state failed where local candidate is a 192.168 address which is my VirtualBox IP address
(IP address information from the output of ipconfig

Note when using campus WiFi
errors as above
about:webrtc ICE stats
shows:
ICE state succeeded where local candidate is my public IP address
ICE state inprogress
ICE state inprogress

Note when using a session at https://test.bigbluebutton.org/
webcam is shared OK
screen is shared OK

[Paulo Lanzarin]

Andy,

Since you did test with the reference mirror (test.bigbluebutton.org) in what I assume to be
equal client conditions, then it's very likely to be a configuration issue of sorts by the provider.

I recommend gathering which is the BBB version being used by them. I'll also assume the BBB

instance is not hosted in the university network?

Pasting the answer I gave on github. I recommend forwarding this to your service provider.

- Have you set up your own coturn instance with TURN+STUN?
- Review your server firewall policies, make sure your TURN instance is working.
- I also suggest reviewing this checklist if you're using Kurento as your media server:

• Add the networkInterfaces config option to your install scripts. It's configured in /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini. You should set it to whichever is the default, public network interface in your server (in this case, ens2).
  • If the NIF has unwanted IPs (ie private intranet IPs for VPS comms which are not used for media exchange), you can add them to ipIgnoreList
• Please set niceAgentIceTcp (/etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini) to 0 if you're not using TCP for media comm (that's BBB's default, so it can be set to 0)
• /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini -> Set externalIPv4 if your server is behind NAT
• /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini -> stunServerAddress/stunServerPort: this config is superseded by externalIPv4 the absolute majority of scenarios, so you don't need to set it. Cases where you do need to set it is on premises deployments where you need media to work both over the intranet and the internet at the same time.

--
You received this message because you are subscribed to the Google Groups "bigbluebutton-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-users/b5bbf692-5801-419d-943d-265141471319n%40googlegroups.com.

[Paulo Lanzarin]

If that's also easy to do, please repeat the tests you made with the problematic network in the

following server: test25.bigbluebutton.org.

Thanks.

[Andrew Brooks]

https://test25.bigbluebutton.org/

tests on Ethernet LAN and campus WiFi (eduroam) were successful

we could share webcam and screen OK

- I am waiting for a response from our Moodle/BBB service provider

Andy

[Andrew Brooks]

Our BBB service provider had to replace some hardware. BBB is now OK:-) So there was nothing wrong with servers or firewalls across our various service providers. (With multiple service providers, it takes time to be sure the fault does not lie with software.)
Andrew Brooks