Microsoft Lync 2010: Interoperability, Integration with Competition or Legacy

Francois DoremieuxProgram ManagerMicrosoft Corporation

EXL317

Adam GentPrincipal Consultant

Datapulse

Agenda

Brief summary of key principles: interop by designLync 2010 interoperability in practice

Video room systems interoperabilityIP-PBX interoperability

Media bypass support in Lync 2010What is it and how does it work

Example: Interoperability with Cisco CallManager and/or Cisco ISRSingle siteMultiple sites, central call control

Migration approaches

Q&A

Agenda

Brief summary of key principles: interop by designLync 2010 interoperability in practice

Video room systems interoperabilityIP-PBX interoperability

Media bypass support in Lync 2010What is it and how does it work

Example: Interoperability with Cisco CallManager and/or Cisco ISRSingle siteMultiple sites, central call control

Migration approaches

Q&A

Principles and industry engagement, rich (Windows and Mac) and reach (WebApp) clients cross platforms, XMPP and IM/P interop, phones (native and third party interop program), peripherals…

TechEd New Orleans 2010: UNC321TechEd Berlin 2010: UNC202

Protocol documentationhttp://msdn.microsoft.com/en-us/library/cc307432.aspx

UC Open Interoperability Programhttp://technet.microsoft.com/ucoip

“Optimized for” deviceshttp://technet.microsoft.com/en-us/bb970310.aspx

UCIFhttp://ucif.org

Microsoft UC: Interoperability by DesignWhere to find details

Agenda

Brief summary of key principles: interop by designLync 2010 interoperability in practice

Video room systems interoperabilityIP-PBX interoperability

Media bypass support in Lync 2010What is it and how does it work

Example: Interoperability with Cisco CallManager and/or Cisco ISRSingle siteMultiple sites, central call control

Migration approaches

Q&A

High quality video in every

desktop

Improve the meeting

roomexperience

Lync Video StrategyHigh quality video in every desktop

High resolution at low cost

Single client experience

Integration with applications

Embrace and lead interoperability

Connect and integrate all legacy rooms (via gateways)

Foster innovation in endpoints natively interoperable with Lync

Develop on market standards and contribute to success of UCIF

Improve the meeting room experience

Simplify and enrich user experience

Expand reach and usage

Improve productivity

Embrace and Lead

Interoperability

Video Interoperability Program

announcement

New: Video Interoperability ProgramAllow partner solutions to make and accept video calls with Lync 2010 (or OCS 2007 R2)

Direct registration to Lync for partner VTC/telepresence and/or MCUGateways to connect any industry-standard VTC/telepresence and/or MCU to Lync

ProcessPartners submit solutions to Microsoft for qualificationQualified partner solutions will be listed on the Microsoft website

RequirementsOCS 2007 R2:

Enhanced security, point-to-point video, firewall traversalLync 2010:

Enhanced security, point-to-point video, firewall traversalRTVideo (HD), multiparty video on Lync MCU

Secure registration with “lowest common denominator” P2P

SIP registrationNTLM authentication or trusted serverSecure signaling (TLS)Wideband audioH.263 (CIF) interopPresence publishing

Lync 2010: Video InteroperabilityTechnical scope

Firewall traversal and secure media for P2P

Firewall transversal (ICE v19)Secure calls (SRTP)

Seamless interop:partner video systems as highly capable Lync endpoints for rich, high quality multiparty calls between OC and partner solution

RTVideo – CIF, VGA, HDCCCP for AVMCU support

Partner Approaches

VTC Direct RegistrationVTC register directly to Lync (or OCS 2007 R2)Multiparty calls on Lync AVMCU (where supported)VTC endpoints appear as contacts to Lync usersUsers can take advantage of existing Lync functionality

Click to call, drag and drop, right-click…

Committed partners:Polycom, Lifesize

Gateway/MCUGateway pass-through, Gateway/MCUUsers meet in virtual rooms for multiparty calls (hosted on partner MCU)Virtual rooms appear as contacts in LyncLegacy VCS/telepresence interoperability, multiple views, transcodingCommitted partners:

Polycom, Lifesize, Radvision

Cisco Telepresence Interoperability

As of today, Cisco does not have any qualified solutionOCS 2007 R2: in processLync: ask Cisco/Tandberg

Cisco/Tandberg planned interop through their gatewaysVCS gateway for signalingTandberg “Advanced Media Gateway” for media transcoding

Need both to get HD video

Two more VCS (control, expressway) to work across firewall

Recommended approach: use partner gatewayPolycom, Radvision

Radvision: gateway based interoperability with Lync

demo

Radvision Scopia Gateway – Point to Point Call

Lync Server

Signaling Video Codec

RTVideoH.264

H.323

SIP/TLS

H.323 Endpoints Lync

GatewayOther Lync

Radvision GW

Radvision Iview Server

Registration, call routing, presence

Lync AVMCU

Registration, call routing, presence

Registration

RTVideo

SIP/TLS

Radvision Scopia Gateway – Point to Point Call

Lync Server

Signaling Video Codec

RTVideoH.264

H.323

SIP/TLS

Lync

GatewayOther Lync

Radvision GW

H.323 Endpoints

Radvision Iview Server

Registration, call routing, presence

Lync AVMCU

Registration, call routing, presence

Registration

RTVideo

SIP/TLS

Something is missing here…What is it?

That’s right,no HW MCU!!!

Radvision Scopia Gateway – Virtual Room

Lync Server

Signaling Video Codec

RTVideoH.264

H.323

SIP/TLS

Lync

GatewayOther Lync

Radvision GW

Video Endpoint

Radvision Iview Server

Registration, call routing, presence

Lync AVMCU

Registration, call routing, presence

Registration

RTVideo

SIP/TLS

HW MCU

Video Endpoint

Virtual Room Demo – Participating Rooms

iVIEWSCOPIA Elite MCU

SCOPIA Video Gateway

RADVISION XT1000

Lync Clients

Tandberg C20 Polycom HDX 4000

RADVISION VC240Cisco CTS 3000RADVISION TP

LifeSize Room 200

Customer TestimonialRadvision Scopia Early Adoption Program

Yannick FlegeauCredit Agricole

customer

Agenda

Brief summary of key principles: interop by designLync 2010 interoperability in practice

Video room systems interoperabilityIP-PBX interoperability

Media bypass support in Lync 2010What is it and how does it work

Example: Interoperability with Cisco CallManager and/or Cisco ISRSingle siteMultiple sites, central call control

Migration approaches

Q&A

IP-PBX InteroperabilityPain points in OCS 2007 R2

Interoperability via Direct SIP (OIP qualification)Very broad range of PSTN gateways, Direct SIP to IP-PBX

However, in R2 Direct SIP requires routing media through Mediation Server

Not a significant problem for central sitesBut difficult in branches:

Requires Mediation Servers in branches and/orMedia tromboning (hairpin through the WAN to Mediation Server in central site)

OIPqualifiedIP-PBX

PBX end-points

OCS pool

OCS end-points

MediationServer

MediaSignaling

IP-PBX Interoperability in OCS 2007 R2Direct SIP to IP-PBX

OIPqualifiedIP-PBX

capable ofbypass

PBX end-points

Lync poolwith

MS role

Lync end-points

MediaSignaling

IP-PBX Interoperability in LyncDirect SIP to IP-PBX with media bypass

Removes need for media transit via a serverSignaling continues to transit through Mediation

B2BUA: security demarc, interop…

Media goes directly from Lync client to next hop (gateway, IP-PBX)Quality optimization (latency reduction, codec selection, media resiliency)

Based on location of Lync clientBypass only occurs if client is “local” to next hop

G.711 direct – optimized for LAN-like conditions; SRTP supported

When client is not “local”, media goes through MediationCodec optimized for WAN using per session CAC; RTANB over internetMediation provides audio healing

Enables “lightweight” Mediation (collocation with FE, SBA)

Lync 2010: Media BypassWhat it is and benefits

“Always Bypass” in “Global Settings”Treats deployment as a single site, requires good connectivityMutually exclusive with Call Admission ControlWill always bypass to trunks enabled for bypass

“Use Sites and Region Configuration”Leverages topology information in Lync from CAC

Uses Region/Sites definition, requires a “Bandwidth Policy Profile”Associates unique Bypass ID with each Region/Site

Uses dynamic (real time) client locationClient IP address Bypass ID associated with client’s locationGateway address (for media) Bypass ID of the gateway’s location

Comparison of the IDs, bypass if the two IDs match

Lync 2010: Media BypassHow it works – two approaches

Lync 2010: Media BypassHow it works – two approaches

Inbound calls (to Lync)Mediation receives invite; IP address of media gateway in SDP

Potentially different from centralized call management (signaling) IP

Mediation computes gateway Bypass ID, puts it in SDP, forks invite to clientsClient makes bypass decision

Outbound calls (from Lync)Client puts its Bypass ID (from inband) in SDP, sends to MediationMediation finds gateway, determines gateway Bypass ID

Uses representative (“alternate”) media IP if configured, or uses IP associated with GW FQDN if not (signaling IP used for media – single site)

Mediation Server compares, call is bypassed if matches

Lync 2010: Media BypassInbound and Outbound logics

Survivable Branch Appliances qualified, all support bypass5 partners – Audiocodes, Dialogic, Ferrari, HP, NET

Gateways (not all support bypass – see OIP page)Cisco ISR series 28xx, 29xx, 38xx, and 39xxAvaya 23xx and 41xxGateways from Media5, Nuera, and Quintum

IP-PBX (not all support bypass – see OIP page)Cisco 4.x, Cisco 6.1, Cisco 7.1 and Cisco 8.x Avaya CM/Aura 4.x, Avaya CM/Aura 5.xAvaya CS1k 5.x, Avaya CS1k 6.x Alcatel Lucent 9.x, Siemens 3.1RxMitel, Genband, Aastra, and Huawei

Testing and Qualification for Lync InteropOpen Interoperability Program – tested or in process of testing

Agenda

Brief summary of key principles: interop by designLync 2010 interoperability in practice

Video interoperabilityClient videoVideo room

IP-PBX interoperabilityMedia bypass support in Lync 2010Example: Interoperability with Cisco CallManager and/or Cisco ISR

Single siteMultiple sites, central call control

Migration approaches

Q&A

Media Bypass with Cisco IP-PBX (CUCM)Single site

HQ Site

Mediation

Ciscophone

LyncEndpoint

Gateway

CUCM (MTP)

G.711

Lync(w/ Mediation Service)

Provisioning media bypass with CUCM 4.1.3 SR8Single site configuration

demo

Demo Setup – Single Site

Step 1: setting up Lync for media bypass interop

Review topology in topology builderRun Powershell script to:

Create trunk and build routeCreate number normalizationAssign policies

Verify script results in Lync Control Panel

Step 2: setting up CUCM for media bypass interop

Create trunkCreate route pattern and associate to trunk

Step 3: place a call and verify media bypass

Centralized IP-PBX with multiple sitesIP-PBX centralized in HQ for signaling and call control

Mediation talks to centralized instance

Local media gateways in branch sites (ex: Cisco ISR with MTP)Want to bypass media to local gateway when Lync is in the branch site

Lync supports media bypass in multiple sitesDefine regions and sites in network topology (same as CAC)Define (virtual) media gateways in topology builder

Associate representative media IP in site to each media gatewayDepending on specific IP-PBX requirements, different listening ports

Establish appropriate routing on both systemsIP-PBX unaware of Lync dynamic location; suggest routing to local trunk

Media Bypass – Multiple Sites, Centralized SignalingWhat’s different

Media Bypass – Multiple Sites, Centralized SignalingWhat’s different

Media Bypass with CUCMIn-branch call between Lync endpoint and Cisco phone via branch MTP

CUCM (MTP)

Lync

Mediation

PSTNPBXEndpoint

LyncEndpoint

LyncEndpoint

Gateway

WAN

Ciscophone

ISR (MTP)

G.711

HQ Site Atlanta Branch

Media Bypass with CUCMIn-branch call between Lync endpoint and Cisco phone via branch MTP

CUCM (MTP)

Lync

Mediation

PSTNPBXEndpoint

LyncEndpoint

LyncEndpoint

Gateway

WAN

Ciscophone

ISR (MTP)

G.711

Call stays up

HQ Site Atlanta Branch

No Media Bypass for Calls on WANWAN call between Lync in branch and Cisco phone via central MTP

CUCM (MTP)

Lync

PSTNPBXEndpoint

Lyncclient

Lyncclient

Gateway

Ciscophone

ISR (MTP)

WAN

G.711

Mediation

RT Audio Narrowband

HQ Site Atlanta Branch

Provisioning media bypass with CUCM 4.1.3 SR8Multiple sites configuration

demo

Demo Setup – Centralized IP-PBX, multisite

Media Bypass with IP-PBXBranch call with local resiliency

CUCM (MTP)

Lync

Mediation

PSTNPBXEndpoint

LyncEndpoint

LyncEndpoint

Gateway

WAN

PBXEndpoint

ISR (MTP)

G.711

Lync SBA

HQ Site Atlanta Branch

A migration and coexistence plan with CUCM and ISR

Topology with CUCM and ISRISR used as GW by both CUCM and Lync

Used for PSTN calls by both “PBX”Including media bypass to ISR

Direct SIP between CUCM and Lync

Used for extension calls by both “PBX”Including media bypass to CUCM

Migrate users stepwise

CUCM (MTP)

ISR (MTP)

Lync

A migration and coexistence plan with CUCM and ISR

Takeaway

Integrating natively with IP-PBXs canEnable a low cost Proof of ConceptProvide calling between migrated and non-migrated usersAllow for long term coexistence with existing IP-PBX starting to take advantage of Lync

Native integration with media bypass enablesCPE-less deployment of Lync in branches coexisting with existing IP-PBX, using existing equipmentKeeping much more of the media local, including in centralized multisite topologies

thank you – any questions?

© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to

be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS

PRESENTATION.

backup slides

Topology Builder

Powershell script# Create Trunk ConfigurationNew-CsTrunkConfiguration -Identity 'Service:PstnGateway:cucm41.contoso.com' -ConcentratedTopology $true -Description 'CUCM 4 at London Site' -EnableBypass $true -EnableReferSupport $false -EnableSessionTimer $true -EnableSignalBoost $false -RTCPActiveCalls $false -RTCPCallsOnHold $false -SRTPMode 'NotSupported'

# Create Translation Rules for Outgoing CallsNew-CsOutboundTranslationRule -Identity 'Service:PstnGateway:cucm41.contoso.com/3 Digit Numbers to CUCM Dialable' -Description 'Convert E164 to CUCM 3 Digit Format' -Pattern '^\+(\d{3})$' -Translation '$1' -Priority 1New-CsOutboundTranslationRule -Identity 'Service:PstnGateway:cucm41.contoso.com/UK Numbers to CUCM Dialable' -Description 'Convert E164 to CUCM National Digit Format' -Pattern '^\+44(\d+)$' -Translation '0$1' -Priority 2 New-CsOutboundTranslationRule -Identity 'Service:PstnGateway:cucm41.contoso.com/International Numbers to CUCM Dialable' -Description 'Convert E164 to CUCM International Digit Format' -Pattern '^\+(\d*)$' -Translation '00$1' -Priority 3

New-CsOutboundTranslationRule -Identity 'Service:PstnGateway:cucm41.contoso.com/Extension to CUCM Dialable' -Description 'Convert E164 to CUCM Extension Digit Format' -Pattern '^\+44207946(8\d\d\d)$' -Translation '$1' -Priority 0

# Create PSTN UsageSet-CsPstnUsage -Identity global -Usage @{add='All Calls'}

# Create Voice RouteNew-CsVoiceRoute -Name 'All Calls' -Description 'Route all calls via the CUCM4 in London' -NumberPattern '^\+' -Priority 0 -PstnGatewayList @{add='PstnGateway:cucm41.contoso.com'} -PstnUsages @{add='All Calls'}

# Create Voice Policy New-CsVoicePolicy -Identity 'Site:London' -AllowCallForwarding $true -AllowPSTNReRouting $true -AllowSimulRing $true -Description 'Policy for all London Users' -EnableBWPolicyOverride $false -EnableCallPark $true -EnableCallTransfer $true -EnableDelegation $true -EnableMaliciousCallTracing $true -EnableTeamCall $true -PreventPSTNTollBypass $false -PstnUsages @{add='All Calls'}

# Create Dial Plan for London SiteNew-CsDialPlan -Identity 'Site:London' -SimpleName LondonSiteDialPlan

# Create Normalization Rules for users in the London SiteNew-CsVoiceNormalizationRule -Identity 'Site:London/UK' -Pattern '^9?0(\d*)$' -Translation '+44$1' -Description 'Convert UK Numbers to E164' -IsInternalExtension $false -Priority 1New-CsVoiceNormalizationRule -Identity 'Site:London/International' -Pattern '^9?00(\d*)$' -Translation '+$1' -Description 'Convert International Numbers to E164' -IsInternalExtension $false -Priority 2New-CsVoiceNormalizationRule -Identity 'Site:London/CUCM4Exts' -Pattern '^(8\d\d\d)$' -Translation '+44207946$1' -Description 'Convert International Numbers to E164' -IsInternalExtension $false -Priority 0

# Remove default Normilization Rule for London SiteRemove-CsVoiceNormalizationRule -Identity 'Site:London/Prefix All'

# Create Dial Plan for CUCM 4New-CsDialPlan -Identity 'Service:PstnGateway:cucm41.contoso.com' -SimpleName CUCM4SiteDialPlan

# Create Normalization Rules for inbound calls for CUCM 4New-CsVoiceNormalizationRule -Identity 'Service:PstnGateway:cucm41.contoso.com/UK' -Pattern '^9?0(\d*)$' -Translation '+44$1' -Description 'Convert UK Numbers to E164' -IsInternalExtension $false -Priority 1New-CsVoiceNormalizationRule -Identity 'Service:PstnGateway:cucm41.contoso.com/International' -Pattern '^9?00(\d*)$' -Translation '+$1' -Description 'Convert International Numbers to E164' -IsInternalExtension $false -Priority 2New-CsVoiceNormalizationRule -Identity 'Service:PstnGateway:cucm41.contoso.com/CUCM4Exts' -Pattern '^(8\d\d\d)$' -Translation '+44207946$1' -Description 'Convert International Numbers to E164' -IsInternalExtension $false -Priority 0

# Remove default Normilization Rule for CUCM 4 PolicyRemove-CsVoiceNormalizationRule -Identity 'Service:PstnGateway:cucm41.contoso.com/Prefix All'

# Configure User to enabled for EV and set Line URISet-CsUser -Identity 'contoso\adamg' -EnterpriseVoiceEnabled $true -LineURI 'tel:+442079468500'

Dial Plan Configuration

Dial Plan Configuration - Site

Dial Plan Configuration – CUCM

Voice Policy

Voice Policy - Site

Route

Route – All Calls

PSTN Usage

PSTN Usage – All Calls

Trunk Configuration

Trunk Configuration - CUCM

User Configuration

CUCM Configuration – SIP Trunk

CUCM Configuration – Route Pattern

Step 2 in R2: setting up CUCM for media bypass interop

Create partition(s)Create calling search space(s)Create translationsCreate trunkCreate route pattern and associate to trunk

Resources

www.microsoft.com/teched

Sessions On-Demand & Community Microsoft Certification & Training Resources

Resources for IT Professionals Resources for Developers

www.microsoft.com/learning

http://microsoft.com/technet http://microsoft.com/msdn

Learning

http://northamerica.msteched.com

Connect. Share. Discuss.

Complete an evaluation on CommNet and enter to win!

Scan the Tag to evaluate this session now on myTech•Ed Mobile

© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to

be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS

PRESENTATION.