v2.5.0-alpha.7

• refactor(video): move bandwidth override to utils 959b65b
• feat(screenshare): add bitrate override for inbound streams 03b6fd6

v2.5.0-alpha.6

Merge pull request #90 from bigbluebutton/development

v2.5.0-alpha.6

v2.5.0-alpha.5

Merge pull request #88 from bigbluebutton/development

v2.5.0-alpha.5

v2.5.0-alpha.4

Merge pull request #86 from bigbluebutton/development

v2.5.0-alpha4 preview

v2.4.28

Patch release v2.4.28

CHANGELOG:

• video,screenshare,listenonly: add flags for ejection on userleft and permission probes
  • Those features were added in release v2.4.27
  • EJECT_ON_USER_LEFT/ejectOnUserLeft: Boolean
  • PERMISSION_PROBES/permissionProbes: Boolean

v2.4.27

Patch release v2.4.27

CHANGELOG:

• Implement media permission probes and improve media cleanup on user left/meeting end #79
  • Better cross-service checks on whether actions over video, screensharing and listen only (ie publishing and subscribing) are allowed. The probes are traded between bbb-webrtc-sfu and akka-apps (bigbluebutton/bigbluebutton#11538)
  • Fix cases where meeting ends and users being marked as left weren't triggering the server side stream tear-off procedures

v2.4.26

Patch release v2.4.26

CHANGELOG:

• kurento: add a mitigation to circumvent potential KMS UUID collisions #78
  • There is a (rare) possibility that two or more separate Kurento instances might generate collisions in the UUIDs they generate to identify media pipelines and media elements if they're spawned in a interval too short between one another.
  • Properly isolate media elements from different Kurento instances. In cases where a collision happens in a single KMS instance, negotiation will be rejected for the offender stream with error code 2214 (MEDIA_ID_COLLISION).
  • This is, of course, a mitigation until we fix the weak generator seed in KMS's uuid generator

v2.4.25

Patch release v2.4.25

CHANGELOG:

• connection-manager: SFU WebSocket connection IDs are now UUIDs (v4) c6f4b27
  • Should be future proof for absurdly long-lived deploys where the connection manager process is isolated
• logging, code quality: improvements to redis-wrapper, bbb-gw, process-manager, connection-manager eb5d4a1 5bc8832 ce0f084 57ab49a 09ce412
• logging: add option to disable stdout logging 74a0321
  • More fine-grained control to avoid logging to two places at once
  • Flags: default.yml's log.stdout, LOG_STDOUT_ENABLED environment flag (boolean)
• connection-manager: fix a rare edge case with error handling when setting up inbound Redis clients in the main process 09ce412
• process-manager: add process respawn interval 57ab49a
  • Avoids a process forking spiral when server gets OOM'ed to hell or something botched one of the children processes
• kurento: add flag to toggle ICE state change tracking 86d2720
  • Enabling it mainly generates logs about peer's ICE state transitions in the server
  • Disabled by default while we assess any performance impact due to enabling it. If it works OK, we'll use it in the future to harden derelict endpoint cleanups
  • default.yml's kurentoTrackIceStateChanges. KURENTO_TRACK_ICE_STATE_CHANGES environment flag (boolean)
• kurento: disable mDNS candidate processing by default d14bb22
  • Commit 377435c (v2.4.23) enabled mDNS processing by default. This was a decision made after testing it in a simulated intranet AND load testing it in regular setups.
  • Seeing that it worked with no apparent drawbacks, it was enabled. It seems, though, that enabling it causes stalls in Kurento
    processing pipelines earlier than expected in some specific providers. That effectively reduces Kurento's capacity by a fair margin.
  • We've only seen that happen in one specific cloud provider. It's not generalized. But we're reverting it to disabled by default until we
    figure out what's up.

v2.4.24

Patch release v2.4.24

CHANGELOG:

• [audio] Fix two edge cases that could cause all listen only endpoints to be wrongfully closed 2ad9f68 9e2c065 4f0427e
• Bump kurento-client to 6.15.0 3a12ee2

v2.4.23

Patch release v2.4.23

CHANGELOG:

• [screenshare] Add default values to vw/vh, soon to be deprecated 51e31a7
• [screenshare] RTMP broadcast: use akka-apps inbound channel 71e4ffc
• [screenshare] Make server-side akka-apps RTMP broadcast messaging optional c4a262a
  • screenshareServerSideAkkaBroadcast/SCREENSHARE_SERVER_AKKA_BROADCAST: true|false
• [kurento] Make mDNS candidate filtering configurable
  • Support for mDNS candidates got in an acceptable state, enable it by default
  • New config and env variables to toggle the filtering: kurentoAllowMDNSCandidates/KURENTO_ALLOW_MDNS: true|false