Jvb log check request

[qwerts89]

What is the error below?

Is there any solution??

org.jitsi.utils.logging.LoggerImpl log
WARNING: Failed to handle packet:
java.lang.IllegalArgumentException: responseTimeMs
at org.jitsi_modified.impl.neomedia.rtp.remotebitrateestimator.AimdRateControl.additiveRateIncrease(AimdRateControl.java:102)
at org.jitsi_modified.impl.neomedia.rtp.remotebitrateestimator.AimdRateControl.changeBitrate(AimdRateControl.java:165)
at org.jitsi_modified.impl.neomedia.rtp.remotebitrateestimator.AimdRateControl.updateBandwidthEstimate(AimdRateControl.java:463)
at org.jitsi_modified.impl.neomedia.rtp.remotebitrateestimator.RemoteBitrateEstimatorAbsSendTime.incomingPacketInfo(RemoteBitrateEstimatorAbsSendTime.java:309)
at org.jitsi.nlj.rtp.bandwidthestimation.GoogleCcEstimator.doProcessPacketArrival(GoogleCcEstimator.kt:82)
at org.jitsi.nlj.rtp.bandwidthestimation.BandwidthEstimator.processPacketArrival(BandwidthEstimator.kt:117)
at org.jitsi.nlj.rtp.bandwidthestimation.BandwidthEstimator.processPacketArrival$default(BandwidthEstimator.kt:98)
at org.jitsi.nlj.rtp.TransportCcEngine.tccReceived(TransportCcEngine.kt:153)
at org.jitsi.nlj.rtp.TransportCcEngine.rtcpPacketReceived(TransportCcEngine.kt:102)
at org.jitsi.nlj.rtcp.RtcpEventNotifier.notifyRtcpReceived(RtcpEventNotifier.kt:35)
at org.jitsi.nlj.transform.node.incoming.RtcpTermination.transform(RtcpTermination.kt:99)
at org.jitsi.nlj.transform.node.TransformerNode.doProcessPacket(Node.kt:376)
at org.jitsi.nlj.transform.node.StatsKeepingNode.processPacket(Node.kt:206)
at org.jitsi.nlj.transform.node.Node.next(Node.kt:107)
at org.jitsi.nlj.transform.node.TransformerNode.doProcessPacket(Node.kt:380)
at org.jitsi.nlj.transform.node.StatsKeepingNode.processPacket(Node.kt:206)
at org.jitsi.nlj.transform.node.Node.next(Node.kt:107)
at org.jitsi.nlj.transform.node.NeverDiscardNode.doProcessPacket(Node.kt:363)
at org.jitsi.nlj.transform.node.StatsKeepingNode.processPacket(Node.kt:206)
at org.jitsi.nlj.transform.node.Node.next(Node.kt:115)
at org.jitsi.nlj.transform.node.MultipleOutputTransformerNode.doProcessPacket(Node.kt:468)
at org.jitsi.nlj.transform.node.StatsKeepingNode.processPacket(Node.kt:206)
at org.jitsi.nlj.transform.node.ExclusivePathDemuxer.doProcessPacket(Node.kt:539)
at org.jitsi.nlj.transform.node.StatsKeepingNode.processPacket(Node.kt:206)
at org.jitsi.nlj.transform.node.Node.next(Node.kt:107)
at org.jitsi.nlj.transform.node.NeverDiscardNode.doProcessPacket(Node.kt:363)
at org.jitsi.nlj.transform.node.StatsKeepingNode.processPacket(Node.kt:206)
at org.jitsi.nlj.RtpReceiverImpl.doProcessPacket(RtpReceiverImpl.kt:275)
at org.jitsi.nlj.StatsKeepingPacketHandler.processPacket(PacketHandler.kt:44)
at org.jitsi.nlj.RtpReceiverImpl.handleIncomingPacket(RtpReceiverImpl.kt:267)
at org.jitsi.nlj.RtpReceiverImpl.access$handleIncomingPacket(RtpReceiverImpl.kt:77)
at org.jitsi.nlj.RtpReceiverImpl$incomingPacketQueue$1.invoke(RtpReceiverImpl.kt:108)
at org.jitsi.nlj.RtpReceiverImpl$incomingPacketQueue$1.invoke(RtpReceiverImpl.kt:77)
at org.jitsi.nlj.util.PacketInfoQueue$sam$org_jitsi_utils_queue_PacketQueue_PacketHandler$0.handlePacket(PacketInfoQueue.kt)
at org.jitsi.utils.queue.PacketQueue$HandlerAdapter.handleItem(PacketQueue.java:380)
at org.jitsi.utils.queue.AsyncQueueHandler$1.run(AsyncQueueHandler.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)

[qwerts89]

next log

org.jitsi.utils.logging2.LoggerImpl log
WARNING: Negative rtt value: -551.604858 ms, remote processing delay was PT1.135604858S (74423), srSentTime was 2021-05-31T07:44:01.480Z, received time was 2021-05-31T07:44:02.064Z

org.jitsi.utils.logging2.LoggerImpl log
INFO: Endpoints were suspended due to insufficient bandwidth (bwe=164111 bps): 548fed02

[Freddie]

The screen flickers in tile view. At this time, the screen status is marked as inactive

Evidently bandwidth is not sufficient if you’re experiencing the same thing on meet.jit.si. You’ve presented this same issue in like 5 different posts and the response has been the same. If you still doubt it, have other people join you from different networks and see if you report the same issue.

[qwerts89]

The above case also happens in one-to-one.

It doesn’t happen in jitsi meet.

The log is as above.

[qwerts89]

jitsi meet ===

self-hositng docker ===

[Freddie]

It’s working on meet.jit.si but not in your deployment. Clearly something’s not configured properly on your end.

[qwerts89]

I proceeded by referring to the docker guide.

Only modified config.js and interface_config.js.

Is there anything else I need to install or configure other than docker?