integrating microsoft surface hub with legacy videoconferencing and ucc

Thank you to our equipment sponsor:

IS13 - Integrating Microsoft Surface Hub With Legacy

Videoconferencing and UCCMarius Nilsen - Pexip

Copyright 2016 by InfoComm International®

Marius NilsenMarius is responsible for product and architecture at Pexip.

He has more than a decade of experience with IP-based video

and voice infrastructure, including videoconferencing and

Microsoft Lync & Skype for Business.

With a technical background from Tandberg, Cisco and now

Pexip, he is well aware of the challenges most users are facing.

He has a burning interest in solving infrastructure challenges,

whether it is on-premise or in the cloud.

Marius represents the Office of the CTO

Twitter: @manilsenEmail/SfB/VC: [email protected]


A bit of background


71% of millennial employees show preference for video over audio conferences

Sources: PwC, NextGen Global Generation Study; American Community Survey, UC Census Bureau by globalworkplaceanalytics.com

71%

55% of managers have seen increased demand for videoconferencing

55%

More than 60% of collaboration is done with employees and partners outside the office

60%

Employees in Fortune 1000 companies are not at their desk 50-60% of their time

50-60%

The way we work, and our attitude is changing


1500%

200%

By 2019, WebRTC will be utilized for 15% of enterprise voice and video communication, up from less than 1% today.

Between 2015 and 2019, the rate at which organizations will deploy cloud telephony will nearly double, from about 10% to almost 20%.

300%By 2020, over 90% of enterprise voice calls in the digital workplace will originate from collaboration applications, up from less than 30% today.

By 2019, group videoconferencing usage volumes enterprise-wide will increase 400% over current levels, driven by commodity endpoints and cloud-based services.

400%

Source: Predicts 2016: UCC Will Thrive With Web Standards, Commodity and Cloud, Gartner Group

What Gartner Thinks

There is an explosion in video usage happening, but it is not driven by traditional video conferencing....


Market status – well known fact

Video is for most not yet a company wide

collaboration capability – as little as 5% of all meeting rooms are video equipped –


Why is video not heavily used within the greater user community?

Video is perceived to be complex

Difficult to connect and schedule

Always checking to ensure you see the

content, can you hear me

Shadow IT – users bring in their own

collaboration software

Interoperability headache

Cables are mess/unplugged so

it won’t work


Agenda

The two worlds– Surface Hub

– VC

Integration architecture

Where to host capacity

Meeting formats

Scheduling and joining

User experience


What is a Surface Hub

• 55" (1080p) or 84" (4K)• Win 10 w/Universal Apps• Whiteboard "on steroids"

with PPI HW + OneNote• Miracast for wireless sharing• Skype meeting client• Dual fixed cameras with

automatic switching


What is a Surface Hub not

• PTZ video conference system• Equal video + content focus• H323/SIP compatible• Designed primarily for pure

video conferencing calls


Hub relation to AD/Exch

• Domain joined in AD• Exchange calendar connected

to room resource account• Skype for Business meetings• Secure mgmt and upgrade


Topology for Surface Hub on-prem

SfB Edge SfB FEP & AV-MCU

Surface Hub / SRS

SfB clients

SfB mobile

DMZ LANExternal and B2B federation

PSTN

SfB external/web/guest

Exchange


Topology for Surface Hub in Office 365Optional: Azure Express Route

PSTN



Surface Hub / SRS

SfB clients

SfB mobile


Signaling and media flow – P2P calls

Skype AV-MCUOn-prem or 365

Surface Hub / SRS

SfB clients

H264SVC video+ RDP content

p2p media flow


Signaling and media flow – Conferences

Skype AV-MCUOn-prem or 365

Surface Hub / SRS

SfB clients

H264SVC video + RDP content

Media flow via AV-MCU


Typical Skype dialing patterns

[email protected] (SIP URI)

[email protected] (SIP URI)

https://meet.company.com/alice/AB12CD34– Click to join, redirects to conference URI, i.e.

[email protected];gruu;opaque=app:conf:focus:id:AB12CD34


What is a VC system

• H323 or SIP• Sharing via H239 or BFCP• Pan/tilt/zoom camera to

capture everyone or a few• Standalone i.e. public IP or

using VC infrastructure• Dialed by IP-address, E164,

alias or URI


Various VC configurations for H323/SIP

Enterprise

VC endpointon Public IP

Enterprise

VC endpointbehind NAT

Enterprise

VC endpoint on VC infrastructure

DMZ Enterprise

VC endpoint on cloud infrastructure

VC cloud provider


Topology for VC on-prem with infrastructure


H323 VC endpoint

SIP VC endpoint

SIP/H323 VC endpointoutside the organization VC Internal

Call controlMCU

VC Edgefirewall traversal


Typical VC dialing patterns

[email protected] (SIP / H323 URI)

[email protected] (SIP / H323 URI)

555123 (H323 E164 alias, or userpart of SIP URI)

198.51.99.200 (H323 IP address for IVR/MCU or endpoint)

oslo.madmen (H323 alias dialing internally on a GK)

[email protected] (SIP/H323 to alias @ GK)

198.51.99.200##55123 (H323 alias @ GK)


Agenda


– VC



Meeting formats


User experience


Integration architecture – Hub with PSTN

Audio– Preferred by using SfB Conferences and Mediation server

– Available both for Office 365 and On-prem

SfB FEP & AV-MCU

Surface Hub / SRS

PSTN

Surface Hub / SRS

PSTN


Integration architecture – Hub with Video

Virtual Meeting Rooms– Hosted on the VC platform, compatible with Skype for Business

Gateway P2P– Dial directly between systems using different standards

Gateway AV-MCU / Skype Conference– Bring video room systems into Skype conference

Optimal Surface Hub workflow


H.323

Voice& Apps

SIP

Jabber

Web

RTMP Streaming

Virtual meeting rooms

Lync/SfB

Surface Hub

• Traditional video MCU flow• Easy to dial in from all

types of clients/endpoints• Requires Surface Hub to

manually do a P2P call• Can be protected by PIN• Complexity for Hub w/PIN• On-prem or cloud provided• Not intended Hub workflow

Video MCU


H.323 and SIP

Gateway P2P

Surface Hub

• H323/SIP to MS-SIP translation for signaling

• H264/H263 to H264SVC translation for video

• Converting H239/BFCP content to RDP content

• Transparent for the end user, same as Hub to Skype/Lync

• Dialed URI must route to GW

VC to SkypeGateway

Signaling: MS-SIPVideo: H264SVCContent: RDP

Signaling: H323 or SIPVideo: H264/H263Content: H239/BFCP


Gateway AV-MCU / Skype Conference

SfB FEP & AV-MCU

AV-MCU compatible VC to Skypegateway

• Multistream AV-MCU GW• Hub connects to AV-MCU• VC endpoint connects as

participant to AV-MCU via GW

• GW mixes streams to a mixed layout for VC endpoint

• Optimal workflow for hub w/click to join via Exchange/ Skype meeting invitation

• A bit more clunky from VC

H.323 and SIP

SfB clients

Surface Hub

H.323 and SIP


Example on-prem topology for integration

SfB Edge SfB FEP & AV-MCU

VC Edgefw traversal

VC InternalCall controlMCU

Surface Hub / SRS

SfB clients

SfB mobile


H323 VC endpoint

SIP VC endpoint

PSTN

SIP/H323 VC endpoint



Example Office 365 topology for integration

GW/MCU in DMZ

Optional: Azure Express Route

PSTN

SfB external/web/guestSurface Hub / SRS

SfB clients

SfB mobile

H323 VC endpoint

SIP VC endpoint

SIP/H323 VC endpoint



Agenda


– VC



Meeting formats


User experience


Where to host the capacity

Transcoding video streams requires "CPU" capacity

The big question is very often:– On-prem

• How much capacity do you need?

– Cloud

• What flavor of cloud?

– Or a combination

• Is that even possible?


Where to host the capacity

On-prem – deployed on internal servers– VMware/HyperV/Xen/KVM

On-prem installation deployed purely on IaaS– Azure/Amazon

Hybrid Cloud– A combination of the above

Private cloud– Dedicated at external provider

Public cloud– Shared at external provider


Enterprise

Dedicated on-premOn internal servers (VMware/HyperV/Xen/KVM)

All media transcoding handled on the enterprise MPLS network

Allows for regional deployment on customer regional data centers

Best quality, managed by enterprise or outsourced mgmt

Optimal for security and flexibility

Some vendors support integration with Skype Conferences on AV-MCU


Surface Hub

VC/Skype GatewayOn prem


Enterprise

Dedicated installationPurely on IaaS cloud (i.e. Azure/Amazon)

Media not on local network, requires good connectivity to IaaS provider

• Azure Express Route

• AWS Direct Connect

Allows for regional deployment on IaaS provider regional data centers

Same as on-prem for security/flexibility and Skype Conferences on AV-MCU

Potentially high cost with dedicated capacity VMs always on + bandwidth


Surface Hub

IaaS provider

VC/Skype Gateway

VP

N


Enterprise

Dedicated installationHybrid Cloud – combo of onprem and IaaS

On-prem capacity for everyday use (i.e. Vmware/HyperV/Xen/KVM)

Burst to IaaS providers when needed (i.e. Azure/Amazon)

Optimal media path for most calls

Efficient cost spending, and risk reduction with overflow to cloud


Surface Hub

IaaS provider

VC/Skype Gateway

VP

N

VC/Skype GatewayOn prem


Enterprise

Private cloud

Media handled at provider or on enterprise network (assuming network interconnect)

Good for security and flexibility

Shared management and possibly transcoding, with some dedicated capacity

Can allow for Skype Conferences on AV-MCU with dedicated integreations


Surface Hub

Private Cloud provider

Curstomerdedicated

VP

N

SP Shared capacity


Enterprise

Public cloud

Shared resources, often at a lower cost, typically VMRs

Less flexibility, normally no or limited gateway offering

URI addressing often uses cloud providers domain name


Surface Hub

Public Cloud provider

SP Shared capacity


Agenda


– VC



Meeting formats


User experience


Meeting formats: VMR, GW and AV-MCUWhat does it mean for the Surface Hub?

Virtual Meeting Rooms– Surface Hub must dial in to VC bridge

Gateway P2P– Dial directly from Hub to video room system

– or to Legacy VC MCU via Interop GW (not recommended)

Gateway AV-MCU / Skype Conference– The native and recommended experience

for a Surface Hub to operate


Virtual Meeting Rooms with Surface Hub

Web

Video MCU

Surface Hub

H.323

Dial in to VMR from Hub Same as P2P from Hub to Skype / Lync PIN entry

– No DTMF option (not intended use case)– Embed PIN into dial string if supported

Hub can share whiteboard as RDP to VMR Video show default small User can choose full screen Manual switch if content is

received from VMR This is not the intended

use case for the Surface Hub

SIP


Gateway P2P with Surface Hub

VC to Skype Gateway

Surface Hub

H.323 Dial VC endpoint from HUB via GW

Can dial to VC MCU via GW (not recommended)

Same as P2P from Hub to Skype / Lync

Hub can share whiteboard as RDP

Video show default small

– User can choose full screen video

– Manual switch if content is received from VMR

Put VC rooms in Exchange – msRTCSIP-PrimaryUserAddress


Gateway AV-MCU / Skype Conference

Easy to schedule

Hub clicks to join on home screen

Hub can share whiteboard as RDP

VC systems can join via gateway

Gateway should support AV-MCU, RDP and Office 365

Surface Hub has data about participants, to send drawings etc

Shows two VC streams on side or side by side in full screen mode

SfB FEP & AV-MCU

AV-MCU compatible VC to Skype gateway

H.323 and SIP

Surface Hub


Skype and VC integration scenarios

H.323

Voice& Apps

SIP

Jabber

Web

RTMP Streaming

Lync/SfB

Surface Hub

Video MCU

H.323, SIP Video

Gateway to AVMCU: bring any VC endpoint into Skype meetings

Skype/Lync AV-MCUVideo GW Surface Hub

Any endpoint to any endpoint gateway

Video GWSurface Hub H.323, SIP Video

Legacy MCU

Gateway to legacy MCU

Video GWSurface Hub H.323, SIP Video


Agenda


– VC



Meeting formats


User experience


Scheduling of video and Hub meetings

VC centric meetings scheduled in many ways– Some times via VC vendor plugins or 3rd party schedulers

– Simply providing a VMR or endpoint address in mail/calendar

– Requires Skype and Surface Hubs to manually dial

Skype for Business meetings are scheduled in Outlook– Outlook for Windows/Mac/mobile or web

– Skype meetings is the optimal flow for Surface Hub

– Assumes Surface Hub is invited to meeting


Scheduling a Skype meeting in Outlook


How can VC endpoints join Skype meetings?

Depending on vendor support and SfB on-prem vs 365

Dial out from Skype meeting– Drag-and-drop VC room from Skype buddy list

– Add participant in the Hub interface after joining meeting

Dial in to Skype meeting– Dial VC-Skype-GW IVR and enter Conference ID

– Dial Conference ID directly – or add @domain.com

– Click to join via scheduler that reads EWS and automatically connects or prompts on endpoint


Drag-and-drop VC room from Skype buddy list

VC room should be in Skype buddy list (via Exchange)– msRTCSIP-PrimaryUserAddress

Search for it, and add to meeting

Must be invited by a host


Add participant in the Hub interface after joining meeting

VC room should be in Exchange directory– msRTCSIP-PrimaryUserAddress

Search for it, and add to meeting


Dial VC-Skype-GW IVR and enter Conference ID

Normally requires Skype or Lync to be installed on-prem so VC-Skype-GW can look up Conf ID (numeric) and get full URI of the conference– Resolving from: 29905

– To: [email protected];gruu;opaque=app:conf:focus:id:BP8GAN12

User dials IP/URI of IVR

Use DTMF to enterConference ID

Connecting to meeting

29905


Dial VC-Skype-GW with Conference ID directly

Normally requires Skype or Lync to be installed on-prem so VC-Skype-GW can look up Conf ID (numeric) and get full URI of the conference– Resolving from: 29905

– To: [email protected];gruu;opaque=app:conf:focus:id:BP8GAN12

User dials Conference IDassuming dial plan allows

Or ie. [email protected]

Dial direct/prefix/domain:• Direct: 29905• With prefix: 5529905 • Domain: [email protected]

29905

Call Cancel


Booking serverBook SfB meeting

include Room1

Read Room1 Exchange mailbox

Message sent to endpoint

On click: Endpoint Dials SfB meeting via Gateway

Exchange

Room1

1

2

3

4

SfB AV-MCU


Click to join


Summary on joining Skype Conferences (AV-MCU)

H323/SIP video endpointdialling in via IVR or direct

SfB FEP & AV-MCU

Surface Hub / SRS

SfB clients

SfB mobile

H323/SIP video endpointvia drag-and-drop



Agenda


– VC



Meeting formats

Scheduling

User experience


Thank you!

Questions or comments:

[email protected]

integrating microsoft surface hub with legacy videoconferencing and ucc

Technology