Hi All,
Here are a couple steps that helped others resolve their request timeout issue.
-
Upgrade to a Pro account. That account that using the JWT app credentials within the Web SDK or hosting the meeting needs to be a Pro account as a workaround for this error right now.
-
Use a newly generated scheduled meeting ID instead of using a PMI meeting number.
-
Make sure that the meeting ID is valid and not deleted. One way to test is to try to join via Native client. If you get an invalid meeting ID error, that most likely means that the Meeting ID is invalid or deleted.
-
If you are getting a Generated Signature error. Please make sure that you’re generating a signature properly on your end by
a) Try to run the meeting using the sample web app to verify that your signature and account/meeting info is able to join successfully.
b) If you’re able to join the meeting successfully using the sample web app and you want to generate the signature on the backend, make sure that your systems time syncs with World time - Join meeting timeout or signature expired.