So I am building a bot using the meetingsdk-headless-linux-sample. So far it has worked great, running it by using the included compose file, but now I have to build it to an image and host that image on AWS. So I built the image and everything works fine, but then when I run docker run IMAGE it gets stuck in MEETING_STATUS_CONNECTING .
It all works with no issue, and it even joins the meeting, but I am not getting any other events from Zoom after the connecting status change (It should get the in-meeting status after joining). I have also tried to send it messages, which should also get registered, but it still does not work. I should note that I am not getting any errors, there are just no events coming in.
Here are the logs from the startup:
✅ configure
✅ initialize
✅ join a meeting
Meeting Status MEETING_STATUS_CONNECTING
⏳ connecting to the meeting
Now another weird thing is if I end the meeting while the bot is still in it, it actually receives new events. Here are the logs:
Meeting Status MEETING_STATUS_DISCONNECTING
⏳ disconnecting from the meeting
Meeting Status MEETING_STATUS_ENDED
✅ meeting ended
⏳ Meeting End
Here is my full docker run cmd: docker run -d --platform linux/amd64 -v "$(pwd):/tmp/meeting-sdk-linux-sample" -p 80:80 IMAGE
I should note that I have also tried to just run docker run IMAGE and the issue persists.
Hey Noah, if you’re still troubleshooting the issue with the meetingsdk-headless-linux-sample getting stuck in MEETING_STATUS_CONNECTING when running via the docker run command, you might want to check out the Recall.ai API.
It’s a simple 3rd party API that lets you use meeting bots to get raw audio/video/metadata from meetings without you needing to spend months to build, scale, and maintain these bots.
I’m building an open source API that simplifies working with Zoom bots, similar to Recall. You can run the API on your local machine or use the hosted instance.
Checkout the project here: GitHub - noah-duncan/attendee: Meeting Bots made easy
It’s still in the early stages, but adding new functionality every day. If some feature is missing just open an issue in the github repo.
Hey Amanda, I took a look at your company a couple of months ago and even had a meeting with you. But sadly your offer is way too expensive for my client, so I have had to build it myself : D
Yes there’s a Dockerfile in the github repo that’s been deployed to Github Actions and Heroku.
There’s actually two different projects I have: Python wrapper for the Zoom Meeting SDK - It’s a python package that you call with python code. It only does what the Meeting SDK does, so you’re responsible for things like storing meeting transcripts and managing the state and compute for the bots.
Meeting bot API - This is an API service you can call from any language. You interact with it through a high-level REST API. It handles things like storing the transcripts and managing the bot compute. Under the hood, the API service is using the Python SDK wrapper.
My first post linked you to the SDK, but the API could be more suitable for your needs.
If you’d like to talk more about what you’re working on and see if the SDK or API could help, then feel free to book a meeting here: Calendly - Noah Duncan
@chunsiong.zoom Just letting you know that this issue persists. It has even started to also happen when I run it with docker compose up. I am using an old version of the SDK, not sure if that could be the issue?
@chunsiong.zoom Not sure, the entire thing is built on Docker, so I am not even sure I can run it without it. I am building off of the headless linux sample.