Integrating AudioCodes 420HD / 440HD into Zoom

Forum|Forum|4 years ago
September 3, 2021
3 replies
0 views

We are looking at migrating from on-premise Skype for Business 2015 to Zoom phones. We have a large number of AudioCodes phones that can be reflashed back to stock images (as listed in Zoom).

When provisioning as Zero Touch (factory reset), the device indicates that the Firmware URL and accompanying Configuration URLs do not exist (Configuration file was not found):

- Firmware URL: https://provacp.zoom.us/api/v2/pbx/provisioning/AudioCodes/420HD.img

- Configuration URL: https://provacp.zoom.us/api/v2/pbx/provisioning/AudioCodes/420hd/<MAC>.cfg <-- this is different than what the configuration site suggests (Zoom Phone provisioning drops the 420hd subdir, but we have tried it both ways)

Has anyone successfully connected an AudioCodes (or Yealink) to Zoom? Support claims a lack of familiarity with the device, even though its supported

CloudCat

Employee

Hello mof_cmsmith,

To confirm,

Have you added the phone to Zoom Phone 1st?

This should create the specific .cfg file for the mac address of the phone.

Then factory reset the Audio Codes phone.

Zero Touch provisioning should work after that.

If not assisted provisioning (where you insert the provisioning URL into the phone) should also work.

M

mof_cmsmithAuthor

Newcomer

The device was added first, prior to the factory reset. It simply appears as though the portal is not creating the CFG file or its in a different location (as mentioned, the Help file indicate one location and the Portal indicates a separate).

N

naveen

Community Champion | Employee

@mof_cmsmith - Configuration URL in the MAC - please update with the phone MAC address. e.g.https://provacp.zoom.us/api/v2/pbx/provisioning/audiocodes/00908faa1245.cfg

Note Attached sample screenshot for 405HD, but the process is the same.

M

mof_cmsmithAuthor

Newcomer

Thank you for the assist on this. When we first attempted to provision the phones, we did replace the <MAC> with the mac address. Your statement validates our attempt. It appears that either the CFG is not being created or the paths are incorrect per the documentation.

Note: your Firmware URL is different than the documentation, which was also an issue for us. Once we changed the URL to mimic your screenshot, our devices pulled firmware properly. It would appear that some inconsistencies in the URL paths exist.