Microsoft has released CU January 2014 for Lync Server 2010/2013 & Lync Edition Phones

Microsoft has released updates for Lync Server 2013 and Lync Server 2010 on time for their quarterly release cadence. The updates are bug fixes to the product and not introducing new features (none of the 2013 databases are updated in this release). If this CU is being applied to RTM, then follow the instructions here to update or check your version level using Doug Deitterick’s blog post.

In addition to the server patches, the Debugging Tools and Resource Kit has been updated. Unfortunately the updates are actually full installs so you will need to uninstall any previous versions before the apps are “updated”. The good news is the Debugging Tools contain the correct updated TMX file from the January 2014 CU so there is no need to manually replace it with the locally installed copy.

Finally, Lync Edition phones have been update which include the entire line of Aastra, HP, and Polycom phones. Updating them is the same method it has been so no news there.

Product

Version

KBs

Download

Lync Server 2013

5.0.8308.577

2809243

MS Download

Lync Server 2013 Debugging Tools

5.0.8308.577

2905051

MS Download

Lync Server 2013 Resource Kit Tools

5.0.8308.577

2905053

MS Download

 

 

 

 

Lync Server 2010

4.0.7577.225

2493736

MS Download

Lync 2010 Client 32-bit

4.0.7577.4419

2912208

MS Download

Lync 2010 Client 64-bit

4.0.7577.4419

2912208

MS Download

 

 

 

 

Lync Phone Edition: Aastra 6721ip / 6725ip

4.0.7577.4420

2918033

MS Download

Lync Phone Edition: HP 4110 / 4120

4.0.7577.4420

2918035

MS Download

Lync Phone Edition: Polycom CX500 / CX600 / CX3000

4.0.7577.4420

2918038

MS Download

Lync Phone Edition: Polycom CX700 / LG-Nortel 8540

4.0.7577.4420

2918036

MS Download

Additional Notes:
Lync Server 2010 build number is 4.0.7577.225
Lync 2010 Client build number is 4.0.7577.4419
Lync Server 2013 build number is 5.0.8308.577
Lync 2013 Client build number is 15.0.4551.1007
Lync Group Chat build number is 4.0.7577. 4409
Lync Group Chat Server build number 4.0.7577. 4409
Lync Group Chat Admin build number 4.0.7577. 4409
Lync Attendee build number is 4.0.7577.4356
Lync Attendant build number is 4.0.7577.4098
Lync Phone Editions build number is 4.0.7577.4420
Lync 2010 for iPhone build number 4.7
Lync 2010 for iPad build number 4.7
Lync 2010 for Android build number 4.0.6509.3001
Lync 2013 for Windows Phone build number is 5.2.1072.0
Lync 2013 for iPad build number is 5.2
Lync 2013 for iPhone build number is 5.2
Lync 2013 for Android build number 5.1.0000
Lync Basic 2013 build number is 15.0.4420.1017
Lync VDI 2013 build number is 15.0.4420.1017

Your Smartphone – the New Lync Portable Phone

With the recent release of the various Lync 2013 mobile clients a new wave of Lync desktop and portable phones have come into play. Yes – desktop and the concept of a portable phone – all available for Lync 2013. How you ask? Quite simply.

With the new Lync 2013 mobile client allowing you to hold VoIP calls natively and its ability to interact with the system, you end up with two calling scenarios.

1)      You are on a call using your laptop/desktop/Aries phones. You realize you need to ‘leave’ your desk and you have the Lync 2013 mobile client installed on your smartphone. From the full Lync client, you park the call, enter the retrieval code into your mobile client (i.e. within the Lync dialer itself) and it retrieves the call. Very nice – you can move any Lync call from your desktop Lync client or Aries phone to your smartphone.

2)      You use the smartphone as your desk phone. Assuming you have wireless (and who doesn’t) sign-in to the Lync 2013 mobile client. All incoming calls will ring on your smartphone as well – just answer it.

The second option is how we replace a desktop phone with your smartphone. You could also use a Bluetooth headset paired with your smartphone making it a complete mobile package. There are a few things to consider however.

1)      The smartphone is VoIP – that means data. If you are using the smartphone on your cellular data network, you are using your data allotment. That may or may not be a problem, but here in the US most mobile phones have unlimited calling/phone minute plans but the data plans are restricted.

2)      If you answer/transfer the call while you are using the corporate Wi-Fi, that call is tied to the IP and network of that Wi-Fi. Leaving the facility or range of Wi-Fi means the call would need to switch to cellular, IP would change, and call would drop. I would bet that something is done to address this by a third-party sometime soon – something like NetMotion offers on the desktop (if not a solution from NetMotion themselves).

3)      Unfortunately the Lync 2013 mobile client lacks the ability to transfer the call back to the call park service – something I suspect will come in time. So, once the call is answered or transferred to the smartphone that is where it lives.

For a desktop or mobile replacement within the office, the issues above are non-existent. Using the new client you have another means to answer your calls and remain portable (not to mention a single phone device). For those looking for a means to use the smartphone as a way to start in the office and then leave we have a workable yet restricted solution. The key would be to make sure your Wi-Fi is OFF prior to transferring the call. This way, when you leave the office you are already on the cellular data network (just make sure you have the cellular data MB available). The last option of course is to simply transfer the call over PSTN to your smartphone. The real cost there will depend on your cellular plan and remember, you are tying up two phone lines (and Lync resources) as the Lync server infrastructure is conferencing the outside call and your smartphone call.

Try it out – play with the new mobile client – make an audio and video call from it – it is simply amazing and it opens up all kinds of possibilities and scenarios.

New Lync Aries Series Phone Reboots

Recently I was working with a client who was moving to a native Lync 2010 Enterprise Voice solution; a very exciting project and one that involved replacing an Avaya phone switch and the desktop phones with Lync and Polycom CX500CX600, and CX3000 phones. In addition to the new phone hardware, there was a switch upgrade happening at the same time to provide PoE to all of the desks. Cisco Catalyst 3750 switches were purchased and used for the new desktop switching which also supported the LLDP-MEP option for VLAN segregation (rather than the DHCP scope options).

Everything appeared to be going great until the next day. We noticed that in the morning as soon as the user unlocked their workstation or touched the phone it would reboot. Not a great result especially since we were using the Ethernet pass-through switch port on the back of the CX600 phones for the user's computer.

As it turns out, the issue dealt with the power saving modes of the Aries Phones and a PoE/LLDP-MEP compatibility issue. There are three stages of power on the phones, full, idle, and sleep. When the phones were jumping from sleep to full (at workstation unlock or touching a key) they jump an additional 2w. The Cisco switches, because LLDP-MEP was being used, knew the devices were phones and in a prevention action saw the jump as a surge and killed power to the port (thus the reboot).

The solution was simple - disable LLDP-MEP on the Cisco switches globally and add the DHCP options to assign the voice VLAN. Once this was done the phones remained up and all was well.

Thanks to Dave Howe of Microsoft PSS and Jeff Schertz of Polycom for pointing us in the right direction.