9. Directly Route dial tone to Teams Users
Direct Routing allows customers to connect their phone
trunks directly to Office 365. Customers can work with their
local Telecommunications providers to enable Microsoft Teams
users to make and receive telephone calls.
PSTN
Provider
Phone System
Voice Trunk
Internet
3rd Party Voice Apps
(supported by certified SBC Partners)
Phone #
Ranges
Certified Session Border
Controller(s)
Interoperability with 3rd party systems
Direct Routing allows customers with users in the
Microsoft cloud to continue using 3rd party systems
such as PBXs, Call Center, and Analog Telephony
Adaptors (ATA) helping preserve key investments.
Office 365 & Teams
13. Self deployed SBC Partner hosted SBC
Benefits • Full control over SBC
• Connectivity to existing PBX
• No need for purchasing, maintaining and
hosting own SBC
Disadvantages • Customer responsible for SBC
configuration
• Need to purchase, maintain and host SBC
• No control over SBC configuration
• Support model more complex
29. Meet better with Microsoft Teams Meetings
Intelligent Meetings
Be more engaged & productive
Quickly join meetings
Share Content from desktop or mobile
Bring your meeting to life w/ F2F video
Microsoft
Graph
Cortana
Organize, Prepare & follow up
Organize your day
Collaborate before the meeting
Meet now or later
Meet confidently – just works!
Great quality & reliability
Desktop, mobile. Phone or rooms
Invite external users to join via web
40. Meeting Lifecycle
During Meeting
F/F video – follow the action
Share content
Record the Meeting w/ transcription
Join from a Skype room easily
Pre Meeting
Contextual conversations in Teams
Prepare and discuss content
Schedule Meetings
Post Meeting
Playback a meeting w/ transcription
Share notes
Post meeting chat & collaboration
43. Edge Chrome
Audio
Video planned
View
screensharing
Active
screenshare
planned planned
50. Microsoft Teams
Cisco/Polycom
VTC system
Pexip is architected as a enterprise cloud application for
customers that requires an authenticted experience and a setup
adjusted to ther existing brand/domain and infrastructure.
51. VTC Rooms VTC Call Control VTC Management
VTC Bridging MCUVTC FW Traversal
Teams client
Microsoft Teams
?
Pexip Self Hosted vs Pexip as a Service
Customer/partner tenant
VTC Rooms VTC Call Control VTC Management
VTC Bridging MCUVTC FW Traversal
Pexip tenant
Self Hosted: For complex deployments As a Service: Turnkey
52. Feature Pexip Self Hosted Pexip as a Service
Installation/topology
Deploy Virtual Machines Yes N/A
Install & Configure Pexip (VMware or Azure) Yes N/A
Integrate with existing VTC call control Yes (or decomission) N/A
Install & Configure Pexip Teams Connector Yes N/A
Choice of Azure regions Customer Pexip
Azure subscription owner Customer Pexip
SLA Customer Pexip
Deployment type Dedicated Shared
Configuration/Features
Customer specific DNS SIP domain Yes Yes
VTC endpoint registration and P2P calling Yes Yes
Lobby bypass for customer owned VTCs Yes Yes
Lobby bypass with customer VTC call control Yes No
SfB and Guest WebRTC dialin to Teams Meetings Yes No
VTC to SfB Meetings during migration period to Teams Yes Yes (customers own VTCs, not guests)
Customer specific branding/splash screens Yes No (at launch time)
Pexip Self Hosted vs Pexip as a Service
54. Environment
• Acoustical noise
• Visual noise
Device
• Device for capturing
audio and video
• Device for playing back
audio
Network
• Connectivity to Office
365 network
• Quality of the network
• Available bandwidth