-
Notifications
You must be signed in to change notification settings - Fork 480
Description
What happened and what did you expect to happen?
When users starts the meeting he can't join the meeting because from time to time chime aren't getting this user audio/video devices. In logs there is no errors, just falling voice focus and background blur but it seams right if there is no devices. Permission were allowed for devices.
Have you reviewed our existing documentation?
Reproduction steps
Host starts meeting but gets stuck on Join page
‘Start meeting’ button never appears and instead user sees inactive ‘Starting…’ button which does not become active
Actually meeting is started and others can ask to join however they will newer be accepted since host is not able to get into the meeting
Amazon Chime SDK for JavaScript version
3.17.0
What browsers are you seeing the problem on?
Google chrome
Browser version
109
Meeting and Attendee ID Information.
MeetingId: 856ac9ab-5a3e-411a-9645-4d6c5a4e6404,
ExternalMeetingId: Sensitive Data Redacted,MediaRegion: eu-north-1,MediaPlacement: {AudioHostUrl: c8b0f6051b38f9a61f2df09c9ba464a3.k.m3.en1.app.chime.aws:3478,AudioFallbackUrl: wss://wss.k.m3.en1.app.chime.aws:443/calls/856ac9ab-5a3e-411a-9645-4d6c5a4e6404,SignalingUrl: wss://signal.m3.en1.app.chime.aws/control/856ac9ab-5a3e-411a-9645-4d6c5a4e6404,TurnControlUrl: https://6404.cell.us-west-2.meetings.chime.aws/v2/turn_sessions,ScreenDataUrl: wss://bitpw.m3.en1.app.chime.aws:443/v2/screen/856ac9ab-5a3e-411a-9645-4d6c5a4e6404,ScreenViewingUrl: wss://bitpw.m3.en1.app.chime.aws:443/ws/connect?passcode=null&viewer_uuid=null&X-BitHub-Call-Id=856ac9ab-5a3e-411a-9645-4d6c5a4e6404,ScreenSharingUrl: wss://bitpw.m3.en1.app.chime.aws:443/v2/screen/856ac9ab-5a3e-411a-9645-4d6c5a4e6404,EventIngestionUrl: https://data.svc.uw2.ingest.chime.aws/v1/client-events}
Browser console logs
3log.log
Reproduced logs on Jul 3, 2025