P2P OK, third party joins - "conference.videobridgeNotAvailable"

I can establish P2P connections between two parties each. Once a third party joins the conference, all devices show “there was a problem, we try to fix it (hehe), retry xx seconds” (or so).

The only instance, which I can examine, is the PC. Chrome developer console shows something self-explanatory:

Logger.js:154 2021-08-28T07:32:16.996Z [conference.js] <ne._onConferenceFailed>: CONFERENCE FAILED: conference.videobridgeNotAvailable

So, the JVB seems to be unreachable, which is involved, once the third party joins. Just — why? :slight_smile:

If I run this on my PC:

~ $ nc -u -v 80.133.188.133 10000
Connection to 80.133.188.133 port 10000 [udp/ndmp] succeeded!
abcd
abcd

and the same time this on the Jetson:

ubuntu@jitsi-meet:~$ sudo tcpdump 'port 10000 and udp'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
10:15:37.772759 IP p5085bc85.dip0.t-ipconnect.de.49912 > jitsi-meet.ddns.net.10000: UDP, length 1
10:15:37.773469 IP p5085bc85.dip0.t-ipconnect.de.49912 > jitsi-meet.ddns.net.10000: UDP, length 1
10:15:37.773504 IP p5085bc85.dip0.t-ipconnect.de.49912 > jitsi-meet.ddns.net.10000: UDP, length 1
10:15:37.773610 IP p5085bc85.dip0.t-ipconnect.de.49912 > jitsi-meet.ddns.net.10000: UDP, length 1
10:15:41.308686 IP p5085bc85.dip0.t-ipconnect.de.49912 > jitsi-meet.ddns.net.10000: UDP, length 5
10:15:45.427691 IP p5085bc85.dip0.t-ipconnect.de.49912 > jitsi-meet.ddns.net.10000: UDP, length 5

…then at least for me it looks like as connectivity could be there…

My jvb.conf contained this (on advice of the forum here):

 sctp {
      enabled = false
    }

This caused this entry in jvb.log:

JVB 2021-08-28 10:42:07.383 SEVERE: [47] [confId=4dee65325f90505c gid=30219 conf_name=conservativethresholdsreducegently@conference.jitsi-meet.ddns.net] ConferenceShim.handleColibriConferenceIQ#483: Error processing sctp connections in IQ: feature-not-implemented SCTP support is not configured

Re-enabled it, restarted the service.

Log now says this on reconnection attempt:

JVB 2021-08-28 10:51:33.696 WARNING: [57] [confId=9f1dd2bab0bb6848 gid=7160 conf_name=silversystemsvanishlikewise@conference.jitsi-meet.ddns.net] ConferenceShim.lambda$new$0#98: Failed to handle colibri request: 
java.lang.NoClassDefFoundError: Could not initialize class org.jitsi.videobridge.sctp.SctpManager
	at org.jitsi.videobridge.Endpoint.createSctpConnection(Endpoint.kt:530)
	at org.jitsi.videobridge.shim.ContentShim.createSctpConnection(ContentShim.java:165)
	at org.jitsi.videobridge.shim.ContentShim.getOrCreateSctpConnectionShim(ContentShim.java:357)
	at org.jitsi.videobridge.shim.ColibriUtil.processSctpConnections(ColibriUtil.java:198)
	at org.jitsi.videobridge.shim.ConferenceShim.handleColibriConferenceIQ(ConferenceShim.java:478)
	at org.jitsi.videobridge.shim.ConferenceShim.lambda$new$0(ConferenceShim.java:83)
	at org.jitsi.utils.queue.PacketQueue$HandlerAdapter.handleItem(PacketQueue.java:381)
	at org.jitsi.utils.queue.AsyncQueueHandler$1.run(AsyncQueueHandler.java:133)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

Successfully replaced one evil with another. Mission accomplished :slight_smile:

Related issue Posibility of proper ARM packaging for JVB2? - #21 by cal413 ??

Make sure you disable sctp and in jicofo.
Normally the error bridge not available is that jvb did not join the brewery room, which jicofo uses to discover available bridges.

Sorry, what do you mean?

When disabling sctp, that need to be done in jvb.conf but also and in jicofo jicofo/reference.conf at aa46146df402042c19cbe459d937291c43036988 · jitsi/jicofo · GitHub

And make sure when you restart the bridge you see it in the logs of jicofo … if not check jvb logs why it doesn’t connect to the brewery room

There are so many scattered configuration files, where is this?

I found /etc/jitsi/jicofo/jicofo.conf and added

sctp {
    enabled = false
  }

/var/log/jitsi/jicofo.log says at restart:

Jicofo 2021-08-28 16:47:06.047 INFO: [27] [type=bridge brewery=jvbbrewery] BaseBrewery.removeInstance#370: Removed brewery instance: jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693

Jicofo 2021-08-28 16:47:06.047 INFO: [27] BridgeSelector.removeJvbAddress#135: Removing JVB: jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693

Jicofo 2021-08-28 16:47:06.048 INFO: [27] JvbDoctor.removeBridge#152: Stopping health-check task for: jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693

Jicofo 2021-08-28 16:47:14.877 INFO: [27] [type=bridge brewery=jvbbrewery] BaseBrewery.addInstance#358: Added brewery instance: jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693

Jicofo 2021-08-28 16:47:14.878 INFO: [27] BridgeSelector.addJvbAddress#118: Added new videobridge: Bridge[jid=jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693, relayId=null, region=null, stress=0.00]

Jicofo 2021-08-28 16:47:14.878 INFO: [27] JvbDoctor.addBridge#140: Scheduled health-check task for: jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693

jvb.log:

JVB 2021-08-28 16:47:09.227 INFO: [12] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester, face=/192.168.190.25, mask=/80.133.188.133
JVB 2021-08-28 16:47:09.229 INFO: [12] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Initialized mapping harvesters (delay=1182ms).  stunDiscoveryFailed=false
JVB 2021-08-28 16:47:09.533 INFO: [17] [hostname=localhost id=shard] MucClient.initializeConnectAndJoin#227: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=shard domain=auth.jitsi-meet.ddns.net hostname=localhost port=null username=jvb mucs=[JvbBrewery@internal.auth.jitsi-meet.ddns.net] mucNickname=c0402e5f-b067-49ab-a6b4-5c47fff76693 disableCertificateVerification=false]
JVB 2021-08-28 16:47:09.622 INFO: [1] LastNReducer.<init>#65: LastNReducer with reductionScale: 0.75 recoverScale: 1.25 impactTime: PT1M minLastN: 1 maxEnforcedLastN: 40
JVB 2021-08-28 16:47:09.627 INFO: [1] TaskPools.<clinit>#81: TaskPools detected 4 processors, creating the CPU pool with that many threads
JVB 2021-08-28 16:47:09.669 INFO: [17] [hostname=localhost id=shard] MucClient.initializeConnectAndJoin#302: Dispatching a thread to connect and login.
JVB 2021-08-28 16:47:09.731 INFO: [1] UlimitCheck.printUlimits#115: Running with open files limit 65000 (hard 65000), thread limit 65000 (hard 65000).
JVB 2021-08-28 16:47:09.735 INFO: [1] VideobridgeExpireThread.start#88: Starting with 60 second interval.
JVB 2021-08-28 16:47:09.809 INFO: [1] HealthChecker.start#118: Started with interval=10000, timeout=PT30S, maxDuration=PT3S, stickyFailures=false.
JVB 2021-08-28 16:47:09.867 INFO: [1] MainKt.main#112: Not starting CallstatsService, disabled in configuration.
JVB 2021-08-28 16:47:09.878 INFO: [1] MainKt.main#121: Starting public http server
JVB 2021-08-28 16:47:10.046 INFO: [1] ColibriWebSocketService.<init>#40: Base URL: wss://jitsi-meet.ddns.net:8443/colibri-ws/default-id
JVB 2021-08-28 16:47:10.153 INFO: [1] org.eclipse.jetty.util.log.Log.initialized: Logging initialized @3851ms to org.eclipse.jetty.util.log.JavaUtilLog
JVB 2021-08-28 16:47:10.414 INFO: [1] ColibriWebSocketService.registerServlet#65: Registering servlet at /colibri-ws/*, baseUrl = wss://jitsi-meet.ddns.net:8443/colibri-ws/default-id
JVB 2021-08-28 16:47:10.474 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.40.v20210413; built: 2021-04-13T20:42:42.668Z; git: b881a572662e1943a14ae12e7e1207989f218b74; jvm 11.0.11+9-Ubuntu-0ubuntu2.20.04
JVB 2021-08-28 16:47:10.659 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@76304b46{/,null,AVAILABLE}
JVB 2021-08-28 16:47:10.704 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@323e8306{HTTP/1.1, (http/1.1)}{0.0.0.0:9090}
JVB 2021-08-28 16:47:10.705 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @4405ms
JVB 2021-08-28 16:47:10.709 INFO: [1] MainKt.main#139: Starting private http server
JVB 2021-08-28 16:47:10.904 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.40.v20210413; built: 2021-04-13T20:42:42.668Z; git: b881a572662e1943a14ae12e7e1207989f218b74; jvm 11.0.11+9-Ubuntu-0ubuntu2.20.04
JVB 2021-08-28 16:47:10.923 INFO: [17] [hostname=localhost id=shard] MucClient$1.connected#259: Connected.
JVB 2021-08-28 16:47:10.924 INFO: [17] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$8#597: Logging in.
JVB 2021-08-28 16:47:11.155 INFO: [17] [hostname=localhost id=shard] MucClient$1.authenticated#265: Authenticated, b=false
JVB 2021-08-28 16:47:11.258 INFO: [17] [hostname=localhost id=shard] MucClient$MucWrapper.join#723: Joined MUC: jvbbrewery@internal.auth.jitsi-meet.ddns.net
JVB 2021-08-28 16:47:12.104 WARNING: [1] org.glassfish.jersey.server.wadl.WadlFeature.configure: JAXBContext implementation could not be found. WADL feature is disabled.
JVB 2021-08-28 16:47:12.515 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Health registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Health will be ignored. 
JVB 2021-08-28 16:47:12.517 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Version will be ignored. 
JVB 2021-08-28 16:47:13.455 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@7be2f29a{/,null,AVAILABLE}
JVB 2021-08-28 16:47:13.460 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@3b152928{HTTP/1.1, (http/1.1)}{127.0.0.1:8080}
JVB 2021-08-28 16:47:13.461 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @7160ms
JVB 2021-08-28 16:47:19.806 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.001704S. Sticky failure: false
JVB 2021-08-28 16:47:29.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000026S. Sticky failure: false
JVB 2021-08-28 16:47:39.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000022S. Sticky failure: false
JVB 2021-08-28 16:47:49.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000019S. Sticky failure: false
JVB 2021-08-28 16:47:59.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.00002S. Sticky failure: false
JVB 2021-08-28 16:48:09.739 INFO: [23] VideobridgeExpireThread.expire#140: Running expire()
JVB 2021-08-28 16:48:09.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000021S. Sticky failure: false
JVB 2021-08-28 16:48:19.804 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000019S. Sticky failure: false
JVB 2021-08-28 16:48:29.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000019S. Sticky failure: false
JVB 2021-08-28 16:48:39.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000024S. Sticky failure: false
JVB 2021-08-28 16:48:49.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000017S. Sticky failure: false
JVB 2021-08-28 16:48:59.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000018S. Sticky failure: false
JVB 2021-08-28 16:49:09.740 INFO: [23] VideobridgeExpireThread.expire#140: Running expire()
JVB 2021-08-28 16:49:09.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000019S. Sticky failure: false
JVB 2021-08-28 16:49:19.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.00002S. Sticky failure: false
JVB 2021-08-28 16:49:29.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000018S. Sticky failure: false
JVB 2021-08-28 16:49:39.804 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000021S. Sticky failure: false
JVB 2021-08-28 16:49:49.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000017S. Sticky failure: false
JVB 2021-08-28 16:49:59.803 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000044S. Sticky failure: false
JVB 2021-08-28 16:50:09.739 INFO: [23] VideobridgeExpireThread.expire#140: Running expire()
JVB 2021-08-28 16:50:09.804 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000019S. Sticky failure: false
JVB 2021-08-28 16:50:19.804 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000018S. Sticky failure: false
JVB 2021-08-28 16:50:29.804 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.000018S. Sticky failure: false
JVB 2021-08-28 16:50:41.660 INFO: [1] JitsiConfig.<clinit>#47: Initialized newConfig: merge of /etc/jitsi/videobridge/jvb.conf: 1,application.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/application.conf: 1,system properties,reference.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/jitsi-media-transform-1.0-247-g900cc79.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/ice4j-3.0-33-g311a495.jar!/reference.conf: 1
JVB 2021-08-28 16:50:41.742 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#51: loading config file at path /etc/jitsi/videobridge/sip-communicator.properties
JVB 2021-08-28 16:50:41.751 INFO: [1] JitsiConfig.<clinit>#68: Initialized legacyConfig: sip communicator props (no description provided)
JVB 2021-08-28 16:50:41.760 INFO: [1] JitsiConfig$Companion.reloadNewConfig#94: Reloading the Typesafe config source (previously reloaded 0 times).
JVB 2021-08-28 16:50:41.838 INFO: [1] MainKt.main#83: Starting jitsi-videobridge version 2.1.538-g062e9f56
JVB 2021-08-28 16:50:43.008 INFO: [13] org.ice4j.ice.harvest.StunMappingCandidateHarvester.discover: Discovered public address 80.133.188.133:37334/udp from STUN server 193.122.15.164:443/udp using local address 192.168.190.25:0/udp
JVB 2021-08-28 16:50:43.021 INFO: [12] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester, face=/192.168.190.25, mask=/80.133.188.133
JVB 2021-08-28 16:50:43.022 INFO: [12] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Initialized mapping harvesters (delay=1169ms).  stunDiscoveryFailed=false
JVB 2021-08-28 16:50:43.333 INFO: [17] [hostname=localhost id=shard] MucClient.initializeConnectAndJoin#227: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=shard domain=auth.jitsi-meet.ddns.net hostname=localhost port=null username=jvb mucs=[JvbBrewery@internal.auth.jitsi-meet.ddns.net] mucNickname=c0402e5f-b067-49ab-a6b4-5c47fff76693 disableCertificateVerification=false]
JVB 2021-08-28 16:50:43.419 INFO: [1] LastNReducer.<init>#65: LastNReducer with reductionScale: 0.75 recoverScale: 1.25 impactTime: PT1M minLastN: 1 maxEnforcedLastN: 40
JVB 2021-08-28 16:50:43.423 INFO: [1] TaskPools.<clinit>#81: TaskPools detected 4 processors, creating the CPU pool with that many threads
JVB 2021-08-28 16:50:43.455 INFO: [17] [hostname=localhost id=shard] MucClient.initializeConnectAndJoin#302: Dispatching a thread to connect and login.
JVB 2021-08-28 16:50:43.491 INFO: [1] UlimitCheck.printUlimits#115: Running with open files limit 65000 (hard 65000), thread limit 65000 (hard 65000).
JVB 2021-08-28 16:50:43.496 INFO: [1] VideobridgeExpireThread.start#88: Starting with 60 second interval.
JVB 2021-08-28 16:50:43.546 INFO: [1] HealthChecker.start#118: Started with interval=10000, timeout=PT30S, maxDuration=PT3S, stickyFailures=false.
JVB 2021-08-28 16:50:43.607 INFO: [1] MainKt.main#112: Not starting CallstatsService, disabled in configuration.
JVB 2021-08-28 16:50:43.619 INFO: [1] MainKt.main#121: Starting public http server
JVB 2021-08-28 16:50:43.799 INFO: [1] ColibriWebSocketService.<init>#40: Base URL: wss://jitsi-meet.ddns.net:8443/colibri-ws/default-id
JVB 2021-08-28 16:50:43.867 INFO: [1] org.eclipse.jetty.util.log.Log.initialized: Logging initialized @3766ms to org.eclipse.jetty.util.log.JavaUtilLog
JVB 2021-08-28 16:50:44.121 INFO: [1] ColibriWebSocketService.registerServlet#65: Registering servlet at /colibri-ws/*, baseUrl = wss://jitsi-meet.ddns.net:8443/colibri-ws/default-id
JVB 2021-08-28 16:50:44.163 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.40.v20210413; built: 2021-04-13T20:42:42.668Z; git: b881a572662e1943a14ae12e7e1207989f218b74; jvm 11.0.11+9-Ubuntu-0ubuntu2.20.04
JVB 2021-08-28 16:50:44.396 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@33c2bd{/,null,AVAILABLE}
JVB 2021-08-28 16:50:44.461 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@67ef029{HTTP/1.1, (http/1.1)}{0.0.0.0:9090}
JVB 2021-08-28 16:50:44.462 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @4362ms
JVB 2021-08-28 16:50:44.466 INFO: [1] MainKt.main#139: Starting private http server
JVB 2021-08-28 16:50:44.686 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.40.v20210413; built: 2021-04-13T20:42:42.668Z; git: b881a572662e1943a14ae12e7e1207989f218b74; jvm 11.0.11+9-Ubuntu-0ubuntu2.20.04
JVB 2021-08-28 16:50:44.721 INFO: [17] [hostname=localhost id=shard] MucClient$1.connected#259: Connected.
JVB 2021-08-28 16:50:44.722 INFO: [17] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$8#597: Logging in.
JVB 2021-08-28 16:50:44.915 INFO: [17] [hostname=localhost id=shard] MucClient$1.authenticated#265: Authenticated, b=false
JVB 2021-08-28 16:50:44.974 INFO: [17] [hostname=localhost id=shard] MucClient$MucWrapper.join#723: Joined MUC: jvbbrewery@internal.auth.jitsi-meet.ddns.net
JVB 2021-08-28 16:50:45.894 WARNING: [1] org.glassfish.jersey.server.wadl.WadlFeature.configure: JAXBContext implementation could not be found. WADL feature is disabled.
JVB 2021-08-28 16:50:46.292 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Health registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Health will be ignored. 
JVB 2021-08-28 16:50:46.293 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Version will be ignored. 
JVB 2021-08-28 16:50:47.186 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@c017175{/,null,AVAILABLE}
JVB 2021-08-28 16:50:47.191 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@3c818ac4{HTTP/1.1, (http/1.1)}{127.0.0.1:8080}
JVB 2021-08-28 16:50:47.192 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @7092ms

However, the problem remains. Third party joins - break down on all devices.

Logger.js:154 2021-08-28T14:53:48.642Z [conference.js] <ne._onConferenceFailed>:  CONFERENCE FAILED: conference.videobridgeNotAvailable
o @ Logger.js:154
Logger.js:154

jvb.log still saying:

JVB 2021-08-28 16:55:58.191 SEVERE: [45] [confId=7e4827974434e7da gid=41769 conf_name=credibleromancesprojecthardly@conference.jitsi-meet.ddns.net] ConferenceShim.handleColibriConferenceIQ#483: Error processing sctp connections in IQ: feature-not-implemented SCTP support is not configured

jicofo.log:

Jicofo 2021-08-28 16:57:03.615 SEVERE: [278] [room=credibleromancesprojecthardly@conference.jitsi-meet.ddns.net meeting_id=b5d2a84d-312c-4f5d-a171-983281d67ce3] AbstractChannelAllocator.allocateChannels#299: jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693 - failed to allocate channels, will consider the bridge faulty: XMPP error: <iq to='focus@auth.jitsi-meet.ddns.net/focus' from='jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693' id='JoSFI-11477' type='error'><error type='cancel'><feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/><text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas' xml:lang='en'>SCTP support is not configured</text></error></iq>
org.jitsi.protocol.xmpp.colibri.exception.ColibriException: XMPP error: <iq to='focus@auth.jitsi-meet.ddns.net/focus' from='jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693' id='JoSFI-11477' type='error'><error type='cancel'><feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/><text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas' xml:lang='en'>SCTP support is not configured</text></error></iq>
	at org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.maybeThrowOperationFailed(ColibriConferenceImpl.java:349)
	at org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.createColibriChannels(ColibriConferenceImpl.java:253)
	at org.jitsi.protocol.xmpp.colibri.ColibriConference.createColibriChannels(ColibriConference.java:97)
	at org.jitsi.jicofo.ParticipantChannelAllocator.doAllocateChannels(ParticipantChannelAllocator.java:122)
	at org.jitsi.jicofo.AbstractChannelAllocator.allocateChannels(AbstractChannelAllocator.java:253)
	at org.jitsi.jicofo.AbstractChannelAllocator.doRun(AbstractChannelAllocator.java:172)
	at org.jitsi.jicofo.AbstractChannelAllocator.run(AbstractChannelAllocator.java:133)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
Jicofo 2021-08-28 16:57:03.616 SEVERE: [279] [room=credibleromancesprojecthardly@conference.jitsi-meet.ddns.net meeting_id=b5d2a84d-312c-4f5d-a171-983281d67ce3] AbstractChannelAllocator.allocateChannels#299: jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693 - failed to allocate channels, will consider the bridge faulty: Creator thread has failed to allocate channels: XMPP error: <iq to='focus@auth.jitsi-meet.ddns.net/focus' from='jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693' id='JoSFI-11477' type='error'><error type='cancel'><feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/><text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas' xml:lang='en'>SCTP support is not configured</text></error></iq>
org.jitsi.protocol.xmpp.colibri.exception.ColibriException: Creator thread has failed to allocate channels: XMPP error: <iq to='focus@auth.jitsi-meet.ddns.net/focus' from='jvbbrewery@internal.auth.jitsi-meet.ddns.net/c0402e5f-b067-49ab-a6b4-5c47fff76693' id='JoSFI-11477' type='error'><error type='cancel'><feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/><text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas' xml:lang='en'>SCTP support is not configured</text></error></iq>
	at org.jitsi.protocol.xmpp.colibri.exception.ColibriException.clone(ColibriException.java:32)
	at org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl$ConferenceCreationSemaphore.acquire(ColibriConferenceImpl.java:891)
	at org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.acquireCreateConferenceSemaphore(ColibriConferenceImpl.java:385)
	at org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.createColibriChannels(ColibriConferenceImpl.java:222)
	at org.jitsi.protocol.xmpp.colibri.ColibriConference.createColibriChannels(ColibriConference.java:97)
	at org.jitsi.jicofo.ParticipantChannelAllocator.doAllocateChannels(ParticipantChannelAllocator.java:122)
	at org.jitsi.jicofo.AbstractChannelAllocator.allocateChannels(AbstractChannelAllocator.java:253)
	at org.jitsi.jicofo.AbstractChannelAllocator.doRun(AbstractChannelAllocator.java:172)
	at org.jitsi.jicofo.AbstractChannelAllocator.run(AbstractChannelAllocator.java:133)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
Jicofo 2021-08-28 16:57:09.374 INFO: [279] ConferenceIqHandler.handleConferenceIq#56: Focus request for room: credibleromancesprojecthardly@conference.jitsi-meet.ddns.net

Then it seems to me you didn’t add the config correctly … make sure you follow the structure of the config …
The sctp { you added is it inside the jicofo { ?

# Jicofo HOCON configuration. See /usr/share/jicofo/jicofo.jar/reference.conf for
#available options, syntax, and default values.
jicofo {
  xmpp: {
    client: {
      client-proxy: focus.jitsi-meet.ddns.net
    }
    trusted-domains: recorder.jitsi-meet.ddns.net
  }
  sctp {
    // Whether to allocate SCTP channels on the bridge (only when the client advertises support, and SCTP is
    // enabled in the per-conference configuration).
    enabled = false
  }
  bridge: {
    brewery-jid: "JvbBrewery@internal.auth.jitsi-meet.ddns.net"
  }
}

jvb.conf:

videobridge {
    http-servers {
        public {
            port = 9090
        }
    }
    sctp {
      enabled = false
    }
    websockets {
        enabled = true
        domain = "jitsi-meet.ddns.net:8443"
        tls = true
    }
}

Nice. Now it works (at least once). What I did? I restarted the entire machine, not only the JVB service (as before) :slight_smile:

When you change jicofo config, you need to restart jicofo …

Arghh… How is this supposed to be done?

Anyway, one question: I now stumbled twice over this “sctp”. Why isn’t it disabled by default? It seems to prevent a lot of functionality…

BTW: Thanks for helping me on a weekend. I admit, I had a lot of problems these days, but your support (and the support given of your colleagues (?)) is simply awesome.

It would be great to see, who of the supporters here is connected to Jitsi (developer, support, etc.) in order to address the right people.

E.g. as Nvidia does in their forum. You always see, if the guy you are talking too is from Nvidia or an ordinary user

Sctp works on intel machines by default.
Websockets require configuration in nginx, so update from sctp to websockets is not possible at the moment for older deployments … so we haven’t worked on enabling that …

Ok, thanks for clarifying this.

Meanwhile (now that my setup works) I see a bit clearer how it is (supposingly) working. On another thread I was a bit worried about TURN and firewall settings. It TURNs out :slight_smile: that port 10000 is the central port of your universe. I don’t know what the TURN server is internally doing, maybe it enables the multiplexing of more than one stream over port 10000, so it is not the TURN I know from plain P2P connections…

I need to dive deeper, but after I have connected my PC via a tethered LTE connection I saw, that the PC received an OFFER already containing the srvrflx public address of my Jitis instance, port 10000, so not even Trickle ICE is used, that makes the decision for what connection to use easy for my PC.

So please understand my comments regarding TURN and firewall from the limited understanding I had with special focus on TURN usage in plain P2P connections :slight_smile: I mean the comments on this thread Prosody source installation not recognized by jitsi-meet installer - #13 by spongebob

I’m really excited about the concept. In the past I have played a bit with Kurento and Janus, at least Kurento as far as I remember, did also made use of TURN the P2P way: A central public server, reachable on the Internet and all relay ports wide open.

Looking forward to learn more about your solution. Is there more general information available? For the dummies?

All you can find is in the handbook, jitsi.org website, and here in the forum.
Architecture · Jitsi Meet Handbook