I would recommend enabling any available debug logging to see if there are error codes or warnings that might pinpoint the issue. If not, I would add additional logging around the part of the code where this seems to be getting stuck.
It also helps to double-check that your token is valid (and hasn’t expired) and that the meeting number matches what’s actually scheduled. Lastly, if you’re still having issues, I would double check that these steps have been followed to ensure the demo app works as expected.
It looks like you might be generating and passing the wrong type of token to this bot when it tries to join the call. You’re generating the local recording token which is an optional token that gives the bot additional recording permissions when it’s joining the call.
Instead, you should generate a Meeting SDK JWT and provide that when the bot is joining the call. You can view Zoom’s docs around how to properly create this JWT for more information. When this is provided, your bot should be able to join your Zoom call and properly request recording permissions.
Great to hear this is working for you now @Amol2! For your other 2 questions:
Can we join multiple meetings? Like thread
I found a forum post saying you can have multiple meetings run at the same time but a single instance of the Meeting SDK can only join one meeting at a time per process. Zoom does not officially support joining multiple meetings simultaneously within the same SDK instance (e.g., using threads)
For a single user or bot to participate in multiple meetings at once, Zoom recommends running separate instances of the application, each with its own SDK initialization and valid JWT token, provided your account supports concurrent meetings
Note that with a free account, you’re limited to hosting or joining one meeting at a time. Paid plans like Business or Enterprise allow licensed users to host up to two concurrent meetings, but joining multiple as a participant still requires separate instances
You might be facing an issue with authentication or missing event listeners. Try the following steps to debug and resolve the issue:
Check Authentication Response:
Ensure your JWT token is valid and not expired.
Decode your token using jwt .io to verify expiration (exp field).
If expired, generate a new one.
Enable Debug Logging:
Modify your code to print more logs by adding debug statements before and after SDK initialization functions.
Verify Config File Path & Formatting:
Ensure config.txt is correctly formatted (no extra spaces or special characters).
Absolute file paths can help prevent issues with relative paths.
Check SDK Dependencies:
Run ldd ./meetingSDKDemo to see if any required libraries are missing.
Add Event Listeners for Debugging:
The SDK may not proceed due to missing listeners. Try adding: