Forum Discussion
Common Area Phones
O365 support have confirmed that this is a known issue on their backend infrastructure, and a fix is expected W/C: 2nd April
It is working now but there is still a an issue for Polycom devices.
It looks like that the firmware that is hosted via cloud PBX is incompatible it lacks the CAP options. When you provision a device it signs in that does an firmware downgrade and removes CAP.
I saw the same behavior here. I only have one polycom phone currently, for evaluation/proof of concept purposes. I manually updated it to the latest firmware available from polycom, v5.7.0, only to find that the next day it had rolled back to v5.6.0. I haven't gotten to trying the Common Area Phone licensing yet, so it wasn't a big deal at the time. I assumed that the firmware was just so new it hadn't been updated on the skype servers yet, but it's been almost a month and nothing has changed.
Looks like Microsoft is pushing the 5.6.x firmware to the phone when connected to Skype for Business Online. Check out Martin Boam's experience with CAP Provisioning on his blog, where he mentions how to configure the IP Phone policy to prevent getting the older firmware pushed to the phone:
https://ucmart.uk/2018/03/23/sfb-online-common-area-phone-my-experience-so-far/
In short, you'll want to run Set-CsIPPhonePolicy -EnableDeviceUpdate $false in order to stop the lower firmware from getting installed on the phone after 900 seconds of inactivity.
Also, there is some good news. Polycom literally just yesterday released the newer 5.7.1 firmware for the various VVX models, so may be worth trying that out.
