Sonus Updates Tenor Config Manager

As outlined in my previous post, the old “Quintum” Config Manager app has just scored an update to match some of the new/changed values in the firmware.

It’s significant if you’ve been around the traps for a while because Sonus has used this as an opportunity to finally replace the old NET and Quintum branding.

What’s Changed?

What, other than the branding and colours you mean?

  • It installs by default to a new path: C:\Program Files (x86)\Sonus Networks\Tenor Configuration Manager
  • Some new prompts (as outlined in the readme for P108-09-32).

Continue reading ‘Sonus Updates Tenor Config Manager’ »

Sonus Tenor Firmware P108-09-32 – January 2016

The old Tenor doesn’t see a lot of attention these days, but they’re still out there providing reliable analog and BRI port interfaces across the planet.

We’ve recently seen an update to the Tenor firmware to P108-09-32, up from this time 2 years ago when we saw P108-09-26.

The ReleaseNotes readme is no longer in the download bundle having moved to the Sonus support website (and to which you may not have access)*:

Continue reading ‘Sonus Tenor Firmware P108-09-32 – January 2016’ »

Lync 2013 / SfB 2015 Client Update – January 2016

This January update (Kb3114502) takes the Office 2013-based Lync/SfB client from 15.0.4779.1001 to 15.0.4787.1001.

What’s Fixed

This update fixes the following issues:

  • Kb3128747 Video is missing in a Skype for Business 2015 meeting recording after the December 2015 security update 3114351 is installed
  • Kb3121276 Title bar displays “Lync” after you install the November 2015 update for Lync 2013 (Skype for Business 2015)
  • Kb3132307 Event ID 1000 is logged and Lync 2013 (Skype for Business) client crashes when you reconnect a remote session
  • Kb3132305 “An unknown participant is now joining” message is displayed in a transferred call in Lync 2013 (Skype for Business)
  • Kb3132304 The Lync 2013 (Skype for Business) user interface of a call monitor flashes constantly
  • Kb3114687 “The address type is not valid” error when you sign in to Lync 2013 (Skype for Business) by using domain\username format

Continue reading ‘Lync 2013 / SfB 2015 Client Update – January 2016’ »

Lync Server 2013 Update – January 2016

This update takes two components on the server from 5.0.8308.941 to 5.0.8308.945, although – as with the December update that gave us .941 – I’m still struggling to see the point of one of them.

What’s Fixed?

It looks like the sole (documented) fix is for the Web Components and relates to the “You can’t join a meeting … on iOS 9” issue we first saw patched in the October update as Kb 3097592. It seems iOS 9.2 broke it again, and thus we now need Kb 3126487.

  • Kb 3126638 (Web Components server). This cumulative update resolves an issue that prevents you from joining a meeting from outside Lync 2013 for iPhone or Lync 2013 for iPad on iOS 9.2.
  • Kb 3126637 (Core Components). This cumulative update resolves the issues that were previously discussed in the following Microsoft Knowledge Base articles…

Continue reading ‘Lync Server 2013 Update – January 2016’ »

Lync Server 2013 Update – December 2015

This update takes the server from 5.0.8308.933 to 5.0.8308.941, although I’m struggling to see anything that’s actually fixed or changed at this stage.

What’s Fixed?

Nothing apparently! According to the kb articles, this cumulative update simply resolves issues that have previously been resolved in earlier updates this year!

What’s New?

Nothing apparently.

Download

Continue reading ‘Lync Server 2013 Update – December 2015’ »

Lync Phone Edition Update – December 2015

This update takes Phone Edition to 4.0.7577.4487 / 4488 & adds SHA-2 support.

There doesn’t seem to be an over-arching KB that goes into any more detail (that I can find), just David Paulino’s post on the UC Lobby page on TechNet:

This update for Microsoft Lync Phone Edition devices adds support for the SHA-2 suite of digest hash and signing algorithms for connections from clients. The SHA-2 protocol uses digest lengths of 224, 256, 384, or 512 bits. After you apply this update, Lync Phone Edition devices can be connected to a Microsoft Lync server that contains a certificate that is issued from the same Certification Authority (CA).

Download the relevant CAB files from here:

Revision History

9th December 2015: This is the initial post.
10th December 2015: Updated version numbers to reflect changes in the KB articles since yesterday. (Thanks Richard!). Firmware loaded into Lync 2013 using http://www.ehloworld.com/1217 and all version numbers above confirmed correct.
 
-G.

SfB 2016 Client Security Update – December 2015

This week’s security update also covers the Office 2016 client for SfB.

Kb3114372: “MS15-128: Description of the security update for Skype for Business 2016: December 8, 2015

This security update resolves vulnerabilities in Skype for Business 2016 that could allow remote code execution if a user opens a specially crafted document or visits a webpage that contains specially crafted embedded fonts. To learn more about these vulnerabilities, see Microsoft Security Bulletin MS15-128.

For a complete list of affected software, see Microsoft Knowledge Base article 3104503.

Continue reading ‘SfB 2016 Client Security Update – December 2015’ »

Lync 2013 / SfB 2015 Client Security Update – December 2015

This week’s security update takes the Office 2013-based Lync/SfB client from 15.0.4771.1001 to 15.0.4779.1001.

Kb3114351 "MS15-128: Description of the security update for Lync 2013 (Skype for Business): December 8, 2015

This security update resolves vulnerabilities in Microsoft Lync 2013 and Skype for Business. The vulnerabilities could allow remote code execution if a user opens a specially crafted document or visits a webpage that contains specially crafted embedded fonts.

To learn more about the vulnerabilities, see Microsoft Security Bulletin MS15-128.

For a complete list of affected software, see Microsoft Knowledge Base article 3104503".

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

SfB 2015 CU1 Server Update – November 2015

Just to keep us on our toes and to confuse those of us who – like Andrew – keep a rolling “CU” count of updates, Microsoft’s just released the third server update for Skype for Business 2015 and officially labelled it  “CU1”. I know; just go with it.

This update (Kb3061064) takes the server from 6.0.9319.88 to 6.0.9319.102, with lots of components affected.

What’s Fixed?

The Kbs contain lots of broad-sweeping “this cumulative update improves the reliability, stability, and performance of Skype for Business Server 2015” without going into detail. These are the named fixes:

  • Kb3095143 This cumulative update resolves an issue in which Windows 10 users who use Edge can’t join a meeting from Skype for Business Web App
  • Response Group issues:
    • Kb3092726 Holiday set names conflict when you run the Move-CsRgsConfiguration cmdlet in Skype for Business Server 2015
    • Kb3092728 Event ID 31128 when RGS can’t synchronize an Agent Group member’s SIP address in Skype for Business Server 2015
    • Kb3092729 High CPU usage after you publish a changed topology in Skype for Business Server 2015 with the Response Group Service
    • Kb3092730 Response group usage report takes longer to run or cannot complete in a Skype for Business Server 2015 environment

What’s New?

Continue reading ‘SfB 2015 CU1 Server Update – November 2015’ »

Quick Tip: Am I SE or EE?

I occasionally find myself thrown into a strange Lync or SfB environment – sometimes it’s even a TeamViewer session – and I need to hit the ground running and start discovering what’s going on.

Quicker than running up Topology Builder or wading through the output of Get-CsPool, “Get-CsComputer –Local” will tell you very quickly if the machine you’re on is a Standard Edition or Enterprise Edition.

PS C:\> Get-CsComputer -Local

Identity : sfb2015fe.contoso.local
Pool     : sfb2015fe.contoso.local
Fqdn     : sfb2015fe.contoso.local

PS C:\>

If all three values are the same, you’re on an SE machine – and if it turns out to be an EE server, its pool will be identified for you too!