WebRTC Release Notes

From Genesys Documentation
Jump to: navigation, search

Not all releases or changes listed below may pertain to your deployment. Check the table below to see which releases apply to you.

Released onReleased forHighlights
September 22, 2021
PrivateEdition.png
Support for arbitrary UIDs in private edition deployments on OpenShift.
September 17, 2021
AWS.png Azure.png
v 100.0.009.0000. DN@SwitchName format handled properly now.
August 31, 2021
Azure.png
v 100.0.008.0000. Fixed WebRTC Media Service processing of ICE/DTLS completion and ICE errors.
July 14, 2021
AWS.png PrivateEdition.png
v 100.0.003.0000. Tested for Hunt Group feature in AWS.
July 09, 2021
AWS.png Azure.png PrivateEdition.png
v 9.0.000.89

Early Adopter Program support for Genesys Engage cloud private edition.

Hunt Group feature successfully tested in SIP Cluster deployments with WebRTC Media Service (AWS only).

200 OK status code sent for a pending/wait request when there is an authorization time out expiration.

September 22, 2021 PrivateEdition.png

PrivateEdition.png Private edition: 100.0.011.0000 available September 22, 2021

    For private edition

    • WebRTC now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
      • The Dockerfile has been modified to specify container and file ownership as user=500 (genesys) and group=0 (root).
      • The securityContext settings exposed in the default values.yaml file specify the user and group IDs for the genesys user (500:500:500). You must override these Helm chart values if you want OpenShift to use arbitrary UIDs. For more information, see Configure WebRTC.
      • WebRTC is deployed using ServiceAccounts that use the restricted Security Context Constraint (SCC). In an earlier implementation, Genesys required you to deploy all private edition services using a ServiceAccount associated with the custom genesys-restricted SCC, to control permissions for the genesys user (500). Genesys now expects OpenShift to use arbitrary UIDs in your deployment, and the genesys-restricted SCC has been deprecated. If you previously deployed WebRTC using the genesys-restricted SCC, Genesys recommends that you redeploy WebRTC so that you use arbitrary UIDs.
        (WRTCMS-764)
      More info: OpenShift security settings

      September 17, 2021 AWS.png Azure.png

        Resolved Issues

        • WebRTC Media Service now handles the DN@SwitchName format properly in sign-in request. Previously, WebRTC Media Service incorrectly handled the DN@SwitcName format for JSON-based signaling protocol, resulting in an invalid SIP DN being registered. (WRTCMS-792)

          August 31, 2021 Azure.png

            Resolved Issues

            • WebRTC Media Service no longer processes SIP re-invite until the current ICE/DTLS establishment process completes. Previously, because SIP re-invite did not require that the WebRTC connection be reestablished, WebRTC Media Service did not wait for the completion of the current ICE/DTLS establishment process. This resulted in the agent missing some part of the call (for example, the call did not include the whisper). (WRTCMS-773)
            • The WebRTC Media Service Java Script API library now handles Interactive Connectivity Establishment (ICE) errors and reconnects the media if possible. Previously, the library did not handle the ICE errors caused by temporarily network disconnection during active calls. This resulted in the media connection being lost. (WRTCMS-750)

              July 14, 2021 AWS.png PrivateEdition.png

              PrivateEdition.png Private edition: 100.0.003.0000 available July 14, 2021

                What's New

                • AWS only. The Hunt Group feature (parallel call distribution strategy) is successfully tested in SIP Cluster deployments with WebRTC Media Service. Supported in WebRTC Media Service v9.0.and v100.0.x. Calls are initiated/received by the browser-based Workspace Web Edition (WWE) 9.0.x. (WRTCMS-725)

                  July 09, 2021 AWS.png Azure.png PrivateEdition.png

                  PrivateEdition.png Private edition: 9.0.000.89 available June 30, 2021

                    What's New

                    • AWS only. The Hunt Group feature (parallel call distribution strategy) is successfully tested in SIP Cluster deployments with WebRTC Media Service. Supported in WebRTC Media Service v9.0.and v100.0.x. Calls are initiated/received by the browser-based Workspace Web Edition (WWE) 9.0.x. (WRTCMS-725)

                      Resolved Issues

                      • WebRTC Media Service now sends a 200 OK status code for a pending/wait request when there is an authorization time out expiration (<60 seconds). The subsequent wait request will be rejected with 403/401 messages. (WRTCMS-698)

                        For private edition

                        • Starting with this release, WebRTC is available for select customers in Genesys Engage cloud private edition, as part of the Early Adopter Program. (WRTCMS-661)
                          More info: WebRTC Private Edition Guide



                          Prior Releases

                          For information about prior releases of WebRTC, click here: WebRTC Release Notes