Brkcol 2611 PDF

Cisco Interoperability with Microsoft
Part 2 - Video Interoperability

Fabio Chiesa Consulting System Engineer
fchiesa@cisco.com
BRKCOL-2611
Cisco Interoperability with Microsoft
Part 2 - Video Interoperability
Disclaimer
The Cisco products, service or features identified in this document may not yet
be available or may not be available in all areas and may be subject to change
without notice. Consult your local Cisco business contact for information on the
products or services available in your area.
You can find additional information via Ciscos World Wide Web server at
http://www.cisco.com. Actual performance and environmental costs of Cisco
products will vary depending on individual customer configurations and
conditions.
BRKCOL-2611 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Agenda
Microsoft UC Solutions Quick Overview (Video Focus)

Interoperability using Cisco Meeting Server (CMS)
Interoperability using Cisco Expressway
Business to Business Federation
Interoperability using Webex MC Video (CMR Cloud)
Summary
Note: for anything else refer to

BRKCOL-2610 (Cisco Interoperability with Microsoft, Part 1 Collaboration)
Microsoft UC Solution Overview
(Video Focus)
Video interoperability with Lync 2010 Server
Native Capabilities
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
Video interoperability with Lync 2013 Server
Native Capabilities
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)
Video interoperability with Skype for Business (S4B) Server
Native Capabilities
Microsoft/Polycom H.264 UC SVC (UCIF) and RTVideo supported as Video Codec
Use Microsoft CCCP as proprietary protocol to manage the multipoint sessions using the A/V MCU
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) - 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
Video interoperability with Lync 2013 & S4B Server
Microsoft A/V MCU Layouts
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)
Video interoperability with Lync 2010, 2013 & S4B Server
Call Routing when User Enabled for P2P calls only (no Enterprise Voice)
I can ONLY call

a SIP URI
if ( (SIP URI) match one of Lync/SFB User) then route locally
elseif ( (SIP URI) and (destination == remote domain) ) /* SIP Trunk Routing
Only one possible

Lync/SFB Pool Video Gateway CUCM
routing behavior for
Lync/SFB outgoing calls.
Video Interoperability with SFB Online (O365)
What about B2B Federation ?
Reference: Federation and Public IM Connectivity (Microsoft Technet)

Only other S4B, Lync and OCS systems are officially supported by Microsoft
The only way to interoperate is appearing to O365 as another Lync/S4B on-prem system
Video Interoperability with SFB Online (O365)
Call Routing for B2B Federation
External Federation must be enabled

The specific target domain must be explicitly listed
or not depending on the policy you are using:
Block everyone except for allowed domains
Allow everyone except for blocked domains
Content Sharing Interoperability
Content Encoding Methods
Background
Content can be shared with a remote party during a SIP call in two ways:
Video Channel
In a separate channel
(BFCP) so the receiver
can control the layout and
SIP / BFCP Content Channel (BFCP) SIP / BFCP negotiate different resolution
for the content
Video Channel
As part of the main video
channel so the receiver
SIP only has no control over layout
SIP / BFCP
Content Channel (NO BFCP) and content resolution
Content Encoding Methods
Possible Endpoint Encoding Behaviors (when BFCP is not available)
People or Content in main Composited People + Content Composited People + Content in

video channel in main video channel (1) main video channel (2)
Switches between people or Takes the camera and PC inputs Takes the camera inputs from the
content depending on if youre and creates a composite encoding participants and the PC input from
presenting or not of both sources the Presenter and creates a
CTS, TX and DX endpoints Some TC endpoints composite encoding of those sources
MCU, TelePresence Server & CMS
Content Sharing Interoperability with Microsoft
Possible Solutions
Microsoft/Cisco
CUCM Gateway Lync/SFB Pool
MX300G2 Lync Client
BFCP RDP
SIP SIP SIP SIP
Cisco uses BFCP for Content Sharing

Microsoft uses RDP for Content Sharing
Three options to interoperate:
RDP to BFCP transcoding
BFCP to RDP transcoding
Encoding Content in Main Video
Interoperability using Cisco
Meeting Server (CMS)
Intra-company Scenario
Few notes before proceeding...
CUCM is always represented in the diagrams, but the same
architecture is also valid for Expressway/VCS as Call Control.
Lync 2013 Server is always represented in the diagram, but the same
architecture is also valid for Lync 2010 and Skype for Business 2015
Server.
The focus of this chapter is Intra-Company, not B2B
Cisco Meeting Server Making Meetings Easier
Single platform for audio, Allows anyone to join a

video and web meetings meeting from room, desktop
or mobile
Offers advanced Supports the Protects

interoperability, easy addition of investment by
preserving the capacity as the working with
user experience organizations existing
including needs grow infrastructure
Skype for
Business users
Cisco Meeting Server Architecture
(without Microsoft Interoperability)
DMZ Internet
Internal External
TMS TMS-XE
CMA
CMS Core CMS Edge
CMA
Phone Expressway C WebRTC (preview on Expressway 8.9)
Expressway E B2B
Immersive Endpoints
Endpoints LEGEND
Standard SIP
UCM Cluster Home / Mobile FW Traversal

Endpoints
Non-Immersive 3rd Party / WebRTC
(MRA)
Endpoints H.323 / SIP
H.323
Legacy
Endpoints XMPP
Lync & Skype for Business Interoperability
Integration Types
Gateway: Allows P2P calling between Room Endpoints and Lync/Skype for
Business users
Spaces: Room Endpoints and Lync/Skype for Business users all connect on Cisco
Meeting Server for best experience
Dual Homed Conferencing: Room endpoints connect on Meeting Server with
connection to Lync/Skype for Business meetings as full-featured participants
B2B Federation (including Office 365)
Lync & Skype for Business Interoperability
Supported Features and Capabilities
Video Codec:
H.264UC-SVC (SFB & Lync 2013)
RTVideo (Lync 2010 & 2011)
Bi-directional RDP Transcoding for Content Sharing (see next slide)
Multi-party conferencing (Microsoft CCCP protocol support)
Drag and Drop escalation from Lync/SFB client
Participant list integration
Group Chat (Spaces only)
NEW - Schedule conferences from S4B with OBTP*
* Requires TMS and Dual Home Configuration
Content Sharing interoperability
Supported Capabilities with CMS
Content Share from Lync/SFB
Video Channel
Lync/S4B
SIP / BFCP
RDP->BFCP Content Channel (RDP only)
Content Share from TP Endpoints

Video Channel
Lync/S4B
SIP / BFCP Content Channel
BFCP->RDP (RDP only)
Important note: Simplified diagrams to explain capability only. This is not the detailed architecture.
Integration Type 1 - Gateway
Call Routing How it works for P2P calls
CMS Call CUCM
Bridge *@company.lab
MX700
*@video.company.lab
TX9000
MX200
SIP
Microsoft SIP
Room01@video.company.lab
H264 AVC
H264 UC-SVC or RTV
Lync
Server Media always flows through the CMS Call Bridge
Bi-directional RDP/BFCP Transcoding for Content Sharing
Different SIP domains as best practice to avoid possible loops
Bob.banks@company.lab
Calling Video Devices from the Lync/SFB Clients
For each shared Video Device a contact can be created in AD, mapping the AD attribute <msRTCSIP-PrimaryUserAddress>
to the endpoints Sip URI
Lync/SFB users will be able to search Video Endpoint, add them to the buddy list and call them when needed
Note: Presence is available but reflect only partially the real Endpoints status
Lync/SFB users will be able to search Video Endpoint, add them to the buddy list and call them when needed
Note: Presence is available but reflect only partially the real Endpoints status
Calling Lync/SFB Users from the Video Devices
It is possible to call a Lync/SFB User after searching him/her in the CUCM Directory
CUCMs Directory URI field must be populated with the Lync/S4B Clients SIP address
Expressway/VCS can leverage TMS Phone Book integration with AD to synchronize the same info
Call Routing How it works for calls to TelePresence Server
CMS Call Bridge CUCM
(Gateway mode)
TMS
*@video.company.lab
TelePresence
Conductor
SIP
Microsoft SIP
H264 AVC
H264 UC-SVC or RTV
Lync
TelePresence
Server
Server
CMR_ID@video.company.lab
CMS acts only as a Gateway here

TelePresence Server is the MCU with the related capabilities
Can be used as temporary solution before migrating to full CMS
CMS as a Gateway to TelePresence Server User Experience
LYNC
TPS
CMS Call Bridge Lync/Skype SKYPE4B
(Gateway) Front End
Dial Conference Address Dial Conference Address
CMR_ID@video.company.lab CMR_ID@video.company.lab
LYNC
TPS
Conference Host (Gateway) Front End
Standards Video Systems Lync/SFB Clients
Dial Conference Address Dial Conference Address
CMR_ID@video.company.lab CMR_ID@video.company.lab
LYNC
TPS
Conference Host (Gateway) Front End
Integration Type 2 - Spaces
Introducing Spaces
Virtual Meeting Room
All Participants Dial the

CMA space Address
Users can have multiple

Immersive Spaces
Endpoints
Lync/S4B
Users
Desktop System
Devices join a space

and get the best
experience
Telepresence
Jabber
Endpoints
User Video/Audio/Content
Other Vendor WebRTC access

phone Guest Users
Endpoints
via WebRTC
Call Routing How it works for calls to CMS (joining Spaces)
Space_ID@video.company.lab CUCM
*@video.company.lab
CMS Call
Bridge
TMS
TMS-XE
Lync
Server
SIP
Microsoft SIP CMS acts as full MCU here, with Enhanced Video Layouts
H264 AVC Bi-directional RDP/BFCP Transcoding for Content Sharing
H264 UC-SVC or RTV Group Chat available also for Lync/SFB clients
Spaces Presence published into Lync/SFB clients
Shared Attendee list
User Experience Video Layout
Flexible in Meeting Layouts
Same Layout for SIP/H323 Endpoints, CMA &
WebRTC clients, Microsoft Lync&SFB clients Layout Families
Active Overlay onePlusN Equal NxN

Speaker
onePlusN and Equal layouts dynamically scale as more participants join
Possibility to pre-configure the initial Layout and/or

change it on the fly using DTMF/Active-Control (see onePlus5 onePlus7 onePlus8
next slides)
Equal 2x2 Equal 3x3 Equal 4x4 Equal 5x5
User Experience Video Layout
Choose the Best Layout Family for Your Device
Active Speaker Overlay
Equal:
onePlusN:
2x2, 3x3,
N=5, 7 or 9
4x4, 5x5
User Experience Active Control
Allows the conference participants to receive details of the meeting and perform a few administrative tasks
Info on who is speaking, sharing & muted, actively drop participants, change layout etc.
Participant list includes Video Endpoints and Lync/SFB clients
This feature is now supported on CMS 2.1 hosted conferences and endpoints running CE8.3.0.
User Experience Scheduling and Joining Spaces
Scheduled Conferences (including OBTP)
Users can schedule a meeting by using:
o TMS Smart Scheduler web GUI
o TMS Administrator Interface
o Outlook Calendar & TMS-XE integration

Lync/SFB users join the meeting clicking on the hyperlink in the Calendar invite
Personal Space (always on, permanent address)

Host can send his Personal Spaces address in the calendar invite
o Lync/SFB Attendee will copy the meeting address (URI) into the Client
Personal Spaces could also be listed into the Lync/SFB Address Book
User Experience - Scheduling using TMS Smart Scheduler
Define here how many

Video Devices will join
(Lync is just one of them...)
Click here to start

the call
User Experience - Scheduling using Outlook and TMS-XE
Send invite Invite participants & Rooms (Video

Endpoints)
Click on the Video Address to cross-launch Lync/SFB Client
User Experience Personal Spaces & Buddy List
For each Space an AD contact can be created, mapping the AD attribute <msRTCSIP-PrimaryUserAddress> to the Rooms Sip URI
Lync/SFB servers will sync the internal Address Book from AD during the night
Users will be able to search for Personal Space, add them to the buddy list and join when needed
Spaces Presence is updated when the first Endpoint/Client joins
Integration Type 3 - Dual Homed
Conferencing
Dual Homed Conferencing - Meeting Experience
Video endpoints and Lync/SFB clients maintain the

native UE (Layout for example)
Participant list on the Lync/SFB client also includes
Video Endpoints
Participant list on the TP Endpoints also includes
Lync/SFB (Active Control)
Bi-directional RDP/BFCP Transcoding for Content
Sharing
Group Chat extended to CMA Clients and WebRTC
Users
Dual Homed conferencing How it works
LYNC
LYNC
CMS Call Bridge SKYPE4B

VIDEO SYSTEMS LYNC SERVER
Conference Host A/V MCU
Click-To-Join
LYNC
LYNC

Click-To-Join
Dial IVR + Conference ID Initiate Dual-Home
LYNC
LYNC

Click-To-Join
LYNC
LYNC

Lync/SFB Clients
Click-To-Join
LYNC
LYNC

Click-To-Join
LYNC
LYNC

The expected experience is maintained:

Gallery View for Lync/SFB clients
Video Layouts for anything else
Dual Homed conferencing Scheduling Experience
For customers using Lync/SFB as their primary meeting tool

Users schedule meetings using Outlook (no change to
current work flow)
It requires the Dial-In feature activated and configured on
the Lync/SFB Pool
[Optional] OBTP from Cisco endpoints into meeting
Microsoft A/V MCU gets a critical role!
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
New meetings scheduled via Outlook will all have
this additional info in the body
Dual Homed conferencing Scheduling using Cisco One Button
to Push (OBTP) ...is 41238 a Lync/SFB Conference ID?
CUCM
*@video.company.lab
CMS Call
Bridge
TMS
TMS-XE
Lync Server
+ A/V MCU
TMS will generate the OBTP Sip address with format:
Conference_ID@Video_Domain
Conference_ID is the one provided by the Microsoft A/V MCU
SIP
Microsoft SIP Video Domain can be the same used for Video Endpoint
H264 AVC and CMS Spaces or a dedicated one
H264 UC-SVC or RTV
The TURN Mystery.....
Lync/SFB Remote Access support - Background
Lync Pool
SIP
Microsoft SIP
media (Direct) Lync Edge Server
media (TURN Tunnel)
CMS Call
Bridge
Internet
CUCM
Lync/SFB clients can register to the Lync Pool from Internet, through Microsoft 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?
Lync/SFB Remote Access support Why do we need TURN?
Lync Pool
SIP
Microsoft SIP
media (Direct)
media (TURN Tunnel)
TURN
Server
TURN
client
Lync Edge Server

CMS Call
Bridge
Internet
CUCM
ICE - Interactive Connectivity Establishment (RFC 5245), TURN and STUN are the answer
Lync/SFB Edge provides TURN Service to CMS (TURN client)
Expr-C/Exp-E (Firewall Traversal chain) are not included in the signaling and media path
Follow the official Microsoft guideline for firewall configuration
Multiple media paths, depending on ICE negotiation, are possible (see next slide for an example)
Lync/SFB Remote Access support Media Flow Example
Lync Pool
SIP
Microsoft SIP
media (Direct)
media (TURN Tunnel) TURN
TURN client
Server
TURN
client
Lync Edge Server

CMS Call
Bridge
Internet
CUCM
In this example the A/V media is flowing through:

1. Lync client <-> TURN Server on the Lync Edge (Encapsulated)
2. TURN Server on the Lync Edge <> Loopback (Direct)
3. TURN server on the Lync Edge <-> CMS (Encapsulated)
4. CMS <-> Video Endpoint (Direct)
Lync Remote Access support CMS TURN Configuration

Insert the Lync/SFBs Front End Pool address in the Server address field (NOT the Lync/SFB Edge...)
Service Lync/SFB users are needed to register CMS to the Front End Pool and ask for TURN access right
Each Service User will be able to allocate 12 concurrent A/V session on the TURN servers
Create multiple users on the Lync/SFB side to scale more
Specify the number of users created in the Number of registrations field
Userss name must follow a pre-defined structure
Interoperability using Expressway
as a Gateway
Intra-company Scenario
Few notes before proceeding...
CUCM is always represented in the diagrams, but the same
architecture is also valid for VCS as Call Control.
Expressway is always mentioned here as Gateway, but also VCS is 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.
The focus of this chapter is Intra-Company, not B2B.
Video Interoperability High Level Architecture
Lync Server Expressway X8.9 CUCM
2013 (Lync Gateway) 10.X/11.X
DX80
B2BUA
H264 AVC <-> H264UC-SVC

Gateway
MX300
Supported Microsoft Environment:

Skype for Business Server 2015 (H264UC-SVC 720p@30fps)
Lync Server 2013 (H264UC-SVC - 720p@30fps) SIP
Lync Server 2010 (H263 - CIF@15fps) Microsoft SIP
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
Call Routing How it works for P2P calls
Expressway
Lync Gateway CUCM
*@company.lab
MX700
B2BUA
*@video.company.lab
TX9000
MX300
SIP
Microsoft SIP
Media H264 AVC
Media H264 UC-SVC
Lync Media always flows through the Expressway Lync Gateway

Server 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)
Bob.banks@company.lab
Call Routing How it works for MultiPoint calls
Expressway
CUCM
Lync Gateway
TMS
B2BUA
*@video.company.lab
TelePresence
Conductor
SIP
Microsoft SIP
Media H264 AVC
Media H264 UC-SVC
Lync
TelePresence
Server
Server
CMR_ID@video.company.lab
No special/additional configuration needed for Lync interop

TelePresence Server manages only standard H264 AVC stream
Content Sharing interoperability
Supported Capabilities with Expressway
Expressway
CUCM Lync Pool
MX300G2 Lync Gateway Lync Client
BFCP RDP
SIP SIP SIP SIP
RDP to BFCP transcoding
Expressway Lync Gateway provides only RDP to BFCP transcoding

No Expressway Lync Gateway interaction in the other direction (see next slide)
User Experience depends on the Video Endpoint Content Encoding capability
Cisco & Microsoft Content Sharing interoperability
Supported Capabilities with Expressway Lync Gateway
Content Share from Lync/SFB
Video Channel
Lync/S4B
RDP->BFCP (RDP only)
Content Share from TP Endpoints

Video Channel
Lync/S4B
(RDP only)
Important note: Simplified diagrams to explain capability only. This is not the detailed architecture.
Lync/SFB Remote Access support What about ICE & TURN?
Lync Pool
SIP
Microsoft SIP
media (Direct)
media (TURN Tunnel) Lync Edge Server
TURN
client
Expressway
TURN
Lync Gateway
Server
Internet
CUCM EXP-C EXP-E
Expr. Lync Gateway does NOT support Lync/SFB Edge as TURN server
Expr-E provides Standard TURN Service to Expr. Lync Gateway (TURN client)
Expr-C (Firewall Traversal chain) is not included in the signaling and media path
Multiple media paths, depending on ICE negotiation, are possible and could also include the Lync/SFB Edge
Lync Remote Access support Expressway TURN capabilities
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 Expr. Lync Gateway, Expr-E (Turn Server) and Lync
Edge must be allowed through the Firewalls (see the deployment guide for further details)
Business to Business Federation
The Collaboration Landscape
Enabling Connection of Any Users to Any Services Through Any Network
Users in Branch Offices

Video
Users in
Headquarters
Cloud
PSTN and Services
IP PSTN
Voice Social Public/
Consumers
Private
Public WAN
Mobile and Internet
Remote Workers
Content and Data IM and Presence
Suppliers,
Partners, and
Customers (B2B)
B2B Federation having a local
On-Premise Lync/SFB
B2B Federation - Architecture
Lync Pool
SIP
Microsoft SIP Lync and Skype for
media (Direct) Business Servers
media (TURN Tunnel)
Lync Edge Server

Microsoft
CMS Call Bridge Office 365
Internet
Any standards
CUCM EXP-C EXP-E
based SIP
or H.323 Video
Local Lync/SFB Edge is used as B2B Federation Gateway to/from Microsoft based Peers
Expr-C/Exp-E chain is used as B2B Federation Gateway to/from Standard based SIP/H323 Peers
CMS is needed for A/V Transcoding, also for P2P calls ( Expressway Lync Gateway is not supported)
Microsoft Office 365 & Lync/S4B Server are both supported as remote destinations
Capabilities available with the B2B scenario
Point to Point Gateway Calls
Remote Microsoft clients can join CMS Spaces via Dial-in (preferred scenario)
Ad-Hoc Dual Homed Conferences started using Drag and Drop from the
remote Microsoft clients
Group Chat inside Spaces
Common Meeting participant list
Note - Scheduled Dual Homed Conferences hosted on remote Lync/SFB are

not supported
B2B Federation Inbound Call Routing
Lync Pool _sipfederationtls._tcp.video.company.lab
SIP
media (TURN Tunnel)
Lync Edge Server

Microsoft
Internet
CUCM EXP-C EXP-E
Local Lync/SFB Edge is used as B2B Federation Gateway FROM Microsoft based Peers
It is mandatory to assign a Microsoft SIP Federation SRV for the Video Domain to the Lync/SFB Edge
Expr-C/Exp-E (Firewall Traversal chain) are not involved in the signaling and media path
B2B Federation Outbound Call Routing
Lync Pool _sipfederationtls._tcp.businesspartner.lab
SIP
SIP:user1@businesspartner.lab
media (TURN Tunnel)
Lync Edge Server

Microsoft
Internet
CUCM EXP-C EXP-E
Local Lync/SFB Edge is used as B2B Federation Gateway TO Microsoft based Peers
Traffic for external Microsoft SIP domains are routed through CMS and the local Front End Pool
B2B Federation - What about ICE & TURN?
Lync Pool
SIP
media (TURN Tunnel)
TURN
Server
TURN
client
Lync Edge Server Microsoft

CMS Call
Bridge Office 365
Internet
CUCM EXP-C EXP-E

Multiple media paths, depending on ICE negotiation, are possible
Follow the official Microsoft guideline for firewall configuration
B2B Federation without having a
local On-Premise Lync/SFB
Standard Based B2B Video Federation (Pre X8.9)
SIP
Microsoft SIP
media (Direct)
media (TURN Tunnel)
WebEx Video
(CMR Cloud)
Internet
CUCM EXP-C EXP-E
Any standards
based SIP
or H.323 Video
Lync & Skype for Business B2B Audio/Video Federation (X8.9)
SIP
Microsoft SIP
media (Direct) Lync and Skype for
media (TURN Tunnel) Business Servers
CMS Call Bridge
Microsoft
Office 365
Internet
CUCM EXP-C EXP-E
Expr-C/Exp-E also provide now B2B Federation with Microsoft, when On-Premise Lync/SFB is not available
Microsoft Office 365 & Lync/S4B Server are both supported as remote destinations
CMS is needed for A/V Transcoding, also for P2P calls ( Expressway Lync Gateway is not supported)
Capabilities available with the B2B scenario
Point to Point Gateway Calls
Remote Microsoft clients can join CMS Spaces via Dial-in (preferred scenario)
Ad-Hoc Dual Homed Conferences started using Drag and Drop from the
remote Microsoft clients
Group Chat inside Spaces
Common Meeting participant list
Note - Scheduled Dual Homed Conferences hosted on remote Lync/SFB are

not supported
Lync/SFB/O365 Integration Enhancement
New Search Rule options:

Detects the SIP variant and routes the
signal/payload
Traffic will be routed only if it matches the SIP
variant
Supported Variants:
All SIP Variants
Standard Based
Microsoft Variants (IM/P/A/V/Share)
Microsoft AV & Share
Microsoft IM/P
B2B Federation Inbound Call Routing
_sipfederationtls._tcp.video.company.lab
SIP
media (TURN Tunnel)
CMS Call Bridge
Microsoft
Office 365
Internet
CUCM EXP-C EXP-E
CMS is always invoked for A/V Transcoding, also for P2P calls
Mandatory to assign a Microsoft Federation SRV for the Video Domain to the Exp-E public interface
Mandatory to assign a Public CA signed certificate to the Exp-E public interface
B2B Federation Outbound Call Routing
_sipfederationtls._tcp.businesspartner.lab
DNS Zone
SIP
if SIP=MS then look for _sipfederationtls
Microsoft SIP if SIP MS then look for _sips
media (Direct) Lync and Skype for
Business Servers
media (TURN Tunnel) SIP:user1@businesspartner.lab
CMS Call Bridge
Microsoft
Office 365
Internet
CUCM EXP-C EXP-E
CMS is always invoked for A/V Transcoding, also for P2P calls
New Microsoft SRV lookup capabilities added to the Exp-E
Possibility to look for both Standard and Microsoft based remote destinations (using multiple search rules)
What about the TURN server in this scenario?
SIP
media (TURN Tunnel)
CMS Call Bridge
TURN
client
Microsoft
TURN Office 365
Server
Internet
CUCM EXP-C EXP-E
Expr-E provides Standard TURN Service to CMS (TURN client)

Expr-C (Firewall Traversal chain) is not directly involved in the TURN connection
Multiple media paths, depending on ICE negotiation, are possible
CMS will act as TURN client and the Expressway-E will act as TURN server
TURN service information must be configured on both side.
the two devices.
Specific TCP/UDP connections between CMS & Expr-E (Turn Server) must be allowed
through the Firewalls (see the deployment guide for further details)
Video Interoperability using Webex MC
Video (CMR Cloud)
Collaboration Meeting Rooms (CMR) Cloud
One Meeting
Converged video and web conferencing meeting
experience from the WebEx Cloud
Join From Anywhere

From the pocket to the boardroom with true platform
independence including SIP, H.323 and Lync/S4B
Superior Scale
Up to 25 video endpoints & additional 500 video-
enabled WebEx users + 500 audio only WebEx
users (1025 users/meeting)
Spark Ready
Integrated with the Spark Platform and compatible
with all the Spark Clients/Endpoints
CMR Cloud Lync & SFB Server (on premise) interoperability
SIP Lync Pool

Microsoft SIP *@lync.webex.com Webex Desktop
Client
Webex Mobile
Client
Lync Edge Server
Cisco WebEx
Cloud
*@*.webex.com
CUCM EXP-C EXP-E
Each solution must use his own Firewall Traversal technology to join the CMR Cloud session:
Microsoft - route domain lync.webex.com through the Lync Edge (as Federated domain)
Cisco - route domains *.webex.com through the Expressway C/E
CMR Cloud SFB Online (Office 365) interoperability
Webex Desktop
SIP Client
Microsoft SIP Cisco WebEx
Cloud
Webex Mobile
Client
*@lync.webex.com
EXP-C EXP-E
CUCM
Internet
O365 S4B Online
External Federation must be enabled for the customers S4B online environment
The specific domain lync.webex.com must be allowed as a Federated Domain
DNS SRV lookup will then make the magic
Summary
Interoperability Summary - Feature Comparison
Expressway / VCS + Webex Video
Cisco Meeting Server
TelePresence Server (Cloud CMR)
Audio/Video H264UC-SVC + H263 H264UC-SVC + RTV H264 UC-SVC + H263
Asymmetric Transcoding Asymmetric Transcoding

Content Sharing Bi-Directional RDP Transcoding
(RDP to BFCP) (RDP to BFCP)
Gateway Calls
Personal Meeting Room CMR Spaces CMR
Virtual Rooms Presence
Note: B2B is not Supported (0365

Dual Homing (Scheduled)
& remote Lync/SFB Server)
Dual Homing (Drag and Drop)
Group Chat
(Lync, SFB, CMA and WebRTC)
B2B with remote Lync/SFB/O365
Not Applicable
(using a local On Premise Lync/SFB)
B2B with remote Lync/SFB/O365
(Direct Federation)
SIP Broker (IM/P + A/V Jabber Interop)
Cisco Video Interoperability with Microsoft
Summary
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
Call to Action
Attend the following related sessions
BRKCOL-2610 (Cisco Interoperability with Microsoft, Part 1 Collaboration)
BRKCOL-2803 (Designing and deploying multiparty conferencing for telepresence video)
Visit the World of Solutions

Cisco Campus (Collaboration Area, Conferencing & Microsoft Interoperability corner)
Complete Your Online Session Evaluation
Please complete your Online
Session Evaluations after each
session
Complete 4 Session Evaluations &
the Overall Conference Evaluation
(available from Thursday) to receive
your Cisco Live T-shirt
All surveys can be completed via
the Cisco Live Mobile App or the
Dont forget: Cisco Live sessions will be available
Communication Stations for viewing on-demand after the event at
CiscoLive.com/Online
Cisco Spark
Ask Questions, Get Answers, Continue the Experience
Use Cisco Spark to communicate with the Speaker and fellow

participants after the session
Download the Cisco Spark app from iTunes or Google Play

1. Go to the Cisco Live Berlin 2017 Mobile app
2. Find this session
3. Click the Spark button under Speakers in the session description
4. Enter the room, room name = BRKCOL-2611
5. Join the conversation!
The Spark Room will be open for 2 weeks after Cisco Live
Thank You
19,000+
Members
Join the Customer Connection Program Strong
Influence product direction

Join in World of Solutions
Access to early adopter & beta trials
Collaboration zone
Monthly technical & roadmap briefings
Join at the Customer Connection stand
Connect in private online community New member thank-you gift *
CCP ribbon for access to NDA sessions
Exclusive perks at Cisco Live
Collaboration NDA Roadmap Sessions Mon & Tues
Q&A Open Forum with Collaboration Product
Management Tues 4:00 5:30 Join Online
Reserved seats at Collaboration Innovation Talk www.cisco.com/go/ccp
Thurs 8:00am 9:00am
Come to Collaboration zone to get your
2 new CCP tracks launching at Cisco Live:
ribbon and new member gift
Security & Enterprise Networks
* While supplies last
Appendix
Interoperability using
Expressway/VCS as a Gateway
Video Interoperability - Most Common Use Case scenarios
Point to Point calls

SX80,MX300, Shared Video Endpoint
Lync 2013
MX800
Client
Point to Point calls

Lync 2013 DX80 Personal Video Endpoint
Client
Multipoint calls
Lync Client, Personal and Shared
Video Endpoint in the same call
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
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

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)
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
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)
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 identitys 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
URI Dialing & Identity Delivery from CUCM towards Lync (1/2)
Caller identity has the format UserID@Sip_Domain (Ex. Alice@video.company.lab)

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)
URI Dialing & Identity Delivery from CUCM towards Lync (2/2)
Caller identity should have the format UserID@Sip_Domain (Ex. Alice@video.company.lab)

Policy on CUCM<->VCS trunk SIP Profile to specify Sip_Domain format
Default: not flagged (send IP address of CUCM as domain like UserID@10.58.9.1)
Recommended: flagged (send alphanumeric string as domain)
Personal Video Endpoint on CUCM Best Practice
Expressway
CUCM Lync Gateway
Lync Server
Keep It simple
DX80 Lync Client
Sip:Davide@video.company.lab Sip:Davide@company.lab
(Ext. 5001)
Davide
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 Users Presence
Lync to Lync P2P calls will not ring users devices on CUCM
Expressway Solution Multipoint calls
use case
Scheduled conference using Webex Productivity Tool
(CMR Hybrid)

(CMR Hybrid)

(CMR Hybrid)

(CMR Hybrid)

Video Devices will join Click here to start
(Lync is just one of them...) the call
(CMR Hybrid)
Click here to start

the call
CMR Cloud Architecture for Lync interoperability (2)
(Future Release, Subject to Change)
Lync Pool
*@lync.webex.com Webex Desktop
Client
Webex Mobile
Lync Edge Server Client
*@video.company.lab
Cisco WebEx
Expressway Cloud
Lync GW
Internet
CUCM Expressway-C Expressway-E
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)
Expressway Solution
...but what about the VCS centric
scenario?
Shared Video Endpoint on VCS
VCS VCS
Lync Gateway Core
H.323
C-Series / SIP
B2BUA Third Party VC Microsoft SIP
Media H264 AVC
Media H264 UC-SVC
Profile
3000MXP
Lync
Server
VCS VCS
Lync Gateway Core
H.323
C-Series / SIP
Media H264 AVC
Media H264 UC-SVC
Profile
3000MXP
Lync
Server
Sip:Davide@company.lab
VCS VCS
Lync Gateway Core
*@company.lab H.323
C-Series / SIP
Media H264 AVC
Media H264 UC-SVC
Profile
3000MXP
Lync
Server
VCS VCS
Lync Gateway Core
*@company.lab H.323
C-Series / SIP
Media H264 AVC
Media H264 UC-SVC
Sip:3000mxp@video.company.lab
Profile
3000MXP
Lync
Server
VCS VCS
Lync Gateway Core
*@company.lab H.323
C-Series / SIP
*@video.company.lab Media H264 AVC
Media H264 UC-SVC
Profile
3000MXP
Lync
Server
VCS VCS
Lync Gateway Core
H.323
C-Series / SIP
Media H264 AVC
Media H264 UC-SVC
Profile
3000MXP
Lync
Server
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 Users Presence
FindMe Alias: Davide@company.lab

1 Associated device: EX60@video.company.lab
VCS Lync Lync Server

Gateway
2
VC EX60 Lync Client
Sip:EX60@video.company.lab Sip:Davide@company.lab
Davide
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 VCs 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
Personal Video Endpoint on VCS VCS to Lync call
FindMe Associated Device
Davide@company.lab EX60@video.company.lab
Davide@company.lab
Lync 2013
Call SX20@video.company.lab
VCS X8.1
Davide (Lync GW)
EX60@video.company.lab Davide@company.lab
Fabio
Davide
1. Fabio calls Davide on his main identity alias (Davide@company.lab)
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. Davides EX60 and Lync client ring at the same time
5. VCS stops any additional call coming back from Lync (due to Findme virtual registration)
Personal Video Endpoint on VCS - Lync to Lync call
FindMe Associated Device
Davide@company.lab EX60@video.company.lab Davide@company.lab

Lync 2013
Call
Davide
Fabio@company.lab
VCS X8.1
(Lync GW)
Fabio
EX60@video.company.lab Davide@company.lab
Davide
1. Fabio calls Davide on his main identity alias (Davide@company.lab)
2. Davides 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. Davides EX60 and Lync client ring at the same time
Expressway Solution Extended
Architectures
Why do we need a dedicated Lync Gateway?
Lync Pool
Lync Edge Server
Expressway
Lync GW
Internet
CUCM Expressway-C Expressway-E
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
Redundancy and Load Balancing
Expressway
CUCM Lync Gateway Lync Pool
cluster cluster HLB or
DNS LB
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
Extended Architecture Redundancy and Load Balancing
Expressway Lync
Lync Gateway HLB or Frontend
CUCM DNS LB
On the Expressway to Lync trunk definition always specify the Lync Pools FQDN
Two possible scenario could be implemented to resolve Lyncs 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.
Expressway Lync
Lync Gateway HLB or Frontend
CUCM DNS LB
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.
Expressway Lync
CUCM Lync Gateway Frontend
The Lync to Expressway trunk definition permit only to specify one FQDN as next hop
Suggested approach is to use the Expressways 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.
Redundancy and Load Balancing
Expressway
CUCM
Lync Gateway Lync Pool
cluster cluster
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
Lync Remote Access support - Background
Lync Pool
Lync Edge Server
Expressway
Lync Gateway
Internet
CUCM
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?
Lync Remote Access support Why do we need TURN?
Lync Pool
SIP
Microsoft SIP
media (Direct)
TURN
client
Expressway
TURN
Lync Gateway
Server
Internet
CUCM Expressway-E
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)
Lync Remote Access support - Media Flow negotiation (1/3)
SIP Lync Pool
Microsoft SIP
media (Direct)
TURN
client
Expressway TURN
Lync Gateway Server
Internet
CUCM Expressway-E
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)
SIP Lync Pool
Microsoft SIP
media (Direct)
Lync Edge Server
media (TURN Tunnel)
TURN
Server
Expressway
Lync Gateway
Internet
CUCM Expressway-E
In this case A/V media is flowing through:

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
SIP Lync Pool
Microsoft SIP
media (Direct)
Lync Edge Server
media (TURN Tunnel)
TURN
Server
TURN
client
Expressway TURN
Lync Gateway Server
Internet
CUCM Expressway-E
In this case A/V media is flowing through:

2. TURN server on the Lync Edge <-> TURN Server on the Expr. Lync Gateway (Direct)
3. TURN tunnel to the Expr. Lync Gateway (Encapsulated)
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.
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)
Multiple Lync Pools - scenario 1
Expressway Geo Region 1
Lync Gateway 1
*@domain-B Lync Pool 1
Sip: user@domain-B
CUCM
sip:user@domain-A
Lync Pool 2
*@domain-C Sip:user@domain-C
Expressway
Lync Gateway 2 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 Microsofts Sip domains, using the Lync
Gateway associated to the target Lync Pool
Multiple Lync Pools - scenario 1
Expressway Geo Region 1
Lync Gateway 1
*@domain-A Lync Pool 1
Sip: user@domain-B
CUCM
sip:user@domain-A
*@domain-A Lync Pool 2

Sip:user@domain-C
Expressway
Lync Gateway 2 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 CUCMs Sip domain, using the local Lync Gateway
Multiple Lync Pools scenario 2
Geo Region 1
Expressway
Lync Pool 1
Lync Gateway 1
Sip: user@domain-B
*@domain-B
CUCM
sip:user@domain-A
*@domain-C
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)
Multiple Lync Pools scenario 2
Geo Region 1
Expressway
Lync Gateway 1 Lync Pool 1
Sip: user@domain-B
*@domain-A
CUCM
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 CUCMs Sip domain, using the same Lync Gateway

Brkcol 2611 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Brkcol 2611 PDF

Uploaded by

Copyright:

Available Formats

Cisco Interoperability with Microsoft

Part 2 - Video Interoperability

Microsoft UC Solutions Quick Overview (Video Focus)

Note: for anything else refer to

Uses the RTVideo codec as default

Support only the RTVideo codec

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

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

New Server role for Video Interoperability (VIS)

4 Layout available (only two with video):

I can ONLY call

Only one possible

Reference: Federation and Public IM Connectivity (Microsoft Technet)

External Federation must be enabled

People or Content in main Composited People + Content Composited People + Content in

SIP SIP SIP SIP

Cisco uses BFCP for Content Sharing

Single platform for audio, Allows anyone to join a

Offers advanced Supports the Protects

Phone Expressway C WebRTC (preview on Expressway 8.9)

UCM Cluster Home / Mobile FW Traversal

* Requires TMS and Dual Home Configuration

Content Share from TP Endpoints

CMS acts only as a Gateway here

Standards Video Systems Lync/SFB Clients

Standards Video Systems Lync/SFB Clients

All Participants Dial the

Users can have multiple

Devices join a space

Other Vendor WebRTC access

Active Overlay onePlusN Equal NxN

onePlusN and Equal layouts dynamically scale as more participants join

Possibility to pre-configure the initial Layout and/or

Equal 2x2 Equal 3x3 Equal 4x4 Equal 5x5

Active Speaker Overlay

o TMS Administrator Interface

o Outlook Calendar & TMS-XE integration

Personal Space (always on, permanent address)

Define here how many

Click here to start

Send invite Invite participants & Rooms (Video

Video endpoints and Lync/SFB clients maintain the

CMS Call Bridge SKYPE4B

CMS Call Bridge SKYPE4B

CMS Call Bridge SKYPE4B

CMS Call Bridge SKYPE4B

CMS Call Bridge SKYPE4B

Standards Video Systems Lync/SFB Clients

CMS Call Bridge SKYPE4B

The expected experience is maintained:

Standards Video Systems Lync/SFB Clients

For customers using Lync/SFB as their primary meeting tool

Select the Meeting Configuration page under the

Lync Edge Server

Lync Edge Server

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

Lync/SFB Edge provides TURN Service to CMS (TURN client)

H264 AVC <-> H264UC-SVC

Supported Microsoft Environment:

Lync Media always flows through the Expressway Lync Gateway