Symptom
In a Vonage Video API session over the Chrome browser on Mac devices, participants receive no audio from Chrome clients, with no logs or errors being generated. The publisher is able to attain microphone access, but the browser does not receive callbacks with audio data.
Applies To
- Chrome
- OS X (Mac)
- Video API
- Audio Quality
Resolution
- Ensure you are on the latest version of Chrome.
- Ensure you are using the latest Video API version.
- Restart your browser.
Cause
This was due to a bug specific to Chrome, hat caused audio bitrate during a session to fall to zero. This bug has been resolved. Within the Video API itself, we have exposed functionality that can be used to detect when this error occurs.
Articles in this section
- Checklist for when cycleVideo is not working in JavaScript
- Why Is My Video Camera Displaying a 4:3 Aspect Ratio Instead of 16:9 When Publishing in HD OR FHD resolution (1280x720)?
- How to use Completion handler for Exception Handling
- Firefox Pre-call test not supported
- Error Creating Session Using Vonage Video API .NET SDK
- Unable to Create Session Even Though API Key and Secret Are Valid
- HTTP 415 Error When Archiving Video Session
- Troubleshooting Invalid JWT When Creating a Video Session using REST API
- Camara Still in Use after Session Disconnect on Android
- Token Shows as Invalid