Support & information center

Testing & Monitoring

Analysis

• We’ve updated the ribbot at the top of test results
  • Added performance (CPU and memory use of probes)
  • Added RTT (round trip time)
  • Removed call setup time, now part of the overview section

• Our Advanced WebRTC Analytics on test results now shows metrics also for the selected candidate pair. This allows us to view the bandwidth estimation of WebRTC (availableOutgoingBitrate)

• We’ve added channels start time and duration information, making it easier to analyze results, especially in large tests

• Machine performance graphs are now synchronized to the same timeline and starting point of all other graphs making it easier to compare results
• Uploading a webrtc-internals dump file has a simpler UI now that allows for both drag & drop as well as uploading files

Testing

• We all have our own favorites. Some of us have favorites in the test scripts they wish to run using testRTC. So we’ve enabled you all to pick your favorites 👍👍👍

• Added a new script command .rtcSetCustomExpectation() and .rtcSetCustomEventsExpectation() that can be used if you’d like to add an expectation that conducts a specific calculation that we don’t offer out of the box using .rtcSetTestExpectation()

• Added a new script command .rtcWaitForExternalValue() which works with a newly introduced REST API /testruns/externalValue. Using this enables sending external values into a running test scripts. What can this be used for? Dealing with 2FA requirements that need to glean information from an SMS or an email that is intercepted outside of the test script itself. There are probably other uses for it as well 😉
• Added new run options #probe-screen-width and #probe-screen-height to enable changing the screen resolution. This is useful in screen sharing testing
• Webhooks are now invoked after the test run is fully completed and has been analyzed instead of when the test completed. This was done to prevent a race condition when trying to access metrics results “too soon”

Monitoring

• Added REST API /monitors/{monitorId} to retrieve list of last monitor run id’s
• Added REST API /monitors/{monitorId}/last to retrieve the status of the last monitor run

qualityRTC

qualityRTC invites

qualityRTC now includes a new invite system in the Enterprise plan. This enables the creation of specialized invites for conducting network tests instead of having a single generic link.

The invite system enables you to create special links that are:

• Time limited
• Count limited (the number of times they will “run”)
• Prefilled fields
• Include new custom fields

This can be used to:

• Restrict the use of the network tests without an explicit invite
• Share an invite with a large user base of a specific account/client of yours
• Collect information from specific users (agents of a contact center, asking them about their location for example – WFH or office)
• Provide access to invites to partners

Invites can be created via a new API call as well as directly from the dashboard:

When users use the invite link, the results appear both in the History section in qualityRTC and in the invite page itself for easy access. The results table can also be embedded as an iframe elsewhere programmatically if needed.

Supported infrastructure

We’ve had quite a few clients onboarding our qualityRTC service recently, which got us working hard on additional integrations. Instead of recounting what we’ve added, here’s the list of what we now support out of the box:

You can find more details in our qualityRTC integrations article.

Widgets improvements

• VIDEO BANDWIDTH, VIDEO P2P and VIDEO QUALITY tests now and share in the log the connection type (this will show if connection is via TURN and what transport is used – UDP, TCP or TLS)

• VOICE TEST tests can now be configured to not use the local microphone and generate audio automatically instead. This can increase privacy as well as enable testing using devices that don’t have a microphone connected to them
• TURN CONNECTIVITY widget now offers a simplified UI option available, where the test widget only shows if it has connectivity and with what protocol (prioritizing UDP over TCP and TCP over TLS). All measurements collected still appear in the log for your support team

• TURN CONNECTIVITY widget now supports the ability to conduct tests on separate TURN server deployments. This can be used when you want to compare different TURN servers (such as your own in-house ones versus a managed service one such as XirSys or Twilio)

• DNS LOOKUP now distinguishes between blocked connections to timeout events in the log
• The silent camera test can now optionally check for camera resolutions as well

Miscellaneous improvements

• Multilingual support is now available for the frontend page the end users view. Current languages include: English, French, Spanish, Portuguese. You can learn more here
• Alert emails for qualityRTC now support multiple email addresses that can be alerted at once
• Log access in qualityRTC results can be restricted to the support person, making it unavailable for the end user who executed the test. This is desirable if you want to keep the results as simple as possible for your users
• Our on premise servers for speed testing and TURN now include management interfaces for easier maintenance (this includes heartbeat, metrics collection, logging and high availability configuration).
• You can now embed the frontend UI as an iframe. For this, you can also use ?/embedded=true as a URL parameter to remove the header and footer of the page

probeRTC

You can now access the history results of probeRTC and not just the last run. At the end of the probe’s results page, there’s now a HISTORY button you can click to access a new detailed table:

Printing results of probeRTC was impossible. This got fixed.

watchRTC

A slew of improvements were added to watchRTC, and we are now ready for launch it to the general public – still as beta, but not private anymore. If you’d like to join – let us know.

Things we’ve done:

• Added a new highlights dashboard, sharing high level information about the recent runs. This can be filtered by dates as well as by tags

• Included unsuccessful connections to peer tables
• Polished results view