cisco interoperability with microsoft - amazon web … · cisco interoperability with microsoft...

Post on 10-May-2018

222 Views

Category:

Documents

1 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Cisco Interoperability with MicrosoftPart 2 - Video Interoperability

Fabio Chiesa – Consulting System Engineerfchiesa@cisco.com

BRKCOL-2611

Continue the Conversation using Cisco Spark

• Sign up free for Cisco Spark at http://www.ciscospark.com/

• Download the application from iOS App Store, Google Play Store, or from http://download.ciscospark.com/

• Visit the World of Solutions Cisco Spark area for demos

• Use Cisco Spark to continue the conversation or ask any additional questions with the speaker for this session. The room name is BRKCOL-2611

• How to get added to the Cisco Spark room for this session

• To opt in, send an email to spark-at-ciscolive@cisco.com with the message “Please add me to the BRKCOL-2611 room”

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.

Agenda

• What customers are facing today

• Microsoft Lync 2010/2013 – Quick Overview (Video Focus)

• Interoperability using Cisco Expressway / VCS

• Single Call Control scenario (CUCILync)

• Office 365 Interoperability

• Summary

Note: for anything else refer to

BRKCOL-2610

Cisco Interoperability with Microsoft, Part 1 – Collaboration

What customers are facing today

Typical customer situation….today!

Two main Independent “Silos” for Audio and Video collaboration.

Cisco

How to

connect them?

Microsoft

TelePresence / Video / PhonesIM/Presence and P2P Audio/Video

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,

DX650…

Microsoft Lync 2010/2013 quick overview (Video Focus)

Video interoperability with Lync 2010

Point to Point video call:

• Uses the RTVideo codec as default

• Single codec supported for interoperability with standard VC is H263(Max resolution is CIF@15fps)

Multipoint video call using Internal A/V MCU:

• Support only 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 create and manage the session.

Video interoperability with Lync 2013

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

Support for H.263 discontinued

Still utilize Microsoft CCCP as proprietary protocol to create and manage the

Multipoint sessions using the A/V MCU

Only one continuous presence layout available (max 5 users with video)

Video interoperability with Skype for Business (SFB)

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

Still utilize Microsoft CCCP as proprietary protocol to create and manage the

Multipoint sessions using the A/V MCU

Only one continuous presence layout available (5 users max with video)

New Server role for Video Interoperability (VIS)

– Provide some kind of “Gateway” function toward SFB

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

Cisco plans to test interoperability with SFB, but no committed date yet

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

if ( (SIP URI) match one of Lync User) then route locally /* Reverse Number Lookup

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

I can ONLY call

a SIP URI…

Video Gateway

Call Routing with Lync 2010/2013User Enabled for P2P calls only (no “Plus CAL”)

Only one possible

routing behavior for

Lync outgoing calls.

Interoperability using the Expressway/VCS Lync Gateway

• Solution designed exclusively for CUCM 9.1 and

above

• No Call Control capabilities

• No additional cost for server software licenses

• New simplified licensing for call sessions (RMS)

VCS X8.x Product Line Options

New

Offering

X8.x

“Expressway C”

Or Core

“Expressway E”

Or Edge

“VCS Control”

No Change

“VCS Expressway”

No Change

VCS Expressway

• Specialized video applications for video-only

customer

• VCS provides full Call Control

• No changes to existing licensing model

VCS and Cisco Expressway Feature Comparison

Feature Cisco Expressway

Series

Cisco VCS

Family

Mobile and Remote Access Y Y

Business to Business Video (B2B) Y Y

Business to Consumer (B2C) with Jabber Guest Y Y

Video Interworking

(H.323<>SIP, Microsoft Interoperability)Y Y

CMR Hybrid Y Y

Video Device Registration & Provisioning

(Cisco and Standards-based 3rd Party Video endpoints)N Y

FindMe capability N Y

A couple of notes before proceeding...

• The main focus here is on CUCM centric scenario, but VCS is still fully

supported as Call Control

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

a valid option

Video Interoperability through Expressway X8.5

CUCM

9.X/10.X

Lync 2013 Client

DX650

SX20, DX80, etc…

H.264 UC-SVC

Lync 2013 Client

B2BUA

H.264 AVC H264 AVC<->SVC

Gateway

Expressway X8.5

(Lync Gateway)

Lync Server

2013

Main Features:

• Interworked calls between H.264 AVC and Lync 2013 H.264 UC-SVC, up to 720p@30fps

• Both 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

• Lync 2010 supported with the same capabilities as before (H263 – CIF@15fps)

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

The “B2BUA” – What is that ?

Point to Point calls use case

Shared Video Endpoint on CUCM – The solution

CUCM

MX300G2

Expressway

Lync Gateway

Sip:mx300g2@video.company.lab

Lync

Server

MX700*@company.lab

*@video.company.lab

Sip:user13@company.lab

TX9000

Media always flows through the Expressway Lync Gateway

Different SIP domains as best practice to avoid possible loops

Caller Identity delivery is crucial to provide the best User

Experience (Ex. callback & caller lookup capabilities)

B2BUA

SIP

Media H264 AVCMicrosoft SIP

Media H264 UC-SVC

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

• Some legacy endpoints might not support URI dialing but they can be called and can provide the Alpha URI as caller identity

• For Additional info on Dial Plan:

• BRKUCC-2008 (Enterprise Dial Plan Fundamentals)

• BRKUCC-3000 (Advanced Dial Plan Design for Unified Communications Networks)

Alpha URI automatic provisioning on CUCM

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

• “Directory URI” field can also be synced from AD/LDAP directory (see slides in the Appendix for more info)

• 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

Calling Video Devices from the Lync Client UI

• For each “shared” Video Device a contact can be created in AD to permit Lync users to search forand call this resource

• A specific AD attribute (msRTCSIP-PrimaryUserAddress) must be populated with the Video Device’s Sip URI

Note: Endpoint Presence available only with VCS as Call Control

Calling Lync Users from the CUCM Devices

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

• The CUCM “Directory URI” field must be populated also for the Lync Users with the relatedLync Client’s SIP address

1

2

3

Personal Video Endpoint on CUCM – Best Practice

• Utilize the CUCM Single Number Reach (SNR) capability

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

• Advanced Feature available for calls extended via SNR:

• Lync’s “in a call” status tracked by CUCM as “Busy” for the user’s line

• Possibility to move the call back to the CUCM’s device after being answered on Lync

• 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:Davide@company.lab

DX80

Sip:Davide@video.company.lab

CUCM

Davide

“Keep It simple”

(Ext. 5001)

Extended Architectures

Internet

Expressway

Lync GW

Lync Edge Server

Expressway-E

Extended Architecture - CUCM with Expressway for B2B

Expressway-CCUCM External Company

(B2B via Standard

SIP/H323)

External Company

(Lync Federation)

Lync Pool

*@company.lab

*@video.company.lab

• Best Practice is to trunk the Expressway Lync Gateway directly with the CUCM

• The same Sip Domain could be used externally on both systems because the SRV records are different:

• _sip._tls.<domain> and _sipfederationtls._tcp.<domain> for Lync

• _sips._tcp.<domain>, _sip._tcp.<domain> and _sip._udp.<domain> for Cisco Solution

• Work in progress to test and document the “Same Domain” scenario with Loop Avoidance Best Practice

Internet

Expressway

Lync GW

Lync Edge Server

Extended Architecture – Lync Remote Access support

CUCM

Lync Pool

Internet

Expressway

Lync GW

Lync Edge Server

Expressway-E

Lync Remote Access support - Media Flow negotiation (1)

CUCM

B2BUA

Lync Pool

TURN

Server

• B2BUA process interworks between Microsoft ICE and Standard ICE

• Expressway-E provides TURN Service to the Expressway Lync GW (TURN client)

• Expressway-C is not involved in the signaling path

• This is only one of the possible media flows (depending on ICE negotiation)

SIP

Media H264 AVCMicrosoft SIP

Media H264 UC-SVC

TURN connection

Expressway-C

Internet

Expressway

Lync GW

Lync Edge Server

Lync Remote Access support - Media Flow negotiation (2)

CUCM

B2BUA

Lync Pool

TURN

Server

• TURN service on Lync Edge could also be used depending on ICE negotiation

• IP Connectivity between Exp. Lync Gateway and Lync Edge must be allowed

• No TURN configuration needed on the Exp. Lync Gateway to “use” Lync Edge

SIP

Media H264 AVCMicrosoft SIP

Media H264 UC-SVC

B2BUA 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.

Connections between the “Lync Gateway” Expressway-C and the Expressway-E must be

permitted through Firewall

Lync Remote Access support – Expressway TURN capabilities

Extended Architecture – Redundancy and Load Balancing

Expressway

Lync GatewayCUCM

Lync

Frontend

• 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

Extended Architecture – Redundancy and Load Balancing

Expressway

Lync GatewayCUCM

Lync

Frontend

• 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

Multipoint calls use case

Multiparty Call Use Case (Cisco CMR)

CMR Cloud

Hosted by Cisco WebEx

Collaboration Cloud

CMR Hybrid

TelePresence on Premises

plus Cisco WebEx

CMR Premises

TelePresence infrastructure @

Customer Datacenter

BOARDROOMBROWSER

CUCM

SIP

Media H264 AVC

Expressway

Lync Gateway

Microsoft SIP

Media H264 UC-SVCLync

Server

Lync and CMR Premise/Hybrid Interoperability - Architecture

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

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

Prominent

Single

Screen

Lync and CMR Interoperability – Joining Experience

• Scheduled Conferences

Users can schedule a meeting by:

o Using the TMS Smart Scheduler web GUI (CMR Premise and CMR Hybrid)

o Using the Webex Productivity Tools Outlook plugin (CMR Hybrid only)

Lync users can join a Cisco conference by just clicking on the hyperlink in the meeting invite (the

protocol handler «sip:» is included in the associated URL)

• Personal CMR (always on, permanent address)

Meeting Host can send his Personal CMR address in the calendar invite

Users will copy/type the meeting address (URI) into the Lync client to join the meeting

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

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

Multiparty Call Use Case (Cisco CMR)

CMR Cloud

Hosted by Cisco WebEx

CMR Hybrid

TelePresence on Premises plus

Cisco WebEx

CMR Premises

TelePresence infrastructure @

Customer Datacenter

BOARDROOMBROWSER

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*

*Lync support not released yet, planned for next major release

For further details –

PSOCOL-1406 (CMR Cloud Overview)

Internet

Expressway

Lync GW

Lync Edge Server

Expressway-E

CMR Cloud – Architecture for Lync interoperability

Expressway-CCUCM

Lync Pool

Customers can have both Cisco and Microsoft, but each solution must use his own Firewall Traversal

technology to reach CMR

Cisco WebEx Cloud

Webex Mobile Client

Webex Desktop Client

(Future Release, Subject to Change)

Desktop Sharing (DS) 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 Endpoints

Content Channel (BFCP)

Video Channel

SIP/BFCP Endpoints SIP/BFCP Endpoints

In a separate channel

(BFCP) – so the receiver

can control the layout and

negotiate different resolution

for the content

SIP Endpoints

(NO BFCP)

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

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

Cisco & Microsoft RDP interoperability(Today’s status)

• Cisco uses BFCP – the Standard Protocol for Desktop Sharing in the video world

• MSFT uses RDP for Desktop Sharing between Lync devices

• Today’s status - Lync can receive content embedded in video from standard-based endpoints and MCU (see previous slide for details)

Content Channel

Video Channel

Lync RDP EndpointsSIP/BFCP Endpoints

Two way HD video

One way content share (content in main video channel)

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

Cisco & Microsoft RDP interoperability(Today’s status)

Lync 2013 receving Video & Content in a CMR session («Content in Main Video»)

Content Channel

Video Channel

Cisco & Microsoft RDP interoperability(Future Release, Subject to Change)

Lync RDP EndpointsSIP/BFCP Endpoints

Two way HD video

Two way content share

Content Channel

Video Channel

Lync RDP EndpointsSIP/BFCP Endpoints

Content Share

to Lync

(as today)

Content Share

from Lync

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

Cisco & Microsoft RDP interoperability Planned Architectures (Future Release, Subject to Change)

Unified CM or VCS

TS

Lync 2013 User

Lync 2013 Server

SIP/BFCP endpoint

Company B Microsoft Lync

Company A Cisco

Internet

CMR Cloud

Service

Cisco Expressway

SVC-AVC + RDP Gateway

CMR Cloud:

Now adding:

• Lync A/V interop

• RDP/BFCP interop

CMR Premises:

• Cisco Expressway is the “Lync Gateway”

• Lync A/V interop

• Now adding RDP/BFCP interop

• No additional transcoder required

Expressway

• Lync 2013 client with 2013 Server

• RDP interop on a single Expressway/VCS (no cluster)

• Lync 2013 client shares/receives content or desktop in a CMR session

• Remote Lync 2013 client shares / receives content or Desktop (Lync Edge support)

• ~33 concurrent content sessions on large VMdepending on desktop size and quality of video call

• ~10 concurrent content sessions on medium VM depending on desktop size and quality of video call

Cisco & Microsoft RDP interoperability RDP status @ FCS release (Subject to Change)

Supported

• Lync 2010 client with 2013 Server

• Skype for Business client with 2013 Server

• Lync 2013 client shares / receives content in point-to-point call (local composition) with TC endpoint (MX Series, EX Series, SX20, C series)

• Lync 2013 client shares / receives content in point-to-point call (content in main) with DX series

• Application sharing from Lync (scalability still TBD)

Feature Preview

Cisco Jabber & Lync Interoperability

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

CUCM A/V

LYNC Pool

IM/P Domain:

company.lab

A/V Domain:

video.company.lab

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

Xmpp: jabber_user@company.lab

Sip: Lync_user@company.lab

Sip: jabber_user@video.company.lab

Expressway

“Lync Gateway”

CUCM IM/P

A/V and IM/P domain:

company.lab

A/V SessionIM Session

SIP registrationXMPP Registration

• Lync can’t split a route for a single domain to two separate addresses for IM/P and A/V

• Jabber users needs therefore two different addresses:

• one for IM/P (Jabber_user@company.lab)

• one for A/V (Jabber_user@video.company.lab)

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

SIP

IM

/P in

vit

e (

4)

Expressway Lync Gateway

Lync Server

Expressway Directory

CUCM / IM&P

IM/P and A/V Interop with Jabber – The Solution (1)

CUCM / AV

SIP

IM

/P s

es

sio

n (

5)

• Expressway “Directory” with a CPL script splits the SIP traffic between IM/P and A/V

• Once the session is established it removes itself from the path

SIP AV invite (2)

SIP

AV

in

vit

e

(3b

)

Expressway Lync Gateway

Lync ServerExpressway Directory

CUCM / IM&P

CUCM / AV

IM/P and A/V Interop with Jabber – The Solution (2)

• Jabber and Lync can share the same domain for IM/P and A/V

• One single contact for each user in the buddy list on both side

• This is in a Pilot Stage today:

• Scalability testing still ongoing

• Loop Avoidance best practice TBD

• New paragraph added to the “Expressway Lync Deployment Guide”

Single Call Control scenario (CuciLync)

SIP Trunk

CUCM

DX80

MX200G2

DX650

TelePresence

Server (TPS)

CUCILYNC

VCS

CUCILYNC

DSP on ISR

Third Party VC

(H323)SIPH.323

SCCP

Lync Pool

2010/2013

Single Call Control (Voice & Video) using CuciLync

• Lync Client used only for IM & Presence

• CuciLync client behaves like any other endpoint registered to CUCM

• Standard based call control for Audio and Video (No Hairpinning or Transcoding)

• Single Dial Plan (no routing between Lync & CUCM)

Third Party VC

(SIP)

Voicemail, MRA support,

Softphone / Desk Phone control

Cisco UC Integration

Microsoft Lync 2010

Microsoft Lync 2013 (shown)

Office 365

Toolbar docks at the top, auto hides

Maximize Screen Real-estate

Can be disabled if needed

Initiate Call from Context Menu

Initiate Call from Dock

Cisco UC Integration for Lync (CuciLync)

Jabber in Phone Mode – an alternative to CuciLync….

• Windows, Mac, iOS, Android Support

• Latest Jabber features (same code)

• Doesn’t require Cisco Presence server

• Simplified migration to Jabber Full Mode

• Separate clients (no direct integration with Lync)

• Possibility to disable Outlook Integration for coexistence with the Lync client on the desktop

Office 365 Interoperability

Microsoft Lync Online – Office 365Overview

• Lync IM, Presence, A/V calling and Web conferencing capabilities

• PSTN connectivity through third-party providers for Conference Dial-in

• Closed community – no standards based interoperability (see next slides)

Lync Online (O365) and A/V InteroperabilityWhat about the Hybrid «Split Domain» scenario?

InternetCUCM

H.264 AVC

H.264 SVC

SIP B2BUA

MSFT Federation

Expressway

Lync GW

O365 Lync Online

Back End

Lync Online

“Edge”

• Lync features delivered through a combination of On-premises and Online deployment.

• Lync Online and On Premise users share the same “Presence Domain”

• All workloads for a given user handled in one environment

• An option could be to use the Lync On-Premise deployment as a “gateway” towards Lync Online

• This scenario has not been tested and is not officially supported from Cisco

Lync

Servers

Lync Edge

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

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

• Other vendors have released basic interoperability appearing to O365 as another Lync on-prem system.

• Work in progress to support Office 365 joining Cisco CMR cloud (see next slide)

Lync Online (O365) and A/V InteroperabilityWhat about B2B «Federation» ?

InternetExpressway-E

Lync Online (O365) and A/V Interoperability

Expressway-CCUCM

• The Lync Online deployment must be enabled for External Federation

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

Cisco WebEx Cloud

Webex Mobile Client

Webex Desktop Client

O365 Lync Online

CMR Cloud support (Future Release, Subject to Change)

InternetExpressway-EExpressway-CCUCM

• CuciLync is fully supported with Lync Online, being a client side integration

• Currently tested with Lync 2010 and Lync 2013 client. SFB client testing timeline TBD.

O365 Lync Online

Lync Online (O365) interoperabilityClient side integration

CUCILync

Summary

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

Continue Your Education

• Demos in the Cisco campus (Collaboration Area)

• Table Topics (Wednesday, 12.00 – 13.00)

• Meet the Engineer 1:1 meetings (Fabio Chiesa, Tobias Neumann)

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

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 though the Cisco Live mobile app or your computer on Cisco Live Connect.

Cisco is fully committed to Interoperability with Microsoft

Thank you

Appendix

Expressway Solution«Point to Point calls use case»

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 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

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”)

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

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: Davide@company.lab

Associated device: EX60@video.company.lab

Lync Client

Sip:Davide@company.lab

VC EX60

Sip:EX60@video.company.lab

Davide

1

2

VCS Lync

Gateway

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

VCS X8.1

(Lync GW)

Lync 2013

EX60@video.company.lab Davide@company.lab

Call

Davide

FindMe Associated Device

Davide@company.lab EX60@video.company.labDavide@company.lab

Personal Video Endpoint on VCS – VCS to Lync call

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. 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

SX20@video.company.lab

VCS X8.1

(Lync GW)

Lync 2013

Fabio@company.lab

EX60@video.company.lab Davide@company.lab

Call

Davide

FindMe Associated Device

Davide@company.lab EX60@video.company.lab Davide@company.lab

Personal Video Endpoint on VCS - Lync to Lync call

1. Fabio calls Davide on his main identity alias (Davide@company.lab)

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

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.

Extended Architecture – Redundancy and Load Balancing

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.

Extended Architecture – Redundancy and Load Balancing

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.

Expressway Solution «Multipoint calls use case»

Transparent name labels

Active Speaker Indicator Overflow indicator Audio participant avatar Recording Indicator

Lync and CMR Interoperability – TPS New Features

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...)

top related