August 31, 2020

Changelog #004

Video call with 12 cameras on A video call with 12 cameras on.

We're back after some well-deserved time off!  ☀️😎☀️  The last few weeks have been focused on call scaling, stability and behind-the-scenes work in preparation for bigger features that we'll soon be sharing.

Most importantly, we've doubled the number of tracks that can be subscribed to in a call, so you can now have up to 200 people with 6 cameras and mics on at once, or 100 people in a call with 12 cameras and mics on, or 50 people in a call with 24 cameras and mics on. We can also increase these limits on a case-by-case basis, so please let us know if you have a use case that requires larger session sizes.


Last Changelog we launched API logs in the dashboard:

Since then, we've clarified how the dashboard records successful GET requests. The Response body now reads, "Response bodies are not saved...." We also continued working on internal backend code improvements related to API logs.


  • Revamped the breadcrumb navigation to make it easier to navigate through sections with multiple levels
  • Added a custom 404 page that provides helpful steps to recover from an unfound page
  • Fixed an issue where unsupported recording files were displaying on the Recordings tab
  • Improved page loading speeds by streamlining the resources that are used

Core call experience

  • Improved switching from p2p to SFU
  • Device selections now persist across sessions for calls in iframe mode
  • Improved https detection for pre-built UI
  • Fixed Firefox Android issue that prompted call participants to allow cam and mic permissions multiple times
  • Fixed delay for participants who join a call with both their audio and video muted
  • Shipped infrastructure improvements to strengthen call reliability
  • Fixed reconnect issues when in WebSocket signalling mode
  • Fixed screenshare recordings in customLayout mode

New blog posts