Default Sonus SBC cause codes “protect” against re-routing

I’ve long been a fan of the “Easy Config Wizard” in Sonus’ SBC 1k, 2k and now SWe Lite devices. With very few exceptions, all of my SBCs are deployed from scratch using it. If you’re not familiar with it, it presents you with a few basic questions and when you click Finish it sets …

Continue reading ‘Default Sonus SBC cause codes “protect” against re-routing’ »

Lync 2013 / SfB 2015 Client Update – August 2017

It’s been 3 weeks since our last update to the Office 2013-based Lync/SfB client. Today we go from 15.0.4945.1000 to 15.0.4953.1000, aka Kb 4011046. What’s Fixed A handful of items are addressed in this update: Kb 4035431 “Call forwarding settings failed” dialog occurs after you sign out Skype for Business 2015 (Lync 2013) if RCC …

Continue reading ‘Lync 2013 / SfB 2015 Client Update – August 2017’ »

Lync 2013 Server Update – July 2017

This July update takes the server to 5.0.8308.992 from March’s 5.0.8308.987. This time ’round 6 components receive an update – and its mysteries have me VERY curious… What’s Fixed? Kb 4034279 Enables the “Move-CsMeetingRoom” cmdlet to move a meeting room from on-premises to Online in Lync Server 2013 Kb 4023333 Peer to peer application sharing …

Continue reading ‘Lync 2013 Server Update – July 2017’ »

Lync 2013 / SfB 2015 Client Update – July 2017

It’s been 3 weeks since our last update to the Office 2013-based Lync/SfB client. Today we go from 15.0.4933.1000 to … 15.0.4933.1000 – although the article (kb3213574) and other evidence – see below – confirms it’s 15.0.4945.1000. What’s Fixed This one contains a solo update: Kb 4032344 Low Internet Explorer performance when Skype for Business …

Continue reading ‘Lync 2013 / SfB 2015 Client Update – July 2017’ »

ClsLogger.EXE Crashes with Unhandled Exception

TLDR: I think it’s broken – or as James Arber implied on Twitter, it might have made it out the gate prematurely. My suggestion: Do not install this version! Out of the blue recently Microsoft updated the Skype for Business 2015 Debugging Tools version from 6.0.9319.73 to the interestingly-named (well, numbered) 7.0.1678.1.1. Before you can …

Continue reading ‘ClsLogger.EXE Crashes with Unhandled Exception’ »

Lync 2013 / SfB 2015 Client Security Update – June 2017

It’s been 3 months since our last security update to the Office 2013-based Lync/SfB client, and five weeks since this one. Today we go from 15.0.4927.1000 to 15.0.4933.1000. It addresses a risk of remote code execution. Kb 3191939: This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user …

Continue reading ‘Lync 2013 / SfB 2015 Client Security Update – June 2017’ »

SfB 2015 Server Update CU5 – May 2017

This May 2017 update takes the server from 6.0.9319.277 to 6.0.9319.281 & updates 8 components on my Standard Edition Front-End. What’s Fixed? Kb4020997 Skype for Business Server 2015 Front-End service may crash in Windows Server 2016 Kb4020994 Event ID 36023 is consistently logged on Multiple Front-End servers in a Skype for Business Server 2015 environment …

Continue reading ‘SfB 2015 Server Update CU5 – May 2017’ »

Lync 2013 / SfB 2015 Client Update – May 2017

Our May update to the Office 2013-based Lync/SfB client (Kb 3191876) follows last month’s update and takes us from 15.0.4919.1000 to 15.0.4927.1000. What’s Fixed This update fixes the following issues: Kb 4019641 Updates the meeting invitation to let mobile client join PSTN calls with one-tap in Skype for Business 2015 (Lync 2013) Kb 4019640 Hebrew …

Continue reading ‘Lync 2013 / SfB 2015 Client Update – May 2017’ »

Lync 2013 / SfB 2015 Client Update – April 2017

Our April update to the Office 2013-based Lync/SfB client (Kb 3178731) follows last month’s Security Update and takes us from 15.0.4911.1000 to 15.0.4919.1000. What’s Fixed This update fixes the following issues: Kb 4016107 Supports to join a meeting in Lync Web App when you don’t sign in to Skype for Business 2015 (Lync 2013) Kb …

Continue reading ‘Lync 2013 / SfB 2015 Client Update – April 2017’ »