Tom Talks Microsoft Teams and Microsoft 365 news and opinions

Taglync

Walkthrough of NET UX1000 Survivable Branch Appliance setup for #Lync

Here are some quick screenshots walking through the setup of a UX1000 with the SBA module for Lync. From a setup point of view you can think of Gateways with SBA’s as 2 devices in one. Where net particularly excels is making it nice and easy to setup both the “gateway” and “SBA” from one Web interface. As you will see on the walkthrough the setup process is pretty fluid. This walkthrough is on a...

Microsoft Q1 2012: Lync revenue grew by 25% year on year

Microsoft released their Q1 2012 earning report. You can get the full report and slides at that link. I’m pleased to say Lync Revenue has grown 25% year on year. From the Transcript “Collaboration and communication continued to be a pillar of strength to our Office business. Lync, SharePoint and Exchange collectively grew double digits. Lync revenue grew over 25% as customers increasingly chose...

How to Upgrade the Firmware on an net UX gateway

The net UX is the newest gateway from net. Details on the UX are available here It is all web based, and I have to say the Web UI is pretty good, making it much easier to manage than the previous VX gateway with a combo of apps telnet (although with the apps and telnet comes a lot of flexibility). Firstly you will need the latest firmware, which you can get from the net website with the...

MS-Diagnostic Errors

Following on from my previous post on Lync Client errors, here is a list of ms-diagnostic errors from SIP clients. (v=office.12).aspx Note that the following placeholder is used in these messages: [user name] is used in place of an actual user name. [client name] is used in place of the name of the SIP protocol client Mode Error ID Error Message Additional Information Diagnostic reason IM 0 This...

Lync Client Error Codes

I was troubleshooting a client error which I hadn’t seen before “Call was not transferred because [user name] does not have an audio device set up to accept calls.” In this case, the error was a little misleading. The endpoint the customer was transferring to was fine, and it was happening to more than one user. In actual fact this was a SIP Refer issue. As soon as we disabled SIP refer on the...

Tom Talks Microsoft Teams and Microsoft 365 news and opinions