Skip to end of metadata
Go to start of metadata

Table of Contents:

About WRTC Release Notes

This page describes the enhancements done in Sonus WebRTC release R002.

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.

Upgrade Paths

Before upgrading to WRTC1.2R002, you must take a backup of startup.json file and replace it once the new package(WRTC 1.2R002) is installed.

Release FamilySeriesUpgrade Path

* The upgrade path is explicitly tested by Sonus with debian upgrade.


The WRTC interoperates with the following:

  • SBC 5.0 to provide media service functionality when WebRTC endpoints are behind a NAT.
  •  EMS 10.0 with DM build [Insight EMS 10.00.00 DM 01.00.00 WRTC 01.02.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

The WRTC 01.02.00R002 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.00R002




Supported Devices

SBC 7000 Series

SBC 5000 Series








* WRTC 01.02.00R002 is explicitly tested with Insight EMS 10.00.00R000 by Sonus with DM build [Insight EMS 10.00.00 DM 01.00.00 WRTC 01.02.00]

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

Sonus WebRTC Installation Notes

For information on installation of WRTC Gateway, refer to the Installing Sonus WebRTC Gateway.

By default, the OVA image is created using small configuration. From WRTC 1.2R001 release onwards, the configuration can be upgraded to large configuration based on the available resources on the VM host machine. For detail information on small and large configurations setting, refer to Virtual Resource and Software Requirement.

The configuration is upgraded using VSphere client settings after creating the VM instance.

The VM instance must not be powered on before upgrading from small to large configuration.

The following figures show the steps to upgrade from small to large configuration using Edit Settings option for a VM instance.

Figure : Hard Disk Settings


Figure : Memory Settings


Figure : vCPU Settings


After the settings are set, the instance must be powered on to install WRTC.

Flexibility for selecting any custom configuration depends on availability of enough resources( RAM, CPU, DISK space) on VMWare Host Machine. 

Installing Sonus WebRTC on Amazon Cloud

The following Amazon Machine Image (AMI Id) is created for this release and shared privately with the customer AWS accounts. For more information on installing WRTC on Amazon cloud, refer to Installing Sonus WebRTC on Amazon Cloud.

Table : AMI Id

N. Virginia


Refer to documentation on how to obtain the AMI image.

 New Features and Enhancements in WRTC 1.2R002

The following enhancement is made in Unity Explorer in this release.

 Modify Enterprise URL Profile in Unity Explorer

From WRTC data model in Unity Explorer, you must update Enterprise URL to map it with the respective Enterprise. It is observed that if you modify an Enterprise URL, the other URLs in the list gets deleted.

To overcome the deletion of saved entries when an existing entry is edited, perform the following steps:

  1. Copy Unity Explorer (UE.V02.00.02A001.tar.gz) at /tmp folder on your EMS server.

  2. Login to EMS Server.

    cd /opt/sonus/ems/
  3. Stop the EMS server.

    ./sonusEms stop
  4. Navigate to the /tmp where you have saved the UE tar file.

    cd /tmp
  5. Unzip the tar file.

    gunzip UE.V02.00.02A001.tar.gz
    tar -xvf UE.V02.00.02A001.tar
  6. Execute the following commands to deploy and use the tar file, and then start the EMS service.

    \rm -rf ema model.tar uekit.tar UE.V02.00.02A001.tar
    cd /opt/sonus/ems
    ./sonusEms start

Log File Rotation Activity

In this release, the following two parameters are introduced in startup.json:

  • LogRotationInterval: 3600 // This is read in seconds
  • MaximumLogFileSize: 1 // This is read in MB

With the introduction of these two parameters, WRTC Gateway checks if wrtc.log and vertx.log are greater than 1 MB for every 1 hour. If found then, WRTC Gateway would tar the log files in tar.gz format.

You must restart the application after updating startup.json with both the parameters. For more information on starting and stopping of WRTC application, refer to Starting and Stopping WRTC Server.

If this feature needs to be disabled, make either or both of this parameter as 0.

Problems Resolved

Problems Resolved in WRTC V01.02.00R002

This section describes the problems resolved in this release.

Table : Problems Resolved



Problems Resolved in WRTC V01.02.00R002




WSX-2714: WRTC unable to read the admin ID and password even after, configured and pushed from EMS.

On deleting the Enterprise domains, the authentication credential of a different Enterprise was getting corrupted. The code has been modified to resolve this issue.


WSX-2769: WRTC EMS REST API password does not allow sufficient flexibility.

Special characters like $ # ! were not supported in EMS reset password. Code has been modified to allow such characters.


Known Limitations

The following are the limitations for this release:

  • EMS UE text boxes are accepting symbol "&" as "&". As a workaround, you need to select login and passwords with character, numbers or any special character expect “&”.

    If “&” is chosen, then user has to input the string as “& “