Acquiring Local Media

---

Application Domain

BlueJeans Web Client SDK relies on getUserMedia to acquire local media. Ensure your application is running either on localhost or an https.

Note:

Web Client SDK makes use of WebRTC APIs exposed by the browsers to get streams from Camera and Microphone. Due to security concerns, most browsers do not expose the WebRTC APIs in http page. We recommend you use https while developing locally as well. Most modern build tools like webpack (through webpack dev server) support https out of the box.

Auto-play Policy

Auto-play policy does not allow you to automatically play audio using <audio> or <video> elements unless the users have interacted with the application (Clicking on auto-play button) especially if your application’s media engagement score is not high enough. So, we recommend using Web Client SDK only after the user has interacted with your application.

Chrome 66+, Firefox 66+ and Safari 11+ all enforce the auto-play policy

Background Application in Mobile Browsers

When you are running the application on a mobile browser in background, the application does not have access to the video feed from the camera until it is foregrounded.

In the back-grounded state, to avoid confusion for other participants with the black video frames, Web Client SDK turns off your video. Your videos will be turned on when you are foregrounded again.

Handling the Page Unloads

When a participant closes the tab/browser or wishes to navigate to another tab in the same browser, the other participants get a notification that the meeting ended.

window.addEventListener('beforeunload', () => 
webClientSDK.meetingService.endMeeting())

It is recommended to end the meeting before you close the tab/browser or navigate to another tab in the browser.