Haiku #86
Published May 20 2019 03:23 PM 111 Views
Occasional Visitor
First published on TECHNET on Apr 11, 2011

Blacks clouds gather and

The rain threatens. So what? We

Have the language list.

It's another Monday morning here at the international headquarters of the Lync Server PowerShell blog and, in addition to posting this week's Lync Server PowerShell Challenge , we're mostly just sitting around waiting for it to start raining. Sadly, the idea that it's going to rain has become pretty much a foregone conclusion here. In March, it rained on 28 of the 31 days. So far in April, we've already had about 2 ½ inches of rain; a typical April gets barely over 1 inch of rain for the whole month. Yesterday the author of today's haiku was driving along the freeway and he had to put his sun visor down because the sun was so bright. And yet, at the same time, he had to have his windshield wipers going because it was raining pretty hard, even though the sun was shining !

That's the kind of year we've been having so far.

True story . Several years ago the author of today's haiku was out working in his front yard when his son, who was probably about 7 or 8 at the time, came running into the front yard all excited and saying, "Dad, Dad! You gotta come in the back yard and see this!" When Dad went into the back yard he discovered that it was raining reasonably hard in the back yard. The front yard? Dry as a bone. The back yard? Raining cats and dogs.

Hmmm, good question: why does anyone want to live here?

Of course, you might think that all this rain would leave everyone in the Seattle area miserable and depressed. And, to be honest, that used to be the case. But that was before Microsoft created the Get-CsDialInConferencingLanguageList cmdlet. Now any time we get depressed we just start running the Get-CsDialInConferencingLanguageList cmdlet and all our troubles just seem to disappear. Ahhh ….

So what exactly is the Get-CsDialInConferencingLanguageList cmdlet? Well, as you probably know, Lync Server 2010 enables users to join conferences by using a plain old telephone; these dial-in users cannot view video or exchange instant messages, but they can participate fully in the audio portion of the meeting. When you dial in to a conference, the first thing that happens is this: you hear a welcome message, and then you're given some instructions on how to join the meeting. (For example, you might be asked to state your name and then press the pound [#] key.)

In addition to that initial welcome, there might be other times during the meeting that Lync Server needs to relay information to you; for example, if you press 1 on your telephone keypad Lync Server will read a list of all the other keypad options available to you.

And yes, that is pretty darn neighborly, isn't it?

Of course, that leads to at least one question: what language is Lync Server going to use to relay these instructions and to recite that welcome message? And the answer to that question is this: it depends. Lync Server supports a number of different languages for use with dial-in conferencing, and it's up to administrators to configure the language (or languages) that will be assigned to a given dial-in access number.

Note . No, sorry, we won't talk about configuring dial-in access numbers today; that's something we'll have to cover in a future haiku. If you can't wait until then, however, take a peek at the help topic for the New-CsDialInConferencingAccessNumber cmdlet.

So what languages are available for use with dial-in conferencing? That's where the Get-CsDialInConferencingLanguageList cmdlet comes in. The Get-CsDialInConferencingLanguageList cmdlet has just one purpose in life: it returns the list of languages that are available for use with dial-in conferencing. For example, suppose you run this command:


Here's what you'll get back:

Identity : Global

Languages : {da-DK, de-DE, en-AU, en-GB…}

Which, now that you mention it, is only of limited value, isn't it? After all, there are approximately 20 languages available for use, but only four or so of those languages appear onscreen. How can you get at the complete list of languages? Try running this command instead:

Get-CsDialInConferencingLanguageList | Select-Object –ExpandProperty Languages

That will give you output that looks like this:





















Which is a little more like it.

Now for a few quick notes about these languages. At this point in time, this is the set of languages; there's no way for an administrator to add additional languages to the list. (You'll note that there is no Set-CsDialInConferencingLanguageList cmdlet.) Because you can't add (or remove) languages from the list, that also means you have only one global list of languages: there's no ability to create new languages at, say, the site scope. (Nor is there any need to, seeing as how any site-scoped lists would have to be identical to the global list.)

You might also note that the languages are listed using a standard language code (like en-AU for Australian English). If you aren't sure what those codes stand for, take a peek at this page on MSDN. Or, if that's too much trouble, refer to this table instead:

Language Code



Danish - Denmark


German - Germany


English - Australia


English - United Kingdom


English - United States


Spanish - Spain


Spanish - Mexico


Finnish - Finland

Version history
Last update:
‎May 20 2019 03:24 PM
Updated by: