Meeting is terminating on second connection with separate JVB

Hi Guys,

I’m trying to connect the jisti meet with existing JVB, that is on separate instance, but while connecting to the meeting i’m getting the error of (pair failed).

INFO: Nominate (first valid): 15.206.146.197:10000/udp/srflx -> 27.255.167.125:44755/udp/prflx (stream-6ce72f28.RTP).
Dec 18, 2020 1:36:05 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: verify if nominated pair answer again
Dec 18, 2020 1:36:05 PM org.ice4j.stack.NetAccessManager handleFatalError
SEVERE: Unexpected Error!
java.lang.NullPointerException
at org.ice4j.socket.MergingDatagramSocket.initializeActive(MergingDatagramSocket.java:577)
at org.ice4j.ice.ComponentSocket.propertyChange(ComponentSocket.java:174)
at org.ice4j.ice.IceMediaStream.firePairPropertyChange(IceMediaStream.java:870)
at org.ice4j.ice.CandidatePair.nominate(CandidatePair.java:629)
at org.ice4j.ice.Agent.nominate(Agent.java:1847)
at org.ice4j.ice.DefaultNominator.strategyNominateFirstValid(DefaultNominator.java:144)
at org.ice4j.ice.DefaultNominator.propertyChange(DefaultNominator.java:120)
at org.ice4j.ice.IceMediaStream.firePairPropertyChange(IceMediaStream.java:870)
at org.ice4j.ice.CandidatePair.validate(CandidatePair.java:667)
at org.ice4j.ice.IceMediaStream.addToValidList(IceMediaStream.java:668)
at org.ice4j.ice.Agent.validatePair(Agent.java:1811)
at org.ice4j.ice.ConnectivityCheckClient.processSuccessResponse(ConnectivityCheckClient.java:638)
at org.ice4j.ice.ConnectivityCheckClient.processResponse(ConnectivityCheckClient.java:405)
at org.ice4j.stack.StunClientTransaction.handleResponse(StunClientTransaction.java:314)
at org.ice4j.stack.StunStack.handleMessageEvent(StunStack.java:1040)
at org.ice4j.stack.MessageProcessingTask.run(MessageProcessingTask.java:196)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Dec 18, 2020 1:36:05 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Pair failed: 172.31.37.229:10000/udp/host -> 192.168.0.32:44755/udp/host (stream-6ce72f28.RTP)
Dec 18, 2020 1:36:06 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Add peer CandidatePair with new reflexive address to checkList: CandidatePair (State=Frozen Priority=7962116751041232895):
LocalCandidate=candidate:2 1 udp 2130706431 172.31.37.229 10000 typ host
RemoteCandidate=candidate:10003 1 udp 1853824767 27.255.167.125 44755 typ prflx

Thanks,
IPS

Are the ip addresses configured in the bridge config correct?

I have seen that config file is fine and the SHARD_PASSWORD is fine, it gets connected sometime and video start showing to second user but sometimes it terminated the meeting. I’m getting the following errors:

Dec 21, 2020 6:58:30 AM org.jitsi.utils.logging2.LoggerImpl log
WARNING: 4058291213 large jump in sequence numbers detected (highest received was 23889, current is 23998, jump of 108), not requesting retransmissions
Dec 21, 2020 6:58:31 AM org.jitsi.utils.logging2.LoggerImpl log
INFO: ICE state changed from Completed to Terminated.
Dec 21, 2020 6:58:31 AM org.jitsi.utils.logging2.LoggerImpl log
INFO: ICE state changed old=Completed new=Terminated
Dec 21, 2020 6:58:34 AM org.jitsi.utils.logging2.LoggerImpl log
WARNING: 4058291213 large jump in sequence numbers detected (highest received was 24453, current is 24709, jump of 255), not requesting retransmissions
Dec 21, 2020 6:58:38 AM org.jitsi.utils.logging2.LoggerImpl log
INFO: create_conf, id=2a60622c42b9b04 gid=null logging=false
Dec 21, 2020 6:58:38 AM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in PT0.016S. Sticky failure: false

Kindly let me know what could be the issue, because before it was working fine and now it’s stopped working

Thanks,
Inder

Hi @damencho, any suggestion?

Is the port 10000 forwarded from the public address of second jvb to its internal address?

Yes, port 10000 is open from JVB end, and on the jitsi installation it is accessible, the server is configured on AWS instances

And is it open in the security group for that jvb? Have you checked jvb logs on startup does it discover the correct public address?

Yes, ports are open in security groups, sometimes video call starts without any issue, and sometimes it’s not working and i’m unable to connect with second device.

Hi @damencho, i found the problem, actually we are using old build of jitsi and it has problem with poor network connection, when i’m using poor network it was terminated the meeting, but it’s working with fast network connections. It is working fine with the latest jitsi release.