Slack Calls are now in beta, on Mac, Windows, iOS, Android and Chrome. If you haven’t given it a try yet, please do (and let us know how it goes)! Our help center article on Calls has more details on the feature. We wanted to answer the age-old question that we have all asked each other…
Overview
The article discusses the implementation of Slack Calls, focusing on how to determine the quality of voice calls through real-time control protocol (RTCP) feedback. It explains the architecture used for group calls and the analysis of upload and download losses to provide users with accurate feedback about their connection quality.
What You'll Learn
How to analyze RTCP Receiver Reports for real-time voice call quality
Why using a Selective Forwarding Unit (SFU) improves group call performance
How to implement accurate UI warnings for call quality issues
Prerequisites & Requirements
- Understanding of real-time communication protocols like RTP and RTCP
- Familiarity with WebRTC and Janus(optional)
Key Questions Answered
How does Slack determine if call quality issues are due to user connections?
What is the role of a Selective Forwarding Unit (SFU) in Slack Calls?
What threshold is used to trigger UI warnings for call quality?
Key Statistics & Figures
Technologies & Tools
Key Actionable Insights
1Implementing accurate feedback mechanisms for call quality can significantly enhance user experience.By providing specific warnings about connection issues rather than generic messages, users can better understand and address their connectivity problems.
2Utilizing SFUs can optimize group call performance by reducing bandwidth usage and improving audio clarity.This architecture allows participants to connect only to the media server, minimizing the impact of individual network issues on the overall call quality.
3Regularly analyze RTCP packets to maintain and improve call quality.Understanding the data within RTCP reports can help identify and rectify issues in real-time, ensuring a smoother communication experience.