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 V01.03.00R002.

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

Email: TechnicalPublications@sonusnet.com.

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.

Interoperability

The 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 EMS10.0.0-WRTC1.3.0-DM1.0.0] to register a WRTC node in to the appropriate cluster. The EMS also supports key functions including cluster configuration, faul and performance management.

Compatibility with Sonus Products

The WRTC Version  01.03.00R002 release is compatible with the following Sonus product releases versions:

Table : Compatibility with Sonus Products


 
 WRTC V01.03.00R002

 

 

 

Supported Devices

SBC 7000 Series

SBC 5000 Series

SBC SWe

EMS

V05.01.00R000

 

V05.01.00R000**

V05.01.00R000**

V10.00.00R000*

* WRTC 01.03.00R002 is explicitly tested with Insight EMS 10.00.00R000 by Sonus with DM build [Insight EMS10.0.0-WRTC1.3.0-DM1.0.0]

** 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

ModeRegionAMI ID
Appliance ModeN.Virginiaami-7f831005.

AWS Appliance Mode Template Changes

Sonus provides a new WRTC-Appliance template for WRTC- Appliance mode of installation in AWS.  The template is ipdated for the region and AMI-ID.

The sample of the WRTC-Appliance template is as follows:

{
  "AWSTemplateFormatVersion" : "2010-09-09",

  "Description" : "Automate creating two WRTC HA nodes in a new VPC that will share a virtual IP address for appliance mode.After successfully launching this CloudFormation stack, you will need to manually create an EIP and attach it to HA Node #1's VIP for external connectivity using the VIP.",

  "Parameters" : {

    "VpcCidr" : {
      "Description" : "CIDR address for the VPC to be created.",
      "Type" : "String",
      "Default" : "10.10.0.0/16"
    },
    "PublicSubnetRange" : {
      "Description" : "Address range for a public subnet to be created in the VPC.",
      "Type" : "String",
      "Default" : "10.10.0.0/24"
    },
    "HANodeInstanceType" : {
      "Description" : "Instance type for HA nodes.",
      "Type" : "String",
      "Default" : "t2.large"
    },
    "HANode1IP" : {
      "Description" : "IP address for the first HA node.",
      "Type" : "String",
      "Default" : "10.10.0.11"
    },
    "HANode2IP" : {
      "Description" : "IP address for the second HA node.",
      "Type" : "String",
      "Default" : "10.10.0.12"
    },
    "VIP" : {
      "Description" : "Private virtual IP address to be swapped between the HA nodes.",
      "Type" : "String",
      "Default" : "10.10.0.10"
    }
  },

  "Mappings" : {
    "AWSInstanceType2Arch" : {
      "t1.small"    : { "Arch" : "64" },
      "t2.large"    : { "Arch" : "64" },
      "m1.medium"   : { "Arch" : "64" },
      "m4.large"    : { "Arch" : "64" },
      "m4.2xlarge"  : { "Arch" : "64" },
      "m2.xlarge"   : { "Arch" : "64" },
      "m2.2xlarge"  : { "Arch" : "64" },
      "m2.4xlarge"  : { "Arch" : "64" },
      "c1.medium"   : { "Arch" : "64" },
      "c1.xlarge"   : { "Arch" : "64" },
      "cc1.4xlarge" : { "Arch" : "64Cluster" },
      "cc2.8xlarge" : { "Arch" : "64Cluster" },
      "cg1.4xlarge" : { "Arch" : "64GPU" }
    },

    "AWSRegionArch2AMI" : {
      "us-east-1"      : { "32" : "ami-7f831005", "64" : "ami-7f831005", "64Cluster" : "ami-7f831005",      "64GPU" : "ami-7f831005" },
      "sa-east-1"      : { "32" : "ami-acc185bb", "64" : "ami-90434787", "64Cluster" : "NOT_YET_SUPPORTED", "64GPU" : "NOT_YET_SUPPORTED" }
    }

  },

  "Resources" : {

    "VIPRole": {
       "Type": "AWS::IAM::Role",
       "Properties": {
          "AssumeRolePolicyDocument": {
             "Statement": [ {
                "Effect": "Allow",
                "Principal": {
                   "Service": [ "ec2.amazonaws.com" ]
                },
                "Action": [ "sts:AssumeRole" ]
             } ]
          },
          "Path": "/",
          "Policies": [ {
             "PolicyName": "VIP_Takeover",
             "PolicyDocument": {
                "Statement": [ {
                   "Effect": "Allow",
                   "Action": [
                        "ec2:AssignPrivateIpAddresses",
                        "ec2:DescribeInstances"
                   ],
                   "Resource": "*"
                } ]
             }
             } ]
          }
    },

    "VIPRoleProfile": {
       "Type": "AWS::IAM::InstanceProfile",
       "Properties": {
          "Path": "/",
          "Roles": [ {
             "Ref": "VIPRole"
          } ]
       }
    },

    "VPC" : {
      "Type" : "AWS::EC2::VPC",
      "Properties" : {
        "CidrBlock" : { "Ref" : "VpcCidr" },
        "Tags" : [
          { "Key" : "Application", "Value" : { "Ref" : "AWS::StackName" } },
          { "Key" : "Network", "Value" : "Public" }
        ]
      }
    },

    "PublicSubnet" : {
      "Type" : "AWS::EC2::Subnet",
      "Properties" : {
        "VpcId" : { "Ref" : "VPC" },
        "CidrBlock" : { "Ref" : "PublicSubnetRange" },
        "Tags" : [
          { "Key" : "Application", "Value" : { "Ref" : "AWS::StackName" } },
          { "Key" : "Network", "Value" : "Public" }
        ]
      }
    },

    "InternetGateway" : {
      "Type" : "AWS::EC2::InternetGateway",
      "Properties" : {
        "Tags" : [
          { "Key" : "Application", "Value" : { "Ref" : "AWS::StackName" } },
          { "Key" : "Network", "Value" : "Public" }
        ]
      }
    },

    "GatewayToInternet" : {
       "Type" : "AWS::EC2::VPCGatewayAttachment",
       "Properties" : {
         "VpcId" : { "Ref" : "VPC" },
         "InternetGatewayId" : { "Ref" : "InternetGateway" }
       }
    },

    "PublicRouteTable" : {
      "Type" : "AWS::EC2::RouteTable",
      "Properties" : {
        "VpcId" : { "Ref" : "VPC" },
        "Tags" : [
          { "Key" : "Application", "Value" : { "Ref" : "AWS::StackName" } },
          { "Key" : "Network", "Value" : "Public" }
        ]
      }
    },

    "PublicRoute" : {
      "Type" : "AWS::EC2::Route",
      "Properties" : {
        "RouteTableId" : { "Ref" : "PublicRouteTable" },
        "DestinationCidrBlock" : "0.0.0.0/0",
        "GatewayId" : { "Ref" : "InternetGateway" }
      }
    },

    "PublicSubnetRouteTableAssociation" : {
      "Type" : "AWS::EC2::SubnetRouteTableAssociation",
      "Properties" : {
        "SubnetId" : { "Ref" : "PublicSubnet" },
        "RouteTableId" : { "Ref" : "PublicRouteTable" }
      }
    },

    "HANode1EIP" : {
      "Type" : "AWS::EC2::EIP",
      "Properties" : {
        "Domain" : "vpc",
        "InstanceId" : { "Ref" : "HANode1" }
      }
    },

    "HANode2EIP" : {
      "Type" : "AWS::EC2::EIP",
      "Properties" : {
        "Domain" : "vpc",
        "InstanceId" : { "Ref" : "HANode2" }
      }
    },

    "HANode1" : {
      "Type" : "AWS::EC2::Instance",
      "Metadata" : {
        "Comment1" : "Create HA Node #1"
      },
      "Properties" : {
        "InstanceType" : { "Ref" : "HANodeInstanceType" } ,
        "IamInstanceProfile" : { "Ref" : "VIPRoleProfile" },
        "SubnetId" : { "Ref" : "PublicSubnet" },
        "SourceDestCheck" : "true",
        "PrivateIpAddress" : { "Ref" : "HANode1IP" },
        "ImageId"        : { "Fn::FindInMap" : [ "AWSRegionArch2AMI", { "Ref" : "AWS::Region" }, { "Fn::FindInMap" : [ "AWSInstanceType2Arch", { "Ref" : "HANodeInstanceType" }, "Arch" ] } ] },
        "SecurityGroupIds" : [{ "Ref" : "HANodeSecurityGroup" }],
        "Tags" : [
          { "Key" : "Name", "Value" : "HA Node #1" }
        ],
        
      "UserData" : { "Fn::Base64" : { "Fn::Join" : [ "", [
                "#cloud-config\n",
                "write_files:\n",
                "-   content: |\n",
                "     {\n",
                "         \"", "Role",                   "\" : \"", "Active",          "\",\n",
                "         \"", "Region",                 "\" : \"", { "Ref" : "AWS::Region" },
                                                                                       "\",\n",
                "         \"", "EmsUsername",            "\" : \"", "restuser",        "\",\n",
                "         \"", "EmsIP",                  "\" : \"", "0.0.0.0",         "\",\n",
                "         \"", "EmsPassword",            "\" : \"", "sonus123",        "\",\n",
                "         \"", "EmsPrivateNodeParameters", "\" : {\n",
                "                  \"", "vnfc_id",         "\" : \"", "appliance",     "\",\n",
                "                  \"", "cluster_id",      "\" : \"", "appliance",     "\",\n",
                "                  \"", "data_ip_address", "\" : \"", "0.0.0.0",       "\"\n",
                "                },\n",
                "         \"", "Interface1",             "\" : \"", "eth0",            "\",\n",
                "         \"", "Interface1Usage1",       "\" : \"", "SIP",             "\",\n",
                "         \"", "Interface1Usage2",       "\" : \"", "HTTP",            "\",\n",
                "         \"", "Interface1Usage3",       "\" : \"", "WebSocket",       "\",\n",
                "         \"", "VIP0", "\" : {\n",
                "                  \"", "IFNAME",        "\" : \"", "IF0",             "\",\n",
                "                  \"", "IP",            "\" : \"", { "Ref" : "VIP" }, "\"\n",
                "              },\n",
                "         \"", "VirtualInterfaceIP",     "\" : \"", { "Ref" : "VIP" }, "\",\n",
                "         \"", "PeerWRTCAddress",        "\" : \"", { "Ref" : "HANode2IP" }, 
                                                                                       "\",\n",
                "         \"", "EmsRegistrationId",      "\" : \"", "WRTC",            "\",\n",
                "         \"", "RestUserName",           "\" : \"", "restuser",        "\",\n",
                "         \"", "RestPassword",           "\" : \"", "sonus",           "\"\n",
                "     }\n",
                "    path: /opt/sonus/userData.json\n"
          ]] }}
      }
    },

    "HANode2" : {
      "Type" : "AWS::EC2::Instance",
      "Metadata" : {
        "Comment1" : "Create HA Node #2"
      },
      "Properties" : {
        "InstanceType" : { "Ref" : "HANodeInstanceType" } ,
        "IamInstanceProfile" : { "Ref" : "VIPRoleProfile" },
        "SubnetId" : { "Ref" : "PublicSubnet" },
        "PrivateIpAddress" : { "Ref" : "HANode2IP" },
        "SourceDestCheck" : "true",
        "ImageId"        : { "Fn::FindInMap" : [ "AWSRegionArch2AMI", { "Ref" : "AWS::Region" }, { "Fn::FindInMap" : [ "AWSInstanceType2Arch", { "Ref" : "HANodeInstanceType" }, "Arch" ] } ] },
        "SecurityGroupIds" : [{ "Ref" : "HANodeSecurityGroup" }],
        "Tags" : [
          { "Key" : "Name", "Value" : "HA Node #2" }
        ],

            "UserData" : { "Fn::Base64" : { "Fn::Join" : [ "", [
                "#cloud-config\n",
                "write_files:\n",
                "-   content: |\n",
                "     {\n",
                "         \"", "Role",                   "\" : \"", "Standby",         "\",\n",
                "         \"", "Region",                 "\" : \"", { "Ref" : "AWS::Region" },
                                                                                       "\",\n",
                "         \"", "EmsUsername",            "\" : \"", "restuser",        "\",\n",
                "         \"", "EmsIP",                  "\" : \"", "0.0.0.0",         "\",\n",
                "         \"", "EmsPassword",            "\" : \"", "sonus123",        "\",\n",
                "         \"", "EmsPrivateNodeParameters", "\" : {\n",
                "                  \"", "vnfc_id",         "\" : \"", "appliance",     "\",\n",
                "                  \"", "cluster_id",      "\" : \"", "appliance",     "\",\n",
                "                  \"", "data_ip_address", "\" : \"", "0.0.0.0",       "\"\n",
                "                },\n",
                "         \"", "Interface1",             "\" : \"", "eth0",            "\",\n",
                "         \"", "Interface1Usage1",       "\" : \"", "SIP",             "\",\n",
                "         \"", "Interface1Usage2",       "\" : \"", "HTTP",            "\",\n",
                "         \"", "Interface1Usage3",       "\" : \"", "WebSocket",       "\",\n",
                "         \"", "VIP0", "\" : {\n",
                "                  \"", "IFNAME",        "\" : \"", "IF0",             "\",\n",
                "                  \"", "IP",            "\" : \"", { "Ref" : "VIP" }, "\"\n",
                "              },\n",
                "         \"", "VirtualInterfaceIP",     "\" : \"", { "Ref" : "VIP" }, "\",\n",
                "         \"", "PeerWRTCAddress",        "\" : \"", { "Ref" : "HANode1IP" }, 
                                                                                       "\",\n",
                "         \"", "EmsRegistrationId",      "\" : \"", "WRTC",            "\",\n",
                "         \"", "RestUserName",           "\" : \"", "restuser",        "\",\n",
                "         \"", "RestPassword",           "\" : \"", "sonus",           "\"\n",
                "     }\n",
                "    path: /opt/sonus/userData.json\n"
          ]] }}
      }
    },

    "HANodeSecurityGroup" : {
      "Type" : "AWS::EC2::SecurityGroup",
      "Properties" : {
        "GroupDescription" : "Rules for allowing access to HA Nodes",
        "VpcId" : { "Ref" : "VPC" },
        "SecurityGroupIngress" : [
           { "IpProtocol" : "tcp", "FromPort" : "80",  "ToPort" : "9090",  "CidrIp" : "0.0.0.0/0" } ,
           { "IpProtocol" : "tcp", "FromPort" : "22",  "ToPort" : "2024",  "CidrIp" : "0.0.0.0/0" } ],
        "SecurityGroupEgress" : [
           { "IpProtocol" : "-1", "FromPort" : "443", "ToPort" : "9080", "CidrIp" : "0.0.0.0/0" } ]
      }
    },

    "HANodesAllowICMP" : {
      "Type" : "AWS::EC2::SecurityGroupIngress",
      "Properties" : {
        "GroupId" : { "Ref" : "HANodeSecurityGroup" },
        "IpProtocol" : "icmp",
        "FromPort" : "-1",
        "ToPort" : "-1",
        "SourceSecurityGroupId" : { "Ref" : "HANodeSecurityGroup" }
      }
    }
  },

  "Outputs" : {
    "HANode1URL" : {
      "Description" : "URL for accessing the WRTC web application.",
      "Value" :  { "Fn::Join" : [ "", [ "https://", { "Ref" : "HANode1EIP" },":8081" ]] }
    },
    "HANode2URL" : {
      "Description" : "URL for accessing the WRTC web application.",
      "Value" :  { "Fn::Join" : [ "", [ "https://", { "Ref" : "HANode2EIP"},":8081" ]] }
    }
  }
}

For more information, refer to Install WebRTC in Appliance Mode and Appliance Mode Template File.

WRTC Compatible Browsers

WRTC SDK is explicitly tested on:

Table : WRTC Compatible Browsers

BrowserVersion

Chrome

60.0.3112.101
Mozilla Firefox54.0.1
Opera42
IE11

WRTC SDK is also expected to work on higher browser versions listed above.

Sonus WebRTC Installation Notes

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

WRTC EMA Login Credentials

To log on to WRTC EMA GUI, you must use the following credentials:

  • Username - admin
  • Password - $0nus123

Sonus API Update

The following new API RTCPMux is added in Initializing WRTC SDK section:

sonus.updateConfig("RTCPMux",value);

Table : API Parameter Description

ParameterDescription
RTCPMux

This is a boolean variable.

  • true - rtcpMuxPolicy is set to "require" in RTCPeerConnection object.
  • false - rtcpMuxPolicy is set to "negotiate" in RTCPeerConnection object.

This feature is tested with SBC 6.1R001 version and above.


Issues Resolved

This section lists resolved customer issues reported in WRTC 01.03.00R002 release.

Table : Issues Resolved

IssueType/CategoryDescriptionResolution
WSX-3844BugWebRTC Gateway in a non-redundant state with High Availability (HA) gateway showing Active/Active mode.

When the active WRTC is started, the AWS infrastructure takes some time (1 - 4 minutes) to report the active usage of VIP to standby WRTC, as its in process of re-associating the public IP for this VIP.

If the standby WRTC is started before this IP association/re-association, then both the WRTC will be in Active-Active state. AWS need to re-plumb the VIP(10.10.0.10) and then re-associate the public IP to this VIP.

Since, the IP plumb/association is AWS infrastructure driven, its not recommended to use WRTC console for start/stop in AWS. Instead switchover the WRTC through AWS dashboard, when the VIP/re-association of public IP is complete and stable.

WSX-3843Bug

WebRTC gateway file operations are failing.

The file operations failed as the JSON files were cleared. The issue is resolved such that the WRTC application populates such empty files with NULL JSON body {}.
WSX-3842BugThe SIP logging fills up the disk space.The issue was due to JAIN SIP log level set to DEBUG level. The code is modified such that the JAIN SIP stack log level is now set to ERROR level.
WSX-3841BugThe /var/log/lsyncd/lsyncd.log file filling up the disk.

The logging level of lsyncd is set to ERROR by using the following command:

lsyncd -log scarce /etc/lsyncd/lsyncd.conf.lua

 

This command is invoked once the lsyncd is restarted.
WSX-3815Bug

The log rotation and compression adds the null/junk characters to wrtc.log

The issue was due to rollover script that edits the log file when the WRTC application is in process of updating the same file. This code is fixed  by modifying the handling of file rollover logic.
WSX-3852BugWebRTC gateways achieved maximum CPU load when more traffic was moved to the systems.

The high CPU issue was due to recursive read and write operation on the profile files during login. The code is fixed by refining the logic to avoid such recursive read/write operation.

Sonus recommends to upgrade the SDK to latest 1.3 version along with WRTC Gateway 1.3R002 for better CPU performance.


This section lists resolved customer issues reported in previous releases.

Table : Issues Resolved

IssueType/CategoryDescriptionResolution
WSX-3434Bug200 OK for login is not sent back to SDK if the assigned number is carrying the country code.The code has been modified to rectify an application error when the country code was attached in assigned number.
WSX-3548BugMemory leak issues found in production network.The code has been modified to resolve the memory leak issues during the error handling cases.
WSX-3606BugEvery time a new CDR file is generated for each record after the first files reaches the maximum file limit.The code has been modified to resolve the error in calculation of maximum file size.
WSX-3762BugRtcpMux support in WRTC SDK.RtcpMux parameter is added in the config object based on which it is set to require or negotiate in the peer connection object.
WSX-3829BugImplementing logout feature in WRTC EMA.The logout feature has been implemented to resolve the issue.
WSX-3831Bugwrtclogging.properties file is packaged in DOS format by mistake.The control characters are removed from the file to resolve the issue.
WSX-3833BugPorting of WRTC 2.0 EMA features like user management.The password change has been implemented to resolve the issue.

Known Issues

This section describes the known issues in this release.

Table : Known Issues

Issue IDCategoryProblem DescriptionSeverityImpact/Workaround
WSX-749ApplicationAdvanced call support in Firefox.3No Workaround
WSX-1378CDR

Incorrect CDRs are generated when the conference invite is in ringing state.

3Rename conference CDR's to "Conference Initiated" instead of "Conference Created".
WSX-1448ApplicationFile share request issue when group chat is upgraded to conference.2No Workaround
WSX-1563ApplicationUnable to add two parties simultaneously in a P2P Conference.3No Workaround

WSX-1721

HAAuto retrieval issue for three users in three node HA.2No Workaround
WSX-1720HAThree node HA issue for desktop request getting cleared after switchover, and unable to perform modality changes.2No Workaround
WSX-2107HAUnable to perform device transfer while switchover is going on in a WSX HA setup.3No Workaround
WSX-2706ApplicationNumber is assigned for users even when number profile is not attached to enterprise.2No Workaround

Known Limitations

Following are the known limitations in this release:

SIP Inter-working Limitations

  • SIP Listener only listens to one port per transport type.

  • Late Media is not supported.

  • Support for SIP modality is only using REINVITE and not UPDATE.

  • Upgrade from audio call to video call fails.

  • Video call and hold from browser does not work as expected.

  • Modalities fail in Firefox web browser, only audio and video calls, and mute and unmute features work in Firefox-to-SIP and SIP-to-Firefox communications.

P2P Conference

  • During a conference call, only one user can initiate conference call hold and retrieve.

  • Conference with SIP users is not support.

  • Simultaneous file transfer is not supported.

Group Chat

  • Group chat with SIP users is not supported.
  • Simultaneous file transfer is not supported.

CAC Policy

  • Multiple routes or prefix for the same user is not supported.

Multiple Point of Presence

  • Logout and login to the peer device when hanging sessions appear in drop-down list.
  • Device transfer and device pickup for SIP endpoints is not supported.
  • The policy query is carried out only once per call. If the callee has MPOP with varying enterprise, the CAC policy is applied based on the POP chosen for first ring on the callee enterprise. Consecutive POPs will be rung if required, but no new CAC policy will be applied for different enterprises.

WRTC in Appliance Mode

  • When client SDK delays in detecting a switchover, any signaling from the client within that time frame do not take effect.
  • Call history is not supported.

WRTC EMA

  • EMA stats displays node resource usage interval data at 5 minute interval. Rest of the stats are real time integrated stats.

Browser Media Statistics

  • Collection of call statistics depends on web browsers such as Opera, Firefox, and Chrome. You must decide what to do in case the information is found to be incorrect or missing.
  • WRTC SDK or WRTC Server does not take any action if the media parameters degrade.
  • WRTC does not analyze statistics.
  • Statistics are only collected at the end of each session. Any updates in the middle such as file transfer inside a call, upgrade audio call to video call, and again downgrade to audio may not be captured.
  • Statistics are not provided by server in case of data channel.

Dryup

  • Page refresh is required in case of disconnection with WRTC or load balancer after multiple dry-ups.

Statistics and Trap Related Limitations

  • No statistics is generated for calls from SBC, if the destination number does not match the registered users.
  • In case of switchover, statistics is not shared across the WRTC nodes.

Cluster Configuration

  • Changes to keystore, trustore requires restarting WRTC application.
  • Changes to port configuration requires restarting WRTC application.

EMS Interworking

  • Web Application Policy profile is not used.

Multitenancy

  • Unique number pool across enterprises must be configured.
  • For multiple enterprises with multiple CAC policies, if CAC policies are different then inconsistent behavior is seen in case of multiparty (group chat or conference) scenarios with users from different enterprises.

Firefox

  • RTC based DTMF is not supported in Firefox web browser. Only info based DTMF is supported.
  • Re-offer/answer leads to failure of SetRemoteDescription in Firefox web browser (version 38 and later), with Chrome and SIP endpoints.

Generic SDK UC App

  • The session does not exist when one of the users in a two party call, ends the call before the third user accepts the invite to join the call.
  • When logged through ORTC, upgrading to a video call or downgrading to an audio call has a delay in media streaming by 6-7 seconds.
  • In a group chat if users (A and B) upgrade to audio call and other users (C) upgrades to video, user C will not get the audio. This is because one way audio and other way video upgrade is not supported in icelink V2.
  • Multiple upgrade requests on the same peer connection is not supported.
  • Conference modalities are not supported.
  • Group chat does not support file transfer.
  • In a Web to SIP video call, call retrieval after hold clears the video call.
  • ORTC/IE to SIP calls is not supported.
  • Safari browser is not supported.