# Understanding common issues with Amazon Chime SDK meetings Understanding common issues The following sections provide troubleshooting methods for common meeting issues. **Topics** + [ ## Connectivity issues ](#connectivity-issues) + [ ## Audio and video quality issues ](#a-v-quality) + [ # Verifying SDK quotas and API throttling for Amazon Chime SDK meetings ](quotas-throttling.md) + [ # Opening support cases for Amazon Chime SDK meetings ](open-support-cases.md) ## Connectivity issues Connectivity issues For connectivity issues, see [Verifying network access](self-troubleshooting.md#net-acess). ## Audio and video quality issues Audio and video quality issues Audio and video quality issues can have several causes. Two main reasons for sub optimal audio/video quality are network bandwidth, and device performance. For detailed information on different challenges and how these impact audio/video quality, see [Quality, Bandwidth, and Connectivity](https://aws.github.io/amazon-chime-sdk-js/modules/qualitybandwidth_connectivity.html) on *GitHub*. This article describes different events and metrics that can be monitored to detect bandwidth issues and potential mitigations. You can choose a Media Region that is closer to the audience of the target meeting session. To understand how to choose an optimal media region, see Using meeting Regions (https://docs.aws.amazon.com/chime-sdk/latest/dg/chime-sdk-meetings-regions.html). Depending on the bandwidth available for a meeting attendee, the Amazon Chime SDK adjusts the video quality of the video being received/uploaded. To understand how you can control the video quality for different video layouts, visit Managing Video Quality for different Video Layouts (https://aws.github.io/amazon-chime-sdk-js/modules/videolayout.html). This article describes video lifecycle management and uplink/downlink policies. **Video resolution considerations** + Default resolution for uploading video is 540p and 15fps at 1400 kbps. Depending on bandwidth, you can reduce that resolution and frame rate. + Based on receiver bandwidth available, determine how many video tiles to show. Don’t overshoot 6Mbps for all video tiles and content sharing. End users see black video tiles when they don't have enough bandwidth. **Using video uplink and downlink bandwidth policies** The Amazon Chime SDK provides the following bandwidth policies. + NScaleVideoUplinkBandwidthPolicy – Implements capture and encoding parameters that nearly equal those used by the desktop, web, and mobile clients. + AllHighestVideoBandwidthPolicy – Always subscribes to the highest quality video stream. + NoVideoDownlinkBandwidthPolicy – Disables video when bandwidth drops below a given threshold. + VideoPriorityBasedPolicy – Prioritizes audio over video in cases of low bandwidth. + VideoAdaptiveProbePolicy # Verifying SDK quotas and API throttling for Amazon Chime SDK meetings Verifying SDK quotas and API throttling The [Amazon Chime SDK endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/chime-sdk.html) page lists the service quotas, API rates, and whether you can adjust them. Use the [AWS Console Service Quota](https://console.aws.amazon.com/servicequotas/home/services/chime/quotas) page to request quota adjustments. **Fine tuning your API rates** Applications that exceed their API rates receive HTTP Status Code 429 and `ThrottledClientException` messages. You can adjust your API rates, but before you do, check your application for bugs that may exhaust those rates. For example, you may create meetings in a loop, or create meetings and not clean up. Depending on how you create meetings, you might need to modify your code. For example, you can replace `CreateMeeting` and `CreateAttendee` with: + [https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_meeting-chime_CreateMeetingWithAttendees.html](https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_meeting-chime_CreateMeetingWithAttendees.html) – Creates up to 10 attendees per meeting. + [https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_meeting-chime_BatchCreateAttendee.html](https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_meeting-chime_BatchCreateAttendee.html) – Creates up to 100 attendees per meeting. You can store created attendees in a database, pull attendee information as invitees join the meeting, and then associate them with the pre-created attendees. # Opening support cases for Amazon Chime SDK meetings Opening support cases If you have more questions, or require support for your business, you can reach out to [AWS Customer support](https://pages.awscloud.com/GLOBAL-aware-GC-Amazon-Chime-SDK-2020-reg.html). For more information about our support plans, see the [Compare support plans](https://aws.amazon.com/premiumsupport/plans/?nc=sn) page. When creating a support case, always open it under the account that has the problem. Include console browser logs, meeting and attendee IDs, and any related support cases or GitHub issues.