There is limited support for remembering microphone permissions settings in Chrome, but it is possible.
Here is how you can set it up:
- Use HTTPS to deliver the customer facing HTML for Twilio Client. For example, if you built a browser phone, users would need to visit https://example.com/slick-webrtc-browser-phone rather than http://example.com/slick-webrtc-browser-phone
- Include twilio.js via HTTPS:
This will allow users to click on "Options", in the microphone permission dialog. In this dialog, users should choose "Always allow this site to use this microphone" before placing a call. Once this option is selected, subsequent calls placed by this user will not cause the permissions dialog to appear.
If the Twilio Client HTML is delivered via HTTP rather than HTTPS, users will need to choose "Allow" each time they make a call.