cancel
Showing results for 
Search instead for 
Did you mean: 

Switch to the new Zoom Phone Common Area Experience before Jan. 1, 2023

HeatherMM
Zoom Employee
Zoom Employee

On May 22, 2022, the option to permanently switch to the new Zoom Phone Common Area management experience became available in your Zoom Phone web portal. Switching to this improved workflow will make it easier and more consistent for admins to add and manage Zoom Phone devices in Common Areas.

 

All accounts that are still on the existing experience will be automatically migrated on January 1, 2023. If you haven’t already switched and want to start using the new Common Area management experience, log into the Zoom Phone web portal and perform the upgrade today by clicking: Systems Management > Users and Rooms > Common Area Phones and selecting the “Update Available” message on the right-hand side. For more information on what this change means for your accounts, please read our support page.

 

Any accounts created after May 22, 2022, are already using the new Zoom Phone Common Area management experience and no further action is required. 

 

Important information for developers

 

A new set of Common Area APIs has been released. If you have been using the Common Area Phones API, you will need to update to the new Common Area API before switching to the new experience. Learn more about the changes on the Zoom Developer Platform site.

2 REPLIES 2

enielsen
Creator I
Creator I

We've found the new Common Area management to be good with CAP phones becoming quite similar to managing user phones. The only weird part (to me at least), is that if one is using ATA devices, if one assigns multiple DIDs to an extension on an ATA, Zoom puts the DIDs on separate ATA ports.

Presumably this is to be consistent with how done on phones, where DIDs are assigned different line keys. But makes no sense on an ATA as a fax machine (for example), will only be on port 1 so assigning additional DIDs to other ports means the call will not reach the fax machine.

Only way around this is to assign the other DIDs to an Auto Receptionist which forwards to the desired extension on the ATA. I need to make a Feature Request about this issue....

Thanks for your feedback! Please go ahead and make a feature request as you would normally, and I will pass this on to the team as well.