Release Note

Genesys WebRTC Gateway

8.5.x

Genesys Telecommunications Laboratories, Inc. © 2014–2020

Contents

Introduction

Release Number AIX HP-UX PA HP-UX IPF Linux Solaris Windows
8.5.210.95 [03/27/2020] – Hot Fix       X   X
8.5.210.93 [01/28/2020] – Hot Fix       X   X
8.5.210.89 [10/03/2019] – Hot Fix       X   X
8.5.210.84 [09/11/2018] – Hot Fix       X   X
8.5.210.75 [08/03/2018] – Hot Fix       X   X
8.5.209.99 [12/20/2017] – Hot Fix       X   X
8.5.208.71 [05/12/2017] – General       X   X
8.5.208.16 [01/31/2017] – Hot Fix       X   X
8.5.206.25 [04/29/2016] – Hot Fix       X   X
8.5.204.88 [10/23/2015] – Hot Fix       X   X
8.5.203.14 [03/24/2015] – General       X   X
8.5.202.44 [12/12/2014] – Hot Fix       X   X
8.5.201.95 [10/06/2014] – General       X   X
8.5.201.30 [07/18/2014] – General       X   X
8.5.200.95 [06/02/2014] – General       X   X

Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


Introduction

This release note applies to all 8.5 releases of Genesys WebRTC Gateway.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For specific information on any third-party software used in this product, see the Legal Notices for WebRTC. Please contact your Genesys Customer Care representative if you have any questions.


Release Number 8.5.210.95 [03/27/2020] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:


WebRTC Gateway now uses Datagram Transport Layer Security (DTLS) version 1.2 for Secure Real-Time Transport Protocol (SRTP) session establishment. WebRTC Gateway previously used the now obsolete DTLS version 1.0 for SRTP session establishment.
(MWA-712)


Top of Page


Release Number 8.5.210.93 [01/28/2020] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following correction and modification:


Genesys WebRTC Gateway now uses request URL parameters or the value of the Cookie header to match the HTTP request with the existing client's session. WebRTC Gateway previously used only the request URL parameters to match the HTTP request with the existing client's session.

To restrict the usage of URL parameters, use use-sid-from-url configuration option.

Note:Genesys WebRTC now sends the cookies that are secured and flagged with the attribute SameSite=None. Cookies with the Secure flag are sent only via HTTPS when the HTTPS mode is enabled in the WebRTC Gateway application. For this, at the application level, the rsmp/tenable-https option should be set to true. If HTTPS is not enabled, WebRTC Gateway only sends the cookies. However, the latest versions of Google Chrome block third-party cookies unless the cookies are secured and flagged.

This option works with Genesys WebRTC Java Script API from version 8.5.210.35.

For more information on Configuration options, see the Configuration Options Reference guide.

(MWA-706)


Top of Page


Release Number 8.5.210.89 [10/03/2019] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following correction and modification:


Previously, WebRTC Gateway incorrectly processed HTTP "OK" message from browser for released call and it leaded DN to be stuck in busy state. Now, WebRTC Gateway properly handles such messages. (MWA-699)


Top of Page


Release Number 8.5.210.84 [09/11/2018] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following correction and modification:


WebRTC Gateway no longer terminates unexpectedly during RTP renegotiation on receiving DTLS packets for the previously established RTP session. (MWA-611)


Top of Page


Release Number 8.5.210.75 [08/03/2018] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following correction and modification:


WebRTC Gateway now correctly processes the media streams by performing SRTP renegotiation when retrieving a video call from hold. Previously, retrieving a video call from hold might fail because WebRTC Gateway did not perform SRTP renegotiation when the remote key was changed and SSRC was unchanged. (MWA-687)


Top of Page


Release Number 8.5.209.99 [12/20/2017] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This section describes new features that were introduced in this release of Genesys WebRTC Gateway.

Corrections and Modifications

This release does not include any corrections or modifications.

Top of Page


Release Number 8.5.208.71 [05/12/2017] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


Session re-negotiations now work correctly in Firefox 55 Nightly, with a=setup:actpass set in offer SDPs by the gateway. Previously, the setup attribute was not set during re-negotiations, resulting in failure. (MWA-590)


Media stream is now established correctly when making a call using Firefox version 51 or 52. Previously, this did not work due to incompatible ciphers, and is now fixed by updating the version of the OpenSSL library. (MWA-584)


Top of Page


Release Number 8.5.208.16 [01/31/2017] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This section describes new features that were introduced in this release of Genesys WebRTC Gateway.

Corrections and Modifications

This release also includes the following corrections and modifications:


An ICE connection is now established between Mozilla Firefox and WebRTC Gateway, when the Gateway is in a private network and is using a STUN Server to find its server reflexive address. (MWA-536)


The G.722 audio codec is now enabled on the WebRTC Gateway by default. (MWA-98)


An audio-only call can now be resumed after video-on-hold is played to the browser client, during a hold by the peer. Previously in Mozilla Firefox, resuming the call did not work. (MWA-576)


Top of Page


Release Number 8.5.206.25 [04/29/2016] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This section describes new features that were introduced in this release of Genesys WebRTC Gateway.

Corrections and Modifications

This release also includes the following corrections and modifications:


In WebRTC Gateway, the client message queue to the browser is now cleared on a new call if a problem is detected. Previously, the queue might have become full due to some client issue, which caused any new message going to the client to be dropped. (MWA-528)


WebRTC Gateway now uses multi-threaded versions of the Management Framework libraries on Linux. Previously, single-threaded versions were used, which caused WebRTC Gateway to shut down unexpectedly. (MWA-525)


When upgrading a WebRTC call from audio only to include video in the Firefox browser, media bundle will now be used, if it is enabled on the platform. Previously, media bundle could not be used in this scenario. (MWA-518)


Top of Page


Release Number 8.5.204.88 [10/23/2015] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


A new SIP INVITE that is immediately preceded by an SDP negotiation is now handled correctly by appropriate queuing. Previously in this scenario, the SIP INVITE was rejected with the error 486 Busy Here. (MWA-499)


WebRTC Gateway now checks configured media codecs’ dynamic payload numbers and, if a number is out of range, it ignores the configured value and selects a valid value. Previously, the Gateway terminated when a dynamic payload number that was configured in the codecs configuration parameter was out of range. (MWA-500)


A race condition related to SIP CANCEL no longer causes WebRTC Gateway to shut down unexpectedly. (MWA-504)


The size of the message queue to the web client has been increased in order to avoid related failures. (MWA-505)


The media-level tags that are used for media bundle support in an SDP Answer now match the tags in the SDP Offer. Previously, these tags were hardcoded to the tags used by Chrome. This hardcoding caused issues with Firefox, which recently added media BUNDLE support. (MWA-506)


The Datagram Transport Layer Security (DTLS) establishment between WebRTC Gateway and Firefox version 38 and higher now works correctly when Firefox is in an active role, that is, when Firefox is the callee. (MWA-507)


You can now use the rsmp.sip-proxy configuration parameter to specify two SIP Server addresses, separated by a comma, which will be used for High Availability. Only one of the SIP Servers will be active at any one time and, when a request to it times-out, the Gateway will start using the other SIP Server. Also, you can use the configuration parameter rsmp.sip-proxy-srv to configure the SRV address of the SIP Server. When a SIP request arrives from this SRV address, the response is sent to the currently active SIP Server address. (MWA-508)


Top of Page


Release Number 8.5.203.14 [03/24/2015] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following correction and modification:


Outbound calls using Broadsoft extensions and 3PCC now work properly. Previously, they could fail due to a race condition in the WebRTC Gateway. (MWA-477)


Top of Page


Release Number 8.5.202.44 [12/12/2014] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


A conferencing issue no longer occurs when using WebRTC Gateway with Chrome version 36 or later. Previously, the following issue occurred:

  1. Inbound call was answered by Agent1.
  2. Agent1 consulted with Agent2.
  3. Agent1 completed conference.
  4. Agent1 could not hear Caller and Agent2.

(MWA-456)


Possible issues in Chrome with SRTP are now avoided during hold and resume operations when music on hold is enabled. Previously, this may have caused issues when the media source changed on the SIP side, as delayed packets from the old media source may have been forwarded to the web client. (MWA-454)


DTLS establishment in the WebRTC Gateway now happens quickly and consistently. Previously, it could be arbitrarily delayed when the Gateway was running on a Linux system. (MWA-464)


Top of Page


Release Number 8.5.201.95 [10/06/2014] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Genesys WebRTC Gateway.

Corrections and Modifications

This release also includes the following corrections and modifications:


When video is disabled and then re-enabled from the SIP-side during a call using DTLS and media-bundle, the video now plays correctly on the web-side. Previously, the video would not play correctly on the web-side under these circumstances. Also, if you carry out hold and resume operations with music-on-hold while using DTLS, these operations now work correctly. (MWA-437)


You can now use the web-ice-addresses configuration parameter to specify multiple local IP addresses for use by the ICE library. The WebRTC Gateway also supports HTTP OPTIONS. (MWA-438)


When using the Chrome web browser, if you re-enable video after disabling it, Chrome receives video from the peer, as expected. However, it will not send video to the peer, due to WebRTC issue 2136. (MWA-442)


Top of Page


Release Number 8.5.201.30 [07/18/2014] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Genesys WebRTC Gateway.

Corrections and Modifications

This release also includes the following corrections and modifications:


Video media are now correctly played when a callee sends a new mid-call offer. Previously, video media were not always played when a new offer was sent. ICE checks are also now only carried out once during session renegotiation, unless more than one ICE check is required. (MWA-390)


New media streams (for example, video) can now be added to a call when using DTLS-SRTP. Support for a new PeerConnection by re-establishing DTLS for all media streams has also been added. This is needed with browsers that do not support call renegotiation, such as Firefox (as explained in Firefox Bug 857115). (MWA-392)


Top of Page


Release Number 8.5.200.95 [06/02/2014] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this initial 8.5 release of Genesys WebRTC Gateway.

Corrections and Modifications

This first release of this product does not include any corrections or modifications.

Top of Page


Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.


Upgrading a video-only call to an audio plus video call currently does not work. (MWA-594).

Found In: 8.5.208.71 Fixed In: 

Firefox has now added support for session renegotiation. However, the default behavior in the gateway and the Genesys WebRTC JavaScript API is to create a new PeerConnection for each renegotiation. You can take advantage of the Firefox renegotiation support without having to create new PeerConnections by doing the following:

  1. Set the configuration option rsmp.new-pc-support to 0 (the default value is 1). Note that you will need to add this option in Configuration Manager.
  2. Set a corresponding option in the Genesys WebRTC JavaScript API by calling the Grtc.Client method setRenewSessionOnNeed(false).

Be aware, however, that the Firefox renegotiation support has not been well tested, and is disabled in the platform by default.


The Chrome browser, since version 47, supports user media operations only from secure origin. If you are using Genesys WebRTC service with Chrome browser version 47 or higher, you must use HTTPS for the application server, as well as the WebRTC Gateway. To do this, configure the WebRTC Gateway and set up the application server with the appropriate security certificates as described in the Genesys WebRTC Service Deployment Guide.


The following conferencing issue occurs when using WebRTC Gateway with Chrome version 36 or 37 (latest stable version):

  1. Inbound call is answered by Agent1.
  2. Agent1 consults with Agent2.
  3. Agent1 completes conference.
  4. Agent1 cannot hear Caller and Agent2.
  5. Agent2 and Caller can hear each other, and they can also hear Agent1.

To work around this issue, Agent1 can hold and then resume the call, and all three parties will be able to hear each other.

(MWA-456)

Found In: 8.5.201.95 Fixed In:  8.5.202.44

Google Chrome has an outstanding issue that affects the WebRTC Gateway:


When you use the Genesys WebRTC Service and the Genesys Voice Platform Media Control Platform (MCP) on Red Hat Enterprise Linux (RHEL), Genesys recommends that MCP be run on a server that is separate from the server running the WebRTC Service, for two reasons:


The WebRTC Gateway displays a memory leak while running under Windows, due to an issue with the LibNice/GLib third-party library that is used by the Gateway. The amount of the leak varies with the call scenario being used. For example, for browser-to-browser call scenarios the observed leak is approximately 70 bytes per audio-only call and approximately 800 bytes per audio-video call.

If you are deploying the WebRTC Gateway in a Windows environment, Genesys recommends that you monitor memory and be prepared to restart the Gateway in cases where it becomes necessary to do so. (MWA-321)


Note that the WebRTC Gateway normally supports only the two most recent versions of supported browsers.


Top of Page


Discontinued Support

This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.


There are no discontinued items for this product.


Top of Page


Internationalization

Information in this section is included for international customers.


There are no internationalization issues for this product.


Top of Page


Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).

Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page