Revision as of 11:38, April 2, 2020 by Lkrishna (talk | contribs)
Jump to: navigation, search

WebRTC Media Service

Information.png Note: Not all changes listed below may pertain to your deployment.

April 03, 2020 (9.0.000.49)

What's New

  • The Coturn server of the WebRTC Media Service Coturn component is upgraded to version 4.5.1.1 to allow the WebRTC Media Service to work with Federal Information Processing Standards (FIPS) compliant version of OpenSSL library.

Resolved Issues

  • The Third party call control (3PCC) retrieve operation in WebRTC now works properly when it is initiated by a browser based WebRTC agent that uses the Opus codec. Previously, this retrieve operation did not work properly as the agent did not receive the media. (WRTCMS-420)
  • The WebRTC Media Service Gateway now checks only the relay type remote candidates, which reduces the total media connection establishment time. Previously, WebRTC Media Service Gateway was processing remote Interactive Connectivity Establishment (ICE) candidates and checks all types of candidates including the host. These checks always failed as the outbound connections from the WebRTC Media Service Gateway are prohibited and increased the media connection establishment time. (WRTCMS-416)
  • To improve the media connection establishment time, WebRTC Media Service Gateway will not re-Invite the WebRTC participant from the Session Initiation Protocol (SIP) side if:
    • There is an SIP re-Invite without Session Description Protocol (SDP).
    • The SIP re-Invite SDP media direction and the active/inactive state was not changed and it does not have any new media types.

For the above cases, WebRTC Gateway creates new offer/answer SDP based on the previously used local SDP. (WRTCMS-415)

  • WebRTC Media Service Gateway now properly process the second INVITE without SDP by replying 200 Ok with offer SDP. Previously, when WebRTC Media Service Gateway received two subsequent SIP INVITE requests without SDP, it sent 200 Ok response for the second INVITE without offer SDP. It violates Request for Comments (RFC) 3261 and could have lead to media connectivity establishment failure. This would have affected the following scenarios:
    • Route call to WebRTC agent with recording
    • 3PCC call from WebRTC agent with recording
    • Consult call from WebRTC agent with recording

(WRTCMS-413)

  • Now, WebRTC Media Service Gateway do not allow G722 codec usage for media connections. (WRTCMS-409)

January 31, 2020 (9.0.000.47)

What's New

  • The WebRTC Media Service now provides call quality statistics using the HTTP call message PUT-STATS. This message is automatically sent by WebRTC Gateway to the WebRTC JavaScript client at the end of each call and contains call quality statistics in JSON format.

    The WebRTC JavaScript library then passes the call quality statistics to WWE 9. WWE 9 then includes the call quality statistics in the AttributeUserData of the RequestDistributeUserEvent message that is distributed to SIP Server at the end of the interaction. The corresponding key-name is retrieved from the value of interaction-workspace/webrtc.quality.statistics.key-name configured at the Application/Person level.
Important
This feature is applicable only for browser-based WebRTC clients with WWE 9.

Resolved Issues

  • WebRTC Gateway now includes SameSite=None and Secure attributes to all Set-Cookie headers generated by the Gateway. (WRTCMS-300)

November 07, 2019 (9.0.000.43 UPDATE)

What's New

Legacy SIP Environment

  • WebRTC Media Service now works with SIP Server operating in Standalone mode. Previously, WebRTC Media Service was integrated only with SIP Cluster.

Microservice Monitoring

  • WebRTC metrics reporting to Prometheus monitoring system is expanded with a new metric named wrtc_system_error to capture internal problems that occur in the WebRTC Media Service. Based on this new metric, the Prometheus monitoring system will raise an alert when an internal problem occurs.

October 02, 2019 (9.0.000.41 UPDATE)

What's New

Elasticsearch

  • WebRTC Media Service now supports Elasticsearch by sending different data into Elasticsearch. This feature allows you to store and quickly analyze large volumes of data in real-time.

Resolved Issues

  • Stability improvements have been made in WebRTC Media Service to prevent WebRTC gateway from terminating unexpectedly under certain conditions. (WRTCMS-253)

July 03, 2019 (9.0.000.37 UPDATE)

What's New

WebRTC Agent timeout

  • WebRTC Agent will now be signed out of the session if the connection between the Endpoint and WebRTC gateway is broken for more than the configured time. For improved security reasons, this time period is set to 5 seconds by default. However, it is configurable up to 15 minutes.

April 11, 2019 (9.0.000.37)

What's New

SIP addresses

  • WebRTC Media Service now retrieves the SIP address from Genesys Web Services (GWS) version 9 automatically and users are not required to configure the SIP address while provisioning Agent Desktop. The Agent Desktop supported version is 9.0.000.21 and above.

December 21, 2018 (9.0.000.27)

What's New

  • WebRTC Media Service now supports OAuth 2.0 authentication and authorization method to validate the user credentials passed from Agent Desktop. The Genesys Softphone compatible version to support OAuth 2.0 is 9.0.004.05 and above and the Agent Desktop version is 9.0.000.17 and above.

June 29, 2018 (9.0.000.15)

What's New

Initial release

This is the initial release of WebRTC Media Service on the PureEngage Cloud (PEC) platform. Agents can handle both inbound and outbound voice calls through WebRTC-capable devices like Genesys Softphone by communicating with the PEC platform through the WebRTC Media Service. The WebRTC Media Service supports Genesys Softphone version 9.0.003.04+.

The key features of the WebRTC Media Service are:

  • Supports G.711 and Opus codecs.
  • Provides real-time media transcoding whenever required.
  • Supports audio calls only.
  • Signalling and media encryption capabilities of WebRTC Media Service ensures appropriate security for voice communications over the public network.

Known Issues

There are currently no known issues.

Comments or questions about this documentation? Contact us for support!