The steps you’re taking sound correct at a high level. But if you’re not getting video, there must be an issue in the source code of your bot.
What we recommend is cross-check your implementation against the Zoom Linux SDK reference code which shows you how to capture the raw video.
Another option is to use Recall.ai . It’s a simple 3rd party API that lets you use meeting bots to get raw audio/video from meetings without you needing to spend months to build, scale and maintain these bots.
Good, I’m tryed using this sample, installed this on Ubuntu 22, but when I start
docker run msdk-5.17.5-on-ubuntu-compact
I have next text
root@server-mmiica:~/Bot/meetingsdk-linux-raw-recording-sample/demo# docker run msdk-5.17.5-on-ubuntu-compact
unix:path=/run/dbus/system_bus_socket,guid=adaefd96ff7dc8d3806adba965c88dc6
Adding user `root' to group `pulse-access' ...
Adding user root to group pulse-access
Done.
Adding user `root' to group `audio' ...
Adding user root to group audio
Done.
cp: target '/root/.config/pulse/' is not a directory
W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
19
mkdir: cannot create directory '/root/.config': File exists
getpath
self path: /app/demo/bin
Readfile success.
Reading..meeting_number: "****************"
Reading..token: "****************"
Reading..meeting_password: ""
Reading..recording_token: "****************"
Reading..GetVideoRawData: "true"
Reading..GetAudioRawData: "false"
Reading..SendVideoRawData: "false"
Reading..SendAudioRawData: "false"
Meeting Number: ****************
Token:****************
meeting_password:
recording_token: ***********
GetVideoRawData before parsing is : true
GetVideoRawData: 1
GetAudioRawData before parsing is : false
GetAudioRawData: 0
SendVideoRawData before parsing is : false
SendVideoRawData: 0
SendAudioRawData before parsing is : false
SendAudioRawData: 0
directory of config file: /app/demo/bin/config.txt
Init meetingSdk:success
AuthService created.
AuthSDK:token extracted from config file ****************
AuthServiceEventListener added.
Bot don’t connecting to the meeting, maybe I do smth wrong?
If you are, on the top left, there is your Client ID and Client Secret, these are used to sign a SDK Auth Signature. You will use your SDK Auth Signature in config.txt’s token field