Skype Academy: What’s New in Cloud Connector Edition V2 Summary

With the recent release of Cloud Connector v2 there’s some great new features and updates to CCE so wanted to summarise the Skype academy video.  There’s tons of useful information in here so hope you find it useful.

CCE v2.0.0 was released and straight after Microsoft provided some great content and learning on what’s new. Thanks Microsoft for very speedy information to the community. Check out the resources at bottom of post as well.

Useful links on great info on CCE v2

CCE manual download here

Skype Academy video link here


Lets start the video, the session is presented by Carolyn Blanding from Microsoft



Usual training disclaimer on Office 365 being subject to change and this ther July 2017 edition.


Also a member of extended hybrid voice team and working with developers on CCE since the first release.

Key Learning’s


CCE v2 bring media bypass ! wohooo

(Great link on Media bypass planning for CCE here

support for 16 CCEs in one pstn site up from 4 ! it now has 4x capacity !

Additional improvement

Session Scope


This session assumes you already know about CCE and have an understanding on deployment and management if not there’s a link on further learning here http://aka/ms/sa-cce

What’s new in CCE V2 ?



Wow what a list !!!

  • Media bypass
  • support for 16 CCEs per one pstn site
  • ability to manipulate sip headers for billing and interop
  • Hybrid voice flag in mediation server agent for CQD
  • Disable SSL 3.0 by default
  • automatic installation of .NET 4.5.2 which is dependency on current SfB
  • New Cmdlets

More details on each further on. Lets breakdown.

Media Bypass


This was top ask from customer

by removing mediation server in path for media we can improve voice quality and reliability by reducing latency, packet loss and points of failure

also reduce number of CCE to support greater number of voice streams

Media bypass requirements


CCE V2 deployed at all sites

tenant admin is required to enable media bypass feature in office 365 tenant this is not enabled by default

media bypass enablement needs to be replicated from office 365 to all CCEs

DNS must be configured to allow client resolution for the media bypass service url

Currently only supported version for CCE media bypass is office 365 pro plus click to run 32 and 64bit version 16.0.7870.2020 or later.

Microsoft Office MSI is not supported ! this again show new features are coming cloud first and the push to move your office installs to office 365 pro plus.

More info on Media bypass with CCE

Plan –

Deploy –

16 Cloud Connectors appliance per site



previously there was support for 4 CCES per PSTN site in a N+1 config where one CCE was was reversed for HA. Each CCE could support 500 simultaneous calls so totalling 1500 simultaneous calls per pstn site.

Now with 16 CCEs per pstn site in N+1 it provides 7,500 simultaneous calls and that’s without media bypass !!

This means can support more sim calls in single pstn site, for example before V2 if a company needs to support 5000 calls in one DC where CCE is deployed previously they would need to setup 4 pstn sites and split users across pstn sites even though all CCEs were physically located on the data centre, by supporting 7500 its reduced the requirement for more pstn sites and users dont have to be split up. Makes its easier to manage.

Modify SIP headers in CCE V2


Prior to v2 the only way to modify sip[ headers was administrators connecting to mediation servers and modifying sip trunk setting but during upgrades the settings while lost. CCE updates then had to set to manual, CCE then updated and then setting configured back again.

This is now persistent and the following settings if changed are kept during CCE upgrades.

Enablefastfailover timer – default is true, when true the 183 progress must return in 10 seconds. Certain network conditions has caused this to not response in 10 second so this can be set to false.

Forward call history – default is fales, history info useful in sim ring and call forward and refereed by useful for call transfer, this is useful for billing purposes and caller id purposes when sbc to replace caller id.

Forward PAI – default false, when true the P asserted identity headers with sip and tel uri from cce mediation to sip trunks. used when call history not available. please see url below for more info.

Hybrid Voice flag in mediation server agent


Set to unique flag so CCE calls can be easily identified from calls placed by other trunks. The user agent was previously reported as “Mediation Server” which is indistinguishable from other SfB Trunks.

Now it shows unique CCE-MediationServer example above show version number as well.


Examples in online reporting.

This is Call analytics preview in sfb admin centre, in this example a user search is done and a call is selected.

Alex is an online user and Alex uses CCE for PSTN calls, under systems you can see the mediation server that part of CCE, and under user agent we see CCE mediation server agent.

Lets look at session details

searched for Alex again and we can see CCE mediation server agent.


if you look before CCE v2 you will see the old Mediation Server


Disable SSL 3.0 by default


CCE does not use SSL and does not require SSL enabled. Please url for security advisory and recommendation on disabling when not needed.

.Net Framework 4.5.2


.NET Framework 4.5.2 will auto install and is a dependency for CCE v2

CCE host must always have internet connectivity and it required this to download 4.5.2 to host machine so its available.

Admins of large deployments can prepare the vhds with .Net 4.5.2 to speed up deployment times. to do this admins can use convert-ccisotovhdx cmdlet and use pause before update switch this allows admin to connect to base vm and install windows updates and .NET 4.5.2 on the base vhd.

New Cmdlets – Online


The new cmdlet are added to SfB Online one for media bypass and two on network. Please refer.

New Cmdlet – CCE Host


On the CCE Host there is also a new Cmdlet

Used to update configuration, if you update CCE config file. cloudconnector.ini after changes you must use import-ccconfiguration. It does auto run but still best practice after any manual change to use the cmdlet.

Example if you you change config file to use WSUS server.



  • Skype for Business administrator role instead of global administrator
  • Reduce number of passwords needed when deploying CCE
  • user corporate network switch instead of management switch for most tasks
  • improvement to auto detection
  • change cmdlets

Let breakdown each one

Skype for Business Administrator Role


CCE requires an O365 tenant admin account to manage CCE services online, prior to V2 this required an account that was a global administrator.

With V2 its supported to use a tenant admin account with Skype for Business administrator role is sufficient for managing CCE services online.

If password expiry is set you need to use set-cccredential to update credentials.


To reduce password for CCE in V2 and reduce complexity.

In V2 the following password will be requested

  • CCEService – used for CCE service account and domain admin, VMAdmin
  • CABackupFile – used to import Root CA when deploying appliances
  • ExternalCert – used to import Edge certificate when deploying appliances
  • TenantAdmin – used to deploy and maange CCE Online

Note CCEService and CABackupfile must be the same for all CCE per site.

Corporate Management Switch


previously we used the cce management switch for all connectivity between host and vms for PowerShell. feedback to customer was that this was great as it caused network disrupts.

CCE v2 now reduces the amount or connections and disconnections, now only used for new deployment or upgrade.

The SfB CCE Corpnet switch will not be used which reduces the number of connections and disconnections. search of clslogging will now be alot faster as network connections are already established.

Since corpnet switch is used now the network adapter bound the cce corpnet network switch must have an ip address assigned in the same subnet as the CCE corporate network. This can be an alternative ip address. before the management switch was matched on the same subnet.


Improvements to Auto Detection


  • There has been some updates to auto detection for CCE recovery to avoid call failures.
  • In HA we want to mark any appliance that is down to avoid issues and call failures
  • Maintenance you have to out CCE in maintenance mode so its doesn’t.
  • All server roles are monitored

Cmdlet Updates – Online


cannot be set from false to true.

with CCE a online dial plan is a hard requirement

Updates to Get-CsHybridPSTNAppliance

Cmdlet Updates – CCE Host


PowerShell verb update from renew-cc to update-cc

You can change domain admin or vmadmin using set-cccredentials as above.

Upgrading to V2



For customer with CCE already deployed to new build

Supported path from version 1.4.2 to version 2 if auto update available then it will autoupdate at scheduled update window.

Manual update process is available if autoupdate disabled.

InPlace upgrades are NOT Supported with version BELOW 1.4.2

In this case you need to unregister appliance, uninstall appliance and deploy new CCE.

To confirm CCE several ways, hyper v console, remote PowerShell and SfB admin centre. more details above.

Update Cloud Configuration File


when upgrading to V2 you need to update cloud connector configuration file with the new sip header setting to cloudconnector.msi.


Open file


Copy three lines from sample file


paste into your file, save and import.



If advanced notice is possible or more likely to have auto upgrade off due to trunk config you can modify trunk config file prior to v2 upgrade.


1.4.2 did not prompt for CABackup pasword the domain admin password was used and its used to encrypt root CApassword. It must be the same for all appliances,

If different domain admin password may be in place if password changed after deployment. You can use the get-cccredential. if you have this the steps are listed above.


from 1.4.2 we don’t prompt for CCEService password the VMAdmin password aka local admin password will be used for cce service password. This password needs to to be same so best to confirm password are the same across all appliances.



Key Learning’s






Lync Server 2013 July 2017 CU – Move Meeting Rooms, Delegate updates and adds CsHybridApplicationEndpoint cmdlets!

There’s been a new Lync Server 2013 July 2017 CU update 5.0.8308.992 released 10/07/2017 and its KB 2809243. Perhaps this is CU9.

The CU adds the following

There’s update to delegates and moving meeting rooms from on-premises to SfB online but the most interesting i found was the new four cmdlets adding CsHybridApplicationEndpoint for cloud voice and bots in Lync Server 2013 ! more details below ! One came in CU5 but perhaps theres more now. Noted here in CU5


More Details on Install

Update Version Number


Fixes / Improvements

KB4034279 Enables the "Move-CsMeetingRoom" cmdlet to move a meeting room from on-premises to Online in Lync Server 2013

The update supports administrators to move a meeting room object from a Microsoft Lync Server 2013 on-premises environment to Microsoft Lync Online in Microsoft Office 365 by running the Move-CsMeetingRoom cmdlet.

KB4023332 Delegate can pick up Peer to Peer call on behalf of delegator now in a Lync server 2013 environment

This cumulative update enables Microsoft Lync 2013 users to manage delegates and set up simultaneous ring feature. Administrators (delegates) can pick up peer to peer (P2P) calls on behalf of Bosses (delegators).

KB4023330 Enables you to manage delegates and set up simultaneous ring feature in a Lync Server 2013 environment

This cumulative update enables Microsoft Lync Server 2013 users to manage delegates and set up simultaneous ring feature.

KB4023327 Adds "CsHybridApplicationEndpoint" cmdlets to manage cloud voice or bot applications in Lync Server 2013

This article introduces the following four cmdlets to manage voice or bot applications in a Microsoft Lync Server 2013 on-premises environment:

  • New-CsOnPremApplicationEndpoint
  • Get-CsOnPremApplicationEndpoint
  • Set-CsOnPremApplicationEndpoint
  • Remove-CsOnPremApplicationEndpoint

Lync 2013 Server update screenshot.

Screenshots to follow.

Copy of Lync Connectivity Analyzer Download link

A fairly recent announcement was that the Lync Connectivity Analyzer tool has been retired noted below and in a blog post from Microsoft here

As some of you may have noticed, the Lync Connectivity Analyzer tool has been retired and is no longer available for public download.  We are interested in hearing how you used the tool, and what we could provide in the form of a tool that would better assist you in troubleshooting connectivity or sign-in issues.

I was deleting my downloads and found a copy of it so thought id share it on OneDrive just in case people want a copy, found it useful or looking for it again.

Microsoft did mention in the comments they may bring it back on the understanding its not managed going forward.

I did find it useful when troubleshooting mobile client sign or just running some checks but i didn’t use it heavily tbh.

64bit Download link is below!AvBNRjYUuhsvjbtI7W-J2JRe7MtaPw


Ive added the documentation from TechNet below just in case it disappears as well

NextHop Blog Post on it as well here


Using Lync Connectivity Analyzer in Lync Server 2013

Lync Server 2013

Topic Last Modified: 2014-02-11

Microsoft Lync Connectivity Analyzer helps Lync administrators determine whether the deployment and configuration of their Office 365 or on-premises Lync Server environment meets the requirements to support connections from Lync Windows Store app and Lync apps on mobile devices.

Lync Connectivity Analyzer attempts to connect to Lync Server on-premises or Lync Online by using the same services and protocols that are used by Lync Windows Store app and Lync mobile apps. You can perform the connection tests over your internal network or over an external network that connects to Lync Server or Lync Online. Lync Connectivity Analyzer provides a report with detailed information about each connection step to help you validate your configuration and troubleshoot connection problems.

Lync Connectivity Analyzer tests the following Lync Server components:

  • Autodiscover service

  • Authentication Broker (Reach) service

  • Mobility (MCX) service

  • Mobility (UCWA) service

  • WebTicket service

Lync Connectivity Analyzer tests the configuration of the following other components:

  • Publication of DNS records for Autodiscover URLs

  • Certificates

  • Proxy servers

You can download Lync Connectivity Analyzer from the Microsoft Download Center at

Checkout my download link above.


To Analyze Your Connectivity

  1. Enter the credentials for a valid Lync account (either an on-premises Lync account or an Office 365 Lync account) that will be used by the tool to test the connection:

    • In Lync Account Type, select Office 365 or On-Premises.

    • In SIP URI, enter the SIP sign-in address for the Lync connection in the format

    • In Password, enter the password associated with this account.

    • In User name (optional), enter a user name if applicable. The user name is also known as the User Principal Name (UPN). If the user name and the SIP URI are the same, you do not need to enter a user name. If they are not the same, enter the user name in the format or domain\user, as appropriate.

    • Network access, choose From inside my organization if you are running Lync Connectivity Analyzer from a computer connected to your internal network. Otherwise, choose External (Internet). Lync Connectivity Analyzer always performs both internal and external tests, but specifying whether you are inside or outside of your own network helps the tool interpret whether certain failures are expected.

    • In Client, select whether to perform connectivity tests for the Lync Windows Store App, Lync Mobile 2010 App, or Lync Mobile 2013 App.

    • Under Server Discovery, select the type of test to perform:

      • If you want the tool to discover the Lync server automatically, select Automatic.

      • If you want the tool to bypass the autodiscover test, or if you know the name of the server you would like to connect to, select Manual using address: and specify the fully qualified domain name (FQDN) of the Lync server—for example,

  2. (Optional) Under Log File, select the checkbox if you would like to create a log file at the specified path. If logging is enabled, click Clear to clear the log file, click Open to open and view the log file, click Email to open an email message to send the results to your support team (you must manually attach the log file from the path specified).

  3. Click Start.

The following figure shows sample results from Lync Connectivity Analyzer.

Lync Connectivity Analyzer

Screenshot of the Lync Connectivity Analyzer

Components Tested by Lync Connectivity Analyzer

Lync Connectivity Analyzer attempts to discover the Lync server and establish a connection by using the same steps used by Lync Windows Store app and Lync mobile apps. It performs the tests as described in this section.

If Automatic discovery is selected, Lync Connectivity Analyzer does the following:

  • Queries Domain Name Service (DNS) for autodiscover URLs.

  • Attempts discovery by using the secured internal channel. For example, HTTPS://

  • Attempts discovery by using the unsecured internal channel. For example, HTTP://

  • Attempts discovery by using the secured external channel. For example, HTTPS://

  • Attempts discovery by using the unsecured external channel. For example, HTTP://

If Use the following server discovery address is selected, Lync Connectivity Analyzer does the following:

  • Queries DNS for the server’s FQDN.

  • Attempts discovery by using the secured channel. For example, HTTPS://serverFQDN/.

  • Attempts discovery by using the unsecured channel. For example, HTTP://serverFQDN/.

If Lync Windows Store app is selected under Test the requirements for, Lync Connectivity Analyzer does the following:

  • Verifies that the WebTicket service is available and tests authentication of the Lync account credentials.

  • Verifies that the Authentication Broker (Reach) service is available.

If Lync Mobile 2010 App is selected under Client, Lync Connectivity Analyzer does the following:

  • Verifies that the WebTicket service is available and tests authentication of the Lync account credentials.

  • Verifies that the Mobility (MCX) service is available.

If Lync Mobile 2013 App is selected under Client, Lync Connectivity Analyzer does the following:

  • Verifies that the WebTicket service is available and tests authentication of the Lync account credentials.

  • Verifies that the Mobility (UCWA) service is available.

While performing these tests, Lync Connectivity Analyzer validates the certificates installed on Lync Server, hardware load balancers, proxy servers, and the computer on which you are running the tests.



Skype for Business Mac Client June update summary – new features, improvements and Known issues

There has been a new June 2017 update released for the Skype for Business Mac Clients. This could be cumulative update 5 i cant see it mentioning cu version anywhere at the mo so its June update for the SfB Mac Client with a lot of new features added and improvements, any SfB mac user I’m sure will want to get this update.

There is a ton of new features including some of the highlights and there’s even Microsoft Teams meeting join from meetings tab which is nice! Some highlights below:

  • PowerPoint presentation while in a meeting
  • Join a meeting by phone
  • Users can now join non-federated meetings directly from Skype for Business
  • Users can now join a Microsoft Teams meeting directly from the Meetings tab in Skype for Business
  • Added Touch bar support

A full feature list with June update is further on in the post.

This again shows Microsoft hard work with improving the mac client.


There seems to be two new known issues to consider as well


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

Download link

Version –

Released – 20/06/2017

New features added and there’s a ton of them!
  • Users can now share a PowerPoint presentation while in a meeting.

  • Join a meeting by phone — Users that are enabled for Enterprise Voice can now join a meeting with the audio on their phone.

  • Call-back on phone in a meeting — Users that are enabled for Enterprise Voice can now get a call-back on their phone while in an on-going meeting. Click the More Options button () to find out more.

  • Users can now search for contacts whom they previously haven’t talked to directly from the Chats tab.

  • Users can now join a Microsoft Teams meeting directly from the Meetings tab in Skype for Business.

  • Users can now join non-federated meetings directly from Skype for Business, rather than having to join in their browser.

  • Users can see meeting information (organizer, join URL, conference ID) while in a meeting.

    NOTE: For Meet Now, the phone number and conference ID are not available; only the join URL is available.

  • New Contacts tab shows who has added you to their contacts list in Skype for Business.

  • Users can close the "On Hold" overlay while in a meeting. Held calls can be resumed from the new More Options button ().

  • Added Touch bar support for various functionality.


  • Losing connection during meetings only will now automatically reconnect if dropped due to network problems once sufficient network quality has been re-established.

  • Fixed a memory issue with the 4th Generation Macbook Pro where the app would leak excessive amounts of memory after a video call, or VBSS screen sharing.

  • Fixed an issue where the notification centre would be filled out with alerts about network problems.

  • Fixed an issue where 00 was always normalized to + regardless of the user’s region.

  • Fixed an issue where dialling vanity numbers wouldn’t correctly translate to digits, and the call would fail.

  • Fixed an issue with double dial-tone sounds while dialling a PSTN number.

  • Fixed an issue that prompted users to update meeting due to policy changes when scheduling public meetings.

  • Fixed mute and unmute issues.

  • Fixed various screen sharing issues.

  • Fixed other UI and crash issues.

  • Fixed issues with sign-in.


System requirements for Mac

  • Skype for Business Server 2015 or Lync Server 2013
  • OSX 10.11 (El Capitan) or OSX 10.12 (Sierra)
  • Outlook Mac build 15.27 (161010) required for Outlook integration

SfB / Lync Server / Online Requirements

For best experience SfB Online is recommended for full feature set but for on premises deployments its the following

Don’t forget about known issues as well

Latest issues added

  • Contact Management, including Delegate Management, is not supported if Unified Contact Store is enabled
    Users cannot modify their contacts list in Skype for Business if a user account is enabled by the Skype for Business administrator for the Unified Contact Store for Exchange. Users can make changes to their contacts list in Outlook.

  • Skype for Business on Mac fails to sign in


    1. Remove “Mozilla/5.0” from the WIASupportedUserAgents parameter in AdfsProperties. Essentially, you will need to:

      1. Run Get-AdfsProperties | select wiasupporteduseragents and get the output.

      2. Then remove _only_ “Mozilla/5.0” from the output.

      3. Then run Set-AdfsProperties -WIASupportedUserAgents with the output from step b.

    2. Revert back to using Lync for Mac 2011.

More details on all known issues below


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 –

Lync Server 2013 list –



Skype for Business Online Cloud PBX with PSTN Calling – Phone Number Requests Forms

Noticed this on twitter over the weekend from @RandyChapman, so wanted to have a bit of look at this. Thanks Randy.

Seems this is a manual process for requesting new subscriber telephone numbers for users using SfBO Cloud PBX with PSTN Calling. This is where Microsoft is your Telco provider and all PSTN services are delivered by Microsoft in Skype for Business Online.

Its noted there are some countries/regions that you can’t get phone numbers using the Skype for Business Online admin centre. Instead you will need to download the correct country/region form and submit it to Microsoft. Once Microsoft receive the request , their service desk will help customers with getting new phone numbers.

It doesn’t say which countries specifically you have to use the forms for as all PSTN Calling countries have a form available it seems, but it does note – Belgium, Germany, Ireland and the Netherlands are only available to preview customers (early adopters).

Perhaps after countries are out of preview the online new telephone provisioning process may be added to admin centre.

This is noted for requesting only new “subscriber” phone numbers and NOT service numbers. Subscriber numbers are numbers that are assigned to your users.

To request new telephone number manually and not via the Skype for Business Online admin centre there are some forms available for download.

You can use these forms to request new subscriber (user) phone numbers that aren’t listed in the Skype for Business admin center.

List of Forms for download

  • New Phone Number Request for Belgium (Geographic numbers) (v.1) (en.US).pdf
  • New Phone Number Request for France (Geographic numbers) (v.1) (en.US).pdf
  • New Phone Number Request for Germany (Geographic numbers) (v.1) (en.US).pdf
  • New Phone Number Request for Ireland (Geographic numbers) (v.1) (en.US).pdf
  • New Phone Number Request for Spain (Geographic numbers) (v.1) (en.US).pdf
  • New Phone Number Request for the Netherlands (Geographic numbers) (v.1) (nl.NL).pdf
  • New Phone Number Request for the U.K. (Subscriber geographic numbers) (v.1) (en.US).pdf
  • New Phone Number Request for the U.S. (Subscriber numbers) (v.1) (en.US).pdf

Download link HERE

Quick look at a form



The form for each country looks the same but the example text in the table is different.

Also all form except the Netherlands are in English.

Notes the following as important on each form

1. Please submit requests for different type of numbers in different form submissions. You
can only request one number type per request/form. More Info.
2. You can list only one “emergency calling address” per request/form.
3. Please submit requests for different cities in different form submissions. You can only
request one city per request/form.

It also doesn’t list where to send the forms so perhaps these will be updated soon.


SfB Broadcast: Ep. 43 Skype for Business Cloud Connector Edition for Hybrid PSTN Summary

This is a SfB Broadcast from Microsoft link to the video is here

The three points i found most interesting

  • Media Bypass – Summer 2017
  • Coexistence – Fall 2017
  • Improved diagnostics – Winter 2017

Lets go.

Bill Verthein, Principal Product Manager

Oliver Chiu – Sr Product Marketing Manager

What Hybrid ??


  • Average PSTN contracts are 5 years durations
  • There are countries where Microsoft don’t have PSTN calling
  • Some people don’t trust Microsoft as a Telco
  • Microsoft may not offer PSTN in some countries full stop
  • Some countries you cant get a PSTN licence

Hybrid allows Microsoft to

Deploy Cloud PBX worldwide

Work with PSTN carriers not against them in some countries

Cloud Connector Edition


CCE set of four customised VMs running SfB components

Two options to deliver Hybrid

  1. Via Cloud Connector Edition
  2. Via an on premises Skype for Business Server deployment

CCE run 4 packaged VMs to provide hybrid connectivity  between PSTN on premises and Cloud PBX where users are homed.

CCE only talks SIP so if you have E1 / T1 / BRI then you need a PSTN gateway / SBC

Cloud Connector available in two ways

1. Download CCE and deploy on your own hardware

2. CCE pre deployed on appliances. Two approved vendors AudioCodes and Sonus. Also includes an SBC as well.

Appliances are tested with Microsoft.



CCE is a direct extension of the SfBO service its not a standalone piece of hardware.

CCE uses AutoUpdate to update itself as SfBO requires so auto updates on the CCE is the carried out when Microsoft require. You have 60 days only to run an older version of CCE.

IT admin can set update windows, set by days /hours. When new update is found and windows is open it will download updates for CCE components. The Update will build the newer version of virtual machines side by side whilst calls are in progress. At a maintenance windows the newer version will swap over. This happens automatically ! Tested N –2

AutoUpdate can be disabled but this MUST be manually updated. You will not be in supported if you dont keep up to date.

Allows Microsoft to push updates to CCE first if required and then update the “Cloud”


CCE requires hardware, is there a hosted offering ?

There is a version of hosting in private cloud

It isnt designed to be multi tenanted or hooked into monitoring systems. If hosted modified VMs then with the next update it will wipe them.

Private cloud would be ok but be careful.


Windows Server 2016 ?

You need Windows Server Datacentre edition to licence the virtual machines. NO restrictions on number of VMs. No User cals required.

CCE is stateless it has no concept of users. All users context is in the cloud. They dont log into the cloud then log into the cloud.


Hybrid Voice options and flows


  • CC Domain Controller – Nothing to do with enterprise AD, its only for CCE.
  • Edge
  • Mediation
  • CMS

IM,Presence, Conferencing, app sharing and peer to peer all go to the cloud (Skype for Business Online)

PSTN calls to and from external numbers will go via Cloud Connector

Media bypass not supported currently be noted above (bypass enabled)

Media bypass is being added to Cloud Connector. With media bypass the medition server tells dave that the client can talk direct to the PSTN gateway. this means all media can stay withing internal ntwork and also should allows CCE to make more calls.

Currently in TAP and being tested, expected end of June 30th. 20 people running it, no bugs found at the moment.

If you have an on premises SfB server deployment you can use this deployment for Hybrid connectivity with Cloud PBX.


OPCH – on premises connected hybrid (Diagram above)


To migrate Hybrid SfB Server to CCE ?

CCE cant coexistenece currently with on premises SfB server deployment

Co existence is coming, Microsoft have a build already.

Its engineering testing and in a week or two come to end to end testing.

Coexistence will come Fall

Should be very popular, its a common question i get asked.

Requirements for coexistience

SfB Server 2015 with CU6 on Federation Edge

CU6 will contain CCE existence

Lync Server 2013 you will need SfB 2015 CU6 Federation Edge. SfB 2015 Edge is approved topology.

No coexistence with Lync Server 2010 or earlier!




Notes coexistence August 2017!

Whats Next ?


  • Media Bypass – Summer 2017
  • Coexistence – Fall 2017
  • Improved diagnostics – Winter 2017

Mid Term – two years

  • reviewing requirements to reduce hardware / software costs




Can one CCE support multiple SIP trunks ?


Will AutoUpdate update my host ?

Yes if it has two, it updates, host, guest OS and may require restart of the host.


Next Webcast will be on Polycom.


*** UPDATE *** Questions posted following the event UPDATE 19/06/2017

Below questions are taken from

What is the YouTube channel we can watch this back on please?

When do you expect that we can use local PSTN connectivity and numbers with service numbers?
We expect this before the end of this calendar year.*

Is there any plan to add automatic disaster recovery?
We plan to support full DR in the first half of 2018.*

Any improvements planned to make config file easy to edit? right now the TEXT file is error prone. Any error leads to script issues and needs CCE deployment to rerun.
Our CCE Appliance partners AudioCodes and Sonus have done a good job of making configuration a set of logical questions and preventing the chance of most conflicting answers. 

HA/DR capabilities for CCE? can it hit SLA targets?
Yes, CCE has HA/DR capabilities. We do not yet claim full DR capability (see the answer above) for CCE. However, we believe CCE in tandem with Skype for Business Online and Cloud PBX can satisfy our SLA obligations to our customers.  We measure and track this every day and have weekly reviews of our metrics in addition to assign product engineers to 24×7 on call support for customer issues.  
Hybrid PSTN is inherently harder to track down issues and understand root causes of issues because quality often depends on the quality of the customer’s network as well as change control on their firewalls and network settings. To help improve resolving issues wherever the fault lies, we are currently and will continue to add improved diagnostics to help resolve problems to eliminate failures outside SFBO or CCE.

Will new tenant dial be supported on CCE?
Yes tenant dial plan is fully supported with Hybrid Voice options.

Is there any plan to add CAC capabilities for SfBO?
We do not have plans for CAC over the next 12 months. If this is a priority for you, please let us know.

Is tail end hop-off supported?
We currently do not support tail end hop off (we call that “destination based routing. This is planned in 2018.* Microsoft is uniquely positioned to drive this globally as we have the 2nd largest global cloud in the world and we have more global fiber than any single carrier. Today our Skype Consumer product is the #1 international long distance provider in the world.

Can you route calls via different CCE appliances based on user DDI? E.g. London based DDI will break out via London CCE and Edinburgh DDI will break out via Edinburgh CCE?
We are planning improved routing rules coming to CCE toward the end of 2017.*  In the interim many customers do this call destination routing today with an intervening SBC.

Does CCE have the capability to support HA in two different DC?
Some customers have split an HA pool of CCEs across different data centers.  We recommend that each CCE be cross connected to every telco gateway in their site so the result of splitting a site across two DCs is you may have a lot of WAN traffic between data centers and that can impact cost.  When we improve our DR performance later this year you should see less need to split across DCs.

Do the local PSTN gateways have to be AudioCodes/Sonus or can they be existing Cisco gateways?
We support ANY SBC that interops with SFB mediation servers.  This includes Cisco and Avaya SBCs (as well as Acme).  There are a lot of smaller SBC companies that we don’t test with that MAY also work as well. Usually all SBCs have well understood config profiles to interop with SFB20015 Mediation Servers (this is what CCE uses).

For the coexistence topology referenced will only SFB 2015 Federation Edge be required? Is there a requirement to deploy next hop SFB 2015 or next hop can still be Lync Server 2013?
The Federation Edge needs to be SFB2015 CU6 Edge and the next hop needs to be SFB2015 CU6 as well.

When CCE will support Media Bypass?

We are targeting this for mid-year 2017.* TAP has already begun.

What the requirements from the legacy PBX side? What is tried, tested and supported?
CCE will interoperate with any device that works with SFB2015 Mediation Server’s SIP interface. There is a long list of partners that have submitted their equipment and officially certified interop.  Others have their own Skype for Business template for interop that they certify. Many other popular solutions have public discussions on how to configure those links (eg. Cisco’s SBC has well known profiles that interop with SFB2015 Mediation Server).

Can one CCE box support multiple SIP trunks?
Yes, CCE can be connected to several SIP trunks. When our Media Bypass release is available, it will support up to 16 SIP trunks per CCE.

Does Microsoft have plans to deliver the topology of co-existince between SFBS and CCE within a single tenant? For example, a HQ user with SFBS on-prem PSTN breakout and an oversea branch user with CCE for branch PSTN breakout?
Yes, we will have coexistence capabilities between CCE and onPrem SFB coming by end of calendar year, 2017.*

When an online user at the internet external network dials a PSTN call, what is the voice codec you use between the online user client and CCE’s edge? This is a media relay through mediation server…is it SILK codec (in this case, mediation do transcoding) or PSTN G711 codec ?

To edge, we use G.711. In some cases we might initiate different codec. We will update our TechNet documentation shortly with describing the codec negotiation.

If we are using RCC today with a hybrid SFBOenviroment. can we use CCE to replace RCC?
CCE does not support RCC, but it does support SIP interop with legacy PBXs like Cisco and Avaya.  RCC was deprecated for SFB2015 (Call via Work was the recommended alternative) and RCC is not supported in CCE.

What are the Reverse Proxy requirements for meetings

All user with CCE are homed online and receive meeting services from Skype for Business Online. Therefore, there is no need for a local reverse proxy server

Is there any planned capabilities to selectively route traffic to PSTN to A) CCE and B) MSFT PSTN Calling Plans, for a given user? i.e. route traffic to an existing PBX (for coexistence purposes), but route to ‘outside world’ via PSTN Calling Plan.
There will be cloud based routing and dial plans for SFB Online where you can distinguish where to send certain destination phone numbers.

Once media bypass delivers, can users use SILK voice call from SFBO user until PSTN GW?
We are working on documenting codec negotiation and plan to update TechNet with detailed logic soon.

Any ETA for supporting collocating SFB on-premises or Hybrid + CCE
This is solved through coexistence which is coming later in calendar year 2017.*

Can a PSTN -> SfB conversation be elevated to a conference call?
Yes, but the call will transparently escalate to a cloud AVMCU (there is no audio mixer in the CCE).

Does Microsoft have plans to deliver the topology of co-exist SFBS and CCE within single tenant? for example, HQ user use SFBS on-prem PSTN breakout and oversea branch user use CCE for branch PSTN breakout?
When we release Coexistence, you will be able to do this.

When can we expect CCE to work with on premise Lync or SFB server
CCE Coexistence is coming later this calendar year, 2017.*,

What is the expected RTO (Recovery time objective) for DR failover (Hybrid PSTN site policy change)?
Right now, customers must run recovery scripts to reassign users to a different surviving CCE site. Scripts moves approximately 3 users per second. This is expected to improve by early 2018.*

My customer has several Lync 2013 pools and needs to move to the cloud, but need to add CCE in phases. In the new office, can we have a mix of CCE and Lync in the same organization? The goal is to remove all the onpremises servers

Coexistence will allow you to use CCE in parallel to an existing onpremises deployment. Either Lync 2013 OR SFB2015 can coexist but in either case you will need to deploy a SFB2015 CU6 Edge as the Federation Edge (even for Lync 2013). Earlier versions of Lync (or OCS) such as Lync 2010 are not supported for coexistence with any modification. With earlier versions you will need to upgrade to Lync2013/SFB2015 and then configure the topology for coexistence.

Can we use PSTN Conferencing Number to land on on-premise PSTN and join the meeting hosted by users who are enabled on Office 365?
Our Cloud PBX team is currently testing this capability and we will have more to share later. 

How to migrate from Hybrid SFB on-premise to CCE?
Coexistence will be needed.

Will dynamic E911 capabilities be introduced to SFBO at some point in time? And if yes, will that feature support Hybrid PSTN scenarios either with CCE or Cloud PBX with on-premises PSTN connectivity?
Currently, we only have Basic 911. By 1st half of 2018* we will have enhanced call routing capabilities that will allow us to route on location of the user. The accuracy of E911 is highly dependent on what types of location data can feed our routing engine and ultimately the calls need to route to the appropriate carrier of record who has the legal obligation to provide 911 services. Even if we route to the right carrier for a user’s current location the customer still has to have a proper 911 address set up for a given local phone # that would be used to proxy the userâ’s phone number. We can’t send a Chicago phone# to a Dallas PSAP when that Chicago user is at Dallas office. Expect this in 1st half of 2018 as well.*

Can you confirm the license requirements for CCE – WInServ16 terms unlike 2012 indicate that everyone needs a Cal?
We have no current plans to move to WS2016 for the next few years. Our OS needs are generic and we mainly just require HyperV.  Our current WS2012r2 based CCE does NOT require per user licensing.

Will auto-update update my host? Is there any MP coming for CCE?
Not sure what MP is (Media Processor?), but yes AutoUpdate will update all the Operating Systems that need it, VM Guest OS as well as the Host OS.

CCE requires on-premises hardware. Is a hosted version of CCE planned and what’s the timeline?
Well we are currently working on a significantly smaller footprint for Hybrid PSTN. In the interim we understand that some people just can’t have on-premises hardware. For these cases, we can support private cloud deployments of stand-alone CCEs in a Hoster’s Data Center that will VPN back to the customer’s enterprise network.
First some background on why CCE is difficult to host. CCE has very intricate scripts that configure and update the SFB VMs. Most of our engineering effort for CCE has been in building the new script capabilities and evolving the older versions in the field. Because CCE needs to AutoUpdate, any 3rd party Hoster modified scripts for hosting will either fail when the next AutoUpdate does its magic OR you can miss a required update for cloud interop. So there is NO Microsoft supported multitenant version of CCE.
Next, while running CCE in Azure seems like a no brainer, Azure is not optimized for bidirectional media like voice, so there are quality risks. There are additional limitations in the current way network interfaces are handled in Azure. Until the network virtualization and the bidirectional media performance issues are addressed we cannot endorse an Azure version of CCE at present.
From PBX integrations perspective can calls be routed via CCE to users who use PSTN Calling plan and Service Numbers such as Dial-in conferencing. This is to avoid call charges during coexistence phases.
Today SFB Hybrid PSTN (both CCE and on-premises Config Hybrid, aka Split Domain Hybrid PSTN) can coexist with cloud homed users who have Microsoft’s PSTN plans. Hybrid PSTN and our PSTN calling can be arbitrarily assigned to all the online users in a tenant. All the users can call each other and can move between both methods of PSTN. All calls will be VoIP calls without going to PSTN network

*Disclaimer: Any date estimates may be changed substantially prior to final release of the solution.  This only represents the current view of Microsoft Corporation at the date of the blog. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after we publish this blog. Dates are for informational purposes only. Microsoft makes no warranties, expressed, implied, or statutory as to this information in this blog.