Skip to content

example of using hardware devices between calling sessions

License

Notifications You must be signed in to change notification settings

alkwa-msft/reuse-calling-devices

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

reuse-calling-devices

An example project to demonstrate how to re-use calling devices from a previous session. This works by storing the device ids for the camera, microphone, camera into local storage.

If there are no elements in local storage we try to use the preferred devices. If we are unable to detect the preferred devices we will use the first item in each enumerated category.

Open questions

  • How come there are is no system default for Cameras?
  • How come there is no way to set a camera like how we can set a speaker or microphone?
  • How come I cant find a specific device?

    Is it in use? It may be locked by another application. Have you allowed permissions for that type of device? Enable permissions for this page and then reload the window

Available Scripts

In the project directory, you can run:

yarn start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

yarn test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

yarn eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

About

example of using hardware devices between calling sessions

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published