Polycom phone stuck at updating initial configuration
The process documented in this article can be used in any Lync 2010 or 2013 environment to setup a centralized provisioning server for managing Polycom SIP phones running Polycom Unified Communications Software (UCS).This article is not intended to replace or accompany any official Polycom documentation.Without it you need to use the VIS role in Skype4B, which doesn’t make much sense when these units support Skype4B natively.
This tutorial isn’t complete, usually units like this are installed as part of a room system from a vendor and thus doesn’t cover things like setting up audio inputs / outputs or IP addressing. For example when you join the meeting Skype4B will ask you if you are in the room and if so, mute all your devices on your laptop/tablet (Note, this is different from a user account and can only be created using powershell) Create the meeting room ‘user’ and grant them the appropriate number and Voice Policy Enable-Cs Meeting Room -Identity “80mpr1” -Sip Address “sip:[email protected]” -Registrar Pool “fepool01.skype4badmin.com” Set-Cs Meeting Room -Identity “80mpr1” -Enterprise Voice Enabled $true -Line URI “tel: 61386408640;ext=8640” Grant-Cs Voice Policy -policyname VP_AU-Vic-Unrestricted -identity “80mpr1” Verify you can log into these accounts using your Skype for Business client and OWA respectively.We tested this with two remote participants, but didn’t encounter any freezing.Now, freezing could occur from any number of factors. One final note here: I’ve written about Music on Hold in the past.The phones will look for specific firmware files to perform an upgrade/downgrade and will download and upload configuration data in XML files.Polycom UCS devices can utilize a variety of different file server platforms to store and manage both firmware packages and configuration files, no additional third-party software is required.
Search for polycom phone stuck at updating initial configuration:
You should see “Registered” in the “Registration Status” field, if not. If the issue persists, check your certificate install, DNS entries and connectivity to the frontends You should also check the devices encryption setting, some integrators turn this off for legacy H.323 setups.