Skip to end of metadata
Go to start of metadata

Table of Contents:

About WRTC Release Notes

This document describes new feature changes, the latest requirements, known issues, resolved issues, and other pertinent release information for the latest release of Web Real Time Communications (WebRTC).

Related Documentation

The Sonus WebRTC documentation is located at the following Sonus Networks Wiki space: WebRTC Services Solution Documentation.

Problems or Questions

For problems or questions, contact the Sonus Technical Assistance Center (TAC) via telephone, fax, or e-mail:

Worldwide Voice: 1 (978) 614-8589

USA Toll-free: 1 (888) 391-3434

Worldwide Fax: 1 (978) 614-8609


About Sonus WebRTC Services Solution

Sonus WebRTC enables you to place a call to a contact center, participate in a multi-party audio and video conference, or engage in a screen sharing collaboration with colleagues over the internet or intranet without any additional plug-ins or downloads on your computer or mobile device. Any device that supports WebRTC enabled browser can be used to communicate with another WebRTC enabled browser or SIP call over the internet or intranet.


WRTC interoperates with the following:

  • SBC 5.1 to provide media service functionality when WebRTC endpoints are behind a NAT.
  • EMS 10.0 with DM build [Insight EMS 10.00.00 DM 02.00.00 WRTC 01.03.00] to register a WRTC node in to the appropriate cluster. The EMS also supports key functions including cluster configuration, fault, and performance management.

Compatibility with Sonus Products

WRTC 01.02.00R003 release is compatible with the following Sonus product releases versions:

The minimum compatible release versions are listed.

Table : Compatibility with Sonus Products

 WRTC V01.02.00R003




Supported Devices

SBC 7000 Series

SBC 5000 Series







WRTC 01.02.00R003 is explicitly tested with Insight EMS 10.00.00R000 by Sonus with DM build [Insight EMS 10.00.00 DM 02.00.00 WRTC 01.03.00]

** Sonus tested with SBC 5200 and SBC SWe explicitly.

Obtaining an AMI Image

The following AMI is created for this release and shared privately with the customer AWS accounts.

Table : AMI IDs

RegionAMI ID
N. Virginiaami-10e62706

Refer to documentation on how to obtain the AMI image.

Metadata and Userdata Changes

From WRTC 01.02.00R003 release, two new variable groups are associated with BillingServerPrimary and BillingServerSecondary with the following default values. These values needs to be manually configured or edited in startup.json file before the WRTC application starts.

"BillingServerAddressSecondary": "",

"BillingServerUsernameSecondary": "user",

"BillingServerPasswordSecondary": "pass",

"BillingServerUsernamePrimary": "user",

"BillingServerTargetDirectory": "/root/",

"BillingServerRetries": "3",

"BillingServerAddressPrimary": "",

"BillingServerPasswordPrimary": "pass",

"BillingServerPort": "21",

Upgrade Procedure from 01.02.00R002 to 01.02.00R003

Software used before upgrade:

EMS version: Insight EMS 10.00.00 DM 01.00.00 WRTC 01.02.00

WRTC version: 01.02.00R002 (Active-Active 2 node)

SDK version: 01.02.00R001


This section describes the upgrade procedure from WRTC 1.2.0R2 to 1.2.0R3:

Upgrading DM

  1. Download the DM package EMS10.0.0-WRTC1.3.0-DM2.0.0-pkg.tar.gz from Salesforce web portal.
  2. Copy the DM package to the /tmp directory of EMS server.
  3. Log on to the EMS server and move to the /tmp directory using the following command.

    cd /tmp
  4. Extract the DM package using the following command

    tar -zxvf EMS10.0.0-WRTC1.3.0-DM2.0.0-pkg.tar.gz
  5. Install the DM using the following commands.

    1. Stop the EMS server by issuing ./sonusEms stop in EMS_HOME

    2. Log on as root user in the EMS server

    3. Change the working directory to untared DM package directory where is located.

      cd EMS10.0.0-WRTC1.3.0-DM2.0.0
    4. Run the following command.

    5. Enter option "a" to install the Device Manager. When prompted to continue DM installation press "Y".

  6. Once the installation is completed successfully, start the EMS server by issuing ./sonusEmsstart in EMS_HOME.
  7. Log on to EMS and verify the existing configuration is retained.

Upgrading WRTC Application

  1. Log on as wrtc and stop the WRTC process.

    su - wrtc
    ./sonuswrtc stop
  2. Log on as root user


  3. Remove the existing package using the following command.

    dpkg -r wrtc
  4. Download the WRTC package wrtc_V01.02.00-R003_amd64.deb from Salesforce.
  5. Copy the package to /opt/sonus/external directory.
  6. Install the new WRTC package from the same path mentioned above.

    dpkg -i wrtc_V01.02.00-R003_amd64.deb
  7. Update the Billing Server information accordingly in /opt/sonus/wrtc/startup.json file.

    "BillingServerAddressSecondary": "",
    "BillingServerUsernameSecondary": "user",
    "BillingServerPasswordSecondary": "pass",
    "BillingServerUsernamePrimary": "user",
    "BillingServerTargetDirectory": "/root/",
    "BillingServerRetries": "3",
    "BillingServerAddressPrimary": "",
    "BillingServerPasswordPrimary": "pass",
    "BillingServerPort": "21",
  8. Make sure the /opt/sonus/wrtc/wrtcCloudInputs is retained as earlier.
  9. Change directory to /opt/sonus/wrtc and perform the following command.

    cd /opt/sonus/wrtc
    ./wrtcnodeinit start
  10. Once the script execution is completed, log on as wrtc user.

    su - wrtc
  11. Start the WRTC application.

    ./sonuswrtc start

Upgrading SDK

  1. Download the package wrtcsdk-V01.02.00-R003.x86_64-sdk.tar from Salesforce web portal.
  2. Untar the package
  3. Extract the wrtcsdk.min.js
  4. Replace the old wrtcsdk.min.js with the new wrtcsdk.min.js in the target web server.
  5. Restart the web server.

Problems Resolved

Problems Resolved in WRTC V01.02.00R003

This section describes the problems resolved in this release.

Table : Problems Resolved


Problems Resolved in WRTC V01.02.00R003



WSX-3212: Huge memory hit on WebRTC GW.

The SJCP ACK message sent by SDK will carry sequence number received in the last SJCP message received from the WRTC Gateway. This helps the WRTC Gateway to clear up the queued messages. The code has been modified to resolve the issue.


WSX-2812: Admin ID for an enterprise do not accept special characters except "@"

The admin ID field in EMS will accept special characters like "@". The code has been modified to resolve the issue.


WSX-2992: Users active are not timing out.

The problem is detected when users switch between the nodes.The code has been modified to resolve the issue.


WSX-3096: When REGISTER has +1 no de-register is sent upon logout

The code has been modified to send de-register for users allocated numbers with country code.


WSX-2526: To track the memory leak issue in WRTC found during performance load testing

Few potential memory leak points have been fixed by removing necessary object from data cache.


WSX-3289: Transport is stuck when switching existing IP Peer from UDP to TCP and back to UDP

This is a rare case scenario in which the SBC transport type was changed before a user logs out. The code has been modified to handle such mid-way changes in IP, port or transport.


WSX-3396: Implementing bi-directional SIP INFO

WRTC Client SDK will now receive SJCP INFO message received directly from peer WRTC client or through SBC in form of SIP INFO.


WSX-3422: ACK messages floods the browser console after login to WSX in Release 1.2

The code has been modified to accept the timer value in seconds.


WSX-3433: RTCP-MUX Issue

The RTCP-MUX value in SDK has been included with "negotiate", while creating the peer connection.


Known Issues

The following issues exist in this release are:

Table : Known Issues in This Release

Issue IDSevPlatformProblem DescriptionWorkaround
WSX-34693DebianThe configured billing server address is not retained in startup.json after upgrading to 1.2R3

Workaround: Update the Billing Server information accordingly in /opt/sonus/wrtc/startup.json file as mentioned in Step 7 of Upgrading WRTC Application.