Configuring Dial Plans and Normalization Rules

 

Create a Dial Plan

 

• To create a dial plan

 

To create a new dial plan, use the New-CsDialPlan cmdlet:

 

New-CsDialPlan -Identity site:Redmond -SimpleName RedmondSiteDialPlan

 

The following command creates a new dial plan, then uses the New-CsVoiceNormalizationRule cmdlet to immediately add a new normalization rule to that dial plan:

 

New-CsDialPlan -Identity site:Redmond -SimpleName RedmondSiteDialPlan

 

New-CsVoiceNormalizationRule -Identity "site:Redmond/SeattlePrefix" -Pattern "^9(\d*){1,5}$" -Translation "+1206$1"

 

 

Modify a Dial Plan

 

• To modify a dial plan

 

To modify a dial plan, use the Set-CsDialPlan cmdlet:

 

Set-CsDialPlan -Identity RedmondDialPlan –ExternalAccessPrefix 8

 

 

For more information

 

• Haiku #92: The CsDialPlan Cmdlets
• The Edit Dial Plan Dialog
• The New Normalization Rule Dialog

 

 

 

 

Create or Modify a Normalization Rule Manually

 

• To define a normalization rule manually

 

To create a new voice normalization rule, use the New-CsVoiceNormalizationRule cmdlet. The following rule has the name SeattleFourDigit and will be assigned to the dial plan SeattleUser:

 

New-CsVoiceNormalizationRule -Parent SeattleUser -Name SeattleFourDigit -Description "Dialing with internal four-digit extension" -Pattern '^(\d{4})$' -Translation '+1206555$1'

 

For more information

 

• The New Normalization Rule Dialog

 

 

 

 

Configuring Voice Policies, PSTN Usage Records, and Voice Routes

 

Configuring Voice Policies and PSTN Usage Records to Authorize Calling Features and Privileges

 

Create a Voice Policy and Configure PSTN Usage Records

 

• To create a voice policy

 

To create a new voice policy, use the New-CsVoicePolicy cmdlet:

 

New-CsVoicePolicy –Identity UserVoicePolicy2 -AllowSimulRing $False -PstnUsages @{Add = "Local"}

 

 

Modify a Voice Policy and Configure PSTN Usage Records

 

• To modify a voice policy

 

To modify an existing voice policy, use the Set-CsVoicePolicy cmdlet:

 

Set-CsVoicePolicy UserVoicePolicy2 -AllowSimulRing $False -PstnUsages @{add = "Long Distance"}

 

 

View PSTN Usage Records

 

• To view a PSTN usage record

 

To view all your PSTN usage records, use the Get-CsPstnUsage cmdlet:

 

Get-CsPstnUsage | Select-Object –ExpandProperty Usage

 

 

Configuring Voice Routes for Outbound Calls

 

Create a Voice Route

 

• To create a voice route

 

To create a new voice route, use the New-CsVoiceRoute cmdlet:

 

New-CsVoiceRoute -Identity Route1 -PstnUsages @{add="Long Distance"} -PstnGatewayList @{add="PstnGateway:redmondpool.litwareinc.com"}

 

 

Modify a Voice Route

 

• To modify a voice route

 

To modify a voice route, use the Set-CsVoiceRoute cmdlet:

 

Set-CsVoiceRoute -Identity Route1 -Description "Test Route"

 

The following commands use both the Get-CsVoiceRoute and Set-CsVoiceRoute cmdlets to add a new PSTN gateway to a voice route:

 

$y = Get-CsVoiceRoute -Identity Route1

$y.PstnGatewayList.Add("PstnGateway:192.168.0.100")

Set-CsVoiceRoute -Instance $y

 

 

For more information

 

• Haiku #36: The CsVoicePolicy Cmdlets
• Haiku #78: The CsPstnUsage Cmdlets
• The Edit Voice Policy Dialog
• The Edit Voice Route Dialog
• The Edit PSTN Usage Record Dialog

 

 

 

 

Configuring Trunks and Translation Rules

 

Configure Media Bypass on a Trunk

 

• To configure media bypass on a trunk

 

To enable media bypass for a new SIP trunk, use the New-CsTrunkConfiguration cmdlet and set the EnableBypass property to True:

 

New-CsTrunkConfiguration -Identity site:Redmond -EnableBypass $True –MaxEarlyDialogs 40 –SRTPMode Required

 

 

Configure a Trunk Without Media Bypass

 

• To configure a trunk without media bypass

 

To disable media bypass for a new SIP trunk, use the New-CsTrunkConfiguration cmdlet and set the EnableBypass property to False:

 

New-CsTrunkConfiguration -Identity site:Redmond -EnableBypass $False –MaxEarlyDialogs 40 –SRTPMode Required

 

 

Defining Translation Rules

 

Create or Modify a Translation Rule Manually

 

• To define a translation rule manually

 

To create a new translation rule use the New-CsSipResponseCodeTranslationRule cmdlet:

 

New-CsSipResponseCodeTranslationRule -Identity "PstnGateway:192.168.0.240/Rule404" -ReceivedResponseCode 434 -TranslatedResponseCode 404

 

 

For more information

 

• Haiku #2: The CsTrunkConfiguration Cmdlets
• Haiku #45: The CsSipResponseCodeTranslationRule Cmdlets
• The Edit Trunk Configuration Dialog

 

 

 

 

Exporting and Importing Voice Routing Configuration

 

Export a Voice Route Configuration File

 

• To export a voice routing configuration

 

With Windows PowerShell you cannot directly export a voice route in the VCFG file format used by the Lync Server Control Panel. However, it is possible to export a voice route in an XML format that can later be imported using Windows PowerShell:

 

Get-CsVoiceRoute –Identity "RedmondRoute" | Export-Clixml –Path "C:\Routes\RedmondRoute.xml"

 

 

Import a Voice Route Configuration File

 

• To import a voice routing configuration

 

To import a voice route that was previously exported using the Export-Clixml cmdlet, use the following command:

 

Import-Clixml –Path "C:\Routes\RedmondRoute.xml" | Set-CsVoiceRoute

 

 

For more information

 

• The Get-CsVoiceRoute Cmdlet
• The Edit Voice Route Dialog
• The Import-Clixml Cmdlet
• The Export-Clixml Cmdlet

 

 

 

 

Test Voice Routing

 

Create a Voice Routing Test Case

 

• To create a test case

 

To create a new test case for voice routing, use the New-CsVoiceTestConfiguration cmdlet:

 

New-CsVoiceTestConfiguration -Identity TestConfig1 -DialedNumber 5551212 -ExpectedTranslatedNumber +5551212

 

 

Run Voice Routing Test Cases

 

• To run all voice routing test cases

 

Use the following command to run all your voice routing test cases, one after another:

 

Get-CsVoiceTestConfiguration | Test-CsVoiceTestConfiguration

 

 

 

• To run one or more selected voice routing test cases

 

Use the following command to run a specific voice routing test case:

 

Get-CsVoiceTestConfiguration -Identity TestConfig1 | Test-CsVoiceTestConfiguration

 

 

For more information

 

• The Test-CsVoiceTestConfiguration Cmdlet

 

 

 

 

 

View a List of Computers Running Lync Server 2010

 

• To view a list of computers running Lync Server

 

Although not quite a perfect match, the following script largely replicates the information found on the Topology\Status tab in the Lync Server Control Panel:

 

$errorPref = $errorActionPreference

$errorActionPreference = "SilentlyContinue"

 

$arrObjects = @()

$computers = Get-CsComputer | Sort-Object Identity

 

foreach ($objComputer in $computers)

   {

        $objSite = Get-CsPool -Identity $objComputer.pool | Select-Object Site

        $objReplication = $Null

        $objReplication = Get-CsManagementStoreReplicationStatus -ReplicaFqdn `

            $objComputer.Identity | Select-Object UpToDate

        $strReplication = $objSite.site -replace("Site:","")

 

        $objDisplayObject = New-Object PSObject

        Add-Member -InputObject $objDisplayObject -memberType NoteProperty `

            -Name Identity -Value $objComputer.Identity

        Add-Member -InputObject $objDisplayObject -memberType NoteProperty `

             -Name Pool -Value $objComputer.Pool

        Add-Member -InputObject $objDisplayObject -memberType NoteProperty `

             -Name Site -Value $strReplication

        Add-Member -InputObject $objDisplayObject -memberType NoteProperty `

             -Name UpToDate -Value $objReplication.UpToDate

 

        $arrObjects += $objDisplayObject

}

 

$labels = @{Expression={$_.Identity};Label="Computer"}, `

          @{Expression={$_.Pool};Label="Pool"}, `

          @{Expression={$_.Site};Label="Site"}, `

          @{Expression={$_.UpToDate};Label="Replication"}

 

$arrObjects | Format-Table $labels

$errorActionPreference = $errorPref

 

To use this script, copy the code, paste it into a text editor, and then save the file using a .ps1 file extension (for example, C:\Scripts\Status.ps1). From there all you have to do is run the script from within the Lync Server Management Shell. For example:

 
C:\Scripts\Status.ps1

 

 

For more information

 

• Haiku # 81: The CsPool Cmdlets
• Haiku #67: The CsManagementStoreReplicationStatus Cmdlets
• Get-CsComputer

 

 

 

 

View the Status of Services Running on a Computer

 

• To view the status of services running on a computer

 

To view the status of all the Lync Server services running on all your computers, use the following command:

 

Get-CsService | Select-Object Role, PoolFqdn | Sort-Object PoolFqdn, Role

 

To view the services running on a specific computer, use this command, replacing atl-cs-001.litwareinc.com with the fully qualified domain name of the computer to be checked:

 

Get-CsService | Where-Object {$_.PoolFqdn –eq "atl-cs-001.litwareinc.com"} | Select-Object Role, PoolFqdn | Sort-Object PoolFqdn, Role

 

 

For more information

 

• Haiku #71: The CsService Cmdlets

 

 

 

 

View Details About a Service

 

• To view details for a service

 

To view detailed information for a particular Lync Server service or server role, use the Get-CsService cmdlet followed by the service Identity:

 

Get-CsService –Identity service:Registrar:atl-cs-001.litwareinc.com

 

To view detailed information for all your Lync Server services or server roles, call Get-CsService without any parameters:

 

Get-CsService

 

 

For more information

 

• Haiku #71: The CsService Cmdlets

 

 

 

 

 

Start or Stop Lync Server 2010 Services

 

• To start or stop all Lync Server services on a computer

 

To start all the Lync Server services on a computer, use the Start-CsWindowsService cmdlet:

 

Start-CsWindowsService -ComputerName atl-cs-001.litwareinc.com

 

Note that the ComputerName parameter is not required if you are starting the Lync Server services on the local computer.

 

To stop all the Lync Server services on a computer, use the Stop-CsWindowsService cmdlet:

 

Stop-CsWindowsService -ComputerName atl-cs-001.litwareinc.com

 

 

• To start or stop a specific service

 

To start a specific service, use the Start-CsWindowsService cmdlet along with the Name parameter:

 

Start-CsWindowsService –Name "RTCRGS" -ComputerName atl-cs-001.litwareinc.com

 

Use the Stop-CsWindowsService cmdlet to stop a specified service:

 

Stop-CsWindowsService –Name "RTCRGS" -ComputerName atl-cs-001.litwareinc.com

 

 

 

 

For more information

 

• Haiku #51: The CsWindowsService Cmdlets

 

 

 

 

Prevent Sessions for Services

 

• To prevent new sessions for all Lync Server services on a computer

 

To prevent new sessions for all the Lync Server services on a computer use the following command:

 

Get-CsWindowsService | Stop-CsWindowsService -ComputerName atl-cs-001.litwareinc.com –Graceful

 

The Graceful parameter used with the Stop-CsWindowsService cmdlet ensures that all existing sessions will be honored but no new sessions will be allowed.

 

 

• To prevent new sessions for a specific service

 

To prevent new sessions for a specific Lync Server service, use the following command:

 

Stop-CsWindowsService -Name "RTCRGS" -ComputerName atl-cs-001.litwareinc.com -Graceful

 

 

For more information

 

• Haiku #51: The CsWindowsService Cmdlets

 

 

 

 

View Microsoft SIP Processing Language (MSPL) Server Applications

 

To return information for all of your MSPL server applications, use the Get-CsServerApplication cmdlet:

 

Get-CsServerApplication

 

The following command returns information for a specific application:

 

Get-CsServerApplication -Identity "service:Registrar:atl-cs-001.litwareinc.com/ExumRouting"

 

And this command returns information about all the applications running under a specific service:

 

Get-CsServerApplication -Identity "service:EdgeServer:atl-edge-001.litwareinc.com"

 

 

For more information

 

• The Server Application Dialog

 

 

 

 

Enable or Disable a Microsoft SIP Processing Language (MSPL) Server Application

 

• To enable or disable an MSPL server application

 

To enable an MPSL server application, use the Set-CsServerApplication cmdlet and set the Enabled property to True:

 

Set-CsServerApplication -Identity "Registrar:atl-cs-001.litwareinc.com/ExumRouting" -Enabled $True

 

To disable an MPSL server application, set the Enabled property to False:

 

Set-CsServerApplication -Identity "Registrar:atl-cs-001.litwareinc.com/ExumRouting" -Enabled $False

 

 

For more information

 

• The Server Application Dialog

 

 

 

 

Mark a Microsoft SIP Processing Language (MSPL) Application as Critical or Not Critical

 

• To mark or unmark an MSPL server application as critical

 

To mark an MPSL server application as critical, use the Set-CsServerApplication cmdlet and set the Critical property to True:

 

Set-CsServerApplication -Identity "Registrar:atl-cs-001.litwareinc.com/QoEAgent" -Critical $True

 

To mark an MPSL server application as not being critical, set the Critical property to False:

 

Set-CsServerApplication -Identity "Registrar:atl-cs-001.litwareinc.com/QoEAgent" -Critical $False

 

 

For more information

 

• The Server Application Dialog

 

 

 

 

View a List of Trusted Applications

 

• To view a list of trusted applications

 

To return information for all your trusted applications, call Get-CsTrustedApplication without any parameters:

 

Get-CsTrustedApplication

 

To return information about a single application, use the Identity parameter followed by the application Identity:

 

Get-CsTrustedApplication -Identity TrustPool.litwareinc.com/tapp2

 

For more information

 

• The Trusted Application Dialog

 

 

 

 

View the Simple URL Details

 

• To view Simple URL details

 

To return information about the Simple URLs configured for use in your organization, use the following command:

 

Get-CsSimpleUrlConfiguration | Select-Object –Expand SimpleUrl

 

 

For more information

 

• Haiku #29: The CsSimpleUrlConfiguration Cmdlets

 

 

 

 

 

Change the Web Services URL

 

• Configure Web Services

 

To modify the Web Services URL used by external users, use the Set-CsWebServer cmdlet and set the value of the ExternalFqdn property:

 

Set-CsWebServer –Identity WebServer:atl-cs-001.litwareinc.com –ExternalFqdn atl-ext-001.litwareinc.com

 

 

For more information

 

• The Set-CsWebServer Cmdlet

 

 

Shall I compare thee

To almost one summer's day?

Test federation.

 

Well, it's July 21^st, it's 57 degrees outside, and it's raining – again. But we have good news for everyone: despite all that, the author of today's haiku is not going to waste your time complaining about the weather and whining about the lack of summer here in the Seattle area. Is that because he finally realized that people would rather read about Lync Server PowerShell than listen to his bellyaching? Well, to be honest, that reason never occurred to him, although it is a pretty good reason. No, the reason he's not going to waste your time complaining about the weather is this: it turns out that, for the first time in his life, he was wrong about something.

 

 

At any rate, after complaining – repeatedly – that there has been no summer here in Seattle, it turns out that the author of today's haiku was wrong: there has been a summer here after all. A local meteorologist recently went through the minute-by-minute weather statistics for the entire year, looking for "summer moments;" by his definition, a summer moment was any time of the day when the temperature was at or above 80 degrees. By that reckoning, it turns out that the Seattle area has had a summer: 78 minutes worth, to be exact.

 

And yes, that is almost an hour and a half.

 

And what if you lower your standards a bit? (Interesting note: the author of today's haiku remembers hearing his wife use that phrase earlier today as well.) Well, if you look for moments when the temperature has been 75 degrees or warmer, the numbers climb dramatically: by that definition, the Seattle area has experienced nearly 16 hours of summer! 16 hours; two-thirds of a day. No wonder it feels so good to have cooler temperatures and a little rain this morning.

 

 

Of course, the big question is really this: other than being wrong about Seattle not having a summer, what other mistake could the author of today's haiku have ever made? And here's your answer: it took him forever to finally get around to talking about the Test-CsFederatedPartner cmdlet. But he's making up for that right now.

 

As you might have guessed, the Test-CsFederatedPartner cmdlet provides a way for you to verify connectivity with a federated domain. (A federated domain, of course, is simply a domain that your users can communicate with, and exchange presence information with, in pretty much the exact same way your users can communicate with, and exchange presence information with, other people in your own domain.)

 

That's good; even better is the fact that Test-CsFederatedPartner is remarkably easy to use. For example, suppose you reside in the litwareinc.com domain, and you have set up federation with the fabrikam.com domain. How can you verify that this federation connection is still up and running? Like this:

 

Test-CsFederatedPartner -TargetFqdn accessproxy.litwareinc.com -Domain fabrikam.com

 

Like we said, remarkably easy. All we have to do is include the TargetFqdn parameter followed by the fully qualified domain name of our Edge server, as well as the Domain parameter followed by the FQDN of the federated domain. (And yes, you can only run this command against federated domains. If you try running it against a random domain, a domain you are not federated with, the command will fail.)

 

That's all you have to do and, to be honest, that's pretty much all you can do with the Test-CsFederatedPartner cmdlet. But here's a bonus command for you anyway, just for the heck of it. This one retrieves all the domains included on your Allowed Domains list (that is, the domains you are federating with) and runs Test-CsFederatedPartner against each one of those domains:

 

Get-CsAllowedDomain | ForEach-Object {Test-CsFederatedPartner –TargetFqdn accessproxy.litwareinc.com –Domain $_.Identity}

 

As you can see, we called Get-CsAllowedDomain to return a collection of allowed domains, and then piped that collection to the ForEach-Object cmdlet; in turn, ForEach-Object then ran the Test-CsFederatedPartner cmdlet against each domain in the collection. Why didn't we just pipe the allowed domains directly to Test-CsFederatedPartner, something like this:

 

Get-CsAllowedDomain | {Test-CsFederatedPartner –TargetFqdn accessproxy.litwareinc.com –Domain $_.Identity

 

Well, believe it or not, we actually had a good reason not to use a command like that one: it won't work. That's because the Test-CsFederatedPartner cmdlet can't accept pipelined input:

 

Test-CsFederatedPartner : The input object cannot be bound to any parameters for the command either because the command does not take pipeline input or the input and its properties do not match any of the parameters that take pipeline input.

 

Because of that, we use the good old-fashioned ForEach-Object workaround instead.

 

And that's pretty much all she wrote (or at least all we wrote) when it comes to the Test-CsFederatedPartner cmdlet. Not only that, but the temperature has climbed all the way to 61 degrees, and the rain has devolved into a sort of misty drizzle kind of thing. Obviously we have nothing to complain about here!

 

 

 

 

 

 

Configuring Conferencing Settings

 

Modify the Default Conferencing User Experience

 

• To modify the global conferencing policy

 

To modify the global policy, use the Set-CsConferencingPolicy cmdlet and set the Identity to global:

 

Set-CsConferencingPolicy –Identity global -AllowAnonymousParticipantsInMeetings $False -EnableDialInConferencing $False

 

Note that you can also modify the global policy by leaving out the Identity parameter altogether:

 

Set-CsConferencingPolicy -AllowAnonymousParticipantsInMeetings $False -EnableDialInConferencing $False

 

 

Create or Modify Conferencing User Experience for a Site or Group of Users

 

• To create a new user or site conferencing policy

 

To create a per-site conferencing policy, use the site: prefix and the name of the site as the Identity:

 

New-CsConferencingPolicy –Identity site:Redmond -AllowAnonymousParticipantsInMeetings $False -EnableDialInConferencing $False

 

To create a per-user conferencing policy, simply use a unique name for the policy Identity:

 

New-CsConferencingPolicy –Identity "RedmondConferencingPolicy" -AllowAnonymousParticipantsInMeetings $False -EnableDialInConferencing $False

 

 

• To modify an existing user or site policy

 

Use the Set-CsConferencingPolicy cmdlet to modify a per-user or per-site policy:

 

Set-CsConferencingPolicy –Identity site:Redmond -AllowAnonymousParticipantsInMeetings $True -EnableDialInConferencing $True

 

Be sure to specify a policy Identity. If you leave off the Identity Set-CsConferencingPolicy will modify the global policy instead.

 

To make the same modification to all your conferencing policies (including the global policy), use a command similar to this one:

 

Get-CsConferencingPolicy | Set-CsConferencingPolicy -AllowAnonymousParticipantsInMeetings $True

 

This command modifies only your per-user conferencing policies:

 

Get-CsConferencingPolicy –Filter "tag:*" | Set-CsConferencingPolicy -AllowAnonymousParticipantsInMeetings $True

 

 

Delete a Conferencing Policy for a Site or Group of Users

 

• To delete a user or site conferencing policy

 

To delete a per-user or per-site policy, using a command similar to this:

 

Remove-CsConferencingPolicy –Identity site:Redmond

 

If you try to remove a per-user policy that is currently assigned to one or more users you will be prompted to first unassign the policy from each user and then delete the policy. (You can remove a policy without unassigning it, but, from then on, any time you call a user management cmdlet you will receive warnings about policies that can no longer be found.) To unassign a per-user policy and then remove that policy use commands similar to these:

 

Get-CsUser -Filter {ConferencingPolicy -eq "RedmondConferencingPolicy"} | Grant-CsConferencingPolicy -PolicyName $Null

 

Remove-CsConferencingPolicy –Identity "RedmondConferencingPolicy"

 

For more information

 

• No Conferencing Policy is an Island
• The Edit Conferencing Policy Dialog

 

 

 

 

Configuring the Meeting Join Experience

 

Modify the Default Meeting Join Experience

 

• To modify the default meeting join settings

 

To modify the default meeting join settings use the Set-CsMeetingConfiguration cmdlet and set the Identity to global:

 

Set-CsMeetingConfiguration -Identity global -DesignateAsPresenter Everyone

 

Alternatively, you can omit the Identity altogether:

 

Set-CsMeetingConfiguration -DesignateAsPresenter Everyone

 

If you leave off the Identity, Set-CsMeetingConfiguration will automatically modify the global settings.

 

 

Create or Modify Meeting Join Settings for a Site or Pool

 

• To create new meeting join settings

 

To create new meeting configuration settings for a site, use a command similar to this:

 

New-CsMeetingConfiguration -Identity site:Redmond -DesignateAsPresenter Everyone

 

To create new meeting configuration settings for a pool, set the Identity parameter to the service location for the User Server used in that pool:

 

New-CsMeetingConfiguration -Identity "service:UserServer:atl-cs-001.litwareinc.com" -DesignateAsPresenter Everyone

 

 

• To modify an existing site or pool meeting join configuration

 

To modify an existing collection of meeting configuration settings, use the Set-CsMeetingConfiguration cmdlet:

 

Set-CsMeetingConfiguration -Identity site:Redmond -DesignateAsPresenter None

 

When calling Set-CsMeetingConfiguration, be sure to include the Identity for the meeting configuration settings to be modified. If you do not, Set-CsMeetingConfiguration will automatically modify the global settings instead.

 

 

Delete Meeting Join Settings for a Site or Pool

 

• To delete meeting join settings for a site or pool

 

To remove the meeting configuration settings for a site, use a command similar to this:

 

Remove-CsMeetingConfiguration -Identity site:Redmond

 

To remove the meeting configuration settings for a pool, use a command similar to this one, which specifies the identity of the User Server in the pool:

 

Remove-CsMeetingConfiguration -Identity "service:UserServer:atl-cs-001.litwareinc.com"

 

 

For more information

 

• Haiku #84: The CsMeetingConfiguration Cmdlets
• The Edit Meeting Configuration Dialog

 

 

 

 

Configure Settings for a Dial-in Conferencing Access Number

 

• To create or modify a dial-in access number

 

To create a new dial-in conferencing access number, use the New-CsDialInConferencingAccessNumber cmdlet:

 

New-CsDialInConferencingAccessNumber -PrimaryUri "sip:RedmondDialIn@litwareinc.com" -DisplayNumber "1-800-555-1234" -LineUri "tel:+18005551234" -Pool atl-cs-001.litwareinc.com -PrimaryLanguage "en-US" -Regions "Redmond"

 

Use the Set-CsDialInConferencingAccessNumber cmdlet to modify an existing access number:

 

Set-CsDialInConferencingAccessNumber -Identity "sip:RedmondDialIn@litwareinc.com" -Regions "Redmond", "Seattle"

 

 

Delete a Dial-in Conferencing Access Number

 

• To delete a dial-in conferencing access number

 

To delete a dial-in access number, use the Remove-CsDialInConferencingAccessNumber cmdlet and specify the number's SIP address as the Identity:

 

Remove-CsDialInConferencingAccessNumber -Identity "sip:RedmondDialIn@litwareinc.com"

 

You can also use a command like this one to delete all your dial-in access numbers:

 

Get-CsDialInConferencingAccessNumber | Remove-CsDialInConferencingAccessNumber

 

 

For more information

 

• Haiku #126: The CsDialInConferencingAccessNumber Cmdlets
• The New Dial-in Access Number Dialog

 

 

 

 

Configure Dial-in Conferencing Personal Identification Number (PIN) Rules

 

Modify the Default Dial-in Conferencing PIN Settings

 

• To modify the global PIN policy

 

To modify the global PIN policy, use the Set-CsPinPolicy cmdlet and set the Identity to global:

 

Set-CsPinPolicy -Identity global -MinPasswordLength 10

 

Alternatively, you can leave out the Identity parameter altogether:

 

Set-CsPinPolicy -MinPasswordLength 10

 

If you do not specify an Identity, Set-CsPinPolicy will modify the global policy.

Create or Modify Dial-in Conferencing PIN Settings for a Site or Group of Users

 

• To create a user or site PIN policy

 

To create a per-site policy, set the Identity to the prefix site: followed by the name of the site:

 

New-CsPinPolicy -Identity "site:Redmond" -MinPasswordLength 10

 

To create a per-user policy, simply use a unique policy name as the Identity:

 

New-CsPinPolicy -Identity "RedmondPinPolicy" -MinPasswordLength 10

 

 

• To change a user or site PIN policy

 

To modify a per-user or per-site PIN policy, use the Set-CsPinPolicy cmdlet:

 

Set-CsPinPolicy -Identity "site:Redmond" -MinPasswordLength 6

 

Delete Dial-in Conferencing PIN Settings for a Site or Group of Users

 

• To delete a user or site PIN policy

 

To delete a per-user or per-site policy, use the Remove-CsPinPolicy cmdlet:

 

Remove-CsPinPolicy –Identity site:Redmond

 

This command removes all the per-site PIN policies:

 

Get-CsPinPolicy –Filter "site:*" | Remove-CsPinPolicy

 

And this one removes all the per-user PIN policies:

 

Get-CsPinPolicy –Filter "tag:*" | Remove-CsPinPolicy

 

 

For more information

 

• Haiku #72: The CsPinPolicy Cmdlets
• The Edit PIN Policy Dialog