The necessary patches have been successfully applied. For customers impacted by this issue and who had previously disabled the OPUS codec, it is now considered safe to re-enable it in the Ringotel connection settings at your discretion.
We are grateful for your patience and cooperation during this time. If you have any inquiries or require further assistance, please do not hesitate to contact us at support@ringotel.co.
Posted Oct 03, 2024 - 11:46 UTC
Identified
The team has pinpointed the root cause of the call quality issues occurring when enabling the OPUS audio codec in the connection settings. They are currently implementing patches to resolve this issue.
Upon investigation, it was discovered that the problem stemmed from the "maxptime" parameter utilized in the 'fmtp' attribute of an SDP packet. This led certain PBX systems to misinterpret media descriptions, leading to audio quality problems such as one-way audio, choppy sounds, or robotic voices.
No further action is required from your side until further notice. We sincerely thank you for your patience and collaboration during our investigative process. We apologize for any inconvenience this may have caused.
Posted Oct 02, 2024 - 10:46 UTC
Investigating
Our team is investigating the cause of the call quality issues that occur when the OPUS audio codec is enabled in the Ringotel connection settings.
Affected services: Inbound and outbound calls made through connections where OPUS codec is enabled.
Temporary solution: Disable OPUS audio codec in the Ringotel connection settings.
Posted Oct 01, 2024 - 21:20 UTC
This incident affected: Regions (Asia Pacific (Singapore), Australia, Europe (Dublin), Europe (Frankfurt), Europe (London), US East, US West, India (Mumbai)).