Symptom
When using the Vonage Video API within embedded iFrames on Chrome 64, Chrome requests camera and microphone access.
Applies To
- Chrome 64
- Embedded iFrames
- Permissions
Resolution
If you are using webRTC applications embedded within iFrames that were created prior to the release of Chrome 64, you need to modify these applications to allow access to the camera and microphone by adding this code to your iFrame tag:
allow="microphone; camera"
An embed iFrame will now look like this:
<iframe
src="https://...."
width=640
height=480
allow="microphone; camera"></iframe>
Cause
With Chrome 64, there was a change introduced to force iFrames to explicitly request camera and microphone access. New embeds generated using the Account Portal after the Chrome 64 release are compliant with the change, however embeds in use prior to the release need to be modified.
Articles in this section
- Video API China Relay Service Interruption Status
- How to avoid native session disconnect latency issues with Video API native SDKs?
- Black Video When Screen Sharing over Chrome 50 on Windows 10
- Publisher Video Freezing on Android Chrome 54
- How to Detect Microphone Audio Drop on Chrome
- No Microphone Input Signal on Chrome on Mac
- Can I access Vonage Video API over non-SSL (HTTP)?
- Chrome 64 iFrame Requests Camera and Microphone Access
- Chrome Audio Auto-Play Policy Prevents Audio and Video From Playing
- VOIP/Video traffic disruption in UAE