microsoft cloud connector overview

Presenter:

Cloud Connector Overview

Agenda

Cloud PBX, so many choicesHybrid Voice OverviewCloud PBX with On Premises PSTN via Cloud Connector

Cloud PBX in Office 365PSTN services provided by Microsoft

Online Hybrid On Premises

Skype for Business PSTN Calling Options

Users hosted in Office 365Customer PSTN services integrated on-premises

End-user features & customer PSTN services integrated on-premises

PSTN Calling option from Microsoft is currently unavailable in your market

Customer just signed a 5y Telco contract Customer has custom services from PBX

entrenched in their work flow

Why Hybrid PSTN Options:

Cloud PBX: so many choices

Cloud PBX: So many choices… With PSTN Calling Service

• Users homed online, PSTN service provided by Microsoft

• No on premises Skype For Business infrastructure required

• Available in the US only With On Premises PSTN Connectivity via Cloud

Connector Edition • Users homed online, PSTN service provided by 3rd party • Deployment of Cloud Connector on premises required ,

cannot coexist with on premises deployment of Skype For Business/Lync Servers

• Available worldwide With On Premises PSTN Connectivity with an existing

deployment• Some users homed online, some users can be homed on

premises, PSTN service provided by 3rd party • Maintaining of Skype For Business or Lync 2013 deployment

required• Available worldwide

Decision Tree Moving to the Cloud is the

strategic goal For US customers consider PSTN

Calling with porting their existing numbers first

Cloud Connector for companies outside the US or when customer wants to keep their existing SIP trunk

On Premises PSTN connectivity with an existing deployment when customer has some unique functionality which not offered in the Cloud (combination)

Do not forget about Dial in conferencing and Express Route

Features comparisonSkype For Business

CapabilitiesSkype For

Business On-Premises

Cloud PBX with on premises PSTN Calling with an existing pool

Cloud PBX with on premises PSTN

Calling via Cloud Connector

Cloud PBX with PSTN Calling

Basic Call Features (hold/retrieve, transfer, forwarding) ü ü ü ü

Voice mail Exchange UM Cloud PBX Voice Mail (Exchange Online Required)

Cloud PBX Voice Mail (Exchange Online Required)

Cloud PBX Voice Mail (Exchange Online Required)

Delegation, team call ü Users should be in the same environment

ü

Auto Attendant Cloud Auto Attendant, available in CY16

Cloud Auto Attendant, available in CY16

Cloud Auto Attendant, available in CY16

Hunt Groups ü Planned for CY16 Planned for CY16 Planned for CY16Call Park Service (CPS) üVoice Resiliency Secured by SLABranch Survivability Only via local poolLocation Based RoutingCall Admission ControlOption to use own SIP trunk ü ü ü ÛCall via WorkPrivate line ü û911 ü Static 911 only Static 911 only Static 911 onlyMedia Bypass üIP phones “Optimized for Skype For Business”IP phones “Compatible with Skype For Business”

Only Polycom VVX supported, Yealink is coming



Analog devices ü Using on premises deployment Can be integrated and via local GW

Common area phone Using on premises deployment

Traffic Flow in Hybrid Scenario Overview

Signaling and MediaOffice 365

Customer Premises

PSTN

PSTN CallsExisting Telephony Infrastructure

Server Pool Or Cloud Connector

Split Domain

John SfB Online user in

Internet


internal network

Signaling

Media

Cloud PBX with On Premises PSTN connectivity via Cloud Connector

What is Cloud Connector?Set of VMs (4) running a mashup of custom pieces of SFB on Windows Server 2012R2 Data Center EditionEnables SFBO users to use onPrem PSTN resourcesRuns on Windows Server 2012R2 Data Center Edition Hypervisor, customer supplied server

Cloud Connector Architecture

SfB Online Infrastructure


Internet

Four VMs on One Physical Host Machine, placed in Perimeter NetworkDuring deployment creates own forestNo dependency on internal AD DomainDial Plan Assigned online based on user location Option to restrict international calling (online)External SIP DNS points at online Skype For BusinessNo co-existence with on premises deployment of Skype For BusinessMedia traffic always flows via Mediation serverUsers can be created on premises and synchronized online using DirSync or created in Azure AD

Sip Traffic Media Traffic

Mediation Edge

Domain Controlle

r

Storage

Cloud Connector

Domain Controller for Cloud

Connector

PSTN GW 1

Dave SfB Online user in internal network

PSTN

PSTN GW 2

High Availability



Internet

Up to 4 instances per siteCalls are distributed in random order between Cloud Connectors in one poolCapacity planning calculation should consider ability to handle load if one or several Cloud Connectors will go down, based on SLA:• N+1 boxes support 500*N

concurrent calls with 99.8% availability;

• N+2 boxes support 500*N concurrent calls with 99.9% availability;

Mediation Edge

Storage

Cloud Connector 2


Connector

PSTN GW3


Mediation Edge

Domain Controlle

r

Storage

Cloud Connector 1


Connector

PSTN GW1


PSTN

Korneel SfB Online user in

Internet

PSTN GW2

Multi Site Scenario


John SfB Online user in Internet, assigned to PSTN

Site 1

PSTN Site to define pool level GW affinity: Cloud Connector Pool + PSTN gateways connected to the pool = PSTN SiteNew-CSHybridPSTNSite –Tenant <TenantGUID> -Identity <PSTNSiteName> -EdgeFQDN <PSTNEdgeFQDN>

User must be assigned to a specific PSTN SiteSet-CSUserPSTNSettings – HybridPSTNSite <name> -AllowInternationalDialing <BooleanValue>

No disaster Recovery between sites


PSTN GW1PSTN

Korneel SfB Online user in Internet, assigned to PSTN

Site 2

PSTN GW2

Mediation Edge

DC CMS

Domain Controlle

r

Mediation Edge

DC CMS

PSTN GW1PSTN

PSTN GW2

Mediation Edge

DC CMS

Domain Controlle

r

Mediation Edge

DC CMS

PSTN Site 1

PSTN Site 2

Seattle

Amsterdam

Gateway Affinity



Internet

M:N Mediation to Gateways supportedGW chosen on round-robin order, can set preferred GWIf gateway cannot accept the call, it will be redetected to another gatewayMinimum 2 gateways recommendedGWs have to be able to handle full amount of calls generated by Cloud Connector if one or more GW goes down, based on SLA

Mediation Edge

Storage

Cloud Connector 2


Connector

PSTN GW3

Mediation Edge

Domain Controlle

r

Storage

Cloud Connector 1


Connector

PSTN GW1


PSTN

Korneel SfB Online user in

Internet

PSTN GW2

Cloud Connector Media Flow: outbound call from internal user to PSTN



Internet

1. Dave places a call to an external PSTN user

2. SIP Traffic routes to SfB Online

3. SfB Online makes RNL of the number

4. Call routed to Edge server (SIP and Media flow via Online Edge first and then via on premises Edge)

5. If route exists, Edge relays the traffic to Media component in DMZ)

6. Media component sends the traffic to PSTN gateway

Domain Controlle

r

Cloud Connector v2

Mediation Edge

StorageDomain

Controller for Cloud

Connector

PSTN GW


PSTN

Media ports can be limited

Cloud Connector Media Flow: inbound call to internal user from PSTN



Internet

1. PSTN GW receives call for user Dave

2. Traffic routes to Mediation server

3. Mediation server sends traffic to Edge and then it goes to SfB Online

4. SfB Online makes RNL of the number

5. Call routed to Dave

Domain Controlle

r

Cloud Connector v2

Mediation Edge

StorageDomain

Controller for Cloud

Connector

PSTN GW


PSTN

Media ports can be limited

Cloud Connector Firewall Requirements (from DMZ perspective)

Internet

• When Cloud Connector is deployed, all users will remain hosted in the cloud and consume all services via the cloud

• Only PSTN Ingress and Egress from on-premises is enabled with Cloud Connector

• Firewall Requirements are identical to compared to Skype for Business Access Edge and A/V Edge

Direction Port/protocol Descriptiom

In/Out TCP 443 STUNBidirectional TCP 5061 SIPIn UDP 3478 STUNIn UDP 50 000 –

59 999RTP (UDP) Recomended ports for media, can be limited

Out TCP/UDP 53 DNS

Direction

Port/protocol Description

In TCP (TLS) 5067 Incoming requests from GW (TLS)

In TCP 5068 Incoming requests from GW

Out TCP 5060 Outbound requests to GW

In/Out 49 152 – 57 500 Meida ports (can be limited, up to 4 ports are required for 1 call)

In/Out 50 000 – 50 019 Media Port Range for internal Clients

Mediation Edge

Domain Controlle

r

CMS

Cloud Connector


Connector

PSTN GW

PSTN

John SfB Online

MICROSOFT CONFIDENTIAL – Approved A i r l i f t Pa r t i c ipants On ly

New voicemail service with no configuration required.Exchange Online for deposit, compliance & archiving.

Features Include• Personalized Greeting• Message waiting indicator• Reply to voicemail with call

Voicemail

Office 365CustomerPremises

Voicemail

Language Country/Region Culture ID Catalan Spain ca-ESChinese (Hong Kong)

China zh-HK

Chinese (Simplified)

China zh-CHS

Chinese (Traditional)

Taiwan zh-TW

Danish Denmark da-DKDutch Netherlands nl-NLEnglish Australia en-AUEnglish Canada en-CAEnglish India en-INEnglish United Kingdom en-GBEnglish United States en-USFinnish Finland fi-FlFrench Canada fr-CA

23 Supported LanguagesLanguage Country/

Region Culture ID

French France fr-FRGerman Germany de-DEItalian Italy it-ITJapanese Japan ja-JPKorean Korean ko-KRNorwegian (Bokmal)

Norway nb-NO

Polish Poland pl-PLPortuguese Brazil pt-BRPortuguese Portugal pt-PTRussian Russia ru-RUSpanish Spain es-ESSpanish Mexico es-MXSwedish Sweden sv-SE

MICROSOFT CONFIDENTIAL – Approved A i r l i f t Pa r t i c ipants On ly

• All Cloud PBX users are homed in Office 365.

• User services include Presence & Meetings.

• PSTN Dial-in and Dial-out through native PSTN Conferencing service.*

• User can also be serviced through ACP.

Cloud PBX: Conferencing

* Tolled Dial-in & Dial-out limited to protect against fraud & service abuse

PSTN Conferencing availabilityUnited States Canada United Kingdom Germany FranceItaly Netherlands Norway Sweden

Spain Belgium Finland Denmark South AfricaSwitzerland

AustriaBrazilBulgaria Croatia Czech RepublicEstoniaGreeceIreland

JapanLuxembourg PolandPortugalRomaniaSingaporeSlovak RepublicSloveniaSouth Korea

Available now

Second Wave*

• Current plan for launch, • subject to change

PSTN Conferencing Dial-in LocationsArgentinaAustraliaAustriaBelgiumBrazilCanadaChileChinaColombiaCosta RicaCzech Republic

DenmarkEstoniaFinlandFranceGermanyHong KongHungaryIndiaIrelandIsraelItaly

JapanMexicoNetherlandsNew ZealandNorwayPhilippinesPolandPortugal RomaniaRussiaSingapore

Slovak RepublicSloveniaSouth AfricaSouth KoreaSpainSwedenSwitzerlandTaiwanThailandTurkeyUnited KingdomUnited States

• No on premises Skype For Business Deployment• Exchange Online for Voice Mail• Qualified PBX/Trunk or qualified SBC/Gateway• Dual 64 bit, six core processor (12 real cores), equivalent or better than

dual Intel Xeon E5-2430 v2, 2.50GHz, 15M Cache, 7.2GT/s QPI, Turbo, 6C, 80W , Max Mem 1600MHz. 32 Gb ECC RAM equivalent or better than 8GB RDIMM, 1600MT/s , Four 600GB ( or better) 10K RPM 128M Cache SAS 6Gbps, configured in RAID 5 configuration. Three 1 Gbps RJ45 high throughput network adapters

• Dial in conferencing from Microsoft or via ACP provider (if required)

Requirements for Cloud Connector deployment

CapacityStand-alone Min Top Capacity: 70% Internal Users, 30% External users, media transcoding performed by Mediation Server, handle up to 500 calls

Deployment

26

Planning• Plan the solution using planning book;• Make sure that all required ports opened in firewalls;• Create external DNS records for Edge pools;• Request external certificate;Deployment• Provide answers in INI file (from planning book);• Put external certificate in …\CloudConnector\Certificates\External• Run the script on new hardware (if you have network switches, use –

skipexistingobjects key);• Provide certificate password, administrator names and administrator passwords

• In about 2 hours VMs will be deployed;

Post deployment

27

• Setup hybrid:Set-CsTenantFederationConfiguration -SharedSipAddressSpace $True

a) One site: Set-CsTenantHybridConfiguration -PeerDestination <External Access Edge FQDN>

b) Multiple sites:New-CsHybridPstnSite -Identity <PSTN Site Name> -EdgeFqdn <External Access

Edge FQDN>

• Enable users: Assign Cloud PBX as a part of E5 or standalone license; Enable users in PowerShell

Get-CsOnlineUser <User name> | Set-CSUser – EnterpriseVoiceEnabled $true – HostedVoiceMail $true –OnPremLineURI <tel:+phonenumber>

For Multiple site scenario:

Set-CsUserPstnSettings -Identity <User name> -HybridPstnSite <PSTN Site Name>

Manageability

28

• Standard PowerShell cmdlets work for Cloud Connector when applicable

• Do not use topology builder• Modifying topology after deployment. Export-

CSConfiguration, modify file and import topology using Import-CSConfiguration

• Changing user LineURISet-CSUser –Identity < User identity > -OnPremLineURI <tel:+ phonenumber>

• Restricting international calling on tenant levelGrant-CsVoiceRoutingPolicy –Identity <User identity> -PolicyName InternationalCallsDisallowed

tel:+%20phonenumber

tel:+%20phonenumber

tel:+%20phonenumber

Cloud PBX with On-Premises PSTN ConnectivityPrerequisites\Features Via Existing Lync 2013\Skype for

Business 2015 PoolVia Cloud Connector Edition

Users must be created Only in on premises AD and syncronized to Azure AD

In on premises AD and syncronized to Azure ADor in the Azure AD directly

AADSync \ Dirsync considerations Latest Version Required* Latest Version Required* if users created in on premises AD, not required if users created in Azure AD

Co-existence with On Premises Deployment supported

Yes, Lync 2013 Pool or higher No

Gateway\IP PBX\SIP Trunk Must be form list of tested devices (http://technet.Microsoft.com/UCOIP)Calling restristions Ability to limit international calling in Voice Policy OnlineDial Plan to accomodate user calling habits

Can be configured in on premises envirionment (default behavior) or assigned pre-defined online dial plan (per tenant configuration)

Pre-defined online dial plan only

External Certificates Must contain Pool name in SN, machine names in SAN

Pool name in SN, machine names in SAN or sip.domainname and wildcard in SAN

Enterprise Voice configured and tested before configuration

Yes No

Active Directory Federation Services

Recommended

Users can be homed In on premises or Office 365 Office 365Services Consumption (Conferencing etc.)

On premises users use on premises environment, Office 365 users use Office 365

Office 365 only, except for PSTN calling*Only the AADSync version of November 2015 and higher is capable of picking up Schema Changes after installation

microsoft cloud connector overview

Technology