Until websocket connection are not established, user can’t start video or audio It keeps saying something like:
on starting video: Camera is loading, Please wait.
on starting audio: Computer audio is loading, Please wait.
Once websocket connection are established, video and audio starts working.
Okay, will check once, But then It should get blocked every time right?
After speaking to @vic.yang , we want to suggest upgrading to Video SDK 1.3.0 which includes an improvement around the data center selection logic. Helps reduce latency and improve in-meeting / session performance. Improvements include geo-fencing and greater prioritization of geographically-close servers.
hey @tommy ,
We still observed this issue in the latest version as well (1.3.0).
Some Additional context:
Whenever this issue occurred it was observed that the user was joining the call for the first time.
After client.join()API is resolved we ask for audio video permission from user using: navigator.mediaDevices.getUserMedia({ audio: true, video: true })
Could you open an individual tab to load the wasm file? We want to determine if this is an issue with our CDN network. Or a temporary workaround, serve these dependent assets on your own servers and specify the asset in the init method.
hey @vic.yang ,
So, do you think serving these dependent assets from own servers will be faster than Zoom-served CDN?
Also just one more thing I forgot to mention that we are currently testing in our private environments with VPN turned on, not sure If this has something to do with it.
It depends on you. Our default setting is using the Zoom-served CDN.
For the sake of some companies having their own assets access policies that prevent the use of external resources, we provide the option to use the privately served assets.
Could you use https://www.speedtest.net/ test your speed? we want know your country. you can mask you ip hidden in the test result screenshot.
we test the source.zoom.us cdn latency can find the issue.
Thanks
Jack