You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all,
We are getting reports that echo has been getting worse with participants on speakers in recent weeks.
Is anyone else noticing this? Do you have any suggestions on what we can do about it? Was there any update on Twilio's backend side that could lead to that?
Most of our meetings happen in the media region de1.
Context:
We are not using noise cancellation so far, and we did not have a problem with echo before. We stopped using the noise cancellation functionality because it led to meeting quality degradation in many meetings (due to high CPU usage).
The text was updated successfully, but these errors were encountered:
Hi all,
We are getting reports that echo has been getting worse with participants on speakers in recent weeks.
Is anyone else noticing this? Do you have any suggestions on what we can do about it? Was there any update on Twilio's backend side that could lead to that?
Most of our meetings happen in the media region de1.
Context:
We are not using noise cancellation so far, and we did not have a problem with echo before. We stopped using the noise cancellation functionality because it led to meeting quality degradation in many meetings (due to high CPU usage).
The text was updated successfully, but these errors were encountered: