Cloud Connector Edition Coexistence with On-Premises Hybrid no longer on roadmap

 

Update 22.10.2017: We heard at Microsoft Ignite that making CCE work alongside SfB Server in the same customer/topology is no longer on the roadmap for CCE. Instead, if you have SfB Server and wanted CCE alongside it, Microsft is recommending instead a small deployment of SfB Server in the OPCH model or AudioCodes CloudBond which is essentially a single “CCE like” appliance but it runs full server so can run OPCH. Sonus’ CCE can also run Server on the appliance blade in “OPCH model” but they don’t have a SKU to buy it/have it officially supported by them in this model. Note all these models run full SfBS server in the “appliance”. You can find the Official announcement here: https://techcommunity.microsoft.com/t5/Skype-for-Business-Blog/New-CCE-version-due-later-in-November/ba-p/123336

Cloud Connector 2.0

Cloud Connector edition 2.0 was just released, and it has some exciting new abilities including Media Bypass and up to 16 CCE’s in a “CCE site”.

Media Bypass allows the audio network traffic stream (media) to not route through (bypass) the CCE Mediation server, meaning it can route direct between the SfBO client and the Session Border Controller or gateway, allowing fewer network hops and enabling new CCE topology Options. This should also allow more calls per CCE, but Microsoft has not offered any official guidance on the expected number as there are too many variables for them to model the expected number of calls that will bypass.

Having up to 16 CCE boxes in a “CCE site” (should have been called a CCE Pool IMHO), allows up to 7,500 calls per “CCE site”, and that’s the number without Media Bypass factored in.

One thing that is hotly requested and didn’t make the cut for 2.0 is Coexistence of CCE alongside an existing SfB server hybrid deployment

Terminology/Acronym Level Set:

Today you can only have SfBO hybrid with On-Premises Server *or* SfBO “hybrid” with Cloud Connector Edition. “Hybrid” is the most overused term these days and means everything and nothing, so a quick terminology level set:

SfBS – Skype for Business Server, as of today there is only one server version, server 2015, so the server version is implicit.

Lync2013S – Lync 2013 Server, Server version has to be explicit as there is still some 2010 server (Lync 2010S) about even though it’s out of mainstream support.

SfBO – Skype for Business Online, the SfB Service from Microsoft that is part of Office 365.

Hybrid – Can mean all sorts of Microsoft Cloud/Server topologies (Exchange Hybrid, Identity/Azure AD Hybrid) and within SfB can mean quite a few different topologies, as much as possible I try to avoid the use of generic “hybrid” and instead use one of the below terms.

SfB Split Domain Hybrid – Simply means that SfBS (or Lync Server) has been “connected” to SfBO/Office 365. Implicit in this is that “Identity and Authentication” is setup between the customers Active Directory and Office 365 (AzureAD/ADFS or some other configuration) and that users can be moved between SfBS and SfBO. This does not define the “type” or users (IM/P, EV, Cloud PBX) on either SfBS or SFBO.

CCE – Cloud Connector Edition, the “downloadable appliance” or “purchased appliance” that allows a customer to connect their PSTN (Public Switched Telephony Network) carrier to SfBO for user phone numbers. Allowing users to make and receive calls from a SfBO Cloud PBX account from a carrier the customer “brings” to the service. Today CCE does not work alongside other “Hybrid” topologies. Implicit is that a CCE user is SFBO and Cloud PBX

OPCH – On Premises Call Handing. This is a term used inside of Microsoft to describe a SfBO Cloud PBX user who has PSTN carrier connectivity for their user phone number “call handling” via “On-Premises” SfB Server. Implicit is that the OPCH user is SfBO and Cloud PBX and that SfB Split Domain Hybrid is setup. Today this cannot coexist with CCE.

EV – Enterprise Voice. Meaning the user is a SfBS (LyncServer) user with the ability to make and receive phone calls

Cloud Connector Edition 2.1 Coexistence with On-Premises Server Split Domain Hybrid?

Many customers have SfBS deployed, possibly already in Hybrid but also want to deploy CCE, today that is blocked; you must be either SFBO and CCE or SfBO and SfBS hybrid. Why would you want both? Some examples:

• Customer has an existing SfBS, Lync2013S or Lync2010S deployment (with or without EV) and wants to move to SfBO/Cloud PBX without making further investments in server infrastructure
• A global customer has SfBS in some regions/countries, but now another country wants to deploy Cloud PBX with CCE and is blocked
• A customer has a small feature requirement for SfBS that isn’t available on SfBO today (server-side call recording for example) but would like to deploy the lighter weight CCE everywhere else

Microsoft has heard these requirements and this ability is already in the works. In the latest Skype Broadcast (a great source for the latest SfB Information) YouTube Archive, which talks about the CCE 2.0 new features, Bill Verthein, Principal Program Manager and Product owner for Hybrid PSTN gave us some insight into when it is coming. As with all pre-release information like this, dates and details are subject to change.

Coexistence is now due in CCE “2.1” (Bill used “2.1” to represent the “next version”). It requires some updates in the SfBO service and SfBS (specifically the Federation edge) hence it’s taking a little longer.

• Coexistence will require the next version of CCE, “2.1” due “US Fall” which is October, November, December, or CY2017 Q4
• It will be supported for SfBS Hybrid
• It will be supported for Lync2013S Hybrid, but like OPCH you will require at least one SfBS pool and Federation Edge. So if you’re a Lync 2013 Install holding out for CCE get deploying at least one SfBS pool now
• Coexistence will Require Cumulative Update 6 (CU6) on SfBS (not yet released)
• Lync 2010 or OCS 2007 R2 will unsurprisingly not be supported, so if you are on these and want to move to CCE you’ll need to look at other upgrade and or migration options
• Private TAP (Technology Adoption Program, similar to “preview”) is due to start in August 2017