Added Citrix 4.1 support

To use Citrix 4.1, upgrade streamJs to 2.23.0 or above, and pass CITRIX_413 instead of CITRIX as the VDIPlatform, which allows you to use the new UCSDK 4.1 support, which supports:

• ICE Restart - Recovers the media connection after a network change
• Connection cleanup - Addresses stale peer connections leading to missed calls after agent reconnection

Requires compatible CWA version. Please refer to Citrix documentation for version requirements:

https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/multimedia/unified-communications-sdk-optimization.html#versions-and-feature-matrix

Support persistent media connection

What's Changed

• Support persistent media connection (require https://github.com/amazon-connect/amazon-connect-streams/releases/tag/v2.21.0)
• Stop refreshing standby peer connection when PCF is closed

v1.2.1

This release contains changes related to:

New features and improvements:

• Added Omnissa VDI Strategy support
• Implemented ICE Restart for all VDI environments (Citrix, Omnissa, DCV)
• Added ChromeOS support for Citrix VDI
• Fixed mute functionality issues in VDI environments
• Persistent Connection

Add close method to peer connection factory

Add close method to peer connection factory.

Supporting AWS Workspaces WebRTC Redirection

Adding AWS Workspaces WebRTC redirection support.

Note: Streams v2.14.4 and above is required for AWS Workspaces WebRTC redirection support.

Resolving Missed Call Issue for Citrix Integration

This release addresses the missed call issue for Citrix integration that could occur after long connection time, by upgrading the UCSDK dependency to v3.1.0

Fix missing standby peer connection issue

Fix missing standby peer connection issue which was introduced in v1.1.22

Supporting Citrix WebRTC Redirection

Adding Citrix WebRTC redirection support.
Note: Streams v2.12.0 and above is required for Citrix WebRTC redirection support.

Enforcing the usage of the standardized getStats API

In this release, we have made improvements to the getStats() function to ensure compatibility with Chrome's upcoming changes.

Background: RTCPeerConnection has two versions of getStats(), one that is spec-compliant returning the report via resolving a promise, and one that is non-standard returning a very different report via a callback as the first argument. The non-standard callback-based version of getStats() will be removed in future versions of Chrome.

To align with Chrome's future release, we have enforced the use of the standardized (promise-based) version of getStats() in this release. This change ensures a seamless transition by generating output that is consistent with the results obtained from the legacy getStats API. Please make sure to upgrade your connect-rtc-js to this version to support the Chrome future release. Please find more about the Chrome deprecation plan here: https://groups.google.com/a/chromium.org/g/blink-dev/c/PxQQtEM7za0/m/Dg-zX1bZBQAJ

Improved error handling for extracting MediaRtpStats

Improved error handling for getStats method. Motivation: #57