Load balancing and ICE config

#1

Hello,
In a load balancing setup where I have video bridges on separate machines.
How is the ICE setup should be?

Is it a requirements each VB should has it is own public IP address?

or private IP address is enough if all the video brigades and Jitsi app on the same network?

In particular: what will be the config for this config in the VB?

org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=<Local.IP.Address>
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=<Public.IP.Address>

Please let me know and thank you for your help and support.

0 Likes

#2

If all jitsi-meet apps are in the same network as the jvb, you don’t need to configure anything on the jvb side, it will pick up its address automatically.

You need to configure local and public address in case jvb is accessed through an ip address which is not configured on the machine and cannot be discovered automatically (NAT and port forwarding also needs to be configured).

When there are multiple bridges you normally setup every one behind its own public address.

0 Likes

#3

Here is my setup:
10.0.19.4, ( public IP also ) My jitsi web app and first bridge are on this machine
10.0.19.5 only video bridge on this machine

on the above setup both considered on the same network up to your answer.
Why I need to setup each VB behind it is own public IP if it is on a separate machine?

Thank you for your help.

0 Likes

#4

When I remove these to lines

org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=<Local.IP.Address>
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=<Public.IP.Address>

from the VB on the separate machine, I start a call with 3 people two cameras are black with no picture.
and the separate VB reports this errors:

JVB 2019-04-09 15:46:50.514 INFO: [926] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 192.168.56.1:55864/udp/host (stream.RTP)
JVB 2019-04-09 15:46:50.534 INFO: [926] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 172.30.176.1:55865/udp/host (stream.RTP)
JVB 2019-04-09 15:46:50.555 INFO: [926] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 10.0.75.1:55866/udp/host (stream.RTP)
JVB 2019-04-09 15:46:50.576 INFO: [926] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 172.17.52.81:55867/udp/host (stream.RTP)
JVB 2019-04-09 15:46:50.598 INFO: [926] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 172.31.99.87:55868/udp/host (stream.RTP)
JVB 2019-04-09 15:46:50.619 INFO: [926] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 192.168.56.1:55864/udp/host (stream.RTP)
JVB 2019-04-09 15:46:50.639 INFO: [926] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 172.30.176.1:55865/udp/host (stream.RTP)
JVB 2019-04-09 15:46:50.660 INFO: [926] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 10.0.75.1:55866/udp/host (stream.RTP)
JVB 2019-04-09 15:46:50.680 INFO: [926] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 172.17.52.81:55867/udp/host (stream.RTP)
JVB 2019-04-09 15:46:50.701 INFO: [926] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 172.31.99.87:55868/udp/host (stream.RTP)

0 Likes

#5

I don’t understand very well your setup.
I see the clients are in 192.168, 172.30, 10.0.75, 172.17., 172.3, but there is none in the jvb network, which ip is 10.0.19.X
Does the client have access directly to 10.0.19.X addresses? And do jvb have access to its network?

Let’s give you an example to understand how things work. There are two cases with and without nat.

  • without nat - jvb sees its public address from the machine’s interface and add it to the signaling saying to the world, hey you can reach me. If the same jvb is behind nat and no public address is configured, it will take for example 192.168.0.2 and will send it to the rest of the world through signaling saying hey you can reach me here and this will not work.
  • with nat and with configured public address a.a.a.a, so jvb will announce a.a.a.a and 192.168.0.2 to the world and will say you can reach me here or here. Mind that udp 10000 is forwarded form a.a.a.a to 192.168.0.2. So if you are somewhere on Internet and you receive that offer and start sending packets to a.a.a.a udp 10000 those packets will be forwarded and will reach jvb and he will start sending back and everything will work. If the client happens to be in 192.168.0.X or any network that can have direct two-way communication with 192.168.0.2 that will be the ice candidate that will succeed and will be used, and there you will have a client connected to the bridge on its internal address.
0 Likes

#6

Thank you Damencho for explaining this,I am not really sure where is these IPs comes from it is not my IPs. the once started with 192.168…
I can explain more about how is my setup installed:

Machine one:
Public IP:52.16.16.27
Private IP: 10.0.19.4

Jitsi meet app
jicofo
prosody ( I have tried everything to make this to work with the public IP nothing ever worked I get this erro:
socket warn server.lua, [52.16.16.27]:5347: Cannot assign requested address
Apr 10 05:17:41 portmanager error Failed to open server port 5347 on 52.16.16.27, Cannot assign requested address
However, I got working if I use the private IP.

JVB: sip-communicator has the private and public IP set as the NAT setup suggestion.
( Machine one connecting and working fine, even after all the setup for the load balancing )

Machine 2:
Private IP ( 10.0.19.5)
JVB Conneting to prosody just find and gets authenticated successfully if prosody in machine one working on the private IP).

the problem starts when I have call with more than 2 users. where we need jicofo and the JVB. I start to see ICE errors in this bridge. the call continues but the other 2 users has no video. I have tried everything but still not working. I have tried the NAT setup also in that JVB, I did set the public IP to a Coturn server I have but it it didn’t work.

I am pretty sure all the machines are in the same network and the same netmask as well.

below is the errors I get once I connect 3 users:

Thank you for your help and looking into this problem.

JVB 2019-04-10 05:52:31.065 FINE: [166] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 75XXc-229):
JVB 2019-04-10 05:52:31.426 INFO: [29] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=fc132c1d43f80f5a conf_name=null,logging=false,conf_count=2,ch_count=9,v_streams=9
JVB 2019-04-10 05:52:31.443 WARNING: [26] org.jitsi.videobridge.EndpointMessageTransport.log() SCTP connection with aa3a1e91f163f576 not ready yet.
JVB 2019-04-10 05:52:31.445 WARNING: [26] org.jitsi.videobridge.EndpointMessageTransport.log() No available transport channel, can’t send a message
JVB 2019-04-10 05:52:31.445 WARNING: [26] org.jitsi.videobridge.EndpointMessageTransport.log() SCTP connection with 8201260a79a80c63 not ready yet.
JVB 2019-04-10 05:52:31.445 WARNING: [26] org.jitsi.videobridge.EndpointMessageTransport.log() No available transport channel, can’t send a message
JVB 2019-04-10 05:52:31.469 INFO: [29] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 43ms. Sticky failure: false
JVB 2019-04-10 05:52:31.577 FINE: [164] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId vt2eK-2691): 95:DC:73:7E:90:B9:12:8C:64:99:64:D3:C7:E9:25:91:44:81:32:35:DF:85:3A:5F:60:A3:76:E5:DA:B3:25:F5
JVB 2019-04-10 05:52:31.579 FINE: [164] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId vt2eK-2691).
JVB 2019-04-10 05:52:31.582 FINE: [90] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId vt2eK-2697): 95:DC:73:7E:90:B9:12:8C:64:99:64:D3:C7:E9:25:91:44:81:32:35:DF:85:3A:5F:60:A3:76:E5:DA:B3:25:F5
JVB 2019-04-10 05:52:31.582 FINE: [90] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId vt2eK-2697).
JVB 2019-04-10 05:52:31.587 FINE: [94] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId vt2eK-2699): 95:DC:73:7E:90:B9:12:8C:64:99:64:D3:C7:E9:25:91:44:81:32:35:DF:85:3A:5F:60:A3:76:E5:DA:B3:25:F5
JVB 2019-04-10 05:52:31.587 FINE: [94] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId vt2eK-2699).
JVB 2019-04-10 05:52:31.589 INFO: [90] org.ice4j.ice.Component.log() Add remote candidate for stream.RTP: 192.168.56.1:63524/udp/host
JVB 2019-04-10 05:52:31.589 INFO: [90] org.ice4j.ice.Component.log() Add remote candidate for stream.RTP: 172.30.176.1:63525/udp/host
JVB 2019-04-10 05:52:31.589 INFO: [90] org.ice4j.ice.Component.log() Add remote candidate for stream.RTP: 10.0.75.1:63526/udp/host
JVB 2019-04-10 05:52:31.590 INFO: [90] org.ice4j.ice.Component.log() Add remote candidate for stream.RTP: 172.17.52.81:63527/udp/host
JVB 2019-04-10 05:52:31.590 INFO: [90] org.ice4j.ice.Component.log() Add remote candidate for stream.RTP: 192.168.1.141:63530/udp/host
JVB 2019-04-10 05:52:31.590 INFO: [90] org.ice4j.ice.Component.log() Add remote candidate for stream.RTP: 192.168.56.1:63524/udp/host
JVB 2019-04-10 05:52:31.590 INFO: [90] org.ice4j.ice.Component.log() Add remote candidate for stream.RTP: 172.30.176.1:63525/udp/host
JVB 2019-04-10 05:52:31.590 INFO: [90] org.ice4j.ice.Component.log() Add remote candidate for stream.RTP: 10.0.75.1:63526/udp/host
JVB 2019-04-10 05:52:31.591 INFO: [90] org.ice4j.ice.Component.log() Add remote candidate for stream.RTP: 172.17.52.81:63527/udp/host
JVB 2019-04-10 05:52:31.591 INFO: [90] org.ice4j.ice.Component.log() Add remote candidate for stream.RTP: 192.168.1.141:63530/udp/host
JVB 2019-04-10 05:52:31.591 INFO: [90] org.jitsi.videobridge.IceUdpTransportManager.log() We have remote candidates for all ICE components. Starting the ICE agent.
JVB 2019-04-10 05:52:31.592 INFO: [90] org.ice4j.ice.Agent.log() Start ICE connectivity establishment. Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.592 INFO: [90] org.ice4j.ice.Agent.log() Init checklist for stream stream
JVB 2019-04-10 05:52:31.592 INFO: [90] org.ice4j.ice.Agent.log() ICE state changed from Waiting to Running. Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.592 INFO: [90] org.jitsi.videobridge.IceUdpTransportManager.log() CAT=stat ice_state_change,conf_id=47bef181bb877659,content=data,ch_id=6da568c9145686d3,endp_id=706537c4 old_state=Waiting,new_state=Running
JVB 2019-04-10 05:52:31.593 INFO: [90] org.ice4j.ice.ConnectivityCheckClient.log() Start connectivity checks. Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.594 WARNING: [164] org.jitsi.videobridge.EndpointMessageTransport.log() SCTP connection with 3cd88d16 not ready yet.
JVB 2019-04-10 05:52:31.597 WARNING: [164] org.jitsi.videobridge.EndpointMessageTransport.log() No available transport channel, can’t send a message
JVB 2019-04-10 05:52:31.600 WARNING: [164] org.jitsi.videobridge.EndpointMessageTransport.log() SCTP connection with 2be4a7e4 not ready yet.
JVB 2019-04-10 05:52:31.600 WARNING: [164] org.jitsi.videobridge.EndpointMessageTransport.log() No available transport channel, can’t send a message
JVB 2019-04-10 05:52:31.602 FINE: [90] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId vt2eK-2697) with: 3D:88:B9:9D:8C:63:76:FD:0E:2A:B4:2B:D0:C7:9A:A5:38:B2:B7:76
JVB 2019-04-10 05:52:31.603 INFO: [164] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 192.168.56.1:63524/udp
JVB 2019-04-10 05:52:31.603 INFO: [164] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 192.168.56.1:63524/udp
JVB 2019-04-10 05:52:31.603 INFO: [164] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 172.30.176.1:63525/udp
JVB 2019-04-10 05:52:31.604 INFO: [164] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 172.30.176.1:63525/udp
JVB 2019-04-10 05:52:31.604 INFO: [164] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 10.0.75.1:63526/udp
JVB 2019-04-10 05:52:31.604 INFO: [164] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 10.0.75.1:63526/udp
JVB 2019-04-10 05:52:31.604 INFO: [164] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 172.17.52.81:63527/udp
JVB 2019-04-10 05:52:31.604 INFO: [164] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 172.17.52.81:63527/udp
JVB 2019-04-10 05:52:31.605 INFO: [164] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 192.168.1.141:63530/udp
JVB 2019-04-10 05:52:31.605 INFO: [164] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 192.168.1.141:63530/udp
JVB 2019-04-10 05:52:31.605 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 192.168.56.1:63524/udp
JVB 2019-04-10 05:52:31.605 INFO: [94] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 192.168.56.1:63524/udp
JVB 2019-04-10 05:52:31.606 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 172.30.176.1:63525/udp
JVB 2019-04-10 05:52:31.606 INFO: [94] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 172.30.176.1:63525/udp
JVB 2019-04-10 05:52:31.606 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 10.0.75.1:63526/udp
JVB 2019-04-10 05:52:31.606 INFO: [94] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 10.0.75.1:63526/udp
JVB 2019-04-10 05:52:31.606 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 172.17.52.81:63527/udp
JVB 2019-04-10 05:52:31.607 INFO: [94] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 172.17.52.81:63527/udp
JVB 2019-04-10 05:52:31.607 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 192.168.1.141:63530/udp
JVB 2019-04-10 05:52:31.607 INFO: [94] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 192.168.1.141:63530/udp
JVB 2019-04-10 05:52:31.607 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 192.168.56.1:63524/udp
JVB 2019-04-10 05:52:31.608 INFO: [94] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 192.168.56.1:63524/udp
JVB 2019-04-10 05:52:31.608 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 172.30.176.1:63525/udp
JVB 2019-04-10 05:52:31.608 INFO: [94] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 172.30.176.1:63525/udp
JVB 2019-04-10 05:52:31.608 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 10.0.75.1:63526/udp
JVB 2019-04-10 05:52:31.608 INFO: [94] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 10.0.75.1:63526/udp
JVB 2019-04-10 05:52:31.608 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 172.17.52.81:63527/udp
JVB 2019-04-10 05:52:31.609 INFO: [94] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 172.17.52.81:63527/udp
JVB 2019-04-10 05:52:31.609 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 192.168.1.141:63530/udp
JVB 2019-04-10 05:52:31.609 INFO: [94] org.ice4j.ice.Component.log() Not adding duplicate remote candidate: 192.168.1.141:63530/udp
JVB 2019-04-10 05:52:31.610 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 192.168.56.1:9/tcp
JVB 2019-04-10 05:52:31.611 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 172.30.176.1:9/tcp
JVB 2019-04-10 05:52:31.611 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 10.0.75.1:9/tcp
JVB 2019-04-10 05:52:31.611 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 172.17.52.81:9/tcp
JVB 2019-04-10 05:52:31.616 INFO: [94] org.ice4j.ice.Component.log() Update remote candidate for stream.RTP: 192.168.1.141:9/tcp
JVB 2019-04-10 05:52:31.617 INFO: [94] org.ice4j.ice.Component.log() new Pair added: 10.0.19.5:443/tcp/host -> 192.168.56.1:9/tcp/host (stream.RTP). Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.617 INFO: [94] org.ice4j.ice.Component.log() new Pair added: 10.0.19.5:443/tcp/host -> 172.30.176.1:9/tcp/host (stream.RTP). Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.618 INFO: [94] org.ice4j.ice.Component.log() new Pair added: 10.0.19.5:443/tcp/host -> 10.0.75.1:9/tcp/host (stream.RTP). Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.618 INFO: [94] org.ice4j.ice.Component.log() new Pair added: 10.0.19.5:443/tcp/host -> 172.17.52.81:9/tcp/host (stream.RTP). Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.618 INFO: [94] org.ice4j.ice.Component.log() new Pair added: 10.0.19.5:443/tcp/host -> 192.168.1.141:9/tcp/host (stream.RTP). Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.618 INFO: [94] org.ice4j.ice.Component.log() new Pair added: 20.37.137.137:443/tcp/srflx -> 192.168.56.1:9/tcp/host (stream.RTP). Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.621 INFO: [94] org.ice4j.ice.Component.log() new Pair added: 20.37.137.137:443/tcp/srflx -> 172.30.176.1:9/tcp/host (stream.RTP). Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.621 INFO: [94] org.ice4j.ice.Component.log() new Pair added: 20.37.137.137:443/tcp/srflx -> 10.0.75.1:9/tcp/host (stream.RTP). Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.621 FINE: [164] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId vt2eK-2691) with: 966800776233039096712369474803429518729255446532344814066911027687093D:88:B9:9D:8C:63:76:FD:0E:2A:B4:2B:D0:C7:9A:A5:38:B2:B7:76
JVB 2019-04-10 05:52:31.622 INFO: [94] org.ice4j.ice.Component.log() new Pair added: 20.37.137.137:443/tcp/srflx -> 172.17.52.81:9/tcp/host (stream.RTP). Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.622 INFO: [94] org.ice4j.ice.Component.log() new Pair added: 20.37.137.137:443/tcp/srflx -> 192.168.1.141:9/tcp/host (stream.RTP). Local ufrag bdjrd1d82ss2n9
JVB 2019-04-10 05:52:31.627 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 192.168.56.1:63524/udp/host (stream.RTP)
JVB 2019-04-10 05:52:31.628 FINE: [94] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId vt2eK-2699) with: 3D:88:B9:9D:8C:63:76:FD:0E:2A:B4:2B:D0:C7:9A:A5:38:B2:B7:76
JVB 2019-04-10 05:52:31.648 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 172.30.176.1:63525/udp/host (stream.RTP)
JVB 2019-04-10 05:52:31.670 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 10.0.75.1:63526/udp/host (stream.RTP)
JVB 2019-04-10 05:52:31.691 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 172.17.52.81:63527/udp/host (stream.RTP)
JVB 2019-04-10 05:52:31.712 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 192.168.1.141:63530/udp/host (stream.RTP)
JVB 2019-04-10 05:52:31.732 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 192.168.56.1:63524/udp/host (stream.RTP)
JVB 2019-04-10 05:52:31.754 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 172.30.176.1:63525/udp/host (stream.RTP)
JVB 2019-04-10 05:52:31.775 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 10.0.75.1:63526/udp/host (stream.RTP)
JVB 2019-04-10 05:52:31.795 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 172.17.52.81:63527/udp/host (stream.RTP)
JVB 2019-04-10 05:52:31.816 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:10000/udp/host -> 192.168.1.141:63530/udp/host (stream.RTP)
JVB 2019-04-10 05:52:31.829 FINE: [25] org.jitsi.videobridge.xmpp.ComponentImpl.log() SENT:
JVB 2019-04-10 05:52:31.831 FINE: [92] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 75XXc-238):
JVB 2019-04-10 05:52:31.836 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:443/tcp/host -> 192.168.56.1:9/tcp/host (stream.RTP)
JVB 2019-04-10 05:52:31.857 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:443/tcp/host -> 172.30.176.1:9/tcp/host (stream.RTP)
JVB 2019-04-10 05:52:31.877 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:443/tcp/host -> 10.0.75.1:9/tcp/host (stream.RTP)
JVB 2019-04-10 05:52:31.899 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:443/tcp/host -> 172.17.52.81:9/tcp/host (stream.RTP)
JVB 2019-04-10 05:52:31.919 INFO: [408] org.ice4j.ice.ConnectivityCheckClient.log() Pair failed: 10.0.19.5:443/tcp/host -> 192.168.1.141:9/tcp/host (stream.RTP)
JVB 2019-04-10 05:52:32.832 FINE: [25] org.jitsi.videobridge.xmpp.ComponentImpl.log() SENT:
JVB 2019-04-10 05:52:32.834 FINE: [99] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 75XXc-241):

0 Likes

#7

What is the network of the clients then?

0 Likes

#8

Sorry I misunderstood your questions I thought the client for the JVB which is jitis meet: My network info is:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2600:8802:2100:50e:f081:46f3:c206:2b25
Temporary IPv6 Address. . . . . . : 2600:8802:2100:50e:b8f5:1a98:5306:bf84
Link-local IPv6 Address . . . . . : fe80::f081:46f3:c206:2b25%7
IPv4 Address. . . . . . . . . . . : 192.168.1.141
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::c256:27ff:febd:70d8%7
192.168.1.1

  • my Public IPv6 is: 2600:8802:2100:50e:b8f5:1a98:5306:bf84
  • my IPv4 is: 98.164.227.21
0 Likes

#9

Then your clients are definitely not in the same network as jvb.

52.16.16.27 do you see this address if you do ifconfig on the machine with internal address 10.0.19.4?

0 Likes

#10

yeah, my client is not in the same network as jitis meet. What I need in that scenario?

0 Likes

#11

What is the answer of this?

0 Likes

#12

No, I don’t see this IP

0 Likes

#13

This is the public IP for the first machine, this is all hosted on the cloud as well.

0 Likes

#14

So you need to make sure you forward the port udp 10000 and tcp 443 from the public address to 10.0.19.4.
And configure those private and public ip addresses in jvb 1 and stop jvb2. Test and see it works.
Then find what will be the public address for jvb2, do the forwarding for it and configure the public and private addresses for jvb2.

0 Likes

#15

So now you see why prosody cannot bind on it:

0 Likes

#16

I thought the 2 JVB dons’t need a public IP address! So what I understand now if the client is not in the same network as the JVB, That means each bridge needs a public IP is that correct?

0 Likes

#17

I see what you are saying, but still not sure why it is not showing in the ifconfig I have that on Azure cloud and the IP assigned to the machine. not really sure if that an Azure cloud issue or setup I am missing. I will find out and update here.

0 Likes

#18

Yes, jvb needs direct access from the web/mobile clients, so it needs a public address.

I’m not familiar with Azure, but for example AWS works like this. All machines are behind NAT and you need to configure port forwarding (in AWS security groups). The machines have assigned public address you see in the admin console, and you don’t see that address configured in the VM.

0 Likes

#19

thank you so much for your help Damencho, appreciate the support. I will change the config and update here too. Thank you, thank you sir

0 Likes