As of the writing of this article the most recent firmware release is from April 2013 (CU8 or 4.0.7577.4387).
Understand that although Microsoft officially supports Lync Phone Edition with Lync Server 2013 starting with this CU7 release it is often still possible to register directly to Lync Server 2013 environments with many older firmware versions.
Microsoft continues to release semi-quarterly Cumulative Updates of firmware for the various LPE models.In the round of releases in December 2012 and January 2013 (aka CU7) official support for Lync Server 2013 was added, as well dropping the ‘2010’ from the previous name of .This signals the intent to provide a single LPE client for both Lync platforms and not have separate 2010 or 2013 clients with different interfaces.What this all means is that to utilize any Lync Phone Edition devices with Lync Server 2013 the phone firmware may need updated to at least the CU7 release, which is version 4.0.7577.4363 / .4366 / .4372 for different device families.Attempts to use 1.0.522.x versions would always fail with As older versions of firmware may still be in use or come pre-installed on new devices then there may exist a scenario where the devices are unable to successfully sign-in to a Lync Server 2013 environment (specifically OCS 2007 RTM versions).
And because the only way to update the Lync Phone Edition firmware is by the device requesting and downloading the package from the Lync Server then this appears to be a cyclic problem.
How can a device which cannot register to the server download an update from the server when it needs to first register to be provided the device update server information?
This article is a brief update to the process previously documented for Lync Server 2010.
In Lync Server 2013 the Device Update service is unchanged and the steps shown in that article are still applicable, so why the need for a new post on this subject?
It is important to understand that although Lync Server 2013 brings a host of new 2013-branded clients (e.g.
Windows, Mobility), the (LPE) client was not updated in the same manner.