Web SDK recommended server specs and setup techniques

Meeting SDK Web
1

Hello @ojus.zoom,

I’ve set up the Web SDK sample on a hosted server. When I connect with 2 people, it works very well. As soon as we add a third, it is extremely slow.

I have the setting active for not using peer-to-peer with 2 people, so it seems like is should be the same regardless of how many people are on.

Do you have recommended specs for the host server?
Are there any setup techniques that would help improve the speed and experience?

2

Also, is there any way to vote for features in the developer roadmap?

I want to give a thumbs up to “Computer Audio for all modern browsers” and specifically for safari (although it has less usage, it is very common for a segment who never use the other browsers).

3

Hi @zeusstl,

What is your network and server speed? The WebSDK should be able to handle 100+ attendees without taking too much memory.

Right now we do not have a way to vote for features on the roadmap. Computer Audio for all browsers is depennt on the browser implementing audio worklet API.

Thanks

4

Thanks @michael_p.zoom!

There was all sorts of lagging occurring when I tried it with 3 people.

  1. I am working with 1GB, 1CPU. It seems like that should be plenty especially when there is basically nothing else running on the server.

  2. The sample says:

notice: the certification signed by localhost. don’t use in your production.
GitHub - zoom/meetingsdk-web-sample: Zoom Meeting SDK web sample

I’m wondering if this could be affecting anything, since it is trying to use a self cert on localhost:9999. I tried setting up an apache reverse proxy, but it doesn’t seem to allow it.

Can you give some advice on where in the code to resolve this, or where to read more about it?

Thanks!

6

Hi @zeusstl,

Please accept our apologies for the delayed response.

We are currently working on your request and will get back to you shortly.

Thanks!

7

@zeusstl if you want to use apache https, you can start zoom demo with http and set enable apache ssl.

apache 2.4 configration

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_http_module modules/mod_proxy_http.so


<VirtualHost localhost:443> 
ServerName localhost 
SSLEngine on 
SSLProxyEngine on 
SSLCertificateFile D:/Zoom/sample-app-web-master/CDN/localhost.crt 
SSLCertificateKeyFile D:/Zoom/sample-app-web-master/CDN/localhost.key
ProxyRequests Off 
<Proxy *>
    Require all granted
</Proxy>
ProxyPass / http://127.0.0.1:9999/ 
ProxyPassReverse / http://127.0.0.1:9999/ 
</VirtualHost>

https://httpd.apache.org/docs/2.4/upgrading.html