The connection from the camera is lost

Hello, the participants’ camera periodically disappears. Ports registered by UDP: 10000,5349 / TСP: 80,443,4443,3478

In the console logs Firefox:

2021-07-22T01:19:45.564Z [modules/RTC/BridgeChannel.js] <_handleChannel/e.onclose>:  Channel closed: 1001 
2021-07-22T00:59:59.325Z [modules/xmpp/XmppConnection.js] <u._maybeEnableStreamResume>:  Stream resume enabled, but WebSockets are not enabled

In the console logs Jitsi Dekstop

2021-07-22T01:00:50.354Z [modules/statistics/AudioOutputProblemDetector.js] A potential problem is detected with the audio output for participant dd583f1a, local audio levels: [null,null], remote audio levels: undefined
Logger.js:154 2021-07-22T01:43:13.950Z [modules/xmpp/XmppConnection.js] <u._maybeEnableStreamResume>:  Stream resume enabled, but WebSockets are not enabled
2021-07-22T00:51:18.061Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 0015e365,3fe55d3b
Logger.js:154 2021-07-22T00:51:18.769Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 0015e365
Logger.js:154 2021-07-22T00:51:24.242Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 0015e365,dd583f1a
Logger.js:154 2021-07-22T00:51:24.803Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 0015e365
Logger.js:154 2021-07-22T00:51:34.472Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 0015e365,dd583f1a
Logger.js:154 2021-07-22T00:51:36.552Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 0015e365
Logger.js:154 2021-07-22T00:51:38.323Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 0015e365,3fe55d3b
Logger.js:154 2021-07-22T00:51:39.337Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 0015e365,dd583f1a
Logger.js:154 2021-07-22T00:51:40.557Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 0015e365
Logger.js:154 2021-07-22T00:51:45.977Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 0015e365,dd583f1a

[Deprecation] Plan B SDP semantics, which is used when constructing an RTCPeerConnection with {sdpSemantics:"plan-b"}, is a legacy version of the Session Description Protocol that has severe compatibility issues on modern browsers. The standardized SDP format, "unified-plan", has been used by default since M72 (January, 2019). Dropping support for Plan B is targeted for M93 (Canary: July 15, 2021; Stable: August 24, 2021).

In the console logs Chrome:

2021-07-22T01:28:19.314Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>:  UnhandledError: Focus error, retry after 1000 Script: null Line: null Column: null StackTrace:  Error: Focus error, retry after 1000
    at l._allocateConferenceFocusError (https://meet.dazel.ru/libs/lib-jitsi-meet.min.js?v=5056:10:169819)
    at https://meet.dazel.ru/libs/lib-jitsi-meet.min.js?v=5056:10:168870
    at w.Handler.handler (https://meet.dazel.ru/libs/lib-jitsi-meet.min.js?v=5056:1:32072)
    at w.Handler.run (https://meet.dazel.ru/libs/lib-jitsi-meet.min.js?v=5056:1:27371)
    at https://meet.dazel.ru/libs/lib-jitsi-meet.min.js?v=5056:1:35809
    at Object.forEachChild (https://meet.dazel.ru/libs/lib-jitsi-meet.min.js?v=5056:1:19033)
    at w.Connection._dataRecv (https://meet.dazel.ru/libs/lib-jitsi-meet.min.js?v=5056:1:35658)
    at O.Bosh._onRequestStateChange (https://meet.dazel.ru/libs/lib-jitsi-meet.min.js?v=5056:1:55643)

2021-07-22T01:28:19.314Z [modules/xmpp/moderator.js] <l._allocateConferenceFocusError>:  Focus error, retry after 1000

2021-07-22T01:29:10.679Z [modules/statistics/AudioOutputProblemDetector.js] A potential problem is detected with the audio output for participant dd583f1a, local audio levels: [null,null], remote audio levels: undefined

2021-07-22T01:38:37.429Z [modules/statistics/AudioOutputProblemDetector.js] A potential problem is detected with the audio output for participant d40809cd, local audio levels: [null,null], remote audio levels: undefined

2021-07-22T01:38:37.429Z [modules/statistics/AudioOutputProblemDetector.js] A potential problem is detected with the audio output for participant 3fe55d3b, local audio levels: [null,null], remote audio levels: undefined

jicofo.log

Jicofo 2021-07-22 10:17:35.724 INFO: [236] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] AbstractChannelAllocator.allocateChannels#248: Using jvbbrewery@internal.auth.meet.dazel.ru/c1e205de-9f16-4a98-a466-1ecd48d4fd79 to allocate channels for: Participant[dazel@conference.meet.dazel.ru/dd583f1a]@1124469649
Jicofo 2021-07-22 10:17:35.724 INFO: [235] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] AbstractChannelAllocator.allocateChannels#248: Using jvbbrewery@internal.auth.meet.dazel.ru/c1e205de-9f16-4a98-a466-1ecd48d4fd79 to allocate channels for: Participant[dazel@conference.meet.dazel.ru/2c1002f2]@387111722
Jicofo 2021-07-22 10:17:35.772 INFO: [236] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4 participant=dd583f1a] ParticipantChannelAllocator.doInviteOrReinvite#229: Sending session-initiate to: dazel@conference.meet.dazel.ru/dd583f1a
Jicofo 2021-07-22 10:17:35.792 INFO: [235] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4 participant=2c1002f2] ParticipantChannelAllocator.doInviteOrReinvite#229: Sending session-initiate to: dazel@conference.meet.dazel.ru/2c1002f2
Jicofo 2021-07-22 10:17:36.198 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.onSessionAccept#1265: Receive session-accept from dazel@conference.meet.dazel.ru/dd583f1a
Jicofo 2021-07-22 10:17:36.200 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.onSessionAcceptInternal#1681: Received session-accept from dd583f1a with accepted sources:Sources{ video: [ssrc=477106514 ssrc=1183735343 ssrc=9683375 ssrc=1248992378 ssrc=3175608815 ssrc=3109796509 ] }@1728366324
Jicofo 2021-07-22 10:17:36.201 WARNING: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.lambda$propagateNewSources$7#1432: No jingle session yet for 2c1002f2
Jicofo 2021-07-22 10:17:36.950 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.onSessionAccept#1265: Receive session-accept from dazel@conference.meet.dazel.ru/2c1002f2
Jicofo 2021-07-22 10:17:36.952 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.onSessionAcceptInternal#1681: Received session-accept from 2c1002f2 with accepted sources:Sources{ video: [ssrc=2229194721 ssrc=1612319654 ssrc=2880142551 ssrc=288852572 ssrc=4142063769 ssrc=818804655 ] audio: [ssrc=1939628341 ] }@1069084390
Jicofo 2021-07-22 10:26:51.622 INFO: [238] ConferenceIqHandler.handleConferenceIq#56: Focus request for room: dazel@conference.meet.dazel.ru
Jicofo 2021-07-22 10:26:51.974 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] ChatRoomRoleAndPresence.memberPresenceChanged#130: Chat room event Joined member=ChatMember[dazel@conference.meet.dazel.ru/0015e365, jid: null]@1825572276
Jicofo 2021-07-22 10:26:51.974 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.onMemberJoined#547: Member joined:0015e365
Jicofo 2021-07-22 10:26:51.975 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.inviteParticipant#771: Added participant id= 0015e365, bridge=jvbbrewery@internal.auth.meet.dazel.ru/c1e205de-9f16-4a98-a466-1ecd48d4fd79
Jicofo 2021-07-22 10:26:51.975 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] ChatRoomRoleAndPresence.memberPresenceChanged#130: Chat room event PresenceUpdated member=ChatMember[dazel@conference.meet.dazel.ru/0015e365, jid: u9suo2xuya8v2rgi@guest.meet.dazel.ru/xmqCiOMt]@1825572276
Jicofo 2021-07-22 10:26:51.976 INFO: [238] DiscoveryUtil.discoverParticipantFeatures#152: Doing feature discovery for dazel@conference.meet.dazel.ru/0015e365
Jicofo 2021-07-22 10:26:51.976 INFO: [238] DiscoveryUtil.discoverParticipantFeatures#192: Successfully discovered features for dazel@conference.meet.dazel.ru/0015e365 in 0
Jicofo 2021-07-22 10:26:51.977 INFO: [238] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] AbstractChannelAllocator.allocateChannels#248: Using jvbbrewery@internal.auth.meet.dazel.ru/c1e205de-9f16-4a98-a466-1ecd48d4fd79 to allocate channels for: Participant[dazel@conference.meet.dazel.ru/0015e365]@694661650
Jicofo 2021-07-22 10:26:52.020 INFO: [238] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4 participant=0015e365] ParticipantChannelAllocator.doInviteOrReinvite#229: Sending session-initiate to: dazel@conference.meet.dazel.ru/0015e365
Jicofo 2021-07-22 10:26:53.539 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] ChatRoomRoleAndPresence.memberPresenceChanged#130: Chat room event PresenceUpdated member=ChatMember[dazel@conference.meet.dazel.ru/0015e365, jid: u9suo2xuya8v2rgi@guest.meet.dazel.ru/xmqCiOMt]@1825572276
Jicofo 2021-07-22 10:26:53.539 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] ChatRoomRoleAndPresence.memberPresenceChanged#130: Chat room event PresenceUpdated member=ChatMember[dazel@conference.meet.dazel.ru/0015e365, jid: u9suo2xuya8v2rgi@guest.meet.dazel.ru/xmqCiOMt]@1825572276
Jicofo 2021-07-22 10:26:54.514 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.onSessionAccept#1265: Receive session-accept from dazel@conference.meet.dazel.ru/0015e365
Jicofo 2021-07-22 10:26:54.516 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.onSessionAcceptInternal#1681: Received session-accept from 0015e365 with accepted sources:Sources{ video: [ssrc=2988926669 ssrc=2153495769 ssrc=1776422042 ssrc=935972106 ssrc=226071207 ssrc=2243211134 ] audio: [ssrc=3455935985 ] }@459991620
Jicofo 2021-07-22 10:27:37.702 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.removeSources#1823: Removing sources from dazel@conference.meet.dazel.ru/dd583f1a: Sources{ video: [ssrc=9683375 ssrc=477106514 ssrc=1183735343 ssrc=1248992378 ssrc=3109796509 ssrc=3175608815 ] }@265638428
Jicofo 2021-07-22 10:27:53.515 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.removeSources#1823: Removing sources from dazel@conference.meet.dazel.ru/0015e365: Sources{ audio: [ssrc=3455935985 ] }@1934683805
Jicofo 2021-07-22 10:27:55.254 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.removeSources#1823: Removing sources from dazel@conference.meet.dazel.ru/0015e365: Sources{ audio: [ssrc=2860955608 ] }@65936197
Jicofo 2021-07-22 10:27:56.282 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.removeSources#1823: Removing sources from dazel@conference.meet.dazel.ru/0015e365: Sources{ audio: [ssrc=840122060 ] }@478204906
Jicofo 2021-07-22 10:29:35.349 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.removeSources#1823: Removing sources from dazel@conference.meet.dazel.ru/0015e365: Sources{ audio: [ssrc=4112117267 ] }@550309146
Jicofo 2021-07-22 10:29:46.274 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.removeSources#1823: Removing sources from dazel@conference.meet.dazel.ru/0015e365: Sources{ audio: [ssrc=2347662192 ] }@1706302006
Jicofo 2021-07-22 10:29:47.152 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.removeSources#1823: Removing sources from dazel@conference.meet.dazel.ru/0015e365: Sources{ audio: [ssrc=3330099240 ] }@468778409
Jicofo 2021-07-22 10:37:23.420 INFO: [240] ConferenceIqHandler.handleConferenceIq#56: Focus request for room: dazel@conference.meet.dazel.ru
Jicofo 2021-07-22 10:37:23.966 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] ChatRoomRoleAndPresence.memberPresenceChanged#130: Chat room event Joined member=ChatMember[dazel@conference.meet.dazel.ru/3fe55d3b, jid: null]@777358597
Jicofo 2021-07-22 10:37:23.967 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.onMemberJoined#547: Member joined:3fe55d3b
Jicofo 2021-07-22 10:37:23.968 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.inviteParticipant#771: Added participant id= 3fe55d3b, bridge=jvbbrewery@internal.auth.meet.dazel.ru/c1e205de-9f16-4a98-a466-1ecd48d4fd79
Jicofo 2021-07-22 10:37:23.969 INFO: [240] DiscoveryUtil.discoverParticipantFeatures#152: Doing feature discovery for dazel@conference.meet.dazel.ru/3fe55d3b
Jicofo 2021-07-22 10:37:23.969 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] ChatRoomRoleAndPresence.memberPresenceChanged#130: Chat room event PresenceUpdated member=ChatMember[dazel@conference.meet.dazel.ru/3fe55d3b, jid: btvhcylljmtito4r@guest.meet.dazel.ru/7UX0CHB5]@777358597
Jicofo 2021-07-22 10:37:23.969 INFO: [240] DiscoveryUtil.discoverParticipantFeatures#192: Successfully discovered features for dazel@conference.meet.dazel.ru/3fe55d3b in 1
Jicofo 2021-07-22 10:37:23.969 INFO: [240] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] AbstractChannelAllocator.allocateChannels#248: Using jvbbrewery@internal.auth.meet.dazel.ru/c1e205de-9f16-4a98-a466-1ecd48d4fd79 to allocate channels for: Participant[dazel@conference.meet.dazel.ru/3fe55d3b]@275075199
Jicofo 2021-07-22 10:37:24.026 INFO: [240] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4 participant=3fe55d3b] ParticipantChannelAllocator.doInviteOrReinvite#229: Sending session-initiate to: dazel@conference.meet.dazel.ru/3fe55d3b
Jicofo 2021-07-22 10:37:28.485 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.onSessionAccept#1265: Receive session-accept from dazel@conference.meet.dazel.ru/3fe55d3b
Jicofo 2021-07-22 10:37:28.487 INFO: [28] [room=dazel@conference.meet.dazel.ru meeting_id=701d9238-15af-40a3-b587-1d5ec68dfec4] JitsiMeetConferenceImpl.onSessionAcceptInternal#1681: Received session-accept from 3fe55d3b with accepted sources:Sources{ video: [ssrc=2563340710 ssrc=1006326130 ssrc=3865798102 ssrc=3377899468 ssrc=2305538381 ssrc=2358485913 ] }@280452344

jvb.log:

JVB 2021-07-20 10:21:13.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000001S. Sticky failure: false
JVB 2021-07-20 10:21:23.535 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000001S. Sticky failure: false
JVB 2021-07-20 10:21:33.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000001S. Sticky failure: false
JVB 2021-07-20 10:21:43.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000001S. Sticky failure: false
JVB 2021-07-20 10:21:53.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000001S. Sticky failure: false
JVB 2021-07-20 10:22:03.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000001S. Sticky failure: false
JVB 2021-07-20 10:22:13.447 INFO: [22] VideobridgeExpireThread.expire#140: Running expire()
JVB 2021-07-22 10:51:50.930 INFO: [78] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=113916 bps): 3fe55d3b
JVB 2021-07-22 10:51:51.160 INFO: [78] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=117713 bps): 3fe55d3b
JVB 2021-07-22 10:51:51.383 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=118981 bps): 3fe55d3b
JVB 2021-07-22 10:51:51.693 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=120061 bps): 3fe55d3b
JVB 2021-07-22 10:51:51.969 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=124029 bps): 3fe55d3b
JVB 2021-07-22 10:51:52.193 INFO: [77] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=128130 bps): 3fe55d3b
JVB 2021-07-22 10:51:52.411 INFO: [81] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=129499 bps): 3fe55d3b
JVB 2021-07-22 10:51:52.694 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=130666 bps): 3fe55d3b
JVB 2021-07-22 10:51:52.735 INFO: [79] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=185485 bps): 3fe55d3b
JVB 2021-07-22 10:51:52.786 INFO: [81] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=187511 bps): 3fe55d3b
JVB 2021-07-22 10:51:52.969 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=134951 bps): 3fe55d3b
JVB 2021-07-22 10:51:53.223 INFO: [77] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=139380 bps): 3fe55d3b
JVB 2021-07-22 10:51:53.428 INFO: [78] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=140859 bps): 3fe55d3b
JVB 2021-07-22 10:51:53.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000001S. Sticky failure: false
JVB 2021-07-22 10:51:53.739 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=142119 bps): 3fe55d3b
JVB 2021-07-22 10:51:53.993 INFO: [78] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=146747 bps): 3fe55d3b
JVB 2021-07-22 10:51:54.252 INFO: [78] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=151530 bps): 3fe55d3b
JVB 2021-07-22 10:51:54.457 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=153128 bps): 3fe55d3b
JVB 2021-07-22 10:51:54.763 INFO: [78] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=154489 bps): 3fe55d3b
JVB 2021-07-22 10:51:55.276 INFO: [77] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=164652 bps): 3fe55d3b
JVB 2021-07-22 10:51:55.486 INFO: [78] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=166378 bps): 3fe55d3b
JVB 2021-07-22 10:51:55.801 INFO: [81] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=167848 bps): 3fe55d3b
JVB 2021-07-22 10:51:56.058 INFO: [78] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=173246 bps): 3fe55d3b
JVB 2021-07-22 10:51:56.311 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=178824 bps): 3fe55d3b
JVB 2021-07-22 10:51:57.443 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=155679 bps): 3fe55d3b
JVB 2021-07-22 10:51:58.321 INFO: [81] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=156436 bps): 3fe55d3b
JVB 2021-07-22 10:51:58.880 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=157516 bps): 3fe55d3b
JVB 2021-07-22 10:51:58.931 INFO: [78] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=162732 bps): 3fe55d3b
JVB 2021-07-22 10:51:59.900 INFO: [77] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=171117 bps): 3fe55d3b
JVB 2021-07-22 10:51:59.958 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=176751 bps): 3fe55d3b
JVB 2021-07-22 10:52:00.104 INFO: [81] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:52:00.167 INFO: [78] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=182572 bps): 3fe55d3b
JVB 2021-07-22 10:52:00.945 INFO: [77] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=185806 bps): 3fe55d3b
JVB 2021-07-22 10:52:01.256 INFO: [79] [confId=41db18a26311211b epId=0015e365 gid=25930 stats_id=Amie-7Rn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=198178 bps): 3fe55d3b
JVB 2021-07-22 10:52:03.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000009S. Sticky failure: false
JVB 2021-07-22 10:52:13.447 INFO: [22] VideobridgeExpireThread.expire#140: Running expire()
JVB 2021-07-22 10:52:13.535 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000001S. Sticky failure: false
JVB 2021-07-22 10:52:15.129 INFO: [79] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:52:16.395 WARNING: [81] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] EndpointConnectionStats.processReportBlock#171: Negative rtt value: -1.334948000000054 ms, remote processing delay was PT0.449996948S (29491), srSentTime was 2021-07-22T00:52:15.946338Z, received time was 2021-07-22T00:52:16.395Z
JVB 2021-07-22 10:52:22.696 WARNING: [77] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] EndpointConnectionStats.processReportBlock#171: Negative rtt value: -1.0263710000000401 ms, remote processing delay was PT0.893005371S (58524), srSentTime was 2021-07-22T00:52:21.804021Z, received time was 2021-07-22T00:52:22.696Z
JVB 2021-07-22 10:52:23.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000011S. Sticky failure: false
JVB 2021-07-22 10:52:25.510 WARNING: [77] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] EndpointConnectionStats.processReportBlock#171: Negative rtt value: -1.0114409999999907 ms, remote processing delay was PT0.690002441S (45220), srSentTime was 2021-07-22T00:52:24.821009Z, received time was 2021-07-22T00:52:25.510Z
JVB 2021-07-22 10:52:30.139 INFO: [81] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:52:33.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000006S. Sticky failure: false
JVB 2021-07-22 10:52:43.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
JVB 2021-07-22 10:52:45.179 INFO: [78] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:52:51.380 INFO: [81] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=204569 bps): 3fe55d3b
JVB 2021-07-22 10:52:51.634 INFO: [79] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=221935 bps): 3fe55d3b
JVB 2021-07-22 10:52:53.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000009S. Sticky failure: false
JVB 2021-07-22 10:53:00.223 INFO: [79] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:53:03.535 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.00001S. Sticky failure: false
JVB 2021-07-22 10:53:05.528 WARNING: [79] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] EndpointConnectionStats.processReportBlock#171: Negative rtt value: -1.075896000000057 ms, remote processing delay was PT0.149993896S (9830), srSentTime was 2021-07-22T00:53:05.379082Z, received time was 2021-07-22T00:53:05.528Z
JVB 2021-07-22 10:53:13.448 INFO: [22] VideobridgeExpireThread.expire#140: Running expire()
JVB 2021-07-22 10:53:13.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000001S. Sticky failure: false
JVB 2021-07-22 10:53:15.243 INFO: [81] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:53:23.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000009S. Sticky failure: false
JVB 2021-07-22 10:53:26.957 INFO: [77] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=142140 bps): 3fe55d3b
JVB 2021-07-22 10:53:28.836 INFO: [79] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=147148 bps): 3fe55d3b
JVB 2021-07-22 10:53:29.852 INFO: [79] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=159920 bps): 3fe55d3b
JVB 2021-07-22 10:53:30.250 INFO: [78] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:53:30.250 INFO: [77] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:53:30.866 INFO: [79] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=173714 bps): 3fe55d3b
JVB 2021-07-22 10:53:33.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000009S. Sticky failure: false
JVB 2021-07-22 10:53:43.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000001S. Sticky failure: false
JVB 2021-07-22 10:53:45.325 INFO: [81] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:53:53.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000007S. Sticky failure: false
JVB 2021-07-22 10:54:00.334 INFO: [81] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:54:03.488 INFO: [81] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=162198 bps): 3fe55d3b
JVB 2021-07-22 10:54:03.535 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000047S. Sticky failure: false
JVB 2021-07-22 10:54:03.792 INFO: [78] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=129885 bps): 3fe55d3b
JVB 2021-07-22 10:54:04.045 INFO: [78] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=141276 bps): 3fe55d3b
JVB 2021-07-22 10:54:05.062 INFO: [77] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=153578 bps): 3fe55d3b
JVB 2021-07-22 10:54:06.077 INFO: [79] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=166864 bps): 3fe55d3b
JVB 2021-07-22 10:54:07.094 INFO: [77] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=181213 bps): 3fe55d3b
JVB 2021-07-22 10:54:08.109 INFO: [78] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=196710 bps): 3fe55d3b
JVB 2021-07-22 10:54:13.447 INFO: [22] VideobridgeExpireThread.expire#140: Running expire()
JVB 2021-07-22 10:54:13.535 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000001S. Sticky failure: false
JVB 2021-07-22 10:54:14.154 INFO: [77] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=166899 bps): 3fe55d3b
JVB 2021-07-22 10:54:15.362 INFO: [81] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:54:21.454 INFO: [79] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=137780 bps): 3fe55d3b
JVB 2021-07-22 10:54:22.576 INFO: [79] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=114691 bps): 3fe55d3b
JVB 2021-07-22 10:54:23.487 INFO: [81] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=124866 bps): 3fe55d3b
JVB 2021-07-22 10:54:23.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000009S. Sticky failure: false
JVB 2021-07-22 10:54:24.298 INFO: [81] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=104083 bps): dd583f1a,3fe55d3b
JVB 2021-07-22 10:54:24.703 INFO: [79] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=105067 bps): 3fe55d3b
JVB 2021-07-22 10:54:26.888 INFO: [81] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=106051 bps): dd583f1a,3fe55d3b
JVB 2021-07-22 10:54:27.900 INFO: [79] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=115535 bps): 3fe55d3b
JVB 2021-07-22 10:54:30.374 INFO: [78] [confId=41db18a26311211b epId=dd583f1a gid=25930 stats_id=Orlando-qVn conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=-1 bps): 0015e365,2c1002f2,3fe55d3b
JVB 2021-07-22 10:54:32.372 INFO: [77] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=117578 bps): 3fe55d3b
JVB 2021-07-22 10:54:33.383 INFO: [78] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=127984 bps): 3fe55d3b
JVB 2021-07-22 10:54:33.534 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000005S. Sticky failure: false
JVB 2021-07-22 10:54:34.400 INFO: [78] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=139223 bps): 3fe55d3b
JVB 2021-07-22 10:54:36.485 INFO: [78] [confId=41db18a26311211b epId=2c1002f2 gid=25930 stats_id=Leif-RhA conf_name=dazel@conference.meet.dazel.ru] BandwidthAllocator.allocate#363: Endpoints were suspended due to insufficient bandwidth (bwe=164470 bps): 3fe55d3b

On my server, there is nginx (SSL 443) and jitsi itself, because of this there can be no problems?

##### VIDEO: https://disk.yandex.ru/i/gzMPdbbwiHf3Qw

Screen Jitsi Dekstop:

Update:
I have nginx and jitsi installed on the server, they use both port 443. I did the following - I wrote in the /etc/jitsi/videobridge/sip-communicator.properties setting

org.jitsi.videobridge.DISABLE_TCP_HARVESTER = false

Is this the correct decision, to drive the traffic through 4443?

Errors disappeared, only sometimes the cameras turn off for a second. Video link above. Help me please :frowning:

Can anyone tell me which direction to dig? :frowning:

I’m not sure I fully understand the problem you’re having. Are you saying some participants sometimes lose connection? How did you install (what guide did you use)? What else is hosted on the server besides Jitsi (and Nginx)?

The virtual machine is lifted, a white subnet is allocated in the DMZ. The latest Debian is installed, the Jitsi Server itself is also unpacked and Nginx + SSL is also there. During installation, I used the official Jitsi documentation. Please see the Video, the problem is displayed there - IMG_5192.MOV — Яндекс.Диск

From the clip, it looks like some participants are temporarily dropping connection. Sounds like what you’re saying the issue is? Can you provide temporary test login credentials so I can run a test meeting to check?

Yes!

There if that test machines hang
The problem is observed at different points in time. It can work for about 20 minutes, and then every 5 minutes the connection to the camera is cut off.

Looks like the problem shows up when using Firefox. Chrome-based browsers appear to work fine.

Edit: Actually, not really. All browsers appear to have the same issue after a while and the bridge crashes. Is everything hosted on the same server (JVB on the same server as the JMS stack)?

Can you share the link to the documentation you used for your installation? Did you customize anything during installation? What else is hosted on the server(s)?

We use the Jitsi desktop app
https://jitsi.org.ru/download/

All conference participants have one IP, can this somehow affect?

Ok, that site is unfamiliar - but I guess it’s the russian version of the official documentation. It’s missing a few steps though - firewalls, for instance. But you already mentioned that all required ports are open.

No, participants being on the same IP is not the issue. There’s something else going on. Again, is everything hosted on the same server?

The ports are open in the firewall.
Nginx, Jitsi (videobridge, jicofo), Prosody, costs nothing else.

Why did you change this to false? Set it back to “true”.

JVB on port 4443 (For single server installations)

If you have all the jitsi meet components on the same server, the web server (Nginx, Apache or Tomcat) which serves the frontend will occupy the port 443 . I this case, we can configure the Jitsi Video Bridge (JVB) to use port 4443 for webRTC Media traffic over TCP. To do that you have to add the following line to /etc/jitsi/videobridge/sip-communicator.properties in JVB.

org.jitsi.videobridge.DISABLE_TCP_HARVESTER=false

Now there are no errors, only constant reconnections:

2021-07-23T03:40:29.548Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 20deaae8,bd4a68a4
Logger.js:154 2021-07-23T03:40:29.799Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: bd4a68a4
Logger.js:154 2021-07-23T03:40:30.002Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 20deaae8,bd4a68a4
Logger.js:154 2021-07-23T03:40:30.256Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: bd4a68a4
Logger.js:154 2021-07-23T03:40:30.459Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 20deaae8,bd4a68a4
Logger.js:154 2021-07-23T03:40:33.065Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: bd4a68a4
Logger.js:154 2021-07-23T03:40:34.367Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 20deaae8,bd4a68a4
Logger.js:154 2021-07-23T03:40:34.623Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: bd4a68a4
Logger.js:154 2021-07-23T03:40:34.830Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 20deaae8,bd4a68a4
Logger.js:154 2021-07-23T03:40:35.032Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: bd4a68a4
Logger.js:154 2021-07-23T03:40:35.234Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 20deaae8,bd4a68a4
Logger.js:154 2021-07-23T03:42:31.092Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: bd4a68a4
Logger.js:154 2021-07-23T03:42:32.697Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 20deaae8,bd4a68a4
Logger.js:154 2021-07-23T03:42:36.350Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: bd4a68a4
Logger.js:154 2021-07-23T03:42:36.398Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onmessage>:  New forwarded endpoints: 20deaae8,bd4a68a4

Again, you need to set that back to “true”. You only send your media over 443/TCP if you’re behind a firewall that’s blocking port 10000/UDP. It’s not the preferred routing because TCP doesn’t relay media as efficiently as UDP. Additionally, you’ll need to deploy a TURN server if you choose to use 443.

At this point, I honestly think your best bet is to purge and start over. Use the official documentation found here - Self-Hosting Guide - Debian/Ubuntu server · Jitsi Meet Handbook

I returned the values back, ok, I’ll try to install everything according to the official documentation.

Run these commands to purge and reinstall. Should only take a few minutes to do:

sudo apt-get purge jitsi-meet jitsi-meet-web-config jitsi-meet-prosody jitsi-meet-web jicofo jitsi-videobridge2

sudo apt-get install jitsi-meet

sudo dpkg-reconfigure jitsi-videobridge2

sudo dpkg-reconfigure jitsi-meet-web-config

sudo /usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh

How to solve this issue correctly on one server nginx + turnserver?
conf nginx … 443->4443 (meet.site.com:4443) ?

If you are already running Nginx on port 443 on the same machine, turnserver configuration will be skipped as it will conflict with your current port 443.

I do not use NAT. White network. Reinstalled the entire server following the official configuration. The problem has not gone away …

2021-07-23T07: 13: 26.234Z [modules / RTC / BridgeChannel.js] <WebSocket.e.onmessage>: New forwarded endpoints: dc59172c, 2f43586d
Logger.js: 154 2021-07-23T07: 13: 26.240Z [modules / UI / videolayout / LargeVideoManager.js] hover in dc59172c
Logger.js: 154 2021-07-23T07: 13: 30.791Z [modules / RTC / BridgeChannel.js] <WebSocket.e.onmessage>: New forwarded endpoints: 2f43586d
Logger.js: 154 2021-07-23T07: 13: 31.806Z [modules / RTC / BridgeChannel.js] <WebSocket.e.onmessage>: New forwarded endpoints: dc59172c, 2f43586d