1. Skype Summit 2016 – Minneapolis
Voice Topologies for Cloud Migration
Presented by
Avi Perpinyal
2. FourKey Scenarios- Notmutually exclusive
SfB Server SfB Hybrid Cloud PBX
w/PSTN
SfB Online (Cloud PBX)
Req’d for Skype
Meeting Broadcast
SFB Server
Mix b/w Server and
Online (Cloud PBX)
CALL
MANAGEMENT
PSTN
CALLING
Connectivity to
PSTN Providers
Cloud PSTN Calling
Connectivity to
PSTN Providers
Cloud PBX
O/P PSTN
SfB Online (Cloud PBX)
Connectivity to
PSTN Providers
Cloud PBX w/
Microsoft Provided
PSTN Calling
On-Premises or Hosted
SfB Server
Split users b/w SfB
Server and SfB Online
Cloud PBX w/
On-Premises PSTN
DESCRIPTION
NOTES
Full PBX Features
Missing advanced
calling features
Feature set not at
parity with on-prem
Deploying Skype for Business
5. Call Routing Summary
User’s Direct Inward Dial (DID) number terminates at PSTN gateway or PBX.
Call is routed to on-premises Skype For Business deployment.
User’s Active Directory object indicates a different deployment locator.
Request is proxied through on-premises Edge proxy to Skype For Business Online.
Invite is routed to end user’s logged-in endpoints.
If accepted, media is routed either locally or through the company’s Edge Server or firewall.
If rejected, media is routed to Cloud PBX Voice Mail.
User instantiates a PSTN call.
Client normalizes number and sends invite to home server.
Voice policy enforcement and call authorization is performed on-premises.
Call is routed to PSTN via Mediation Server.
6. Registration – Online User
Skype For Business Online client
discovers the server through the Domain
Name Service (DNS) Service Location
(SRV) resource record
On-premises server redirects the Skype
For Business Online client to the cloud
Dave
Sfb Online
Skype For Business On-Premises
SfB Online
Infrastructure
1
2
3
DNSSRV
PSTN
Internet
0
Media
Signaling
PSTN GW
Front-End Edge
7. Call Flow – Peer to Peer Online Users
Peer to Peer: Two Skype For
Business Online Users
Session Initiation Protocol (SIP) signaling
flows through Skype For Business Online
Media flows using the optimal path
between the client endpoints
Dave
SfB Online
Skype For Business On-Premises
SfB Online
Infrastructure
3
1
PSTN
Internet
4
John
SfB Online 2
Media
Signaling
PSTN GW
Front-End Edge
8. Call Flow – Peer to Peer On Premise to Online User
Peer to Peer: On-Premises
to Skype For Business Online Users
SIP signaling is routed between the
on-premises deployment and
Skype For Business Online
Media flows using the optimal
path between the client endpoints
Dave
SfB Online
SfBOn-
Premises SfB Online
Infrastructure
3
Internet
5
Kathy
SfB On-
Premises 4
1
2
Media
Signaling
Front-End
Edge
9. Call Flow – Incoming PSTN Call to Online User
Incoming PSTN Call
An incoming PSTN call is routed to the on-
premises gateway, then moves to the on-
premises Skype For Business Server
The number is located via Reverse Number
Lookup (RNL), routed to Skype For Business
Online, and then routed to the Skype For
Business Online endpoint
Media always flows through Mediation server
and PSTN Gateway
Dave
LyncOnline
SfB Online
Infrastructure
5
PSTN
Internet
4
5a
1 2
5b 3
4
Media
Signaling
Skype For Business On-Premises
Front-End
Edge
PSTN
GW
10. Call Flow – Incoming PSTN Call to Online User
Incoming PSTN Call (External
User)
An incoming PSTN call is routed to the on-premises
gateway, then moves to the on-premises Skype For
Business Server
The number is located via RNL, routed to Skype For
Business Online, and then routed to the Skype For
Business Online endpoint (on the Internet)
Media flows using the optimal path between the
client endpoint and the MS
Most likely through the on-premises Edge Server; if
not, between the online and on-premises Edge
Server
John
SbBOnline
SfB Online
Infrastructure
PSTN
Internet
3
4
1 2
5
5
2
5
3
Media
Signaling
Skype For Business On-Premises
Front-End
Edge
PSTN
GW
11. Call Flow – Outgoing PSTN Call from Online User
Outgoing PSTN Call
An outgoing PSTN call request is placed by a user
hosted on Skype For Business Online
An RNL is performed and fails to associate a user
The request is assumed to be a PSTN/PBX call and is
proxied to the on-premises Skype For Business
Server
Voice policy enforcement and call authorization are
performed on-premises
The call is routed to PSTN egress
Media flows using the optimal path between the
client endpoint and PSTN infrastructure/MS
Dave
SfB Online
Skype For Business On-Premises
SfB Online
Infrastructure
PSTN
Internet
2
4b
3
2
4a
Voicepolicy
enforcementandcall
authorizationdone
on-premises
1
Media
Signaling
Front-
End
Edge
PSTN
GW
12. Call Flow – Outgoing PSTN Call from Online User (External)
Outgoing PSTN Call (External
User)
An outgoing PSTN call request is placed by a user
hosted on Skype For Business Online
An RNL is performed and fails to associate a user
The request is assumed to be a PSTN/PBX call and is
proxied to on-premises Skype For Business Server
Voice policy enforcement and call authorization are
performed on-premises
The call is routed to PSTN egress
Media flows using the optimal path between the
client endpoint and MS
Most likely through the on-premises Edge Server; if
not, between the online and on-premises Edge
Server
John
LyncOnline
SfB Online
Infrastructure
PSTN
Internet
2
1
4
5
5
3
5
2
Media
Signaling
Skype For Business On-Premises
Front-End
Edge
PSTN
GW
18. Cloud Connector Architecture
SfB OnlineInfrastructure
JohnSfB Online
user in Internet
Sip Traffic
Media Traffic
Mediation Edge
Domain
Controller
Storage
Cloud Connector
Domain
Controller for
Cloud
Connector
PSTN GW 1
Dave SfB
Onlineuser
in internal
network
PSTN
PSTN GW 2
19. High Availability
SfB OnlineInfrastructure
Reed SfB Online
user in Internet
Mediation Edge
Storage
Cloud Connector 2
Domain
Controller for
Cloud
Connector
PSTN GW3
Sip Traffic
Media Traffic
Mediation Edge
Domain
Controller
Storage
Cloud Connector 1
Domain
Controller for
Cloud
Connector
PSTN GW1
Dave SfB
Onlineuser
in internal
network
PSTN
MaureenSfB
Onlineuser in
Internet
PSTN GW2
20. Multi Site Scenario
SfB OnlineInfrastructure
JoannaSfB Onlineuser in
Internet, assigned to PSTN Site 1
Sip Traffic
Media Traffic
PSTN GW1
PSTN
Maureen SfB Onlineuser in
Internet, assigned to PSTN Site 2
PSTN
GW2
Mediation Edge
DC
CMS
Domain
Controller
Mediation Edge
DC
CMS
PSTN GW1
PSTN
PSTN
GW2
Mediation Edge
DC
CMS
Domain
Controller
Mediation Edge
DC
CMS
PSTN Site 1
PSTN Site 2
Chicago
Hoboken
21. Gateway Affinity
SfB OnlineInfrastructure
AaronSfB Online
user in Internet
Mediation Edge
Storage
Cloud Connector 2
Domain
Controller for
Cloud
Connector
PSTN GW3
Mediation Edge
Domain
Controller
Storage
Cloud Connector 1
Domain
Controller for
Cloud
Connector
PSTN GW1
Dave SfB
Onlineuser
in internal
network
PSTN
Ishita SfB Online
user in Internet
PSTN GW2
22. Cloud Connector Media Flow: outbound call from internal user
to PSTN
SfB OnlineInfrastructure
Amber SfB
Onlineuser in
Internet
Domain
Controller
Cloud Connector v2
Mediation Edge
Storage
Domain
Controller for
Cloud
Connector
PSTN GW
Ricardo SfB
Onlineuser
in internal
network
PSTN
Media portscan belimited
23. Cloud Connector Media Flow: inbound call to internal user from
PSTN
SfB OnlineInfrastructure
JohnSfB Online
user in Internet
Domain
Controller
Cloud Connector v2
Mediation Edge
Storage
Domain
Controller for
Cloud
Connector
PSTN GW
Dave SfB
Onlineuser
in internal
network
PSTN
Media portscan belimited
24. Cloud Connector Firewall Requirements (from DMZ perspective)
Internet
Direction Port/protocol Descriptiom
In/Out TCP 443 STUN
In/Out TCP 5061 SIP
In UDP 3478 STUN
In/Out TCP/UDP 50,000
– 59,999
RTP (UDP)
Recomended
ports for media,
can be limited
Out TCP/UDP 53 DNS
Directi
on
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 UDP 49,152 – 57,500 Meida ports (can
be limited, up to 4
ports are required
for 1 call)
In/Out TCP/UDP 50,000 – 50 ,019 Media Port Range
for internal Clients
Mediation Edge
Domain
Controller
CMS
Cloud Connector
Domain
Controller for
Cloud
Connector
PSTN GW
PSTN
JohnSfB Online
27. Co-Existence with legacy PBX or IP-PBX through CCE
SfB Online Infrastructure
John SfB Online
user in Internet
SIP Traffic
Media Traffic
Mediation Edge
Domain
Controller
Storage
Cloud Connector
Domain
Controllerfor
Cloud
Connector
Dave SfB
Onlineuser
in internal
network
PSTN
(SIP or PRI)
• Use SBC Wizard to connect the IP-
PBX to the CCE
• SIP Normalization
• Dial plan
• Number manipulation
• Transcoding
GW/SBC
28. Recording PSTN and CDRs
SfB Online Infrastructure
John SfB Online
user in Internet
SIP Traffic
Media Traffic
R
Mediation Edge
Billing
Server
Storage
Cloud Connector
Domain
Controllerfor
Cloud
Connector
GW/SBC
Dave SfB
Onlineuser
in internal
network
PSTN
SIPT
Recording
CDR
• Provide CDR for Cloud PBX user calls to the PSTN
• Local recording for PSTN calls by the SmartTAP
29. Analog Device Support
SfB Online Infrastructure
John SfB Online
user in Internet
SIP Traffic
Media Traffic
R
Mediation Edge
Storage
Cloud Connector
Domain
Controllerfor
Cloud
Connector
GW/SBC
Dave SfB
Onlineuser
in internal
network
PSTN
SIPT
• AudioCodes SBC can terminate analog GW
registrations
• Present the analog device toward the
Cloud PBX
• Rout the calls to the analog extensions
MediaPack 1xx
30. CCE Fail over and site Voice resiliency using AD look-Up
SfB Online Infrastructure
John SfB Online
user in Internet
SIP Traffic
Media Traffic
R
Mediation Edge
Storage
Cloud Connector
Domain
Controllerfor
Cloud
Connector
Customer
Domain
Controller
GW/SBC
Dave SfB
Onlineuser
in internal
network
PSTN
SIPT
For Incoming calls
• If the Cloud PBX is not available
• SBC/GW can use AD lookup, and
Find the user Mobile number.
• SBC/GW can call the mobile
31. High end, executive model
5” TFT 800x480 touch screen
Integrated Bluetooth,
USB Port
1GB Eth
Optional Expansion unit
Cost-effective, basic model
Basic LCD with 4
programmable soft keys
1GB Eth (Optional)
Skype Business Desk Phones
AudioCodes Managed IP Phone solution Now support Silk!
User Experience through voice quality, intuitive design, and powerful features
AudioCodes provides INNOVATIVE, MANAGED, RESILIENT Solution at affordable price
405HD IP Phone
420HD IP Phone
430HD IP Phone
Mid-range model
Boast a large LCD and 12
programmable speed dials
keys
USB Port
1GB Eth (Optional)
Advanced mid-range model
Improved Graphic LCD
256x128 Dedicated LCD
displaying
12 contacts and their presence
1GB Eth
USB Port
440HD IP Phone
450HD IP Phone
PRICE
MODEL
Low-cost, Entry level model
Basic LCD with 4
programmable soft keys
*1GB Eth & USB starting July
16
32.
33. Features comparison
Basic Call Features (hold/retrieve, transfer, forwarding)
Voice mail Exchange UM Cloud PBX Voice Mail Cloud PBX Voice Mail
USB peripherals
Delegation, team call Users should be in the same environment
Voice Resiliency Secured by SLA
Branch Survivability
Location Based Routing
Call Admission Control
Integration with on-premises PBX
Call via Work
Private line
911 Static 911 only Static 911 only
RGS/Call Park Service (CPS)
Media Bypass
Number porting
IP phones “Optimized for Skype For Business”
IP phones “Compatible with Skype For Business”
Analog devices Using on premises deployment
Common area phone Using on premises deployment
34. On-premises PSTN Connectivity
New
Customer
Server Pool
Cloud
Connector
Edition
Partner
Appliance
Cloud
Connected
Appliance
Existing
Customer
Server Pool
Connect existing
topology to
Office 365 using
Split Domain &
migrate users to
Cloud PBX.
Cloud PBX user’s
PSTN Traffic
transits pool.
Deploy Skype for
Business Server
and connect it
with Office 365.
Customers can
operate
additional
services on-
prem (VIS, etc.)
Packaged VMs
on Customer
Hardware
provides PSTN
connectivity
components with
Office 365.
Cloud PBX users
PSTN Traffic
transits VMs
Future offering
where partner
packages
required Skype
for Business
Server software
or VMs with
SBC/Gateway
Future offering
where PSTN
connectivity is
bundled with
network
management
and quality of
service telemetry
for O365.
35. The Smoothest Road to Cloud PBX is Through CloudBond 365
Full SfB Deployment with
GW/SBC
Special O365 Connector Third Party Applications
Simplified and Enhanced
Management
AudioCodes CloudBond 365
36. All-in-one appliance for offices and branches
and virtualized software for datacenters and operators
Sync and management tool for complete life-
cycle operations of UC users
Mediant 800
with OSN
HP
Server
Voice
Connectivity
SfB/Min Topology
Installer and Wizard
O365/CloudPBX and AD
Connectors and User
Management (incl IPP)
CloudBond Standard Box Edition v Gateway/ SBC v v
CloudBond Pro Box Edition
CloudBond Enterprise Box Edition
v SBC v v
CloudBond Virtualized Edition SBC v v
CloudBond Management Pack v
CloudBond™ 365 CloudBond™ Management Pack
CloudBond 365 Family
37. Same platform as CloudBond 365 Standard+ Edition
Identical CCE experience
Identical experience to when installed on external server
Pre-integrated with gateway/SBC
Users capacity: Related to M800 SBC/E1/T1 capacity
High user capacity possible because users are registered to the cloud, not to
appliance
Supports SBC HA with active-active CCE architecture
Pricing
Based on Mediant 800 with OSN
CCE software is FREE
Windows O/S licensing included (OEM)
Depends on TDM or SBC capacity
Mediant 800 CCE Appliance
38. Same platform as CloudBond 365 Enterprise Edition
Identical CCE experience
Identical experience to when installed on external server
Pre-integrated with SBC (only)
Users capacity: 500 concurrent sessions , correlates to ~ 5000 users
Supports SBC HA with active-active CCE architecture
Pricing
CCE software is FREE
Windows O/S licensing included (OEM)
Depends on SBC capacity
Server Based CCE Appliance
39. Deciding which topology is right for you
Your situation Cloud PBX solution
Your PBX system offers unique features that you need
to retain.
Investigate replacing
your PBX with Skype
for Business Server
Your PBX does not offer unique features that you
need to retain, PSTN Calling service is available in your
region, and you want to use Microsoft-provided PSTN
services.
Subscribe to PSTN
Calling service
Your PBX does not offer unique features that you
need to retain, PSTN Calling service is not available in
your region, and you have an existing Lync or Skype
for Business Server deployment.
In this scenario it is also possible that all your users
are in the United States, but you cannot consider
moving to Microsoft-provided PSTN for other reasons-
- such as contractual obligations with your existing
carrier.
Connect your existing
Skype for Business
Server deployment
with Cloud PBX
Your PBX does not offer unique features that you
need to retain, PSTN Calling service in not available in
your region, and you do not have an existing Lync or
Skype for Business Server deployment.
In this scenario, it is also possible that PSTN Calling
service is available in your region, but you cannot
consider moving to Microsoft-provided PSTN for other
reasons-- such as contractual obligations with your
existing carrier.
Deploy Cloud
Connector
AD sync between on-prem and AAD
“Hybrid Organization” is that a property somewhere
“Deployment Locator” - Ie. AD object attribute that indicates user lives in the cloud
“Home Server” Is this the FE pool where user initially registered
Reverse number lookup (RNL) – Look up of dialed number in local AD to determine when user “lives”
In this case, Dave Online is within the LAN!
Why does John’s call always go to Redmond? John was registered via Redmond using SRV or LyncDiscover. ONLY one on premise pool can be designated “first “registrar.
Does the “Voice Policy” at Redmond FE determine that the call should be routed to Amsterdam FE?
So, a deployment of Cloud Connector itself is really just four virtual machines, running a Skype for Business 2015 Edge server, a Skype for Business 2015 Mediation Server, there’s an Active Directory server or domain controller and there’s a CMS or Central Management Server.
The first thing to note here is that when we say there is an Active Directory server. It’s simply used by the application servers, these are entirely independent of the enterprises Active Directory infrastructure.
In regards to the server roles that you’re familiar with, they are not quite the same. We have customized the Skype for Business deployment and the bits inside of the deployment, specifically as it relates to how we route signaling. You’ll note that we don’t have a conventional Front End server or Registrar role, so that’s why we refer to this as a mashup of customized roles to make up the Cloud Connector deployment.
As you’ve probably figured out Cloud Connector is a stateless application, that don’t really know anything about the users, since these users are homed in the cloud, they are not homed on-premises. For the most part, we’re probably 98% the same code we have in a standard Skype for Business deployment, with that 2% of customization to address some of the Cloud Connector requirements with things like custom static routes.
These VMs are deployed on top of hardware provided by the customer in this iteration, eventually our goal is to be an appliance based solution that the customer configures in the cloud, a synchronization of sorts happens and then the device is configured with that information.
There can be no more than 30% ext users. When external, both Edge and Mediation resources in use. Internal, only mediation.
So let’s look under the covers of a typical Cloud Connector deployment and talk about the Cloud Connector architecture. In this overview you can see I have a Cloud Connector deployment in the middle, which is located in the customers DMZ. We have John who’s who is connecting remotely over the internet from his local coffee shop. Inside of the corporate network we have two PSTN gateways, we are showing those as PSTN Gateway 1 and PSTN Gateway 2.
We’ve got the customers internal Active Directory infrastructure and notice it’s not shared, connected or even trusted with the Cloud Connector deployment.
Let’s look at the call flow in this animated example, remember that Media is always leveraging the on-premises assets. We have the SIP traffic talking to the Skype for Business Online infrastructure, which then routes that SIP traffic to the Edge server role within the Cloud Connector deployment. The Edge role routes the SIP signaling to the Mediation Server and then to the PSTN Gateway.
Media in this scenario flows from John, to the Edge server role, to the Mediation Server and to the on-premises PSTN Gateway.
Other things to note, which we call out on the left is that when you deploy Cloud Connector, we create our own AD DS forest for Cloud Connector Edition, with no connectivity or dependency on the customers internal AD DS.
The dial plan assigned is an online dial plan which is assigned based on user location . We do have the ability to restrict international calling. External SIP DNS points at online Skype For Business, this is where the users registrar is located. There is no co-existence with on premises deployment of Skype For Business.
Users can be created on-premises and synchronized online using DirSync or created in Azure AD
We have the ability to scale out Cloud Connector Edition by simply deploying more physical hosts. We can deploy up to four Cloud Connector instances per site.
<Walk through animated slides>
Note that this is multiple Cloud Connectors in a single site distributing calls across multiple PSTN Gateways.
The following is an example of a multi site scenario where we are keeping affinity to the local PSTN gateways. In this scenario Joanna is in Chicago, which is where PSTN Site 1 is located and her two cloud Connector deployments will not leverage the gateways in Hoboken or PSTN Site 2.
Maureen, who is assigned to PSTN Site 2, will leverage the CCE deployments in Hoboken, as set per the Set-CsUserPSTNSettings cmdlet .
How many gateways can be connected to Cloud Connector? There is no published limit, however recommendation is to plan number of ports accordingly. For example, there is no sense in deploying 6 gateways with 20 ports each, instead recommendation is to deploy two gateways with 60 ports each.
In Cloud Connector configuration file (CloudConnector.ini), you can specify Media port range for External Edge. This will configure the Edge Service MediaCommunicationPort count starting from Port of 50000. This could also be configured/modified after the fact using Set-CsService –EdgeServer –MediaCommunicationPortCount.
To limit Mediation Server port range, use Set-CsMediationServer -AudioPortStart 49152 -AudioPortCount 8438
Modifying the topology is limited in support and scope and will push the boundaries of what is possible.
Where are the above stated PowerShell cmdlets run? Online or on the CCE itself?
Don’t use Topology Builder where?
Slide Objective: Introduce Min Topology approach
Speaker Notes
Most notable:
Integration with on-prem PBX (problem with Cloud PBX with Cloud PSTN)
RGS and Call Park Service
Not sure why Number porting is shown the way it is
Analog Devices
Common area phones
What is VIS in second column?
Partner Appliance = CloudBond
Cloud Connected Appliance = M800 CCE
From Technet: https://technet.microsoft.com/en-us/library/mt612869.aspx