Edit

Set-CsBusyOptions

  • Reference
Module:
SkypeForBusiness

Sets up the processing of incoming calls for users who are already engaged in another communication stream. This cmdlet was introduced in Skype for Business Server 2015 June 2016 Cumulative Update.

Syntax

Set-CsBusyOptions
   [-Identity] <UserIdParameter>
   -ActionType <ActionType>
   [-Confirm]
   [-PassThru]
   [-WhatIf]
   [<CommonParameters>]

Description

This cmdlet sets the configuration for processing of incoming calls defined for a specific user. If Busy Options is enabled for the organization, all users in your organization, both Enterprise Voice and non-Enterprise Voice users, can use the following features:

  • Busy on Busy - In which new incoming calls will be rejected with a busy signal if the user is busy.

  • Voicemail on Busy - In which new incoming calls will be forwarded to voice mail if the user is busy.

The Busy Options feature provides failover capability. If a problem occurs and users fail over to another Front End Server or to another pool in Skype for Business Server, their Busy Options settings will be preserved.

Regardless of how their busy options are configured, users in a call or conference, or those with a call on hold, are not prevented from initiating new calls or conferences.

After configuration, the Busy Options setting is in effect for all the user's Skype for Business call devices and clients. Based on the user's Busy Options settings, the call that is rejected or sent to voice mail would not ring on any of the user's call devices--including Macintosh, Windows Desktop, mobile clients, or IP phones--on which the user is signed in.

Users will see missed-call notifications on their Skype for Business clients and devices, and they will be notified by email as well. Callers whose call was rejected due to Busy on Busy will see a notification in their Skype for Business client stating that the user they attempted to reach is busy on another call.

For more information about how to enable Busy Options in your organization, see (https://learn.microsoft.com/skypeforbusiness/deploy/deploy-enterprise-voice/install-and-configure-busy-options).

Examples

-------------------------- Example 1 --------------------------

Set-CsBusyOptions -Identity "Ken Myer" -ActionType BusyOnBusy

This cmdlet configures busy options for the user "Ken Myer". In this configuration, any call to "Ken Myer" will return a busy signal when he is already in a call.

-------------------------- Example 2 --------------------------

Set-CsBusyOptions -Identity "Chrystal Velasquez" -ActionType VoicemailOnBusy

This cmdlet configures busy options for the user "Chrystal Velasquez". In this configuration, new incoming calls to "Chrystal Velasquez" will be forwarded to voice mail when she is already in a call.

Parameters

-ActionType

There are two Action Type options:

  • BusyOnBusy - In which new incoming calls will be rejected with a busy signal if the user is busy.

  • VoicemailOnBusy - In which new incoming calls will be forwarded to voice mail if the user is busy.

Type:ActionType
Accepted values:BusyOnBusy, VoicemailOnBusy
Position:Named
Default value:None
Required:True
Accept pipeline input:True
Accept wildcard characters:False
Applies to:Skype for Business Server 2015, Skype for Business Server 2019

-Confirm

Prompts you for confirmation before running the cmdlet.

Type:SwitchParameter
Aliases:cf
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Skype for Business Server 2015, Skype for Business Server 2019

-Identity

Indicates the Identity of the user account to be modified. User Identities can be specified using one of four formats: 1) the user's SIP address; 2) the user's user principal name (UPN); 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer) and 4) the user's Active Directory display name (for example, Ken Myer). User Identities can also be referenced by using the user's Active Directory distinguished name.

You can use the asterisk (*) wildcard character when using the display name as the user Identity. For example, the Identity "*Smith" returns all the users who have a display name that ends with the string value "Smith".

Type:UserIdParameter
Position:0
Default value:None
Required:True
Accept pipeline input:True
Accept wildcard characters:False
Applies to:Skype for Business Server 2015, Skype for Business Server 2019

-PassThru

Returns an object representing the item with which you are working. By default, this cmdlet does not generate any output.

Type:SwitchParameter
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Skype for Business Server 2015, Skype for Business Server 2019

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.

Type:SwitchParameter
Aliases:wi
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Skype for Business Server 2015, Skype for Business Server 2019

Inputs

Microsoft.Rtc.Management.Bob.Cmdlets.ActionType object. Microsoft.Rtc.Management.AD.UserIdParameter object.

Outputs

Microsoft.Rtc.Management.Bob.Cmdlets.ActionType object. Microsoft.Rtc.Management.AD.UserIdParameter object.