Hi all,

I'm currently hosting a webinar with an audience who is trying to access translated closed captions in Spanish... after following the setup instructions found in Zoom Support, we found that the only option to select is English. Also, I noticed that I was only able to translate the support article itself into English and one other language with Asian characters. Do we know if there's an outage on language translators currently happening? 

I just spent 40 minutes trying to get through the Zoom system to try and reach support staff but was unable to, Yesterday my credit card was charged by Zoom. I had suspended my account. I don't have students at the moment and I don't need zoom. How can I find out why my card was charged?

Hi there! 

I have just set up a one-on-one event that I will send to a group of students for them to make individual appointments with me via Zoom.

I've set everything up (configured my available times and synced it to my Outlook calendar) and it's all fine EXCEPT for one date.

When I look at my available appointments for this specific day (a Friday), my available times jump from 12pm to 5:30pm as if the Scheduler is seeing that I have a conflicting event on the synced Outlook calendar--except there isn't anything on my Outlook calendar. I've tried to remove this Friday from the available days and add it as a specific day with special availability. I've also double and triple checked my Outlook calendar to make sure there isn't an event I'm not seeing--I have nothing scheduled for that day. 

Am I missing something? Are there other parameters I can change to bypass this? 

Thanks in advance for your help! 

I updated my MacBook (macOS Sequoia v15.3.1) and can no longer log in to my account (error code 5003). I have uninstalled Zoom, restarted my MacBook, installed Zoom, and restarted again (multiple times). And I am still receiving the same error code. 

Apart from updating my MacBook, nothing else has changed. What should I do now? 

We recently updated our redirect URL, which was functioning correctly in the staging environment. However, in production, we encounter 4700 "Invalid redirect" error during the OAuth authorization process. Despite adding the new redirect URL to the "OAuth Allow Lists," redirection issues persist in production.

Staging Environment:

• Users access our application.
• They are redirected to the Zoom authorization page.
• Upon authorization, users return to our application with an authorization code.
• This code is exchanged with Zoom for access and refresh tokens successfully.

Production Environment:

• Users attempting authorization receive the following error:
  • https://zoom.us/oauth/authorize?response_type=code
  • Error: 4700 "Invalid redirect"

Client Id and Client secret remains the same. The change only is in updating the new redirect url.

After spending hours trying to contact tech support I am trying here.

ZoomInstallerVDI.msi is causing machines to reboot during installation despite being called wit hthe '/quiet /qn /norestart' switches.

"The process msiexec.exe has initiated the restart of computer WSAMZN-76FDEC on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found Reason Code: 0x80030002 Shutdown Type: restart Comment: The Windows Installer initiated a system restart to complete or continue the configuration of 'Zoom VDI Workplace (64-bit)'."

We have deployed Zoom Phone system with IP Phones etc at our offices along with Emergency addresses etc.
These all work just fine, and this is for people working remotely using the Desktop Client (on Windows).

Windows 11 has now started prioritizing IPv6 as the default protocol if it is available. So for example if you ping www.google.com in a command prompt it will respond with the IPv6 Address instead of the IPv4.

The problem with this is that the Zoom Client will complain that it cannot confirm my home address location and I will get the error at all times.

There are some workarounds.

1) Disable IPv6 on the router (not ideal)

2) Apply a registry fix to prioritize IPv4 over IPv6 on the OS (needs a reboot)

3) use command Prompt to manually set IPv4 Priority over IPv6 (Does not need a reboot but requires setting on subsequent reboots)

Once you have changed the priority and restart the desktop client the error goes away and it sets the Emergency Address correctly.

Is this behavior going to be addressed in a later version of the Desktop Client so it requires no user interaction?

Thanks

Shad