Lync for Windows Phone update 5.6.1308.0_Release Date 12/10/2014

This Windows Phone update provides three defined options for VoIP calls; previously there were two options.

• VoIP always - Will use a Wi-Fi connection to place the call. If Wi-Fi is not available, the device will default to the cellular data plan (3G/4G).
• VoIP over Wi-Fi only - If available, the device will use a Wi-Fi connection to place the call. If Wi-Fi not available, Call Forwarding will be set to simultaneously ring your mobile phone number so that you can still receive work calls.
• Cellular - The device will default to the cellular data plan (3G/4G). Call Forwarding will be set to simultaneously ring your mobile phone number so that you can still receive work calls.

Mobile platform clients:

• Lync 2013 for Windows Phone
• Lync 2013 for iPad
• Lync 2013 for iPhone
• Lync 2013 for Android

November 11, 2014 updates for Lync 2013 now available

http://support2.microsoft.com/kb/2899507

Centralized Logging Service Agent (Error code - 20000, TCP error code 10061)

Issue: Centralized Logging Service Agent cannot start after you install September 2014 update for Lync Server 2013. You may experience one of two different issues with the Centralized Logging Service after applying the update.

• Centralized Logging Service Agent Service cannot start.
• Logging Service starts but you get Error code - 20000, TCP error code 10061.

Resolution: Apply October 2014 Cumulative Update 5.0.8308.831 for Lync Server 2013 core components.

http://support2.microsoft.com/kb/3003358/en-us

 Note: Build .815 no reboot required. Build .556 requires reboot.

Use command: Get-CSManagementStoreReplicationStatus to verify version.

Lync Client Update - August 2014

Link to August update for Lync client 

Version: 15.0.4641.1000

Calls failing at exactly 10 seconds

Check setting  "EnableFastFailoverTimer"

When set to True, outbound calls that are not answered by the gateway within 10 seconds will be routed to the next available trunk; if there are no additional trunks then the call will automatically be dropped. In an organization with slow networks and gateway responses, that could potentially result in calls being dropped unnecessarily.

The default value is True.

Set-CsTrunkConfiguration -Identity "site specific trunk" -EnableFastFailoverTimer $false"