Configure new Busy Options

Within Cumulative Update 3 for Skype for Business Microsoft delivered new voice options to their customers: Busy Options

Today I will show you how to configure busy options within your Skype for Business Server deployment:

After you have installed the CU3 Update (Download here)  you have to take additional configuration that the new busy options works within your Skype for Business deployment.

Server configuration

At first you have to add the busy options as a new server application to every front end pool in your environment via the Skype for Business Management Shell:

serverapplication

New-CsServerApplication ´
-Identity 'Service:Registrar:FQDNskypeFEpool/BusyOptions' ´ 
-Uri http://www.microsoft.com/LCS/BusyOptions ´ 
-Critical $False -Enabled $True ´ 
-Priority (Get-CsServerApplication ´ 
-Identity 'Service:Registrar:FQDNskypeFEpool/UserServices').Priority

After that you have to restart the Front End Server service “RTCSRV” on every Front End in the pool.

Voice Policy

Now we can start with the configuration for our end users. Busy options are part of the users voice policy. Within my deployment i want to enable it for all existing voice policies. So I run the following PowerShell cmdlet:

Get-CsVoicePolicy | Set-CsVoicePolicy -EnableBusyOptions $true

For sure you can activate the busy options just for dedicated voice policies and also use the Skype for Business Control Panel.

busy_controlpanel

 

 

 

 

 

 

 

end user configuration

After  you have enabled the busy options within the voice policy nothing has changed for the end users. But why? Unfortunately busy options can not be set by the end users. They have to be set from the administrator. And per default no specific busy option is set after activating it within the voice policy.

You can choose between two busy options:
– Busy on Busy -> a busy tone is send when the user is “busy”
– Voicemail on Busy -> incoming call is forwarded to the users voicemail

To set busy options administrators have to use the PowerShell again:

Set-CsBusyOptions ´
-Identity sip:firstname.lastname@sipdomain.tld ´
-ActionType BusyOnBusy 

Set-CsBusyOptions ´
-Identity sip:firstname.lastname@sipdomain.tld ´
-ActionType VoicemailOnBusy

To remove the configured busy options use the following cmdlet:

Get-CsBusyOptions ´
-Identity sip:firstname.lastname@sipdomain.tld | ´
Remove-CsBusyOptions

conclusion

Well, you see that administrators have to set the new busy options for the end users. This causes more administrative effort and differs totally from the common voice features. Just to remember: call forwarding, simultaneous ringing and the voicemail options are configured by the end user directly within the Skype for Business client.

Another point is that the configured busy options only work if the end user is in a call or a conference call. A manually set presence status “busy” or a “busy” set through an outlook meeting will not effect that the configured busy options reject or forward another incoming call.

Nevertheless the new busy options are really good feature for end users with a high call volume that do not want to get interrupted permanently from new incoming calls.