I've recently obtained 2 IP 5000 conference phones. After a little tinkering I've managed to provision one successfully, howeer I'm now trying to provision and register the second and have encountered a problem.
After introducing the device onto the network and logging onto it through the web I changed the admin and user passwords as per best practices, then updated the firmware to 184.108.40.2065, exactly as I did with the other device. For some reason though this device will now repeatedly do the following:
Having looked around online I've found the 1,3,5,7 method to reset the phone, but my problem is I don't have time to enter the new admin password before the phone reboots itself automatically, nor do I have time to change the password on the web portal before it reboots - Is there any way I can stop thjis happening?
Hello, and welcome to the community!
It sounds like you initiated the software upgrade to 220.127.116.115 via the Web Configuration Utility. The instruction below assumes that is true.
In effort to stabilize the phone without a factory reset:
This will clear the parameter which holds the upgrade server address (which gets configured when attempting a software upgrade via the Web Configuration Utility.) If that field is already blank, or the above steps do not address the issue, you can factory reset the phone from the boot setup menu.
To factory reset the phone from the boot setup menu:
If the phone is provisioning and is able to upload logs to the provisioning server, you may want to review the app and boot logs the phone is generating and search for "sip.ld" in those files. You should find, logged by the curl module, the URL the phone is attempting to retrieve the software package from as well as a reason for any failures.
If the phone is attempting to retrieve the files from the Polycom Hosted Server--indicating the software update was initiated through the Web Configuration Utility, the URL will reflect our downloads.polycom.com domain. Otherwise, you may see your own provisioning server address being used for the request. If the log does not indicate a clear and resolvable reason for failure please feel free to post sanitized snippets of the log here for analysis (you can either attach a file or use the code tag.)