Skip to main content

testRTC April 2023 Release Notes

Breaking change in testingRTC/upRTC

Note that rtcEvent() now expects 2 parameters at all times.

Up until recently, if you passed a single parameter, rtcEvent() assumed a “global” event type. A decision was made to make the event type explicit and not assume anything for the user.

If you are using the rtcEvent() function, please be sure to check if you need to update your test script accordingly.


  • When the incoming RTT metric is reported on RTCP, we now collect, analyze and display it on charts
  • Additions to the event log:
    • We now provide the track label (=device) when logging addTrack, addTransceiver and replaceTrack events
    • Added track.onended event to log the track state. The event log will display both live/ended track state as per context
    • Added log for muted property on track along with event listeners for unmute/mute events

qualityRTC & probeRTC

  • We’ve added a popup telling the user to allow access to the microphone (and camera where applicable) if we understand that the browser will make sure a request
  • TURN CONNECTIVITY and VIDEO P2P test widgets can now run silently and log the information without showing the widget itself
  • DEVICE STATE test widget will now also show the media path (region) the call used, where applicable
  • Video related tests now also report in the logs frames per second and quality limitation metrics
  • In probeRTC, you can now provide an end date. Once reached, the probe will become inactive automatically
  • probeRTC now has a flexible date picker to choose viewing range



We have new video resolution graphs. These will indicate which send/rect resolutions are most “popular” and used in your application:

Persistent connections

We’ve added support for persistent connections.

If you are running a contact center, you might be using such a feature where a single WebRTC peer connection is used to connect the agent to the server, and then all calls flow through that connection.

In order to distinguish between these calls in watchRTC, you can now use new SDK APIs to tell watchRTC where to start and stop your calls – since they are now application specific and don’t show in WebRTC traffic.

You can read more about persistent connections in watchRTC.


  • mapStream() is now deprecated, replaced with mapTrack()
  • We’ve introduced an onstatechange callback to JavaScript SDK. This will enable the application to know and understand when the SDK is connected or disconnected from the watchRTC server
  • For our iOS SDK, we’ve removed all external dependencies and shrunk the binary size considerably

Here and there

  • Data streams in watchRTC now include MOS, score values on the receive and send stream levels and not only at the peer level. We’ve also added audio and video device values on the peer level

Was this article helpful?

0 out of 0 found this helpful