We are in the process of implementing OCS 2007 R2 Enterprise Edition. One thing we never got going is updating a phone device (Specifically, the Polycom CX700).
Updating the software (ie, the Communicator client) worked just fine. So below are the various things I tried in order to fix the issue, which I finally did.
In all cases, the following should work: If it does not, check the IIS logs. Also, within IE, enable enhanced error display by unchecking the box next to “Show friendly HTTP error messages” in the Tools/Options menu. In reverse-order of fixes (ie, the last fix is listed first).
Added a MIME type to IIS for the.nbt file type.nbt – binary/octet stream. Discovered this fix via a 404.3 error in the IIS logs 2. Debugged the status code (0x2ee7) – The Server Name could not be resolved. Codes are listed here:. This launched a rash of fixes, some of which may or may not have helped. Set a static mapping within WINS for front end server.
Edited the ucupdates-r2.opensolutions.com DNS record to point to the front end host, not the pool. Edited the WMI entries for “InternalUpdatesDownloadURL” and “InternalUpdatesStoreURL”. open the WBEMTest utility and connect to rootcimv2. click the Query button and enter this query:. select.
from MSFTSIPUpdatesServerSetting where backend=' ocs’. Double click on the line that is returned (not intuitive that you can double click). Scroll down to the values listed above and changed them from “to /RequestHandler/ucdevice.upx 3. IIS Changes.
Changed virtual directory in IIS from a DFS share to a direct share (was domainshareupdates. Now – C:OCS SharesupdatesDeviceUpdates) 4. Client Device Filter Settings. Edited Client Version Filter to be: OCPhone 1.0.522. = Allow and Upgrade Folder: DeviceUpdates 5.
Security. Verified all the security everywhere – within IIS, Shares, file shares, files themselves Websites referenced throughout process.
October 31, 2012 by This process can be used on any of the Polycom SIP Phones which support 4.x software today (SoundPoint IP, SoundStation IP, VVX, and SpectraLink models). This only applies to devices which are already running at least version 4.0.0 of the UCS firmware.
In previous versions (Polycom SIP software 3.x or earlier) this manual process was not available. Also the firmware was packaged differently in the previous SIP versions as the device firmware was provided as two separate binary files, the bootloader image and the application image. In the 4.x UCS release these were merged into the same binary file. New devices like the VVX500 and SpectraLink phones have only ever shipped with 4.x UCS releases, while older devices like SoundPoint IP phones may still have previous 3.x SIP releases on them.
In order to utilize Lync integration a must first be used to upgrade devices running 3.x to 4.x. This process can be used on any of the Polycom SIP Phones which support 4.x software today (SoundPoint IP, SoundStation IP, VVX, and SpectraLink models).
Updating Firmware The Polycom SIP phones support a few different methods for software updates, most commonly utilizing a central FTP provisioning server so that all devices will check a single distribution point for configuration changes and new firmware images. The previous article mentioned above contains links with more details on enterprise deployment and management practices. But when trying to update the firmware for a few phones there is a new process which was introduced with the 4.0 release of UCS. This process allows the device to be manually pointed to a Polycom hosted web server distribution point on the Internet to download and install new firmware packages from. As of the writing of this article the Lync specific firmware release is not yet included on the Polycom Hosted Server, so primarily Open SIP only firmware releases will be available using this method. This same process can also be used to download files from a custom distribution server for use with the Lync Qualified releases, as covered in the next section of this article.
Identify the IP address assigned to the first phone to be upgraded by navigating on the device to the Settings Menu Status Network TCP/IP Parameters and check the IP value. Connect to the IP address of the phone using a web browser.
When prompted for login information select Logon As Admin and enter ‘456’ which is the default password (or the custom administrator password assigned to the specific phone, if one was previously set). From the Utilities menu select Software Upgrade. Verify that the Server Type is set to Polycom Hosted Server and then click the Check for Updates button. If the connection is successful then a list of currently provided software versions will be returned. Select the desired version (if there is more than one listed) and click the Install button.
This will trigger a reboot of the phone and begin the update process. Immediately after rebooting the phone should report the status of “ Updating, Please Wait” followed soon after by “ Downloading new Updater”.
This status bar here will indicate the completion of downloading the.sip.ld binary file for the desired update version for the specific phone model. The phone will then report “ Updater updated, rebooting” and then after the reboot should report “ Downloading new application”. Once this process is complete the device update will be complete and it will start the application interface. Any configuration settings previously entered will be retained. Normally only the latest version will be provided on the Polycom Hosted Server, but this central distribution point may not include the most recent versions released depending on what features or capabilities were introduced in the last release. For example the recent 4.1 release is only providing Lync-specific features so devices currently used with other SIP platforms (.e.g Broadsoft, Avaya, Nortel, etc) should not install this update and should remain on 4.0 software for now. For this reason it may be necessary to download the available software package for the 4.1 release and then create a custom distribution server to point the devices to.
Using Custom Software Distribution To create a custom software distribution a software package must first be downloaded, the firmware files extracted, and then a configuration file created and modified. Vsco cam cracked ios. There is still some initial setup required but this is a basic as creating a single XML file and then dropping it an the desired firmware files directly into any web server directory. For engineers looking to carry phones around to different sites for demonstration purposes then selecting a web server on the Internet makes it very easy to update the phones over the Internet, while for supporting updates for a handful of devices on an internal network then utilizing an existing web server is ideal.
Either way once the directory is setup then any device can be manually pointed to the directory and the phone will utilize HTTP to download and apply the firmware. Also this process can be used to downgrade software if needed as multiple versions can be stored in the same location and a menu will be presented to allow the desired version to be installed. All currently available versions of the Polycom UCS can be located in the official software release matrix online as well as on the product support page for any model SIP phone. Always make sure to download the Split version of any versions as two different types of packages are provided: a Combined package with all firmware files for all phones provided in a single large binary, or a Split package which contains individual binary files for each phone model’s specific software version. Browse to the website to locate the software package for a specific family of devices or go to to the website and download the desired release package.
(Note that the newly qualified Lync software release of 4.1 is currently only available through your Polycom reseller for some devices.). Read and accept the notice regarding the previously explained upgrade process requirements for older devices. Once the download is complete open the compressed file and look for the.sip.ld files. These are the individual firmware files for each model of Polycom SIP phone. The table below indicates which firmware file is used by which device.
Currently only the Lync Phone Edition devices provide any of the 'better together' scenarios. But this functionality is covered in the third party interoperability specification documents from Microsoft, so other vendors will be able to include it in their devices. I can't speak to any company's unannounced plans though. I will say that you will continue to see the feature list grow for third party qualified devices over time, as opposed to the LPE client which has had the same feature set for 2 years now.
Great article as usual, Jeff. We are trying to update VVX 500's from 4.1.0.73405 to 4.1.2.22625 but are running into some issues. When trying to check for builds using the Polycom Hosted Server it locks up the browser. We have tried this from IE and Chrome on multiple machines and networks but get the same results each time. To get around this issue we setup a Customer Server using your instructions in this article. It sees the server, find the correct build, asks for confirmation, displays the EULA, and then says the phone will reboot on it's own and update.
The phone never reboots on it's own and will not update if we try manually rebooting. Any ideas on what the problem might be? Are incremental updates required to get from 4.1.0.73405 to 4.1.2.2262?
Iphone Software Update
Any advice you can give would be greatly appreciated. Hi Jeff, We are trying to configure Sound point IP 331 phones It restarts many times before working 1)Upgraded the Boot Rom ( Updater ) 4.4.0.0080, Boot Block version: 3.0.2 0024. 2)Used PolycomUCSoftware410RevI firmware 3)Used SoundPointIPBootROM440BUpgrader 4)Using the Centralized provisioning server FTP & DHCP ( with option ntp, 160, 66, 43, & 120 ) for downloading the configuration.
5)Used Lync Device.cfg ( attached for your reference) 6)After booting the Phone shows network is down & reboots continuously, 7)After 20 25 reboots the SIP log in option will come, if given correct details it logs in to lync 8)If end point is restarted again, it takes 20 25 reboots to get in to sip login page. Hi Jeff, this post 'looks' like it should resolve my issue (I need to update the firmware on my PC IP 331. When i try to access the phone's web interface it does not accept the ID and Password. I'm on a Mac using Safari, and the interface is slightly different.
I don't have the radial button to choose Admin or User I have to actually enter 'Admin' (and yes i've tried 'admin' as well. I know the password is still 456. But when I try these credentials, it kicks back and I can't get in. I'm currently running Firmware 2345-12365-001 Rev:B and I need to have it running 2345-126XX-XXX.
Hi Jeff, just wanted to know with the VVX500 vesion 5.0.0 UC firmware update. On which minimum version does the VVX500 needs to be to be able to pull the updates from lync 2013 server. If uploaded the cab files, but the phone does not seem to pull it. The vvx500 phone we're testing is on version 4.1.2 at the moment.
I would like to try and avoid using a ftp/web server as we have the lync frontend to cope with that and also with the test devices and approval processes which is quite easy with the cx600 phones. Any help will be appreciated.
Regards Danie. It is new functionality in the 5.0.0 release, but if it was differed to the next release then you'd have to wait another release to use it. The CAB files were released for 5.0.0 in addition to the standard split and combined packages as there are many development or beta 5.x builds prior to this public release which contain the feature, so pre-release environments were able to take advantage of this for incremental updates as well as the final release upgrade. For the average deployment you'll have no need for the 5.0.0 CAB files, but you will be able to use the next release of CAB files.
Hi Jeff, many thaks for this article. It was just what I was looking for. I've got a problem however. I'm updating using the custom server otion. I've placed all the required files in my webserver and confirmed that the ucs.xml file and the 3111-44500-001.sip.ld file are both present and available.
Everything proceeds as expected but my VVX500 does not reboot. When I check the logs its shows: cfg. 00 Prov Starting to update 502/3111-44500-001.sip.ld copy.
00 Server '10.165.35.86' said '502/3111-44500-001.sip.ld' is not present cfg. 00 Prov Starting to update 502/sip.ld copy. 00 Server '10.165.35.86' said '502/sip.ld' is not present I don't understand why the phone would not detect the file since the.sip.ld file is definitely there and I can download the file from my computer's browser. Any help would be appreciated. Hi Jeff, Thanks for the Article. I would like to have your advice on below scenario also.
Thanks in Advance. Current Scenario: We are organization which uses ten thousands of Polycom devices(Includes IP Series and SS Devices) across different geographical locations. Currenly all devices are using BootRom 4.2.1.0499 and SIP 3.3.2 and few locations has SIP 3.3.4. We follow zero touch provisioning with Centralised Provisioning Server. So when we connect a device to the network it gets Provisioning server path from DHCP Then it device boots with the BootRom/SIP kept in 'home' folder(The Prov Server redirects./Polycom/PolycomANY/part-no.boot sip.id to./polycom/firmware/part-no.boot sip.id ). Planned System: We are planning to upgrade the devices to 4.x.
Which comes with latest bootRom 5.0.1 for a pilot location with few hundread devices with central provisioning Problem: There is no difference in bootserver Location/Both bootRoms 4.x and 5.X for a device will be having same name. To be more clear, If have 100 Polycom650 device, we would like to upgrade only 10 of them to Latest bootRom/SIP with Same Privisioning Server. Able to acheive different SIP for different locations by using APPFILEPATH='new/sip.ID' in user level after a user logging in successfully to the device.
Not sure about BootRom. I am unable to get/locate reference for this scenario as its a Mixed environment for BootRoms.
Suggestions are welcome. Kidly redirect me if this question is already answered in this forum Thanks. Regards, Ganesh. Ganesh, you are correct in that you cannot easily limit the scope of which devices will attempt to access the newer firmware as all devices pointed to the 0.cfg file will follow the same rule. Your best option to control the roll-out of the new firmware is to leverage device-specific.cfg files.
Simply duplicate the current 00.cfg file and change the name to match the MAC address of one of the desired phones (e.g. A1B2C3D4E5F6.cfg) and then change the APPFILEPATH value to a different location (like 'new/sip.ld') and them place the BootROM upgrader and 5.x firmware files in that location.
Test with that phone and then duplicate that.cfg file and make one copy for each of the ten phones you want to upgrade, using their MAC addresses as the file names. Once you decide to upgrade all the rest of the phones either continue to follow this model, or instead delete the MAC-specific.cfg files and move the new firmware file into the default location for all device to access. Hi Jeff, Our client is using Polycom phones. We have issues with vvx600 model, when we make any call the user doesnot get call on the vvx 600 but they get missed call alert.
We are trying to upgrade the firmware of the phone, which is currently 4.1. But it is not working. We tried 3 different version 5.0.0, 5.2.2 and 4.1.8 in so many ways like setting up provisoning server, using.cab file and.sip.ld file but all in vain. Under utilities if we select custom server and provide the link it does show the firmware which we have updated on the server but when we click install it is not getting installed. Not sure what we are missing, could you please suggest what can be done to get the firmware upgarded successfully. Regards, Khushboo.
We have 3 Polycom VVX500’s that we got as part of the start of service with Intermedia. I noticed throughout the selection process that they take 10 line phones and through firm where lower it to a 5 line phone or in this case took the VVX500 which is a 12 line phone and made it an 8 line phone. I think this is foolish and assume it has to do with revenue and trying to make you buy an even more expensive phone. I might be wrong but this is my assumption. So, the phone get setup and when you hit the home button and slide to the right from the left I have 2 rows of 4 icons each with the EXACT same extension on that particular phone.
I want to update these softkeys with members of the office but I can’t. I contacted Intermedia and they told me that this function is “locked down” with the firmware they have deployed. I was told by the rep that this is not the first time he has had complaints about this exact same issue but that engineering doesn’t have to or typically answer to technical support.
Is there a workaround this issue that you might be aware of? Thanks for your time in advance. Just got two shiny new VVX500 phones which have arrived with firmware 4.1.7.1210. Neither will connect to the Polycom Hosted Server, so I’ve followed your very helpful instructions and tried to use both HTTP (with MIME types for.LD and.CFG allowed) and TFTP to connect to my custom server. In both cases the phone recognises the available version, and I get all the warnings about the update and rebooting, but then.
Nothing Any suggestions as to what I should do will be very welcome. My aim is to connect to Lync 2013 asap. Many thanks William. I have several VVX phones of varying models 400,500 & 600. They are all stuck on the firmware build 5.4.2.0334. I think these might have last been updated when testing a cloud provisioning server but not sure. Regardless I have been unable to get the web interface to kick off the update.
The Check for Updates works and finds the latest builds but when I select and apply one it never installs and reboots the phone. I’ve tried rolling back the phone to an no luck.
Any ideas for me on options? Thanks, Luke.
Hi Jeff: I have a VOIP vendor who suddenly stopped provisioning our (old admittedly) IP 430 phones. I can get some used IP 650 phones very reasonably, but they have 4.1.1 firmware, and my VOIP vendor can only take up to 4.0.8. I am not a Windows guy, I do everything with Linux and usually a command line. Can I just download the 4.0.8 firmware file to a Linux box on the same node as the phone, and point the phone to it as a TFTP server? I am getting kind of desparate, as I have a total of 15 phones down in 2 locations, and we have even more of the IP 430’s in service.
Can the IP 650’s be safely downgraded from firmware 4.1.1 to 4.0.8? Thanks, Bill.
Hello, Polycom and other manufacturers produce these optimized for Microsoft® Lync® or Skype® for Business devices after a reference design and the embedded OS running on the phones is provided, supported and maintained by our partner Microsoft®. You therefore may want to reach out to the Microsoft® community and / or Microsoft® support directly instead as this is the most direct and efficient path. Polycom is unable to add any new features into the functionality of these CX Devices Please try Best Regards Steffen Baier.
Please be aware: The purpose of these forums is to allow community members collaborate and help each other. Questions posted here do not follow Polycom’s SLA guidelines.
If you require assistance from Polycom technical support, please open a. The above is necessary in order to track issue internally within Polycom. You are welcome to post more questions or configuration or logs for other community members to look at but if your issue requires a fix via Polycom you must go via the official support structure. Please ensure you always check the, or FAQ's Please remember, if you see a post that helped you, and it answers your question, please mark it as an 'Accept as Solution'. This forum reply or post is based upon my personal experience and does not reflect the opinion or view of my employer. Polycom employee participation within this community is not mandatory and any post or FAQ article provided by myself is done either during my working hours or outside working hours, in my private time, and may be answered on weekends, bank holidays or personal holidays.
Please be aware: The purpose of these forums is to allow community members collaborate and help each other. Questions posted here do not follow Polycom’s SLA guidelines. If you require assistance from Polycom technical support, please open a. The above is necessary in order to track issue internally within Polycom. You are welcome to post more questions or configuration or logs for other community members to look at but if your issue requires a fix via Polycom you must go via the official support structure. Please ensure you always check the, or FAQ's Please remember, if you see a post that helped you, and it answers your question, please mark it as an 'Accept as Solution'.
Ipad Software Update
This forum reply or post is based upon my personal experience and does not reflect the opinion or view of my employer. Polycom employee participation within this community is not mandatory and any post or FAQ article provided by myself is done either during my working hours or outside working hours, in my private time, and may be answered on weekends, bank holidays or personal holidays.