Zoom Webhook participant IP address mismatch

API and Webhooks
1

Hi folks,

I’ve been using the zoom webhook to send information about the participants information particularly IP Address to Google PubSub and then CRIBL. Everything was going great till we realised that some participants are joining via “Web browser“ and the IP logged is one that belongs to Zoom’s IP range .

But when we checked the call information via the Admin panel we are able to see the participants actual IP.

Is there a way to always get the participants true IP via the webhook?

Thanks!

2

Hi @conrad1
Thanks for reaching out to us and welcome to the Zoom Developer forum
Have you been able to troubleshoot this on your end? I will try and replicate this on my end to give you some feedback because I have not tested this specific scenario just yet

1 Like
3

Hi Elisa,

I believe this is a issue with the webhook itself. I’ve confirmed this over email with the product team.

4

Thanks for getting back to me! @conrad1
Could you please confirm what webhooks are you listening to so I can reproduce this on my end and escalate to our Engineering team please

5

Sure, its for the following events selected below.

image
image359×211 27.1 KB

to simulate the problem, try joining a meeting via the web browser and look at the participant’s “public_ip”. The IP gets logged as belonging to Zoom’s infra i.e. IP’s in this range Zoom network firewall or proxy server settings. However, when we have a look via the admin console we can see the actual IP.

When a participant joins via the zoom client the correct IP is logged.

6

Thanks for sharing more details @conrad1
I am able to reproduce this on my end and I can see the mismatch you are talking about.
I will escalate this internally and will report back to you with an update ( ZSEE-188112 internal ticket number for reference)

1 Like
7

Hi @elisa.zoom is there anyway for me to track ZSEE-188112? Thank you!

8

Hi @conrad1
Thanks so much for your patience and sorry for the late reply here!
I did hear back from our Engineering team and they shared the following:

The IP address mismatch, is expected behaviour because when joining through the web client. Web client use RWG(gateway) to join the meeting. So the webhook contains RWG gateway’s IP address in payload. You can use GET /metrics/meetings/{meetingId}/participants to get the real IP of participant joining using web client.

9

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.