* fix: Drops unused parameter of join and sendPresence.

* feat: Skips using disco-info for features.

Uses presence to publish features added externally.
Recognizes jigasi participants using a specific presence extension used by jigasi.

* squash: Fixes tests.

* squash: Adds e2ee to the features in presence.

* squash: Fix function name and docs.

* squash: Drops detecting jigasi from initiator.

Using the newly added presence features.

* squash: Drops unused var.

* squash: Fix comments.

* squash: Adds a constant and for E2EEE feature.

which should include the colon in order not to match something like
  a=simulcast-is-cool

in order to not match a=msid-somethingelse, a=ridiculous and similar

Explicitly check if all the encodings report the same scaleResolutionDownBy value before trying to ensure they match the expected values. This makes Chrome VP9 work again.

Due to no timeout value passed the disconnection was not detected.

Now stores the time of the raw input when ping is received. Before this change we were storing the Date.now and comparing to _getTimeSinceLastServerResponse and we needed small adjustment of values as it may lead to no pings sent.

* fix: Always query the main domain for features.

* squash: Always use the main domain for turn credentials and ping.

* squash: Fix tests.

* feat: Make enableRemb signal client remb support.

* feat: Make enableTcc signal client tcc support.

* ref: Remove the enableOpusRed conference-wide option.

* ref: Remove the "enforcedBridge" option.

* ref: Remove pre-configured jigasi address.

The plan is to move the lastNLimits logic to bridge. The clients will be able to override(lower) the bridge limits through the bridge channel only. Also, this lets us configure last-n per receiver and not set the last-n value for the whole conference the way Jicofo sets it currently.

Fixes https://github.com/jitsi/jitsi-meet/issues/8094.

It has been `true` for a very long time.

Cleanup some unused code after the bump.

On every call to RTCRtpSender.setParameters(), ensure that the resolution configured for the encoding matches that of the value configured on the RTCRtpSender when the source was added to the peerconnection. This should prevent us from overriding the default values if the browser returns erroneous values when RTCRtpSender.getParameters is used for getting the encodings info. This fixes the issue on recent versions of Safari where the 'scaleResolutionDownBy' value comes back as 1 for all encodings even though the encoding resolution is different from the stream capture resolution.

In p2p mode, 'scaleResolutionDownBy' is used for downscaling a stream when needed, i.e. when the user receives a receive constraint of 360p because the other participant is in tile view. When desktop share is started, the encoding config has to be scaled back up so that the other participant starts receiving HD resolution for the share as desktop shares are autopinned. Therefore, encodings have to enabled/disabled for desktop shares as well. Earlier it was done only for camera tracks.

* feat: Skips pinging when there was a recent server response.

* feat: Adds options to control xmpp ping settings.

* fix: Fixes wrong default value.

* squash: Received messages in ping interval sets failed ping to 0

Co-authored-by: Saúl Ibarra Corretgé <s@saghul.net>

The old stream needs to be released while keeping the tracks intact

Signs and verifies frames. For now this is done on every frame.
This is not the long-term goal and there needs to be a better strategy.

Fixes https://github.com/jitsi/lib-jitsi-meet/issues/1333 in applications that use lib-jitsi-meet and do not have layer suspension enabled.

Add the conference flag back since the bridge is able to handle the case where more than 1 temporal layers are received even when only 1 ssrc is signaled.

* ref: Do not include the full JSON when firing event (unused).

* ref: Logging and formatting fixes.

seen in #1364 but it is older

In Chrome, if 'maxBitratesVideo' options are specified
and 'capScreenshareBitrate' is disabled, then simulcast is enabled
for screenshare. Chrome in plan B, does not send screen stream if
'maxBitrate' are set and simulcast is enabled.

and add a few new ones.