Cloud PBX and Hybrid Voice Overview

Cloud Connector Overview Presenter:

Agenda Cloud PBX, so many choices Hybrid Voice Overview Cloud PBX with On Premises PSTN via Cloud Connector

Skype for Business PSTN Calling Options Online Hybrid On Premises Cloud PBX in Office 365 PSTN services provided by Microsoft End-user features & customer PSTN services integrated on- premises Users hosted in Office 365 Customer PSTN services integrated on- premises

Why Hybrid PSTN Options: 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

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 comparison Cloud PBX with on premises PSTN Calling with an existing pool Cloud PBX with on premises PSTN Calling via Cloud Connector Skype For Business On-Premises Cloud PBX with PSTN Calling Skype For Business Capabilities 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) Users should be in the same environment Delegation, team call Cloud Auto Attendant, available in CY16 Cloud Auto Attendant, available in CY16 Cloud Auto Attendant, available in CY16 Auto Attendant Hunt Groups Call Park Service (CPS) Voice Resiliency Branch Survivability Location Based Routing Call Admission Control Option to use own SIP trunk Call via Work Private line 911 Media Bypass IP phones Optimized for Skype For Business IP phones Compatible with Skype For Business Analog devices Common area phone Planned for CY16 Planned for CY16 Planned for CY16 Secured by SLA Only via local pool Static 911 only Static 911 only Static 911 only Only Polycom VVX supported, Yealink is coming Only Polycom VVX supported, Yealink is coming Only Polycom VVX supported, Yealink is coming Using on premises deployment Can be integrated and via local GW Using on premises deployment

Traffic Flow in Hybrid Scenario Overview

Signaling and Media Office 365 Server Pool Or Cloud Connector John SfB Online user in internal network Split Domain John SfB Online user in Internet PSTN Calls Existing Telephony Infrastructure Customer Premises Signaling PSTN 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 Edition Enables SFBO users to use onPrem PSTN resources Runs on Windows Server 2012R2 Data Center Edition Hypervisor, customer supplied server

Cloud Connector Architecture Four VMs on One Physical Host Machine, placed in Perimeter Network During deployment creates own forest No dependency on internal AD Domain Dial Plan Assigned online based on user location Option to restrict international calling (online) External SIP DNS points at online Skype For Business No co-existence with on premises deployment of Skype For Business Media traffic always flows via Mediation server Users can be created on premises and synchronized online using DirSync or created in Azure AD John SfB Online user in Internet PSTN PSTN GW 1 Mediation Edge PSTN GW 2 Domain Controller for Cloud Connector Storage SfB Online Infrastructure Dave SfB Online user in internal network Domain Controller Cloud Connector Sip Traffic Media Traffic

High Availability Up to 4 instances per site Calls are distributed in random order between Cloud Connectors in one pool Capacity 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; John SfB Online user in Internet Mediation Edge PSTN PSTN GW1 Domain Controller for Cloud Connector Storage Dave SfB Online user in internal network PSTN GW2 Cloud Connector 1 SfB Online Infrastructure PSTN GW3 Mediation Edge Domain Controller Korneel SfB Online user in Internet Domain Controller for Cloud Connector Storage Sip Traffic Media Traffic Cloud Connector 2

Multi Site Scenario PSTN Site to define pool level GW affinity: Cloud Connector Pool + PSTN gateways connected to the pool = PSTN Site New-CSHybridPSTNSite Tenant <TenantGUID> -Identity <PSTNSiteName> -EdgeFQDN <PSTNEdgeFQDN> Mediation Edge PSTN PSTN GW1 John SfB Online user in Internet, assigned to PSTN Site 1 DC CMS PSTN GW2 Mediation Edge Domain Controller PSTN Site 1 DC Seattle CMS User must be assigned to a specific PSTN Site Set-CSUserPSTNSettings HybridPSTNSite <name> - AllowInternationalDialing <BooleanValue> SfB Online Infrastructure Mediation Edge PSTN PSTN GW1 DC CMS Korneel SfB Online user in Internet, assigned to PSTN Site 2 PSTN GW2 No disaster Recovery between sites Mediation Edge Domain Controller PSTN Site 2 DC CMS Amsterdam Sip Traffic Media Traffic

Gateway Affinity M:N Mediation to Gateways supported GW chosen on round-robin order, can set preferred GW If gateway cannot accept the call, it will be redetected to another gateway Minimum 2 gateways recommended GWs have to be able to handle full amount of calls generated by Cloud Connector if one or more GW goes down, based on SLA John SfB Online user in Internet Mediation Edge PSTN PSTN GW1 Domain Controller for Cloud Connector Storage Dave SfB Online user in internal network PSTN GW2 Cloud Connector 1 SfB Online Infrastructure PSTN GW3 Mediation Edge Domain Controller Korneel SfB Online user in Internet Domain Controller for Cloud Connector Storage Cloud Connector 2

Cloud Connector Media Flow: outbound call from internal user to PSTN Dave places a call to an external PSTN user SIP Traffic routes to SfB Online SfB Online makes RNL of the number Call routed to Edge server (SIP and Media flow via Online Edge first and then via on premises Edge) If route exists, Edge relays the traffic to Media component in DMZ) Media component sends the traffic to PSTN gateway Media ports can be limited John SfB Online user in Internet PSTN GW Mediation Edge PSTN Domain Controller for Cloud Connector Storage Domain Controller SfB Online Infrastructure Dave SfB Online user in internal network Cloud Connector v2

Cloud Connector Media Flow: inbound call to internal user from PSTN PSTN GW receives call for user Dave Traffic routes to Mediation server Mediation server sends traffic to Edge and then it goes to SfB Online SfB Online makes RNL of the number Call routed to Dave Media ports can be limited John SfB Online user in Internet PSTN GW Mediation Edge PSTN Domain Controller for Cloud Connector Storage Domain Controller SfB Online Infrastructure Dave SfB Online user in internal network Cloud Connector v2

Cloud Connector Firewall Requirements (from DMZ perspective) Directi on Port/protocol Description Direction Port/protocol Descriptiom In TCP (TLS) 5067 Incoming requests from GW (TLS) In/Out TCP 443 STUN In TCP 5068 Incoming requests from GW Bidirectional TCP 5061 SIP 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 In UDP 3478 STUN Out TCP 5060 Outbound requests to GW In UDP 50 000 59 999 RTP (UDP) Recomended ports for media, can be limited In/Out 49 152 57 500 Meida ports (can be limited, up to 4 ports are required for 1 call) Out TCP/UDP 53 DNS In/Out 50 000 50 019 Media Port Range for internal Clients Internet PSTN PSTN GW Mediation Edge Domain Controller for Cloud Connector CMS Domain Controller John SfB Online Cloud Connector

Voicemail New voicemail service with no configuration required. Exchange Online for deposit, compliance & archiving. Features Include Personalized Greeting Message waiting indicator Customer Premises Office 365 Reply to voicemail with call MICROSOFT CONFIDENTIAL Approved Airlift Participants Only

Voicemail 23 Supported Languages Language Catalan Chinese (Hong Kong) China Chinese (Simplified) Chinese (Traditional) Taiwan Danish Dutch English English English English English Finnish French Country/Region Spain Culture ID ca-ES zh-HK zh-CHS zh-TW da-DK nl-NL en-AU en-CA en-IN en-GB en-US fi-Fl fr-CA Language French German Italian Japanese Korean Norwegian (Bokmal) Norway Polish Portuguese Portuguese Russian Spanish Spanish Swedish Country/Region France Germany Italy Japan Korean Culture ID fr-FR de-DE it-IT ja-JP ko-KR nb-NO pl-PL pt-BR pt-PT ru-RU es-ES es-MX sv-SE China Denmark Netherlands Australia Canada India United Kingdom United States Finland Canada Poland Brazil Portugal Russia Spain Mexico Sweden

Cloud PBX: Conferencing 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 . * Tolled Dial-in & Dial-out limited to protect against fraud & service abuse MICROSOFT CONFIDENTIAL Approved Airlift Participants Only

PSTN Conferencing availability Available now Second Wave* Austria Brazil Bulgaria Croatia Czech Republic Estonia Greece Ireland Current plan for launch, subject to change Japan Luxembourg Poland Portugal Romania Singapore Slovak Republic Slovenia South Korea United States Canada United Kingdom Germany France Italy Netherlands Norway Sweden Spain Belgium Finland Denmark South Africa Switzerland

PSTN Conferencing Dial-in Locations Argentina Australia Austria Belgium Brazil Canada Chile China Colombia Costa Rica Czech Republic Denmark Estonia Finland France Germany Hong Kong Hungary India Ireland Israel Italy Japan Mexico Netherlands New Zealand Norway Philippines Poland Portugal Romania Russia Singapore Slovak Republic Slovenia South Africa South Korea Spain Sweden Switzerland Taiwan Thailand Turkey United Kingdom United States

Requirements for Cloud Connector deployment 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) Capacity Stand-alone Min Top Capacity: 70% Internal Users, 30% External users, media transcoding performed by Mediation Server, handle up to 500 calls

Deployment Planning 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 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; 26

Post deployment 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> 27

Manageability 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 LineURI Set-CSUser Identity < User identity > -OnPremLineURI <tel:+ phonenumber> Restricting international calling on tenant level Grant-CsVoiceRoutingPolicy Identity <User identity> -PolicyName InternationalCallsDisallowed 28

Q&A

Cloud PBX with On-Premises PSTN Connectivity Prerequisites\Features Via Existing Lync 2013\Skype for Business 2015 Pool Users must be created Only in on premises AD and syncronized to Azure AD AADSync \ Dirsync considerations Latest Version Required* Via Cloud Connector Edition In on premises AD and syncronized to Azure AD or in the Azure AD directly Latest Version Required* if users created in on premises AD, not required if users created in Azure AD No Co-existence with On Premises Deployment supported Gateway\IP PBX\SIP Trunk Calling restristions Dial Plan to accomodate user calling habits Yes, Lync 2013 Pool or higher Must be form list of tested devices (http://technet.Microsoft.com/UCOIP) Ability to limit international calling in Voice Policy Online Can be configured in on premises envirionment (default behavior) or assigned pre-defined online dial plan (per tenant configuration) Must contain Pool name in SN, machine names in SAN Yes Pre-defined online dial plan only External Certificates Pool name in SN, machine names in SAN or sip.domainname and wildcard in SAN No Enterprise Voice configured and tested before configuration Active Directory Federation Services Recommended Users can be homed In on premises or Office 365 Office 365 Services 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