One to file under classic telephony features now in Microsoft Teams, “Busy on Busy” (Busy Options) is a user-level or tenant level configuration to Busy on Busy (Busy Options) allows you to configure how an incoming calls when you are in an existing call or meeting.
The second incoming calls can be rejected with a busy signal or can be routed accordingly to the user’s unanswered settings.
You can enable busy options at the tenant level or at the user level.
This is asked for because in some countries/cultures it is considered rude that when you are in a call or meeting you would be allowed to be distracted by another incoming call, or because users themselves find a second incoming call distracting.
It’s a feature we didn’t initially have in Skype for Business Server either it was added in June 2016 CU3. Again, if enough customers want a feature. It will usually get prioritised.
Set-CsTeamsCallingPolicy –BusyOnBusyEnabledType configures Busy on Busy. Valid options are:
- Enabled – new or incoming calls will be rejected with a busy signal
- Unanswered – the user’s unanswered settings will take effect, such as routing to voicemail or forwarding to another user
- Disabled – Disables Busy on Busy
We are having issues with call failures when a user with Busy on Busy configured but no Call Forward on No Answer set up. My understanding is that an external caller should receive busy tone when calling a user configured in this way when they are already on a call.
Our carriage service provider is advising that Microsoft are sending back a SIP Q.850 code as follows:
480 Temporarily Not Available
cause=31 Call rejected due to inability to route
This causes the carrier SBCs to retry multiple times before the call eventually fails and the called party sees multiple missed calls for a single call attempt.
Is this an issue unique to our deployment, our region or is it a worldwide one?
There’s another option for Set-CsTeamsCallingPolicy BusyOnBusyEnabledType – namely “UserOverride”. Perhaps that one deserves a mention? :-)
Note: UserOverride option value is not available for use currently, if set it will be read as setting value to Disabled.