Skip to main content
  1. testRTC
  2. General
  3. Release Notes

24.11 Release Notes

Release Date: 26th November 2024



watchRTC

In this release, watchRTC has some exciting new additions:

Rearranging Highlights and Trends: We’ve rearranged the Highlights and Trends dashboards a bit, moving some of the charts back and forth between these two pages.

Why? To make it easier for you to review and analyze the charts.

Score and MOS are now front and center in the Highlights dashboard. Browsers, operating systems and browser charts have also found a new home here.

In Trends, we’ve put Insight charts right at the top, so you can focus on what’s important in your deployment. Just below them, you will find Rooms and Concurrency charts – to put context into the Insights charts while at it.

History - Peers and Rooms: Until today, the History table in watchRTC only displayed rooms, with each row representing a room. While useful, this made identifying issues with specific peers within rooms more tedious.
  1. Now, we’ve added a Peers table, where each row represents a peer from a room. For example, if a room has 3 peers, you’ll see 3 separate rows.
  2. You can now also filter by browser and OS, which is useful when you want to view all users with a specific OS and browser combination.
  3. You can switch your view between peers and rooms, and testRTC will remember your last selection, displaying it the next time you access History. A convenient button in the top-right corner of the page allows you to switch views.


SDK Improvements: We now detect media device changes and add it to the event log view

Here and there:
  • We’ve improved how insights are displayed and managed, making them easier to navigate and understand.
  • You can now easily copy peer names and room names in both room and peer views.
  • On the backend, we’re upgrading our databases, which will enable some exciting new features in future releases—stay tuned!

Analysis

New insights: As we continue our journey towards better root cause analysis and making sure you spend LESS time looking at our dashboard to find issues and MORE time solving these issues, we are working on ever more complex insights that are being added. To that end we’ve introduced 8 new insights.
  1. Status 30100 - User changed location or ISP since last run
  2. Status 60015 - Microphone/camera not supported
  3. Status 60100 - User switched microphone since last run
  4. Status 60101 - User switched camera since last run
  5. Status 2030 - Microphone/camera not supported
  6. Status 3500 - Call failed to connect
  7. Status 4003 - No media for an hour or more
  8. Status 4220 - Last minute media quality deterioration

qualityRTC & probeRTC

In this round, we're introducing customization capabilities for Insights:

  • You can now reach out to support to change the status of specific insights you see (ignore, warning, error or information)
  • For qualityRTC customers, there is the option of changing the knowledge base article link, making white labeling possible for insights
  • Some of the new insights now can be customized for certain threshold and configuration parameters. More on that can be found in the documentation of the insights themselves
Here and there:
  • We've added a knowledge base article about the new NETWORK SCORE, with a link from the UI, so users can better understand it.
  • When the network test is run and the user doesn't have the CompanionRTC extension installed, they will be prompted to install the extension via a pop-up. A 'Skip' option is now available for users running network tests without the CompanionRTC extension installed.

  • We’ve also published best practices articles for using qualityRTC and probeRTC—be sure to check them out!

testingRTC

We’re enhancing our infrastructure for large tests, and working with closed labs. Due to some of these changes, tests will now start faster. To achieve this we the process by running tasks in parallel rather than sequentially.

Was this article helpful?

0 out of 0 found this helpful