# Failed to connect the meeting server

**URL:** <https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133>\
**Category:** Meeting SDK\
**Tags:** recording\
**Created:** [February 19, 2024, 9:20am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133 "2024-02-19T09:20:23Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![abhishekmv.dev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abhishekmv.dev/32/56042_2.png) [@abhishekmv.dev](https://devforum.zoom.us/u/abhishekmv.dev)\
**Post date:** [February 19, 2024, 9:20am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/1 "2024-02-19T09:20:23Z")

</div>

@chunsiong.zoom  
Meeting SDK Type : Linux  
Meeting SDK Version: v5.17.5.2561

I’m implimenting meetingsdk-linux-raw-recording-sample ([GitHub - zoom/meetingsdk-linux-raw-recording-sample](https://github.com/zoom/meetingsdk-linux-raw-recording-sample)).

I followed the README instructions in Zoom Meeting SDK Linux Sample App.  
I build the image using the command mentioned in README:-  
docker build -t msdk-5.17.5-on-ubuntu-compact -f Dockerfile-Ubuntu/Dockerfile .  
and run the container using the command :- docker run -it --rm msdk-5.17.5-on-ubuntu-compact  
After running the container, at last I got “Failed to connect the meeting server” message in terminal . Please find the attached screenshot of the terminal.

 ![Capture11](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/4/6/462eb134cbb08df78371f2f4e1ff3897def25d88.png)

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 19, 2024, 10:06am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/2 "2024-02-19T10:06:49Z")

</div>

@abhishekmv.dev one thing I would troubleshoot first is to remove the recording token.

If it works, then add the recording token back.

This can help eliminate the possible issues down to the recording token

---

<div class="post-metadata">

**Author:** ![abhishekmv.dev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abhishekmv.dev/32/56042_2.png) [@abhishekmv.dev](https://devforum.zoom.us/u/abhishekmv.dev)\
**Post date:** [February 19, 2024, 10:39am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/3 "2024-02-19T10:39:20Z")

</div>

@chunsiong.zoom  
After removing recording token , LinuxChun was able to join the meeting and I got the  
following output in terminal .  
Please find the attached screenshot of terminal.

 ![Capture22](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/2/8/284bfd3be7b91e04d4f5eb76b1012445d5e2e85a.png)

 ![Capture21.PNG](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/e/7/e7c41a44bbea0deb56850dac57c4988c765a324b.jpeg)

But again if I add the new recording token , I got the below output and LinuxChun was not able to join. Please find the screenshot below.

 ![Capture23](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/e/9/e9a16b019e9483bf5f56d4f0480e0a4df7edc498.png)

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 19, 2024, 11:48am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/4 "2024-02-19T11:48:37Z")

</div>

@abhishekmv.dev there is a high likelyhood that the recording token is incorrect.

Do make sure that this recording token is for meeting ID 4174859488

The REST API should be calling  
GET /meetings/4174859488/jointoken/local\_recording

---

<div class="post-metadata">

**Author:** ![abhishekmv.dev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abhishekmv.dev/32/56042_2.png) [@abhishekmv.dev](https://devforum.zoom.us/u/abhishekmv.dev)\
**Post date:** [February 19, 2024, 12:34pm UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/5 "2024-02-19T12:34:48Z")

</div>

After changing the recording token , Bot was able to join the meeting but I’m not able to get raw video and audio data. Terminal processing is not continuing. Please find the attached screenshot of terminal.

 ![Capture25](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/e/c/ecd02c2641ae4a21879898a7dabdf328a5ecc1f9.png)

 ![Capture24.PNG](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/9/4/94541eca6094193fa1d6e5d397431855fe86c29c.jpeg)

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 20, 2024, 2:31am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/6 "2024-02-20T02:31:27Z")

</div>

@abhishekmv.dev it seems that the bot did not successfully join the meeting with the recording token.

Here’s what you should see

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/0/b/0b66572ccc70a03f1351a403e399a1c0b3d1a24b.jpeg)

---

<div class="post-metadata">

**Author:** ![abhishekmv.dev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abhishekmv.dev/32/56042_2.png) [@abhishekmv.dev](https://devforum.zoom.us/u/abhishekmv.dev)\
**Post date:** [February 20, 2024, 10:20am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/7 "2024-02-20T10:20:27Z")

</div>

@chunsiong.zoom  
Recording token is expiring within 120 sec. So I tried to build image and run container within 120sec.  
Bot is able to join the meeting and also recording is happening successfully. Please find the attached screenshot below.  
Please guide me where the raw video and audio data will be saved ?

 ![Capture29](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/7/d/7dfdfc86b575d8e84c53007c7368eb9a6f4b814a.png)

 ![Capture28.PNG](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/4/1/41c48e31438869937eafe49fe04ac245ffd32826.jpeg)

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 20, 2024, 10:37am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/8 "2024-02-20T10:37:53Z")

</div>

@abhishekmv.dev the raw audio and raw video is stored in the directory where the compiled code is . It is within the docker container

---

<div class="post-metadata">

**Author:** ![abhishekmv.dev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abhishekmv.dev/32/56042_2.png) [@abhishekmv.dev](https://devforum.zoom.us/u/abhishekmv.dev)\
**Post date:** [February 21, 2024, 7:17am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/9 "2024-02-21T07:17:02Z")

</div>

@chunsiong.zoom @donte.zoom  
Recording token that I’m getting by calling this API : GET /meetings/4174859488/jointoken/local\_recording  
is expiring in 120sec. By the time container spins up, recording token is expiring, so Bot is not able to join the meeting.  
Only once bot was able to join the meeting when container got spinned up within 120sec. Later on container is taking more time to spin up and so bot unable to join the meeting.  
Please suggest what can we do about this ?

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 21, 2024, 7:39am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/10 "2024-02-21T07:39:18Z")

</div>

@abhishekmv.dev , this is beyond the scope of this SDK as it is best practices on docker containers.

The creation of docker container is typically done once.  
Subsequently when spinning it up, you do not need to build again as the image has already been built.

You just need to pass in the new auth token, meeting number, password and recording token.

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 21, 2024, 7:43am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/11 "2024-02-21T07:43:18Z")

</div>

@abhishekmv.dev ,

you can probably now run something like  
`docker exec -it msdk-5.17.5-on-ubuntu-compact /bin/bash`

use nano or vim to change the config file  
then launch the app in /bin folder

---

<div class="post-metadata">

**Author:** ![abhishekmv.dev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abhishekmv.dev/32/56042_2.png) [@abhishekmv.dev](https://devforum.zoom.us/u/abhishekmv.dev)\
**Post date:** [February 23, 2024, 7:51am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/12 "2024-02-23T07:51:27Z")

</div>

Thank you @chunsiong.zoom . I’m able to get output.yuv file.  
I’m using ffmpeg to convert yuv to mp4. After converting I’m getting mp4 video , but at the end of video there is blurred mess of colours and lines and I got the following error while converting:

[rawvideo @ 0x5574cfd0d800] Invalid buffer size, packet size 302400 \< expected frame\_size 460800  
Error while decoding stream #0:0: Invalid argument

I used the following command to convert yuv to mp4  
ffmpeg -video\_size 640x360 -i rawVideo.yuv -c:v libx264 -s:v 640x360 -preset slow videoOut17.mp4

I have attached the link to mp4 video that I got

> **[videoOut17.mp4](https://drive.google.com/file/d/1saAr9H5yIi6Xc_vo97DRT_NgJsxOHbso/view?usp=sharing)**
>
> Google Drive file.

I also used Gstreamer to convert and I didnt get any errors but video was the same with colour blurrness at the end.

 ![Capture33](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/c/6/c68cc844917516235655d3528c6afcf50db5ef8f.png)

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 23, 2024, 8:57am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/13 "2024-02-23T08:57:45Z")

</div>

@abhishekmv.dev you might want to try something like this

ffmpeg -f rawvideo -pix\_fmt yuv420p -video\_size 640\*360 -framerate 25 -i chrome.yuv -f mp4 chrome.mp4

---

<div class="post-metadata">

**Author:** ![abhishekmv.dev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abhishekmv.dev/32/56042_2.png) [@abhishekmv.dev](https://devforum.zoom.us/u/abhishekmv.dev)\
**Post date:** [February 23, 2024, 9:38am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/14 "2024-02-23T09:38:58Z")

</div>

@chunsiong.zoom  
Again I got the same video with blurred mess of colours and lines at the end and error with respect to frame size.

Also I observed that I’m getting blurred mess of colours and lines only in the part of the video when I start to speak while recording. I tried without speaking and there was no blurred mess of colours and lines in the mp4.

 ![Capture44](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/7/7/77f38a8164dabe01252da737b4d433c2c08646ba.png)

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 23, 2024, 12:18pm UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/15 "2024-02-23T12:18:54Z")

</div>

@abhishekmv.dev here’s the tricky part about raw data. the video frames which are returned can be of various size.

I’ve just tried only saving frames which are 720p. If you only choose to save frames which are 720p, there is no corruption in the resulting conversion.

If you want to save all the frames (of various resolution), you will need to do conversion on the fly as you are receiving the yuv420p frames. There are code samples online on how to do it using ffmpeg library.

---

<div class="post-metadata">

**Author:** ![amanda-recallai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amanda-recallai/32/44747_2.png) [@amanda-recallai](https://devforum.zoom.us/u/amanda-recallai)\
**Post date:** [February 26, 2024, 8:01am UTC](https://devforum.zoom.us/t/failed-to-connect-the-meeting-server/104133/16 "2024-02-26T08:01:15Z")

</div>

Hey @abhishekmv.dev as @chunsiong.zoom mentioned, the incoming frames can be different sizes. This causes the errors you observed, as you’re specifying a hardcoded video size with the `-video_size 640x360` flag.

Because of this, any frames that are of a different size than 640x360 will be parsed incorrectly and result in an incorrect output frame. This size change can happen dynamically as more videos are subscribed to, or network conditions change.

The most straightforward way to take these incoming frames and turn them into a fixed-resolution output video would be to use GStreamer with an `appsrc` at the input (so you can specify frame width and height for each frame individually), a `videoscale` in the middle so you can normalize the frames to your desired output size, and an `x264enc` + `mp4mux` to encode and mux the video.

Another alternative is to use [Recall.ai](https://www.recall.ai/)for your meeting bots instead. 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.

Let me know if you have any questions!
