We want to use Zoom phone to handle all calls in auto attendant mode AND have the voicemails left in the main mailbox. We have been able to set up auto attendant and have calls routed to the attendant mailbox (#801) but have not been successful in getting the messages at the #800 level.

Hey, 

It seems that we are unable to use certain special characters within the comments field of the Zoom phone integration with Salesforce. 

When trying to add either '#' or '&' to the comments box, the following error is returned. "Unexpected end-of-input: was expecting closing quote for a string value at [line:1, column:265]"

We have the field synced to a long text area in our task object. 

Can anyone please advise? Thanks

I've tried to contact Zoom sales, support, and chat but I have not been able to get an answer.

I'm one of the thousands affected by Skype discontinuing, so I am looking for alternative phone platforms. I see Zoom added phones in 2019, so potentially a good option since it seems to function just like Skype (your own phone number, cellular data or wifi calling, make or receive calls). I like Zoom as a platform and use it regularly for video conferencing. 

I've had a Zoom Pro account since 2016 and, therefore, have legacy pricing of $99.90 per year.  I don't want to lose that because Zoom conferencing is vital to my work. It might be nice to have phone and video conferencing bundled together.

First question: Can I port my Skype number to Zoom? (lots of places say they will accept ported numbers, but the fine print says they won't accept Skype numbers. I have not found one yet that accepts Skype numbers)

Second, and more important, question: If I go with a Zoom bundle of Pro/Phone, will I lose my legacy pricing?

When I answer an incoming call on my Android Softphone, the call always switches to my watch.

I have to click on Bluetooth and change from my watch to 'Handset'.

How can I remove my watch from the list of Bluetooth audio devices for Zoom?

Zoom V 5.17.7 (19440)

Android Galaxy S10e: V 12

Ticwatch Pro 3 Ultra P628 - Wear OS 2.45 

so we use a headset here to answer multiple calls. when i am on one call and the phone rings it rings through the headset and i can't hear my current customer that i am speaking with. is their any setting or any advice to fix this problem. i tried the audio use separate audio device to play ringtone simultaneously and that didn't work. 

thank you, Chris

I recently created a program to sync contacts from our CRM system into Zoom Phone as External Contacts. This works great, but it has the problem of making it difficult to search for internal extensions in the directory. 

It's not so much a problem on the Zoom Workplace app, but it is an issue on our desk phones (Yealink). For example, if I search the directory for 'Jason', it shows the max results of 200, which doesn't include the internal extension for Jason. Searching the full name doesn't return a result, when it did before syncing the external contacts. 

Is there any way to prioritise internal contacts in the search so they are returned before external contacts? If there is a way to amend the LDAP search filter to only show internal users, that would be a suitable solution too. 

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