Embed zoom video to a web server

[quest (Sequester McKinney)]

Hey Tommy,

No, I am trying to embed the iFrame in our WordPress website. Thanks so much.

-Q

[tommy (Tommy Gaessler)]

Hey @quest,

I have replied to your private message regarding this.

Thanks,
Tommy

[raul]

Is there a way to move chat to the side when you embed your meeting in web page? Chat takes over the whole window when launched.

Thanks!!!

[tommy (Tommy Gaessler)]

Hey @raul,

Can you please provide a screenshot of the issue?

Thanks,
Tommy

[raul]

thanks for the quick reply. This is a screen shot of chat in the embeded window on my website.

[tommy (Tommy Gaessler)]

Hey @raul,

That is strange. It is probably because you are custom sizing the Zoom Window which is meant to be full width.

Can you share your iFrame code?

Thanks,
Tommy

[Cristian]

Hi Tommy, thanks for all replies

This is my code embedded in a WP page:

<div class="iframe-container" style="overflow: hidden; padding-top: 56.25%; position: relative;"> <iframe allow="microphone; camera" style="border: 0; height: 100%; left: 0; position: absolute; top: 0; width: 100%;" src="https://zoom.us/wc/{{meeting_zoom_id}}/join" frameborder="0"></iframe></div>

I have some question (I’m on Mojave/Chrome):

1. Which is the correct URL to use, https://zoom.us/wc/{{meeting_zoom_id}}/join or https://zoom.us/wc/join/{{meeting_zoom_id}}?
   Is there any difference of using it?

2. which is the difference between embed a Meeting or a Webinar?

3. un = base64encoded of username, but WHICH username? The host or the participant? Or the topic?

4. pwd=passwordhere is the password of the meeting? or the participant?

5. uel=which email is?

6. If I use “sandbox=“allow-forms allow-scripts”" the JOIN button stop to work

7. With this configuration, embedding a WEBINAR, the user has to put an email and a nane, than, click on agree and then there’s a loop of the first scree, so he needs to put again an email and a name. After that he can join.

How can avoid this behaviour?

Thanks in advance

Cris

[ricardo.tavares]

Hello and thank you for being so helpful,

I’d just like to confirm what limitations we currently have when embeding the zoom web client through an iframe. I believe it’s still possible to join a meeting directly with the usual https://zoom.us/wc/{{meetingId}}/join?prefer=1&un={{base64username}}pwd={{password}} source, but it seems that, if the client needs to ask for cookies to be accepted, bypassing the password+username form is not possible.

Should we expect similar restrictions to come to the Web SDK or is that the better option for always beeing able to join a meeting directly?

[raul]

You are right. I was able to fi by adjusting the width. Next ?. What is best way to optimize this on mobile device?

[developer613 (George)]

Hello, Tommy.
How are you?
I am trying to customize Web SDK UI.

Is a such design possible?
Every red block means a user video block.
I look forward to your kind reply.

Thank you.

[developer613 (George)]

Hello, Tommy.
How are you?

[tommy (Tommy Gaessler)]

Hey @developer613,

Custom layouts are not supported yet on the Web SDK. You could use CSS to do this in the meantime.

Thanks,
Tommy

[tommy (Tommy Gaessler)]

Hey @raul,

The default Web SDK styling is responsive on mobile.

Thanks,
Tommy

[tommy (Tommy Gaessler)]

Hey @Cristian,

@Cristian

Which is the correct URL to use, https://zoom.us/wc/{{meeting_zoom_id}}/join or https://zoom.us/wc/join/{{meeting_zoom_id}}?
Is there any difference of using it?

https://zoom.us/wc/{{meeting_zoom_id}}/join

@Cristian

which is the difference between embed a Meeting or a Webinar?

See the differences between Webinar and Meeting.

@Cristian

un = base64encoded of username, but WHICH username? The host or the participant? Or the topic?

It is any username you want. Whatever you want that participant to be called.

@Cristian

pwd=passwordhere is the password of the meeting? or the participant?

Password of the meeting.

@Cristian

uel=which email is?

Email of the participant.

@Cristian

If I use “sandbox=“allow-forms allow-scripts”" the JOIN button stop to work

Can you clarify the issue?

@Cristian

With this configuration, embedding a WEBINAR, the user has to put an email and a nane, than, click on agree and then there’s a loop of the first scree, so he needs to put again an email and a name. After that he can join.

See my post here:

Embed zoom video to a web server

Hey @gabriele.limonta, Thanks for your patience! For this to work you need to have Webinar Registration Required turned off, and then use the uel={base64EncodedEmail} query param. For example: https://zoom.us/wc/123456789/join?prefer=1&un=bmFtZQ==&uel=ZW1haWxAZG9tYWluLmNvbQ== Thanks, Tommy

For additional questions please start a new thread.

Thanks,
Tommy

[tommy (Tommy Gaessler)]

Hey @ricardo.tavares, you are welcome!

@ricardo.tavares

Should we expect similar restrictions to come to the Web SDK or is that the better option for always beeing able to join a meeting directly?

The Web SDK is your best option.

Thanks,
Tommy

[developer613 (George)]

Thank you for your reply.
Can you explain more details?
I don’t understand you.

[Cristian]

Hi @tommy, thanks for the answers.
I started a webinar without password, nor registration, and I used this link:

“https://zoom.us/wc/89056880113/join?prefer=1&un=bmFtZQ==&uel=ZW1haWxAZG9tYWluLmNvbQ==”

Still I have to insert:

1. name + captcha
2. click on AGREE
3. insert the email

Is there a way to remove this three steps?

[deepak1 (Deepak)]

Hi @tommy
I have face one issue when I use below code

it’s work some time and some time it’s give error like this

Mixed Content: The page at ‘https://test.com/Democracy/’ was loaded over HTTPS, but requested an insecure frame ‘http://zoom.us/wc/join/4584848647?tk=&prefer=1&track_id=&meeting_result=&jmf_code=&wpk=&_x_zm_rtaid=xdWQ_j-YRVG8_CEsIv63qw.1588071797322.410532085969fd729f8e0bacc2e29f51&_x_zm_rhtaid=172’. This request has been blocked; the content must be served over HTTPS.

but some time same code is working after hard refresh or other browser

[Cristian]

Hi @deepak1, try adding this meta on your page:

"<meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">"

[deepak1 (Deepak)]

Hi @Cristian which one?
can you please write here