Enable Skype Meetings App to replace Skype for Business Web App on Skype for Business Server 2015 with CU5

Following Skype for Business Server 2015 CU5 May 2017 installation as part of the release notes i noticed something regarding meeting join experiences and i had a light bulb moment perhaps the new meeting join experience that’s already live in Skype for Business Online has come on premises. I had to dig on this.

From release notes sparking my thinking

4015907 Update that enables simplified meeting join experience in Skype for Business Server 2015 from here

and “4. JoinLauncher: Port Modern Meeting Join Experience to W16” from here

Testing Post CU 5 Install

So after installing CU5 i tried to join a meeting and i got the same Skype for Business Web App Prompts. Seems nothing new here. Dam it. I thought the on premises guys are left behind again but fear not.


Then i thought as its listed twice perhaps it needs enabling ? Then i found this


And i noticed these steps

So it seems there is now a Skype Web App and Skype Meeting App more details on this here https://support.office.com/en-us/article/Join-a-Skype-for-Business-meeting-with-Skype-Meetings-App-Skype-for-Business-Web-App-4828ad18-ed21-422a-a870-94d676d4b72a?ui=en-US&rs=en-US&ad=US#Version=Skype-Meetings-App 


and its dependent how the deployment is configured to which is available. Both still need a plugin installation. The default with SfB Server event with CU5 is SkypeWebApp.

Once i had the meeting app installed and went to join a meeting after when i click the Meeting join it launch the Skypemeetingapp straight away and i entered my join and i was in. Once better user experience than the SkypeWebApp.

If you don’t have the desktop version of Skype for Business, or don’t have a Skype for Business account, you can use Skype Meetings App or Skype for Business Web App to join a Skype for Business meeting from your browser.

Depending on how your organization is set up, you will use either Skype Meetings App or Skype for Business Web App.

It seems for to enable the Meeting App we need to do something on the backend and here it is.

It appears for the Meeting App we allow access to the CDN where the meetings App can be downloaded from instead of from your Skype for Business server.  Also allows the simplifed meeting join experience and noted more reliable than webapp.

What is the SkypeMeetingApp and SkypeWebApp and differences before we enable it from here

Whenever a user clicks a meeting URL but does not have the Skype for Business client installed, the user is presented with the option to join the meeting by using Skype for Business Web App.

The default server behaviour is to interact with a user to download and install Skype for Business Web App to join the meeting.

Starting with CU5, Skype Meetings App is available as a replacement for Skype for Business Web App. Skype Meetings App offers a simplified browser experience for downloading and installing the app and joining meetings, including one-click join for users of Internet Explorer. Skype Meetings App also has many improvements over the Skype for Business Web App for reliability and the meeting experience.

If Skype Meetings App is enabled, users will download the latest version of the app from the online Content Delivery Network (CDN) rather than from your Skype for Business server.

Skype for Business Server 2015 works with the Skype for Business Web App by default. The Skype for Business Web App is stored on the Front End Server and gets sent to the meeting attendee.

As of Skype for Business Server 2015 CU5 or later, meetings held using Skype for Business Online will no longer send a clientless user the Skype for Business Web App, they will instead be sent Skype Meetings App. As of Skype for Business Server 2015 CU5 or later, if you Enable the simplified meeting join experience and Skype Meetings App, clientless users will be sent Skype Meetings App instead of Skype for Business Web App.


Enable Skype Meetings App to replace Skype for Business Web App (Optional)
This procedure is optional. If you do not use it, external users will continue to join meetings using Skype for Business Web App.

Enable simplified meeting join and Skype Meetings App

1. When you enable access to the Content Delivery Network (CDN), users will have the ability to connect to CDN online and get Skype Meetings App, and will use the simplified meeting join experience.

Set-CsWebServiceConfiguration -MeetingUxUseCdn $True

2. Allow client side logging telemetry from the meeting join web page or the Skype Meetings App to be sent to Microsoft servers (the command defaults to false).

Set-CsWebServiceConfiguration -MeetingUxEnableTelemetry $True

Information sent to Microsoft is in strict compliance with Skype for Business data collection practices.

3. Set the timeout before fall back to the locally hosted Skype for Business Web App experience if CDN isn’t available. The default value is 6 seconds. If this value is set to 0, there will be no timeout.

Set-CsWebServiceConfiguration -JoinLauncherCdnTimeout (New-TimeSpan -Seconds 10)


First i thought id check the settings after applying CU5


By default the MeetingUXCDN was set to false so the Skype Web App was always being used.

So i went along and completed these steps on my Standard Edition Front End server in my lab

MeetinApp Capture1

After running the cmdlets i tried to join again and look what i got Smile I have the



So i clicked the Install and join with Skype Meeting Apps



The help link took me to Microsoft site for skype meeting help.



Check out Toms Post on more details on the Skype MeetingApp



And job done i have the same meeting experience as SfB Online now and its simpler and easier for my users. Again for an easier life Smile









Plan for Web downloadable clients


Supported Platforms for SkypeMeetingApp and SkypeWebApp


Skype for Business Server 2015 Cumulative update 5 May 2017

There’s a new Skype for Business Server 2015 cumulative update May 2017 which is CU5.

This update notes enables Location-Based Routing to support the Skype for Business mobile clients. This was mentioned on the previous CU4 HF1.

This CU seems a biggy with many many fixes and new stuff as well in it. Took a while to read over them. There’s updates and fixes for lots here

  • Pool Pairing fixes
  • voicemail
  • Busy on Busy
  • In Place upgrade
  • Allows move a meeting room object from a Microsoft Skype for Business Server 2015 on-premises environment to Microsoft Skype for Business Online

What i cant see and i was looking for is SfB Server support on Windows Server 2016. I check the Supported OS list here and i cant see support yet here

Update 19/05/2017 – Thanks to @tobiefysh on twitter he spotted Window Server 2016 is supported with CU5 or later now


We may just have to wait a little longer.doh!

*** Update*** 19th May -  I found this link on Microsoft Tech Community that notes in the comments  CU5 does not support Windows Server 2016. There some great information on whats new though check it out here

In addition to various bug fixes, several new features are included in this update.

From Microsoft Tech Community – What’s New: 

1. Enable Delegate Management in UCWA (Unified Communication Web API)

2. UCWA scopes based authorization supported for onprem

3. CORS (Cross Origin) supported for onprem

4. JoinLauncher: Port Modern Meeting Join Experience to W16

5. Fix move-csmeetingroom cmdlet for onprem->online move

6. Supporting CallerID policy for hybrid tenants

7. Create New-CsOnPremApplicationEndpoint commandlet (Intune)

Modern Meeting Join Experience

For the JoinLauncher: Port Modern Meeting Join Experience to W16 i thought they might have brought the new Office 365 Meeting Join experience to on premises.

But after installing CU5 i still got the old meeting join page Sad smile tried a restart but the same. Seems we still need to wait for this to come on premises.


But i managed to work out you need to enable the new meeting experience following CU5 installation ! Check this blog post out here Smile


More details on the new SkypeMeetingApp with CU5 in my blog post for enabling from here

Starting with CU5, Skype Meetings App is available as a replacement for Skype for Business Web App. Skype Meetings App offers a simplified browser experience for downloading and installing the app and joining meetings, including one-click join for users of Internet Explorer. Skype Meetings App also has many improvements over the Skype for Business Web App for reliability and the meeting experience.

If Skype Meetings App is enabled, users will download the latest version of the app from the online Content Delivery Network (CDN) rather than from your Skype for Business server.

Skype for Business Server 2015 works with the Skype for Business Web App by default. The Skype for Business Web App is stored on the Front End Server and gets sent to the meeting attendee.

As of Skype for Business Server 2015 CU5 or later, meetings held using Skype for Business Online will no longer send a clientless user the Skype for Business Web App, they will instead be sent Skype Meetings App. As of Skype for Business Server 2015 CU5 or later, if you Enable the simplified meeting join experience and Skype Meetings App, clientless users will be sent Skype Meetings App instead of Skype for Business Web App.

Version Number for this update – 9319.281

Lets dig into some details.

Skype for Business Server CU5 details

Man there’s alot of issues ! This update enables Location-Based Routing to support the Skype for Business mobile clients. It also fixes the following issues

Improvements and fixes in the May 2017 update
Fix and Improvement Symptom / Cause
  • 4020997 Skype for Business Server 2015 Front-End service may crash in Windows Server 2016
When you configure multiple Microsoft Skype For Business Front-End pools on computers that are running Windows Server 2016, the Skype For Business Server Front-End service (RTCSrv.exe process) may be unable to start and crash in crypt32.dll.

This issue occurs because the certificate chain of a certificate that’s used by a Front-End server in a different pool cannot be validated.

  • 4020994 Event ID 36023 is consistently logged on Multiple Front-End servers in a Skype for Business Server 2015 environment that enables CAC

When this issue occurs, the Bandwidth Policy Service event ID 36023 is logged on front-end servers every few minutes.

Note When this issue occurs, there is no actual function effect in Skype for Business Server 2015.

This issue occurs because the delay in call admission control (CAC) verifications for Inter-Cluster mode is set incorrectly.

  • 4020993 DTMF tone isn’t played when some DTMF packets are dropped in the network in Skype for Business Server 2015

Consider the following scenario:

  • You deploy a dual tone multi-frequency (DTMF) based Interactive Voice Response (IVR) application in a Microsoft Skype for Business Server 2015 environment.
  • The application is developed by using Unified Communications Managed API.
  • The application joins a conference.
  • A user connects to the application, and then the user starts pressing DTMF digits.

In this scenario, the DTMF tone is missing.

This issue occurs because the Audio Video Multipoint Conferencing Unit (AVMCU) does not process the DTMF tone when the DTMF packets that carry the end of tone flag are dropped in the network.

  • 4020991 Enables “move-csmeetingroom” cmdlet to move meeting room from on-premises to Online in Skype for Business Server 2015
The update supports administrators to move a meeting room object from a Microsoft Skype for Business Server 2015 on-premises environment to Microsoft Skype for Business Online in Microsoft Office 365 by running the Move-CsMeetingRoom cmdlet.
  • 4020987 The update to OcsMcu.msp can’t be applied when conferencing is disabled in Skype for Business Server 2015
Assume that you have a topology where conferencing is disabled. This means that ASMCU and AVMCU should not be installed. When you try to apply patches to Microsoft Skype for Business Server 2015, you find OcsMcu.msp is not able to be installed.

This issue occurs because OcsMcu.msp tries to find the RTCASMCU and RTCAVMCU services that aren’t present because conferencing is disabled on the topology.

  • 4020984 The ms-client-diagnostics header for application sharing scenario is not correctly formatted in Skype for Business Server 2015
The ms-client-diagnostics header that’s used to troubleshoot application sharing issue is not correctly formatted.

This issue occurs because the incorrect type is put in the MediaType filed in a diagnostic blob that is added to the ms-client-diagnostic.

  • 4020983 “sorry, I didn’t get that…” GVA announcement is triggered by external audio sources in Skype for Business Server 2015
When you have a Microsoft Skype for Business conference call ongoing in a Microsoft Skype for Business Server 2015 environment, participants in the conference call occasionally hear the following Group Virtual Assistant (GVA) announcement:

The GVA announcement is triggered by external audio sources that sound like a dual tone multi-frequency (DTMF) tone.

Note The external audio sources that are identified are as follows:

  • A Windows notification sound that’s confirmed to technically resemble the audio wave of the * DTMF tone.
  • DTMF tones that are played by other phones in speaker mode nearby an audio device that’s connected to a meeting.

  • 4019726 Call remains ringing on a PSTN phone when you click End Meeting in a Skype meeting in Skype for Business Server 2015

Consider the following scenario:

  • You join a Skype meeting in a Microsoft Skype for Business Server 2015 environment.
  • You invite a Public Switched Telephone Network (PSTN) number to the meeting.
  • You click the End Meeting button before the PSTN callee takes the call.

In this scenario, the call continues to ring on the PSTN phone.

This issue occurs because the Audio Video Multipoint Conferencing Unit (AVMCU) cannot send the Cancel request to the Mediation Server.

  • 4019725 Event ID 44005 and 44008 are logged when you try to leave a voicemail in Skype for Business Server 2015
You can’t leave a voicemail until the Skype for Business Front-End service gets restarted in a Microsoft Skype for Business Server 2015 environment.

This issue occurs because the Skype for Business Front-End service cannot connect to Domain Controller to read dial plan records.

  • 4019724 You cannot join Skype meeting after you perform a pool failover in Skype for Business Server 2015

Consider the following scenario:

  • You deploy two paired Front-End pools in a Microsoft Skype for Business Server 2015 environment.
  • You perform a pool failover to fail over to the backup pool.
  • A user creates a Skype meeting.
  • You perform a pool failover to fail back to the primary pool.
  • You join the meeting that’s created by the user.

In this scenario, you can’t join the Skype meeting.

This issue occurs because the conference data is inconsistent between the primary pool and the backup pool.

  • 4019723 Agents in a Response Group can’t receive call after you invoke pool failover in Skype for Business Server 2015

Consider the following scenario:

  • You deploy two paired Front-End pools in a Microsoft Skype for Business Server 2015 environment.
  • You deploy Response Group Service (RGS) in the environment.
  • You perform a pool failover by running the Invoke-csPoolFailover cmdlet between the two paired Front-End pools.
  • After the pool failover, you run the Import-CsRgsConfiguration cmdlet to import the Workflows, Queue and Agents to the paired pool.
  • You make a call to a Response Group.

In this scenario, the agents in the Response Group can’t receive the call.

This issue occurs because the value of the EnterpriseVoiceEnabled parameter isn’t set to True when you run the Import-CsRgsConfiguration cmdlet on the backup pool.

  • 4019722 Event ID 30210 occurs when you try to leave voicemail in Skype for Business Server 2015

You cannot leave a voice mail message until the Skype for Business Front-End service is restarted in a Microsoft Skype for Business Server 2015 environment. Additionally, the following event is logged on the Microsoft Skype for Business 2015 Front End server.

Time: Date/Time
ID: 30210
Level: Warning
Source: LS Applications Module
Machine: SERVER Name
Message: Lync Server application is not responding and is being disconnected.

Application Uri ‘http://www.microsoft.com/LCS/ExumRouting‘ Cause: This can occur if the managed application is slow to respond to messages or if the server is under heavy load or the application has become unresponsive.
If the server load is too heavy, consider getting a faster machine or hosting fewer users on the server. If the application is slow, contact the author of the application.

This issue occurs because the ExUMRouting application is uninstalled from the TrustedServerList.

  • 4015911 Pool failover fails when you have many conference directories in Skype for Business Server 2015

Consider the following scenario:

• You deploy two paired Front-End pools in a Microsoft Skype for Business Server 2015 environment.

• You create many conference directories.

• You start pool failover between the two paired Front-End pools.

• There are many meetings being scheduled during the pool failover.

In this scenario, the pool failover fails.

This issue occurs because a back-end SQL stored procedure takes more than one minute to sync the change of the conference directories.

  • 4015910 Event ID 53106 "Unable to Save Message" occurs in Skype for Business Server 2015 Persistent Chat Server

When you configure the Persistent Chat Compliance service in a Microsoft Skype for Business Server 2015 multiple-server pool environment, the following event is logged on the Skype for Business Server 2015, Persistent Chat server.

Time: Date/Time
ID: 53106
Level: Error
Source: LS Persistent Chat Compliance Server
Machine: SERVER Name
Message: Unable to save message Date/Time PART ma-chan://domain.com/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX X XXXXX to database due to exception:
CmdID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX The server could not restore db connection within the allowed time (00:10:00) using connection string: Data Source=SERVER.domain.com\PCHATDB; Initial Catalog=mgccomp; Integrated Security=SSPI. at
at Microsoft.Rtc.Internal.Chat.Server.ServerCommon.Database.DbCommand.executeUntilSuccessOrTimeout[TR](Fun`2 executeDelegate, RetryInfo retryInfo)
at Microsoft.Rtc.Internal.Chat.Server.ServerCommon.Database.DbCommand.executeImp[TR](Fun`2 executeDelegate, Int32 retryTimeoutInMs)
at Microsoft.Rtc.Internal.Chat.Server.ServerCommon.Database.DbCommand.ExecuteNonQuery(Int32 retryTimeoutInMs)
at Microsoft.Rtc.Internal.Chat.Server.Compliance.ComplianceDataAccess.Save(RawComplianceData data)
at Microsoft.Rtc.Internal.Chat.Server.Compliance.ComplianceServer.Save(RawComplianceData data).

This issue occurs because of a race condition when you update tblComplianceParticipant table entries.

  • 4015907 Update that enables simplified meeting join experience in Skype for Business Server 2015

This update enables the simplified meeting join experience and Skype Meetings App in Microsoft Skype for Business Server 2015.

For more information, refer to the following links:

  • 4015904 Enables UCWA to populate "OTHER CONTACTS" and "FAVORITES" groups at first sign in to Skype for Business mobile app
This update enables Unified Communications Web API (UCWA) to auto populate the OTHER CONTACTS and FAVORITES default groups when you sign in to a Microsoft Skype for Business mobile client for the first time in a Microsoft Skype for Business Server 2015 environment.
  • 4015902 Failed to start MatchMaking service and its dependencies if FIPS for RGS is enabled in Skype for Business Server 2015

This issue occurs when Federal Information Processing Standards (FIPS) for Response Group Service (RGS) is enabled in a Microsoft Skype for Business Server 2015 environment.

Additionally, when you establish application endpoints, you may see the following exception:

Exception: System.Reflection.TargetInvocationException – System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.SHA512Managed..ctor()
— End of inner exception stack trace —

at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)
at System.Security.Cryptography.SHA512.Create()
at Microsoft.Rtc.Acd.Common.ConsistentHash`2..ctor(Func`2 nodeToHashKeyConverter, Func`2 requestToHashKeyConverter, Int32 virtualNodesMultiplier)
at Microsoft.Rtc.Acd.MatchMaking.PresenceProvider.PresenceComponent.Initialize(IReadOnlyCollection`1 presenceEndpoints, Int32 maxRgsAgentsPerPresenceWatcher)
at Microsoft.Rtc.Acd.MatchMaking.MatchMakingService.Start(IReadOnlyCollection`1 presenceEndpoints)
at Microsoft.Rtc.Acd.AepManager.StartMMAndItsDependencies(IReadOnlyCollection`1 presenceEndpoints)
Cause: Failed to connect to Front End server or the Front End server is misconfigured.
Resolution: Check the Front End server for errors.

This issue occurs because the MD5 and SHA512Managed classes don’t have FIPS enabled.
  • 4015901 Calls to RGS may fail after an in-place upgrade from Lync server 2013 to Skype for Business Server 2015
The Response Group Service (RGS) service fails to start after an in-place upgrade from Microsoft Lync Server 2013 to Microsoft Skype for Business Server 2015 when you apply the May 2017 cumulative update 6.0.9319.281 in certain situations.

In Skype for Business Server 2015, the default design is changed to use three Presence Watcher contact objects (instead of one Presence Watcher contact object in earlier versions). The service startup failure is introduced to prevent an issue in which the service has started, but calls to RGS fail with "500 Internal Server error", because only one Presence Watcher contact object is found after the start of the RGS service.

  • 4015900 Enables “VoicemailOnBusy” ActionType to be set for Exchange Online users in Skype for Business Server 2015 Busy Options

Consider the following scenario:

  • You have enabled Busy Options feature in a Microsoft Skype for Business Server 2015 environment that has Cumulative Update 2 (Version 6.0.9319.235) or later versions installed.
  • You enable a user for Microsoft Exchange Unified Messaging (UM) On-Premises.
  • You move the user’s mailbox to Exchange Online.
  • You enable the user for Exchange UM Online by assigning on-premises hosted voice mail policy.
    Note The on-premises attributes for this user are now set as follows:
    • ExUmEnabled=False
    • HostedVoiceMail=True

In this scenario, you can’t set the BusyOnBusy option to an ActionType of VoicemailOnBusy for this user.

Additionally, you receive the following error message:

PS C:\Users\SfBadmin> Set-CsBusyOptions -Identity "Ken Myer" -ActionType VoicemailOnBusy
Set-CsBusyOptions : Voicemail is not enabled for Identity "Ken Myer".
At line:1 char:1
+ Set-CsBusyOptions "Ken Myer" -ActionType VoicemailOnBusy
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Set-CsBusyOptions], BobException
+ FullyQualifiedErrorId : Microsoft.Rtc.Management.Bob.Cmdlets.BobSetConfigurationCmdlet

This issue occurs because the VoicemailOnBusy action type was designed to support only on-premises Exchange UM deployments.

  • 4015899 "Busy Options" feature doesn’t check the second incoming call in Skype for Business Server 2015

Consider the following scenario:

  • You have enabled Busy Options feature for internal Skype for Business users in a Microsoft Skype for Business Server 2015 environment.
  • You have the following restriction in your manifest file:
  • You are in a call with another federated user.
  • A user is trying to call you.

In this scenario, you find double toast notifications.

This issue occurs because calls to federated users are not tracked by Busy Options when the domainSupported parameter is set to true.

  • 4015898 RGS agents may stop receiving calls after you run the “Enable-CsTopology” cmdlet in Skype for Business Server 2015
Assume that you enable response group service (RGS) in a Microsoft Skype for Business Server 2015 environment. When you run the Enable-CsTopology cmdlet to have the changes published, some RGS agents can’t receive toast notifications even their presence status is available.

This issue occurs because the presence watcher is reset when the Enable-CsTopology cmdlet is invoked.

  • 4015893 Enables delegate management feature for Unified Communications Web API in Skype for Business Server 2015
This update let you enable the delegate management feature for Unified Communications Web API (UCWA) that’s based on Microsoft Skype for Business Server 2015.

To get this update, install the May 2017 cumulative update 6.0.9319.281 for Skype for Business Server 2015, core components.

Note After you install this update, run the following Skype for Business management PowerShell command to enable the feature:

‘Set-CsPlatformServiceSettings –EnableDelegateManagement $true’

Restart Required

Seems after CU5 its best to restart as the new cmdlets for enabling the new Meeting UX may not display. More great information on this on Randys blog below. check it out.


There seems to be quite a few components are require updating



Seems like one DB update on rtcxds

DatabaseName  ExpectedVersion InstalledVersion
rtcxds 15.13.11 15.13.10
rtcshared 5.0.1 5.0.1
rtcab 62.42.12 62.42.12
rgsconfig 5.5.1 5.5.1
rgsdyn 2.2.1 2.2.1
cpsdyn 1.1.2 1.1.2
xds 10.15.4 10.15.4
lis 3.1.1 3.1.1
mgc 1.42.1 1.42.1

Download Link






Microsoft Teams–How to use the Teams Bandwidth Calculator video Summary

Continuing with Teams summaries i wanted to provide a summary of the latest video available on the success with teams academy which is “How to use the Bandwidth Calculator”. Thanks to Tom Arbuthnot for pointing out the new video as well.

Critically important to teams as it uses real time media is your network and also ensuring enough bandwidth is always available so before your deployment preferably check this tool out.

Plan before you deploy !

Calculator Link below to check it out.



Information on presenter Korneel Bullens



Calculating Bandwidth is IMPORTANT !

a well prepared network delivered great quality!

calculator tool to help guide you but note tool is based on typical value and assumptions so calculations must be monitoring and confirmed during deployment.



Usual disclaimer with Cloud sessions this is the April 2017 recording and content is subject to change.

Lets go!



Why calculate bandwidth?

  • help prepare for possible impact of adding Microsoft Teams to your network
  • quality is critically important !
  • User experience is key!
  • fundamental for a successful deployment !
  • not preparing network will lead to issues and poor user experience and adoption !
  • More return on ROI and more people will use it !
  • Don’t want to scare people from using it
  • MANDATORY when using Microsoft teams to calculate bandwidth and impact to network!
  • The quality and bandwidth available on the network is KEY ! Plan, Plan, Plan

Also from me with experience on SfB side when you look at networks and bandwidth consider the different types of network people will connect to, use and how media will flow. For example, LAN, WiFi, Internet, MPLS, IP VPNs, connect to Office 365. IPSec VPN encryption impact to media traffic. Will users use Desktop or mobile clients will desktops be connected to Lan or WiFi or ive even seen both ! Is the network ready for real time media / communications. Just because you can quickly enable and deploy teams doesn’t mean you want to skip planning phase and network is critical.

What is calculated with the tool ?


  • Uses averages and typical values (NOT MAXIMUM by default)
  • 60% of time people speak and 40% people are silent
  • Number is based on expected usage when number of users is entered in the tools
  • Monitoring and adjusted may be requirements as there could be peaks for example all users after lunch all jump in meetings.
  • Great for guidance, keep monitoring and adjust as needed
  • Typical NOT maximum values
  • keep these in mind these are typical !
  • QoS may need to use maximum numbers
  • guidance available on maximum numbers below


  • Best practice no more than 30% being used by real time traffic
  • Based on average usage
  • For max values multiple by 1.4 mentioned roughly here
  • For max 1.4 is based not on all users making calls at the same time, calculates based on the 60% people speak and 40% silence and making them 100% speaking.

Where to find it ?



How to use ?


  • Add up to 10 rows
  • Site names
  • user counts
  • remote percentage – how many working remotely from home / road. 20% good starting numbers
  • Teams usage – will it be used heavily
  • P2P – peer to peer (one to one)
  • Conferencing – how much will it be used for conferencing
  • if you set one conferencing value to low then all the other should be set to low
  • Medium and 20% remote is default and typical Microsoft find


Sites added as shown above – note video for one set to none as users dont have video cameras in this example.



WAN Impact usually means MPLS (Maybe VPN) between sites

O365 Impact – usually internet connection to Office 365 (Maybe ExpressRoute)

Notice above Houten has huge difference in WAN and O365 impact due to no video camera. Video consumed the most bandwidth.

Export button available as well to export to excel


  • recommended for new site please revisit the bandwidth calculator as formulas may get updated.


Important to understand these !


  • Based on typical bandwidth (max can be used using multiple value by 1.4)
  • Monitoring of usage after deployment is required
  • Based on assumed usage


  • Calculate before you deploy !
  • be prepared before you deploy!





Introduction to Microsoft Teams Summary

So wanted to give a summary of the Microsoft teams videos series available on Success with Team Microsoft site here in the academy section.

Similar to the Skype Academy videos series i wanted to summarise the video in a blog post for myself and hopefully people may find this useful. I recommend watching the video as well if you have time.

Some great downloads to start with on Team planning and guidance.

First up we have introduction to Microsoft Teams which is a good start.


This is part 1 of a two part series


As usual with Cloud based solutions a training disclaimer and information is valid as of March 2017 and innovation is on-going.



We will learn about What is Microsoft teams and introduction, features and requirements.

Key Learning’s on Teams


Teams is a Chat based collaboration hub allowing ad-hoc and scheduled meetings with audio, video and sharing. Teams is based on channels and can be extended.


Out of scope for this session in Part 1, this is included in Part 2 which ill summarise soon.


This training has already been updated since preview so if you have already seen this content previously look out for the banner in the top right and ill try and flag this as well.


Introduction to Microsoft Teams


First we need to look at the way we work has changed.


  • People are part of 2 times the amount of teams when compared to 5 years ago
  • Amount of time on meeting calls and meeting has increased by 50%
  • This type of work takes up to 80% more of their time
  • Also noted are team members are internal and external, geographical dispersed


Team fits in Office 365 collaboration portfolio by giving teams easy access to information via a team based hub.


  • People can see content and chat history anytime, if your familiar with Lync / SfB persistent chat is similar in the way it has chat history and chat isn’t lost when you close the client.
  • Chats are team based or private and there is mobile access on most mobile platforms so teams can be accessed anywhere on any device.


Its not just chat its content

Also easy assess to apps to what teams rely on.


Customizable for each teams with different channels for topics



Security is important designed for great experience to protect customer and team data.



Built upon existing services in Office 365 to unify collaboration into one place



Teams – group of people working on a project


  • Look into the UI, you see the Northwind trader team highlighted with multiple channels marked as a favourite
  • option to swap between activity, chat, teams, meetings and files on left hand side of the ui.
  • search bar is global search

Creating Teams


  • Teams can be added as security, distribution groups, email aliases or individually
  • Private Office 365 groups can be migrated straight to team.
  • Team creation is lower left hand corner with team name, description and has privacy setting choose from public or private
  • General channel is default and cant be removed.

Public Teams


  • Public teams viewable by all and all people can find them.
  • 999 people max people size



  • Channel are the building blocks of Teams !
  • To view channels under teams they must be marked as a favourite, other channels are viewable from the more button.
  • Discussions in progress on a favourite channel is marked in bold


  • any users can create channels on any topic
  • try and keep discussion around the channel
  • activity in the channels are presented via a toast notification
  • any users can follow a channel


  • Team Owner
  • Team Member


  • Up to 10 Owners per team!
  • Owners have most rights
  • manage team settings, rename team and delete teams


  • TM can still create channels within a team
  • up to 999 people per team
  • edit channel names and descriptions
  • add tabs connectors and bots can be removed by team owners

Some sample teams and channels


Great to have some examples or teams and their team channels.

Product Team A shows Cross department teams as well.



  • threaded conversation so replies don’t get lost.
  • New topics can be started as well using text box at the bottom.
  • GA update auto scroll is released so messages in flight will be added and viewable if open on screen.


  • Message composer for adding text, updated with keyboard shortcuts and optimized for text entry.
  • Updated from preview



  • Channel has unique email address and can be directly emailed
  • replies only visible in teams


  • Like and save messages
  • Like added a thumbs up
  • save for later adds bookmark icon which can be viewed later


Activity shows your like and saved messages in order across all teams your apart of.


  • Documents uploaded are stored in SharePoint site thats created when team is created
  • Upload can be new thread or existing.


  • Mention team members using @
  • or whole team if enabled by team owners

for a bit of fun as well in teams we have

  • Emojis
  • gifs
  • stickers


Private conservations


Team conversation are public but Teams also has private chat.


  • Use the chat icon on the left hand side to view private chats
  • Chat you can have audio and video and mobile one to one calling
  • Private chats can be group chats for up to 9. Chats are not threaded


Private chats can also share files but a difference here is the file is stored in your OneDrive for Business accounts and shared out from there.




  • Use the meet now icon in compose box or from existing conversation
  • Only available on desktop clients


When in a meeting you can invite people by clicking on the people names and it will send a toast notification to join the meeting.


  • Team members can see who in a meeting with the camera icon appears next to channel name and they can see who’s in the meeting
  • You can join into a meeting
  • If you not in the meeting you can still see the chat in the meeting



  • Full screen video experience (similar to SfB Mac Client)

Sharing content


  • Content with Video in bottom right hand view
  • four most active member in video can be swapped
  • click on any active member to swap to video and content preview


Meeting History

Really nice touch i think


  • Team members can see when meeting took place and who with and what was discussed in the text.
  • useful is certain member of the team weren’t available at that time.

Scheduled Meetings


  • Meeting scheduled in teams or Outlook
  • Viewable in team client under meeting icon on left hand bar
  • Details of meeting invite
  • join online meeting either in SfB or team
  • SfB meetings will launch SfB
  • New meetings can be created
  • when invitees are added suggested times are suggest



  • Tabs are always visible along the top


  • default tabs , files in files
  • new wiki tab you can draft docs collaborate, work and work in all one tab


Add tabs such as

  • PowerBI reports
  • Excel
  • OneNote
  • Word
  • YouTube
  • Secure Websites



  • tracking tasks
  • work items
  • ideal for project management in familiar kamban board


New for GA – Wiki tab you can draft docs, chats, notes edit and share ideas in all one place.

the tab or all tabs Winking smile


  • Chat about a tab and track document comments and discussion all in one place



You can even develop your own tabs !


integrated with Office 365 connectors

to add click the three dot





Option to discover bots and drag and drop


  • have to mention the bot to communicate with it.
  • bots helps aiding adoption


  • Custom bot new in GA


Client Managed settings


Team owner settings


  • Set contact rating
  • set more resticted setting than tenant


any user can customise the notification setting including SfB interop




Licencing is important as always

  • Above are the SKUs required for team, most enterprise with E1, E3 or E5 are already licenced for teams!
  • E4 gone but not forgotten with teams


Recommend to have Exchange Online with users mailbox online and SharePoint Online

Practical guidance doc has more information if you don’t meet these requirements


  • unsupported web browsers will be BLOCKED and recommended to use mobile or supported client


interactive workshop and bandwidth calculator



There’s alot of good stuff here!










References and Resources above


Teams Bandwidth Calculator


Practical Guidance Document Download


Planning Workshop Kit


Skype for Business Online Cloud PBX Voicemail transcript Summary

Well this announcement came out of the blue for me but its awesome its here! its a new feature to Azure Voicemail for SfB Online Cloud PBX users but has been available with Exchange UM for a while.

I don’t often use voicemail a lot but anyway to quickly view what a voicemail is about is great as i can hopefully see how urgent it is, also phone numbers left in VMs are now in text in your inbox and also for users with hearing impairments its great to have voicemail as text as well.

Cloud PBX voicemail doesn’t use Exchange UM as it utilises Azure Voicemail platform. There are currently it seems seven language available for transcribing which I’m sure will grow and grow.

Language recognition is based on users language setting in voicemail and is changeable on user and tenant level. For users level Sign in to the Office 365 portal. In the portal, go to Settings and change the language to the language of your choice


This feature is enabled by default now so you don’t have to do anything ! unless as an administrator you want to disable that is.

As admin Turn off at tenant level

Set-CsOnlineVoicemailPolicy -EnableTranscription $false

or for a user Grant-CsOnlineVoicemailPolicy -PolicyName TranscriptionDisabled -Identity sip:brucewayne@ucmart.co.uk


So heres a test drive of the new feature.

I called my Cloud PBX PSTN number from my mobile and call was forwarded to voicemail and i left a message as Dave.

In the voicemail i said “ Hi Martin, its Dave just wondering if you could give me a call back please as i don’t to talk to you about something, thank you, bye bye.

So it didn’t transcribe it 100% but overall it transcribed the message well but missed out the person name.

Also it mentions below “Transcription service is in preview state”


If you follow the feedback you can leave feedback and comments on the transcription


I left some  more messages and it wasn’t catching peoples names or numbers, suggested a few times i said I’m off today which i didn’t say and added a time for a meeting which i didn’t say so its work in progress.

Tried to leave phone number and this message didn’t transcribe at all.


No name mentioned and it suggested a time for the meeting which i didn’t say.


This one had a phone number but missed the first zero and added extra numbers.



I think the transcription will without a doubt get better as it learns more and it does mention transcription in preview and will improve.

I think its great to have and Exchange UM transcription wasn’t 100%. I do wonder how it will cope with accents though.

Also i think its a good idea to let your users know this feature is enabled now.



Change VM Language for whole tenant


Skype for Business Mac Client March 2017 Update Summary – Note UCWA dependencies

There been a new March 2017 update released for the Skype for Business Mac Clients. This could be cumulative update 4 i cant see it mentioning cu version anywhere at the mo so its march update for the SfB Mac Client with a lot of new features and bugs addressed which is great and shows Microsoft hard work with improving the mac client.

The March 2017 update brings a huge number of new features and improvement to the Mac client which is great !

Be careful though as some functionality is dependent on if your running Lync Server 2013, SfB Server 2015 or SfB Online. Only SfB online has all the functionality available. Please see below in the UCWA dependencies section.

More info check out on info on Tech Community here


You can AutoUpdate or the Manual download link if below. Suspect the new update will be there soon.


March 2017 Update Version Number

With 28th March 2017 update –

Features Added / Bugs

There’s a lot of new features added and also a good number bug fixes which are  from Microsoft Tech Community site.

Features Added Details
Users can now add delegates to “My Delegates” group in contact group and set call routing preferences to delegates
Delegates can see who has made them a delegate.
Delegates can make calls on behalf of a delegator. Note: Delegate/delegator features are currently available for Skype for Business Online customers only. More features to come.
Users can add a separate audio setting for a “ringing” device.
Users are prompted to switch to device when user plugs in USB device.
Added “Groups” button to the Contact Card and detailed Contact views, so users can quickly add other users to their contact list.
Users can call and send IMs to the DL and Groups via the Group Contact Card.
Messages are now separated by date.
Added support for option SIP URIs in chat window.
Admins can set the email and username with user profiles
Users will now occasionally be prompted to rate their call experience
Further Improvements / Bug Fixes
Fixed a false warning about Conversation History availability when the computer resumes.
Fixed an issue about users not receiving an error message when trying to sign in to Skype for Business on Mac on a network that uses network proxy server without configuring the HTTP proxy setting.
Fixed various headset mute/unmute problems.
Fixed issues related to muting and connectivity.
Fixed issues related to muting and connectivity. Note: Existing meetings scheduled by Mac client on Skype Room Systems must be rescheduled for fixes to apply.
Users will be prompted to sign in to Exchange for meeting and calendar updates, if they are not already signed in to Exchange.
Improved screen sharing in 1:1 conversations.
Improved ending a call — some users could not end call when in the lobby.
Improvements to voice-over announcements and other accessibility improvements
Changed the position of the message “Your microphone is muted” and call controls
Implemented other UI improvements and bug fixes.
Fixed crash issues.

PLEASE NOTE – UCWA Dependencies !!!

Client functionality is now also based on UCWA dependencies in the server version and from the screenshot below taken from Tech Community training here and academy recording here you can see that Lync Server 2013 is missing the most functionality, followed by SfB Server and Skype for Business Online has all client functionality.

This is key to understanding new features and the dependency they have with the server version and UCWA. For all functionality you need to be running SfB Online, sorry server guys Sad smile


Don’t forget about Known Issues

Its worth reading over these as there’s quite a few ! – Updated 28th March 2017

E911 support required SfB Server CU4 or Lync Server 2013 CU8 HF2 – Please make sure you have these updates deployed if you require E-911 services. It does state the below in grey though. Also in known issues it mentions E-911 with ADFS not supported yet.

Important: Users will not be able to dial 911 until the CU4 server update is applied.

Also mentions the requirement for mobility again and the requirements for the latest SfB Servers and Lync Server 2013 CUs if you don’t have mobility enabled.

Other known issues that took my interest are below but there’s more so please check them out before you get questions and helpdesk tickets.

  • E-911 with ADFS not supported
  • Presence does not automatically update to “In Meeting” based on Outlook calendar
  • Multiple prompts to leave meeting when pressing the hang-up button on a UC USB device
  • Single/tabbed window experience not available
  • Search contacts limitation
  • Desktop viewing in Skype for Business on Windows client

More known issues details check them out i recommended it.


How do i update ?

Two methods which are the same as the previous updates.

  • Either using the Microsoft AutoUpdate (MAU) if you have already deployed the SfB Mac client already Smile ( I did try but was showing older version at the time of writing this)
  • Or for new users a manual download via Microsoft download centre here

Do i need to update Lync / SfB Servers ?

For the March 2017 CU  the requirements server side are the same as previous SfB Mac Client Cumulative updates but on the known issues page there are two important things to note, the first around E911 support which is very important and the second the requirement for mobility to be enabled if you don’t have the latest CUs deployed for Lync Server 2013 or SfB Server 2015. Details are below.

  • 911 support requires Skype for Business Server 2015 CU4 (build 9319.272 or higher, now available) or Lync Server 2013 CU8 HF2  (8308.974) here.

Important: Users will not be able to dial 911 until the CU4 server update is applied.

  • Without Skype for Business Server 2015 CU4 (build 9319.272 or higher, now available) or Lync Server 2013 CU8 HF2 or higher, now available), Skype for Business on Mac requires Mobility enablement on the server side. After updating to builds 9317.272 or 8309.973, Mobility enablement will no longer be required.

It does note under the manual download detail that’s its recommended for the best user experience to ensure customers are running the latest Server side cumulative updates for both SfB and Lync Server 2013. Or it mentions move to Office365 for always up to date infrastructure which made me smile. Downloads link are below.

  • SfB Server 2015 (9319.272) – November 2016 CU4 here
  • Lync Server 2013 (8308.974) – November 2016 CU8 HF2 here
  • Lync Server 2010 – SfB Client not supported I’m afraid so it suggests Mac 2011 client only.

System requirements for Mac
OSX 10.11 (El Capitan) or OSX 10.12 (Sierra)
Outlook Mac build 15.27 (161010) required for Outlook integration

Client Functionality and Client Comparison

Also worth checking out the Client comparison tables for Skype for Business Server 2015 with the new update so you know differences between windows and Mac clients.

Interesting it now notes separate client comparison for Skype for Business Server 2015 and Lync Server 2013

SfB Server list – https://technet.microsoft.com/en-us/library/dn933896.aspx

Lync Server 2013 list – https://technet.microsoft.com/en-us/library/gg425836(v=ocs.15).aspx

Screenshots of AutoUpdate , Manual Process and couple of new features

Booted my iMac up and first got asked to update the Microsoft AutoUpdate Tool. I’ve not booted my mac in a while.


clicked restart app



Seems the new version via AutoUpdate isn’t there yet.

Seem the version available in auto update is the December update. I thought this was applied but lets go.

I also tried Insider Slow and inside fast but both showed no new updates.


So perhaps the CU4 update version isn’t available on AutoUpdate just yet.

Manual Install


Find the package in downloads










Nice touch to ask to trash the installer Smile


Checked version using SfB > About.


Manual download is the March 2017 version, not sure why AutoUpdate wasn’t updating to this version yet but I’m sure it will soon. i had this with the last update.

New Delegates


Set different ringing



Download –https://www.microsoft.com/en-us/download/details.aspx?id=54108

More info on CU4 – https://techcommunity.microsoft.com/t5/Skype-Operations-Framework-Skype/Skype-for-Business-on-Mac-March-2017-readiness-update/ba-p/58369

Known Issues – https://support.office.com/en-us/article/Known-issues-Skype-for-Business-on-Mac-494ac5d5-50be-4aa7-8f5a-669c71c98c9a?ui=en-US&rs=en-US&ad=US

Desktop client comparison tables for Skype for Business Server 2015


Client comparison tables for Lync Server 2013


Skype Academy March Recording – here

Skype Academy presents On-premises PSTN connectivity using Cloud Connector Edition (CCE) Summary

In the series of Cloud PBX Skype academy videos this is Cloud PBX using on-premises PSTN connectivity using Cloud Connector Edition (CCE). This is where you don’t have an existing Lync or Skype for Business Server deployment so greenfield but you have the requirement to use your existing PSTN connection with Cloud PBX.

CCE is a smaller footprint on premises deployment than deployed a full server deployment. Users are all homed online and CCE is used to connect to your on premises PSTN for Cloud PBX users.


Brian nice, principal program manager in Skype product group at Microsoft.

This is based on CCE version 1.4.1 release

What is Cloud Connector and Architecture


Cloud Connector is an extension to SfB Online Service

provides PSTN interconnect for SfB Online users.

Users are homed in SfB Online but PSTN is coming via the on premises Cloud Connector. User still leaves in the cloud but interconnect for PSTN is deployed on-premises.

Cloud connector is a dedicated hypervisor running Hyper-V that has set of sealed virtual machines (4), the VMs perform discrete functions such as Edge, Mediation server, domain controller and CMS.

This is a dedicated appliance and the components work in tandem with each other. The Active Directory deployed in CCE is for the its own environment it has NO communication or integration with an existing on premises active directory. Its its own forest.

The appliance has sip trunks to PSTN Gateways, dial plans is assigned online based on where the user is located. There are options online to restrict internally dialling.

External DNS (SRV and lyncdiscover) is pointed to SfB online not on premises! (There are External DNS records required for CCE but client discovery is pointed to SfB Online)

Key to note in version 1.4.1 there is no support for co-existence with an existing on premises Lync or SfB Servers. Key to note.

There is no media bypass so media always flows via the mediation server!

Users can be created on premises or created in the Cloud. Most organisations will have AD sync via Azure AD connect so users are synced to online.

Below Johns signing in to Skype for Business Online, his SfB client talks to SfB online when John makes a PSTN call now the call signalling is routed from SfB online down to Cloud connector. The call signalling from SfB Online infrastructure to CCE edge to CCE mediation to CCE PSTN GW.


Media traffic will flow via CCE Edge as John is external and on the internet then from CCE Edge to CCE Mediation then from CCE Mediation to PSTN GW.

Media bypass cant be used as discussed earlier




Follow TechNet documentation using the link below


Also worth checking is Skype operations framework

Capacity and PSTN connectivity types are key as these can be different at each site.

Firewall – make sure all required ports are open.

Make sure you have your office 365 Administrator credentials.



Critical one to start with no existing on premises deployment of Lync or Skype for Business server deployed on premises. The current version does not support co-existence!

Qualified PBX / SIP trunk / SBC / Gateway for a full list go here

Dedicated hardware is required for hyper v. the hardware is dedicated for CCE.


Capacity is key and with two different flavours based on hardware specs.

  • Large – typically 500 calls per cloud connector
  • Small – 50 calls per cloud connector (Great for Proof of concepts or smaller call concurrency site requirements)

Hardware spec from above URL

The necessary hardware to support installation of the 4 VMs for each Cloud Connector Edition in your deployment.

  • The following configurations are recommended: (Large 500 simultaneous calls)

    • 64-bit dual processor, six core (12 real cores), 2.50 gigahertz (GHz) or higher

    • 64 gigabytes (GB) ECC RAM

    • Four 600 GB (or better) 10K RPM 128M Cache SAS 6Gbps disks, configured in a RAID 5 configuration

    • Three 1 Gbps RJ45 high throughput network adapters

  • If you choose to deploy the smaller version of Cloud Connector Edition that supports up to 50 simultaneous calls, you will need the following hardware:

    • Intel i7 4790 quad core with Intel 4600 Graphics (no high end graphics needed)

    • 32 GB DDR3-1600 non ECC

    • 2: 1TB 7200RPM SATA III (6 Gbps) in RAID 0

    • 2: 1 Gbps Ethernet (RJ45)

General guidelines, you can up to four Cloud Connecters per PSTN site.

PSTN site is defined in cloud connector when registering. If you have N+1 model with 500 per CCE and 3 active and one idle that gives 1500 simultaneous calls.

N+1 allows for one CCE to fail and still keep 1500 simultaneous call. You could go for all 4 CCEs active and have max 2000 but if one failed you will lose 500 straight away and there’s a risk.

With smaller CCE you can do the same but call capacity is lower with 50 calls per cloud connector, with N+1 again 50 * 3 = 150 simultaneous calls.

Deployment Planning


Host server runs Hyper-V and require internet access, public DNS resolutions and remote PowerShell.

GPO required to prevent forceful unload of user registry at logoff.

Base VM requires internet access and public dns resolutions

External DNS records are required for CCE Edge server and with HA if you have 3 CCEs in one site in HA then you have to have that edge name listed three times. External DNS is critical.

External certificates are required, certificate requests and have certificate available in .pfx format so it can be imported as part of the installation process of CCE. Details available here

CloudConnector.ini – CCE Configuration file


The CloudConnector.ini is critically important and controls almost everything.

IP Addresses, small or large CCE.

Don’t mess this up if there is a mistake is a start over job.

There a deployment checklist, this is printable and recommended to be printed so all details can be written and ensured.


There isn’t a CloudConnector.ini file by default but you can generate one as noted above using export-ccConfigurationsamplefile.

You have to have this file updated before you create a base VM and you need the values for the base VM and the base VM needs internet access.

There’s alot of settings in the .ini recommended to visit here


HA and Multi side Planning considerations


Really important if designing with HA and multi site in mind that you consider the information above. Some parts are the same and some are not with multisite.

Single site with HA (Multiple CCEs up to 4)

Shared folder – same shared folder on all CCEs instances

Virtual machine domain – same across instance

SIP domains – same

Site name – same as they are in the same site

External FQDN – (Access edge) same across all CCEs instance in the same site

External IP – different across instances

Hybrid tenant – peer destination is where a call exits office 365 it needs to know where to send the traffic to the edge single site. Multisite you can set failback as multiple sites.

Firewall Requirements – Internal



When deploy CCE appliance these are deployed in a DMZ as they need to allow connections from Internet and also be able to communicate with internal network.

Usually there will be an internal firewall protecting internal networks this table is for the internal firewall. so mediation server to PSTN Gateway.

Talk across internal firewall to internal network.

Default port range marked by * above this the default port range on mediation 4 ports required per call. These can be adjusted.

Gateway port is an example could be 5060 or 5061 this needs updating as required.

You can limit port ranges as well.

Firewall Requirements – External (Minimum)


There are the minimum ports required for external side of CCE this is between the internet and the external firewall. If you follow the minimum there may be some hair pinning issues.

Firewall Requirements – External (Recommended)


Here you can see the Cloud Connector Edge external interface is different, this allows for optimal media flow.


Following the planning is time to prepare the first host appliance and follow the steps above. Items in bold are required for first appliance only.

The share needs permissions for all CCEs in the same site.

Windows server 2012 iso is required to generate the base vhdx. this can be copied and pasted and used for other appliances.

Public certificate required upfront.

All appliances will be registered prior to deploying them, this registers with Office 365 so Office 365 is aware of all appliances in the site.

Last of all configure the PSTN gateways.

Deeper dive in to deployment


Who do we register ?

Management and HA.


i can view the PSTN sites and then view access edge for each site and if auto update is enabled.


All appliances need to know about each other for HA, by registering the appliance we know all the mediation servers on all appliance in a PSTN site.


Two different appliances with two different mediation server.

You can export this information as well and view


High Availability


You can have up to 4 Cloud Connector per one PSTN calling site.

Calls are distributed in random order between the cloud connectors. In the image below CC 1 and CC 2 are two different appliances.

Capacity planning is key, Large 500 per CCE 4 * 500 = 2000 with N+1 = 3 * 500 = 1500 allowing for one CCE to fail

Johns signs into Office 365, johns calls a pstn number, this call will be routed to the PSTN via CCE, johns account is assigned to a PSTN site so when call does out the online infrastructure will route out to one of the CCE edges then from edge to mediation to PSTN GW.

Media is sent edge to mediation and mediation to PSTN GW.


Second user signs into Office 365 and this time the call is routed to CCE 2 on the same site and signalling and media flow is the same.


Manage HA Mediation Pool


First you register then install and all is working, all mediation knows about each other.

But now i want to add more and add a third

so i register, the third appliance knows about all of them but the first two don’t. On the first and second appliance we need to update their configuration  by running publish-ccappliance cmdlet and this instructs existing appliances to update their topology and it will show a third was added.

What happened if i need to remove one we now unregister from Office 365 and again we need to publish and ensure the remaining appliances know one has been removed.

Media flow – outbound PSTN call from internal user


Dave is on internal network, he signs into Office 365, now he makes external pstn call, when the call reaches Office 365 first it does reverse number lookup to check if its a number for a sfb user, its not so the call is routed to Cloud Connector so its routed to Dave sites Edge, then mediation then gateway.

Media – Dave is inside the network so the media can be sent to the mediation server direct. Dave cant send his media direct to PSTN gateway as media bypass is not supported.

Media flow – Inbound PSTN call to internal user

Inbound call comes into the PSTN GW and into the mediation server then to the edge server then to SfB Online and then SfB online looksup the number and finds this is Dave and send an invite and can answer the call.

The media will go PSTN gateway to CCE Mediation then to Dave as he’s internal.


Gateway Affinity


On premises you have M:N one mediation pool can talk to multiple gateway and multiple gateways can talk to multiple mediation servers.

Same with Cloud Connector, All PSTN GWs can talk to all Mediations, PSTN GW chosen is round robin, If GW1 cant accept call it can be rerouted. With HA CC you need multiple GWs.

For planning you also need to consider PSTN GW and PSTN capacity.

Multi site scenario


Multiple Cloud Connectors with multiple sites.

Above Seattle (PSTN Site 1) within this site it has two Cloud Connector appliance deployed this provides HA

Secondary site Amsterdam (PSTN Site 2) also with multiple Cloud Connectors deployed.

Here we can assign users to specific sites. John is assigned to PSTN site 1 and Komanal is assigned to PSTN site 2.

Johns calls will go via PSTN site 1 and Kormmels via PSTN site 2

There is NO DR between sites. In the event Amsterdam (PSTN Site2) goes offline there’s no automatic failover so calls go out the US (PSTN Site1). This is manual DR but considerations for inbound calls are required.

You can change the users site associated to PSTN site 1 but this would work only for outbound as inbound relies on Sites 2 PSTN connections. Also remember calls will be routed out of another country which could have legal implications and network latency may not be optimal.

Post Deployment


Once all appliances are deployed and ready to go, you configure your tenant and enabled sharesipaddress space and set peer destionation and useonpremdialplan to false.

Best practice to assign users to PSTN sites but –peer destination is a failback.

New in 1.4.1 is auto updates, this automatically update the hosted and machines and Cloud Connector edition, auto updates takes care of this.

You need to configure a time windows for these updates to occur in. As improvements are made to the SfB Online service auto update will keep CCE inline as well.

It builds a new set of VMs in the background side by side and then drain active traffic and switch to new VMs. Existing VMs remain in place incase we need to switch back to them.

Thinks of the VMs as sealed VMs so don’t add antivirus or customise them as they will be replaced. Host can have AV but vm are sealed.

Post Deployment – Auto Update Configuration


Check its enabled and then check when its enabled for.

You can create custom autoupdate time windows and defines days and week and time.

you can have up to 20 custom time windows

You need to assign the custom update time window to the PSTN site.

Post Deployment – Configure Users


Now for user you need to assign cloud PBX licence and enable users.

Dial in conferencing is from the service you cant bring a conferencing number with Cloud Connector. It comes from PSTN Conferencing from SfB online only.

Voicemail is provided by Azure Voicemail, Exchange UM does not provided voicemail services, but the client wants part of Exchange UM enabled.

Assign user to PSTN Site (Case sensitive) this is where you associate user to cloud connector site.

You can restrict international calls as well.



Cloud Connector has a management service for auto recovery, auto update and event viewer has CceManagementService

The management service can show errors on remote PowerShell sessions


Above you can see Registration status is showing error and then an error message is displayed RTCSRV not found or not running

The management service can try and recover these and below its fixed it.

Updating to version 1.4.1


Recommended to upgrade to version 1.4.1 if your running an older version, 1.4.1 would be the last manual upgrade method.

You need to uninstall older version from host and install the new version.

You need to get new .ini file version and make sure its updated with your information on each cloud connector. The upgrade process is straight forward. start download, register and install with upgrade switch.

With existing HA do one at a time.

You can update credentials as well.