My Topology here in the Lab started with a Standard Edition FE, and I later added an EE. Accordingly, the XDS is on the SE FE, which would be considered ‘unconventional’ in the outside world, and certainly highly undesirable if you’re aiming for high availability.
CU4 went on to the SE without any problems, but when I got to the EE server the Database Update failed with following error:
Here’s a cute one: after a period of inactivity the CX600 signs the user out and shows the following error:
“Sign-in Error. Account used is not authorized. Please contact your support team.”
I’m big on consistency, so who am I to break with tradition? Every OTHER blog on the internet has re-posted the links to CU4, so why should mine be any different?
Lync and Exchange will let you customise and import new recordings for various greetings, voice announcements, messages, etc.
Here are the respective requirements for the audio file formats. The source is hyperlinked or referenced beneath each item. Yes, some of this is a cut and paste job.
Just taking any old audio file and converting it as recommended/required below isn’t necessarily going to deliver an ideal or acceptable outcome. You might end up with sibilants (“ess-ing”) or quiet patches. Any commercial audio production house will be familiar with the tricks for phone production, but if you’re doing it yourself: Continue reading ‘Audio file formats for Lync and Exchange’ »
Updated 12th December 2011. (Scroll to the bottom)
We’ve found here in Oz with the UX that occasionally a random failure code from the carrier is enough to block the entire gateway.
The NET faithfully interprets the applicable standards, mapping the ISDN failure messages to their SIP equivalents, then sends the resulting message to Lync.
Unfortunately then Lync – itself also dogmatically sticking to the standards – decides that the message indicates a failure of the entire route/gateway, not just a single call, and temporarily blocks the gateway for all further outgoing call attempts.
This post is obsolete. ‘Profiles’ has been replaced by bounSky!
This post is WAAAAY obsolete. ;-) The latest Profiles post (1 Jan 2015) is here: https://greiginsydney.com/p4l-sticky/.
A free multi-user account management application for Lync.
If you’re following my exploits here you might have seen my “C-Change PHP” application, and the accompanying disclaimer “I’m not a programmer”.
I’m also not a C# programmer, and until a couple of months ago I’d never seen it before – and not programmed anything vaguely C-shaped since Granville TAFE almost 20 years ago, back in DOS where using ANSI colour was considered adventurous.
Still, with my usual stubbornness and determination (and plenty of help from several of my friends and the members of the Lync API forums) I’ve written “Profiles for Lync” (“Profiles”, or P4L for short).
This app fills what has been to date an annoying gap in the feature offer, especially for partners/integrators: with P4L it’s as easy as clicking a button to logout of Lync and log back in with another set of credentials – and even into another system!
Microsoft’s provided great, customisable training material for Lync. Download the Lync training intranet site and publish on your webserver, applying your own CSS to give them a look and feel consistent with the rest of your organisation.
If you don’t want to go to that effort, check out this link. From here you can drill down to individual pages that provide useful individual articles like:
This is one of those posts selfishly for my own use. Until I start to dream in Lync PowerShell commandlets I’ll be referring back to this one to get the syntax right.
Today I need to see how many users were homed to a particular Front-End server, and here’s the commandlet I used. It demonstrates filtering, piping and an output/display filter of sorts.
get-csuser -filter {RegistrarPool -eq "<FE FQDN>"} | Select-Object SamAccountName
And while we’re on the subject of piping and PowerShell, if you’ve not yet realised it, Lync can sometimes withhold information! If you "| fl" and the output wasn’t as interesting as you were hoping, you might find "| fl *" more fulfilling.
I’ve loved phones since I was a kid, and possess a small collection including my grandmother’s Commonwealth Ericsson and a candlestick, as well as the usual more modern plastic and Bakelite affairs. The mechanical aspects of payphones always fascinated me, so I have some of them here too.
I’ve had a “Pyramid” phone here for a while, wrapped in newspaper in a milk-crate, and I’ve been meaning to clean it up. Today was the day.
It’s been a while coming, but one of the bugs with the Lync Reskit’s “ABSConfig.exe” has finally been updated in a Hotfix for OCSCore.
http://support.microsoft.com/kb/2621857
The ABSConfig tool does not function correctly when you use the tool to customize the Address Book Service configuration or restore default attributes in Lync Server 2010
Strangely, it updates the Core Components to 4.0.7577.172 (from CU3’s .166) and leaves Reskit at “.0”.
I guess we won’t see a fix for the faulty operation of the “Which value of the phone number” radio buttons (which I blogged in March but raised with PSS in December) until we get a new build of ABSConfig.exe.
– Greig.