cisco interoperability with microsoftd2zmdbbm9feqrf.cloudfront.net/2016/usa/pdf/brkcol-2611.pdf ·...

Cisco Interoperability with MicrosoftPart 2 - Video Interoperability

Fabio Chiesa – Consulting System [email protected]

BRKCOL-2611

© 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public

Cisco Interoperability with MicrosoftPart 2 - Video Interoperability

Disclaimer

The Cisco products, service or features identified in this document may not yetbe available or may not be available in all areas and may be subject to changewithout notice. Consult your local Cisco business contact for information on theproducts or services available in your area.

You can find additional information via Cisco’s World Wide Web server athttp://www.cisco.com. Actual performance and environmental costs of Ciscoproducts will vary depending on individual customer configurations andconditions.

BRKCOL-2611 3


Cisco is fully committed to Interoperability with Microsoft

BRKCOL-2611 4


+What does the Acano acquisition mean for Cisco?

• Cisco + Acano provides best in industry interoperability with Microsoft Lync/Skype for Business.

• Compliments Cisco’s focus on a flexible and scalable collaboration architecture.

• Underscores Cisco’s position of leadership in the industry.

BRKCOL-2611 5

• Microsoft UC Solutions – Quick Overview (Video Focus)

• Video Interoperability using Cisco Expressway / VCS

• Video Interoperability using the Acano (CMS) Solution

• Lync & Jabber Interoperability (multiple workload)

• Video Interoperability using Webex CMR Cloud

• Summary

Agenda

Note: for anything else refer to

BRKCOL-2610 (Cisco Interoperability with Microsoft, Part 1 – Collaboration)

Microsoft Lync 2010 / 2013 & S4B overview (Video Focus)


Video interoperability with Lync 2010• Point to Point video call:

• Uses the RTVideo codec as default

• The only codec supported for interoperability with standard VC is H263 (CIF@15fps)

• Microsoft RDP utilized for Desktop Sharing

• Multipoint video call using Internal A/V MCU:

• Support only the RTVideo codec

• Support CIF and VGA as resolutions (No HD)

• Support only Voice Activated Switching (no Continuous Presence)

• Utilize Microsoft CCCP as proprietary protocol to manage the multipoint sessions

BRKCOL-2611 8


Video interoperability with Lync 2013

Microsoft/Polycom H.264 UC SVC (UCIF) and RTVideo supported as Video Codec

Support for H.263 discontinued

Microsoft RDP utilized for Desktop Sharing

Microsoft CCCP as proprietary protocol to manage the multipoint sessions using

the internal A/V MCU

Only one continuous presence layout available, called “Gallery View” (max 5

users with video)

BRKCOL-2611 9


Video interoperability with Skype for Business (S4B) Server

Microsoft/Polycom H.264 UC SVC (UCIF) and RTVideo supported as Video Codec

Still use Microsoft CCCP as proprietary protocol to manage the multipoint sessions using the A/V MCU

Still only one continuous presence layout available, called “Gallery View” (5 users max with video)

Desktop Sharing

– Still utilize Microsoft RDP for most of the use case

– New VBSS High Quality capability (only with S4B 2016 clients, no standard BFCP based)

New Server role for Video Interoperability (VIS)

– Provide some kind of “Gateway” function toward S4B

– Multiple Caveats (one way only, no BFCP/RDP, CUCM only, limited scalability, etc..) (*)

(*) https://technet.microsoft.com/en-us/library/dn933920.aspx

BRKCOL-2611 10

https://technet.microsoft.com/en-us/library/dn933920.aspx

https://technet.microsoft.com/en-us/library/dn933920.aspx


if ( (SIP URI) match one of Lync User) then route locally

elseif ( (SIP URI) and (destination == remote domain) ) /* SIP Trunk Routing

I can ONLY call

a SIP URI…

Video Gateway

Call Routing with Lync 2010/2013/SFB ServerUser Enabled for P2P calls only (no Enterprise Voice, AKA “Plus CAL”)

Only one possible

routing behavior for

Lync outgoing calls.

BRKCOL-2611 11


• Reference: Federation and Public IM Connectivity (Microsoft Technet)

• Only other S4B, Lync and OCS systems are officially supported from Microsoft

• The only way to interoperate is appearing to O365 as another Lync/S4B on-prem system

Video Interoperability with SFB Online (O365)What about B2B «Federation» ?

BRKCOL-2611 12

https://technet.microsoft.com/en-us/library/skype-for-business-online-federation-and-public-im-conectivity.aspx

Interoperability using Expressway/VCS as a Gateway


Few notes before proceeding...

• CUCM is always represented in the diagrams, but the same

architecture is valid also for VCS as Call Control.

• Expressway is always mentioned here as Gateway, but VCS is also a

valid option (see next slide)

• Lync 2013 Server is always represented in the diagram, but the same

architecture is valid also for Lync 2010 and Skype for Business 2015

Server.

BRKCOL-2611 14


Video Interoperability – High Level Architecture

CUCM

9.X/10.X/11.X

B2BUA

H264 AVC <-> H264UC-SVC

Gateway

Expressway X8.8

(Lync Gateway)Lync Server

2013

• Supported Microsoft Environment:

• Skype for Business Server 2015 (H264UC-SVC – 720p@30fps)

• Lync Server 2013 (H264UC-SVC - 720p@30fps)

• Lync Server 2010 (H263 - CIF@15fps)

• CUCM and VCS supported as Call Control

• Cisco and 3rd party endpoint supported (registered to VCS)

• End to End Encryption for media and signaling

• Lync Client Remote Access through Edge supported

DX80

MX300

SIPMicrosoft SIP

BRKCOL-2611 15

Point to Point calls use case


Call Routing – How it works for P2P calls

CUCMExpressway

Lync Gateway

[email protected]

Lync

Server

MX700*@company.lab

*@video.company.lab

[email protected]

TX9000

Media always flows through the Expressway Lync Gateway

Different domains used here to simplify, but same domain is

also supported

Caller Identity delivery is crucial to provide the best User

Experience (Ex. callback & caller lookup capabilities)

B2BUA

SIP

Media H264 AVC

Microsoft SIP

Media H264 UC-SVC

MX300

BRKCOL-2611 17


Calling Video Devices from the Lync Clients

• For each shared Video Device a contact can be created in AD, mapping the AD attribute <msRTCSIP-PrimaryUserAddress>

to the endpoint’s Sip URI

• Lync/SFB users will be able to search Video Endpoint, add them to the buddy list and call them when needed

Note: Endpoint’s status (Presence) available today only with VCS as Call Control

BRKCOL-2611 18


Calling Lync Users from the Video Devices

• It is possible to call a Lync/SFB User after searching him/her in the CUCM Directory

• CUCM’s “Directory URI” field must be populated with the Lync/S4B Client’s SIP address

• VCS can leverage TMS Phone Book integration with AD to synchronize the same info

1

2

3

BRKCOL-2611 19

Multipoint calls use case


CUCM

SIP

Media H264 AVC

Expressway

Lync Gateway

Microsoft SIP

Media H264 UC-SVCLync

Server

Call Routing – How it works for calls to TelePresence Server

TelePresence

Conductor

TelePresence

Server

No special/additional configuration needed for Lync interop

TelePresence Server manages only standard H264 AVC stream

(thanks to Expressway Lync Gateway)

TMS

B2BUA

[email protected]

*@video.company.lab

BRKCOL-2611 21


Lync and CMR Interoperability – Layout Comparison

Equal (up to 16 PIP)

Cisco CMR Layouts

(Video Focus)

Lync A/V MCU Layouts

(Video Focus)

4 Layout available (only two with video):

• Gallery View - shows all of the participants’ videos (up to 5 max)

• Speaker View - shows only the presenter’ video

• Content View - shows only the meeting content (no video)

• Compact View - shows the tiles of the participants in a compact window

(only picture, no video)

Overlay

(up to 6 PIP)

Prominent

Single

Screen

BRKCOL-2611 22


Scheduled conference using TMS Smart Scheduler (CMR Premise and CMR Hybrid)

Define here how many

«Video» Devices will join

(Lync is just one of them...)Click here to start

the call

BRKCOL-2611 24


Personal CMR(CMR Premise and CMR Hybrid)

TelePresence User Portal

You have your Personal

CMR Info here

Click here to generate an

email with the Personal

CMR Info

BRKCOL-2611 25


How to add a Personal CMR contact into Lync Address Book:

• For each Personal CMR a contact can be created in AD, mapping the AD attribute <msRTCSIP-PrimaryUserAddress> to the

Room’s Sip URI

• Lync servers will sync the internal Address Book from AD during the night

• Lync users will be able to search for Personal CMR contacts, add them to the buddy list and join the room when needed

• Same concept applies to shared static CMR (“Rendezvous” style)

Personal CMR(CMR Premise and CMR Hybrid)

Note: CMR’s status (Presence) available today only with VCS as Call Control

BRKCOL-2611 26

Extended Architectures


Internet

Expressway

Lync GW

Lync Edge Server

Expressway-EExpressway-CCUCM

Lync Pool

Benefit of a dedicated Expressway Lync Gateway:

• Single point of configuration

• Single point to update for further enhancement / bug fixes

• Scalability Assurance

Best Practice – direct trunk between CUCM and the Expr. Lync Gateway

Why do we need a dedicated Lync Gateway?

BRKCOL-2611 28


Redundancy and Load Balancing

Expressway

Lync Gateway

cluster

CUCM

clusterLync Pool

• On the CUCM to Expressway trunk definition specify multiple entries as Destination Address

• CUCM will statistically load balance the outgoing traffic between the Expressway nodes

HLB or

DNS LB

BRKCOL-2611 29


Redundancy and Load Balancing

Expressway

Lync Gateway

cluster

CUCM

clusterLync Pool

• Specify a single neighbor zone on Expressway with the CUCM nodes listed as peer addresses

• Expressway will use an internal algorithm to Load Balance between the different CUCM nodes

BRKCOL-2611 30


Internet

Expressway

Lync Gateway

Lync Edge Server

Lync Remote Access support - Background

CUCM

Lync Pool

• Lync clients can register to the Lync Pool from Internet, through Lync Edge

• Local Firewalls and Multiple NAT are quite common scenario to deal with

• How will be A/V media streams able to traverse all these obstacles?

BRKCOL-2611 31


Internet

Expressway

Lync Gateway

Lync Edge Server

Expressway-E

Lync Remote Access support – Why do we need TURN?

CUCM

TURN

client

Lync Pool

TURN

Server

• ICE - Interactive Connectivity Establishment (RFC 5245) , TURN and STUN are the answer

• Expr-E provides Standard TURN Service to the Expr. Lync Gateway (TURN client)

• Expr-C (Firewall Traversal chain) is not involved in the signaling and media path

• Multiple media path, depending on ICE negotiation, are possible (see next slides)

SIP

media (Direct)

Microsoft SIP

media (TURN Tunnel)

BRKCOL-2611 32

https://tools.ietf.org/html/rfc5245


Internet

Expressway

Lync Gateway

Lync Edge Server

Expressway-E

Lync Remote Access support - Media Flow negotiation (1/3)

CUCM

Lync Pool

In this case the A/V media is flowing through:

1. Lync client <-> TURN server on the Expressway-E (Direct)

2. TURN Tunnel to the Expr. Lync Gateway (Encapsulated)

3. Expr. Lync Gateway <-> Video Endpoint (Direct)

TURN

client

TURN

Server

SIP

media (Direct)

Microsoft SIP

media (TURN Tunnel)

BRKCOL-2611 33


Internet

Expressway

Lync Gateway

Lync Edge Server

Expressway-E


CUCM

Lync Pool

• In this case A/V media is flowing through:

1. Lync client <-> TURN Server on the Lync Edge (Encapsulated)

2. TURN server on the Expressway-E <-> Expr. Lync Gateway (Direct)


• Expr. Lync Gateway does NOT create/use a TURN Tunnel with the Lync Edge

TURN

Server

SIP

media (Direct)

Microsoft SIP

media (TURN Tunnel)

BRKCOL-2611 34


Internet

Expressway

Lync Gateway

Lync Edge Server

Expressway-E


CUCM

Lync Pool

In this case A/V media is flowing through:

1. Lync client <-> TURN Server on the Lync Edge (Encapsulated)

2. TURN server on the Lync Edge <-> TURN Server on the Expr. Lync Gateway (Direct)

3. TURN tunnel to the Expr. Lync Gateway (Encapsulated)


TURN

client

TURN

Server

TURN

Server

SIP

media (Direct)

Microsoft SIP

media (TURN Tunnel)

BRKCOL-2611 35


Expr. Lync Gateway will act as TURN client and the Expressway-E will act as TURN server

TURN service information must be configured on both Expressway.

A shared username + password must be used to authenticate the TURN connection between

the two Expressway devices.

Specific TCP/UDP connections between Lync Gateway, Expr-E (Turn Server) and Lync Edge

must be allowed through the Firewalls (see the deployment guide for further details)

Lync Remote Access support – Expressway TURN capabilities

BRKCOL-2611 36

Content Sharing Interoperability


Content Encoding MethodsBackground

Content can be shared with a remote party during a SIP call in two ways:

As part of the main video

channel – so the receiver

has no control over layout

and content resolutionContent Channel

Video Channel

SIP / BFCP

Content Channel (BFCP)

Video Channel

SIP / BFCP SIP / BFCP

In a separate channel

(BFCP) – so the receiver

can control the layout and

negotiate different resolution

for the content

SIP only

(NO BFCP)

BRKCOL-2611 38

© 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public 39

Content Encoding MethodsPossible Endpoint Encoding Behaviors (when BFCP is not available)

Composited People + Content in main video channel (1)

• Takes the camera and PC inputs and creates a composite encoding of both sources

• TC endpoints

People or Content in main video channel

Switches between people or content depending on if you’re presenting or not

CTS, TX and DX endpoints

Composited People + Content in main video channel (2)

Takes the camera inputs from the participants and the PC input from the presenting participant and creates a composite encoding of those sources

MCU and TelePresence® Server

BRKCOL-2611

© 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public 40

Cisco & Microsoft Content Sharing interoperabilityArchitecture

• Cisco uses BFCP for Content Sharing

• Microsoft uses RDP for Content Sharing

• Expressway Lync Gateway provides now RDP to BFCP transcoding

• No Expressway Lync Gateway interaction in the other direction (see next slide)

SIPSIP

Lync Pool

SIP

Lync Client

Expressway

Lync GatewayCUCM

SIP

RDP to BFCP transcoding

RDPBFCPMX300G2

BRKCOL-2611


Content Channel

Video Channel

Cisco & Microsoft Content Sharing interoperabilitySupported Capabilities

SIP / BFCP

Content Channel

Video Channel

Lync/S4B

(RDP only)SIP / BFCP

Content Share to Lync

Content Share from Lync

Important note: Simplified diagrams to explain capability only. This is not the detailed architecture.

Lync/S4B

(RDP only)

BRKCOL-2611 41


Cisco & Microsoft Content Sharing interoperabilityAdditional details...

• Supported with Lync 2013 Server and SFB 2015 Server as backend

• Lync/SFB client shares/receives content to/from TPS bridge (multipoint calls)

• Lync/SFB client shares/receives content to/from Standard based SIP/H323 Endpoints in P2P calls (TC endpoints have been tested and validated)

• Content Sharing user experience in P2P calls may vary depending on source endpoint capabilities (i.e. Content in main Vs Local Composition)

• Content Sharing is not working today in P2P calls with Jabber due to a Bug

• Max concurrent content sessions: 20 on large VM and 10 on medium VM depending on desktop size and quality of video call

42BRKCOL-2611

Cisco Meeting Server (Acano)


Chat, talk, meet and share in one place

And more

BRKCOL-2611 44


Our capabilities

Audio conferencing Video conferencing Browser conferencing

Skype for Business

(Lync) integration

Team spaces Apps

BRKCOL-2611 45


UCM Cluster

Immersive

Endpoints

TelePresence

Endpoints

Expressway-C

3rd Party - H.323 /

SIP Endpoints

Architecture with Lync/S4B on Premise

Internal DMZ

Lync FE Lync Edge

Lync/S4B

UsersLync/S4B

Users

Expressway-E

Home/Mobile

Endpoints (MRA)

External

Acano Core Acano Edge

Acano Client

Acano

WebRTC

B2B Endpoints

LEGEND

Standard SIP

MSFT SIP

FW Traversal

Guest (WebRTC)

H.323

XMPP

Acano Client

phone

VCS-C

• Lync/SFB Clients in remote

access through Lync Edge

• Federated Lync/SFB systems

BRKCOL-2611 46


Lync & Skype for Business Integration Types

• Gateway – Allows calling between Room Endpoints and Lync/Skype4B

• Spaces – Room Endpoints and Lync/Skype4B users dial into an Acano Space

• Dual Homed conferencing – Room Endpoints can dial into Lync/SFBMeetings as a full featured participant

• Skype For Business (Office 365) direct federation

Native support:

• H.264UC-SVC (SFB & Lync 2013)

• RTVideo (Lync 2010 & 2011)

• Bi-directional RDP Transcoding for

Content Sharing

• Multi-party conferencing (Microsoft

CCCP protocol support)

• Drag and Drop from Lync/SFB client

• Participant list integration

BRKCOL-2611 47

Integration Type 1 - Gateway


Call Routing – How it works for P2P calls

CUCMAcano Core

(CMS)

[email protected]

Lync

Server

MX700*@company.lab

*@video.company.lab

[email protected]

TX9000

Media always flows through the Acano Core (CMS)

Bi-directional RDP/BFCP Transcoding for Content Sharing

Different SIP domains as best practice to avoid possible loops

SIP

H264 AVC

Microsoft SIP

H264 UC-SVC or RTV

BRKCOL-2611 49

MX200


CUCM

SIP

H264 AVCMicrosoft SIP

H264 UC-SVC or RTVLync

Server

Call Routing – How it works for calls to TelePresence Server

TelePresence

Conductor

TelePresence

Server

Acano Core (CMS) acts only as a Gateway

TelePresence Server is the bridge here with the related capabilities


TMS

[email protected]

*@video.company.lab

Acano Core

(CMS)

BRKCOL-2611 50


CMS as a Gateway to TelePresence Server – User Experience

Lync/Skype

Front EndSKYPE4B

LYNC

Acano Core

(CMS)

Standards Video Systems Lync/SFB Clients

Dial Conference Address

[email protected]

TPS

Conference Host

Dial Conference Address

[email protected]

BRKCOL-2611 51

Integration Type 2 - Spaces

© 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public 53BRKCOL-2611

Introducing Spaces

Spaces

Telepresence

Endpoints

Immersive

Endpoints

Desktop System

Lync/S4B

Users

• Virtual Meeting Room

• All Participants Dial the

space Address

• Users can have multiple

Spaces

• Devices join a space

and get the best

experience

• Video/Audio/Content

• WebRTC accessphone

Jabber

UserGuest Users

via WebRTC

Other Vendor

Endpoints

Acano client

(CMA)


CUCM

Lync

Server

Call Routing – How it works for calls to CMS (joining Spaces)

CMS Enhanced Video Layouts

Bi-directional RDP/BFCP Transcoding for Content

Sharing

Group Chat available also for Lync/SFB clients

Space’s “Presence” published into Lync/SFB clients

TMS

[email protected]

Acano Core

(CMS)

SIP

H264 AVCMicrosoft SIP

H264 UC-SVC or RTV

*@video.company.lab

BRKCOL-2611 54


• For each “Space” an AD contact can be created, mapping the AD attribute <msRTCSIP-PrimaryUserAddress> to the Room’s Sip URI

• Lync servers will sync the internal Address Book from AD during the night

• Lync users will be able to search for “Space” contacts, add them to the buddy list and join the room when needed

• Space’s Presence is updated when the first Endpoint/Client joins

User Experience – Spaces & Buddy List

BRKCOL-2611 55


User Experience – Video Layout

• Same Layout for Sip/H323 Endpoints, Acano Clients, WebRTC and Microsoft clients

• ‘Hollywood Squares’ layouts new with CMS 1.9

BRKCOL-2611 56

Integration Type 3 - Dual Home Conferencing


Dial IVR + Conference IDClick-To-Join

Initiate Dual-Home

Dual Home conferencing – How it works

VIDEO SYSTEMS LYNC SERVER

A/V MCU

LYNC

SKYPE4B

LYNC

Standards Video Systems Lync/SFB Clients

The expected experience is maintained:

• “Gallery View” for Lync/SFB clients

• Video Layouts for anything else

BRKCOL-2611 58

Acano Core

(CMS)


Dual Home Conferencing - User Experience


Group Chat extended to Acano Clients andWebRTC Users

Participant list on the Lync/SFB client alsoincludes Video Endpoints

Host can mute, remove, Spotlight, Pin toGallery, etc.. each individual Video Endpoint

BRKCOL-2611 59


Dual Home conferencing – Scheduling Experience

• For customers with Lync/SFB as their primary meeting tool

• Based on the native Lync/SFB scheduling plugin inside Outlook

• It requires the Dial-In feature activated and configured on the Lync/SFB Pool

• Microsoft A/V MCU gets a critical role!

BRKCOL-2611 60


How to customize the Lync/SFB Outlook Invitation

• Select the Meeting Configuration page under the

Conferencing menu

• Create a custom footer text with the instructions to

join the CMS Space

• [Optional] add an URL pointing to a Graphical Logo

BRKCOL-2611 61


Why Spaces Are Better Than AVMCU

• Multiple and extended Layouts

• Scale

• Geo-Distribution

• Hybrid Transcoding

• TIP support

• Friendlier on bandwidth

• Microsoft A/V MCU and Enterprise CAL not needed

BRKCOL-2611 62

Integration Type 4 – Office 365 Interoperability


UCM Cluster

Immersive

Endpoints

TelePresence

Endpoints

Expressway-C

3rd Party - H.323 /

SIP Endpoints

Architecture with SFB online (Office 365)

DMZ

Lync/S4B

Users

Expressway-E

Home/Mobile

Endpoints (MRA)

External

Acano Core Acano Edge

Acano Client

Acano

WebRTC

B2B Endpoints

LEGEND

Standard SIP

MSFT SIP

FW Traversal

Guest (WebRTC)

H.323

XMPP

Acano Client

phone

VCS-C

Beta Feature

with CMS 1.9

SFB Clients registered to SFB

online (Office 365)

BRKCOL-2611 64


Capabilities available with Office 365

• Point to Point Gateway Calls

• SFB clients can join CMS Spaces (preferred scenario)

• Dual Home Conferences started using Drag and Drop from the SFB clients

• Bi-directional RDP/BFCP Transcoding for Content Sharing

• Note 1 – Scheduled Dual Home Conferences are not possible today

• Note 2 – Currently this is a Beta Feature, official release date still TBD

BRKCOL-2611 65

Lync & Jabber Interoperability (multiple workload)


IM/P and A/V Interoperability with Jabber – Background

CUCM A/V

IM/P Domain:

company.lab

A/V Domain:

video.company.lab

*@video.company.lab *@video.company.lab

Xmpp: [email protected]

Sip: [email protected]


Expressway

Lync Gateway

CUCM IM/P

A/V and IM/P domain:

company.lab

• Target Scenario – Lync/Jabber coexistence / migration

• Lync can’t split the traffic for IM/P and A/V to two destinations for the same «domain»

• Jabber users need therefore two different addresses:• one for IM/P ([email protected])

• one for A/V ([email protected])

• Two different buddy list items are needed on the Lync side for each Jabber user

Lync Pool

A/V Session (signaling)IM Session (signaling)

SIP registration

XMPP registration

MSFT SIP registration

BRKCOL-2611 67


IM/P and A/V Interoperability with Jabber – SIP Broker

CUCM A/V

IM/P Domain:

company.lab

A/V Domain:

company.lab

*@company.lab

Xmpp: [email protected]



Expressway

Lync Gateway

CUCM IM/P

A/V and IM/P domain:

company.lab

Lync Pool*@company.lab

• Jabber users need now only one address for IM/P and A/V

• One single buddy list item is needed on the Lync side for each Jabber user

• It supports only Expressway/VCS as «Media Gateway» today, work in progress to

use also CMS (Acano)

*@company.lab

SIP Broker

A/V Session (signaling)IM Session (signaling)

SIP registration

XMPP registration

MSFT SIP registration

New with

X8.8

BRKCOL-2611 68

Video Interoperability using Webex CMR Cloud


Collaboration Meeting Rooms (CMR) Cloud

One Meeting

Converged video and web conferencing meeting

experience from the WebEx Cloud

Superior Scale

Up to 25 video endpoints & additional 500 video-

enabled WebEx users + 500 audio only WebEx

users (1025 users/meeting)

Join From Anywhere

From the pocket to the boardroom with true platform

independence including SIP, H.323 and Lync/S4B

For further detailsBRKCOL-2612 (Understanding WebEx CMR Cloud)

BRKCOL-2611 70


Lync Edge Server

Expressway-E

CMR Cloud – Lync & SFB Server (on premise) interoperability

Expressway-CCUCM

Lync Pool

Each solution must use his own Firewall Traversal technology to join the CMR Cloud session:

• Microsoft - route to *@lync.webex.com through the Lync Edge (as a Federated domain)

• Cisco - route to *@*.webex.com through the Expressway C/E

Cisco WebEx Cloud

Webex Mobile Client

Webex Desktop Client

*@lync.webex.com

*@*.webex.com

BRKCOL-2611 71


InternetExpressway-EExpressway-CCUCM

• External Federation must be enabled for the customer‘s S4B online environment

• The specific domain “lync.webex.com” must be allowed as a Federated Domain

Cisco WebEx Cloud

Webex Mobile Client


O365 S4B Online

CMR Cloud – SFB Online (Office 365) interoperability

BRKCOL-2611 72

mailto:*@lync.webex.com

Summary


Interoperability Summary - Feature ComparisonExpressway / VCS +

TelePresence Server

Cisco Meeting Server

(Acano)Cloud Webex CMR

Audio/Video H264UC-SVC + H263 H264UC-SVC + RTV H264 UC-SVC + H263

Content SharingAsymmetric Transcoding

(RDP to BFCP)

Bi-Directional RDP

Transcoding

Asymmetric Transcoding

(RDP to BFCP)

Gateway Calls

Personal Meeting Room CMR Spaces CMR

Virtual Room’s Presence

Dual Homing (Scheduled)

Dual Homing (Drag and Drop)

Group Chat

(Lync, SFB, Acano Clients and WebRTC)

B2B with remote Lync/SFB/O365

(using a local On Premise Lync/SFB)Not Applicable

B2B with remote Lync/SFB/O365

(Direct Federation)(Beta Feature with CMS 1.9)

SIP Broker (IM/P + A/V Jabber Interop)

BRKCOL-2611 74


Cisco Video Interoperability with MicrosoftSummary

There are multiple ways to interoperate – choose the one that is right

for your environment

End User experience is crucial for a successful Interoperability project

Cisco is fully committed to Interoperability with Microsoft

BRKCOL-2611 75

Thank you


Call to Action

• Attend the following related sessions

• BRKCOL-2610 (Cisco Interoperability with Microsoft, Part 1 – Collaboration)

• BRKCOL-2612 (Understanding WebEx Collaboration Meeting Room (CMR) Cloud)

• BRKCOL-2803 (Designing and deploying multiparty conferencing for telepresence video)

• Visit the World of Solutions

• Cisco Campus – (Collaboration Area, Microsoft Interoperability corner)

BRKCOL-2611 77


Complete Your Online Session Evaluation

Don’t forget: Cisco Live sessions will be available for viewing on-demand after the event at CiscoLive.com/Online

• Give us your feedback to be entered into a Daily Survey Drawing. A daily winner will receive a $750 Amazon gift card.

• Complete your session surveys through the Cisco Live mobile app or from the Session Catalog on CiscoLive.com/us.

BRKCOL-2611 78

CiscoLive.com/Online

http://ciscolive.com/Online

http://ciscolive.com/Online

http://ciscolive.com/us

http://ciscolive.com/us


Join the Customer Connection Program19,000+

Members

Strong

• Influence product direction

• Access to early adopter & beta trials

• Monthly technical & roadmap briefings

• Connect in private online community

• Exclusive perks at Cisco Live

• Collaboration NDA Roadmap Sessions Mon & Tues

• Q&A Open Forum with Collaboration Product Management Tues 4:00 – 5:30

• Reserved seats at Collaboration Innovation Talk Thurs 8:00am – 9:00am

• 2 new CCP tracks launching at Cisco Live: Security & Enterprise Networks

Join in World of Solutions

Collaboration zone

Join at the Customer Connection stand

New member thank-you gift *

CCP ribbon for access to NDA sessions

Join Online

www.cisco.com/go/ccp

Come to Collaboration zone to get your

ribbon and new member gift

* While supplies last

BRKCOL-2611 79

http://www.cisco.com/go/ccp

Appendix

Interoperability using Expressway/VCS as a Gateway


Video Interoperability - Most Common Use Case scenarios

SX80,MX300,

MX800Lync 2013

Client

Point to Point calls

“Shared Video Endpoint”

Point to Point calls

“Personal Video Endpoint”

Multipoint calls

“Lync Client, Personal and Shared

Video Endpoint in the same call”

Lync 2013

Client

DX80

BRKCOL-2611 83

Expressway Solution«Point to Point calls use case»


The “B2BUA” – What is that ?

Back to Back User Agent (B2BUA) :

Process running only on the “Lync Gateway” Expressway

Translate between Standard based and Lync specific SIP signalling

Media (RTP) always passes through Expressway, also with Lync 2013

The Microsoft Interoperability option key is required to enable this process

BRKCOL-2611 85


Assigning Alpha URIs to a CUCM Endpoint (manually)

• All endpoints still register with a DN (numeric address) as unique identity

• Up to 5 alpha URIs can be associated with any DN

• One alpha URI is marked as primary and is sent together with DN as caller Identity

• Delivering the correct Caller Identity to Lync requires specific configuration on the CUCM (see

slides in appendix for further details)

BRKCOL-2611 86


Assigning Alpha URIs to a CUCM Endpoint (automatically)

• “Directory URI” field can be defined on end-user page

• “Directory URI” field can also be synced from an AD/LDAP directory

• If the Primary extension of the user is set, the Directory URI value is automatically assigned to the DN as Primary URI

• Check the slides in the Appendix for more info

1

2

3

3

BRKCOL-2611 87


Syncing Directory URI from AD

• Enduser Directory URI field can be synced from LDAP directory

• Standard LDAP attributes

• msRTCSIP-primaryuseraddress

• mail

• Syncing Directory URI from LDAP also triggers automatic creation of alpha URI on DN (assuming device association)

BRKCOL-2611 88


Directory URI Partition Alias

• Auto-generated directory URI are in partition “Directory URI”

• “Directory URI” partition is predefined and can not be changed/deleted

• To be reachable this partition needs to be member of calling identity’s CSS

• An already existing partition can be defined as alias for “Directory URI” partition URIs in Directory URI partition can be reached by all CSSes which have the alias partition

• Good candidate: already existing DN partition

BRKCOL-2611 89


URI Dialing & Identity Delivery from CUCM towards Lync (1/2)

• Caller identity has the format “UserID@Sip_Domain” (Ex. [email protected])

• Policy on the CUCM<->VCS trunk definition to specify info sent as Caller Identity

• Default: “DN only…” (send only extension number assigned to the device)

• Recommended: “Deliver URI and DN…” (send both Primary Directory URI & DN)

BRKCOL-2611 90


URI Dialing & Identity Delivery from CUCM towards Lync (2/2)

• Caller identity should have the format “UserID@Sip_Domain” (Ex. [email protected])

• Policy on CUCM<->VCS trunk SIP Profile to specify Sip_Domain format

• Default: «not flagged» (send IP address of CUCM as “domain” – like [email protected])

• Recommended: «flagged» (send alphanumeric string as “domain”)

BRKCOL-2611 91


Personal Video Endpoint on CUCM – Best Practice

• Utilize the CUCM Single Number Reach (SNR) capability

• Any Call to the CUCM Identity Alias (or Ext. Number) will ring also the Lync Client

• Caveats:

• CUCM Video Endpoint status is not reflected into Lync User’s Presence

• Lync to Lync P2P calls will not ring user’s devices on CUCM

Expressway

Lync Gateway

Lync Server

Lync Client

Sip:[email protected]

DX80


CUCM

Davide

“Keep It simple”

(Ext. 5001)

BRKCOL-2611 92

Expressway Solution «Multipoint calls use case»


Scheduled conference using Webex Productivity Tool(CMR Hybrid)

Click here to start

the call

Define here how many

Video Devices will join

(Lync is just one of them...)

BRKCOL-2611 94


Internet

Expressway

Lync GW

Lync Edge Server

Expressway-E

CMR Cloud – Architecture for Lync interoperability (2)

Expressway-CCUCM

Lync Pool

Lync traffic must not go through the Expressway Lync Gateway when joining CMR cloud:

• Create a route to *@video.company.lab via the Expressway Lync Gateway

• Create a route to *@lync.webex.com through the Lync Edge (as a Federated domain)

Cisco WebEx Cloud

Webex Mobile Client


*@lync.webex.com

*@video.company.lab

(Future Release, Subject to Change)

BRKCOL-2611 95

Expressway Solution«...but what about the VCS centric scenario?»


Media passes through B2BUA engine

Video codec supported: H.264 AVC up to 720p@30fps

Audio codec supported: G.722, 722.1, G.711A, G.711U.

Shared Video Endpoint on VCSVCS

Core

H.323

Profile

3000MXP

VCS

Lync Gateway


Lync

Server

C-Series /

Third Party VC

*@company.lab

*@video.company.lab


SIP

Media H264 AVCMicrosoft SIP

Media H264 UC-SVC

B2BUA

BRKCOL-2611 97


Personal Video Endpoint on VCS

The “FindMe” feature on the VCS Lync Gateway provide the following capabilities:

• Single Identity – Single AD contact to identify Lync client and Video Endpoint

• Call Forking – Calls to the Identity Alias will also ring the Video Endpoint on VCS

• Presence - Status of the video endpoint should be reflected into Lync User’s Presence

Lync Server

FindMe Alias: [email protected]

Associated device: [email protected]

Lync Client


VC EX60


Davide

1

2

VCS Lync

Gateway

BRKCOL-2611 98

mailto:[email protected]


VCS “FindMe” – Additional Info

• SIP Trunking alone provides Basic Presence in Lync (Offline/Online status)

• FindMe is mandatory to see Enhanced Presence in Lync (Offline, Online & “In a call” status)

• FindMe supports max 10K users per cluster

• FindMe is only supported on the VCS platform (not on Expressway)

• FindMe provides Call forking for Personal VC paired with Lync Client

• FindMe can also be used for Shared VC Room if Enhanced Presence is needed

• FindMe Proxies VC’s registration into Lync acting as a “Virtual” Lync client:

• Personal VC – Lync User already defined so no need for additional Lync license

• Shared VC – A new Lync User must be defined and enabled so additional Lync license are needed

BRKCOL-2611 99


VCS X8.1

(Lync GW)

Lync 2013

[email protected] [email protected]

Call

Davide

FindMe Associated Device

[email protected] [email protected]@company.lab

Personal Video Endpoint on VCS – VCS to Lync call

1. Fabio calls Davide on his main identity alias ([email protected])

2. VCS extends the call to the EX60 device using the Findme Table

3. The call is forked from VCS side towards Lync (using Findme Virtual registration info)

4. Davide’s EX60 and Lync client ring at the same time

5. VCS stops any additional call coming back from Lync (due to Findme virtual registration)

Davide

Fabio

[email protected]

BRKCOL-2611 100




VCS X8.1

(Lync GW)

Lync 2013

[email protected]

[email protected] [email protected]

Call

Davide

FindMe Associated Device

[email protected] [email protected] [email protected]

Personal Video Endpoint on VCS - Lync to Lync call

1. Fabio calls Davide on his main identity alias ([email protected])

2. Davide’s Lync client rings

3. The call is forked from Lync side towards VCS via the Findme virtual registration

4. VCS extends the call to the EX60 device using the Findme Table

5. Davide’s EX60 and Lync client ring at the same time

Davide

Fabio

BRKCOL-2611 101




Expressway Solution «Extended Architectures»


Extended Architecture – Redundancy and Load Balancing

Expressway

Lync GatewayCUCMHLB or

DNS LB

Lync

Frontend

• On the Expressway to Lync trunk definition always specify the Lync Pool’s FQDN

• Two possible scenario could be implemented to resolve Lync’s Pool FQDN:

HLB – Redundancy/Balancing based on HLB capabilities (VIP address management)

DNS LB – Each Expressway box will use the first DNS Server defined in the

configuration, unless It fails. Load Balancing of the DNS servers is not implemented.

BRKCOL-2611 103



Expressway

Lync GatewayCUCMHLB or

DNS LB

Lync

Frontend

• Two possible balancing scenario could be achieved for the Lync Servers:

HLB - load balancing based on algorithm configured on the HLB itself

DNS LB – Each Expressway box will use the first DNS entry received in the

answer unless It fails or the DNS cache expires Load Balancing is achievable,

also if less accurate than with HLB.

BRKCOL-2611 104



Expressway

Lync GatewayCUCM

Lync

Frontend

• The Lync to Expressway trunk definition permit only to specify one FQDN as next hop

• Suggested approach is to use the Expressway’s cluster FQDN and use DNS LB

• The Lync Server selects one IP address to use, based on its own logic, and use it

unless It fails or the DNS cache expires

• Load Balancing is achievable, also if accuracy depends on the number of Lync servers

in the pool and DNS timer.

BRKCOL-2611 105


Multiple Lync Pools - scenario 1

Lync Pool 1

Sip: user@domain-B

Expressway

Lync Gateway 1

CUCM

sip:user@domain-A

Lync Pool 2

Sip:user@domain-C

Expressway

Lync Gateway 2

*@domain-B

*@domain-C

Geo Region 1

Geo Region 2

Scenario 1 – multiple GEO Regions, each one with a local Lync Pool, most of the calls are between

endpoint inside the same region:

• Use multiple Lync Gateway to keep media traffic local as much as possible

• On the CUCM we need specific routes to the different Microsoft’s Sip domains, using the Lync

Gateway associated to the target Lync Pool

BRKCOL-2611 106


Multiple Lync Pools - scenario 1

Lync Pool 1

Sip: user@domain-B

Expressway

Lync Gateway 1

Lync Pool 2

Sip:user@domain-C

Expressway

Lync Gateway 2

*@domain-A

*@domain-A

Geo Region 1

Geo Region 2

Scenario 1 – multiple GEO Regions, each one with a local Lync Pool, most of the calls are between

endpoint inside the same region:

• Use multiple Lync Gateway to keep media traffic local as much as possible

• On each Lync Pool we need a local route to the CUCM’s Sip domain, using the local Lync Gateway

CUCM

sip:user@domain-A

BRKCOL-2611 107


Multiple Lync Pools – scenario 2

Lync Pool 1

Sip: user@domain-B

Expressway

Lync Gateway 1

*@domain-BCUCM

sip:user@domain-A

Lync Pool 2

Sip:user@domain-C

Scenario 2 – single GEO Region, multiple Lync Pools, customer wants to use a single Lync Gateway:

• Expr. Lync Gateway can route multiple Sip domains towards the same Lync Pool

• Expr. Lync Gateway can send “Microsoft” traffic to one Lync Pool only

• Lync Pool 1 must be able to forward traffic directed to Lync Pool 2 (*@domain-C)

*@domain-C

Geo Region 1

BRKCOL-2611 108


Geo Region 1

Multiple Lync Pools – scenario 2

Lync Pool 1

Sip: user@domain-B

Expressway

Lync Gateway 1

*@domain-ACUCM

sip:user@domain-A

Lync Pool 2

Sip:user@domain-C

Scenario 2 – single GEO Region, multiple Lync Pools, customer wants to use a single Lync Gateway:

• Expr. Lync Gateway can receive traffic from multiple Lync Pools (need to trust all the Lync Servers)

• On each Lync Pool we need a local route to the CUCM’s Sip domain, using the same Lync Gateway

BRKCOL-2611 109

cisco interoperability with microsoftd2zmdbbm9feqrf.cloudfront.net/2016/usa/pdf/brkcol-2611.pdf ·...

Documents