Lync 2013 Client Update – December 2014

Hot on the heels of – and fixing a bug introduced *in* – November’s, we now have a December update to the Lync 2013 client. Read all about kb2910927 here.

This update takes the Lync 2013 Client to 15.0.4675.1000/1002.

What’s Fixed?

  • kb3017596 Sharing session stops in Lync 2013 when the display resolution of a shared monitor is changed
  • kb3004595 E.164 normalized telephone numbers are not displayed in Lync 2013 contact cards or the “Call” menu

Continue reading ‘Lync 2013 Client Update – December 2014’ »

Lync Server 2013 Update – December 2014

Another one! We seem to be on a three-weekly cycle at the moment! (November’s I wrote up here).

This update takes Lync Server 2013 from 5.0.8308.834 to 5.0.8308.857.

What’s Fixed?

Of the four MSIs in this update, only ONE has any specific fixes mentioned, with the others containing the usual improvements to the “reliability, stability, and performance” of the product. Here are the fixes we know of:

  • kb3018165 Agents in a response group cannot receive a call in a Lync Server 2013-based Lync client
  • kb3018167 External user cannot sign in to a Lync client by using a SIP address of a new domain in a Lync Server 2013 environment

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

Telstra SIP Connect IP Addresses

If you’re deploying a gateway and interfacing to Telstra’s Australian “SIP Connect” SIP trunk service you’ll need to know a few values. Most of the below you’ll get from the relevant Telstra and/or gateway integration guides.

Each state and territory has its own SBC and Telstra STRONGLY prefers you reference these by their host name and use Telstra’s DNS to resolve this. Their requirement here is that you add a conditional forwarder to your corporate DNS for the “nipt.telstra.com” domain.

Domain DNS forwarder IP
nipt.telstra.com 203.52.0.221 203.52.1.222

The above isn’t to every customer’s liking, or it’s perhaps not something they’re able to do in the required timeframe. Your alternative or temporary workaround is to take the potentially risky step of hard-coding the IP address into the gateway’s Hosts table. Continue reading ‘Telstra SIP Connect IP Addresses’ »

A Look at the Yealink T48G for Lync

Yealink’s not a brand you normally associate with Lync and the corporate end of town, but perhaps as an indicator of the strength of the Lync brand they’ve thrown their hat into the ring and released two phone models with firmware for Lync.

I managed to get my mitts on the high-end “T48G” and thought I’d take it for a spin.

OOB Experience

Out of the box it looks quite a respectable piece of kit, albeit perhaps a little large at 26.5cm/10.5” wide. The desk stand only has the one position, but that seemed to work for me.

Yealink-BoxShot

I was surprised to find that the angle of the display isn’t adjustable. The look of it, with a gloss surround set into a matt phone body screamed “adjust me”, but alas it was for nought.
Continue reading ‘A Look at the Yealink T48G for Lync’ »

Sonus SBC 1k/2k v4 firmware

One of the significant edges that the Sonus SBC 1k/2k (nee UX 1000 and UX 2000) voice gateways / Session Border Controllers have over the competition is the real-time visibility of calls. You can sit back and watch them as they delicately twinkle into existence and later clear, or have your adrenalin rush as you see channel after channel seized when your imperfect config results in a routing loop.

RealTimeMonitor - the old way

This functionality has however been cursed to date (and blocked in many a deployment) by a reliance on Java. No more.

Continue reading ‘Sonus SBC 1k/2k v4 firmware’ »

Lync Server 2013 Update – November 2014

As Michael LaMontagne so succinctly put it on Twitter, the monthly CU’s we’ve been seeing recently are to make up for the dearth of them at the start of the year. And so it is that three weeks after the October update we have another, this time taking Lync Server 2013 from 5.0.8308.831 to 5.0.8308.834.

What’s Fixed?

Of the seven MSIs in this update, only three have any specific fixes mentioned, with the rest containing the usual improvements to the “reliability, stability, and performance” of the product. Here are the fixes we know of:

  • 3010330 Response group usage report displays incorrect amount of offered calls and answered calls in Lync Server 2013
  • 3014834 Lync Web App users are disconnected to a video meeting on a Mac device in a Lync Server 2013 environment
  • 3010327 Event 36023 is consistently logged on multiple front-end servers in a Lync Server 2013 environment that enables CAC

Continue reading ‘Lync Server 2013 Update – November 2014’ »

Lync 2013 Client Update – November 2014

We have a November update to the Lync client. Read all about KB2899507 here.

This update takes the Lync 2013 Client to 15.0.4667.1000/1001.

What’s Fixed?

  • 3010340 Video freezes consistently for two second-intervals when you make a video call in Lync 2013
  • 3009723 Incorrect format of string in a trace statement when application sharing session viewers stop viewing in a conference
  • 3009722 Memory leak occurs when you start a peer-to-peer application sharing session in Lync 2013
  • 3009721 Lync 2013 crashes when you join a meeting that is hosted on Lync Server 2010 as an anonymous user
  • 3009719 Lync 2013 freezes when a toast notification of a call appears

Continue reading ‘Lync 2013 Client Update – November 2014’ »

Lync ‘vNext’ is “Skype for Business”

s4b

Since paying US$8.5Billion for Skype back in 2011, Microsoft’s been slowly absorbing its technology into the existing Lync product. Last year we saw Federation between Skype and Lync (albeit with some caveats), this year it was the inclusion of Skype’s “SILK” codecs into the Lync clients, and now today it’s official: “vNext” of Lync (to be released next year) will be “Skype for Business”.

Here’s the official announcement.

Matt Landis has written a great post on the subject, collating the publicly-available information into a nice features list.

 

Continue reading ‘Lync ‘vNext’ is “Skype for Business”’ »

Lync Server 2013 Update – October 2014

The only thing better than a CU for Lync is a CU that contains fixes you personally recognise. And so it is with this update. An October 2014 update for Lync Server 2013 has landed, taking the Server from 5.0.8308.815 to  5.0.8308.831.

What’s Fixed?

Only the Front-End, Edge & Core Components get a refresh in this update. Here are the fixed bits:

  • 3003346 Cannot see presence status or send instant messages when OWA is integrated with Lync Server 2013 instant messaging
  • 3003347 User cannot dial out to a PSTN number as a guest in an online meeting in a Lync Server 2013 environment
  • 3003350 Cannot search users by using a keyword that differs from Lync Server 2013 AD DS display name format in a Lync client
  • 3003347 User cannot dial out to a PSTN number as a guest in an online meeting in a Lync Server 2013 environment
  • 3008181 Centralized Logging Service Agent Service cannot start after you install a September 2014 update for Lync Server 2013

Continue reading ‘Lync Server 2013 Update – October 2014’ »

Lync Phone Edition Update – October 2014

We have a new update for Lync Phone Edition, although its benefit is rather localised. This LPE firmware update takes us from 4.0.7577.44451 to 4.0.7577.4455.

Timezone Updates

Quoting from the KB:

This update adds the following new time zones for Lync Phone Edition telephones:

  • N/A (UTC+04:00) Izhevsk, Samara (RTZ3)
  • N/A (UTC+11:00) Chokurdakh (RTZ10)
  • Kamchatka Standard Time (obsolete) (UTC+12:00) Anadyr, Petropavlovsk-Kamchatsky

This update also updates the following time zones:

  • Kaliningrad Standard Time (UTC+02:00) Kaliningrad (RTZ1)
  • Russian Standard Time (UTC+03:00) Moscow, St. Petersburg, Volgograd (RTZ2)
  • Ekaterinburg Standard Time (UTC+05:00) Ekaterinburg (RTZ4)
  • N. Central Asia Standard Time (UTC+06:00) Novosibirsk (RTZ5)
  • North Asia Standard Time (UTC+07:00) Krasnoyarsk (RTZ6)
  • North Asia East Standard Time (UTC+08:00) Irkutsk (RTZ7)
  • Yakutsk Standard Time (UTC+09:00) Yakutsk (RTZ8)
  • Vladivostok Standard Time / Magadan Standard Time (UTC+10:00) Vladivostok, Magadan (RTZ9)

This update removes the existing UI entry for (GMT+12:00) Magadan, because Magadan is already covered in Vladivostok Standard Time / Magadan Standard Time.

Continue reading ‘Lync Phone Edition Update – October 2014’ »