AudioCodes’ solution for
Microsoft
Ran Inbar CTO Unified Communication
April 2019
Sponsored by:
Agenda
AudioCodes One The Journey to Azure Management
Voice offering Teams
The Future Partner Experience
Deployment Types
•
•
•
O365
SP Cloud
Online Hybrid SP Private Cloud On premises
Delivering Voice Innovation for Microsoft UC for Over 10 Years
Voice Apps CloudBond 365
SBA OVOC Direct Routing
(IVR/AA, SPS, FAX Ser) UMP 365
Gateways SBCs Call Recording IP Phones OVR CCE Teams Devices
2006 2007 2009 2011 2012 2015 2018
Exchange & LCS OCS 2007 Lync Server 2010 Lync Server 2013 Teams
OCS 2007 R2 Skype for Business
Based on the most comprehensive product suite
OVOC
Management
Routing EMS SEM IP Phone User Management Pack Call Fax
& Apps Manager Manager 365 Recording Server
All-in-One and
Cloud Appliances CloudBond 365 CloudBond 365 CCE and OPCH
IP Phones
HRS 450 445 440 430 420 405
Hardware
Software SBC Mediant 2600 Mediant 4000 Mediant 9000 Mediant Virtual Edition & Software Edition
Hybrid SBC/
Gateway/SBA Mediant 800 Mediant 1000 Mediant 3000
Gateways/Adaptors
MP124/1xx MP2xx MP1288
Number of Verified AudioCodes’ SBCs deployed with Teams
Teams Direct Routing SBC – Deployed with live calls
1839
Teams Direct Routing SBC per SBC type
SBC in Direct Routing
NGC
Resource Forest User Forest CS PSTN Hub
Event Hub
TCDR
CC VR
PSTN Selector CQD
FE ACMS
FE PSTN CA
LGW
Mediation .live. Mediation Controller
MC Health DB
Geneva
Edge
MP SIP proxy
MPLS OTT OTT
BW NGC
Colt Media
SIP
Tata CCE/OPCH
SBC
Microsoft Teams PSTN connectivity using Direct Routing
What is Direct Routing?
A capability of Phone System to connect Microsoft Teams to PSTN or 3rd party on-prem
infrastructure
Session Border Controller
Analog telephony
adapter (ATA) Third-party PBX
(supported by certified SBC
Partners)
Connect to local PSTN trunk Interoperability with third-party systems
For countries where Microsoft Calling plans are not available Mix two systems (for example, provide the option to connect analog
devices), legacy PBX / IP PBX
Customers that want to keep existing telco contract
Global view of cloud topology
North America
CC
PSTN HUB
MC
MP
Azure SIP proxy
Europe Asia
CC CC
PSTN HUB PSTN HUB
MC MC
MP MP
Azure SIP proxy Azure SIP proxy
Service Provider Teams SBC Deployment Options
Shared SBC for all Customers Private Dedicated SBC per Customer
Dedicated DR SBC
Office 365/Teams Multi-Tenant Per Customer
Teams DR SBC Office 365/Teams
PSTN PSTN
SIP Trunk
Service Service
Provider Core Provider Core
Teams Customers Teams Customers
Enterprise - Multi sites with AudioCodes SBC in Direct Routing
• large SBC Centralized data center
• Centralized SBC for main SIP Trunk connection
• Local Breakout at the branches
• PSTN breakout
• PBX/IPBX connection
MPLS PSTN
PSTN
PSTN
• Routing is done by the center SBC
• Support “ Double Media Bypass” PBX
Branch A Branch B Branch C Branch D
Enterprise - Multi sites with AudioCodes SBC in Direct Routing –
centralized SIP Trunk
PSTN SIP Trunk
MPLS
Branch A Branch B Branch C Branch D
AudioCodes’ SBC on Azure network
Office 365/Teams
Mediant Cloud Edition at a Glance
• Designed for high scalability AudioCodes
and optimal data center Stack
resource utilization Manager
Mediant CE SBC
• Microservices SBC - separated SIP
signaling and media processing Signaling Signaling
• Elastic media cluster (managed
by the Stack Manager)
RTP Media Media Media
• Full SBC functionality
• Single management point
• Built-in HA
Mediant CE on Azure – Architecture
AudioCodes products offering from
Azure MarketPlace
AudioCodes’ Products available from Azure MarketPlace
Products Publishing planning
• One Voice Operation Center (OVOC) – April 2019
• AudioCodes Routing Manager (ARM) – May 2019
• Mediant Cloud Edition (MCE) - May 2019
Analog Device in Teams deployment
Analog Gateway options
1. The ATA register to the local SBC
2. The ATA is register to the center SBC
3. The ATA register to Teams HUB
4. The local GW has analog ports
MPLS PSTN
PSTN
PSTN
PBX
Branch A Branch B Branch C Branch D
AudioCodes SBC Direct Routing
Media Optimization
Multi sites with AudioCodes SBC – Media optimized
challenge
• In a distributed topology , the requirement is
to keep the media local in the remote branch
• If the user is external to the company – the SBC
will expose the external interface
• When the user is mobile ( in another branch )
the media to the local SBC/GW will be based
on the connection between the sites
MPLS Signaling PSTN
PSTN
PSTN
PBX
Branch A Branch B Branch C Branch D
Teams Direct Routing SBC with Media Optimization
•• Central
Central SBC
Central SBC
SBC
•••Each
No breakouthas
Each Branch
Branch at aathe
has local
local GW/SBC
GW/SBC
branches
•• User
User is Internal
•User isisInternal
External
internal
•• User
User located
located not
not
ininto
hisin his
inthe “Home”
his Central
“Home”“Home”
•Media
User
branch will
located go a remote
branch
SBC
branch
•• Call external interface
Call be
be routed
routed to to the
the user
local home
user home
breakout
breakout
•• Media
Media will
will go
stayvia
go the central
between
local SBC (
branches,
the connection
directly between sites is
to the GW/SBC
not good)
Management
OVOC in Teams
▪ In Teams the media from MSFT clients is traversing via SBC directly
▪ AudioCodes’ SBC reports the calls media quality trends to OVOC
▪ OVOC quality monitoring in Teams provides End to End quality
monitoring
▪ OVOC will support Teams REST API for full quality monitoring for
internal Teams calls
ARM in Teams
• Teams routing is basic, static and cumbersome
• ARM completes Teams with additional functionalities
• Centralized Routing Management for all network voice devices
• Dynamic quality based routing
• Least cost routing
• Network Load Balancing
• Network Planning
• Call simulation using test route
• Network wide number normalization
• Call screening
• Users policy enforcement
• …
AudioCodes Routing Manager and AudioCodes SBC Direct
Routing
• GW/SBC at the remote branches
• Centralizes enterprise-wide session routing
manager
• Centralized & optimized PSTN routing
• Smart manipulation of dial plans
PSTN
PSTN
MPLS PSTN
• Advanced routing based on user attributes
• Routing per destination
• And more PBX
Branch A Branch B Branch C Branch D
User Management Pack™ 365
User Management Pack™ 365 Advantage
Reduce OpEx Enhanced Security Enhanced Simplicity
$
Alleviates the need for Microsoft Enhanced Security by Revoke User Bring simplicity to the life cycle
experts or PowerShell Ninjas certificate and (Re)Set User Pin management with few quick clicks
Smooth Migration Consolidates WEB Portal Increased Efficiency
Assured E2E Migration process to Unified Platform for all topologies Simple to use web-portal user
Microsoft teams and Skype for and MSFT Policies interface with Realtime MACDs for
Business User Management (Future extend beyond UC ) All User Environments
Simplicity is the Key to Success
Full Migration wizard for Microsoft Teams Calling
Teams Direct Routing SBC pairing
Voice Routes
Users Lifecycle management
Meet the expert and see the Demo
David Edri – Microsoft solutions Product Manager
Almost everything is possible
New Options
AudioCodes Paging System for Teams BoT
PSTN
Zone Text/Anno
Zone 1 Bla Bla 1
Zone 2 Yada Yada
Zone 3
All
Announcement
Zone 1 Zone 2 Zone 3
Connecting AudioCodes SBC to Microsoft Flow
Quick Connect Interview Page
Quick Connect
O365
User Name: FQDN Name:
Create user with SP suffix (optional):
Password: SIP Signaling Port:
User Name:
Tenant Name: Number Pattern:
SBC
Proxy Name: IP Group Name: SIP Group Name: FQDN Name
SIP interfaces Name: Proxy Set ID: SBC Dial Plan Name:
Proxy Address: Local Host Name: FQDN Name Tags Name:
Routing Method Customer DID Range Update from CSV:
Name: 2nd Prefix:
Prefix: Name:
Tag: Tags Name Prefix:
Process Pairing
OVOC Screen
Compliance Recording
SmartTap BoT
Relay
CC
Storage blob PSTN HUB
Voice routes
Voice policies
MC SBC trunk configuration
Call detail records
MP
Monitoring
Troubleshooting
HTTP REST signaling
sRTP media SIP proxy
SIP signaling
Azure
Configuration
Telemetry Customer SBC
Microsoft voice developments continuously push us to change our
Skype for Business and Microsoft Teams portfolio
#1
In SfB hosting in NL Voice in Office 365
• Phone System
Evolving business
model
#2 telco in NL • Calling Plans
• Direct Routing
Voice is commoditizing
Vodafone Private
Cloud
• Skype for Embrace shift to Office 365 via
Business Server introducing Professional Services
and leveraging scalability via
On customer Microsoft Partner ecosystem
location
• Skype for
Business Server
C1 - Public
With Direct Routing, Vodafone extends Microsoft Teams with Voice
services in a cloud solution
Vodafone Calling in Office 365 for Microsoft Teams
• Vodafone connects telephony service with Office • Standardized solution, build on multi-tenant virtual
365 Phone System via Direct Routing SBC’s from Audiocodes
• Every user gets a fixed phonenumber connected to • Private infrastructure when integration is required
Teams with existing PBX, analogue devices or QoS
C1 - Public
Our Direct Routing proposition focuses on increasing volumes and
added value of voice services
Increase volume business by onboarding new channels and focus
01 on more segments
• Leveraging scalability advantages of Direct Routing infrastructure
• Target SMB in addition to Enterprise segment
• Sell both directly and via Microsoft IT partner ecosystem
Increase added value of Voice services
02 • Ensure legacy technology is not in the way of Teams adoption by enabling
integration on a private vSBC (i.e. existing PBX or analogue devices)
• Differentiate with offering self-service capabilities
• Connect international locations with existing local SIP contracts
• Always accessible in case of Cloud/ WAN disruptions
• Support advanced calling capability requirements via integration with
A365 contact center
C1 - Public
Thank You
Sponsored by:
