# The Meeting number is wrong - Error 3706

**URL:** <https://devforum.zoom.us/t/the-meeting-number-is-wrong-error-3706/97063>\
**Category:** Web\
**Created:** [October 19, 2023, 11:46am UTC](https://devforum.zoom.us/t/the-meeting-number-is-wrong-error-3706/97063 "2023-10-19T11:46:21Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmalik](https://avatars.discourse-cdn.com/v4/letter/b/a9a28c/32.png) [@bmalik](https://devforum.zoom.us/u/bmalik)\
**Post date:** [October 19, 2023, 11:46am UTC](https://devforum.zoom.us/t/the-meeting-number-is-wrong-error-3706/97063/1 "2023-10-19T11:46:21Z")

</div>

I am using the steps mentioned on the github page for meeting web sdk to join a zoom meeting .  
I have a developer account with zoom . I generated the sdkkey and sdksecret and then used the steps mentioned in [GitHub - zoom/meetingsdk-auth-endpoint-sample: Generate a Meeting SDK JWT to join Zoom meetings and webinars with the Meeting SDK.](https://github.com/zoom/meetingsdk-auth-endpoint-sample) to generate the signature . The role is 0.  
Also I am using CDN for the SDK .The version number is 2.17.0  
The code that I use to start the meeting is

client.join({  
sdkKey:sdkkeystring,  
signature: signaturestring,  
meetingNumber: meetingNumberstring,  
password: passcodestring,  
userName: usernamestring  
})

But when I run the code, I can see the error:-

- {type: ‘JOIN\_MEETING\_FAILED’, reason: ‘The meeting number is wrong.’, errorCode: 3706}

1. errorCode: 3706
2. reason: “The meeting number is wrong.”
3. type: “JOIN\_MEETING\_FAILED”

The meetingNumber is correct according to me . I had started the meeting before running the code . Request you to help me in resolving this issue.

---

<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:** [October 20, 2023, 3:03am UTC](https://devforum.zoom.us/t/the-meeting-number-is-wrong-error-3706/97063/2 "2023-10-20T03:03:42Z")

</div>

@bmalik ,

The meetingNumber in the clientJoin must match the meetingNumber in the JWT token as well. Could you check that?

---

<div class="post-metadata">

**Author:** ![bmalik](https://avatars.discourse-cdn.com/v4/letter/b/a9a28c/32.png) [@bmalik](https://devforum.zoom.us/u/bmalik)\
**Post date:** [October 20, 2023, 6:26am UTC](https://devforum.zoom.us/t/the-meeting-number-is-wrong-error-3706/97063/3 "2023-10-20T06:26:39Z")

</div>

Hi,

The meeting number is :- 81793851836

I passed ita s a string and the JWT token value is:-

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzZGtLZXkiOiJ5Z2VSdDdDWVRrdlJjVEdTSGtnNkEiLCJpYXQiOjE2OTc3MTQ0NzIsImV4cCI6MTY5NzcyMTY3MiwiYXBwS2V5IjoieWdlUnQ3Q1lUa3ZSY1RHU0hrZzZBIiwidG9rZW5FeHAiOjE2OTc3MjE2NzJ9.oZpLnG29SNbt1X\_lGAiQz0LSHPxCb-VMLK\_cu\_blcLo

How can I decode the token to see if the meeting number is correct? Though I passed the same value with role as 0 to create the JWT token.

Thanks,  
Bhawana

---

<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:** [October 20, 2023, 6:53am UTC](https://devforum.zoom.us/t/the-meeting-number-is-wrong-error-3706/97063/4 "2023-10-20T06:53:09Z")

</div>

@bmalik your JWT token is missing the meetingNumber and role  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/5/f/5fc0c4d4924ec6fbd0583907d9eb356eb699f97e.png)

You can use [jwt.io](http://jwt.io) to decode it

---

<div class="post-metadata">

**Author:** ![bmalik](https://avatars.discourse-cdn.com/v4/letter/b/a9a28c/32.png) [@bmalik](https://devforum.zoom.us/u/bmalik)\
**Post date:** [October 20, 2023, 8:04am UTC](https://devforum.zoom.us/t/the-meeting-number-is-wrong-error-3706/97063/5 "2023-10-20T08:04:52Z")

</div>

What is the best way to generate the JWT token?

Thanks,  
Bhawana

---

<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:** [October 20, 2023, 8:20am UTC](https://devforum.zoom.us/t/the-meeting-number-is-wrong-error-3706/97063/6 "2023-10-20T08:20:32Z")

</div>

The sample which you have shared is a good way to do so.

> **[GitHub - zoom/meetingsdk-auth-endpoint-sample: Generate a Meeting SDK JWT to...](https://github.com/zoom/meetingsdk-auth-endpoint-sample)**
>
> Generate a Meeting SDK JWT to join Zoom meetings and webinars with the Meeting SDK. - GitHub - zoom/meetingsdk-auth-endpoint-sample: Generate a Meeting SDK JWT to join Zoom meetings and webinars wi...

---

<div class="post-metadata">

**Author:** ![bmalik](https://avatars.discourse-cdn.com/v4/letter/b/a9a28c/32.png) [@bmalik](https://devforum.zoom.us/u/bmalik)\
**Post date:** [October 20, 2023, 11:12am UTC](https://devforum.zoom.us/t/the-meeting-number-is-wrong-error-3706/97063/7 "2023-10-20T11:12:39Z")

</div>

Thanks. I could finally create a valid jwt token and join the meeting . The issue was the way in which I was sending the meeting number and role in Postman . After I changed the payload to json format . It worked.

---

<div class="post-metadata">

**Author:** ![bmalik](https://avatars.discourse-cdn.com/v4/letter/b/a9a28c/32.png) [@bmalik](https://devforum.zoom.us/u/bmalik)\
**Post date:** [October 20, 2023, 11:13am UTC](https://devforum.zoom.us/t/the-meeting-number-is-wrong-error-3706/97063/8 "2023-10-20T11:13:45Z")

</div>

The ticket can be closed now. Thanks for your help.

Bhawana

---

<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:** [October 23, 2023, 2:36am UTC](https://devforum.zoom.us/t/the-meeting-number-is-wrong-error-3706/97063/9 "2023-10-23T02:36:28Z")

</div>

Closed on October 23, 2023, 2:36am UTC


