Polycom Cx700 Firmware Upgrade Lync

On

Auto Bringing up-to-date Polycom CX Design Cell phones - A Lesson Learned Dave Lighting Lately, we found out an issue with PoIycom CX500, CX600, and CX3000 design phones in our atmosphere. New phones and cell phones that were hard reset while troubleshooting problems would simply no longer enroll with Lync. As we were servicing through log data files on the phone, we noticed the adhering to error - 0x2F0D/0 on telephone = ERRORWINHTTPSECUREINVALIDCA. The time of this pointed to when we recently up to date both our internal and exterior Lync accreditation to Sha2. Searching in to articles online, this seemed to point to Entrust making use of new intermediate certificates in the string that the mobile phone did not possess as component of its firmware. We possess been implementing brand-new firmware to Polycom CX phone versions through Lync making use of the ucupdates package deal from Microsoft. This technique kept linked mobile phones up-to-date immediately and included the new intermediate certificates.

  1. Polycom Cx700 Drivers
  2. Firmware Upgrade Download

However, any cell phone that we attempted to set up out of the package was using an older firmware that did not have these accreditation. Furthermore, whenever we carried out a difficult reset to zero of the phone, it reverted back again to an old edition of the firmware that after that avoided the phone from applying with Lync. This reminded mé of the aged proverb, “Which came very first? The chicken or the egg?”. The mobile phone needs a brand-new firmware in purchase to sign up tó Lync, but we cannót get the update unless the phone is registered to Lync. This presents a little bit of a issue. Luckily, we found out there is a little known function on the mobile phones.

Upgrade Polycom cx600 firmware No lync. To my knowledge the phone and LYNC design does require a LYNC server in order to update the firmware and. Hello everyone, I am new to the site and am looking for some assitance. I have a Polycom CX3000 Lync conference room phone that authenticates to. A long and sad story about trouble upgrading the firmware in Office Communication Server enabled phones, specifically the Polycom CX700. This particular problem manifests itself as follows: The phone logs on to the server successfully and gets almost to the end of the login process.

Polycom Cx700 Drivers

During the shoe up and connection procedure, the phones check out for a report in your Lync environment known as ucupdates-r2 based off your domain name's FQDN. For example, if your internal domain can be ragnar.lothbrok.local, the telephone lookups for both ucupdatés-r2 and ucupdatés-r2.ragnar.Iothbrok.local. If it discovers DNS information that go with, the telephone will attempt to connect to this deal with to execute a firmware update.

Component of the verification process demands that these DNS information also become discovered on the inner Lync front side end certificate. Next, the needed DNS information were produced and during off hrs the Lync front end certificates were up to date to consist of the brand-new records in the additional SAN listing.

The revise appeared to proceed well and Lync gentle customers on Windows and Apple company registered normally. I snapped up a Polycom telephone out of the container, bootéd it up, and waitéd for a several mins. The phone rebooted on its very own and up to date itself with the fresh firmware. I was able to sign up the phone with Lync making use of both the pin authentication method, as properly as tethering a CX600 design mobile phone to my Computer and applying making use of the Lync soft client. The next time I had taken some cell phones to our satellite office and attempted to sign up them as well. I booted up the cell phone and waited a few mins, but nothing occurred.

Rebooted once again and waited a few more minutes. The phones would not really sign up with Lync. Searching in to the logs on the cell phone, I discovered an error stating that it could not find the Drink server FQDN. Searching at DHCP choices, they all appeared to be set correctly. On my computer I ran thé DHCPUtil.exe command word with the -emulateclient parameter. Medieval 2 total war stainless steel 6.4 download. This came back everything as expected, except the SIP FQDN had been lacking!

I reset to zero the DHCP choices several occasions, but it would not return the FQDN. During night time hours, I rebooted the domain control running DHCP. The next morning, I returned to our satellite office and bootéd up one óf the phones. After a few mins the mobile phone updated and I had been able to sign up it with Lync. DHCP options also returned the correct Drink FQDN environment.

All appeared to end up being going nicely until we began receiving reports of difficulty with some Lync reaction groups. Mobile phone calls to these reaction groups did not ring through to customers, but instead went straight to the tone of voice mail fixed up for the response team. I examined with my reaction team and some othérs.

They all worked normally. Searching through journal documents on both the Lync top end server and edge web servers, I found errors in the advantage server logs directing to certificates.

I after that recognized that when I up to date the Lync front end accreditation, they had been issued making use of a new California. All various other domain destined hosts and computers in our atmosphere respected this brand-new CA, as it acquired been pushed out through team plan.

Because the edge servers are not really domain limited, they certainly not received the fresh CA certification. I installed the brand-new CA chain on the edge computers, rebooted the entire Lync atmosphere immediately, and the response groups started working again. As a aspect take note, if there are usually other child websites that are usually part of the Lync atmosphere making use of Polycom CX phones, DNS information must be arranged up for thé ucupdates-r2 record, as well as included to the checklist of SANs ón the Lync top end certification. For example, ucupdates-r2.bjorn.lothbrok.regional.

Firmware Upgrade Download

Tech Talk Live Blog site Comment Recommendations:One particular of our major objectives at Tech Talk Live is to construct a community. It is definitely our hope that this blog can end up being a forum for conversation around our articles.

We see commenting as an integral component of this community. It enables everyone to take part, contribute, connect, and talk about relevant private encounter that provides value to the conversation. Respect counts. We believe you can take issue without being disagreeable.

Make sure you avoid from private attacks, title getting in touch with, libel/defamation, detest conversation, discriminatory or obscene/profane vocabulary, etc. Feedback should maintain to the subject at hand, and not really end up being promotional or industrial in character. Please perform not link to private blog articles, sites, or social media accounts that are irrelevant to the discussion. This will be considered self-promotion. We allowed hyperlinks that help further the conversation and preserve the best to delete those we consider needless.

The appearance of exterior links on this web site does not constitute established recommendation on behalf of Tech Talk Live or Lancaster-Lebanon More advanced Device 13. You are usually solely accountable for the content that you blog post - please make use of your greatest verdict. We arrange the best to remove content that perform not follow these guidelines.