Refreshing on remote client kills audio for safari users when using externalIDs

Affects

Dolby Product(s)

• Javascript SDK

Third Party Product(s)

• Safari

Description

When refreshing a page on a remote client, a Safari user will not be able to hear the remote client(s) until the Safari user also refreshes. This only happens when users are reusing their externalID and with dolbyVoice:true

Reproduction Steps

1. Start a conference with one Safari browser user and one user of another browser
2. Join conference using externalID and constraints:  {audio:false, video:false}
3.  Start audio on both users. Audio should work as expected.
4. Refresh the non-Safari browser and start audio. The Safari user will not hear the audio of the other browser but they will be heard by the remote browser.
5. Refresh the Safari browser. Audio will be restored and work correctly in both directions.

Workaround(s)

• None known at this time.

Action Plan

• Wait for Safari update with appropriate fix.

Ticket References

Third Party Reference

• None known at this time.

Dolby Reference

• CC-220