Skype for Business Server– Deploy and configure Busy on Busy Options


Busy on Busy came in CU3 of Skype for Business Server 2015 and adds the options to send calls a busy tone or send calls to voicemail if the person you are calling is on the phone / Busy. Also in CU3 came offline messaging, Video based screen sharing and multiple emergency numbers.

The default behaviour for busy up until now was a second toast pop up would alert the user who is on the phone that they have another calls and from there they can action to answer, forward, send to voicemail etc. while the caller is hearing the usual ringing tone.

Now if i was a traditional PBX user i probably wouldn’t have this behaviour or get notified whilst i was on the phone that another caller was calling and be able to answer that call. From PBX migrations I’ve found users not liking the fact they are receiving another call whilst on the phone and the common phase “the old system didn’t do, it distracts me and can we turn it off” well now with CU3 for Sfb Server we have the option to.


For me think is it the right option to do?  i personally like the fact i can see the other call and action it. for example i may be expecting an urgent call but someone calls me just before, when the important call comes i can jump to it.

Enabling Busy on Busy (BoB) options send a busy tone or goes to voicemail nice feature to have but please consider the options and don’t limit the power of SfB Smile.

Well hope that waffle made sense let get to the deployment and config bits.


Prereq items

  • Skype for Business Server 2015 (Sorry Lync Server Guys)
  • You must have Skype for Business Server 2015 Cumulative Update 3 installed. This is a requirement to add the busy on busy options. Link below.

After you have deployed CU3 you need deploy and configure the busy on busy (BoB) functionality.

The below assumes you have already deployed CU3

(Please note following the deployment of CU3 i had to restart the SfB services to register the Busy on Busy Application but you can see below where we can check the Event viewer on the server.



1. Enable Busy Option in Voice Policies

Open SfB Management Shell and

Lets check the SfB Voice Policies for the BoB option, as we can see below they are false by default.


To enable for the global policy (Please note this does not enabled for user based voice policies)

Set-CsVoicePolicy -EnableBusyOptions $true


Lets check the voice policies again


Enable for user based Voice Policies

use get-csvoicepolicy to find all policies and identity to use below.

Get-CsVoicePolicy -Identity "<VOICE POLICY IDENTITY>" |
set-csvoicepolicy -EnableBusyOptions $true


To Enable all user based  voice policies

Get-CsVoicePolicy | Set-CsVoicePolicy -EnableBusyOption
s $true


Site based voice policies


Get-CsVoicePolicy –identity Site: <Site Name>


2. Add Busy Option Server Application

From SfB Control you can see the list of server applications


To add the new application from SfB Management Shell enter

New-CsServerApplication -Identity ‘Service:Registrar <Registrar Name>/BusyOptions’ -Uri -Critical $False -Enabled $True -Priority (Get-CsServerApplication -Identity ‘Service:Registrar:<Registrar Name>/UserServices’).Priority



You can now see BusyOptions has been added as a server application Smile



Verify Busy Application has loaded Settings in Event Viewer

You can also use Windows Event Viewer to verify that the Busy Options installation was successful and that Skype for Business Server successfully loaded Busy Options. From an FE check for.

To verify Busy Options, open Event Viewer -> Application and Services Logs –> Lync Server and search for Event ID = 30253.



As you can see the last event above was following the CU3 update and BusyOptions applications wasnt deployed so i have to restart the SfB Services using Management Shell.


followed by to start them back up.


There we go its registered Smile




3. Update RBAC for Busy Options

Open SfB Management Shell and run update-csAdminRole



Deployment over time to configure !



You can set this on a per user basis from SfB management shell

Set Busy Options

Set-CsBusyOptions –identity “Display Name” – ActionType BusyOnBusy

Set-CsBusyOptions –identity “Display Name” – ActionType VoicemailOnBusy


Notice a warning in this case the user selected voice policy did not have Busy Options enabled which is a good reminder!


To set All users busy options if your brave. warning this will take a while and do you want to set this for all your users.

Get-CsUser | Set-CsBusyOptions  -ActionType BusyOnBusy

Get-CsUser | Set-CsBusyOptions  -ActionType VoicemailOnBusy

Check Busy Options set on user

Get-CsBusyOptions -Identity sip: <SIP URI>


For all users but be warned you may see alot of errors see below.

Get-CSUser | Get-CsBusyOptions

Remove Busy Options

Remove-CsBusyOptions -Identity "Martin Boam"

Remove All

Get-CSUser | Remove-csbusyoptions

When no busy options assigned and you try Get-CsBusyOptions




Link to TechNet for further info.

Skype for Business Server 2015 – Cumulative Update 3 brings Busy On Busy voice policy options !

Well its happy Busy on Busy day for SfB Server with cumulative update 3.

Its a very commonly asked question when moving from a PBX to Lync or Skype for Business Server ive found. Where is the busy tone ? Why am i receiving a toast pop up for a call when im busy / already in a call ?

There are two options with the new busy policy and its enabled for EV and non EV users. The policy can be set for all the users, users on a pool or individual users but it would affect all a users endpoints ie, sfb client, LPE, mobile client etc if your busy then your busy on all your devices.

Two Options

  • Busy on Busy: New incoming calls are rejected and sent a busy signal when the user is busy.
  • Voicemail on Busy: New incoming calls are forwarded to voice mail when the user is busy.

One feature that commonly do is whilst having an IM “free for a call” and then we end up calling each other at the same time and hitting voicemail. Now if two users call each other at the same time from any Skype for Business endpoint, both calls are rejected and sent a busy signal.

Also which i think is great is users are notified of calls that they missed because of a Busy Options setting. Notifications are sent through voice mail, through missed call notifications in Skype for Business clients and devices, and through email🙂 so you know if someone hits busy so you can call them back🙂

Configuration wise it looks like SfB Management shell and can be set at different levels which is great🙂

  • Enable or disable Busy Options Voice Policy for the enterprise
  • Administer Busy on Busy or Voicemail on Busy for all the users in the enterprise
  • Administer Busy on Busy or Voicemail on Busy for all the users homed in a particular Front End pool
  • Administer Busy on Busy or Voicemail on Busy for a list of users
  • Administer Busy on Busy or Voicemail on Busy for a single user
  • View users who are currently enabled for Busy on Busy or Voicemail on Busy

Ill see if i can post some screenshot once i get CU3 on my lab.

Microsoft KB with full Details

Download Cumulative Update 3

Cloud PBX, a Polycom VVX and ADFS

Came across an issue recently where a Polycom VVX wouldn’t sign in correctly when trying to sign in against an Office 365 tenant with ADFS enabled.

We reviewed the Cloud PBX configuration in the tenant and voice settings for the user and these were correct as we could make and receive calls from the SfB desktop client.

So we started with the VVX, we updated the phone to the latest UCS software release and ensured it was a compatible software version for Cloud PBX. At this time it was 5.4.4

We tried signing in again and the issue was the same so we tested with another tenant and it worked ! so this proved its not the phone that’s the problem here.

BUT this tenant didn’t have ADFS deployed so this made me think how is this different.

I looked into the VVX issues online and found a common issue when connecting to an on premises deployment of Lync or SfB was you had to deployed internal certificates so i wondered if this is similar with the ADFS servers as part of the user authentication.


Internal Root Certificate upload via FTP

This is what i did to upload the certificate to the VVX via FTP using a tftp server.

1. I downloaded the internal trusted root certificate from the ADFS server and saved to my PC. (You will also need any intermediate certificates for the full chain)

2. I downloaded and started TFTP Server on my PC and placed the certificates in the TFTP root folder. I noted my PCs internal IP Address and ensure windows firewalls are configured to allow access.

3. From the web interface on the VVX phone i went to Settings > Network > TLS

Under Certificate Configuration > CA Certificates

Under Application CA 1 i entered (If you have intermediates cert please ensure they are uploaded in order)

ftp://<IP Address of TFTP Server>/cert3.cer


and click “Install”


For a much more detailed blog on importing certificates to the VVX please see Jeff Schertz’s blog post here

After uploading the root certificates we tried to sign in again and it worked🙂 whoop whoop so the internal root certificates were required for ADFS to sign the user in.

Hope this helps Cloud PBX users using ADFS🙂

Skype Room System Update – April 2016 (15.15.04)

Just noticed on SMARTs website that there’s an updates for SRS last month on 19th April 2016 software version 15.15.04. Reading the MS KB looks to also apply to Crestron RL and Polycom Cx8000 systems.

Looks to be some bug fixes, improvements,UI tweaks, SMART bios update, a bunch of Microsoft updates and adding a new front of room touch administrator setting to allow use of non-touch front of room displays which sounds interesting. Ill have to do some more digging on this one but I’ve noticed if you have touch displays its not recommend and has some things to be aware of when enabling listed below.

Microsoft Link KB


  • If you ignore the first incoming call, the additional calls to a Skype Room System are not received as expected.
  • Reworded a user tip for the private meeting logon screen.
  • Fixed some font and background colors to better reflect the Skype for Business rebranding.

This update provides the following improvements:

  • Enables non-touch support. Admin can configure the Skype Room System to work with non-touch front-of-the-room displays. The table-top console continues to support touch.
  • Skype Room System lets you enable an additional tab that offers OEM customization, such as PTZ cameras controls. Contact your provider for more information about their product plans and release notes.

Things to be aware of when you enable the non-touch user interface (UI):

  • The whiteboard can be launched only by remote participants.
  • Embedded PowerPoint videos can be played only by remote participants.
  • The non-touch UI isn’t recommended when you use touch displays.

SMART Knowledge Base Link

SMART KB Summary

  • Resolves Video and console Display tab responsiveness issues:
  • Resolves an issue where if the first incoming call was ignored, additional calls to a Skype Room System were not received.
  • Includes user-interface cosmetic improvements for the private-meeting logon screen and other screens.
  • Includes BIOS update version Z301-034 for the SMART AM70-L computing appliance (with network, USB, and video display subsystem improvements).
  • Adds a new Front of room touch administrator setting to allow use of non-touch front-of-room displays on Microsoft Skype for Business room systems.
    Things to be aware of when the Front of room touch setting is turned off:
    • The console on the meeting room table will continue to support touch control.
    • Use of the SMART SRS-USB-Bridge cable empowering touch pass-through to attached guest computers requires SMART front-of-room touch displays (don’t turn off the Front of room touch setting if you want to use the SMART SRS-USB-Bridge cable).
    • The whiteboard can only be launched by remote participants, not from the room system.
    • Embedded PowerPoint videos can only be played only by remote participants, not from the room system.
    • Use of the non-touch user-interface is not recommended with touch-enabled displays.
  • Also includes the following 25 additional Microsoft updates: KB3080446, KB3093513, KB3101722, KB3092601, KB3098781, KB3097996, KB3108381, KB3108670, KB3109103, KB3108371, KB3109094, KB3108669, KB3124280, KB3135445, KB3126587, KB3097966, KB3112148, KB3108664, KB3109560, KB3110329, KB3124001, KB3124275, KB3123479, KB3134214, KB3126593.

Download and KB

Internal Update Server Guys the full SMART download is below

Skype for Business Cloud Connector Edition Download available

Microsoft have released SfB Cloud Connector Edition. It’s been in preview for a little while now but MS have released it as GA now.🙂 Grab the download below. 

Cloud Connector provides on premises PSTN connectivity with SfB Cloud PBX. Cloud Connector is a set of packaged VMs for Hyper V deployed in a permiter network which removes the requirement for a full on premises SfB deployment for on Premises PSTN connectivity with Cloud PBX. 

The VMs are an

– Edge server

– Mediation Server

– Central Management Store Storage

– Domain controller (not connected to production AD)

Cloud Connector can’t coexist with an existing on premises deployment. It’s available for two different hardware sizes large and small depending on call volumes, ( there’s quite a difference between call volumes with small and large so plan carefully) you can have multiple cloud connectors (up to 4) at a site for HA and to increase call volumes. Ther s multiple sites options up to 200 sites as well. 

For HA you need to cautious around restarting mediation if the single domain controller is down. Monitoring is recommended.

Design and planning for Cloud Connector is very important and just because your not deploying a full SfB deployment I would treat the planning the same as there’s a lot to consider which are very similar to a full deployment for example firewalls , certificates, IP addressing, call flows, PSTN planning, DNS, High Availabilty Connector provides a packaged way to deployed the required roles it’s not a way to cut corners in my eyes. 

Also There are some limitations and its definately worth reading the planning documentation first on TechNet. Link below. 


Cloud Connector TechNet information
The below is from TechNet. 

Consider the following when planning your Cloud Connector Edition deployment:

– To use Cloud Connector to take advantage of cloud voice solutions, you’ll need to sign up for an Office 365 tenant that includes Cloud PBX. If you do not yet have an Office 365 tenant you can learn how to sign up here: Office 365 for Business. Note that you’ll need to sign up for a plan that includes Skype for Business Online.

– Cloud Connector does not require a full on-premises Skype for Business Server deployment.

– Currently, Cloud Connector cannot co-exist with Lync or Skype for Business on-premises servers. If you want to move existing Lync or Skype for Business users to Office 365 and keep providing on-premises telephony to your users, consider Cloud PBX with on-premises connectivity using an existing Skype for Business Server deployment. For more information, see Plan your Cloud PBX solution in Skype for Business 2015 or Lync Server 2013 and Plan Cloud PBX with on-premises PSTN connectivity in Skype for Business Server 2015 or Lync Server 2013.

– Cloud Connector is available worldwide.

– Your users are homed online.

– You can keep your current PSTN carrier if required.

– If you want to provide dial-in conferencing to users hosted on Cloud Connector, you can purchase PSTN conferencing from Microsoft or from audio conferencing provider (ACP) partners.
Known Limitations

– The following are known limitations with Cloud Connector. We are working on addressing these limitations and will update this list as fixes become available. Please review and consider whether you want to proceed with production deployment or whether you want to deploy Cloud Connector as a pilot project initially:

– Consultative transfer is not supported.

– You cannot transfer an active call to your cell phone that is registered in your Active Directory by picking it from a list of suggested phones in the transfer menu. You can transfer to any other number.

– Escalation to conference from a call between a PSTN and Skype for Business user is not possible (you can, however, escalate call to conference between two Skype for Business users).

– Dial plan is not applied on Polycom phones and Skype for Business clients for Android and Windows phone. To dial a number, you must use the full E.164 phone number.

SMART – Skype for Business Room System software 15.14.09 – January 2016

Just noticed there was an SRS update in Jan 2016.



Info Source

Skype for Business / Lync / Exchange and . NET 4.6.1 update. Recommendation DO NOT Install / Update

More details below, next hop blog states do not install this for Lync and sfb. This follows the decision by exchange team also. Please be aware.
How to block update with ref key. 

May Be worth doing this just in case and to safeguard against installing this update.
Exchange Blog Update details

Exchange has stated this is not supported and there are known issues following the installation of this update.

Lync 2013 Client Update Feb 2016 (KB3114732) 15.0.4797.1000.

New Lync 2013 Client Update 15.0.4797.1000 this also includes the SfB client update so be cautious if your have chosen not be deploy the SfB update yet.

Please note:

  • After you apply this update, Lync 2013 will be upgraded to Skype for Business User interface but you can still choose to use the Lync 2013 UI after you apply this update.


Details from KB

This update fixes the following issues:

Known issues

After you install this update, you may experience the issues that are described in the following Microsoft Knowledge Base articles:

Get planning with the SfB Planning Tool

The SfB planning tool has been released check it out and download from

Note – you cant have Lync 2013 Planning tools and also i found i had to remove all Lync 2013 components installed such as admin tools, debugging tools etc, then it allowed me to installed. Shame i cant have both versions as i have customers with both versions.

Installation errors i found

You will to uninstall the Lync 2013 planning tool first as prompted.


Next i got this message and i thought this was related to the other Lync 2013 tools i have installed such as Lync 2013 administrator tools, resource kit, core core components and debugging tools. I removed these and it installed ok.


Lync Room Systems – November 2015 CU available – rebranding for SfB, LRS is now SRS :) (15.14.2)

Biggest enhancement here is the rebrand for Skype for Business🙂 Lync is now branded Skype for Business with SfB logos and the UI has a dark theme. The design also includes round icons and a round presence indicator. Lync Room Systems are now Skype Room Systems no more LRS its now SRS🙂

Skype for Business gets a new look 1

This update provides the following improvements:

  • Microsoft branding changes: Rebrands the Lync Room System user interface with Skype for Business logo, colours, and icon design styles.
  • New settings option enables the system administrator to prevent subject line information from being displayed on the meeting calendar (this client-side setting overrides the equivalent server-side setting).
  • Resolves an issue where video streams were limited to a maximum resolution of 1280×720 (720p) instead of 1920×1080 (1080p) on some systems.
  • Includes the following Windows Updates & Patches – See below SMART KB link for more information.

Update will be applied via Windows Update if your LRS uses this if a manual update server is being used the download details are available below.

Office Blog

Provides an overview for the SfB rebranding and UI changes.

CU Download for SMART and Cestron

You can download the exe and extract the new files or you can download the full download from SMART (if using SMART) and grab the new updates already extracted below.

SMART 15.14.12 Full Download (3.46GB)

Easiest option to download all SMART updates in one download and copy to your internal update server.

Full SMART Update Summary details


Known issues:

Microsoft has reported that this update has the following issues which Microsoft is working to resolve in a future update:

1. Loss of conferencing video, and loss of touch responsiveness on Console Display Tab options, with single display SKUs (dual-display SKUs are not affected).

This issue will occur when the following specific actions are taken:

a. Add remote participants (Console will be in Gallery view).  Make sure that remote participants turn on their video.
b. Add a Whiteboard (Console will be in Gallery + Content view).
c. Go to Console and switch the view to Content only view.
d. Go to Console and switch the view to Gallery only view.  At this point, remote participant video will be lost.
e. Go to Console and switch the view to Content and then switch back to Gallery view.  At this point, the controls in the Display tab will no longer respond to touch.

Workaround: Exit the meeting by pressing the Leave Meeting button on the Console, then re-join the meeting.  Remote participant video will now re-appear, and Console Display tab controls will respond to touch.  Any shared content will still be present.

2. IMs will not be received by room after remote participant enters carriage return.

IMs do not appear in the device Console after carriage return from remote participant (responding with an IM from the LRS side resets the routine).

Workaround: No workaround.

Universal Communications, My experiences.

Skype4B, Lync, Exchange & O365 Technical

The Lync Dude

All About Skype for Business, Lync and Unified Communication

UCsteve's blog

My thoughts in an interconnected UC world

Martin Boam's Microsoft UC Blog

All things Microsoft UC including Skype for Business, Lync and Exchange Blog

Skype4Business UC

Sharing my experiences whilst learning about Skype for Business, UC and life itself ...

The Daily Post

The Art and Craft of Blogging News

The latest news on and the WordPress community.